- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Apr 2015 07:52:43 +0000
- To: public-annotation@w3.org
Rob, I would like to understand it more. Do you mean that there will be different flavors of JSON-LD using the annotation model, or that the JSON-LD used *for* the encoding of the annotation model is, *by itself* a flavor of JSON-LD and we have to allow for content negotiations to find that out? If the latter: note that the CSVW Working Group defines a [metadata format for CSV files](http://w3c.github.io/csvw/metadata/index.html) which also restricts JSON-LD in some sense. Ie, it is a different 'flavor', so to say. The decision we took was to simply define a different media type, derived from JSON; that may be more flexible for clients that want JSON and they do not care about the relationship to JSON-LD. I am not saying this is what we should do, but it may be a data point to consider. -- GitHub Notif of comment by iherman See https://github.com/w3c/web-annotation/issues/30#issuecomment-91469980
Received on Friday, 10 April 2015 07:52:54 UTC