[web-annotation] Make Turtle support optional?

azaroth42 has just created a new issue for 
https://github.com/w3c/web-annotation:

== Make Turtle support optional? ==

LDP requires the turtle serialization to be supported for all RDF 
Sources, which would include both Annotations and Annotation 
Containers.  For JSON based systems, which we expect to be the 
majority of annotation servers, this is a barrier to adoption.  
Requiring that implementers do something that none of their 
anticipated clients will ever use should be avoided if possible.
So the question (post FPWD) is the degree to which this is a real 
barrier, versus one that is just perceived.

Proposal:  To evaluate, we should determine in at least two 
implementations in different languages, how much code was actually 
required to support it, given the existence of JSON-LD / RDF 
libraries.  If that code is not extensive and can be easily provided 
to implementers, we could maintain full compatibility with LDP.  If 
there are a lot of hoops to jump through we should strongly consider 
breaking compatibility with LDP, potentially at a "level 0" 
specification.


See https://github.com/w3c/web-annotation/issues/34

Received on Thursday, 18 June 2015 16:58:36 UTC