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

Re: Updated JSON-LD draft - no more microsyntaxes

From: Thomas Steiner <tomac@google.com>
Date: Mon, 16 May 2011 09:21:39 +0200
Message-ID: <BANLkTinrQthhzJaXBT+Kge5s1Ns2OeTRSA@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: Linked JSON <public-linked-json@w3.org>
Hi Manu, JSONers,

Finally had the time to work through the new spec draft. Thank you
very much for your hard work, this looks like something I was hoping
for, and that I can perfectly live with. For what it's worth, I add a
"+1" from my side under this draft. What would be the concrete next
steps in order to push this forward in the RDF(a) WGs? What can I do?
Please do let me know how I can help. Not sure if you had more
feedback from people (I know of Gregg Kellog's email). Somehow no one
seemed to react on your email, at least not on the JSON list. I am
still a big supporter of JSON for serializing RDF, you know that :-)
Looking forward to pushing this forward.


On Sun, May 8, 2011 at 00:07, Manu Sporny <msporny@digitalbazaar.com> wrote:
> Much of today was spent updating the JSON-LD draft to reflect
> discussions that have been taking place over the last three months in
> the RDF Working Group, internally at Digital Bazaar for the PaySwarm
> work, and after implementation experience feedback from a few other
> developers throughout the Web community. All of this feedback resulted
> in the following changes to the JSON-LD spec, resulting in a
> simplification of the syntax that would be most commonly used:
>  * Removal of all microsyntax features, making JSON-LD directly usable
>   in many applications via simply passing the text through JSON.parse()
>  * Modified type coercion associative array format slightly to make
>   it easier to specify a large number of vocabulary terms that the
>   author would like to have coerced.
>  * Changed a number of JSON-LD keywords to be more consistent. '#' was
>   changed to '@context', '#types' was changed to '@type', and added
>   keywords for @literal, @datatype and @iri.
>  * Added new "expanded object value" EOV syntax so that full RDF can
>   still be expressed by experts. This was also required for the
>   normalization  algorithm, which is a primary requirement of digital
>   signatures in PaySwarm.
>  * Added new normalization mechanism using new EOV syntax.
>  * Added support for "arrays of objects" as a top-level structure.
>  * Added a fairly strict "Default Context" at the request of Gavin
>   Carothers and the WHATWG folks.
> You can read the dated Editor's Draft spec here:
> http://json-ld.org/spec/ED/20110507/
> Diff-marked version from the previous is available here:
> http://json-ld.org/spec/ED/20110507/diff-20110201.html
> Here are the bits that are of most interest to those that are already
> familiar with JSON-LD.
> Specifying languages for literals:
> http://json-ld.org/spec/ED/20110507/#language-specification-in-plain-literals
> Specifying typed literals:
> http://json-ld.org/spec/ED/20110507/#typed-literals
> Expressing IRIs:
> http://json-ld.org/spec/ED/20110507/#iris
> New normalization mechanism:
> http://json-ld.org/spec/ED/20110507/#the-normalization-algorithm
> The Default Context:
> http://json-ld.org/spec/ED/20110507/#the-default-context
> -- manu
> --
> Manu Sporny (skype: msporny, twitter: manusporny)
> President/CEO - Digital Bazaar, Inc.
> blog: The PaySwarm Vocabulary
> http://digitalbazaar.com/2011/03/31/payswarm-vocab/

Thomas Steiner, Research Scientist, Google Inc.
http://blog.tomayac.com, http://twitter.com/tomayac
Received on Monday, 16 May 2011 07:22:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:53:17 UTC