Re: IANA Considerations

On Aug 19, 2011, at 6:00 AM, Markus Lanthaler wrote:

Gregg Kellogg wrote:
Also, we discussed format=context to describe the format of an @context
document.


Yes, we should add that as well. I think it would also be interesting to
link from a context document to a data document as Glenn proposed:


On 07/06/2011 11:46 AM, glenn mcdonald wrote:
If it's a goal to be able to impose context on an "existing" JSON
feed, it might be even more effective, instead of allowing @context
to point to an external file, to invert this and have a context file
that can point to a data file. That way the data file itself can be
completely untouched.

Would something like this work for you, Glenn?

{
 "@context": "http://example.org/microblog",
 "@data": "http://foo.bar/posts/15"
}


We could define an optional "data" or "instance" MIME type parameter for
JSON-LD context documents. TO link from an data/instance document to a
JSON-LD context document we could use a link header (RFC5988), e.g.:

Link: <http://www.example.com/context.jsonld>; rel="describedby";
type="application/ld+json";

This actually seems quite appropriate, from IANA Link Relations [1], described:

Refers to a resource providing information about the link's context.

What better way to indicate the location of a @context document? We should also encourage the use even if the @context is made explicit within the document. But, as the type of a context is not actually JSON-LD itself, we discussed using a parameter on the type, so it should be

Link: <http://www.example.com/context.jsonld>; rel="describedby"; type="application/ld+json;format=context"

Gregg

[1] http://www.iana.org/assignments/link-relations/link-relations.xml

--
Markus Lanthaler
@markuslanthaler