--- a/rdf-concepts/index.html Mon Dec 16 16:44:49 2013 +0100
+++ b/rdf-concepts/index.html Mon Dec 16 17:05:09 2013 +0100
@@ -136,16 +136,10 @@
</section>
<section id="sotd">
-
- <p>The following features are at risk and may be changed from normative to non-normative:</p>
-
- <ul>
- <li><a href="#at-risk-html">The <code>rdf:HTML</code> datatype may be made non-normative</a></li>
- <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>
-
+ <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 is not
+ expecting to track implementations of this document on its own.</p>
</section>
</div>
@@ -887,8 +881,7 @@
[[!XMLSCHEMA11-2]]. Any datatype definition that conforms
to this abstraction MAY 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,
+ built-in datatypes, and defines two additional non-normative datatypes,
<code><a>rdf:HTML</a></code> and <code><a>rdf:XMLLiteral</a></code>.
The list of datatypes supported by an implementation is determined
by its <a>recognized datatype IRIs</a>.</p>
@@ -1064,142 +1057,117 @@
</section>
-<section id="section-html">
+<section id="section-html" class="informative">
<h3>The <code>rdf:HTML</code> Datatype</h3>
- <div class="issue atrisk" id="at-risk-html">
- <p>The <code>rdf:HTML</code> datatype is at risk of being changed from normative to non-normative
- because the definitions in [[DOM4]] and thus the lexical-to-value mapping are not yet stable.
- Consequently interoperability can not be guaranteed at this point in time. Please send feedback
- to <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a>.</p>
- </div>
-
<p>RDF provides for HTML content as a possible <a>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>.
- This datatype is defined as follows:</p>
+ 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 set to <code><dfn>rdf:HTML</dfn></code>. This datatype is defined
+ as follows:</p>
<dl>
- <dt>An IRI 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>
-
- <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
- <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>
+ <dt>The IRI denoting this datatype</dt>
+ <dd>is <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#HTML</code>.</dd>
- <dt>The lexical-to-value mapping</dt>
- <dd>
- <p>Each member of the lexical space is associated with the result
- 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]]
- that result from applying the
- <a href="http://www.w3.org/TR/html5/syntax.html#parsing-html-fragments">HTML fragment parsing algorithm</a> [[!HTML5]]
- to the input string, without a context element.</li>
- <li>Let <code>domfrag</code> be a DOM
+ <dt>The lexical space</dt>
+ <dd>is the set of Unicode [[UNICODE]] 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>
- [[!DOM4]] 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>
- </dd>
+ nodes [[DOM4]]. 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>
+
+ <dt>The lexical-to-value mapping</dt>
+ <dd>
+ <p>Each member of the lexical space is associated with the result
+ 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]]
+ that result from applying the
+ <a href="http://www.w3.org/TR/html5/syntax.html#parsing-html-fragments">HTML fragment parsing algorithm</a> [[HTML5]]
+ 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 <code>domnodes</code></li>
+ <li>Return <code>domfrag.<a href="http://www.w3.org/TR/dom/#dom-node-normalize">normalize</a>()</code></li>
+ </ul>
+ </dd>
</dl>
<p class="note" id="note-html">
- Any language annotation (<code>lang="…"</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
- base URL and are best avoided.
- RDF applications may use additional equivalence relations,
- 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>
+ Any language annotation (<code>lang="…"</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
+ base URL and are best avoided.
+ RDF applications may use additional equivalence relations,
+ 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>
-<section id="section-XMLLiteral">
+<section id="section-XMLLiteral" class="informative">
<h3>The <code>rdf:XMLLiteral</code> Datatype</h3>
- <div class="issue atrisk" id="at-risk-xmlliteral">
- <p>The <code>rdf:XMLLiteral</code> datatype is at risk of being changed from normative to non-normative
- because the definitions in [[DOM4]] and thus the lexical-to-value mapping are not yet stable.
- Consequently interoperability can not be guaranteed at this point in time. Please send feedback
- to <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a>.</p>
- </div>
-
<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>
+ Such content is indicated in an <a>RDF graph</a> using a <a>literal</a>
+ whose <a>datatype</a> is set to <code><dfn>rdf:XMLLiteral</dfn></code>.
+ This datatype is defined as follows:</p>
<dl>
- <dt id="XMLLiteral-uri">An IRI denoting this <a>datatype</a></dt>
-
- <dd>is
- <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>.</dd>
+ <dt id="XMLLiteral-uri">The IRI denoting this <a>datatype</a></dt>
+ <dd>is <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>.</dd>
<dt id="XMLLiteral-lexical-space">The <a>lexical space</a></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
- 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>
+ <a href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">XML content</a>
+ [[XML10]]; 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>
<dt id="XMLLiteral-value-space">The <a>value space</a></dt>
-
- <dd>is a set of DOM
- <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
- nodes [[!DOM4]]. 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>
+ <dd>is a set of DOM
+ <a href="http://www.w3.org/TR/dom/#interface-documentfragment"><code>DocumentFragment</code></a>
+ nodes [[DOM4]]. 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 <a>lexical-to-value mapping</a></dt>
-
<dd>
- <p>Each member of the lexical space is associated with the result
- of applying the following algorithm:</p>
- <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>
- <li>Return <code>domfrag.<a href="http://www.w3.org/TR/dom/#dom-node-normalize">normalize</a>()</code></li>
- </ul></dd>
+ <p>Each member of the lexical space is associated with the result of applying the following algorithm:</p>
+ <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>
+ <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</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.
- 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]].
+ <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. 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]].</dd>
+ </dl>
- </dl>
-
- <p class="note">Any XML namespace declarations (<code>xmlns</code>),
- language annotation (<code>xml:lang</code>) or base URI
- 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>
+ <p class="note">Any XML namespace declarations (<code>xmlns</code>),
+ language annotation (<code>xml:lang</code>) or base URI 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>
@@ -1388,6 +1356,7 @@
<a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">5 November 2013 Candidate Recommendation (CR)</a>.</p>
<ul>
+ <li>2013-12-16: Make <code>rdf:HTML</code> and <code>rdf:XMLLiteral</code> non-normative</li>
<li>2013-12-16: Update acknowledgments</li>
<li>2013-12-12: Editorial changes in response to a review by
<a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Dec/0084.html">Thomas Baker</a></li>