- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Fri, 24 Jan 2014 13:37:05 -0700
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: Linked JSON <public-linked-json@w3.org>
Received on Friday, 24 January 2014 20:37:40 UTC
Hi Markus, On Fri, Jan 24, 2014 at 1:31 PM, Markus Lanthaler <markus.lanthaler@gmx.net>wrote: > > > 1. Content Negotiation Use a header on the HTTP request to ask for a > > particular context by its full URI. For example: X-JSONLD-Context: > > http://www.openannotation.org/spec/core/context.json > > A variation of that would be my preferred approach. JSON-LD's media type > [1] > features a profile parameter that you can use for such purposes. Just > define > a profile and give it a unique URL identifying it. Then you simply use > HTTP's > > Accept: application/ld+json; > profile="http://www.openannotation.org/profile/default" > > You should consider registering that profile. There's an IETF Internet > Draft > of mine [2] establishing a registry for such profiles. I expect it to > become > an RFC shortly. Perfect :) And just to be clear, the representation returned from the profile's URI MAY be a context document, but could be something else, given the description in [1]? So this would be a potential best practice, but not necessarily mandatory. R
Received on Friday, 24 January 2014 20:37:40 UTC