--- a/rdf-mt/index.html Fri Mar 01 10:43:33 2013 -0600
+++ b/rdf-mt/index.html Fri Mar 01 13:32:16 2013 -0600
@@ -5,12 +5,12 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <title>RDF 1.1 Semantics Editor's Draft</title>
+ <title>RDF 1.1 Semantics Editors Draft</title>
<style type="text/css">
.figure { text-align: center; }
.figure a[href]:hover { background: transparent; }
table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
-
+font-family: sans-serif
/*<![CDATA[*/
code {font-family: monospace }
a.termref:visited, a.termref:link {font-family: sans-serif;
@@ -539,7 +539,7 @@
<body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"></a></p>
<h1 property="dcterms:title" class="title" id="title">RDF 1.1 Semantics</h1>
-<h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-02-28T00:00:00+0000" id="w3c-working-draft-28-february-2013"> Editors Working Draft 28 February 2013</h2><dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html">https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html</a></dd><dt>Latest published version:</dt><dd><a href=""></a></dd><dt>Latest editor's draft:</dt><dd><a href=""></a></dd>
+<h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-03-01T00:00:00+0000" id="w3c-working-draft-1-March-2013"> Editors Working Draft 1 March 2013</h2><dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html">https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html</a></dd><dt>Latest published version:</dt><dd><a href=""></a></dd><dt>Latest editor's draft:</dt><dd><a href=""></a></dd>
<dt>Previous version:</dt><dd><a rel="dcterms:replaces" href=""></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 rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Patrick Hayes" href="http://www.ihmc.us/groups/phayes/">Patrick Hayes</a>, <a rel="foaf:workplaceHomepage" href="http://www.ihmc.us/index.php">Florida IHMC</a></span>
</dd>
<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Peter F. Patel-Schneider" href="////">Peter F. Patel-Schneider</a>, <a rel="foaf:workplaceHomepage" href="////">////</a></span>
@@ -882,9 +882,9 @@
<p>Ill-typed literals are the only form of simple D-contradiction, but datatypes can give rise to a variety of other contradictions when combined with the RDFS vocabulary, defined later.</p>
-<h3><a name="RDFINTERP" id="RDFINTERP">3.1 RDF Interpretations</a></h3>
+<h3><a name="RDFINTERP" id="RDFINTERP">3.1 RDF-D Interpretations</a></h3>
- <p ><a name="defRDFV" id="defRDFV"></a>RDF interpretations impose extra semantic conditions on <code>xsd:string</code> and part of the infinite
+ <p ><a name="defRDFV" id="defRDFV"></a>RDF-D interpretations impose extra semantic conditions on <code>xsd:string</code> and part of the infinite
set of IRIs in the <code>rdf:</code> namespace.
<p> <a id="rdfinterpdef" name="rdfinterpdef"></a>An <i>rdf-D-interpretation</i>
@@ -926,6 +926,16 @@
<p>No other semantic constraints are imposed upon rdf-D-interpretations, so RDF imposes no particular normative meanings on the rest of the RDF vocabulary. Some consequences of this are discussed in Appendix ///</p>
+<p> The last condition gives entailments of this form for recognized datatypes: </p>
+
+<p><code>aaa ppp "nnn"^^xsd:number .</code></p>
+
+<p>rdf-{<code>xsd:number</code>}-entails</p>
+
+<code>aaa ppp _:x . <br/> _:x rdf:type xsd:number .</code>
+
+</p>
+
<p>An <em>rdf-interpretation</em>, or <em>RDF interpretation</em>, is an rdf-{<code>rdf:langString</code>, <code>xsd:string</code> }-interpretation, i.e. an rdf-D-Interpretation with a minimal set D. The datatypes <code>rdf:langString</code> and <code>xsd:string</code> must be recognized by all RDF interpretations. </p><p>The RDF built-in datatypes <code>rdf:XMLLiteral</code> and <code>rdf:HTML</code> are defined in ///RDF Concepts///. RDF interpretations are not required to recognize these datatypes. </p>
<h3><a name="rdf_entail" id="rdf_entail"></a>RDF entailment</h3>
@@ -1129,17 +1139,7 @@
<p>Since I is an <a href="#rdfinterpdef" class="termref">rdf-interpretation</a>, the first condition implies that IP
= ICEXT(I(<code>rdf:Property</code>)).</p>
- <p>The semantic conditions on rdf-D-interpretations, together with the RDFS conditions on ICEXT, mean that every recognized datatype can be treated as an RDFS class, whose extension contains all the datatype values which are in the range of the datatype L2V mapping: ICEXT(I(aaa)) = { x : x = L2V(I(aaa))(sss) } for some string sss, when aaa is a datatype IRI in D. This produces a number of intuitive entailments, for example </p>
-
-<p><code>aaa ppp "nnn"^^xsd:number .</code></p>
-
-<p>rdfs-{<code>xsd:number</code>}-entails</p>
-
-<code>aaa ppp _:x . <br/> _:x rdf:type xsd:number .</code>
-
-</p>
-<p class="issue"> Why wouldn't this be an RDF-D-entailment? After all, it only uses terms in the RDF namespace. In general, the RDF/RDFS distinction seems to be somewhat muddled. </p>
-
+ <p>The semantic conditions on rdf-D-interpretations, together with the RDFS conditions on ICEXT, mean that every recognized datatype can be treated as an RDFS class, whose extension contains all the datatype values which are in the range of the datatype L2V mapping: ICEXT(I(aaa)) = { x : x = L2V(I(aaa))(sss) } for some string sss, when aaa is a datatype IRI in D. </p>
<p>These axioms and conditions have some redundancy. For example, all but one
of the RDF axiomatic triples can be derived from the RDFS axiomatic triples
and the semantic conditions on ICEXT,<code> rdfs:domain</code> and <code>rdfs:range</code>.