- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jul 2015 20:37:49 +0000
- To: public-annotation@w3.org
And, in fact, the JSON you included would be completely compatible with using the context [once it includes iana and ldp] as the requirement for using particular keys comes from a profile, not the context itself. The reason for requiring the particular shape of the JSON-LD is to enable regular JSON based clients to understand and process the content without requiring a JSON-LD, or worse full RDF, stack. At the same time the great advantage of JSON-LD is that it *is* RDF underneath the covers so people wanting to do linked data can also make use of it at the same time without multiple representations. So I'm :-1: to making the serialization form unrestricted as this makes client development harder. See also #51 regarding constraining HTTP level features at the protocol level. -- GitHub Notif of comment by azaroth42 See https://github.com/w3c/web-annotation/issues/52#issuecomment-119724710
Received on Wednesday, 8 July 2015 20:37:51 UTC