[html5] r7665 - [e] (0) Cleanup Affected topics: HTML
whatwg at whatwg.org
whatwg at whatwg.org
Mon Jan 28 17:07:39 PST 2013
Author: ianh
Date: 2013-01-28 17:07:38 -0800 (Mon, 28 Jan 2013)
New Revision: 7665
Modified:
complete.html
index
source
Log:
[e] (0) Cleanup
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2013-01-29 01:05:08 UTC (rev 7664)
+++ complete.html 2013-01-29 01:07:38 UTC (rev 7665)
@@ -16953,34 +16953,27 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-article-element>article</a></code> element <a href=#represents>represents</a> a
- complete, or self-contained, composition in a document, page, application, or site
- and that is, in principle, independently distributable or reusable,
- e.g. in syndication. This could be a forum post, a magazine or
- newspaper article, a blog entry, a user-submitted comment, an
- interactive widget or gadget, or any other independent item of
- content.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-article-element>article</a></code> element <a href=#represents>represents</a> a complete, or self-contained,
+ composition in a document, page, application, or site and that is, in principle, independently
+ distributable or reusable, e.g. in syndication. This could be a forum post, a magazine or
+ newspaper article, a blog entry, a user-submitted comment, an interactive widget or gadget, or any
+ other independent item of content.</p>
- <p>When <code><a href=#the-article-element>article</a></code> elements are nested, the inner
- <code><a href=#the-article-element>article</a></code> elements represent articles that are in
- principle related to the contents of the outer article. For
- instance, a blog entry on a site that accepts user-submitted
- comments could represent the comments as <code><a href=#the-article-element>article</a></code>
- elements nested within the <code><a href=#the-article-element>article</a></code> element for the blog
+ <p>When <code><a href=#the-article-element>article</a></code> elements are nested, the inner <code><a href=#the-article-element>article</a></code> elements
+ represent articles that are in principle related to the contents of the outer article. For
+ instance, a blog entry on a site that accepts user-submitted comments could represent the comments
+ as <code><a href=#the-article-element>article</a></code> elements nested within the <code><a href=#the-article-element>article</a></code> element for the blog
entry.</p>
- <p>Author information associated with an <code><a href=#the-article-element>article</a></code>
- element (q.v. the <code><a href=#the-address-element>address</a></code> element) does not apply to
- nested <code><a href=#the-article-element>article</a></code> elements.</p>
+ <p>Author information associated with an <code><a href=#the-article-element>article</a></code> element (q.v. the
+ <code><a href=#the-address-element>address</a></code> element) does not apply to nested <code><a href=#the-article-element>article</a></code> elements.</p>
- <p class=note>When used specifically with content to be
- redistributed in syndication, the <code><a href=#the-article-element>article</a></code> element is
- similar in purpose to the <code title="">entry</code> element in
+ <p class=note>When used specifically with content to be redistributed in syndication, the
+ <code><a href=#the-article-element>article</a></code> element is similar in purpose to the <code title="">entry</code> element in
Atom. <a href=#refsATOM>[ATOM]</a>
- <p class=note>The schema.org microdata vocabulary can be used to
- provide the publication date for an <code><a href=#the-article-element>article</a></code>
- element, using one of the CreativeWork subtypes.</p>
+ <p class=note>The schema.org microdata vocabulary can be used to provide the publication date
+ for an <code><a href=#the-article-element>article</a></code> element, using one of the CreativeWork subtypes.</p>
<p>When the main content of the page (i.e. excluding footers, headers, navigation blocks, and
sidebars) is all one single self-contained composition, that content may be marked with an
@@ -16989,8 +16982,8 @@
<div class=example id=article-example>
- <p>This example shows a blog post using the <code><a href=#the-article-element>article</a></code>
- element, with some schema.org annotations:</p>
+ <p>This example shows a blog post using the <code><a href=#the-article-element>article</a></code> element, with some schema.org
+ annotations:</p>
<pre><article itemscope itemtype="http://schema.org/BlogPosting">
<header>
@@ -17042,12 +17035,10 @@
</section>
</article></pre>
- <p>Notice the use of <code><a href=#the-footer-element>footer</a></code> to give the information
- for each comment (such as who wrote it and when): the
- <code><a href=#the-footer-element>footer</a></code> element <em>can</em> appear at the start of its
- section when appropriate, such as in this case. (Using
- <code><a href=#the-header-element>header</a></code> in this case wouldn't be wrong either; it's
- mostly a matter of authoring preference.)</p>
+ <p>Notice the use of <code><a href=#the-footer-element>footer</a></code> to give the information for each comment (such as who
+ wrote it and when): the <code><a href=#the-footer-element>footer</a></code> element <em>can</em> appear at the start of its
+ section when appropriate, such as in this case. (Using <code><a href=#the-header-element>header</a></code> in this case wouldn't
+ be wrong either; it's mostly a matter of authoring preference.)</p>
</div>
@@ -17067,34 +17058,28 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-section-element>section</a></code> element <a href=#represents>represents</a> a
- generic section of a document or application. A section, in this
- context, is a thematic grouping of content, typically with a
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-section-element>section</a></code> element <a href=#represents>represents</a> a generic section of a document or
+ application. A section, in this context, is a thematic grouping of content, typically with a
heading.</p>
- <p class=example>Examples of sections would be chapters, the
- various tabbed pages in a tabbed dialog box, or the numbered
- sections of a thesis. A Web site's home page could be split into
- sections for an introduction, news items, and contact
- information.</p>
+ <p class=example>Examples of sections would be chapters, the various tabbed pages in a tabbed
+ dialog box, or the numbered sections of a thesis. A Web site's home page could be split into
+ sections for an introduction, news items, and contact information.</p>
- <p class=note>Authors are encouraged to use the
- <code><a href=#the-article-element>article</a></code> element instead of the <code><a href=#the-section-element>section</a></code>
- element when it would make sense to syndicate the contents of the
+ <p class=note>Authors are encouraged to use the <code><a href=#the-article-element>article</a></code> element instead of the
+ <code><a href=#the-section-element>section</a></code> element when it would make sense to syndicate the contents of the
element.</p>
- <p class=note id=use-div-for-wrappers>The <code><a href=#the-section-element>section</a></code>
- element is not a generic container element. When an element is
- needed only for styling purposes or as a convenience for scripting,
- authors are encouraged to use the <code><a href=#the-div-element>div</a></code> element instead.
- A general rule is that the <code><a href=#the-section-element>section</a></code> element is
- appropriate only if the element's contents would be listed
- explicitly in the document's <a href=#outline>outline</a>.</p>
+ <p class=note id=use-div-for-wrappers>The <code><a href=#the-section-element>section</a></code> element is not a generic
+ container element. When an element is needed only for styling purposes or as a convenience for
+ scripting, authors are encouraged to use the <code><a href=#the-div-element>div</a></code> element instead. A general rule is
+ that the <code><a href=#the-section-element>section</a></code> element is appropriate only if the element's contents would be
+ listed explicitly in the document's <a href=#outline>outline</a>.</p>
<div class=example>
- <p>In the following example, we see an article (part of a larger
- Web page) about apples, containing two short sections.</p>
+ <p>In the following example, we see an article (part of a larger Web page) about apples,
+ containing two short sections.</p>
<pre><article>
<hgroup>
@@ -17114,10 +17099,9 @@
</section>
</article></pre>
- <p>Notice how the use of <code><a href=#the-section-element>section</a></code> means that the author
- can use <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> elements throughout, without having to
- worry about whether a particular section is at the top level, the
- second level, the third level, and so on.</p>
+ <p>Notice how the use of <code><a href=#the-section-element>section</a></code> means that the author can use <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>
+ elements throughout, without having to worry about whether a particular section is at the top
+ level, the second level, the third level, and so on.</p>
</div>
@@ -17175,11 +17159,10 @@
<div class=example>
- <p>In this example, a book author has marked up some sections as
- chapters and some as appendices, and uses CSS to style the headers
- in these two classes of section differently. The whole book is
- wrapped in an <code><a href=#the-article-element>article</a></code> element as part of an even
- larger document containing other books.</p>
+ <p>In this example, a book author has marked up some sections as chapters and some as appendices,
+ and uses CSS to style the headers in these two classes of section differently. The whole book is
+ wrapped in an <code><a href=#the-article-element>article</a></code> element as part of an even larger document containing other
+ books.</p>
<pre><article class="book">
<style>
@@ -17238,31 +17221,25 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-nav-element>nav</a></code> element <a href=#represents>represents</a> a section of
- a page that links to other pages or to parts within the page: a
- section with navigation links.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-nav-element>nav</a></code> element <a href=#represents>represents</a> a section of a page that links to other
+ pages or to parts within the page: a section with navigation links.</p>
- <p class=note>Not all groups of links on a page need to be in a
- <code><a href=#the-nav-element>nav</a></code> element — the element is primarily intended
- for sections that consist of major navigation blocks. In particular,
- it is common for footers to have a short list of links to various
- pages of a site, such as the terms of service, the home page, and a
- copyright page. The <code><a href=#the-footer-element>footer</a></code> element alone is sufficient
- for such cases; while a <code><a href=#the-nav-element>nav</a></code> element can be used in such
- cases, it is usually unnecessary.</p>
+ <p class=note>Not all groups of links on a page need to be in a <code><a href=#the-nav-element>nav</a></code> element —
+ the element is primarily intended for sections that consist of major navigation blocks. In
+ particular, it is common for footers to have a short list of links to various pages of a site,
+ such as the terms of service, the home page, and a copyright page. The <code><a href=#the-footer-element>footer</a></code> element
+ alone is sufficient for such cases; while a <code><a href=#the-nav-element>nav</a></code> element can be used in such cases, it
+ is usually unnecessary.</p>
- <p class=note>User agents (such as screen readers) that are
- targeted at users who can benefit from navigation information being
- omitted in the initial rendering, or who can benefit from navigation
- information being immediately available, can use this element as a
- way to determine what content on the page to initially skip or
- provide on request (or both).</p>
+ <p class=note>User agents (such as screen readers) that are targeted at users who can benefit
+ from navigation information being omitted in the initial rendering, or who can benefit from
+ navigation information being immediately available, can use this element as a way to determine
+ what content on the page to initially skip or provide on request (or both).</p>
<div class=example>
- <p>In the following example, the page has several places where
- links are present, but only one of those places is considered a
- navigation section.</p>
+ <p>In the following example, the page has several places where links are present, but only one of
+ those places is considered a navigation section.</p>
<pre><body itemscope itemtype="http://schema.org/Blog">
<header>
@@ -17306,21 +17283,19 @@
</footer>
</body></pre>
- <p>Notice the <code><a href=#the-div-element>div</a></code> elements being used to wrap all the
- contents of the page other than the header and footer, and all the
- contents of the blog entry other than its header and footer.</p>
+ <p>Notice the <code><a href=#the-div-element>div</a></code> elements being used to wrap all the contents of the page other
+ than the header and footer, and all the contents of the blog entry other than its header and
+ footer.</p>
- <p>You can also see microdata annotations in the above example that
- use the schema.org vocabulary to provide the publication date and
- other metadata about the blog post.</p>
+ <p>You can also see microdata annotations in the above example that use the schema.org vocabulary
+ to provide the publication date and other metadata about the blog post.</p>
</div>
<div class=example>
- <p>In the following example, there are two <code><a href=#the-nav-element>nav</a></code>
- elements, one for primary navigation around the site, and one for
- secondary navigation around the page itself.</p>
+ <p>In the following example, there are two <code><a href=#the-nav-element>nav</a></code> elements, one for primary navigation
+ around the site, and one for secondary navigation around the page itself.</p>
<pre><body>
<h1>The Wiki Center Of Exampland</h1>
@@ -17367,9 +17342,8 @@
<div class=example>
- <p>A <code><a href=#the-nav-element>nav</a></code> element doesn't have to contain a list, it
- can contain other kinds of content as well. In this navigation
- block, links are provided in prose:</p>
+ <p>A <code><a href=#the-nav-element>nav</a></code> element doesn't have to contain a list, it can contain other kinds of
+ content as well. In this navigation block, links are provided in prose:</p>
<pre><nav>
<h1>Navigation</h1>
@@ -17406,26 +17380,22 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-aside-element>aside</a></code> element <a href=#represents>represents</a> a section
- of a page that consists of content that is tangentially related to
- the content around the <code><a href=#the-aside-element>aside</a></code> element, and which could
- be considered separate from that content. Such sections are often
- represented as sidebars in printed typography.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-aside-element>aside</a></code> element <a href=#represents>represents</a> a section of a page that consists of
+ content that is tangentially related to the content around the <code><a href=#the-aside-element>aside</a></code> element, and
+ which could be considered separate from that content. Such sections are often represented as
+ sidebars in printed typography.</p>
- <p>The element can be used for typographical effects like pull
- quotes or sidebars, for advertising, for groups of <code><a href=#the-nav-element>nav</a></code>
- elements, and for other content that is considered separate from the
- main content of the page.</p>
+ <p>The element can be used for typographical effects like pull quotes or sidebars, for
+ advertising, for groups of <code><a href=#the-nav-element>nav</a></code> elements, and for other content that is considered
+ separate from the main content of the page.</p>
- <p class=note>It's not appropriate to use the <code><a href=#the-aside-element>aside</a></code>
- element just for parentheticals, since those are part of the main
- flow of the document.</p>
+ <p class=note>It's not appropriate to use the <code><a href=#the-aside-element>aside</a></code> element just for
+ parentheticals, since those are part of the main flow of the document.</p>
<div class=example>
- <p>The following example shows how an aside is used to mark up
- background material on Switzerland in a much longer news story on
- Europe.</p>
+ <p>The following example shows how an aside is used to mark up background material on Switzerland
+ in a much longer news story on Europe.</p>
<pre><aside>
<h1>Switzerland</h1>
@@ -17438,8 +17408,8 @@
<div class=example>
- <p>The following example shows how an aside is used to mark up
- a pull quote in a longer article.</p>
+ <p>The following example shows how an aside is used to mark up a pull quote in a longer
+ article.</p>
<pre>...
@@ -17464,8 +17434,8 @@
<div class=example>
- <p>The following extract shows how <code><a href=#the-aside-element>aside</a></code> can be used
- for blogrolls and other side content on a blog:</p>
+ <p>The following extract shows how <code><a href=#the-aside-element>aside</a></code> can be used for blogrolls and other side
+ content on a blog:</p>
<pre><body>
<header>
@@ -17556,22 +17526,19 @@
<dd>
<pre class=idl>interface <dfn id=htmlheadingelement>HTMLHeadingElement</dfn> : <a href=#htmlelement>HTMLElement</a> {};</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>These elements <a href=#represents title=represents>represent</a> headings
- for their sections.</p>
+ </dl><!--TOPIC:HTML--><p>These elements <a href=#represents title=represents>represent</a> headings for their sections.</p>
- <p>The semantics and meaning of these elements are defined in the
- section on <a href=#headings-and-sections>headings and sections</a>.</p>
+ <p>The semantics and meaning of these elements are defined in the section on <a href=#headings-and-sections>headings and
+ sections</a>.</p>
- <p>These elements have a <dfn id=rank>rank</dfn> given by the number in
- their name. The <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element is said to have the highest
- rank, the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element has the lowest rank, and two
+ <p>These elements have a <dfn id=rank>rank</dfn> given by the number in their name. The <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>
+ element is said to have the highest rank, the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element has the lowest rank, and two
elements with the same name have equal rank.</p>
<div class=example>
- <p>As far as their respective document outlines (their heading and
- section structures) are concerned, these two snippets are
- semantically equivalent:</p>
+ <p>As far as their respective document outlines (their heading and section structures) are
+ concerned, these two snippets are semantically equivalent:</p>
<pre><body>
<h1>Let's call it a draw(ing surface)</h1>
@@ -17601,9 +17568,9 @@
</section>
</body></pre>
- <p>Authors might prefer the former style for its terseness, or the
- latter style for its convenience in the face of heavy editing;
- which is best is purely an issue of preferred authoring style.</p>
+ <p>Authors might prefer the former style for its terseness, or the latter style for its
+ convenience in the face of heavy editing; which is best is purely an issue of preferred authoring
+ style.</p>
</div>
@@ -17624,24 +17591,20 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-hgroup-element>hgroup</a></code> element <a href=#represents>represents</a> the
- heading of a section. The element is used to group a set of
- <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> elements when the heading has
- multiple levels, such as subheadings, alternative titles, or
- taglines.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-hgroup-element>hgroup</a></code> element <a href=#represents>represents</a> the heading of a section. The element
+ is used to group a set of <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> elements when the heading has
+ multiple levels, such as subheadings, alternative titles, or taglines.</p>
- <p>Other elements of <a href=#heading-content>heading content</a> in the
- <code><a href=#the-hgroup-element>hgroup</a></code> element indicate subheadings or subtitles.</p>
+ <p>Other elements of <a href=#heading-content>heading content</a> in the <code><a href=#the-hgroup-element>hgroup</a></code> element indicate
+ subheadings or subtitles.</p>
- <p>The <a href=#rank>rank</a> of an <code><a href=#the-hgroup-element>hgroup</a></code> element is the
- rank of the highest-ranked <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code>
- element descendant of the <code><a href=#the-hgroup-element>hgroup</a></code> element, if there are
- any such elements, or otherwise the same as for an <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>
- element (the highest rank).</p>
+ <p>The <a href=#rank>rank</a> of an <code><a href=#the-hgroup-element>hgroup</a></code> element is the rank of the highest-ranked
+ <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element descendant of the <code><a href=#the-hgroup-element>hgroup</a></code> element, if
+ there are any such elements, or otherwise the same as for an <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element (the highest
+ rank).</p>
- <p>The section on <a href=#headings-and-sections>headings and sections</a>
- defines how <code><a href=#the-hgroup-element>hgroup</a></code> elements are assigned to individual
- sections.</p>
+ <p>The section on <a href=#headings-and-sections>headings and sections</a> defines how <code><a href=#the-hgroup-element>hgroup</a></code> elements are
+ assigned to individual sections.</p>
<div class=example>
@@ -17657,16 +17620,13 @@
<h2>Or: How I Learned to Stop Worrying and Love the Bomb</h2>
</hgroup></pre>
- <p>The point of using <code><a href=#the-hgroup-element>hgroup</a></code> in these examples is to
- mask the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code> element (which acts as a secondary title)
- from the <a href=#outline>outline</a> algorithm.</p><!--
- http://www.brucelawson.co.uk/2009/html-5-is-a-mess/#comment-618895
- -->
+ <p>The point of using <code><a href=#the-hgroup-element>hgroup</a></code> in these examples is to mask the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code>
+ element (which acts as a secondary title) from the <a href=#outline>outline</a> algorithm.</p>
+ <!-- http://www.brucelawson.co.uk/2009/html-5-is-a-mess/#comment-618895 -->
- <p>How a user agent exposes such multi-level headings in user
- interfaces (e.g. in tables of contents or search results) is left
- open to implementors, as it is a user interface issue. The first
- example above could be rendered as:</p>
+ <p>How a user agent exposes such multi-level headings in user interfaces (e.g. in tables of
+ contents or search results) is left open to implementors, as it is a user interface issue. The
+ first example above could be rendered as:</p>
<pre>The reality dysfunction: Space is not the only void</pre>
@@ -17674,9 +17634,8 @@
<pre>The reality dysfunction (Space is not the only void)</pre>
- <p>In interfaces where a title can be rendered on multiple lines,
- it could be rendered as follows, maybe with the first line in a
- bigger font size:</p>
+ <p>In interfaces where a title can be rendered on multiple lines, it could be rendered as
+ follows, maybe with the first line in a bigger font size:</p>
<pre>The reality dysfunction
Space is not the only void</pre>
@@ -17698,15 +17657,13 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-header-element>header</a></code> element <a href=#represents>represents</a> a group
- of introductory or navigational aids.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-header-element>header</a></code> element <a href=#represents>represents</a> a group of introductory or navigational
+ aids.</p>
- <p class=note>A <code><a href=#the-header-element>header</a></code> element is intended to usually
- contain the section's heading (an
- <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element or an
- <code><a href=#the-hgroup-element>hgroup</a></code> element), but this is not required. The
- <code><a href=#the-header-element>header</a></code> element can also be used to wrap a section's
- table of contents, a search form, or any relevant logos.</p>
+ <p class=note>A <code><a href=#the-header-element>header</a></code> element is intended to usually contain the section's heading
+ (an <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element or an <code><a href=#the-hgroup-element>hgroup</a></code> element), but this is
+ not required. The <code><a href=#the-header-element>header</a></code> element can also be used to wrap a section's table of
+ contents, a search form, or any relevant logos.</p>
<div class=example>
@@ -17744,18 +17701,15 @@
</div>
- <p class=note>The <code><a href=#the-header-element>header</a></code> element is not
- <a href=#sectioning-content>sectioning content</a>; it doesn't introduce a new
- section.</p>
+ <p class=note>The <code><a href=#the-header-element>header</a></code> element is not <a href=#sectioning-content>sectioning content</a>; it doesn't
+ introduce a new section.</p>
<div class=example>
- <p>In this example, the page has a page heading given by the
- <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element, and two subsections whose headings are
- given by <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code> elements. The content after the
- <code><a href=#the-header-element>header</a></code> element is still part of the last subsection
- started in the <code><a href=#the-header-element>header</a></code> element, because the
- <code><a href=#the-header-element>header</a></code> element doesn't take part in the
+ <p>In this example, the page has a page heading given by the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element, and two
+ subsections whose headings are given by <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code> elements. The content after the
+ <code><a href=#the-header-element>header</a></code> element is still part of the last subsection started in the
+ <code><a href=#the-header-element>header</a></code> element, because the <code><a href=#the-header-element>header</a></code> element doesn't take part in the
<a href=#outline>outline</a> algorithm.</p>
<pre><body>
Modified: index
===================================================================
--- index 2013-01-29 01:05:08 UTC (rev 7664)
+++ index 2013-01-29 01:07:38 UTC (rev 7665)
@@ -16953,34 +16953,27 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-article-element>article</a></code> element <a href=#represents>represents</a> a
- complete, or self-contained, composition in a document, page, application, or site
- and that is, in principle, independently distributable or reusable,
- e.g. in syndication. This could be a forum post, a magazine or
- newspaper article, a blog entry, a user-submitted comment, an
- interactive widget or gadget, or any other independent item of
- content.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-article-element>article</a></code> element <a href=#represents>represents</a> a complete, or self-contained,
+ composition in a document, page, application, or site and that is, in principle, independently
+ distributable or reusable, e.g. in syndication. This could be a forum post, a magazine or
+ newspaper article, a blog entry, a user-submitted comment, an interactive widget or gadget, or any
+ other independent item of content.</p>
- <p>When <code><a href=#the-article-element>article</a></code> elements are nested, the inner
- <code><a href=#the-article-element>article</a></code> elements represent articles that are in
- principle related to the contents of the outer article. For
- instance, a blog entry on a site that accepts user-submitted
- comments could represent the comments as <code><a href=#the-article-element>article</a></code>
- elements nested within the <code><a href=#the-article-element>article</a></code> element for the blog
+ <p>When <code><a href=#the-article-element>article</a></code> elements are nested, the inner <code><a href=#the-article-element>article</a></code> elements
+ represent articles that are in principle related to the contents of the outer article. For
+ instance, a blog entry on a site that accepts user-submitted comments could represent the comments
+ as <code><a href=#the-article-element>article</a></code> elements nested within the <code><a href=#the-article-element>article</a></code> element for the blog
entry.</p>
- <p>Author information associated with an <code><a href=#the-article-element>article</a></code>
- element (q.v. the <code><a href=#the-address-element>address</a></code> element) does not apply to
- nested <code><a href=#the-article-element>article</a></code> elements.</p>
+ <p>Author information associated with an <code><a href=#the-article-element>article</a></code> element (q.v. the
+ <code><a href=#the-address-element>address</a></code> element) does not apply to nested <code><a href=#the-article-element>article</a></code> elements.</p>
- <p class=note>When used specifically with content to be
- redistributed in syndication, the <code><a href=#the-article-element>article</a></code> element is
- similar in purpose to the <code title="">entry</code> element in
+ <p class=note>When used specifically with content to be redistributed in syndication, the
+ <code><a href=#the-article-element>article</a></code> element is similar in purpose to the <code title="">entry</code> element in
Atom. <a href=#refsATOM>[ATOM]</a>
- <p class=note>The schema.org microdata vocabulary can be used to
- provide the publication date for an <code><a href=#the-article-element>article</a></code>
- element, using one of the CreativeWork subtypes.</p>
+ <p class=note>The schema.org microdata vocabulary can be used to provide the publication date
+ for an <code><a href=#the-article-element>article</a></code> element, using one of the CreativeWork subtypes.</p>
<p>When the main content of the page (i.e. excluding footers, headers, navigation blocks, and
sidebars) is all one single self-contained composition, that content may be marked with an
@@ -16989,8 +16982,8 @@
<div class=example id=article-example>
- <p>This example shows a blog post using the <code><a href=#the-article-element>article</a></code>
- element, with some schema.org annotations:</p>
+ <p>This example shows a blog post using the <code><a href=#the-article-element>article</a></code> element, with some schema.org
+ annotations:</p>
<pre><article itemscope itemtype="http://schema.org/BlogPosting">
<header>
@@ -17042,12 +17035,10 @@
</section>
</article></pre>
- <p>Notice the use of <code><a href=#the-footer-element>footer</a></code> to give the information
- for each comment (such as who wrote it and when): the
- <code><a href=#the-footer-element>footer</a></code> element <em>can</em> appear at the start of its
- section when appropriate, such as in this case. (Using
- <code><a href=#the-header-element>header</a></code> in this case wouldn't be wrong either; it's
- mostly a matter of authoring preference.)</p>
+ <p>Notice the use of <code><a href=#the-footer-element>footer</a></code> to give the information for each comment (such as who
+ wrote it and when): the <code><a href=#the-footer-element>footer</a></code> element <em>can</em> appear at the start of its
+ section when appropriate, such as in this case. (Using <code><a href=#the-header-element>header</a></code> in this case wouldn't
+ be wrong either; it's mostly a matter of authoring preference.)</p>
</div>
@@ -17067,34 +17058,28 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-section-element>section</a></code> element <a href=#represents>represents</a> a
- generic section of a document or application. A section, in this
- context, is a thematic grouping of content, typically with a
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-section-element>section</a></code> element <a href=#represents>represents</a> a generic section of a document or
+ application. A section, in this context, is a thematic grouping of content, typically with a
heading.</p>
- <p class=example>Examples of sections would be chapters, the
- various tabbed pages in a tabbed dialog box, or the numbered
- sections of a thesis. A Web site's home page could be split into
- sections for an introduction, news items, and contact
- information.</p>
+ <p class=example>Examples of sections would be chapters, the various tabbed pages in a tabbed
+ dialog box, or the numbered sections of a thesis. A Web site's home page could be split into
+ sections for an introduction, news items, and contact information.</p>
- <p class=note>Authors are encouraged to use the
- <code><a href=#the-article-element>article</a></code> element instead of the <code><a href=#the-section-element>section</a></code>
- element when it would make sense to syndicate the contents of the
+ <p class=note>Authors are encouraged to use the <code><a href=#the-article-element>article</a></code> element instead of the
+ <code><a href=#the-section-element>section</a></code> element when it would make sense to syndicate the contents of the
element.</p>
- <p class=note id=use-div-for-wrappers>The <code><a href=#the-section-element>section</a></code>
- element is not a generic container element. When an element is
- needed only for styling purposes or as a convenience for scripting,
- authors are encouraged to use the <code><a href=#the-div-element>div</a></code> element instead.
- A general rule is that the <code><a href=#the-section-element>section</a></code> element is
- appropriate only if the element's contents would be listed
- explicitly in the document's <a href=#outline>outline</a>.</p>
+ <p class=note id=use-div-for-wrappers>The <code><a href=#the-section-element>section</a></code> element is not a generic
+ container element. When an element is needed only for styling purposes or as a convenience for
+ scripting, authors are encouraged to use the <code><a href=#the-div-element>div</a></code> element instead. A general rule is
+ that the <code><a href=#the-section-element>section</a></code> element is appropriate only if the element's contents would be
+ listed explicitly in the document's <a href=#outline>outline</a>.</p>
<div class=example>
- <p>In the following example, we see an article (part of a larger
- Web page) about apples, containing two short sections.</p>
+ <p>In the following example, we see an article (part of a larger Web page) about apples,
+ containing two short sections.</p>
<pre><article>
<hgroup>
@@ -17114,10 +17099,9 @@
</section>
</article></pre>
- <p>Notice how the use of <code><a href=#the-section-element>section</a></code> means that the author
- can use <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> elements throughout, without having to
- worry about whether a particular section is at the top level, the
- second level, the third level, and so on.</p>
+ <p>Notice how the use of <code><a href=#the-section-element>section</a></code> means that the author can use <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>
+ elements throughout, without having to worry about whether a particular section is at the top
+ level, the second level, the third level, and so on.</p>
</div>
@@ -17175,11 +17159,10 @@
<div class=example>
- <p>In this example, a book author has marked up some sections as
- chapters and some as appendices, and uses CSS to style the headers
- in these two classes of section differently. The whole book is
- wrapped in an <code><a href=#the-article-element>article</a></code> element as part of an even
- larger document containing other books.</p>
+ <p>In this example, a book author has marked up some sections as chapters and some as appendices,
+ and uses CSS to style the headers in these two classes of section differently. The whole book is
+ wrapped in an <code><a href=#the-article-element>article</a></code> element as part of an even larger document containing other
+ books.</p>
<pre><article class="book">
<style>
@@ -17238,31 +17221,25 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-nav-element>nav</a></code> element <a href=#represents>represents</a> a section of
- a page that links to other pages or to parts within the page: a
- section with navigation links.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-nav-element>nav</a></code> element <a href=#represents>represents</a> a section of a page that links to other
+ pages or to parts within the page: a section with navigation links.</p>
- <p class=note>Not all groups of links on a page need to be in a
- <code><a href=#the-nav-element>nav</a></code> element — the element is primarily intended
- for sections that consist of major navigation blocks. In particular,
- it is common for footers to have a short list of links to various
- pages of a site, such as the terms of service, the home page, and a
- copyright page. The <code><a href=#the-footer-element>footer</a></code> element alone is sufficient
- for such cases; while a <code><a href=#the-nav-element>nav</a></code> element can be used in such
- cases, it is usually unnecessary.</p>
+ <p class=note>Not all groups of links on a page need to be in a <code><a href=#the-nav-element>nav</a></code> element —
+ the element is primarily intended for sections that consist of major navigation blocks. In
+ particular, it is common for footers to have a short list of links to various pages of a site,
+ such as the terms of service, the home page, and a copyright page. The <code><a href=#the-footer-element>footer</a></code> element
+ alone is sufficient for such cases; while a <code><a href=#the-nav-element>nav</a></code> element can be used in such cases, it
+ is usually unnecessary.</p>
- <p class=note>User agents (such as screen readers) that are
- targeted at users who can benefit from navigation information being
- omitted in the initial rendering, or who can benefit from navigation
- information being immediately available, can use this element as a
- way to determine what content on the page to initially skip or
- provide on request (or both).</p>
+ <p class=note>User agents (such as screen readers) that are targeted at users who can benefit
+ from navigation information being omitted in the initial rendering, or who can benefit from
+ navigation information being immediately available, can use this element as a way to determine
+ what content on the page to initially skip or provide on request (or both).</p>
<div class=example>
- <p>In the following example, the page has several places where
- links are present, but only one of those places is considered a
- navigation section.</p>
+ <p>In the following example, the page has several places where links are present, but only one of
+ those places is considered a navigation section.</p>
<pre><body itemscope itemtype="http://schema.org/Blog">
<header>
@@ -17306,21 +17283,19 @@
</footer>
</body></pre>
- <p>Notice the <code><a href=#the-div-element>div</a></code> elements being used to wrap all the
- contents of the page other than the header and footer, and all the
- contents of the blog entry other than its header and footer.</p>
+ <p>Notice the <code><a href=#the-div-element>div</a></code> elements being used to wrap all the contents of the page other
+ than the header and footer, and all the contents of the blog entry other than its header and
+ footer.</p>
- <p>You can also see microdata annotations in the above example that
- use the schema.org vocabulary to provide the publication date and
- other metadata about the blog post.</p>
+ <p>You can also see microdata annotations in the above example that use the schema.org vocabulary
+ to provide the publication date and other metadata about the blog post.</p>
</div>
<div class=example>
- <p>In the following example, there are two <code><a href=#the-nav-element>nav</a></code>
- elements, one for primary navigation around the site, and one for
- secondary navigation around the page itself.</p>
+ <p>In the following example, there are two <code><a href=#the-nav-element>nav</a></code> elements, one for primary navigation
+ around the site, and one for secondary navigation around the page itself.</p>
<pre><body>
<h1>The Wiki Center Of Exampland</h1>
@@ -17367,9 +17342,8 @@
<div class=example>
- <p>A <code><a href=#the-nav-element>nav</a></code> element doesn't have to contain a list, it
- can contain other kinds of content as well. In this navigation
- block, links are provided in prose:</p>
+ <p>A <code><a href=#the-nav-element>nav</a></code> element doesn't have to contain a list, it can contain other kinds of
+ content as well. In this navigation block, links are provided in prose:</p>
<pre><nav>
<h1>Navigation</h1>
@@ -17406,26 +17380,22 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-aside-element>aside</a></code> element <a href=#represents>represents</a> a section
- of a page that consists of content that is tangentially related to
- the content around the <code><a href=#the-aside-element>aside</a></code> element, and which could
- be considered separate from that content. Such sections are often
- represented as sidebars in printed typography.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-aside-element>aside</a></code> element <a href=#represents>represents</a> a section of a page that consists of
+ content that is tangentially related to the content around the <code><a href=#the-aside-element>aside</a></code> element, and
+ which could be considered separate from that content. Such sections are often represented as
+ sidebars in printed typography.</p>
- <p>The element can be used for typographical effects like pull
- quotes or sidebars, for advertising, for groups of <code><a href=#the-nav-element>nav</a></code>
- elements, and for other content that is considered separate from the
- main content of the page.</p>
+ <p>The element can be used for typographical effects like pull quotes or sidebars, for
+ advertising, for groups of <code><a href=#the-nav-element>nav</a></code> elements, and for other content that is considered
+ separate from the main content of the page.</p>
- <p class=note>It's not appropriate to use the <code><a href=#the-aside-element>aside</a></code>
- element just for parentheticals, since those are part of the main
- flow of the document.</p>
+ <p class=note>It's not appropriate to use the <code><a href=#the-aside-element>aside</a></code> element just for
+ parentheticals, since those are part of the main flow of the document.</p>
<div class=example>
- <p>The following example shows how an aside is used to mark up
- background material on Switzerland in a much longer news story on
- Europe.</p>
+ <p>The following example shows how an aside is used to mark up background material on Switzerland
+ in a much longer news story on Europe.</p>
<pre><aside>
<h1>Switzerland</h1>
@@ -17438,8 +17408,8 @@
<div class=example>
- <p>The following example shows how an aside is used to mark up
- a pull quote in a longer article.</p>
+ <p>The following example shows how an aside is used to mark up a pull quote in a longer
+ article.</p>
<pre>...
@@ -17464,8 +17434,8 @@
<div class=example>
- <p>The following extract shows how <code><a href=#the-aside-element>aside</a></code> can be used
- for blogrolls and other side content on a blog:</p>
+ <p>The following extract shows how <code><a href=#the-aside-element>aside</a></code> can be used for blogrolls and other side
+ content on a blog:</p>
<pre><body>
<header>
@@ -17556,22 +17526,19 @@
<dd>
<pre class=idl>interface <dfn id=htmlheadingelement>HTMLHeadingElement</dfn> : <a href=#htmlelement>HTMLElement</a> {};</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>These elements <a href=#represents title=represents>represent</a> headings
- for their sections.</p>
+ </dl><!--TOPIC:HTML--><p>These elements <a href=#represents title=represents>represent</a> headings for their sections.</p>
- <p>The semantics and meaning of these elements are defined in the
- section on <a href=#headings-and-sections>headings and sections</a>.</p>
+ <p>The semantics and meaning of these elements are defined in the section on <a href=#headings-and-sections>headings and
+ sections</a>.</p>
- <p>These elements have a <dfn id=rank>rank</dfn> given by the number in
- their name. The <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element is said to have the highest
- rank, the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element has the lowest rank, and two
+ <p>These elements have a <dfn id=rank>rank</dfn> given by the number in their name. The <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>
+ element is said to have the highest rank, the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element has the lowest rank, and two
elements with the same name have equal rank.</p>
<div class=example>
- <p>As far as their respective document outlines (their heading and
- section structures) are concerned, these two snippets are
- semantically equivalent:</p>
+ <p>As far as their respective document outlines (their heading and section structures) are
+ concerned, these two snippets are semantically equivalent:</p>
<pre><body>
<h1>Let's call it a draw(ing surface)</h1>
@@ -17601,9 +17568,9 @@
</section>
</body></pre>
- <p>Authors might prefer the former style for its terseness, or the
- latter style for its convenience in the face of heavy editing;
- which is best is purely an issue of preferred authoring style.</p>
+ <p>Authors might prefer the former style for its terseness, or the latter style for its
+ convenience in the face of heavy editing; which is best is purely an issue of preferred authoring
+ style.</p>
</div>
@@ -17624,24 +17591,20 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-hgroup-element>hgroup</a></code> element <a href=#represents>represents</a> the
- heading of a section. The element is used to group a set of
- <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> elements when the heading has
- multiple levels, such as subheadings, alternative titles, or
- taglines.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-hgroup-element>hgroup</a></code> element <a href=#represents>represents</a> the heading of a section. The element
+ is used to group a set of <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> elements when the heading has
+ multiple levels, such as subheadings, alternative titles, or taglines.</p>
- <p>Other elements of <a href=#heading-content>heading content</a> in the
- <code><a href=#the-hgroup-element>hgroup</a></code> element indicate subheadings or subtitles.</p>
+ <p>Other elements of <a href=#heading-content>heading content</a> in the <code><a href=#the-hgroup-element>hgroup</a></code> element indicate
+ subheadings or subtitles.</p>
- <p>The <a href=#rank>rank</a> of an <code><a href=#the-hgroup-element>hgroup</a></code> element is the
- rank of the highest-ranked <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code>
- element descendant of the <code><a href=#the-hgroup-element>hgroup</a></code> element, if there are
- any such elements, or otherwise the same as for an <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>
- element (the highest rank).</p>
+ <p>The <a href=#rank>rank</a> of an <code><a href=#the-hgroup-element>hgroup</a></code> element is the rank of the highest-ranked
+ <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element descendant of the <code><a href=#the-hgroup-element>hgroup</a></code> element, if
+ there are any such elements, or otherwise the same as for an <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element (the highest
+ rank).</p>
- <p>The section on <a href=#headings-and-sections>headings and sections</a>
- defines how <code><a href=#the-hgroup-element>hgroup</a></code> elements are assigned to individual
- sections.</p>
+ <p>The section on <a href=#headings-and-sections>headings and sections</a> defines how <code><a href=#the-hgroup-element>hgroup</a></code> elements are
+ assigned to individual sections.</p>
<div class=example>
@@ -17657,16 +17620,13 @@
<h2>Or: How I Learned to Stop Worrying and Love the Bomb</h2>
</hgroup></pre>
- <p>The point of using <code><a href=#the-hgroup-element>hgroup</a></code> in these examples is to
- mask the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code> element (which acts as a secondary title)
- from the <a href=#outline>outline</a> algorithm.</p><!--
- http://www.brucelawson.co.uk/2009/html-5-is-a-mess/#comment-618895
- -->
+ <p>The point of using <code><a href=#the-hgroup-element>hgroup</a></code> in these examples is to mask the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code>
+ element (which acts as a secondary title) from the <a href=#outline>outline</a> algorithm.</p>
+ <!-- http://www.brucelawson.co.uk/2009/html-5-is-a-mess/#comment-618895 -->
- <p>How a user agent exposes such multi-level headings in user
- interfaces (e.g. in tables of contents or search results) is left
- open to implementors, as it is a user interface issue. The first
- example above could be rendered as:</p>
+ <p>How a user agent exposes such multi-level headings in user interfaces (e.g. in tables of
+ contents or search results) is left open to implementors, as it is a user interface issue. The
+ first example above could be rendered as:</p>
<pre>The reality dysfunction: Space is not the only void</pre>
@@ -17674,9 +17634,8 @@
<pre>The reality dysfunction (Space is not the only void)</pre>
- <p>In interfaces where a title can be rendered on multiple lines,
- it could be rendered as follows, maybe with the first line in a
- bigger font size:</p>
+ <p>In interfaces where a title can be rendered on multiple lines, it could be rendered as
+ follows, maybe with the first line in a bigger font size:</p>
<pre>The reality dysfunction
Space is not the only void</pre>
@@ -17698,15 +17657,13 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-header-element>header</a></code> element <a href=#represents>represents</a> a group
- of introductory or navigational aids.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-header-element>header</a></code> element <a href=#represents>represents</a> a group of introductory or navigational
+ aids.</p>
- <p class=note>A <code><a href=#the-header-element>header</a></code> element is intended to usually
- contain the section's heading (an
- <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element or an
- <code><a href=#the-hgroup-element>hgroup</a></code> element), but this is not required. The
- <code><a href=#the-header-element>header</a></code> element can also be used to wrap a section's
- table of contents, a search form, or any relevant logos.</p>
+ <p class=note>A <code><a href=#the-header-element>header</a></code> element is intended to usually contain the section's heading
+ (an <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>–<code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h6</a></code> element or an <code><a href=#the-hgroup-element>hgroup</a></code> element), but this is
+ not required. The <code><a href=#the-header-element>header</a></code> element can also be used to wrap a section's table of
+ contents, a search form, or any relevant logos.</p>
<div class=example>
@@ -17744,18 +17701,15 @@
</div>
- <p class=note>The <code><a href=#the-header-element>header</a></code> element is not
- <a href=#sectioning-content>sectioning content</a>; it doesn't introduce a new
- section.</p>
+ <p class=note>The <code><a href=#the-header-element>header</a></code> element is not <a href=#sectioning-content>sectioning content</a>; it doesn't
+ introduce a new section.</p>
<div class=example>
- <p>In this example, the page has a page heading given by the
- <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element, and two subsections whose headings are
- given by <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code> elements. The content after the
- <code><a href=#the-header-element>header</a></code> element is still part of the last subsection
- started in the <code><a href=#the-header-element>header</a></code> element, because the
- <code><a href=#the-header-element>header</a></code> element doesn't take part in the
+ <p>In this example, the page has a page heading given by the <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> element, and two
+ subsections whose headings are given by <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h2</a></code> elements. The content after the
+ <code><a href=#the-header-element>header</a></code> element is still part of the last subsection started in the
+ <code><a href=#the-header-element>header</a></code> element, because the <code><a href=#the-header-element>header</a></code> element doesn't take part in the
<a href=#outline>outline</a> algorithm.</p>
<pre><body>
Modified: source
===================================================================
--- source 2013-01-29 01:05:08 UTC (rev 7664)
+++ source 2013-01-29 01:07:38 UTC (rev 7665)
@@ -17892,34 +17892,27 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>article</code> element <span>represents</span> a
- complete, or self-contained, composition in a document, page, application, or site
- and that is, in principle, independently distributable or reusable,
- e.g. in syndication. This could be a forum post, a magazine or
- newspaper article, a blog entry, a user-submitted comment, an
- interactive widget or gadget, or any other independent item of
- content.</p>
+ <p>The <code>article</code> element <span>represents</span> a complete, or self-contained,
+ composition in a document, page, application, or site and that is, in principle, independently
+ distributable or reusable, e.g. in syndication. This could be a forum post, a magazine or
+ newspaper article, a blog entry, a user-submitted comment, an interactive widget or gadget, or any
+ other independent item of content.</p>
- <p>When <code>article</code> elements are nested, the inner
- <code>article</code> elements represent articles that are in
- principle related to the contents of the outer article. For
- instance, a blog entry on a site that accepts user-submitted
- comments could represent the comments as <code>article</code>
- elements nested within the <code>article</code> element for the blog
+ <p>When <code>article</code> elements are nested, the inner <code>article</code> elements
+ represent articles that are in principle related to the contents of the outer article. For
+ instance, a blog entry on a site that accepts user-submitted comments could represent the comments
+ as <code>article</code> elements nested within the <code>article</code> element for the blog
entry.</p>
- <p>Author information associated with an <code>article</code>
- element (q.v. the <code>address</code> element) does not apply to
- nested <code>article</code> elements.</p>
+ <p>Author information associated with an <code>article</code> element (q.v. the
+ <code>address</code> element) does not apply to nested <code>article</code> elements.</p>
- <p class="note">When used specifically with content to be
- redistributed in syndication, the <code>article</code> element is
- similar in purpose to the <code title="">entry</code> element in
+ <p class="note">When used specifically with content to be redistributed in syndication, the
+ <code>article</code> element is similar in purpose to the <code title="">entry</code> element in
Atom. <a href="#refsATOM">[ATOM]</a>
- <p class="note">The schema.org microdata vocabulary can be used to
- provide the publication date for an <code>article</code>
- element, using one of the CreativeWork subtypes.</p>
+ <p class="note">The schema.org microdata vocabulary can be used to provide the publication date
+ for an <code>article</code> element, using one of the CreativeWork subtypes.</p>
<p>When the main content of the page (i.e. excluding footers, headers, navigation blocks, and
sidebars) is all one single self-contained composition, that content may be marked with an
@@ -17928,8 +17921,8 @@
<div id="article-example" class="example">
- <p>This example shows a blog post using the <code>article</code>
- element, with some schema.org annotations:</p>
+ <p>This example shows a blog post using the <code>article</code> element, with some schema.org
+ annotations:</p>
<pre><article itemscope itemtype="http://schema.org/BlogPosting">
<header>
@@ -17981,12 +17974,10 @@
</section>
</article></pre>
- <p>Notice the use of <code>footer</code> to give the information
- for each comment (such as who wrote it and when): the
- <code>footer</code> element <em>can</em> appear at the start of its
- section when appropriate, such as in this case. (Using
- <code>header</code> in this case wouldn't be wrong either; it's
- mostly a matter of authoring preference.)</p>
+ <p>Notice the use of <code>footer</code> to give the information for each comment (such as who
+ wrote it and when): the <code>footer</code> element <em>can</em> appear at the start of its
+ section when appropriate, such as in this case. (Using <code>header</code> in this case wouldn't
+ be wrong either; it's mostly a matter of authoring preference.)</p>
</div>
@@ -18009,34 +18000,28 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>section</code> element <span>represents</span> a
- generic section of a document or application. A section, in this
- context, is a thematic grouping of content, typically with a
+ <p>The <code>section</code> element <span>represents</span> a generic section of a document or
+ application. A section, in this context, is a thematic grouping of content, typically with a
heading.</p>
- <p class="example">Examples of sections would be chapters, the
- various tabbed pages in a tabbed dialog box, or the numbered
- sections of a thesis. A Web site's home page could be split into
- sections for an introduction, news items, and contact
- information.</p>
+ <p class="example">Examples of sections would be chapters, the various tabbed pages in a tabbed
+ dialog box, or the numbered sections of a thesis. A Web site's home page could be split into
+ sections for an introduction, news items, and contact information.</p>
- <p class="note">Authors are encouraged to use the
- <code>article</code> element instead of the <code>section</code>
- element when it would make sense to syndicate the contents of the
+ <p class="note">Authors are encouraged to use the <code>article</code> element instead of the
+ <code>section</code> element when it would make sense to syndicate the contents of the
element.</p>
- <p class="note" id="use-div-for-wrappers">The <code>section</code>
- element is not a generic container element. When an element is
- needed only for styling purposes or as a convenience for scripting,
- authors are encouraged to use the <code>div</code> element instead.
- A general rule is that the <code>section</code> element is
- appropriate only if the element's contents would be listed
- explicitly in the document's <span>outline</span>.</p>
+ <p class="note" id="use-div-for-wrappers">The <code>section</code> element is not a generic
+ container element. When an element is needed only for styling purposes or as a convenience for
+ scripting, authors are encouraged to use the <code>div</code> element instead. A general rule is
+ that the <code>section</code> element is appropriate only if the element's contents would be
+ listed explicitly in the document's <span>outline</span>.</p>
<div class="example">
- <p>In the following example, we see an article (part of a larger
- Web page) about apples, containing two short sections.</p>
+ <p>In the following example, we see an article (part of a larger Web page) about apples,
+ containing two short sections.</p>
<pre><article>
<hgroup>
@@ -18056,10 +18041,9 @@
</section>
</article></pre>
- <p>Notice how the use of <code>section</code> means that the author
- can use <code>h1</code> elements throughout, without having to
- worry about whether a particular section is at the top level, the
- second level, the third level, and so on.</p>
+ <p>Notice how the use of <code>section</code> means that the author can use <code>h1</code>
+ elements throughout, without having to worry about whether a particular section is at the top
+ level, the second level, the third level, and so on.</p>
</div>
@@ -18117,11 +18101,10 @@
<div class="example">
- <p>In this example, a book author has marked up some sections as
- chapters and some as appendices, and uses CSS to style the headers
- in these two classes of section differently. The whole book is
- wrapped in an <code>article</code> element as part of an even
- larger document containing other books.</p>
+ <p>In this example, a book author has marked up some sections as chapters and some as appendices,
+ and uses CSS to style the headers in these two classes of section differently. The whole book is
+ wrapped in an <code>article</code> element as part of an even larger document containing other
+ books.</p>
<pre><article class="book">
<style>
@@ -18183,31 +18166,25 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>nav</code> element <span>represents</span> a section of
- a page that links to other pages or to parts within the page: a
- section with navigation links.</p>
+ <p>The <code>nav</code> element <span>represents</span> a section of a page that links to other
+ pages or to parts within the page: a section with navigation links.</p>
- <p class="note">Not all groups of links on a page need to be in a
- <code>nav</code> element — the element is primarily intended
- for sections that consist of major navigation blocks. In particular,
- it is common for footers to have a short list of links to various
- pages of a site, such as the terms of service, the home page, and a
- copyright page. The <code>footer</code> element alone is sufficient
- for such cases; while a <code>nav</code> element can be used in such
- cases, it is usually unnecessary.</p>
+ <p class="note">Not all groups of links on a page need to be in a <code>nav</code> element —
+ the element is primarily intended for sections that consist of major navigation blocks. In
+ particular, it is common for footers to have a short list of links to various pages of a site,
+ such as the terms of service, the home page, and a copyright page. The <code>footer</code> element
+ alone is sufficient for such cases; while a <code>nav</code> element can be used in such cases, it
+ is usually unnecessary.</p>
- <p class="note">User agents (such as screen readers) that are
- targeted at users who can benefit from navigation information being
- omitted in the initial rendering, or who can benefit from navigation
- information being immediately available, can use this element as a
- way to determine what content on the page to initially skip or
- provide on request (or both).</p>
+ <p class="note">User agents (such as screen readers) that are targeted at users who can benefit
+ from navigation information being omitted in the initial rendering, or who can benefit from
+ navigation information being immediately available, can use this element as a way to determine
+ what content on the page to initially skip or provide on request (or both).</p>
<div class="example">
- <p>In the following example, the page has several places where
- links are present, but only one of those places is considered a
- navigation section.</p>
+ <p>In the following example, the page has several places where links are present, but only one of
+ those places is considered a navigation section.</p>
<pre><body itemscope itemtype="http://schema.org/Blog">
<header>
@@ -18251,21 +18228,19 @@
</footer>
</body></pre>
- <p>Notice the <code>div</code> elements being used to wrap all the
- contents of the page other than the header and footer, and all the
- contents of the blog entry other than its header and footer.</p>
+ <p>Notice the <code>div</code> elements being used to wrap all the contents of the page other
+ than the header and footer, and all the contents of the blog entry other than its header and
+ footer.</p>
- <p>You can also see microdata annotations in the above example that
- use the schema.org vocabulary to provide the publication date and
- other metadata about the blog post.</p>
+ <p>You can also see microdata annotations in the above example that use the schema.org vocabulary
+ to provide the publication date and other metadata about the blog post.</p>
</div>
<div class="example">
- <p>In the following example, there are two <code>nav</code>
- elements, one for primary navigation around the site, and one for
- secondary navigation around the page itself.</p>
+ <p>In the following example, there are two <code>nav</code> elements, one for primary navigation
+ around the site, and one for secondary navigation around the page itself.</p>
<pre><body>
<h1>The Wiki Center Of Exampland</h1>
@@ -18312,9 +18287,8 @@
<div class="example">
- <p>A <code>nav</code> element doesn't have to contain a list, it
- can contain other kinds of content as well. In this navigation
- block, links are provided in prose:</p>
+ <p>A <code>nav</code> element doesn't have to contain a list, it can contain other kinds of
+ content as well. In this navigation block, links are provided in prose:</p>
<pre><nav>
<h1>Navigation</h1>
@@ -18354,26 +18328,22 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>aside</code> element <span>represents</span> a section
- of a page that consists of content that is tangentially related to
- the content around the <code>aside</code> element, and which could
- be considered separate from that content. Such sections are often
- represented as sidebars in printed typography.</p>
+ <p>The <code>aside</code> element <span>represents</span> a section of a page that consists of
+ content that is tangentially related to the content around the <code>aside</code> element, and
+ which could be considered separate from that content. Such sections are often represented as
+ sidebars in printed typography.</p>
- <p>The element can be used for typographical effects like pull
- quotes or sidebars, for advertising, for groups of <code>nav</code>
- elements, and for other content that is considered separate from the
- main content of the page.</p>
+ <p>The element can be used for typographical effects like pull quotes or sidebars, for
+ advertising, for groups of <code>nav</code> elements, and for other content that is considered
+ separate from the main content of the page.</p>
- <p class="note">It's not appropriate to use the <code>aside</code>
- element just for parentheticals, since those are part of the main
- flow of the document.</p>
+ <p class="note">It's not appropriate to use the <code>aside</code> element just for
+ parentheticals, since those are part of the main flow of the document.</p>
<div class="example">
- <p>The following example shows how an aside is used to mark up
- background material on Switzerland in a much longer news story on
- Europe.</p>
+ <p>The following example shows how an aside is used to mark up background material on Switzerland
+ in a much longer news story on Europe.</p>
<pre><aside>
<h1>Switzerland</h1>
@@ -18386,8 +18356,8 @@
<div class="example">
- <p>The following example shows how an aside is used to mark up
- a pull quote in a longer article.</p>
+ <p>The following example shows how an aside is used to mark up a pull quote in a longer
+ article.</p>
<pre>...
@@ -18412,8 +18382,8 @@
<div class="example">
- <p>The following extract shows how <code>aside</code> can be used
- for blogrolls and other side content on a blog:</p>
+ <p>The following extract shows how <code>aside</code> can be used for blogrolls and other side
+ content on a blog:</p>
<pre><body>
<header>
@@ -18512,22 +18482,19 @@
</dd>
</dl><!--TOPIC:HTML-->
- <p>These elements <span title="represents">represent</span> headings
- for their sections.</p>
+ <p>These elements <span title="represents">represent</span> headings for their sections.</p>
- <p>The semantics and meaning of these elements are defined in the
- section on <span>headings and sections</span>.</p>
+ <p>The semantics and meaning of these elements are defined in the section on <span>headings and
+ sections</span>.</p>
- <p>These elements have a <dfn>rank</dfn> given by the number in
- their name. The <code>h1</code> element is said to have the highest
- rank, the <code>h6</code> element has the lowest rank, and two
+ <p>These elements have a <dfn>rank</dfn> given by the number in their name. The <code>h1</code>
+ element is said to have the highest rank, the <code>h6</code> element has the lowest rank, and two
elements with the same name have equal rank.</p>
<div class="example">
- <p>As far as their respective document outlines (their heading and
- section structures) are concerned, these two snippets are
- semantically equivalent:</p>
+ <p>As far as their respective document outlines (their heading and section structures) are
+ concerned, these two snippets are semantically equivalent:</p>
<pre><body>
<h1>Let's call it a draw(ing surface)</h1>
@@ -18557,9 +18524,9 @@
</section>
</body></pre>
- <p>Authors might prefer the former style for its terseness, or the
- latter style for its convenience in the face of heavy editing;
- which is best is purely an issue of preferred authoring style.</p>
+ <p>Authors might prefer the former style for its terseness, or the latter style for its
+ convenience in the face of heavy editing; which is best is purely an issue of preferred authoring
+ style.</p>
</div>
@@ -18583,24 +18550,20 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>hgroup</code> element <span>represents</span> the
- heading of a section. The element is used to group a set of
- <code>h1</code>–<code>h6</code> elements when the heading has
- multiple levels, such as subheadings, alternative titles, or
- taglines.</p>
+ <p>The <code>hgroup</code> element <span>represents</span> the heading of a section. The element
+ is used to group a set of <code>h1</code>–<code>h6</code> elements when the heading has
+ multiple levels, such as subheadings, alternative titles, or taglines.</p>
- <p>Other elements of <span>heading content</span> in the
- <code>hgroup</code> element indicate subheadings or subtitles.</p>
+ <p>Other elements of <span>heading content</span> in the <code>hgroup</code> element indicate
+ subheadings or subtitles.</p>
- <p>The <span>rank</span> of an <code>hgroup</code> element is the
- rank of the highest-ranked <code>h1</code>–<code>h6</code>
- element descendant of the <code>hgroup</code> element, if there are
- any such elements, or otherwise the same as for an <code>h1</code>
- element (the highest rank).</p>
+ <p>The <span>rank</span> of an <code>hgroup</code> element is the rank of the highest-ranked
+ <code>h1</code>–<code>h6</code> element descendant of the <code>hgroup</code> element, if
+ there are any such elements, or otherwise the same as for an <code>h1</code> element (the highest
+ rank).</p>
- <p>The section on <span>headings and sections</span>
- defines how <code>hgroup</code> elements are assigned to individual
- sections.</p>
+ <p>The section on <span>headings and sections</span> defines how <code>hgroup</code> elements are
+ assigned to individual sections.</p>
<div class="example">
@@ -18616,16 +18579,13 @@
<h2>Or: How I Learned to Stop Worrying and Love the Bomb</h2>
</hgroup></pre>
- <p>The point of using <code>hgroup</code> in these examples is to
- mask the <code>h2</code> element (which acts as a secondary title)
- from the <span>outline</span> algorithm.</p><!--
- http://www.brucelawson.co.uk/2009/html-5-is-a-mess/#comment-618895
- -->
+ <p>The point of using <code>hgroup</code> in these examples is to mask the <code>h2</code>
+ element (which acts as a secondary title) from the <span>outline</span> algorithm.</p>
+ <!-- http://www.brucelawson.co.uk/2009/html-5-is-a-mess/#comment-618895 -->
- <p>How a user agent exposes such multi-level headings in user
- interfaces (e.g. in tables of contents or search results) is left
- open to implementors, as it is a user interface issue. The first
- example above could be rendered as:</p>
+ <p>How a user agent exposes such multi-level headings in user interfaces (e.g. in tables of
+ contents or search results) is left open to implementors, as it is a user interface issue. The
+ first example above could be rendered as:</p>
<pre>The reality dysfunction: Space is not the only void</pre>
@@ -18633,9 +18593,8 @@
<pre>The reality dysfunction (Space is not the only void)</pre>
- <p>In interfaces where a title can be rendered on multiple lines,
- it could be rendered as follows, maybe with the first line in a
- bigger font size:</p>
+ <p>In interfaces where a title can be rendered on multiple lines, it could be rendered as
+ follows, maybe with the first line in a bigger font size:</p>
<pre>The reality dysfunction
Space is not the only void</pre>
@@ -18660,15 +18619,13 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>header</code> element <span>represents</span> a group
- of introductory or navigational aids.</p>
+ <p>The <code>header</code> element <span>represents</span> a group of introductory or navigational
+ aids.</p>
- <p class="note">A <code>header</code> element is intended to usually
- contain the section's heading (an
- <code>h1</code>–<code>h6</code> element or an
- <code>hgroup</code> element), but this is not required. The
- <code>header</code> element can also be used to wrap a section's
- table of contents, a search form, or any relevant logos.</p>
+ <p class="note">A <code>header</code> element is intended to usually contain the section's heading
+ (an <code>h1</code>–<code>h6</code> element or an <code>hgroup</code> element), but this is
+ not required. The <code>header</code> element can also be used to wrap a section's table of
+ contents, a search form, or any relevant logos.</p>
<div class="example">
@@ -18706,18 +18663,15 @@
</div>
- <p class="note">The <code>header</code> element is not
- <span>sectioning content</span>; it doesn't introduce a new
- section.</p>
+ <p class="note">The <code>header</code> element is not <span>sectioning content</span>; it doesn't
+ introduce a new section.</p>
<div class="example">
- <p>In this example, the page has a page heading given by the
- <code>h1</code> element, and two subsections whose headings are
- given by <code>h2</code> elements. The content after the
- <code>header</code> element is still part of the last subsection
- started in the <code>header</code> element, because the
- <code>header</code> element doesn't take part in the
+ <p>In this example, the page has a page heading given by the <code>h1</code> element, and two
+ subsections whose headings are given by <code>h2</code> elements. The content after the
+ <code>header</code> element is still part of the last subsection started in the
+ <code>header</code> element, because the <code>header</code> element doesn't take part in the
<span>outline</span> algorithm.</p>
<pre><body>
More information about the Commit-Watchers
mailing list