Open almereyda opened 7 years ago
The JSON-LD serialization of a dataset is produced by mixing API and Linked Data design patterns. Currently a ?format=schema parameter is being used to produce an almost desired effect, which breaks the ability to directly link to the document.
We didn't take the time to go to the end by lack of time but what you have seen is a serialisation of json-LD this will be available for in depth data LD parsing our translation engine is generic and makes this changes really easy
Instead, the route could make use of content negotiation headers to distinguish which serialization is requested. For JSON-LD it is application/ld+json.
I think this has been changed , just not available yet in PROD we are aware of the technical features of JSON-LD and we do playground validation but we are mainly focusing on the interfaces at the moment with a great user experience surprise soon to come Therefore we're just lacking time on the api reusability part but it's all part of the roadmap , so no worries, we're on the road Jack (Jon) ;)
The JSON-LD serialization of a dataset is produced by mixing API and Linked Data design patterns. Currently a
?format=schema
parameter is being used to produce an almost desired effect, which breaks the ability to directly link to the document.Instead, the route could make use of content negotiation headers to distinguish which serialization is requested. For JSON-LD it is
application/ld+json
.Additionally the stable IRIs provided by the returned document of the
?format=schema
route cannot be dereferenced and produce 404s:This depends on #5 . Also read https://ruben.verborgh.org/blog/2013/11/29/the-lie-of-the-api/