-
Adding the ability to manage taxonomies, so we can search against them.
- Issue: https://github.com/openreferral/api-specification/issues/73#issuecomment-427621557
- OpenAPI: https://gist.gith…
-
I started focusing on HSDA search features during the latest push of the specification. This work spans multiple HSDA services, but focuses on expanding and standardizing the search interface for HSDA…
-
now that we have a taxonomy system for adding, editing, and managing taxonomy. We can add back sub-elements of taxonomy to the full results, and add endpoints for /services/taxonomy. These are option…
-
Adding page count headers for each of the core resources (organization, locations, and services).
- Issue: https://github.com/openreferral/api-specification/issues/82#issue-367517429
- OpenAP…
-
Adding postal code search for HSDA, allowing searching using proximity across all core resources.
- Issue: https://github.com/openreferral/api-specification/issues/46#issuecomment-427619061
-…
-
Adding postal code search for HSDA search, allowing searching using proximity across all core resources.
- Issue: https://github.com/openreferral/api-specification/issues/46#issuecomment-4276191…
-
Version 1.1 of HSDS did not have NAME as a required field in LOCATION.
Version 1.2 of HSDA introduces NAME as a required field in LOCATION at line 637 of https://github.com/openreferral/api-specifi…
-
Adding proximity search for HSDA Search, across all the core resources (organization, locations, and services).
- Issue: https://github.com/openreferral/api-specification/issues/46#issuecomment…
-
I want to introduce this thread to overlap with discussions around data filtering #22, schema filtering #21, response structure #6, and hypermedia #7.
Basics of content negotiation would be, do we …
-
I am working on a JSON schema for HSDS, and for HSDA.
I already have an API for validating an API path or JSON snippet against any JSON schema when ready. Will release as extra set of API paths.
…