--- a/spec/latest/json-ld-syntax/index.html Sun Aug 19 13:40:23 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html Mon Aug 20 12:29:01 2012 +0200
@@ -479,18 +479,18 @@
footprint when processing documents. For example, to expand a JSON-LD document
from a compacted form, only one pass is required over the data.</dd>
<dt>Linked Data-centric</dt>
- <dd>The focus on Linked Data is placed at a much higher priority than the
- focus on the Semantic Web. One outcome of this ordering of
- priorities is an aggressively reduced focus on the Semantic Web stack
- (RDF [[RDF-CONCEPTS]], TURTLE [[TURTLE-TR]], triple stores, and
- SPARQL [[RDF-SPARQL-QUERY]]).
- While this may be off-putting to proponents of the Semantic Web, the audience
+ <dd>The focus on Linked Data is placed at a much higher priority than the
+ focus on the Semantic Web. One outcome of this ordering of
+ priorities is an aggressively reduced focus on the Semantic Web stack
+ (RDF [[RDF-CONCEPTS]], TURTLE [[TURTLE-TR]], triple stores, and
+ SPARQL [[RDF-SPARQL-QUERY]]).
+ While this may be off-putting to proponents of the Semantic Web, the audience
for this specification are Web developers that want a gentler introduction
and a simpler technology stack for using Linked Data in their Web applications.
Semantic Web concepts, such as conversion to and from RDF, are fully supported
- by JSON-LD, but the implementation of these features are not elaborated upon
- in this specification. See <a href="#relationship-to-other-rdf-formats"></a>
- for more information about how JSON-LD integrates into the more traditional
+ by JSON-LD, but the implementation of these features are not elaborated upon
+ in this specification. See <a href="#relationship-to-other-rdf-formats"></a>
+ for more information about how JSON-LD integrates into the more traditional
Semantic Web stack.
</dd>
</dl>
@@ -1072,7 +1072,7 @@
<h2>Specifying the Type</h2>
<p>The type of a particular subject can be specified using the
-<code>@type</code> <tref>keyword</tref>. Specifying the type in this way will
+<code>@type</code> <tref>keyword</tref>. Specifying the type in this way will
generate a triple of the form (subject, type, type-IRI). To be considered
<tref>Linked Data</tref>, types MUST be uniquely identified by
an <tref>IRI</tref>.</p>
@@ -1413,10 +1413,10 @@
also possible to use a <tref>term</tref> or a <tref>compact IRI</tref> to
express the value of a type.</p>
-The <code>@type</code> <tref>keyword</tref> is also used to associate a type
-with a <tref>subject</tref>. The concept of an <tdef>subject type</tdef> and
-a <tdef>value type</tdef> are different. This is similar to object-oriented
-programming languages where both scalar and structured types use the same
+The <code>@type</code> <tref>keyword</tref> is also used to associate a type
+with a <tref>subject</tref>. The concept of an <tdef>subject type</tdef> and
+a <tdef>value type</tdef> are different. This is similar to object-oriented
+programming languages where both scalar and structured types use the same
class inheritance mechanism, even though scalar types and structured types are
inherently different.
@@ -1440,14 +1440,14 @@
<p>
The first use of <code>@type</code> associates a <tref>subject type</tref>
(<code>http://schema.org/BlogPosting</code>) with the <tref>subject</tref>,
-which is expressed using the <code>@id</code> <tref>keyword</tref>.
+which is expressed using the <code>@id</code> <tref>keyword</tref>.
The second use of <code>@type</code> associates a <tref>value type</tref>
-(<code>http://www.w3.org/2001/XMLSchema#dateTime</code>) with the
-<tref>object</tref>, which is expressed using the <code>@value</code>
+(<code>http://www.w3.org/2001/XMLSchema#dateTime</code>) with the
+<tref>object</tref>, which is expressed using the <code>@value</code>
<tref>keyword</tref>. As a general rule, when <code>@value</code> and
-<code>@type</code> are used in the same <tref>JSON object</tref>
+<code>@type</code> are used in the same <tref>JSON object</tref>
in JSON-LD data, the <code>@type</code> <tref>keyword</tref> is expressing a
-<tref>value type</tref>. Otherwise, the <code>@type</code>
+<tref>value type</tref>. Otherwise, the <code>@type</code>
<tref>keyword</tref> is expressing a <tref>subject type</tref>.
</p>
@@ -1470,8 +1470,8 @@
<li>By utilizing the <code>@language</code> <tref>keyword</tref> when defining
a <tref>term</tref> within a <code>@context</code> section.</li>
<li>By utilizing the expanded form for specifying objects.</li>
- <li>By utilizing the <code>@container</code> <tref>keyword</tref> with a
- value of <code>@language</code> when defining a <tref>term</tref> within
+ <li>By utilizing the <code>@container</code> <tref>keyword</tref> with a
+ value of <code>@language</code> when defining a <tref>term</tref> within
a <code>@context</code> section. This usage pattern is called a
<tdef>language map</tdef>.</li>
</ol>
@@ -1533,8 +1533,8 @@
<p>Systems that support multiple languages often need to express data values in
each language. Typically, such systems also try to ensure that developers have
-a programatically easy way to navigate the datastructures for the
-language-specific data. In this case, <tref>language map</tref>s
+a programatically easy way to navigate the datastructures for the
+language-specific data. In this case, <tref>language map</tref>s
may be utilized.</p>
<pre class="example" data-transform="updateExample"
@@ -1564,8 +1564,8 @@
<p>In the example above, the title is expressed in three languages; English,
Russian, and Japanese. To access the data above in a programming language
supporting dot-notation accessors for object properties, a developer may use the
-<strong>PROPERTY</strong>.<strong>LANGUAGE</strong> pattern. For example, to
-access the Japanese version of the title, a developer would use the following
+<strong>PROPERTY</strong>.<strong>LANGUAGE</strong> pattern. For example, to
+access the Japanese version of the title, a developer would use the following
code snippet: <code>obj.title.ja</code>.</p>
</section>
@@ -1923,7 +1923,7 @@
great deal of confusion among developers attempting to understand the JSON-LD document.</p>
<p>Type coercion is performed using the unexpanded value of the key,
- which MUST have an exact match for an entry in the
+ which MUST have an exact match for an entry in the
<tref>active context</tref>.</p>
</section>
@@ -1967,7 +1967,7 @@
{
"@context":
{
- ****"title": { "@id": ["http://purl.org/dc/terms/title",
+ ****"title": { "@id": ["http://purl.org/dc/terms/title",
"http://schema.org/name",
"http://www.w3.org/2000/01/rdf-schema#label"] }****,
},
@@ -1977,20 +1977,20 @@
-->
</pre>
-<p>While the term above is only used once outside of the <code>@context</code>,
-a JSON-LD processor will internally transform the document above into
+<p>While the term above is only used once outside of the <code>@context</code>,
+a JSON-LD processor will internally transform the document above into
the following set of statements:</p>
<pre class="example" data-transform="updateExample">
<!--
-<http://example.com/book>
+<http://example.com/book>
<http://purl.org/dc/terms/title>
"The Count of Monte Cristo" .
-<http://example.com/book>
- <http://schema.org/name>
+<http://example.com/book>
+ <http://schema.org/name>
"The Count of Monte Cristo" .
-<http://example.com/book>
- <http://www.w3.org/2000/01/rdf-schema#label>
+<http://example.com/book>
+ <http://www.w3.org/2000/01/rdf-schema#label>
"The Count of Monte Cristo" .
-->
</pre>
@@ -2687,7 +2687,7 @@
<section id="grammar-subject-definition">
<h3>Subject Definition</h3>
<p>A <tref>subject definition</tref> is a <tref>JSON object</tref>
- containing one or more key/value pairs. Keys are <tref>IRI</tref>s,
+ containing one or more key/value pairs. Keys are <tref>IRI</tref>s,
<tref>compact IRI</tref>s,
<tref>term</tref>s defined within the <tref>active context</tref>, or one of the
following keywords:</p>
@@ -2724,7 +2724,7 @@
key, it's value
MUST be a <tref>string</tref> having the lexical form of <tref>IRI</tref>,
<tref>compact IRI</tref> (including <tref>unlabeled node</tref>), or a
- <tref>term</tref> defined in the <tref>active context</tref> expanding
+ <tref>term</tref> defined in the <tref>active context</tref> expanding
into an <tref>IRI</tref> or an <tref>unlabeled node</tref>.</p>
<pre class="example" data-transform="updateExample"
@@ -2816,9 +2816,9 @@
alias expanding to any other keyword.</p>
<p>Other keys MUST expand to an <tref>absolute IRI</tref> using the
- <tref>active context</tref>. The values associated with these keys
+ <tref>active context</tref>. The values associated with these keys
may be any of the following:</p>
-
+
<ul>
<li><tref>string</tref>,</li>
<li><tref>number</tref>,</li>
@@ -2920,28 +2920,28 @@
<section id="grammar-expanded-values">
<h2>Expanded Values</h2>
-<p>An <tdef>expanded value</tdef> is a <tref>JSON object</tref> containing the
- <code>@value</code> key, or an alias for the <code>@value</code> value key.
- It MAY
+<p>An <tdef>expanded value</tdef> is a <tref>JSON object</tref> containing the
+ <code>@value</code> key, or an alias for the <code>@value</code> value key.
+ It MAY
also contain the <code>@type</code> or <code>@language</code> keys, or their
respective keyword aliases. An <tref>expanded value</tref> MUST NOT
- contain keys other than <code>@value</code>, <code>@language</code>, and
+ contain keys other than <code>@value</code>, <code>@language</code>, and
<code>@type</code>.
- An <tref>expanded value</tref> MUST NOT contain both the
+ An <tref>expanded value</tref> MUST NOT contain both the
<code>@language</code> and <code>@type</code> keys.</p>
- <p>The value of the <code>@value</code> key, or its alias, MUST be either a
- <tref>string</tref>, <tref>number</tref>, <tref>true</tref>, or
+ <p>The value of the <code>@value</code> key, or its alias, MUST be either a
+ <tref>string</tref>, <tref>number</tref>, <tref>true</tref>, or
<tref>false</tref>.</p>
-<p>If an <tref>expanded value</tref> contains a <code>@language</code> key,
- it MUST NOT contain any other key except <code>@value</code>. The value of
- the <code>@language</code> key MUST have the lexical form described in
+<p>If an <tref>expanded value</tref> contains a <code>@language</code> key,
+ it MUST NOT contain any other key except <code>@value</code>. The value of
+ the <code>@language</code> key MUST have the lexical form described in
[[!BCP47]], or be <tref>null</tref>.</p>
-<p>If an <tref>expanded value</tref> contains a <code>@type</code> key, it
+<p>If an <tref>expanded value</tref> contains a <code>@type</code> key, it
MUST NOT contain any other key except <code>@value</code>. The value of
<code>@type</code> MUST be a <tref>term</tref>, <tref>compact IRI</tref>,
<tref>absolute IRI</tref>, or <code>null</code>.</p>
<p>See <a href="#typed-values"></a> and <a href="#language-values"></a>
- for a further discussion of
+ for a further discussion of
<tref title="expanded value">expanded values</tref>.</p>
</section>
@@ -2949,7 +2949,7 @@
<h2>List and Set Values</h2>
<p>A <tdef>list</tdef> is a <tref>JSON object</tref> having only the <code>@list</code>
- <tref>keyword</tref>. Its value MUST be an <tref>array</tref> any of the following:</p>
+ <tref>keyword</tref>. Its value MUST be an <tref>array</tref> of any of the following:</p>
<ul>
<li><tref>string</tref>,</li>
<li><tref>subject reference</tref>,</li>