--- a/spec/latest/json-ld-syntax/index.html Tue Mar 19 16:54:17 2013 -0400
+++ b/spec/latest/json-ld-syntax/index.html Wed Mar 20 12:10:52 2013 +0100
@@ -312,23 +312,23 @@
<dd>Used to define the short-hand names that are used throughout a JSON-LD
document. These short-hand names are called <tref title="term">terms</tref> and help
developers to express specific identifiers in a compact manner. The
- <code>@context</code> keyword is described in detail in section
+ <code>@context</code> keyword is described in detail in
<a class="sectionRef" href="#the-context"></a>.</dd>
<dt><code>@id</code></dt>
<dd>Used to uniquely identify <em>things</em> that are being described in the document.
This keyword is described in <a class="sectionRef" href="#node-identifiers"></a>.</dd>
<dt><code>@value</code></dt>
<dd>Used to specify the data that is associated with a particular
- <tref>property</tref> in the graph. This keyword is described in section
+ <tref>property</tref> in the graph. This keyword is described in
<a class="sectionRef" href="#string-internationalization"></a> and
<a class="sectionRef" href="#typed-values"></a>.</dd>
<dt><code>@language</code></dt>
<dd>Used to specify the natural (human) language for a particular value or the default
- language of a JSON-LD document. This keyword is described in section
+ language of a JSON-LD document. This keyword is described in
<a class="sectionRef" href="#string-internationalization"></a>.</dd>
<dt><code>@type</code></dt>
<dd>Used to set the data type of a <tref>node</tref> or
- <tref>typed value</tref>. This keyword is described in section
+ <tref>typed value</tref>. This keyword is described in
<a class="sectionRef" href="#typed-values"></a>.</dd>
<dt><code>@container</code></dt>
<dd>Used to set the default container type for a <tref>term</tref>.
@@ -371,8 +371,8 @@
This criteria is relevant to authors and authoring tool implementers.</p>
<p>A <tref>JSON-LD document</tref> complies with this specification if it follows
- the normative statements in <a class="sectionRef" href="#json-ld-grammar"></a>. JSON documents
- can be interpreted as JSON-LD by following the normative statements in section
+ the normative statements in appendix <a href="#json-ld-grammar"></a>. JSON documents
+ can be interpreted as JSON-LD by following the normative statements in
<a class="sectionRef" href="#interpreting-json-as-json-ld"></a>. For convenience, normative
statements for documents are often phrased as statements on the properties of the document.</p>
@@ -585,7 +585,7 @@
<code>http://example.com/about/</code>, the <tref>relative IRI</tref>
<code>../</code> would expand to <code>http://example.com/</code> (for more
information on where <tref title="relative IRI">relative IRIs</tref> can be
- used, please refer to appendix <a class="sectionRef" href="#json-ld-grammar"></a>).</p>
+ used, please refer to appendix <a href="#json-ld-grammar"></a>).</p>
<pre class="example" data-transform="updateExample"
title="IRIs can be relative">
@@ -1290,7 +1290,7 @@
<section>
<h2>Advanced Context Usage</h2>
- <p>Section <a class="sectionRef" href="#the-context"></a> introduced the basics of what makes
+ <p>Section <a href="#the-context"></a> introduced the basics of what makes
JSON-LD work. This section expands on the basic principles of the
<tref>context</tref> and demonstrates how more advanced use cases can
be achieved using JSON-LD. </p>
@@ -1535,7 +1535,7 @@
<p>The example above would associate the <code>ja</code> language
code with the two <tref title="string">strings</tref> <em>花澄</em> and <em>科学者</em>.
Languages codes are defined in [[!BCP47]]. The default language applies to all
- <tref>string</tref> values that are not <a class="sectionRef" href="#type-coercion">type coerced</a>.</p>
+ <tref>string</tref> values that are not <a href="#type-coercion">type coerced</a>.</p>
<p>To clear the default language for a subtree, <code>@language</code> can
be set to <code>null</code> in a <tref>local context</tref> as follows:</p>
@@ -1593,7 +1593,8 @@
<p class="note">Language associations are only applied to plain
<tref title="string">strings</tref>. <tref title="typed value">Typed values</tref>
- or values that are subject to <a class="sectionRef" href="#type-coercion"></a> are not language tagged.</p>
+ or values that are subject to <a href="#type-coercion">type coercion</a>
+ are not language tagged.</p>
<p>Just as in the example above, systems often need to express the value of a
property in multiple languages. Typically, such systems also try to ensure that
@@ -2769,7 +2770,8 @@
be an empty <tref>string</tref> (<code>""</code>) as not all programming languages
are able to handle empty property names.</p>
- <p>See <a class="sectionRef" href="#the-context"></a> and <a class="sectionRef" href="#iris"></a> for further discussion
+ <p>See <a class="sectionRef" href="#the-context"></a> and
+ <a class="sectionRef" href="#iris"></a> for further discussion
on mapping <tref title="term">terms</tref> to <tref title="IRI">IRIs</tref>.</p>
</section>
@@ -2821,8 +2823,9 @@
its value MUST be an <tref>absolute IRI</tref>, a <tref>relative IRI</tref>,
or a <tref>compact IRI</tref> (including
<tref title="blank node identifier">blank node identifiers</tref>).
- See <a class="sectionRef" href="#node-identifiers"></a>, <a href="#compact-iris"></a>,
- and <a class="sectionRef" href="#identifying-blank-nodes"></a> for further discussion on
+ See <a class="sectionRef" href="#node-identifiers"></a>,
+ <a class="sectionRef" href="#compact-iris"></a>, and
+ <a class="sectionRef" href="#identifying-blank-nodes"></a> for further discussion on
<code>@id</code> values.</p>
<p>If the <tref>node object</tref> contains the <code>@graph</code>
@@ -2857,9 +2860,9 @@
a <tref>node object</tref> or an <tref>array</tref> containing a combination of these.</p>
<p>If the <tref>node object</tref> contains the <code>@index</code> key,
- its value MUST be a <tref>string</tref>. See section
- <a class="sectionRef" href="#data-indexing"></a> for further discussion on <code>@index</code>
- values.</p>
+ its value MUST be a <tref>string</tref>. See
+ <a class="sectionRef" href="#data-indexing"></a> for further discussion
+ on <code>@index</code> values.</p>
<p>Keys in a <tref>node object</tref> that are not
<tref title="keyword">keywords</tref> MAY expand to an <tref>absolute IRI</tref>
@@ -2910,7 +2913,8 @@
<p>The value associated with the <code>@index</code> key MUST be a
<tref>string</tref>.</p>
- <p>See <a class="sectionRef" href="#typed-values"></a> and <a class="sectionRef" href="#string-internationalization"></a>
+ <p>See <a class="sectionRef" href="#typed-values"></a> and
+ <a class="sectionRef" href="#string-internationalization"></a>
for more information on <tref title="value object">value objects</tref>.</p>
</section>
@@ -2926,7 +2930,7 @@
of terms associated with a <code>@set</code> or <code>@list</code> container
will always be represented in the form of an <tref>array</tref> when a document
is processed—even if there is just a single value that would otherwise be optimized to
- a non-array form in <a hclass="sectionRef" ref="#compact-document-form"></a>.
+ a non-array form in <a href="#compact-document-form">compact document form</a>.
This simplifies post-processing of the data as the data is always in a
deterministic form.</p>
@@ -3126,21 +3130,21 @@
<section>
<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/#convert-to-rdf-algorithm">
- JSON-LD-API Convert to RDF Algorithm
- </a></cite>
+ <cite><a href="../json-ld-api/#convert-to-rdf-algorithm">JSON-LD-API Convert to RDF Algorithm</a></cite>
[[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>
+
<ol>
<li>Expand the JSON-LD document, removing any context; this ensures
that properties, types, and values are given their full representation
- as <tref title="IRI">IRIs</tref> and expanded values. The process of expanding
- is discussed further in
- <a class="sectionRef" href="#expanded-document-form"></a>.</li>
+ as <tref title="IRI">IRIs</tref> and expanded values. Expansion
+ is discussed further in <a class="sectionRef" href="#expanded-document-form"></a>.</li>
<li>Flatten the document, which turns the document into an array of
<tref title="node object">node objects</tref>. Flattening is discussed
further in <a class="sectionRef" href="#flattened-document-form"></a>.</li>
@@ -3149,6 +3153,7 @@
</ol>
<p>For example, consider the following JSON-LD document in compact form:</p>
+
<pre class="example" data-transform="updateExample"
title="Sample JSON-LD document">
<!--