specification
specification copied to clipboard
The Human Services Data Specification - a data exchange format developed by the Open Referral Initiative
The HSDS [objects and fields reference documentation](http://docs.openreferral.org/en/latest/hsds/reference/#objects-and-fields) currently does not list acceptable values for enum fields (or denote that these fields are enums at all) as described in the datapackage.json...
The EU have been working on a data model to describe Public Services. This may have some strong overlaps with the idea of Human Services. During work on 1.1 or...
`payments_accepted` sounds like it could be a boolean field that denotes whether or not payments are accepted, whereas that ambiguity does not exist when the field is named `accepted_payments`. Moreover,...
Leaving this open for interpretation is dangerous, especially when it is important to have well-structuredservice areas defined for purposes of searching/sorting/filtering the data that might serve a help-seeker. Rather than...
Has there been consideration of including a flat, single-sheet data model in the core OR spec, similar to what was described in [Introducing the Humanitarian Service Data Model](https://openreferral.org/introducing-the-humanitarian-service-data-model/)?
Not an issue but rather a 'help wanted' : Is anyone aware of code generators for datapackage.json files? I am thinking of something that you feed it the datapackage.json file,...
I recently connected with @danbri, who suggested that we look into [the CSV-on-the-Web](https://www.w3.org/2013/05/lcsv-charter.html) metadata vocabulary. This may be less relevant for the API-related use cases that we've recently been discussing....
In the [Open Referral Legal Services](https://openreferral.org/?s=legal&submit=Search) working group call the issue came up of organisations that are only able to offer a particular service for a set period of time....
Regarding the service_taxonomy table, the taxonomy_details field describes allowing linked Terms (two terms used together to make a compound term) but still implies a single Taxonomy ID from the service_taxonomy...
We have a highly structured alternate name system that includes individual entries for multiple alternate names (AKAs), former names with dates of change, and legal names. I wouldn't necessarily argue...