--- a/spec/latest/json-ld-api/index.html Mon Feb 18 16:55:22 2013 -0800
+++ b/spec/latest/json-ld-api/index.html Tue Feb 19 00:23:07 2013 -0500
@@ -774,9 +774,9 @@
<dt><tdef>RDF object</tdef></dt>
<dd>An <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-object">object</tref> as specified by [[RDF-CONCEPTS]].</dd>
<dt><tdef>RDF triple</tdef></dt>
- <dd>An <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-triple">triple</tref> as specified by [[RDF-CONCEPTS]].</dd>
+ <dd>A <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-triple">triple</tref> as specified by [[RDF-CONCEPTS]].</dd>
<dt><tdef>RDF dataset</tdef></dt>
- <dd>An <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">dataset</tref> as specified by [[RDF-CONCEPTS]] representing a collection of
+ <dd>A <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">dataset</tref> as specified by [[RDF-CONCEPTS]] representing a collection of
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-graph">RDF graphs</tref>.</dd>
</dl>
@@ -1875,7 +1875,7 @@
a <tref>compact IRI</tref>:
<ol class="algorithm">
<li>Split <em>value</em> into a <tref>prefix</tref> and <em>suffix</em>
- at the first occurence of a colon (<code>:</code>).</li>
+ at the first occurrence of a colon (<code>:</code>).</li>
<li>If <tref>prefix</tref> does not equal underscore (<code>_</code>)
and <em>suffix</em> does not begin with double-forward-slash
(<code>//</code>), then it may be a <tref>compact IRI</tref>:
@@ -3044,7 +3044,7 @@
key <code>@none</code>. This allows the
<a href="#term-selection-subalgorithm">Term Selection</a> subalgorithm to fall back
to choosing more generic <tref title="term">terms</tref> when a more
-specificly-matching <tref>term</tref> is not available for a particular
+specifically-matching <tref>term</tref> is not available for a particular
<tref>IRI</tref> and value combination.
</p>
@@ -3961,7 +3961,7 @@
<section class="informative">
<h4>General Solution</h4>
-
+
<p>The JSON-LD document is expanded converted to a <em>node map</em> using the
<a href="#node-map-generation">Node Map Generation algorithm</a>.
This allows each graph represented within the document to be
@@ -4015,7 +4015,7 @@
<section class="informative">
<h4>General Solution</h4>
-
+
<p>Identify <tref title="RDF subject">RDF subjects</tref> and
<tref title="RDF predicate">RDF predicates</tref> from the
<tref>node</tref> identifier and properties. Transform each property value
@@ -4092,7 +4092,7 @@
<section class="informative">
<h4>General Solution</h4>
-
+
<p>Transform <tref title="value object">value objects</tref> to their
<tref>RDF literal</tref> form and
<tref title="node object">node objects</tref> to an
@@ -4101,7 +4101,7 @@
<section>
<h4>Algorithm</h4>
-<p>The algoritm takes as it's sole argument <em>item</em> which MUST BE either a <tref>value object</tref> or <tref>node object</tref>.</p>
+<p>The algorithm takes as its sole argument <em>item</em> which MUST be either a <tref>value object</tref> or <tref>node object</tref>.</p>
<ol class="algorithm">
<li>If <em>item</em> is a <tref>value object</tref>:
<ol class="algorithm">
@@ -4110,7 +4110,6 @@
to the value associated with the <code>@type</code> key in
<em>item</em>, or <code>null</code> if <em>item</em> does not contain
that key.</li>
- <li>If value is true or false, then set value its canonical lexical form as defined in the section Data Round Tripping. If datatype is null, set it to xsd:boolean.</li>
<li>If <em>value</em> is <tref>true</tref> or
<tref>false</tref>, then set <em>value</em> to its
<tref>canonical lexical form</tref> as defined
@@ -4135,7 +4134,7 @@
<li>Return <em>literal</em>.</li>
</ol>
</li>
- <li>Otherwise, <em>item</em> MUST BE a <tref>node object</tref> containing only <code>@id</code> having an <tref>IRI</tref> or <tref>blank node identifier</tref> value. Return that value.</li>
+ <li>Otherwise, <em>item</em> MUST be a <tref>node object</tref> containing only <code>@id</code> having an <tref>IRI</tref> or <tref>blank node identifier</tref> value. Return that value.</li>
</ol>
</section>
</section> <!-- Object to RDF Conversion Subalgorithm -->
@@ -4159,7 +4158,7 @@
<section class="informative">
<h4>General Solution</h4>
-
+
<p>Allocate a new <tref>blank node</tref> for each element of the
<tref>list</tref> and generate <code>rdf:first</code> and
<code>rdf:rest</code> <tref title="RDF triple">triples</tref> for each,
@@ -4226,7 +4225,7 @@
<section class="informative">
<h4>General Solution</h4>
-
+
<p>Iterate through each graph in the dataset, converting <tref title="rdf collection">RDF Collections</tref> into a <tref>list</tref> and generating an JSON-LD document in expanded form for all <tref title="RDF literal">RDF literals</tref>, <tref title="IRI">IRIs</tref> and <tref title="blank node identifier">blank node identifiers</tref>.</p>
</section>
@@ -4257,7 +4256,7 @@
<li>If <em>predicate</em> is <code>rdf:first</code>,
use the entry in <em>graph.listMap</em> identified by
<em>subject</em>, initializing it to a new <tref>JSON object</tref>
- if nesessary. Represent <em>object</em> in <tref>expanded
+ if necessary. Represent <em>object</em> in <tref>expanded
form</tref>, as described in <a href="#value-expansion">Value
Expansion</a>. Add the resulting <em>object representation</em> to
the entry indexed by <em>first</em>, and skip to the next
@@ -4342,7 +4341,7 @@
<li>If <em>object</em> is a <tref>blank node</tref>,
use the entry in <em>graph.listMap</em> indexed by
<em>object</em>, initializing it to a new <tref>JSON
- object</tref> if nesessary. Add an entry for <em>head</em> with
+ object</tref> if necessary. Add an entry for <em>head</em> with
<em>object representation</em>.</li>
<li>Append <em>object representation</em> to the array value for
<em>key</em>, creating an entry in <em>value</em> if
@@ -4401,7 +4400,7 @@
<p>The canonical lexical form of an <em>integer</em>, i.e., a number without fractions
or a number coerced to <strong>xsd:integer</strong>, is a finite-length sequence of decimal
- digits (<code>0-9</code>) with an optional leading minus sign; leading zeroes are prohibited.
+ digits (<code>0-9</code>) with an optional leading minus sign; leading zeros are prohibited.
To convert the number in JavaScript, implementers can use the following snippet of code:</p>
<pre class="example" data-transform="updateExample"
@@ -4414,10 +4413,10 @@
<p>The canonical lexical form of a <em>double</em>, i.e., a number with fractions
or a number coerced to <strong>xsd:double</strong>, consists of a mantissa followed by the
character "E", followed by an exponent. The mantissa MUST be a decimal number. The exponent
- MUST be an integer. Leading zeroes and a preceding plus sign (<code>+</code>) are prohibited
+ MUST be an integer. Leading zeros and a preceding plus sign (<code>+</code>) are prohibited
in the exponent. If the exponent is zero, it must be indicated by <code>E0</code>.
For the mantissa, the preceding optional plus sign is prohibited and the decimal point is
- required. Leading and trailing zeroes are prohibited subject to the following: number
+ required. Leading and trailing zeros are prohibited subject to the following: number
representations must be normalized such that there is a single digit which is non-zero to the
left of the decimal point and at least a single digit to the right of the decimal point unless
the value being represented is zero. The canonical representation for zero is <code>0.0E0</code>.
@@ -4443,7 +4442,7 @@
are the strings <strong>true</strong> and <strong>false</strong>.</p>
<p>When JSON-native <tref>number</tref>s, are type coerced, lossless data round-tripping can not
- be guaranted as rounding errors might occur. Additionally, only literals typed as
+ be guaranteed as rounding errors might occur. Additionally, only literals typed as
<strong>xsd:integer</strong>, <strong>xsd:double</strong>, and <strong>xsd:boolean</strong> are
automatically converted back to their JSON-native counterparts in when
<a href="#rdf-conversion">converting from RDF</a>.</p>
@@ -4535,7 +4534,7 @@
<dt>(object or DOMString)? context</dt>
<dd>The context to use when compacting the flattened <code>input</code>; either
in the form of an <tref>JSON object</tref> or as <tref>IRI</tref>. If
- <tref>null</tref> is passed, the result will not be compacted but keept
+ <tref>null</tref> is passed, the result will not be compacted but kept
in expanded form.</dd>
<dt>JsonLdCallback callback</dt>
<dd>A callback that is called when processing completed successfully