W3C home > Mailing lists > Public > public-html-commits@w3.org > January 2011

html5/rdfa Overview-src.html,1.13,1.14

From: Manu Sporny via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 12 Jan 2011 02:44:57 +0000
To: public-html-commits@w3.org
Message-Id: <E1Pcqhl-0007RG-64@lionel-hutz.w3.org>
Update of /sources/public/html5/rdfa
In directory hutz:/tmp/cvs-serv28406

Modified Files:
	Overview-src.html 
Log Message:
[html+rdfa] Removed a few issue markers, added DOM1 prefix algorithm.


Index: Overview-src.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview-src.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- Overview-src.html	20 Oct 2010 21:40:39 -0000	1.13
+++ Overview-src.html	12 Jan 2011 02:44:55 -0000	1.14
@@ -162,11 +162,11 @@
           // only "name" is required. Same format as editors.
 
           authors:  [
-              { name: "Ben Adida", url: "",
+              { name: "Ben Adida", url: "http://adida.net/",
                 company: "Creative Commons", companyURL: "http://creativecommons.org/" },
-              { name: "Mark Birbeck", url: "",
+              { name: "Mark Birbeck", url: "http://webbackplane.com/",
                 company: "Web Backplane Ltd.", companyURL: "http://webbackplane.com/" },
-              { name: "Steven Pemberton", url: "",
+              { name: "Steven Pemberton", url: "http://homepages.cwi.nl/~steven/",
                 company: "CWI", companyURL: "http://www.cwi.nl/" },
           ],
 
@@ -258,13 +258,10 @@
 <p>There are a few substantive differences between this version and its 
 predecessor, including:</p>
 <ol>
-<li>The removal of the <code>@version</code> attribute to bring the 
-specification more in-line with HTML5's version-less design.</li>
-<li>Removed the HTML Default Vocabulary Terms section from this document, 
-instead deferring the definitions in a default RDFa Profile document, which is
-also shared with XHTML+RDFa for the purposes of consistency and
-interoperability.</li>
-<li>The addition of RDFa to the document markup.</li>
+<li>Removal of the decentralized extensibility issue markers - web developers
+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>
 </ol>
 
 <p>The latest stable version of the editor's draft of this specification is
@@ -612,11 +609,13 @@
   <section>
   <h3><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
-  and xmlns:) is still an open issue. This section may be further modified
-  before Last Call based on progress made on the distributed extensibility
-  issue.</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>CURIE prefix mappings specified using attributes prepended with
   <code>xmlns:</code> MUST be processed using the algorithm defined in
@@ -645,8 +644,6 @@
 <section>
   <h2>Extensions to the HTML5 Syntax</h2>
 
-  <p class="issue"><b>Status:</b> <a href="http://www.w3.org/html/wg/tracker/issues/41">ISSUE-41</a> (decentralized extensibility) blocks progress to Last Call</p>
-
   <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>
@@ -656,21 +653,16 @@
 
   <p>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 HTML5 or XHTML5
-  document.</p>
+  The RDFa Attributes</a>, are conforming when used in an HTML4, HTML5 
+  or XHTML5 document.</p>
 
 </section>
 
 <section>
   <h3>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
 
-  <p class="issue">While this section outlines xmlns: conformance criteria for
-  HTML+RDFa, the support for distributed extensibility in non-XML mode HTML5
-  (using xmlns and xmlns:) is still an open issue. This section may be
-  further modified before Last Call based on progress made on the distributed
-  extensibility issue.</p>
-
-  <p>Since RDFa uses attributes starting with <code>xmlns:</code> to specify
+  <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.
@@ -697,7 +689,7 @@
   ensure that this feature does not conflict with user agent architecture and
   has no technical reason that it cannot be implemented.</p>
 
-  <p>RDFa is uses the <code>xmlns:</code> pattern to
+  <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
@@ -720,7 +712,7 @@
 
   <p>For example, given the following input text:</p>
 <pre class="example">
-   &lt;div xmlns:audio="http://purl.org/media/audio#"&gt;
+   &lt;div xmlns:com="http://purl.org/commerce#"&gt;
 </pre>
 
 <p>
@@ -729,8 +721,8 @@
 "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>".
+<code>com</code>, and a [normalized value] of
+"<code>http://purl.org/commerce#</code>".
 </p>
 
 </section>
@@ -819,18 +811,34 @@
 </section>
 
 <section>
-  <h2>DOM Level 2-based Processors</h2>
+  <h2>DOM Level 1 and Level 2-based Processors</h2>
 
   <p class="issue">This mechanism should be double-checked against all of the
   RDFa Javascript implementations to ensure correctness.</p>
 
-  <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 in a DOM2 environment are provided below.</p>
+  <p>Most DOM-aware RDFa Processors are capable of accessing DOM Level 1 
+  [[!DOM1-LEVEL-1]]
+  methods to process attributes on elements. To discover all
+  <code>xmlns:</code>-specified CURIE prefix mappings, the
+  <a href="http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-1950641247">
+  Node.attributes</a>
+  <a href="http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-1780488922">
+  NamedNodeMap</a> can be iterated over. Each 
+  <a href="http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-637646024">
+  Attr.name</a> that
+  starts with the text string <code>xmlns:</code> specifies a CURIE prefix 
+  mapping. The value to be mapped is the string after the <code>xmlns:</code>
+  substring in the Attr.name variable and the value to be mapped is 
+  the value of the Attr.value variable.</p>
+
+  <p>The intent of the RDFa processing instructions are to provide a
+  set of rules that are as language and toolchain agnostic as possible. If
+  a developer chooses to not use the DOM1 environment mechanism outlined in
+  the previous paragraph, they may use the following DOM2 [[!DOM-LEVEL-2]]
+  environment mechanism.</p>
 
 <section>
-  <h3>Extracting URI Mappings from DOMs</h3>
+  <h3>Extracting URI Mappings via DOM Level 2</h3>
 
   <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 
@@ -878,11 +886,11 @@
   <p>For example, assume that the following markup is processed by a
   DOM2-based RDFa processor:</p>
   <pre class="example">
-&lt;div xmlns:audio="http://purl.org/media/audio#" ...
+&lt;div xmlns:com="http://purl.org/commerce#" ...
 </pre>
 <p>After the markup is processed, there should exist a [URI mapping] in
 the [local list of URI mappings] that contains a mapping from
-<code>audio</code> to <code>http://purl.org/media/audio#</code>.
+<code>com</code> to <code>http://purl.org/commerce#</code>.
 </p>
 </section>
 
@@ -1003,6 +1011,9 @@
 <p>2010-10-19: Removal of @version attribute, migrated HTML Vocabulary Terms to
 RDFa Profile document, added statement to send comments to the HTML WG bug tracker.
 </p>
+<p>2011-01-11: Removed decentralized extensibility issue markers, added 
+DOM Level 1 prefix mapping extraction algorithm.
+</p>
 </section>
 
 <section class='informative'>
Received on Wednesday, 12 January 2011 02:44:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 January 2011 02:45:00 GMT