--- a/rdf-turtle/index.html Thu Mar 22 14:57:27 2012 -0400
+++ b/rdf-turtle/index.html Thu Mar 22 14:57:57 2012 -0400
@@ -152,15 +152,14 @@
<p>This document defines Turtle, the Terse RDF Triple Language,
a concrete syntax for RDF as defined in the
<a href="../rdf-concepts/index.html">RDF Concepts and Abstract Syntax</a> ([[!RDF-CONCEPTS]]) W3C Recommendation.
- Turtle is an extension of
- <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">N-Triples</a>
+ Turtle is an extension of the
+ <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">RDF Test Cases format</a>
([[!N-TRIPLES]])
carefully taking the most useful and appropriate things added from
<a href="http://www.w3.org/DesignIssues/Notation3">Notation 3</a>
([[N3]])
while staying within the RDF model.</p>
- <p class="issue"><a href="http://www.w3.org/2011/rdf-wg/track/issues/4">ISSUE-4</a>: A future version of this document is expected to define N-Triples.</p>
<p>The Turtle grammar for <a href="#prod-turtle2-triples"><code>triples</code></a> is a subset of the
<a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/">SPARQL Query Language for RDF</a>
[[RDF-SPARQL-QUERY]] grammar for <a href="http://www.w3.org/TR/sparql11-query/#rTriplesBlock"><code>TriplesBlock</code></a>. The two grammars share production and terminal names where possible.</p>
@@ -179,11 +178,10 @@
<p>Simple triples are a sequence of (subject, predicate, object)
terms, separated by whitespace and terminated by '.' after each
- triple. This corresponds to
- <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">N-Triples</a>
+ triple. This corresponds to the
+ <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">RDF Test Cases format</a>
[[N-TRIPLES]].
</p>
- <p class="issue"><a href="http://www.w3.org/2011/rdf-wg/track/issues/4">ISSUE-4</a>: A future version of this document is expected to define N-Triples.</p>
<p>There are three types of <em>RDF Term</em>:
<a href="../rdf-concepts/index.html#dfn-iri">Internationalized Resource Identifiers</a> (IRIs for short),
@@ -271,10 +269,6 @@
The <code>"That Seventies Show"</code> above is equivalent to <code>"That Seventies Show"^^xsd:string</code>.
</p>
- <p class="issue">
- <a href="http://www.w3.org/2011/rdf-wg/track/issues/12">ISSUE-12</a> The RDF Working Group is currently examining a simplification of RDF which considers plain literals with no language tag to be literals with a datatype <code>xsd:string</code>.
- </p>
-
<p>Blank nodes are written as <code>_:</code><em>BLANK_NODE_LABEL</em>
to provide a blank node either from the given <a href="#prod-turtle2-BLANK_NODE_LABEL">BLANK_NODE_LABEL</a>.
A generated blank node may also be made with <code>[]</code>
@@ -314,10 +308,6 @@
<p>See the <a href="#sec-strings">String escape sequences</a> section for full details.</p>
- <p class="issue">
- <a href="http://www.w3.org/2011/rdf-wg/track/issues/67">ISSUE 67</a> The inclusion of escape sequences in prefixed names is undecided.
- </p>
-
</section>
<section id="iris">
<h3>Abbreviating IRIs</h3>
@@ -1095,17 +1085,23 @@
<section id="n-triple-changes" class="informative">
<h3>Changes from RDF Test Cases format</h3>
<ul>
- <li>Default encoding is UTF-8 rather than US-ASCII only
+ <li>Encoding is UTF-8 rather than US-ASCII
<li>Uses IRIs rather than RDF URI References
<li>Defines a unique media type <code>application/ntriples</code>
<li>Subset of Turtle rather than Notation 3
<li>Comments may occur after a triple production
+ <li>Allows <code>\b</code> and <code>\f</code> for backspace and form feed
+ <li>More than one way to represent a single character
</ul>
</section>
<section id="n-triples-compatibility" class="informative">
<h3>Compatibility with previous RDF Test Cases N-Triples</h3>
+ <p class="issue">This section is very prescriptive and contains no information not contained above.</p>
<p>
- Full backwards compatibility with RDF Test Cases N-Triples is supported. An RDF Test Cases document written using only absolute IRIs is a valid N-Triples document generating the same triples. Both use <code>\u</code> escape sequences for characters outside US-ASCII and processing will have turned these into the original character. A N-Triples document that is serialized into ASCII and uses <code>\u</code> escape sequences for any character outside US-ASCII is equivalent to a RDF Test Cases document. Any comments may also be removed to avoid changes in the locations that comments are allowed.
+ Full backwards compatibility with RDF Test Cases N-Triples is supported. An RDF Test Cases document written using only absolute IRIs is a valid N-Triples document generating the same triples. Both use <code>\u</code> escape sequences for characters outside US-ASCII and processing will have turned these into the original character.
+ </p>
+
+ <p>N-Triples is also forwards compatible with existing RDF Test Cases format parsers. A N-Triples document that is serialized into US-ASCII and uses <code>\u</code> escape sequences for any character outside US-ASCII is equivalent to a RDF Test Cases document. In addition the backspace (<code>U+0008</code>) and form feed (<code>U+000C</code>) characters SHOULD be escaped using the <code>\u</code> sequence rather than using <code>\b</code> or <code>\f</code>. Any comments SHOULD also be removed to avoid changes in the locations that comments are allowed. Such a document provided as <code>text/plain</code> is indistinguishable from an RDF Test Cases format document.
</p>
</section>
<section id="n-triple-grammar">
--- a/rdf-turtle/turtle.bnf Thu Mar 22 14:57:27 2012 -0400
+++ b/rdf-turtle/turtle.bnf Thu Mar 22 14:57:57 2012 -0400
@@ -98,9 +98,9 @@
[86s] EXPONENT ::= [eE] [+-]? [0-9]+
-[87s] STRING_LITERAL1 ::= "'" ( ( [^'\\\n\r] ) | ECHAR | UCHAR )* "'"
+[148s] STRING_LITERAL1 ::= '"' ( ( [^#x27#x5C#xA#xD]) | ECHAR | UCHAR )* '"'
-[88s] STRING_LITERAL2 ::= '"' ( ( [^\"\\\n\r] ) | ECHAR | UCHAR )* '"'
+[149s] STRING_LITERAL2 ::= '"' ( ( [^#x22#x5C#xA#xD]) | ECHAR | UCHAR )* '"'
[89s] STRING_LITERAL_LONG1 ::= "'''" ( ( "'" | "''" )? ( [^'\\] | ECHAR | UCHAR ) )* "'''"
@@ -133,7 +133,6 @@
| [#F900-#FDCF]
| [#FDF0-#FFFD]
| [#10000-#EFFFF]
- | UCHAR
[96s] PN_CHARS_U ::= PN_CHARS_BASE
| "_"
[98s] PN_CHARS ::= PN_CHARS_U