-
I will be moving the /search option beyond just returning locations, and give it a collection of organizations, locations, services, and contracts.
I will also give /search an /everything, so that …
-
I'd like to introduce guidance for messaging. Suggesting it is a standalone layer to the system that other areas use. To suppor the approval, and other aspects of the system we will need messaging.
…
-
Generate a JSON schema from the v2.01 [datapackage.json](https://github.com/openreferral/specification/blob/master/datapackage.json)
-
Hey @kinlane , related but different than https://github.com/openreferral/api-specification/issues/46
I have some major concerns with the current definition of the Search parameters found here: htt…
-
In the error response definition the description of the message field seems to contradict the field type. I suggest we change the type of message to be a string to allow for more descriptive error mes…
-
The requests below should be specified for the physical addresses of a specific location, but in [openapi-hsda.yaml](https://github.com/openreferral/api-specification/blob/master/_data/api-commons/op…
-
I'm told we're using OpenAPI spec v.2 and that we should upgrade at some point soon to v.3
-
We've had a number of discussion regarding not being able to understand the counts of API responses, and since we can't have change the default message, we need to add some mechanism for understanding…
-
This is the thread to discuss the versioning plan for the API. The starting suggestion is to use the current v1.0 and v1.1, with keeping in alignment with semantic versioning used by major providers l…
-
This is a project to begin defining a set of objects to be returned as part of error codes, providing a structure, and common language set to describe common, as well as custom error responses.