--- a/spec/latest/json-ld/index.html Tue Aug 06 07:10:55 2013 -0700
+++ b/spec/latest/json-ld/index.html Tue Aug 06 07:11:15 2013 -0700
@@ -2760,7 +2760,7 @@
<p>If JSON-LD content is extracted as RDF [[RDF11-CONCEPTS]], it should be expanded into an
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">RDF Dataset</tref> using the
- <cite><a href="../json-ld-api/#convert-to-rdf-algorithm">Convert to RDF Algorithm</a></cite>
+ <cite><a href="../json-ld-api/#deserialize-json-ld-to-rdf-algorithm">Deserialize JSON-LD to RDF Algorithm</a></cite>
[[JSON-LD-API]].</p>
</section>
@@ -2848,9 +2848,9 @@
<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 a <tref>property</tref>, while JSON-LD
- does. JSON-LD to RDF converters can work around this restriction, when interpreting
+ does. JSON-LD to RDF deserializers can work around this restriction, when interpreting
JSON-LD as RDF, by transforming such <tref title="blank node">blank nodes</tref> to
- <tref title="IRI">IRIs</tref>, minting new "Skolem IRIs" as per
+ <tref title="IRI">IRIs</tref>, by 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]]. Based on feedback from implementors, the
Working Group may decide to disallow blank node properties in JSON-LD.
@@ -3231,7 +3231,7 @@
as described in [[RDF11-CONCEPTS]]. Hence, a JSON-LD document is an
RDF document and a JSON document and correspondingly represents an
instance of an RDF data model, namely
- <tref href="http://www.w3.org/TR/rdf11-concepts/#fn-generalized-rdf-dataset">generalized RDF Datasets</tref>.
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-generalized-rdf-dataset">generalized RDF Datasets</tref>.
The extensions to the RDF data model are:</p>
<ul>
@@ -3239,7 +3239,7 @@
<tref title="IRI">IRIs</tref> or <tref title="blank node">blank nodes</tref>
whereas in RDF properties (predicates) have to be <tref title="IRI">IRIs</tref>. This
means that JSON-LD serializes
- <tref href="http://www.w3.org/TR/rdf11-concepts/#fn-generalized-rdf-dataset">generalized RDF Datasets</tref>.</li>
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-generalized-rdf-dataset">generalized RDF Datasets</tref>.</li>
<li>In JSON-LD <tref title="list">lists</tref> are part of the data model
whereas in RDF they are part of a vocabulary, namely [[RDF-SCHEMA]].</li>
<li>RDF values are either typed <em>literals</em>
@@ -3256,38 +3256,39 @@
graph or dataset and most, but not all, JSON-LD documents can be directly
interpreted as RDF as described in RDF 1.1 Concepts [[RDF11-CONCEPTS]].</p>
- <p>For authors and developers working with
- <tref title="blank node">blank nodes</tref> as
- <tref title="property">properties</tref> when converting to RDF, there are
- three potential approaches (in order of preference):</p>
-
- <ol>
+ <p>For authors and developers working with <tref title="blank node">blank nodes</tref>
+ as <tref title="property">properties</tref> when deserializing to RDF,
+ three potential approaches are suggested:</p>
+
+ <ul>
<li>If the author is not yet ready to commit to a stable IRI, the
property should be mapped to an IRI that is documented as unstable.</li>
- <li>If the developer wishes to use
- <tref title="blank node">blank nodes</tref> as
- <tref title="property">properties</tref> and also wishes to interpret the
- data as a
- <tref href="http://www.w3.org/TR/rdf11-concepts/#fn-generalized-rdf-dataset">generalized RDF Dataset</tref>,
- there is an option in the [[JSON-LD-API]] to do so.</li>
- <li>If the author or developer wishes to use
- <tref title="blank node">blank nodes</tref> as
- <tref title="property">properties</tref> and wishes to interpret the data
- as a non-generalized RDF Dataset, it is possible
- to losslessly interpret JSON-LD as RDF by
- transforming <tref title="blank node">blank nodes</tref> used as
- <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]].</li>
- </ol>
+ <li>If the developer wishes to use <tref title="blank node">blank nodes</tref>
+ as <tref title="property">properties</tref> and also wishes to interpret the
+ data as a
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-generalized-rdf-dataset">generalized RDF Dataset</tref>,
+ there is an option, <i>produce generalized RDF</i>, in the
+ Deserialize JSON-LD to RDF algorithm [[JSON-LD-API]] to do so. Note that a
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-generalized-rdf-dataset">generalized RDF Dataset</tref>
+ is an extension of RDF; it does not conform to the RDF standard.</li>
+ <li>If the author or developer wishes to use <tref title="blank node">blank nodes</tref>
+ as <tref title="property">properties</tref> and wishes to interpret the data
+ as a standard (non-generalized)
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">RDF Dataset</tref>,
+ it is possible to losslessly interpret JSON-LD as RDF by transforming
+ <tref title="blank node">blank nodes</tref> used as
+ <tref title="property">properties</tref> to <tref title="IRI">IRIs</tref>,
+ by 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]].</li>
+ </ul>
<p>The normative algorithms for interpreting JSON-LD as RDF and serializing
RDF as JSON-LD are specified in the JSON-LD Processing Algorithms and API
specification [[JSON-LD-API]].</p>
<p>Even though JSON-LD serializes
- <tref href="http://www.w3.org/TR/rdf11-concepts/#fn-generalized-rdf-dataset">generalized RDF Datasets</tref>, it can
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-generalized-rdf-dataset">generalized RDF Datasets</tref>, it can
also be used as a <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-source">RDF graph source</tref>.
In that case, a consumer MUST only use the default graph and ignore all named graphs.
This allows servers to expose data in languages such as Turtle and JSON-LD
@@ -3298,16 +3299,17 @@
datasets to process the information.</p>
<section class="informative">
- <h3>Transformation from JSON-LD to RDF</h3>
-
- <p>The process of turning a JSON-LD document depends on executing the
- algorithms defined in
- <cite><a href="../json-ld-api/#rdf-conversion-algorithms">RDF Conversion Algorithms</a></cite>
+ <h3>Serializing/Deserializing RDF</h3>
+
+ <p>The process of serializing RDF as JSON-LD and deserializing JSON-LD to RDF
+ depends on executing the algorithms defined in
+ <cite><a href="../json-ld-api/#rdf-serialization-deserialization-algorithms">RDF Serialization-Deserialization Algorithms</a></cite>
in the JSON-LD Processing Algorithms and API specification [[JSON-LD-API]].
It is beyond the scope of this document to detail these algorithms any further,
but a summary of the necessary operations is provided to illustrate the process.</p>
- <p>The procedure involves the following steps:</p>
+ <p>The procedure to deserialize a JSON-LD document to RDF involves the
+ following steps:</p>
<ol>
<li>Expand the JSON-LD document, removing any context; this ensures
@@ -3374,7 +3376,7 @@
-->
</pre>
- <p>Transforming this to RDF now is a straightforward process of turning
+ <p>Deserializing this to RDF now is a straightforward process of turning
each <tref>node object</tref> into one or more RDF triples. This can be
expressed in Turtle as follows:</p>
@@ -3390,7 +3392,7 @@
-->
</pre>
- <p>The process of turning RDF into JSON-LD can be thought of as the
+ <p>The process of serializing RDF as JSON-LD can be thought of as the
inverse of this last step, creating an expanded JSON-LD document closely
matching the triples from RDF, using a single <tref>node object</tref>
for all triples having a common subject, and a single <tref>property</tref>