Re: [web-annotation] Define json-ld profile URI for OA serialization context and structure

Noting external discussions relevant to this issue:
  * Discussion with the Social Web WG resulted in the point that AS 
will create its own media type (activity+json) as they want to have it
 be able to legitimately include information that is NOT valid in 
JSON-LD.  An example given was list of lists, which are not possible 
in JSON-LD, but used in GeoJSON.  The compromise (thanks to @jasnell) 
was to _also_ mint a profile URI for when the content _is_ JSON-LD
  * Discussion with @manusporny confirmed that using the context 
document as the URI for the profile document is fine, and that 
documentation could be included within the body of the document as 
JSON-LD processors MUST ignore it.
  * Discussions with IETF revealed that it should be possible to 
register a file extension (or other such features typically associated
 with full media types) when registering a profile.  That we should 
try to do so, and work with them to ensure that the process is 
consistent and smooth.

-- 
GitHub Notif of comment by azaroth42
See 
https://github.com/w3c/web-annotation/issues/30#issuecomment-153487296

Received on Tuesday, 3 November 2015 21:02:32 UTC