--- a/spec/latest/json-ld-syntax/index.html Sun Sep 30 16:26:08 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html Mon Oct 01 12:26:04 2012 +0200
@@ -467,7 +467,7 @@
<ol>
<li>It is easy for humans to read and write.</li>
<li>It is easy for machines to parse and generate.</li>
-<li>It has a syntax that is familiar across a large number of programming
+<li>It has a syntax that is familiar across a large number of programming
languages.</li>
<li>It is capable of representing many different types of data using two
universal data structures; a collection of key-value pairs and lists.</li>
@@ -476,24 +476,24 @@
<p>
JSON has become a very popular data-interchange format on the Web, particularly
for <a href="http://en.wikipedia.org/wiki/REST">REST</a>-based Web Services.
-Unfortunately, it has a number of short-comings that other Web-native data
+Unfortunately, it has a number of short-comings that other Web-native data
formats do not have:
</p>
<ol>
<li>There is no standardized, universal identifier mechanism for
<tref>JSON object</tref>s.</li>
-<li>The meaning of the keys used in a
+<li>The meaning of the keys used in a
<tref>JSON object</tref>s are ambiguous and often conflict with other data
-published on the Web.
+published on the Web.
</li>
-<li>There is no standardized way for a value in a <tref>JSON object</tref> to
+<li>There is no standardized way for a value in a <tref>JSON object</tref> to
refer to a <tref>JSON object</tref> on a different site on the Web.</li>
-<li>A developer cannot express the language associated with a
+<li>A developer cannot express the language associated with a
<tref>string</tref> value in a standardized manner.</li>
-<li>There is no standard mechanism to associate datatypes with values such as
+<li>There is no standard mechanism to associate datatypes with values such as
dates, times, weights, and distances.</li>
-<li>There is no facility to express a Web of information (directed graph),
+<li>There is no facility to express a Web of information (directed graph),
such as a social network, in a standardized manner.</li>
</ol>
@@ -509,13 +509,13 @@
<li>A way to dis-ambiguate the keys used between multiple JSON documents
by mapping them to <tref>IRI</tref>s via a <tref>context</tref>.
</li>
-<li>A mechanism in which a value in a <tref>JSON object</tref> may
+<li>A mechanism in which a value in a <tref>JSON object</tref> may
refer to a <tref>JSON object</tref> on a different site on the Web.</li>
-<li>The ability to express the language associated with a
+<li>The ability to express the language associated with a
<tref>string</tref> value.</li>
-<li>A way to associate datatypes with values such as dates, times,
+<li>A way to associate datatypes with values such as dates, times,
weights, and distances.</li>
-<li>A facility to express one or more directed graphs, such as a social
+<li>A facility to express one or more directed graphs, such as a social
network, in a single document.</li>
</ol>
@@ -536,12 +536,12 @@
name links, when followed, provide more information about the name, and
4) The data expresses links to data on other Web sites. These properties
allow data published on the Web to work much like Web pages do today. One
-can start at one piece of Linked Data, and follow the links to other pieces
-of data that are hosted on different sites across the Web.
+can start at one piece of Linked Data, and follow the links to other pieces
+of data that are hosted on different sites across the Web.
</p>
<p>
-JSON-LD is a way of expressing <tref>Linked Data</tref> on the Web. The
+JSON-LD is a way of expressing <tref>Linked Data</tref> on the Web. The
JSON-LD data model encapsulates the following concepts:
</p>
@@ -560,8 +560,8 @@
<div class="note">
<p>
-A <tref>Linked Data</tref> document does not necessarily need to be expressed
-in JSON-LD. The notion of <tref>Linked Data</tref> is a concept independent of
+A <tref>Linked Data</tref> document does not necessarily need to be expressed
+in JSON-LD. The notion of <tref>Linked Data</tref> is a concept independent of
any given serialization format.
</p>
</div>
@@ -570,13 +570,13 @@
<p style="text-align: center;">
Figure 1: An example of a linked data graph.
</p>
-<p>There are a number of best practices that can ensure that developers
+<p>There are a number of best practices that can ensure that developers
will generate good Linked Data for the Web. JSON-LD
-formalizes those techniques by providing a mechanism to map JSON data,
+formalizes those techniques by providing a mechanism to map JSON data,
i.e., keys and values, to <tref>IRI</tref>s. This does not mean
that JSON-LD requires every key or value to be an IRI, but rather ensures that
keys and values can be mapped to IRIs if the developer desires to transform
-their data into <tref>Linked Data</tref>.
+their data into <tref>Linked Data</tref>.
</p>
</section>
@@ -584,8 +584,8 @@
<section>
<h2>General Terminology</h3>
- <p>The following is an explanation of the general terminology used in this
- document. Many of the terms should be familiar to developers that have
+ <p>The following is an explanation of the general terminology used in this
+ document. Many of the terms should be familiar to developers that have
used JSON:</p>
<dl>
@@ -1040,15 +1040,11 @@
<p><code>foaf:name</code> above will automatically expand out to the IRI
<code>http://xmlns.com/foaf/0.1/name</code>. See <a href="#compact-iris"></a> for more details.</p>
-<p>If the <code>@vocab</code> is set, all keys that do not match a <tref>term</tref> or a <tref>prefix</tref>
- are
-
-
-It is often common that all types and properties come from the same vocabulary. JSON-LD's
-<code>@vocab</code> keyword allows to set a base <tref>IRI</tref> to be used for all properties and types
-that that do not match a <tref>term</tref>, a <tref>prefix</tref>, or an <tref>absolute IRI</tref>
-(i.e., do not contain a colon). The <code>@vocab</code> mapping MUST have a value of a simple string with the
-lexical form of an absolute IRI.</p>
+<p>It is often common that all types and properties come from the same vocabulary. JSON-LD's
+ <code>@vocab</code> keyword allows to set a base <tref>IRI</tref> to be used for all properties and types
+ that that do not match a <tref>term</tref>, a <tref>prefix</tref>, or an <tref>absolute IRI</tref>
+ (i.e., do not contain a colon). The <code>@vocab</code> mapping MUST have a value of a simple string with the
+ lexical form of an absolute IRI.</p>
<pre class="example" data-transform="updateExample"
title="Vocabulary base IRI">
@@ -2929,7 +2925,7 @@
<section id="grammar-node-reference">
<h2>Node Reference</h2>
-<p>A <tref>JSON object</tref> containing only the <code>@id</code>
+<p>A <tref>JSON object</tref> containing only the <code>@id</code>
(or an alias for <code>@id</code>) is a <tref>node reference</tref> and not a
<tref>node definition</tref>.
</p>
@@ -3157,14 +3153,14 @@
</p>
<p>JSON-LD allows properties to be BNodes, while RDF does
- not. Expressing properties as BNodes in JSON-LD only becomes an issue
+ not. Expressing properties as BNodes in JSON-LD only becomes an issue
(and could raise an exception) when it is transformed to RDF.</p>
- <p>Note that the JSON-LD data model is silent on the topic of
- <tref title="unlabeled node">unlabeled nodes</tref>. Nevertheless,
- this specification allows for the expression of
- <tref title="unlabeled node">unlabeled nodes</tref>, as most graph-based data
- sets on the Web contain a number of associated nodes that are not named and
+ <p>Note that the JSON-LD data model is silent on the topic of
+ <tref title="unlabeled node">unlabeled nodes</tref>. Nevertheless,
+ this specification allows for the expression of
+ <tref title="unlabeled node">unlabeled nodes</tref>, as most graph-based data
+ sets on the Web contain a number of associated nodes that are not named and
thus are not directly de-referenceable.
</p>