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

html5/rdfa Overview.html,1.13,1.14

From: Manu Sporny via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 20 Jan 2010 04:57:46 +0000
To: public-html-commits@w3.org
Message-Id: <E1NXSdW-0008F9-IP@lionel-hutz.w3.org>
Update of /sources/public/html5/rdfa
In directory hutz:/tmp/cvs-serv31571

Modified Files:
	Overview.html 
Log Message:
Updated HTML5 RDFa heartbeat WD and added diff-marked version.


Index: Overview.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- Overview.html	14 Oct 2009 03:18:06 -0000	1.13
+++ Overview.html	20 Jan 2010 04:57:44 -0000	1.14
@@ -203,8 +203,8 @@
     <h2 class="no-num no-toc" id="a-mechanism-for-embedding-rdf-in-html">A
     mechanism for embedding RDF in HTML</h2>
 
-    <h2 class="no-num no-toc" id="editor-s-draft-date-13-October-2009">W3C
-    Working Draft 15 October 2009</h2><!--:ZZZ-->
+    <h2 class="no-num no-toc" id="editor-s-draft-date-19-January-2010">W3C
+    Working Draft 15 January 2010</h2><!--:ZZZ-->
 
     <dl>
       <!-- ZZZ: update the month/day (twice), (un)comment out
@@ -215,13 +215,23 @@
       <dt>This Version</dt>
 
       <dd><a href=
-      "http://www.w3.org/TR/2009/WD-rdfa-in-html-20091015/">http://www.w3.org/TR/2009/WD-rdfa-in-html-20091015/</a></dd>
+      "http://dev.w3.org/html5/rdfa/">http://dev.w3.org/html5/rdfa/</a></dd>
 
       <dt>Latest Version</dt>
 
       <dd><a href=
       "http://www.w3.org/TR/rdfa-in-html/">http://www.w3.org/TR/rdfa-in-html/</a></dd>
 
+      <dt>Previous Versions</dt>
+
+      <dd><a href=
+      "http://www.w3.org/TR/2009/WD-rdfa-in-html-20091015/">http://www.w3.org/TR/2009/WD-rdfa-in-html-20091015/</a></dd>
+
+      <dt>Diff-marked version</dt>
+
+      <dd><a href=
+      "http://dev.w3.org/html5/rdfa/diffs/rdfa-diff-20091015-20100115.html">http://dev.w3.org/html5/rdfa/diffs/rdfa-diff-20091015-20100115.html</a></dd>
+
       <dt>Authors (alphabetical order):</dt>
 
       <dd>Ben Adida (Chair, RDFa Task Force, Creative Commons)</dd>
@@ -276,9 +286,20 @@
   can be found in the <a href="http://www.w3.org/TR/">W3C technical reports
   index</a> at http://www.w3.org/TR/.</em></p>
 
-  <p>This is the First Public Working Draft of the "HTML+RDFa: A mechanism
-  for embedding RDF in HTML" specification for review by W3C members and
-  other interested parties.</p>
+  <p>This is a Working Draft of the "HTML+RDFa: A mechanism for embedding RDF
+  in HTML" specification for review by W3C members and other interested
+  parties.</p>
+
+  <p>This Working Draft includes the following changes:</p>
+
+  <ul>
+    <li>Updating HTML5 coercion to Infoset rules (normative)</li>
+
+    <li>Clarifying how to extract RDFa attributes via Infoset
+    (informative)</li>
+
+    <li>Clarifying how to extract RDFa attributes via DOM2 (informative)</li>
+  </ul>
 
   <p>If you wish to make comments regarding this document, please send them
   to <a href=
@@ -416,27 +437,55 @@
         "#conformance-criteria-for-xmlns:-prefixed-attributes"><span class=
         "secno">5.2</span> Conformance Criteria for
         <code>xmlns:</code>-Prefixed Attributes</a></li>
+
+        <li><a href=
+        "#preserving-namespaces-via-coercion-to-infoset"><span class=
+        "secno">5.3</span> Preserving Namespaces via Coercion to
+        Infoset</a></li>
       </ol>
     </li>
 
     <li>
-      <a href="#references"><span class="secno">6</span> References</a>
+      <a href="#infoset-based-processors"><span class="secno">6</span>
+      Infoset-based Processors</a>
 
       <ol>
-        <li><a href="#normative-references"><span class="secno">6.1</span>
+        <li><a href="#processing-namespaced-rdfa-attributes"><span class=
+        "secno">6.1</span> Processing Namespaced RDFa Attributes</a></li>
+
+        <li><a href="#processing-rdfa-attributes"><span class=
+        "secno">6.2</span> Processing RDFa Attributes</a></li>
+      </ol>
+    </li>
+
+    <li>
+      <a href="#dom-level-2-based-processors"><span class="secno">7</span>
+      DOM Level 2-based Processors</a>
+
+      <ol>
+        <li><a href="#processing-namespaced-rdfa-attributes-0"><span class=
+        "secno">7.1</span> Processing Namespaced RDFa Attributes</a></li>
+
+        <li><a href="#processing-rdfa-attributes-0"><span class=
+        "secno">7.2</span> Processing RDFa Attributes</a></li>
+      </ol>
+    </li>
+
+    <li>
+      <a href="#references"><span class="secno">8</span> References</a>
+
+      <ol>
+        <li><a href="#normative-references"><span class="secno">8.1</span>
         Normative References</a></li>
 
         <li><a href="#non-normative-references"><span class=
-        "secno">6.2</span> Non-Normative References</a></li>
+        "secno">8.2</span> Non-Normative References</a></li>
       </ol>
     </li>
   </ol><!--end-toc-->
-  <hr>
 
   <h2 id="introduction"><span class="secno">1</span> Introduction</h2>
 
-  <p class="XXX annotation"><b>Status:</b> <i>Working draft</i></p>
-
   <p><em>This section is informative.</em></p>
 
   <p>Today's web is built predominantly for human consumption. Even as
@@ -453,8 +502,6 @@
 
   <h3 id="history"><span class="secno">1.1</span> History</h3>
 
-  <p class="XXX annotation"><b>Status:</b> <i>Working draft</i></p>
-
   <p>In early 2004, Mark Birbeck published a document named [<a href=
   "#refsXHTMLRDF">XHTMLRDF</a>] via the XHTML2 Working Group wherein he laid
   the groundwork for what would eventually become RDFa (The Resource
@@ -537,8 +584,6 @@
   <h2 id="conformance-requirements"><span class="secno">3</span> Conformance
   Requirements</h2>
 
-  <p class="XXX annotation"><b>Status:</b> <i>Working draft</i></p>
-
   <p><em>This section is normative.</em></p>
 
   <p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
@@ -768,11 +813,213 @@
   names that have the case insensitive prefix "<code>xmlns:</code>" are
   conforming in both HTML5 and XHTML5.</p>
 
-  <h2 id="references"><span class="secno">6</span> References</h2>
+  <h3 id="preserving-namespaces-via-coercion-to-infoset"><span class=
+  "secno">5.3</span> Preserving Namespaces via Coercion to Infoset</h3>
 
-  <p class="XXX annotation"><b>Status:</b> <i>First draft</i></p>
+  <p class="XXX">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>
 
-  <h3 id="normative-references"><span class="secno">6.1</span> Normative
+  <p>RDFa is currently dependent on the <code>xmlns:</code> pattern to
+  declare prefix mappings, it is imperative 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 [<a href=
+  "refsHTML5">HTML5</a>] must be modified to include the following rule:</p>
+
+  <p>If the XML API is namespace-aware, the tool must ensure that proper
+  ([<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>
+
+  <p>For example, given the following input text:</p>
+  <pre>
+       &lt;div xmlns:audio="http://purl.org/media/audio#"&gt;
+    
+</pre>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>".
+
+  <h2 id="infoset-based-processors"><span class="secno">6</span>
+  Infoset-based Processors</h2>
+
+  <p><em>This section is informative</em></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 on an XML Information Set are provided below.</p>
+
+  <h3 id="processing-namespaced-rdfa-attributes"><span class=
+  "secno">6.1</span> Processing Namespaced RDFa Attributes</h3>
+
+  <p>Extracting namespaced RDFa attributes 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 href=
+  "refsXHTMLRDFA">XHTML+RDFA</a>], Section 5.5, <a href=
+  "http://www.w3.org/TR/rdfa-syntax/#T_URI_mapping">Step #2</a>:</p>
+
+  <ol>
+    <li>For each attribute in the [<a href=
+    "http://www.w3.org/TR/xml-infoset/#infoitem.element">namespace
+    attributes</a>] list that has a [<a href=
+    "http://www.w3.org/TR/xml-infoset/#infoitem.attribute">prefix</a>] value,
+    create a [<a href="http://www.w3.org/TR/rdfa-syntax/#T_URI_mapping">URI
+    mapping</a>] by storing the [prefix] as the value to be mapped, and the
+    [<a href=
+    "http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
+    value</a>] as the value to map.</li>
+
+    <li>For each attribute in the in the [<a href=
+    "http://www.w3.org/TR/xml-infoset/#infoitem.element">attributes</a>] list
+    that has no value for [<a href=
+    "http://www.w3.org/TR/xml-infoset/#infoitem.attribute">prefix</a>] and a
+    [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">local
+    name</a>] that starts with <code>xmlns:</code>, create a [<a href=
+    "http://www.w3.org/TR/rdfa-syntax/#T_URI_mapping">URI mapping</a>] by
+    storing the [local name] part with the <code>xmlns:</code> characters
+    removed as the value to be mapped, and the [<a href=
+    "http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
+    value</a>] as the value to map.<br>
+    <br>
+    <span class="XXX">Note: This step is unnecessary if the Infoset coercion
+    rules preserve namespaces specified in non-XML mode.</span></li>
+  </ol>
+
+  <p>To demonstrate, assume that the following markup is processed by an
+  Infoset-based RDFa processor:</p>
+  <pre>
+&lt;div xmlns:audio="http://purl.org/media/audio#" ...
+</pre>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>.
+
+  <h3 id="processing-rdfa-attributes"><span class="secno">6.2</span>
+  Processing RDFa Attributes</h3>
+
+  <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
+  used to process these attributes, the following algorithm should be used to
+  detect and extract the values of the attributes.</p>
+
+  <p>While processing an element as described in [<a href=
+  "refsXHTMLRDFA">XHTML+RDFA</a>], Section 5.5, <a href=
+  "http://www.w3.org/TR/rdfa-syntax/#T_current_element">Step #4 through Step
+  #9</a>:</p>
+
+  <ol>
+    <li>For each RDFa attribute in the [<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
+    value</a>].</li>
+  </ol>
+
+  <h2 id="dom-level-2-based-processors"><span class="secno">7</span> DOM
+  Level 2-based Processors</h2>
+
+  <p><em>This section is informative</em></p>
+
+  <p class="XXX">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>
+
+  <h3 id="processing-namespaced-rdfa-attributes-0"><span class=
+  "secno">7.1</span> Processing Namespaced RDFa Attributes</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>While processing each [<a href=
+  "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Element</a>]
+  as described in [<a href="refsXHTMLRDFA">XHTML+RDFA</a>], Section 5.5,
+  <a href="http://www.w3.org/TR/rdfa-syntax/#T_URI_mapping">Step #2</a>:</p>
+
+  <ol>
+    <li>For each [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Attr</a>]
+    in the [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1950641247">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>] value of <code>xmlns</code>, create a [<a href=
+    "http://www.w3.org/TR/rdfa-syntax/#T_URI_mapping">URI mapping</a>] by
+    storing the [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-localname">local
+    name</a>] as the value to be mapped, and the [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
+    as the value to map.</li>
+
+    <li>For each [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Attr</a>]
+    in the [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1950641247">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>] value of null and a [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-localname">local
+    name</a>] that starts with <code>xmlns:</code>, create a [<a href=
+    "http://www.w3.org/TR/rdfa-syntax/#T_URI_mapping">URI mapping</a>] by
+    storing the [local name] part with the <code>xmlns:</code> characters
+    removed as the value to be mapped, and the [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
+    as the value to map.<br>
+    <br>
+    <span class="XXX">Note: This step is unnecessary if the XML and non-XML
+    mode DOMs are namespace consistent.</span></li>
+  </ol>
+
+  <p>To demonstrate, assume that the following markup is processed by a
+  DOM2-based RDFa processor:</p>
+  <pre>
+&lt;div xmlns:audio="http://purl.org/media/audio#" ...
+</pre>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>.
+
+  <h3 id="processing-rdfa-attributes-0"><span class="secno">7.2</span>
+  Processing RDFa Attributes</h3>
+
+  <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
+  process these attributes, the following algorithm should be used to detect
+  and extract the values of the attributes.</p>
+
+  <p>While processing an element as described in [<a href=
+  "refsXHTMLRDFA">XHTML+RDFA</a>], Section 5.5, <a href=
+  "http://www.w3.org/TR/rdfa-syntax/#T_current_element">Step #4 through Step
+  #9</a>:</p>
+
+  <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 the [<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
+    as the value.</li>
+  </ol>
+
+  <h2 id="references"><span class="secno">8</span> References</h2>
+
+  <h3 id="normative-references"><span class="secno">8.1</span> Normative
   References</h3>
 
   <dl>
@@ -792,16 +1039,29 @@
 
     <dd>RDFa in XHTML: Syntax and Processing, Mark Birbeck, Shane McCarron,
     Steven Pemberton. W3C, October 2008.</dd>
+
+    <dt id="refsDOM2">[<a href=
+    "http://www.w3.org/TR/DOM-Level-2-Core/">DOM2</a>]</dt>
+
+    <dd>Document Object Model (DOM) Level 2 Core Specification, Arnaud Le
+    Hors, Philippe Le H&eacute;garet, Lauren Wood, Gavin Nicol, Jonathan
+    Robie, Mike Champion, Steve Byrne, W3C, November 2000</dd>
+
+    <dt id="refsInfoset">[<a href=
+    "http://www.w3.org/TR/xml-infoset/">INFOSET</a>]</dt>
+
+    <dd>XML Information Set (Second Edition), John Cowan, Richard Tobin, W3C,
+    February 2004</dd>
   </dl>
 
-  <h3 id="non-normative-references"><span class="secno">6.2</span>
+  <h3 id="non-normative-references"><span class="secno">8.2</span>
   Non-Normative References</h3>
 
   <dl>
     <dt id="refsXHTMLRDF">[<a href=
     "http://www.w3.org/MarkUp/2004/02/xhtml-rdf.html">XHTMLRDF</a>]</dt>
 
-    <dd>XHTML and RDF, Mark Birbeck. W3C, February 2008.</dd>
+    <dd>XHTML and RDF, Mark Birbeck. W3C, February 2004.</dd>
   </dl>
 </body>
 </html>
Received on Wednesday, 20 January 2010 04:57:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 20 January 2010 04:57:49 GMT