W3C home > Mailing lists > Public > public-annotation@w3.org > July 2015

Re: [web-annotation] Yet Another JSON-LD the protocol spec to use?

From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
Date: Thu, 09 Jul 2015 15:48:58 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-120044459-1436456937-sysbot+gh@w3.org>
@tilgovi I disagree... I think there will be many more consuming 
systems written than producing systems, and unless we're assuming that
 every web browser will have a JSON-LD stack built in, we would be 
deciding from the outset that there would not be browser-native 
annotation support for the foreseeable future. I think that would be a
 great shame, and hence a mistake to progress down that path.  

So ... by having a recommended context and shape, we hope that JSON 
clients will be able to consume the annotations.  A JSON-LD client 
would be able to consume them regardless of consistent context or not,
 because it would turn the annotations into an RDF graph and then 
process the graph.

For an example of what happens when you don't use the same context, 
compare the Open Annotation context annotations [1] with the IIIF 
context annotations [2].  Exactly the same model and graphs, but quite
 a different look and feel just from changing a few of the mappings.  
Without fixing the serialization, conforming clients would have to 
support both of these.  My experience to date is that work is always 
put off and put off... I'm sure I don't need to point fingers here :) 
... so making it more complex is just going to have it put off 
indefinitely.

[1] e.g. 
http://openannotation.org/spec/core/publishing.html#Serialization
[2] e.g. http://iiif.io/api/presentation/2.0/#other-content-resources

-- 
GitHub Notif of comment by azaroth42
See 
https://github.com/w3c/web-annotation/issues/52#issuecomment-120044459
Received on Thursday, 9 July 2015 15:49:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:37 UTC