- From: Anne van Kesteren via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 08 Jun 2010 12:53:44 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html4-differences
In directory hutz:/tmp/cvs-serv3287
Modified Files:
Overview.html Overview.src.html
Log Message:
address comments from Marcos Caceres
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.html,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -d -r1.96 -r1.97
--- Overview.html 8 Jun 2010 11:43:17 -0000 1.96
+++ Overview.html 8 Jun 2010 12:53:42 -0000 1.97
@@ -145,9 +145,6 @@
<li><a href="#development-model"><span class=secno>1.3.
</span>Development Model</a>
-
- <li><a href="#webarch"><span class=secno>1.4. </span>Impact on Web
- Architecture</a>
</ul>
<li><a href="#syntax"><span class=secno>2. </span>Syntax</a>
@@ -294,65 +291,10 @@
<h3 id=development-model><span class=secno>1.3. </span>Development Model</h3>
<p>The HTML5 specification will not be considered finished before there are
- at least two complete implementations of the specification. This is a
- different approach than previous versions of HTML had. The goal is to
- ensure that the specification is implementable and usable by designers and
- developers once it is finished.</p>
- <!-- The following <div> is here for Michael(tm) Smith who owes the
- editor one beer in exchange. -->
-
- <div>
- <h3 id=webarch><span class=secno>1.4. </span>Impact on Web Architecture</h3>
- <!-- http://lists.w3.org/Archives/Public/www-tag/2008May/0087.html
- modified to match actual contents of W3C HTML5 -->
-
- <p>The following areas / features defined in HTML5 are believed to impact
- the Web architecture:</p>
-
- <ul>
- <li>The use of the DOM as a basis for defining the language.
-
- <li>The concept of browsing contexts.
-
- <li>The distinction between user agent requirements and authoring
- requirements.
-
- <li>The use of imperative definitions rather than abstract definitions
- with the requirement of black-box equivalence in implementations.
-
- <li>The new content model concepts (replacing HTML4's block and inline
- concepts).
-
- <li>The focus on accessibility as a built-in concept for new features
- (such as the <code>hidden</code> attribute, the <code>progress</code>
- element, et cetera) instead of an add-on (like the <code>alt</code>
- attribute).
-
- <li>The focus on defining the semantics in detail (e.g. the outline
- algorithm, replacing the vague semantics in HTML4).
-
- <li>The <code>menu</code> and <code>command</code> elements.
-
- <li>The origin concept.
-
- <li>Offline Web application caches.
-
- <li>The definition of the browsing context "navigation" algorithm and the
- related session history traversal algorithms.
-
- <li>The content-type sniffing and character encoding sniffing.
-
- <li>The very explicit definition of a parser.
-
- <li>The <code>contentEditable</code> feature and the
- <code>UndoManager</code> feature.
-
- <li>The Drag and Drop and Copy and Paste architecture.
-
- <li>The new sandboxing features for <code>iframe</code>.
- </ul>
- </div>
- <!-- This closes the <div> added for Michael(tm) Smith. -->
+ at least two complete implementations of the specification. A test suite
+ will be used to measure completeness of the implementations. This approach
+ differs from previous versions of HTML. The goal is to ensure that the
+ specification is implementable, and usable by authors once it is finished.
<h2 id=syntax><span class=secno>2. </span>Syntax</h2>
@@ -362,8 +304,9 @@
href="http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.3.6">processing
instructions</a> and <a
href="http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.3.7">shorthand
- markup</a>. Documents using the HTML syntax are almost always served with
- the <code>text/html</code> media type.
+ markup</a> as these are not supported by most user agents. Documents using
+ the HTML syntax are almost always served with the <code>text/html</code>
+ media type.
<p>HTML5 also defines detailed parsing rules (including "error handling")
for this syntax which are largely compatible with popular implementations.
@@ -394,7 +337,7 @@
href="#ref-xml">XML</a></cite>]
<p>Below is an example document that conforms to the XML syntax of HTML5.
- Note that XML documents must have an XML media type such as
+ Note that XML documents must be served with an XML media type such as
<code>application/xhtml+xml</code> or <code>application/xml</code>.
<pre><code><?xml version="1.0" encoding="UTF-8"?>
@@ -409,7 +352,7 @@
<h3 id=character-encoding><span class=secno>2.1. </span>Character Encoding</h3>
- <p>For the HTML syntax of HTML5 authors have three means of setting the
+ <p>For the HTML syntax of HTML5, authors have three means of setting the
character encoding:
<ul>
@@ -569,7 +512,9 @@
<li>
<p><a
href="http://www.w3.org/TR/html5/text-level-semantics.html#the-mark-element"><code>mark</code></a>
- represents a run of marked text.
+ represents represents a run of text in one document marked or
+ highlighted for reference purposes, due to its relevance in another
+ context.
<li>
<p><a
@@ -717,7 +662,7 @@
<li>
<p>The <code>a</code> and <code>area</code> elements now have a
<code>media</code> attribute for consistency with the <code>link</code>
- element. It is purely advisory.
+ element.
<li>
<p>The <code>a</code> and <code>area</code> elements have a new attribute
@@ -757,12 +702,13 @@
<code>hidden</code>), <code>select</code>, <code>textarea</code> and
<code>button</code> elements. It provides a declarative way to focus a
form control during page load. Using this feature should enhance the
- user experience as the user can turn it off if he does not like it, for
- instance.
+ user experience as the user can turn it off if the user does not like
+ it, for instance.
<li>
<p>A new <code>placeholder</code> attribute can be specified on the
- <code>input</code> and <code>textarea</code> elements.
+ <code>input</code> and <code>textarea</code> elements. It represents a
+ hint intended to aid the user with data entry.
<li>
<p>The new <code>form</code> attribute for <code>input</code>,
@@ -770,7 +716,12 @@
<code>button</code> and <code>fieldset</code> elements allows for
controls to be associated with a form. I.e. these elements can now be
placed anywhere on a page, not just as descendants of the
- <code>form</code> element.
+ <code>form</code> element.</p>
+
+ <pre class=example><code><label>Email:
+ <input type=email form=x name=email>
+</label>
+<form id=x></form></code></pre>
<li>
<p>The new <code>required</code> attribute applies to <code>input</code>
@@ -877,11 +828,11 @@
content can be checked for spelling or not.
</ul>
- <p>HTML5 also makes all event handler attributes from HTML4 that take the
- form <code>on<var>event-name</var></code> global attributes and adds
- several new event handler attributes for new events it defines, such as
- the <code>play</code> event which is used by the API for the media
- elements, <code>video</code> and <code>audio</code>.
+ <p>HTML5 also makes all event handler attributes from HTML4, which take the
+ form <code>on<var>event-name</var></code>, global attributes and adds
+ several new event handler attributes for new events it defines. E.g. the
+ <code>play</code> event which is used by the API for the media elements
+ (<code>video</code> and <code>audio</code>).
<h3 id=changed-elements><span class=secno>3.3. </span>Changed Elements</h3>
@@ -945,8 +896,8 @@
<h3 id=changed-attributes><span class=secno>3.4. </span>Changed attributes</h3>
- <p>The following attributes are allowed but authors are strongly encouraged
- to not use them and instead use an alternative solution:
+ <p>The following attributes are allowed but authors are discouraged from
+ using them and instead strongly encouraged to use an alternative solution:
<ul>
<li>
@@ -1024,9 +975,9 @@
<li><code>dir</code> has been obsoleted in favor of <code>ul</code>.
</ul>
- <p>Finally the <code>noscript</code> is only conforming in the HTML syntax.
- It is not included in the XML syntax as its usage relies on an HTML
- parser.
+ <p>Finally the <code>noscript</code> element is only conforming in the HTML
+ syntax. It is not included in the XML syntax as its usage relies on an
+ HTML parser.
<h3 id=absent-attributes><span class=secno>3.6. </span>Absent Attributes</h3>
@@ -1215,9 +1166,9 @@
<li>
<p><code>classList</code> is a convenient accessor for
- <code>className</code>. The object it returns exposes methods,
- <code>contains()</code>, <code>add()</code>, <code>remove()</code> and
- <code>toggle()</code>, for manipulating the element's classes. The
+ <code>className</code>. The object it returns, exposes methods
+ (<code>contains()</code>, <code>add()</code>, <code>remove()</code>, and
+ <code>toggle()</code>) for manipulating the element's classes. The
<code>a</code>, <code>area</code> and <code>link</code> elements have a
similar attribute called <code>relList</code> that provides the same
functionality for the <code>rel</code> attribute.
@@ -1923,11 +1874,11 @@
McCathieNevile, Dan Connolly, David Håsäther, Dennis German,
Frank Ellermann, Frank Palinkas, Gordon P. Hemsley, Henri Sivonen, James
Graham, Jens Meiert, Jeremy Keith, Jürgen Jeka, Krijn Hoetmer, Maciej
- Stachowiak, Mark Pilgrim, Martijn Wargers, Martyn Haigh, Masataka Yakura,
- Michael Smith, Olivier Gendrin, Øistein E. Andersen, Philip Taylor,
- Simon Pieters, and Yngve Spjeld Landro for their contributions to this
- document as well as to all the people who have contributed to HTML5 over
- the years for improving the Web!
+ Stachowiak, Marcos Caceres, Mark Pilgrim, Martijn Wargers, Martyn Haigh,
+ Masataka Yakura, Michael Smith, Olivier Gendrin, Øistein E.
+ Andersen, Philip Taylor, Simon Pieters, and Yngve Spjeld Landro for their
+ contributions to this document as well as to all the people who have
+ contributed to HTML5 over the years for improving the Web!
<h2 class=no-num id=references>References</h2>
Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.src.html,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -d -r1.74 -r1.75
--- Overview.src.html 8 Jun 2010 11:43:17 -0000 1.74
+++ Overview.src.html 8 Jun 2010 12:53:42 -0000 1.75
@@ -191,68 +191,12 @@
<h3 id="development-model">Development Model</h3>
<p>The HTML5 specification will not be considered finished before
- there are at least two complete implementations of the specification.
- This is a different approach than previous versions of HTML had. The
- goal is to ensure that the specification is implementable and usable by
- designers and developers once it is finished.</p>
-
-
- <!-- The following <div> is here for Michael(tm) Smith who owes the
- editor one beer in exchange. -->
- <div>
-
- <h3 id="webarch">Impact on Web Architecture</h3>
- <!-- http://lists.w3.org/Archives/Public/www-tag/2008May/0087.html
- modified to match actual contents of W3C HTML5 -->
-
- <p>The following areas / features defined in HTML5 are believed to
- impact the Web architecture:</p>
-
- <ul>
- <li>The use of the DOM as a basis for defining the language.</li>
-
- <li>The concept of browsing contexts.</li>
-
- <li>The distinction between user agent requirements and authoring
- requirements.</li>
-
- <li>The use of imperative definitions rather than abstract definitions
- with the requirement of black-box equivalence in implementations.</li>
-
- <li>The new content model concepts (replacing HTML4's block and
- inline concepts).</li>
-
- <li>The focus on accessibility as a built-in concept for new features
- (such as the <code>hidden</code> attribute, the
- <code>progress</code> element, et cetera) instead of an add-on (like
- the <code>alt</code> attribute).</li>
-
- <li>The focus on defining the semantics in detail (e.g. the outline
- algorithm, replacing the vague semantics in HTML4).</li>
-
- <li>The <code>menu</code> and <code>command</code> elements.</li>
-
- <li>The origin concept.</li>
-
- <li>Offline Web application caches.</li>
-
- <li>The definition of the browsing context "navigation" algorithm and
- the related session history traversal algorithms.</li>
-
- <li>The content-type sniffing and character encoding sniffing.</li>
-
- <li>The very explicit definition of a parser.</li>
-
- <li>The <code>contentEditable</code> feature and the
- <code>UndoManager</code> feature.</li>
-
- <li>The Drag and Drop and Copy and Paste architecture.</li>
+ there are at least two complete implementations of the specification. A
+ test suite will be used to measure completeness of the implementations.
+ This approach differs from previous versions of HTML. The
+ goal is to ensure that the specification is implementable, and usable by
+ authors once it is finished.</p>
- <li>The new sandboxing features for <code>iframe</code>.</li>
- </ul>
-
- </div>
- <!-- This closes the <div> added for Michael(tm) Smith. -->
<h2 id="syntax">Syntax</h2>
@@ -263,9 +207,10 @@
HTML4, such as
<a href="http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.3.6">processing instructions</a>
and
- <a href="http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.3.7">shorthand markup</a>.
- Documents using the HTML syntax are almost always served with the
- <code>text/html</code> media type.</p>
+ <a href="http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.3.7">shorthand markup</a>
+ as these are not supported by most user agents. Documents using the HTML
+ syntax are almost always served with the <code>text/html</code> media
+ type.</p>
<p>HTML5 also defines detailed parsing rules (including "error
handling") for this syntax which are largely compatible with popular
@@ -296,8 +241,9 @@
[<cite><span>XML</span></cite>]</p>
<p>Below is an example document that conforms to the XML syntax of
- HTML5. Note that XML documents must have an XML media type such as
- <code>application/xhtml+xml</code> or <code>application/xml</code>.</p>
+ HTML5. Note that XML documents must be served with an XML media type
+ such as <code>application/xhtml+xml</code> or
+ <code>application/xml</code>.</p>
<pre><code><?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -311,7 +257,7 @@
<h3 id="character-encoding">Character Encoding</h3>
- <p>For the HTML syntax of HTML5 authors have three means of
+ <p>For the HTML syntax of HTML5, authors have three means of
setting the character encoding:</p>
<ul>
@@ -458,7 +404,9 @@
is used for plugin content.</p></li>
<li><p><a href="http://www.w3.org/TR/html5/text-level-semantics.html#the-mark-element"><code>mark</code></a>
- represents a run of marked text.</p></li>
+ represents represents a run of text in one document marked or
+ highlighted for reference purposes, due to its relevance in another
+ context.</p></li>
<li><p><a href="http://www.w3.org/TR/html5/text-level-semantics.html#the-progress-element"><code>progress</code></a>
represents a completion of a task, such as downloading or when
@@ -558,8 +506,8 @@
<ul>
<li><p>The <code>a</code> and <code>area</code> elements now have a
<code>media</code> attribute for consistency with the <code>link</code>
- element. It is purely advisory.
-
+ element.
+
<li><p>The <code>a</code> and <code>area</code> elements have a new
attribute called <code>ping</code> that specifies a space-separated list
of URLs which have to be pinged when the hyperlink is followed. Currently
@@ -592,19 +540,28 @@
<code>input</code> (except when the <code>type</code> attribute is
<code>hidden</code>), <code>select</code>, <code>textarea</code> and
<code>button</code> elements. It provides a declarative way to focus a
- form control during page load. Using this feature should enhance the user
- experience as the user can turn it off if he does not like it, for
- instance.
+ form control during page load. Using this feature should enhance the
+ user experience as the user can turn it off if the user does not like
+ it, for instance.
<li><p>A new <code>placeholder</code> attribute can be specified on
- the <code>input</code> and <code>textarea</code> elements.</p></li>
+ the <code>input</code> and <code>textarea</code> elements. It
+ represents a hint intended to aid the user with data entry.</p></li>
- <li><p>The new <code>form</code> attribute for <code>input</code>,
- <code>output</code>, <code>select</code>, <code>textarea</code>,
- <code>button</code> and <code>fieldset</code> elements allows for
- controls to be associated with a form. I.e. these elements can now be
- placed anywhere on a page, not just as descendants of the
- <code>form</code> element.</p></li>
+ <li>
+ <p>The new <code>form</code> attribute for <code>input</code>,
+ <code>output</code>, <code>select</code>, <code>textarea</code>,
+ <code>button</code> and <code>fieldset</code> elements allows for
+ controls to be associated with a form. I.e. these elements can now be
+ placed anywhere on a page, not just as descendants of the
+ <code>form</code> element.</p>
+
+ <pre class="example"><code><label>Email:
+ <input type=email form=x name=email>
+</label>
+<form id=x></form></code></pre>
+ </div>
+ </li>
<li><p>The new <code>required</code> attribute applies to
<code>input</code> (except when the <code>type</code> attribute is
@@ -702,11 +659,11 @@
</ul>
- <p>HTML5 also makes all event handler attributes from HTML4
- that take the form <code>on<var>event-name</var></code> global
- attributes and adds several new event handler attributes for new events
- it defines, such as the <code>play</code> event which is used by the API
- for the media elements, <code>video</code> and <code>audio</code>.</p>
+ <p>HTML5 also makes all event handler attributes from HTML4, which take
+ the form <code>on<var>event-name</var></code>, global attributes and
+ adds several new event handler attributes for new events
+ it defines. E.g. the <code>play</code> event which is used by the API
+ for the media elements (<code>video</code> and <code>audio</code>).</p>
<h3 id="changed-elements">Changed Elements</h3>
@@ -764,8 +721,9 @@
<h3 id="changed-attributes">Changed attributes</h3>
- <p>The following attributes are allowed but authors are strongly
- encouraged to not use them and instead use an alternative solution:</p>
+ <p>The following attributes are allowed but authors are discouraged from
+ using them and instead strongly encouraged to use an alternative
+ solution:</p>
<ul>
<li><p>The <code>border</code> attribute on <code>img</code>. It is
@@ -843,9 +801,9 @@
<li><code>dir</code> has been obsoleted in favor of <code>ul</code>.
</ul>
- <p>Finally the <code>noscript</code> is only conforming in the HTML syntax.
- It is not included in the XML syntax as its usage relies on an HTML
- parser.</p>
+ <p>Finally the <code>noscript</code> element is only conforming in the
+ HTML syntax. It is not included in the XML syntax as its usage relies on
+ an HTML parser.</p>
<h3 id="absent-attributes">Absent Attributes</h3>
@@ -1034,9 +992,9 @@
document).
<li><p><code>classList</code> is a convenient accessor for
- <code>className</code>. The object it returns exposes methods,
- <code>contains()</code>, <code>add()</code>, <code>remove()</code> and
- <code>toggle()</code>, for manipulating the element's classes. The
+ <code>className</code>. The object it returns, exposes methods
+ (<code>contains()</code>, <code>add()</code>, <code>remove()</code>,
+ and <code>toggle()</code>) for manipulating the element's classes. The
<code>a</code>, <code>area</code> and <code>link</code> elements have
a similar attribute called <code>relList</code> that provides the same
functionality for the <code>rel</code> attribute.
@@ -1585,6 +1543,7 @@
Jürgen Jeka,
Krijn Hoetmer,
Maciej Stachowiak,
+ Marcos Caceres,
Mark Pilgrim,
Martijn Wargers,
Martyn Haigh,
Received on Tuesday, 8 June 2010 12:53:46 UTC