Re: JSON-LD spec split preview

On 10/16/2011 10:11 AM, Danny Ayers wrote:
> Oh Manu, working too hard.

The difference between try and triumph is a little umph. :P

> The JSON core stuff is looking good, my stupid crit has pretty much
> been answered.

Glad to hear that. :)

> 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.

I don't completely understand this statement, but I'll take a stab at
responding.

We've been chatting back and forth with Gavin Carothers at TopQuadrant
for the past several months and have been verifying their test data
against the algorithm in the spec.

The graph normalization stuff /is/ grounded in the RDF model. The name
of the spec is "RDF Graph Normalization" and it operates on an RDF
graph. Any hints at JSON-LD are accidental remnants of the spec split -
they will be removed in time. The specification will be fully
generalized to RDF in time - it's not specific to JSON-LD.

> 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.

We codified this graph normalization algorithm because it was a 
requirement for the Web Payments / PaySwarm work. We can't create a 
stable, decentralized payment standard for the Web without a solid, 
decentralized, temporally-accurate graph signature algorithm. In order 
to have that, we need to solve the Graph Normalization problem (and with 
the publication of this specification, we're asserting that we have done 
just that).

To put it another way - we're a commercial company that is betting its
future on Linked Data. Graph normalization for Linked Data is not an
optional feature for us - it's a requirement. We're not going to be the
only company that has this requirement. If we want Linked Data to go
further than it has today, we have to address this problem.

We can talk about scope creep and where this work should be done, but 
one thing is certain (in my mind, at least), the work /MUST/ be done. 
This is not an optional feature for us, and I think you'll agree that it 
has deep ramifications for the world:

http://manu.sporny.org/2011/better-world/

-- 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/

Received on Sunday, 16 October 2011 19:50:57 UTC