--- a/spec/latest/json-ld-syntax/index.html Sun Jul 29 18:41:27 2012 -0700
+++ b/spec/latest/json-ld-syntax/index.html Sun Jul 29 19:26:09 2012 -0700
@@ -542,7 +542,8 @@
rest of this section:
</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Sample JSON object">
<!--
{
"name": "Manu Sporny",
@@ -634,7 +635,8 @@
<p>These Linked Data <tref>term</tref>s are typically collected in a
context document that would look something like this:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Context definition">
<!--
{
"@context":
@@ -659,7 +661,8 @@
it can be referenced from a JSON-LD document by adding a single line. The JSON markup shown in the previous
section could be changed as follows:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Adding context reference to JSON document">
<!--
{
****"@context": "http://json-ld.org/contexts/person.jsonld",****
@@ -685,7 +688,8 @@
<p>Contexts MAY be specified in-line. This ensures that JSON-LD documents
can be processed when a JSON-LD processor does not have access to the Web.</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="In-line context definition">
<!--
{
****"@context":
@@ -732,7 +736,8 @@
the document. The following example specifies an external context and then
layers a local context on top of the external context:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="External and local contexts">
<!--
{
****"@context": [
@@ -777,7 +782,8 @@
names in <tref title="JSON object">JSON objects</tref>, machines are able to automatically expand the terms to
something meaningful and unambiguous, like this:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded terms">
<!--
{
"****http://xmlns.com/foaf/0.1/name****": "Manu Sporny",
@@ -834,7 +840,8 @@
<p>IRIs can be expressed directly in the key position like so:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="IRI as a key">
<!--
{
...
@@ -852,7 +859,8 @@
<p>Term expansion occurs for IRIs if the value matches a <tref>term</tref> defined within the
<tref>active context</tref>:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Term expansion from context definition">
<!--
{
"****@context****":
@@ -880,7 +888,8 @@
combination, and the prefix matches a <tref>term</tref> defined within the
<tref>active context</tref>:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Prefix expansion">
<!--
{
"****@context****":
@@ -900,7 +909,8 @@
<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>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded IRI definition">
<!--
{
...
@@ -922,7 +932,8 @@
<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>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Type coercion">
<!--
{****
"@context":
@@ -971,7 +982,8 @@
first piece of information needed by the JSON-LD processor in order to
create the (subject, property, object) tuple, also known as a triple.</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Identifying the Subject">
<!--
{
"@context":
@@ -1025,7 +1037,8 @@
<tref>Linked Data</tref>, types MUST be uniquely identified by
an <tref>IRI</tref>.</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Specifying the Type">
<!--
{
...
@@ -1046,7 +1059,8 @@
by setting the <code>@language</code> key in the <code>@context</code> or in a
<tref>term</tref> definition:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="String Internationalization">
<!--
{
****"@context":
@@ -1067,7 +1081,8 @@
<p>It is possible to override the default language by using the expanded
form of a value:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded value with language">
<!--
{
"@context": {
@@ -1087,7 +1102,8 @@
value by omitting the <code>@language</code> tag or setting it to
<code>null</code> when expressing the expanded value:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded value to remove language">
<!--
{
"@context": {
@@ -1114,7 +1130,8 @@
<p>To clear the default language for a subtree, <code>@language</code> can
be set to <code>null</code> in a <tref>local context</tref> as follows:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Clearing default language">
<!--
{
"@context": {
@@ -1209,7 +1226,8 @@
containing a colon will be interpreted by a JSON-LD processor as an IRI.
</p>
<p>Consider the following example:</p>
- <pre class="example" data-transform="updateExample">
+ <pre class="example" data-transform="updateExample"
+ title="Compact IRIs">
<!--
{
"@context":
@@ -1243,7 +1261,8 @@
</p>
<p>It's also possible to use compact IRIs within the context as shown in the
following example:</p>
- <pre class="example" data-transform="updateExample">
+ <pre class="example" data-transform="updateExample"
+ title="Using vocabularies">
<!--
{
"@context":
@@ -1283,7 +1302,8 @@
<p>The first example uses the <code>@type</code> keyword to associate a
type with a particular <tref>term</tref> in the <code>@context</code>:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded term definition with type coercion">
<!--
{
****"@context":
@@ -1308,7 +1328,8 @@
<p>The second example uses the expanded form of setting the type information
in the body of a JSON-LD document:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded value with type">
<!--
{
"@context":
@@ -1369,7 +1390,8 @@
<p>The first example uses the <code>@language</code> keyword to associate a
type with a particular <tref>term</tref> in the <code>@context</code>:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded term definition with language coerceion">
<!--
{
****"@context":
@@ -1394,7 +1416,8 @@
<p>The second example uses the expanded form of setting the language information
in the body of a JSON-LD document:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded value with language">
<!--
{
"@context":
@@ -1438,7 +1461,8 @@
<p>The following example demonstrates the use of an external context:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="External context">
<!--
{
****"@context": "http://json-ld.org/contexts/person.jsonld"****,
@@ -1452,7 +1476,8 @@
<p>Authors may also import multiple contexts or a combination of external
and local contexts by specifying a list of contexts:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Combining external and local contexts">
<!--
{
****"@context":
@@ -1486,7 +1511,8 @@
more deeply nested contexts overriding the values in previously defined
contexts:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Nested contexts within subject definitions">
<!--
{
****"@context":
@@ -1551,7 +1577,8 @@
<p>The following example demonstrates the use of an external context with an
ordinary JSON document:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Specifing context through HTTP header">
<!--
GET /ordinary-json-document.json HTTP/1.1
Host: example.com
@@ -1592,7 +1619,8 @@
<tref>compact IRI</tref>, or an <tref>absolute IRI</tref>. Such
an object is called a <tref>subject reference</tref>.</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded term definition">
<!--
{
"@context":
@@ -1614,7 +1642,8 @@
<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">
+<pre class="example" data-transform="updateExample"
+ title="Expanded term definition with language">
<!--
{
"@context": {
@@ -1679,7 +1708,8 @@
<p>The example below demonstrates how a JSON-LD author can coerce values to
<tref>typed value</tref>s, IRIs and lists.</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Expanded term definition with types">
<!--
{
"@context":
@@ -1726,7 +1756,8 @@
This allows coercion rules to be applied to keys which are not represented as a simple <tref>term</tref>.
For example:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="Term definition with absolute IRI">
<!--
{
"@context":
@@ -1778,7 +1809,8 @@
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
the <code>xsd</code> namespace when defining <tref>typed value</tref>s:</p>
-<pre class="example" data-transform="updateExample">
+<pre class="example" data-transform="updateExample"
+ title="IRI expansion within context">
<!--
{
"@context":