Closed monfresh closed 9 years ago
Enumerations such as accessibility should be optional and in a separate table. This allows for domain specific or location specific folksonomies. OpenReferral defines a core set of elements. Profiles will implement domain or location specific values.
That being said, we can incorporate these values in an example "San Mateo County" profile.
There's probably a limited set of accessibility options, so just like we define an accepted set of "types" for Phone (voice, fax, or tty), couldn't we do the same for accessibility?
added in datapackage.json
These should be part of the standard. A good starting point could be the ones we've used for SMC: https://github.com/codeforamerica/ohana-api/wiki/Populating-the-Postgres-database-from-a-JSON-file#accessibility