saving the ReSpec-less HTML rdf-concepts-WD3
authorRichard Cyganiak <richard@cyganiak.de>
Mon, 14 Jan 2013 10:53:08 +0000
branchrdf-concepts-WD3
changeset 575 59695895ece3
parent 574 3f32665d746a
child 577 cd6887bae6a0
saving the ReSpec-less HTML
rdf-concepts/index.html
--- a/rdf-concepts/index.html	Mon Jan 14 10:49:38 2013 +0000
+++ b/rdf-concepts/index.html	Mon Jan 14 10:53:08 2013 +0000
@@ -1,6 +1,7 @@
-<!DOCTYPE html>
-<html lang="en">
-  <head>
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
+<html dir="ltr" about="" property="dcterms:language" content="en" xmlns="http://www.w3.org/1999/xhtml" prefix='bibo: http://purl.org/ontology/bibo/' typeof="bibo:Document">
+<head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     <title>RDF 1.1 Concepts and Abstract Syntax</title>
     <style type="text/css">
@@ -8,119 +9,488 @@
 .figure a[href]:hover { background: transparent; }
 table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
     </style>
-    <script src='../ReSpec.js/js/respec.js' class='remove'></script>
-    <script class='remove'>
-      var respecConfig = {
-          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "WD",
-          
-          // the specification's short name, as in http://www.w3.org/TR/short-name/
-          shortName:            "rdf11-concepts",
-
-          // if your specification has a subtitle that goes below the main
-          // formal title, define it here
-          // subtitle   :  "an excellent document",
-
-          // if you wish the publication date to be other than today, set this
-          publishDate:  "2013-01-15",
-
-          // if the specification's copyright date is a range of years, specify
-          // the start date here:
-          copyrightStart: "2004",
-
-          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
-          // and its maturity status
-          previousPublishDate:  "2012-06-05",
-          previousMaturity:  "WD",
-
-          // if there a publicly available Editor's Draft, this is the link
-          edDraftURI:           "http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html",
-
-          // if this is a LCWD, uncomment and set the end of its review period
-          // lcEnd: "2009-08-05",
-
-          // if there is an earler version of this specification at the Recommendation level,
-          // set this to the shortname of that version. This is optional and not usually
-          // necessary.
-          prevRecShortname: "rdf-concepts",
-
-          // if you want to have extra CSS, append them to this list
-          // it is recommended that the respec.css stylesheet be kept
-          extraCSS:             ["https://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css"],
+    
+    
+  <style type="text/css">
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
 
-          // editors, add as many as you like
-          // only "name" is required
-          editors:  [
-              { name: "Richard Cyganiak", url: "http://richard.cyganiak.de/",
-                company: "DERI, NUI Galway", companyURL: "http://www.deri.ie/",
-              },
-              { name: "David Wood", // url: "http://example.org/",
-                company: "3 Round Stones", companyURL:
-								"http://www.3roundstones.com/",
-              },
-          ],
-          otherContributors: {
-              "Previous editor": [
-                  { name: "Graham Klyne",
-                    //url: "http://www.ninebynine.org/",
-                    company: "Nine by Nine",
-                    //companyURL: "http://example.com/"
-                    //mailto: "[email protected]",
-                  },
-                  { name: "Jeremy J. Carroll",
-                    //url: "http://www-uk.hpl.hp.com/people/jjc/",
-                    company: "Hewlett Packard Labs",
-                    //companyURL: "http://example.com/"
-                    //mailto: "[email protected]",
-                  },
-                  { name: "Brian McBride",
-                    //url: "http://www-uk.hpl.hp.com/people/bwm/",
-                    company: "Hewlett Packard Labs",
-                    //companyURL: "http://example.com/"
-                    //mailto: "[email protected]",
-                    note: "RDF 2004 Series Editor",
-                  },
-              ],
-          },
 
-          // authors, add as many as you like. 
-          // This is optional, uncomment if you have authors as well as editors.
-          // only "name" is required. Same format as editors.
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
 
-          //authors:  [
-          //    { name: "Your Name", url: "http://example.org/",
-          //      company: "Your Company", companyURL: "http://example.com/" },
-          //],
-          
-          // name of the WG
-          wg:           "RDF Working Group",
-          
-          // URI of the public WG page
-          wgURI:        "http://www.w3.org/2011/rdf-wg/",
-          
-          // name (with the @w3c.org) of the public mailing to which comments are due
-          wgPublicList: "public-rdf-comments",
-          
-          // URI of the patent status for this WG, for Rec-track documents
-          // !!!! IMPORTANT !!!!
-          // This is important for Rec-track documents, do not copy a patent URI from a random
-          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
-          // Team Contact.
-          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46168/status",
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
 
-          // if this parameter is set to true, ReSpec.js will embed various RDFa attributes
-          // throughout the generated specification. The triples generated use vocabulary items
-          // from the dcterms, foaf, and bibo. The parameter defaults to false.
-          doRDFa: "1.1",
-      };
+dfn {
+    font-weight:    bold;
+}
 
-// @@@ A number of references have been patched into the local berjon.biblio and need to be added to the global biblio in CVS:
-    </script>
-  </head>
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
 
-  <body>
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  medium dotted #ccc;
+    text-decoration:    none;
+}
 
-<section id="abstract">
+a.bibref {
+    text-decoration:    none;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a {
+    text-decoration:    none;
+}
+
+a .secno {
+    color:  #000;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+    border-top: 1px solid #ff4500;
+    border-bottom: 1px solid #ff4500;
+    padding:    1em;
+    margin-top: 1em;
+}
+
+pre.example::before {
+    content:    "Example";
+    display:    block;
+    width:      150px;
+    background: #ff4500;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+    padding:    1em;
+    margin: 1em 0em 0em;
+    border: 1px solid #f00;
+    background: #ffc;
+}
+
+.issue::before {
+    content:    "Issue";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #f00;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+.note {
+    margin: 1em 0em 0em;
+    padding:    1em;
+    border: 2px solid #cff6d9;
+    background: #e2fff0;
+}
+
+.note::before {
+    content:    "Note";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #cff6d9;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+    border: solid #bebebe 1px;
+    margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+    margin: 1.5em 0.5em 1em 1em;
+    font-weight: bold;
+    font-style: italic;
+}
+
+span.practicelab   { background: #dfffff; }
+
+span.practicelab {
+    position: relative;
+    padding: 0 0.5em;
+    top: -1.5em;
+}
+
+p.practicedesc {
+    margin: 1.5em 0.5em 1em 1em;
+}
+
[email protected] screen {
+    p.practicedesc {
+        position: relative;
+        top: -2em;
+        padding: 0;
+        margin: 1.5em 0.5em -1em 1em;
+    }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+  background-color: white;
+  color: black;
+  font-style: normal;
+  font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; }           /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; }                            /* basic types */
+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_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 */
+pre.sh_sourceCode .sh_symbol { color: blue; }                            /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; }         /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; }                              /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; }   /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+pre.sh_sourceCode .sh_paren { color: red; }
+pre.sh_sourceCode .sh_attribute { color: #006400; }
+
+</style><link href="https://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" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a></p><h1 property="dcterms:title" class="title" id="title">RDF 1.1 Concepts and Abstract Syntax</h1><h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-01-15T00:00:00+0000" id="w3c-working-draft-15-january-2013"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 15 January 2013</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/">http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html">http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html</a></dd><dt>Previous version:</dt><dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/">http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/</a></dd><dt>Latest recommendation:</dt><dd><a href="http://www.w3.org/TR/rdf-concepts/">http://www.w3.org/TR/rdf-concepts/</a></dd><dt>Editors:</dt><dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Richard Cyganiak" href="http://richard.cyganiak.de/">Richard Cyganiak</a>, <a rel="foaf:workplaceHomepage" href="http://www.deri.ie/">DERI, NUI Galway</a></span>
+</dd>
+<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><span property="foaf:name">David Wood</span>, <a rel="foaf:workplaceHomepage" href="http://www.3roundstones.com/">3 Round Stones</a></span>
+</dd>
+<dt>Previous editors:</dt><dd><span><span>Graham Klyne</span>, Nine by Nine</span>
+</dd>
+<dd><span><span>Jeremy J. Carroll</span>, Hewlett Packard Labs</span>
+</dd>
+<dd><span><span>Brian McBride</span>, Hewlett Packard Labs (RDF 2004 Series Editor)</span>
+</dd>
+</dl><p class="copyright"><a rel="license" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2004-2013 <span rel="dcterms:publisher"><span typeof="foaf:Organization"><a rel="foaf:homepage" property="foaf:name" content="World Wide Web Consortium" href="http://www.w3.org/"><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. <acronym title="World Wide Web Consortium">W3C</acronym> <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" resource="#abstract" rel="bibo:chapter"><h2>Abstract</h2>
     <p>The Resource Description Framework (RDF) is a framework for
     representing information in the Web.</p>
     <p>RDF 1.1 Concepts and Abstract Syntax defines an abstract syntax
@@ -134,10 +504,7 @@
     This document also introduces key concepts and terminology, and discusses
     datatyping and the handling of fragment identifiers in IRIs within
     RDF graphs.</p>
-</section>
-
-
-<section id="sotd">
+</div><div id="sotd" class="introductory section" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><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 <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
     <p>This document is a snapshot of the
     <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a>'s
     progress towards updating the RDF data model for RDF 1.1.
@@ -159,11 +526,14 @@
     <a href="#section-dataset">operations on RDF datasets</a>,
     and the <a href="#section-fragID">relation of RDF datasets to
     aspects of web architecture</a>.</p>
-</section>
+<p>This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46168/status" rel="disclosure">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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" typeof="bibo:Chapter" resource="#toc" rel="bibo:chapter" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#section-Introduction" class="tocxref"><span class="secno">1 </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#data-model" class="tocxref"><span class="secno">1.1 </span>Graph-based Data Model</a></li><li class="tocline"><a href="#resources-and-statements" class="tocxref"><span class="secno">1.2 </span>Resources and Statements</a></li><li class="tocline"><a href="#referents" class="tocxref"><span class="secno">1.3 </span>The Referent of an <acronym title="Internationalized Resource Identifier">IRI</acronym></a></li><li class="tocline"><a href="#vocabularies" class="tocxref"><span class="secno">1.4 </span>RDF Vocabularies and Namespace IRIs</a></li><li class="tocline"><a href="#change-over-time" class="tocxref"><span class="secno">1.5 </span>RDF and Change Over Time</a></li><li class="tocline"><a href="#managing-graphs" class="tocxref"><span class="secno">1.6 </span>Working with Multiple RDF Graphs</a></li><li class="tocline"><a href="#entailment" class="tocxref"><span class="secno">1.7 </span>Equivalence, Entailment and Inconsistency</a></li><li class="tocline"><a href="#rdf-documents" class="tocxref"><span class="secno">1.8 </span>RDF Documents and Syntaxes</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2 </span>Conformance</a></li><li class="tocline"><a href="#section-rdf-graph" class="tocxref"><span class="secno">3 </span>RDF Graphs</a><ul class="toc"><li class="tocline"><a href="#section-triples" class="tocxref"><span class="secno">3.1 </span>Triples</a></li><li class="tocline"><a href="#section-IRIs" class="tocxref"><span class="secno">3.2 </span>IRIs</a></li><li class="tocline"><a href="#section-Graph-Literal" class="tocxref"><span class="secno">3.3 </span>Literals</a></li><li class="tocline"><a href="#section-blank-nodes" class="tocxref"><span class="secno">3.4 </span>Blank Nodes</a></li><li class="tocline"><a href="#section-skolemization" class="tocxref"><span class="secno">3.5 </span>Replacing Blank Nodes with IRIs</a></li><li class="tocline"><a href="#graph-isomorphism" class="tocxref"><span class="secno">3.6 </span>Graph Isomorphism</a></li></ul></li><li class="tocline"><a href="#section-dataset" class="tocxref"><span class="secno">4 </span>RDF Datasets</a></li><li class="tocline"><a href="#section-Datatypes" class="tocxref"><span class="secno">5 </span>Datatypes</a><ul class="toc"><li class="tocline"><a href="#xsd-datatypes" class="tocxref"><span class="secno">5.1 </span>The XML Schema Built-in Datatypes</a></li><li class="tocline"><a href="#section-html" class="tocxref"><span class="secno">5.2 </span>The <code>rdf:HTML</code> Datatype</a></li><li class="tocline"><a href="#section-XMLLiteral" class="tocxref"><span class="secno">5.3 </span>The <code>rdf:XMLLiteral</code> Datatype</a></li><li class="tocline"><a href="#datatype-maps" class="tocxref"><span class="secno">5.4 </span>Datatype Maps</a></li><li class="tocline"><a href="#section-Literal-Value" class="tocxref"><span class="secno">5.5 </span>The Value Corresponding to a Literal</a></li></ul></li><li class="tocline"><a href="#section-fragID" class="tocxref"><span class="secno">6 </span>Fragment Identifiers</a></li><li class="tocline"><a href="#section-Acknowledgments" class="tocxref"><span class="secno">7 </span>Acknowledgments</a></li><li class="tocline"><a href="#changes" class="tocxref"><span class="secno">A </span>Changes between RDF 2004 and RDF 1.1</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno">B </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#changes-wd3" class="tocxref"><span class="secno">B.1 </span>Changes from 05 June 2012 WD to this version</a></li><li class="tocline"><a href="#changes-wd2" class="tocxref"><span class="secno">B.2 </span>Changes from FPWD to 05 June 2012 WD</a></li><li class="tocline"><a href="#changes-fpwd" class="tocxref"><span class="secno">B.3 </span>Changes from RDF 2004 to FPWD</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
 
 
-<section id="section-Introduction" class="informative">
-    <h2>Introduction</h2>
+
+
+
+<div id="section-Introduction" class="informative section" typeof="bibo:Chapter" resource="#section-Introduction" rel="bibo:chapter">
+    <h2><span class="secno">1 </span>Introduction</h2><p><em>This section is non-normative.</em></p>
 
     <p class="issue">This is a work-in-progress Working Draft. Various open
     issues are flagged throughout the text with boxes like this.
@@ -178,27 +548,27 @@
 
     <ul>
       <li>serialization syntaxes for storing and exchanging RDF
-      (e.g., <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[TURTLE-TR]]
+      (e.g., <a href="http://www.w3.org/TR/turtle/">Turtle</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>]
       and <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF/XML</a>
-      [[RDF-SYNTAX-GRAMMAR]]),</li>
+      [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>]),</li>
 
       <li>the <a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL
-      Query Language</a> [[RDF-SPARQL-QUERY]],</li>
+      Query Language</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>],</li>
 
       <li>the <a href="http://www.w3.org/TR/rdf-schema/">RDF Vocabulary
-      Description Language</a> (RDFS) [[RDF-SCHEMA]],</li>
+      Description Language</a> (RDFS) [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>],</li>
 
       <li>the <a href="http://www.w3.org/TR/rdf-mt/">formal
-      model-theoretic semantics for RDF and RDFS</a> [[RDF-MT]].</li>
+      model-theoretic semantics for RDF and RDFS</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>].</li>
     </ul>
 
-<section id="data-model">
-    <h3>Graph-based Data Model</h3>
+<div id="data-model" typeof="bibo:Chapter" resource="#data-model" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.1 </span>Graph-based Data Model</h3>
 
     <p>The core structure of the abstract syntax is a set of
-    <a title="RDF triple">triples</a>, each consisting of a <a>subject</a>,
-    a <a>predicate</a> and an <a>object</a>. A set of such triples is called
-    an <a>RDF graph</a>. An RDF graph can be visualized as a node and
+    <a title="RDF triple" href="#dfn-rdf-triple" class="internalDFN">triples</a>, each consisting of a <a href="#dfn-subject" class="internalDFN">subject</a>,
+    a <a href="#dfn-predicate" class="internalDFN">predicate</a> and an <a href="#dfn-object" class="internalDFN">object</a>. A set of such triples is called
+    an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>. An RDF graph can be visualized as a node and
     directed-arc diagram, in which each triple is represented as a
     node-arc-node link.</p>
 
@@ -206,126 +576,126 @@
       <a href="rdf-graph.png"><img src="rdf-graph.svg" alt="An RDF graph with two nodes (Subject and Object) and a triple connecting them (Predicate)" /></a>
     </div>
 
-    <p>There can be three kinds of <a title="node">nodes</a> in an
-    <a>RDF graph</a>: <a title="IRI">IRIs</a>, <a title="literal">literals</a>,
-    and <a title="blank node">blank nodes</a>.</p>
-</section>
+    <p>There can be three kinds of <a title="node" href="#dfn-node" class="internalDFN">nodes</a> in an
+    <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>: <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>, <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>,
+    and <a title="blank node" href="#dfn-blank-node" class="internalDFN">blank nodes</a>.</p>
+</div>
 
 
-<section id="resources-and-statements">
-    <h3>Resources and Statements</h3>
+<div id="resources-and-statements" typeof="bibo:Chapter" resource="#resources-and-statements" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.2 </span>Resources and Statements</h3>
 
-    <p>Any <a>IRI</a> or <a>literal</a> <dfn title="denote">denotes</dfn>
+    <p>Any <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> or <a href="#dfn-literal" class="internalDFN">literal</a> <dfn title="denote" id="dfn-denote">denotes</dfn>
     some thing in the universe of discourse. These things are called
-    <dfn title="resource">resources</dfn>. Anything can be a resource,
+    <dfn title="resource" id="dfn-resource">resources</dfn>. Anything can be a resource,
     including physical things, documents, abstract concepts, numbers
     and strings; the term is synonymous with “entity”.
-    The resource denoted by an IRI is called its <a>referent</a>, and the
+    The resource denoted by an <acronym title="Internationalized Resource Identifier">IRI</acronym> is called its <a href="#dfn-referent" class="internalDFN">referent</a>, and the
     resource denoted by a literal is called its
-    <a title="literal value">literal value</a>. Literals have
-    <a title="datatype">datatypes</a> that define the range of possible
+    <a title="literal value" href="#dfn-literal-value" class="internalDFN">literal value</a>. Literals have
+    <a title="datatype" href="#dfn-datatype" class="internalDFN">datatypes</a> that define the range of possible
     values, such as strings, numbers, and dates. A special kind of literals,
     <a>language-tagged strings</a>, denote plain-text strings in a
     natural language.</p>
 
-    <p>The assertion of an <a>RDF triple</a> says that <em>some relationship,
-    indicated by the <a>predicate</a>, holds between the
-    <a title="resource">resources</a> <a title="denote">denoted</a> by
-    the <a>subject</a> and <a>object</a></em>. This statement corresponding
-    to an RDF triple is known as an <dfn>RDF statement</dfn>.
-    The predicate itself is an <a>IRI</a> and denotes a <dfn>property</dfn>,
-    that is, a <a>resource</a> that can be thought of as a binary relation.
+    <p>The assertion of an <a href="#dfn-rdf-triple" class="internalDFN">RDF triple</a> says that <em>some relationship,
+    indicated by the <a href="#dfn-predicate" class="internalDFN">predicate</a>, holds between the
+    <a title="resource" href="#dfn-resource" class="internalDFN">resources</a> <a title="denote" href="#dfn-denote" class="internalDFN">denoted</a> by
+    the <a href="#dfn-subject" class="internalDFN">subject</a> and <a href="#dfn-object" class="internalDFN">object</a></em>. This statement corresponding
+    to an RDF triple is known as an <dfn id="dfn-rdf-statement">RDF statement</dfn>.
+    The predicate itself is an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> and denotes a <dfn id="dfn-property">property</dfn>,
+    that is, a <a href="#dfn-resource" class="internalDFN">resource</a> that can be thought of as a binary relation.
     (Relations that involve more than two entities can only be
     <a href="http://www.w3.org/TR/swbp-n-aryRelations/">indirectly
-    expressed in RDF</a> [[SWBP-N-ARYRELATIONS]].)</p>
+    expressed in RDF</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-SWBP-N-ARYRELATIONS">SWBP-N-ARYRELATIONS</a></cite>].)</p>
 
-    <p>Unlike <a title="IRI">IRIs</a> and <a title="literal">literals</a>,
-    <a title="blank node">blank nodes</a> do not denote specific
-    <a title="resource">resources</a>.
-    <a title="RDF statement">Statements</a> involving
+    <p>Unlike <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> and <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>,
+    <a title="blank node" href="#dfn-blank-node" class="internalDFN">blank nodes</a> do not denote specific
+    <a title="resource" href="#dfn-resource" class="internalDFN">resources</a>.
+    <a title="RDF statement" href="#dfn-rdf-statement" class="internalDFN">Statements</a> involving
     blank nodes say that something with the given
     relationships exists, without explicitly naming it.</p>
-</section>
+</div>
 
 
-<section id="referents">
-    <h3>The Referent of an IRI</h3>
+<div id="referents" typeof="bibo:Chapter" resource="#referents" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.3 </span>The Referent of an <acronym title="Internationalized Resource Identifier">IRI</acronym></h3>
 
-    <p>The <a>resource</a> <a title="denote">denoted</a> by an <a>IRI</a>
-    is also called its <dfn>referent</dfn>.
-    What exactly is denoted by any given IRI is not defined by this
+    <p>The <a href="#dfn-resource" class="internalDFN">resource</a> <a title="denote" href="#dfn-denote" class="internalDFN">denoted</a> by an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a>
+    is also called its <dfn id="dfn-referent">referent</dfn>.
+    What exactly is denoted by any given <acronym title="Internationalized Resource Identifier">IRI</acronym> is not defined by this
     specification.</p>
 
-    <p>Guidelines for determining the <a>referent</a> of an <a>IRI</a> are
+    <p>Guidelines for determining the <a href="#dfn-referent" class="internalDFN">referent</a> of an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> are
     provided in other documents, like
     <em><a href="http://www.w3.org/TR/webarch/">Architecture of the
-    World Wide Web, Volume One</a></em> [[WEBARCH]] and
+    World Wide Web, Volume One</a></em> [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] and
     <em><a href="http://www.w3.org/TR/cooluris/">Cool URIs for the
-    Semantic Web</a></em> [[COOLURIS]].
+    Semantic Web</a></em> [<cite><a class="bibref" rel="biblioentry" href="#bib-COOLURIS">COOLURIS</a></cite>].
     A very brief, informal and partial account follows:</p>
 
     <ul>
-    <li>IRIs have global scope: An IRI is assumed to <a>denote</a>
-    the same <a>resource</a> regardless of where the IRI occurs.</li>
+    <li>IRIs have global scope: An <acronym title="Internationalized Resource Identifier">IRI</acronym> is assumed to <a href="#dfn-denote" class="internalDFN">denote</a>
+    the same <a href="#dfn-resource" class="internalDFN">resource</a> regardless of where the <acronym title="Internationalized Resource Identifier">IRI</acronym> occurs.</li>
 
     <li>By social convention, the
-    <a href="http://www.w3.org/TR/webarch/#uri-ownership">IRI owner</a>
-    [[WEBARCH]] gets to say what an <a>IRI</a> <a title="denote">denotes</a>.
-    They do this when “<dfn>minting</dfn>” a new IRI.</li>
+    <a href="http://www.w3.org/TR/webarch/#uri-ownership"><acronym title="Internationalized Resource Identifier">IRI</acronym> owner</a>
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] gets to say what an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> <a title="denote" href="#dfn-denote" class="internalDFN">denotes</a>.
+    They do this when “<dfn id="dfn-minting">minting</dfn>” a new <acronym title="Internationalized Resource Identifier">IRI</acronym>.</li>
 
-    <li>The IRI owner can establish the intended <a>referent</a>
+    <li>The <acronym title="Internationalized Resource Identifier">IRI</acronym> owner can establish the intended <a href="#dfn-referent" class="internalDFN">referent</a>
     by means of a specification or other document that explains
     what is denoted. For example, the
     <a href="http://www.w3.org/TR/vocab-org/">Organization Ontology
-    document</a> [[VOCAB-ORG]] specifies the referents
+    document</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-VOCAB-ORG">VOCAB-ORG</a></cite>] specifies the referents
     of various IRIs that start with
     <code>http://www.w3.org/ns/org#</code>.</li>
 
     <li>A good way of communicating the intended referent
-    is to set up the IRI so that it
+    is to set up the <acronym title="Internationalized Resource Identifier">IRI</acronym> so that it
     <a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferences</a>
-    [[WEBARCH]] to such a document.</li>
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] to such a document.</li>
 
-    <li>Such a document can, in fact, be an <a>RDF document</a>
+    <li>Such a document can, in fact, be an <a href="#dfn-rdf-document" class="internalDFN">RDF document</a>
     that describes the denoted resource by means of
-    <a title="RDF statement">RDF statements</a>.</li>
+    <a title="RDF statement" href="#dfn-rdf-statement" class="internalDFN">RDF statements</a>.</li>
     </ul>
 
-    <p>Perhaps the most important characterisitic of <a title="IRI">IRIs</a>
+    <p>Perhaps the most important characterisitic of <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>
     in web architecture is that they can be 
     <a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferenced</a>,
     and hence serve as starting points for interactions with a remote server.
     This specification, however, is not concerned with such interactions.
     It does not define an interaction model. It only treats IRIs as globally
     unique identifiers in a graph data model that describes resources.</p>
-</section>
+</div>
 
-<section id="vocabularies">
-    <h3>RDF Vocabularies and Namespace IRIs</h3>
+<div id="vocabularies" typeof="bibo:Chapter" resource="#vocabularies" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.4 </span>RDF Vocabularies and Namespace IRIs</h3>
 
-    <p>An <dfn>RDF vocabulary</dfn> is a collection of <a title="IRI">IRIs</a>
-    with clearly established <a title="referent">referents</a>
-    intended for use in <a title="RDF graph">RDF graphs</a>. For example,
-    the IRIs documented in [[RDF-SCHEMA]] are the RDF Schema vocabulary.
+    <p>An <dfn id="dfn-rdf-vocabulary">RDF vocabulary</dfn> is a collection of <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>
+    with clearly established <a title="referent" href="#dfn-referent" class="internalDFN">referents</a>
+    intended for use in <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>. For example,
+    the IRIs documented in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>] are the RDF Schema vocabulary.
     RDF Schema can itself be used to define and document additional
     RDF vocabularies. Some such vocabularies are mentioned in the
-    Primer [[RDF-PRIMER]].</p>
-
-    <p>The <a title="IRI">IRIs</a> in an <a>RDF vocabulary</a> often share
-    a common substring known as a <dfn>namespace IRI</dfn>.
-    Some namespace IRIs are associated by convention with a short name
-    known as a <dfn>namespace prefix</dfn>. Some examples:
+    Primer [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>].</p>
 
-    <table rules="all" summary="Some example namespace prefixes and IRIs">
-      <tr><th>Namespace prefix</th><th>Namespace IRI</th><th>RDF vocabulary</th></tr>
-      <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td><td>The RDF built-in vocabulary [[RDF-SCHEMA]]</td></tr>
-      <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema#"><code>http://www.w3.org/2000/01/rdf-schema#</code></a></td><td>The RDF Schema vocabulary [[RDF-SCHEMA]]</td></tr>
-      <tr><td>xsd</td><td><a href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The <a>RDF-compatible XSD types</a></td></tr>
-    </table>
+    <p>The <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> in an <a href="#dfn-rdf-vocabulary" class="internalDFN">RDF vocabulary</a> often share
+    a common substring known as a <dfn id="dfn-namespace-iri">namespace <acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>.
+    Some namespace IRIs are associated by convention with a short name
+    known as a <dfn id="dfn-namespace-prefix">namespace prefix</dfn>. Some examples:
 
-    <p>In some contexts it is common to abbreviate <a title="IRI">IRIs</a>
-    that start with <a title="namespace IRI">namespace IRIs</a> by using the
-    associated <a>namespace prefix</a>. For example, the IRI
+    </p><table rules="all" summary="Some example namespace prefixes and IRIs">
+      <tbody><tr><th>Namespace prefix</th><th>Namespace <acronym title="Internationalized Resource Identifier">IRI</acronym></th><th>RDF vocabulary</th></tr>
+      <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td><td>The RDF built-in vocabulary [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</td></tr>
+      <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema#"><code>http://www.w3.org/2000/01/rdf-schema#</code></a></td><td>The RDF Schema vocabulary [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</td></tr>
+      <tr><td>xsd</td><td><a href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a></td></tr>
+    </tbody></table>
+
+    <p>In some contexts it is common to abbreviate <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>
+    that start with <a title="namespace IRI" href="#dfn-namespace-iri" class="internalDFN">namespace IRIs</a> by using the
+    associated <a href="#dfn-namespace-prefix" class="internalDFN">namespace prefix</a>. For example, the <acronym title="Internationalized Resource Identifier">IRI</acronym>
     <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
     would be abbreviated as <code>rdf:XMLLiteral</code>.
     Note however that these abbreviations are <em>not</em> valid IRIs,
@@ -334,99 +704,99 @@
     RDF data model. They are merely a syntactic convenience for
     abbreviating IRIs.</p>
 
-    <p>The term “<dfn>namespace</dfn>” on its own does not have a
+    <p>The term “<dfn id="dfn-namespace">namespace</dfn>” on its own does not have a
     well-defined meaning in the context of RDF, but is sometimes informally
-    used to mean “<a>namespace IRI</a>” or “<a>RDF vocabulary</a>”.</p>
-</section>
+    used to mean “<a href="#dfn-namespace-iri" class="internalDFN">namespace <acronym title="Internationalized Resource Identifier">IRI</acronym></a>” or “<a href="#dfn-rdf-vocabulary" class="internalDFN">RDF vocabulary</a>”.</p>
+</div>
 
 
-<section id="change-over-time">
-    <h2>RDF and Change Over Time</h2>
+<div id="change-over-time" typeof="bibo:Chapter" resource="#change-over-time" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.5 </span>RDF and Change Over Time</h3>
 
     <p>The RDF data model is <em>atemporal</em>: It does not deal with time,
     and does not have a built-in notion of temporal validity of information.
-    <a title="RDF graph">RDF graphs</a> are static snapshots of
+    <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a> are static snapshots of
     information.</p>
 
-    <p>However, <a title="RDF graph">RDF graphs</a> can express information
+    <p>However, <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a> can express information
     about events and about temporal aspects of other entities,
-    given appropriate <a title="RDF vocabulary">vocabulary</a> terms.</p>
+    given appropriate <a title="RDF vocabulary" href="#dfn-rdf-vocabulary" class="internalDFN">vocabulary</a> terms.</p>
 
-    <p>Since <a title="RDF graph">RDF graphs</a> are defined as mathematical
-    sets, adding or removing <a title="RDF triple">triples</a> from an
+    <p>Since <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a> are defined as mathematical
+    sets, adding or removing <a title="RDF triple" href="#dfn-rdf-triple" class="internalDFN">triples</a> from an
     RDF graph yields a different RDF graph.</p>
 
-    <p>We informally use the term <dfn>RDF source</dfn> to refer to a
+    <p>We informally use the term <dfn id="dfn-rdf-source">RDF source</dfn> to refer to a
     persistent yet mutable source or container of
-    <a title="RDF graph">RDF graphs</a>. An RDF source is a <a>resource</a>
+    <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>. An RDF source is a <a href="#dfn-resource" class="internalDFN">resource</a>
     that may be said to have a state that can change over time.
     A snapshot of the state can be expressed as an RDF graph.
     For example, any web document that has an RDF-bearing representation
     may be considered an RDF source. Like all resources, RDF sources may
-    be named with <a title="IRI">IRIs</a> and therefore described in
+    be named with <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> and therefore described in
     other RDF graphs.</p>
 
     <p>Intuitively speaking, changes in the universe of discourse
     can be reflected in the following ways:</p>
 
     <ul>
-      <li>An <a>IRI</a>, once <a title="minting">minted</a>, should never
-      change its <a>referent</a>. (See
-      <a href="http://www.w3.org/TR/webarch/#URI-persistence">URI
-      persistence</a> [[WEBARCH]].)</li>
-      <li><a title="literal">Literals</a>, by design, are constants and
-      never change their <a title="literal value">value</a>.</li>
-      <li>Some <a title="property">properties</a> may change over time.
-      A relationship that holds between two <a title="resource">resources</a>
+      <li>An <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a>, once <a title="minting" href="#dfn-minting" class="internalDFN">minted</a>, should never
+      change its <a href="#dfn-referent" class="internalDFN">referent</a>. (See
+      <a href="http://www.w3.org/TR/webarch/#URI-persistence"><acronym title="Uniform Resource Identifier">URI</acronym>
+      persistence</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>].)</li>
+      <li><a title="literal" href="#dfn-literal" class="internalDFN">Literals</a>, by design, are constants and
+      never change their <a title="literal value" href="#dfn-literal-value" class="internalDFN">value</a>.</li>
+      <li>Some <a title="property" href="#dfn-property" class="internalDFN">properties</a> may change over time.
+      A relationship that holds between two <a title="resource" href="#dfn-resource" class="internalDFN">resources</a>
       at one time may not hold at another time.</li>
-      <li><a title="RDF source">RDF sources</a> may change their state
+      <li><a title="RDF source" href="#dfn-rdf-source" class="internalDFN">RDF sources</a> may change their state
       over time.
-      That is, they may provide different <a title="RDF graph">RDF graphs</a>
+      That is, they may provide different <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>
       at different times.</li>
-      <li>Some <a title="RDF source">RDF sources</a> may, however, be immutable
+      <li>Some <a title="RDF source" href="#dfn-rdf-source" class="internalDFN">RDF sources</a> may, however, be immutable
       snapshots of another RDF source, archiving its state at some
       point in time.</li>
     </ul>
 
-</section>
+</div>
 
 
-<section id="managing-graphs">
-    <h3>Working with Multiple RDF Graphs</h3>
+<div id="managing-graphs" typeof="bibo:Chapter" resource="#managing-graphs" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.6 </span>Working with Multiple RDF Graphs</h3>
 
     <p>As RDF graphs are sets of triples, they can be
-    <a title="merge">merged</a> easily, supporting the use of data from
+    <a title="merge" href="#dfn-merge" class="internalDFN">merged</a> easily, supporting the use of data from
     multiple sources. Nevertheless, it is sometimes desirable to work
     with multiple RDF graphs while keeping their contents separate.
-    <a title="RDF dataset">RDF datasets</a> support this requirement.</p>
+    <a title="RDF dataset" href="#dfn-rdf-dataset" class="internalDFN">RDF datasets</a> support this requirement.</p>
 
-    <p>An <a>RDF dataset</a> is a collection of
-    <a title="RDF graph">RDF graphs</a>. All but one of these graphs have
-    an associated <a>IRI</a>. They are called
-    <a title="named graph">named graphs</a>, and the IRI is called the
-    <a>graph name</a>.
-    The remaining graph does not have an associated IRI, and is called
-    the <a>default graph</a> of the RDF dataset.</p>
+    <p>An <a href="#dfn-rdf-dataset" class="internalDFN">RDF dataset</a> is a collection of
+    <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>. All but one of these graphs have
+    an associated <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a>. They are called
+    <a title="named graph" href="#dfn-named-graph" class="internalDFN">named graphs</a>, and the <acronym title="Internationalized Resource Identifier">IRI</acronym> is called the
+    <a href="#dfn-graph-name" class="internalDFN">graph name</a>.
+    The remaining graph does not have an associated <acronym title="Internationalized Resource Identifier">IRI</acronym>, and is called
+    the <a href="#dfn-default-graph" class="internalDFN">default graph</a> of the RDF dataset.</p>
 
-    <p>There are many possible uses for <a title="RDF dataset">RDF datasets</a>.
+    <p>There are many possible uses for <a title="RDF dataset" href="#dfn-rdf-dataset" class="internalDFN">RDF datasets</a>.
     One such use is to hold snapshots of multiple
-    <a title="RDF source">RDF sources</a>. It is common to have the
-    <a>default graph</a> contain <a title="RDF triple">triples</a>
-    that involve the <a title="graph name">graph names</a>
+    <a title="RDF source" href="#dfn-rdf-source" class="internalDFN">RDF sources</a>. It is common to have the
+    <a href="#dfn-default-graph" class="internalDFN">default graph</a> contain <a title="RDF triple" href="#dfn-rdf-triple" class="internalDFN">triples</a>
+    that involve the <a title="graph name" href="#dfn-graph-name" class="internalDFN">graph names</a>
     of the other graphs in the dataset.</p>
-</section>
+</div>
 
 
-<section id="entailment">
-    <h3>Equivalence, Entailment and Inconsistency</h3>
+<div id="entailment" typeof="bibo:Chapter" resource="#entailment" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.7 </span>Equivalence, Entailment and Inconsistency</h3>
 
     <p class="issue">No Editor's Draft of <em>RDF 1.1 Semantics</em> is
     available yet
     (<a href="https://www.w3.org/2011/rdf-wg/track/actions/214">ACTION-214</a>),
     and its relationship to this document is not yet
     entirely clear. Some Semantics-related material may be moved here,
-    in particular the definition of <dfn title="merge">graph merge</dfn> and
-    <dfn>subgraph</dfn></li>, and informative
+    in particular the definition of <dfn title="merge" id="dfn-merge">graph merge</dfn> and
+    <dfn id="dfn-subgraph">subgraph</dfn>, and informative
     <a href="http://www.w3.org/TR/rdf-mt/#rules">entailment rules</a>
     for the entailments over the RDF data model
     (excluding any specific vocabulary). This is
@@ -438,192 +808,194 @@
     <a href="http://www.w3.org/2011/rdf-wg/track/actions/209">ACTION-209</a>.
     </p>
 
-    <p>An <a>RDF triple</a> encodes a <a title="RDF statement">statement</a>—a
-    simple <dfn>logical expression</dfn>, or claim about the world.
-    An <a>RDF graph</a> is the conjunction (logical <em>AND</em>) of
-    its triples, and the conjunction of two RDF graphs is their <a>merge</a>.
+    <p>An <a href="#dfn-rdf-triple" class="internalDFN">RDF triple</a> encodes a <a title="RDF statement" href="#dfn-rdf-statement" class="internalDFN">statement</a>—a
+    simple <dfn id="dfn-logical-expression">logical expression</dfn>, or claim about the world.
+    An <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> is the conjunction (logical <em>AND</em>) of
+    its triples, and the conjunction of two RDF graphs is their <a href="#dfn-merge" class="internalDFN">merge</a>.
     This treatment of RDF graphs as logical expressions is
     normatively defined in the
     <a href="http://www.w3.org/TR/rdf-mt/">RDF Semantics</a>
-    specification [[RDF-MT]], using a model-theoretic semantics.
+    specification [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>], using a model-theoretic semantics.
     It yields various relationships between RDF graphs:</p>
 
     <dl>
-    <dt><dfn>Entailment</dfn></dt>
-    <dd>An <a>RDF graph</a> <em>A</em> entails another RDF graph <em>B</em>
+    <dt><dfn id="dfn-entailment">Entailment</dfn></dt>
+    <dd>An <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> <em>A</em> entails another RDF graph <em>B</em>
     if every possible arrangement of the world
     that makes <em>A</em> true also makes <em>B</em> true. When <em>A</em>
     entails <em>B</em>, if the truth of <em>A</em> is presumed or demonstrated
     then the truth of <em>B</em> is established.</dd>
 
-    <dt><dfn>Equivalence</dfn></dt>
-    <dd>Two <a title="RDF graph">RDF graphs</a> <em>A</em> and <em>B</em>
+    <dt><dfn id="dfn-equivalence">Equivalence</dfn></dt>
+    <dd>Two <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a> <em>A</em> and <em>B</em>
     are equivalent if they make the same claim about the world.
     <em>A</em> is equivalent to <em>B</em> if and only if
-    <em>A</em> <a title="entailment">entails</a> <em>B</em> and
+    <em>A</em> <a title="entailment" href="#dfn-entailment" class="internalDFN">entails</a> <em>B</em> and
     <em>B</em> entails <em>A</em>.</dd>
 
-    <dt><dfn>Inconsistency</dfn></dt>
-    <dd>An <a>RDF graph</a> is inconsistent if it contains
+    <dt><dfn id="dfn-inconsistency">Inconsistency</dfn></dt>
+    <dd>An <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> is inconsistent if it contains
     an internal contradiction. There is no possible arrangement
     of the world that would make the expression true.</dd>
     </dl>
 
-    <p>An <dfn>entailment regime</dfn> [[RDF-MT]] is a specification that
+    <p>An <dfn id="dfn-entailment-regime">entailment regime</dfn> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>] is a specification that
     defines precise conditions that make these relationships hold. 
     RDF itself recognizes only some basic cases of entailment, equivalence
     and inconsistency. Other specifications, such as
-    <a href="http://www.w3.org/TR/rdf-schema/">RDF Schema</a> [[RDF-SCHEMA]]
+    <a href="http://www.w3.org/TR/rdf-schema/">RDF Schema</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]
     and <a href="http://www.w3.org/TR/owl2-overview/">OWL 2</a>
-    [[OWL2-OVERVIEW]], add more powerful entailment regimes,
-    as do some domain-specific <a title="RDF vocabulary">vocabularies</a>.
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-OVERVIEW">OWL2-OVERVIEW</a></cite>], add more powerful entailment regimes,
+    as do some domain-specific <a title="RDF vocabulary" href="#dfn-rdf-vocabulary" class="internalDFN">vocabularies</a>.
     Some entailment regimes are defined with respect to a
-    <a>datatype map</a>.</p>
+    <a href="#dfn-datatype-map" class="internalDFN">datatype map</a>.</p>
 
     <p>This specification does not constrain how implementations
     use the logical relationships defined by 
-    <a title="entailment regime">entailment regimes</a>.
+    <a title="entailment regime" href="#dfn-entailment-regime" class="internalDFN">entailment regimes</a>.
     Implementations may or may not detect
-    <a title="inconsistency">inconsistencies</a>, and may make all,
-    some or no <a title="entailment">entailed</a> information
+    <a title="inconsistency" href="#dfn-inconsistency" class="internalDFN">inconsistencies</a>, and may make all,
+    some or no <a title="entailment" href="#dfn-entailment" class="internalDFN">entailed</a> information
     available to users.</p>
-</section>
+</div>
 
 
-<section id="rdf-documents">
-    <h2>RDF Documents and Syntaxes</h2>
+<div id="rdf-documents" typeof="bibo:Chapter" resource="#rdf-documents" rel="bibo:chapter" class="section">
+    <h3><span class="secno">1.8 </span>RDF Documents and Syntaxes</h3>
 
-    <p>An <dfn>RDF document</dfn> is a document that encodes an
-    <a>RDF graph</a> or <a>RDF dataset</a> in a <dfn>concrete RDF syntax</dfn>,
-    such as Turtle [[TURTLE-TR]], RDFa [[RDFA-PRIMER]],
-    RDF/XML [[RDF-SYNTAX-GRAMMAR]], or N-Triples [[N-TRIPLES]].  
+    <p>An <dfn id="dfn-rdf-document">RDF document</dfn> is a document that encodes an
+    <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> or <a href="#dfn-rdf-dataset" class="internalDFN">RDF dataset</a> in a <dfn id="dfn-concrete-rdf-syntax">concrete RDF syntax</dfn>,
+    such as Turtle [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>], RDFa [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-PRIMER">RDFA-PRIMER</a></cite>],
+    RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>], or N-Triples [<cite><a class="bibref" rel="biblioentry" href="#bib-N-TRIPLES">N-TRIPLES</a></cite>].  
     RDF documents enable the exchange of RDF graphs and RDF datasets
     between systems.</p>
 
-    <p>A <a>concrete RDF syntax<a> may offer
-    many different ways to encode the same <a>RDF graph</a> or
-    <a>RDF dataset</a>, for example through the use of
-    <a title="namespace prefix">namespace prefixes</a>,
-    relative IRIs, <a title="blank node identifier">blank node identifiers</a>,
+    <p>A <a href="#dfn-concrete-rdf-syntax" class="internalDFN">concrete RDF syntax</a><a> may offer
+    many different ways to encode the same </a><a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> or
+    <a href="#dfn-rdf-dataset" class="internalDFN">RDF dataset</a>, for example through the use of
+    <a title="namespace prefix" href="#dfn-namespace-prefix" class="internalDFN">namespace prefixes</a>,
+    relative IRIs, <a title="blank node identifier" href="#dfn-blank-node-identifier" class="internalDFN">blank node identifiers</a>,
     and different ordering of statements. While these aspects can have great
-    effect on the convenience of working with the <a>RDF document</a>,
+    effect on the convenience of working with the <a href="#dfn-rdf-document" class="internalDFN">RDF document</a>,
     they are not significant for its meaning.</p>
-</section>
+</div>
 
 
-</section>
+</div>
 
 
-<section id="conformance">
+<div id="conformance" typeof="bibo:Chapter" resource="#conformance" rel="bibo:chapter" class="section"><h2><span class="secno">2 </span>Conformance</h2><p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
+<p>The key words <em class="rfc2119" title="must">must</em>, <em class="rfc2119" title="must not">must not</em>, <em class="rfc2119" title="required">required</em>, <em class="rfc2119" title="should">should</em>, <em class="rfc2119" title="should not">should not</em>, <em class="rfc2119" title="recommended">recommended</em>, <em class="rfc2119" title="may">may</em>, and <em class="rfc2119" title="optional">optional</em> in this specification are to be interpreted as described in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a></cite>].</p>
+
     <p>This specification, <em>RDF 1.1 Concepts and Abstract Syntax</em>,
     defines a data model and related terminology for use in
     other specifications, such as
-    <a title="concrete RDF syntax">concrete RDF syntaxes</a>,
+    <a title="concrete RDF syntax" href="#dfn-concrete-rdf-syntax" class="internalDFN">concrete RDF syntaxes</a>,
     API specifications, and query languages.
     Implementations cannot directly conform to
     <em>RDF 1.1 Concepts and Abstract Syntax</em>,
     but can conform to such other specifications that normatively
     reference terms defined here.</p>
-</section>
-
-
-<section id="section-rdf-graph">
-    <h2>RDF Graphs</h2>
-
-    <p>An <dfn>RDF graph</dfn> is a set of
-    <a title="RDF triple">RDF triples</a>.</p>
+</div>
 
 
-<section id="section-triples">
-    <h3>Triples</h3>
+<div id="section-rdf-graph" typeof="bibo:Chapter" resource="#section-rdf-graph" rel="bibo:chapter" class="section">
+    <h2><span class="secno">3 </span>RDF Graphs</h2>
 
-    <p>An <dfn>RDF triple</dfn> consists of three components:</p>
+    <p>An <dfn id="dfn-rdf-graph">RDF graph</dfn> is a set of
+    <a title="RDF triple" href="#dfn-rdf-triple" class="internalDFN">RDF triples</a>.</p>
+
+
+<div id="section-triples" typeof="bibo:Chapter" resource="#section-triples" rel="bibo:chapter" class="section">
+    <h3><span class="secno">3.1 </span>Triples</h3>
+
+    <p>An <dfn id="dfn-rdf-triple">RDF triple</dfn> consists of three components:</p>
 
     <ul>
-      <li>the <dfn>subject</dfn>, which is an
-      <a>IRI</a> or a <a>blank node</a></li>
+      <li>the <dfn id="dfn-subject">subject</dfn>, which is an
+      <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> or a <a href="#dfn-blank-node" class="internalDFN">blank node</a></li>
 
-      <li>the <dfn>predicate</dfn>, which is an <a>IRI</a></li>
+      <li>the <dfn id="dfn-predicate">predicate</dfn>, which is an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a></li>
 
-      <li>the <dfn>object</dfn>, which is an <a>IRI</a>,
-      a <a>literal</a> or a <a>blank node</a></li>
+      <li>the <dfn id="dfn-object">object</dfn>, which is an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a>,
+      a <a href="#dfn-literal" class="internalDFN">literal</a> or a <a href="#dfn-blank-node" class="internalDFN">blank node</a></li>
     </ul>
 
     <p>An RDF triple is conventionally written in the order subject,
     predicate, object.</p>
     
-    <p>The set of <dfn title="node">nodes</dfn> of an <a>RDF graph</a>
+    <p>The set of <dfn title="node" id="dfn-node">nodes</dfn> of an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>
     is the set of subjects and objects of triples in the graph.
-    It is possible for a predicate IRI to also occur as a node in
+    It is possible for a predicate <acronym title="Internationalized Resource Identifier">IRI</acronym> to also occur as a node in
     the same graph.</p>
 
-    <p><a title="IRI">IRIs</a>, <a title="literal">literals</a> and
-    <a title="blank node">blank nodes</a> are collectively known as
-    <dfn title="RDF term">RDF terms</dfn>.</p>
+    <p><a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>, <a title="literal" href="#dfn-literal" class="internalDFN">literals</a> and
+    <a title="blank node" href="#dfn-blank-node" class="internalDFN">blank nodes</a> are collectively known as
+    <dfn title="RDF term" id="dfn-rdf-term">RDF terms</dfn>.</p>
 
-    <p class="note"><a title="IRI">IRIs</a>, <a title="literal">literals</a>
-    and <a title="blank node">blank nodes</a> are distinct and distinguishable.
+    <p class="note"><a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>, <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>
+    and <a title="blank node" href="#dfn-blank-node" class="internalDFN">blank nodes</a> are distinct and distinguishable.
     For example, <code>http://example.org/</code> as a string literal
-    is not equal to <code>http://example.org/</code> as an IRI,
-    nor to a blank node with the <a>blank node identifier</a>
+    is not equal to <code>http://example.org/</code> as an <acronym title="Internationalized Resource Identifier">IRI</acronym>,
+    nor to a blank node with the <a href="#dfn-blank-node-identifier" class="internalDFN">blank node identifier</a>
     <code>http://example.org/</code>.</p>
-</section>
+</div>
 
 
-<section id="section-IRIs">
-    <h3>IRIs</h3>
+<div id="section-IRIs" typeof="bibo:Chapter" resource="#section-IRIs" rel="bibo:chapter" class="section">
+    <h3><span class="secno">3.2 </span>IRIs</h3>
 
-    <p>An <dfn title="IRI"><acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>
+    <p>An <dfn title="IRI" id="dfn-iri"><acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>
     (Internationalized Resource Identifier) within an RDF graph
-    is a Unicode string [[!UNICODE]] that conforms to the syntax
-    defined in RFC 3987 [[!RFC3987]].</p>
+    is a Unicode string [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] that conforms to the syntax
+    defined in RFC 3987 [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>].</p>
 
-    <p>IRIs in the RDF abstract syntax MUST be absolute, and MAY
+    <p>IRIs in the RDF abstract syntax <em class="rfc2119" title="must">must</em> be absolute, and <em class="rfc2119" title="may">may</em>
     contain a fragment identifier.</p>
 
-    <p><dfn>IRI equality</dfn>:
+    <p><dfn id="dfn-iri-equality"><acronym title="Internationalized Resource Identifier">IRI</acronym> equality</dfn>:
     Two IRIs are equal if and only if they are equivalent
     under Simple String Comparison according to
     <a href="http://tools.ietf.org/html/rfc3987#section-5.1">section 5.1</a>
-    of [[!RFC3987]]. Further normalization MUST NOT be performed when
+    of [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>]. Further normalization <em class="rfc2119" title="must not">must not</em> be performed when
     comparing IRIs for equality.</p>
 
     <div class="note" id="note-iris">
     <p><strong>URIs and IRIs:</strong>
     IRIs are a generalization of
-    <dfn title="URI"><acronym title="Uniform Resource Identifier">URI</acronym>s</dfn> [[RFC3986]] that permits a much wider range of Unicode characters.
-    Every absolute URI and URL is an IRI, but not every IRI is an URI.
+    <dfn title="URI" id="dfn-uri"><acronym title="Uniform Resource Identifier">URI</acronym>s</dfn> [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3986">RFC3986</a></cite>] that permits a much wider range of Unicode characters.
+    Every absolute <acronym title="Uniform Resource Identifier">URI</acronym> and URL is an <acronym title="Internationalized Resource Identifier">IRI</acronym>, but not every <acronym title="Internationalized Resource Identifier">IRI</acronym> is an <acronym title="Uniform Resource Identifier">URI</acronym>.
     When IRIs are used in operations that are only
     defined for URIs, they must first be converted according to
     the mapping defined in
     <a href="http://tools.ietf.org/html/rfc3987#section-3.1">section 3.1</a>
-    of [[!RFC3987]]. A notable example is retrieval over the HTTP
+    of [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>]. A notable example is retrieval over the HTTP
     protocol. The mapping involves UTF-8 encoding of non-ASCII
     characters, %-encoding of octets not allowed in URIs, and
     Punycode-encoding of domain names.</p>
 
     <p><strong>Relative IRIs:</strong>
-    Some <a title="concrete RDF syntax">concrete RDF syntaxes</a> permit
-    <dfn title="relative IRI">relative IRIs</dfn> as a convenient shorthand
+    Some <a title="concrete RDF syntax" href="#dfn-concrete-rdf-syntax" class="internalDFN">concrete RDF syntaxes</a> permit
+    <dfn title="relative IRI" id="dfn-relative-iri">relative IRIs</dfn> as a convenient shorthand
     that allows authoring of documents independently from their final
     publishing location. Relative IRIs must be
     <a href="http://tools.ietf.org/html/rfc3986#section-5.2">resolved
-    against</a> a <dfn>base IRI</dfn> to make them absolute.
+    against</a> a <dfn id="dfn-base-iri">base <acronym title="Internationalized Resource Identifier">IRI</acronym></dfn> to make them absolute.
     Therefore, the RDF graph serialized in such syntaxes is well-defined only
-    if a <a href="http://tools.ietf.org/html/rfc3986#section-5.1">base IRI
-    can be established</a> [[RFC3986]].</p>
+    if a <a href="http://tools.ietf.org/html/rfc3986#section-5.1">base <acronym title="Internationalized Resource Identifier">IRI</acronym>
+    can be established</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3986">RFC3986</a></cite>].</p>
 
-      <p><strong>IRI normalization:</strong>
+      <p><strong><acronym title="Internationalized Resource Identifier">IRI</acronym> normalization:</strong>
       Interoperability problems can be avoided by minting
       only IRIs that are normalized according to
       <a href="http://tools.ietf.org/html/rfc3987#section-5">Section 5</a>
-      of [[!RFC3987]]. Non-normalized forms that are best avoided
+      of [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>]. Non-normalized forms that are best avoided
       include:</p>
 
       <ul>
         <li>Uppercase characters in scheme names and domain names</li>
         <li>Percent-encoding of characters where it is not
-          required by IRI syntax</li>
+          required by <acronym title="Internationalized Resource Identifier">IRI</acronym> syntax</li>
         <li>Explicitly stated HTTP default port
           (<code>http://example.com:80/</code>);
           <code>http://example.com/</code> is preferrable</li>
@@ -631,66 +1003,66 @@
           (<code>http://example.com</code>);
           <code>http://example.com/</code> is preferrable</li>
         <li>“<code>/./</code>” or “<code>/../</code>” in the path
-          component of an IRI</li>
+          component of an <acronym title="Internationalized Resource Identifier">IRI</acronym></li>
         <li>Lowercase hexadecimal letters within percent-encoding
           triplets (“<code>%3F</code>” is preferable over
           “<code>%3f</code>”)</li>
         <li>Punycode-encoding of Internationalized Domain Names
           in IRIs</li>
         <li>IRIs that are not in Unicode Normalization
-          Form C [[!NFC]]</li>
+          Form C [<cite><a class="bibref" rel="biblioentry" href="#bib-NFC">NFC</a></cite>]</li>
       </ul>
     </div>
-</section>
+</div>
 
 
-<section id="section-Graph-Literal">
-    <h2>Literals</h2>
+<div id="section-Graph-Literal" typeof="bibo:Chapter" resource="#section-Graph-Literal" rel="bibo:chapter" class="section">
+    <h3><span class="secno">3.3 </span>Literals</h3>
 
     <p>Literals are used to denote values such as strings, numbers and dates
     by means of a lexical representation.</p>
 
-    <p>A <dfn>literal</dfn> in an <a>RDF graph</a> consists of two or three
+    <p>A <dfn id="dfn-literal">literal</dfn> in an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> consists of two or three
     elements:</p>
 
     <ul>
-    <li>a <dfn>lexical form</dfn>, being a Unicode [[!UNICODE]] string,
-    which SHOULD be in Normal Form C [[!NFC]],</li>
-    <li>a <dfn>datatype IRI</dfn>, being an <a>IRI</a> that determines
-    how the lexical form maps to a <a>literal value</a>.</li>
+    <li>a <dfn id="dfn-lexical-form">lexical form</dfn>, being a Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] string,
+    which <em class="rfc2119" title="should">should</em> be in Normal Form C [<cite><a class="bibref" rel="biblioentry" href="#bib-NFC">NFC</a></cite>],</li>
+    <li>a <dfn id="dfn-datatype-iri">datatype <acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>, being an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> that determines
+    how the lexical form maps to a <a href="#dfn-literal-value" class="internalDFN">literal value</a>.</li>
     </ul>
 
-    <p>A literal is a <dfn>language-tagged string</dfn> if and only if its
-    <a>datatype IRI</a> is
+    <p>A literal is a <dfn id="dfn-language-tagged-string">language-tagged string</dfn> if and only if its
+    <a href="#dfn-datatype-iri" class="internalDFN">datatype <acronym title="Internationalized Resource Identifier">IRI</acronym></a> is
     <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#langString</code>,
     and only in this case the third element is present:</p>
 
     <ul>
-    <li>a non-empty <dfn>language tag</dfn> as defined by [[!BCP47]].
-    The language tag MUST be well-formed according to
+    <li>a non-empty <dfn id="dfn-language-tag">language tag</dfn> as defined by [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>].
+    The language tag <em class="rfc2119" title="must">must</em> be well-formed according to
     <a href="http://tools.ietf.org/html/bcp47#section-2.2.9">section 2.2.9</a>
-    of [[!BCP47]], and MUST be normalized to lowercase.</li>
+    of [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>], and <em class="rfc2119" title="must">must</em> be normalized to lowercase.</li>
     </ul>
 
-    <p>Concrete syntaxes MAY support <dfn title="simple literal">simple
-    literals</dfn>, consisting of only a <a>lexical form</a>
-    without any datatype IRI or language tag. Simple literals only
+    <p>Concrete syntaxes <em class="rfc2119" title="may">may</em> support <dfn title="simple literal" id="dfn-simple-literal">simple
+    literals</dfn>, consisting of only a <a href="#dfn-lexical-form" class="internalDFN">lexical form</a>
+    without any datatype <acronym title="Internationalized Resource Identifier">IRI</acronym> or language tag. Simple literals only
     exist in concrete syntaxes, and are treated as
     syntactic sugar for abstract syntax
-    <a title="literal">literals</a> with the <a>datatype IRI</a>
+    <a title="literal" href="#dfn-literal" class="internalDFN">literals</a> with the <a href="#dfn-datatype-iri" class="internalDFN">datatype <acronym title="Internationalized Resource Identifier">IRI</acronym></a>
     <code>http://www.w3.org/2001/XMLSchema#string</code>.</p>
 
-    <p><dfn>Literal equality</dfn>:
+    <p><dfn id="dfn-literal-equality">Literal equality</dfn>:
     Two literals are equal if and only if the two
-    <a title="lexical form">lexical forms</a>, the two
-    <a title="datatype IRI">datatype IRIs</a>, and the two
-    <a title="language tag">language tags</a> (if any)
+    <a title="lexical form" href="#dfn-lexical-form" class="internalDFN">lexical forms</a>, the two
+    <a title="datatype IRI" href="#dfn-datatype-iri" class="internalDFN">datatype IRIs</a>, and the two
+    <a title="language tag" href="#dfn-language-tag" class="internalDFN">language tags</a> (if any)
     compare equal, character by character.</p>
-</section>
+</div>
 
 
-<section id="section-blank-nodes">
-    <h2>Blank Nodes</h2>
+<div id="section-blank-nodes" typeof="bibo:Chapter" resource="#section-blank-nodes" rel="bibo:chapter" class="section">
+    <h3><span class="secno">3.4 </span>Blank Nodes</h3>
 
     <p class="issue">Various proposals have been made for revising
     this section, ranging from editorial re-wordings to major re-writes
@@ -698,10 +1070,10 @@
     and define the concept of a “fresh” blank node. This is
     <a href="https://www.w3.org/2011/rdf-wg/track/issues/107">ISSUE-107</a>.</p>
 
-    <p>The <dfn title="blank node">blank nodes</dfn> in an RDF graph 
+    <p>The <dfn title="blank node" id="dfn-blank-node">blank nodes</dfn> in an RDF graph 
     are drawn from an infinite set. This set is disjoint from the set
-    of all <a title="IRI">IRIs</a> and the set of all
-    <a title="literal">literals</a>.
+    of all <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> and the set of all
+    <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>.
     Otherwise, this set of blank nodes is arbitrary.</p>
 
     <p>Given two blank nodes, it is 
@@ -710,9 +1082,9 @@
     of blank nodes.</p>
 
     <p class="note" id="note-bnode-id">
-    <dfn title="blank node identifier">Blank node identifiers</dfn>
+    <dfn title="blank node identifier" id="dfn-blank-node-identifier">Blank node identifiers</dfn>
     are local identifiers that are used in some
-    <a title="concrete RDF syntax">concrete RDF syntaxes</a>
+    <a title="concrete RDF syntax" href="#dfn-concrete-rdf-syntax" class="internalDFN">concrete RDF syntaxes</a>
     or RDF store implementations.
     They are always locally scoped to the file or RDF store,
     and are <em>not</em> persistent or portable identifiers
@@ -721,22 +1093,22 @@
     on the concrete syntax or implementation. The syntactic restrictions
     on blank node identifiers, if any, therefore also depend on
     the concrete RDF syntax or implementation.</p>
-</section>
+</div>
 
 
-<section id="section-skolemization">
-    <h3>Replacing Blank Nodes with IRIs</h3>
+<div id="section-skolemization" typeof="bibo:Chapter" resource="#section-skolemization" rel="bibo:chapter" class="section">
+    <h3><span class="secno">3.5 </span>Replacing Blank Nodes with IRIs</h3>
 
     <p>Blank nodes do not have identifiers in the RDF abstract syntax. The
-    <a title="blank node identifier">blank node identifiers</a> introduced
+    <a title="blank node identifier" href="#dfn-blank-node-identifier" class="internalDFN">blank node identifiers</a> introduced
     by some concrete syntaxes have only
     local scope and are purely an artifact of the serialization.</p>
 
-    <p>In situations where stronger identification is needed, systems MAY
+    <p>In situations where stronger identification is needed, systems <em class="rfc2119" title="may">may</em>
     systematically replace some or all of the blank nodes in an RDF graph
-    with <a title="IRI">IRIs</a>.  Systems wishing to do this SHOULD
-    <a title="minting">mint</a> a new, globally
-    unique IRI (a <dfn>Skolem IRI</dfn>) for each blank node so replaced.</p>
+    with <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>.  Systems wishing to do this <em class="rfc2119" title="should">should</em>
+    <a title="minting" href="#dfn-minting" class="internalDFN">mint</a> a new, globally
+    unique <acronym title="Internationalized Resource Identifier">IRI</acronym> (a <dfn id="dfn-skolem-iri">Skolem <acronym title="Internationalized Resource Identifier">IRI</acronym></dfn>) for each blank node so replaced.</p>
 
     <p>This transformation does not appreciably change the meaning of an
     RDF graph, provided that the Skolem IRIs do not occur anywhere else.
@@ -750,37 +1122,37 @@
     if needed.</p>
 
     <p>Systems that want Skolem IRIs to be recognizable outside of the system
-    boundaries SHOULD use a well-known IRI [[WELL-KNOWN]] with the registered
-    name <code>genid</code>. This is an IRI that uses the HTTP or HTTPS scheme,
+    boundaries <em class="rfc2119" title="should">should</em> use a well-known <acronym title="Internationalized Resource Identifier">IRI</acronym> [<cite><a class="bibref" rel="biblioentry" href="#bib-WELL-KNOWN">WELL-KNOWN</a></cite>] with the registered
+    name <code>genid</code>. This is an <acronym title="Internationalized Resource Identifier">IRI</acronym> that uses the HTTP or HTTPS scheme,
     or another scheme that has been specified to use well-known IRIs; and whose
     path component starts with <code>/.well-known/genid/</code>.
 
-    <p>For example, the authority responsible for the domain
-    <code>example.com</code> could mint the following recognizable Skolem IRI:</p>
+    </p><p>For example, the authority responsible for the domain
+    <code>example.com</code> could mint the following recognizable Skolem <acronym title="Internationalized Resource Identifier">IRI</acronym>:</p>
 
     <pre>http://example.com/.well-known/genid/d26a2d0e98334696f4ad70a677abc1f6</pre>
 
-    <p class="note">RFC 5785 [[WELL-KNOWN]] only specifies well-known URIs,
-    not IRIs. For the purpose of this document, a well-known IRI is any
-    IRI that results in a well-known URI after IRI-to-URI mapping [[!RFC3987]].</p>
-</section>
+    <p class="note">RFC 5785 [<cite><a class="bibref" rel="biblioentry" href="#bib-WELL-KNOWN">WELL-KNOWN</a></cite>] only specifies well-known URIs,
+    not IRIs. For the purpose of this document, a well-known <acronym title="Internationalized Resource Identifier">IRI</acronym> is any
+    <acronym title="Internationalized Resource Identifier">IRI</acronym> that results in a well-known <acronym title="Uniform Resource Identifier">URI</acronym> after <acronym title="Internationalized Resource Identifier">IRI</acronym>-to-<acronym title="Uniform Resource Identifier">URI</acronym> mapping [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>].</p>
+</div>
 
 
-<section id="graph-isomorphism">
-    <h3>Graph Isomorphism</h3>
+<div id="graph-isomorphism" typeof="bibo:Chapter" resource="#graph-isomorphism" rel="bibo:chapter" class="section">
+    <h3><span class="secno">3.6 </span>Graph Isomorphism</h3>
 
     <p id="section-graph-equality">Two
-    <a title="RDF graph">RDF graphs</a> <var>G</var> and <var>G'</var> are
-    <dfn title="graph isomorphism">isomorphic</dfn> if there
+    <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a> <var>G</var> and <var>G'</var> are
+    <dfn title="graph isomorphism" id="dfn-graph-isomorphism">isomorphic</dfn> if there
     is a bijection <var>M</var> between the sets of nodes of the two graphs,
     such that:</p>
 
     <ol>
       <li><var>M</var> maps blank nodes to blank nodes.</li>
-      <li><var>M(lit)=lit</var> for all <a title="literal">RDF literals</a> <var>lit</var> which
+      <li><var>M(lit)=lit</var> for all <a title="literal" href="#dfn-literal" class="internalDFN">RDF literals</a> <var>lit</var> which
       are nodes of <var>G</var>.</li>
 
-      <li><var>M(uri)=uri</var> for all <a title="IRI">IRIs</a> <var>uri</var>
+      <li><var>M(uri)=uri</var> for all <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> <var>uri</var>
       which are nodes of <var>G</var>.</li>
 
       <li>The triple <var>( s, p, o )</var> is in <var>G</var> if and
@@ -788,45 +1160,45 @@
       <var>G'</var></li>
     </ol>
 
-    <p>See also: <a>IRI equality</a>, <a>literal equality</a>.</p>
+    <p>See also: <a href="#dfn-iri-equality" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym> equality</a>, <a href="#dfn-literal-equality" class="internalDFN">literal equality</a>.</p>
 
     <p>With this definition, <var>M</var> shows how each blank node 
     in <var>G</var> can be replaced with
     a new blank node to give <var>G'</var>. Graph isomorphism
-    is needed to support the RDF Test Cases [[RDF-TESTCASES]] specification.</p>
-</section>
+    is needed to support the RDF Test Cases [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-TESTCASES">RDF-TESTCASES</a></cite>] specification.</p>
+</div>
 
-</section>
+</div>
 
 
-<section id="section-dataset">
-    <h2>RDF Datasets</h2>
+<div id="section-dataset" typeof="bibo:Chapter" resource="#section-dataset" rel="bibo:chapter" class="section">
+    <h2><span class="secno">4 </span>RDF Datasets</h2>
 
-    <p>An <dfn>RDF Dataset</dfn> is a collection of
-    <a title="RDF graph">RDF graphs</a>, and comprises:</p>
+    <p>An <dfn id="dfn-rdf-dataset">RDF Dataset</dfn> is a collection of
+    <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>, and comprises:</p>
 
     <ul>
-    <li>Exactly one <dfn>default graph</dfn>, being an <a>RDF graph</a>.
-    The default graph does not have a name and MAY be empty.</li>
-    <li>Zero or more <dfn title="named graph">named graphs</dfn>.
-    Each named graph is a pair consisting of an <a>IRI</a>
-    (the <dfn>graph name</dfn>), and an <a>RDF graph</a>.
+    <li>Exactly one <dfn id="dfn-default-graph">default graph</dfn>, being an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>.
+    The default graph does not have a name and <em class="rfc2119" title="may">may</em> be empty.</li>
+    <li>Zero or more <dfn title="named graph" id="dfn-named-graph">named graphs</dfn>.
+    Each named graph is a pair consisting of an <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a>
+    (the <dfn id="dfn-graph-name">graph name</dfn>), and an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>.
     Graph names are unique within an RDF dataset.</li>
     </ul>
 
-    <p><a title="blank node">Blank nodes</a> MAY be shared between graphs
-    in an <a>RDF dataset</a>.</p>
+    <p><a title="blank node" href="#dfn-blank-node" class="internalDFN">Blank nodes</a> <em class="rfc2119" title="may">may</em> be shared between graphs
+    in an <a href="#dfn-rdf-dataset" class="internalDFN">RDF dataset</a>.</p>
 
     <div class="note" id="note-datasets">
     <p>Despite the use of the word “name”
-    in “<a>named graph</a>”, the <a>graph name</a> does not formally
-    <a>denote</a> the graph. It is merely syntactically paired with
+    in “<a href="#dfn-named-graph" class="internalDFN">named graph</a>”, the <a href="#dfn-graph-name" class="internalDFN">graph name</a> does not formally
+    <a href="#dfn-denote" class="internalDFN">denote</a> the graph. It is merely syntactically paired with
     the graph. RDF does not place any formal restrictions on what
-    <a>resource</a> the graph name may denote, nor on the relationship between
+    <a href="#dfn-resource" class="internalDFN">resource</a> the graph name may denote, nor on the relationship between
     that resource and the graph.</p>
 
-    <p>Some <a>RDF dataset</a>
-    implementations do not track empty <a title="named graph">named graphs</a>.
+    <p>Some <a href="#dfn-rdf-dataset" class="internalDFN">RDF dataset</a>
+    implementations do not track empty <a title="named graph" href="#dfn-named-graph" class="internalDFN">named graphs</a>.
     Applications can avoid interoperability issues by not
     ascribing importance to the presence or absence of empty named graphs.</p>
     </div>
@@ -835,49 +1207,49 @@
     such as merge, union, isomorphism, equality, equivalence? Is anything
     needed to support the TriG test cases, SPARQL, etc.? This is
     <a href="https://www.w3.org/2011/rdf-wg/track/issues/111">ISSUE-111</a>.</p>
-</section>
+</div>
 
 
-<section id="section-Datatypes">
-    <h2>Datatypes</h2>
+<div id="section-Datatypes" typeof="bibo:Chapter" resource="#section-Datatypes" rel="bibo:chapter" class="section">
+    <h2><span class="secno">5 </span>Datatypes</h2>
 
-    <p>Datatypes are used with RDF <a title="literal">literals</a>
+    <p>Datatypes are used with RDF <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>
     to represent values such as strings, numbers and dates.
     The datatype abstraction used in RDF is compatible with XML Schema
-    [[!XMLSCHEMA11-2]]. Any datatype definition that conforms
-    to this abstraction MAY be used in RDF, even if not defined
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]. Any datatype definition that conforms
+    to this abstraction <em class="rfc2119" title="may">may</em> be used in RDF, even if not defined
     in terms of XML Schema. RDF re-uses many of the XML Schema
     built-in datatypes,
     and provides two additional built-in datatypes,
-    <code><a>rdf:HTML</a></code> and <code><a>rdf:XMLLiteral</a></code>.
+    <code><a href="#dfn-rdf-html" class="internalDFN">rdf:HTML</a></code> and <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code>.
     The list of datatypes supported by an implementation is determined
-    by its <a>datatype map</a>.</p>
+    by its <a href="#dfn-datatype-map" class="internalDFN">datatype map</a>.</p>
 
-    <p>A <dfn>datatype</dfn> consists of a <a>lexical space</a>,
-    a <a>value space</a> and a <a>lexical-to-value mapping</a>, and
-    is denoted by one or more <a title="IRI">IRIs</a>.</p>
+    <p>A <dfn id="dfn-datatype">datatype</dfn> consists of a <a href="#dfn-lexical-space" class="internalDFN">lexical space</a>,
+    a <a href="#dfn-value-space" class="internalDFN">value space</a> and a <a href="#dfn-lexical-to-value-mapping" class="internalDFN">lexical-to-value mapping</a>, and
+    is denoted by one or more <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>.</p>
 
-<p>The <dfn>lexical space</dfn> of a datatype is a set of Unicode [[!UNICODE]] strings.</p>
+<p>The <dfn id="dfn-lexical-space">lexical space</dfn> of a datatype is a set of Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] strings.</p>
 
-    <p>The <dfn>lexical-to-value mapping</dfn> of a datatype is a set of
-    pairs whose first element belongs to the <a>lexical space</a>,
-    and the second element belongs to the <dfn>value space</dfn>
+    <p>The <dfn id="dfn-lexical-to-value-mapping">lexical-to-value mapping</dfn> of a datatype is a set of
+    pairs whose first element belongs to the <a href="#dfn-lexical-space" class="internalDFN">lexical space</a>,
+    and the second element belongs to the <dfn id="dfn-value-space">value space</dfn>
     of the datatype. Each member of the lexical space is paired with exactly
     one value, and is a <em>lexical representation</em>
     of that value. The mapping can be seen as a function
     from the lexical space to the value space.</p>
 
-    <p class="note"><a title="language-tagged string">Language-tagged
-    strings</a> have the <a>datatype IRI</a>
+    <p class="note"><a title="language-tagged string" href="#dfn-language-tagged-string" class="internalDFN">Language-tagged
+    strings</a> have the <a href="#dfn-datatype-iri" class="internalDFN">datatype <acronym title="Internationalized Resource Identifier">IRI</acronym></a>
     <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#langString</code>.
-    No datatype is formally defined for this IRI because the definition
-    of <a title="datatype">datatypes</a> does not accommodate
-    <a title="language tag">language tags</a> in the <a>lexical space</a>.
-    The <a>value space</a> associated with this datatype IRI is the set
+    No datatype is formally defined for this <acronym title="Internationalized Resource Identifier">IRI</acronym> because the definition
+    of <a title="datatype" href="#dfn-datatype" class="internalDFN">datatypes</a> does not accommodate
+    <a title="language tag" href="#dfn-language-tag" class="internalDFN">language tags</a> in the <a href="#dfn-lexical-space" class="internalDFN">lexical space</a>.
+    The <a href="#dfn-value-space" class="internalDFN">value space</a> associated with this datatype <acronym title="Internationalized Resource Identifier">IRI</acronym> is the set
     of all pairs of strings and language tags.</p>
 
     <p>For example, the XML Schema datatype <code>xsd:boolean</code>,
-    where each member of the <a>value space</a> has two lexical
+    where each member of the <a href="#dfn-value-space" class="internalDFN">value space</a> has two lexical
     representations, is defined as follows:</p>
 
     <dl>
@@ -894,11 +1266,11 @@
         }</dd>
     </dl>
 
-    <p>The <a title="literal">literals</a> that can be defined using this
+    <p>The <a title="literal" href="#dfn-literal" class="internalDFN">literals</a> that can be defined using this
     datatype are:</p>
 
     <table rules="all" summary="This table lists the literals of type xsd:boolean.">
-      <tr>
+      <tbody><tr>
         <th>Literal</th>
         <th>Value</th>
       </tr>
@@ -918,23 +1290,23 @@
         <td align="center">&lt;“<code>0</code>”, <code>xsd:boolean</code>&gt;</td>
         <td align="center"><em><strong>false</strong></em></td>
       </tr>
-    </table>
+    </tbody></table>
 
 
-<section id="xsd-datatypes">
-    <h3>The XML Schema Built-in Datatypes</h3>
+<div id="xsd-datatypes" typeof="bibo:Chapter" resource="#xsd-datatypes" rel="bibo:chapter" class="section">
+    <h3><span class="secno">5.1 </span>The XML Schema Built-in Datatypes</h3>
 
-    <p><a title="IRI">IRIs</a> of the form
+    <p><a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a> of the form
     <code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
     where <code><em>xxx</em></code>
     is the name of a datatype, denote the built-in datatypes defined in
     <em><a href="http://www.w3.org/TR/xmlschema11-2/">XML Schema 1.1 Part 2:
-    Datatypes</a></em> [[!XMLSCHEMA11-2]]. The XML Schema built-in types
+    Datatypes</a></em> [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]. The XML Schema built-in types
     listed in the following table are the
-    <dfn>RDF-compatible XSD types</dfn>. Their use is RECOMMENDED.</p>
+    <dfn id="dfn-rdf-compatible-xsd-types">RDF-compatible XSD types</dfn>. Their use is <em class="rfc2119" title="recommended">recommended</em>.</p>
  
     <table rules="all" summary="A list of the RDF-compatible XSD types, with short descriptions">
-    <tr><th></th><th>Datatype</th><th>Value space (informative)</th></tr>
+    <tbody><tr><th></th><th>Datatype</th><th>Value space (informative)</th></tr>
 
     <tr><th rowspan="4">Core types</th><td><a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a></td><td>Character strings</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#boolean"><code>xsd:boolean</code></a></td><td>true, false</td></tr>
@@ -983,16 +1355,16 @@
 
     <tr><th rowspan="7">Miscellaneous<br />XSD types</th>
         <td><a href="http://www.w3.org/TR/xmlschema11-2/#anyURI"><code>xsd:anyURI</code></a></td><td>Absolute or relative URIs and IRIs</td></tr>
-    <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#language"><code>xsd:language</code></a></td><td>Language tags per [[BCP47]]</td></tr>
+    <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#language"><code>xsd:language</code></a></td><td>Language tags per [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>]</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#normalizedString"><code>xsd:normalizedString</code></a></td><td>Whitespace-normalized strings</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#token"><code>xsd:token</code></a></td><td>Tokenized strings</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#NMTOKEN"><code>xsd:NMTOKEN</code></a></td><td>XML NMTOKENs</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#Name"><code>xsd:Name</code></a></td><td>XML Names</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#NCName"><code>xsd:NCName</code></a></td><td>XML NCNames</td></tr>
-    </table>
+    </tbody></table>
 
     <p>The other built-in XML Schema datatypes are unsuitable
-    for various reasons, and SHOULD NOT be used.</p>
+    for various reasons, and <em class="rfc2119" title="should not">should not</em> be used.</p>
 
     <div class="note">
     <ul>
@@ -1010,39 +1382,39 @@
     <a href="http://www.w3.org/TR/xmlschema11-2/#ENTITIES"><code>xsd:ENTITIES</code></a> 
     and
     <a href="http://www.w3.org/TR/xmlschema11-2/#NMTOKENS"><code>xsd:NMTOKENS</code></a> 
-    are sequence-valued datatypes which do not fit the RDF <a>datatype</a>
+    are sequence-valued datatypes which do not fit the RDF <a href="#dfn-datatype" class="internalDFN">datatype</a>
     model.</li>
     </ul>
     </div>
 
-</section>
+</div>
 
 
-<section id="section-html">
-    <h3>The <code>rdf:HTML</code> Datatype</h3>
+<div id="section-html" typeof="bibo:Chapter" resource="#section-html" rel="bibo:chapter" class="section">
+    <h3><span class="secno">5.2 </span>The <code>rdf:HTML</code> Datatype</h3>
 
-    <p>RDF provides for HTML content as a possible <a>literal value</a>.
+    <p>RDF provides for HTML content as a possible <a href="#dfn-literal-value" class="internalDFN">literal value</a>.
     This allows markup in literal values. Such content is indicated
-    in an <a>RDF graph</a> using a <a>literal</a> whose <a>datatype</a>
-    is a special built-in datatype <code><dfn>rdf:HTML</dfn></code>.
+    in an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> using a <a href="#dfn-literal" class="internalDFN">literal</a> whose <a href="#dfn-datatype" class="internalDFN">datatype</a>
+    is a special built-in datatype <code><dfn id="dfn-rdf-html">rdf:HTML</dfn></code>.
     This datatype is defined as follows:</p>
 
     <dl>
-    <dt>An IRI denoting this datatype</dt>
+    <dt>An <acronym title="Internationalized Resource Identifier">IRI</acronym> denoting this datatype</dt>
     <dd>is <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#HTML</code>.</dd>
 
     <dt>The lexical space</dt>
-    <dd>is the set of Unicode [[UNICODE]] strings.</dd>
+    <dd>is the set of Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] strings.</dd>
 
     <dt>The value space</dt>
     <dd>is a set of DOM
     <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
-    nodes [[!DOM4]]. Two
+    nodes [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>]. Two
     <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
     nodes <em>A</em> and <em>B</em> are considered equal if and only if
     the DOM method
     <code><em>A</em>.<a href="http://www.w3.org/TR/dom/#dom-node-isequalnode">isEqualNode</a>(<em>B</em>)</code>
-    [[!DOM4]] returns <code>true</code>.</dd>
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>] returns <code>true</code>.</dd>
 
     <dt>The lexical-to-value mapping</dt>
     <dd>
@@ -1050,13 +1422,13 @@
       of applying the following algorithm:</p>
       <ul>
         <li>Let <code>domnodes</code> be the list of
-        <a href="http://www.w3.org/TR/dom/#node">DOM nodes</a> [[!DOM4]]
+        <a href="http://www.w3.org/TR/dom/#node">DOM nodes</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>]
         that result from applying the
-        <a href="http://www.w3.org/TR/html5/the-end.html#parsing-html-fragments">HTML fragment parsing algorithm</a> [[!HTML5]]
+        <a href="http://www.w3.org/TR/html5/the-end.html#parsing-html-fragments">HTML fragment parsing algorithm</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]
         to the input string, without a context element.</li>
         <li>Let <code>domfrag</code> be a DOM
         <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
-        [[!DOM4]] whose <code>childNodes</code> attribute is equal to
+        [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>] whose <code>childNodes</code> attribute is equal to
         <code>domnodes</code></li>
         <li>Return <code>domfrag.<a href="http://www.w3.org/TR/dom/#dom-node-normalize">normalize</a>()</code></li>
       </ul>
@@ -1064,7 +1436,7 @@
     </dl>
 
     <p class="note" id="note-html">
-    Any language annotation (<code>lang="…"</code>) or
+    Any language annotation (<code>lang=&quot;…&quot;</code>) or
     XML namespaces (<code>xmlns</code>) desired in the HTML content
     must be included explicitly in the HTML literal. Relative URLs
     in attributes such as <code>href</code> do not have a well-defined
@@ -1073,44 +1445,44 @@
     such as that which relates an <code>xsd:string</code> with an
     <code>rdf:HTML</code> literal corresponding to a single text node
     of the same string.</p>
-</section>
+</div>
 
-<section id="section-XMLLiteral">
-    <h3>The <code>rdf:XMLLiteral</code> Datatype</h3>
+<div id="section-XMLLiteral" typeof="bibo:Chapter" resource="#section-XMLLiteral" rel="bibo:chapter" class="section">
+    <h3><span class="secno">5.3 </span>The <code>rdf:XMLLiteral</code> Datatype</h3>
 
-    <p>RDF provides for XML content as a possible <a>literal value</a>.
-    Such content is indicated in an <a>RDF graph</a> using a <a>literal</a>
-    whose <a>datatype</a> is a special built-in datatype
-    <code><dfn>rdf:XMLLiteral</dfn></code>, which is defined as follows:</p>
+    <p>RDF provides for XML content as a possible <a href="#dfn-literal-value" class="internalDFN">literal value</a>.
+    Such content is indicated in an <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> using a <a href="#dfn-literal" class="internalDFN">literal</a>
+    whose <a href="#dfn-datatype" class="internalDFN">datatype</a> is a special built-in datatype
+    <code><dfn id="dfn-rdf-xmlliteral">rdf:XMLLiteral</dfn></code>, which is defined as follows:</p>
    
     <dl>
-      <dt id="XMLLiteral-uri">An IRI denoting
-      this datatype</a></dt>
+      <dt id="XMLLiteral-uri">An <acronym title="Internationalized Resource Identifier">IRI</acronym> denoting
+      this datatype</dt>
 
       <dd>is
       <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>.</dd>
 
-      <dt id="XMLLiteral-lexical-space">The lexical space</a></dt>
+      <dt id="XMLLiteral-lexical-space">The lexical space</dt>
 
       <dd>is the set of all strings which are well-balanced, self-contained 
       <a href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">XML content</a> 
-      [[!XML10]]; and for which embedding between an arbitrary
+      [<cite><a class="bibref" rel="biblioentry" href="#bib-XML10">XML10</a></cite>]; and for which embedding between an arbitrary
       XML start tag and an end tag yields a document conforming to
       <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">XML Namespaces</a>
-      [[!XML-NAMES]].</dd>
+      [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-NAMES">XML-NAMES</a></cite>].</dd>
 
-      <dt id="XMLLiteral-value-space">The value space</a></dt>
+      <dt id="XMLLiteral-value-space">The value space</dt>
 
       <dd>is a set of DOM
       <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
-      nodes [[!DOM4]]. Two
+      nodes [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>]. Two
       <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
       nodes <em>A</em> and <em>B</em> are considered equal
       if and only if the DOM method
       <code><em>A</em>.<a href="http://www.w3.org/TR/dom/#dom-node-isequalnode">isEqualNode</a>(<em>B</em>)</code>
       returns <code>true</code>.</dd>
 
-      <dt id="XMLLiteral-mapping">The lexical-to-value mapping</a></dt>
+      <dt id="XMLLiteral-mapping">The lexical-to-value mapping</dt>
 
       <dd>
       <p>Each member of the lexical space is associated with the result 
@@ -1118,110 +1490,110 @@
       <ul>
       <li>Let <code>domfrag</code> be a DOM
       <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
-      node [[!DOM4]] corresponding to the input string</li>
+      node [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM4">DOM4</a></cite>] corresponding to the input string</li>
       <li>Return <code>domfrag.<a href="http://www.w3.org/TR/dom/#dom-node-normalize">normalize</a>()</code></li>
       </ul></dd>
 
-      <dt id="XMLLiteral-canonical">The canonical mapping</a></dt>
+      <dt id="XMLLiteral-canonical">The canonical mapping</dt>
       <dd>defines a
       <a href="http://www.w3.org/TR/xmlschema11-2/#dt-canonical-mapping">canonical lexical form</a>
-      [[!XMLSCHEMA11-2]] for each member of the value space.
+      [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>] for each member of the value space.
       The <code>rdf:XMLLiteral</code> canonical mapping is the
       <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-exclusive-XML-canonicalization-method">exclusive
       XML canonicalization method</a> (<em>with comments, with empty  
       <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces-PrefixList">
-      InclusiveNamespaces PrefixList</a></em>) [[!XML-EXC-C14N]].
+      InclusiveNamespaces PrefixList</a></em>) [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-EXC-C14N">XML-EXC-C14N</a></cite>].
 
-      </dl>
+      </dd></dl>
 
       <p class="note">Any XML namespace declarations (<code>xmlns</code>),
-      language annotation (<code>xml:lang</code>) or base URI
+      language annotation (<code>xml:lang</code>) or base <acronym title="Uniform Resource Identifier">URI</acronym>
       declarations (<code>xml:base</code>) desired in the
       XML content must be included explicitly in the XML literal.
       Note that some concrete RDF syntaxes may define mechanisms
       for inheriting them from the context
-      (e.g., <a href="http://www.w3.org/TR/rdf-syntax-grammar/#parseTypeLiteralPropertyElt"><code>@parseType="literal"</code></a>
-      in RDF/XML [[RDF-SYNTAX-GRAMMAR]]).</p>
-</section>
+      (e.g., <a href="http://www.w3.org/TR/rdf-syntax-grammar/#parseTypeLiteralPropertyElt"><code>@parseType=&quot;literal&quot;</code></a>
+      in RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>]).</p>
+</div>
 
-<section id="datatype-maps">
-    <h3>Datatype Maps</h3>
+<div id="datatype-maps" typeof="bibo:Chapter" resource="#datatype-maps" rel="bibo:chapter" class="section">
+    <h3><span class="secno">5.4 </span>Datatype Maps</h3>
 
-    <p>A <dfn>datatype map</dfn> is an implementation-defined set of
-    &lt;<a>IRI</a>, <a>datatype</a>&gt; pairs such that no
-    IRI appears twice in the set.
+    <p>A <dfn id="dfn-datatype-map">datatype map</dfn> is an implementation-defined set of
+    &lt;<a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a>, <a href="#dfn-datatype" class="internalDFN">datatype</a>&gt; pairs such that no
+    <acronym title="Internationalized Resource Identifier">IRI</acronym> appears twice in the set.
     It can be seen as a function from IRIs to datatypes,
     where the IRIs denote the datatypes.</p>
 
-    <p>If a <a>datatype map</a> contains the IRI
+    <p>If a <a href="#dfn-datatype-map" class="internalDFN">datatype map</a> contains the <acronym title="Internationalized Resource Identifier">IRI</acronym>
     <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>,
-    then it MUST be paired with the datatype
-    <code><a>rdf:XMLLiteral</a></code>.</p>
+    then it <em class="rfc2119" title="must">must</em> be paired with the datatype
+    <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code>.</p>
 
-    <p>If a <a>datatype map</a> contains the IRI
+    <p>If a <a href="#dfn-datatype-map" class="internalDFN">datatype map</a> contains the <acronym title="Internationalized Resource Identifier">IRI</acronym>
     <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#HTML</code>,
-    then it MUST be paired with the datatype
-    <code><a>rdf:HTML</a></code>.</p>
+    then it <em class="rfc2119" title="must">must</em> be paired with the datatype
+    <code><a href="#dfn-rdf-html" class="internalDFN">rdf:HTML</a></code>.</p>
 
-    <p>If a <a>datatype map</a> contains an IRI of the form
+    <p>If a <a href="#dfn-datatype-map" class="internalDFN">datatype map</a> contains an <acronym title="Internationalized Resource Identifier">IRI</acronym> of the form
     <code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
-    then it MUST be paired with the
-    <a title="RDF-compatible XSD types">RDF-compatible XSD type</a>
-    named <code>xsd:<em>xxx</em></code>.<p>
+    then it <em class="rfc2119" title="must">must</em> be paired with the
+    <a title="RDF-compatible XSD types" href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD type</a>
+    named <code>xsd:<em>xxx</em></code>.</p><p>
 
-    <p>Other specifications
-    MAY impose additional constraints on the <a>datatype map</a>,
+    </p><p>Other specifications
+    <em class="rfc2119" title="may">may</em> impose additional constraints on the <a href="#dfn-datatype-map" class="internalDFN">datatype map</a>,
     for example, require support for certain datatypes.</p>
 
     <p class="note" id="note-custom-datatypes">The Web Ontology Language
-    [[OWL2-OVERVIEW]] offers facilities for formally defining 
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-OVERVIEW">OWL2-OVERVIEW</a></cite>] offers facilities for formally defining 
     <a href="http://www.w3.org/TR/owl2-syntax/#Datatype_Definitions">custom
     datatypes</a> that can be used with RDF. Furthermore, a practice for 
     identifying 
     <a href="http://www.w3.org/TR/swbp-xsch-datatypes/#sec-userDefined">
     user-defined simple XML Schema datatypes</a>
-    is suggested in [[SWBP-XSCH-DATATYPES]]. RDF implementations
+    is suggested in [<cite><a class="bibref" rel="biblioentry" href="#bib-SWBP-XSCH-DATATYPES">SWBP-XSCH-DATATYPES</a></cite>]. RDF implementations
     are not required to support either of these facilities.</p>
-</section>
+</div>
 
 
-<section id="section-Literal-Value">
-    <h3>The Value Corresponding to a Literal</h3>
+<div id="section-Literal-Value" typeof="bibo:Chapter" resource="#section-Literal-Value" rel="bibo:chapter" class="section">
+    <h3><span class="secno">5.5 </span>The Value Corresponding to a Literal</h3>
 
-    <p>The <dfn>literal value</dfn> associated with a <a>literal</a> is:</p>
+    <p>The <dfn id="dfn-literal-value">literal value</dfn> associated with a <a href="#dfn-literal" class="internalDFN">literal</a> is:</p>
 
     <ol>
-    <li><strong>If the literal is a <a>language-tagged string</a>,</strong>
-    then the literal value is a pair consisting of its <a>lexical form</a>
-    and its <a>language tag</a>, in that order.</li>
-    <li><strong>If the literal's <a>datatype IRI</a> is not in the
-    implementation-defined <a>datatype map</a>,</strong> then the literal value
+    <li><strong>If the literal is a <a href="#dfn-language-tagged-string" class="internalDFN">language-tagged string</a>,</strong>
+    then the literal value is a pair consisting of its <a href="#dfn-lexical-form" class="internalDFN">lexical form</a>
+    and its <a href="#dfn-language-tag" class="internalDFN">language tag</a>, in that order.</li>
+    <li><strong>If the literal's <a href="#dfn-datatype-iri" class="internalDFN">datatype <acronym title="Internationalized Resource Identifier">IRI</acronym></a> is not in the
+    implementation-defined <a href="#dfn-datatype-map" class="internalDFN">datatype map</a>,</strong> then the literal value
     is not defined by this specification.</li>
-    <li>Let <em>d</em> be the <a>datatype</a> associated with the
-    datatype IRI in the implementation-defined datatype map.</li> 
-    <li><strong>If the literal's <a>lexical form</a> is in the
-    <a>lexical space</a> of <em>d</em>,</strong> then the literal value
-    is the result of applying the <a>lexical-to-value mapping</a>
-    of <em>d</em> to the <a>lexical form</a>.</li>
+    <li>Let <em>d</em> be the <a href="#dfn-datatype" class="internalDFN">datatype</a> associated with the
+    datatype <acronym title="Internationalized Resource Identifier">IRI</acronym> in the implementation-defined datatype map.</li> 
+    <li><strong>If the literal's <a href="#dfn-lexical-form" class="internalDFN">lexical form</a> is in the
+    <a href="#dfn-lexical-space" class="internalDFN">lexical space</a> of <em>d</em>,</strong> then the literal value
+    is the result of applying the <a href="#dfn-lexical-to-value-mapping" class="internalDFN">lexical-to-value mapping</a>
+    of <em>d</em> to the <a href="#dfn-lexical-form" class="internalDFN">lexical form</a>.</li>
     <li><strong>Otherwise,</strong> the literal is
-    <dfn>ill-typed</dfn>, and no literal value can be
+    <dfn id="dfn-ill-typed">ill-typed</dfn>, and no literal value can be
     associated with the literal. Such a case, while in error, is not
     <em>syntactically</em> ill-formed.</li>
     </ol>
 
     <p class="issue">What does it mean when a literal is ill-typed or when something is not in the datatype map? What should an implementation do? Should authors avoid generating such graphs? Should consumers reject it? Is an implementation that rejects ill-formed xsd:dates conforming? Why is an ill-typed literal not necessarily an inconsistency? This is <a href="https://www.w3.org/2011/rdf-wg/track/issues/109">ISSUE-109</a>.</p>
-</section>
-
-
-</section>
+</div>
 
 
-<section id="section-fragID" class="informative">
-    <h2>Fragment Identifiers</h2>
+</div>
+
+
+<div id="section-fragID" class="informative section" typeof="bibo:Chapter" resource="#section-fragID" rel="bibo:chapter">
+    <h2><span class="secno">6 </span>Fragment Identifiers</h2><p><em>This section is non-normative.</em></p>
 
     <p class="issue">This section addresses the use of fragment IRIs
-    in concrete syntaxes for <a title="RDF graph">RDF graphs</a>, but not 
-    for <a title="RDF dataset">RDF datasets</a>. Going beyond the questions
+    in concrete syntaxes for <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>, but not 
+    for <a title="RDF dataset" href="#dfn-rdf-dataset" class="internalDFN">RDF datasets</a>. Going beyond the questions
     of pure fragment identifiers, the introduction of RDF datasets raises
     additional questions related to content negotiation and the
     authoritativeness of representations. For example, is it legitimate
@@ -1232,61 +1604,61 @@
     <code>&lt;#xxx&gt;</code>? This is
     <a href="https://www.w3.org/2011/rdf-wg/track/issues/105">ISSUE-105</a>.</p>
 
-    <p>RDF uses <a title="IRI">IRIs</a>, which may include
-    <dfn>fragment identifiers</dfn>, as resource identifiers.
+    <p>RDF uses <a title="IRI" href="#dfn-iri" class="internalDFN">IRIs</a>, which may include
+    <dfn id="dfn-fragment-identifiers">fragment identifiers</dfn>, as resource identifiers.
     The semantics of fragment identifiers is
     <a href="http://tools.ietf.org/html/rfc3986#section-3.5">defined in
-    RFC 3986</a> [[RFC3986]]: They identify a secondary resource
+    RFC 3986</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3986">RFC3986</a></cite>]: They identify a secondary resource
     that is usually a part of, view of, defined in, or described in
     the primary resource, and the precise semantics depend on the set
     of representations that might result from a retrieval action
     on the primary resource.</p>
 
     <p>This section discusses the handling of fragment identifiers
-    in representations that encode <a title="RDF graph">RDF graphs</a>.</p>
+    in representations that encode <a title="RDF graph" href="#dfn-rdf-graph" class="internalDFN">RDF graphs</a>.</p>
 
     <p>In RDF-bearing representations of a primary resource
     <code>&lt;foo&gt;</code>,
     the secondary resource identified by a fragment <code>bar</code>
-    is the <a>resource</a> <a title="denote">denoted</a> by the
-    full <a>IRI</a> <code>&lt;foo#bar&gt;</code> in the <a>RDF graph</a>.
+    is the <a href="#dfn-resource" class="internalDFN">resource</a> <a title="denote" href="#dfn-denote" class="internalDFN">denoted</a> by the
+    full <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> <code>&lt;foo#bar&gt;</code> in the <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a>.
     Since IRIs in RDF graphs can denote anything, this can be
     something external to the representation, or even external
     to the web.</p>
 
     <p>In this way, the RDF-bearing representation acts as an intermediary
     between the web-accessible primary resource, and some set of possibly
-    non-web or abstract entities that the <a>RDF graph</a> may describe.</p>
+    non-web or abstract entities that the <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> may describe.</p>
 
     <p>In cases where other specifications constrain the semantics of
     fragment identifiers in RDF-bearing representations, the encoded
-    <a>RDF graph</a> should use fragment identifiers in a way that is consistent
-    with these constraints. For example, in an HTML+RDFa document [[HTML-RDFA]],
+    <a href="#dfn-rdf-graph" class="internalDFN">RDF graph</a> should use fragment identifiers in a way that is consistent
+    with these constraints. For example, in an HTML+RDFa document [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML-RDFA">HTML-RDFA</a></cite>],
     the fragment <code>chapter1</code> may identify a document section
     via the semantics of HTML's <code>@name</code> or <code>@id</code>
-    attributes. The <a>IRI</a> <code>&lt;#chapter1&gt;</code> should
-    then be taken to <a>denote</a> that same section in any RDFa-encoded
-    <a title="RDF triple">triples</a> within the same document.
-    Similarly, if the <code>@xml:id</code> attribute [[XML-ID]] is used
-    in an RDF/XML document, then the corresponding IRI
+    attributes. The <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a> <code>&lt;#chapter1&gt;</code> should
+    then be taken to <a href="#dfn-denote" class="internalDFN">denote</a> that same section in any RDFa-encoded
+    <a title="RDF triple" href="#dfn-rdf-triple" class="internalDFN">triples</a> within the same document.
+    Similarly, if the <code>@xml:id</code> attribute [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-ID">XML-ID</a></cite>] is used
+    in an RDF/XML document, then the corresponding <acronym title="Internationalized Resource Identifier">IRI</acronym>
     should be taken to denote an XML element.</p>
 
     <p>Primary resources may have multiple representations that are
     made available via
     <a href="http://www.w3.org/TR/webarch/#frag-coneg">content negotiation</a>
-    [[WEBARCH]]. Fragments in RDF-bearing representations
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>]. Fragments in RDF-bearing representations
     should be used in a way that is consistent with the semantics imposed by any
     non-RDF representations. For example, if the fragment
     <code>chapter1</code> identifies a document section in an
-    HTML representation of the primary resource, then the <a>IRI</a>
+    HTML representation of the primary resource, then the <a href="#dfn-iri" class="internalDFN"><acronym title="Internationalized Resource Identifier">IRI</acronym></a>
     <code>&lt;#chapter1&gt;</code>
-    should be taken to <a>denote</a> that same section in all RDF-bearing
+    should be taken to <a href="#dfn-denote" class="internalDFN">denote</a> that same section in all RDF-bearing
     representations of the same primary resource.</p>
-</section>
+</div>
 
 
-<section id="section-Acknowledgments" class="informative">
-    <h2>Acknowledgments</h2>
+<div id="section-Acknowledgments" class="informative section" typeof="bibo:Chapter" resource="#section-Acknowledgments" rel="bibo:chapter">
+    <h2><span class="secno">7 </span>Acknowledgments</h2><p><em>This section is non-normative.</em></p>
 
     <p>The RDF 1.1 editors acknowledge valuable contributions from
     Thomas Baker, Dan Brickley, Gavin Carothers, Jeremy Carroll, 
@@ -1302,17 +1674,17 @@
     Massimo Marchiori, Tim Berners-Lee, Dave Reynolds and Dan Connolly.</p>
 
     <p>This specification is a product of extended deliberations by the
-    <a href="http://www.w3.org/2000/09/dbwg/details?group=46168&public=1">members of the RDF Working Group</a>.
+    <a href="http://www.w3.org/2000/09/dbwg/details?group=46168&amp;public=1">members of the RDF Working Group</a>.
     It draws upon two earlier specifications,
     <em><a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">RDF Model and Syntax</a></em>, edited by Ora Lassilla and Ralph Swick,
     and <em><a href="http://www.w3.org/TR/2000/CR-rdf-schema-20000327/">RDF Schema</a></em>, edited by Dan Brickley and R. V. Guha, which were produced by
     <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Acknowledgments">members
     of the RDFcore and Schema Working Groups</a>.</p>
-</section>
+</div>
 
 
-<section class="appendix informative" id="changes">
-    <h2>Changes between RDF 2004 and RDF 1.1</h2>
+<div class="appendix informative section" id="changes" typeof="bibo:Chapter" resource="#changes" rel="bibo:chapter">
+    <h2><span class="secno">A </span>Changes between RDF 2004 and RDF 1.1</h2><p><em>This section is non-normative.</em></p>
 
     <p class="issue">The Working Group intends to publish a separate
     Working Group Note entitled
@@ -1328,7 +1700,7 @@
     the RDF 1.1 versions of this specification.</p>
 
     <p>Previous versions of RDF used the term
-    “<dfn>RDF URI Reference</dfn>” instead of “IRI” and allowed
+    “<dfn id="dfn-rdf-uri-reference">RDF <acronym title="Uniform Resource Identifier">URI</acronym> Reference</dfn>” instead of “<acronym title="Internationalized Resource Identifier">IRI</acronym>” and allowed
     additional characters:
     “<code>&lt;</code>”, “<code>&gt;</code>”,
     “<code>{</code>”, “<code>}</code>”,
@@ -1337,36 +1709,36 @@
     ‘<code>“</code>’ (double quote), and “<code> </code>” (space).
     In IRIs, these characters must be percent-encoded as
     described in <a href="http://tools.ietf.org/html/rfc3986#section-2.1">section 2.1</a>
-    of [[RFC3986]].</p>
+    of [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3986">RFC3986</a></cite>].</p>
 
-    <p>In earlier versions of RDF, <a title="literal">literals</a>
-    with a <a>language tag</a> did not have a <a>datatype IRI</a>, and
-    <a title="simple literal">simple literals</a> could appear
+    <p>In earlier versions of RDF, <a title="literal" href="#dfn-literal" class="internalDFN">literals</a>
+    with a <a href="#dfn-language-tag" class="internalDFN">language tag</a> did not have a <a href="#dfn-datatype-iri" class="internalDFN">datatype <acronym title="Internationalized Resource Identifier">IRI</acronym></a>, and
+    <a title="simple literal" href="#dfn-simple-literal" class="internalDFN">simple literals</a> could appear
     directly in the abstract syntax. Simple literals and literals with a
     language tag were collectively known as
-    <dfn title="plain literal">plain literals</dfn>.</p>
+    <dfn title="plain literal" id="dfn-plain-literal">plain literals</dfn>.</p>
 
     <p>Earlier versions of RDF permitted
-    <a title="language tag">language tags</a> that
+    <a title="language tag" href="#dfn-language-tag" class="internalDFN">language tags</a> that
     adhered to the generic tag/subtag syntax of language tags,
-    but were not well-formed according to [[!BCP47]]. Such
+    but were not well-formed according to [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>]. Such
     language tags do not conform to RDF 1.1.</p>
 
     <p>The <code>xsd:string</code> datatype does not
     permit the <code>#x0</code> character, and implementations may not permit
     control codes in the <code>#x1-#x1F</code> range. Earlier versions of
     RDF allowed these characters in
-    <a title="simple literal">simple literals</a>, although they
-    could never be serialized in a W3C-recommended concrete syntax.</p>
-</section>
+    <a title="simple literal" href="#dfn-simple-literal" class="internalDFN">simple literals</a>, although they
+    could never be serialized in a <acronym title="World Wide Web Consortium">W3C</acronym>-recommended concrete syntax.</p>
+</div>
 
 
-<section class="appendix informative" id="change-log">
-  <h2>Change Log</h2>
+<div class="appendix informative section" id="change-log" typeof="bibo:Chapter" resource="#change-log" rel="bibo:chapter">
+  <h2><span class="secno">B </span>Change Log</h2><p><em>This section is non-normative.</em></p>
 
 
-<section class="appendix" id="changes-wd3">
-  <h3>Changes from 05 June 2012 WD to this version</h3>
+<div class="appendix section" id="changes-wd3" typeof="bibo:Chapter" resource="#changes-wd3" rel="bibo:chapter">
+  <h3><span class="secno">B.1 </span>Changes from 05 June 2012 WD to this version</h3>
 
   <p>This section lists changes from the
   <a href="http://www.w3.org/TR/2012/WD-rdf11-concepts-20120605/">05 June 2012 Working Draft (WD)</a> to this Working Draft of 
@@ -1374,7 +1746,7 @@
 
   <ul>
     <li>2013-01-14: Editorial changes in response to <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0354.html">reviews from Antoine Zimmermann</a> <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0360.html">and Peter Patel-Schneider</a></li>
-    <li>2012-11-21: Replaced the placeholder term “g-box” with “<a>RDF source</a>” (<a href="https://www.w3.org/2011/rdf-wg/track/issues/110">ISSUE-110</a>)</li>
+    <li>2012-11-21: Replaced the placeholder term “g-box” with “<a href="#dfn-rdf-source" class="internalDFN">RDF source</a>” (<a href="https://www.w3.org/2011/rdf-wg/track/issues/110">ISSUE-110</a>)</li>
     <li>2012-11-21: Removed various Notes (as <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0131.html">listed here</a>), and refactored others (<a href="https://www.w3.org/2011/rdf-wg/track/issues/104">ISSUE-104</a>)</li>
     <li>2012-11-17: Many changes to Introduction, including mostly new subsections on <a href="#managing-graphs">Working with Multiple RDF Graphs and G-Boxes</a>, <a href="#entailment">Equivalence, Entailment and Inconsistencies</a>, and <a href="#rdf-documents">RDF Documents and Syntaxes</a></li>
     <li>2012-11-17: Reverted section on <a href="#section-blank-nodes">Blank Nodes</a> to earlier state</li>
@@ -1385,18 +1757,18 @@
     <li>2012-11-09: Moved all informative material about changes between RDF 2004 and RDF 1.1 to a <a href="#changes">new appendix</a></li>
     <li>2012-11-07: Add <a href="#change-over-time">new informative section on Change Over Time</a></li>
     <li>2012-11-07: New <a href="#abstract">abstract</a>, based on comments from Dan Connolly</li>
-    <li>2012-11-06: Tweak definition of <a title="literal">literals</a> to avoid apparent contradiction (<a href="http://www.w3.org/2011/rdf-wg/track/issues/94">ISSUE-94</a>)</li>
+    <li>2012-11-06: Tweak definition of <a title="literal" href="#dfn-literal" class="internalDFN">literals</a> to avoid apparent contradiction (<a href="http://www.w3.org/2011/rdf-wg/track/issues/94">ISSUE-94</a>)</li>
     <li>2012-11-06: Add a <a href="#note-custom-datatypes">note</a> on the use of OWL2 custom datatypes and simple user-defined XML Schema datatypes (<a href="http://www.w3.org/2011/rdf-wg/track/issues/96">ISSUE-96</a>)</li>
     <li>2012-11-06: Add a <a href="#note-empty-named-graphs">note on empty named graphs</a> (<a href="http://www.w3.org/2011/rdf-wg/track/issues/22">ISSUE-22</a>)</li>
-    <li>2012-11-06: Modify the <a title="relative IRI">Note on relative IRIs</a> to stress their usefulness and to clarify the role of RFC 3986 in the resolution process</li>
+    <li>2012-11-06: Modify the <a title="relative IRI" href="#dfn-relative-iri" class="internalDFN">Note on relative IRIs</a> to stress their usefulness and to clarify the role of RFC 3986 in the resolution process</li>
     <li>2012-11-06: Informatively <a href="#referents">explain</a> that IRIs in this spec are treated only as nodes in a graph data model, and no interaction model is implied</li>
-    <li>2012-08-09: Clarify that all datatypes are optional, but RDF-conformant specifications MAY require specific <a title="datatype map">datatype maps</a></li>
+    <li>2012-08-09: Clarify that all datatypes are optional, but RDF-conformant specifications <em class="rfc2119" title="may">may</em> require specific <a title="datatype map" href="#dfn-datatype-map" class="internalDFN">datatype maps</a></li>
   </ul>
-</section>
+</div>
 
 
-<section class="appendix" id="changes-wd2">
-  <h3>Changes from FPWD to 05 June 2012 WD</h3>
+<div class="appendix section" id="changes-wd2" typeof="bibo:Chapter" resource="#changes-wd2" rel="bibo:chapter">
+  <h3><span class="secno">B.2 </span>Changes from FPWD to 05 June 2012 WD</h3>
 
   <p>This section lists changes from the
   <a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">First Public Working Draft (FPWD)</a>
@@ -1406,32 +1778,32 @@
   <ul>
     <li>2012-05-31: Update <a href="#section-Acknowledgments">Acknowledgements</a> for RDF 1.1; added RDFa 1.1 markup</li>
     <li>2012-05-24: Moved the multigraph section to an earlier position and renamed it to “<a href="#section-dataset">RDF Datasets</a>”</li>
-    <li>2012-05-17: Changed normative reference for DOM in <code><a>rdf:XMLLiteral</a></code> from [DOM3CORE] to [DOM4] as we need DOM4 anyways for <code><a>rdf:HTML</a></code></li>
-    <li>2012-05-17: Added <code><a>rdf:HTML</a></code> datatype (<a href="http://www.w3.org/2011/rdf-wg/track/issues/63">ISSUE-63</a>)</li>
-    <li>2012-05-17: Added <a href="http://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a> to list of <a>RDF-compatible XSD types</a> (<a href="http://www.w3.org/2011/rdf-wg/track/issues/88">ISSUE-88</a>)</li>
+    <li>2012-05-17: Changed normative reference for DOM in <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code> from [DOM3CORE] to [DOM4] as we need DOM4 anyways for <code><a href="#dfn-rdf-html" class="internalDFN">rdf:HTML</a></code></li>
+    <li>2012-05-17: Added <code><a href="#dfn-rdf-html" class="internalDFN">rdf:HTML</a></code> datatype (<a href="http://www.w3.org/2011/rdf-wg/track/issues/63">ISSUE-63</a>)</li>
+    <li>2012-05-17: Added <a href="http://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a> to list of <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a> (<a href="http://www.w3.org/2011/rdf-wg/track/issues/88">ISSUE-88</a>)</li>
     <li>2012-05-14: Replaced the example graph diagram in <a href="#data-model">Section 1.1</a> with a re-drawn SVG version, with support from Dominik Tomaszuk</li>
     <li>2012-05-10: New <a href="#conformance">Conformance section</a> to explain that this specification is not implemented directly, but through other specifications that use our definitions</li>
-    <li>2012-05-10: Simplified <code><a>rdf:XMLLiteral</a></code>'s new value space slightly after feedback from Ivan Herman and Arnaud Le Hors.</li>
+    <li>2012-05-10: Simplified <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code>'s new value space slightly after feedback from Ivan Herman and Arnaud Le Hors.</li>
     <li>2012-05-10: Added an informative subsection on <a href="#vocabularies">RDF vocabularies and namespace IRIs</a>.</li>
     <li>2012-05-09: Removed an example from the conformance section that didn't make sense any more with the modified <code>rdf:XMLLiteral</code>. Added some new issue boxes.</li>
-    <li>2012-05-09: <code><a>rdf:XMLLiteral</a></code> no longer requires lexical forms to be canonicalized, and the value space is now defined in terms of [DOM-LEVEL-3-CORE] (<a href="https://www.w3.org/2011/rdf-wg/track/issues/13">ISSUE-13</a>)</li>
-    <li>2012-05-09: Removed Section 3 <em>RDF Vocabulary IRI and Namespace</em>; its contents will be folded into the RDF Schema document</li>
-    <li>2012-05-02: Renamed “graph equivalence” to “<a>graph isomorphism</a>” (<a href="https://www.w3.org/2011/rdf-wg/track/issues/86">ISSUE-86</a>)</li>
-    <li>2012-05-02: Updated [[XMLSCHEMA11-1]] and [[XMLSCHEMA11-2]] references to the new REC versions</li>
-    <li>2012-05-02: Added the new XSD 1.1 datatypes <a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration">xsd:dayTimeDuration</a>, <a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration">xsd:yearMonthDuration</a> and <a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp">xsd:dateTimeStamp</a> to the list of <a>RDF-compatible XSD types</a> (<a href="https://www.w3.org/2011/rdf-wg/track/issues/66">ISSUE-66</a>)</li>
+    <li>2012-05-09: <code><a href="#dfn-rdf-xmlliteral" class="internalDFN">rdf:XMLLiteral</a></code> no longer requires lexical forms to be canonicalized, and the value space is now defined in terms of [DOM-LEVEL-3-CORE] (<a href="https://www.w3.org/2011/rdf-wg/track/issues/13">ISSUE-13</a>)</li>
+    <li>2012-05-09: Removed Section 3 <em>RDF Vocabulary <acronym title="Internationalized Resource Identifier">IRI</acronym> and Namespace</em>; its contents will be folded into the RDF Schema document</li>
+    <li>2012-05-02: Renamed “graph equivalence” to “<a href="#dfn-graph-isomorphism" class="internalDFN">graph isomorphism</a>” (<a href="https://www.w3.org/2011/rdf-wg/track/issues/86">ISSUE-86</a>)</li>
+    <li>2012-05-02: Updated [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-1">XMLSCHEMA11-1</a></cite>] and [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>] references to the new REC versions</li>
+    <li>2012-05-02: Added the new XSD 1.1 datatypes <a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration">xsd:dayTimeDuration</a>, <a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration">xsd:yearMonthDuration</a> and <a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp">xsd:dateTimeStamp</a> to the list of <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a> (<a href="https://www.w3.org/2011/rdf-wg/track/issues/66">ISSUE-66</a>)</li>
     <li>2012-04-26: Remove normative definition of “property” as it disagreed with RDF Semantics; small editorial changes.</li>
     <li>2011-11-21: Updated XHTML 1.0 reference to XHTML 1.1</li>
-    <li>2011-11-20: Added table of <a>RDF-compatible XSD types</a>, and definition of <a>datatype map</a>, both adapted from previous content in [[RDF-MT]]
-    <li>2011-11-18: Replaced informative <em>Introduction</em> and <em>RDF Concepts</em> sections with a new extended introduction. Folded some content from <em>RDF Concepts</em> into the later normative sections, mostly as examples and notes.</li>
+    <li>2011-11-20: Added table of <a href="#dfn-rdf-compatible-xsd-types" class="internalDFN">RDF-compatible XSD types</a>, and definition of <a href="#dfn-datatype-map" class="internalDFN">datatype map</a>, both adapted from previous content in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>]
+    </li><li>2011-11-18: Replaced informative <em>Introduction</em> and <em>RDF Concepts</em> sections with a new extended introduction. Folded some content from <em>RDF Concepts</em> into the later normative sections, mostly as examples and notes.</li>
     <li>2011-11-10: Changed XSD references to version 1.1</li>
     <li>2011-11-10: Replaced the <a href="#section-fragID">section on fragment identifiers</a> with an updated account that follows RFC 3986</li>
-    <li>2011-11-09: Updated the two sections on literals to reflect the <a href="http://www.w3.org/2011/rdf-wg/track/issues/71">ISSUE-71</a> resolution that literals with language tag now have the datatype IRI <code>rdf:langString</code>. Formally introduced the term “language-tagged string”.</li>
+    <li>2011-11-09: Updated the two sections on literals to reflect the <a href="http://www.w3.org/2011/rdf-wg/track/issues/71">ISSUE-71</a> resolution that literals with language tag now have the datatype <acronym title="Internationalized Resource Identifier">IRI</acronym> <code>rdf:langString</code>. Formally introduced the term “language-tagged string”.</li>
     <li>2011-11-09: Add a note that explains that #x0-#x1F are no longer allowed in simple literals
-  </ul>
-</section>
+  </li></ul>
+</div>
 
-<section class="appendix" id="changes-fpwd">
-  <h3>Changes from RDF 2004 to FPWD</h3>
+<div class="appendix section" id="changes-fpwd" typeof="bibo:Chapter" resource="#changes-fpwd" rel="bibo:chapter">
+  <h3><span class="secno">B.3 </span>Changes from RDF 2004 to FPWD</h3>
 
   <p>This section lists changes from the
   <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/">2004 Recommendation of
@@ -1446,20 +1818,52 @@
     <li>2011-07-21: Updated the introduction, and removed many mentions of RDF/XML. Changed the normative reference for the terms in the RDF namespace from the RDF/XML spec to the RDF Schema spec. Removed any mention of the 1999 version of RDF.</li>
     <li>2011-07-21: Replaced RFC 2279 reference (UTF-8) with RFC 3629</li>
     <li>2011-07-20: Removed informative sections “Motivations and Goals” (see <a href="http://www.w3.org/TR/rdf-concepts/#section-Overview">RDF 2004 version</a>) and “RDF Expression of Simple Facts” (see <a href="http://www.w3.org/TR/rdf-concepts/#section-SimpleFacts">RDF 2004 version</a>)</li>
-    <li>2011-06-01: Replaced the URI References section with <a href="#section-IRIs">new section on IRIs</a>, and changed “RDF URI Reference” to “IRI” throughout the document.</li>
+    <li>2011-06-01: Replaced the <acronym title="Uniform Resource Identifier">URI</acronym> References section with <a href="#section-IRIs">new section on IRIs</a>, and changed “RDF <acronym title="Uniform Resource Identifier">URI</acronym> Reference” to “<acronym title="Internationalized Resource Identifier">IRI</acronym>” throughout the document.</li>
     <li>2011-06-01: Changed language tag definition to require well-formedness according to BCP47; added a note that this invalidates some RDF</li>
     <li>2011-05-25: Added boxes for known WG issues throught the document</li>
     <li>2011-05-25: Deleted “Structure of this Document” section, it added no value beyond the TOC</li>
     <li>2011-05-25: Implemented resolution of <a href="http://www.w3.org/2011/rdf-wg/track/issues/40">ISSUE-40: Skolemization advice in the RDF dcocument</a> by adding a section on <a href="#section-skolemization">Replacing Blank Nodes with IRIs</a></li>
     <li>2011-05-25: rdf:XMLLiteral is disjoint from any datatype not explicitly related to it, per erratum <a href="http://www.w3.org/2001/sw/RDFCore/errata#concept-xmlliteral">[concept-xmlliteral]</a></li>
     <li>2011-05-25: Added Conformance section with RFC2119 reference</li>
-    <li>2011-05-25: Updated all W3C references to latest editions, and Unicode from v3 to v4</li>
+    <li>2011-05-25: Updated all <acronym title="World Wide Web Consortium">W3C</acronym> references to latest editions, and Unicode from v3 to v4</li>
     <li>2011-05-24: Converted to ReSpec, changed metadata to reflect RDF 1.1</li>
   </ul>
-</section>
+</div>
 
-</section>
+</div>
 
-  </body>
-</html>
+  
 
+
+<div id="references" class="appendix section" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter"><h2><span class="secno">C </span>References</h2><div id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-BCP47">[BCP47]</dt><dd rel="dcterms:requires">A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a> September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a> 
+</dd><dt id="bib-DOM4">[DOM4]</dt><dd rel="dcterms:requires">Anne van Kesteren; Aryeh Gregor; Ms2ger. <a href="http://www.w3.org/TR/2012/WD-dom-20120405/"><cite>DOM4.</cite></a> 5 April 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-dom-20120405/">http://www.w3.org/TR/2012/WD-dom-20120405/</a> 
+</dd><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires">Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/html5"><cite>HTML5.</cite></a> 25 October 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-html5-20121025/">http://www.w3.org/TR/2012/WD-html5-20121025/</a> 
+</dd><dt id="bib-NFC">[NFC]</dt><dd rel="dcterms:requires">M. Davis, Ken Whistler. <a href="http://www.unicode.org/reports/tr15/"><cite>TR15, Unicode Normalization Forms.</cite></a>. 17 September 2010, URL: <a href="http://www.unicode.org/reports/tr15/">http://www.unicode.org/reports/tr15/</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.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>. Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , 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-XML-EXC-C14N">[XML-EXC-C14N]</dt><dd rel="dcterms:requires">Donald E. Eastlake 3rd; Joseph Reagle; John Boyer. <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/"><cite>Exclusive XML Canonicalization Version 1.0.</cite></a> 18 July 2002. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/</a> 
+</dd><dt id="bib-XML-NAMES">[XML-NAMES]</dt><dd rel="dcterms:requires">Richard Tobin; et al. <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/"><cite>Namespaces in XML 1.0 (Third Edition).</cite></a> 8 December 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/">http://www.w3.org/TR/2009/REC-xml-names-20091208/</a> 
+</dd><dt id="bib-XML10">[XML10]</dt><dd rel="dcterms:requires">C. M. Sperberg-McQueen; et al. <a href="http://www.w3.org/TR/2008/REC-xml-20081126/"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition).</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a> 
+</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd rel="dcterms:requires">Henry S. Thompson; et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.</cite></a> 5 April 2012. W3C Recommendation URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a> 
+</dd></dl></div><div id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-COOLURIS">[COOLURIS]</dt><dd rel="dcterms:references">Richard Cyganiak; Leo Sauermann. <a href="http://www.w3.org/TR/2008/NOTE-cooluris-20081203"><cite>Cool URIs for the Semantic Web.</cite></a> 3 December 2008. W3C Note. URL: <a href="http://www.w3.org/TR/2008/NOTE-cooluris-20081203">http://www.w3.org/TR/2008/NOTE-cooluris-20081203</a> 
+</dd><dt id="bib-HTML-RDFA">[HTML-RDFA]</dt><dd rel="dcterms:references">Manu Sporny; et al. <a href="http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/"><cite>HTML+RDFa 1.1</cite></a> 25 May 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/</a> 
+</dd><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd rel="dcterms:references">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-OWL2-OVERVIEW">[OWL2-OVERVIEW]</dt><dd rel="dcterms:references">W3C OWL Working Group. <a href="http://www.w3.org/TR/2009/REC-owl2-overview-20091027/"><cite>OWL 2 Web Ontology Language: Overview.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-overview-20091027/">http://www.w3.org/TR/2009/REC-owl2-overview-20091027/</a> 
+</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd rel="dcterms:references">Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a> 
+</dd><dt id="bib-RDF-PRIMER">[RDF-PRIMER]</dt><dd rel="dcterms:references">Frank Manola; Eric Miller. <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/"><cite>RDF Primer.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">http://www.w3.org/TR/2004/REC-rdf-primer-20040210/</a> 
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd rel="dcterms:references">Dan Brickley; Ramanathan V. Guha. <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210"><cite>RDF Vocabulary Description Language 1.0: RDF Schema.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">http://www.w3.org/TR/2004/REC-rdf-schema-20040210</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-RDF-TESTCASES">[RDF-TESTCASES]</dt><dd rel="dcterms:references">Jan Grant; Dave Beckett. <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210"><cite>RDF Test Cases.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210">http://www.w3.org/TR/2004/REC-rdf-testcases-20040210</a> 
+</dd><dt id="bib-RDFA-PRIMER">[RDFA-PRIMER]</dt><dd rel="dcterms:references">Ben Adida, Ivan Herman, Manu Sporny. <a href="http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607"><cite>RDFa Primer.</cite></a> 07 June 2012. W3C Note. URL: <a href="http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607">http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607</a> 
+</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd rel="dcterms:references">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-SWBP-N-ARYRELATIONS">[SWBP-N-ARYRELATIONS]</dt><dd rel="dcterms:references">Natasha Noy; Alan Rector. <a href="http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412"><cite>Defining N-ary Relations on the Semantic Web.</cite></a> 12 April 2006. W3C Note. URL: <a href="http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412">http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412</a> 
+</dd><dt id="bib-SWBP-XSCH-DATATYPES">[SWBP-XSCH-DATATYPES]</dt><dd rel="dcterms:references">Jeremy J. Carroll; Jeff Z. Pan. <a href="http://www.w3.org/TR/2006/NOTE-swbp-xsch-datatypes-20060314"><cite>XML Schema Datatypes in RDF and OWL.</cite></a> 14 March 2006. W3C Note. URL: <a href="http://www.w3.org/TR/2006/NOTE-swbp-xsch-datatypes-20060314">http://www.w3.org/TR/2006/NOTE-swbp-xsch-datatypes-20060314</a> 
+</dd><dt id="bib-TURTLE-TR">[TURTLE-TR]</dt><dd rel="dcterms:references">Eric Prud'hommeaux, Gavin Carothers. <a href="http://www.w3.org/TR/2012/WD-turtle-20120710/"><cite>Turtle: Terse RDF Triple Language.</cite></a> 10 July 2012. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2012/WD-turtle-20120710/">http://www.w3.org/TR/2012/WD-turtle-20120710/</a>
+</dd><dt id="bib-VOCAB-ORG">[VOCAB-ORG]</dt><dd rel="dcterms:references">Dave Reynolds. <a href="http://www.w3.org/TR/2012/WD-vocab-org-20121023/"><cite>An organization ontology.</cite></a> 23 October 2012. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2012/WD-vocab-org-20121023/">http://www.w3.org/TR/2012/WD-vocab-org-20121023/</a>
+</dd><dt id="bib-WEBARCH">[WEBARCH]</dt><dd rel="dcterms:references">Norman Walsh; Ian Jacobs. <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/"><cite>Architecture of the World Wide Web, Volume One.</cite></a> 15 December 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">http://www.w3.org/TR/2004/REC-webarch-20041215/</a> 
+</dd><dt id="bib-WELL-KNOWN">[WELL-KNOWN]</dt><dd rel="dcterms:references">M. Nottingham; E. Hammer-Lahav. <a href="http://tools.ietf.org/html/rfc5785"><cite>Defining Well-Known Uniform Resource Identifiers (URIs).</cite></a> April 2010. Internet RFC 5785. URL: <a href="http://tools.ietf.org/html/rfc5785">http://tools.ietf.org/html/rfc5785</a>
+</dd><dt id="bib-XML-ID">[XML-ID]</dt><dd rel="dcterms:references">Daniel Veillard; Jonathan Marsh; Norman Walsh. <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909"><cite>xml:id Version 1.0.</cite></a> 9 September 2005. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909">http://www.w3.org/TR/2005/REC-xml-id-20050909</a> 
+</dd><dt id="bib-XMLSCHEMA11-1">[XMLSCHEMA11-1]</dt><dd rel="dcterms:references">C. M. Sperberg-McQueen; Henry S. Thompson; Shudi Gao. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures.</cite></a> 5 April 2012. W3C Recommendation URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/</a> 
+</dd></dl></div></div></body></html>