- From: John Walker <john.walker@semaku.com>
- Date: Sat, 5 Apr 2014 07:41:36 +0200
- To: "public-linked-json@w3.org" <public-linked-json@w3.org>
- Message-Id: <133B6218-AD28-452B-9600-5A9D621744E2@semaku.com>
Re-post as didn't seem to work the first time > Greetings, > > Following on from a Twitter exchange with Manu, Markus and Gregg where I asked about best practices regarding embedding or referencing to a context in a JSON-LD document. > I wondered if there is any way for a client to indicate a preference for embedded or referenced context when making a request? > > Having read the IANA Considerations chapter of the JSON-LD recommendation [1] I'm none the wiser. > > Would it be useful to add more values for the profile parameter that would allow the client to indicate a preference: > - http://www.w3.org/ns/json-ld#embedded > - http://www.w3.org/ns/json-ld#referenced > > These could either be used in combination with the URI http://www.w3.org/ns/json-ld#compacted, but just specifying either of these should be enough to infer that compacted form is preferred. > > Also when requesting compacted document form, how does a client indicate the context which should be used to compact the JSON-LD response? > > I could imagine the URI of the context might be included in the list of URIs for the profile parameter, or perhaps supplied in a HTTP Link Header using the http://www.w3.org/ns/json-ld#context link relation. > The latter is probably less ambiguous. > > Cheers, > John > > [1] http://www.w3.org/TR/json-ld/#iana-considerations
Received on Saturday, 5 April 2014 05:58:07 UTC