Open spyysalo opened 9 years ago
OK, this sucks: http://www.w3.org/TR/2015/REC-ldp-20150226/#h-ldprs-get-turtle
4.3.2.1 LDP servers MUST respond with a Turtle representation of the requested LDP-RS when the request includes an Accept header specifying text/turtle, unless HTTP content negotiation requires a different outcome [turtle].
It's hard enough to get people to add @context
to their JSON, leading off with "this is a turtle-based API, but ..." will have them zoning out before you can say "content negotiation".
IMHO this is a dealbreaker for trying to follow the LDP spec in REST-OA core, but we could get conformance using a simple piece of middleware.
Yes, the LDP Working Group perhaps should better have selected JSON-LD as the primary RDF serialization. Wilful violations of the requirement to support Turtle can be considered.
As of about two weeks ago there is now a W3C recommendation covering things like how to implement the collection pattern for linked data: (from http://www.w3.org/)