hixie: Expand the history section, drop the relationships sections. (whatwg r3884)

hixie: Expand the history section, drop the relationships sections.
(whatwg r3884)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3046&r2=1.3047&f=h
http://html5.org/tools/web-apps-tracker?from=3883&to=3884

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3046
retrieving revision 1.3047
diff -u -d -r1.3046 -r1.3047
--- Overview.html 17 Sep 2009 22:50:56 -0000 1.3046
+++ Overview.html 18 Sep 2009 00:07:29 -0000 1.3047
@@ -215,7 +215,7 @@
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
    <!--ZZZ:-->
    <!--<h2 class="no-num no-toc">W3C Working Draft 25 August 2009</h2>-->
-   <h2 class="no-num no-toc" id="editor-s-draft-17-september-2009">Editor's Draft 17 September 2009</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-18-september-2009">Editor's Draft 18 September 2009</h2>
    <!--:ZZZ-->
    <dl><!-- ZZZ: update the month/day (twice), (un)comment out--><!--
     <dt>This Version:</dt>
@@ -314,7 +314,7 @@
   track.
   <!--ZZZ:-->
   <!--This specification is the 25 August 2009 Working Draft.-->
-  This specification is the 17 September 2009 Editor's Draft.
+  This specification is the 18 September 2009 Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href="http://www.whatwg.org/">WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -340,17 +340,13 @@
     <ol>
      <li><a href="#serializability-of-script-execution"><span class="secno">1.5.1 </span>Serializability of script execution</a></li>
      <li><a href="#compliance-with-other-specifications"><span class="secno">1.5.2 </span>Compliance with other specifications</a></ol></li>
-   <li><a href="#relationships-to-other-specifications"><span class="secno">1.6 </span>Relationships to other specifications</a>
-    <ol>
-     <li><a href="#relationship-to-html4-and-dom2-html"><span class="secno">1.6.1 </span>Relationship to HTML4 and DOM2 HTML</a></li>
-     <li><a href="#relationship-to-xhtml1"><span class="secno">1.6.2 </span>Relationship to XHTML1</a></ol></li>
-   <li><a href="#html-vs-xhtml"><span class="secno">1.7 </span>HTML vs XHTML</a></li>
-   <li><a href="#structure-of-this-specification"><span class="secno">1.8 </span>Structure of this specification</a>
+   <li><a href="#html-vs-xhtml"><span class="secno">1.6 </span>HTML vs XHTML</a></li>
+   <li><a href="#structure-of-this-specification"><span class="secno">1.7 </span>Structure of this specification</a>
     <ol>
-     <li><a href="#how-to-read-this-specification"><span class="secno">1.8.1 </span>How to read this specification</a></li>
-     <li><a href="#typographic-conventions"><span class="secno">1.8.2 </span>Typographic conventions</a></ol></li>
-   <li><a href="#a-quick-introduction-to-html"><span class="secno">1.9 </span>A quick introduction to HTML</a></li>
-   <li><a href="#recommended-reading"><span class="secno">1.10 </span>Recommended reading</a></ol></li>
+     <li><a href="#how-to-read-this-specification"><span class="secno">1.7.1 </span>How to read this specification</a></li>
+     <li><a href="#typographic-conventions"><span class="secno">1.7.2 </span>Typographic conventions</a></ol></li>
+   <li><a href="#a-quick-introduction-to-html"><span class="secno">1.8 </span>A quick introduction to HTML</a></li>
+   <li><a href="#recommended-reading"><span class="secno">1.9 </span>Recommended reading</a></ol></li>
  <li><a href="#infrastructure"><span class="secno">2 </span>Common infrastructure</a>
   <ol>
    <li><a href="#terminology"><span class="secno">2.1 </span>Terminology</a>
@@ -1247,28 +1243,70 @@
   systems, searching systems, games (especially multiplayer online
   games), public telephone books or address books, communications
   software (e-mail clients, instant messaging clients, discussion
-  software), document editing software, etc.<h3 id="history-1"><span class="secno">1.4 </span>History</h3><p><i>This section is non-normative.</i><p>Work on HTML5 originally started in late 2003, as a proof of
-  concept to show that it was possible to extend HTML4's forms to
-  provide many of the features that XForms 1.0 introduced, without
-  requiring browsers to implement rendering engines that were
-  incompatible with existing HTML Web pages. At this early stage,
-  while the draft was already publicly available, and input was
-  already being solicited from all sources, the specification was only
-  under Opera Software's copyright.<p>In early 2004, some of the principles that underlie this effort,
-  as well as an early draft proposal covering just forms-related
-  features, were presented to the W3C jointly by Mozilla and Opera at
-  a workshop discussing the future of Web Applications on the Web. The
-  proposal was rejected on the grounds that the proposal conflicted
-  with the previously chosen direction for the Web's evolution.<p>Shortly thereafter, Apple, Mozilla, and Opera jointly announced
+  software), document editing software, etc.<h3 id="history-1"><span class="secno">1.4 </span>History</h3><p><i>This section is non-normative.</i><p>For its first first years (1990-1995), HTML went through a number
+  of revisions and experienced a number of extensions, primarily
+  hosted first at CERN, and then at the IETF.<p>With the creation of the W3C, HTML's development changed venue
+  again. A first abortive attempt at extending HTML in 1995 known as
+  HTML 3.0 then made way to a more pragmatic approach known as HTML
+  3.2, which was completed in 1997. HTML4 followed, reaching
+  completion in 1998.<p>At this time, the W3C membership decided to stop evolving HTML
+  and instead begin work on an XML-based equivalent, called
+  XHTML. This effort started with a reforumlation of HTML4 in XML,
+  known as XHTML 1.0, which added no new features except the new
+  serialization, and which was completed in 2000. After XHTML 1.0, the
+  W3C's focus turned to making it easier for other working groups to
+  extend XHTML, under the banner of XHTML Modularization. In parallel
+  with this, the W3C also worked on a new language that was no
+  compatible with the earlier HTML and XHTML languages, calling it
+  XHTML2.<p>Around the time that HTML's evolution was stopped in 1998, parts
+  of the API for HTML developed by browsers were specified and
+  published under the name DOM Level 1 (in 1998) and DOM Core Level 2
+  and DOM HTML Level 2 (starting in 2000 and culminating in
+  2003). These efforts then petered out, with some DOM Level 3
+  specifications published in 2004 but the working group being closed
+  before all the Level 3 drafts were published.<p>In 2003, the publication of XForms, a technology which was
+  positioned as the next generation of Web forms, sparked a renewed
+  interest in evolving HTML itself, rather than finding replacements
+  for it. This interest was borne from the realization that XML's
+  deployment as a Web technology was limited to entirely new
+  technologies (like RSS and later Atom), rather than as a replacement
+  for existing deployed technologies (like HTML).<p>A proof of concept to show that it was possible to extend HTML4's
+  forms to provide many of the features that XForms 1.0 introduced,
+  without requiring browsers to implement rendering engines that were
+  incompatible with existing HTML Web pages, was the first result of
+  this renewed interest. At this early stage, while the draft was
+  already publicly available, and input was already being solicited
+  from all sources, the specification was only under Opera Software's
+  copyright.<p>The idea that HTML's evolution should be reopened was tested at a
+  W3C workshop in 2004, where some of the principles that underlie the
+  HTML5 work (described below), as well as the aforementioned early
+  draft proposal covering just forms-related features, were presented
+  to the W3C jointly by Mozilla and Opera. The proposal was rejected
+  on the grounds that the proposal conflicted with the previously
+  chosen direction for the Web's evolution; the W3C staff and
+  membership voted to continue developing XML-based replacements
+  instead.<p>Shortly thereafter, Apple, Mozilla, and Opera jointly announced
   their intent to continue working on the effort. A public mailing
   list was created, and the drafts were moved to the WHATWG site. The
   copyright was subsequently amended to be jointly owned by all three
-  vendors, and to allow reuse of the specifications.<p>In 2006, the W3C expressed interest in the specification, and
-  created a working group chartered to work with the WHATWG on the
-  development of the HTML5 specifications. The working group opened in
-  2007. Apple, Mozilla, and Opera allowed the W3C to publish the
-  specifications under the W3C copyright, while keeping versions with
-  the less restrictive license on the WHATWG site.<p>Since then, both groups have been working together.<h3 id="design-notes"><span class="secno">1.5 </span>Design notes</h3><p><i>This section is non-normative.</i><p>It must be admitted that many aspects of HTML appear at first
+  vendors, and to allow reuse of the specifications.<p>The WHATWG was based on several core principles, in particular
+  that technologies need to be backwards compatible, that
+  specifications and implementations need to match even if this means
+  changing the specification rather than the implementations, and that
+  specifications need to be detailed enough that implementations can
+  achieve complete interoperability without reverse-engineering each
+  other.<p>The latter requirement in particular required that the scope of
+  the HTML5 specification include what had previously been specified
+  in three separate documents: HTML4, XHTML1, and DOM2 HTML. It also
+  meant including significantly more detail than had previously been
+  included.<p>In 2006, the W3C indicated an interest to participate in the
+  development of HTML5 after all, and in 2007 formed a working group
+  chartered to work with the WHATWG on the development of the HTML5
+  specification. Apple, Mozilla, and Opera allowed the W3C to publish
+  the specification under the W3C copyright, while keeping a version
+  with the less restrictive license on the WHATWG site.<p>Since then, both groups have been working together.<p>A separate document has been published by the W3C HTML working
+  group to document the differences between this specification and the
+  language described in the HTML4 specification. <a href="#refsHTMLDIFF">[HTMLDIFF]</a><h3 id="design-notes"><span class="secno">1.5 </span>Design notes</h3><p><i>This section is non-normative.</i><p>It must be admitted that many aspects of HTML appear at first
   glance to be nonsensical and inconsistent.<p>HTML, its supporting DOM APIs, as well as many of its supporting
   technologies, have been developed over a period of several decades
   by a wide array of people with different priorities who, in many
@@ -1291,25 +1329,7 @@
   specification violating the requirements of these other
   specifications. Whenever this has occurred, the transgressions have
   been noted as "<dfn id="willful-violation" title="willful violation">willful
-  violations</dfn>".<h3 id="relationships-to-other-specifications"><span class="secno">1.6 </span>Relationships to other specifications</h3><h4 id="relationship-to-html4-and-dom2-html"><span class="secno">1.6.1 </span>Relationship to HTML4 and DOM2 HTML</h4><p><i>This section is non-normative.</i><p>This specification describes a new revision of the HTML language
-  and its associated DOM API.<p>The requirements in this specification for features that were
-  already in HTML4 and DOM2 HTML are based primarily on the
-  implementation and deployment experience collected over the past ten
-  years. Some features have been removed from the language, based on
-  best current practices; implementation requirements for some of
-  these, as well as for non-standard features that have nonetheless
-  garnered wide use, are still included in this specification to allow
-  implementations to continue supporting legacy content.  <a href="#refsHTML4">[HTML4]</a> <a href="#refsDOM2HTML">[DOM2HTML]</a><p>A separate document has been published by the W3C HTML working
-  group to provide a more detailed reference of the differences
-  between this specification and the language described in the HTML4
-  specification. <a href="#refsHTMLDIFF">[HTMLDIFF]</a><h4 id="relationship-to-xhtml1"><span class="secno">1.6.2 </span>Relationship to XHTML1</h4><p><i>This section is non-normative.</i><p>This specification is intended to replace XHTML1 as the normative
-  definition of the XML serialization of the HTML vocabulary. <a href="#refsXHTML1">[XHTML1]</a><p>While this specification updates the semantics and requirements
-  of the vocabulary defined by XHTML Modularization 1.1, it does not
-  attempt to provide a replacement for the modularization scheme
-  defined and used by that specification and its companion
-  specifications. <a href="#refsXHTMLMOD">[XHTMLMOD]</a><p>Thus, authors and implementors who need such a modularization
-  scheme are encouraged to continue using the XHTML Modularization
-  line of specifications.<h3 id="html-vs-xhtml"><span class="secno">1.7 </span>HTML vs XHTML</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>This specification defines an abstract language for describing
+  violations</dfn>".<h3 id="html-vs-xhtml"><span class="secno">1.6 </span>HTML vs XHTML</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>This specification defines an abstract language for describing
   documents and applications, and some APIs for interacting with
   in-memory representations of resources that use this language.<p>The in-memory representation is known as "DOM HTML", or "the DOM"
   for short. This specification defines version 5 of DOM HTML, known
@@ -1334,7 +1354,7 @@
   Similarly, documents that use the <code><a href="#the-noscript-element">noscript</a></code> feature can
   be represented using the HTML syntax, but cannot be represented with
   the DOM or in XML. Comments that contain the string "<code title="">--&gt;</code>" can be represented in the DOM but not in the
-  HTML syntax or in XML.<h3 id="structure-of-this-specification"><span class="secno">1.8 </span>Structure of this specification</h3><p><i>This section is non-normative.</i><p>This specification is divided into the following major
+  HTML syntax or in XML.<h3 id="structure-of-this-specification"><span class="secno">1.7 </span>Structure of this specification</h3><p><i>This section is non-normative.</i><p>This specification is divided into the following major
   sections:<dl><dt><a href="#infrastructure">Common Infrastructure</a></dt>
 
    <dd>The conformance classes, algorithms, definitions, and the
@@ -1398,11 +1418,11 @@
 
   </dl><p>There are also a couple of appendices, defining <a href="#rendering">rendering rules</a> for Web browsers and listing
   <a href="#obsolete">obsolete features</a> and <a href="#no">areas
-  that are out of scope</a> for this specification.<h4 id="how-to-read-this-specification"><span class="secno">1.8.1 </span>How to read this specification</h4><p>This specification should be read like all other specifications.
+  that are out of scope</a> for this specification.<h4 id="how-to-read-this-specification"><span class="secno">1.7.1 </span>How to read this specification</h4><p>This specification should be read like all other specifications.
   First, it should be read cover-to-cover, multiple times. Then, it
   should be read backwards at least once. Then it should be read by
   picking random sections from the contents list and following all the
-  cross-references.<h4 id="typographic-conventions"><span class="secno">1.8.2 </span>Typographic conventions</h4><p class="XXX annotation"><b>Status: </b><i>Implemented and widely deployed</i><p>This is a definition, requirement, or explanation.<p class="note">This is a note.<p class="example">This is an example.<p class="XXX">This is an open issue.<p class="warning">This is a warning.<pre class="idl extract">interface <dfn title="">Example</dfn> {
+  cross-references.<h4 id="typographic-conventions"><span class="secno">1.7.2 </span>Typographic conventions</h4><p class="XXX annotation"><b>Status: </b><i>Implemented and widely deployed</i><p>This is a definition, requirement, or explanation.<p class="note">This is a note.<p class="example">This is an example.<p class="XXX">This is an open issue.<p class="warning">This is a warning.<pre class="idl extract">interface <dfn title="">Example</dfn> {
   // this is an IDL definition
 };</pre><dl class="domintro"><dt><var title="">variable</var> = <var title="">object</var> . <code title="">method</code>( [ <var title="">optionalArgument</var> ] )</dt>
 
@@ -1416,7 +1436,7 @@
   <a href="#x-this" title="x-this">this</a> or like <i title="x-this"><a href="#x-this">this</a></i>.<p>The defining instance of an element, attribute, or API is marked
   up like <dfn id="x-that" title="x-that"><code>this</code></dfn>. References to
   that element, attribute, or API are marked up like <code title="x-that"><a href="#x-that">this</a></code>.<p>Other code fragments are marked up <code title="">like
-  this</code>.<p>Variables are marked up like <var title="">this</var>.<p class="impl">This is an implementation requirement.<h3 id="a-quick-introduction-to-html"><span class="secno">1.9 </span>A quick introduction to HTML</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>A basic HTML document looks like this:<pre id="intro-early-example">&lt;!DOCTYPE html&gt;
+  this</code>.<p>Variables are marked up like <var title="">this</var>.<p class="impl">This is an implementation requirement.<h3 id="a-quick-introduction-to-html"><span class="secno">1.8 </span>A quick introduction to HTML</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>A basic HTML document looks like this:<pre id="intro-early-example">&lt;!DOCTYPE html&gt;
 &lt;html&gt;
  &lt;head&gt;
   &lt;title&gt;Sample page&lt;/title&gt;
@@ -1504,7 +1524,7 @@
   specification might also be of use, but the novice author is
   cautioned that this specification, by necessity, defines the
   language with a level of detail that might be difficult to
-  understand at first.<h3 id="recommended-reading"><span class="secno">1.10 </span>Recommended reading</h3><p><i>This section is non-normative.</i><p>The following documents might be of interest to readers of this
+  understand at first.<h3 id="recommended-reading"><span class="secno">1.9 </span>Recommended reading</h3><p><i>This section is non-normative.</i><p>The following documents might be of interest to readers of this
   specification.<dl><dt><cite>Character Model for the World Wide Web 1.0: Fundamentals</cite> <a href="#refsCHARMOD">[CHARMOD]</a></dt>
 
    <dd><blockquote><p>This Architectural Specification provides
@@ -68782,11 +68802,6 @@
    <dd><cite><a href="http://www.w3.org/TR/css3-ui/">CSS3 Basic User
    Interface Module</a></cite>, T. &Ccedil;elik. W3C, May 2004.</dd>
 
-   <dt id="refsDOM2HTML">[DOM2HTML]</dt>
-   <dd>(Non-normative) <cite><a href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document Object Model
-   (DOM) Level 2 HTML Specification</a></cite>, J. Stenback, P. Le
-   Hegaret, A. Le Hors. W3C, January 2003.</dd>
-
    <dt id="refsDOMCORE">[DOMCORE]</dt>
    <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Core/">Document
    Object Model (DOM) Level 3 Core Specification</a></cite>, A. Le
@@ -68862,11 +68877,6 @@
    <dd>(Non-normative) <cite>Inter Gravissimas</cite>, A. Lilius,
    C. Clavius. Gregory XIII Papal Bulls, February 1582.</dd>
 
-   <dt id="refsHTML4">[HTML4]</dt>
-   <dd>(Non-normative) <cite><a href="http://www.w3.org/TR/html4/">HTML 4.01
-   Specification</a></cite>, D. Raggett, A. Le Hors, I. Jacobs.  W3C,
-   December 1999.</dd>
-
    <dt id="refsHTMLDIFF">[HTMLDIFF]</dt>
    <!--
    <dd>(Non-normative) <cite><a
@@ -69245,16 +69255,6 @@
    <dd><cite><a href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/"><code>XMLHttpRequest</code></a></cite>,
    A. van Kesteren. W3C, June 2009.</dd>
 
-   <dt id="refsXHTML1">[XHTML1]</dt>
-   <dd><cite><a href="http://www.w3.org/TR/xhtml1/">XHTML(TM) 1.0 The
-   Extensible HyperText Markup Language (Second Edition)</a></cite>. W3C,
-   August 2002.</dd>
-
-   <dt id="refsXHTMLMOD">[XHTMLMOD]</dt>
-   <dd><cite><a href="http://www.w3.org/TR/xhtml-modularization">Modularization of
-   XHTML(TM)</a></cite>, M. Altheim, F. Boumphrey, S. Dooley, S.
-   McCarron, S. Schnitzenbaumer, T. Wugofski. W3C, April 2001.</dd>
-
    <dt id="refsXML">[XML]</dt>
    <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup
    Language</a></cite>, T. Bray, J. Paoli, C. Sperberg-McQueen,

Received on Friday, 18 September 2009 00:08:43 UTC