LC version
authorGuus Schreiber <guus.schreiber@vu.nl>
Fri, 19 Jul 2013 01:24:15 +0200
changeset 963 cdd9bd4492dc
parent 962 d8621304592b
child 964 bd6d343e0f31
LC version
drafts/rdf11-mt/Overview.html
--- a/drafts/rdf11-mt/Overview.html	Fri Jul 19 01:16:02 2013 +0200
+++ b/drafts/rdf11-mt/Overview.html	Fri Jul 19 01:24:15 2013 +0200
@@ -1,11 +1,10 @@
 <!DOCTYPE html>
-<html lang="en" dir="ltr">
+<html lang="en" dir="ltr" typeof="bibo:Document w3p:LastCall" about="" property="dcterms:language" content="en">
 <head>
      <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
      <title>RDF 1.1 Semantics</title>
     
     
-
    
 <style type="text/css">
 .semantictable {background-color: #FFFFAA; padding:0.5em;}
@@ -178,13 +177,13 @@
       <a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a>
     
   </p>
-  <h1 class="title p-name" id="title">RDF 1.1 Semantics</h1>
+  <h1 class="title p-name" id="title" property="dcterms:title">RDF 1.1 Semantics</h1>
   
-  <h2 id="w3c-last-call-working-draft-03-july-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Last Call Working Draft <time class="dt-published" datetime="2013-07-03">03 July 2013</time></h2>
+  <h2 id="w3c-last-call-working-draft-23-july-2013" property="dcterms:issued" datatype="xsd:dateTime" content="2013-07-22T22:00:00.000Z"><abbr title="World Wide Web Consortium">W3C</abbr> Last Call Working Draft <time class="dt-published" datetime="2013-07-23">23 July 2013</time></h2>
   <dl>
     
       <dt>This version:</dt>
-      <dd><a class="u-url" href="http://www.w3.org/TR/2013/WD-rdf11-mt-20130703/">http://www.w3.org/TR/2013/WD-rdf11-mt-20130703/</a></dd>
+      <dd><a class="u-url" href="http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/">http://www.w3.org/TR/2013/WD-rdf11-mt-20130723/</a></dd>
       <dt>Latest published version:</dt>
       <dd><a href="http://www.w3.org/TR/rdf11-mt/">http://www.w3.org/TR/rdf11-mt/</a></dd>
     
@@ -197,15 +196,17 @@
     
     
       <dt>Previous version:</dt>
-      <dd><a href="http://www.w3.org/TR/2013/WD-rdf11-mt-20130409/">http://www.w3.org/TR/2013/WD-rdf11-mt-20130409/</a></dd>
+      <dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2013/WD-rdf11-mt-20130409/">http://www.w3.org/TR/2013/WD-rdf11-mt-20130409/</a></dd>
     
     
       <dt>Latest recommendation:</dt>
       <dd><a href="http://www.w3.org/TR/rdf-mt/">http://www.w3.org/TR/rdf-mt/</a></dd>
     
     <dt>Editors:</dt>
-    <dd class="p-author h-card vcard"><a class="u-url url p-name fn" href="http://www.ihmc.us/groups/phayes/">Patrick J. Hayes</a>, <a class="p-org org h-org h-card" href="http://www.ihmc.us/index.php">Florida IHMC</a></dd>
-<dd class="p-author h-card vcard"><span class="p-name fn">Peter F. Patel-Schneider</span>, <a class="p-org org h-org h-card" href="http://www.nuance.com/">Nuance Communications</a></dd>
+    <dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Patrick J. Hayes" href="http://www.ihmc.us/groups/phayes/">Patrick J. Hayes</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.ihmc.us/index.php">Florida IHMC</a></span>
+</dd>
+<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><span property="foaf:name" class="p-name fn">Peter F. Patel-Schneider</span>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.nuance.com/">Nuance Communications</a></span>
+</dd>
 
     
     
@@ -231,10 +232,10 @@
   
   <hr>
 </div>
-    <section class="introductory" id="abstract"><h2>Abstract</h2>
+    <section rel="bibo:chapter" resource="#abstract" typeof="bibo:Chapter" datatype="" property="dcterms:abstract" class="introductory" id="abstract"><h2>Abstract</h2>
     <p>  This document describes a precise semantics for the Resource Description 
   Framework 1.1 [<cite><a href="#bib-RDF11-CONCEPTS" class="bibref">RDF11-CONCEPTS</a></cite>] and RDF Schema [<cite><a href="#bib-RDF-SCHEMA" class="bibref">RDF-SCHEMA</a></cite>]. It defines a number of distinct entailment regimes and corresponding patterns of entailment. It is part of a suite of documents which comprise the full specification of RDF 1.1.</p>
-  </section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
+  </section><section rel="bibo:chapter" resource="#sotd" typeof="bibo:Chapter" id="sotd" class="introductory"><h2>Status of This Document</h2>
   
     
       
@@ -280,7 +281,9 @@
         <p>
           
             This document was produced by a group operating under the 
-            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+             
+                <a id="sotd_patent" about="" rel="w3p:patentRules" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+            
           
           
           
@@ -303,16 +306,16 @@
 
 
 
-    <section class="introductory"><h2 id="notes">Notes</h2>
+    <section rel="bibo:chapter" resource="#notes" typeof="bibo:Chapter" class="introductory"><h2 id="notes">Notes</h2>
 <p class="changenote">Notes in this style indicate changes from the 2004 RDF 1.0 semantics.</p>
 <p class="technote">Notes in this style are technical asides on obscure or recondite matters.</p></section>
-    <section id="introduction-1">
+    <section id="introduction-1" rel="bibo:chapter" resource="#introduction" typeof="bibo:Chapter">
       <!--OddPage--><h2 id="introduction"><span class="secno">1. </span>Introduction</h2>
       <p>
         This document defines a model-theoretic semantics for RDF graphs and the RDF and RDFS vocabularies, providing an exact formal specification of when truth is preserved by transformations of RDF or operations which derive RDF content from other RDF. </p>
 
     </section>
-<section id="conformance"><!--OddPage--><h2><span class="secno">2. </span>Conformance</h2>
+<section rel="bibo:chapter" resource="#conformance" typeof="bibo:Chapter" id="conformance"><!--OddPage--><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
@@ -324,7 +327,7 @@
 </p>
 <p>This specification, <em>RDF 1.1 Semantics</em>, is normative for RDF semantics and the validity of RDF inference processes. It is not normative for many aspects of RDF meaning which are not described or specified by this semantics, including social issues of how IRIs are assigned meanings in use and how the referents of IRIs are related to Web content expressed in other media such as natural language texts. </p></section>
     
- <section id="semantic-extensions-and-entailment-regimes">
+ <section id="semantic-extensions-and-entailment-regimes" rel="bibo:chapter" resource="#extensions" typeof="bibo:Chapter">
       <!--OddPage--><h2 id="extensions"><span class="secno">3. </span>Semantic Extensions and Entailment Regimes</h2>
       <p>RDF is intended for use as a base notation for a variety of extended notations such as OWL [<cite><a href="#bib-OWL2-OVERVIEW" class="bibref">OWL2-OVERVIEW</a></cite>] and RIF [<cite><a href="#bib-RIF-OVERVIEW" class="bibref">RIF-OVERVIEW</a></cite>], whose expressions can be encoded as RDF graphs which use a particular vocabulary with a specially defined meaning. Also, particular IRI vocabularies may be given meanings by other specifications or conventions. When such extra meanings are assumed, a given RDF graph may support more extensive entailments than are sanctioned by the basic RDF semantics. In general, the more assumptions that are made about the meanings of IRIs in an RDF graph, the more entailments follow from those assumptions. </p>
 
@@ -335,7 +338,7 @@
 <p>All entailment regimes <em title="MUST" class="rfc2119">MUST</em> be <a>monotonic</a> extensions of the simple entailment regime described in the document, in the sense that if A <a class="internalDFN" href="#dfn-simply-entails">simply entails</a> B then A also entails B under any extended notion of entailment, provided that any syntactic conditions of the extension are also satisfied. Put another way, a <a class="internalDFN" href="#dfn-semantic-extension">semantic extension</a> cannot "cancel" an entailment made by a weaker entailment regime, although it can treat the result as a syntax error.</p>
     </section>
 
- <section id="notation-and-terminology">
+ <section id="notation-and-terminology" rel="bibo:chapter" resource="#notation" typeof="bibo:Chapter">
       <!--OddPage--><h2 id="notation"><span class="secno">4. </span>Notation and Terminology</h2>
 
 
@@ -347,7 +350,7 @@
 <p>Throughout this document, the equality sign = indicates strict identity. The statement "A = B" means that there is one entity to which both expressions "A" and "B" refer.  Angle brackets &lt; x, y &gt; are used to indicate an ordered pair 
   of x and y.</p>
 
-<p>Throughout this document, RDF graphs and other fragments of RDF abstract syntax are written using the notational conventions of the Turtle syntax [<cite><a href="#bib-TURTLE-TR" class="bibref">TURTLE-TR</a></cite>]. The namespace prefixes <code>rdf:</code> <code>rdfs:</code> and <code>xsd:</code> are used as in [<cite><a href="#bib-RDF11-CONCEPTS" class="bibref">RDF11-CONCEPTS</a></cite>], <a href="http://www.w3.org/TR/rdf11-concepts/#vocabularies">section 1.4</a>. When the exact IRI does not matter, the prefix <code>ex:</code> is used. When stating general rules or conditions we use three-character variables such as aaa, xxx, sss  to indicate arbitrary IRIs, literals, or other components of RDF syntax. Some cases are illustrated by node-arc diagrams showing the graph structure directly.</p>
+<p>Throughout this document, RDF graphs and other fragments of RDF abstract syntax are written using the notational conventions of the Turtle syntax [<cite><a href="#bib-TURTLE-CR" class="bibref">TURTLE-CR</a></cite>]. The namespace prefixes <code>rdf:</code> <code>rdfs:</code> and <code>xsd:</code> are used as in [<cite><a href="#bib-RDF11-CONCEPTS" class="bibref">RDF11-CONCEPTS</a></cite>], <a href="http://www.w3.org/TR/rdf11-concepts/#vocabularies">section 1.4</a>. When the exact IRI does not matter, the prefix <code>ex:</code> is used. When stating general rules or conditions we use three-character variables such as aaa, xxx, sss  to indicate arbitrary IRIs, literals, or other components of RDF syntax. Some cases are illustrated by node-arc diagrams showing the graph structure directly.</p>
 
 <p>A <dfn id="dfn-name">name</dfn> is any IRI or literal. A typed literal contains
   two <a class="internalDFN" href="#dfn-name">name</a>s: itself and its internal type 
@@ -393,7 +396,7 @@
 <p>is lean. <a class="internalDFN" href="#dfn-ground">Ground</a> graphs are lean. </p>
 
 
-<section id="shared-blank-nodes-unions-and-merges"> <h3 id="unions_merges"><span class="secno">4.1 </span>Shared blank nodes, unions and merges</h3>
+<section id="shared-blank-nodes-unions-and-merges" rel="bibo:chapter" resource="#unions_merges" typeof="bibo:Chapter"> <h3 id="unions_merges"><span class="secno">4.1 </span>Shared blank nodes, unions and merges</h3>
 <p>
 Graphs share blank nodes only if they are derived from graphs
 described by documents or other structures (such as an RDF dataset) that explicitly provide for the sharing of blank nodes between different RDF graphs.  Simply downloading a
@@ -441,7 +444,7 @@
 
 </section>
 
- <section id="simple-interpretations">
+ <section id="simple-interpretations" rel="bibo:chapter" resource="#simple" typeof="bibo:Chapter">
       <!--OddPage--><h2 id="simple"><span class="secno">5. </span> Simple Interpretations</h2>
   
 <p>This section defines the basic notions of interpretation and truth for RDF graphs. All <a class="internalDFN" href="#dfn-semantic-extension">semantic extension</a>s of any vocabulary or higher-level notation encoded in RDF <em title="MUST" class="rfc2119">MUST</em> conform to these minimal truth conditions. Other <a class="internalDFN" href="#dfn-semantic-extension">semantic extension</a>s may extend and add to these, but they <em title="MUST NOT" class="rfc2119">MUST NOT</em> modify or negate them. For example, because interpretations are mappings which apply to IRIs, a <a class="internalDFN" href="#dfn-semantic-extension">semantic extension</a> cannot interpret different occurrences of a single IRI differently.</p>
@@ -522,7 +525,7 @@
 
 <p><a class="internalDFN" href="#dfn-semantic-extension">Semantic extension</a>s may impose further constraints upon interpretation mappings by requiring some IRIs to refer in particular ways. For example, D-interpretations, described below, require some IRIs, understood as <a class="internalDFN" href="#dfn-identify">identify</a>ing and referring to datatypes, to have a fixed interpretation. </p>
 
-<section id="blank-nodes">
+<section id="blank-nodes" rel="bibo:chapter" resource="#blank_nodes" typeof="bibo:Chapter">
   <h3 id="blank_nodes"><span class="secno">5.1 </span>Blank nodes</h3>
 
     
@@ -549,7 +552,7 @@
 a denotation by an interpretation, reflecting the intuition that
 they have no 'global' meaning. </p>
 
-<section id="shared-blank-nodes-informative" class="informative"><h4 id="shared_blank_nodes"><span class="secno">5.1.1 </span>Shared blank nodes (Informative)</h4><p><em>This section is non-normative.</em></p>
+<section id="shared-blank-nodes-informative" rel="bibo:chapter" resource="#shared_blank_nodes" typeof="bibo:Chapter" class="informative"><h4 id="shared_blank_nodes"><span class="secno">5.1.1 </span>Shared blank nodes (Informative)</h4><p><em>This section is non-normative.</em></p>
 
 <p> The semantics for blank nodes are stated in terms of the truth of a graph. However, when two (or more) graphs share a blank node, their meaning is not fully captured by treating them in isolation. For example, consider the overlapping graphs</p>
 <p><img src="RDF11SemanticsDiagrams/example5.jpg" alt="Overlapping Graphs"></p>
@@ -562,7 +565,7 @@
 
 </section>
 </section>
-<section id="intuitive-summary-informative" class="informative">
+<section id="intuitive-summary-informative" rel="bibo:chapter" resource="#intuitions" typeof="bibo:Chapter" class="informative">
 <h3 id="intuitions" class="informative"><span class="secno">5.2 </span>Intuitive summary (Informative)</h3><p><em>This section is non-normative.</em></p>
 
 <p>An RDF graph is true exactly when:</p>
@@ -570,7 +573,7 @@
   
 </section>
 
-<section id="simpleentailment"><h3><span class="secno">5.3 </span>Simple Entailment</h3>
+<section rel="bibo:chapter" resource="#simpleentailment" typeof="bibo:Chapter" id="simpleentailment"><h3><span class="secno">5.3 </span>Simple Entailment</h3>
 
 <p>Following standard terminology, we say that I <dfn id="dfn-satisfies">satisfies</dfn> E when I(E)=true, that E is <dfn id="dfn-satisfiable">satisfiable</dfn> when an interpretation exists which satisfies it, (otherwise <dfn id="dfn-unsatisfiable">unsatisfiable</dfn>), and that a graph G <dfn id="dfn-simply-entails">simply entails</dfn> a graph E when every interpretation which satisfies G also satisfies E. </p>
 <p>In later sections these notions will be adapted to other classes of interpretations, but throughout this section 'entailment' should be interpreted as meaning simple entailment.
@@ -588,7 +591,7 @@
 
 </section>
 
-<section id="properties-of-simple-entailment-informative" class="informative">
+<section id="properties-of-simple-entailment-informative" rel="bibo:chapter" resource="#simple_entailment_properties" typeof="bibo:Chapter" class="informative">
 
 <h3 id="simple_entailment_properties"><span class="secno">5.4 </span>Properties of simple entailment (Informative) </h3><p><em>This section is non-normative.</em></p>    
 <p>The properties described here apply only to simple entailment, not to extended notions of entailment introduced in later sections. Proofs are given in Appendix C. </p>
@@ -642,7 +645,7 @@
 </section>
 </section>
 
-<section id="skolemization-informative" class="informative"><!--OddPage--><h2 id="skolemization"><span class="secno">6. </span>Skolemization (Informative)</h2><p><em>This section is non-normative.</em></p>
+<section id="skolemization-informative" rel="bibo:chapter" resource="#skolemization" typeof="bibo:Chapter" class="informative"><!--OddPage--><h2 id="skolemization"><span class="secno">6. </span>Skolemization (Informative)</h2><p><em>This section is non-normative.</em></p>
 <p><a class="externaldefinition">Skolemization</a> is a transformation on RDF graphs which eliminates blank nodes by replacing them with "new" IRIs, which means IRIs which are coined for this purpose and are therefore guaranteed to not occur in any other RDF graph (at the time of creation). See <a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Section 3.5</a> of [<cite><a href="#bib-RDF11-CONCEPTS" class="bibref">RDF11-CONCEPTS</a></cite>] for a fuller discussion. </p> 
 <p> Suppose G is a graph containing blank nodes and sk is a skolemization mapping from the blank nodes in G to the skolem IRIs which are substituted for them, so that sk(G) is a skolemization of G.  Then the semantic relationship between them can be summarized as follows. </p>
 
@@ -656,7 +659,7 @@
 
 </section>
 
-<section id="literals-and-datatypes"><!--OddPage--><h2 id="datatypes"><span class="secno">7. </span>Literals and datatypes</h2>
+<section id="literals-and-datatypes" rel="bibo:chapter" resource="#datatypes" typeof="bibo:Chapter"><!--OddPage--><h2 id="datatypes"><span class="secno">7. </span>Literals and datatypes</h2>
 <p class="changenote">  In the 2004 RDF 1.0 specification, datatype D-entailment was defined as a <a class="internalDFN" href="#dfn-semantic-extension">semantic extension</a> of RDFS-entailment. Here it is defined as a direct extension to basic RDF. This is more in conformity with actual usage, where RDF with datatypes is widely used without the RDFS vocabulary. If there is a need to distinguish this from the 2004 RDF 1.0 terminology, the longer phrasing "simple D-entailment" or "simple datatype entailment" should be used rather than "D-entailment". </p>
 
 <p> Datatypes are <a class="internalDFN" href="#dfn-identify" title="identify">identified</a> by IRIs. Interpretations will vary according to which IRIs they recognize as denoting datatypes. We describe this using a parameter D on interpretations. where D is the set of <dfn id="dfn-recognize">recognize</dfn><strong>d</strong> datatype IRIs. We assume that a recognized IRI <a class="internalDFN" href="#dfn-identify" title="identify">identifies</a> a unique datatype wherever it occurs, and the semantics requires that it refers to this identified datatype. The exact mechanism by which an IRI <a class="internalDFN" href="#dfn-identify" title="identify">identifies</a> a datatype IRI is considered to be external to the semantics. RDF processors which are not able to determine which datatype is identifier by an IRI cannot <a class="internalDFN" href="#dfn-recognize">recognize</a> that IRI, and should treat any literals type with that IRI as unknown names. </p>
@@ -673,7 +676,7 @@
 <p>RDF literal syntax allows any IRI to be used in a typed literal, even when it is not <a class="internalDFN" href="#dfn-recognize">recognize</a>d as referring to a datatype. Literals with such an "unknown" datatype IRI, which is not in the set of <a class="internalDFN" href="#dfn-recognize">recognize</a>d datatypes, <em title="SHOULD NOT" class="rfc2119">SHOULD NOT</em> be treated as errors, although RDF applications <em title="MAY" class="rfc2119">MAY</em> issue a warning. Such literals <em title="SHOULD" class="rfc2119">SHOULD</em> be treated like IRIs and assumed to denote some thing in the universe IR. RDF processors which fail to <a class="internalDFN" href="#dfn-recognize">recognize</a> a datatype IRI will not be able to detect some entailments which are visible to one which does.  For example, the fact that </p><p><code>ex:a ex:p "20.0000"^^xsd:decimal .</code></p><p>entails </p><p><code>ex:a ex:p "20.0"^^xsd:decimal .</code></p><p>will not be visible to a processor which does not <a class="internalDFN" href="#dfn-recognize">recognize</a> the datatype IRI <code>xsd:decimal</code>.</p>
 
 
-<section id="D_interpretations"><h3><span class="secno">7.1 </span>D-interpretations</h3>
+<section rel="bibo:chapter" resource="#D_interpretations" typeof="bibo:Chapter" id="D_interpretations"><h3><span class="secno">7.1 </span>D-interpretations</h3>
 <p>Let D be a set of IRIs <a class="internalDFN" href="#dfn-identify">identify</a>ing datatypes. A  <dfn id="dfn-simple-d-interpretation">(simple) D-interpretation</dfn> is a <a class="internalDFN" href="#dfn-simple-interpretation">simple interpretation</a>  which satisfies the following conditions:</p> 
 
 <div class="tabletitle">Semantic conditions for datatyped literals.</div>
@@ -700,7 +703,7 @@
 
 
 </section>
-<section id="datatype-entailment">
+<section id="datatype-entailment" rel="bibo:chapter" resource="#D_entailment" typeof="bibo:Chapter">
 <h3 id="D_entailment"><span class="secno">7.2 </span>Datatype entailment</h3>
 
 <p>A graph is (simply) <dfn id="dfn-d-satisfiable">D-satisfiable</dfn> or <dfn id="dfn-satisfiable-recognizing-d">satisfiable recognizing D</dfn> when it has the value true in some D-interpretation, and a graph S (simply) <dfn id="dfn-d-entails">D-entails</dfn> or <dfn id="dfn-entails-recognizing-d">entails recognizing D</dfn> a graph G when every D-interpretation which satisfies S also D-satisfies G.</p>
@@ -715,7 +718,7 @@
 
 
 
-<section id="patterns-of-datatype-entailment-informative" class="informative"> <h4 id="datatype_entailment_patterns"><span class="secno">7.2.1 </span>Patterns of datatype entailment (Informative)</h4><p><em>This section is non-normative.</em></p>
+<section id="patterns-of-datatype-entailment-informative" rel="bibo:chapter" resource="#datatype_entailment_patterns" typeof="bibo:Chapter" class="informative"> <h4 id="datatype_entailment_patterns"><span class="secno">7.2.1 </span>Patterns of datatype entailment (Informative)</h4><p><em>This section is non-normative.</em></p>
 <p>Unlike <a class="internalDFN" href="#dfn-simply-entails" title="simply entails">simple entailment</a>, it is not possible to give a single syntactic criterion to detect all D-entailments, which 
 can hold because of particular properties of the lexical-to-value mappings of the  <a class="internalDFN" href="#dfn-recognize">recognize</a>d datatypes. For example, if D contains <code>xsd:decimal</code> then </p>
 
@@ -739,7 +742,7 @@
 
 </section>
 </section>
-<section id="rdf-interpretations"><!--OddPage--><h2 id="rdf_d_interpretations"><span class="secno">8. </span>RDF Interpretations</h2>
+<section id="rdf-interpretations" rel="bibo:chapter" resource="#rdf_d_interpretations" typeof="bibo:Chapter"><!--OddPage--><h2 id="rdf_d_interpretations"><span class="secno">8. </span>RDF Interpretations</h2>
     <p>RDF interpretations impose extra semantic conditions on <code>xsd:string</code> and part of the infinite 
   set of IRIs with the namespace prefix <code>rdf:</code> .  
 
@@ -786,7 +789,7 @@
 <p>Two other datatypes <a href="http://www.w3.org/TR/rdf11-concepts/#section-XMLLiteral"><code>rdf:XMLLiteral</code></a> and <a href="http://www.w3.org/TR/rdf11-concepts/#section-html"><code>rdf:HTML</code></a> are defined in [<cite><a href="#bib-RDF11-CONCEPTS" class="bibref">RDF11-CONCEPTS</a></cite>]. RDF-D interpretations <em title="MAY" class="rfc2119">MAY</em> fail to <a class="internalDFN" href="#dfn-recognize">recognize</a> these datatypes. </p>
 
 
-<section id="rdf-entailment">
+<section id="rdf-entailment" rel="bibo:chapter" resource="#rdf_entail" typeof="bibo:Chapter">
 
 <h3 id="rdf_entail"><span class="secno">8.1 </span>RDF entailment</h3>
 
@@ -795,7 +798,7 @@
 <p>The properties of <a>simple entailment</a> described earlier do not all apply to <a class="internalDFN" href="#dfn-rdf-entail">RDF entail</a>ment. For example, all the RDF axioms are true in every <a class="internalDFN" href="#dfn-rdf-interpretation">RDF interpretation</a>, and so are <a class="internalDFN" href="#dfn-rdf-entail">RDF entail</a>ed by the empty graph, contradicting <a class="internalDFN" href="#dfn-interpolation">interpolation</a> for RDF entailment. </p>
 
 
-<section id="patterns-of-rdf-entailment-informative" class="informative"><h4 id="rdf_entailment_patterns"><span class="secno">8.1.1 </span>Patterns of RDF entailment (Informative)</h4><p><em>This section is non-normative.</em></p>
+<section id="patterns-of-rdf-entailment-informative" rel="bibo:chapter" resource="#rdf_entailment_patterns" typeof="bibo:Chapter" class="informative"><h4 id="rdf_entailment_patterns"><span class="secno">8.1.1 </span>Patterns of RDF entailment (Informative)</h4><p><em>This section is non-normative.</em></p>
 <p> The last semantic condition in the above table gives the following entailment pattern for <a class="internalDFN" href="#dfn-recognize">recognize</a>d datatype IRIs: </p> 
 
 <div class="tabletitle">RDF entailment pattern.</div> 
@@ -870,7 +873,7 @@
 </section>
 </section>
 </section>
-<section id="rdfs-interpretations"><!--OddPage--><h2 id="rdfs_interpretations"><span class="secno">9. </span>RDFS Interpretations</h2>
+<section id="rdfs-interpretations" rel="bibo:chapter" resource="#rdfs_interpretations" typeof="bibo:Chapter"><!--OddPage--><h2 id="rdfs_interpretations"><span class="secno">9. </span>RDFS Interpretations</h2>
 <p>RDF Schema [<cite><a href="#bib-RDF-SCHEMA" class="bibref">RDF-SCHEMA</a></cite>]
   extends RDF to a larger vocabulary 
   with more complex semantic constraints:</p>
@@ -1091,7 +1094,7 @@
 </tbody></table>
 
 <p>RDFS does not partition the universe into disjoint categories of classes, properties and individuals. Anything in the universe can be used as a class or as a property, or both, while retaining its status as an individual which may be in classes and have properties. Thus, RDFS permits classes which contain other classes, classes of properties, properties of classes, etc. As the axiomatic triples above illustrate, it also permits classes which contain themselves and properties which apply to themselves. A property of a class is not necessarily a property of its members, nor vice versa. </p>
-<section id="a-note-on-rdfs-literal-informative" class="informative">
+<section id="a-note-on-rdfs-literal-informative" rel="bibo:chapter" resource="#rdfs_literal_note" typeof="bibo:Chapter" class="informative">
 <h3 id="rdfs_literal_note"><span class="secno">9.1 </span>A note on rdfs:Literal (Informative)</h3><p><em>This section is non-normative.</em></p>
 <p>The class <code>rdfs:Literal</code> is not the class of literals, but rather that of literal values, which may also be referred to by IRIs. For example, LV does not contain the literal <code>"foodle"^^xsd:string</code> but it does contain the string "foodle".</p>
 
@@ -1103,7 +1106,7 @@
     than a literal. It says that the IRI '<code>ex:a</code>'
     refers to a literal value, which is quite possible since literal values are things in the universe. Blank nodes may range over literal values, for the same reason. </p>
 </section>
-<section id="rdfs-entailment">
+<section id="rdfs-entailment" rel="bibo:chapter" resource="#rdfs_entailment" typeof="bibo:Chapter">
 
 <h3 id="rdfs_entailment"><span class="secno">9.2 </span>RDFS entailment</h3>
 <p>S <dfn id="dfn-rdfs-entails">RDFS entails</dfn> E <strong>recognizing D</strong> when every <a class="internalDFN" href="#dfn-rdfs-interpretation">RDFS interpretation</a> recognizing D
@@ -1115,7 +1118,7 @@
 <p> aaa <code>rdf:type rdfs:Resource .</code></p>
 <p>where aaa is an IRI, are true in all RDFS interpretations.</p>
 
-<section id="patterns-of-rdfs-entailment-informative" class="informative"> <h4 id="rdfs_patterns"><span class="secno">9.2.1 </span>Patterns of RDFS entailment (Informative)</h4><p><em>This section is non-normative.</em></p>
+<section id="patterns-of-rdfs-entailment-informative" rel="bibo:chapter" resource="#rdfs_patterns" typeof="bibo:Chapter" class="informative"> <h4 id="rdfs_patterns"><span class="secno">9.2.1 </span>Patterns of RDFS entailment (Informative)</h4><p><em>This section is non-normative.</em></p>
 
 <p>RDFS entailment holds for all the following patterns, which correspond closely to the RDFS semantic conditions:</p>
 
@@ -1216,7 +1219,7 @@
 </section>
 </section>
 </section>
-<section id="rdf-datasets"><!--OddPage--><h2 id="rdf_datasets"><span class="secno">10. </span>RDF Datasets</h2>
+<section id="rdf-datasets" rel="bibo:chapter" resource="#rdf_datasets" typeof="bibo:Chapter"><!--OddPage--><h2 id="rdf_datasets"><span class="secno">10. </span>RDF Datasets</h2>
 
 <p>An RDF <a href="http://www.w3.org/TR/rdf11-concepts/#section-dataset" class="externalDFN">dataset</a> (see [<cite><a href="#bib-RDF11-CONCEPTS" class="bibref">RDF11-CONCEPTS</a></cite>]) is a finite set of RDF graphs each paired with an IRI or blank node called the <strong>graph name</strong>, plus a <strong>default graph</strong>, without a name. Graphs in a single dataset may share blank nodes. The association of graph name IRIs with graphs is used by SPARQL [<cite><a href="#bib-RDF-SPARQL-QUERY" class="bibref">RDF-SPARQL-QUERY</a></cite>] to allow queries to be directed against particular graphs.</p>
 
@@ -1233,7 +1236,7 @@
 
 <h2 id="appendices">Appendices</h2>
 
-<section id="entailment-rules-informative" class="informative appendix"><!--OddPage--><h2 id="entailment_rules"><span class="secno">A. </span>Entailment rules (Informative)</h2><p><em>This section is non-normative.</em></p>
+<section id="entailment-rules-informative" rel="bibo:chapter" resource="#entailment_rules" typeof="bibo:Chapter" class="informative appendix"><!--OddPage--><h2 id="entailment_rules"><span class="secno">A. </span>Entailment rules (Informative)</h2><p><em>This section is non-normative.</em></p>
 
 <p>(<em>This section is based on work described more fully in </em>[<cite><a href="#bib-HORST04" class="bibref">HORST04</a></cite>]<em>, </em>[<cite><a href="#bib-HORST05" class="bibref">HORST05</a></cite>]<em>, which should be consulted for technical details and proofs.</em>) </p>
 <p> The RDF and RDFS entailment patterns listed in the above tables can be viewed as left-to-right rules which add the entailed conclusion to a graph. These rule sets can be used to check RDF (or RDFS) entailment between graphs S and E, by the following sequence of operations:</p>
@@ -1334,7 +1337,7 @@
 
 </section>
  
-<section id="finite-interpretations-informative" class="informative appendix"><!--OddPage--><h2 id="finite_interpretations"><span class="secno">B. </span>Finite interpretations (Informative)</h2><p><em>This section is non-normative.</em></p>
+<section id="finite-interpretations-informative" rel="bibo:chapter" resource="#finite_interpretations" typeof="bibo:Chapter" class="informative appendix"><!--OddPage--><h2 id="finite_interpretations"><span class="secno">B. </span>Finite interpretations (Informative)</h2><p><em>This section is non-normative.</em></p>
 <p>To keep the exposition simple, the RDF semantics has been phrased in a way which requires interpretations to be larger than absolutely necessary. For example, all interpretations are required to interpret the whole IRI vocabulary, and the universes of all D-interpretations must contain all possible strings and therefore be infinite. This appendix sketches, without proof, how to re-state the semantics using smaller semantic structures, without changing any entailments. </p>
 
 <p>Basically, it is only necessary for an interpretation structure to interpret the <a class="internalDFN" href="#dfn-name">name</a>s actually used in the graphs whose entailment is being considered, and to consider interpretations whose universes are at most as big as the number of names and blank nodes in the graphs.  More formally, we can define a <dfn id="dfn-pre-interpretation">pre-interpretation</dfn> over a <a class="internalDFN" href="#dfn-vocabulary">vocabulary</a> V to be a structure I similar to a <a class="internalDFN" href="#dfn-simple-interpretation">simple interpretation</a> but with a mapping only from V to its universe IR.  Then when determining whether G entails E, consider only pre-interpretations over the finite vocabulary of <a class="internalDFN" href="#dfn-name">name</a>s actually used in G union E. The universe of such a pre-interpretation can be restricted to the cardinality N+B+1, where N is the size of the vocabulary and B is the number of blank nodes in the graphs. Any such pre-interpretation may be extended to <a class="internalDFN" href="#dfn-simple-interpretation">simple interpretation</a>s, all of which which will give the same truth values for any triples in G or E. Satisfiability, entailment and so on can then be defined with respect to these finite pre-interpretations, and shown to be identical to the ideas defined in the body of the specification.</p>
@@ -1346,7 +1349,7 @@
 </p></section>
 
 
-<section id="proofs-of-some-results-informative" class="informative appendix"><!--OddPage--><h2 id="proofs"><span class="secno">C. </span>Proofs of some results (Informative)</h2><p><em>This section is non-normative.</em></p>
+<section id="proofs-of-some-results-informative" rel="bibo:chapter" resource="#proofs" typeof="bibo:Chapter" class="informative appendix"><!--OddPage--><h2 id="proofs"><span class="secno">C. </span>Proofs of some results (Informative)</h2><p><em>This section is non-normative.</em></p>
 
 <p class="fact"> The <a class="internalDFN" href="#dfn-empty-graph">empty graph</a> is entailed by 
   any graph, and does not entail any graph except itself.
@@ -1391,7 +1394,7 @@
 </section>
 
 
-<section class="informative appendix" id="whatnot"><!--OddPage--><h2 id="non_semantics"><span class="secno">D. </span>RDF reification, containers and collections (Informative)</h2><p><em>This section is non-normative.</em></p>
+<section rel="bibo:chapter" resource="#whatnot" typeof="bibo:Chapter" class="informative appendix" id="whatnot"><!--OddPage--><h2 id="non_semantics"><span class="secno">D. </span>RDF reification, containers and collections (Informative)</h2><p><em>This section is non-normative.</em></p>
 
 <p>The RDF semantic conditions do not place formal constraints on the meaning 
   of much of the RDF vocabulary which is intended for use in describing containers and bounded collections, 
@@ -1403,7 +1406,7 @@
   processes to check formal RDF entailment. For example, implementations may decide 
   to use special procedural techniques to implement the RDF collection vocabulary.</p>
 
-<section id="reification">
+<section id="reification" rel="bibo:chapter" resource="#Reif" typeof="bibo:Chapter">
     
 <h3 id="Reif"><span class="secno">D.1 </span>Reification</h3><p><em>This section is non-normative.</em></p>
 
@@ -1482,7 +1485,7 @@
     <p><code>_:yyy ex:property ex:foo .</code></p>
 </section>
 
-<section id="rdf-containers">
+<section id="rdf-containers" rel="bibo:chapter" resource="#containers" typeof="bibo:Chapter">
     
 <h3 id="containers"><span class="secno">D.2 </span>RDF containers</h3>
 
@@ -1578,7 +1581,7 @@
     only finitely many members.</p>
 </section>
 
-<section id="rdf-collections">
+<section id="rdf-collections" rel="bibo:chapter" resource="#collections" typeof="bibo:Chapter">
     
 <h3 id="collections"><span class="secno">D.3 </span>RDF collections</h3>
 
@@ -1666,7 +1669,7 @@
 </section>
 
 
-    <section id="acknowledgements-1" class="informative appendix">
+    <section id="acknowledgements-1" rel="bibo:chapter" resource="#acknowledgements" typeof="bibo:Chapter" class="informative appendix">
       <!--OddPage--><h2 id="acknowledgements"><span class="secno">E. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
 
 <p>The basic idea of using an explicit extension mapping to allow self-application without violating the axiom of foundation was
@@ -1683,22 +1686,22 @@
     </section>
   
 
-<section class="appendix" id="references"><!--OddPage--><h2><span class="secno">F. </span>References</h2><section id="normative-references"><h3><span class="secno">F.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-OWL2-SYNTAX">[OWL2-SYNTAX]</dt><dd>Boris Motik; Peter F. Patel-Schneider; Bijan Parsia. <a href="http://www.w3.org/TR/owl2-syntax/"><cite>OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax</cite></a>. 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/owl2-syntax/">http://www.w3.org/TR/owl2-syntax/</a>
-</dd><dt id="bib-RDF-PLAIN-LITERAL">[RDF-PLAIN-LITERAL]</dt><dd>Jie Bao, Sandro Hawke, Boris Motik, Peter F. Patel-Schneider, Alex Polleres. <cite><a href="http://www.w3.org/TR/rdf-plain-literal/">rdf:PlainLiteral: A Datatype for RDF Plain Literals (Second Edition)</a></cite> 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-plain-literal/">http://www.w3.org/TR/rdf-plain-literal/</a>
-</dd><dt id="bib-RDF11-CONCEPTS">[RDF11-CONCEPTS]</dt><dd>Richard Cyganiak, David Wood. <cite><a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 15 January 2013. W3C Working Draft (work in progress). URL: <a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/">http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
-</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>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-TURTLE-TR">[TURTLE-TR]</dt><dd>David Beckett, Tim Berners-Lee, Eric Prud'hommeaux, Gavin Carothers. <cite><a href="http://www.w3.org/TR/turtle/">Turtle; Terse RDF Triple Language</a></cite> 19 February 2013. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
-</dd></dl></section><section id="informative-references"><h3><span class="secno">F.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-HORST04">[HORST04]</dt><dd>Herman J. ter Horst. <cite>Extending the RDFS Entailment Lemma</cite>, in S.A. McIlraith et al. (Eds.), The Semantic Web - ISWC2004, Proceedings of the Third International Semantic Web Conference, Hiroshima, Japan, November 2004, Springer, LNCS 3298, pp. 77-91.
-</dd><dt id="bib-HORST05">[HORST05]</dt><dd>Herman J. ter Horst. <cite>Completeness, Decidability and Complexity of Entailment for RDF Schema and a Semantic Extension Involving the OWL Vocabulary</cite>, Journal of Web Semantics 3 (2005) 79-115.
-</dd><dt id="bib-ISO24707">[ISO24707]</dt><dd><cite>Information technology — Common Logic (CL): a framework for a family of logic-based languages</cite> 1 October 2007. International Standard ISO/IEC 24707:2007(E). URL: <a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c039175_ISO_IEC_24707_2007%28E%29.zip"> http://standards.iso.org/ittf/PubliclyAvailableStandards/c039175_ISO_IEC_24707_2007%28E%29.zip</a>
-</dd><dt id="bib-OWL2-OVERVIEW">[OWL2-OVERVIEW]</dt><dd>W3C OWL Working Group. <a href="http://www.w3.org/TR/owl2-overview/"><cite>OWL 2 Web Ontology Language: Overview</cite></a>. 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/owl2-overview/">http://www.w3.org/TR/owl2-overview/</a>
-</dd><dt id="bib-OWL2-PROFILES">[OWL2-PROFILES]</dt><dd>Boris Motik; Bernardo Cuenca Grau; Ian Horrocks; Zhe Wu; Achille Fokoue; Carsten Lutz. <a href="http://www.w3.org/TR/owl2-profiles/"><cite>OWL 2 Web Ontology Language:Profiles</cite></a>. 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/owl2-profiles/">http://www.w3.org/TR/owl2-profiles/</a>
-</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd>Patrick Hayes. <a href="http://www.w3.org/TR/rdf-mt/"><cite>RDF Semantics</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-mt/">http://www.w3.org/TR/rdf-mt/</a>
-</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd>Dan Brickley; Ramanathan V. Guha. <a href="http://www.w3.org/TR/rdf-schema/"><cite>RDF Vocabulary Description Language 1.0: RDF Schema</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-schema/">http://www.w3.org/TR/rdf-schema/</a>
-</dd><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd>Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/rdf-sparql-query/"><cite>SPARQL Query Language for RDF</cite></a>. 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-sparql-query/">http://www.w3.org/TR/rdf-sparql-query/</a>
-</dd><dt id="bib-RDF-TESTCASES">[RDF-TESTCASES]</dt><dd>Jan Grant; Dave Beckett. <a href="http://www.w3.org/TR/rdf-testcases/"><cite>RDF Test Cases</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-testcases/">http://www.w3.org/TR/rdf-testcases/</a>
-</dd><dt id="bib-RIF-OVERVIEW">[RIF-OVERVIEW]</dt><dd>Michael Kifer; Harold Boley. <a href="http://www.w3.org/TR/rif-overview/"><cite>RIF Overview</cite></a>. 22 June 2010. W3C Working Group Note. URL: <a href="http://www.w3.org/TR/rif-overview/">http://www.w3.org/TR/rif-overview/</a>
-</dd><dt id="bib-SWBP-XSCH-DATATYPES">[SWBP-XSCH-DATATYPES]</dt><dd>Jeremy J. Carroll; Jeff Z. Pan. <a href="http://www.w3.org/TR/swbp-xsch-datatypes/"><cite>XML Schema Datatypes in RDF and OWL</cite></a>. 14 March 2006. W3C Note. URL: <a href="http://www.w3.org/TR/swbp-xsch-datatypes/">http://www.w3.org/TR/swbp-xsch-datatypes/</a>
-</dd><dt id="bib-XML10">[XML10]</dt><dd>C. M. Sperberg-McQueen et al. <a href="http://www.w3.org/TR/xml/"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition)</cite></a>. 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xml/">http://www.w3.org/TR/xml/</a>
-</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd>Henry S. Thompson et al. <a href="http://www.w3.org/TR/xmlschema11-2/"><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/xmlschema11-2/">http://www.w3.org/TR/xmlschema11-2/</a>
-</dd></dl></section></section></body></html>
+<section rel="bibo:chapter" resource="#references" typeof="bibo:Chapter" class="appendix" id="references"><!--OddPage--><h2><span class="secno">F. </span>References</h2><section rel="bibo:chapter" resource="#normative-references" typeof="bibo:Chapter" id="normative-references"><h3><span class="secno">F.1 </span>Normative references</h3><dl about="" class="bibliography"><dt id="bib-OWL2-SYNTAX">[OWL2-SYNTAX]</dt><dd rel="dcterms:requires">Boris Motik; Peter Patel-Schneider; Bijan Parsia. <a href="http://www.w3.org/TR/owl2-syntax/"><cite>OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax (Second Edition)</cite></a>. 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/owl2-syntax/">http://www.w3.org/TR/owl2-syntax/</a>
+</dd><dt id="bib-RDF-PLAIN-LITERAL">[RDF-PLAIN-LITERAL]</dt><dd rel="dcterms:requires">Jie Bao, Sandro Hawke, Boris Motik, Peter F. Patel-Schneider, Alex Polleres. <cite><a href="http://www.w3.org/TR/rdf-plain-literal/">rdf:PlainLiteral: A Datatype for RDF Plain Literals (Second Edition)</a></cite> 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-plain-literal/">http://www.w3.org/TR/rdf-plain-literal/</a>
+</dd><dt id="bib-RDF11-CONCEPTS">[RDF11-CONCEPTS]</dt><dd rel="dcterms:requires">Richard Cyganiak, David Wood. <cite><a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130723/">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 23 July 2013. W3C Last Call Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-rdf11-concepts-20130723/">http://www.w3.org/TR/2013/WD-rdf11-concepts-20130723/</a>. The latest edition is available at <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</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-TURTLE-CR">[TURTLE-CR]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux, Gavin Carothers. <cite><a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">Turtle; Terse RDF Triple Language</a></cite>. 19 February 2013. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>. The latest edition is available at <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
+</dd></dl></section><section rel="bibo:chapter" resource="#informative-references" typeof="bibo:Chapter" id="informative-references"><h3><span class="secno">F.2 </span>Informative references</h3><dl about="" class="bibliography"><dt id="bib-HORST04">[HORST04]</dt><dd rel="dcterms:references">Herman J. ter Horst. <cite>Extending the RDFS Entailment Lemma</cite>, in S.A. McIlraith et al. (Eds.), The Semantic Web - ISWC2004, Proceedings of the Third International Semantic Web Conference, Hiroshima, Japan, November 2004, Springer, LNCS 3298, pp. 77-91.
+</dd><dt id="bib-HORST05">[HORST05]</dt><dd rel="dcterms:references">Herman J. ter Horst. <cite>Completeness, Decidability and Complexity of Entailment for RDF Schema and a Semantic Extension Involving the OWL Vocabulary</cite>, Journal of Web Semantics 3 (2005) 79-115.
+</dd><dt id="bib-ISO24707">[ISO24707]</dt><dd rel="dcterms:references"><cite>Information technology — Common Logic (CL): a framework for a family of logic-based languages</cite> 1 October 2007. International Standard ISO/IEC 24707:2007(E). URL: <a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c039175_ISO_IEC_24707_2007%28E%29.zip"> http://standards.iso.org/ittf/PubliclyAvailableStandards/c039175_ISO_IEC_24707_2007%28E%29.zip</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/owl2-overview/"><cite>OWL 2 Web Ontology Language Document Overview (Second Edition)</cite></a>. 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/owl2-overview/">http://www.w3.org/TR/owl2-overview/</a>
+</dd><dt id="bib-OWL2-PROFILES">[OWL2-PROFILES]</dt><dd rel="dcterms:references">Boris Motik; Bernardo Cuenca Grau; Ian Horrocks; Zhe Wu; Achille Fokoue. <a href="http://www.w3.org/TR/owl2-profiles/"><cite>OWL 2 Web Ontology Language Profiles (Second Edition)</cite></a>. 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/owl2-profiles/">http://www.w3.org/TR/owl2-profiles/</a>
+</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd rel="dcterms:references">Patrick Hayes. <a href="http://www.w3.org/TR/rdf-mt/"><cite>RDF Semantics</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-mt/">http://www.w3.org/TR/rdf-mt/</a>
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd rel="dcterms:references">Dan Brickley; Ramanathan Guha. <a href="http://www.w3.org/TR/rdf-schema"><cite>RDF Vocabulary Description Language 1.0: RDF Schema</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-schema">http://www.w3.org/TR/rdf-schema</a>
+</dd><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd rel="dcterms:references">Eric Prud'hommeaux; Andy Seaborne. <a href="http://www.w3.org/TR/rdf-sparql-query/"><cite>SPARQL Query Language for RDF</cite></a>. 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-sparql-query/">http://www.w3.org/TR/rdf-sparql-query/</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/rdf-testcases"><cite>RDF Test Cases</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-testcases">http://www.w3.org/TR/rdf-testcases</a>
+</dd><dt id="bib-RIF-OVERVIEW">[RIF-OVERVIEW]</dt><dd rel="dcterms:references">Michael Kifer; Harold Boley. <a href="http://www.w3.org/TR/rif-overview/"><cite>RIF Overview (Second Edition)</cite></a>. 5 February 2013. W3C Note. URL: <a href="http://www.w3.org/TR/rif-overview/">http://www.w3.org/TR/rif-overview/</a>
+</dd><dt id="bib-SWBP-XSCH-DATATYPES">[SWBP-XSCH-DATATYPES]</dt><dd rel="dcterms:references">Jeremy Carroll; Jeff Pan. <a href="http://www.w3.org/TR/swbp-xsch-datatypes"><cite>XML Schema Datatypes in RDF and OWL</cite></a>. 14 March 2006. W3C Note. URL: <a href="http://www.w3.org/TR/swbp-xsch-datatypes">http://www.w3.org/TR/swbp-xsch-datatypes</a>
+</dd><dt id="bib-XML10">[XML10]</dt><dd rel="dcterms:references">Tim Bray; Jean Paoli; Michael Sperberg-McQueen; Eve Maler; François Yergeau et al. <a href="http://www.w3.org/TR/xml"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition)</cite></a>. 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/xml">http://www.w3.org/TR/xml</a>
+</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd rel="dcterms:references">David Peterson; Sandy Gao; Ashok Malhotra; Michael Sperberg-McQueen; Henry Thompson; Paul V. Biron et al. <a href="http://www.w3.org/TR/xmlschema11-2/"><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/xmlschema11-2/">http://www.w3.org/TR/xmlschema11-2/</a>
+</dd></dl></section></section></body></html>
\ No newline at end of file