Re: JSON-LD Telecon Minutes for 2013-06-11

On 11/06/13 17:43, Manu Sporny wrote:
>     7. Conversion of blank nodes to Skolemization IDs when going
>        to RDF

Please don't require this.

Let the receiver of the (generalized) RDF decide how to handle it. 
Otherwise, systems that can handle partial or full generalized RDF will 
not so easily be able to get such generalised RDF.

I hope to use a standard, high-quality JSON-LD library and I don't want 
to have to use a modified version of it.  If the library is 
required-by-spec to skolemize, then it hides the generalization. 
Skolemization by one component is not easily reversible by another 
component.


As far as I'm concerned, JSON-LD is RDF - a couple of generalizations to 
bNodes here and there is not significant in data model terms; inference 
can put bNodes anywhere anyway.  The major issue is breaking existing 
deployed software.  We can't assume the whole world upgrades to the new 
forms when the specs are finalized.

Obviously JSON-LD sees itself as "new tech/no legacy" whereas other RDF 
systems that hope to ingest JSON-LD see themselves as having an 
installed base "existing tech/existing users".

	Andy

Received on Sunday, 16 June 2013 12:13:15 UTC