[html5] r6240 - [e] (0) update the intro
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jun 16 00:16:16 PDT 2011
Author: ianh
Date: 2011-06-16 00:16:14 -0700 (Thu, 16 Jun 2011)
New Revision: 6240
Modified:
complete.html
index
source
Log:
[e] (0) update the intro
Modified: complete.html
===================================================================
--- complete.html 2011-06-16 04:55:29 UTC (rev 6239)
+++ complete.html 2011-06-16 07:16:14 UTC (rev 6240)
@@ -282,7 +282,9 @@
<ol class=toc>
<li><a href=#introduction><span class=secno>1 </span>Introduction</a>
<ol>
- <li><a href=#is-this-html5?><span class=secno>1.1 </span>Is this HTML5?</a></li>
+ <li><a href=#is-this-html5?><span class=secno>1.1 </span>Is this HTML5?</a>
+ <ol>
+ <li><a class=notoc href=#how-do-the-whatwg-and-w3c-specifications-differ?><span class=secno>1.1.1 </span>How do the WHATWG and W3C specifications differ?</a></ol></li>
<li><a href=#background><span class=secno>1.2 </span>Background</a></li>
<li><a href=#audience><span class=secno>1.3 </span>Audience</a></li>
<li><a href=#scope><span class=secno>1.4 </span>Scope</a></li>
@@ -929,7 +931,7 @@
<li><a href=#killing-scripts><span class=secno>7.1.3.4 </span>Killing scripts</a></li>
<li><a href=#runtime-script-errors><span class=secno>7.1.3.5 </span>Runtime script errors</a>
<ol>
- <li><a href=#runtime-script-errors><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</a></ol></ol></li>
+ <li><a href=#runtime-script-errors-in-documents><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</a></ol></ol></li>
<li><a href=#event-loops><span class=secno>7.1.4 </span>Event loops</a>
<ol>
<li><a href=#definitions-1><span class=secno>7.1.4.1 </span>Definitions</a></li>
@@ -1379,19 +1381,183 @@
<p><i>This section is non-normative.</i></p>
+ <p>In short: Yes.</p>
- <p>No, although it does contain everything that is part of HTML5. If
- you want only HTML5, please see <a href=http://www.whatwg.org/html>the HTML specification</a>.</p>
+ <p>In more length: The term "HTML5" is widely used as a buzzword to
+ refer to modern Web technologies, many of which (though by no means
+ all) are developed at the WHATWG, in some cases in conjunction with
+ the W3C and IETF.</p>
- <p><em>This</em> specification contains everything that the WHATWG
- is actively working on. For more details, please see <a href=http://wiki.whatwg.org/wiki/FAQ#What_are_the_various_versions_of_the_spec.3F>the
- relevant FAQ entry</a>.</p>
+ <p>The WHATWG work is all published in one specification
-<!--VERSION-->
+ (the one you are reading right now),
- <h3 id=background><span class=secno>1.2 </span>Background</h3>
+ parts of which are republished in a variety of other forms,
+ including an edition optimized for Web developers
+ (known as <a href=http://developers.whatwg.org/>HTML5</a>),
+
+
+ and one which focuses mainly on the core HTML language
+
+ (known as the <a href=http://www.whatwg.org/specs/web-apps/current-work/multipage/>HTML Living Standard</a>).
+
+
+ In addition, two subparts of the specification are republished as
+ separate documents, for ease of reference:
+ <a href=http://www.whatwg.org/specs/web-apps/current-work/webvtt.html>WebVTT</a>
+ and
+ <a href=http://www.whatwg.org/specs/web-apps/current-work/webrtc.html>WebRTC</a>.
+ </p>
+
+ <p>The W3C also publishes parts of this specification as separate
+ documents. One of these parts is called "HTML5"; it is a subset of
+
+ the <a href=http://www.whatwg.org/specs/web-apps/current-work/multipage/>HTML
+ Living Standard</a>.</p>
+
+
+<!--
+ <p>The WHATWG specification is a continuously maintained living
+ standard, with maturity managed at a very granular per-section
+ scale, indicated by markers in the left margin; this is intended to
+ model the way in which specifications are approached in practice by
+ implementors and authors alike. The W3C specifications follow a more
+ traditional style, with versioned releases of the specification, and
+ with maturity management being done only at the document level; this
+ means that the W3C specifications have version numbers (e.g.
+ "HTML5") and necessarily go through periods of "feature freeze"
+ where new features are not added, so that the specifications can as
+ a whole reach a more mature state.</p>
+-->
+
+ <h6 class=notoc id=how-do-the-whatwg-and-w3c-specifications-differ?><span class=secno>1.1.1 </span>How do the WHATWG and W3C specifications differ?</h6>
+
+ <p>The features present in both the WHATWG and W3C specifications
+ are specified using identical text, except for the following (mostly
+ editorial) differences:</p><!--FORK-->
+
+ <ul><!--
+ <li>Instead of this section, the W3C HTML specification has a
+ different paragraph explaining the difference between the W3C and
+ WHATWG versions of HTML.</li>
+--><!-- in the status section --><li>The W3C HTML specification refers to the technology as HTML5,
+ rather than just HTML.</li><!--VERSION-->
+
+ <li>Examples that use features from HTML5 are not present in the
+ W3C specifications since the W3C specifications are published as
+ HTML4 due to <a href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
+ publication policies</a>.</li><!--HTML4POLICE-->
+
+ <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
+ working group decision from March 2011</a>. This specification, in
+ part driven by its versionless development model, instead uses a
+ conformance definition that more closely models how specifications
+ are used in practice.</li><!--CONFORMANCE-->
+
+ <li>The W3C HTML specification omits a paragraph of implementation
+ advice because of <a href=http://lists.w3.org/Archives/Public/public-html/2010Jun/0001.html>a
+ working group decision from June 2010</a>.</li>
+
+ <li>The W3C HTML specification includes a paragraph of advice
+ redundant with the ARIA specifications because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0244.html>a
+ working group decision from March 2011</a>.</li>
+
+ <li>The W3C HTML specification gives incomplete advice regarding
+ the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute and instead
+ references other documents on the matter because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0691.html>a
+ working group decision from March 2011</a>.</li>
+
+ <li>The W3C HTML specification includes a link to an incomplete
+ document that contradict this specification because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Feb/0407.html>a
+ working group decision from Februray 2011</a>.</li><!--HPAAIG-->
+
+ <li>The W3C HTML specification has different prose regarding the
+ use of tables for layout purposes because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0245.html>a
+ working group decision from March 2011</a>. In contrast, this
+ specification unambiguously disallows the use of <code><a href=#the-table-element>table</a></code>
+ elements for layout purposes.</li>
+
+ <li>The W3C HTML specification requires authors who are writing
+ HTML e-mails with images to people they know can see the images
+ (e.g. a wife sending her husband photos of their child) to
+ nonetheless include textual alternatives to those images, because
+ of <a href=http://lists.w3.org/Archives/Public/public-html/2011Apr/0451.html>a
+ working group decision from April 2011</a>.</li>
+
+ <li>The W3C HTML specification does not state that the
+ <code><a href=#the-img-element>img</a></code> element's <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code>
+ attribute is its <a href=#fallback-content>fallback content</a>, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Apr/0452.html>a
+ working group decision from April 2011</a>.</li>
+
+ <li>The W3C HTML specification is missing a clause that requires
+ conformance checkers to discourage cargo-cult accessibility
+ authoring because of <a href=http://lists.w3.org/Archives/Public/public-html/2011May/0018.html>a
+ working group chair decision from May 2011</a>.</li><!--bug
+ 11557-->
+
+ <li>The W3C HTML specification is missing some conformance
+ constraints that would make documents misusing <code><a href=#the-canvas-element>canvas</a></code>
+ invalid, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Jun/0083.html>a
+ working group chair decision from June 2011</a>.</li><!--bug
+ 12906-->
+
+ <li>The W3C 2D Context specification has a different API for
+ handling focus and selection in the 2D canvas API, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011May/0138.html>a
+ working group chair decision from May 2011</a>.</li>
+
+ </ul><p>The following sections are only published in the WHATWG
+ specifications and are not currently available anywhere else:</p>
+
+ <ul><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
+ <li>The <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute and related <a href=#hyperlink-auditing>hyperlink auditing</a> features.</li> <!--PING-->
+ <li>The <a href=#webvtt>WebVTT</a> format and some <a href=#text-track>text track</a> API features.</li> <!--TTVTT-->
+ <li>Rules for <a href=#atom>converting HTML to Atom</a>.</li> <!--MD-->
+ <li>The <code title=dom-document-cssElementMap><a href=#dom-document-csselementmap>cssElementMap</a></code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
+ <li>An experimental <code><a href=#undomanager>UndoManager</a></code> interface.</li><!--UNDO-->
+ <li>Some predefined <a href=#mdvocabs>Microdata vocabularies</a>.</li>
+ </ul><!--
+ <p>Features that are part of the WHATWG HTML Living Standard
+ specification but that are currently published as separate
+ specifications as well, and are not included in the W3C HTML5
+ specification, consist of:</p>
+
+ <ul>
+ <li><a href="#2dcontext">Canvas 2D Graphics Context</a>--><!--2DCONTEXT--><!--
+ <li><a href="#microdata">Microdata</a>--><!--MD--><!--
+ <li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)--><!--POSTMSG--><!--
+ <li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)--><!--POSTMSG--><!--
+ </ul>
+--><!--
+ <h6 class="notoc">What else is HTML5?</h6>
+
+ <p>Features that are not currently published or maintained by the
+ WHATWG but that are sometimes considered to be informally part of
+ "HTML5" include:</p>
+
+ <ul>
+ <li><a href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol">WebSocket protocol</a>
+ <li><a href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Media Type Sniffing</a>
+ <li><a href="http://tools.ietf.org/html/draft-abarth-origin">The Web Origin Concept</a>
+ <li><a href="http://dev.w3.org/geo/api/spec-source.html">Geolocation API</a>
+ <li><a href="http://www.w3.org/TR/SVG/">SVG</a>
+ <li><a href="http://www.w3.org/TR/MathML/">MathML</a>
+ <li><a href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/">XMLHttpRequest</a>
+ <li>Parts of <a href="http://www.w3.org/Style/CSS/current-work">CSS</a>.</li>
+ </ul>
+--><!--
+ <p>The <a href="#forms">forms</a> part of this specification was
+ previously published separately in a specification known as Web
+ Forms 2. The <a href="#workers">Web Workers</a> section was also
+ previously published as a separate document.</p>
+--><!--
+ <p>See also <a
+ href="http://wiki.whatwg.org/wiki/FAQ#What_are_the_various_versions_of_the_spec.3F">the
+ relevant FAQ entry</a>.</p>
+--><!--VERSION--><h3 id=background><span class=secno>1.2 </span>Background</h3>
+
<p><i>This section is non-normative.</i></p>
<p>The World Wide Web's markup language has always been HTML. HTML
@@ -67474,7 +67640,7 @@
</dd>
- </dl><h6 id=runtime-script-errors><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</h6>
+ </dl><h6 id=runtime-script-errors-in-documents><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</h6>
<p>Whenever an uncaught runtime script error occurs in one of the
scripts associated with a <code><a href=#document>Document</a></code>, the user agent must
Modified: index
===================================================================
--- index 2011-06-16 04:55:29 UTC (rev 6239)
+++ index 2011-06-16 07:16:14 UTC (rev 6240)
@@ -282,7 +282,9 @@
<ol class=toc>
<li><a href=#introduction><span class=secno>1 </span>Introduction</a>
<ol>
- <li><a href=#is-this-html5?><span class=secno>1.1 </span>Is this HTML5?</a></li>
+ <li><a href=#is-this-html5?><span class=secno>1.1 </span>Is this HTML5?</a>
+ <ol>
+ <li><a class=notoc href=#how-do-the-whatwg-and-w3c-specifications-differ?><span class=secno>1.1.1 </span>How do the WHATWG and W3C specifications differ?</a></ol></li>
<li><a href=#background><span class=secno>1.2 </span>Background</a></li>
<li><a href=#audience><span class=secno>1.3 </span>Audience</a></li>
<li><a href=#scope><span class=secno>1.4 </span>Scope</a></li>
@@ -929,7 +931,7 @@
<li><a href=#killing-scripts><span class=secno>7.1.3.4 </span>Killing scripts</a></li>
<li><a href=#runtime-script-errors><span class=secno>7.1.3.5 </span>Runtime script errors</a>
<ol>
- <li><a href=#runtime-script-errors><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</a></ol></ol></li>
+ <li><a href=#runtime-script-errors-in-documents><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</a></ol></ol></li>
<li><a href=#event-loops><span class=secno>7.1.4 </span>Event loops</a>
<ol>
<li><a href=#definitions-1><span class=secno>7.1.4.1 </span>Definitions</a></li>
@@ -1298,139 +1300,182 @@
<p><i>This section is non-normative.</i></p>
+ <p>In short: Yes.</p>
+ <p>In more length: The term "HTML5" is widely used as a buzzword to
+ refer to modern Web technologies, many of which (though by no means
+ all) are developed at the WHATWG, in some cases in conjunction with
+ the W3C and IETF.</p>
- <p>In short: Yes.</p>
+ <p>The WHATWG work is all published in one specification
- <p>In more length: "HTML5" has at various times been used to refer
- to a wide variety of technologies, some of which originated in this
- document, and some of which have only ever been tangentially
- related.</p>
- <p>This specification, published by the WHATWG and developed in
- conjunction with the W3C, defines the core HTML language and some
- the infrastructure on which it relies. The W3C also publishes parts
- of this specification. One of these parts is called "HTML5".</p>
+ (known as "<a href=http://www.whatwg.org/specs/web-apps/current-work/complete/>Web Applications 1.0</a>"),
- <p>This specification and the specifications published by the W3C
- differ in a small number of ways. The main difference is that the
- W3C version does not include some newer features, such as:</p>
+ parts of which are republished in a variety of other forms,
+ including an edition optimized for Web developers
- <ul class=brief><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
- <li>The <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute and related <a href=#hyperlink-auditing>hyperlink auditing</a> features.</li> <!--PING-->
- <li>The <a href=#webvtt>WebVTT</a> format and some <a href=#text-track>text track</a> API features.</li> <!--TTVTT-->
- <li>Rules for <a href=#atom>converting HTML to Atom</a>.</li> <!--MD-->
- <li>The <code title=dom-document-cssElementMap><a href=#dom-document-csselementmap>cssElementMap</a></code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
- <li>An experimental <code><a href=#undomanager>UndoManager</a></code> interface.</li><!--UNDO-->
- </ul><p>This is a result of the specifications having different
- development modalities. The WHATWG specification is a continuously
- maintained living standard, with maturity managed at a very granular
- per-section scale, indicated by markers in the left margin; this is
- intended to model the way in which specifications are approached in
- practice by implementors and authors alike. The W3C specification
- follows a more traditional style, with versioned releases of the
- specification, and with maturity management being done only at the
- document level; this means that the W3C specification has a version
- number (currently "5") and necessarily goes through periods of
- "feature freeze" where new features are not added, so that the
- specification can as a whole reach a more mature state.</p>
+ (known as <a href=http://developers.whatwg.org/>HTML5</a>),
- <p>In addition to the above, there are some small differences,
- mostly editorial, between the two versions of the specification:</p><!--FORK-->
- <ul class=brief><li>Instead of this section, the W3C version has a different
- paragraph explaining the difference between the W3C and WHATWG
- versions of HTML.</li> <!-- in the status section -->
+ and one which focuses mainly on the core HTML language
- <li>The W3C version refers to the technology as HTML5, rather than
- just HTML.</li><!--VERSION-->
+ (which you are reading right now).
+
+ In addition, two subparts of the specification are republished as
+ separate documents, for ease of reference:
+ <a href=http://www.whatwg.org/specs/web-apps/current-work/webvtt.html>WebVTT</a>
+ and
+ <a href=http://www.whatwg.org/specs/web-apps/current-work/webrtc.html>WebRTC</a>.
+ </p>
+
+ <p>The W3C also publishes parts of this specification as separate
+ documents. One of these parts is called "HTML5"; it is a subset of
+
+
+ this specification (the HTML Living Standard).</p>
+
+<!--
+ <p>The WHATWG specification is a continuously maintained living
+ standard, with maturity managed at a very granular per-section
+ scale, indicated by markers in the left margin; this is intended to
+ model the way in which specifications are approached in practice by
+ implementors and authors alike. The W3C specifications follow a more
+ traditional style, with versioned releases of the specification, and
+ with maturity management being done only at the document level; this
+ means that the W3C specifications have version numbers (e.g.
+ "HTML5") and necessarily go through periods of "feature freeze"
+ where new features are not added, so that the specifications can as
+ a whole reach a more mature state.</p>
+-->
+
+ <h6 class=notoc id=how-do-the-whatwg-and-w3c-specifications-differ?><span class=secno>1.1.1 </span>How do the WHATWG and W3C specifications differ?</h6>
+
+ <p>The features present in both the WHATWG and W3C specifications
+ are specified using identical text, except for the following (mostly
+ editorial) differences:</p><!--FORK-->
+
+ <ul><!--
+ <li>Instead of this section, the W3C HTML specification has a
+ different paragraph explaining the difference between the W3C and
+ WHATWG versions of HTML.</li>
+--><!-- in the status section --><li>The W3C HTML specification refers to the technology as HTML5,
+ rather than just HTML.</li><!--VERSION-->
+
<li>Examples that use features from HTML5 are not present in the
- W3C version since the W3C version is published as HTML4 due to <a href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
+ W3C specifications since the W3C specifications are published as
+ HTML4 due to <a href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
publication policies</a>.</li><!--HTML4POLICE-->
- <li>The W3C version 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
+ <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
working group decision from March 2011</a>. This specification, in
part driven by its versionless development model, instead uses a
conformance definition that more closely models how specifications
are used in practice.</li><!--CONFORMANCE-->
- <li>The W3C version omits a paragraph of implementation advice
- because of <a href=http://lists.w3.org/Archives/Public/public-html/2010Jun/0001.html>a
+ <li>The W3C HTML specification omits a paragraph of implementation
+ advice because of <a href=http://lists.w3.org/Archives/Public/public-html/2010Jun/0001.html>a
working group decision from June 2010</a>.</li>
- <li>The W3C version includes a paragraph of advice redundant with
- the ARIA specifications because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0244.html>a
+ <li>The W3C HTML specification includes a paragraph of advice
+ redundant with the ARIA specifications because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0244.html>a
working group decision from March 2011</a>.</li>
- <li>The W3C version gives incomplete advice regarding the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute and instead references
- other documents on the matter because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0691.html>a
+ <li>The W3C HTML specification gives incomplete advice regarding
+ the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute and instead
+ references other documents on the matter because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0691.html>a
working group decision from March 2011</a>.</li>
- <li>The W3C version includes a link to an incomplete document that
- contradict this specification because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Feb/0407.html>a
+ <li>The W3C HTML specification includes a link to an incomplete
+ document that contradict this specification because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Feb/0407.html>a
working group decision from Februray 2011</a>.</li><!--HPAAIG-->
- <li>The W3C version has different prose regarding the use of tables
- for layout purposes because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0245.html>a
+ <li>The W3C HTML specification has different prose regarding the
+ use of tables for layout purposes because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0245.html>a
working group decision from March 2011</a>. In contrast, this
specification unambiguously disallows the use of <code><a href=#the-table-element>table</a></code>
elements for layout purposes.</li>
- <li>The W3C version requires authors who are writing HTML e-mails
- with images to people they know can see the images (e.g. a wife
- sending her husband photos of their child) to nonetheless include
- textual alternatives to those images, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Apr/0451.html>a
+ <li>The W3C HTML specification requires authors who are writing
+ HTML e-mails with images to people they know can see the images
+ (e.g. a wife sending her husband photos of their child) to
+ nonetheless include textual alternatives to those images, because
+ of <a href=http://lists.w3.org/Archives/Public/public-html/2011Apr/0451.html>a
working group decision from April 2011</a>.</li>
- <li>The W3C version does not state that the <code><a href=#the-img-element>img</a></code>
- element's <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute is its
- <a href=#fallback-content>fallback content</a>, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Apr/0452.html>a
+ <li>The W3C HTML specification does not state that the
+ <code><a href=#the-img-element>img</a></code> element's <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code>
+ attribute is its <a href=#fallback-content>fallback content</a>, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Apr/0452.html>a
working group decision from April 2011</a>.</li>
- <li>The W3C version is missing a clause that requires conformance
- checkers to discourage cargo-cult accessibility authoring because
- of <a href=http://lists.w3.org/Archives/Public/public-html/2011May/0018.html>a
- working group chair decision from May 2011</a>.</li><!--bug 11557-->
+ <li>The W3C HTML specification is missing a clause that requires
+ conformance checkers to discourage cargo-cult accessibility
+ authoring because of <a href=http://lists.w3.org/Archives/Public/public-html/2011May/0018.html>a
+ working group chair decision from May 2011</a>.</li><!--bug
+ 11557-->
- <li>The W3C version is missing some conformance constraints that
- would make documents misusing <code><a href=#the-canvas-element>canvas</a></code> invalid, because
- of <a href=http://lists.w3.org/Archives/Public/public-html/2011Jun/0083.html>a
+ <li>The W3C HTML specification is missing some conformance
+ constraints that would make documents misusing <code><a href=#the-canvas-element>canvas</a></code>
+ invalid, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Jun/0083.html>a
working group chair decision from June 2011</a>.</li><!--bug
12906-->
- </ul><p>Features that are part of HTML (and this specification) but that
- are currently published as separate specifications as well, and are
- not included in the W3C HTML5 specification, consist of:</p>
+ <li>The W3C 2D Context specification has a different API for
+ handling focus and selection in the 2D canvas API, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011May/0138.html>a
+ working group chair decision from May 2011</a>.</li>
- <ul class=brief><li><a href=#2dcontext>Canvas 2D Graphics Context</a><!--2DCONTEXT-->
- <li><a href=#microdata>Microdata</a><!--MD-->
- <li><a href=#mdvocabs>Microdata vocabularies</a>
- <li><a href=#crossDocumentMessages>Cross-document messaging</a> (also known as Communications)<!--POSTMSG-->
- <li><a href=#channel-messaging>Channel messaging</a> (also known as Communications)<!--POSTMSG-->
- </ul><p>The <a href=#forms>forms</a> part of this specification was
- previously published separately in a specification known as Web
- Forms 2.</p>
+ </ul><p>The following sections are only published in the WHATWG
+ specifications and are not currently available anywhere else:</p>
- <p>Features that are not currently in this document that were in the
- past considered part of HTML5, or that were never part of HTML5 but
- have been referred to as part of HTML5 in the media, include:</p>
+ <ul><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
+ <li>The <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute and related <a href=#hyperlink-auditing>hyperlink auditing</a> features.</li> <!--PING-->
+ <li>The <a href=#webvtt>WebVTT</a> format and some <a href=#text-track>text track</a> API features.</li> <!--TTVTT-->
+ <li>Rules for <a href=#atom>converting HTML to Atom</a>.</li> <!--MD-->
+ <li>The <code title=dom-document-cssElementMap><a href=#dom-document-csselementmap>cssElementMap</a></code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
+ <li>An experimental <code><a href=#undomanager>UndoManager</a></code> interface.</li><!--UNDO-->
+ <li>Some predefined <a href=#mdvocabs>Microdata vocabularies</a>.</li>
+ </ul><!--
+ <p>Features that are part of the WHATWG HTML Living Standard
+ specification but that are currently published as separate
+ specifications as well, and are not included in the W3C HTML5
+ specification, consist of:</p>
- <ul class=brief><li><a href=http://www.whatwg.org/specs/web-workers/current-work/>Web Workers</a>
- <li><a href=http://dev.w3.org/html5/webstorage/>Web Storage</a>
- <li><a href=http://dev.w3.org/html5/websockets/>WebSocket API</a>
- <li><a href=http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol>WebSocket protocol</a>
- <li><a href=http://dev.w3.org/html5/eventsource/>Server-sent Events</a>
- <li><a href=http://tools.ietf.org/html/draft-abarth-mime-sniff>Media Type Sniffing</a>
- <li><a href=http://tools.ietf.org/html/draft-abarth-origin>The Web Origin Concept</a>
- <li><a href=http://dev.w3.org/geo/api/spec-source.html>Geolocation API</a>
- <li><a href=http://www.w3.org/TR/SVG/>SVG</a>
- <li><a href=http://www.w3.org/TR/MathML/>MathML</a>
- <li><a href=http://dev.w3.org/2006/webapi/XMLHttpRequest-2/>XMLHttpRequest</a>
- <li>Parts of <a href=http://www.w3.org/Style/CSS/current-work>CSS</a>.</li>
- </ul><h3 id=background><span class=secno>1.2 </span>Background</h3>
+ <ul>
+ <li><a href="#2dcontext">Canvas 2D Graphics Context</a>--><!--2DCONTEXT--><!--
+ <li><a href="#microdata">Microdata</a>--><!--MD--><!--
+ <li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)--><!--POSTMSG--><!--
+ <li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)--><!--POSTMSG--><!--
+ </ul>
+--><!--
+ <h6 class="notoc">What else is HTML5?</h6>
+ <p>Features that are not currently published or maintained by the
+ WHATWG but that are sometimes considered to be informally part of
+ "HTML5" include:</p>
+
+ <ul>
+ <li><a href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol">WebSocket protocol</a>
+ <li><a href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Media Type Sniffing</a>
+ <li><a href="http://tools.ietf.org/html/draft-abarth-origin">The Web Origin Concept</a>
+ <li><a href="http://dev.w3.org/geo/api/spec-source.html">Geolocation API</a>
+ <li><a href="http://www.w3.org/TR/SVG/">SVG</a>
+ <li><a href="http://www.w3.org/TR/MathML/">MathML</a>
+ <li><a href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/">XMLHttpRequest</a>
+ <li>Parts of <a href="http://www.w3.org/Style/CSS/current-work">CSS</a>.</li>
+ </ul>
+--><!--
+ <p>The <a href="#forms">forms</a> part of this specification was
+ previously published separately in a specification known as Web
+ Forms 2. The <a href="#workers">Web Workers</a> section was also
+ previously published as a separate document.</p>
+--><!--
+ <p>See also <a
+ href="http://wiki.whatwg.org/wiki/FAQ#What_are_the_various_versions_of_the_spec.3F">the
+ relevant FAQ entry</a>.</p>
+--><!--VERSION--><h3 id=background><span class=secno>1.2 </span>Background</h3>
+
<p><i>This section is non-normative.</i></p>
<p>The World Wide Web's markup language has always been HTML. HTML
@@ -67482,7 +67527,7 @@
</dd>
- </dl><h6 id=runtime-script-errors><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</h6>
+ </dl><h6 id=runtime-script-errors-in-documents><span class=secno>7.1.3.5.1 </span>Runtime script errors in documents</h6>
<p>Whenever an uncaught runtime script error occurs in one of the
scripts associated with a <code><a href=#document>Document</a></code>, the user agent must
Modified: source
===================================================================
--- source 2011-06-16 04:55:29 UTC (rev 6239)
+++ source 2011-06-16 07:16:14 UTC (rev 6240)
@@ -58,153 +58,204 @@
<!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
+ <p>In short: Yes.</p>
+
+ <p>In more length: The term "HTML5" is widely used as a buzzword to
+ refer to modern Web technologies, many of which (though by no means
+ all) are developed at the WHATWG, in some cases in conjunction with
+ the W3C and IETF.</p>
+
+ <p>The WHATWG work is all published in one specification
+
<!--END complete--><!--END epub-->
+ (known as "<a href="http://www.whatwg.org/specs/web-apps/current-work/complete/">Web Applications 1.0</a>"),
+<!--END html--><!--END dev-html-->
+<!--START complete--><!--START epub-->
+ (the one you are reading right now),
+<!--START html--><!--START dev-html-->
- <p>In short: Yes.</p>
+ parts of which are republished in a variety of other forms,
+ including an edition optimized for Web developers
- <p>In more length: "HTML5" has at various times been used to refer
- to a wide variety of technologies, some of which originated in this
- document, and some of which have only ever been tangentially
- related.</p>
+<!--END complete--><!--END epub--><!--END html-->
+ (which you are reading right now),
+<!--END dev-html-->
+<!--START complete--><!--START epub--><!--START html-->
+ (known as <a href="http://developers.whatwg.org/">HTML5</a>),
+<!--START dev-html-->
- <p>This specification, published by the WHATWG and developed in
- conjunction with the W3C, defines the core HTML language and some
- the infrastructure on which it relies. The W3C also publishes parts
- of this specification. One of these parts is called "HTML5".</p>
+ and one which focuses mainly on the core HTML language
- <p>This specification and the specifications published by the W3C
- differ in a small number of ways. The main difference is that the
- W3C version does not include some newer features, such as:</p>
+<!--END complete--><!--END epub--><!--END dev-html-->
+ (which you are reading right now).
+<!--END html-->
+<!--START complete--><!--START epub--><!--START dev-html-->
+ (known as the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/">HTML Living Standard</a>).
+<!--START html-->
- <ul class="brief">
- <li>The <code>PeerConnection</code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
- <li>The <code title="attr-hyperlink-ping">ping</code> attribute and related <span>hyperlink auditing</span> features.</li> <!--PING-->
- <li>The <span>WebVTT</span> format and some <span>text track</span> API features.</li> <!--TTVTT-->
- <li>Rules for <a href="#atom">converting HTML to Atom</a>.</li> <!--MD-->
- <li>The <code title="dom-document-cssElementMap">cssElementMap</code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
- <li>An experimental <code>UndoManager</code> interface.</li><!--UNDO-->
- </ul>
+ In addition, two subparts of the specification are republished as
+ separate documents, for ease of reference:
+ <a href="http://www.whatwg.org/specs/web-apps/current-work/webvtt.html">WebVTT</a>
+ and
+ <a href="http://www.whatwg.org/specs/web-apps/current-work/webrtc.html">WebRTC</a>.
+ </p>
- <p>This is a result of the specifications having different
- development modalities. The WHATWG specification is a continuously
- maintained living standard, with maturity managed at a very granular
- per-section scale, indicated by markers in the left margin; this is
- intended to model the way in which specifications are approached in
- practice by implementors and authors alike. The W3C specification
- follows a more traditional style, with versioned releases of the
- specification, and with maturity management being done only at the
- document level; this means that the W3C specification has a version
- number (currently "5") and necessarily goes through periods of
- "feature freeze" where new features are not added, so that the
- specification can as a whole reach a more mature state.</p>
+ <p>The W3C also publishes parts of this specification as separate
+ documents. One of these parts is called "HTML5"; it is a subset of
- <p>In addition to the above, there are some small differences,
- mostly editorial, between the two versions of the specification:</p><!--FORK-->
+<!--END complete--><!--END epub--><!--END dev-html-->
+ this specification (the HTML Living Standard).</p>
+<!--END html-->
+<!--START complete--><!--START epub--><!--START dev-html-->
+ the <a
+ href="http://www.whatwg.org/specs/web-apps/current-work/multipage/">HTML
+ Living Standard</a>.</p>
+<!--START html-->
- <ul class="brief">
+<!--
+ <p>The WHATWG specification is a continuously maintained living
+ standard, with maturity managed at a very granular per-section
+ scale, indicated by markers in the left margin; this is intended to
+ model the way in which specifications are approached in practice by
+ implementors and authors alike. The W3C specifications follow a more
+ traditional style, with versioned releases of the specification, and
+ with maturity management being done only at the document level; this
+ means that the W3C specifications have version numbers (e.g.
+ "HTML5") and necessarily go through periods of "feature freeze"
+ where new features are not added, so that the specifications can as
+ a whole reach a more mature state.</p>
+-->
- <li>Instead of this section, the W3C version has a different
- paragraph explaining the difference between the W3C and WHATWG
- versions of HTML.</li> <!-- in the status section -->
+ <h6 class="notoc">How do the WHATWG and W3C specifications differ?</h6>
- <li>The W3C version refers to the technology as HTML5, rather than
- just HTML.</li><!--VERSION-->
+ <p>The features present in both the WHATWG and W3C specifications
+ are specified using identical text, except for the following (mostly
+ editorial) differences:</p><!--FORK-->
+ <ul>
+
+<!--
+ <li>Instead of this section, the W3C HTML specification has a
+ different paragraph explaining the difference between the W3C and
+ WHATWG versions of HTML.</li>
+--> <!-- in the status section -->
+
+ <li>The W3C HTML specification refers to the technology as HTML5,
+ rather than just HTML.</li><!--VERSION-->
+
<li>Examples that use features from HTML5 are not present in the
- W3C version since the W3C version is published as HTML4 due to <a
+ W3C specifications since the W3C specifications are published as
+ HTML4 due to <a
href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
publication policies</a>.</li><!--HTML4POLICE-->
- <li>The W3C version defines conformance for documents in a more
- traditional (version-orientated) way, because of <a
+ <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
working group decision from March 2011</a>. This specification, in
part driven by its versionless development model, instead uses a
conformance definition that more closely models how specifications
are used in practice.</li><!--CONFORMANCE-->
- <li>The W3C version omits a paragraph of implementation advice
- because of <a
+ <li>The W3C HTML specification omits a paragraph of implementation
+ advice because of <a
href="http://lists.w3.org/Archives/Public/public-html/2010Jun/0001.html">a
working group decision from June 2010</a>.</li>
- <li>The W3C version includes a paragraph of advice redundant with
- the ARIA specifications because of <a
+ <li>The W3C HTML specification includes a paragraph of advice
+ redundant with the ARIA specifications because of <a
href="http://lists.w3.org/Archives/Public/public-html/2011Mar/0244.html">a
working group decision from March 2011</a>.</li>
- <li>The W3C version gives incomplete advice regarding the <code
- title="attr-img-alt">alt</code> attribute and instead references
- other documents on the matter because of <a
+ <li>The W3C HTML specification gives incomplete advice regarding
+ the <code title="attr-img-alt">alt</code> attribute and instead
+ references other documents on the matter because of <a
href="http://lists.w3.org/Archives/Public/public-html/2011Mar/0691.html">a
working group decision from March 2011</a>.</li>
- <li>The W3C version includes a link to an incomplete document that
- contradict this specification because of <a
+ <li>The W3C HTML specification includes a link to an incomplete
+ document that contradict this specification because of <a
href="http://lists.w3.org/Archives/Public/public-html/2011Feb/0407.html">a
working group decision from Februray 2011</a>.</li><!--HPAAIG-->
- <li>The W3C version has different prose regarding the use of tables
- for layout purposes because of <a
+ <li>The W3C HTML specification has different prose regarding the
+ use of tables for layout purposes because of <a
href="http://lists.w3.org/Archives/Public/public-html/2011Mar/0245.html">a
working group decision from March 2011</a>. In contrast, this
specification unambiguously disallows the use of <code>table</code>
elements for layout purposes.</li>
- <li>The W3C version requires authors who are writing HTML e-mails
- with images to people they know can see the images (e.g. a wife
- sending her husband photos of their child) to nonetheless include
- textual alternatives to those images, because of <a
+ <li>The W3C HTML specification requires authors who are writing
+ HTML e-mails with images to people they know can see the images
+ (e.g. a wife sending her husband photos of their child) to
+ nonetheless include textual alternatives to those images, because
+ of <a
href="http://lists.w3.org/Archives/Public/public-html/2011Apr/0451.html">a
working group decision from April 2011</a>.</li>
- <li>The W3C version does not state that the <code>img</code>
- element's <code title="attr-img-alt">alt</code> attribute is its
- <span>fallback content</span>, because of <a
+ <li>The W3C HTML specification does not state that the
+ <code>img</code> element's <code title="attr-img-alt">alt</code>
+ attribute is its <span>fallback content</span>, because of <a
href="http://lists.w3.org/Archives/Public/public-html/2011Apr/0452.html">a
working group decision from April 2011</a>.</li>
- <li>The W3C version is missing a clause that requires conformance
- checkers to discourage cargo-cult accessibility authoring because
- of <a
+ <li>The W3C HTML specification is missing a clause that requires
+ conformance checkers to discourage cargo-cult accessibility
+ authoring because of <a
href="http://lists.w3.org/Archives/Public/public-html/2011May/0018.html">a
- working group chair decision from May 2011</a>.</li><!--bug 11557-->
+ working group chair decision from May 2011</a>.</li><!--bug
+ 11557-->
- <li>The W3C version is missing some conformance constraints that
- would make documents misusing <code>canvas</code> invalid, because
- of <a
+ <li>The W3C HTML specification is missing some conformance
+ constraints that would make documents misusing <code>canvas</code>
+ invalid, because of <a
href="http://lists.w3.org/Archives/Public/public-html/2011Jun/0083.html">a
working group chair decision from June 2011</a>.</li><!--bug
12906-->
+ <li>The W3C 2D Context specification has a different API for
+ handling focus and selection in the 2D canvas API, because of <a
+ href="http://lists.w3.org/Archives/Public/public-html/2011May/0138.html">a
+ working group chair decision from May 2011</a>.</li>
+
</ul>
- <p>Features that are part of HTML (and this specification) but that
- are currently published as separate specifications as well, and are
- not included in the W3C HTML5 specification, consist of:</p>
+ <p>The following sections are only published in the WHATWG
+ specifications and are not currently available anywhere else:</p>
- <ul class="brief">
- <li><a href="#2dcontext">Canvas 2D Graphics Context</a><!--2DCONTEXT-->
- <li><a href="#microdata">Microdata</a><!--MD-->
- <li><a href="#mdvocabs">Microdata vocabularies</a>
- <li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)<!--POSTMSG-->
- <li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)<!--POSTMSG-->
+ <ul>
+ <li>The <code>PeerConnection</code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
+ <li>The <code title="attr-hyperlink-ping">ping</code> attribute and related <span>hyperlink auditing</span> features.</li> <!--PING-->
+ <li>The <span>WebVTT</span> format and some <span>text track</span> API features.</li> <!--TTVTT-->
+ <li>Rules for <a href="#atom">converting HTML to Atom</a>.</li> <!--MD-->
+ <li>The <code title="dom-document-cssElementMap">cssElementMap</code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
+ <li>An experimental <code>UndoManager</code> interface.</li><!--UNDO-->
+ <li>Some predefined <a href="#mdvocabs">Microdata vocabularies</a>.</li>
</ul>
- <p>The <a href="#forms">forms</a> part of this specification was
- previously published separately in a specification known as Web
- Forms 2.</p>
+<!--
+ <p>Features that are part of the WHATWG HTML Living Standard
+ specification but that are currently published as separate
+ specifications as well, and are not included in the W3C HTML5
+ specification, consist of:</p>
- <p>Features that are not currently in this document that were in the
- past considered part of HTML5, or that were never part of HTML5 but
- have been referred to as part of HTML5 in the media, include:</p>
+ <ul>
+ <li><a href="#2dcontext">Canvas 2D Graphics Context</a>--><!--2DCONTEXT--><!--
+ <li><a href="#microdata">Microdata</a>--><!--MD--><!--
+ <li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)--><!--POSTMSG--><!--
+ <li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)--><!--POSTMSG--><!--
+ </ul>
+-->
- <ul class="brief">
- <li><a href="http://www.whatwg.org/specs/web-workers/current-work/">Web Workers</a>
- <li><a href="http://dev.w3.org/html5/webstorage/">Web Storage</a>
- <li><a href="http://dev.w3.org/html5/websockets/">WebSocket API</a>
+<!--
+ <h6 class="notoc">What else is HTML5?</h6>
+
+ <p>Features that are not currently published or maintained by the
+ WHATWG but that are sometimes considered to be informally part of
+ "HTML5" include:</p>
+
+ <ul>
<li><a href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol">WebSocket protocol</a>
- <li><a href="http://dev.w3.org/html5/eventsource/">Server-sent Events</a>
<li><a href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Media Type Sniffing</a>
<li><a href="http://tools.ietf.org/html/draft-abarth-origin">The Web Origin Concept</a>
<li><a href="http://dev.w3.org/geo/api/spec-source.html">Geolocation API</a>
@@ -213,20 +264,22 @@
<li><a href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/">XMLHttpRequest</a>
<li>Parts of <a href="http://www.w3.org/Style/CSS/current-work">CSS</a>.</li>
</ul>
+-->
-<!--END html--><!--END dev-html-->
-<!--START complete--><!--START epub-->
+<!--
+ <p>The <a href="#forms">forms</a> part of this specification was
+ previously published separately in a specification known as Web
+ Forms 2. The <a href="#workers">Web Workers</a> section was also
+ previously published as a separate document.</p>
+-->
- <p>No, although it does contain everything that is part of HTML5. If
- you want only HTML5, please see <a
- href="http://www.whatwg.org/html">the HTML specification</a>.</p>
-
- <p><em>This</em> specification contains everything that the WHATWG
- is actively working on. For more details, please see <a
+<!--
+ <p>See also <a
href="http://wiki.whatwg.org/wiki/FAQ#What_are_the_various_versions_of_the_spec.3F">the
relevant FAQ entry</a>.</p>
+-->
-<!--START html--><!--START dev-html--><!--START w3c-html--><!--VERSION-->
+<!--START w3c-html--><!--VERSION-->
<h3>Background</h3>
@@ -76987,7 +77040,7 @@
</dl>
- <h6 id="runtime-script-errors">Runtime script errors in documents</h6>
+ <h6>Runtime script errors in documents</h6>
<p>Whenever an uncaught runtime script error occurs in one of the
scripts associated with a <code>Document</code>, the user agent must
More information about the Commit-Watchers
mailing list