example of embedding openeligibility taxonomy

[lilybradley]

Could you provide one example of how openeligibility taxonomy can be incorporated into a JSON-LD format?

For example could it look like this:
"@context": "openeligibility.org",
"@services": "Medical Care",
"@situations": "Uninsured",

Or is there a different way to refer to second_level id="1199"?

Thanks!

[motinda]

Hi Lily--

Thanks for the note. We've been working hard on new releases, so apologies for the late reply. We have a beta JSON version of the taxonomy that we'll be sharing soon. I think we should consider thinking about a JSON-LD endpoint as well. I will definitely keep you posted.

[KalmanG]

Looping on this.

Publishing a website for a social services org and wonder if this project relates to something like schema.org markup we could place for their services?

[greggish]

I don't know about aligning Open Eligibility the taxonomy itself with schema.org (I suspect that would be a hard problem) but we did produce an alignment of the industry standard for social service directory information (which can be used with Open Eligibility, or any other taxonomy) with schema.org for legal services – see here: https://openreferral.org/improving-access-to-legal-aid-by-improving-search-results-with-schema-org/

Would be glad to talk about how we might iterate on that translation and make it more useful!