--- a/rdf-turtle/index.html Wed Jun 20 11:54:26 2012 -0700
+++ b/rdf-turtle/index.html Wed Jun 20 14:02:17 2012 -0700
@@ -244,10 +244,6 @@
<p>
The token <code>a</code> in the predicate position of a Turtle triple represents the IRI <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</code> .
</p>
- </section>
-
- <section id="prefixed-names">
- <h3>Prefixed Names in Turtle</h3>
<p>
A prefixed name is a prefix label and a local part, separated by a colon ":".
@@ -278,24 +274,6 @@
<li><a href="#reserved">reserved character escape sequences</a>, e.g. <code>wgs:lat\-long</code></li>
</ul>
</div>
- </section>
- <section>
- <h3>Relative IRIs</h3>
- <p>
- Relative IRIs are resolved with base IRIs as per <a href="http://www.ietf.org/rfc/rfc3986.txt" class="norm">Uniform Resource Identifier (URI): Generic Syntax</a> [<a href="#rfc3986">RFC3986</a>] using only the basic algorithm in section 5.2.
- Neither Syntax-Based Normalization nor Scheme-Based Normalization (described in sections 6.2.2 and 6.2.3 of RFC3986) are performed.
- Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of <a href="http://www.ietf.org/rfc/rfc3987.txt" class="norm">Internationalized Resource Identifiers (IRIs)</a> [<a href="#rfc3987">RFC3987</a>].
- </p>
- <p>
- The <code>@base</code> directive defines the Base IRI used to resolve relative IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content".
- Section 5.1.2, "Base URI from the Encapsulating Entity" defines how the In-Scope Base IRI may come from an encapsulating document, such as a SOAP envelope with an xml:base directive or a mime multipart document with a Content-Location header.
- The "Retrieval URI" identified in 5.1.3, Base "URI from the Retrieval URI", is the URL from which a particular Turtle document was retrieved.
- If none of the above specifies the Base URI, the default Base URI (section 5.1.4, "Default Base URI") is used.
- Each <code>@base</code> directive sets a new In-Scope Base URI, relative to the previous one.
- </p>
- </section>
- <section>
- <h3>Examples of IRIs</h3>
<p>The following Turtle document contains examples of all the diffrent ways of writting IRIs in Turtle.</p>
@@ -596,6 +574,22 @@
</p>
</section>
+ <section>
+ <h3>IRI References</h3>
+ <p>
+ Relative IRIs are resolved with base IRIs as per <a href="http://www.ietf.org/rfc/rfc3986.txt" class="norm">Uniform Resource Identifier (URI): Generic Syntax</a> [<a href="#rfc3986">RFC3986</a>] using only the basic algorithm in section 5.2.
+ Neither Syntax-Based Normalization nor Scheme-Based Normalization (described in sections 6.2.2 and 6.2.3 of RFC3986) are performed.
+ Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of <a href="http://www.ietf.org/rfc/rfc3987.txt" class="norm">Internationalized Resource Identifiers (IRIs)</a> [<a href="#rfc3987">RFC3987</a>].
+ </p>
+ <p>
+ The <code>@base</code> directive defines the Base IRI used to resolve relative IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content".
+ Section 5.1.2, "Base URI from the Encapsulating Entity" defines how the In-Scope Base IRI may come from an encapsulating document, such as a SOAP envelope with an xml:base directive or a mime multipart document with a Content-Location header.
+ The "Retrieval URI" identified in 5.1.3, Base "URI from the Retrieval URI", is the URL from which a particular Turtle document was retrieved.
+ If none of the above specifies the Base URI, the default Base URI (section 5.1.4, "Default Base URI") is used.
+ Each <code>@base</code> directive sets a new In-Scope Base URI, relative to the previous one.
+ </p>
+ </section>
+
<section id="sec-escapes">
<h3>Escape Sequences</h3>