--- a/spec/latest/json-ld-api/index.html Wed Dec 04 11:44:29 2013 -0800
+++ b/spec/latest/json-ld-api/index.html Wed Dec 11 21:42:13 2013 +0100
@@ -1679,7 +1679,7 @@
<code class="error"><a href="#idl-def-JsonLdErrorCode.invalid-language-tagged-value">invalid language-tagged value</a></code>
error has been detected (only <tref title="string">strings</tref>
can be language-tagged) and processing is aborted.</li>
- <li>Otherwise, if the <i>result</i> has a <code>@type</code> member
+ <li>Otherwise, if the <i>result</i> has an <code>@type</code> member
and its value is not an <tref>IRI</tref>, an
<code class="error"><a href="#idl-def-JsonLdErrorCode.invalid-typed-value">invalid typed value</a></code>
error has been detected and processing is aborted.</li>
@@ -1852,7 +1852,7 @@
maps.</li>
</ol>
- <p>The final output is a <tref>JSON object</tref> with a <code>@context</code>
+ <p>The final output is a <tref>JSON object</tref> with an <code>@context</code>
key, if a non-empty <tref>context</tref> was given, where the <tref>JSON object</tref>
is either <i>result</i> or a wrapper for it where <i>result</i> appears
as the value of an (aliased) <code>@graph</code> key because <i>result</i>
@@ -2256,7 +2256,7 @@
<li>Reference the value associated with the <code>@type</code>
member in <i>type/language map</i> using the variable
<i>type map</i>.</li>
- <li>If <i>type map</i> does not have a <code>@reverse</code>
+ <li>If <i>type map</i> does not have an <code>@reverse</code>
member, create one and set its value to the <tref>term</tref>
being processed.</li>
</ol>
@@ -2295,13 +2295,13 @@
<li>If <i>language map</i> does not have a <i>default language</i>
member, create one and set its value to the <tref>term</tref>
being processed.</li>
- <li>If <i>language map</i> does not have a <code>@none</code>
+ <li>If <i>language map</i> does not have an <code>@none</code>
member, create one and set its value to the <tref>term</tref>
being processed.</li>
<li>Reference the value associated with the <code>@type</code>
member in <i>type/language map</i> using the variable
<i>type map</i>.</li>
- <li>If <i>type map</i> does not have a <code>@none</code>
+ <li>If <i>type map</i> does not have an <code>@none</code>
member, create one and set its value to the <tref>term</tref>
being processed.</li>
</ol>
@@ -3539,7 +3539,7 @@
</li>
<li>Remove the <code>@id</code> member from <i>head</i>.</li>
<li>Reverse the order of the <i>list</i> <tref>array</tref>.</li>
- <li>Add a <code>@list</code> member to <i>head</i> and initialize
+ <li>Add an <code>@list</code> member to <i>head</i> and initialize
its value to the <i>list</i> <tref>array</tref>.</li>
<li>For each item <i>node id</i> in <i>list nodes</i>, remove the
<i>node id</i> member from <i>graph object</i>.</li>
@@ -3553,7 +3553,7 @@
<ol class="algorithm">
<li>If <i>graph map</i> has a <i>subject</i> member:
<ol class="algorithm">
- <li>Add a <code>@graph</code> member to <i>node</i> and initialize
+ <li>Add an <code>@graph</code> member to <i>node</i> and initialize
its value to an empty <tref>array</tref>.</li>
<li>For each key-value pair <i>s</i>-<i>n</i> in the <i>subject</i>
member of <i>graph map</i> ordered by <i>s</i>, append <i>n</i>
@@ -3826,7 +3826,7 @@
<code class="idlMemberName"><a href="#widl-JsonLdOptions-expandContext">expandContext</a></code>
as <tref>local context</tref>. If
<code class="idlMemberName"><a href="#widl-JsonLdOptions-expandContext">expandContext</a></code>
- is a <tref>JSON object</tref> having a <code>@context</code> member, pass that member's value instead.</li>
+ is a <tref>JSON object</tref> having an <code>@context</code> member, pass that member's value instead.</li>
<li>If the <i>input</i> has been retrieved, the response has an HTTP Link Header [[!RFC5988]]
using the <code>http://www.w3.org/ns/json-ld#context</code> link relation
and a content type of <code>application/json</code> or any media type
@@ -3842,7 +3842,7 @@
<li>Set <i>expanded</i> to the result of using the
<a href="#expansion-algorithm">Expansion algorithm</a>, passing the
<tref>active context</tref> and <i>input</i> as <i>element</i>.</li>
- <li>If <i>context</i> is a <tref>JSON object</tref> having a <code>@context</code> member, set
+ <li>If <i>context</i> is a <tref>JSON object</tref> having an <code>@context</code> member, set
<i>context</i> to that member's value.</li>
<li>Set <i>compacted</i> to the result of using the
<a href="#compaction-algorithm">Compaction algorithm</a>, passing
@@ -3894,7 +3894,7 @@
<code class="idlMemberName"><a href="#widl-JsonLdOptions-expandContext">expandContext</a></code>
as <tref>local context</tref>. If
<code class="idlMemberName"><a href="#widl-JsonLdOptions-expandContext">expandContext</a></code>
- is a <tref>JSON object</tref> having a <code>@context</code> member, pass that member's value instead.</li>
+ is a <tref>JSON object</tref> having an <code>@context</code> member, pass that member's value instead.</li>
<li>If the <i>input</i> has been retrieved, the response has an HTTP Link Header [[!RFC5988]]
using the <code>http://www.w3.org/ns/json-ld#context</code> link relation
and a content type of <code>application/json</code> or any media type
@@ -3951,7 +3951,7 @@
<code class="idlMemberName"><a href="#widl-JsonLdOptions-expandContext">expandContext</a></code>
as <tref>local context</tref>. If
<code class="idlMemberName"><a href="#widl-JsonLdOptions-expandContext">expandContext</a></code>
- is a <tref>JSON object</tref> having a <code>@context</code> member, pass that member's value instead.</li>
+ is a <tref>JSON object</tref> having an <code>@context</code> member, pass that member's value instead.</li>
<li>If the <i>input</i> has been retrieved, the response has an HTTP Link Header [[!RFC5988]]
using the <code>http://www.w3.org/ns/json-ld#context</code> link relation
and a content type of <code>application/json</code> or any media type
@@ -3967,7 +3967,7 @@
<li>Set <i>expanded</i> to the result of using the
<a href="#expansion-algorithm">Expansion algorithm</a>, passing the
<tref>active context</tref> and <i>input</i> as <i>element</i>.</li>
- <li>If <i>context</i> is a <tref>JSON object</tref> having a <code>@context</code> member, set
+ <li>If <i>context</i> is a <tref>JSON object</tref> having an <code>@context</code> member, set
<i>context</i> to that member's value.</li>
<li>Initialize an empty <i>identifier map</i> and a <i>counter</i> (set to <code>0</code>)
to be used by the
--- a/spec/latest/json-ld/index.html Wed Dec 04 11:44:29 2013 -0800
+++ b/spec/latest/json-ld/index.html Wed Dec 11 21:42:13 2013 +0100
@@ -773,7 +773,7 @@
<li>An <tref>IRI</tref> is generated for the <tref>string</tref> value specified using
<code>@id</code> or <code>@type</code>.</li>
<li>An <tref>IRI</tref> is generated for the <tref>string</tref> value of any key for which there
- are <tref>coercion</tref> rules that contain a <code>@type</code> key that is
+ are <tref>coercion</tref> rules that contain an <code>@type</code> key that is
set to a value of <code>@id</code> or <code>@vocab</code>.</li>
</ol>
@@ -858,7 +858,7 @@
-->
</pre>
-<p>The value of a <code>@type</code> key may also be a <tref>term</tref> defined in the <tref>active context</tref>:</p>
+<p>The value of an <code>@type</code> key may also be a <tref>term</tref> defined in the <tref>active context</tref>:</p>
<pre class="example" data-transform="updateExample"
title="Using a term to specify the type">
<!--
@@ -924,7 +924,7 @@
<p>This document uses an empty <code>@id</code>, which resolves to the document base.
However, if the document is moved to a different location, the <tref>IRI</tref> would change.
To prevent this without having to use an <tref>absolute IRI</tref>, a <tref>context</tref>
- may define a <code>@base</code> mapping, to overwrite the base IRI for the document.</p>
+ may define an <code>@base</code> mapping, to overwrite the base IRI for the document.</p>
<pre class="example" data-transform="updateExample"
title="Setting the document base in a document">
@@ -1081,7 +1081,7 @@
<ol>
<li>By utilizing the <code>@type</code> <tref>keyword</tref> when defining
- a <tref>term</tref> within a <code>@context</code> section.</li>
+ a <tref>term</tref> within an <code>@context</code> section.</li>
<li>By utilizing a <tref>value object</tref>.</li>
<li>By using a native JSON type such as <tref>number</tref>, <tref>true</tref>, or <tref>false</tref>.</li>
</ol>
@@ -2068,7 +2068,7 @@
is optimized away when processing the document, as it is just syntactic
sugar. However, <code>@set</code> is helpful when used within the context
of a document.
- Values of terms associated with a <code>@set</code> or <code>@list</code> container
+ Values of terms associated with an <code>@set</code> or <code>@list</code> container
are always represented in the form of an <tref>array</tref>,
even if there is just a single value that would otherwise be optimized to
a non-array form in compact form (see
@@ -2378,11 +2378,11 @@
-->
</pre>
- <p>The example above contains information about to secret agents that cannot be identified
- with an <tref>IRI</tref>. While expressing that <em>agent 1</em> knows <em>agent 2</em> is possible
- without using <tref title="blank node identifier">blank node identifiers</tref>, it is
- necessary assign <em>agent 1</em> an identifier so that it can be referenced from
- <em>agent 2</em>.</p>
+ <p>The example above contains information about two secret agents that cannot be identified
+ with an <tref>IRI</tref>. While expressing that <em>agent 1</em> knows <em>agent 2</em>
+ is possible without using <tref title="blank node identifier">blank node identifiers</tref>,
+ it is necessary to assign <em>agent 1</em> an identifier so that it can be referenced
+ from <em>agent 2</em>.</p>
<p>It is worth nothing that blank node identifiers may be relabeled during processing.
If a developer finds that they refer to the <tref>blank node</tref> more than once,
they should consider naming the node using a dereferenceable <tref>IRI</tref> so that
@@ -2478,12 +2478,11 @@
</pre>
<p>In the example above, the <strong>post</strong> <tref>term</tref> has
- been marked as an <tref>index map</tref>. The <strong>en</strong>,
- <strong>de</strong>, and <strong>ja</strong> keys will be ignored
- semantically, but preserved syntactically, by the JSON-LD Processor.
- This allows a developer to access the German version
- of the <strong>post</strong> using the following code snippet:
- <code>obj.post.de</code>.</p>
+ been marked as an <tref>index map</tref>. The <strong>en</strong> and
+ <strong>de</strong> keys will be ignored semantically, but preserved
+ syntactically, by the JSON-LD Processor. This allows a developer to
+ access the German version of the <strong>post</strong> using the
+ following code snippet: <code>obj.post.de</code>.</p>
<p>The interpretation of the data above is expressed in
the table below. Note how the index keys do not appear in the Linked Data
@@ -3035,9 +3034,9 @@
string</tref>.</p>
<p>A <tref>value object</tref> MUST be a <tref>JSON object</tref> containing the
- <code>@value</code> key. It MAY also contain a <code>@type</code>,
- a <code>@language</code>, an <code>@index</code>, or an <code>@context</code> key but MUST NOT contain
- both a <code>@type</code> and a <code>@language</code> key at the same time.
+ <code>@value</code> key. It MAY also contain an <code>@type</code>,
+ an <code>@language</code>, an <code>@index</code>, or an <code>@context</code> key but MUST NOT contain
+ both an <code>@type</code> and an <code>@language</code> key at the same time.
A <tref>value object</tref> MUST NOT contain any other keys that expand to an
<tref>absolute IRI</tref> or <tref>keyword</tref>.</p>
@@ -3069,7 +3068,7 @@
<code>@set</code> keyword, when used in the body of a JSON-LD document,
represents just syntactic sugar which is optimized away when processing the document.
However, it is very helpful when used within the context of a document. Values
- of terms associated with a <code>@set</code> or <code>@list</code> container
+ of terms associated with an <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 href="#compacted-document-form">compact document form</a>.
@@ -3160,14 +3159,14 @@
or the <tref title="keyword">keywords</tref> <code>@language</code>, <code>@base</code>,
and <code>@vocab</code>.</p>
- <p>If the <tref>context definition</tref> has a <code>@language</code> key,
+ <p>If the <tref>context definition</tref> has an <code>@language</code> key,
its value MUST have the lexical form described in [[!BCP47]] or be <tref>null</tref>.</p>
- <p>If the <tref>context definition</tref> has a <code>@base</code> key,
+ <p>If the <tref>context definition</tref> has an <code>@base</code> key,
its value MUST be an <tref>absolute IRI</tref>, a <tref>relative IRI</tref>,
or <tref>null</tref>.</p>
- <p>If the <tref>context definition</tref> has a <code>@vocab</code> key,
+ <p>If the <tref>context definition</tref> has an <code>@vocab</code> key,
its value MUST be a <tref>absolute IRI</tref>, a <tref>compact IRI</tref>,
a <tref>blank node identifier</tref>, a <tref>term</tref>, or <tref>null</tref>.</p>
@@ -3248,8 +3247,8 @@
<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>
- (<tref title="typed value">typed values</tref>) or <em>language-tagged strings</em>
- (<tref title="language-tagged string">language-tagged strings</tref>) whereas
+ (<tref title="typed value">typed values</tref>) or
+ <tref title="language-tagged string">language-tagged strings</tref> whereas
JSON-LD also supports JSON's native data types, i.e., <tref title="number">number</tref>,
<tref title="string">strings</tref>, and the boolean values <tref>true</tref>
and <tref>false</tref>. The JSON-LD Processing Algorithms and API specification [[JSON-LD-API]]