- From: Anne van Kesteren via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 23 Jun 2010 08:20:31 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html4-differences
In directory hutz:/tmp/cvs-serv30384
Modified Files:
Overview.html Overview.src.html
Log Message:
address some comments from Marcos; update references a bit
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.html,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -d -r1.100 -r1.101
--- Overview.html 23 Jun 2010 06:58:39 -0000 1.100
+++ Overview.html 23 Jun 2010 08:20:29 -0000 1.101
@@ -259,15 +259,7 @@
<p><strong>HTML5 is still a draft.</strong> The contents of HTML5, as well
as the contents of this document which depend on HTML5, are still being
discussed on the HTML Working Group and WHATWG mailing lists. The open
- issues include (this list is not exhaustive):
-
- <ul>
- <li>De facto semantic definitions for some formerly presentational
- elements.
-
- <li>Details of accessibility and media-independence features, such as the
- <code>alt</code> and <code>summary</code> attributes.
- </ul>
+ issues are linked from the HTML5 draft.
<h3 id=backwards-compatible><span class=secno>1.2. </span>Backwards
Compatible</h3>
@@ -279,11 +271,12 @@
presentational elements that are better dealt with using CSS.
<p>User agents, however, will always have to support these older elements
- and attributes and this is why the specification clearly separates
- requirements for authors and user agents. This means that authors cannot
- use the <code>isindex</code> or the <code>plaintext</code> element, but
- user agents are required to support them in a way that is compatible with
- how these elements need to behave for compatibility with deployed content.
+ and attributes and this is why the HTML5 specification clearly separates
+ requirements for authors and user agents. For instance, this means that
+ authors cannot use the <code>isindex</code> or the <code>plaintext</code>
+ element, but user agents are required to support them in a way that is
+ compatible with how these elements need to behave for compatibility with
+ deployed content.
<p>Since HTML5 has separate conformance requirements for authors and user
agents there is no longer a need for marking features "deprecated".
@@ -293,8 +286,10 @@
<p>The HTML5 specification will not be considered finished before 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.
+ differs from previous versions of HTML, where the final specification
+ would typically be approved by a committee before being actually
+ implemented. The goal of this change 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>
@@ -735,7 +730,7 @@
<li>
<p>The <code>fieldset</code> element now allows the <code>disabled</code>
- attribute disabling all its contents when specified.
+ attribute. It disables all descendant controls when specified.
<li>
<p>The <code>input</code> element has several new attributes to specify
@@ -784,12 +779,13 @@
<p>The <code>link</code> element has a new attribute called
<code>sizes</code>. It can be used in conjunction with the
<code>icon</code> relationship (set through the <code>rel</code>
- attribute) to indicate the size of the referenced icon.
+ attribute) to indicate the size of the referenced icon. Thus allowing
+ for icons of distinct dimensions.
<li>
<p>The <code>ol</code> element has a new attribute called
- <code>reversed</code> to indicate that the list order is descending when
- present.
+ <code>reversed</code>. When present, it indicates that the list order is
+ descending.
<li>
<p>The <code>iframe</code> element has three new attributes called
@@ -845,8 +841,9 @@
<ul>
<li>
<p>The <code>a</code> element without an <code>href</code> attribute now
- represents a "placeholder link". It can also contain flow content rather
- than being restricted to phrase content.
+ represents a placeholder for where a link otherwise might have been
+ placed. It can also contain flow content rather than being restricted to
+ phrase content.
<li>
<p>The <code>address</code> element is now scoped by the new concept of
@@ -1185,9 +1182,10 @@
href="http://lists.w3.org/Archives/Public/public-html/"><code>public-html@w3.org</code></a>
and <a
href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/"><code>whatwg@whatwg.org</code></a>
- mailing list archives, the <a
+ mailing list archives, and the <a
href="http://blog.whatwg.org/category/weekly-review">This Week in
- HTML5</a> series of blog posts, and the WHATWG <a
+ HTML5</a> series of blog posts. More fundamental rationale is being
+ collected on the WHATWG <a
href="http://wiki.whatwg.org/wiki/Rationale">Rationale</a> wiki page. Many
editorial and minor technical changes are not included in these
changelogs. I.e. implementors are strongly encouraged to follow the
@@ -1892,7 +1890,7 @@
<dt>[<dfn id=ref-css-ui>CSS-UI</dfn>]
<dd><cite><a href="http://www.w3.org/TR/css3-ui/">CSS3 Basic User
- Interface Module</a></cite>, T. Çelik, editor. W3C.
+ Interface Module</a></cite>, T. Çelik. W3C.
<dt>[<dfn id=ref-doctype>DOCTYPE</dfn>]
@@ -1903,7 +1901,7 @@
<dd><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
- Hégaret, A. Le Hors, editors. W3C.
+ Hégaret, A. Le Hors. W3C.
<dt>[<dfn id=ref-html4>HTML4</dfn>]
@@ -1914,14 +1912,14 @@
<dt>[<dfn id=ref-html5>HTML5</dfn>]
<dd><cite><a href="http://www.w3.org/TR/html5/">HTML5</a></cite>, I.
- Hickson, D. Hyatt, editors. W3C.
+ Hickson. W3C.
<dd><cite><a
href="http://www.whatwg.org/specs/web-apps/current-work/">HTML5</a></cite>
- (editor's draft), I. Hickson, editor. WHATWG.
+ (editor's draft), I. Hickson. WHATWG.
<dd><cite><a href="http://www.w3.org/html/wg/html5/">HTML5</a></cite>
- (editors' draft), I. Hickson, D. Hyatt, editors. W3C.
+ (editors' draft), I. Hickson. W3C.
<dt>[<dfn id=ref-psl>PSL</dfn>]
@@ -1932,21 +1930,21 @@
<dd><cite><a
href="http://www.w3.org/TR/css3-selectors/">Selectors</a></cite>, D.
- Glazman, T. Çelik, I. Hickson, editors. W3C.
+ Glazman, T. Çelik, I. Hickson. W3C.
<dt>[<dfn id=ref-xhtml1>XHTML1</dfn>]
<dd><cite><a href="http://www.w3.org/TR/xhtml11">XHTML™ 1.1 -
- Module-based XHTML (Second Edition)</a></cite>, S. McCarron, M. Ishikawa,
- editors. W3C.
+ Module-based XHTML (Second Edition)</a></cite>, S. McCarron, M. Ishikawa.
+ W3C.
<dt>[<dfn id=ref-xml>XML</dfn>]
<dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
(XML) 1.0 (Fifth Edition)</a></cite>, T. Bray, J. Paoli, C.
- Sperberg-McQueen, E. Maler, F. Yergeau, editors. W3C.
+ Sperberg-McQueen, E. Maler, F. Yergeau. W3C.
<dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML 1.0
(Third Edition)</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin,
- H. S. Thompson, editors. W3C.
+ H. S. Thompson. W3C.
</dl>
Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.src.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -d -r1.78 -r1.79
--- Overview.src.html 23 Jun 2010 06:58:40 -0000 1.78
+++ Overview.src.html 23 Jun 2010 08:20:29 -0000 1.79
@@ -155,15 +155,8 @@
<p><strong>HTML5 is still a draft.</strong> The contents of
HTML5, as well as the contents of this document which depend on
HTML5, are still being discussed on the HTML Working Group
- and WHATWG mailing lists. The open issues include (this list is not
- exhaustive):</p>
-
- <ul>
- <li>De facto semantic definitions for some formerly presentational
- elements.</li>
- <li>Details of accessibility and media-independence features, such as
- the <code>alt</code> and <code>summary</code> attributes.</li>
- </ul>
+ and WHATWG mailing lists. The open issues are linked from the HTML5
+ draft.</p>
<h3 id="backwards-compatible">Backwards Compatible</h3>
@@ -176,9 +169,9 @@
CSS.</p>
<p>User agents, however, will always have to support these older
- elements and attributes and this is why the specification clearly
- separates requirements for authors and user agents. This means that
- authors cannot use the <code>isindex</code> or the
+ elements and attributes and this is why the HTML5 specification clearly
+ separates requirements for authors and user agents. For instance, this
+ means that authors cannot use the <code>isindex</code> or the
<code>plaintext</code> element, but user agents are required to support
them in a way that is compatible with how these elements need to behave
for compatibility with deployed content.</p>
@@ -193,9 +186,11 @@
<p>The HTML5 specification will not be considered finished before
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>
+ This approach differs from previous versions of HTML, where the final
+ specification would typically be approved by a committee before being
+ actually implemented. The goal of this change is to ensure that the
+ specification is implementable, and usable by authors once it is
+ finished.</p>
@@ -571,8 +566,8 @@
has to fill in a value in order to submit the form.
<li><p>The <code>fieldset</code> element now allows the
- <code>disabled</code> attribute disabling all its contents when
- specified.
+ <code>disabled</code> attribute. It disables all descendant controls
+ when specified.
<li><p>The <code>input</code> element has several new attributes to
specify constraints: <code>autocomplete</code>, <code>min</code>,
@@ -613,11 +608,12 @@
<li><p>The <code>link</code> element has a new attribute called
<code>sizes</code>. It can be used in conjunction with the
<code>icon</code> relationship (set through the <code>rel</code>
- attribute) to indicate the size of the referenced icon.
+ attribute) to indicate the size of the referenced icon. Thus allowing
+ for icons of distinct dimensions.
<li><p>The <code>ol</code> element has a new attribute called
- <code>reversed</code> to indicate that the list order is
- descending when present.
+ <code>reversed</code>. When present, it indicates that the list order
+ is descending.
<li><p>The <code>iframe</code> element has three new attributes called
<code>sandbox</code>, <code>seamless</code>, and <code>srcdoc</code>
@@ -675,8 +671,9 @@
<ul>
<li><p>The <code>a</code> element without an <code>href</code>
- attribute now represents a "placeholder link". It can also contain
- flow content rather than being restricted to phrase content.</p></li>
+ attribute now represents a placeholder for where a link otherwise
+ might have been placed. It can also contain flow content rather than
+ being restricted to phrase content.</p></li>
<li><p>The <code>address</code> element is now scoped by the new
concept of sectioning.</p></li>
@@ -1010,9 +1007,10 @@
<a href="http://lists.w3.org/Archives/Public/public-html/"><code>public-html@w3.org</code></a>
and
<a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/"><code>whatwg@whatwg.org</code></a>
- mailing list archives, the
+ mailing list archives, and the
<a href="http://blog.whatwg.org/category/weekly-review">This Week in HTML5</a>
- series of blog posts, and the WHATWG
+ series of blog posts. More fundamental rationale is being collected on
+ the WHATWG
<a href="http://wiki.whatwg.org/wiki/Rationale">Rationale</a> wiki page.
Many editorial and minor technical changes are not
included in these changelogs. I.e. implementors are strongly encouraged
@@ -1571,7 +1569,7 @@
<dt>[<dfn id="ref-css-ui">CSS-UI</dfn>]</dt>
<dd><cite><a href="http://www.w3.org/TR/css3-ui/">CSS3 Basic User
- Interface Module</a></cite>, T. Çelik, editor. W3C.</dd>
+ Interface Module</a></cite>, T. Çelik. W3C.</dd>
<dt>[<dfn id="ref-doctype">DOCTYPE</dfn>]</dt>
@@ -1582,7 +1580,7 @@
<dd><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
- Hégaret, A. Le Hors, editors. W3C.</dd>
+ Hégaret, A. Le Hors. W3C.</dd>
<dt>[<dfn id="ref-html4">HTML4</dfn>]</dt>
@@ -1592,13 +1590,13 @@
<dt>[<dfn id="ref-html5">HTML5</dfn>]</dt>
<dd><cite><a href="http://www.w3.org/TR/html5/">HTML5</a></cite>,
- I. Hickson, D. Hyatt, editors. W3C.</dd>
+ I. Hickson. W3C.</dd>
<dd><cite><a href="http://www.whatwg.org/specs/web-apps/current-work/">HTML5</a></cite>
- (editor's draft), I. Hickson, editor. WHATWG.</dd>
+ (editor's draft), I. Hickson. WHATWG.</dd>
<dd><cite><a href="http://www.w3.org/html/wg/html5/">HTML5</a></cite>
- (editors' draft), I. Hickson, D. Hyatt, editors. W3C.</dd>
+ (editors' draft), I. Hickson. W3C.</dd>
<dt>[<dfn id="ref-psl">PSL</dfn>]</dt>
@@ -1608,23 +1606,23 @@
<dt>[<dfn id="ref-selectors">SELECTORS</dfn>]</dt>
<dd><cite><a href="http://www.w3.org/TR/css3-selectors/">Selectors</a></cite>,
- D. Glazman, T. Çelik, I. Hickson, editors. W3C.</dd>
+ D. Glazman, T. Çelik, I. Hickson. W3C.</dd>
<dt>[<dfn id="ref-xhtml1">XHTML1</dfn>]</dt>
<dd><cite><a href="http://www.w3.org/TR/xhtml11">XHTML™
1.1 - Module-based XHTML (Second Edition)</a></cite>, S. McCarron,
- M. Ishikawa, editors. W3C.</dd>
+ M. Ishikawa. W3C.</dd>
<dt>[<dfn id="ref-xml">XML</dfn>]</dt>
<dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
(XML) 1.0 (Fifth Edition)</a></cite>, T. Bray, J. Paoli, C.
- Sperberg-McQueen, E. Maler, F. Yergeau, editors. W3C.</dd>
+ Sperberg-McQueen, E. Maler, F. Yergeau. W3C.</dd>
<dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML 1.0
(Third Edition)</a></cite>, T. Bray, D. Hollander, A. Layman, R.
- Tobin, H. S. Thompson, editors. W3C.</dd>
+ Tobin, H. S. Thompson. W3C.</dd>
</dl>
</body>
</html>
Received on Wednesday, 23 June 2010 08:20:33 UTC