[html5] r7311 - [e] (0) update fork section Affected topics: HTML
whatwg at whatwg.org
whatwg at whatwg.org
Tue Sep 4 11:33:34 PDT 2012
Author: ianh
Date: 2012-09-04 11:33:33 -0700 (Tue, 04 Sep 2012)
New Revision: 7311
Modified:
complete.html
index
source
Log:
[e] (0) update fork section
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2012-09-03 16:16:49 UTC (rev 7310)
+++ complete.html 2012-09-04 18:33:33 UTC (rev 7311)
@@ -246,7 +246,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 3 September 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 4 September 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -1465,9 +1465,12 @@
publication policies</a>.</li>
-->
- <li>The W3C HTML specification omits an example as part of a
- compromise intended to resolve larger issues of divergence between
- the specifications.</li>
+ <li>The W3C HTML specification omits an example that references the
+ schema.org microdata vocabulary as part of a compromise intended to
+ resolve larger issues of divergence between the specifications.
+ (Many other examples that reference schema.org and microdata are
+ included apparently without issue, however.)</li><!-- "I put a bike
+ bell on his bike." -->
<li>The W3C HTML specification defines conformance for documents in
a more traditional (version-orientated) way, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0574.html>a
@@ -1577,6 +1580,12 @@
the <code><a href=#the-object-element>object</a></code> element, due to <a href=http://lists.w3.org/Archives/Public/public-html/2012Jul/0250.html>a
working group chair decision from July 2012</a>.</li>
+ <li>The W3C HTML specification has a different approach to topics
+ relating to registering extensibility tokens.</li> <!-- e.g.
+ different conformance criteria for validators for pragmas,
+ different text for web+, etc. I haven't fixed these yet since I
+ expect the WHATWG to switch approach at some point soon too. -->
+
</ul><p>The following sections are only published in the WHATWG
specifications and are not currently available anywhere else:</p>
Modified: index
===================================================================
--- index 2012-09-03 16:16:49 UTC (rev 7310)
+++ index 2012-09-04 18:33:33 UTC (rev 7311)
@@ -246,7 +246,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 3 September 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 4 September 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -1465,9 +1465,12 @@
publication policies</a>.</li>
-->
- <li>The W3C HTML specification omits an example as part of a
- compromise intended to resolve larger issues of divergence between
- the specifications.</li>
+ <li>The W3C HTML specification omits an example that references the
+ schema.org microdata vocabulary as part of a compromise intended to
+ resolve larger issues of divergence between the specifications.
+ (Many other examples that reference schema.org and microdata are
+ included apparently without issue, however.)</li><!-- "I put a bike
+ bell on his bike." -->
<li>The W3C HTML specification defines conformance for documents in
a more traditional (version-orientated) way, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0574.html>a
@@ -1577,6 +1580,12 @@
the <code><a href=#the-object-element>object</a></code> element, due to <a href=http://lists.w3.org/Archives/Public/public-html/2012Jul/0250.html>a
working group chair decision from July 2012</a>.</li>
+ <li>The W3C HTML specification has a different approach to topics
+ relating to registering extensibility tokens.</li> <!-- e.g.
+ different conformance criteria for validators for pragmas,
+ different text for web+, etc. I haven't fixed these yet since I
+ expect the WHATWG to switch approach at some point soon too. -->
+
</ul><p>The following sections are only published in the WHATWG
specifications and are not currently available anywhere else:</p>
Modified: source
===================================================================
--- source 2012-09-03 16:16:49 UTC (rev 7310)
+++ source 2012-09-04 18:33:33 UTC (rev 7311)
@@ -167,9 +167,12 @@
publication policies</a>.</li>
-->
- <li>The W3C HTML specification omits an example as part of a
- compromise intended to resolve larger issues of divergence between
- the specifications.</li>
+ <li>The W3C HTML specification omits an example that references the
+ schema.org microdata vocabulary as part of a compromise intended to
+ resolve larger issues of divergence between the specifications.
+ (Many other examples that reference schema.org and microdata are
+ included apparently without issue, however.)</li><!-- "I put a bike
+ bell on his bike." -->
<li>The W3C HTML specification defines conformance for documents in
a more traditional (version-orientated) way, because of <a
@@ -297,6 +300,12 @@
href="http://lists.w3.org/Archives/Public/public-html/2012Jul/0250.html">a
working group chair decision from July 2012</a>.</li>
+ <li>The W3C HTML specification has a different approach to topics
+ relating to registering extensibility tokens.</li> <!-- e.g.
+ different conformance criteria for validators for pragmas,
+ different text for web+, etc. I haven't fixed these yet since I
+ expect the WHATWG to switch approach at some point soon too. -->
+
</ul>
<p>The following sections are only published in the WHATWG
More information about the Commit-Watchers
mailing list