4 ms·
With your first point, you are talking about versioning (switching to a new IRI while keeping the old one for compatibility)? I agree that there probably is no
by aeberhart 6y ago
With your first point, you are talking about versioning (switching to a new IRI while keeping the old one for compatibility)?
I agree that there probably is no value in using JSON-LD for an application that was built without LD in mind.
Regarding your last statement about APIs. JSON API (https://jsonapi.org/ https://jsonapi.org/) looks interesting. Have you worked with that?
- remram 6y agoWhat's frustrating is that mapping to multiple terms was almost included: https://github.com/json-ld/json-ld.org/issues/142 https://github.com/json-ld/json-ld.org/issues/142 I didn't know about JSON:API, thanks for the pointer. It seems to tighten the JSON responses a bit, but doesn't address linking or extending vocabularies though.
- aeberhart 6y agoThanks for the link to the discussion on Github. I don't think it is a good idea to rely on inference (owl:sameAs) for something as basic as foaf:name vs. rdfs:label vs. schema:name, ... I have not used JSON API yet but it is cool to see the "follow your nose" approach be applied to REST APIs.