- From: poot <cvsmail@w3.org>
- Date: Thu, 20 Nov 2008 22:32:05 +0900 (JST)
- To: public-html-diffs@w3.org
Add the Audience section to the intro. (whatwg r2424)
1.7.1 How to read this specification
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#how-to-read-this-specification
1.5.4 Relationship to Flash, Silverlight, XUL and similar proprietary languages
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#relationship-to-flash-silverlight-xul-and-similar-proprietary-languages
1.5.2 Relationship to XHTML 1.x
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#relationship-to-xhtml-1.x
1.7 Structure of this specification
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#structure-of-this-specification
1 Introduction
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#introduction
this
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#x-that
1.6 HTML vs XHTML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#html-vs-xhtml
1.7.2 Typographic conventions
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#typographic-conventions
1.5.3 Relationship to XHTML2 and XForms
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#relationship-to-xhtml2-and-xforms
1.2 Audience
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#audience
1.4 History
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#history-0
1.3 Scope
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#scope
1.5 Relationships to other specifications
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1596.html#relationships-to-other-specifications
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1595&r2=1.1596&f=h
http://html5.org/tools/web-apps-tracker?from=2423&to=2424
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1595
retrieving revision 1.1596
diff -u -d -r1.1595 -r1.1596
--- Overview.html 20 Nov 2008 02:52:49 -0000 1.1595
+++ Overview.html 20 Nov 2008 13:28:17 -0000 1.1596
@@ -121,20 +121,21 @@
<li><a href=#introduction><span class=secno>1 </span>Introduction</a>
<ol>
<li><a href=#background><span class=secno>1.1 </span>Background</a></li>
- <li><a href=#scope><span class=secno>1.2 </span>Scope</a></li>
- <li><a href=#history-0><span class=secno>1.3 </span>History</a></li>
- <li><a href=#relationships-to-other-specifications><span class=secno>1.4 </span>Relationships to other specifications</a>
+ <li><a href=#audience><span class=secno>1.2 </span>Audience</a></li>
+ <li><a href=#scope><span class=secno>1.3 </span>Scope</a></li>
+ <li><a href=#history-0><span class=secno>1.4 </span>History</a></li>
+ <li><a href=#relationships-to-other-specifications><span class=secno>1.5 </span>Relationships to other specifications</a>
<ol>
- <li><a href=#relationship-to-html-4.01-and-dom2-html><span class=secno>1.4.1 </span>Relationship to HTML 4.01 and DOM2 HTML</a></li>
- <li><a href=#relationship-to-xhtml-1.x><span class=secno>1.4.2 </span>Relationship to XHTML 1.x</a></li>
- <li><a href=#relationship-to-xhtml2-and-xforms><span class=secno>1.4.3 </span>Relationship to XHTML2 and XForms</a></li>
- <li><a href=#relationship-to-flash-silverlight-xul-and-similar-proprietary-languages><span class=secno>1.4.4 </span>Relationship to Flash, Silverlight, XUL <!-- alphabetical -->
+ <li><a href=#relationship-to-html-4.01-and-dom2-html><span class=secno>1.5.1 </span>Relationship to HTML 4.01 and DOM2 HTML</a></li>
+ <li><a href=#relationship-to-xhtml-1.x><span class=secno>1.5.2 </span>Relationship to XHTML 1.x</a></li>
+ <li><a href=#relationship-to-xhtml2-and-xforms><span class=secno>1.5.3 </span>Relationship to XHTML2 and XForms</a></li>
+ <li><a href=#relationship-to-flash-silverlight-xul-and-similar-proprietary-languages><span class=secno>1.5.4 </span>Relationship to Flash, Silverlight, XUL <!-- alphabetical -->
and similar proprietary languages</a></ol></li>
- <li><a href=#html-vs-xhtml><span class=secno>1.5 </span>HTML vs XHTML</a></li>
- <li><a href=#structure-of-this-specification><span class=secno>1.6 </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.6.1 </span>How to read this specification</a></li>
- <li><a href=#typographic-conventions><span class=secno>1.6.2 </span>Typographic conventions</a></ol></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></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>
@@ -928,7 +929,20 @@
other types of documents.<p>The main area that has not been adequately addressed by HTML is a
vague subject referred to as Web Applications. This specification
attempts to rectify this, while at the same time updating the HTML
- specifications to address issues raised in the past few years.<h3 id=scope><span class=secno>1.2 </span>Scope</h3><p><em>This section is non-normative.</em><p>This specification is limited to providing a semantic-level
+ specifications to address issues raised in the past few years.<h3 id=audience><span class=secno>1.2 </span>Audience</h3><p><em>This section is non-normative.</em><p>This specification is intended for authors of documents and
+ scripts that use the features defined in this specificaton, and
+ implementors of tools that are intended to conform to this
+ specification, and individuals wishing to establish the correctness
+ of documents or implementations with respect to the requirements of
+ this specification.<p>This document is probably not suited to readers who do not
+ already have at least a passing familiarity with Web technologies,
+ as in places it sacrifices clarity for precision, and brevity for
+ completeness. More approachable tutorials and authoring guides can
+ provide a gentler introduction to the topic.<p>In particular, readers should be familiar with the basics of DOM
+ Core and DOM Events before reading this specification. An
+ understanding of WebIDL, HTTP, XML, Unicode, character encodings,
+ JavaScript, and CSS will be helpful in places but is not
+ essential.<h3 id=scope><span class=secno>1.3 </span>Scope</h3><p><em>This section is non-normative.</em><p>This specification is limited to providing a semantic-level
markup language and associated semantic-level scripting APIs for
authoring accessible pages on the Web ranging from static documents
to dynamic applications.<p>The scope of this specification does not include providing
@@ -960,7 +974,7 @@
to achieve interoperability with, than the solutions described in
this document. Platform-specific solutions for such sophisticated
applications (for example the Mac OS X Core APIs) are even further
- ahead.<h3 id=history-0><span class=secno>1.3 </span>History</h3><p><em>This section is non-normative.</em><p>Work on HTML5 originally started in late 2003, as a proof of
+ ahead.<h3 id=history-0><span class=secno>1.4 </span>History</h3><p><em>This section is non-normative.</em><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
@@ -981,11 +995,11 @@
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=relationships-to-other-specifications><span class=secno>1.4 </span>Relationships to other specifications</h3><h4 id=relationship-to-html-4.01-and-dom2-html><span class=secno>1.4.1 </span>Relationship to HTML 4.01 and DOM2 HTML</h4><p><em>This section is non-normative.</em><p>This specification represents a new version of HTML4, along with
+ the less restrictive license on the WHATWG site.<p>Since then, both groups have been working together.<h3 id=relationships-to-other-specifications><span class=secno>1.5 </span>Relationships to other specifications</h3><h4 id=relationship-to-html-4.01-and-dom2-html><span class=secno>1.5.1 </span>Relationship to HTML 4.01 and DOM2 HTML</h4><p><em>This section is non-normative.</em><p>This specification represents a new version of HTML4, along with
a new version of the associated DOM2 HTML API. Migration from HTML4
to the format and APIs described in this specification should in
most cases be straightforward, as care has been taken to ensure that
- backwards-compatibility is retained. <a href=#references>[HTML4]</a> <a href=#references>[DOM2HTML]</a><h4 id=relationship-to-xhtml-1.x><span class=secno>1.4.2 </span>Relationship to XHTML 1.x</h4><p><em>This section is non-normative.</em><p>This specification is intended to replace XHTML 1.0 as the
+ backwards-compatibility is retained. <a href=#references>[HTML4]</a> <a href=#references>[DOM2HTML]</a><h4 id=relationship-to-xhtml-1.x><span class=secno>1.5.2 </span>Relationship to XHTML 1.x</h4><p><em>This section is non-normative.</em><p>This specification is intended to replace XHTML 1.0 as the
normative definition of the XML serialization of the HTML
vocabulary. <a href=#references>[XHTML10]</a><p>While this specification updates the semantics and requirements
of the vocabulary defined by XHTML Modularization 1.1 and used by
@@ -995,7 +1009,7 @@
replacement for them. <a href=#references>[XHTMLMOD]</a> <a href=#references>[XHTML11]</a><p>Thus, authors and implementors who do not need such a
modularization scheme can consider this specification a replacement
for XHTML 1.x, but those who do need such a mechanism are encouraged
- to continue using the XHTML 1.1 line of specifications.<h4 id=relationship-to-xhtml2-and-xforms><span class=secno>1.4.3 </span>Relationship to XHTML2 and XForms</h4><p><em>This section is non-normative.</em><p>XHTML2 defines a new vocabulary with features for hyperlinks,
+ to continue using the XHTML 1.1 line of specifications.<h4 id=relationship-to-xhtml2-and-xforms><span class=secno>1.5.3 </span>Relationship to XHTML2 and XForms</h4><p><em>This section is non-normative.</em><p>XHTML2 defines a new vocabulary with features for hyperlinks,
multimedia content, annotating document edits, rich metadata,
declarative interactive forms, and describing the semantics of human
literary works such as poems and scientific papers. <a href=#references>[XHTML2]</a><p>XForms similarly defines a new vocabulary with features for
@@ -1007,7 +1021,7 @@
strategy games, and the like.<p><em>This</em> specification aims to extend HTML so that it is
also suitable in these contexts.<p>XHTML2, XForms, and this specification all use different
namespaces and therefore can all be implemented in the same XML
- processor.<h4 id=relationship-to-flash-silverlight-xul-and-similar-proprietary-languages><span class=secno>1.4.4 </span>Relationship to Flash, Silverlight, XUL <!-- alphabetical -->
+ processor.<h4 id=relationship-to-flash-silverlight-xul-and-similar-proprietary-languages><span class=secno>1.5.4 </span>Relationship to Flash, Silverlight, XUL <!-- alphabetical -->
and similar proprietary languages</h4><p><em>This section is non-normative.</em><p>This specification is independent of the various proprietary
application languages that various vendors provide, but is intended
to address many of the same problems.<p>In contrast with proprietary languages, this specification is
@@ -1021,7 +1035,7 @@
they are forced to switch (or desire to switch) to another vendor's
platform, using an openly-produced and vendor neutral language means
that application authors can switch vendors with little to no
- cost.<h3 id=html-vs-xhtml><span class=secno>1.5 </span>HTML vs XHTML</h3><p><em>This section is non-normative.</em><p>This specification defines an abstract language for describing
+ cost.<h3 id=html-vs-xhtml><span class=secno>1.6 </span>HTML vs XHTML</h3><p><em>This section is non-normative.</em><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 "DOM5 HTML", or "the
DOM" for short.<p>There are various concrete syntaxes that can be used to transmit
@@ -1043,7 +1057,7 @@
feature can be represented using "HTML5", but cannot be represented
with "XHTML5" and "DOM5 HTML". Comments that contain the string
"<code title="">--></code>" can be represented in "DOM5 HTML" but
- not in "HTML5" and "XHTML5". And so forth.<h3 id=structure-of-this-specification><span class=secno>1.6 </span>Structure of this specification</h3><p><em>This section is non-normative.</em><p>This specification is divided into the following major
+ not in "HTML5" and "XHTML5". And so forth.<h3 id=structure-of-this-specification><span class=secno>1.7 </span>Structure of this specification</h3><p><em>This section is non-normative.</em><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
@@ -1098,11 +1112,11 @@
</dl><p>There are also a couple of appendices, defining <a href=#rendering>rendering rules</a> for Web browsers and listing
<a href=#no>areas that are out of scope</a> for this
- specification.<h4 id=how-to-read-this-specification><span class=secno>1.6.1 </span>How to read this specification</h4><p>This specification should be read like all other specifications.
+ 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.6.2 </span>Typographic conventions</h4><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.<p>The defining instance of a term is marked up like <dfn id=x-this title=x-this>this</dfn>. Uses of that term are marked up like
+ cross-references.<h4 id=typographic-conventions><span class=secno>1.7.2 </span>Typographic conventions</h4><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.<p>The defining instance of a term is marked up like <dfn id=x-this title=x-this>this</dfn>. Uses of that term are marked up like
<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
Received on Thursday, 20 November 2008 13:32:49 UTC