--- a/rdf-turtle/index.html Wed Jun 20 14:35:53 2012 -0700
+++ b/rdf-turtle/index.html Wed Jun 20 14:54:27 2012 -0700
@@ -182,7 +182,7 @@
</p>
<p>
- The <a href="#sec-grammar">Turtle Grammar</a> and <a href="#sec-parsing">Parsing</a> sections define the construction of an RDF graph from a Turtle document.
+ The construction of an RDF graph from a Turtle document is defined in <a href="#sec-grammar" class="sectionRef">Turtle Grammar</a> and <a href="#sec-parsing" class="sectionRef">Parsing</a>.
</p>
</section>
@@ -240,7 +240,7 @@
<a href="../rdf-concepts/index.html#dfn-iri">IRIs</a> may be written as relative or absolute IRIs or prefixed names.
Relative and absolute IRIs are enclosed in '<' and '>' and may contain <a href="#numeric">numeric escape sequences</a> (described below). For example <code><http://example.org/#green-goblin></code>.
</p>
-
+ <p>Relative IRIs like <code><#green-goblin<</code> are resolved relative to the current base IRI. A new base IRI can be defined using the <code>@base</code> directive. Specifics of this operation are defined in <a href="#iri-references" class="sectionRef"></a> </p>
<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>
@@ -593,9 +593,9 @@
<li>Turtle documents
<li>Turtle parsers
</ul>
- <p>A conforming <strong>Turtle document</strong> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#sec-grammar">Turtle Grammar</a>, starting with the <a href="#grammar-production-turtleDoc"><code>turtleDoc</code> production</a>. A Turtle document serializes an RDF graph.</p>
+ <p>A conforming <strong>Turtle document</strong> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#sec-grammar" class="sectionRef"></a>, starting with the <a href="#grammar-production-turtleDoc"><code>turtleDoc</code> production</a>. A Turtle document serializes an RDF graph.</p>
- <p>A conforming <strong>Turtle parser</strong> is a system capable of reading Turtle documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing">Parsing</a>, available to the application, usually through some form of API.</p>
+ <p>A conforming <strong>Turtle parser</strong> is a system capable of reading Turtle documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing" class="sectionRef"></a>, available to the application, usually through some form of API.</p>
<p>The IRI that identifies the Turtle language is: <code>http://www.w3.org/ns/formats/Turtle</code></p>
@@ -607,8 +607,7 @@
The content encoding of Turtle content is always UTF-8. Charset
parameters on the mime type are required until such time as the
<code>text/</code> media type tree permits UTF-8 to be sent without a
- charset parameter. See <a href="#sec-mediaReg">B. Internet Media
- Type, File Extension and Macintosh File Type</a> for the media type
+ charset parameter. See <a href="#sec-mediaReg" class="sectionRef"></a> for the media type
registration form.
</p>
</section>
@@ -831,7 +830,7 @@
<!-- The Turtle grammar uses the same productions and terminals to create these terms as does <a href="http://www.w3.org/TR/rdf-sparql-query/#grammar">SPARQL</a>. --><!-- This set is listed in <a href="http://www.w3.org/TR/rdf-sparql-query/#docTerminology">SPARQL §1.2.4</a>. -->
- This section maps a string conforming to the grammar in <a href="#sec-grammar-grammar">section 4.4</a> to a set of triples by mapping strings matching productions and lexical tokens to RDF terms or their components (e.g. language tags, lexical forms of literals). Some productions change the parser state (base or prefix declarations).</p>
+ This section maps a string conforming to the grammar in <a href="#sec-grammar-grammar" class="sectionRef"></a> to a set of triples by mapping strings matching productions and lexical tokens to RDF terms or their components (e.g. language tags, lexical forms of literals). Some productions change the parser state (base or prefix declarations).</p>
<section id="sec-parsing-state">
<h3>Parser State</h3>
@@ -852,7 +851,7 @@
<section id="sec-parsing-terms">
<h3>RDF Term Constructors</h3>
- <p>This table maps productions and lexical tokens to <code>RDF terms</code> or components of <code>RDF terms</code> listed in <a href="#sec-parsing">section 5</a>:</p>
+ <p>This table maps productions and lexical tokens to <code>RDF terms</code> or components of <code>RDF terms</code> listed in <a href="#sec-parsing" class="sectionRef"></a>:</p>
<table>
<thead>
@@ -879,7 +878,7 @@
</tbody>
</table>
- <p><a id="unescape">¹</a> <a href="#sec-escapes">Escape Sequences</a> defines a mapping from <code>escaped unicode strings</code> to <code>unicode strings</code>. The following lexical tokens are unescaped to produce <code>unicode strings</code>: <a class="type IRI" href="#grammar-production-IRIREF">IRIREF</a>, <!-- <a class="type PNAME_NS" href="#grammar-production-PNAME_NS">PNAME_NS</a>, --><!-- <a class="type IRI" href="#grammar-production-PNAME_LN">PNAME_LN</a>, --><a class="type lexicalForm" href="#grammar-production-STRING_LITERAL1">STRING_LITERAL1</a>, <a class="type lexicalForm" href="#grammar-production-STRING_LITERAL2">STRING_LITERAL2</a>, <a class="type lexicalForm" href="#grammar-production-STRING_LITERAL_LONG1">STRING_LITERAL_LONG1</a> and <a class="type lexicalForm" href="#grammar-production-STRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a><!-- and <a class="type langTag" href="#grammar-production-LANGTAG">LANGTAG</a> --><!-- and <a class="type bNode" href="#grammar-production-BLANK_NODE_LABEL">BLANK_NODE_LABEL</a> -->.</p>
+ <p><a id="unescape">¹</a> <a href="#sec-escapes" class="sectionRef">Escape Sequences</a> defines a mapping from <code>escaped unicode strings</code> to <code>unicode strings</code>. The following lexical tokens are unescaped to produce <code>unicode strings</code>: <a class="type IRI" href="#grammar-production-IRIREF">IRIREF</a>, <!-- <a class="type PNAME_NS" href="#grammar-production-PNAME_NS">PNAME_NS</a>, --><!-- <a class="type IRI" href="#grammar-production-PNAME_LN">PNAME_LN</a>, --><a class="type lexicalForm" href="#grammar-production-STRING_LITERAL1">STRING_LITERAL1</a>, <a class="type lexicalForm" href="#grammar-production-STRING_LITERAL2">STRING_LITERAL2</a>, <a class="type lexicalForm" href="#grammar-production-STRING_LITERAL_LONG1">STRING_LITERAL_LONG1</a> and <a class="type lexicalForm" href="#grammar-production-STRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a><!-- and <a class="type langTag" href="#grammar-production-LANGTAG">LANGTAG</a> --><!-- and <a class="type bNode" href="#grammar-production-BLANK_NODE_LABEL">BLANK_NODE_LABEL</a> -->.</p>
</section>
<section id="sec-parsing-triples">
<h3>RDF Triples Constructors</h3>
@@ -1130,7 +1129,6 @@
<li>digits in the first character of the <a href="http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL">PN_LOCAL</a> lexical token, e.g. <code>ex:7tm</code>.</li>
</ul></li>
- <li>Made <a href="#sec-syntax">syntax section</a> normative.
<ul>
<li>adopted SPARQL's IRI resolution and prefix substitution text.</li>