- From: Manu Sporny via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 05 Apr 2011 14:40:58 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/rdfa
In directory hutz:/tmp/cvs-serv17207
Modified Files:
Overview-src.html Overview.html
Log Message:
[html-rdfa] Added new Working Draft for HTML+RDFa.
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- Overview.html 12 Jan 2011 03:40:28 -0000 1.36
+++ Overview.html 5 Apr 2011 14:40:56 -0000 1.37
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.0//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd'>
-<html dir="ltr" about="" property="dcterms:language" content="en" xmlns="http://www.w3.org/1999/xhtml" xmlns:dcterms='http://purl.org/dc/terms/' xmlns:bibo='http://purl.org/ontology/bibo/' xmlns:foaf='http://xmlns.com/foaf/0.1/' xmlns:xsd='http://www.w3.org/2001/XMLSchema#'>
+<html dir="ltr" about="http://sites.local/dev.w3.org/html5/rdfa/Overview-src.html#xmlns--prefixed-attributes" property="dcterms:language" content="en" xmlns="http://www.w3.org/1999/xhtml" xmlns:dcterms='http://purl.org/dc/terms/' xmlns:bibo='http://purl.org/ontology/bibo/' xmlns:foaf='http://xmlns.com/foaf/0.1/' xmlns:xsd='http://www.w3.org/2001/XMLSchema#'>
<head>
<title>HTML+RDFa 1.1</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
@@ -512,8 +512,8 @@
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }
-</style><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 property="dcterms:title" class="title" id="title">HTML+RDFa 1.1</h1><h2 property="bibo:subtitle" id="subtitle">Support for RDFa in HTML4 and HTML5</h2><h2 property="dcterms:issued" datatype="xsd:dateTime" content="2011-01-12T03:39:26+0000" id="w3c-editor-s-draft-11-january-2011">W3C Editor's Draft 11 January 2011</h2><dl><dt>This version:</dt><dd><a href="http://dev.w3.org/html5/rdfa/">http://dev.w3.org/html5/rdfa/</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/">http://dev.w3.org/html5/rdfa/</a></dd><dt>Previous version:</dt><dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2010/WD-rdfa-in-html-20101019/">http://www.w3.org/TR/2010/WD-rdfa-in-html-20101019/</a></dd><dt>ditors:</dt><dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://blog.digitalbazaar.com">Digital Bazaar, Inc.</a></span>
+</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8" /></head>
+ <body style="display: inherit; " about="http://sites.local/dev.w3.org/html5/rdfa/Overview-src.html#xmlns--prefixed-attributes"><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 property="dcterms:title" class="title" id="title">HTML+RDFa 1.1</h1><h2 property="bibo:subtitle" id="subtitle">Support for RDFa in HTML4 and HTML5</h2><h2 property="dcterms:issued" datatype="xsd:dateTime" content="2011-04-05T18:36:11+0000" id="w3c-working-draft-05-april-2011">W3C Working Draft 05 April 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-rdfa-in-html-20110405/">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110405/</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/">http://dev.w3.org/html5/rdfa/</a></dd><dt>Previous version:</dt><dd><a rel="dcterms:rplaces" href="http://www.w3.org/TR/2010/WD-rdfa-in-html-20101019/">http://www.w3.org/TR/2010/WD-rdfa-in-html-20101019/</a></dd><dt>Editors:</dt><dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://blog.digitalbazaar.com">Digital Bazaar, Inc.</a></span>
</dd>
<dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Shane McCarron" href="mailto:shane@aptest.com">Shane McCarron</a>, <a rel="foaf:workplaceHomepage" href="http://www.aptest.com/">Applied Testing and Technology, Inc.</a></span>
</dd>
@@ -523,7 +523,7 @@
</dd>
<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Steven Pemberton" href="http://homepages.cwi.nl/~steven/">Steven Pemberton</a>, <a rel="foaf:workplaceHomepage" href="http://www.cwi.nl/">CWI</a></span>
</dd>
-</dl><p class="copyright"><a rel="license" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009-2011 <span rel="dcterms:publisher"><span typeof="foaf:Organization"><a rel="foaf:homepage" property="foaf:name" content="World Wide Web Consotrium" href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup></span></span> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <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>
+</dl><p>This document is also available in this non-normative format: <a href="diff-20110113.html">Changes since previous Working Draft</a>.</p><p class="copyright"><a rel="license" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009-2011 <span rel="dcterms:publisher"><span typeof="foaf:Organization"><a rel="foaf:homepage" property="foaf:name" content="World Wide Web Consotrium" href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup></span></span> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <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 hrf="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr /></div>
<div id="abstract" class="introductory section" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" about="#abstract"><h2>Abstract</h2>
<p>This specification defines rules and guidelines for adapting the RDFa Core
@@ -550,6 +550,7 @@
are going to use xmlns: in HTML5 documents, the rules need to be clear in
the cases where this happens.</li>
<li>Added DOM Level 1 prefix mapping algorithm.</li>
+<li>Added backwards-compatibility section for xmlns:.</li>
</ol>
<p>The latest stable version of the editor's draft of this specification is
@@ -577,7 +578,7 @@
content in the HTML5 specification, unless specifically overridden by this
specification, is intended to be the basis for this specification.</p>
-<p>A <a href="http://rdfa.digitalbazaar.com/rdfa-test-harness/">sample
+<p>A <a href="http://rdfa.digitalbazaar.com/test-suite/">sample
test harness</a> is available. This set of tests is
not intended to be exhaustive. Users may find the tests to
be useful examples of RDFa usage.
@@ -600,7 +601,7 @@
<a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG">public bug
database</a>. All feedback is welcome.</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 W3C 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 W3C Patent Policy</a>. W3C 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 wih 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 W3C Patent Policy</a>.</p></div><div id="toc" typeof="bibo:Chapter" about="#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 href="#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="toxref"><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></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="tocxrf"><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-1-and-level-2-based-processors" class="tocxref"><span class="secno">4.5 </span>DOM Level 1 and Level 2-based Processors</a><ul class="toc"><li class="tocline"><a href="#extracting-uri-mappings-via-dom-level-2" class="tocxref"><span class="secno">4.5.1 </span>Extracting URI Mappings via DOM Level 2</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="#validation" class="tocxref"><span class="secno">A. </span>Validation</a><ul class="toc"><li class="tocline"><a href="#the-html-4.01---rdfa-1.1-dtd" class="tocxref"><span class="secno">A.1 </span>The HTML 4.01 + RDFa 1.1 DTD</a></li></ul></li><li cass="tocline"><a href="#about-this-document" class="tocxref"><span class="secno">B. </span>About this Document</a><ul class="toc"><li class="tocline"><a href="#history" class="tocxref"><span class="secno">B.1 </span>History</a></li><li class="tocline"><a href="#change-history" class="tocxref"><span class="secno">B.2 </span>Change History</a></li><li class="tocline"><a href="#acknowledgments" class="tocxref"><span class="secno">B.3 </span>Acknowledgments</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.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 a Working Draft. This document is intended to become a W3C Recommendation. 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 Working Draft does not imply endorsement by the W3C 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 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/40318/status" rel="disclosure">public lst 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 W3C Patent Policy</a>.</p></div><div id="toc" typeof="bibo:Chapter" about="#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 href="#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></ul></li><l class="tocline"><a href="#extensions-to-the-html5-syntax" class="tocxref"><span class="secno">4. </span>Extensions to the HTML5 Syntax</a></li><li class="tocline"><a href="#backwards-compatibility" class="tocxref"><span class="secno">5. </span>Backwards Compatibility</a><ul class="toc"><li class="tocline"><a href="#xmlns--prefixed-attributes" class="tocxref"><span class="secno">5.1 </span><code>xmlns:</code>-Prefixed Attributes</a></li><li class="tocline"><a href="#conformance-criteria-for-xmlns--prefixed-attributes" class="tocxref"><span class="secno">5.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">5.3 </span>Preserving Namespaces via Coercion to Infoset</a></li><li class="tocline"><a href="#infoset-based-processors" class="tocxref"><span class="secno">5.4 </span>Infoset-based Processors</a><ul class="toc"><li class="tocline"><a href="#extracting-uri-mappingsfrom-infosets" class="tocxref"><span class="secno">5.4.1 </span>Extracting URI Mappings from Infosets</a></li><li class="tocline"><a href="#processing-rdfa-attributes" class="tocxref"><span class="secno">5.4.2 </span>Processing RDFa Attributes</a></li></ul></li><li class="tocline"><a href="#dom-level-1-and-level-2-based-processors" class="tocxref"><span class="secno">5.5 </span>DOM Level 1 and Level 2-based Processors</a><ul class="toc"><li class="tocline"><a href="#extracting-uri-mappings-via-dom-level-2" class="tocxref"><span class="secno">5.5.1 </span>Extracting URI Mappings via DOM Level 2</a></li><li class="tocline"><a href="#processing-rdfa-attributes-1" class="tocxref"><span class="secno">5.5.2 </span>Processing RDFa Attributes</a></li></ul></li></ul></li><li class="tocline"><a href="#validation" class="tocxref"><span class="secno">A. </span>Validation</a><ul class="toc"><li class="tocline"><a href="#the-html-4.01---rdfa-1.1-dtd" class="tocxref"><span class="secno">A.1 </span>The HTML 4.01 + RDFa 1.1DTD</a></li></ul></li><li class="tocline"><a href="#about-this-document" class="tocxref"><span class="secno">B. </span>About this Document</a><ul class="toc"><li class="tocline"><a href="#history" class="tocxref"><span class="secno">B.1 </span>History</a></li><li class="tocline"><a href="#change-history" class="tocxref"><span class="secno">B.2 </span>Change History</a></li><li class="tocline"><a href="#acknowledgments" class="tocxref"><span class="secno">B.3 </span>Acknowledgments</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
@@ -609,14 +610,14 @@
<!-- OddPage -->
<h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
- <p>Today's web is built predominantly for human consumption. Even as
+ <p>Today's web is built predominantly for human readers. Even as
machine-readable data begins to permeate the web, it is typically
distributed in a separate file, with a separate format, and very limited
correspondence between the human and machine versions. As a result, web
browsers can provide only minimal assistance to humans in parsing and
- processing web data: browsers only see presentation information. RDFa is
- intended to solve the problem of machine-readable data in HTML documents.
- RDFa provides a set of HTML attributes to augment visual data with
+ processing web pages: browsers only see presentation information. RDFa is
+ intended to solve the problem of marking up machine-readable data in HTML
+ documents. RDFa provides a set of HTML attributes to augment visual data with
machine-readable hints. Using RDFa, authors may turn their existing
human-visible text and links into machine-readable data without repeating
content.</p>
@@ -652,7 +653,7 @@
<li>If HTML4 is the target language, the document <em class="rfc2119" title="should">should</em> conform to the
constraints expressed in the
<a href="#html-rdfa-dtd">HTML 4.01 + RDFa 1.1 Document Type Definition</a>
- located in the Appendix.
+ located in Appendix A.
</li>
</ul>
@@ -744,8 +745,10 @@
according to [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>] with the following extensions:</p>
<ul>
<li>The <a class="tref" title="default_vocabulary_URI">default vocabulary URI</a> is undefined.</li>
- <li>The <a class="tref" title="default_RDFa_profile">default RDFa profile</a> document is
- <code>http://www.w3.org/1999/xhtml/vocab</code>.</li>
+ <li>HTML+RDFa uses two profiles by default - first incorporating the
+ XML+RDFa profile document <code>http://www.w3.org/profile/rdfa-1.1</code>,
+ and then incorporating the RDFa Profile at
+ <code>http://www.w3.org/profile/html-rdfa-1.1</code>.</li>
<li>The <a class="tref" title="base">base</a> can be set using the <code>base</code> element.</li>
<li>The <a class="tref" title="current_language">current language</a> can be set using either the
<span class="aref">@lang</span> or <span class="aref">@xml:lang</span> attributes.</li>
@@ -762,6 +765,18 @@
<code>body</code> element. If it is, then act as if there is an empty <span class="aref">@about</span> present,
and process it according to the rule for <span class="aref">@about</span>.</li>
</ul>
+
+<p>
+The <code>version</code> attribute is not supported in HTML5 and is
+non-conforming. However, if an HTML+RDFa document contains the
+<code>version</code> attribute on the <code>html</code> element, a conforming
+RDFa Processor must examine the value of this attribute. If the value matches
+that of a defined version of RDFa, then the processing rules for that version
+must be used. If the value does not match a defined version, or there is no
+<code>version</code> attribute, then the processing rules for the most recent
+version of RDFa 1.1 must be used.
+</p>
+
</div>
<div id="modifying-the-input-document" typeof="bibo:Chapter" about="#modifying-the-input-document" class="section">
@@ -876,8 +891,8 @@
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>
+ 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>
@@ -896,39 +911,6 @@
<p></p>
</div>
-
- <div id="xmlns--prefixed-attributes" typeof="bibo:Chapter" about="#xmlns--prefixed-attributes" class="section">
- <h3><span class="secno">3.5 </span><code>xmlns:</code>-Prefixed Attributes</h3>
-
- <p>The RDFa Core 1.1 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>] specification effectively deprecates the
- use of the <code>xmlns:</code> mechanism to declare CURIE prefix mappings in
- favor of the <code>prefix</code> attribute. While utilizing
- <code>xmlns:</code> is now frowned upon, there are instances where it is
- unavoidable - such as publishing legacy documents as HTML5 or supporting
- older XHTML+RDFa 1.0 documents that rely on the <code>xmlns:</code>
- attribute.</p>
-
- <p>CURIE prefix mappings specified using attributes prepended with
- <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,
- CURIE prefix names declared using the <code>xmlns:</code>attribute-name
- pattern <code>xmlns:<PREFIX>="<URI>"</code> <em class="rfc2119" title="should">should</em> be specified
- using only lower-case characters. For example, the text
- "<code>xmlns:</code>" and the text in <code>"<PREFIX>"</code> <em class="rfc2119" title="should">should</em>
- be lower-case only. This is to ensure that prefix mappings are interpreted
- in the same way between HTML (case-insensitive attribute names) and XHTML
- (case-sensitive attribute names) document types.</p>
- </div>
</div>
@@ -937,96 +919,147 @@
<!-- OddPage -->
<h2><span class="secno">4. </span>Extensions to the HTML5 Syntax</h2>
- <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 extensions to the base HTML5 specification.</p>
-
-<div id="the-rdfa-attributes-and-valid-values" typeof="bibo:Chapter" about="#the-rdfa-attributes-and-valid-values" class="section">
- <h3><span class="secno">4.1 </span>The RDFa Attributes and Valid Values</h3>
+ <p>There are a few attributes that are added as extensions to the HTML5
+ syntax in order to fully support RDFa:
- <p>All RDFa attributes and valid values (including CURIEs), as listed in
+ </p><ul>
+ <li>All RDFa attributes and valid values (including CURIEs), as listed in
<a href="http://www.w3.org/TR/rdfa-core/#rdfa-attributes">Section 2.1:
- The RDFa Attributes</a>, are conforming when used in an HTML4, HTML5
- or XHTML5 document.</p>
+ The RDFa Attributes</a>, <em class="rfc2119" title="must">must</em> be allowed and seen as conforming when used in
+ an HTML4, HTML5 or XHTML5 document.</li>
+ </ul>
</div>
-<div id="conformance-criteria-for-xmlns--prefixed-attributes" typeof="bibo:Chapter" about="#conformance-criteria-for-xmlns--prefixed-attributes" class="section">
- <h3><span class="secno">4.2 </span>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
- <p>Since RDFa documents may contain attributes starting with
- <code>xmlns:</code> to specify
- 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>
+<div id="backwards-compatibility" typeof="bibo:Chapter" about="#backwards-compatibility" class="section">
- <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 [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-NAMES11">XML-NAMES11</a></cite>],
- <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>
+<!-- OddPage -->
+<h2><span class="secno">5. </span>Backwards Compatibility</h2>
-<div id="preserving-namespaces-via-coercion-to-infoset" typeof="bibo:Chapter" about="#preserving-namespaces-via-coercion-to-infoset" class="section">
- <h3><span class="secno">4.3 </span>Preserving Namespaces via Coercion to Infoset</h3>
+ <p>RDFa Core 1.1 deprecates the usage of <code>xmlns:</code> in RDFa 1.1
+ documents. Web page authors <em class="rfc2119" title="should not">should not</em> use <code>xmlns:</code> to express
+ prefix mappings in RDFa 1.1 documents. Web page authors <em class="rfc2119" title="should">should</em> use
+ the <code>prefix</code> attribute to specify prefix mappings.</p>
- <p class="issue">This section needs feedback from the user agent vendors to
- ensure that this feature does not conflict with user agent architecture and
- has no technical reason that it cannot be implemented.</p>
+ <p>However, there are times when XHTML+RDFa 1.0 documents are served by web
+ servers using the <code>text/html</code> MIMEType. In these instances, the
+ HTML5 specification asserts that the document is processed according to the
+ non-XML mode HTML5 processing rules. In these particular cases, it is
+ important that the prefixes declared via <code>xmlns:</code> are preserved
+ for the RDFa processors to ensure backwards-compatibility with RDFa 1.0
+ documents. The following sections detail the backwards compatibility
+ details for RDFa processor implementations.</p>
- <p>RDFa documents may contain the <code>xmlns:</code> pattern to
- declare prefix mappings, it is important that namespace information that
- 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]
- must be extended to include the following rule:</p>
+ <div id="xmlns--prefixed-attributes" typeof="bibo:Chapter" about="#xmlns--prefixed-attributes" class="section">
+ <h3><span class="secno">5.1 </span><code>xmlns:</code>-Prefixed Attributes</h3>
- <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. 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>The RDFa Core 1.1 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>] specification effectively deprecates the
+ use of the <code>xmlns:</code> mechanism to declare CURIE prefix mappings in
+ favor of the <code>prefix</code> attribute. While utilizing
+ <code>xmlns:</code> is now frowned upon, there are instances where it is
+ unavoidable - such as publishing legacy documents as HTML5 or supporting
+ older XHTML+RDFa 1.0 documents that rely on the <code>xmlns:</code>
+ attribute.</p>
- <p>For example, given the following input text:</p>
-<pre class="example">
-<div xmlns:com="http://purl.org/commerce#"></pre>
+ <p>CURIE prefix mappings specified using attributes prepended with
+ <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>
-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>com</code>, and a [normalized value] of
-"<code>http://purl.org/commerce#</code>".
-</p>
+ <p>Since CURIE prefix mappings have been specified using
+ <code>xmlns:</code>, and since HTML attribute names are case-insensitive,
+ CURIE prefix names declared using the <code>xmlns:</code>attribute-name
+ pattern <code>xmlns:<PREFIX>="<URI>"</code> <em class="rfc2119" title="should">should</em> be specified
+ using only lower-case characters. For example, the text
+ "<code>xmlns:</code>" and the text in <code>"<PREFIX>"</code> <em class="rfc2119" title="should">should</em>
+ be lower-case only. This is to ensure that prefix mappings are interpreted
+ in the same way between HTML (case-insensitive attribute names) and XHTML
+ (case-sensitive attribute names) document types.</p>
+ </div>
-</div>
+ <div id="conformance-criteria-for-xmlns--prefixed-attributes" typeof="bibo:Chapter" about="#conformance-criteria-for-xmlns--prefixed-attributes" class="section">
+ <h3><span class="secno">5.2 </span>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
-<div id="infoset-based-processors" typeof="bibo:Chapter" about="#infoset-based-processors" class="section">
- <h3><span class="secno">4.4 </span>Infoset-based Processors</h3>
+ <p>Since RDFa 1.0 documents may contain attributes starting with
+ <code>xmlns:</code> to specify 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. Conformance checkers <em class="rfc2119" title="should">should</em> generate
+ warnings noting that the use of <code>xmlns:</code> is deprecated.
+ </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 [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-NAMES11">XML-NAMES11</a></cite>],
+ <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>
- <p>While the intent of the RDFa processing instructions were to provide a
- set of rules that are as language and toolchain agnostic as possible, for
- the sake of clarity, detailed methods of extracting RDFa content from
- processors operating on an XML Information Set are provided below.</p>
+ <div id="preserving-namespaces-via-coercion-to-infoset" typeof="bibo:Chapter" about="#preserving-namespaces-via-coercion-to-infoset" class="section">
+ <h3><span class="secno">5.3 </span>Preserving Namespaces via Coercion to Infoset</h3>
-<div id="extracting-uri-mappings-from-infosets" typeof="bibo:Chapter" about="#extracting-uri-mappings-from-infosets" class="section">
- <h4><span class="secno">4.4.1 </span>Extracting URI Mappings from Infosets</h4>
+ <p class="issue">This section needs feedback from the user agent vendors to
+ ensure that this feature does not conflict with user agent architecture and
+ has no technical reason that it cannot be implemented.</p>
+
+ <p>RDFa 1.0 documents may contain the <code>xmlns:</code> pattern to
+ declare prefix mappings, it is important that namespace information that
+ 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]
+ must be extended to include the following rule:</p>
+
+ <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. 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:com="http://purl.org/commerce#"></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>com</code>, and a [normalized value] of
+ "<code>http://purl.org/commerce#</code>".
+ </p>
+ </div>
+
+ <div id="infoset-based-processors" typeof="bibo:Chapter" about="#infoset-based-processors" class="section">
+ <h3><span class="secno">5.4 </span>Infoset-based Processors</h3>
+
+ <p>While the intent of the RDFa processing instructions are to provide a
+ set of rules that are as language and toolchain agnostic as possible, for
+ the sake of clarity, detailed methods of extracting RDFa content from
+ processors operating on an XML Information Set are provided below.</p>
+
+ <div id="extracting-uri-mappings-from-infosets" typeof="bibo:Chapter" about="#extracting-uri-mappings-from-infosets" class="section">
+ <h4><span class="secno">5.4.1 </span>Extracting URI Mappings from Infosets</h4>
<p>Extracting URI Mappings declared via <code>xmlns:</code>
while operating from within an Infoset-based RDFa processor can be achieved
@@ -1068,7 +1101,7 @@
</div>
<div id="processing-rdfa-attributes" typeof="bibo:Chapter" about="#processing-rdfa-attributes" class="section">
- <h4><span class="secno">4.4.2 </span>Processing RDFa Attributes</h4>
+ <h4><span class="secno">5.4.2 </span>Processing RDFa Attributes</h4>
<p>There are a number of non-prefixed attributes that are associated with
RDFa Processing in HTML5. If an XML Information Set based RDFa processor is
@@ -1091,7 +1124,7 @@
</div>
<div id="dom-level-1-and-level-2-based-processors" typeof="bibo:Chapter" about="#dom-level-1-and-level-2-based-processors" class="section">
- <h3><span class="secno">4.5 </span>DOM Level 1 and Level 2-based Processors</h3>
+ <h3><span class="secno">5.5 </span>DOM Level 1 and Level 2-based Processors</h3>
<p class="issue">This mechanism should be double-checked against all of the
RDFa Javascript implementations to ensure correctness.</p>
@@ -1118,7 +1151,7 @@
environment mechanism.</p>
<div id="extracting-uri-mappings-via-dom-level-2" typeof="bibo:Chapter" about="#extracting-uri-mappings-via-dom-level-2" class="section">
- <h4><span class="secno">4.5.1 </span>Extracting URI Mappings via DOM Level 2</h4>
+ <h4><span class="secno">5.5.1 </span>Extracting URI Mappings via DOM Level 2</h4>
<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
@@ -1161,7 +1194,7 @@
</div>
<div id="processing-rdfa-attributes-1" typeof="bibo:Chapter" about="#processing-rdfa-attributes-1" class="section">
- <h4><span class="secno">4.5.2 </span>Processing RDFa Attributes</h4>
+ <h4><span class="secno">5.5.2 </span>Processing RDFa Attributes</h4>
<p>There are a number of non-prefixed attributes that are associated with
RDFa processing in HTML5. If an DOM2-based RDFa processor is used to
@@ -2380,6 +2413,9 @@
<p>2011-01-11: Removed decentralized extensibility issue markers, added
DOM Level 1 prefix mapping extraction algorithm.
</p>
+<p>2011-04-05: Moved all xmlns: rules into a section titled Backwards
+Compatibility and brought spec in-line with latest RDFa Core 1.1 spec.
+</p>
</div>
<div class="informative section" id="acknowledgments" typeof="bibo:Chapter" about="#acknowledgments">
@@ -2389,7 +2425,7 @@
RDFa Working Group were:</p>
<p>
-Ben Adida (chair), Benjamin Adrian, Mark Birbeck, Ivan Herman (staff contact), Toby Inkster, Shane McCarron, Knud Möller, Steven Pemberton, Nathan Rixham, Manu Sporny (chair)
+Ben Adida, Benjamin Adrian, Mark Birbeck, Ivan Herman (staff contact), Toby Inkster, Shane McCarron, Knud Möller, Steven Pemberton, Nathan Rixham, Manu Sporny (chair), Thomas Steiner, Ted Thibodeau
</p>
<p>At the time of publication, the members of the HTML Working Group were:</p>
@@ -2405,13 +2441,13 @@
<div id="references" class="appendix section" typeof="bibo:Chapter" about="#references">
<!-- OddPage -->
-<h2><span class="secno">C. </span>References</h2><div id="normative-references" typeof="bibo:Chapter" about="#normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-DOM-LEVEL-1">[DOM-LEVEL-1]</dt><dd rel="dcterms:requires">Vidur Apparao; et al. <a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/"><cite>Document Object Model (DOM) Level 1.</cite></a> 1 October 1998. W3C Recommendation. URL: <a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/">http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/</a>
-</dd><dt id="bib-DOM-LEVEL-2-CORE">[DOM-LEVEL-2-CORE]</dt><dd rel="dcterms:requires">Arnaud Le Hors; et al. <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/"><cite>Document Object Model (DOM) Level 2 Core Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/">http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/</a>
-</dd><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires">Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2010/WD-html5-20100304/"><cite>HTML 5.</cite></a> 4 March 2010. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2010/WD-html5-20100304/">http://www.w3.org/TR/2010/WD-html5-20100304/</a>
-</dd><dt id="bib-RDFA-CORE">[RDFA-CORE]</dt><dd rel="dcterms:requires">Shane McCarron; et al. <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20101026"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a>26 October 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20101026">http://www.w3.org/TR/2010/WD-rdfa-core-20101026</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-RFC3236">[RFC3236]</dt><dd rel="dcterms:requires">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 rel="dcterms:requires">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" typeof="bibo:Chapter" about="#informative-references" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-RDFA-SYNTAX">[RDFA-SYNTAX]</dt><dd rel="dcterms:references">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 rel="dcterms:references">Shane McCarron; et. al. <a href="http://www.w3.org/TR/2010/WD-xhtml-rdfa-20100803"><cite>XHTML+RDFa 1.1.</cite></a> 3 August 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-xhtml-rdfa-20100803">http://www.w3.org/TR/WD-xhtml-rdfa-20100803</a>
+<h2><span class="secno">C. </span>References</h2><div id="normative-references" typeof="bibo:Chapter" about="#normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography" about="http://sites.local/dev.w3.org/html5/rdfa/Overview-src.html#xmlns--prefixed-attributes"><dt id="bib-DOM-LEVEL-1">[DOM-LEVEL-1]</dt><dd rel="dcterms:requires" about="_:0">Vidur Apparao; et al. <a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/"><cite>Document Object Model (DOM) Level 1.</cite></a> 1 October 1998. W3C Recommendation. URL: <a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/">http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/</a>
+</dd><dt id="bib-DOM-LEVEL-2-CORE">[DOM-LEVEL-2-CORE]</dt><dd rel="dcterms:requires" about="_:1">Arnaud Le Hors; et al. <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/"><cite>Document Object Model (DOM) Level 2 Core Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/">http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/</a>
+</dd><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires" about="_:2">Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2010/WD-html5-20100304/"><cite>HTML 5.</cite></a> 4 March 2010. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2010/WD-html5-20100304/">http://www.w3.org/TR/2010/WD-html5-20100304/</a>
+</dd><dt id="bib-RDFA-CORE">[RDFA-CORE]</dt><dd rel="dcterms:requires" about="_:3">Shane McCarron; et al. <a href="http://www.w3.org/TR/2011/WD-rdfa-core-20110331"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a>31 March 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-rdfa-core-20110331">http://www.w3.org/TR/2011/WD-rdfa-core-20110331</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires" about="_:4">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-RFC3236">[RFC3236]</dt><dd rel="dcterms:requires" about="_:5">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 rel="dcterms:requires" about="_:6">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" typeof="bibo:Chapter" about="#informative-references" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about="http://sites.local/dev.w3.org/html5/rdfa/Overview-src.html#xmlns--prefixed-attributes"><dt id="bib-RDFA-SYNTAX">[RDFA-SYNTAX]</dt><dd rel="dcterms:references" about="_:7">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 rel="dcterms:references" about="_:8">Shane McCarron; et. al. <a href="http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331"><cite>XHTML+RDFa 1.1.</cite></a> 31 March 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331">http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331</a>
</dd></dl></div></div></body></html>
Index: Overview-src.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview-src.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- Overview-src.html 12 Jan 2011 03:39:25 -0000 1.17
+++ Overview-src.html 5 Apr 2011 14:40:56 -0000 1.18
@@ -118,7 +118,7 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ specStatus: "WD",
//publishDate: "2010-10-19",
diffTool: "http://www3.aptest.com/standards/htmldiff/htmldiff.pl",
@@ -174,8 +174,8 @@
doRDFa: true,
alternateFormats: [
-// { uri: 'diff-20101019.html',
-// label: "Changes since previous Working Draft" }
+ { uri: 'diff-20110113.html',
+ label: "Changes since previous Working Draft" }
// { uri: 'html-rdfa.ps',
// label: 'Postscript version' },
// { uri: 'html-rdfa.pdf',
@@ -262,6 +262,7 @@
are going to use xmlns: in HTML5 documents, the rules need to be clear in
the cases where this happens.</li>
<li>Added DOM Level 1 prefix mapping algorithm.</li>
+<li>Added backwards-compatibility section for xmlns:.</li>
</ol>
<p>The latest stable version of the editor's draft of this specification is
@@ -280,7 +281,7 @@
content in the HTML5 specification, unless specifically overridden by this
specification, is intended to be the basis for this specification.</p>
-<p>A <a href="http://rdfa.digitalbazaar.com/rdfa-test-harness/">sample
+<p>A <a href="http://rdfa.digitalbazaar.com/test-suite/">sample
test harness</a> is available. This set of tests is
not intended to be exhaustive. Users may find the tests to
be useful examples of RDFa usage.
@@ -308,14 +309,14 @@
<section class='informative'>
<h2>Introduction</h2>
- <p>Today's web is built predominantly for human consumption. Even as
+ <p>Today's web is built predominantly for human readers. Even as
machine-readable data begins to permeate the web, it is typically
distributed in a separate file, with a separate format, and very limited
correspondence between the human and machine versions. As a result, web
browsers can provide only minimal assistance to humans in parsing and
- processing web data: browsers only see presentation information. RDFa is
- intended to solve the problem of machine-readable data in HTML documents.
- RDFa provides a set of HTML attributes to augment visual data with
+ processing web pages: browsers only see presentation information. RDFa is
+ intended to solve the problem of marking up machine-readable data in HTML
+ documents. RDFa provides a set of HTML attributes to augment visual data with
machine-readable hints. Using RDFa, authors may turn their existing
human-visible text and links into machine-readable data without repeating
content.</p>
@@ -347,7 +348,7 @@
<li>If HTML4 is the target language, the document SHOULD conform to the
constraints expressed in the
<a href="#html-rdfa-dtd">HTML 4.01 + RDFa 1.1 Document Type Definition</a>
- located in the Appendix.
+ located in Appendix A.
</li>
</ul>
@@ -441,8 +442,10 @@
according to [[!RDFA-CORE]] with the following extensions:</p>
<ul>
<li>The <tref>default vocabulary URI</tref> is undefined.</li>
- <li>The <tref>default RDFa profile</tref> document is
- <code>http://www.w3.org/1999/xhtml/vocab</code>.</li>
+ <li>HTML+RDFa uses two profiles by default - first incorporating the
+ XML+RDFa profile document <code>http://www.w3.org/profile/rdfa-1.1</code>,
+ and then incorporating the RDFa Profile at
+ <code>http://www.w3.org/profile/html-rdfa-1.1</code>.</li>
<li>The <tref>base</tref> can be set using the <code>base</code> element.</li>
<li>The <tref>current language</tref> can be set using either the
<aref>lang</aref> or <aref>xml:lang</aref> attributes.</li>
@@ -459,6 +462,18 @@
<code>body</code> element. If it is, then act as if there is an empty <aref>about</aref> present,
and process it according to the rule for <aref>about</aref>.</li>
</ul>
+
+<p>
+The <code>version</code> attribute is not supported in HTML5 and is
+non-conforming. However, if an HTML+RDFa document contains the
+<code>version</code> attribute on the <code>html</code> element, a conforming
+RDFa Processor must examine the value of this attribute. If the value matches
+that of a defined version of RDFa, then the processing rules for that version
+must be used. If the value does not match a defined version, or there is no
+<code>version</code> attribute, then the processing rules for the most recent
+version of RDFa 1.1 must be used.
+</p>
+
</section>
<section>
@@ -582,8 +597,8 @@
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>
+ 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>
@@ -605,137 +620,153 @@
</p>
</section>
-
- <section>
- <h3><code>xmlns:</code>-Prefixed Attributes</h3>
-
- <p>The RDFa Core 1.1 [[!RDFA-CORE]] specification effectively deprecates the
- use of the <code>xmlns:</code> mechanism to declare CURIE prefix mappings in
- favor of the <code>prefix</code> attribute. While utilizing
- <code>xmlns:</code> is now frowned upon, there are instances where it is
- unavoidable - such as publishing legacy documents as HTML5 or supporting
- older XHTML+RDFa 1.0 documents that rely on the <code>xmlns:</code>
- attribute.</p>
-
- <p>CURIE prefix mappings specified using attributes prepended with
- <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,
- CURIE prefix names declared using the <code>xmlns:</code>attribute-name
- pattern <code>xmlns:<PREFIX>="<URI>"</code> SHOULD be specified
- using only lower-case characters. For example, the text
- "<code>xmlns:</code>" and the text in <code>"<PREFIX>"</code> SHOULD
- be lower-case only. This is to ensure that prefix mappings are interpreted
- in the same way between HTML (case-insensitive attribute names) and XHTML
- (case-sensitive attribute names) document types.</p>
- </section>
</section>
<section>
<h2>Extensions to the HTML5 Syntax</h2>
- <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 extensions to the base HTML5 specification.</p>
-
-<section>
- <h3>The RDFa Attributes and Valid Values</h3>
+ <p>There are a few attributes that are added as extensions to the HTML5
+ syntax in order to fully support RDFa:
- <p>All RDFa attributes and valid values (including CURIEs), as listed in
+ <ul>
+ <li>All RDFa attributes and valid values (including CURIEs), as listed in
<a href="http://www.w3.org/TR/rdfa-core/#rdfa-attributes">Section 2.1:
- The RDFa Attributes</a>, are conforming when used in an HTML4, HTML5
- or XHTML5 document.</p>
+ The RDFa Attributes</a>, MUST be allowed and seen as conforming when used in
+ an HTML4, HTML5 or XHTML5 document.</li>
+ </ul>
</section>
+</section>
<section>
- <h3>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
+ <h2>Backwards Compatibility</h2>
- <p>Since RDFa documents may contain attributes starting with
- <code>xmlns:</code> to specify
- 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>
+ <p>RDFa Core 1.1 deprecates the usage of <code>xmlns:</code> in RDFa 1.1
+ documents. Web page authors SHOULD NOT use <code>xmlns:</code> to express
+ prefix mappings in RDFa 1.1 documents. Web page authors SHOULD use
+ the <code>prefix</code> attribute to specify prefix mappings.</p>
-<section>
- <h3>Preserving Namespaces via Coercion to Infoset</h3>
+ <p>However, there are times when XHTML+RDFa 1.0 documents are served by web
+ servers using the <code>text/html</code> MIMEType. In these instances, the
+ HTML5 specification asserts that the document is processed according to the
+ non-XML mode HTML5 processing rules. In these particular cases, it is
+ important that the prefixes declared via <code>xmlns:</code> are preserved
+ for the RDFa processors to ensure backwards-compatibility with RDFa 1.0
+ documents. The following sections detail the backwards compatibility
+ details for RDFa processor implementations.</p>
- <p class="issue">This section needs feedback from the user agent vendors to
- ensure that this feature does not conflict with user agent architecture and
- has no technical reason that it cannot be implemented.</p>
+ <section>
+ <h3><code>xmlns:</code>-Prefixed Attributes</h3>
- <p>RDFa documents may contain the <code>xmlns:</code> pattern to
- declare prefix mappings, it is important that namespace information that
- 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 extended to include the following rule:</p>
+ <p>The RDFa Core 1.1 [[!RDFA-CORE]] specification effectively deprecates the
+ use of the <code>xmlns:</code> mechanism to declare CURIE prefix mappings in
+ favor of the <code>prefix</code> attribute. While utilizing
+ <code>xmlns:</code> is now frowned upon, there are instances where it is
+ unavoidable - such as publishing legacy documents as HTML5 or supporting
+ older XHTML+RDFa 1.0 documents that rely on the <code>xmlns:</code>
+ attribute.</p>
- <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. 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>CURIE prefix mappings specified using attributes prepended with
+ <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>For example, given the following input text:</p>
-<pre class="example">
- <div xmlns:com="http://purl.org/commerce#">
-</pre>
+ <p>Since CURIE prefix mappings have been specified using
+ <code>xmlns:</code>, and since HTML attribute names are case-insensitive,
+ CURIE prefix names declared using the <code>xmlns:</code>attribute-name
+ pattern <code>xmlns:<PREFIX>="<URI>"</code> SHOULD be specified
+ using only lower-case characters. For example, the text
+ "<code>xmlns:</code>" and the text in <code>"<PREFIX>"</code> SHOULD
+ be lower-case only. This is to ensure that prefix mappings are interpreted
+ in the same way between HTML (case-insensitive attribute names) and XHTML
+ (case-sensitive attribute names) document types.</p>
+ </section>
-<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>com</code>, and a [normalized value] of
-"<code>http://purl.org/commerce#</code>".
-</p>
+ <section>
+ <h3>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
-</section>
+ <p>Since RDFa 1.0 documents may contain attributes starting with
+ <code>xmlns:</code> to specify 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. Conformance checkers SHOULD generate
+ warnings noting that the use of <code>xmlns:</code> is deprecated.
+ </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>
- <h2>Infoset-based Processors</h2>
+ <section>
+ <h3>Preserving Namespaces via Coercion to Infoset</h3>
- <p>While the intent of the RDFa processing instructions were to provide a
- set of rules that are as language and toolchain agnostic as possible, for
- the sake of clarity, detailed methods of extracting RDFa content from
- processors operating on an XML Information Set are provided below.</p>
+ <p class="issue">This section needs feedback from the user agent vendors to
+ ensure that this feature does not conflict with user agent architecture and
+ has no technical reason that it cannot be implemented.</p>
-<section>
+ <p>RDFa 1.0 documents may contain the <code>xmlns:</code> pattern to
+ declare prefix mappings, it is important that namespace information that
+ 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 extended to include the following rule:</p>
+
+ <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. 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:com="http://purl.org/commerce#">
+ </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>com</code>, and a [normalized value] of
+ "<code>http://purl.org/commerce#</code>".
+ </p>
+ </section>
+
+ <section>
+ <h2>Infoset-based Processors</h2>
+
+ <p>While the intent of the RDFa processing instructions are to provide a
+ set of rules that are as language and toolchain agnostic as possible, for
+ the sake of clarity, detailed methods of extracting RDFa content from
+ processors operating on an XML Information Set are provided below.</p>
+
+ <section>
<h3>Extracting URI Mappings from Infosets</h3>
<p>Extracting URI Mappings declared via <code>xmlns:</code>
@@ -1014,6 +1045,9 @@
<p>2011-01-11: Removed decentralized extensibility issue markers, added
DOM Level 1 prefix mapping extraction algorithm.
</p>
+<p>2011-04-05: Moved all xmlns: rules into a section titled Backwards
+Compatibility and brought spec in-line with latest RDFa Core 1.1 spec.
+</p>
</section>
<section class='informative'>
@@ -1023,7 +1057,7 @@
RDFa Working Group were:</p>
<p>
-Ben Adida (chair), Benjamin Adrian, Mark Birbeck, Ivan Herman (staff contact), Toby Inkster, Shane McCarron, Knud Möller, Steven Pemberton, Nathan Rixham, Manu Sporny (chair)
+Ben Adida, Benjamin Adrian, Mark Birbeck, Ivan Herman (staff contact), Toby Inkster, Shane McCarron, Knud Möller, Steven Pemberton, Nathan Rixham, Manu Sporny (chair), Thomas Steiner, Ted Thibodeau
</p>
<p>At the time of publication, the members of the HTML Working Group were:</p>
Received on Tuesday, 5 April 2011 14:41:09 UTC