- From: Danny Ayers <danny.ayers@gmail.com>
- Date: Sun, 16 Oct 2011 16:11:51 +0200
- To: Manu Sporny <msporny@digitalbazaar.com>, www-archive <www-archive@w3.org>
- Cc: Reto Bachmann-Gmür <me@farewellutopia.com>, Jeremy Carroll <jeremy@topquadrant.com>
Oh Manu, working too hard. The JSON core stuff is looking good, my stupid crit has pretty much been answered. But there's huge scope spread here, please pull that back until you've confirmed it works with folks that have played there already. Graph Normalization should be grounded in the RDF model, not a Hixie-like magic trick. Basically I think this is wrong-minded : http://manu.sporny.org/tmp/json-ld.org/spec/ED/rdf-graph-normalization I could well be wrong, so cc'ing a second opinion. Cheers, Danny. On 16 October 2011 09:11, Manu Sporny <msporny@digitalbazaar.com> wrote: > The first pass of the spec split is done and preview-able (temporarily) > here: > > http://manu.sporny.org/tmp/json-ld.org/spec/ > > There are three Editor's Drafts for 2011-10-16: > > The JSON-LD Syntax: > http://manu.sporny.org/tmp/json-ld.org/spec/ED/json-ld-syntax/20111016/ > > The JSON-LD API: > http://manu.sporny.org/tmp/json-ld.org/spec/ED/json-ld-api/20111016/ > > RDF Graph Normalization: > http://manu.sporny.org/tmp/json-ld.org/spec/ED/rdf-graph-normalization/20111016/ > > The work was done on a separate branch (2011-09-spec-split) and will be > merged if we decide this is the direction in which the community wants to > head. Detailed diff for this branch vs. the main branch is available here: > > https://github.com/json-ld/json-ld.org/compare/master...2011-09-spec-split > > The split is pretty clean between each of the specs modulo some language > that needs to be duplicated across specifications. There is some duplication > between the JSON-LD API and the RDF Graph Normalization spec (basically the > normalization algorithm). We have yet to determine whether generalizing the > normalization algorithm in the JSON-LD API will make it difficult to > understand. However, keeping two normalization algorithms that are 90% > similar in language, and which are meant to produce the same result, will be > a maintainability nightmare. It seems like we'll be able to fully move the > normalization algorithm into its own spec, but until we change the language > and have a couple of people review it... we won't know for sure. > > Take a look if you're interested. Perhaps we should put this on the Agenda > for our upcoming telecon and decide to accept/reject these changes during > the call. In the meantime, if you support/disapprove of this direction, but > won't be able to make the call, you can always +1/-1 it via the mailing > list. > > -- manu > > -- > Manu Sporny (skype: msporny, twitter: manusporny) > Founder/CEO - Digital Bazaar, Inc. > blog: Standardizing Payment Links - Why Online Tipping has Failed > http://manu.sporny.org/2011/payment-links/ > > -- http://dannyayers.com
Received on Sunday, 16 October 2011 14:12:19 UTC