- From: Manu Sporny via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 05 May 2010 03:47:18 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/rdfa
In directory hutz:/tmp/cvs-serv4663
Modified Files:
Overview-src.html Overview.html
Log Message:
Checking in current version of HTML+RDFa ED after clearing bug queue.
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- Overview.html 3 May 2010 00:52:54 -0000 1.22
+++ Overview.html 5 May 2010 03:47:16 -0000 1.23
@@ -45,7 +45,7 @@
span.entity { color: red; }
span.element { color: green; }
-</style><link href="http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" 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 class="title" id="title">HTML+RDFa 1.1</h1><h2 id="subtitle">Support for RDFa in HTML4 and HTML5</h2><h2 id="w3c-editor-s-draft-02-may-2010"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 02 May 2010</h2><dl><dt>This version:</dt><dd><a href="http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/">http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/rdfa-in-html/">http://www.w3.org/TR/rdfa-in-html/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-tml-20100502/">http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-rdfa-in-html-20100304/">http://www.w3.org/TR/2010/WD-rdfa-in-html-20100304/</a></dd><dt>Editors:</dt><dd><a href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, <a href="http://blog.digitalbazaar.com">Digital Bazaar, Inc.</a></dd><dd><a href="mailto:shane@aptest.com">Shane McCarron</a>, <a href="http://www.aptest.com/">Applied Testing and Technology, Inc.</a></dd><dt>Authors:</dt><dd>Ben Adida, <a href="http://">Creative Commons</a></dd><dd>Mark Birbeck, <a href="http://">Web Backplane Ltd.</a></dd><dd>Steven Pemberton, <a href="http://">CWI</a></dd></dl><p>This document is also available in these non-normative formats: <a href="html-rdfa.ps">Postscript version</a> and <a href="html-rdfa.pdf">PDF version</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009-2010 <a href="http://www.w3.org/">acronym title="World Wide Web Consortium"><acronym title="World Wide Web Consortium">W3C</acronym></acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology"><acronym title="Massachusetts Institute of Technology">MIT</acronym></acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></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>
+</style><link href="http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" 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 class="title" id="title">HTML+RDFa 1.1</h1><h2 id="subtitle">Support for RDFa in HTML4 and HTML5</h2><h2 id="w3c-editor-s-draft-04-may-2010"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 04 May 2010</h2><dl><dt>This version:</dt><dd><a href="http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/">http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/rdfa-in-html/">http://www.w3.org/TR/rdfa-in-html/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-tml-20100502/">http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-rdfa-in-html-20100304/">http://www.w3.org/TR/2010/WD-rdfa-in-html-20100304/</a></dd><dt>Editors:</dt><dd><a href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, <a href="http://blog.digitalbazaar.com">Digital Bazaar, Inc.</a></dd><dd><a href="mailto:shane@aptest.com">Shane McCarron</a>, <a href="http://www.aptest.com/">Applied Testing and Technology, Inc.</a></dd><dt>Authors:</dt><dd>Ben Adida, <a href="http://">Creative Commons</a></dd><dd>Mark Birbeck, <a href="http://">Web Backplane Ltd.</a></dd><dd>Steven Pemberton, <a href="http://">CWI</a></dd></dl><p>This document is also available in these non-normative formats: <a href="html-rdfa.ps">Postscript version</a> and <a href="html-rdfa.pdf">PDF version</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009-2010 <a href="http://www.w3.org/">acronym title="World Wide Web Consortium"><acronym title="World Wide Web Consortium">W3C</acronym></acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology"><acronym title="Massachusetts Institute of Technology">MIT</acronym></acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></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"><h2>Abstract</h2>
@@ -72,8 +72,7 @@
<li>Inclusion of the HTML Default Vocabulary Terms, which mirror the XHTML
Default Vocabulary Terms, for the purpose of HTML/XHTML interoperability.</li>
<li>Inclusion of a HTML 4.01 + RDFa 1.1 DTD for validation purposes.</li>
-<li>All bugs concerning HTML+RDFa have been addressed in the HTML WG bug
-tracker.</li>
+<li>Added normative definition of @version attribute.</li>
</ol>
<p>The latest stable version of the editor's draft of this specification is
@@ -98,7 +97,7 @@
A community-maintained
<a href="http://rdfa.info/rdfa-implementations/">Wiki page</a> includes
subsequent updates.</p>
-<p>This document was published by the <a href="http://www.w3.org/html/wg">HTML Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-rdfa-wg@w3.org">public-rdfa-wg@w3.org</a> (<a href="mailto:public-rdfa-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdfa-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Editor's 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/40318/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" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a><ul class="toc"><li class="tocline"><a hrf="#document-conformance" class="tocxref"><span class="secno">2.1 </span>Document Conformance</a></li><li class="tocline"><a href="#user-agent-conformance" class="tocxref"><span class="secno">2.2 </span>User Agent Conformance</a></li><li class="tocline"><a href="#rdfa-processor-conformance" class="tocxref"><span class="secno">2.3 </span>RDFa Processor Conformance</a></li></ul></li><li class="tocline"><a href="#extensions-to-rdfa-core-1.1" class="tocxref"><span class="secno">3. </span>Extensions to RDFa Core 1.1</a><ul class="toc"><li class="tocline"><a href="#additional-rdfa-processing-rules" class="tocxref"><span class="secno">3.1 </span>Additional RDFa Processing Rules</a></li><li class="tocline"><a href="#specifying-the-language-for-a-literal" class="tocxref"><span class="secno">3.2 </span>Specifying the language for a literal</a></li><li class="tocline"><a href="#invalid-xmlliteral-values" class="tocxref"><span class="secno">3.3 </span>Invalid XMLLiteral values</a></li><li class="tocline"><a href="#xmln--prefixed-attributes" class="tocxref"><span class="secno">3.4 </span><code>xmlns:</code>-Prefixed Attributes</a></li></ul></li><li class="tocline"><a href="#extensions-to-the-html5-syntax" class="tocxref"><span class="secno">4. </span>Extensions to the HTML5 Syntax</a><ul class="toc"><li class="tocline"><a href="#the-rdfa-attributes-and-valid-values" class="tocxref"><span class="secno">4.1 </span>The RDFa Attributes and Valid Values</a></li><li class="tocline"><a href="#conformance-criteria-for-xmlns--prefixed-attributes" class="tocxref"><span class="secno">4.2 </span>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</a></li><li class="tocline"><a href="#preserving-namespaces-via-coercion-to-infoset" class="tocxref"><span class="secno">4.3 </span>Preserving Namespaces via Coercion to Infoset</a></li><li class="tocline"><a href="#infoset-based-processors" class="tocxref"><span class="secno">4.4 </span>Infoset-based Processors</a><ul class="toc"><li class="tocline"><a href="#processing-namespaed-rdfa-attributes" class="tocxref"><span class="secno">4.4.1 </span>Processing Namespaced RDFa Attributes</a></li><li class="tocline"><a href="#processing-rdfa-attributes" class="tocxref"><span class="secno">4.4.2 </span>Processing RDFa Attributes</a></li></ul></li><li class="tocline"><a href="#dom-level-2-based-processors" class="tocxref"><span class="secno">4.5 </span>DOM Level 2-based Processors</a><ul class="toc"><li class="tocline"><a href="#processing-namespaced-rdfa-attributes-1" class="tocxref"><span class="secno">4.5.1 </span>Processing Namespaced RDFa Attributes</a></li><li class="tocline"><a href="#processing-rdfa-attributes-1" class="tocxref"><span class="secno">4.5.2 </span>Processing RDFa Attributes</a></li></ul></li></ul></li><li class="tocline"><a href="#html-default-vocabulary-terms" class="tocxref"><span class="secno">A. </span>HTML Default Vocabulary Terms</a></li><li class="tocline"><a href="#validation" class="tocxref"><span class="secno">B. </span>Validation</a><ul class="toc"><li clas="tocline"><a href="#the-html-4.01---rdfa-1.1-dtd" class="tocxref"><span class="secno">B.1 </span>The HTML 4.01 + RDFa 1.1 DTD</a></li></ul></li><li class="tocline"><a href="#about-this-document" class="tocxref"><span class="secno">C. </span>About this Document</a><ul class="toc"><li class="tocline"><a href="#history" class="tocxref"><span class="secno">C.1 </span>History</a></li><li class="tocline"><a href="#change-history" class="tocxref"><span class="secno">C.2 </span>Change History</a></li><li class="tocline"><a href="#acknowledgments" class="tocxref"><span class="secno">C.3 </span>Acknowledgments</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul><div>
+<p>This document was published by the <a href="http://www.w3.org/html/wg">HTML Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-rdfa-wg@w3.org">public-rdfa-wg@w3.org</a> (<a href="mailto:public-rdfa-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdfa-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Editor's 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/40318/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" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a><ul class="toc"><li class="tocline"><a hrf="#document-conformance" class="tocxref"><span class="secno">2.1 </span>Document Conformance</a></li><li class="tocline"><a href="#rdfa-processor-conformance" class="tocxref"><span class="secno">2.2 </span>RDFa Processor Conformance</a></li><li class="tocline"><a href="#user-agent-conformance" class="tocxref"><span class="secno">2.3 </span>User Agent Conformance</a></li></ul></li><li class="tocline"><a href="#extensions-to-rdfa-core-1.1" class="tocxref"><span class="secno">3. </span>Extensions to RDFa Core 1.1</a><ul class="toc"><li class="tocline"><a href="#additional-rdfa-processing-rules" class="tocxref"><span class="secno">3.1 </span>Additional RDFa Processing Rules</a></li><li class="tocline"><a href="#modifying-the-input-document" class="tocxref"><span class="secno">3.2 </span>Modifying the Input Document</a></li><li class="tocline"><a href="#specifying-the-language-for-a-literal" class="tocxref"><span class="secno">3.3 </span>Specifying the language for a literal</a></li><li class="tocline"><a href=#invalid-xmlliteral-values" class="tocxref"><span class="secno">3.4 </span>Invalid XMLLiteral values</a></li><li class="tocline"><a href="#xmlns--prefixed-attributes" class="tocxref"><span class="secno">3.5 </span><code>xmlns:</code>-Prefixed Attributes</a></li></ul></li><li class="tocline"><a href="#extensions-to-the-html5-syntax" class="tocxref"><span class="secno">4. </span>Extensions to the HTML5 Syntax</a><ul class="toc"><li class="tocline"><a href="#the-rdfa-attributes-and-valid-values" class="tocxref"><span class="secno">4.1 </span>The RDFa Attributes and Valid Values</a><ul class="toc"><li class="tocline"><a href="#the-version-attribute" class="tocxref"><span class="secno">4.1.1 </span>The version Attribute</a></li></ul></li><li class="tocline"><a href="#conformance-criteria-for-xmlns--prefixed-attributes" class="tocxref"><span class="secno">4.2 </span>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</a></li><li class="tocline"><a href="#preserving-namespaces-via-coercion-to-infoset"class="tocxref"><span class="secno">4.3 </span>Preserving Namespaces via Coercion to Infoset</a></li><li class="tocline"><a href="#infoset-based-processors" class="tocxref"><span class="secno">4.4 </span>Infoset-based Processors</a><ul class="toc"><li class="tocline"><a href="#extracting-uri-mappings-from-infosets" class="tocxref"><span class="secno">4.4.1 </span>Extracting URI Mappings from Infosets</a></li><li class="tocline"><a href="#processing-rdfa-attributes" class="tocxref"><span class="secno">4.4.2 </span>Processing RDFa Attributes</a></li></ul></li><li class="tocline"><a href="#dom-level-2-based-processors" class="tocxref"><span class="secno">4.5 </span>DOM Level 2-based Processors</a><ul class="toc"><li class="tocline"><a href="#extracting-uri-mappings-from-doms" class="tocxref"><span class="secno">4.5.1 </span>Extracting URI Mappings from DOMs</a></li><li class="tocline"><a href="#processing-rdfa-attributes-1" class="tocxref"><span class="secno">4.5.2 </span>Processing RDFa Attributes</a></li></u></li></ul></li><li class="tocline"><a href="#html-default-vocabulary-terms" class="tocxref"><span class="secno">A. </span>HTML Default Vocabulary Terms</a></li><li class="tocline"><a href="#validation" class="tocxref"><span class="secno">B. </span>Validation</a><ul class="toc"><li class="tocline"><a href="#the-html-4.01---rdfa-1.1-dtd" class="tocxref"><span class="secno">B.1 </span>The HTML 4.01 + RDFa 1.1 DTD</a></li></ul></li><li class="tocline"><a href="#about-this-document" class="tocxref"><span class="secno">C. </span>About this Document</a><ul class="toc"><li class="tocline"><a href="#history" class="tocxref"><span class="secno">C.1 </span>History</a></li><li class="tocline"><a href="#change-history" class="tocxref"><span class="secno">C.2 </span>Change History</a></li><li class="tocline"><a href="#acknowledgments" class="tocxref"><span class="secno">C.3 </span>Acknowledgments</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul cass="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></div>
@@ -133,6 +132,15 @@
<ul>
<li>All document conformance requirements stated as mandatory in the
HTML5 specification <em class="rfc2119" title="must">must</em> be met.</li>
+
+ <li>All
+ <a href="#extensions-to-the-html5-syntax">Extensions to the HTML5 Syntax</a>,
+ as described in this document, <em class="rfc2119" title="must">must</em> be considered valid and conforming in
+ a HTML+RDFa 1.1 document.</li>
+
+ <li>All HTML5 elements and attributes <em class="rfc2119" title="should">should</em> be used in a way that is
+ conformant with [<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>]. All RDFa attributes <em class="rfc2119" title="should">should</em> be used in a way that
+ is conformant with [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>] and this document.</li>
<li>There <em class="rfc2119" title="should">should</em> be a <code>version</code> attribute on the
<code>html</code> element. The value of the <code>version</code>
@@ -164,8 +172,29 @@
</div>
+<div id="rdfa-processor-conformance" class="section">
+ <h3><span class="secno">2.2 </span>RDFa Processor Conformance</h3>
+
+ <p>The RDFa Processor conformance criteria are listed below, all of
+ which are mandatory:</p>
+ <ul>
+ <li>An RDFa Processor <em class="rfc2119" title="must">must</em> implement all of the mandatory features
+ specified in the RDFa Core 1.1 specification [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>].</li>
+ <li>An RDFa Processor <em class="rfc2119" title="must">must</em> support any mandatory features described in this
+ specification.</li>
+ </ul>
+</div>
+
<div id="user-agent-conformance" class="section">
-<h3><span class="secno">2.2 </span>User Agent Conformance</h3>
+<h3><span class="secno">2.3 </span>User Agent Conformance</h3>
+
+ <p>A User Agent is considered to be a type of RDFa Processor when the
+ User Agent stores or processes RDFa attributes and their values. The
+ reason there are separate <em>RDFa Processor Conformance</em> and a
+ <em>User Agent Conformance</em> sections is because one can be a valid
+ HTML5 RDFa Processor but not a valid HTML5 User Agent (for example, by only
+ providing a very small subset of rendering functionality).
+ </p>
<p>The User Agent conformance criteria are listed below, all of which are
mandatory:</p>
@@ -185,19 +214,6 @@
</div>
-<div id="rdfa-processor-conformance" class="section">
- <h3><span class="secno">2.3 </span>RDFa Processor Conformance</h3>
-
- <p>The RDFa Processor conformance criteria are listed below, all of
- which are mandatory:</p>
- <ul>
- <li>An RDFa Processor <em class="rfc2119" title="must">must</em> implement all of the mandatory features
- specified in the RDFa Core 1.1 specification [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>].</li>
- <li>An RDFa Processor <em class="rfc2119" title="must">must</em> support any mandatory features described in this
- specification.</li>
- </ul>
-</div>
-
</div>
@@ -213,7 +229,7 @@
RDFa Core 1.1 in order to support extracting RDF from HTML documents.</p>
<p>The requirements and rules, as specified in RDFa Core and further
- modified in this document, apply to all HTML5 documents. The RDFa Processor
+ extended in this document, apply to all HTML5 documents. The RDFa Processor
operating on HTML and XHTML documents, specifically the resulting DOMs or
Infosets, <em class="rfc2119" title="must">must</em> apply the same processing rules for HTML4, HTML5 and XHTML5
serializations, DOMs and/or Infosets.</p>
@@ -244,15 +260,34 @@
</ul>
</div>
+<div id="modifying-the-input-document" class="section">
+ <h3><span class="secno">3.2 </span>Modifying the Input Document</h3>
+
+ <p>RDFa's tree-based processing rules, outlined in <a href="http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a> of
+ the RDFa Core 1.1 specification [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>], allow an input document to be
+ automatically corrected, cleaned-up, re-arranged, or modified in any way that
+ is approved by the host language prior to processing. Element nesting issues
+ in HTML documents <em class="rfc2119" title="should">should</em> be corrected before the input document is
+ translated into the DOM, a valid tree-based model, on which the RDFa
+ processing rules will operate.</p>
+
+ <p>Any mechanism that generates a data structure equivalent to the HTML5 or
+ XHTML5 DOM, such as the html5lib library, <em class="rfc2119" title="may">may</em> be used as the mechanism to
+ construct the tree-based model provided as input to the RDFa processing
+ rules.</p>
+</div>
+
<div id="specifying-the-language-for-a-literal" class="section">
- <h3><span class="secno">3.2 </span>Specifying the language for a literal</h3>
+ <h3><span class="secno">3.3 </span>Specifying the language for a literal</h3>
- <p>The <code>lang</code> attribute <em class="rfc2119" title="must">must</em> be processed in the same manner as
- the <code>xml:lang</code> attribute is in the RDFa Core 1.1 specification,
- <a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5:
- Sequence</a>, step #3.</p>The rules for determining the language of a node
- are specified in the section titled <a href="http://www.w3.org/TR/html5#the-lang-and-xml:lang-attributes">
- The lang and xml:lang attributes</a> in the HTML5 specification.
+ <p>RDFa Core 1.1 allows for the
+ <a class="tref" title="current_language" href="http://www.w3.org/TR/rdfa-core#dfn-current_language">current language</a>
+ to be specified by the Host Language. In order for RDFa Processors to conform
+ to this specification, they <em class="rfc2119" title="must">must</em> use the mechanism described in
+ <em>The lang and xml:lang attributes</em> section of the [<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>]
+ specification to determine the
+ <a class="tref" title="language" href="http://www.w3.org/TR/html5/Overview.html#language">language</a>
+ of a node.</p>
<p>If an author is editing an HTML fragment and is unsure of the final
encapsulating MIME type for their markup, it is suggested that the author
@@ -261,7 +296,7 @@
</div>
<div id="invalid-xmlliteral-values" class="section">
- <h3><span class="secno">3.3 </span>Invalid XMLLiteral values</h3>
+ <h3><span class="secno">3.4 </span>Invalid XMLLiteral values</h3>
<p>When generating literals of type XMLLiteral, the processor <em class="rfc2119" title="must">must</em> ensure
that the output XMLLiteral is a namespace well-formed XML fragment. A
@@ -273,24 +308,27 @@
well-formed XML document is specified in <a href="http://www.w3.org/TR/REC-xml/#sec-well-formed">Section 2.1 "Well-Formed
XML Documents"</a> of the XML specification.</li>
- <li>A case-insensitive match for the currently active <code>xmlns</code>
- attribute as well as all currently active attributes starting with
- <code>xmlns:</code> <em class="rfc2119" title="must">must</em> be preserved in the generated XMLLiteral. This
- preservation <em class="rfc2119" title="must">must</em> be accomplished by placing all active namespaces in
- each top-level element in the generated XMLLiteral, taking care to not
- over-write pre-existing namespace values.</li>
- </ul>If the input is not a namespace well-formed XML fragment, the
- processor <em class="rfc2119" title="must">must</em> transform the input text in a way that ensures the
- well-formedness rules described in this section. If a sequence of
- characters cannot be transformed into a namespace well-formed XML fragment,
- the triple containing the XMLLiteral <em class="rfc2119" title="must">must</em> not be generated.
-
+ <li>The XML fragment, when placed inside of a single root element, <em class="rfc2119" title="must">must</em>
+ retain all active namespace information. The currently active attributes
+ declared using <code>xmlns</code> and <code>xmlns:</code> stored in the
+ RDFa Processor's current
+ <a class="tref" title="evaluation_context" href="http://www.w3.org/TR/rdfa-core#dfn-evaluation_context">evaluation context</a>
+ in the
+ <a class="tref" title="list_of_URI_mappings" href="http://www.w3.org/TR/rdfa-core#dfn-list_of_uri_mappings">list of URI mappings</a>
+ <em class="rfc2119" title="must">must</em> be preserved in the generated XMLLiteral. The <em>PREFIX</em> value for
+ <code>xmlns:PREFIX</code> <em class="rfc2119" title="must">must</em> be transformed to all lower-case characters
+ when preserving the value in the XMLLiteral. All active namespaces declared
+ via <code>xmlns</code> and <code>xmlns:</code> <em class="rfc2119" title="must">must</em> be placed in each
+ top-level element in the generated XMLLiteral, taking care to not overwrite
+ pre-existing namespace values.</li>
+ </ul>
+
<p>An RDFa Processor that transforms the XML fragment <em class="rfc2119" title="must">must</em> use the <a href="http://www.w3.org/TR/html5/Overview.html#coercing-an-html-dom-into-an-infoset">
- Coercing an HTML DOM into an Infoset</a> rules, as specified in the HTML5
- specification, prior to generating the triple containing the XMLLiteral.
- The serialization algorithm that <em class="rfc2119" title="must">must</em> be used for generating the XMLLiteral
- is normatively defined in the <a href="http://www.w3.org/TR/html5/Overview.html#serializing-xhtml-fragments">Serializing
- XHTML Fragments</a> section of the HTML5 specification.</p>
+ Coercing an HTML DOM into an Infoset</a> algorithm, as specified in the HTML5
+ specification, followed by the algorithm defined in the <a href="http://www.w3.org/TR/html5/Overvxiew.html#serializing-xhtml-fragments">Serializing
+ XHTML Fragments</a> section of the HTML5 specification. If an error or
+ exception occurs at any point during the transformation, the triple containing
+ the XMLLiteral <em class="rfc2119" title="must not">must not</em> be generated.</p>
<p>Transformation to a namespace well-formed XML fragment is required
because an application that consumes XMLLiteral data expects that data to
@@ -327,10 +365,32 @@
namespaces are not used in either <code>rect</code> element, they are not
preserved in the XMLLiteral.
</p>
+
+<p>Similarly, compound document elements that reside in different
+namespaces must have their namespaces declarations preserved:</p>
+<pre class="example" title="Namespace preservation for compound document elements"><p xmlns:ex="http://example.org/vocab#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ <span class="hilite">xmlns:fb="http://www.facebook.com/2008/fbml"</span>>
+ This is how you markup a user in FBML:
+ <span property="ex:markup" datatype="rdf:XMLLiteral">
+→<p><fb:user uid="12345">The User</fb:user></p>
+→</span>
+<p></p></pre>
+<p>The markup above <em class="rfc2119" title="should">should</em> produce the following triple, which preserves the
+<code>fb</code> namespace in the corresponding triple:</p>
+
+<pre class="example" title="Namespace element preservation triple"><>
+ <http://example.org/vocab#markup>
+ "<p <span class="hilite">xmlns:fb="http://www.facebook.com/2008/fbml"</span>>
+→<fb:user uid="12345">
+→</p>"^^http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral .</pre>
+
+<p></p>
+
</div>
<div id="xmlns--prefixed-attributes" class="section">
- <h3><span class="secno">3.4 </span><code>xmlns:</code>-Prefixed Attributes</h3>
+ <h3><span class="secno">3.5 </span><code>xmlns:</code>-Prefixed Attributes</h3>
<p class="issue">While this section outlines xmlns: processing in RDFa, the
support for distributed extensibility in non-XML mode HTML5 (using xmlns
@@ -339,9 +399,15 @@
issue.</p>
<p>CURIE prefix mappings specified using attributes prepended with
- <code>xmlns:</code> <em class="rfc2119" title="must">must</em> be processed using the rules specified in
- <a href="http://www.w3.org/TR/rdfa-core/#s_curieprocessing">Section 7.4, CURIE and URI Processing</a>,
- contained in the RDFa Core 1.1 specification.</p>
+ <code>xmlns:</code> <em class="rfc2119" title="must">must</em> be processed using the algorithm defined in
+ section 4.4.1:
+ <a href="#extracting-uri-mappings-from-infosets">Extracting URI Mappings from Infosets</a>
+ for Infoset-based processors, or section 4.5.1:
+ <a href="#extracting-uri-mappings-from-doms">Extracting URI Mappings from DOMs</a>
+ for DOM Level 2-based processors. For CURIE prefix mappings using the
+ <code>prefix</code> attribute,
+ <a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5: Sequence</a>,
+ step #4 <em class="rfc2119" title="must">must</em> be used to process namespace values.</p>
<p>Since CURIE prefix mappings have been specified using
<code>xmlns:</code>, and since HTML attribute names are case-insensitive,
@@ -363,7 +429,7 @@
<p>There are a few extensions to the HTML5 specification that are required in
order to fully support RDFa. The following sub-sections outline the
- necessary modifications to the base HTML5 specification.</p>
+ necessary extensions to the base HTML5 specification.</p>
<div id="the-rdfa-attributes-and-valid-values" class="section">
<h3><span class="secno">4.1 </span>The RDFa Attributes and Valid Values</h3>
@@ -372,6 +438,19 @@
<a href="http://www.w3.org/TR/rdfa-core/#rdfa-attributes">Section 2.1:
The RDFa Attributes</a>, are conforming when used in an HTML5 or XHTML5
document.</p>
+
+<div id="the-version-attribute" class="section">
+ <h4><span class="secno">4.1.1 </span>The version Attribute</h4>
+
+ <p>The <code>@version</code> attribute is an <em class="rfc2119" title="optional">optional</em> attribute that is
+ allowed on the <code>html</code> element. It specifies the HTML5 language
+ features that are enabled for the current document. The value <em class="rfc2119" title="must">must</em> contain at
+ least one non-<strong>space character</strong>. The value must conform to a
+ <strong>set of space-separated tokens</strong>, as defined in
+ [<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>], Space-separated tokens.
+ </p>
+</div>
+
</div>
<div id="conformance-criteria-for-xmlns--prefixed-attributes" class="section">
@@ -384,14 +463,23 @@
extensibility issue.</p>
<p>Since RDFa uses attributes starting with <code>xmlns:</code> to specify
- CURIE prefixes, it is important that any attribute starting with a
- case-insensitive match on the text string "<code>xmlns:</code>" be
- preserved in the DOM or other tree-like model that is passed to the RDFa
- Processor. While it is specified that HTML5 must preserve these attributes
- in the DOM, it must also accept these attributes as conforming in non-XML
- HTML5. For documents conforming to this specification, attributes with
- names that have the case insensitive prefix "<code>xmlns:</code>" are
- conforming in both HTML5 and XHTML5.</p>
+ CURIE prefixes, any attribute starting with a case-insensitive match on the
+ text string "<code>xmlns:</code>" <em class="rfc2119" title="must">must</em> be preserved in the DOM or other
+ tree-like model that is passed to the RDFa Processor.
+ For documents conforming to this specification, attributes with
+ names that have a case insensitive prefix matching "<code>xmlns:</code>"
+ <em class="rfc2119" title="must">must</em> be considered conforming. Conformance checkers <em class="rfc2119" title="must">must</em>
+ accept attribute names that have a case insensitive prefix matching
+ "<code>xmlns:</code>" as conforming.
+ </p>
+
+ <p>All attributes starting with a case insensitive prefix matching
+ "<code>xmlns:</code>" <em class="rfc2119" title="must">must</em> conform to the production rules outlined in
+ Namespaces in XML [<a class="bibref" rel="biblioentry" href="#bib-XML-NAMES11">XML-NAMES11</a>],
+ <a href="http://www.w3.org/TR/xml-names11#ns-decl">Section 3: Declaring Namespaces</a>.
+ Documents that contain <code>xmlns:</code> attributes that do not conform to
+ Namespaces in XML <em class="rfc2119" title="must not">must not</em> be accepted as conforming.
+ </p>
</div>
<div id="preserving-namespaces-via-coercion-to-infoset" class="section">
@@ -406,24 +494,32 @@
is declared in non-XML mode HTML5 documents are mapped to an Infoset
correctly. In order to ensure this mapping is performed correctly, the
"Coercing an HTML DOM into an infoset" rules defined in [<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>]
- must be modified to include the following rule:</p>
+ must be extended to include the following rule:</p>
- <p>If the XML API is namespace-aware, the tool must ensure that proper
+ <p>If the XML API is namespace-aware, the tool must ensure that
([<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">namespace
name</a>], [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">local name</a>],
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>]) namespace tuples are created when converting the non-XML mode
- DOM into an Infoset.</p>
+ DOM into an Infoset. Given a standard <code>xmlns:</code> definition,
+ <code>xmlns:foo="http://example.org/bar#"</code>, the [namespace name]
+ is <code>http://www.w3.org/2000/xmlns/</code>,
+ the [local name] is <code>foo</code>, and the
+ [normalized value] is <code>http://example.org/bar#</code>, thus the
+ namespace tuple would be (<code>http://www.w3.org/2000/xmlns/</code>,
+ <code>foo</code>, <code>http://example.org/bar#</code>).</p>
<p>For example, given the following input text:</p>
<pre class="example"><div xmlns:audio="http://purl.org/media/audio#"></pre>
+<p>
The <code>div</code> element above, when coerced from an HTML DOM into
an Infoset, should contain an attribute in the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.element">namespace
attributes</a>] list with a [namespace name] set to
"<code>http://www.w3.org/2000/xmlns/</code>", a [local name] set to
<code>audio</code>, and a [normalized value] of
"<code>http://purl.org/media/audio#</code>".
+</p>
</div>
@@ -435,12 +531,12 @@
the sake of clarity, detailed methods of extracting RDFa content from
processors operating on an XML Information Set are provided below.</p>
-<div id="processing-namespaced-rdfa-attributes" class="section">
- <h4><span class="secno">4.4.1 </span>Processing Namespaced RDFa Attributes</h4>
+<div id="extracting-uri-mappings-from-infosets" class="section">
+ <h4><span class="secno">4.4.1 </span>Extracting URI Mappings from Infosets</h4>
- <p>Extracting namespaced RDFa attributes while operating from within an
- Infoset-based RDFa processor can be achieved using the following
- algorithm:</p>
+ <p>Extracting URI Mappings declared via <code>xmlns:</code>
+ while operating from within an Infoset-based RDFa processor can be achieved
+ using the following algorithm:</p>
<p>While processing an element as described in [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>],
<a href="http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a>,
@@ -493,8 +589,7 @@
<li>For each Attribute Information Item specific to RDFa in the Infoset
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">attributes</a>]
list that has a [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">prefix</a>] with
- no value or a [prefix] with the value of
- <code>http://www.w3.org/1999/xhtml</code>, extract and use the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
+ no value, extract and use the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>].</li>
</ol>
</div>
@@ -511,12 +606,12 @@
the sake of clarity, detailed methods of extracting RDFa content from
processors operating in a DOM2 environment are provided below.</p>
-<div id="processing-namespaced-rdfa-attributes-1" class="section">
- <h4><span class="secno">4.5.1 </span>Processing Namespaced RDFa Attributes</h4>
+<div id="extracting-uri-mappings-from-doms" class="section">
+ <h4><span class="secno">4.5.1 </span>Extracting URI Mappings from DOMs</h4>
- <p>Extracting namespaced RDFa attributes while operating from within a DOM
- Level 2 based RDFa processor can be achieved using the following
- algorithm:</p>
+ <p>Extracting URI Mappings declared via <code>xmlns:</code> while operating
+ from within a DOM Level 2 based RDFa processor can be achieved using the
+ following algorithm:</p>
<p>While processing each DOM2 [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Element</a>]
as described in [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>],
@@ -567,8 +662,7 @@
<ol>
<li>For each RDFa attribute in the [<a href="%3Ca%20href=" http:="">Node.attributes</a>] list that has a [<a href="http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-namespaceprefix">namespace
- prefix</a>] that is null or a [namespace prefix] with the value of
- <code>http://www.w3.org/1999/xhtml</code>, extract and use [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
+ prefix</a>] that is null, extract and use [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
as the value.</li>
</ol>
</div>
@@ -1872,7 +1966,7 @@
document, also a <em>thin</em> specification, is targeted at HTML4, HTML5 and
XHTML5.
-</p><p>This document describes the modifications to the RDFa Core 1.1
+</p><p>This document describes the extensions to the RDFa Core 1.1
specification that permits the use of RDFa in all HTML family documents. By
using the attributes and processing rules described in the RDFa Core 1.1
specification and heeding the minor changes in this document, authors can
@@ -1923,6 +2017,7 @@
</dd><dt id="bib-RDFA-CORE">[RDFA-CORE]</dt><dd>Shane McCarron; et al. <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20100422"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a>22 April 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20100422">http://www.w3.org/TR/2010/WD-rdfa-core-20100422</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> 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-RFC3236">[RFC3236]</dt><dd>P. Stark; M. Baker. <a href="http://www.rfc-editor.org/rfc/rfc3236.txt"><cite>The 'application/xhtml+xml' Media Type.</cite></a> January 2002. Internet RFC 3236. URL: <a href="http://www.rfc-editor.org/rfc/rfc3236.txt">http://www.rfc-editor.org/rfc/rfc3236.txt</a>
+</dd><dt id="bib-XML-NAMES11">[XML-NAMES11]</dt><dd>Andrew Layman; et al. <a href="http://www.w3.org/TR/2006/REC-xml-names11-20060816"><cite>Namespaces in XML 1.1 (Second Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2006/REC-xml-names11-20060816">http://www.w3.org/TR/2006/REC-xml-names11-20060816</a>
</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-RDFA-SYNTAX">[RDFA-SYNTAX]</dt><dd>Ben Adida, et al. <a href="http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014"><cite>RDFa in XHTML: Syntax and Processing.</cite></a> 14 October 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014">http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014</a>
</dd><dt id="bib-XHTML-RDFA">[XHTML-RDFA]</dt><dd>Shane McCarron; et. al. <a href="http://www.w3.org/TR/2010/WD-xhtml-rdfa-20100422"><cite>XHTML+RDFa 1.1.</cite></a> 22 April 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-xhtml-rdfa-20100422">http://www.w3.org/TR/WD-xhtml-rdfa-20100422</a>
</dd><dt id="bib-XHTML-VOCAB">[XHTML-VOCAB]</dt><dd>XHTML 2 Working Group. <a href="http://www.w3.org/1999/xhtml/vocab"><cite>XHTML Vocabulary</cite></a>. URL: <a href="http://www.w3.org/1999/xhtml/vocab">http://www.w3.org/1999/xhtml/vocab</a>
Index: Overview-src.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview-src.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- Overview-src.html 3 May 2010 00:52:54 -0000 1.3
+++ Overview-src.html 5 May 2010 03:47:16 -0000 1.4
@@ -93,6 +93,7 @@
var p = item.parentNode ;
var con = item.innerHTML ;
var ref = item.getAttribute('title') ;
+ var href = item.getAttribute('href') ;
if (!ref) {
ref = item.textContent ;
}
@@ -105,6 +106,9 @@
var id = item.textContent ;
sp.className = 'tref' ;
sp.title = ref ;
+ if(href) {
+ sp.href = href;
+ }
sp.innerHTML = con ;
p.replaceChild(sp, item) ;
}
@@ -258,8 +262,7 @@
<li>Inclusion of the HTML Default Vocabulary Terms, which mirror the XHTML
Default Vocabulary Terms, for the purpose of HTML/XHTML interoperability.</li>
<li>Inclusion of a HTML 4.01 + RDFa 1.1 DTD for validation purposes.</li>
-<li>All bugs concerning HTML+RDFa have been addressed in the HTML WG bug
-tracker.</li>
+<li>Added normative definition of @version attribute.</li>
</ol>
<p>The latest stable version of the editor's draft of this specification is
@@ -316,6 +319,15 @@
<ul>
<li>All document conformance requirements stated as mandatory in the
HTML5 specification MUST be met.</li>
+
+ <li>All
+ <a href="#extensions-to-the-html5-syntax">Extensions to the HTML5 Syntax</a>,
+ as described in this document, MUST be considered valid and conforming in
+ a HTML+RDFa 1.1 document.</li>
+
+ <li>All HTML5 elements and attributes SHOULD be used in a way that is
+ conformant with [[!HTML5]]. All RDFa attributes SHOULD be used in a way that
+ is conformant with [[!RDFA-CORE]] and this document.</li>
<li>There SHOULD be a <code>version</code> attribute on the
<code>html</code> element. The value of the <code>version</code>
@@ -350,8 +362,29 @@
</section>
<section>
+ <h2>RDFa Processor Conformance</h2>
+
+ <p>The RDFa Processor conformance criteria are listed below, all of
+ which are mandatory:</p>
+ <ul>
+ <li>An RDFa Processor MUST implement all of the mandatory features
+ specified in the RDFa Core 1.1 specification [[!RDFA-CORE]].</li>
+ <li>An RDFa Processor MUST support any mandatory features described in this
+ specification.</li>
+ </ul>
+</section>
+
+<section>
<h2>User Agent Conformance</h2>
+ <p>A User Agent is considered to be a type of RDFa Processor when the
+ User Agent stores or processes RDFa attributes and their values. The
+ reason there are separate <em>RDFa Processor Conformance</em> and a
+ <em>User Agent Conformance</em> sections is because one can be a valid
+ HTML5 RDFa Processor but not a valid HTML5 User Agent (for example, by only
+ providing a very small subset of rendering functionality).
+ </p>
+
<p>The User Agent conformance criteria are listed below, all of which are
mandatory:</p>
@@ -371,19 +404,6 @@
</section>
-<section>
- <h2>RDFa Processor Conformance</h2>
-
- <p>The RDFa Processor conformance criteria are listed below, all of
- which are mandatory:</p>
- <ul>
- <li>An RDFa Processor MUST implement all of the mandatory features
- specified in the RDFa Core 1.1 specification [[!RDFA-CORE]].</li>
- <li>An RDFa Processor MUST support any mandatory features described in this
- specification.</li>
- </ul>
-</section>
-
</section>
</section>
@@ -401,7 +421,7 @@
RDFa Core 1.1 in order to support extracting RDF from HTML documents.</p>
<p>The requirements and rules, as specified in RDFa Core and further
- modified in this document, apply to all HTML5 documents. The RDFa Processor
+ extended in this document, apply to all HTML5 documents. The RDFa Processor
operating on HTML and XHTML documents, specifically the resulting DOMs or
Infosets, MUST apply the same processing rules for HTML4, HTML5 and XHTML5
serializations, DOMs and/or Infosets.</p>
@@ -433,15 +453,34 @@
</section>
<section>
+ <h3>Modifying the Input Document</h3>
+
+ <p>RDFa's tree-based processing rules, outlined in <a href=
+ "http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a> of
+ the RDFa Core 1.1 specification [[!RDFA-CORE]], allow an input document to be
+ automatically corrected, cleaned-up, re-arranged, or modified in any way that
+ is approved by the host language prior to processing. Element nesting issues
+ in HTML documents SHOULD be corrected before the input document is
+ translated into the DOM, a valid tree-based model, on which the RDFa
+ processing rules will operate.</p>
+
+ <p>Any mechanism that generates a data structure equivalent to the HTML5 or
+ XHTML5 DOM, such as the html5lib library, MAY be used as the mechanism to
+ construct the tree-based model provided as input to the RDFa processing
+ rules.</p>
+</section>
+
+<section>
<h3>Specifying the language for a literal</h3>
- <p>The <code>lang</code> attribute MUST be processed in the same manner as
- the <code>xml:lang</code> attribute is in the RDFa Core 1.1 specification,
- <a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5:
- Sequence</a>, step #3.</p>The rules for determining the language of a node
- are specified in the section titled <a href=
- "http://www.w3.org/TR/html5#the-lang-and-xml:lang-attributes">
- The lang and xml:lang attributes</a> in the HTML5 specification.
+ <p>RDFa Core 1.1 allows for the
+ <tref href="http://www.w3.org/TR/rdfa-core#dfn-current_language">current language</tref>
+ to be specified by the Host Language. In order for RDFa Processors to conform
+ to this specification, they MUST use the mechanism described in
+ <em>The lang and xml:lang attributes</em> section of the [[!HTML5]]
+ specification to determine the
+ <tref href="http://www.w3.org/TR/html5/Overview.html#language">language</tref>
+ of a node.</p>
<p>If an author is editing an HTML fragment and is unsure of the final
encapsulating MIME type for their markup, it is suggested that the author
@@ -463,26 +502,29 @@
"http://www.w3.org/TR/REC-xml/#sec-well-formed">Section 2.1 "Well-Formed
XML Documents"</a> of the XML specification.</li>
- <li>A case-insensitive match for the currently active <code>xmlns</code>
- attribute as well as all currently active attributes starting with
- <code>xmlns:</code> MUST be preserved in the generated XMLLiteral. This
- preservation MUST be accomplished by placing all active namespaces in
- each top-level element in the generated XMLLiteral, taking care to not
- over-write pre-existing namespace values.</li>
- </ul>If the input is not a namespace well-formed XML fragment, the
- processor MUST transform the input text in a way that ensures the
- well-formedness rules described in this section. If a sequence of
- characters cannot be transformed into a namespace well-formed XML fragment,
- the triple containing the XMLLiteral MUST not be generated.
-
+ <li>The XML fragment, when placed inside of a single root element, MUST
+ retain all active namespace information. The currently active attributes
+ declared using <code>xmlns</code> and <code>xmlns:</code> stored in the
+ RDFa Processor's current
+ <tref href="http://www.w3.org/TR/rdfa-core#dfn-evaluation_context">evaluation context</tref>
+ in the
+ <tref href="http://www.w3.org/TR/rdfa-core#dfn-list_of_uri_mappings">list of URI mappings</tref>
+ MUST be preserved in the generated XMLLiteral. The <em>PREFIX</em> value for
+ <code>xmlns:PREFIX</code> MUST be transformed to all lower-case characters
+ when preserving the value in the XMLLiteral. All active namespaces declared
+ via <code>xmlns</code> and <code>xmlns:</code> MUST be placed in each
+ top-level element in the generated XMLLiteral, taking care to not overwrite
+ pre-existing namespace values.</li>
+ </ul>
+
<p>An RDFa Processor that transforms the XML fragment MUST use the <a href=
"http://www.w3.org/TR/html5/Overview.html#coercing-an-html-dom-into-an-infoset">
- Coercing an HTML DOM into an Infoset</a> rules, as specified in the HTML5
- specification, prior to generating the triple containing the XMLLiteral.
- The serialization algorithm that MUST be used for generating the XMLLiteral
- is normatively defined in the <a href=
- "http://www.w3.org/TR/html5/Overview.html#serializing-xhtml-fragments">Serializing
- XHTML Fragments</a> section of the HTML5 specification.</p>
+ Coercing an HTML DOM into an Infoset</a> algorithm, as specified in the HTML5
+ specification, followed by the algorithm defined in the <a href=
+ "http://www.w3.org/TR/html5/Overvxiew.html#serializing-xhtml-fragments">Serializing
+ XHTML Fragments</a> section of the HTML5 specification. If an error or
+ exception occurs at any point during the transformation, the triple containing
+ the XMLLiteral MUST NOT be generated.</p>
<p>Transformation to a namespace well-formed XML fragment is required
because an application that consumes XMLLiteral data expects that data to
@@ -526,6 +568,33 @@
namespaces are not used in either <code>rect</code> element, they are not
preserved in the XMLLiteral.
</p>
+
+<p>Similarly, compound document elements that reside in different
+namespaces must have their namespaces declarations preserved:</p>
+<pre class="example" title="Namespace preservation for compound document elements">
+<p xmlns:ex="http://example.org/vocab#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ <span class="hilite">xmlns:fb="http://www.facebook.com/2008/fbml"</span>>
+ This is how you markup a user in FBML:
+ <span property="ex:markup" datatype="rdf:XMLLiteral">
+→<p><fb:user uid="12345">The User</fb:user></p>
+→</span>
+</p>
+
+</pre>
+<p>The markup above SHOULD produce the following triple, which preserves the
+<code>fb</code> namespace in the corresponding triple:</p>
+
+<pre class="example" title="Namespace element preservation triple">
+<>
+ <http://example.org/vocab#markup>
+ "<p <span class="hilite">xmlns:fb="http://www.facebook.com/2008/fbml"</span>>
+→<fb:user uid="12345"></fb:user>
+→</p>"^^http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral .
+</pre>
+
+</p>
+
</section>
<section>
@@ -538,9 +607,15 @@
issue.</p>
<p>CURIE prefix mappings specified using attributes prepended with
- <code>xmlns:</code> MUST be processed using the rules specified in
- <a href="http://www.w3.org/TR/rdfa-core/#s_curieprocessing">Section 7.4, CURIE and URI Processing</a>,
- contained in the RDFa Core 1.1 specification.</p>
+ <code>xmlns:</code> MUST be processed using the algorithm defined in
+ section 4.4.1:
+ <a href="#extracting-uri-mappings-from-infosets">Extracting URI Mappings from Infosets</a>
+ for Infoset-based processors, or section 4.5.1:
+ <a href="#extracting-uri-mappings-from-doms">Extracting URI Mappings from DOMs</a>
+ for DOM Level 2-based processors. For CURIE prefix mappings using the
+ <code>prefix</code> attribute,
+ <a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5: Sequence</a>,
+ step #4 MUST be used to process namespace values.</p>
<p>Since CURIE prefix mappings have been specified using
<code>xmlns:</code>, and since HTML attribute names are case-insensitive,
@@ -562,7 +637,7 @@
<p>There are a few extensions to the HTML5 specification that are required in
order to fully support RDFa. The following sub-sections outline the
- necessary modifications to the base HTML5 specification.</p>
+ necessary extensions to the base HTML5 specification.</p>
<section>
<h3>The RDFa Attributes and Valid Values</h3>
@@ -571,6 +646,19 @@
<a href="http://www.w3.org/TR/rdfa-core/#rdfa-attributes">Section 2.1:
The RDFa Attributes</a>, are conforming when used in an HTML5 or XHTML5
document.</p>
+
+<section>
+ <h4>The version Attribute</h4>
+
+ <p>The <code>@version</code> attribute is an OPTIONAL attribute that is
+ allowed on the <code>html</code> element. It specifies the HTML5 language
+ features that are enabled for the current document. The value MUST contain at
+ least one non-<strong>space character</strong>. The value must conform to a
+ <strong>set of space-separated tokens</strong>, as defined in
+ [[!HTML5]], Space-separated tokens.
+ </p>
+</section>
+
</section>
<section>
@@ -583,14 +671,23 @@
extensibility issue.</p>
<p>Since RDFa uses attributes starting with <code>xmlns:</code> to specify
- CURIE prefixes, it is important that any attribute starting with a
- case-insensitive match on the text string "<code>xmlns:</code>" be
- preserved in the DOM or other tree-like model that is passed to the RDFa
- Processor. While it is specified that HTML5 must preserve these attributes
- in the DOM, it must also accept these attributes as conforming in non-XML
- HTML5. For documents conforming to this specification, attributes with
- names that have the case insensitive prefix "<code>xmlns:</code>" are
- conforming in both HTML5 and XHTML5.</p>
+ CURIE prefixes, any attribute starting with a case-insensitive match on the
+ text string "<code>xmlns:</code>" MUST be preserved in the DOM or other
+ tree-like model that is passed to the RDFa Processor.
+ For documents conforming to this specification, attributes with
+ names that have a case insensitive prefix matching "<code>xmlns:</code>"
+ MUST be considered conforming. Conformance checkers MUST
+ accept attribute names that have a case insensitive prefix matching
+ "<code>xmlns:</code>" as conforming.
+ </p>
+
+ <p>All attributes starting with a case insensitive prefix matching
+ "<code>xmlns:</code>" MUST conform to the production rules outlined in
+ Namespaces in XML [[!XML-NAMES11]],
+ <a href="http://www.w3.org/TR/xml-names11#ns-decl">Section 3: Declaring Namespaces</a>.
+ Documents that contain <code>xmlns:</code> attributes that do not conform to
+ Namespaces in XML MUST NOT be accepted as conforming.
+ </p>
</section>
<section>
@@ -605,21 +702,28 @@
is declared in non-XML mode HTML5 documents are mapped to an Infoset
correctly. In order to ensure this mapping is performed correctly, the
"Coercing an HTML DOM into an infoset" rules defined in [[!HTML5]]
- must be modified to include the following rule:</p>
+ must be extended to include the following rule:</p>
- <p>If the XML API is namespace-aware, the tool must ensure that proper
+ <p>If the XML API is namespace-aware, the tool must ensure that
([<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">namespace
name</a>], [<a href=
"http://www.w3.org/TR/xml-infoset/#infoitem.attribute">local name</a>],
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>]) namespace tuples are created when converting the non-XML mode
- DOM into an Infoset.</p>
+ DOM into an Infoset. Given a standard <code>xmlns:</code> definition,
+ <code>xmlns:foo="http://example.org/bar#"</code>, the [namespace name]
+ is <code>http://www.w3.org/2000/xmlns/</code>,
+ the [local name] is <code>foo</code>, and the
+ [normalized value] is <code>http://example.org/bar#</code>, thus the
+ namespace tuple would be (<code>http://www.w3.org/2000/xmlns/</code>,
+ <code>foo</code>, <code>http://example.org/bar#</code>).</p>
<p>For example, given the following input text:</p>
<pre class="example">
<div xmlns:audio="http://purl.org/media/audio#">
</pre>
+<p>
The <code>div</code> element above, when coerced from an HTML DOM into
an Infoset, should contain an attribute in the [<a href=
"http://www.w3.org/TR/xml-infoset/#infoitem.element">namespace
@@ -627,6 +731,7 @@
"<code>http://www.w3.org/2000/xmlns/</code>", a [local name] set to
<code>audio</code>, and a [normalized value] of
"<code>http://purl.org/media/audio#</code>".
+</p>
</section>
@@ -639,11 +744,11 @@
processors operating on an XML Information Set are provided below.</p>
<section>
- <h3>Processing Namespaced RDFa Attributes</h3>
+ <h3>Extracting URI Mappings from Infosets</h3>
- <p>Extracting namespaced RDFa attributes while operating from within an
- Infoset-based RDFa processor can be achieved using the following
- algorithm:</p>
+ <p>Extracting URI Mappings declared via <code>xmlns:</code>
+ while operating from within an Infoset-based RDFa processor can be achieved
+ using the following algorithm:</p>
<p>While processing an element as described in [[!RDFA-CORE]],
<a href="http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a>,
@@ -706,8 +811,7 @@
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">attributes</a>]
list that has a [<a href=
"http://www.w3.org/TR/xml-infoset/#infoitem.attribute">prefix</a>] with
- no value or a [prefix] with the value of
- <code>http://www.w3.org/1999/xhtml</code>, extract and use the [<a href=
+ no value, extract and use the [<a href=
"http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>].</li>
</ol>
@@ -726,11 +830,11 @@
processors operating in a DOM2 environment are provided below.</p>
<section>
- <h3>Processing Namespaced RDFa Attributes</h3>
+ <h3>Extracting URI Mappings from DOMs</h3>
- <p>Extracting namespaced RDFa attributes while operating from within a DOM
- Level 2 based RDFa processor can be achieved using the following
- algorithm:</p>
+ <p>Extracting URI Mappings declared via <code>xmlns:</code> while operating
+ from within a DOM Level 2 based RDFa processor can be achieved using the
+ following algorithm:</p>
<p>While processing each DOM2 [<a href=
"http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Element</a>]
@@ -798,8 +902,7 @@
<li>For each RDFa attribute in the [<a href="%3Ca%20href=" http:=
"">Node.attributes</a>] list that has a [<a href=
"http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-namespaceprefix">namespace
- prefix</a>] that is null or a [namespace prefix] with the value of
- <code>http://www.w3.org/1999/xhtml</code>, extract and use [<a href=
+ prefix</a>] that is null, extract and use [<a href=
"http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
as the value.</li>
</ol>
@@ -1028,7 +1131,7 @@
document, also a <em>thin</em> specification, is targeted at HTML4, HTML5 and
XHTML5.
-<p>This document describes the modifications to the RDFa Core 1.1
+<p>This document describes the extensions to the RDFa Core 1.1
specification that permits the use of RDFa in all HTML family documents. By
using the attributes and processing rules described in the RDFa Core 1.1
specification and heeding the minor changes in this document, authors can
Received on Wednesday, 5 May 2010 03:47:23 UTC