- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Aug 2011 00:59:15 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv26656
Modified Files:
Overview.html elements.html spec.html spec.preprocessed.html
Log Message:
Explain requirements (whatwg r6479)
[updated by splitter]
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/Overview.html,v
retrieving revision 1.1572
retrieving revision 1.1573
diff -u -d -r1.1572 -r1.1573
--- Overview.html 16 Aug 2011 06:57:09 -0000 1.1572
+++ Overview.html 17 Aug 2011 00:59:04 -0000 1.1573
@@ -340,7 +340,7 @@
<h1>HTML5: Edition for Web Authors</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-16-august-2011">Editor's Draft 16 August 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-17-august-2011">Editor's Draft 17 August 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5-author/">http://www.w3.org/TR/html5-author/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -362,7 +362,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5180.</p>
+ This is revision 1.5181.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -513,7 +513,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 16 August 2011 Editor's Draft.
+ This specification is the 17 August 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.1702
retrieving revision 1.1703
diff -u -d -r1.1702 -r1.1703
--- spec.html 16 Aug 2011 06:57:09 -0000 1.1702
+++ spec.html 17 Aug 2011 00:59:05 -0000 1.1703
@@ -341,7 +341,7 @@
<h1>HTML5: Edition for Web Authors</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-16-august-2011">Editor's Draft 16 August 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-17-august-2011">Editor's Draft 17 August 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5-author/">http://www.w3.org/TR/html5-author/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -363,7 +363,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5180.</p>
+ This is revision 1.5181.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -514,7 +514,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 16 August 2011 Editor's Draft.
+ This specification is the 17 August 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -3402,11 +3402,49 @@
(by this specification) to have certain meanings (semantics). For
example, the <code><a href="#the-ol-element" id="ol">ol</a></code> element represents an ordered list, and
the <code title="attr-lang"><a href="#attr-lang" id="lang_0">lang</a></code> attribute represents the
- language of the content.</p><p>Authors must not use elements, attributes, or attribute values
- for purposes other than their appropriate intended semantic
- purpose. Authors must not use elements, attributes, or attribute
- values that are not permitted by this specification or <a href="http://dev.w3.org/html5/spec/infrastructure.html#other-applicable-specifications" class="full-spec-link" title='Read about this "other applicable specifications" reference in the full HTML5 spec.'>other
- applicable specifications</a>.</p><div class="example">
+ language of the content.</p><p>These definitions allow HTML processors, such as Web browsers or
+ search engines, to present and use documents and applications in a
+ wide variety of contexts that the author might not have
+ considered.</p><div class="example">
+
+ <p>As a simple example, consider a Web page written by an author
+ who only considered desktop computer Web browsers. Because HTML
+ conveys <em>meaning</em>, rather than presentation, the same page
+ can also be used by a small browser on a mobile phone, without any
+ change to the page. Instead of headings being in large letters as
+ on the desktop, for example, the browser on the mobile phone might
+ use the same size text for the whole the page, but with the
+ headings in bold.</p>
+
+ <p>But it goes further than just differences in screen size: the
+ same page could equally be used by a blind user using a browser
+ based around speech synthesis, which instead of displaying the page
+ on a screen, reads the page to the user, e.g. using headphones.
+ Instead of large text for the headings, the speech browser might
+ use a different volume or a slower voice.</p>
+
+ <p>That's not all, either. Since the browsers know which parts of
+ the page are the headings, they can create a document outline that
+ the user can use to quickly navigate around the document, using
+ keys for "jump to next heading" or "jump to previous heading". Such
+ features are especially common with speech browsers, where users
+ would otherwise find quickly navigating a page quite difficult.</p>
+
+ <p>Even beyond browsers, software can make use of this information.
+ Search engines can use the headings to more effectively index a
+ page, or to provide quick links to subsections of the page from
+ their results. Tools can use the headings to create a table of
+ contents (that is in fact how this very specification's table of
+ contents is generated).</p>
+
+ <p>This example has focused on headings, but the same principle
+ applies to all of the semantics in HTML.</p>
+
+ </div><p>Authors must not use elements, attributes, or attribute values
+ for purposes other than their appropriate intended semantic purpose,
+ as doing so prevents software from correctly processing the
+ page.</p><div class="example">
+
<p>For example, the following document is non-conforming, despite
being syntactically correct:</p>
@@ -3427,8 +3465,15 @@
</html></pre>
<p>...because the data placed in the cells is clearly not tabular
- data (and the <code><a href="#the-cite-element" id="cite_2">cite</a></code> element mis-used). A corrected
- version of this document might be:</p>
+ data (and the <code><a href="#the-cite-element" id="cite_2">cite</a></code> element mis-used). This would make
+ software that relies on these semantics fail: for example, a speech
+ browser that allowed a blind user to navigate tables in the
+ document would report the quote above as a table, confusing the
+ user; similarly, a tool that extracted titles of works from pages
+ would extract "Ernest" as the title of a work, even though it's
+ actually a person's name, not a title.</p>
+
+ <p>A corrected version of this document might be:</p>
<pre><!DOCTYPE HTML>
<html lang="en-GB">
@@ -3444,6 +3489,8 @@
</body>
</html></pre>
+ </div><div class="example">
+
<p>This next document fragment, intended to represent the heading
of a corporate site, is similarly non-conforming because the second
line is not intended to be a heading of a subsection, but merely a
@@ -3465,6 +3512,11 @@
</hgroup>
...</pre>
+ </div><p>Authors must not use elements, attributes, or attribute values
+ that are not permitted by this specification or <a href="http://dev.w3.org/html5/spec/infrastructure.html#other-applicable-specifications" class="full-spec-link" title='Read about this "other applicable specifications" reference in the full HTML5 spec.'>other
+ applicable specifications</a>, as doing so makes it significantly
+ harder for the language to be extended in the future.</p><div class="example">
+
<p>In the next example, there is a non-conforming attribute value
("carpet") and a non-conforming attribute ("texture"), which
is not permitted by this specification:</p>
Index: spec.preprocessed.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.preprocessed.html,v
retrieving revision 1.554
retrieving revision 1.555
diff -u -d -r1.554 -r1.555
--- spec.preprocessed.html 16 Aug 2011 06:57:14 -0000 1.554
+++ spec.preprocessed.html 17 Aug 2011 00:59:12 -0000 1.555
@@ -357,7 +357,7 @@
<h1>HTML5: Edition for Web Authors</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-16-august-2011">Editor's Draft 16 August 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-17-august-2011">Editor's Draft 17 August 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5-author/">http://www.w3.org/TR/html5-author/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -379,7 +379,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5180.</p>
+ This is revision 1.5181.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -532,7 +532,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 16 August 2011 Editor's Draft.
+ This specification is the 17 August 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -2970,11 +2970,49 @@
(by this specification) to have certain meanings (semantics). For
example, the <code><a href="#the-ol-element">ol</a></code> element represents an ordered list, and
the <code title="attr-lang"><a href="#attr-lang">lang</a></code> attribute represents the
- language of the content.</p><p>Authors must not use elements, attributes, or attribute values
- for purposes other than their appropriate intended semantic
- purpose. Authors must not use elements, attributes, or attribute
- values that are not permitted by this specification or <a href="#other-applicable-specifications">other
- applicable specifications</a>.</p><div class="example">
+ language of the content.</p><p>These definitions allow HTML processors, such as Web browsers or
+ search engines, to present and use documents and applications in a
+ wide variety of contexts that the author might not have
+ considered.</p><div class="example">
+
+ <p>As a simple example, consider a Web page written by an author
+ who only considered desktop computer Web browsers. Because HTML
+ conveys <em>meaning</em>, rather than presentation, the same page
+ can also be used by a small browser on a mobile phone, without any
+ change to the page. Instead of headings being in large letters as
+ on the desktop, for example, the browser on the mobile phone might
+ use the same size text for the whole the page, but with the
+ headings in bold.</p>
+
+ <p>But it goes further than just differences in screen size: the
+ same page could equally be used by a blind user using a browser
+ based around speech synthesis, which instead of displaying the page
+ on a screen, reads the page to the user, e.g. using headphones.
+ Instead of large text for the headings, the speech browser might
+ use a different volume or a slower voice.</p>
+
+ <p>That's not all, either. Since the browsers know which parts of
+ the page are the headings, they can create a document outline that
+ the user can use to quickly navigate around the document, using
+ keys for "jump to next heading" or "jump to previous heading". Such
+ features are especially common with speech browsers, where users
+ would otherwise find quickly navigating a page quite difficult.</p>
+
+ <p>Even beyond browsers, software can make use of this information.
+ Search engines can use the headings to more effectively index a
+ page, or to provide quick links to subsections of the page from
+ their results. Tools can use the headings to create a table of
+ contents (that is in fact how this very specification's table of
+ contents is generated).</p>
+
+ <p>This example has focused on headings, but the same principle
+ applies to all of the semantics in HTML.</p>
+
+ </div><p>Authors must not use elements, attributes, or attribute values
+ for purposes other than their appropriate intended semantic purpose,
+ as doing so prevents software from correctly processing the
+ page.</p><div class="example">
+
<p>For example, the following document is non-conforming, despite
being syntactically correct:</p>
@@ -2995,8 +3033,15 @@
</html></pre>
<p>...because the data placed in the cells is clearly not tabular
- data (and the <code><a href="#the-cite-element">cite</a></code> element mis-used). A corrected
- version of this document might be:</p>
+ data (and the <code><a href="#the-cite-element">cite</a></code> element mis-used). This would make
+ software that relies on these semantics fail: for example, a speech
+ browser that allowed a blind user to navigate tables in the
+ document would report the quote above as a table, confusing the
+ user; similarly, a tool that extracted titles of works from pages
+ would extract "Ernest" as the title of a work, even though it's
+ actually a person's name, not a title.</p>
+
+ <p>A corrected version of this document might be:</p>
<pre><!DOCTYPE HTML>
<html lang="en-GB">
@@ -3012,6 +3057,8 @@
</body>
</html></pre>
+ </div><div class="example">
+
<p>This next document fragment, intended to represent the heading
of a corporate site, is similarly non-conforming because the second
line is not intended to be a heading of a subsection, but merely a
@@ -3033,6 +3080,11 @@
</hgroup>
...</pre>
+ </div><p>Authors must not use elements, attributes, or attribute values
+ that are not permitted by this specification or <a href="#other-applicable-specifications">other
+ applicable specifications</a>, as doing so makes it significantly
+ harder for the language to be extended in the future.</p><div class="example">
+
<p>In the next example, there is a non-conforming attribute value
("carpet") and a non-conforming attribute ("texture"), which
is not permitted by this specification:</p>
Index: elements.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/elements.html,v
retrieving revision 1.601
retrieving revision 1.602
diff -u -d -r1.601 -r1.602
--- elements.html 15 Aug 2011 20:59:32 -0000 1.601
+++ elements.html 17 Aug 2011 00:59:04 -0000 1.602
@@ -354,11 +354,49 @@
(by this specification) to have certain meanings (semantics). For
example, the <code><a href="the-ol-element.html#the-ol-element" id="ol">ol</a></code> element represents an ordered list, and
the <code title="attr-lang"><a href="global-attributes.html#attr-lang" id="lang_0">lang</a></code> attribute represents the
- language of the content.<p>Authors must not use elements, attributes, or attribute values
- for purposes other than their appropriate intended semantic
- purpose. Authors must not use elements, attributes, or attribute
- values that are not permitted by this specification or <a class="full-spec-link" href="http://dev.w3.org/html5/spec/infrastructure.html#other-applicable-specifications" title='Read about this "other applicable specifications" reference in the full HTML5 spec.'>other
- applicable specifications</a>.<div class="example">
+ language of the content.<p>These definitions allow HTML processors, such as Web browsers or
+ search engines, to present and use documents and applications in a
+ wide variety of contexts that the author might not have
+ considered.<div class="example">
+
+ <p>As a simple example, consider a Web page written by an author
+ who only considered desktop computer Web browsers. Because HTML
+ conveys <em>meaning</em>, rather than presentation, the same page
+ can also be used by a small browser on a mobile phone, without any
+ change to the page. Instead of headings being in large letters as
+ on the desktop, for example, the browser on the mobile phone might
+ use the same size text for the whole the page, but with the
+ headings in bold.</p>
+
+ <p>But it goes further than just differences in screen size: the
+ same page could equally be used by a blind user using a browser
+ based around speech synthesis, which instead of displaying the page
+ on a screen, reads the page to the user, e.g. using headphones.
+ Instead of large text for the headings, the speech browser might
+ use a different volume or a slower voice.</p>
+
+ <p>That's not all, either. Since the browsers know which parts of
+ the page are the headings, they can create a document outline that
+ the user can use to quickly navigate around the document, using
+ keys for "jump to next heading" or "jump to previous heading". Such
+ features are especially common with speech browsers, where users
+ would otherwise find quickly navigating a page quite difficult.</p>
+
+ <p>Even beyond browsers, software can make use of this information.
+ Search engines can use the headings to more effectively index a
+ page, or to provide quick links to subsections of the page from
+ their results. Tools can use the headings to create a table of
+ contents (that is in fact how this very specification's table of
+ contents is generated).</p>
+
+ <p>This example has focused on headings, but the same principle
+ applies to all of the semantics in HTML.</p>
+
+ </div><p>Authors must not use elements, attributes, or attribute values
+ for purposes other than their appropriate intended semantic purpose,
+ as doing so prevents software from correctly processing the
+ page.<div class="example">
+
<p>For example, the following document is non-conforming, despite
being syntactically correct:</p>
@@ -379,8 +417,15 @@
</html></pre>
<p>...because the data placed in the cells is clearly not tabular
- data (and the <code><a href="the-cite-element.html#the-cite-element" id="cite_2">cite</a></code> element mis-used). A corrected
- version of this document might be:</p>
+ data (and the <code><a href="the-cite-element.html#the-cite-element" id="cite_2">cite</a></code> element mis-used). This would make
+ software that relies on these semantics fail: for example, a speech
+ browser that allowed a blind user to navigate tables in the
+ document would report the quote above as a table, confusing the
+ user; similarly, a tool that extracted titles of works from pages
+ would extract "Ernest" as the title of a work, even though it's
+ actually a person's name, not a title.</p>
+
+ <p>A corrected version of this document might be:</p>
<pre><!DOCTYPE HTML>
<html lang="en-GB">
@@ -396,6 +441,8 @@
</body>
</html></pre>
+ </div><div class="example">
+
<p>This next document fragment, intended to represent the heading
of a corporate site, is similarly non-conforming because the second
line is not intended to be a heading of a subsection, but merely a
@@ -417,6 +464,11 @@
</hgroup>
...</pre>
+ </div><p>Authors must not use elements, attributes, or attribute values
+ that are not permitted by this specification or <a class="full-spec-link" href="http://dev.w3.org/html5/spec/infrastructure.html#other-applicable-specifications" title='Read about this "other applicable specifications" reference in the full HTML5 spec.'>other
+ applicable specifications</a>, as doing so makes it significantly
+ harder for the language to be extended in the future.<div class="example">
+
<p>In the next example, there is a non-conforming attribute value
("carpet") and a non-conforming attribute ("texture"), which
is not permitted by this specification:</p>
Received on Wednesday, 17 August 2011 00:59:17 UTC