- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Tue, 2 Jul 2013 10:46:35 +0200
- To: <public-linked-json@w3.org>
On Monday, July 01, 2013 11:14 PM, David Booth wrote: > On 06/30/2013 10:25 AM, Pat Hayes wrote: > >> At present, the results of JSON-LD-compliant parsing of a JSON-LD > >> document to produce a set of RDF triples is non-deterministic > >> because JSON-LD allows blank node predicates and RDF does not. > > > > That is a nonsequiteur. There is a perfectly deterministic algorithm > > to map JSON-LD into RDF, with information loss. Option (a) below, for > > example. > > No, option 1 below is a **potential solution** to the problem. It is > not what the spec currently says. The spec is currently > non-deterministic. It is non-deterministic because there is a mismatch > between what the mapping algorithm produces and what RDF allows, and > the spec does not specify how that mismatch must be resolved -- leaving it > up to the parser to decide. That means that two JSON-LD-compliant > parsers may not produce the same RDF triples (aside from blank node > labels and (possibly) datatype conversions) when parsing the same > JSON-LD document. That's incorrect. The spec is deterministic. Every conformant JSON-LD processor must produce the same generalized RDF dataset. The problem (if there's any) is that not all potential consumers (RDF tools) are able to consume a generalized RDF dataset. -- Markus Lanthaler @markuslanthaler
Received on Tuesday, 2 July 2013 08:47:10 UTC