- From: Gregg Kellogg <gregg@kellogg-assoc.com>
- Date: Thu, 18 Aug 2011 18:27:16 -0400
- To: Manu Sporny <msporny@digitalbazaar.com>
- CC: Linked JSON <public-linked-json@w3.org>
Framed is definitely an issue, since passing a URI as a mime-type parameter would be a non-starter; probably not sufficient to set format=framed without some other out-of-band communication of the frame. Note that application/json+ld;format=framed is reasonable as a Content-Type. Also, I'd like to keep the straight application/ld+json for an un-specified serialization. My library tries to be intelligent about creating @context/@coerce entries and use of chaining along the lines of other serializers I've written. This may not be specified, but it should be allowed. Gregg On Aug 18, 2011, at 1:18 PM, Manu Sporny wrote: > 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 22:28:24 UTC