W3C home > Mailing lists > Public > public-linked-json@w3.org > August 2011

IANA Considerations

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Thu, 18 Aug 2011 16:18:37 -0400
Message-ID: <4E4D739D.5030609@digitalbazaar.com>
To: Linked JSON <public-linked-json@w3.org>
An IANA Considerations section has been added to the specification
(Appendix D):

http://json-ld.org/spec/latest/

Input from the mailing list was considered, as was a bit of discussion
with the WHATWG folks:

http://krijnhoetmer.nl/irc-logs/whatwg/20110818#l-963

I also talked w/ Shane McCarron, who was involved in many of the XHTML
specs, who pointed me to how the "+xml" pattern started for IANA
registration:

http://www.ietf.org/rfc/rfc3023.txt

I also looked at the list of application/* IANA types, which has some
prior art for a "+json" pattern:

http://www.iana.org/assignments/media-types/application/index.html

All of that resulted in a MIME media type for JSON-LD of:

application/ld+json

I don't necessarily like it - but it is consistent with the state of the
art in MIME media type registration. You can specifically request things
like Compacted form by doing the following in the HTTP request header:

Content-Type: application/ld+json;format=compacted

As an added bonus, this "format" mechanism is going to make writing the
test suite a bit easier as it will be able to switch on the "format"
parameter in the Content-Type field.

So, the IANA Considerations are nailed down pretty well at this point.
If you don't agree with the direction, please say why and make sure to
reference specs, consistent usage or prior-art as a basis for your
arguments.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarm Developer Tools and Demo Released
http://digitalbazaar.com/2011/05/05/payswarm-sandbox/
Received on Thursday, 18 August 2011 20:19:02 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:35 GMT