--- a/trig/index.html Sun Dec 22 20:19:44 2013 +0000
+++ b/trig/index.html Sun Dec 22 22:21:50 2013 +0100
@@ -165,7 +165,7 @@
that allows an RDF dataset to be completely written in a compact and
natural text form, with abbreviations for common usage patterns and
datatypes. TriG is an extension of the
- <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!TURTLE]] format.
+ Turtle [[!TURTLE]] format.
</p>
</section>
@@ -173,7 +173,7 @@
<p>TriG is intended the meet the charter requirement of the
<a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> to
define an RDF syntax for multiple graphs. TriG is an extension of the
-<a href="http://www.w3.org/TR/turtle/">Turtle</a>
+Turtle
syntax for RDF [[!TURTLE]]. The current document is based on
the original proposal by Chris Bizer and Richard Cyganiak.</p>
@@ -183,8 +183,8 @@
<h2>Introduction</h2>
<p>This document defines TriG, a concrete syntax for RDF as defined in the
RDF Concepts and Abstract Syntax
- ([[!RDF11-CONCEPTS]]). TriG is an extension of
- <a href="http://www.w3.org/TR/turtle/">Turtle</a> ([[!TURTLE]]), extended
+ [[!RDF11-CONCEPTS]]. TriG is an extension of
+ Turtle [[!TURTLE]], extended
to support representing a complete RDF Dataset.
</section>
@@ -203,7 +203,7 @@
Optionally a graph statement may not not be labeled with an IRI. Such a
graph statement corresponds to the Default Graph of an RDF Dataset.</p>
<p>
- The construction of an RDF Dataset from a TriG document is defined in <a href="#sec-grammar" class="sectionRef">TriG Grammar</a> and <a href="#sec-parsing" class="sectionRef">Parsing</a>.
+ The construction of an RDF Dataset from a TriG document is defined in <a href="#sec-grammar" class="sectionRef"></a> and <a href="#sec-parsing" class="sectionRef"></a>.
</p>
<section id="sec-triple-statements">
@@ -333,7 +333,7 @@
<h2>TriG Grammar</h2>
- <p>A TriG document is a Unicode[[!UNICODE]] character string
+ <p>A TriG document is a Unicode [[!UNICODE]] character string
encoded in UTF-8.
Unicode characters only in the range U+0000 to U+10FFFF inclusive are
allowed.
@@ -358,9 +358,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> [[!RFC3986]] using only the basic algorithm in section 5.2.
+ Relative IRIs are resolved with base IRIs as per "Uniform Resource Identifier (URI): Generic Syntax" [[!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> [[!RFC3987]].
+ 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 "Internationalized Resource Identifiers (IRIs)" [[!RFC3987]].
</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".
@@ -528,8 +528,8 @@
<p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0
[[!EBNF-NOTATION]]. Production labels consisting of a number and a final 'g' are unique to TriG. All Production labels consisting of only a number reference the production with that number in the
-<a href="http://www.w3.org/TR/turtle/">Turtle</a> grammar
-[[!TURTLE]]. Production labels consisting of a number and a final 's', e.g. [<a href="http://www.w3.org/TR/sparql11-query/#rRDFLiteral"><span class="prodNo">60s</span></a>], reference the production with that number in the <a href="http://www.w3.org/TR/sparql11-query/#sparqlGrammar">SPARQL Query Language for RDF grammar</a> [[RDF-SPARQL-QUERY]].
+Turtle grammar
+[[!TURTLE]]. Production labels consisting of a number and a final 's', e.g. [<a href="http://www.w3.org/TR/sparql11-query/#rRDFLiteral"><span class="prodNo">60s</span></a>], reference the production with that number in the "SPARQL Query Language for RDF grammar" [[RDF-SPARQL-QUERY]].
</p>
@@ -597,7 +597,9 @@
</section>
<section id="sec-parsing">
<h2>Parsing</h2>
- <p>The <a href="http://www.w3.org/TR/rdf11-concepts/">RDF Concepts and Abstract Syntax</a> ([[!RDF11-CONCEPTS]]) specification defines three types of <em>RDF Term</em>:
+ <p>The RDF Concepts and Abstract Syntax [[!RDF11-CONCEPTS]]
+ specification defines three types of <em>RDF
+ Term</em>:
<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-iri">IRIs</a>,
<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">literals</a> and
@@ -616,7 +618,9 @@
<li id="namespaces">Map[<a class="type prefix" href="#prefix">prefix</a> -> IRI] <code class="dfn">namespaces</code> — The second and third rule arguments (<code>PNAME_NS</code> and <code>IRIREF</code>) in the <a href="#grammar-production-prefixID">prefixID production</a> assign a namespace name (<code>IRIREF</code>) for the prefix (<code>PNAME_NS</code>). Outside of a <code>prefixID</code> production, any <code>PNAME_NS</code> is substituted with the namespace. Note that the prefix may be an empty string, per the <code>PNAME_NS,</code> production: <code>(PN_PREFIX)? ":"</code>.</li>
<li id="bnodeLabels">Map[string -> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">blank node</a>] <code class="dfn">bnodeLabels</code> — A mapping from string to blank node.</li>
- <li id="curSubject">RDF_Term <code class="dfn">curSubject</code> — The <code class="curSubject">curSubject</code> is bound to the <code><a href="#grammar-production-subject">subject</a></code> production.</li>
+ <li id="curSubject">RDF_Term <code
+ class="dfn">curSubject</code> — The <code
+ class="curSubject">curSubject</code> is bo und to the <code><a href="#grammar-production-subject">subject</a></code> production.</li>
<li id="curPredicate">RDF_Term <code class="dfn">curPredicate</code> — The <code class="curPredicate">curPredicate</code> is bound to the <code><a href="#grammar-production-verb">verb</a></code> production. If token matched was "<code>a</code>", <code class="curPredicate">curPredicate</code> is bound to the IRI <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</code>.</li>
@@ -779,7 +783,7 @@
defined in this document, and earlier forms.
<ul>
<li>Syntax is aligned to the
- <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!TURTLE]] recommendation
+ Turtle [[!TURTLE]] recommendation
for RDF terms.</li>
<li>Graph labels can be blank nodes.</li>
<li>The default graph, or sections of the default graph, do not
@@ -842,10 +846,8 @@
<!-- (<code>foo:resum鼯code> and <code>fоо:resumé</code>)-->
Any person or application that is writing or interpreting data in TriG must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar.
Further information about matching of similar characters can be found
- in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security
- Considerations</a> [[UNICODE-SECURITY]] and
- <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
- Identifiers (IRIs)</a> [[RFC3987]] Section 8.</dd>
+ in "Unicode Security Considerations" [[UNICODE-SECURITY]] and
+ "Internationalized Resource Identifiers (IRIs)" [[RFC3987]], Section 8.</dd>
<dt>Interoperability considerations:</dt>
<dd>There are no known interoperability issues.</dd>