--- a/rdf-turtle/index.html Fri Jan 03 16:34:03 2014 -0500
+++ b/rdf-turtle/index.html Fri Jan 03 17:08:01 2014 -0500
@@ -181,11 +181,11 @@
foaf:name "Spiderman", "Человек-паук"@ru .</script></pre>
<p>
This example introduces many of features of the Turtle language:
-<a href="#relative-iris">@base and Relative IRIs</a>,
-<a href="#turtleIRIs">@prefix and prefixed names</a>,
+<a href="#relative-iri">@base and Relative IRIs</a>,
+<a href="#prefixed-name">@prefix and prefixed names</a>,
<a href="#predicate-lists">predicate lists</a> separated by '<code>;</code>',
<a href="#object-lists">object lists</a> separated by '<code>,</code>',
-the token <code><a href="#IRIs">a</a></code>,
+the token <code><a href="#iri-a">a</a></code>,
and <a href="#literals">literals</a>.
</p>
@@ -253,8 +253,8 @@
<a href="htp://www.w3.org/TR/rdf11-concepts/#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>' or '<code>BASE</code>' directive. Specifics of this operation are defined in <a href="#sec-iri-references" class="sectionRef"></a> </p>
- <p>
+ <p id="relative-iri">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>' or '<code>BASE</code>' directive. Specifics of this operation are defined in <a href="#sec-iri-references" class="sectionRef"></a> </p>
+ <p id="iri-a">
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>
@@ -682,9 +682,9 @@
<section id="sec-iri-references">
<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.
+ 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> [[RFC3986]] 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>].
+ 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> [[RFC3987]].
</p>
<p>
The <code>@base</code> or <code>BASE</code> directive defines the Base IRI used to resolve relative IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content".
@@ -720,14 +720,14 @@
<tbody>
<tr>
- <td>'\u' <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a></td>
+ <td>'\u' <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a></td>
<td>A Unicode character in the range U+0000 to U+FFFF inclusive
corresponding to the value encoded by the four hexadecimal digits interpreted from most significant to least significant digit.</td>
</tr>
<tr>
- <td>'\U' <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a></td>
+ <td>'\U' <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a> <a href="#grammar-production-HEX">hex</a></td>
<td>A Unicode character in the range U+0000 to U+10FFFF inclusive
corresponding to the value encoded by the eight hexadecimal digits interpreted from most significant to least significant digit.</td>
@@ -736,7 +736,7 @@
</tbody>
</table>
- <p>where <a href="#rHEX">HEX</a> is a hexadecimal character</p>
+ <p>where <a href="#grammar-production-HEX">HEX</a> is a hexadecimal character</p>
<blockquote>
<p><span style="font-family: monospace; font-size: 85%;"><a id="rHEX">HEX</a>
::= [0-9] | [A-F] | [a-f]</span></p>
@@ -826,7 +826,7 @@
</thead>
<tbody>
<tr>
- <td class="r"><span style="font-weight:bold;">IRI</span>s, used as <a href="#grammar-production-IRIref">RDF terms</a> or as in <a href="#grammar-production-prefixID">@prefix</a>, <a href="#grammar-production-sparqlPrefix">PREFIX</a>, <a href="#grammar-production-base">@base</a>, or <a href="#grammar-production-sparqlBase">BASE</a> declarations</td>
+ <td class="r"><span style="font-weight:bold;">IRI</span>s, used as <a href="#grammar-production-IRIREF">RDF terms</a> or as in <a href="#grammar-production-prefixID">@prefix</a>, <a href="#grammar-production-sparqlPrefix">PREFIX</a>, <a href="#grammar-production-base">@base</a>, or <a href="#grammar-production-sparqlBase">BASE</a> declarations</td>
<td style="background-color: green; border:1px solid black;">yes</td>
<td>no</td>
<td>no</td>
@@ -1218,7 +1218,7 @@
<h3>Changes from <a href="http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114/">January 2008 Team Submission</a> to <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">First Public Working Draft</a></h3>
<ul>
- <li>Adopted three additional string syntaxes from SPARQL: <a href="#grammar-production-STRING_LITERAL2">STRING_LITERAL2</a>, <a href="#grammar-production-STRING_LITERAL_LONG1">STRING_LITERAL_LONG1</a>, <a href="#grammar-production-STRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a></li>
+ <li>Adopted three additional string syntaxes from SPARQL: <a href="http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL2">STRING_LITERAL2</a>, <a href="http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG1">STRING_LITERAL_LONG1</a>, <a href="http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a></li>
<li>Adopted SPARQL's syntax for prefixed names (see <a href="http://www.w3.org/TR/sparql11-query/#rPrefixedName">editor's draft</a>):
<ul>