--- a/rdf-turtle/index.html Wed Jun 13 10:15:34 2012 -0700
+++ b/rdf-turtle/index.html Wed Jun 13 10:37:22 2012 -0700
@@ -555,6 +555,30 @@
sections of the SPARQL query document [[RDF-SPARQL-QUERY]].
</p>
</section>
+ <section id="conformance">
+ <p>This specification defines conformance criteria for:</p>
+ <ul>
+ <li>Turtle documents
+ <li>Turtle parsers
+ </ul>
+ <p>A conforming <strong>Turtle document</strong> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#sec-grammar">Turtle Grammar</a>, starting with the <a href="#grammar-production-turtleDoc"><code>turtleDoc</code> production</a>. A Turtle document serializes an RDF graph.</p>
+
+ <p>A conforming <strong>Turtle parser</strong> is a system capable of reading Turtle documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing">Parsing</a>, available to the application, usually through some form of API.</p>
+
+ <p class="note">This specification does not define how Turtle parsers handle non-conforming input documents.</p>
+ <section id="sec-mime">
+ <h2>Media Type and Content Encoding</h2>
+
+ <p>The media type of Turtle is <code>text/turtle</code>.
+ The content encoding of Turtle content is always UTF-8. Charset
+ parameters on the mime type are required until such time as the
+ <code>text/</code> media type tree permits UTF-8 to be sent without a
+ charset parameter. See <a href="#sec-mediaReg">B. Internet Media
+ Type, File Extension and Macintosh File Type</a> for the media type
+ registration form.
+ </p>
+ </section>
+ </section>
<section id="sec-grammar">
<h2>Turtle Grammar</h2>
@@ -935,33 +959,9 @@
<code>http://www.w3.org/ns/formats/Turtle</code>
</p>
</section>
- <section id="conformance">
- <p>This specification defines conformance criteria for:</p>
- <ul>
- <li>Turtle documents
- <li>Turtle parsers
- </ul>
- <p>A conforming <strong>Turtle document</strong> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#sec-grammar">Turtle Grammar</a>, starting with the <a href="#grammar-production-turtleDoc"><code>turtleDoc</code> production</a>. A Turtle document serializes an RDF graph.</p>
-
- <p>A conforming <strong>Turtle parser</strong> is a system capable of reading Turtle documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing">Parsing</a>, available to the application, usually through some form of API.</p>
-
- <p class="note">This specification does not define how Turtle parsers handle non-conforming input documents.</p>
- </section>
- <section id="sec-mime">
- <h2>Media Type and Content Encoding</h2>
-
- <p>The media type of Turtle is <code>text/turtle</code>.
- The content encoding of Turtle content is always UTF-8. Charset
- parameters on the mime type are required until such time as the
- <code>text/</code> media type tree permits UTF-8 to be sent without a
- charset parameter. See <a href="#sec-mediaReg">B. Internet Media
- Type, File Extension and Macintosh File Type</a> for the media type
- registration form.
- </p>
- </section>
- <section id="in-html" class="informative">
- <h2>Turtle in HTML</h2>
+ <section id="in-html" class="appendix informative">
+ <h2>Embedding Turtle in HTML documents</h2>
<p>HTML ([[!HTML5]]) <code>script</code> <a href="http://dev.w3.org/html5/spec/Overview.html#scripting-1">tags</a>
can be used to embed data blocks in documents. Turtle can be easily embedded in HTML this way.</p>
<pre class="example"><script type="text/turtle">
@@ -1002,23 +1002,6 @@
<p>When embedded in XHTML Turtle data blocks MUST be enclosed in CDATA sections. Those CDATA markers MUST be in Turtle comments. If the character sequence "<code>]]></code>" occurs in the document it MUST be escaped using strings escapes (<code>\u005d\u0054\u003e</code>). This will also make Turtle safe in polyglot documents served as both <code>text/html</code>
and <code>application/xhtml+xml</code>.</p>
</section>
- <section class="informative">
- <h3>Displaying Examples</h3>
- <p>
- It is possible to display the contents of script tags containing Turtle for use in examples or other guides
- using Cascading Style Sheets Selectors Level 3 ([[SELECT]]).
- </p>
-<pre class="example">script[type='text/turtle'] {
- display:block;
- white-space: pre;
- font-family: monospace;
-}
-</pre>
- <p>
- However, this creates issues with polyglot documents. If you wish to display Turtle from script tags you
- SHOULD only use <code>text/html</code>.
- </p>
- </section>
<section id="in-html-parsing" class="informative">
<h3>Parsing Turtle in HTML</h3>
<p>There are no syntactic or grammar differences between parsing Turtle that has been embedded