Re: social-ISSUE-11 (W3C Namespace): Have W3C Namespace URI serve the JSON-LD @context

Good luck with this.  W3C (at least previously) did not consider a context
document to be valid for inclusion within /ns/ .
The way that the Open Annotation group got around the problem was to
include the ontology in JSON-LD within the graph of the document.  Context
processors ignore it, but it adds data that's redundantly retrieved every
time.


On Tue, Nov 4, 2014 at 10:22 AM, Social Web Working Group Issue Tracker <
sysbot+tracker@w3.org> wrote:

> social-ISSUE-11 (W3C Namespace): Have W3C Namespace URI serve the JSON-LD
> @context
>
> http://www.w3.org/Social/track/issues/11
>
> Raised by: Reuben Binns
> On product:
>
> See: https://github.com/jasnell/w3c-socialwg-activitystreams/issues/49
>
> We need the "http://www.w3.org/ns/activitystreams" Namespace URI to
> return the JSON-LD @context document with proper CORS and Content-Type
> headers included
>
>
>
>


-- 
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305