Change preprocessing to use span not div
authorGavin Carothers <gavin@carothers.name>
Fri, 05 Aug 2011 07:59:15 -0700
changeset 110 9b4523cc9347
parent 109 2034b34bd139
child 111 b2fd170f8d79
Change preprocessing to use span not div
rdf-turtle/built-xhtml/FPWD.html
rdf-turtle/index.html
--- a/rdf-turtle/built-xhtml/FPWD.html	Wed Aug 03 09:31:00 2011 -0700
+++ b/rdf-turtle/built-xhtml/FPWD.html	Fri Aug 05 07:59:15 2011 -0700
@@ -1,28 +1,20 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.0//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd'>
-<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" about="" property="dcterms:language" content="en" xmlns:dcterms='http://purl.org/dc/terms/' xmlns:bibo='http://purl.org/ontology/bibo/' xmlns:foaf='http://xmlns.com/foaf/0.1/' xmlns:xsd='http://www.w3.org/2001/XMLSchema#'>
+<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
+<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
 <head>
-	<title>Turtle</title>
-	<meta content="text/html;charset=utf-8" http-equiv="Content-Type" />
-	
-	
-    <script>
-    function updateExample(doc, content) {
-    // perform transformations to make it render and prettier
-      return '<pre class="example">' + doc._esc(content) + '</pre>';
-    }
-    function esc(doc, content) {
-      return doc._esc(content);
-    }
-
-    </script>
+    <title>Turtle</title>
+    <meta content="text/html;charset=utf-8" http-equiv="Content-Type" />
+    
+    
+    
+    
     <style type="text/css">
-    /* Style Turtle <script> blocks to be visable */
+    /* Style Turtle script blocks to be visable */
     pre.example script {
         display:block;
     }
     </style> 
-	
+    
     <style type="text/css">
 /*****************************************************************
  * ReSpec CSS
@@ -432,7 +424,7 @@
 pre.sh_sourceCode .sh_usertype { color: teal; }                             /* user defined types */
 pre.sh_sourceCode .sh_string { color: red; font-family: monospace; }        /* strings and chars */
 pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; }     /* regular expressions */
-pre.sh_sourceCode .sh_specialchar { color: 	#ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_specialchar { color:  #ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
 pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; }         /* comments */
 pre.sh_sourceCode .sh_number { color: purple; }                             /* literal numbers */
 pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; }       /* e.g., #include, import */
@@ -489,272 +481,268 @@
 
 </style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8" /></head>
 
-    <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p><h1 id="title" class="title" property="dcterms:title">Turtle</h1><h2 id="subtitle" property="bibo:subtitle">Terse RDF Triple Language</h2><h2 content="2011-08-02T02:43:54+0000" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-working-draft-02-august-2011">W3C Working Draft 02 August 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-Turtle-20110706/">http://www.w3.org/TR/2011/WD-Turtle-20110706/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/Turtle/">http://www.w3.org/TR/Turtle/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html">http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html</a></dd><dt>Previous version:</dt><dd>none</dd><dt>Editors:</dt><dd rel="bibo:editor"><span typeof="foaf:Person"><a href="http://www.w3.org/People/Eric/" hommeaux'="" content="Eric Prud" property="foaf:name" rel="foaf:homepage">Eric Prud'hommeaux</a>, <a href="http://www.w3.org/" rel="foaf:workplaceHomepage">W3C</a></span>
-</dd>
-<dd rel="bibo:editor"><span typeof="foaf:Person"><a href="http://gavin.carothers.name/" content="Gavin Carothers" property="foaf:name" rel="foaf:homepage">Gavin Carothers</a>, <a href="http://topquadrant.com/" rel="foaf:workplaceHomepage">TopQuadrant, Inc</a></span>
-</dd>
-<dt>Authors:</dt><dd rel="dcterms:contributor"><span typeof="foaf:Person"><a href="http://purl.org/net/dajobe/" content="David Beckett" property="foaf:name" rel="foaf:homepage">David Beckett</a></span>
-</dd>
-<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a href="http://www.w3.org/People/Berners-Lee/" content="Tim Berners-Lee" property="foaf:name" rel="foaf:homepage">Tim Berners-Lee</a>, <a href="http://www.w3.org/" rel="foaf:workplaceHomepage">W3C</a></span>
-</dd>
-<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a href="http://www.w3.org/People/Eric/" hommeaux'="" content="Eric Prud" property="foaf:name" rel="foaf:homepage">Eric Prud'hommeaux</a>, <a href="http://www.w3.org/" rel="foaf:workplaceHomepage">W3C</a></span>
-</dd>
-</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" rel="license">Copyright</a> © 2008-2011 <span rel="dcterms:publisher"><span typeof="foaf:Organization"><a href="http://www.w3.org/" content="World Wide Web Consotrium" property="foaf:name" rel="foaf:homepage"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup></span></span> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr /></div>
-	<div id="abstract" class="introductory section" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" about="#abstract"><h2>Abstract</h2>
-			<p>The Resource Description Framework
-			(<abbr title="Resource Description Framework">RDF</abbr>) is a 
-			general-purpose language for representing information in the Web.</p>
+    <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p><h1 id="title" class="title">Turtle</h1><h2 id="subtitle">Terse RDF Triple Language</h2><h2 id="w3c-working-draft-05-august-2011">W3C Working Draft 05 August 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-Turtle-20110805/">http://www.w3.org/TR/2011/WD-Turtle-20110805/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/Turtle/">http://www.w3.org/TR/Turtle/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html">http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html</a></dd><dt>Editors:</dt><dd><a href="http://www.w3.org/People/Eric/">Eric Prud'hommeaux</a>, <a href="http://www.w3.org/">W3C</a></dd>
+<dd><a href="http://gavin.carothers.name/">Gavin Carothers</a>, <a href="http://topquadrant.com/">TopQuadrant, Inc</a></dd>
+<dt>Authors:</dt><dd><a href="http://purl.org/net/dajobe/">David Beckett</a></dd>
+<dd><a href="http://www.w3.org/People/Berners-Lee/">Tim Berners-Lee</a>, <a href="http://www.w3.org/">W3C</a></dd>
+<dd><a href="http://www.w3.org/People/Eric/">Eric Prud'hommeaux</a>, <a href="http://www.w3.org/">W3C</a></dd>
+</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2008-2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr /></div>
+    <div id="abstract" class="introductory section"><h2>Abstract</h2>
+            <p>The Resource Description Framework
+            (<abbr title="Resource Description Framework">RDF</abbr>) is a 
+            general-purpose language for representing information in the Web.</p>
 
-			<p>This document defines a textual syntax for RDF called Turtle
-			that allows an RDF graph to be completely written in a compact and
-			natural text form, with abbreviations for common usage patterns and
-			datatypes.  Turtle provides levels of compatibility with the existing
-			<a href="http://www.w3.org/TR/rdf-testcases/#ntriples">N-Triples</a>
-			<!-- and
-			<a href="http://www.w3.org/DesignIssues/Notation3">Notation 3</a> -->
-			format as well as the triple pattern syntax of the
-			<a href="http://www.w3.org/TR/sparql11-query/">SPARQL</a>
-			W3C Recommendation.
-			</p>
-	</div><div class="introductory section" id="sotd" typeof="bibo:Chapter" about="#sotd"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
+            <p>This document defines a textual syntax for RDF called Turtle
+            that allows an RDF graph to be completely written in a compact and
+            natural text form, with abbreviations for common usage patterns and
+            datatypes.  Turtle provides levels of compatibility with the existing
+            <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">N-Triples</a>
+            
+<!--  and
+            <a href="http://www.w3.org/DesignIssues/Notation3">Notation 3</a>  -->
+
+            format as well as the triple pattern syntax of the
+            <a href="http://www.w3.org/TR/sparql11-query/">SPARQL</a>
+            W3C Recommendation.
+            </p>
+    </div><div class="introductory section" id="sotd"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
       <p>
-			Turtle is already a reasonably settled serialization of RDF.  Many 
-			implementations of Turtle already exist, we are hoping for feedback from those
-			existing implementers and other people deciding that now would be a good time
-			to support Turtle. There are still a few rough edges that need polishing, and 
-			better alignment with the SPARQL triple patterns. The working group does not 
-			expect to make any large changes to the existing syntax.
+            Turtle is already a reasonably settled serialization of RDF.  Many 
+            implementations of Turtle already exist, we are hoping for feedback from those
+            existing implementers and other people deciding that now would be a good time
+            to support Turtle. There are still a few rough edges that need polishing, and 
+            better alignment with the SPARQL triple patterns. The working group does not 
+            expect to make any large changes to the existing syntax.
       </p>
-    <p>This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:[email protected]">[email protected]</a> (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>). All feedback is welcome.</p><p>Publication as a Editor's Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/46168/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div id="toc" typeof="bibo:Chapter" about="#toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#sec-intro" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#an-introduction-to-turtle--informative" class="tocxref"><span class="secno">2. </span>An Introduction to Turtle (Informative)</a><ul class="toc"><li class="tocline"><a href="#terms" class="tocxref"><span class="secno">2.1 </span>RDF Terms</a></li><li class="tocline"><a href="#iris" class="tocxref"><span class="secno">2.2 </span>Abbreviating IRIs</a></li><li class="tocline"><a href="#abbrev" class="tocxref"><span class="secno">2.3 </span>Abbreviating common datatypes</a></li><li class="tocline"><a href="#groups" class="tocxref"><span class="secno">2.4 </span>Abbreviating groups of triples</a></li><li class="tocline"><a href="#collections" class="tocxref"><span class="secno">2.5 </span>Abbreviating RDF Collections</a></li></ul></li><li class="tocline"><a href="#sec-syntax" class="tocxref"><span class="secno">3. </span>Syntax for IRIs, Literals and Blank Nodes</a></li><li class="tocline"><a href="#sec-grammar" class="tocxref"><span class="secno">4. </span>Turtle Grammar</a><ul class="toc"><li class="tocline"><a href="#sec-grammar-ws" class="tocxref"><span class="secno">4.1 </span>White Space</a></li><li class="tocline"><a href="#sec-grammar-comments" class="tocxref"><span class="secno">4.2 </span>Comments</a></li><li class="tocline"><a href="#sec-strings" class="tocxref"><span class="secno">4.3 </span>String Escapes</a></li><li class="tocline"><a href="#sec-grammar-grammar" class="tocxref"><span class="secno">4.4 </span>Grammar</a></li></ul></li><li class="tocline"><a href="#sec-parsing" class="tocxref"><span class="secno">5. </span>Parsing</a><ul class="toc"><li class="tocline"><a href="#sec-parsing-state" class="tocxref"><span class="secno">5.1 </span>Parser State</a></li><li class="tocline"><a href="#sec-parsing-terms" class="tocxref"><span class="secno">5.2 </span>RDF Term Constructors</a></li><li class="tocline"><a href="#sec-parsing-triples" class="tocxref"><span class="secno">5.3 </span>RDF Triples Constructors</a></li><li class="tocline"><a href="#sec-parsing-example" class="tocxref"><span class="secno">5.4 </span>Parsing Example (Informative)</a></li></ul></li><li class="tocline"><a href="#sec-examples" class="tocxref"><span class="secno">6. </span>Examples (Informative)</a></li><li class="tocline"><a href="#sec-identifiers" class="tocxref"><span class="secno">7. </span>Identifiers for the Turtle Language</a></li><li class="tocline"><a href="#sec-conformance" class="tocxref"><span class="secno">8. </span>Conformance</a></li><li class="tocline"><a href="#sec-mime" class="tocxref"><span class="secno">9. </span>Media Type and Content Encoding</a></li><li class="tocline"><a href="#sec-compared" class="tocxref"><span class="secno">10. </span>Turtle compared</a><ul class="toc"><li class="tocline"><a href="#sec-diff-ntriples" class="tocxref"><span class="secno">10.1 </span>Turtle compared to N-Triples (Informative)</a></li><li class="tocline"><a href="#sec-diff-n3" class="tocxref"><span class="secno">10.2 </span>Turtle compared to Notation 3 (Informative)</a></li><li class="tocline"><a href="#sec-diff-rdfxml" class="tocxref"><span class="secno">10.3 </span>Turtle compared to RDF/XML (Informative)</a></li><li class="tocline"><a href="#sec-diff-sparql" class="tocxref"><span class="secno">10.4 </span>Turtle compared to SPARQL (Informative)</a></li></ul></li><li class="tocline"><a href="#sec-mediaReg" class="tocxref"><span class="secno">A. </span>Internet Media Type, File Extension and Macintosh File Type (Normative)</a></li><li class="tocline"><a href="#sec-acks" class="tocxref"><span class="secno">B. </span>Acknowledgements (Informative)</a></li><li class="tocline"><a href="#sec-changelog" class="tocxref"><span class="secno">C. </span>Changes (Informative)</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></div>
+    <p>This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a First Public Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:[email protected]">[email protected]</a> (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/46168/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#sec-intro" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#an-introduction-to-turtle--informative" class="tocxref"><span class="secno">2. </span>An Introduction to Turtle (Informative)</a><ul class="toc"><li class="tocline"><a href="#terms" class="tocxref"><span class="secno">2.1 </span>RDF Terms</a></li><li class="tocline"><a href="#iris" class="tocxref"><span class="secno">2.2 </span>Abbreviating IRIs</a></li><li class="tocline"><a href="#abbrev" class="tocxref"><span class="secno">2.3 </span>Abbreviating common datatypes</a></li><li class="tocline"><a href="#groups" class="tocxref"><span class="secno">2.4 </span>Abbreviating groups of triples</a></li><li class="tocline"><a href="#collections" class="tocxref"><span class="secno">2.5 </span>Abbreviating RDF Collections</a></li></ul></li><li class="tocline"><a href="#sec-syntax" class="tocxref"><span class="secno">3. </span>Syntax for IRIs, Literals and Blank Nodes</a></li><li class="tocline"><a href="#sec-grammar" class="tocxref"><span class="secno">4. </span>Turtle Grammar</a><ul class="toc"><li class="tocline"><a href="#sec-grammar-ws" class="tocxref"><span class="secno">4.1 </span>White Space</a></li><li class="tocline"><a href="#sec-grammar-comments" class="tocxref"><span class="secno">4.2 </span>Comments</a></li><li class="tocline"><a href="#sec-strings" class="tocxref"><span class="secno">4.3 </span>String Escapes</a></li><li class="tocline"><a href="#sec-grammar-grammar" class="tocxref"><span class="secno">4.4 </span>Grammar</a></li></ul></li><li class="tocline"><a href="#sec-parsing" class="tocxref"><span class="secno">5. </span>Parsing</a><ul class="toc"><li class="tocline"><a href="#sec-parsing-state" class="tocxref"><span class="secno">5.1 </span>Parser State</a></li><li class="tocline"><a href="#sec-parsing-terms" class="tocxref"><span class="secno">5.2 </span>RDF Term Constructors</a></li><li class="tocline"><a href="#sec-parsing-triples" class="tocxref"><span class="secno">5.3 </span>RDF Triples Constructors</a></li><li class="tocline"><a href="#sec-parsing-example" class="tocxref"><span class="secno">5.4 </span>Parsing Example (Informative)</a></li></ul></li><li class="tocline"><a href="#sec-examples" class="tocxref"><span class="secno">6. </span>Examples (Informative)</a></li><li class="tocline"><a href="#sec-identifiers" class="tocxref"><span class="secno">7. </span>Identifiers for the Turtle Language</a></li><li class="tocline"><a href="#sec-conformance" class="tocxref"><span class="secno">8. </span>Conformance</a></li><li class="tocline"><a href="#sec-mime" class="tocxref"><span class="secno">9. </span>Media Type and Content Encoding</a></li><li class="tocline"><a href="#sec-compared" class="tocxref"><span class="secno">10. </span>Turtle compared</a><ul class="toc"><li class="tocline"><a href="#sec-diff-ntriples" class="tocxref"><span class="secno">10.1 </span>Turtle compared to N-Triples (Informative)</a></li><li class="tocline"><a href="#sec-diff-n3" class="tocxref"><span class="secno">10.2 </span>Turtle compared to Notation 3 (Informative)</a></li><li class="tocline"><a href="#sec-diff-rdfxml" class="tocxref"><span class="secno">10.3 </span>Turtle compared to RDF/XML (Informative)</a></li><li class="tocline"><a href="#sec-diff-sparql" class="tocxref"><span class="secno">10.4 </span>Turtle compared to SPARQL (Informative)</a></li></ul></li><li class="tocline"><a href="#sec-mediaReg" class="tocxref"><span class="secno">A. </span>Internet Media Type, File Extension and Macintosh File Type (Normative)</a></li><li class="tocline"><a href="#sec-acks" class="tocxref"><span class="secno">B. </span>Acknowledgements (Informative)</a></li><li class="tocline"><a href="#sec-changelog" class="tocxref"><span class="secno">C. </span>Changes (Informative)</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></div>
 
     
-	
-	<div id="sec-intro" typeof="bibo:Chapter" about="#sec-intro" class="section">
-			
+    
+    <div id="sec-intro" class="section">
+            
 <!-- OddPage -->
 <h2><span class="secno">1. </span>Introduction</h2>
-			<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> ([<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]) W3C Recommendation.
-			Turtle is an extension of 
-			<a href="http://www.w3.org/TR/rdf-testcases/#ntriples">N-Triples</a>
+            <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> ([<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]) W3C Recommendation.
+            Turtle is an extension of 
+            <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">N-Triples</a>
 
-			([<cite><a class="bibref" rel="biblioentry" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>])
-			carefully taking the most useful and appropriate things added from
-			<a href="http://www.w3.org/DesignIssues/Notation3">Notation 3</a>
-			([<cite><a class="bibref" rel="biblioentry" href="#bib-N3">N3</a></cite>])
-			while staying within the RDF model.</p>
+            ([<cite><a class="bibref" rel="biblioentry" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>])
+            carefully taking the most useful and appropriate things added from
+            <a href="http://www.w3.org/DesignIssues/Notation3">Notation 3</a>
+            ([<cite><a class="bibref" rel="biblioentry" href="#bib-N3">N3</a></cite>])
+            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>
-			[<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>] 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>
-	</div>
-	<div id="an-introduction-to-turtle--informative" typeof="bibo:Chapter" about="#an-introduction-to-turtle--informative" class="section">
+            <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>
+            [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>] 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>
+    </div>
+    <div id="an-introduction-to-turtle--informative" class="section">
 
-			
+            
 <!-- OddPage -->
 <h2><span class="secno">2. </span>An Introduction to Turtle (Informative)</h2>
-			<p>This section is informative.  The
-			<a href="#sec-syntax">Turtle Syntax</a> and <a href="#sec-grammar">Turtle Grammar</a> sections formally define the language.
-			</p>
+            <p>This section is informative.  The
+            <a href="#sec-syntax">Turtle Syntax</a> and <a href="#sec-grammar">Turtle Grammar</a> sections formally define the language.
+            </p>
 
-			<p>A Turtle document allows writing down an RDF graph in a compact
-			textual form.  It consists of a sequence of directives, triple-generating
-			statements or blank lines.  Comments may be given after a <code>#</code> that is not part of another lexical token
-			and continue to the end of the line.</p>
+            <p>A Turtle document allows writing down an RDF graph in a compact
+            textual form.  It consists of a sequence of directives, triple-generating
+            statements or blank lines.  Comments may be given after a <code>#</code> that is not part of another lexical token
+            and continue to the end of the line.</p>
 
-			<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>
-			[<cite><a class="bibref" rel="biblioentry" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>].
-			</p>
+            <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>
+            [<cite><a class="bibref" rel="biblioentry" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>].
+            </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),
-			<a href="../rdf-concepts/index.html#dfn-literal">literals</a> and
-			<a href="../rdf-concepts/index.html#dfn-blank-node">blank nodes</a>.</p>
-
-			<div id="terms" typeof="bibo:Chapter" about="#terms" class="section">
-				<h3><span class="secno">2.1 </span>RDF Terms</h3>
-
-				<p>IRIs are written enclosed in '<' and '>' and may be
-				absolute RDF URI References or relative to the current base IRI
-				(described below).
-				</p>
-
-				<pre class="example">
-<script type="text/turtle"># this is not a complete turtle document
-<http://example.org/path/>
+            <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),
+            <a href="../rdf-concepts/index.html#dfn-literal">literals</a> and
+            <a href="../rdf-concepts/index.html#dfn-blank-node">blank nodes</a>.</p>
 
-<http://example.org/path/#fragment>
-</path>
-<#fragment>
-<>
-</script></pre>
+            <div id="terms" class="section">
+                <h3><span class="secno">2.1 </span>RDF Terms</h3>
 
-				<p>IRIs may also be abbreviated by using Turtle's <code>@prefix</code>
-				directive that allows declaring a short prefix name for a long prefix
-				of repeated IRIs. This is useful for many RDF vocabularies that are
-				all defined with a common namespace like IRI.</p>
-				
-				<p class="note">While <code>@prefix</code> works somewhat like XML 
-				namespaces the restrictions from XML QNames do NOT apply. <code>leg:3032571</code>
-				is a perfectly fine prefixed name.</p>
+                <p>IRIs are written enclosed in '<' and '>' and may be
+                absolute RDF URI References or relative to the current base IRI
+                (described below).
+                </p>
 
-				<p>Once a prefix such as <code>@prefix foo:
-				&lt;http://example.org/ns#&gt;</code> is defined, any mention of a
-				URI later in the document may use a <em>prefixed name</em> that
-				starts <code>foo:</code> to stand for the longer IRI.  So for
-				example, the prefixed name <code>foo:bar</code> is a shorthand for
-				the IRI <code>http://example.org/ns#bar</code>.</p>
+                <pre class="example">
+<span># this is not a complete turtle document
+&lt;http://example.org/path/&gt;
 
-				<pre class="example">
-<script type="text/turtle"># this is a complete turtle document
[email protected] foo: <http://example.org/ns#> .
[email protected] : <http://other.example.org/ns#> .
+&lt;http://example.org/path/#fragment&gt;
+&lt;/path&gt;
+&lt;#fragment&gt;
+&lt;&gt;</span></pre>
+
+                <p>IRIs may also be abbreviated by using Turtle's <code>@prefix</code>
+                directive that allows declaring a short prefix name for a long prefix
+                of repeated IRIs. This is useful for many RDF vocabularies that are
+                all defined with a common namespace like IRI.</p>
+                
+                <p class="note">While <code>@prefix</code> works somewhat like XML 
+                namespaces the restrictions from XML QNames do NOT apply. <code>leg:3032571</code>
+                is a perfectly fine prefixed name.</p>
+
+                <p>Once a prefix such as <code>@prefix foo:
+                <http://example.org/ns#></code> is defined, any mention of a
+                URI later in the document may use a <em>prefixed name</em> that
+                starts <code>foo:</code> to stand for the longer IRI.  So for
+                example, the prefixed name <code>foo:bar</code> is a shorthand for
+                the IRI <code>http://example.org/ns#bar</code>.</p>
+
+                <pre class="example">
+<span># this is a complete turtle document
[email protected] foo: &lt;http://example.org/ns#&gt; .
[email protected] : &lt;http://other.example.org/ns#&gt; .
 foo:bar foo: : .
 :bar : foo:bar .
-</script></pre>
+</span></pre>
 
-				<p>Literals are written either using double-quotes when they do not
-				contain linebreaks like <code>"simple literal"</code> or
-				<code>"""long literal"""</code> when they may contain linebreaks.
-				</p>
+                <p>Literals are written either using double-quotes when they do not
+                contain linebreaks like <code>"simple literal"</code> or
+                <code>"""long literal"""</code> when they may contain linebreaks.
+                </p>
 
-				<pre class="example">
-<script type="text/turtle"># this is not a complete turtle document
+                <pre class="example">
+<span># this is not a complete turtle document
 "a string"
 """a string"""
 """a string
 with newlines
 """
-</script></pre>
+</span></pre>
 
-				<p>Literals have either a language suffix or a datatype IRI
-				but not both.  Languages are indicated by appending the simple
-				literal with <code>@</code> and the language tag.  Datatype IRIs
-				similarly append <code>^^</code> followed by any legal IRI form (full
-				or prefixed) as described above to give the datatype IRI. <span class="non-issue">Literals
-				may be written without either a language tag or a datatype IRI as a
-				shortcut for a literal with the type <code>xsd:string</code>.</span>
-				</p>
+                <p>Literals have either a language suffix or a datatype IRI
+                but not both.  Languages are indicated by appending the simple
+                literal with <code>@</code> and the language tag.  Datatype IRIs
+                similarly append <code>^^</code> followed by any legal IRI form (full
+                or prefixed) as described above to give the datatype IRI. <span class="non-issue">Literals
+                may be written without either a language tag or a datatype IRI as a
+                shortcut for a literal with the type <code>xsd:string</code>.</span>
+                </p>
 
-				<pre class="example">
-<script type="text/turtle"># this is not a complete turtle document
+                <pre class="example">
+<span># this is not a complete turtle document
 "That Seventies Show"
 "That Seventies Show"@en
 "Cette Série des Années Soixante-dix"@fr
 "Cette Série des Années Septante"@fr-be
-"mylexicaldata"^^<http://example.org/my/datatype>
+"mylexicaldata"^^&lt;http://example.org/my/datatype&gt;
 """10"""^^xsd:decimal
-</script></pre>
-
-				<p>
-				  The <code>"That Seventies Show"</code> above is equivalent to <code>"That Seventies Show"^^xsd:string</code>.
-				</p>
+</span></pre>
 
-				<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>
+                  The <code>"That Seventies Show"</code> above is equivalent to <code>"That Seventies Show"^^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>
+                <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>
 
-				which is useful to provide the subject of RDF triples for
-				each pair from the <a href="#prod-turtle2-predicateObjectList">predicateObjectList</a>
-				or the root of the <a href="#prod-turtle2-collection">collection</a>.
-				</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>
 
-				<pre class="example">
-<script type="text/turtle"># this is not a complete turtle document
+                which is useful to provide the subject of RDF triples for
+                each pair from the <a href="#prod-turtle2-predicateObjectList">predicateObjectList</a>
+                or the root of the <a href="#prod-turtle2-collection">collection</a>.
+                </p>
+
+                <pre class="example">
+<span># this is not a complete turtle document
 _:me
 _:a1234
-</script></pre>
+</span></pre>
 
 
-				<p>Literals <span class="non-issue">, prefixed names</span> and IRIs may also contain escapes to encode surrounding
-				syntax, non-printable characters and to encode Unicode characters by
-				codepoint number (although they may also be given directly, encoded
-				as UTF-8).  The character escapes are:</p>
-
-				<ul>
-				<li><code>\t</code> (U+0009, tab)</li>
-				<li><code>\n</code> (U+000A, linefeed)</li>
-				<li><code>\r</code> (U+000D, carriage return)</li>
-
-				<li><code>\"</code> (U+0022, double quote - only allowed inside <a href="#prod-turtle2-String">strings</a>)</li>
-				<li><code>\></code> (U+003E, greater than - only allowed inside <a href="#prod-turtle2-IRI_REF">IRI_REFs</a>)</li>
-				<li><code>\\</code> (U+005C, backslash)</li>
-
-				<li>
-				<code>\u</code><em>HHHH</em> or
-				<code>\U</code><em>HHHHHHHH</em>
-				for writing Unicode characters by hexadecimal codepoint where
-				<em>H</em> is a single hexadecimal digit.
-				</li>
-				</ul>
+                <p>Literals <span class="non-issue">, prefixed names</span> and IRIs may also contain escapes to encode surrounding
+                syntax, non-printable characters and to encode Unicode characters by
+                codepoint number (although they may also be given directly, encoded
+                as UTF-8).  The character escapes are:</p>
 
-				<p>See the <a href="#sec-strings">String escapes</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>
-
-			</div>
-			<div id="iris" typeof="bibo:Chapter" about="#iris" class="section">
-				<h3><span class="secno">2.2 </span>Abbreviating IRIs</h3>
+                <ul>
+                <li><code>\t</code> (U+0009, tab)</li>
+                <li><code>\n</code> (U+000A, linefeed)</li>
+                <li><code>\r</code> (U+000D, carriage return)</li>
 
-				<p>The current base IRI may be altered in a Turtle document using the
-				<code>@base</code> directive.  It allows further abbreviation of
-				IRIs but is usually for simplifying the IRIs in the data, where
-				the prefix directives are for vocabularies that describe the data.</p>
+                <li><code>\"</code> (U+0022, double quote - only allowed inside <a href="#prod-turtle2-String">strings</a>)</li>
+                <li><code>\></code> (U+003E, greater than - only allowed inside <a href="#prod-turtle2-IRI_REF">IRI_REFs</a>)</li>
+                <li><code>\\</code> (U+005C, backslash)</li>
 
-				<p>Whenever this directive appears, it defines the base IRI for which
-				all relative IRIs are resolved against.  That includes IRIs,
-				qualified names, prefix directives as well as later base directives.
-				</p>
+                <li>
+                <code>\u</code><em>HHHH</em> or
+                <code>\U</code><em>HHHHHHHH</em>
+                for writing Unicode characters by hexadecimal codepoint where
+                <em>H</em> is a single hexadecimal digit.
+                </li>
+                </ul>
 
-				<pre class="example">
-<script type="text/turtle"># this is a complete turtle document
+                <p>See the <a href="#sec-strings">String escapes</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>
+
+            </div>
+            <div id="iris" class="section">
+                <h3><span class="secno">2.2 </span>Abbreviating IRIs</h3>
+
+                <p>The current base IRI may be altered in a Turtle document using the
+                <code>@base</code> directive.  It allows further abbreviation of
+                IRIs but is usually for simplifying the IRIs in the data, where
+                the prefix directives are for vocabularies that describe the data.</p>
+
+                <p>Whenever this directive appears, it defines the base IRI for which
+                all relative IRIs are resolved against.  That includes IRIs,
+                qualified names, prefix directives as well as later base directives.
+                </p>
+
+                <pre class="example">
+<span># this is a complete turtle document
 # In-scope base URI is the document URI at this point
-<a1> <b1> <c1> .
[email protected] <http://example.org/ns/> .
+&lt;a1&gt; &lt;b1&gt; &lt;c1&gt; .
[email protected] &lt;http://example.org/ns/&gt; .
 # In-scope base URI is http://example.org/ns/ at this point
 
-<a2> <http://example.org/ns/b2> <c2> .
[email protected] <foo/> .
+&lt;a2&gt; &lt;http://example.org/ns/b2&gt; &lt;c2&gt; .
[email protected] &lt;foo/&gt; .
 # In-scope base URI is http://example.org/ns/foo/ at this point
-<a3> <b3> <c3> .
[email protected] : <bar#> .
+&lt;a3&gt; &lt;b3&gt; &lt;c3&gt; .
[email protected] : &lt;bar#&gt; .
 :a4 :b4 :c4 .
[email protected] : <http://example.org/ns2#> .
-:a5 :b5 :c5 .</script></pre>
[email protected] : &lt;http://example.org/ns2#&gt; .
+:a5 :b5 :c5 .</span></pre>
 
 
-				<p>The token <code>a</code> is equivalent to the IRI
-				<code>&lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#type&gt;</code>
-				</p>
-
-				<pre class="example">
-<script type="text/turtle"># this is a complete turtle document
[email protected] doc: <http://example.org/#ns> .
+                <p>The token <code>a</code> is equivalent to the IRI
+                <code><http://www.w3.org/1999/02/22-rdf-syntax-ns#type></code>
+                </p>
 
-<http://example.org/path> a doc:Document .
-                </script></pre>
-				</div>
-				<div id="abbrev" typeof="bibo:Chapter" about="#abbrev" class="section">
-				<h3><span class="secno">2.3 </span>Abbreviating common datatypes</h3>
+                <pre class="example">
+<span># this is a complete turtle document
[email protected] doc: &lt;http://example.org/#ns&gt; .
 
-				<p>Decimal integers may be written directly and correspond to
-				the XML Schema Datatype
-				<a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:integer</a>
-				in both syntax and datatype IRI.</p>
+&lt;http://example.org/path&gt; a doc:Document .
+                </span></pre>
+                </div>
+                <div id="abbrev" class="section">
+                <h3><span class="secno">2.3 </span>Abbreviating common datatypes</h3>
 
-				<pre class="example">
-<script type="text/turtle">
+                <p>Decimal integers may be written directly and correspond to
+                the XML Schema Datatype
+                <a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:integer</a>
+                in both syntax and datatype IRI.</p>
+
+                <pre class="example">
+<span>
 # this is not a complete turtle document
 -5
 0
@@ -763,34 +751,34 @@
 +1
 # some long form examples
 "-5"^^xsd:integer
-"10"^^<http://www.w3.org/2001/XMLSchema#integer>
-				</script></pre>
+"10"^^&lt;http://www.w3.org/2001/XMLSchema#integer&gt;
+                </span></pre>
 
-				<p>Decimal floating point double/fixed precision numbers may be written
-				directly and correspond to the XML Schema Datatype
-				<a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:double</a>
-				in both syntax and datatype IRI.
-				</p>
+                <p>Decimal floating point double/fixed precision numbers may be written
+                directly and correspond to the XML Schema Datatype
+                <a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:double</a>
+                in both syntax and datatype IRI.
+                </p>
 
-				<pre class="example">
-<script type="text/turtle">
+                <pre class="example">
+<span>
 # this is not a complete turtle document
 1.3e2
 10e0
 -12.5e10
 # some long form examples
 "1.3e2"^^xsd:double
-"-12.5e10"^^<http://www.w3.org/2001/XMLSchema#double>
-				</script></pre>
+"-12.5e10"^^&lt;http://www.w3.org/2001/XMLSchema#double&gt;
+                </span></pre>
 
-				<p>Decimal floating point arbitrary precision numbers may be written
-				directly and correspond to the XML Schema Datatype
-				<a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:decimal</a>.
-				in both syntax and datatype IRI.
-				</p>
+                <p>Decimal floating point arbitrary precision numbers may be written
+                directly and correspond to the XML Schema Datatype
+                <a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:decimal</a>.
+                in both syntax and datatype IRI.
+                </p>
 
-				<pre class="example">
-<script type="text/turtle">
+                <pre class="example">
+<span>
 # this is not a complete turtle document
 0.0
 1.0
@@ -798,102 +786,102 @@
 -5.0
 # some long form examples
 "0.0"^^xsd:decimal
-"-5.0"^^<http://www.w3.org/2001/XMLSchema#decimal>
-
-				</script></pre>
+"-5.0"^^&lt;http://www.w3.org/2001/XMLSchema#decimal&gt;
 
-				<p>Boolean may be written directly as <code>true</code> or
-				<code>false</code> and correspond to the
-				the XML Schema Datatype
-				<a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:boolean</a>
-				in both syntax and datatype IRI.
-				</p>
+                </span></pre>
 
-				<pre class="example">
-<script type="text/turtle">
+                <p>Boolean may be written directly as <code>true</code> or
+                <code>false</code> and correspond to the
+                the XML Schema Datatype
+                <a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:boolean</a>
+                in both syntax and datatype IRI.
+                </p>
+
+                <pre class="example">
+<span>
 # this is not a complete turtle document
 true
 false
 # same in long form
 "true"^^xsd:boolean
-"false"^^<http://www.w3.org/2001/XMLSchema#boolean>
-				</script></pre>
-			</div>
+"false"^^&lt;http://www.w3.org/2001/XMLSchema#boolean&gt;
+                </span></pre>
+            </div>
 
-			<div id="groups" typeof="bibo:Chapter" about="#groups" class="section">
-				<h3><span class="secno">2.4 </span>Abbreviating groups of triples</h3>
+            <div id="groups" class="section">
+                <h3><span class="secno">2.4 </span>Abbreviating groups of triples</h3>
 
-				<p>The <code>,</code> symbol may be used to repeat the subject and
-				predicate of triples that only differ in the object RDF term.</p>
-				<pre class="example">
-<script type="text/turtle">
+                <p>The <code>,</code> symbol may be used to repeat the subject and
+                predicate of triples that only differ in the object RDF term.</p>
+                <pre class="example">
+<span>
 # this is not a complete turtle document
 :subject :predicate :object1 ,
-	:object2 .
+    :object2 .
 # creates two triples, the last triple is :subject :predicate :object2 .
-				</script></pre>
+                </span></pre>
 
-				<p>The <code>;</code> symbol may be used to repeat the subject of
-				triples that vary only in predicate and object RDF terms.</p>
-				<pre class="example">
-<script type="text/turtle">
+                <p>The <code>;</code> symbol may be used to repeat the subject of
+                triples that vary only in predicate and object RDF terms.</p>
+                <pre class="example">
+<span>
 # this is not a complete turtle document
 :subject :predicate1 :obj1 ;
 :predicate2 :obj2 .
 # creates two triples, the last triple is :subject :predicate2 :obj2 .
-				</script></pre>
-
-				</div>
-				<div id="collections" typeof="bibo:Chapter" about="#collections" class="section">
-				<h3><span class="secno">2.5 </span>Abbreviating RDF Collections</h3>
+                </span></pre>
 
-				<p>An RDF Collection may be abbreviated using a sequence of
-				RDF Terms enclosed in <code>( )</code> brackets.  Whitespace may
-				be used to separate them, as usual.  This format provides a
-				blank node at the start of RDF Collection which may be used
-				in further abbreviations.
-				</p>
+                </div>
+                <div id="collections" class="section">
+                <h3><span class="secno">2.5 </span>Abbreviating RDF Collections</h3>
 
-				<pre class="example">
-<script type="text/turtle">
+                <p>An RDF Collection may be abbreviated using a sequence of
+                RDF Terms enclosed in <code>( )</code> brackets.  Whitespace may
+                be used to separate them, as usual.  This format provides a
+                blank node at the start of RDF Collection which may be used
+                in further abbreviations.
+                </p>
+
+                <pre class="example">
+<span>
 # this is a complete turtle document
[email protected] : <http://example.org/foo> .
[email protected] : &lt;http://example.org/foo&gt; .
 # the object of this triple is the RDF collection blank node
 :subject :predicate ( :a :b :c ) .
 
 # an empty collection value - rdf:nil
 :subject :predicate2 () .
-				</script></pre>
+                </span></pre>
 
-				<p>See section <a href="#sec-collections">Collections</a> for
-				the details on the long form of the generated triples.
-				</p>
-			</div>
-		</div>
-		<div id="sec-syntax" typeof="bibo:Chapter" about="#sec-syntax" class="section">
-			
+                <p>See section <a href="#sec-collections">Collections</a> for
+                the details on the long form of the generated triples.
+                </p>
+            </div>
+        </div>
+        <div id="sec-syntax" class="section">
+            
 <!-- OddPage -->
 <h2><span class="secno">3. </span>Syntax for IRIs, Literals and Blank Nodes</h2>
-			<p>Turtle is a language for an <a href="../rdf-concepts/index.html#dfn-rdf-graph">RDF graph</a>,
-			a set of <a href="../rdf-concepts/index.html#dfn-rdf-triple">RDF triple</a>s. An RDF graph is 
-			composed of <a href="../rdf-concepts/index.html#dfn-iri">URI reference</a>s (now interpreted as IRIs),
-			<a href="../rdf-concepts/index.html#dfn-literal">literal</a>s and 
-			<a href="../rdf-concepts/index.html#dfn-blank-node">blank node</a>s.</p>
-			<p>The Turtle syntax for IRIs is identical to that of SPARQL Query, including the use of 
-			<code>prefix</code> and <code>base</code> directives, though these are spelled 
-			<code>@prefix</code> and <code>@base</code> respectively in Turtle. 
-			Per <a href="http://tools.ietf.org/html/rfc3986#section-5.1.1">RFC3986 section 5.1.1</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3986">RFC3986</a></cite>], 
-			the parsing begins with a context-defined In-Scope Base URI. Each <code>@base</code> directive 
-			sets a new In-Scope Base URI, relative to the previous one. <code>@prefix</code> directives 
-			map a local name to an IRI, also resolved against the current In-Scope Base URI. 
-			Subsequent <code>@prefix</code> may re-map the same local name.</p>
+            <p>Turtle is a language for an <a href="../rdf-concepts/index.html#dfn-rdf-graph">RDF graph</a>,
+            a set of <a href="../rdf-concepts/index.html#dfn-rdf-triple">RDF triple</a>s. An RDF graph is 
+            composed of <a href="../rdf-concepts/index.html#dfn-iri">URI reference</a>s (now interpreted as IRIs),
+            <a href="../rdf-concepts/index.html#dfn-literal">literal</a>s and 
+            <a href="../rdf-concepts/index.html#dfn-blank-node">blank node</a>s.</p>
+            <p>The Turtle syntax for IRIs is identical to that of SPARQL Query, including the use of 
+            <code>prefix</code> and <code>base</code> directives, though these are spelled 
+            <code>@prefix</code> and <code>@base</code> respectively in Turtle. 
+            Per <a href="http://tools.ietf.org/html/rfc3986#section-5.1.1">RFC3986 section 5.1.1</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3986">RFC3986</a></cite>], 
+            the parsing begins with a context-defined In-Scope Base URI. Each <code>@base</code> directive 
+            sets a new In-Scope Base URI, relative to the previous one. <code>@prefix</code> directives 
+            map a local name to an IRI, also resolved against the current In-Scope Base URI. 
+            Subsequent <code>@prefix</code> may re-map the same local name.</p>
 
-			<p>Turtle IRI syntax, including relative IRI resolution, is defined by <a href="http://www.w3.org/TR/rdf-sparql-query/#QSynIRI">SPARQL Query section 4.1.1</a> (noting the different spellings of the <code>PREFIX</code> and <code>BASE</code> keywords).</p>
+            <p>Turtle IRI syntax, including relative IRI resolution, is defined by <a href="http://www.w3.org/TR/rdf-sparql-query/#QSynIRI">SPARQL Query section 4.1.1</a> (noting the different spellings of the <code>PREFIX</code> and <code>BASE</code> keywords).</p>
 
-			<p>Example (<a href="tests/test-30.ttl">test-30.ttl</a>) with document base IRI 
-			http://www.w3.org/2001/sw/DataAccess/df1/tests/</p>
+            <p>Example (<a href="tests/test-30.ttl">test-30.ttl</a>) with document base IRI 
+            http://www.w3.org/2001/sw/DataAccess/df1/tests/</p>
 
-			<div><pre class="example">
+            <div><pre class="example">
 # In-scope base URI is http://www.w3.org/2001/sw/DataAccess/df1/tests/ at this point
 &lt;a1&gt; &lt;b1&gt; &lt;c1&gt; .
 @base &lt;http://example.org/ns/&gt; .
@@ -906,20 +894,20 @@
 :a4 :b4 :c4 .
 @prefix : &lt;http://example.org/ns2#&gt; .
 :a5 :b5 :c5 .</pre></div>
-			<p>encodes the following N-Triples
-			(<a href="tests/test-30.out">test-30.out</a>):
+            <p>encodes the following N-Triples
+            (<a href="tests/test-30.out">test-30.out</a>):
 
-			</p>
-			<div><pre class="example">
+            </p>
+            <div><pre class="example">
 &lt;http://www.w3.org/2001/sw/DataAccess/df1/tests/a1&gt; &lt;http://www.w3.org/2001/sw/DataAccess/df1/tests/b1&gt; &lt;http://www.w3.org/2001/sw/DataAccess/df1/tests/c1&gt; .
 &lt;http://example.org/ns/a2&gt; &lt;http://example.org/ns/b2&gt; &lt;http://example.org/ns/c2&gt; .
 &lt;http://example.org/ns/foo/a3&gt; &lt;http://example.org/ns/foo/b3&gt; &lt;http://example.org/ns/foo/c3&gt; .
 &lt;http://example.org/ns/foo/bar#a4&gt; &lt;http://example.org/ns/foo/bar#b4&gt; &lt;http://example.org/ns/foo/bar#c4&gt; .
 &lt;http://example.org/ns2#a5&gt; &lt;http://example.org/ns2#b5&gt; &lt;http://example.org/ns2#c5&gt; .</pre></div>
 
-			<p>The Turtle syntax for literals and blank nodes are defined by <a href="http://www.w3.org/TR/rdf-sparql-query/#QSynLiterals">SPARQL Query section 4.1.2</a> and <a href="http://www.w3.org/TR/rdf-sparql-query/#QSynBlankNodes">SPARQL Query section 4.1.4</a> respectively.</p>
-		</div>
-        <div id="sec-grammar" typeof="bibo:Chapter" about="#sec-grammar" class="section">
+            <p>The Turtle syntax for literals and blank nodes are defined by <a href="http://www.w3.org/TR/rdf-sparql-query/#QSynLiterals">SPARQL Query section 4.1.2</a> and <a href="http://www.w3.org/TR/rdf-sparql-query/#QSynBlankNodes">SPARQL Query section 4.1.4</a> respectively.</p>
+        </div>
+        <div id="sec-grammar" class="section">
           
 <!-- OddPage -->
 <h2><span class="secno">4. </span>Turtle Grammar</h2>
@@ -930,7 +918,7 @@
           Unicode codepoints only in the range U+0 to U+10FFFF inclusive are
           allowed.
           </p>
-          <div id="sec-grammar-ws" typeof="bibo:Chapter" about="#sec-grammar-ws" class="section">
+          <div id="sec-grammar-ws" class="section">
             <h3><span class="secno">4.1 </span>White Space</h3>
 
             <p>White space (production <a href="#prod-turtle2-WS">ws</a>) is used to separate
@@ -942,7 +930,7 @@
             <a href="#prod-turtle2-IRI_REF">IRI_REF</a> and <a href="#prod-turtle2-String">string</a>.
             </p>
           </div>
-          <div id="sec-grammar-comments" typeof="bibo:Chapter" about="#sec-grammar-comments" class="section">
+          <div id="sec-grammar-comments" class="section">
             <h3><span class="secno">4.2 </span>Comments</h3>
 
             <p>Comments in Turtle take the form of '#', outside an
@@ -953,7 +941,7 @@
 
             </p>
           </div>
-          <div id="sec-strings" typeof="bibo:Chapter" about="#sec-strings" class="section">
+          <div id="sec-strings" class="section">
             <h3><span class="secno">4.3 </span>String Escapes</h3>
 
             <p>Turtle strings and IRIs can use <code>\</code>-escape sequences to
@@ -964,14 +952,16 @@
             allowed inside a <a href="#prod-turtle2-String">string</a>
             or <a href="#prod-turtle2-IRI_REF">IRI_REF</a>:</p>
 
-            <table border="1" summary="Turtle string escapes">
-              <tbody>
+            <table>
+              <thead>
                 <tr>
                   <th>Escape</th>
 
                   <th>Unicode code point</th>
 
                 </tr>
+              </thead>
+              <tbody>
 
                 <tr>
                   <td>'\u' <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a> <a href="#rHEX">hex</a></td>
@@ -1033,9 +1023,9 @@
 
             </blockquote>
           </div>
-          <div id="sec-grammar-grammar" typeof="bibo:Chapter" about="#sec-grammar-grammar" class="section">
+          <div id="sec-grammar-grammar" class="section">
           <h3><span class="secno">4.4 </span>Grammar</h3>
-            <p>The <acronym title="Extended Backus–Naur Form">EBNF</acronym> used here is defined in XML 1.0 (Third Edition)
+            <p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0 (Third Edition)
             [<cite><a class="bibref" rel="biblioentry" href="#bib-EBNF-NOTATION">EBNF-NOTATION</a></cite>]. Production labels consisting of a number and a final 's', e.g. [<a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#rRDFLiteral"><span class="prodNo">60s</span></a>], reference to the production with that number in the <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#sparqlGrammar">SPARQL Query Language for RDF grammar</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>].
             </p>
             <p class="note">There are known formating issues with the table form of the grammar. Please see <a href="turtle.bnf">turtle.bnf</a> for exact grammar.</p>
@@ -1639,7 +1629,7 @@
 </table></div>
           </div>
         </div>
-        <div id="sec-parsing" typeof="bibo:Chapter" about="#sec-parsing" class="section"> 
+        <div id="sec-parsing" class="section"> 
           
 <!-- OddPage -->
 <h2><span class="secno">5. </span>Parsing</h2>
@@ -1659,7 +1649,7 @@
 
 
           This section maps a string conforming to the grammar in <a href="#sec-grammar-grammar">section 4.4</a> to a set of triples by mapping strings matching productions and lexical tokens to RDF terms or their components (e.g. language tags, lexical forms of literals). Some productions change the parser state (base or prefix declarations).</p>
-          <div id="sec-parsing-state" typeof="bibo:Chapter" about="#sec-parsing-state" class="section">
+          <div id="sec-parsing-state" class="section">
           <h3><span class="secno">5.1 </span>Parser State</h3>
 
               <p>Parsing Turtle requires a state of four items:</p>
@@ -1678,7 +1668,7 @@
 
               </ul>
           </div>
-          <div id="sec-parsing-terms" typeof="bibo:Chapter" about="#sec-parsing-terms" class="section">
+          <div id="sec-parsing-terms" class="section">
           <h3><span class="secno">5.2 </span>RDF Term Constructors</h3>
 
               <p>This table maps productions and lexical tokens to <code>RDF terms</code> or components of <code>RDF terms</code> listed in <a href="#sec-parsing">section 5</a>:</p>
@@ -1718,7 +1708,7 @@
 <!--  and <a class="type bNode"        href="#term-turtle2-BLANK_NODE_LABEL">BLANK_NODE_LABEL</a>  -->
 .</p>
           </div>
-          <div id="sec-parsing-triples" typeof="bibo:Chapter" about="#sec-parsing-triples" class="section">
+          <div id="sec-parsing-triples" class="section">
           <h3><span class="secno">5.3 </span>RDF Triples Constructors</h3>
               <p>A Turtle document defines an <a href="../rdf-concepts/index.html#dfn-rdf-graph">RDF graph</a> composed of set of <a href="../rdf-concepts/index.html#dfn-rdf-triple">RDF triple</a>s.
           Each <a href="#prod-turtle2-object" class="grammarRef" tabindex="30">object</a> <code>N</code> in the document produces an RDF triple: <span class="ntriple"><code class="curSubject">curSubject</code> <code class="curPredicate">curPredicate</code> <code>N</code> .</span>
@@ -1740,19 +1730,19 @@
           The node produced by matching <code><a href="#prod-turtle2-collection">collection</a></code> is the blank node <code>B<sub>head</sub></code>.
           </p>
           </div>
-          <div class="informative section" id="sec-parsing-example" typeof="bibo:Chapter" about="#sec-parsing-example">
+          <div class="informative section" id="sec-parsing-example">
           <h3><span class="secno">5.4 </span>Parsing Example (Informative)</h3><p><em>This section is non-normative.</em></p>
 
           <p>The following informative example shows the semantic actions performed when  parsing this Turtle document with an LALR(1) parser:</p>
           <pre class="example">
-<script type="text/turtle">
[email protected] ericFoaf: <http://www.w3.org/People/Eric/ericP-foaf.rdf#> .
[email protected] : <http://xmlns.com/foaf/0.1/> .
+<span>
[email protected] ericFoaf: &lt;http://www.w3.org/People/Eric/ericP-foaf.rdf#&gt; .
[email protected] : &lt;http://xmlns.com/foaf/0.1/&gt; .
 ericFoaf:ericP :givenName "Eric" ;
-              :knows <http://norman.walsh.name/knows/who/dan-brickley> ,
-                      [ :mbox <mailto:[email protected]> ] ,
-                      <http://getopenid.com/amyvdh> .
-          </script></pre>
+              :knows &lt;http://norman.walsh.name/knows/who/dan-brickley&gt; ,
+                      [ :mbox &lt;mailto:[email protected]&gt; ] ,
+                      &lt;http://getopenid.com/amyvdh&gt; .
+          </span></pre>
 
               <ul>
                 <li>Map the prefix <code>ericFoaf</code> to the IRI <code>http://www.w3.org/People/Eric/ericP-foaf.rdf#</code>.</li>
@@ -1760,25 +1750,25 @@
                 <li>Assign <code class="curSubject">curSubject</code> the IRI <code>http://www.w3.org/People/Eric/ericP-foaf.rdf#ericP</code>.</li>
 
                 <li>Assign <code class="curPredicate">curPredicate</code> the IRI <code>http://xmlns.com/foaf/0.1/givenName</code>.</li>
-                <li>Emit an RDF triple: <span class="ntriple"><code>&lt;...rdf#ericP&gt;</code> <code>&lt;.../givenName&gt;</code> <code>"Eric"</code> .</span></li>
+                <li>Emit an RDF triple: <span class="ntriple"><code><...rdf#ericP></code> <code><.../givenName></code> <code>"Eric"</code> .</span></li>
 
                 <li>Assign <code class="curPredicate">curPredicate</code> the IRI <code>http://xmlns.com/foaf/0.1/knows</code>.</li>
-                <li>Emit an RDF triple: <span class="ntriple"><code>&lt;...rdf#ericP&gt;</code> <code>&lt;.../knows&gt;</code> <code>&lt;...who/dan-brickley&gt;</code> .</span></li>
+                <li>Emit an RDF triple: <span class="ntriple"><code><...rdf#ericP></code> <code><.../knows></code> <code><...who/dan-brickley></code> .</span></li>
 
-                <li>Emit an RDF triple: <span class="ntriple"><code>&lt;...rdf#ericP&gt;</code> <code>&lt;.../knows&gt;</code> <code>_:1</code> .</span></li>
+                <li>Emit an RDF triple: <span class="ntriple"><code><...rdf#ericP></code> <code><.../knows></code> <code>_:1</code> .</span></li>
                 <li>Save <code class="curSubject">curSubject</code> and reassign to the blank node <code>_:1</code>.</li>
 
                 <li>Save <code class="curPredicate">curPredicate</code>.</li>
                 <li>Assign <code class="curPredicate">curPredicate</code> the IRI <code>http://xmlns.com/foaf/0.1/mbox</code>.</li>
-                <li>Emit an RDF triple: <span class="ntriple"><code>_:1</code> <code>&lt;.../mbox&gt;</code> <code>&lt;mailto:[email protected]&gt;</code> .</span></li>
+                <li>Emit an RDF triple: <span class="ntriple"><code>_:1</code> <code><.../mbox></code> <code><mailto:[email protected]></code> .</span></li>
 
-                <li>Restore <code class="curSubject">curSubject</code> and <code class="curPredicate">curPredicate</code> to their saved values (<code>&lt;...rdf#ericP&gt;</code>, <code>&lt;.../knows&gt;</code>).</li>
-                <li>Emit an RDF triple: <span class="ntriple"><code>&lt;...rdf#ericP&gt;</code> <code>&lt;.../knows&gt;</code> <code>&lt;http://getopenid.com/amyvdh&gt;</code> .</span></li>
+                <li>Restore <code class="curSubject">curSubject</code> and <code class="curPredicate">curPredicate</code> to their saved values (<code><...rdf#ericP></code>, <code><.../knows></code>).</li>
+                <li>Emit an RDF triple: <span class="ntriple"><code><...rdf#ericP></code> <code><.../knows></code> <code><http://getopenid.com/amyvdh></code> .</span></li>
 
               </ul>
           </div>
         </div>
-        <div class="informative section" id="sec-examples" typeof="bibo:Chapter" about="#sec-examples">
+        <div class="informative section" id="sec-examples">
         
 <!-- OddPage -->
 <h2><span class="secno">6. </span>Examples (Informative)</h2><p><em>This section is non-normative.</em></p>
@@ -1805,10 +1795,10 @@
 
           <p>An example of an RDF collection of two literals.</p>
           <pre class="example">
-<script type="text/turtle">
[email protected] : <http://example.org/stuff/1.0/> .
+<span>
[email protected] : &lt;http://example.org/stuff/1.0/&gt; .
 :a :b ( "apple" "banana" ) .
-          </script></pre>
+          </span></pre>
           <p>which is short for (<a href="examples/example2.ttl">example2.ttl</a>):</p>
 
           <div><pre class="example">
@@ -1839,18 +1829,18 @@
           <p>For example,</p>
 
           <pre class="example untested">
-<script type="text/turtle">(1 2.0 3E1) :p "w" .</script></pre>
+<span>(1 2.0 3E1) :p "w" .</span></pre>
 
           <p>is syntactic sugar for (noting that the blank nodes <code>b0</code>, <code>b1</code> and <code>b2</code> do not occur anywhere else in the RDF graph):</p>
 
 <pre class="example untested">
-<script type="text/turtle">    _:b0  rdf:first  1 ;
+<span>    _:b0  rdf:first  1 ;
           rdf:rest   _:b1 .
     _:b1  rdf:first  2.0 ;
           rdf:rest   _:b2 .
     _:b2  rdf:first  3E1 ;
           rdf:rest   rdf:nil .
-    _:b0  :p         "w" . </script></pre>
+    _:b0  :p         "w" . </span></pre>
 
           <p>RDF collections can be nested and can involve other syntactic forms:</p>
 
@@ -1858,7 +1848,7 @@
 (1 [:p :q] ( 2 ) ) .</pre>
 
           <p>is syntactic sugar for:</p><pre class="example untested">
-<script type="text/turtle">    _:b0  rdf:first  1 ;
+<span>    _:b0  rdf:first  1 ;
           rdf:rest   _:b1 .
     _:b1  rdf:first  _:b2 .
     _:b2  :p         :q .
@@ -1866,9 +1856,9 @@
     _:b3  rdf:first  _:b4 .
     _:b4  rdf:first  2 ;
           rdf:rest   rdf:nil .
-    _:b3  rdf:rest   rdf:nil .</script></pre>
+    _:b3  rdf:rest   rdf:nil .</span></pre>
         </div>
-        <div id="sec-identifiers" typeof="bibo:Chapter" about="#sec-identifiers" class="section">
+        <div id="sec-identifiers" class="section">
           
 <!-- OddPage -->
 <h2><span class="secno">7. </span>Identifiers for the Turtle Language</h2>
@@ -1885,7 +1875,7 @@
           </p>
           
         </div>
-        <div id="sec-conformance" typeof="bibo:Chapter" about="#sec-conformance" class="section">
+        <div id="sec-conformance" class="section">
           
 <!-- OddPage -->
 <h2><span class="secno">8. </span>Conformance</h2>
@@ -1907,7 +1897,7 @@
           </li>
           </ol>
         </div>
-        <div id="sec-mime" typeof="bibo:Chapter" about="#sec-mime" class="section">
+        <div id="sec-mime" class="section">
           
 <!-- OddPage -->
 <h2><span class="secno">9. </span>Media Type and Content Encoding</h2>
@@ -1915,19 +1905,19 @@
           <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 
-          <tt>text/</tt> media type tree permits UTF-8 to be sent without a 
+          <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>
         </div>
 
-      <div id="sec-compared" typeof="bibo:Chapter" about="#sec-compared" class="section">
+      <div id="sec-compared" class="section">
         
 <!-- OddPage -->
 <h2><span class="secno">10. </span>Turtle compared</h2>
         <p>Turtle is related to a number of other languages.</p>
-      <div class="informative section" id="sec-diff-ntriples" typeof="bibo:Chapter" about="#sec-diff-ntriples">
+      <div class="informative section" id="sec-diff-ntriples">
         <h3><span class="secno">10.1 </span>Turtle compared to N-Triples (Informative)</h3><p><em>This section is non-normative.</em></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. 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>
@@ -1955,11 +1945,11 @@
           <li><a href="#prod-turtle2-BooleanLiteral">Boolean literals</a> of type <code>xsd:boolean</code></li>
         </ol>
       </div>
-      <div class="informative section" id="sec-diff-n3" typeof="bibo:Chapter" about="#sec-diff-n3">
+      <div class="informative section" id="sec-diff-n3">
         <h3><span class="secno">10.2 </span>Turtle compared to Notation 3 (Informative)</h3><p><em>This section is non-normative.</em></p>
 
-        <p>Turtle is similar to and inspired by the more powerful Notation 3 (<acronym title="Notation 3">N3</acronym>).
-	Please see the most recent Notation3 specification for comparison with Turtle.
+        <p>Turtle is similar to and inspired by the more powerful Notation 3 (<abbr title="Notation 3">N3</abbr>).
+    Please see the most recent Notation3 specification for comparison with Turtle.
 
 <!--  
         While the syntax played a role in the creation of Turtle
@@ -1990,7 +1980,7 @@
  -->
 
       </p></div>
-      <div class="informative section" id="sec-diff-rdfxml" typeof="bibo:Chapter" about="#sec-diff-rdfxml">
+      <div class="informative section" id="sec-diff-rdfxml">
         <h3><span class="secno">10.3 </span>Turtle compared to RDF/XML (Informative)</h3><p><em>This section is non-normative.</em></p>
         <p>
             <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/">RDF/XML</a>
@@ -2000,10 +1990,10 @@
             forbidden and XML 1.0 forbids encoding some Unicode codepoints).
             These restrictions do not apply to Turtle.</p>
       </div>
-      <div class="informative section" id="sec-diff-sparql" typeof="bibo:Chapter" about="#sec-diff-sparql">
+      <div class="informative section" id="sec-diff-sparql">
       <h3><span class="secno">10.4 </span>Turtle compared to SPARQL (Informative)</h3><p><em>This section is non-normative.</em></p>
 
-      <p>The <a href="http://www.w3.org/TR/sparql11-query/">SPARQL Query Language for RDF</a> (<acronym title="SPARQL Protocol And RDF Query Language">SPARQL</acronym>) [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>] uses a Turtle style syntax for its <a href=".http://www.w3.org/TR/sparql11-query/#rTriplesBlock">TriplesBlock production</a>.
+      <p>The <a href="http://www.w3.org/TR/sparql11-query/">SPARQL Query Language for RDF</a> (<abbr title="SPARQL Protocol And RDF Query Language">SPARQL</abbr>) [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>] uses a Turtle style syntax for its <a href="http://www.w3.org/TR/sparql11-query/#rTriplesBlock">TriplesBlock production</a>.
       This production differs from the Turtle language in that:
       </p>
 
@@ -2024,7 +2014,7 @@
       
       </div>
       
-      <div class="appendix section" id="sec-mediaReg" typeof="bibo:Chapter" about="#sec-mediaReg">
+      <div class="appendix section" id="sec-mediaReg">
         
 <!-- OddPage -->
 <h2><span class="secno">A. </span>Internet Media Type, File Extension and Macintosh File Type (Normative)</h2>
@@ -2050,7 +2040,7 @@
           <dt>Required parameters:</dt>
           <dd>None</dd>
           <dt>Optional parameters:</dt>
-          <dd><tt>charset</tt> — this parameter is required when transferring non-ASCII data. If present, the value of <tt>charset</tt> is always <tt>UTF-8</tt>.</dd>
+          <dd><code>charset</code> — this parameter is required when transferring non-ASCII data. If present, the value of <code>charset</code> is always <code>UTF-8</code>.</dd>
 
           <dt>Encoding considerations:</dt>
           <dd>The syntax of Turtle is expressed over code points in Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" rel="biblioentry" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
@@ -2100,12 +2090,12 @@
           <dd>".ttl"</dd>
 
           <dt>Base URI:</dt>
-          <dd>The Turtle '@base &lt;IRIref&gt;' term can change the current base URI for relative IRIrefs in the query language that are used sequentially later in the document.</dd>
+          <dd>The Turtle '@base <IRIref>' term can change the current base URI for relative IRIrefs in the query language that are used sequentially later in the document.</dd>
           <dt>Macintosh file type code(s):</dt>
           <dd>"TEXT"</dd>
-          <dt>Person &amp; email address to contact for further information:</dt>
+          <dt>Person & email address to contact for further information:</dt>
 
-          <dd>Eric Prud'hommeaux &lt;[email protected]&gt;</dd>
+          <dd>Eric Prud'hommeaux <[email protected]></dd>
           <dt>Intended usage:</dt>
           <dd>COMMON</dd>
           <dt>Restrictions on usage:</dt>
@@ -2117,7 +2107,7 @@
       </div>
       
       
-      <div class="appendix section" id="sec-acks" typeof="bibo:Chapter" about="#sec-acks">
+      <div class="appendix section" id="sec-acks">
         
 <!-- OddPage -->
 <h2><span class="secno">B. </span>Acknowledgements (Informative)</h2>
@@ -2136,7 +2126,7 @@
         </p>
 
       </div>
-      <div class="appendix section" id="sec-changelog" typeof="bibo:Chapter" about="#sec-changelog">
+      <div class="appendix section" id="sec-changelog">
       
 <!-- OddPage -->
 <h2><span class="secno">C. </span>Changes (Informative)</h2>
@@ -2176,18 +2166,18 @@
 
 
 
-<div id="references" class="appendix section" typeof="bibo:Chapter" about="#references">
+<div id="references" class="appendix section">
 <!-- OddPage -->
-<h2><span class="secno">D. </span>References</h2><div id="normative-references" typeof="bibo:Chapter" about="#normative-references" class="section"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-EBNF-NOTATION">[EBNF-NOTATION]</dt><dd rel="dcterms:requires">Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href="http://www.w3.org/TR/REC-xml/#sec-notation"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/REC-xml/#sec-notation">http://www.w3.org/TR/REC-xml/#sec-notation</a> 
-</dd><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd rel="dcterms:requires">Jan Grant; Dave Beckett. <a href="http://www.w3.org/TR/rdf-testcases/#ntriples"><cite>N-Triples</cite></a> 10 February 2004. W3C Recommendation. URL:  <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">http://www.w3.org/TR/rdf-testcases/#ntriples</a>
-</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd rel="dcterms:requires">Graham Klyne; Jeremy J. Carroll. <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</a> 
-</dd><dt id="bib-RFC3023">[RFC3023]</dt><dd rel="dcterms:requires">M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a> January 2001. Internet RFC 3023. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a> 
-</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd rel="dcterms:requires">T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a> 
-</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd rel="dcterms:requires">M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs).</cite></a> January 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a> 
-</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd rel="dcterms:requires">The Unicode Consortium. <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a> 2003. Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, ISBN 0-321-18578-1), as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a> 
-</dd><dt id="bib-UTF-8">[UTF-8]</dt><dd rel="dcterms:requires">F. Yergeau. <a href="http://www.ietf.org/rfc/rfc3629.txt"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a>
-</dd></dl></div><div id="informative-references" typeof="bibo:Chapter" about="#informative-references" class="section"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-N3">[N3]</dt><dd rel="dcterms:references">Tim Berners-Lee; Dan Connolly. <a href="http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/"><cite>Notation3 (N3): A readable RDF syntax.</cite></a> 14 January 2008. W3C Team Submission. URL: <a href="http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/">http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/</a> 
-</dd><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd rel="dcterms:references">Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115"><cite>SPARQL Query Language for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</a> 
-</dd><dt id="bib-RDF-SYNTAX-GRAMMAR">[RDF-SYNTAX-GRAMMAR]</dt><dd rel="dcterms:references">Dave Beckett. <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210"><cite>RDF/XML Syntax Specification (Revised).</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210">http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210</a> 
-</dd><dt id="bib-UNISEC">[UNISEC]</dt><dd rel="dcterms:references">Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations</cite></a> 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
+<h2><span class="secno">D. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-EBNF-NOTATION">[EBNF-NOTATION]</dt><dd>Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href="http://www.w3.org/TR/REC-xml/#sec-notation"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/REC-xml/#sec-notation">http://www.w3.org/TR/REC-xml/#sec-notation</a> 
+</dd><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd>Jan Grant; Dave Beckett. <a href="http://www.w3.org/TR/rdf-testcases/#ntriples"><cite>N-Triples</cite></a> 10 February 2004. W3C Recommendation. URL:  <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">http://www.w3.org/TR/rdf-testcases/#ntriples</a>
+</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd>Graham Klyne; Jeremy J. Carroll. <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</a> 
+</dd><dt id="bib-RFC3023">[RFC3023]</dt><dd>M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a> January 2001. Internet RFC 3023. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a> 
+</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a> 
+</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs).</cite></a> January 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a> 
+</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a> 2003. Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, ISBN 0-321-18578-1), as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a> 
+</dd><dt id="bib-UTF-8">[UTF-8]</dt><dd>F. Yergeau. <a href="http://www.ietf.org/rfc/rfc3629.txt"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a>
+</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-N3">[N3]</dt><dd>Tim Berners-Lee; Dan Connolly. <a href="http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/"><cite>Notation3 (N3): A readable RDF syntax.</cite></a> 14 January 2008. W3C Team Submission. URL: <a href="http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/">http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/</a> 
+</dd><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd>Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115"><cite>SPARQL Query Language for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</a> 
+</dd><dt id="bib-RDF-SYNTAX-GRAMMAR">[RDF-SYNTAX-GRAMMAR]</dt><dd>Dave Beckett. <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210"><cite>RDF/XML Syntax Specification (Revised).</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210">http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210</a> 
+</dd><dt id="bib-UNISEC">[UNISEC]</dt><dd>Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations</cite></a> 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
 </dd></dl></div></div></body></html>
\ No newline at end of file
--- a/rdf-turtle/index.html	Wed Aug 03 09:31:00 2011 -0700
+++ b/rdf-turtle/index.html	Fri Aug 05 07:59:15 2011 -0700
@@ -18,8 +18,8 @@
         });
       };
       preprocessTurtle = { apply: function (ignore) {
-          $("script[type='text/turtle']").removeAttr('type').renameElement('div');
-          $("script[type='text/plain']").removeAttr('type').renameElement('div');
+          $("script[type='text/turtle']").removeAttr('type').renameElement('span');
+          $("script[type='text/plain']").removeAttr('type').renameElement('span');
         }
       }
       var respecConfig = {