Should LOCATION_ID be in the SERVICE entity

openreferral / api-specification

This is the working repository for Open Referral's Human Services Data API protocols.

https://openreferral.readthedocs.io/en/latest/hsda/

Other

29 stars 13 forks source link

Should LOCATION_ID be in the SERVICE entity #70

Closed MaxWhitney closed 9 months ago

MaxWhitney commented 6 years ago

Version 1.1 of HSDS did not have LOCATION_ID as a field in SERVICE.

Version 1.2 of HSDA (re)introduces LOCATION_ID as a field in SERVICE at line 6748 of https://github.com/openreferral/api-specification/blob/d34ba89cb133b7f76397c10a909766b5f8ed78da/_data/api-commons/openapi-hsda.yaml#L6748

Is this as intended, since it feels like a reversion to an earlier version of the HSDS spec?

mrshll1001 commented 9 months ago

We will be archiving this repository soon. We're closing this issue because we believe it has been conclusively addressed as part of work on the main HSDS standard.

In this case, HSDS 3.0 introduces a JSON-first model where locations are embedded underneath services. In the data package serializations, the HSDS schema tools will represent a one-to-many relationship with an appropriate id field