[web-annotation] Is a JSON-LD library required?

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

== Is a JSON-LD library required? ==
I've just discovered this series of specs and am very delighted. It 
seems to be the missing pieces to make (open) annotations a reality.

One question though: Does an annotation service linked via a Link 
header with `http://www.w3.org/ns/oa#annotationService` always return 
JSON-LD with a fixed structure for the core terms etc? Said 
differently: Do I need a JSON-LD library to understand the basic data 
contained within the annotations? I hope not! But note that 
associating a JSON-LD context to a profile is not enough to enforce a 
certain JSON structure. 

I'm working on annotations for geospatial datasets, so obviously we'd 
include some domain-specific data as well in an annotation, for 
example a bounding box within the dataset for which the annotation 
applies. And I could imagine that this would result in a new JSON-LD 
domain-specific profile that again guarantees a certain structure, 
with the goal of not forcing users to have JSON-LD parsers at hand if 
they want to understand the additional geospatial information.

Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/180 using your GitHub 
account

Received on Thursday, 25 February 2016 10:24:30 UTC