- From: Manu Sporny via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 31 Dec 2011 03:17:14 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/rdfa
In directory hutz:/tmp/cvs-serv15632
Modified Files:
Overview-src.html Overview.html
Log Message:
Added RDFa Lite dependency to HTML+RDFa, updated to reflect RDFWAWG resolutions.
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- Overview.html 12 May 2011 19:14:05 -0000 1.38
+++ Overview.html 31 Dec 2011 03:17:11 -0000 1.39
@@ -81,7 +81,7 @@
a.externalDFN {
color: inherit;
- border-bottom: medium dotted #ccc;
+ border-bottom: 1px dotted #ccc;
text-decoration: none;
}
@@ -123,7 +123,7 @@
/*.idlModule*/
/*.idlModuleID*/
[...1685 lines suppressed...]
+Manu Sporny (chair), Stéphane Corlosquet and Thomas Steiner.
</p>
<p>At the time of publication, the members of the HTML Working Group were:</p>
@@ -2437,11 +1418,12 @@
<!-- 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/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-HTML5">[HTML5]</dt><dd rel="dcterms:requires">Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/html5"><cite>HTML5.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/html5">http://www.w3.org/TR/html5</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/2011/WD-rdfa-core-20111215"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a> 15 December 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-rdfa-core-20111215">http://www.w3.org/TR/2011/WD-rdfa-core-20111215</a>
+</dd><dt id="bib-RDFA-LITE">[RDFA-LITE]</dt><dd rel="dcterms:requires">Manu Sporny; et al. <a href="http://www.w3.org/TR/rdfa-lite/"><cite>RDFa Lite</cite></a> December 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/rdfa-lite/">http://www.w3.org/TR/rdfa-lite/</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/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><dt id="bib-XHTML-RDFA">[XHTML-RDFA]</dt><dd rel="dcterms:references">Shane McCarron; et. al. <a href="http://www.w3.org/TR/2011/WD-xhtml-rdfa-20111215"><cite>XHTML+RDFa 1.1.</cite></a> 15 December 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-xhtml-rdfa-20111215">http://www.w3.org/TR/2011/WD-xhtml-rdfa-20111215</a>
</dd></dl></div></div></body></html>
Index: Overview-src.html
===================================================================
RCS file: /sources/public/html5/rdfa/Overview-src.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- Overview-src.html 12 May 2011 19:14:05 -0000 1.22
+++ Overview-src.html 31 Dec 2011 03:17:11 -0000 1.23
@@ -12,6 +12,8 @@
<script class='remove'>
var preProc = {
apply: function(c) {
+ berjon.biblio["RDFA-LITE"] = "Manu Sporny; et al. <a href=\"http://www.w3.org/TR/rdfa-lite/\"><cite>RDFa Lite</cite></a> December 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/rdfa-lite/\">http://www.w3.org/TR/rdfa-lite/</a>";
+
// process the document before anything else is done
var refs = document.querySelectorAll('aref') ;
for (var i = 0; i < refs.length; i++) {
@@ -118,8 +120,8 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "LC",
- publishDate: "2011-05-24",
+ specStatus: "ED",
+ //publishDate: "2011-05-24",
diffTool: "http://www3.aptest.com/standards/htmldiff/htmldiff.pl",
// the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -132,16 +134,16 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2011-04-05",
- previousMaturity: "WD",
+ previousPublishDate: "2011-05-24",
+ previousMaturity: "LC",
// prevRecShortname: "rdfa-in-html",
- previousURI: "http://www.w3.org/TR/2011/WD-rdfa-in-html-20110405/",
+ previousURI: "http://www.w3.org/TR/2011/WD-rdfa-in-html-20110524/",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "http://dev.w3.org/html5/rdfa/",
// if this is a LCWD, uncomment and set the end of its review period
- lcEnd: "2011-XX-XX",
+ //lcEnd: "2011-XX-XX",
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
@@ -173,14 +175,14 @@
// Perform RDFa markup on the document
doRDFa: true,
- alternateFormats: [
- { uri: 'diff-20110405.html',
- label: "Changes since previous Working Draft" }
+// alternateFormats: [
+// { uri: 'diff-20110405.html',
+// label: "Changes since previous Working Draft" }
// { uri: 'html-rdfa.ps',
// label: 'Postscript version' },
// { uri: 'html-rdfa.pdf',
// label: 'PDF version' },
- ],
+// ],
// errata: 'http://www.w3.org/MarkUp/2008/REC-rdfa-core-20081014-errata',
@@ -239,10 +241,10 @@
<section id='abstract'>
<p>This specification defines rules and guidelines for adapting the RDFa Core
- 1.1 specification for use in HTML5 and XHTML5. The rules defined in this
- specification not only apply to HTML5 documents in non-XML and XML mode,
- but also to HTML4 and XHTML documents interpreted through the HTML5 parsing
- rules.</p>
+ 1.1 and RDFa Lite 1.1 specifications for use in HTML5 and XHTML5. The rules
+ defined in this specification not only apply to HTML5 documents in non-XML
+ and XML mode, but also to HTML4 and XHTML documents interpreted through the
+ HTML5 parsing rules.</p>
</section>
@@ -319,27 +321,32 @@
<section>
<h2>Document Conformance</h2>
- <p>In order for a document to claim that it is a conforming HTML+RDFa
- document, it MUST provide the facilities described as mandatory in this
- section. The document conformance criteria are listed below, of which only
- a subset are mandatory:</p>
+ <p>There are two types of document conformance criteria for HTML
+ documents containing RDFa semantics; <strong>HTML+RDFa</strong> and
+ <strong>HTML+RDFa Lite</strong>.
+ </p>
+
+ <p>The following conformance criteria apply to any HTML document
+ including RDFa markup:</p>
<ul>
<li>All document conformance requirements stated as mandatory in the
HTML5 specification MUST be met.</li>
- <li>All
+ <li>The appropriate
<a href="#extensions-to-the-html5-syntax">Extensions to the HTML5 Syntax</a>,
- as described in this document, MUST be considered valid and conforming in
- a HTML+RDFa 1.1 document.</li>
+ as described in this document, MUST be considered valid and conforming.
+ Note that there are fewer supported attributes if the RDFa Lite
+ syntax [[!RDFA-LITE]] is desired over the more advanced set of RDFa
+ attributes outlined in RDFa Core.</li>
<li>All HTML5 elements and attributes SHOULD be used in a way that is
conformant with [[!HTML5]]. All RDFa attributes SHOULD be used in a way that
is conformant with [[!RDFA-CORE]] and this document.</li>
-
+
<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>
+ appropriate constraints expressed in the
+ <a href="#html-rdfa-dtd">HTML + RDFa DTDs</a> section
located in Appendix A.
</li>
</ul>
@@ -434,25 +441,63 @@
according to [[!RDFA-CORE]] with the following extensions:</p>
<ul>
<li>The <tref>default vocabulary URI</tref> is undefined.</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>HTML+RDFa uses an additional initial context by default,
+ <code>http://www.w3.org/2011/rdfa-context/html-rdfa-1.1</code>,
+ which must be applied after the initial context for [[!RDFA-CORE]]
+ (<code>http://www.w3.org/2011/rdfa-context/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>
<li>In
- <a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5: Sequence</a>,
- processing step 6, if no URI is provided by a resource attribute, then
- first check to see if the element is the <code>head</code> or
- <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>
+ <a href="http://www.w3.org/TR/rdfa-core/#PS-new-subject">Section 7.5: Sequence,
+ processing step 5</a>, if no IRI is provided by a resource attribute
+ (e.g., <code>@about</code>, <code>@href</code>, <code>@resource</code>, or
+ <code>@src</code>), then first check to see if the
+ element is the <code>head</code> or <code>body</code> element. If it is,
+ then act as if
+ <a href="http://www.w3.org/TR/rdfa-core/#T-new-subject">new subject</a>
+ is set to
+ <a href="http://www.w3.org/TR/rdfa-core/#T-parent-object">parent object</a>.
+ </li>
<li>In
- <a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5: Sequence</a>,
- processing step 7, if no URI is provided, then
- first check to see if the element is the <code>head</code> or
- <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>
+ <a href="http://www.w3.org/TR/rdfa-core/#PS-new-subject-and-object">
+ Section 7.5: Sequence,
+ processing step 6</a>, if no IRI is provided by a resource attribute
+ (e.g., <code>@about</code>, <code>@href</code>, <code>@resource</code>, or
+ <code>@src</code>), then first check to see if the
+ element is the <code>head</code> or <code>body</code> element. If it is,
+ then act as if
+ <a href="http://www.w3.org/TR/rdfa-core/#T-new-subject">new subject</a>
+ is set to
+ <a href="http://www.w3.org/TR/rdfa-core/#T-parent-object">parent object</a>.
+ </li>
+ <li>In
+ <a href="http://www.w3.org/TR/rdfa-core/#PS-current-object-literal">
+ Section 7.5: Sequence,
+ processing step 11</a>, the HTML5 <code>@datetime</code> attribute
+ MUST be utilized when generating output, overriding any value expressed
+ using the <code>@content</code> attribute.
+ If <code>@datetime</code> is detected and the value of the attribute is
+ a valid <code>xsd:dateTime</code>, <code>xsd:date</code>, or
+ <code>xsd:time</code>, then a triple MUST be generated where
+ the <a href="http://www.w3.org/TR/rdfa-core/#T-current-property-value">
+ current property value</a> is the respective datatype and the value is the
+ value contained in the <code>@datetime</code> attribute.
+ If <code>@datatype</code> is specified, it
+ MUST override the automatic datatype. If no <code>@datatype</code> is
+ specified and the value does not match a <code>xsd:dateTime</code>,
+ <code>xsd:date</code>, or <code>xsd:time</code> pattern, a plain literal
+ MUST be generated with the associated language of the node, if available.
+ </li>
+ <li>In
+ <a href="http://www.w3.org/TR/rdfa-core/#PS-current-object-literal">
+ Section 7.5: Sequence,
+ processing step 11</a>, the HTML5 <code>@value</code> attribute MUST be
+ utilized when generating output.
+ If <code>@value</code> is detected, it MUST override and be processed
+ according to the rules for <code>@content</code>.
+ </li>
+
</ul>
<p>
@@ -622,10 +667,21 @@
syntax in order to fully support RDFa:
<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>, MUST be allowed and seen as conforming when used in
- an HTML4, HTML5 or XHTML5 document.</li>
+ <li>If HTML+RDFa Lite document conformance is desired, all RDFa attributes and
+ valid values (including CURIEs), as listed in
+ <a href="http://www.w3.org/TR/rdfa-lite/#the-attributes">
+ RDFa Lite 1.1, Section 2: The Attributes</a>,
+ MUST be allowed and validate as conforming when used in an HTML4, HTML5
+ or XHTML5 document.</li>
+ <li>If HTML+RDFa document conformance is desired, all RDFa attributes and
+ valid values (including CURIEs), as listed in
+ <a href="http://www.w3.org/TR/rdfa-core/#rdfa-attributes">
+ RDFa Core 1.1, Section 2.1: The RDFa Attributes</a>, MUST be allowed and
+ validate as conforming when used in an HTML4, HTML5 or XHTML5 document.</li>
+ <li>If any RDFa attribute is present on the <code>link</code> or
+ <code>meta</code> elements, they MUST be considered flow and
+ phrasing content if used outside of the <code>head</code> of the
+ document.</li>
</ul>
</section>
@@ -938,6 +994,15 @@
"http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
as the value.</li>
</ol>
+
+ <p class="note">When extracting values from <code>@href</code>,
+ <code>@src</code> and <code>@data</code>, Web authors and developers should
+ note that certain values MAY be transformed if accessed via the DOM versus
+ a non-DOM processor. The rules for modification of URL values can be
+ found in the main HTML5 specification under
+ <a href="http://www.w3.org/TR/html5/urls.html#parsing-urls">
+ Section 2.6.2: Parsing URLs</a>.
+ </p>
</section>
</section>
</section>
@@ -946,18 +1011,36 @@
<h2>Validation</h2>
<p>Documents written using the markup language defined in
this specification MAY be validated using the
-DTD defined in this section. If a document author wants
+DTDs defined in this section. If a document author wants
to facilitate such validation, they MAY include the following
-declaration at the top of their document:</p>
+declaration at the top of their document for HTML 4.01 + RDFa 1.1:</p>
<pre class='example'>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa 1.1//EN"
"http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd">
</pre>
+<p>The following declaration MAY be included at the top of their document for
+HTML 4.01 + RDFa Lite 1.1:
+
+<pre class='example'>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa Lite 1.1//EN"
+ "http://www.w3.org/MarkUp/DTD/html401-rdfalite11-1.dtd">
+</pre>
+
<section>
-<h2 id="html-rdfa-dtd">The HTML 4.01 + RDFa 1.1 DTD</h2>
-<div data-include="DTD/html401-rdfa11-1.dtd" data-oninclude='updateDTD'></div>
+<h2 id="html-rdfa-dtd">HTML4 + RDFa DTDs</h2>
+<p>For the purposes of DTD-based validation, there are two DTDs that can be
+utilized to validate an HTML 4.01 document containing RDFa;
+<a href="DTD/html401-rdfa11-1.dtd">HTML4+RDFa 1.1</a> and
+<a href="DTD/html401-rdfalite11-1.dtd">HTML4+RDFa Lite 1.1</a>. The only
+difference between the RDFa 1.1 DTD versus the RDFa 1.1 Lite DTD is the
+addition of the following attributes to the metainformation attributes
+collection;
+<code>content</code>, <code>rel</code>, <code>rev</code>,
+<code>datatype</code>, <code>resource</code>, and <code>inlist</code>.
+</p>
+<!-- div data-include="DTD/html401-rdfa11-1.dtd" data-oninclude='updateDTD'></div -->
</section>
</section>
@@ -1042,16 +1125,24 @@
</p>
<p>2011-05-12: Generated Last Call document, no substatitive changes.
</p>
+<p>2011-12-30: Addition of normative dependency for RDFa Lite 1.1.
+Addition of rules to allow <code>meta</code> and
+<code>link</code> elements in flow and phrasing content as long as they
+contain at least one RDFa-specific attribute. Added support for
+<code>@datetime</code> and <code>value</code> processing.
+</p>
</section>
<section class='informative'>
<h1>Acknowledgments</h1>
<p>At the time of publication, the members of the
-RDFa Working Group were:</p>
+RDF Web Applications Working Group were:</p>
<p>
-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
+Ivan Herman (staff contact), Shane McCarron, Gregg Kellogg,
+Niklas Lindström, Knud Möller, Steven Pemberton,
+Manu Sporny (chair), Stéphane Corlosquet and Thomas Steiner.
</p>
<p>At the time of publication, the members of the HTML Working Group were:</p>
Received on Saturday, 31 December 2011 03:17:20 UTC