--- a/spec/latest/json-ld-syntax/index.html Sun Jul 29 18:36:59 2012 -0700
+++ b/spec/latest/json-ld-syntax/index.html Sun Jul 29 18:41:27 2012 -0700
@@ -397,7 +397,7 @@
the collection is <em>unordered</em> by default. While order is
preserved in regular JSON arrays, it is not in regular JSON-LD arrays
unless specific markup is provided
- (see <a href="#sets-and-lists">Sets and Lists</a>).</dd>
+ (see <a href="#sets-and-lists"></a>).</dd>
<dt><tdef>string</tdef></dt><dd>
A string is a sequence of zero or more Unicode characters,
wrapped in double quotes, using backslash escapes (if necessary). A
@@ -564,36 +564,35 @@
document. These short-hand names are called <tref>term</tref>s and help
developers to express specific identifiers in a compact manner. The
<code>@context</code> keyword is described in detail in the section titled
- <a href="#the-context">The Context</a>.</dd>
+ <a href="#the-context"></a>.</dd>
<dt><code>@graph</code></dt><dd>Used to explicitly label a <tref>linked data graph</tref>.
- This keyword is described in the section titled <a href="#named-graphs">Named Graphs</a>.</dd>
+ This keyword is described in <a href="#named-graphs"></a>.</dd>
<dt><code>@id</code></dt>
<dd>Used to uniquely identify <em>things</em> that are being described in the document.
- This keyword is described in the section titled
- <a href="#identifying-the-subject">Identifying the Subject</a>.</dd>
+ This keyword is described in
+ <a href="#identifying-the-subject"></a>.</dd>
<dt><code>@value</code></dt>
<dd>Used to specify the data that is associated with a particular
- <tref>property</tref> in the graph. This keyword is described
- in the sections titled
- <a href="#string-internationalization">String Internationalization</a> and
- <a href="#typed-values">Typed Values</a>.</dd>
+ <tref>property</tref> in the graph. This keyword is described in
+ <a href="#string-internationalization"></a> and
+ <a href="#typed-values"></a>.</dd>
<dt><code>@language</code></dt>
<dd>Used to specify the native language for a particular value or the default
language of a JSON-LD document. This keyword is described in the section titled
- <a href="#string-internationalization">String Internationalization</a>.</dd>
+ <a href="#string-internationalization"></a>.</dd>
<dt><code>@type</code></dt>
<dd>Used to set the data type of a <tref>subject</tref> or
<tref>typed value</tref>. This keyword is described in the section titled
- <a href="#typed-values">Typed Values</a>.</dd>
+ <a href="#typed-values"></a>.</dd>
<dt><code>@container</code></dt>
<dd>Used to set the container of a particular value.
- This keyword is described in the section titled <a href="#sets-and-lists">Sets and Lists</a>.</dd>
+ This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
<dt><code>@list</code></dt>
<dd>Used to express an ordered set of data.
- This keyword is described in the section titled <a href="#sets-and-lists">Sets and Lists</a>.</dd>
+ This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
<dt><code>@set</code></dt>
<dd>Used to express an unordered set of data.
- This keyword is described in the section titled <a href="#sets-and-lists">Sets and Lists</a>.</dd>
+ This keyword is described in the section titled <a href="#sets-and-lists"></a>.</dd>
<dt><code>:</code></dt>
<dd>The separator for JSON keys and values that use
<tref title="compact_iri">compact IRIs</tref>.</dd>
@@ -896,7 +895,7 @@
</pre>
<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">Compact IRIs</a> for more details.</p>
+<code>http://xmlns.com/foaf/0.1/name</code>. See <a href="#compact-iris"></a> for more details.</p>
<p>An <tref>IRI</tref> is generated when a JSON object is used in the
value position that contains an <code>@id</code> keyword:</p>
@@ -918,7 +917,7 @@
This facility MAY also be used to link to another
<tref>subject definition</tref> using a mechanism called
<tref>embedding</tref>, which is covered in the section titled
- <a href="#embedding">Embedding</a>.</p>
+ <a href="#embedding"></a>.</p>
<p>If type <tref>coercion</tref> rules are specified in the <code>@context</code> for
a particular <tref>term</tref> or property IRI, an IRI is generated:</p>
@@ -1109,7 +1108,7 @@
<p class="note">Please note that language associations MUST only be applied
to plain literal <tref>string</tref>s. That is, <tref>typed value</tref>s
- or values that are subject to <a href="#type-coercion">type coercion</a>
+ or values that are subject to <a href="#type-coercion"></a>
won't be language tagged.</p>
<p>To clear the default language for a subtree, <code>@language</code> can
@@ -1135,7 +1134,7 @@
<p class="note">JSON-LD allows one to associate language information with
<tref>term</tref>s.
- See <a href="#expanded-term-definition">Expanded Term Definition</a> for
+ See <a href="#expanded-term-definition"></a> for
more details.</p>
</section>
@@ -1148,10 +1147,10 @@
MUST be processed by a conforming JSON-LD processor. However, JSON-LD
describes a specific syntax to use for expressing Linked Data. This
includes the use of specific keywords, as identified in <a
- href="#syntax-tokens-and-keywords">Syntax Tokens and Keywords</a> for
+ href="#syntax-tokens-and-keywords"></a> for
expressing <a title="subject definition">subject definitions</a>, values,
and the <a>context</a>. See <a
- href="#json-ld-authoring-guidelines">Appendix A</a> for authoring
+ href="#json-ld-grammar"></a> for authoring
guidelines and a BNF description of JSON-LD.</p>
</section>
@@ -1584,8 +1583,8 @@
<p>Within a <tref>context</tref> definition, <tref>term</tref>s MAY be
defined using an expanded notation to allow for additional information
associated with the term to be specified (see also
- <a href="#type-coercion">Type Coercion</a> and
- <a href="#sets-and-lists">Sets and Lists</a>).</p>
+ <a href="#type-coercion"></a> and
+ <a href="#sets-and-lists"></a>).</p>
<p>Instead of using a string representation of an IRI, the IRI MAY be
specified using a <tref>JSON object</tref> having an <code>@id</code> key.
@@ -1611,8 +1610,8 @@
</pre>
<p>This allows additional information to be associated with the term. This
- MAY be used for <a href="#type-coercion">Type Coercion</a>,
- <a href="#sets-and-lists">Sets and Lists</a>), or to associate language
+ MAY be used for <a href="#type-coercion"></a>,
+ <a href="#sets-and-lists"></a>), or to associate language
information with a term as shown in the following example:</p>
<pre class="example" data-transform="updateExample">
@@ -1665,7 +1664,7 @@
<tref>term</tref>s. Using type coercion, value representation is preserved without requiring
the data type to be specified with each piece of data.</p>
-<p>Type coercion is specified within an <a href="#expanded-term-definition">expanded term definition</a>
+<p>Type coercion is specified within an <a href="#expanded-term-definition"></a>
using the <code>@type</code> key. The value of this key represents a type IRI and MUST take the form of
a <tref>term</tref>, <tref>compact IRI</tref>, <tref>absolute IRI</tref>, or the <tref>keyword</tref> <code>@id</code>. Specifying
<code>@id</code> indicates that within the body of a JSON-LD document, a string value of a <tref>term</tref> coerced to
@@ -1774,7 +1773,7 @@
<section>
<h3>IRI Expansion Within a Context</h3>
<p>In general, normal IRI expansion rules apply
- anywhere an IRI is expected (see <a href="#iris">IRIs</a>). Within
+ anywhere an IRI is expected (see <a href="#iris"></a>). Within
a <tref>context</tref> definition, this can mean that terms defined
within the context MAY also be used within that context as long as
there are no circular dependencies. For example, it is common to use
@@ -2053,7 +2052,7 @@
Values of terms associated with a <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 a
- <a href="#compact-document-form">compacted document</a>. This makes post-processing of
+ <a href="#compact-document-form"></a>. This makes post-processing of
the data easier as the data is always in array form, even if the array only
contains a single value.</p>
@@ -2315,7 +2314,7 @@
data in a deterministic form. It has been optimized to ensure that the code
that developers have to write is minimized compared to the code that would
have to be written to operate on
-<a href="#compact-document-form">compact document form</a>.</p>
+<a href="#compact-document-form"></a>.</p>
</section>
@@ -2383,7 +2382,7 @@
</pre>
<p>The compaction algorithm enables a developer to map any document into an
- application-specific compacted form by first <a href="#expanded-document-form">expanding the document</a>.
+ application-specific compacted form by first <a href="#expanded-document-form"></a>.
While the context provided above mapped <code>http://xmlns.com/foaf/0.1/name</code>
to <strong>name</strong>, it could have also mapped it to any arbitrary string
provided by the developer. This powerful mechanism, along with another