--- a/rdf-turtle/n-triples.html Thu Dec 05 18:26:38 2013 +0000
+++ b/rdf-turtle/n-triples.html Thu Dec 05 18:33:38 2013 +0000
@@ -197,7 +197,7 @@
</section>
- <section id="n-triple-changes" class="informative">
+ <section id="n-triples-changes" class="informative">
<h3>Changes from RDF Test Cases format</h3>
<ul>
<li>Encoding is UTF-8 rather than US-ASCII
@@ -214,13 +214,13 @@
<section id="conformance">
<p>This specification defines conformance criteria for:</p>
<ul>
- <li>N-Triple documents
- <li>Canonical N-Triple documents
- <li>N-Triple parsers
+ <li>N-Triples documents
+ <li>Canonical N-Triples documents
+ <li>N-Triples parsers
</ul>
- <p>A conforming <dfn>N-Triple document</dfn> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#n-triples-grammar" class="sectionRef"></a>, starting with the <a href="#grammar-production-ntriplesDoc"><code>ntriplesDoc</code> production</a>. A N-Triple document serializes an RDF graph.</p>
+ <p>A conforming <dfn>N-Triples document</dfn> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#n-triples-grammar" class="sectionRef"></a>, starting with the <a href="#grammar-production-ntriplesDoc"><code>ntriplesDoc</code> production</a>. An N-Triples document serializes an RDF graph.</p>
- <p>A <dfn>canonical N-Triple document</dfn> is a <strong>N-Triple document</strong> with additional constraints:<p>
+ <p>A <dfn>canonical N-Triples document</dfn> is a <strong>N-Triples document</strong> with additional constraints:<p>
<ul>
<li>Whitespace following <code>subject</code>, <code>predicate</code>, and <code>object</code> MUST be a single space, (<code>U+0020</code>) all other locations that allow whitespace MUST be empty.
@@ -230,9 +230,9 @@
<li>Characters MUST be represented directly and not by <code>UCHAR</code>.
</ul>
- <p>A conforming <dfn>N-Triple parser</dfn> is a system capable of reading N-Triple 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>A conforming <dfn>N-Triples parser</dfn> is a system capable of reading N-Triples 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 N-Triple language is: <code>http://www.w3.org/ns/formats/N-Triples</code></p>
+ <p>The IRI that identifies the N-Triples language is: <code>http://www.w3.org/ns/formats/N-Triples</code></p>
<section id="n-triples-mediatype">
<h2>Media Type and Content Encoding</h2>
@@ -245,7 +245,7 @@
<section id="sec-other-media-types">
<h3>Other Media Types</h3>
- <p>N-Triples has been historically provided with other media types. N-Triples may also be provided as <code>text/plain</code>. When used in this way N-Triples MUST use the escaped form of any character outside US-ASCII. As N-Triples is a subset of Turtle a N-Triples document MAY also be provided as <code>text/turtle</code>. In both of these cases the document is not an N-Triples document as an N-Triples document is only provided as <code>application/n-triples</code>.</p>
+ <p>N-Triples has been historically provided with other media types. N-Triples may also be provided as <code>text/plain</code>. When used in this way N-Triples MUST use the escaped form of any character outside US-ASCII. As N-Triples is a subset of Turtle an N-Triples document MAY also be provided as <code>text/turtle</code>. In both of these cases the document is not an N-Triples document as an N-Triples document is only provided as <code>application/n-triples</code>.</p>
</section>
</section>
@@ -253,7 +253,7 @@
<section id="n-triples-grammar">
<h3>Grammar</h3>
- <p>A N-Triples document is a Unicode [[!UNICODE]] character string encoded in UTF-8.
+ <p>An N-Triples document is a Unicode [[!UNICODE]] character string encoded in UTF-8.
Unicode code points only in the range U+0 to U+10FFFF inclusive are allowed.</p>
<p>White space (tab <code>U+0009</code> or space <code>U+0020</code>) is used to separate two terminals which would otherwise be (mis-)recognized as one terminal. White space is significant in the production <a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a>.</p>
<p>Comments in N-Triples take the form of '<code>#</code>', outside an <code>IRIREF</code> or <code>STRING_LITERAL_QUOTE</code>, and continue to the end of line (<code>EOL</code>) or end of file if there is no end of line after the comment marker. Comments are treated as white space.</p>
@@ -290,7 +290,7 @@
</section>
<section>
<h3>RDF Triple Construction</h3>
- <p>A N-Triple document defines an RDF graphs composed of a set of RDF triples. The <code><a href="#grammar-production-triple">triple</a></code> production produces a triple defined by the terms constructed for <code><a href="#grammar-production-subject">subject</a></code>, <code><a href="#grammar-production-predicate">predicate</a></code> and <code><a href="#grammar-production-object">object</a></code>.
+ <p>An N-Triples document defines an RDF graphs composed of a set of RDF triples. The <code><a href="#grammar-production-triple">triple</a></code> production produces a triple defined by the terms constructed for <code><a href="#grammar-production-subject">subject</a></code>, <code><a href="#grammar-production-predicate">predicate</a></code> and <code><a href="#grammar-production-object">object</a></code>.
</section>
@@ -310,7 +310,7 @@
<p>No substitutive changes.</p>
<h3>Changes since original publication as Note</h3>
<ul>
- <li>Conformance section now defines <a href="#dfn-canonical-n-triple-document">canonical N-Triple document</a>.
+ <li>Conformance section now defines <a href="#dfn-canonical-n-triples-document">canonical N-Triples document</a>.
<li>White space rules defined outside of grammar, as in Turtle.
<li>Comment processing defined.
<li>Parsing is defined.