-
In the [Controlled Vocabulary](https://github.com/codeforamerica/OpenReferral/blob/master/Human%20Services%20Data%20Specification%20%20v1.0.md#a-controlled-vocabulary-for-human-services-data) section,…
-
The way I'm reading the spec, it looks like both physical and mail address are required for every location. And every service requires a location, thus, no web-based or phone-based locations (ie. virt…
-
Since each CSV file is meant to contain multiple rows, the file names should be pluralized to better represent their contents.
-
This is just a question, but in some of the work I've been doing recently we're trying to model these things and its quite useful to have a `type` field (or perhaps category) that describes what kind …
-
-
There are no keys linking postal_address/physical_address to organizations. In airtable, I've added an organization_id field to both address tables in order to create example data.
-
There is no key linking holiday_schedule to organizations. In airtable, I've added an organization_id field to holiday_schedule table in order to create example data.
-
I was sure in the documentation prior to its new home there was an entity called taxonomy_service that allowed a one-to-many association. It's fields were: id, service_id, service_name, taxonomy, axon…
-
We can now specify that a given column must be one of several values in core JSON Table Schema. We can use the "enum" constraint for this:
http://specs.frictionlessdata.io/json-table-schema/#field-…
-
On https://github.com/openreferral/specification/blob/master/datapackage.json#L4
Currently, `license` is defined to as a string or object, not an array:
> `license` is an object OR string. The v…