RE: Input needed from RDF group on JSON-LD skolemization

On Monday, June 17, 2013 2:21 AM, David Booth wrote:
> On 06/16/2013 01:45 PM, Pat Hayes wrote:
> > Well, I guess that I agree with David that if you call it JSON-to-RDF
> > and say it converts to RDF datasets, then it ought to actually
> > convert to RDF datasets. You could fix this my just changing the
> > first sentence above, which is not strictly true at present. The
> > algorithm changes JSON-LD to something like an RDF dataset that is
> > sometimes an RDF dataset.
> 
> that would make the claim true, but at the expense of larger goals,
> because it would make JSON-LD significantly less useful as an RDF
> serialization.

Why would it make "JSON-LD significantly less useful as an RDF
serialization"? It may make the to RDF algorithm "less useful" because in
your specific implementation you would have to wrap it in another algorithm
which does nothing else than replacing bnode ids with skolem IRIs. Such
layering is a normal engineering process and we even give guidance how to do
it.


> > But I don't see why you would need to go to RFC2119 to do this, just
> > either change the claim for the algorithm, or put the skolemization
> > step into the algorithm itself.
> 
> the point is to require skolemization in the algorithm, rather than
> making it optional as it is currently stands.  wehether that is
> achieved through careful prose or standard 2119 terminology is an
> editorial matter.

The problem I have with requiring skolemization is that it isn't
implementable in some cases. For instance, if you are a client you can't
guarantee that you replace bnode ids with *new, globally unique* IRIs
because you don't have an IRI space you control. Using an arbitrary base or
UUIDs will generate clashes (even if the likelihood might be small).


--
Markus Lanthaler
@markuslanthaler

Received on Monday, 17 June 2013 09:31:32 UTC