--- a/rdf-turtle/index.html	Fri Dec 13 10:31:51 2013 -0800
+++ b/rdf-turtle/index.html	Sun Dec 15 11:30:44 2013 -0500
@@ -36,7 +36,7 @@
 	  subtitle   :  "Terse RDF Triple Language",
 
 	  // if you wish the publication date to be other than today, set this
-	  publishDate:  "2014-02-19",
+	  publishDate:  "2014-01-07",
 
 	  // if the specification's copyright date is a range of years, specify
 	  // the start date here:
@@ -257,16 +257,33 @@
 				  A prefixed name is turned into an IRI by concatenating the IRI associated with the prefix and the local part. The '<code>@prefix</code>' or '<code>PREFIX</code>' directive associates a prefix label with an IRI.
 				  Subsequent '<code>@prefix</code>' or '<code>PREFIX</code>' directives may re-map the same prefix label. </p>
 
+                  <div class="note">
+                      <p>
+                          The Turtle language originally permitted only the syntax including the '<code>@</code>' character for writing prefix and base directives.
+                          The case-insensitive '<code>PREFIX</code>' and '<code>BASE</code>' forms were added to align Turtle's syntax with that of SPARQL.
+                          It is advisable to serialize RDF using the '<code>@prefix</code>' and '<code>@base</code>' forms until RDF 1.1 Turtle parsers are widely deployed.
+                      </p>
+                  </div>
+
 				  <p>
 				  	To write <code>http://www.perceive.net/schemas/relationship/enemyOf</code> using a prefixed name: </p>
 				  	<ol>
-				  		<li>Define a prefix label for the vocabulary IRI <code>http://www.perceive.net/schemas/relationship/</code> as <code>rel</code>
-			  			<li>Then write <code>rel:enemyOf</code> which is equivalent to writing <code>&lt;http://www.perceive.net/schemas/relationship/enemyOf></code></li>
+				  		<li>Define a prefix label for the vocabulary IRI <code>http://www.perceive.net/schemas/relationship/</code> as <code>somePrefix</code>
+			  			<li>Then write <code>somePrefix:enemyOf</code> which is equivalent to writing <code>&lt;http://www.perceive.net/schemas/relationship/enemyOf></code></li>
 			  		</ol>
 
-				  <pre class="example"><script type="text/turtle">@prefix rel: <http://www.perceive.net/schemas/relationship/> .
+                    <p>
+                      This can be written using either the original Turtle syntax for prefix declarations:</p>
 
-<http://example.org/#green-goblin> rel:enemyOf <http://example.org/#spiderman> .
+				  <pre class="example"><script type="text/turtle">@prefix somePrefix: <http://www.perceive.net/schemas/relationship/> .
+
+<http://example.org/#green-goblin> somePrefix:enemyOf <http://example.org/#spiderman> .
+				  </script></pre>
+                    <p>
+                      or SPARQL's syntax for prefix declarations:</p>
+				  <pre class="example"><script type="text/turtle">PREFIX somePrefix: <http://www.perceive.net/schemas/relationship/>
+
+<http://example.org/#green-goblin> somePrefix:enemyOf <http://example.org/#spiderman> .
 				  </script></pre>
 
 
@@ -413,7 +430,7 @@
     :specificGravity 1.663E-4 .     # xsd:double                                                                       
 				</script></pre>
 			</section>
-			<section>
+			<section id="booleans">
 				<h3>Booleans</h3>
 				<p>Boolean values may be written as either '<code>true</code>' or '<code>false</code>' (case-sensitive) and represent RDF literals with the datatype <a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:boolean</a>.</p>
 				<pre class="example"><script type="text/turtle">@prefix : <http://example.org/stats> .
@@ -1119,7 +1136,7 @@
           <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
           <dt>Additional information:</dt>
           <dt>Magic number(s):</dt>
-          <dd>Turtle documents may have the strings '@prefix' or '@base' (case dependent) or the strings 'PREFIX' or 'BASE' (case independent) near the beginning of the document.</dd>
+          <dd>Turtle documents may have the strings '@prefix' or '@base' (case sensitive) or the strings 'PREFIX' or 'BASE' (case insensitive) near the beginning of the document.</dd>
           <dt>File extension(s):</dt>
           <dd>".ttl"</dd>
 
@@ -1168,13 +1185,13 @@
       </section>
       <section id="sec-changelog" class="appendix">
       <h2>Change Log</h2>
-      <section>
+      <section id="sec-changelog-CR-PR">
       <h2>Changes from Candidate Recommendation 19 February 2013 to this version</h2>
       <ul>
-      	<li>The addition of <a href="#grammar-production-sparqlPrefix">sparqlPrefix</a> and <a href="#grammar-production-sparqlBase">sparqlBase</a> which allow for using SPARQL style <code>BASE</code> and <code>PREFIX</code> directives in a Turtle document. No longer at risk.</li>
+      	<li>The addition of <a href="#grammar-production-sparqlPrefix">sparqlPrefix</a> and <a href="#grammar-production-sparqlBase">sparqlBase</a> which allow for using SPARQL style <code>BASE</code> and <code>PREFIX</code> directives in a Turtle document was marked "at risk" in the Candidate Recommendation publication. This feature is no longer at risk.</li>
 	    </ul>
       </section>
-      <section>
+      <section id="sec-changelog-WD-CR">
       <h3>Changes in Working Drafts to Candidate Recommendation</h3>
         <ul>
       		<li>Renaming for STRING_* productions to STRING_LITERAL_QUOTE sytle names rather than numbers
@@ -1188,7 +1205,7 @@
     			<li>Whitespace required between @prefix and prefix label
     	  </ul>
       </section>
-      <section>
+      <section id="sec-changelog-Subm-WD">
       <h3>Other changes</h3>
 
       <p>Other changes since the Team Submission