I would like to reference OpenEligibility in a RESTful way. Part of this means that I need to be able to uniquely identify OpenEligibility definitions with a reference to OpenEligibility or AuntBertha.
In order to do this, I need a canonical URI for your definitions. I would suggest something like the following (for "Adoption & Foster Care" and "Learning Disability", respectfully):
https://taxonomy.openeligibility.org/v2.0.0/services/1271
https://taxonomy.openeligibility.org/v2.0.0/situations/20018
It doesn't involve writing new code or actually opening that endpoint. It's just useful to declare the intended URI.
It would be even better if you updated the canonical website (http://about.auntbertha.com/openeligibility) and gave each service and situation listed an HTML id, so I can reference it with http://about.auntbertha.com/openeligibility#1271 and consumers of my API can reference your definitions directly.
I would like to reference OpenEligibility in a RESTful way. Part of this means that I need to be able to uniquely identify OpenEligibility definitions with a reference to OpenEligibility or AuntBertha.
In order to do this, I need a canonical URI for your definitions. I would suggest something like the following (for "Adoption & Foster Care" and "Learning Disability", respectfully):
It doesn't involve writing new code or actually opening that endpoint. It's just useful to declare the intended URI.
It would be even better if you updated the canonical website (http://about.auntbertha.com/openeligibility) and gave each service and situation listed an HTML id, so I can reference it with
http://about.auntbertha.com/openeligibility#1271and consumers of my API can reference your definitions directly.