specification
specification copied to clipboard
The Human Services Data Specification - a data exchange format developed by the Open Referral Initiative
An issue has come up in [discussions over the API specification](https://apievangelist.com/2017/07/17/making-all-sub-resources-available-within-the-core-set-of-human-service-apis/) over whether HSDS should describe a 'sanctioned' way of representing services, organizations and locations as nested objects, containing the...
Are there any example datasets (that match the 1.0 spec!) available on the web? Would be great to have those linked from http://openreferral.org/.
As schema.org is a widely applicable standard it would be great to see this added to the documentation. This has already been suggested in https://github.com/codeforamerica/OpenReferral/issues/67#issuecomment-70290794.
Related to #492 as it relates to schedule. We may need to provide more explicit support (either guidance or models) for Events in the standard. Events can be tricky to...
Related to #493 and #492 as pertains to events and scheduling, and would be dependant on those conversations taking place. There have been discussions about the fitness of the current...
Continued from https://github.com/openreferral/api-specification/issues/20 This likely intersects various facets of the specification: data modelling, API specification (for API behaviour), and guidance for publishers.
It'd be useful to establish some sort of heuristic or guidance as to where the "limits" of the specification are vs what should go in a Profile. There are different...
We currently host our documentation on readthedocs, which is an instance of sphinxdocs. #448 flags that some behaviours (ie redirections for older versions) throw up some error pages which may...
Continued from https://github.com/openreferral/api-specification/issues/34 How should platforms exchanging HSDS data audit and control access? What facilities should be specified by our API spec?