--- a/rdf-turtle/index.html	Mon Aug 22 16:24:11 2011 -0700
+++ b/rdf-turtle/index.html	Mon Aug 22 17:03:07 2011 -0700
@@ -860,9 +860,11 @@
         <!-- BEGIN N-TRIPLES SPEC -->
 
       <section id="sec-triples">
-        <h2>N′-Triples</h2>
+        <h2>N′ (N-Triples)</h2>
+        <p class="issue">The RDF WG has not settled on a name for N′, N′ is used to distinguish it from the RDF Test Cases N-Triples.</p>
+        <p class="issue"><a href="http://www.w3.org/2011/rdf-wg/track/issues/4">ISSUE-4</a>: The RDF WG has specified N-Triples Prime to allow UTF-8 characters in IRIs, literals and blank node identifiers. Readers with an opinion about whether or not N-Triples should be ASCII-only may wish to comment.</p>
         <p>This section defines an easy to parse line-based subset of
-Turtle. Currently named N-Triples Prime (<abbr title="N-Triples Prime">N′-triples</abbr>).</p>
+Turtle named N-Triples Prime (<abbr title="N-Triples Prime">N′</abbr>).</p>
         <p>The syntax is an improved version of N-Triples. N-Triples is a format
 originally defined in the RDF Test Cases [[!RDF-TESTCASES]] document. Its original intent was for
 writing test cases, but it has proven to be popular as a dump format for RDF
@@ -874,16 +876,21 @@
             <li>Uses IRIs rather then RDF URI References
             <li>Defines a unique media type <code>text/ntriples+turtle</code>
             <li>Subset of Turtle rather then Notation 3
+            <li>Comments may occur after a triple production
           </ul>
         </section>
         <section id="n-triples-compatibility"  class="informative">
           <h3>Compatibility with previous N-Triples</h3>
           <p>
-          An N-Triples document written using only absolute IRIs is a valid N′-triples document generating the same triples. N-triples uses <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 should be equivalent to a N-Triples document.
+          An N-Triples document written using only absolute IRIs is a valid N′ document generating the same triples. N-Triples uses <code>\u</code> escape sequences for characters outside US-ASCII and processing will have turned these into the original character. A N′ document that is serialized into ASCII and uses <code>\u</code> escape sequences for any character outside US-ASCII should be equivalent to a N-Triples document. Any comments may also be removed to avoid changes in the locations that comments are allowed.
           </p>
         </section>
         <section id="n-triple-grammar">
           <h3>Grammar</h3>
+          <p>A N′ document is a Unicode[[!UNICODE]] character string encoded in UTF-8.
+          Unicode codepoints only in the range U+0 to U+10FFFF inclusive are allowed.</p>
+          <p><a href="#sec-strings">Escape sequence rules</a> are the same as Turtle. However, as only the <code>STRING_LITERAL2</code> production is allowed new lines in literals MUST be escaped.</p>
+          <p class="issue">Current grammar is not in fact line oriented.</p>
           <pre data-include="n-prime.bnf" data-oninclude="esc">
           </pre>
         </section>
@@ -897,7 +904,6 @@
       <section id="sec-diff-ntriples" class="informative">
         <h3>Turtle compared to N-Triples (Informative)</h3>
        
-        <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. By default, the RDF WG will specify N-Triples to allow UTF-8 characters in IRIs, literals and blank node identifiers. Readers with an opinion about whether or not N-Triples should be ASCII-only may wish to comment.</p>
         <p>All N-Triples files are vaild Turtle documents. Turtle adds the following syntax to N-Triples:</p>
 
         <ol>