a number of small editorial changes

Author: pchampin

common/terms.html

@@ -86,12 +86,12 @@
     is a string that can be used as an identifier for a <a>blank node</a> within the scope of a JSON-LD document.
     Blank node identifiers begin with <code>_:</code>.</dd>
   <dt><dfn>compact IRI</dfn></dt><dd>
-    A compact IRI is has the form of <a>prefix</a>:<em>suffix</em>
+    A compact IRI has the form of <a>prefix</a>:<em>suffix</em>
     and is used as a way of expressing an <a>IRI</a> without needing to define separate <a>term</a> definitions
     for each IRI contained within a common vocabulary identified by <a>prefix</a>.</dd>
   <dt><dfn>context</dfn></dt><dd>
     A set of rules for interpreting a <a>JSON-LD document</a>
-    as specified in <a data-cite="JSON-LD11#the-context">The Context</a> of the JSON-LD Syntax specification [[JSON-LD11]].</dd>
+    as specified in the <a data-cite="JSON-LD11#the-context">The Context</a> section of the JSON-LD Syntax specification [[JSON-LD11]].</dd>
   <dt><dfn>datatype IRI</dfn></dt><dd>
     A <a data-cite="RDF11-CONCEPTS#dfn-datatype-iri" class="externalDFN">datatype IRI</a>
     as specified by [[RDF11-CONCEPTS]].</dd>
@@ -142,18 +142,18 @@
     a <a>node object</a> or a <a>value object</a>
     in the input.</dd>
   <dt><dfn>graph name</dfn></dt><dd>
-    The <a>IRI</a> identifying a <a data-cite="RDF11-CONCEPTS#dfn-graph-name" class="externalDFN">named graph</a>.</dd>
+    The <a>IRI</a> or <a>blank node</a> identifying a <a data-cite="RDF11-CONCEPTS#dfn-graph-name" class="externalDFN">named graph</a>.</dd>
   <dt class="changed"><dfn>id map</dfn></dt><dd class="changed">
     An <a>id map</a> is a <a>dictionary</a> value of a <a>term</a>
-    defined with <code>@container</code> set to <code>@id</code>,
-    whose keys are interpreted as <a>IRIs</a> representing
-    the <code>@id</code> of the associated <a>node object</a>;
-    value MUST be a <a>node object</a>.
-    If the value contains a key expanding to <code>@id</code>,
-    it's value MUST be equivalent to the referencing key.</dd>
+    defined with <code>@container</code> set to <code>@id</code>.
+    The values of the <a>id map</a> MUST be a <a>node objects</a>,
+    and its keys are interpreted as <a>IRIs</a> representing
+    the <code>@id</code> of the associated <a>node object</a>.
+    If a value in the <a>id map</a> contains a key expanding to <code>@id</code>,
+    it's value MUST be equivalent to the referencing key in the <a>id map</a>.</dd>
   <dt class="changed"><dfn>graph object</dfn></dt><dd class="changed">
     A <a>graph object</a> represents a <a>named graph</a>
-    represented as the value of a <a>dictionary member</a> within a <a>node object</a>.
+    as the value of a <a>dictionary member</a> within a <a>node object</a>.
     When expanded, a graph object MUST have an <code>@graph</code> <a>member</a>,
     and MAY also have <code>@id</code>, and <code>@index</code> <a>members</a>.
     A <dfn class="preserve">simple graph object</dfn>
@@ -240,7 +240,7 @@
   <dt><dfn>nested property</dfn></dt><dd>
     A <a>nested property</a> is a key in a <a>node object</a>
     whose value is a <a>dictionary</a> containing <a>members</a> which are treated as if they were values of the <a>node object</a>.
-    The <a>nested property</a> itself is semantically meaningless used only to create a sub-structure within a <a>node object</a>.
+    The <a>nested property</a> itself is semantically meaningless and used only to create a sub-structure within a <a>node object</a>.
   </dd>
   <dt><dfn>node</dfn></dt><dd>
     Every <a data-cite="RDF11-CONCEPTS#dfn-node" class="externalDFN">node</a> is an <a>IRI</a>,

index.html

@@ -394,7 +394,7 @@ <h2>Design Goals and Rationale</h2>
    <dd>A JSON-LD document is always a valid JSON document. This ensures that
     all of the standard JSON libraries work seamlessly with JSON-LD documents.</dd>
    <dt>Expressiveness</dt>
-   <dd>The syntax serializes directed graphs. This ensures that almost
+   <dd>The syntax serializes labeled directed graphs. This ensures that almost
     every real world data model can be expressed.</dd>
    <dt>Terseness</dt>
    <dd>The JSON-LD syntax is very terse and human readable, requiring as
@@ -435,7 +435,7 @@ <h2>Data Model Overview</h2>
       such as a <a>string</a>, <a>number</a>,
       <a>typed values</a> (like dates and times)
       or an <a>IRI</a>.</p>
-    <p class="changed">Within a directed graph, nodes with may
+    <p class="changed">Within a directed graph, nodes may
       be <em>unnamed</em>, i.e., not identified by an <a>IRI</a> or representing
       data such as <a>strings</a> or <a>numbers</a>. Such nodes are called <a>blank nodes</a>,
       and may be identified using a <a>blank node identifier</a>.
@@ -966,7 +966,7 @@ <h2>The Context</h2>
       <a href="#sets-and-lists">ordered values</a>, and
       <a href="#nested-properties">nested properties</a>.
       More advanced features related to the JSON-LD Context are covered in
-      section <a href="#advanced-concepts" class="sectionRef"></a>.</p>
+      <a href="#advanced-concepts" class="sectionRef"></a>.</p>
   </section>
 
 <section class="informative">
@@ -981,7 +981,7 @@ <h2>IRIs</h2>
     <em>scheme</em> along with <em>path</em> and optional <em>query</em> and
     <em>fragment</em> segments. A <a>relative IRI</a> is an IRI
     that is relative to some other <a>absolute IRI</a>.
-    In JSON-LD, with exceptions are as described below, all <a>relative IRIs</a>
+    In JSON-LD, with exceptions that are as described below, all <a>relative IRIs</a>
     are resolved relative to the <a>base IRI</a>.</p>
 
   <p class="note">As noted in <a href="#how-to-read-this-document" class="sectionRef"></a>,
@@ -1279,7 +1279,7 @@ <h2>Uses of JSON Objects</h2>
     <li><a>Numbers</a>, which describe literal numeric values,</li>
     <li><a>Strings</a>, which may describe literal string values, or be used as the keys in a <a>JSON object</a>.</li>
     <li><a>Boolean</a> <code>true</code> and <code>false</code>, which describe literal boolean values,</li>
-    <li><code>Null</code>, which describes the absense of a value,</li>
+    <li><code>null</code>, which describes the absense of a value,</li>
     <li><a>Arrays</a>, which describe an ordered set of values of any type, and</li>
     <li><a>JSON objects</a>, which provide a set of <a>dictionary members</a>, relating keys with values.</li>
   </ul>
@@ -1363,7 +1363,7 @@ <h2>Specifying the Type</h2>
     given <a>node object</a>, or the property for which a node is a value. For
     example, in the <em>schema.org</em> vocabulary, the <em>givenName</em>
     property is associated with a <em>Person</em>. Therefore, one may reason that
-    if a <a>node object</a> contains the property <em>firstName</em>, that the
+    if a <a>node object</a> contains the property <em>givenName</em>, that the
     type is a <em>Person</em>; making this explicit with <code>@type</code> helps
     to clarify the association.</p>
 
@@ -1578,7 +1578,7 @@ <h1>Advanced Concepts</h1>
     describe such value typing.</p></dd>
   <dt>Value ordering</dt>
   <dd><p>In JSON, a property with an array value implies an implicit order;
-    arrays in JSON-LD do not provide an ordering of the contained elements by
+    arrays in JSON-LD do not convey any ordering of the contained elements by
     default, unless defined using embedded structures or through a context
     definition. See <a href="#sets-and-lists" class="sectionRef"></a> for a
     further discussion.</p></dd>
@@ -2539,7 +2539,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     The <a>prefix</a> is a <a>term</a> taken from the
     <a>active context</a> and is a short string identifying a
     particular <a>IRI</a> in a JSON-LD document. For example, the
-    prefix <code>foaf</code> may be used as a short hand for the
+    prefix <code>foaf</code> may be used as a shorthand for the
     Friend-of-a-Friend vocabulary, which is identified using the <a>IRI</a>
     <code>http://xmlns.com/foaf/0.1/</code>. A developer may append
     any of the FOAF vocabulary terms to the end of the prefix to specify a short-hand
@@ -3859,7 +3859,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     The use of <a>JSON literals</a> creates blobs of data which are not available for interpretation.
     It is for use only in the rare cases that JSON cannot be represented as JSON-LD.</p>
 
-  <p>When a term is defined with <code>@type</code> <code>@json</code>,
+  <p>When a term is defined with <code>@type</code> set to <code>@json</code>,
     a JSON-LD processor will treat the value as a <a>JSON literal</a>,
     rather than interpreting it further as JSON-LD.
     In the <a>expanded document form</a>, such JSON will become the value of <code>@value</code> within a <a>value object</a>
@@ -4241,12 +4241,12 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
 
   ex1:barney ex2:mnemonic "the sidekick" .
 
-  [ ex2:fred ex1:barney, ex1:barney] .
+  [] ex2:fred ex1:barney, ex1:barney.
   -->
   </pre>
 </aside>
 
-<p class="note">The triple <code>[ ex2:fred ex1:barney, ex1:barney] .</code> is emitted twice,
+<p class="note">The triple <code>[] ex2:fred ex1:barney .</code> is emitted twice,
   but exists only once in an output dataset, as it is a duplicate triple.</p>
 
 <p>Terms may also be defined using <a>absolute IRIs</a>
@@ -4567,7 +4567,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
 
 <p>A JSON-LD author can express multiple values in a compact way by using
   <a>arrays</a>. Since graphs do not describe ordering for links
-  between nodes, arrays in JSON-LD do not provide an ordering of the
+  between nodes, arrays in JSON-LD do not convey any ordering of the
   contained elements by default. This is exactly the opposite from regular JSON
   arrays, which are ordered by default. For example, consider the following
   simple document:</p>
@@ -4993,8 +4993,9 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
 <p>The implementation of <a>lists</a> in RDF depends on linking anonymous nodes
   together using the properties <code>rdf:first</code> and
   <code>rdf:rest</code>, with the end of the list defined as the resource
-  <code>rdf:nil</code>. This can be represented as statments, as the "statements"
-  tab illustrates.</p>
+  <code>rdf:nil</code>, as the "statements" tab illustrates.
+  This allows order to be represented within an unordered set of statements.
+</p>
 
 <p>Both JSON-LD and Turtle provide shortcuts for representing ordered lists.</p>
 
@@ -5276,7 +5277,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
 </aside>
 
 <p>This describes the use of this <a>array</a> as being unordered,
-  and order is maintained when processing a document. By default,
+  and order may change when processing a document. By default,
   arrays of values are unordered, but this may be made explicit by
   setting <code>@container</code> to <code>@set</code> in the <a>context</a>: