change refs from rdf-mt to rdf11-mt, add sotd about lack of impl rept
authorSandro Hawke <sandro@hawke.org>
Tue, 05 Nov 2013 07:15:34 -0500
changeset 1211 e2253ada36a1
parent 1210 c5f25c79614f
child 1212 9935ca65012b
child 1214 8dbe9af2d96b
change refs from rdf-mt to rdf11-mt, add sotd about lack of impl rept
rdf-concepts/index.html
--- a/rdf-concepts/index.html	Mon Nov 04 15:16:18 2013 -0800
+++ b/rdf-concepts/index.html	Tue Nov 05 07:15:34 2013 -0500
@@ -141,6 +141,8 @@
       <li><a href="#at-risk-xmlliteral">The <code>rdf:XMLLiteral</code> datatype may be made non-normative</a></li>
     </ul>
 
+    <p>This document is a part of the RDF 1.1 document suite.  The RDF Working Group welcomes comments and reports of implementations in general, but given the nature of this document (as a conceptual overview), the group not expecting to track implementations of this document on its own.</p>
+ 
   </section>
 </div>
 
@@ -200,7 +202,7 @@
     <dfn title="resource">resources</dfn>. Anything can be a resource,
     including physical things, documents, abstract concepts, numbers
     and strings; the term is synonymous with "entity" as it is used in
-		the RDF Semantics specification [[RDF-MT]].
+		the RDF Semantics specification [[RDF11-MT]].
     The resource denoted by an IRI is called its <a>referent</a>, and the
     resource denoted by a literal is called its
     <a title="literal value">literal value</a>. Literals have
@@ -411,7 +413,7 @@
     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.   The precise details of this meaning of RDF triples and graphs are
-    the subject of the RDF Semantics specification [[RDF-MT]], which yields the
+    the subject of the RDF Semantics specification [[RDF11-MT]], which yields the
     following relationships between <a>RDF graph</a>s:</p>
 
     <dl>
@@ -435,7 +437,7 @@
     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>entailment regime</dfn> [[RDF11-MT]] 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
@@ -1234,7 +1236,7 @@
     <p class="note">Semantic extensions of RDF might choose to
 		recognize other datatype IRIs
     and require them to refer to a fixed datatype.  See the RDF
-		Semantics specification [[RDF-MT]] for more information on
+		Semantics specification [[RDF11-MT]] for more information on
 		semantic extensions.</p>
 
     <p>RDF processors are not required to recognize datatype IRIs.
@@ -1553,7 +1555,7 @@
     <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-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 datatype map, both adapted from previous content in [[RDF-MT]]
+    <li>2011-11-20: Added table of <a>RDF-compatible XSD types</a>, and definition of datatype map, both adapted from previous content in [[RDF11-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-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>