W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2009

html5/rdfa Overview.html,1.4,1.5 rdfa-module.html,1.6,1.7 source,1.4,1.5

From: Manu Sporny via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 13 Jul 2009 15:05:27 +0000
To: public-html-commits@w3.org
Message-Id: <E1MQN5r-0001ah-9l@lionel-hutz.w3.org>
Update of /sources/public/html5/rdfa
In directory hutz:/tmp/cvs-serv6004

Modified Files:
	Overview.html rdfa-module.html source 
Log Message:
Updated HTML5+RDFa with a number of changes requested by Ben Adida,
Steven Pemberton and Ivan Herman.


Index: source
===================================================================
RCS file: /sources/public/html5/rdfa/source,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- source	13 Jul 2009 01:14:22 -0000	1.4
+++ source	13 Jul 2009 15:05:25 -0000	1.5
@@ -31,8 +31,8 @@
    a bug/feature in the Anolis specification processor. 
   <p class="XXX">
    These down-sides are not ideal and will eventually be remedied as we find
-   a way to either fix Anolis or integrate the RDFa document into the HTML5
-   specification.
+   a way to either fix Anolis or no longer support the smaller, standalone 
+   HTML5+RDFa document.
   </p>
   <h3>
    Introduction
@@ -154,10 +154,22 @@
     There should be a DOCTYPE declaration specified prior to the root element
     in the document that follows the conventions outlined in the
     "The DOCTYPE section" of the HTML5 specification.
+    <div class="XXX">
+     This item may be removed once this document is integrated with the
+     HTML5 specification. It is currently included for the purposes of
+     clarifying the full set of Document Conformance requirements for 
+     an HTML5+RDFa document.
+    </div>
    </li>
    <li>
     The root element of the document must follow the conventions outlined
     in "The root element" section of the HTML5 specification.
+    <div class="XXX">
+     This item may be removed once this document is integrated with the
+     HTML5 specification. It is currently included for the purposes of
+     clarifying the full set of Document Conformance requirements for 
+     an HTML5+RDFa document.
+    </div>
    </li>
    <li>
     There may be a <code>link</code> element contained in the 
@@ -172,8 +184,8 @@
      attribute is deprecated in HTML5.
     </div>
     <div class="XXX">
-     There has also been heavy push-back from the RDFa Task Force that the
-     <code>profile</code> attribute should be re-introduced in HTML5, as it
+     There has also been strong support from the RDFa Task Force that the 
+     <code>profile</code> attribute should be retained in HTML5, as it
      provides an "out-of-band" mechanism for signaling that the document
      contains RDFa. The <code>profile</code> attribute may also be used 
      extensively to provide 
@@ -267,17 +279,15 @@
   <p>
    <div class="XXX">
     There have been various objections to the usage of the <code>xmlns</code>: 
-    attribute across all HTML family languages. It is currently unknown whether 
-    or not the <code>xmlns</code>: attribute will be supported in HTML5 as it 
-    is defined in the 
+    attribute across all HTML family languages. It is currently unknown 
+    whether or not the <code>xmlns</code>: attribute will be supported in 
+    HTML5 as it is defined in the 
     [<a href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML</a>]
-    specification. This section assumes deprecation of the <code>xmlns:</code> 
-    attribute. The next section provides an alternate mechanism for 
-    specifying prefix mappings in addition to deprecated use of 
-    <code>xmlns:</code>.
+    specification. The RDFa Task Force is actively working on an
+    improvement/replacement to xmlns: that can be used in non-XML languages.
    </div>
    <div class="XXX">
-    While deprecation of the xmlns: attribute is assumed for this section, it
+    While deprecation of the xmlns: attribute is attempted in HTML5, it
     must still be available to ensure backwards-compatability for existing
     XHTML code snippets on the web. Which raises the question, if HTML5 
     subsumes XHTML 1.0 documents, and it is going to be long-lived, and 
@@ -287,15 +297,15 @@
    </div>
   </p>
   <p>
-   If CURIE prefix mappings are specified using <code>xmlns:</code>, 
-   the definitions must be processed using the rules specified in the
+   CURIE prefix mappings specified using <code>xmlns:</code>
+   must be processed using the rules specified in the
    [<a href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML</a>]
    Recommendation.
   </p>
   <p>
-   If CURIE prefix mappings are 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 
+   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:&lt;PREFIX&gt;="&lt;URI&gt;"</code> should be specified
    using only lower-case characters. For example, the text "xmlns:" and the
    text in "&lt;PREFIX&gt;" should be lower-case only. This is to ensure that 
@@ -304,6 +314,7 @@
    names) document types.
   </p>
 
+<!-- experimental new RDFa features
   <h4>The <code>token</code> attribute</h4>
   <p>
    <div class="XXX">
@@ -453,3 +464,5 @@
 z39.50r
 z39.50s
   </p>
+
+end experimental RDFa features -->

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- Overview.html	13 Jul 2009 01:14:22 -0000	1.4
+++ Overview.html	13 Jul 2009 15:05:24 -0000	1.5
@@ -1,4 +1,8 @@
-<!DOCTYPE html><!-- when publishing, change bits marked ZZZ --><html lang=en-US-x-Hixie><head><title>HTML 5</title><style type=text/css>
+<!DOCTYPE html><!-- when publishing, change bits marked ZZZ --><html lang=en-US-x-Hixie><head>
+
+<meta content="text/html; charset=UTF-8" http-equiv=Content-Type>
+
+<title>HTML 5</title><style type=text/css>
 
    pre { margin-left: 2em; white-space: pre-wrap; }
 
@@ -1089,11 +1093,7 @@
     <ol class=toc>
[...2650 lines suppressed...]
   David Matja,
 
+  David Remahl,
+
   David Smith,
 
   David Woolley,
@@ -159125,12 +159317,6 @@
 
        various states, instead of the attribute
 
- XXX * make the text consistent about whether it is ":<em>" and
-
-       ":<strong>" or "</em>:" and "</strong>:". Same for other
-
-       punctuation.
-
  XXX * take references to "valid mime type" / RFC2046 and make them
 
        mean something. (2046 doesn't define anything like that, and

Index: rdfa-module.html
===================================================================
RCS file: /sources/public/html5/rdfa/rdfa-module.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- rdfa-module.html	13 Jul 2009 01:14:22 -0000	1.6
+++ rdfa-module.html	13 Jul 2009 15:05:24 -0000	1.7
@@ -1,4 +1,5 @@
 <!DOCTYPE html><!-- when publishing, change bits marked ZZZ --><html lang=en-US-x-Hixie><head>
+  <meta content="text/html; charset=UTF-8" http-equiv=Content-Type>
   <title>HTML5+RDFa</title>
   <style type=text/css>
  pre { margin-left: 2em; white-space: pre-wrap; }
@@ -229,6 +230,9 @@
     <dd>
      <a href=mailto:msporny@digitalbazaar.com>Manu Sporny</a>, (Editor, HTML5+RDFa, Digital Bazaar, Inc.)
     </dd>
+    <dd>
+     Ralph R. Swick (Domain Leader, Technology and Society, W3C)
+    </dd>
    </dl>
    <p class=copyright>
     <a href=http://www.w3.org/Consortium/Legal/ipr-notice#Copyright>Copyright</a> © 2009 <a href=http://www.w3.org/><abbr title="World Wide Web
@@ -301,7 +305,7 @@
   </p>
   <!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) -->
   <p>
-   This specification is intended to be included in the HTML5 specification
+   Most of this text is intended to be included in the HTML5 specification
    as a section of the overall specification.
   </p>
   <!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate -->
@@ -347,8 +351,8 @@
    a bug/feature in the Anolis specification processor. 
   </p><p class=XXX>
    These down-sides are not ideal and will eventually be remedied as we find
-   a way to either fix Anolis or integrate the RDFa document into the HTML5
-   specification.
+   a way to either fix Anolis or no longer support the smaller, standalone 
+   HTML5+RDFa document.
   </p>
   <h3 id=introduction><span class=secno>1.2 </span>
    Introduction
@@ -469,10 +473,22 @@
     There should be a DOCTYPE declaration specified prior to the root element
     in the document that follows the conventions outlined in the
     "The DOCTYPE section" of the HTML5 specification.
+    <div class=XXX>
+     This item may be removed once this document is integrated with the
+     HTML5 specification. It is currently included for the purposes of
+     clarifying the full set of Document Conformance requirements for 
+     an HTML5+RDFa document.
+    </div>
    </li>
    <li>
     The root element of the document must follow the conventions outlined
     in "The root element" section of the HTML5 specification.
+    <div class=XXX>
+     This item may be removed once this document is integrated with the
+     HTML5 specification. It is currently included for the purposes of
+     clarifying the full set of Document Conformance requirements for 
+     an HTML5+RDFa document.
+    </div>
    </li>
    <li>
     There may be a <code>link</code> element contained in the 
@@ -487,8 +503,8 @@
      attribute is deprecated in HTML5.
     </div>
     <div class=XXX>
-     There has also been heavy push-back from the RDFa Task Force that the
-     <code>profile</code> attribute should be re-introduced in HTML5, as it
+     There has also been strong support from the RDFa Task Force that the 
+     <code>profile</code> attribute should be retained in HTML5, as it
      provides an "out-of-band" mechanism for signaling that the document
      contains RDFa. The <code>profile</code> attribute may also be used 
      extensively to provide 
@@ -582,17 +598,15 @@
   <p>
    </p><div class=XXX>
     There have been various objections to the usage of the <code>xmlns</code>: 
-    attribute across all HTML family languages. It is currently unknown whether 
-    or not the <code>xmlns</code>: attribute will be supported in HTML5 as it 
-    is defined in the 
+    attribute across all HTML family languages. It is currently unknown 
+    whether or not the <code>xmlns</code>: attribute will be supported in 
+    HTML5 as it is defined in the 
     [<a href=http://www.w3.org/TR/REC-xml-names/>Namespaces in XML</a>]
-    specification. This section assumes deprecation of the <code>xmlns:</code> 
-    attribute. The next section provides an alternate mechanism for 
-    specifying prefix mappings in addition to deprecated use of 
-    <code>xmlns:</code>.
+    specification. The RDFa Task Force is actively working on an
+    improvement/replacement to xmlns: that can be used in non-XML languages.
    </div>
    <div class=XXX>
-    While deprecation of the xmlns: attribute is assumed for this section, it
+    While deprecation of the xmlns: attribute is attempted in HTML5, it
     must still be available to ensure backwards-compatability for existing
     XHTML code snippets on the web. Which raises the question, if HTML5 
     subsumes XHTML 1.0 documents, and it is going to be long-lived, and 
@@ -602,15 +616,15 @@
    </div>
   <p></p>
   <p>
-   If CURIE prefix mappings are specified using <code>xmlns:</code>, 
-   the definitions must be processed using the rules specified in the
+   CURIE prefix mappings specified using <code>xmlns:</code>
+   must be processed using the rules specified in the
    [<a href=http://www.w3.org/TR/REC-xml-names/>Namespaces in XML</a>]
    Recommendation.
   </p>
   <p>
-   If CURIE prefix mappings are 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 
+   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:&lt;PREFIX&gt;="&lt;URI&gt;"</code> should be specified
    using only lower-case characters. For example, the text "xmlns:" and the
    text in "&lt;PREFIX&gt;" should be lower-case only. This is to ensure that 
@@ -619,9 +633,10 @@
    names) document types.
   </p>
 
-  <h4 id=the-token-attribute><span class=secno>1.5.4 </span>The <code>token</code> attribute</h4>
+<!-- experimental new RDFa features
+  <h4>The <code>token</code> attribute</h4>
   <p>
-   </p><div class=XXX>
+   <div class="XXX">
     Warning: All statements regarding the <code>token</code> attribute 
     do not enjoy consensus in the RDFa Task Force and could be removed at
     any point without notice.
@@ -629,44 +644,49 @@
    If authors would like to ensure that their prefix mappings are supported 
    across all XHTML and HTML documents, they should use the <code>token</code> 
    attribute to specify CURIE prefix mappings.
-  <p></p>
+  </p>
   <p>
    The syntax for the <code>token</code> attribute value is as follows:
-   </p><pre>    prefix_mappings := 1*(token_mapping *whitespace)
+   <pre>
+    prefix_mappings := 1*(token_mapping *whitespace)
     token_mapping   := token *whitespace '=' *whitespace mapping
-    token           := NCName        ; as defined in [<a href=http://www.w3.org/TR/REC-xml-names/#NT-NCName>Namespaces in XML</a>]
-    mapping         := irelative-ref ; as defined in [<a href=http://www.ietf.org/rfc/rfc3987>IRI</a>]
+    token           := NCName        ; as defined in [<a href="http://www.w3.org/TR/REC-xml-names/#NT-NCName">Namespaces in XML</a>]
+    mapping         := irelative-ref ; as defined in [<a href="http://www.ietf.org/rfc/rfc3987">IRI</a>]
     whitespace      := White_Space   ; as defined in the HTML5 Specification under '"White_Space" characters'
    </pre>
    For example, the following markup:
-   <pre>    &lt;body token="ex=http://example.org/"&gt;
+   <pre>
+    &lt;body token="ex=http://example.org/"&gt;
    </pre>
    when applied to the following HTML snippet:
-   <pre>    &lt;a rel="ex:bar"&gt;
+   <pre>
+    &lt;a rel="ex:bar"&gt;
    </pre>
    would expand the CURIE value in <code>rel</code> as 
    <code>http://example.org/bar</code>. Similarly, for the following markup:
-   <pre>    &lt;body token="author=http://example.org/author publisher=http://example.org/publisher"&gt;
+   <pre>
+    &lt;body token="author=http://example.org/author publisher=http://example.org/publisher"&gt;
    </pre>
    when applied to the following HTML snippet:
-   <pre>    &lt;a rel="author"&gt;
+   <pre>
+    &lt;a rel="author"&gt;
    </pre>
    would expand the CURIE value in <code>rel</code> as <code>http://example.org/author</code>.
-  <p></p>
-  <h4 id=use-of-uris-in-curie-only-attribute-values><span class=secno>1.5.5 </span>Use of URIs in CURIE-only attribute values</h4>
+  </p>
+  <h4>Use of URIs in CURIE-only attribute values</h4>
   <p>
-   </p><div class=XXX>
+   <div class="XXX">
     Warning: All statements regarding the use of URIs in attribute value's
     intended to receive reserved_words, CURIEs or Safe CURIEs, per the 
     XHTML+RDFa specification do not enjoy consensus in the RDFa Task Force 
     and could be removed at any point without notice.
    </div>
   <p>
-  </p><p>
+  <p>
    Document authors should not create CURIE token mappings for well-known
    URI schemes such as http, ftp, urn and a number of other well-known schemes 
    specified in 
-   [<a href=http://www.iana.org/assignments/uri-schemes.html>The IANA URI Schemes Registry</a>], 
+   [<a href="http://www.iana.org/assignments/uri-schemes.html">The IANA URI Schemes Registry</a>], 
    as well as other URI schemes that are 
    commonly used on the Internet. If common URI schemes are used as CURIE
    tokens, then they may affect triple generation via modifications to the 
@@ -682,17 +702,17 @@
    If a token mapping is not found for text that is given to the CURIE 
    processing algorithm, and the text is an Internationalized Resource 
    Identifier as defined in 
-   [<a href=http://www.ietf.org/rfc/rfc3987>IRI</a>], and the scheme is
+   [<a href="http://www.ietf.org/rfc/rfc3987">IRI</a>], and the scheme is
    one of the allowable scheme values in the section below, then the expanded 
    value of the potential CURIE should be the IRI. 
   </p>
-  <h5 id=allowable-curie-scheme-values><span class=secno>1.5.5.1 </span>Allowable CURIE Scheme values</h5>
+  <h5>Allowable CURIE Scheme values</h5>
   <p>
    <em>This section is informative.</em>
   </p>
   <p>
    Each of these listed values is a 
-   [<a href=http://www.iana.org/assignments/uri-schemes.html>registered IANA Scheme</a>] 
+   [<a href="http://www.iana.org/assignments/uri-schemes.html">registered IANA Scheme</a>] 
    with a corresponding RFC:
   </p>
   <p>
@@ -763,4 +783,6 @@
 z39.50r
 z39.50s
   </p>
+
+end experimental RDFa features -->
 </body></html>
\ No newline at end of file
Received on Monday, 13 July 2009 15:05:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 13 July 2009 15:05:43 GMT