--- a/spec/latest/json-ld-api/index.html Thu Apr 04 13:53:12 2013 -0400
+++ b/spec/latest/json-ld-api/index.html Thu Apr 04 20:25:39 2013 +0200
@@ -171,11 +171,11 @@
the following audiences:</p>
<ul>
- <li>Developers that want an overview of the JSON-LD API.</li>
- <li>Web authors and developers that want a very detailed view of how
+ <li>Developers who want an overview of the JSON-LD API.</li>
+ <li>Web authors and developers who want a very detailed view of how
a <tref>JSON-LD Processor</tref> or a <tref>JSON-LD API Implementation</tref>
operates.</li>
- <li>Software developers that want to implement the algorithms to transform
+ <li>Software developers who want to implement the algorithms to transform
JSON-LD documents.</li>
</ul>
@@ -559,8 +559,9 @@
in [[!RFC2119]].</p>
<p>There are three classes of products that can claim conformance to this
- specification: <tref title="JSON-LD Processor">JSON-LD Processors</tref>
- and <tref title="JSON-LD API Implementation">JSON-LD API Implementations</tref>.</p>
+ specification: <tref title="JSON-LD Processor">JSON-LD Processors</tref>,
+ <tref title="JSON-LD API Implementation">JSON-LD API Implementations</tref>,
+ and <tref title="JSON-LD-RDF Converter">JSON-LD-RDF Converters</tref>.</p>
<p>A conforming <tdef>JSON-LD Processor</tdef> is a system which can perform the
<a href="#expansion-algorithm">Expansion</a>, <a href="#compaction-algorithm">Compaction</a>,
@@ -3075,7 +3076,15 @@
<section>
<h2>Convert to RDF Algorithm</h2>
- <p>This algorithms converts a JSON-LD document to an <tref>RDF dataset</tref>.</p>
+ <p>This algorithms converts a JSON-LD document to an <tref>RDF dataset</tref>.
+ Please note that RDF does not allow a <tref>blank node</tref> to be used
+ as a <tref>graph name</tref> or <tref>property</tref>, while JSON-LD does.
+ <tref title="JSON-LD-RDF Converter">JSON-LD-RDF Converters</tref> can work
+ around this restriction, when converting JSON-LD to RDF, by converting such
+ <tref title="blank node">blank nodes</tref> to <tref title="IRI">IRIs</tref>,
+ minting new "Skolem IRIs" as per
+ <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
+ of [[RDF11-CONCEPTS]].</p>
<div class="issue atrisk" data-number="3" title="Allow blank nodes to be used as graph name or property">
<p class="atrisk-head">Note: This feature is
@@ -3085,11 +3094,16 @@
For the current status see
<a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
<p>RDF does not currently allow a <tref>blank node</tref> to be
- used as <tref>graph name</tref> or <tref>property</tref>. Implementations
- might convert such <tref title="blank node">blank nodes</tref> to
- <tref title="IRI">IRIs</tref> by minting new "Skolem IRIs" as per
+ used as <tref>graph name</tref> or <tref>property</tref>, while JSON-LD
+ does. <tref title="JSON-LD-RDF Converter">JSON-LD-RDF Converters</tref>
+ can work around this restriction, when converting JSON-LD to RDF, by
+ converting such <tref title="blank node">blank nodes</tref> to
+ <tref title="IRI">IRIs</tref>, minting new "Skolem IRIs" as per
<cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
- of [[RDF11-CONCEPTS]].</p>
+ of [[RDF11-CONCEPTS]]. Based on feedback from implementors the
+ Working Group may decide to disallow blank nodes as graph names and
+ properties in JSON-LD. If this change would affect you, be sure to
+ send in a comment.</p>
</div>
<section class="informative">
--- a/spec/latest/json-ld/index.html Thu Apr 04 13:53:12 2013 -0400
+++ b/spec/latest/json-ld/index.html Thu Apr 04 20:25:39 2013 +0200
@@ -2739,11 +2739,15 @@
For the current status see
<a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
<p>RDF does not currently allow a <tref>blank node</tref> to be
- used as <tref>graph name</tref> or <tref>property</tref>. Implementations
- might convert such <tref title="blank node">blank nodes</tref> to
- <tref title="IRI">IRIs</tref> by minting new "Skolem IRIs" as per
+ used as <tref>graph name</tref> or <tref>property</tref>, while JSON-LD
+ does. JSON-LD to RDF converters can work around this restriction, when converting
+ JSON-LD to RDF, by converting such <tref title="blank node">blank nodes</tref> to
+ <tref title="IRI">IRIs</tref>, minting new "Skolem IRIs" as per
<cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
- of [[RDF11-CONCEPTS]].</p>
+ of [[RDF11-CONCEPTS]]. Based on feedback from implementors the
+ Working Group may decide to disallow blank nodes as graph names and
+ properties in JSON-LD. If this change would affect you, be sure to
+ send in a comment.</p>
</div>
<p><tref title="JSON-LD document">JSON-LD documents</tref> MAY contain data that cannot be
@@ -3154,10 +3158,16 @@
</ul>
<p>Summarized these differences mean that JSON-LD is capable of serializing any RDF
- graph or dataset and most, but not all, JSON-LD documents can be transformed to RDF.
- A complete description of the algorithms to convert from RDF to JSON-LD and from
- JSON-LD to RDF is included in the JSON-LD Processing Algorithms and API specification
- [[JSON-LD-API]].</p>
+ graph or dataset and most, but not all, JSON-LD documents can be directly
+ transformed to RDF. It is possible to work around this restriction, when
+ converting JSON-LD to RDF, by converting <tref title="blank node">blank nodes</tref>
+ used as <tref title="graph name">graph names</tref> or
+ <tref title="property">properties</tref> to <tref title="IRI">IRIs</tref>,
+ minting new "Skolem IRIs" as per
+ <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
+ of [[RDF11-CONCEPTS]]. A complete description of the algorithms to convert
+ from RDF to JSON-LD and from JSON-LD to RDF is included in the JSON-LD
+ Processing Algorithms and API specification [[JSON-LD-API]].</p>
<p>Even though JSON-LD serializes RDF datasets, it can also be used as a RDF graph source.
In that case, a consumer MUST only use the default graph and ignore all named graphs.