Swapped section 4.1 with 4.2.
authorManu Sporny <msporny@digitalbazaar.com>
Fri, 22 Jun 2012 23:25:50 -0400
changeset 739 62299461b2fe
parent 738 c0d6046465b6
child 740 e7ef310d5fc7
child 761 9c6341444376
Swapped section 4.1 with 4.2.
spec/latest/json-ld-syntax/index.html
--- a/spec/latest/json-ld-syntax/index.html	Fri Jun 22 23:21:41 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html	Fri Jun 22 23:25:50 2012 -0400
@@ -1280,89 +1280,6 @@
 </p>
 
 <section>
-<h2>Typed Values</h2>
-
-<p>
-  A value with an associated type, also known as a
-  <tdef>typed value</tdef>, is indicated by associating a value with
-  an <tref>IRI</tref> which indicates the value's type. Typed values may be
-  expressed in JSON-LD in two ways:
-</p>
-
-<ol>
-  <li>By utilizing the <code>@type</code> <tref>keyword</tref> when defining
-    a <tref>term</tref> within a <code>@context</code> section.</li>
-  <li>By utilizing the expanded form for specifying objects.</li>
-</ol>
-
-<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">
-<!--
-{
-  ****"@context":
-  {
-    "modified":
-    {
-      "@id": "http://purl.org/dc/terms/modified",
-      "@type": "http://www.w3.org/2001/XMLSchema#dateTime"
-    }
-  },****
-...
-  "modified": "2010-05-29T14:17:39+02:00",
-...
-}
--->
-</pre>
-
-<p>The <em>modified</em> key's value above is automatically type coerced to a
-datetime value because of the information specified in the
-<code>@context</code>.</p>
-
-<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">
-<!--
-{
-  "@context":
-  {
-    "modified":
-    {
-      "@id": "http://purl.org/dc/terms/modified"
-    }
-  },
-...
-  "modified":
-  ****{
-    "@value": "2010-05-29T14:17:39+02:00",
-    "@type": "http://www.w3.org/2001/XMLSchema#dateTime"
-  }****
-...
-}
--->
-</pre>
-
-<p>Both examples above would generate an object with the value of
-<code>2010-05-29T14:17:39+02:00</code> and the type of
-<code>http://www.w3.org/2001/XMLSchema#dateTime</code>. Note that it is
-also possible to use a <tref>term</tref> or a <tref>compact IRI</tref> to
-express the value of a type.</p>
-
-<p class="note">
-  The <code>@type</code> <tref>keyword</tref> is also used to associate a type with
-  a <tref>subject</tref>. Although the same keyword is used in both places,
-  the concept of an <em>object type</em> and a <em>value type</em>
-  are different. This is similar to object-oriented programming languages
-  where both scalar and structured types use the same class inheritance
-  mechanism, even though scalar types and structured types are
-  inherently different.
-</p>
-
-</section>
-
-<section>
   <h2>Compact IRIs</h2>
   <p>
     <tref>Term</tref>s in <tref>Linked Data</tref> documents may draw from
@@ -1460,6 +1377,89 @@
 </section>
 
 <section>
+<h2>Typed Values</h2>
+
+<p>
+  A value with an associated type, also known as a
+  <tdef>typed value</tdef>, is indicated by associating a value with
+  an <tref>IRI</tref> which indicates the value's type. Typed values may be
+  expressed in JSON-LD in two ways:
+</p>
+
+<ol>
+  <li>By utilizing the <code>@type</code> <tref>keyword</tref> when defining
+    a <tref>term</tref> within a <code>@context</code> section.</li>
+  <li>By utilizing the expanded form for specifying objects.</li>
+</ol>
+
+<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">
+<!--
+{
+  ****"@context":
+  {
+    "modified":
+    {
+      "@id": "http://purl.org/dc/terms/modified",
+      "@type": "http://www.w3.org/2001/XMLSchema#dateTime"
+    }
+  },****
+...
+  "modified": "2010-05-29T14:17:39+02:00",
+...
+}
+-->
+</pre>
+
+<p>The <em>modified</em> key's value above is automatically type coerced to a
+datetime value because of the information specified in the
+<code>@context</code>.</p>
+
+<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">
+<!--
+{
+  "@context":
+  {
+    "modified":
+    {
+      "@id": "http://purl.org/dc/terms/modified"
+    }
+  },
+...
+  "modified":
+  ****{
+    "@value": "2010-05-29T14:17:39+02:00",
+    "@type": "http://www.w3.org/2001/XMLSchema#dateTime"
+  }****
+...
+}
+-->
+</pre>
+
+<p>Both examples above would generate an object with the value of
+<code>2010-05-29T14:17:39+02:00</code> and the type of
+<code>http://www.w3.org/2001/XMLSchema#dateTime</code>. Note that it is
+also possible to use a <tref>term</tref> or a <tref>compact IRI</tref> to
+express the value of a type.</p>
+
+<p class="note">
+  The <code>@type</code> <tref>keyword</tref> is also used to associate a type with
+  a <tref>subject</tref>. Although the same keyword is used in both places,
+  the concept of an <em>object type</em> and a <em>value type</em>
+  are different. This is similar to object-oriented programming languages
+  where both scalar and structured types use the same class inheritance
+  mechanism, even though scalar types and structured types are
+  inherently different.
+</p>
+
+</section>
+
+<section>
 <h2>External Contexts</h2>
 
 <p>Authors may choose to declare JSON-LD <tref>context</tref>s in external