Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) update fork section
Affected topics: HTML

git-svn-id: http://svn.whatwg.org/webapps@7311 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Sep 4, 2012
1 parent 950eade commit 72342b6
Show file tree
Hide file tree
Showing 3 changed files with 38 additions and 11 deletions.
17 changes: 13 additions & 4 deletions complete.html
Expand Up @@ -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 &mdash; Last Updated 3 September 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; 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>
Expand Down Expand Up @@ -1465,9 +1465,12 @@ <h6 class=no-toc id=how-do-the-whatwg-and-w3c-specifications-differ?><span class
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
Expand Down Expand Up @@ -1577,6 +1580,12 @@ <h6 class=no-toc id=how-do-the-whatwg-and-w3c-specifications-differ?><span class
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>

Expand Down
17 changes: 13 additions & 4 deletions index
Expand Up @@ -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 &mdash; Last Updated 3 September 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; 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>
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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>

Expand Down
15 changes: 12 additions & 3 deletions source
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down

0 comments on commit 72342b6

Please sign in to comment.