- From: Manu Sporny via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 13 Jul 2009 01:14:24 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/rdfa
In directory hutz:/tmp/cvs-serv15032
Modified Files:
Overview.html rdfa-module.html source
Log Message:
Fixed a number of issues that Mark Birbeck had with the HTML5+RDFa draft
spec.
Index: source
===================================================================
RCS file: /sources/public/html5/rdfa/source,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- source 12 Jul 2009 22:37:42 -0000 1.3
+++ source 13 Jul 2009 01:14:22 -0000 1.4
@@ -41,13 +41,19 @@
<em>This section is informative.</em>
</p>
<p>
- Starting in 2006, the Semantic Web Deployment Work Group
- began work to develop a technology to express semantic data in
- XHTML. This technology was successfully developed and is now
- called RDFa (The Resource Description Framework in Attributes).
- While HTML provides a mechanism to express the structure of a document
- (title, paragraphs, links), RDFa provides a mechanism to express
- the meaning of a document (people, places, events).
+ In early 2004, Mark Birbeck published a document named
+ [<a href="http://www.w3.org/MarkUp/2004/02/xhtml-rdf.html">XHTML and RDF</a>]
+ via the XHTML2 Working Group wherein he laid the groundwork for what
+ would eventually become RDFa (The Resource Description Framework in
+ Attributes).
+ <p>
+ In 2006, the work was co-sponsored by the Semantic Web Deployment Work Group,
+ which began to formalize a technology to express semantic data in
+ XHTML. This technology was successfully developed and reached consensus
+ at the W3C, later published as an official W3C Recommendation.
+ While HTML provides a mechanism to express the structure of a
+ document (title, paragraphs, links), RDFa provides a mechanism to express
+ the meaning in a document (people, places, events).
<p>
<p>
The document, titled "RDF in XHTML: Syntax and Processing"
@@ -165,6 +171,17 @@
mechansim for an RDFa document because the <code>profile</code>
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
+ 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
+ [<a href="http://rdfa.info/wiki/RDFa_Profiles">RDFa Profiles</a>] support.
+ Adding <code>profile</code> to the list of <code>rel</code> values
+ and using it to signal that the document contains RDFa places document
+ processing instructions into the RDF graph, which is problematic.
+ </div>
</li>
</ol>
<h4>
@@ -247,25 +264,36 @@
</p>
<h4>The <code>xmlns:</code> attribute</h4>
- <p 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
- [<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>.
+ <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
+ [<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>.
+ </div>
+ <div class="XXX">
+ While deprecation of the xmlns: attribute is assumed for this section, 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
+ xmlns: is required to ensure backwards with XHTML documents, then there
+ is no choice but to support xmlns: as it is defined in
+ [<a href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML</a>].
+ </div>
</p>
<p>
- If CURIE prefix name definitions are specified using <code>xmlns:</code>,
+ If CURIE prefix mappings are specified using <code>xmlns:</code>,
the definitions 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 name definitions are specified using <code>xmlns:</code>, and
+ 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
<code>xmlns:<PREFIX>="<URI>"</code> should be specified
@@ -285,16 +313,16 @@
</div>
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 mapping values.
+ attribute to specify CURIE prefix mappings.
</p>
<p>
The syntax for the <code>token</code> attribute value is as follows:
<pre>
- token_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>]
- whitespace := White_Space ; as defined in the HTML5 Specification under '"White_Space" characters'
+ 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>]
+ whitespace := White_Space ; as defined in the HTML5 Specification under '"White_Space" characters'
</pre>
For example, the following markup:
<pre>
@@ -325,15 +353,15 @@
</div>
<p>
<p>
- Document authors should not create CURIE prefix mappings for well-known
+ 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>],
as well as other URI schemes that are
commonly used on the Internet. If common URI schemes are used as CURIE
- prefixes, then they may affect triple generation via modifications to the
+ tokens, then they may affect triple generation via modifications to the
CURIE processing algorithm (described below). The use of common URI schemes
- as CURIE prefixes may result in unexpected substitutions in certain
+ as CURIE tokens may result in unexpected substitutions in certain
markup scenarios.
</p>
<p>
@@ -341,7 +369,7 @@
the XHTML+RDFa Recommendation with the following modification:
</p>
<p>
- If a prefix mapping is not found for text that is given to the CURIE
+ 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
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- Overview.html 12 Jul 2009 22:37:42 -0000 1.3
+++ Overview.html 13 Jul 2009 01:14:22 -0000 1.4
@@ -86285,13 +86285,19 @@
<em>This section is informative.</em>
</p>
<p>
- Starting in 2006, the Semantic Web Deployment Work Group
- began work to develop a technology to express semantic data in
- XHTML. This technology was successfully developed and is now
- called RDFa (The Resource Description Framework in Attributes).
- While HTML provides a mechanism to express the structure of a document
- (title, paragraphs, links), RDFa provides a mechanism to express
- the meaning of a document (people, places, events).
+ In early 2004, Mark Birbeck published a document named
+ [<a href=http://www.w3.org/MarkUp/2004/02/xhtml-rdf.html>XHTML and RDF</a>]
+ via the XHTML2 Working Group wherein he laid the groundwork for what
+ would eventually become RDFa (The Resource Description Framework in
+ Attributes).
+ </p><p>
+ In 2006, the work was co-sponsored by the Semantic Web Deployment Work Group,
+ which began to formalize a technology to express semantic data in
+ XHTML. This technology was successfully developed and reached consensus
+ at the W3C, later published as an official W3C Recommendation.
+ While HTML provides a mechanism to express the structure of a
+ document (title, paragraphs, links), RDFa provides a mechanism to express
+ the meaning in a document (people, places, events).
</p><p>
</p><p>
The document, titled "RDF in XHTML: Syntax and Processing"
@@ -86408,6 +86414,17 @@
mechansim for an RDFa document because the <code>profile</code>
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
+ 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
+ [<a href=http://rdfa.info/wiki/RDFa_Profiles>RDFa Profiles</a>] support.
+ Adding <code>profile</code> to the list of <code>rel</code> values
+ and using it to signal that the document contains RDFa places document
+ processing instructions into the RDF graph, which is problematic.
+ </div>
</li>
</ol>
<h4 id=user-agent-conformance><span class=secno>5.4.2 </span>
@@ -86490,25 +86507,36 @@
</p>
<h4 id=the-xmlns:-attribute><span class=secno>5.5.3 </span>The <code>xmlns:</code> attribute</h4>
- <p 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
- [<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>.
- </p>
<p>
- If CURIE prefix name definitions are specified using <code>xmlns:</code>,
+ </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
+ [<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>.
+ </div>
+ <div class=XXX>
+ While deprecation of the xmlns: attribute is assumed for this section, 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
+ xmlns: is required to ensure backwards with XHTML documents, then there
+ is no choice but to support xmlns: as it is defined in
+ [<a href=http://www.w3.org/TR/REC-xml-names/>Namespaces in XML</a>].
+ </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
[<a href=http://www.w3.org/TR/REC-xml-names/>Namespaces in XML</a>]
Recommendation.
</p>
<p>
- If CURIE prefix name definitions are specified using <code>xmlns:</code>, and
+ 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
<code>xmlns:<PREFIX>="<URI>"</code> should be specified
@@ -86528,15 +86556,15 @@
</div>
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 mapping values.
+ attribute to specify CURIE prefix mappings.
<p></p>
<p>
The syntax for the <code>token</code> attribute value is as follows:
- </p><pre> token_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>]
- whitespace := White_Space ; as defined in the HTML5 Specification under '"White_Space" characters'
+ </p><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>]
+ whitespace := White_Space ; as defined in the HTML5 Specification under '"White_Space" characters'
</pre>
For example, the following markup:
<pre> <body token="ex=http://example.org/">
@@ -86563,15 +86591,15 @@
</div>
<p>
</p><p>
- Document authors should not create CURIE prefix mappings for well-known
+ 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>],
as well as other URI schemes that are
commonly used on the Internet. If common URI schemes are used as CURIE
- prefixes, then they may affect triple generation via modifications to the
+ tokens, then they may affect triple generation via modifications to the
CURIE processing algorithm (described below). The use of common URI schemes
- as CURIE prefixes may result in unexpected substitutions in certain
+ as CURIE tokens may result in unexpected substitutions in certain
markup scenarios.
</p>
<p>
@@ -86579,7 +86607,7 @@
the XHTML+RDFa Recommendation with the following modification:
</p>
<p>
- If a prefix mapping is not found for text that is given to the CURIE
+ 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
Index: rdfa-module.html
===================================================================
RCS file: /sources/public/html5/rdfa/rdfa-module.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- rdfa-module.html 12 Jul 2009 22:37:42 -0000 1.5
+++ rdfa-module.html 13 Jul 2009 01:14:22 -0000 1.6
@@ -357,13 +357,19 @@
<em>This section is informative.</em>
</p>
<p>
- Starting in 2006, the Semantic Web Deployment Work Group
- began work to develop a technology to express semantic data in
- XHTML. This technology was successfully developed and is now
- called RDFa (The Resource Description Framework in Attributes).
- While HTML provides a mechanism to express the structure of a document
- (title, paragraphs, links), RDFa provides a mechanism to express
- the meaning of a document (people, places, events).
+ In early 2004, Mark Birbeck published a document named
+ [<a href=http://www.w3.org/MarkUp/2004/02/xhtml-rdf.html>XHTML and RDF</a>]
+ via the XHTML2 Working Group wherein he laid the groundwork for what
+ would eventually become RDFa (The Resource Description Framework in
+ Attributes).
+ </p><p>
+ In 2006, the work was co-sponsored by the Semantic Web Deployment Work Group,
+ which began to formalize a technology to express semantic data in
+ XHTML. This technology was successfully developed and reached consensus
+ at the W3C, later published as an official W3C Recommendation.
+ While HTML provides a mechanism to express the structure of a
+ document (title, paragraphs, links), RDFa provides a mechanism to express
+ the meaning in a document (people, places, events).
</p><p>
</p><p>
The document, titled "RDF in XHTML: Syntax and Processing"
@@ -480,6 +486,17 @@
mechansim for an RDFa document because the <code>profile</code>
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
+ 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
+ [<a href=http://rdfa.info/wiki/RDFa_Profiles>RDFa Profiles</a>] support.
+ Adding <code>profile</code> to the list of <code>rel</code> values
+ and using it to signal that the document contains RDFa places document
+ processing instructions into the RDF graph, which is problematic.
+ </div>
</li>
</ol>
<h4 id=user-agent-conformance><span class=secno>1.4.2 </span>
@@ -562,25 +579,36 @@
</p>
<h4 id=the-xmlns:-attribute><span class=secno>1.5.3 </span>The <code>xmlns:</code> attribute</h4>
- <p 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
- [<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>.
- </p>
<p>
- If CURIE prefix name definitions are specified using <code>xmlns:</code>,
+ </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
+ [<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>.
+ </div>
+ <div class=XXX>
+ While deprecation of the xmlns: attribute is assumed for this section, 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
+ xmlns: is required to ensure backwards with XHTML documents, then there
+ is no choice but to support xmlns: as it is defined in
+ [<a href=http://www.w3.org/TR/REC-xml-names/>Namespaces in XML</a>].
+ </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
[<a href=http://www.w3.org/TR/REC-xml-names/>Namespaces in XML</a>]
Recommendation.
</p>
<p>
- If CURIE prefix name definitions are specified using <code>xmlns:</code>, and
+ 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
<code>xmlns:<PREFIX>="<URI>"</code> should be specified
@@ -600,15 +628,15 @@
</div>
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 mapping values.
+ attribute to specify CURIE prefix mappings.
<p></p>
<p>
The syntax for the <code>token</code> attribute value is as follows:
- </p><pre> token_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>]
- whitespace := White_Space ; as defined in the HTML5 Specification under '"White_Space" characters'
+ </p><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>]
+ whitespace := White_Space ; as defined in the HTML5 Specification under '"White_Space" characters'
</pre>
For example, the following markup:
<pre> <body token="ex=http://example.org/">
@@ -635,15 +663,15 @@
</div>
<p>
</p><p>
- Document authors should not create CURIE prefix mappings for well-known
+ 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>],
as well as other URI schemes that are
commonly used on the Internet. If common URI schemes are used as CURIE
- prefixes, then they may affect triple generation via modifications to the
+ tokens, then they may affect triple generation via modifications to the
CURIE processing algorithm (described below). The use of common URI schemes
- as CURIE prefixes may result in unexpected substitutions in certain
+ as CURIE tokens may result in unexpected substitutions in certain
markup scenarios.
</p>
<p>
@@ -651,7 +679,7 @@
the XHTML+RDFa Recommendation with the following modification:
</p>
<p>
- If a prefix mapping is not found for text that is given to the CURIE
+ 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
Received on Monday, 13 July 2009 01:14:35 UTC