--- a/spec/latest/json-ld-syntax/index.html Tue Feb 19 09:13:26 2013 -0800
+++ b/spec/latest/json-ld-syntax/index.html Tue Feb 19 09:15:53 2013 -0800
@@ -357,7 +357,7 @@
This keyword is described in <a href="#named-graphs"></a>.</dd>
<dt><code>:</code></dt>
<dd>The separator for JSON keys and values that use
- <tref title="compact_iri">compact IRIs</tref>.</dd>
+ <tref title="compact iri">compact IRIs</tref>.</dd>
</dl>
<p>For the avoidance of doubt, all keys, <tref title="keyword">keywords</tref>,
@@ -487,10 +487,10 @@
and to specify whether <tref title="array">array</tref> values are to be
interpreted as <a href="#sets-and-lists">sets or lists</a>.
<tref title="expanded term definition">Expanded term definitions</tref> may
- be defined using <tref title="absolute_iri">absolute</tref> or
- <tref title="compact_iri">compact IRIs</tref> as keys, which is
+ be defined using <tref title="absolute iri">absolute</tref> or
+ <tref title="compact iri">compact IRIs</tref> as keys, which is
mainly used to associate type or language information with an
- <tref title="absolute_iri">absolute</tref> or <tref>compact IRI</tref>.</p>
+ <tref title="absolute iri">absolute</tref> or <tref>compact IRI</tref>.</p>
<p><tref title="context">Contexts</tref> can either be directly embedded
into the document or be referenced. Assuming the context document in the previous
@@ -567,7 +567,7 @@
relative to the <tdef>base IRI</tdef> associated with the document, which
is typically the directory path containing the document.</p>
- <p><tref title="absolute_iri">IRIs</tref> can be expressed directly in the key
+ <p><tref title="absolute iri">IRIs</tref> can be expressed directly in the key
position like so:</p>
<pre class="example" data-transform="updateExample"
@@ -702,7 +702,7 @@
<h2>Node Identifiers</h2>
<p>To be able to externally reference <tref title="node">nodes</tref>
- in a <tref title="json-ld_graph">graph</tref>, it is important that each <tref>node</tref> has
+ in a <tref title="json-ld graph">graph</tref>, it is important that each <tref>node</tref> has
an unambiguous identifier. <tref title="IRI">IRIs</tref> are a fundamental concept of
<tref>Linked Data</tref>, and <tref title="node">nodes</tref> should have a de-referenceable
identifier used to name and locate them. For <tref title="node">nodes</tref> to be truly linked,
@@ -711,7 +711,7 @@
can fetch the resource associated with the IRI and get back a description of the
<tref>node</tref>.</p>
- <p><tref title="json-ld_document">JSON-LD documents</tref> may also contain descriptions
+ <p><tref title="json-ld document">JSON-LD documents</tref> may also contain descriptions
of other <tref title="node">nodes</tref>, so it is necessary to be able to
uniquely identify each <tref>node</tref> so that the data is associated
with the correct <tref>node</tref> in an unambiguous way.</p>
@@ -860,7 +860,7 @@
<p><code>foaf:name</code> above will automatically expand out to the IRI
<code>http://xmlns.com/foaf/0.1/name</code>.</p>
- <p>Terms are interpreted as <tref title="compact_iri">compact IRIs</tref> if they contain at least one
+ <p>Terms are interpreted as <tref title="compact iri">compact IRIs</tref> if they contain at least one
colon and the first colon is not followed by two slashes (<code>//</code>, as in
<code>http://example.com</code>). To generate the full <tref>IRI</tref>,
the value is first split into a <em>prefix</em> and <em>suffix</em> at the first
@@ -1110,7 +1110,7 @@
<tref>compact IRI</tref> or <tref>absolute IRI</tref> if a colon is present; otherwise, they are interpreted
as <tref>relative IRI</tref>.
-<p><tref title="term">Terms</tref> or <tref title="compact_iri">compact IRIs</tref> used as the value of a
+<p><tref title="term">Terms</tref> or <tref title="compact iri">compact IRIs</tref> used as the value of a
<code>@type</code> key may be defined within the same context. This means that one may specify a
<tref>term</tref> like <code>xsd</code> and then use <code>xsd:integer</code> within the same
context definition.</p>
@@ -1187,7 +1187,7 @@
</tbody>
</table>
-<p>Terms may also be defined using <tref title="absolute_iri">absolute IRIs</tref> or <tref title="compact_iri">compact IRIs</tref>.
+<p>Terms may also be defined using <tref title="absolute iri">absolute IRIs</tref> or <tref title="compact iri">compact IRIs</tref>.
This allows coercion rules to be applied to keys which are not represented as a simple <tref>term</tref>.
For example:</p>
@@ -1735,7 +1735,7 @@
-->
</pre>
-<p><tref title="compact_iri">Compact IRIs</tref>
+<p><tref title="compact iri">Compact IRIs</tref>
and <tref title="IRI">IRIs</tref> may be used on the left-hand side of a
<tref>term</tref> definition.</p>
@@ -1776,7 +1776,7 @@
</p>
<p>
-<tref title="absolute_iri">Absolute IRIs</tref> may also be used in the key position in a <tref>context</tref>:
+<tref title="absolute iri">Absolute IRIs</tref> may also be used in the key position in a <tref>context</tref>:
</p>
<pre class="example" data-transform="updateExample"
@@ -2649,7 +2649,7 @@
<p>A <tref>node object</tref> MUST be a <tref>JSON object</tref>. All keys
which are not <tref title="IRI">IRIs</tref>,
- <tref title="compact_iri">compact IRIs</tref>, <tref title="term">terms</tref>
+ <tref title="compact iri">compact IRIs</tref>, <tref title="term">terms</tref>
valid in the <tref>active context</tref>, or one of the following
<tref title="keyword">keywords</tref> MUST be ignored when processed:</p>