HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
3859[Authors] [Conformance Checkers] [Gecko] [Internet Explorer] [Opera] [Webkit] [Tools] Parser changes: <dc>, <ds>, <dialog> are now treated differently. Styling changes: <dialog>, <dc>, <ds>, and <details> are now treated differently. Semantic changes: Dropped <dialog>. <figure> and <details> now use <dt>/<dd> instead of <legend>. Editorial changes: Added a section on how to mark up conversations, moved the sections on footnotes and tag clouds around. Updated lots of examples. Validator changes: Changed rules for missing alt='' given the new elements.2009-09-15 11:09
@@ -8558,21 +8558,20 @@ background: transparent">blue&lt;/span>.&lt;/p></pre>
    <li><code>button</code></li>
    <li><code>canvas</code></li>
    <li><code>cite</code></li>
    <li><code>code</code></li>
    <li><code>command</code></li>
 <!-- v2DATAGRID   <li><code>datagrid</code></li> -->
    <li><code>datalist</code></li>
    <li><code>del</code></li>
    <li><code>details</code></li>
    <li><code>dfn</code></li>
-   <li><code>dialog</code></li>
    <li><code>div</code></li>
    <li><code>dl</code></li>
    <li><code>em</code></li>
    <li><code>embed</code></li>
    <li><code>fieldset</code></li>
    <li><code>figure</code></li>
    <li><code>footer</code></li>
    <li><code>form</code></li>
    <li><code>h1</code></li>
    <li><code>h2</code></li>
@@ -15352,77 +15351,20 @@ that i admit loss of a feline
 
 a friend lost to the
         unknown
                                 (night)
 
 ~cdr 11dec07&lt;/pre></pre>
 
   </div>
 
 
-  <h4>The <dfn><code>dialog</code></dfn> element</h4>
-
-  <dl class="element">
-   <dt>Categories</dt>
-   <dd><span>Flow content</span>.</dd>
-   <dt>Contexts in which this element may be used:</dt>
-   <dd>Where <span>flow content</span> is expected.</dd>
-   <dt>Content model:</dt>
-   <dd>Zero or more pairs of one <code>dt</code> element followed by
-   one <code>dd</code> element.</dd>
-   <dt>Content attributes:</dt>
-   <dd><span>Global attributes</span></dd>
-   <dt>DOM interface:</dt>
-   <dd>Uses <code>HTMLElement</code>.</dd>
-  </dl>
-
-  <p>The <code>dialog</code> element <span>represents</span> a
-  conversation, meeting minutes, a chat transcript, a dialog in a
-  screenplay, an instant message log, or some other construct in which
-  different players take turns in discourse.</p>
-
-  <p>Each part of the conversation must have an explicit talker (or
-  speaker) given by a <code>dt</code> element, and a discourse (or
-  quote) given by a <code>dd</code> element.</p>
-
-  <div class="example">
-   <p>This example demonstrates this using an extract from Abbot and
-   Costello's famous sketch, <cite>Who's on first</cite>:</p>
-<pre>&lt;dialog>
- &lt;dt> Costello
- &lt;dd> Look, you gotta first baseman?
- &lt;dt> Abbott
- &lt;dd> Certainly.
- &lt;dt> Costello
- &lt;dd> Who's playing first?
- &lt;dt> Abbott
- &lt;dd> That's right.
- &lt;dt> Costello
- &lt;dd> When you pay off the first baseman every month, who gets the money?
- &lt;dt> Abbott
- &lt;dd> Every dollar of it.
-&lt;/dialog></pre>
-  </div>
-
-  <p class="note">Text in a <code>dt</code> element in a
-  <code>dialog</code> element is implicitly the source of the text
-  given in the following <code>dd</code> element, and the contents of
-  the <code>dd</code> element are implicitly a quote from that
-  speaker. There is thus no need to include <code>cite</code>,
-  <code>q</code>, or <code>blockquote</code> elements in this
-  markup. Indeed, a <code>q</code> element inside a <code>dd</code>
-  element in a conversation would actually imply the people talking
-  were themselves quoting another work. See the <code>cite</code>,
-  <code>q</code>, and <code>blockquote</code> elements for other ways
-  to cite or quote.</p>
-
-
 
   <h4>The <dfn><code>blockquote</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
    <dd><span>Sectioning root</span>.</dd>
    <dd><span><code title="">formatBlock</code> candidate</span>.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>flow content</span> is expected.</dd>
@@ -15457,37 +15399,38 @@ a friend lost to the
   such citation links.</span></p>
 
   <div class="impl">
 
   <p>The <dfn title="dom-quote-cite"><code>cite</code></dfn> IDL
   attribute must <span>reflect</span> the element's <code
   title="">cite</code> content attribute.</p>
 
   </div>
 
-  <p class="note">The best way to represent a conversation is not with
-  the <code>cite</code> and <code>blockquote</code> elements, but with
-  the <code>dialog</code> element.</p>
-
   <div class="example">
 
    <p>This next example shows the use of <code>cite</code> alongside
    <code>blockquote</code>:</p>
 
    <pre>&lt;p>His next piece was the aptly named &lt;cite>Sonnet 130&lt;/cite>:&lt;/p>
 &lt;blockquote cite="http://quotes.example.org/s/sonnet130.html">
   &lt;p>My mistress' eyes are nothing like the sun,&lt;br>
   Coral is far more red, than her lips red,&lt;br>
   ...</pre>
 
   </div>
 
+  <p class="note"><a href="#conversations">Examples of how to
+  represent a conversation</a> are shown below; it is not appropriate
+  to use the <code>cite</code> and <code>blockquote</code> elements
+  for this purpose.</p>
+
 
 
   <h4>The <dfn><code>ol</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>flow content</span> is expected.</dd>
    <dt>Content model:</dt>
@@ -15699,55 +15642,59 @@ I first lived there):&lt;/p>
 
   <p>The <dfn title="dom-li-value"><code>value</code></dfn> IDL
   attribute must <span>reflect</span> the value of the <code
   title="dom-li-value">value</code> content attribute.</p>
 
   </div>
 
   <div class="example">
    <p>The following example, the top ten movies are listed (in reverse
    order). Note the way the list is given a title by using a
-   <code>figure</code> element and its <code>legend</code>.</p>
+   <code>figure</code> element and its <code>dt</code> element.</p>
    <pre>&lt;figure>
- &lt;legend>The top 10 movies of all time&lt;/legend>
- &lt;ol>
-  &lt;li value="10">&lt;cite>Josie and the Pussycats&lt;/cite>, 2001&lt;/li>
-  &lt;li value="9">&lt;cite lang="sh">&#x0426;&#x0440;&#x043d;&#x0430; &#x043c;&#x0430;&#x0447;&#x043a;&#x0430;, &#x0431;&#x0435;&#x043b;&#x0438; &#x043c;&#x0430;&#x0447;&#x043e;&#x0440;&lt;/cite>, 1998&lt;/li>
-  &lt;li value="8">&lt;cite>A Bug's Life&lt;/cite>, 1998&lt;/li>
-  &lt;li value="7">&lt;cite>Toy Story&lt;/cite>, 1995&lt;/li>
-  &lt;li value="6">&lt;cite>Monsters, Inc&lt;/cite>, 2001&lt;/li>
-  &lt;li value="5">&lt;cite>Cars&lt;/cite>, 2006&lt;/li>
-  &lt;li value="4">&lt;cite>Toy Story 2&lt;/cite>, 1999&lt;/li>
-  &lt;li value="3">&lt;cite>Finding Nemo&lt;/cite>, 2003&lt;/li>
-  &lt;li value="2">&lt;cite>The Incredibles&lt;/cite>, 2004&lt;/li>
-  &lt;li value="1">&lt;cite>Ratatouille&lt;/cite>, 2007&lt;/li>
- &lt;/ol>
+ &lt;dt>The top 10 movies of all time&lt;/dt>
+ &lt;dd>
+  &lt;ol>
+   &lt;li value="10">&lt;cite>Josie and the Pussycats&lt;/cite>, 2001&lt;/li>
+   &lt;li value="9">&lt;cite lang="sh">&#x0426;&#x0440;&#x043d;&#x0430; &#x043c;&#x0430;&#x0447;&#x043a;&#x0430;, &#x0431;&#x0435;&#x043b;&#x0438; &#x043c;&#x0430;&#x0447;&#x043e;&#x0440;&lt;/cite>, 1998&lt;/li>
+   &lt;li value="8">&lt;cite>A Bug's Life&lt;/cite>, 1998&lt;/li>
+   &lt;li value="7">&lt;cite>Toy Story&lt;/cite>, 1995&lt;/li>
+   &lt;li value="6">&lt;cite>Monsters, Inc&lt;/cite>, 2001&lt;/li>
+   &lt;li value="5">&lt;cite>Cars&lt;/cite>, 2006&lt;/li>
+   &lt;li value="4">&lt;cite>Toy Story 2&lt;/cite>, 1999&lt;/li>
+   &lt;li value="3">&lt;cite>Finding Nemo&lt;/cite>, 2003&lt;/li>
+   &lt;li value="2">&lt;cite>The Incredibles&lt;/cite>, 2004&lt;/li>
+   &lt;li value="1">&lt;cite>Ratatouille&lt;/cite>, 2007&lt;/li>
+  &lt;/ol>
+ &lt;dd>
 &lt;/figure></pre>
 
    <p>The markup could also be written as follows, using the <code
    title="attr-ol-reversed">reversed</code> attribute on the
    <code>ol</code> element:</p>
 
    <pre>&lt;figure>
- &lt;legend>The top 10 movies of all time&lt;/legend>
- &lt;ol reversed>
-  &lt;li>&lt;cite>Josie and the Pussycats&lt;/cite>, 2001&lt;/li>
-  &lt;li>&lt;cite lang="sh">&#x0426;&#x0440;&#x043d;&#x0430; &#x043c;&#x0430;&#x0447;&#x043a;&#x0430;, &#x0431;&#x0435;&#x043b;&#x0438; &#x043c;&#x0430;&#x0447;&#x043e;&#x0440;&lt;/cite>, 1998&lt;/li>
-  &lt;li>&lt;cite>A Bug's Life&lt;/cite>, 1998&lt;/li>
-  &lt;li>&lt;cite>Toy Story&lt;/cite>, 1995&lt;/li>
-  &lt;li>&lt;cite>Monsters, Inc&lt;/cite>, 2001&lt;/li>
-  &lt;li>&lt;cite>Cars&lt;/cite>, 2006&lt;/li>
-  &lt;li>&lt;cite>Toy Story 2&lt;/cite>, 1999&lt;/li>
-  &lt;li>&lt;cite>Finding Nemo&lt;/cite>, 2003&lt;/li>
-  &lt;li>&lt;cite>The Incredibles&lt;/cite>, 2004&lt;/li>
-  &lt;li>&lt;cite>Ratatouille&lt;/cite>, 2007&lt;/li>
- &lt;/ol>
+ &lt;dt>The top 10 movies of all time&lt;/dt>
+ &lt;dd>
+  &lt;ol reversed>
+   &lt;li>&lt;cite>Josie and the Pussycats&lt;/cite>, 2001&lt;/li>
+   &lt;li>&lt;cite lang="sh">&#x0426;&#x0440;&#x043d;&#x0430; &#x043c;&#x0430;&#x0447;&#x043a;&#x0430;, &#x0431;&#x0435;&#x043b;&#x0438; &#x043c;&#x0430;&#x0447;&#x043e;&#x0440;&lt;/cite>, 1998&lt;/li>
+   &lt;li>&lt;cite>A Bug's Life&lt;/cite>, 1998&lt;/li>
+   &lt;li>&lt;cite>Toy Story&lt;/cite>, 1995&lt;/li>
+   &lt;li>&lt;cite>Monsters, Inc&lt;/cite>, 2001&lt;/li>
+   &lt;li>&lt;cite>Cars&lt;/cite>, 2006&lt;/li>
+   &lt;li>&lt;cite>Toy Story 2&lt;/cite>, 1999&lt;/li>
+   &lt;li>&lt;cite>Finding Nemo&lt;/cite>, 2003&lt;/li>
+   &lt;li>&lt;cite>The Incredibles&lt;/cite>, 2004&lt;/li>
+   &lt;li>&lt;cite>Ratatouille&lt;/cite>, 2007&lt;/li>
+  &lt;/ol>
+ &lt;/dd>
 &lt;/figure></pre>
   </div>
 
   <p class="note">If the <code>li</code> element is the child of a
   <code>menu</code> element and itself has a child that defines a
   <span title="concept-command">command</span>, then the
   <code>li</code> element will match the <code
   title="selector-enabled">:enabled</code> and <code
   title="selector-disabled">:disabled</code> pseudo-classes in the
   same way as the first such child element does.</p>
@@ -15770,21 +15717,23 @@ I first lived there):&lt;/p>
    <dt>DOM interface:</dt>
    <dd>
     <pre class="idl">interface <dfn>HTMLDListElement</dfn> : <span>HTMLElement</span> {};</pre>
    </dd>
   </dl>
 
   <p>The <code>dl</code> element <span>represents</span> an
   association list consisting of zero or more name-value groups (a
   description list). Each group must consist of one or more names
   (<code>dt</code> elements) followed by one or more values
-  (<code>dd</code> elements).</p>
+  (<code>dd</code> elements). Within a single <code>dl</code> element,
+  there should not be more than one <code>dt</code> element for each
+  name.</p>
 
   <p>Name-value groups may be terms and definitions, metadata topics
   and values, or any other groups of name-value data.</p>
 
   <p>The values within a group are alternatives; multiple paragraphs
   forming part of the same value must all be given within the same
   <code>dd</code> element.</p>
 
   <p>The order of the list of groups, and of the names and values
   within each group, may be significant.</p>
@@ -15895,98 +15844,78 @@ first matching case):&lt;/p&gt;
  &lt;dd>An execution context grouping one or more threads with one or
  more COM objects.&lt;/dd>
  &lt;dt>&lt;dfn>Flat&lt;/dfn>, n.&lt;/dt>
  &lt;dd>A deflated tire.&lt;/dd>
  &lt;dt>&lt;dfn>Home&lt;/dfn>, n.&lt;/dt>
  &lt;dd>The user's login directory.&lt;/dd>
 &lt;/dl></pre>
   </div>
 
   <p class="note">The <code>dl</code> element is inappropriate for
-  marking up dialogue. For an example of how to mark up dialogue, see
-  the <code>dialog</code> element.</p>
+  marking up dialogue. <a href="#conversations">Examples of how to
+  mark up dialogue</a> are shown below.</p>
 
 
   <h4>The <dfn><code>dt</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd>None.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Before <code>dd</code> or <code>dt</code> elements inside <code>dl</code> elements.</dd>
-   <dd>Before a <code>dd</code> element inside a <code>dialog</code> element.</dd>
+   <dd>As a child of a <code>figure</code> element.</dd>
+   <dd>As a child of a <code>details</code> element.</dd>
    <dt>Content model:</dt>
-   <dd><span>Phrasing content</span>.</dd>
+   <dd>When the parent node is a <code>figure</code> element: <span>flow content</span>, but with no descendant <code>figure</code> elements.</dd>
+   <dd>Otherwise: <span>phrasing content</span>.</dd>   
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dt>DOM interface:</dt>
    <dd>Uses <code>HTMLElement</code>.</dd>
   </dl>
 
-  <p>The <code>dt</code> element <span>represents</span> the term, or
-  name, part of a term-description group in a description list
-  (<code>dl</code> element), and the talker, or speaker, part of a
-  talker-discourse pair in a conversation (<code>dialog</code>
-  element).</p>
+  <p>The <code>dt</code> element <span>represents</span> either: the
+  term, or name, part of a term-description group in a description
+  list (<code>dl</code> element); or, the caption of a
+  <code>figure</code> element; or, the summary of a
+  <code>details</code> element.</p>
 
   <p class="note">The <code>dt</code> element itself, when used in a
   <code>dl</code> element, does not indicate that its contents are a
   term being defined, but this can be indicated using the
   <code>dfn</code> element.</p>
 
-  <p>If the <code>dt</code> element is the child of a
-  <code>dialog</code> element, and it further contains a
-  <code>time</code> element, then that <code>time</code> element
-  represents a timestamp for when the associated discourse
-  (<code>dd</code> element) was said, and is not part of the name of
-  the talker.</p>
 
-  <div class="example">
-
-   <p>The following extract shows how an IM conversation log could be
-   marked up.</p>
-
-   <pre>&lt;dialog>
- &lt;dt> &lt;time>14:22&lt;/time> egof
- &lt;dd> I'm not that nerdy, I've only seen 30% of the star trek episodes
- &lt;dt> &lt;time>14:23&lt;/time> kaj
- &lt;dd> if you know what percentage of the star trek episodes you have seen, you are inarguably nerdy
- &lt;dt> &lt;time>14:23&lt;/time> egof
- &lt;dd> it's unarguably
- &lt;dt> &lt;time>14:24&lt;/time> kaj
- &lt;dd> you are not helping your case
-&lt;/dialog></pre>
-   <!-- with thanks to http://bash.org/?854262 -->
-
-  </div>
 
 
   <h4>The <dfn><code>dd</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd>None.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>After <code>dt</code> or <code>dd</code> elements inside <code>dl</code> elements.</dd>
-   <dd>After a <code>dt</code> element inside a <code>dialog</code> element.</dd>
+   <dd>As a child of a <code>figure</code> element.</dd>
+   <dd>As a child of a <code>details</code> element.</dd>
    <dt>Content model:</dt>
    <dd><span>Flow content</span>.</dd>
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dt>DOM interface:</dt>
    <dd>Uses <code>HTMLElement</code>.</dd>
   </dl>
 
-  <p>The <code>dd</code> element <span>represents</span> the
+  <p>The <code>dt</code> element <span>represents</span> either: the
   description, definition, or value, part of a term-description group
-  in a description list (<code>dl</code> element), and the discourse,
-  or quote, part in a conversation (<code>dialog</code> element).</p>
+  in a description list (<code>dl</code> element); or, the data of a
+  <code>figure</code> element; or, the details of a
+  <code>details</code> element.</p>
 
   <div class="example">
 
    <p>A <code>dl</code> can be used to define a vocabulary list, like
    in a dictionary. In the following example, each entry, given by a
    <code>dt</code> with a <code>dfn</code>, has several
    <code>dd</code>s, showing the various parts of the definition.</p>
 
    <!-- the actual pronunciations below are nonsense. -->
    <pre>&lt;dl>
@@ -15996,75 +15925,20 @@ first matching case):&lt;/p&gt;
  &lt;dd>The state of being happy.&lt;/dd>
  &lt;dd>Good fortune; success. &lt;q>Oh &lt;b>happiness&lt;/b>! It worked!&lt;/q>&lt;/dd>
  &lt;dt>&lt;dfn>rejoice&lt;/dfn>&lt;/dt>
  &lt;dd class="pronunciation">/ri jois'/&lt;/dd>
  &lt;dd>&lt;i class="part-of-speech">&lt;abbr>v.intr.&lt;/abbr>&lt;/i> To be delighted oneself.&lt;/dd>
  &lt;dd>&lt;i class="part-of-speech">&lt;abbr>v.tr.&lt;/abbr>&lt;/i> To cause one to be delighted.&lt;/dd>
 &lt;/dl></pre>
   </div>
 
 
-  <h4>Common grouping idioms</h4>
-
-  <h5>Tag clouds</h5>
-
-  <p id="tag-cloud">This specification does not define any markup
-  specifically for marking up lists of keywords that apply to a group
-  of pages (also known as <i>tag clouds</i>). In general, authors are
-  encouraged to either mark up such lists using <code>ul</code>
-  elements with explicit inline counts that are then hidden and turned
-  into a presentational effect using a style sheet, or to use SVG.</p>
-
-  <div class="example">
-
-   <p>Here, three tags are included in a short tag cloud:</p>
-
-   <pre>&lt;style>
-@media screen, print, handheld, tv {
-  /* should be ignored by non-visual browsers */
-  .tag-cloud > li > span { display: none; }
-  .tag-cloud > li { display: inline; }
-  .tag-cloud-1 { font-size: 0.7em; }
-  .tag-cloud-2 { font-size: 0.9em; }
-  .tag-cloud-3 { font-size: 1.1em; }
-  .tag-cloud-4 { font-size: 1.3em; }
-  .tag-cloud-5 { font-size: 1.5em; }
-}
-&lt;/style>
-...
-&lt;ul class="tag-cloud">
- &lt;li class="tag-cloud-4">&lt;a title="28 instances" href="/t/apple">apple&lt;/a> &lt;span>(popular)&lt;/span>
- &lt;li class="tag-cloud-2">&lt;a title="6 instances"  href="/t/kiwi">kiwi&lt;/a> &lt;span>(rare)&lt;/span>
- &lt;li class="tag-cloud-5">&lt;a title="41 instances" href="/t/pear">pear&lt;/a> &lt;span>(very popular)&lt;/span>
-&lt;/ul></pre>
-
-   <p>The actual frequency of each tag is given using the <code
-   title="attr-title">title</code> attribute. A CSS style sheet is
-   provided to convert the markup into a cloud of differently-sized
-   words, but for user agents that do not support CSS or are not
-   visual, the markup contains annotations like "(popular)" or
-   "(rare)" to categorize the various tags by frequency, thus enabling
-   all users to benefit from the information.</p>
-
-   <p>The <code>ul</code> element is used (rather than
-   <code>ol</code>) because the order is not particular important:
-   while the list is in fact ordered alphabetically, it would convey
-   the same information if ordered by, say, the length of the tag.</p>
-
-   <p>The <code title="rel-tag">tag</code> <code
-   title="attr-hyperlink-rel">rel</code>-keyword is <em>not</em> used
-   on these <code>a</code> elements because they do not represent tags
-   that apply to the page itself; they are just part of an index
-   listing the tags themselves.</p>
-
-  </div>
-
 
 
   <h3>Text-level semantics</h3>
 
   <h4>The <dfn><code>a</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
    <dd>When the element only contains <span>phrasing content</span>: <span>phrasing content</span>.</dd>
@@ -17357,33 +17231,35 @@ flavors of ice cream to be available for purchase!&lt;/p></pre>
   variables that are then mentioned in MathML expressions.</p>
 
   <div class="example">
 
    <p>In this example, an equation is shown, with a legend that
    references the variables in the equation. The expression itself is
    marked up with MathML, but the variables are mentioned in the
    figure's legend using <code>var</code>.</p>
 
    <pre>&lt;figure>
- &lt;math>
-  &lt;mi>a&lt;/mi>
-  &lt;mo>=&lt;/mo>
-  &lt;msqrt>
-   &lt;msup>&lt;mi>b&lt;/mi>&lt;mn>2&lt;/mn>&lt;/msup>
-   &lt;mi>+&lt;/mi>
-   &lt;msup>&lt;mi>c&lt;/mi>&lt;mn>2&lt;/mn>&lt;/msup>
-  &lt;/msqrt>
- &lt;/math>
- &lt;legend>
+ &lt;dd>
+  &lt;math>
+   &lt;mi>a&lt;/mi>
+   &lt;mo>=&lt;/mo>
+   &lt;msqrt>
+    &lt;msup>&lt;mi>b&lt;/mi>&lt;mn>2&lt;/mn>&lt;/msup>
+    &lt;mi>+&lt;/mi>
+    &lt;msup>&lt;mi>c&lt;/mi>&lt;mn>2&lt;/mn>&lt;/msup>
+   &lt;/msqrt>
+  &lt;/math>
+ &lt;/dd>
+ &lt;dt>
   Using Pythagoras' theorem to solve for the hypotenuse &lt;var>a&lt;/var> of
   a triangle with sides &lt;var>b&lt;/var> and &lt;var>c&lt;/var>
- &lt;/legend>
+ &lt;/dt>
 &lt;/figure></pre>
 
   </div>
 
 
   <h4>The <dfn><code>samp</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
@@ -18936,146 +18812,20 @@ and a height of &lt;meter>2cm&lt;/meter>.&lt;/p> &lt;!-- <strong>BAD!</strong> -
      <td><pre class="example">The proposal is to write English, but in reverse order. "Juice" would become "<strong>&lt;bdo dir=rtl>Juice&lt;/bdo></strong>"</pre>
 
     <tr>
      <td><code>span</code>
      <td>Other
      <td><pre class="example">In French we call it <strong>&lt;span lang="fr">sirop de sureau&lt;/span></strong>.</pre>
 
   </table>
 
 
-  <h4 id="footnotes">Footnotes</h4>
-
-  <p>HTML does not have a dedicated mechanism for marking up
-  footnotes. Here are the recommended alternatives.</p>
-
-  <p>For short inline annotations, the <code
-  title="attr-title">title</code> attribute should be used.</p>
-
-  <div class="example">
-
-   <p>In this example, two parts of a dialog are annotated.</p>
-
-   <pre>&lt;dialog>
- &lt;dt>Customer
- &lt;dd>Hello! I wish to register a complaint. Hello. Miss?
- &lt;dt>Shopkeeper
- &lt;dd>&lt;span title="Colloquial pronunciation of 'What do you'"
- >Watcha&lt;/span> mean, miss?
- &lt;dt>Customer
- &lt;dd>Uh, I'm sorry, I have a cold. I wish to make a complaint.
- &lt;dt>Shopkeeper
- &lt;dd>Sorry, &lt;span title="This is, of course, a lie.">we're
- closing for lunch&lt;/span>.
-&lt;/dialog></pre>
-
-  </div>
-
-  <p>For longer annotations, the <code>a</code> element should be
-  used, pointing to an element later in the document. The convention
-  is that the contents of the link be a number in square brackets.</p>
-
-  <div class="example">
-
-   <p>In this example, a footnote in the dialog links to a paragraph
-   below the dialog. The paragraph then reciprocally links back to the
-   dialog, allowing the user to return to the location of the
-   footnote.</p>
-
-   <pre>&lt;dialog>
- &lt;dt>Announcer
- &lt;dd>Number 16: The &lt;i>hand&lt;/i>.
- &lt;dt>Interviewer
- &lt;dd>Good evening. I have with me in the studio tonight Mr
- Norman St John Polevaulter, who for the past few years has
- been contradicting people. Mr Polevaulter, why &lt;em>do&lt;/em>
- you contradict people?
- &lt;dt>Norman
- &lt;dd>I don't. &lt;a href="#fn1" id="r1">[1]&lt;/a>
- &lt;dt>Interviewer
- &lt;dd>You told me you did!
-&lt;/dialog>
-&lt;section>
- &lt;p id="fn1">&lt;a href="#r1">[1]&lt;/a> This is, naturally, a lie,
- but paradoxically if it were true he could not say so without
- contradicting the interviewer and thus making it false.&lt;/p>
-&lt;/section></pre>
-
-  </div>
-
-  <p>For side notes, longer annotations that apply to entire sections
-  of the text rather than just specific words or sentences, the
-  <code>aside</code> element should be used.</p>
-
-  <div class="example">
-
-   <p>In this example, a sidebar is given after a dialog, giving some
-   context to the dialog.</p>
-
-   <pre>&lt;dialog>
- &lt;dt>Customer
- &lt;dd>I will not buy this record, it is scratched.
- &lt;dt>Shopkeeper
- &lt;dd>I'm sorry?
- &lt;dt>Customer
- &lt;dd>I will not buy this record, it is scratched.
- &lt;dt>Shopkeeper
- &lt;dd>No no no, this's'a tobacconist's.
-&lt;/dialog>
-&lt;aside>
- &lt;p>In 1970, the British Empire lay in ruins, and foreign
- nationalists frequented the streets &mdash; many of them Hungarians
- (not the streets &mdash; the foreign nationals). Sadly, Alexander
- Yalt has been publishing incompetently-written phrase books.
-&lt;/aside></pre>
-
-  </div>
-
-  <p>For figures or tables, footnotes can be included in the relevant
-  <code>legend</code> or <code>caption</code> element, or in
-  surrounding prose.</p>
-
-  <div class="example">
-
-   <p>In this example, a <!-- round --> table has cells with footnotes
-   that are given in prose. A <code>figure</code> element is used to
-   give a single legend to the combination of the table and its
-   footnotes.</p>
-
-   <pre>&lt;figure>
- &lt;legend>Table 1. Alternative activities for knights.&lt;/legend>
- &lt;table>
-  &lt;tr>
-   &lt;th> Activity
-   &lt;th> Location
-   &lt;th> Cost
-  &lt;tr>
-   &lt;td> Dance
-   &lt;td> Wherever possible
-   &lt;td> &#x00A3;0&lt;sup>&lt;a href="#fn1">1&lt;/a>&lt;/sup>
-  &lt;tr>
-   &lt;td> Routines, chorus scenes&lt;sup>&lt;a href="#fn2">2&lt;/a>&lt;/sup>
-   &lt;td> Undisclosed
-   &lt;td> Undisclosed
-  &lt;tr>
-   &lt;td> Dining&lt;sup>&lt;a href="#fn3">3&lt;/a>&lt;/sup>
-   &lt;td> Camelot
-   &lt;td> Cost of ham, jam, and spam&lt;sup>&lt;a href="#fn4">4&lt;/a>&lt;/sup>
- &lt;/table>
- &lt;p id="fn1">1. Assumed.&lt;/p>
- &lt;p id="fn2">2. Footwork impeccable.&lt;/p>
- &lt;p id="fn3">3. Quality described as "well".&lt;/p>
- &lt;p id="fn4">4. A lot.&lt;/p>
-&lt;/figure></pre>
-
-  </div>
-
 
 
   <h3>Edits</h3>
 
   <p>The <code>ins</code> and <code>del</code> elements represent
   edits to the document.</p>
 
 
   <h4>The <dfn><code>ins</code></dfn> element</h4>
 
@@ -19391,142 +19141,152 @@ and a height of &lt;meter>2cm&lt;/meter>.&lt;/p> &lt;!-- <strong>BAD!</strong> -
 
   <h4>The <dfn><code>figure</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
    <dd><span>Sectioning root</span>.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>flow content</span> is expected.</dd>
    <dt>Content model:</dt>
-   <dd>Either: one <code>legend</code> element followed by <span>flow content</span>.</dd>
-   <dd>Or: <span>Flow content</span> followed by one <code>legend</code> element.</dd>
-   <dd>Or: <span>Flow content</span>.</dd>
+   <dd>In any order, one <code>dd</code> element, and optionally one <code>dt</code> element.</dd>
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dt>DOM interface:</dt>
    <dd>Uses <code>HTMLElement</code>.</dd>
   </dl>
 
-  <!-- v2: Add a <credit> element for photo credits -->
+  <!-- v2: Add a <dc> or <credit> element for photo credits -->
 
   <p>The <code>figure</code> element <span>represents</span> some
   <span>flow content</span>, optionally with a caption, that is
   self-contained and is typically referenced as a single unit from the
   main flow of the document.</p>
 
   <p>The element can thus be used to annotate illustrations, diagrams,
   photos, code listings, etc, that are referred to from the main
   content of the document, but that could, without affecting the flow
   of the document, be moved away from that primary content, e.g. to
   the side of the page, to dedicated pages, or to an appendix.</p>
 
-  <p>The first <code>legend</code> element child of the element, if
-  any, represents the caption of the <code>figure</code> element's
-  contents. If there is no child <code>legend</code> element, then
-  there is no caption.</p>
+  <p>The <span class="impl">first</span> <code>dt</code> element child
+  of the element, if any, represents the caption of the
+  <code>figure</code> element's contents. If there is no child
+  <code>dt</code> element, then there is no caption.</p>
 
-  <p>The remainder of the element's contents, if any, represents the
-  content.</p>
+  <p>The <span class="impl">first</span> <code>dd</code> element child
+  of the element<span class="impl">, if any,</span> represents the
+  element's contents. <span class="impl">If there is no child
+  <code>dd</code> element, then there is no caption.</span></p>
 
   <div class="example">
 
    <p>This example shows the <code>figure</code> element to mark up a
    code listing.</p>
 
    <pre>&lt;p>In &lt;a href="#l4">listing 4&lt;/a> we see the primary core interface
 API declaration.&lt;/p>
 &lt;figure id="l4">
- &lt;legend>Listing 4. The primary core interface API declaration.&lt;/legend>
- &lt;pre>&lt;code>interface PrimaryCore {
+ &lt;dt>Listing 4. The primary core interface API declaration.&lt;/dt>
+ &lt;dd>
+  &lt;pre>&lt;code>interface PrimaryCore {
   boolean verifyDataLine();
   void sendData(in sequence&amp;lt;byte> data);
   void initSelfDestruct();
 }&lt;/code>&lt;/pre>
+ &lt;/dd>
 &lt;/figure>
 &lt;p>The API is designed to use UTF-8.&lt;/p></pre>
 
   </div>
 
   <div class="example">
 
    <p>Here we see a <code>figure</code> element to mark up a
    photo.</p>
 
    <pre>&lt;figure>
- &lt;img src="bubbles-work.jpeg"
-      alt="Bubbles, sitting in his office chair, works on his
-           latest project intently.">
- &lt;legend>Bubbles at work&lt;/legend>
+ &lt;dd>
+  &lt;img src="bubbles-work.jpeg"
+       alt="Bubbles, sitting in his office chair, works on his
+            latest project intently.">
+ &lt;/dd>
+ &lt;dt>Bubbles at work&lt;/dt>
 &lt;/figure></pre>
 
   </div>
 
   <div class="example">
 
    <p>In this example, we see an image that is <em>not</em>
    a figure, as well as an image and a video that are.</p>
 
    <pre>&lt;h2>Malinko's comics&lt;/h2>
 
 &lt;p>This case centered on some sort of "intellectual property"
 infringement related to a comic (see Exhibit A). The suit started
-after a trailer ending with these words:&lt;/p>
+after a trailer ending with these words:
 
-&lt;img src="promblem-packed-action.png" alt="ROUGH COPY! Promblem-Packed Action!">
+&lt;blockquote>
+ &lt;img src="promblem-packed-action.png" alt="ROUGH COPY! Promblem-Packed Action!">
+&lt;/blockquote>
 
 &lt;p>...was aired. A lawyer, armed with a Bigger Notebook, launched a
 preemptive strike using snowballs. A complete copy of the trailer is
-included with Exhibit B.&lt;/p>
+included with Exhibit B.
 
 &lt;figure>
- &lt;img src="ex-a.png" alt="Two squiggles on a dirty piece of paper.">
- &lt;legend>Exhibit A. The alleged &lt;cite>rough copy&lt;/cite> comic.&lt;/legend>
+ &lt;dd>&lt;img src="ex-a.png" alt="Two squiggles on a dirty piece of paper.">
+ &lt;dt>Exhibit A. The alleged &lt;cite>rough copy&lt;/cite> comic.
 &lt;/figure>
 
 &lt;figure>
- &lt;video src="ex-b.mov">&lt;/video>
- &lt;legend>Exhibit B. The &lt;cite>Rough Copy&lt;/cite> trailer.&lt;/legend>
+ &lt;dd>&lt;video src="ex-b.mov">&lt;/video>
+ &lt;dt>Exhibit B. The &lt;cite>Rough Copy&lt;/cite> trailer.
 &lt;/figure>
 
-&lt;p>The case was resolved out of court.&lt;/p></pre>
+&lt;p>The case was resolved out of court.</pre>
 
   </div>
 
   <div class="example">
 
    <p>Here, a part of a poem is marked up using
    <code>figure</code>.</p>
 
    <pre>&lt;figure>
- &lt;p>'Twas brillig, and the slithy toves&lt;br>
-Did gyre and gimble in the wabe;&lt;br>
-All mimsy were the borogoves,&lt;br>
-And the mome raths outgrabe.&lt;/p>
- &lt;legend>&lt;cite>Jabberwocky&lt;/cite> (first verse). Lewis Carroll, 1832-98&lt;/legend>
+ &lt;dd>
+  &lt;p>'Twas brillig, and the slithy toves&lt;br>
+  Did gyre and gimble in the wabe;&lt;br>
+  All mimsy were the borogoves,&lt;br>
+  And the mome raths outgrabe.&lt;/p>
+ &lt;/dd>
+ &lt;dt>&lt;cite>Jabberwocky&lt;/cite> (first verse). Lewis Carroll, 1832-98&lt;/dt>
 &lt;/figure></pre>
 
   </div>
 
   <div class="example">
 
    <p>In this example, which could be part of a much larger work
    discussing a castle, the figure has three images in it.</p>
 
    <pre>&lt;figure>
- &lt;img src="castle1423.jpeg" title="Etching. Anonymous, ca. 1423."
-      alt="The castle has one tower, and a tall wall around it.">
- &lt;img src="castle1858.jpeg" title="Oil-based paint on canvas. Maria Towle, 1858."
-      alt="The castle now has two towers and two walls.">
- &lt;img src="castle1999.jpeg" title="Film photograph. Peter Jankle, 1999."
-      alt="The castle lies in ruins, the original tower all that remains in one piece.">
- &lt;legend>The castle through the ages: 1423, 1858, and 1999 respectively.&lt;/legend>
+ &lt;dd>
+  &lt;img src="castle1423.jpeg" title="Etching. Anonymous, ca. 1423."
+       alt="The castle has one tower, and a tall wall around it.">
+  &lt;img src="castle1858.jpeg" title="Oil-based paint on canvas. Maria Towle, 1858."
+       alt="The castle now has two towers and two walls.">
+  &lt;img src="castle1999.jpeg" title="Film photograph. Peter Jankle, 1999."
+       alt="The castle lies in ruins, the original tower all that remains in one piece.">
+ &lt;/dd>
+ &lt;dt>The castle through the ages: 1423, 1858, and 1999 respectively.&lt;/dt>
 &lt;/figure></pre>
 
   </div>
 
 
   <h4>The <dfn><code>img</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
@@ -19815,22 +19575,22 @@ interface <dfn>HTMLImageElement</dfn> : <span>HTMLElement</span> {
     for the image, derived as follows:</p>
 
     <ol>
 
      <li><p>If the image has a <code title="attr-title">title</code>
      attribute whose value is not the empty string, then the value of
      that attribute is the caption information; abort these
      steps.</p></li>
 
      <li><p>If the image is the child of a <code>figure</code> element
-     that has a child <code>legend</code> element, then the contents
-     of the first such <code>legend</code> element are the caption
+     that has a child <code>dt</code> element, then the contents of
+     the first such <code>dt</code> element are the caption
      information; abort these steps.</p></li>
 
      <li><p>Run the algorithm to create the <span>outline</span> for
      the document.</p></li>
 
      <li><p>If the <code>img</code> element did not end up associated
      with a heading in the outline, or if there are any other images
      that are lacking an <code title="attr-img-alt">alt</code>
      attribute and that are associated with the same heading in the
      outline as the <code>img</code> element in question, then there
@@ -20254,21 +20014,21 @@ document.write(), passes data to the Tokenizer."></strong>&lt;/p></pre>
    <pre class="bad">&lt;!-- <em>This is the wrong way to do things.</em> -->
 &lt;p>
  You are standing in an open field west of a house.
  &lt;img src="house.jpeg" alt="A white house, with a boarded front door.">
  There is a small mailbox here.
 &lt;/p></pre>
 
    <p>Text such as "Photo of white house with boarded door" would be
    equally bad alternative text (though it could be suitable for the
    <code title="attr-title">title</code> attribute or in the
-   <code>legend</code> element of a <code>figure</code> with this
+   <code>dt</code> element of a <code>figure</code> with this
    image).</p>
 
   </div>
 
 
   <h6>A short phrase or label with an alternative graphical representation: icons, logos</h6>
 
   <p>A document can contain information in iconic form. The icon is
   intended to help users of visual browsers to recognize features at
   a glance.</p>
@@ -20443,48 +20203,50 @@ at least that would look good on the cover of a blue book.&lt;/p></pre>
    <pre>&lt;p>The network passes data to the Tokenizer stage, which
 passes data to the Tree Construction stage. From there, data goes
 to both the DOM and to Script Execution. Script Execution is
 linked to the DOM, and, using document.write(), passes data to
 the Tokenizer.&lt;/p>
 <strong>&lt;p>&lt;img src="images/parsing-model-overview.png" alt="">&lt;/p></strong></pre>
 
    <p>In these cases, it would be wrong to include alternative text
    that consists of just a caption. If a caption is to be included,
    then either the <code title="attr-title">title</code> attribute can
-   be used, or the <code>figure</code> and <code>legend</code>
-   elements can be used. In the latter case, the image would in fact
-   be a phrase or paragraph with an alternative graphical
-   representation, and would thus require alternative text.</p>
+   be used, or the <code>figure</code> and <code>dt</code> elements
+   can be used. In the latter case, the image would in fact be a
+   phrase or paragraph with an alternative graphical representation,
+   and would thus require alternative text.</p>
 
    <pre>&lt;!-- Using the title="" attribute -->
 &lt;p>The network passes data to the Tokenizer stage, which
 passes data to the Tree Construction stage. From there, data goes
 to both the DOM and to Script Execution. Script Execution is
 linked to the DOM, and, using document.write(), passes data to
 the Tokenizer.&lt;/p>
 &lt;p><strong>&lt;img src="images/parsing-model-overview.png" alt=""
         title="Flowchart representation of the parsing model."></strong>&lt;/p></pre>
 
-   <pre>&lt;!-- Using &lt;figure> and &lt;legend> -->
+   <pre>&lt;!-- Using &lt;figure> and &lt;dt> -->
 &lt;p>The network passes data to the Tokenizer stage, which
 passes data to the Tree Construction stage. From there, data goes
 to both the DOM and to Script Execution. Script Execution is
 linked to the DOM, and, using document.write(), passes data to
 the Tokenizer.&lt;/p>
 &lt;figure>
- <strong>&lt;img src="images/parsing-model-overview.png" alt="The Network leads
- to the Tokenizer, which leads to the Tree Construction. The Tree
- Construction leads to two items. The first is Script Execution, which
- leads via document.write() back to the Tokenizer. The second item
- from which Tree Construction leads is the DOM. The DOM is related to
- the Script Execution."></strong>
- &lt;legend>Flowchart representation of the parsing model.&lt;/legend>
+ &lt;dd>
+  <strong>&lt;img src="images/parsing-model-overview.png" alt="The Network leads
+  to the Tokenizer, which leads to the Tree Construction. The Tree
+  Construction leads to two items. The first is Script Execution, which
+  leads via document.write() back to the Tokenizer. The second item
+  from which Tree Construction leads is the DOM. The DOM is related to
+  the Script Execution."></strong>
+ &lt;/dd>
+ &lt;dt>Flowchart representation of the parsing model.&lt;/dt>
 &lt;/figure></pre>
 
    <pre class="bad">&lt;!-- This is WRONG. Do not do this. Instead, do what the above examples do. -->
 &lt;p>The network passes data to the Tokenizer stage, which
 passes data to the Tree Construction stage. From there, data goes
 to both the DOM and to Script Execution. Script Execution is
 linked to the DOM, and, using document.write(), passes data to
 the Tokenizer.&lt;/p>
 &lt;p>&lt;img src="images/parsing-model-overview.png"
         alt="Flowchart representation of the parsing model.">&lt;/p>
@@ -20635,31 +20397,33 @@ Noodliness do you wish to reach out for?&lt;/p>
     a photograph in a blog entry about that photograph, text that can
     serve as a substitute for the image must be given as the contents
     of the <code title="attr-img-alt">alt</code> attribute.</p>
 
     <div class="example">
 
      <p>A screenshot in a gallery of screenshots for a new OS, with
      some alternative text:</p>
 
      <pre>&lt;figure>
- <strong>&lt;img src="KDE%20Light%20desktop.png"
-      alt="The desktop is blue, with icons along the left hand side in
-           two columns, reading System, Home, K-Mail, etc. A window is
-           open showing that menus wrap to a second line if they
-           cannot fit in the window. The window has a list of icons
-           along the top, with an address bar below it, a list of
-           icons for tabs along the left edge, a status bar on the
-           bottom, and two panes in the middle. The desktop has a bar
-           at the bottom of the screen with a few buttons, a pager, a
-           list of open applications, and a clock."></strong>
- &lt;legend>Screenshot of a KDE desktop.&lt;/legend>
+ &lt;dd>
+  <strong>&lt;img src="KDE%20Light%20desktop.png"
+       alt="The desktop is blue, with icons along the left hand side in
+            two columns, reading System, Home, K-Mail, etc. A window is
+            open showing that menus wrap to a second line if they
+            cannot fit in the window. The window has a list of icons
+            along the top, with an address bar below it, a list of
+            icons for tabs along the left edge, a status bar on the
+            bottom, and two panes in the middle. The desktop has a bar
+            at the bottom of the screen with a few buttons, a pager, a
+            list of open applications, and a clock."></strong>
+ &lt;/dd>
+ &lt;dt>Screenshot of a KDE desktop.&lt;/dt>
 &lt;/figure></pre>
 
     </div>
 
     <div class="example">
 
      <p>A graph in a financial report:</p>
 
      <pre><strong>&lt;img src="sales.gif"
      title="Sales graph"
@@ -20689,39 +20453,39 @@ Noodliness do you wish to reach out for?&lt;/p>
     be somewhat brief.</p>
 
     <div class="example">
 
      <p>Sometimes there simply is no text that can do justice to an
      image. For example, there is little that can be said to usefully
      describe a Rorschach inkblot test. However, a description, even
      if brief, is still better than nothing:</p>
 
      <pre>&lt;figure>
- <strong>&lt;img src="/commons/a/a7/Rorschach1.jpg" alt="A shape with left-right
+ &lt;dd><strong>&lt;img src="/commons/a/a7/Rorschach1.jpg" alt="A shape with left-right
  symmetry with indistinct edges, with a small gap in the center, two
  larger gaps offset slightly from the center, with two similar gaps
  under them. The outline is wider in the top half than the bottom
  half, with the sides extending upwards higher than the center, and
- the center extending below the sides."></strong>
- &lt;legend>A black outline of the first of the ten cards
- in the Rorschach inkblot test.&lt;/legend>
+ the center extending below the sides."></strong>&lt;/dd>
+ &lt;dt>A black outline of the first of the ten cards
+ in the Rorschach inkblot test.&lt;/dt>
 &lt;/figure></pre>
 
      <p>Note that the following would be a very bad use of alternative
      text:</p>
 
      <pre class="bad">&lt;!-- This example is wrong. Do not copy it. -->
 &lt;figure>
- &lt;img src="/commons/a/a7/Rorschach1.jpg" alt="A black outline
- of the first of the ten cards in the Rorschach inkblot test.">
- &lt;legend>A black outline of the first of the ten cards
- in the Rorschach inkblot test.&lt;/legend>
+ &lt;dd>&lt;img src="/commons/a/a7/Rorschach1.jpg" alt="A black outline
+ of the first of the ten cards in the Rorschach inkblot test.">&lt;/dd>
+ &lt;dt>A black outline of the first of the ten cards
+ in the Rorschach inkblot test.&lt;/dt>
 &lt;/figure></pre>
 
      <p>Including the caption in the alternative text like this isn't
      useful because it effectively duplicates the caption for users
      who don't have images, taunting them twice yet not helping them
      any more than if they had only read or heard the caption
      once.</p>
 
     </div>
 
@@ -20761,21 +20525,21 @@ of various sizes."></strong></pre>
     <p>In such cases, the <code title="attr-img-alt">alt</code>
     attribute's value may be omitted, but one of the following
     conditions must be met as well:</p>
 
     <ul>
 
      <li>The <code title="attr-title">title</code> attribute is
      present and has a non-empty value.</li>
 
      <li>The <code>img</code> element is in a <code>figure</code>
-     element that contains a <code>legend</code> element that contains
+     element that contains a <code>dt</code> element that contains
      content other than <span>inter-element whitespace</span>.</li>
 
      <li>The <code>img</code> element is part of the only
      <span>paragraph</span> directly in its <span
      title="concept-section">section</span>, and is the only
      <code>img</code> element without an <code
      title="attr-img-alt">alt</code> attribute in its section, and its
      <span title="concept-section">section</span> has an associated
      heading.</li>
 
@@ -20786,22 +20550,22 @@ of various sizes."></strong></pre>
     having the ability to provide real alternative text, then it would
     not be acceptable to omit the <code title="attr-img-alt">alt</code>
     attribute.</p>
 
     <div class="example">
 
      <p>A photo on a photo-sharing site, if the site received the
      image with no metadata other than the caption:</p>
 
      <pre>&lt;figure>
- <strong>&lt;img src="1100670787_6a7c664aef.jpg"></strong>
- &lt;legend>Bubbles traveled everywhere with us.&lt;/legend>
+ &lt;dd><strong>&lt;img src="1100670787_6a7c664aef.jpg"></strong>&lt;/dd>
+ &lt;dt>Bubbles traveled everywhere with us.&lt;/dt>
 &lt;/figure></pre>
 
      <p>It could also be marked up like this:</p>
 
      <pre>&lt;article>
  &lt;h1>Bubbles traveled everywhere with us.&lt;/h1>
  <strong>&lt;img src="1100670787_6a7c664aef.jpg"></strong>
 &lt;/article></pre>
 
      <p>In either case, though, it would be better if a detailed
@@ -20813,39 +20577,39 @@ of various sizes."></strong></pre>
     <div class="example">
 
      <p>A blind user's blog in which a photo taken by the user is
      shown. Initially, the user might not have any idea what the photo
      he took shows:</p>
 
      <pre>&lt;article>
  &lt;h1>I took a photo&lt;/h1>
  &lt;p>I went out today and took a photo!&lt;/p>
  &lt;figure>
-  <strong>&lt;img src="photo2.jpeg"></strong>
-  &lt;legend>A photograph taken blindly from my front porch.&lt;/legend>
+  &lt;dd><strong>&lt;img src="photo2.jpeg"></strong>&lt;/dd>
+  &lt;dt>A photograph taken blindly from my front porch.&lt;/dt>
  &lt;/figure>
 &lt;/article></pre>
 
      <p>Eventually though, the user might obtain a description of the
      image from his friends and could then include alternative text:</p>
 
      <pre>&lt;article>
  &lt;h1>I took a photo&lt;/h1>
  &lt;p>I went out today and took a photo!&lt;/p>
  &lt;figure>
-  <strong>&lt;img src="photo2.jpeg" alt="The photograph shows my hummingbird
+  &lt;dd><strong>&lt;img src="photo2.jpeg" alt="The photograph shows my hummingbird
   feeder hanging from the edge of my roof. It is half full, but there
   are no birds around. In the background, out-of-focus trees fill the
   shot. The feeder is made of wood with a metal grate, and it contains
   peanuts. The edge of the roof is wooden too, and is painted white
-  with light blue streaks."></strong>
-  &lt;legend>A photograph taken blindly from my front porch.&lt;/legend>
+  with light blue streaks."></strong>&lt;/dd>
+  &lt;dt>A photograph taken blindly from my front porch.&lt;/dt>
  &lt;/figure>
 &lt;/article></pre>
 
     </div>
 
     <div class="example">
 
      <p>Sometimes the entire point of the image is that a textual
      description is not available, and the user is to provide the
      description. For instance, the point of a CAPTCHA image is to see
@@ -22377,37 +22141,39 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
 
    <p>In the following example, a Java applet is embedded in a page
    using the <code>object</code> element. (Generally speaking, it is
    better to avoid using applets like these and instead use native
    JavaScript and HTML to provide the functionality, since that way
    the application will work on all Web browsers without requiring a
    third-party plugin. Many devices, especially embedded devices, do
    not support third-party technologies like Java.)</p>
 
    <pre>&lt;figure>
- &lt;object type="application/x-java-applet">
-  &lt;param name="code" value="MyJavaClass">
-  &lt;p>You do not have Java available, or it is disabled.&lt;/p>
- &lt;/object>
- &lt;legend>My Java Clock&lt;/legend>
+ &lt;dd>
+  &lt;object type="application/x-java-applet">
+   &lt;param name="code" value="MyJavaClass">
+   &lt;p>You do not have Java available, or it is disabled.&lt;/p>
+  &lt;/object>
+ &lt;/dd>
+ &lt;dt>My Java Clock&lt;/dt>
 &lt;/figure></pre>
 
   </div>
 
   <div class="example">
 
    <p>In this example, an HTML page is embedded in another using the
    <code>object</code> element.</p>
 
    <pre>&lt;figure>
- &lt;object data="clock.html">&lt;/object>
- &lt;legend>My HTML Clock&lt;/legend>
+ &lt;dd>&lt;object data="clock.html">&lt;/object>
+ &lt;dt>My HTML Clock
 &lt;/figure></pre>
 
   </div>
 
 
 
   <h4>The <dfn><code>param</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
@@ -30727,24 +30493,26 @@ side in the right column.&lt;/p>
 &lt;/table></pre></div>
    </dd>
 
    <dt>In the table's <code>caption</code>, in a <code>details</code> element</dt>
 
    <dd>
     <div class="example"><pre>&lt;table>
  &lt;caption>
   &lt;strong>Characteristics with positive and negative sides.&lt;/strong>
   &lt;details>
-   &lt;legend>Help&lt;/legend>
-   &lt;p>Characteristics are given in the second column, with the
-   negative side in the left column and the positive side in the right
-   column.&lt;/p>
+   &lt;dt>Help&lt;/dt>
+   &lt;dd>
+    &lt;p>Characteristics are given in the second column, with the
+    negative side in the left column and the positive side in the right
+    column.&lt;/p>
+   &lt;/dd>
   &lt;/details>
  &lt;/caption>
  &lt;thead>
   &lt;tr>
    &lt;th id="n"> Negative
    &lt;th> Characteristic
    &lt;th> Positive
  &lt;tbody>
   &lt;tr>
    &lt;td headers="n r1"> Sad
@@ -30754,71 +30522,75 @@ side in the right column.&lt;/p>
    &lt;td headers="n r2"> Failing
    &lt;th id="r2"> Grade
    &lt;td> Passing
 &lt;/table></pre></div>
    </dd>
 
    <dt>Next to the table, in the same <code>figure</code></dt>
 
    <dd>
     <div class="example"><pre>&lt;figure>
- &lt;legend>Characteristics with positive and negative sides&lt;/legend>
- &lt;p>Characteristics are given in the second
- column, with the negative side in the left column and the positive
- side in the right column.&lt;/p>
- &lt;table>
-  &lt;thead>
-   &lt;tr>
-    &lt;th id="n"> Negative
-    &lt;th> Characteristic
-    &lt;th> Positive
-  &lt;tbody>
-   &lt;tr>
-    &lt;td headers="n r1"> Sad
-    &lt;th id="r1"> Mood
-    &lt;td> Happy
-   &lt;tr>
-    &lt;td headers="n r2"> Failing
-    &lt;th id="r2"> Grade
-    &lt;td> Passing
- &lt;/table>
-&lt;figure>
+ &lt;dt>Characteristics with positive and negative sides&lt;/dt>
+ &lt;dd>
+  &lt;p>Characteristics are given in the second column, with the
+  negative side in the left column and the positive side in the right
+  column.&lt;/p>
+  &lt;table>
+   &lt;thead>
+    &lt;tr>
+     &lt;th id="n"> Negative
+     &lt;th> Characteristic
+     &lt;th> Positive
+   &lt;tbody>
+    &lt;tr>
+     &lt;td headers="n r1"> Sad
+     &lt;th id="r1"> Mood
+     &lt;td> Happy
+    &lt;tr>
+     &lt;td headers="n r2"> Failing
+     &lt;th id="r2"> Grade
+     &lt;td> Passing
+  &lt;/table>
+ &lt;/dd>
+&lt;/figure>
 </pre></div>
    </dd>
 
-   <dt>Next to the table, in a <code>figure</code>'s <code>legend</code></dt>
+   <dt>Next to the table, in a <code>figure</code>'s <code>dt</code></dt>
 
    <dd>
     <div class="example"><pre>&lt;figure>
- &lt;legend>
+ &lt;dt>
   &lt;strong>Characteristics with positive and negative sides&lt;/strong>
-  &lt;p>Characteristics are given in the second
-  column, with the negative side in the left column and the positive
-  side in the right column.&lt;/p>
- &lt;/legend>
- &lt;table>
-  &lt;thead>
-   &lt;tr>
-    &lt;th id="n"> Negative
-    &lt;th> Characteristic
-    &lt;th> Positive
-  &lt;tbody>
-   &lt;tr>
-    &lt;td headers="n r1"> Sad
-    &lt;th id="r1"> Mood
-    &lt;td> Happy
-   &lt;tr>
-    &lt;td headers="n r2"> Failing
-    &lt;th id="r2"> Grade
-    &lt;td> Passing
- &lt;/table>
-&lt;figure>
+  &lt;p>Characteristics are given in the second column, with the
+  negative side in the left column and the positive side in the right
+  column.&lt;/p>
+ &lt;/dt>
+ &lt;dd>
+  &lt;table>
+   &lt;thead>
+    &lt;tr>
+     &lt;th id="n"> Negative
+     &lt;th> Characteristic
+     &lt;th> Positive
+   &lt;tbody>
+    &lt;tr>
+     &lt;td headers="n r1"> Sad
+     &lt;th id="r1"> Mood
+     &lt;td> Happy
+    &lt;tr>
+     &lt;td headers="n r2"> Failing
+     &lt;th id="r2"> Grade
+     &lt;td> Passing
+  &lt;/table>
+ &lt;/dd>
+&lt;/figure>
 </pre></div>
    </dd>
 
   </dl>
 
   <p>Authors may also use other techniques, or combinations of the
   above techniques, as appropriate.</p>
 
   <p>The <dfn title="attr-table-summary"><code>summary</code></dfn>
   attribute on <code>table</code> elements was suggested in earlier
@@ -31167,24 +30939,24 @@ side in the right column.&lt;/p>
   <code>table</code> that is its parent, if it has a parent and that
   is a <code>table</code> element.</p>
 
   <div class="impl">
 
   <p>The <code>caption</code> element takes part in the <span>table
   model</span>.</p>
 
   </div>
 
-  <p>When a <code>table</code> element is in a <code>figure</code>
-  element alone but for the <code>figure</code>'s <code>legend</code>,
-  the <code>caption</code> element should be omitted in favor of the
-  <code>legend</code>.</p>
+  <p>When a <code>table</code> element is the only content in a
+  <code>figure</code> element's <code>dd</code>, the
+  <code>caption</code> element should be omitted in favor of the
+  <code>dt</code>.</p>
 
   <p>A caption can introduce context for a table, making it
   significantly easier to understand.</p>
 
   <div class="example">
 
    <p>Consider, for instance, the following table:</p>
 
    <table class="dice-example">
     <tr> <th>   <th> 1 <th> 2 <th> 3 <th> 4 <th> 5 <th> 6
@@ -43863,49 +43635,50 @@ fur
 
   <h4>The <dfn><code>details</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
    <dd><span>Interactive content</span>.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>flow content</span> is expected.</dd>
    <dt>Content model:</dt>
-   <dd>One <code>legend</code> element followed by <span>flow content</span>.</dd>
+   <dd>One <code>dt</code> element followed by one <code>dd</code> element.</dd>
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dd><code title="attr-details-open">open</code></dd>
    <dt>DOM interface:</dt>
    <dd>
 <pre class="idl">interface <dfn>HTMLDetailsElement</dfn> : <span>HTMLElement</span> {
            attribute boolean <span title="dom-details-open">open</span>;
 };</pre>
    </dd>
   </dl>
 
   <p>The <code>details</code> element <span>represents</span> additional
   information or controls which the user can obtain on demand.</p>
 
   <p class="note">The <code>details</code> element is not appropriate
   for footnotes. Please see <a href="#footnotes">the section on
   footnotes</a> for details on how to mark up footnotes.</p>
 
-  <p>The first element child of a <code>details</code> element, <span
-  class="impl">if it is</span> a <code>legend</code> element,
-  <span>represents</span> the summary of the details.</p>
-
-  <div class="impl">
-
-  <p>If the first element is not a <code>legend</code> element, the
-  UA should provide its own legend (e.g. "Details").</p>
+  <p>The <span class="impl">first</span> <code>dt</code> element child
+  of the element<span class="impl">, if any,</span>
+  <span>represents</span> the summary of the details.  <span
+  class="impl">If there is no child <code>dt</code> element, the user
+  agent should provide its own legend (e.g. "Details").</span></p>
 
-  </div>
+  <p>The <span class="impl">first</span> <code>dd</code> element child
+  of the element<span class="impl">, if any,</span>
+  <span>represents</span> the details. <span class="impl">If there is
+  no child <code>dd</code> element, then there are no
+  details.</span></p>
 
   <p>The <dfn title="attr-details-open"><code>open</code></dfn>
   content attribute is a <span>boolean attribute</span>. If present,
   it indicates that the details are to be shown to the user. If the
   attribute is absent, the details are not to be shown.</p>
 
   <div class="impl">
 
   <p>If the attribute is removed, then the details should be
   hidden. If the attribute is added, the details should be shown.</p>
@@ -43926,29 +43699,31 @@ fur
   </div>
 
   <div class="example">
 
    <p>The following example shows the <code>details</code> element
    being used to hide technical details in a progress report.</p>
 
    <pre>&lt;section class="progress window">
  &lt;h1>Copying "Really Achieving Your Childhood Dreams"&lt;/h1>
  &lt;details>
-  &lt;legend>Copying... &lt;progress max="375505392" value="97543282">&lt;/progress> 25%&lt;/legend>
-  &lt;dl>
-   &lt;dt>Transfer rate:&lt;/dt> &lt;dd>452KB/s&lt;/dd>
-   &lt;dt>Local filename:&lt;/dt> &lt;dd>/home/rpausch/raycd.m4v&lt;/dd>
-   &lt;dt>Remote filename:&lt;/dt> &lt;dd>/var/www/lectures/raycd.m4v&lt;/dd>
-   &lt;dt>Duration:&lt;/dt> &lt;dd>01:16:27&lt;/dd>
-   &lt;dt>Color profile:&lt;/dt> &lt;dd>SD (6-1-6)&lt;/dd>
-   &lt;dt>Dimensions:&lt;/dt> &lt;dd>320&times;240&lt;/dd>
-  &lt;/dl>
+  &lt;dt>Copying... &lt;progress max="375505392" value="97543282">&lt;/progress> 25%&lt;/dt>
+  &lt;dd>
+   &lt;dl>
+    &lt;dt>Transfer rate:&lt;/dt> &lt;dd>452KB/s&lt;/dd>
+    &lt;dt>Local filename:&lt;/dt> &lt;dd>/home/rpausch/raycd.m4v&lt;/dd>
+    &lt;dt>Remote filename:&lt;/dt> &lt;dd>/var/www/lectures/raycd.m4v&lt;/dd>
+    &lt;dt>Duration:&lt;/dt> &lt;dd>01:16:27&lt;/dd>
+    &lt;dt>Color profile:&lt;/dt> &lt;dd>SD (6-1-6)&lt;/dd>
+    &lt;dt>Dimensions:&lt;/dt> &lt;dd>320&times;240&lt;/dd>
+   &lt;/dl>
+  &lt;/dd>
  &lt;/details>
 &lt;/section></pre>
 
   </div>
 
 
 
 <!-- v2DATAGRID
   <h4 id="datagrid">The <dfn><code>datagrid</code></dfn> element</h4>
 
@@ -47869,38 +47644,36 @@ interface <dfn>DataGridListener</dfn> {
 
   <h3>Miscellaneous elements</h3>
 
   <h4>The <dfn><code>legend</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd>None.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>As the first child of a <code>fieldset</code> element.</dd>
-   <dd>As the first child of a <code>details</code> element.</dd>
-   <dd>As the first or last child of a <code>figure</code> element, if there are no other <code>legend</code> element children of that element.</dd>
    <dt>Content model:</dt>
-   <dd>When the parent node is a <code>figure</code> element: <span>flow content</span>, but with no descendant <code>figure</code> elements.</dd>
-   <dd>Otherwise: <span>phrasing content</span>.</dd>
+   <dd><span>Phrasing content</span>.</dd>
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dt>DOM interface:</dt>
    <dd>
     <pre class="idl">interface <dfn>HTMLLegendElement</dfn> : <span>HTMLElement</span> {
   readonly attribute <span>HTMLFormElement</span> <span title="dom-legend-form">form</span>;
 };</pre>
    </dd>
   </dl>
 
-  <p>The <code>legend</code> element <span>represents</span> a title
-  or explanatory caption for the rest of the contents of the
-  <code>legend</code> element's parent element.</p>
+  <p>The <code>legend</code> element <span>represents</span> a caption
+  for the rest of the contents of the <code>legend</code> element's
+  parent <code>fieldset</code> element<span class="impl">, if
+  any</span>.</p>
 
   <dl class="domintro">
 
    <dt><var title="">legend</var> . <code title="dom-legend-form">form</code></dt>
 
    <dd>
 
     <p>Returns the element's <code>form</code> element, if any, or
     null otherwise.</p>
 
@@ -47980,20 +47753,238 @@ interface <dfn>DataGridListener</dfn> {
   &lt;p>Hm, I just noticed that in the last paragraph I used British
   English. But I'm supposed to write in American English. So I
   shouldn't say "pavement" or "flat" or "colour"...&lt;/p>
  &lt;/div>
  &lt;p>I should say "sidewalk" and "apartment" and "color"!&lt;/p>
 &lt;/article></pre>
 
   </div>
 
 
+  <h3>Common idioms without dedicated elements</h3>
+
+  <h5>Tag clouds</h5>
+
+  <p id="tag-cloud">This specification does not define any markup
+  specifically for marking up lists of keywords that apply to a group
+  of pages (also known as <i>tag clouds</i>). In general, authors are
+  encouraged to either mark up such lists using <code>ul</code>
+  elements with explicit inline counts that are then hidden and turned
+  into a presentational effect using a style sheet, or to use SVG.</p>
+
+  <div class="example">
+
+   <p>Here, three tags are included in a short tag cloud:</p>
+
+   <pre>&lt;style>
+@media screen, print, handheld, tv {
+  /* should be ignored by non-visual browsers */
+  .tag-cloud > li > span { display: none; }
+  .tag-cloud > li { display: inline; }
+  .tag-cloud-1 { font-size: 0.7em; }
+  .tag-cloud-2 { font-size: 0.9em; }
+  .tag-cloud-3 { font-size: 1.1em; }
+  .tag-cloud-4 { font-size: 1.3em; }
+  .tag-cloud-5 { font-size: 1.5em; }
+}
+&lt;/style>
+...
+&lt;ul class="tag-cloud">
+ &lt;li class="tag-cloud-4">&lt;a title="28 instances" href="/t/apple">apple&lt;/a> &lt;span>(popular)&lt;/span>
+ &lt;li class="tag-cloud-2">&lt;a title="6 instances"  href="/t/kiwi">kiwi&lt;/a> &lt;span>(rare)&lt;/span>
+ &lt;li class="tag-cloud-5">&lt;a title="41 instances" href="/t/pear">pear&lt;/a> &lt;span>(very popular)&lt;/span>
+&lt;/ul></pre>
+
+   <p>The actual frequency of each tag is given using the <code
+   title="attr-title">title</code> attribute. A CSS style sheet is
+   provided to convert the markup into a cloud of differently-sized
+   words, but for user agents that do not support CSS or are not
+   visual, the markup contains annotations like "(popular)" or
+   "(rare)" to categorize the various tags by frequency, thus enabling
+   all users to benefit from the information.</p>
+
+   <p>The <code>ul</code> element is used (rather than
+   <code>ol</code>) because the order is not particular important:
+   while the list is in fact ordered alphabetically, it would convey
+   the same information if ordered by, say, the length of the tag.</p>
+
+   <p>The <code title="rel-tag">tag</code> <code
+   title="attr-hyperlink-rel">rel</code>-keyword is <em>not</em> used
+   on these <code>a</code> elements because they do not represent tags
+   that apply to the page itself; they are just part of an index
+   listing the tags themselves.</p>
+
+  </div>
+
+
+  <h4>Conversations</h4>
+
+  <p>This specification does not define a specific element for marking
+  up conversations, meeting minutes, chat transcripts, dialogues in
+  screenplays, instant message logs, and other situations where
+  different players take turns in discourse.</p>
+
+  <p>Instead, authors are encouraged to mark up conversations using
+  <code>p</code> elements, with the <code>b</code> element for marking
+  up the speaker, optionally separated from their lines with
+  punctuation. Paragraphs with their text wrapped in the
+  <code>i</code> element can be used for marking up stage
+  directions.</p>
+
+  <div class="example">
+
+   <p>This example demonstrates this using an extract from Abbot and
+   Costello's famous sketch, <cite>Who's on first</cite>:</p>
+
+<pre>&lt;p> &lt;b>Costello&lt;/b>: Look, you gotta first baseman?
+&lt;p> &lt;b>Abbott&lt;/b>: Certainly.
+&lt;p> &lt;b>Costello&lt;/b>: Who's playing first?
+&lt;p> &lt;b>Abbott&lt;/b>: That's right.
+&lt;p> &lt;i>Costello becomes exasperated.&lt;/i>
+&lt;p> &lt;b>Costello&lt;/b>: When you pay off the first baseman every month, who gets the money?
+&lt;p> &lt;b>Abbott&lt;/b>: Every dollar of it.</pre>
+
+  </div>
+
+  <div class="example">
+
+   <p>The following extract shows how an IM conversation log could be
+   marked up.</p>
+
+   <pre>&lt;p> &lt;time>14:22&lt;/time> &lt;b>egof&lt;/b> I'm not that nerdy, I've only seen 30% of the star trek episodes
+&lt;p> &lt;time>14:23&lt;/time> &lt;b>kaj&lt;/b> if you know what percentage of the star trek episodes you have seen, you are inarguably nerdy
+&lt;p> &lt;time>14:23&lt;/time> &lt;b>egof&lt;/b> it's unarguably
+&lt;p> &lt;time>14:24&lt;/time> &lt;b>kaj&lt;/b> you are not helping your case</pre>
+   <!-- with thanks to http://bash.org/?854262 -->
+
+  </div>
+
+
+  <h4 id="footnotes">Footnotes</h4>
+
+  <p>HTML does not have a dedicated mechanism for marking up
+  footnotes. Here are the recommended alternatives.</p>
+
+  <hr>
+
+  <p>For short inline annotations, the <code
+  title="attr-title">title</code> attribute should be used.</p>
+
+  <div class="example">
+
+   <p>In this example, two parts of a dialogue are annotated.</p>
+
+   <pre>&lt;p> &lt;b>Customer&lt;/b>: Hello! I wish to register a complaint. Hello. Miss?
+&lt;p> &lt;b>Shopkeeper&lt;/b>: &lt;span title="Colloquial pronunciation of 'What do you'"
+>Watcha&lt;/span> mean, miss?
+&lt;p> &lt;b>Customer&lt;/b>: Uh, I'm sorry, I have a cold. I wish to make a complaint.
+&lt;p> &lt;b>Shopkeeper&lt;/b>: Sorry, &lt;span title="This is, of course, a lie.">we're
+closing for lunch&lt;/span>.</pre>
+
+  </div>
+
+  <hr>
+
+  <p>For longer annotations, the <code>a</code> element should be
+  used, pointing to an element later in the document. The convention
+  is that the contents of the link be a number in square brackets.</p>
+
+  <div class="example">
+
+   <p>In this example, a footnote in the dialogue links to a paragraph
+   below the dialogue. The paragraph then reciprocally links back to the
+   dialogue, allowing the user to return to the location of the
+   footnote.</p>
+
+   <pre>&lt;p> &lt;b>Announcer&lt;/b>: Number 16: The &lt;i>hand&lt;/i>.
+&lt;p> &lt;b>Interviewer&lt;/b>: Good evening. I have with me in the
+studio tonight Mr Norman St John Polevaulter, who for the past few
+years has been contradicting people. Mr Polevaulter, why
+&lt;em>do&lt;/em> you contradict people?
+&lt;p> &lt;b>Norman&lt;/b>: I don't. &lt;a href="#fn1" id="r1">[1]&lt;/a>
+&lt;p> &lt;b>Interviewer&lt;/b>: You told me you did!
+<em>...</em>
+&lt;section>
+ &lt;p id="fn1">&lt;a href="#r1">[1]&lt;/a> This is, naturally, a lie,
+ but paradoxically if it were true he could not say so without
+ contradicting the interviewer and thus making it false.&lt;/p>
+&lt;/section></pre>
+
+  </div>
+
+  <hr>
+
+  <p>For side notes, longer annotations that apply to entire sections
+  of the text rather than just specific words or sentences, the
+  <code>aside</code> element should be used.</p>
+
+  <div class="example">
+
+   <p>In this example, a sidebar is given after a dialogue, giving it
+   some context.</p>
+
+   <pre>&lt;p> &lt;b>Customer&lt;/b>: I will not buy this record, it is scratched.
+&lt;p> &lt;b>Shopkeeper&lt;/b>: I'm sorry?
+&lt;p> &lt;b>Customer&lt;/b>: I will not buy this record, it is scratched.
+&lt;p> &lt;b>Shopkeeper&lt;/b>: No no no, this's'a tobacconist's.
+&lt;aside>
+ &lt;p>In 1970, the British Empire lay in ruins, and foreign
+ nationalists frequented the streets &mdash; many of them Hungarians
+ (not the streets &mdash; the foreign nationals). Sadly, Alexander
+ Yalt has been publishing incompetently-written phrase books.
+&lt;/aside></pre>
+
+  </div>
+
+  <hr>
+
+  <p>For figures or tables, footnotes can be included in the relevant
+  <code>dt</code> or <code>caption</code> element, or in surrounding
+  prose.</p>
+
+  <div class="example">
+
+   <p>In this example, a <!-- round --> table has cells with footnotes
+   that are given in prose. A <code>figure</code> element is used to
+   give a single legend to the combination of the table and its
+   footnotes.</p>
+
+   <pre>&lt;figure>
+ &lt;dt>Table 1. Alternative activities for knights.&lt;/dt>
+ &lt;dd>
+  &lt;table>
+   &lt;tr>
+    &lt;th> Activity
+    &lt;th> Location
+    &lt;th> Cost
+   &lt;tr>
+    &lt;td> Dance
+    &lt;td> Wherever possible
+    &lt;td> &#x00A3;0&lt;sup>&lt;a href="#fn1">1&lt;/a>&lt;/sup>
+   &lt;tr>
+    &lt;td> Routines, chorus scenes&lt;sup>&lt;a href="#fn2">2&lt;/a>&lt;/sup>
+    &lt;td> Undisclosed
+    &lt;td> Undisclosed
+   &lt;tr>
+    &lt;td> Dining&lt;sup>&lt;a href="#fn3">3&lt;/a>&lt;/sup>
+    &lt;td> Camelot
+    &lt;td> Cost of ham, jam, and spam&lt;sup>&lt;a href="#fn4">4&lt;/a>&lt;/sup>
+  &lt;/table>
+  &lt;p id="fn1">1. Assumed.&lt;/p>
+  &lt;p id="fn2">2. Footwork impeccable.&lt;/p>
+  &lt;p id="fn3">3. Quality described as "well".&lt;/p>
+  &lt;p id="fn4">4. A lot.&lt;/p>
+ &lt;/dd>
+&lt;/figure></pre>
+
+  </div>
+
 
 
   <div class="impl">
 
   <h3>Matching HTML elements using selectors</h3>
 
   <p>There are a number of dynamic selectors that can be used with
   HTML. This section defines when these selectors match HTML
   elements.</p>
 
@@ -48600,28 +48591,28 @@ interface <dfn>DataGridListener</dfn> {
   <p>It's important to note that there is no relationship between the
   microdata and the content of the document where the microdata is
   marked up.</p>
 
   <div class="example">
 
    <p>There is no semantic difference, for instance, between the
    following two examples:</p>
 
    <pre>&lt;figure>
- &lt;img src="castle.jpeg">
- &lt;legend>&lt;span item>&lt;span itemprop="name">The Castle&lt;/span>&lt;/span> (1986)&lt;/legend>
+ &lt;dd>&lt;img src="castle.jpeg">
+ &lt;dt>&lt;span item>&lt;span itemprop="name">The Castle&lt;/span>&lt;/span> (1986)
 &lt;/figure></pre>
 
    <pre>&lt;span item>&lt;meta itemprop="name" content="The Castle">&lt;/span>
 &lt;figure>
- &lt;img src="castle.jpeg">
- &lt;legend>The Castle (1986)&lt;/legend>
+ &lt;dd>&lt;img src="castle.jpeg">
+ &lt;dt>The Castle (1986)
 &lt;/figure></pre>
 
    <p>Both have a figure with a caption, and both, completely
    unrelated to the figure, have an item with a name-value pair with
    the name "name" and the value "The Castle". The only
    difference is that if the user drags the caption out of the
    document, in the former case, the item will be included in the
    drag-and-drop data. In neither case is the image in any way
    associated with the item.</p>
 
@@ -51648,30 +51639,29 @@ document.body.appendChild(outer);</pre>
   <h5>Examples</h5>
 
   <div class="example">
 
    <p>This example shows an embedded image entitled <cite>My
    Pond</cite>, licensed under the Creative Commons Attribution-Share
    Alike 3.0 United States License and the MIT license
    simultaneously.</p>
 
    <pre>&lt;figure <strong>item="work"</strong>>
- &lt;img <strong>itemprop="about"</strong> src="mypond.jpeg">
- &lt;legend>
+ &lt;dd>&lt;img <strong>itemprop="about"</strong> src="mypond.jpeg">
+ &lt;dt>
   &lt;p>&lt;cite <strong>itemprop="title"</strong>>My Pond&lt;/cite>&lt;/p>
   &lt;p>&lt;small>Licensed under the &lt;a <strong>itemprop="license"</strong>
   href="http://creativecommons.org/licenses/by-sa/3.0/us/">Creative
   Commons Attribution-Share Alike 3.0 United States License&lt;/a>
   and the &lt;a <strong>itemprop="license"</strong>
   href="http://www.opensource.org/licenses/mit-license.php">MIT
   license&lt;/a>.&lt;/small>
- &lt;/legend>
 &lt;/figure></pre>
 
   </div>
 
 
 
   <div class="impl">
 
   <h3>Converting HTML to other formats</h3>
 
@@ -64951,22 +64941,22 @@ interface <dfn>SQLTransactionSync</dfn> {
  &lt;head>
   &lt;title>Exampl Pictures: Kissat&lt;/title>
   &lt;link rel="stylesheet" href="/style/default">
  &lt;/head>
  &lt;body>
   &lt;h1>Kissat&lt;/h1>
   &lt;nav>
    &lt;a href="../">Return to photo index&lt;/a>
   &lt;/nav>
   &lt;figure>
-   &lt;img src="/pix/39627052_fd8dcd98b5.jpg">
-   &lt;legend>Kissat&lt;/legend>
+   &lt;dd>&lt;img src="/pix/39627052_fd8dcd98b5.jpg">
+   &lt;dt>Kissat
   &lt;/figure>
   &lt;p>One of them has six toes!&lt;/p>
   &lt;p>&lt;small>&lt;a rel="license" href="http://www.opensource.org/licenses/mit-license.php">MIT Licensed&lt;/a>&lt;/small>&lt;/p>
   &lt;footer>
    &lt;a href="/">Home&lt;/a> | &lt;a href="../">Photo index&lt;/a>
    &lt;p>&lt;small>&copy; copyright 2009 Exampl Pictures. All Rights Reserved.&lt;/small>&lt;/p>
   &lt;/footer>
  &lt;/body>
 &lt;/html></pre>
 
@@ -75632,45 +75622,47 @@ interface <dfn>MessagePort</dfn> {
   tag</span> may be omitted if the <code>body</code> element is not
   immediately followed by a <span
   title="syntax-comments">comment</span>.</p>
 
   <!-- </li> -->
   <p>A <code>li</code> element's <span title="syntax-end-tag">end
   tag</span> may be omitted if the <code>li</code> element is
   immediately followed by another <code>li</code> element or if there
   is no more content in the parent element.</p>
 
+  <!-- </dc> and </ds> can be added here one they are invented --> 
+
   <!-- </dt> -->
   <p>A <code>dt</code> element's <span title="syntax-end-tag">end
   tag</span> may be omitted if the <code>dt</code> element is
   immediately followed by another <code>dt</code> element or a
   <code>dd</code> element.</p>
 
   <!-- </dd> -->
   <p>A <code>dd</code> element's <span title="syntax-end-tag">end
   tag</span> may be omitted if the <code>dd</code> element is
   immediately followed by another <code>dd</code> element or a
   <code>dt</code> element, or if there is no more content in the
   parent element.</p>
 
   <!-- </p> -->
   <p>A <code>p</code> element's <span title="syntax-end-tag">end
   tag</span> may be omitted if the <code>p</code> element is
   immediately followed by an <code>address</code>,
   <code>article</code>, <code>aside</code>, <code>blockquote</code>,
-  <!--v2DATAGRID <code>datagrid</code>,--> <code>dialog</code>,
-  <code>dir</code>, <code>div</code>, <code>dl</code>,
-  <code>fieldset</code>, <code>footer</code>, <code>form</code>,
-  <code>h1</code>, <code>h2</code>, <code>h3</code>, <code>h4</code>,
-  <code>h5</code>, <code>h6</code>, <code>header</code>,
-  <code>hgroup</code>, <code>hr</code>, <code>menu</code>,
-  <code>nav</code>, <code>ol</code>, <code>p</code>, <code>pre</code>,
+  <!--v2DATAGRID <code>datagrid</code>,--> <code>dir</code>,
+  <code>div</code>, <code>dl</code>, <code>fieldset</code>,
+  <code>footer</code>, <code>form</code>, <code>h1</code>,
+  <code>h2</code>, <code>h3</code>, <code>h4</code>, <code>h5</code>,
+  <code>h6</code>, <code>header</code>, <code>hgroup</code>,
+  <code>hr</code>, <code>menu</code>, <code>nav</code>,
+  <code>ol</code>, <code>p</code>, <code>pre</code>,
   <code>section</code>, <code>table</code>, or <code>ul</code>,
   element, or if there is no more content in the parent element and
   the parent element is not an <code>a</code> element.</p>
 
   <!-- </rt> -->
   <p>An <code>rt</code> element's <span title="syntax-end-tag">end
   tag</span> may be omitted if the <code>rt</code> element is
   immediately followed by an <code>rt</code> or <code>rp</code>
   element, or if there is no more content in the parent element.</p>
 
@@ -77047,22 +77039,23 @@ interface <dfn>MessagePort</dfn> {
 
    <dt><dfn>Special</dfn></dt>
 
    <dd><p>The following HTML elements have varying levels of special
    parsing rules: <code>address</code>, <code>area</code>,
    <code>article</code>, <code>aside</code>, <code>base</code>,
    <code>basefont</code>, <code>bgsound</code>,
    <code>blockquote</code>, <code>body</code>, <code>br</code>,
    <code>center</code>, <code>col</code>, <code>colgroup</code>,
    <code>command</code>, <!--v2DDATAGRID--><code>datagrid</code>,
-   <code>dd</code>, <code>details</code>, <code>dialog</code>,
-   <code>dir</code>, <code>div</code>, <code>dl</code>,
+   <code>dc</code><!-- speculative -->, <code>dd</code>,
+   <code>details</code>, <code>dir</code>, <code>div</code>,
+   <code>dl</code>, <code>ds</code><!-- speculative -->,
    <code>dt</code>, <code>embed</code>, <code>fieldset</code>,
    <code>figure</code>, <code>footer</code>, <code>form</code>,
    <code>frame</code>, <code>frameset</code>, <code>h1</code>,
    <code>h2</code>, <code>h3</code>, <code>h4</code>, <code>h5</code>,
    <code>h6</code>, <code>head</code>, <code>header</code>,
    <code>hgroup</code>, <code>hr</code>, <code>iframe</code>, <!--
    <code>image</code>, (commented out because this isn't an element
    that can end up on the stack, so it doesn't matter) -->
    <code>img</code>, <code>input</code>, <code>isindex</code>,
    <code>li</code>, <code>link</code>, <code>listing</code>,
@@ -79200,23 +79193,25 @@ document.body.appendChild(text);
    <li><p>Then, switch the <span>insertion mode</span> to "<span
    title="insertion mode: in RAWTEXT/RCDATA">in
    RAWTEXT/RCDATA</span>".</p></li>
 
   </ol>
 
 
 
   <h5>Closing elements that have implied end tags</h5>
 
+  <!-- <dc> and <ds> are here speculatively for future expansion (they're not defined elements yet) -->
   <p>When the steps below require the UA to <dfn>generate implied end
   tags</dfn>, then, while the <span>current node</span> is a
-  <code>dd</code> element, a <code>dt</code> element, an
+  <code>dc</code> element, a <code>dd</code> element, a
+  <code>ds</code> element, a <code>dt</code> element, an
   <code>li</code> element, an <code>option</code> element, an
   <code>optgroup</code> element, a <code>p</code> element, an
   <code>rp</code> element, or an <code>rt</code> element, the UA must
   pop the <span>current node</span> off the <span>stack of open
   elements</span>.</p>
 
   <p>If a step requires the UA to generate implied end tags but lists
   an element to exclude from the process, then the UA must perform the
   above steps as if that element was not in the above list.</p>
 
@@ -80090,57 +80085,60 @@ document.body.appendChild(text);
      title="insertion mode: in frameset">in frameset</span>".</p>
 
     </ol>
 
    </dd>
 
    <dt>An end-of-file token</dt>
    <dd>
 
     <p>If there is a node in the <span>stack of open elements</span>
-    that is not either a <code>dd</code> element, a <code>dt</code>
-    element, an <code>li</code> element, a <code>p</code> element, a
+    that is not either a <code>dc</code> element, a <code>dd</code>
+    element, a <code>ds</code> element, a <code>dt</code> element, an
+    <code>li</code> element, a <code>p</code> element, a
     <code>tbody</code> element, a <code>td</code> element, a
     <code>tfoot</code> element, a <code>th</code> element, a
     <code>thead</code> element, a <code>tr</code> element, the
     <code>body</code> element, or the <code>html</code> element, then
     this is a <span>parse error</span>.</p> <!-- (some of those are
-    fragment cases) -->
+    fragment cases) --> <!-- <dc> and <ds> are there speculatively -->
 
     <p><span>Stop parsing</span>.</p>
 
    </dd>
 
    <dt>An end tag whose tag name is "body"</dt>
    <dd>
 
     <p>If the <span>stack of open elements</span> does not <span
     title="has an element in scope">have a <code>body</code> element
     in scope</span>, this is a <span>parse error</span>; ignore the
     token.</p>
 
     <!-- if we get here, the insertion mode here is forcibly "in
     body". -->
 
     <p>Otherwise, if there is a node in the <span>stack of open
-    elements</span> that is not either a <code>dd</code> element, a
+    elements</span> that is not either a <code>dc</code> element, a
+    <code>dd</code> element, a <code>ds</code> element, a
     <code>dt</code> element, an <code>li</code> element, an
     <code>optgroup</code> element, an <code>option</code> element, a
     <code>p</code> element, an <code>rp</code> element, an
     <code>rt</code> element, a <code>tbody</code> element, a
     <code>td</code> element, a <code>tfoot</code> element, a
     <code>th</code> element, a <code>thead</code> element, a
     <code>tr</code> element, the <code>body</code> element, or the
     <code>html</code> element, then this is a <span>parse
     error</span>.</p> <!-- (some of those are fragment cases, e.g. for
     <tbody> you'd have hit the first paragraph since the <body>
-    wouldn't be in scope, unless it was a fragment case) -->
+    wouldn't be in scope, unless it was a fragment case) --> <!-- <dc>
+    and <ds> are there speculatively -->
 
     <!-- If we ever change the frameset-ok flag to an insertion mode,
     then we'd have to somehow keep track of its state when we switch
     to after-body. -->
 
     <p>Switch the <span>insertion mode</span> to "<span
     title="insertion mode: after body">after body</span>".</p>
 
    </dd>
 
@@ -80154,23 +80152,22 @@ document.body.appendChild(text);
     <p class="note">The fake end tag token here can only be
     ignored in the <span>fragment case</span>.</p>
 
    </dd>
 
    <!-- start tags for non-phrasing flow content elements -->
 
    <!-- the normal ones -->
    <dt>A start tag whose tag name is one of: "address", "article",
    "aside", "blockquote", "center", <!--v2DATAGRID-->"datagrid",
-   "details", "dialog", "dir", "div", "dl", "fieldset", "figure",
-   "footer", "header", "hgroup", "menu", "nav", "ol", "p", "section",
-   "ul"</dt>
+   "details", "dir", "div", "dl", "fieldset", "figure", "footer",
+   "header", "hgroup", "menu", "nav", "ol", "p", "section", "ul"</dt>
    <dd>
 
     <!-- As of May 2008 this doesn't match any browser exactly, but is
     as close to what IE does as I can get without doing the non-tree
     DOM nonsense, and thus should actually afford better compatibility
     when implemented by the other browsers. -->
 
     <p>If the <span>stack of open elements</span> <span title="has
     an element in scope">has a <code>p</code> element in
     scope</span>, then act as if an end tag with the tag name
@@ -80287,36 +80284,38 @@ document.body.appendChild(text);
       <p>Finally, <span>insert an HTML element</span> for the
       token.</p>
 
      </li>
 
     </ol>
 
    </dd>
 
    <!-- as normal, but imply </dt> or </dd> when there's another <dt> or <dd> open in weird cases  -->
-   <dt>A start tag whose tag name is one of: "dd", "dt"</dt>
+   <!-- <dc> and <ds> are here speculatively for future expansion (they're not defined elements yet) -->
+   <dt>A start tag whose tag name is one of: "dc", "dd", "ds", "dt"</dt>
    <dd>
 
     <p>Run the following algorithm:</p>
 
     <ol>
 
      <li><p>Set the <span>frameset-ok flag</span> to "not ok".</p></li>
 
      <li><p>Initialize <var title="">node</var> to be the <span>current
      node</span> (the bottommost node of the stack).</p></li>
 
      <li><p><i>Loop</i>: If <var title="">node</var> is a
-     <code>dd</code> or <code>dt</code> element, then act as if an end
-     tag with the same tag name as <var title="">node</var> had been
-     seen, then jump to the last step.</p></li>
+     <code>dc</code>, <code>dd</code>, <code>ds</code>, or
+     <code>dt</code> element, then act as if an end tag with the same
+     tag name as <var title="">node</var> had been seen, then jump to
+     the last step.</p></li>
 
      <li><p>If <var title="">node</var> is not in the
      <span>formatting</span> category, and is not in the
      <span>phrasing</span> category, and is not an
      <code>address</code>, <code>div</code>, or <code>p</code>
      element, then jump to the last step.</p></li> <!-- an element
      <foo> is in this list if the following markup:
 
          <!DOCTYPE html><body><dl><dt><foo><dt>
 
@@ -80366,23 +80365,23 @@ document.body.appendChild(text);
     there is no way to switch the <span>content model flag</span>
     out of the PLAINTEXT state.</p>
 
    </dd>
 
    <!-- end tags for non-phrasing flow content elements -->
 
    <!-- the normal ones -->
    <dt>An end tag whose tag name is one of: "address", "article",
    "aside", "blockquote", "center", <!--v2DATAGRID-->"datagrid",
-   "details", "dialog", "dir", "div", "dl", "fieldset", "figure",
-   "footer", "header", "hgroup", "listing", "menu", "nav", "ol",
-   "pre", "section", "ul"</dt>
+   "details", "dir", "div", "dl", "fieldset", "figure", "footer",
+   "header", "hgroup", "listing", "menu", "nav", "ol", "pre",
+   "section", "ul"</dt>
    <dd>
 
     <p>If the <span>stack of open elements</span> does not <span
     title="has an element in scope">have an element in scope</span>
     with the same tag name as that of the token, then this is a
     <span>parse error</span>; ignore the token.</p>
 
     <p>Otherwise, run these steps:</p>
 
     <ol>
@@ -80485,21 +80484,22 @@ document.body.appendChild(text);
 
      <li><p>Pop elements from the <span>stack of open elements</span>
      until an element with the same tag name as the token has been
      popped from the stack.</p></li>
 
     </ol>
 
    </dd>
 
    <!-- as normal, but needs care as the elements have optional tags -->
-   <dt>An end tag whose tag name is one of: "dd", "dt"</dt>
+   <!-- <dc> and <ds> are here speculatively for future expansion (they're not defined elements yet) -->
+   <dt>An end tag whose tag name is one of: "dc", "dd", "ds", "dt"</dt>
    <dd>
 
     <p>If the <span>stack of open elements</span> does not <span
     title="has an element in scope">have an element in scope</span>
     with the same tag name as that of the token, then this is a
     <span>parse error</span>; ignore the token.</p>
 
     <p>Otherwise, run these steps:</p>
 
     <ol>
@@ -82430,39 +82430,38 @@ document.body.appendChild(text);
     content</span>", but there is no element in scope that has a
     namespace other than the <span>HTML namespace</span><!-- XXX this
     isn't well-defined; it means check to see if the bottom-most HTML
     element on the stack is in scope -->, switch the <span>insertion
     mode</span> to the <span>secondary insertion mode</span>.</p>
 
    </dd>
 
    <dt>A start tag whose tag name is one of: <!--"a",--> "b", "big",
    "blockquote", "body"<!--by inspection-->, "br", "center", "code",
-   "dd", "div", "dl", "dt"<!-- so that dd and dt can be handled
-   uniformly throughout the parser -->, "em", "embed", "h1", "h2",
-   "h3", "h4"<!--for completeness-->, "h5", "h6"<!--for
+   "dc"<!-- with dt -->, "dd", "div", "dl", "ds"<!-- with dt -->,
+   "dt"<!-- so that dd and dt can be handled uniformly throughout the
+   parser; dc and ds are here for the same reason -->, "em", "embed",
+   "h1", "h2", "h3", "h4"<!--for completeness-->, "h5", "h6"<!--for
    completeness-->, "head"<!--by inspection-->, "hr", "i", "img",
    "li", "listing"<!-- so that pre and listing can be handled
    uniformly throughout the parser -->, "menu", "meta", "nobr",
    "ol"<!-- so that dl, ul, and ol can be handled uniformly throughout
    the parser -->, "p", "pre", "ruby", "s", <!--"script",--> "small",
    "span", "strong", "strike"<!-- so that s and strike can be handled
    uniformly throughout the parser -->, <!--"style",--> "sub", "sup",
-   "table"<!--by inspection-->, "tt", "u", "ul", "var"</dt>
-   <!-- this list was determined empirically by studying over
-   6,000,000,000 pages that were specifically not XML pages -->
-   <dt>A start tag whose tag name is "font", if the token has
-   any attributes named "color", "face", or "size"</dt>
-   <!-- the attributes here are required so that SVG <font> will go
-   through as SVG but legacy <font>s won't -->
-   <dt>An end-of-file token</dt>
-   <dd>
+   "table"<!--by inspection-->, "tt", "u", "ul", "var"</dt> <!-- this
+   list was determined empirically by studying over 6,000,000,000
+   pages that were specifically not XML pages --> <dt>A start tag
+   whose tag name is "font", if the token has any attributes named
+   "color", "face", or "size"</dt> <!-- the attributes here are
+   required so that SVG <font> will go through as SVG but legacy
+   <font>s won't --> <dt>An end-of-file token</dt> <dd>
 
     <p><span>Parse error</span>.</p>
 
     <p>Pop elements from the <span>stack of open elements</span> until
     the <span>current node</span> is in the <span>HTML
     namespace</span>.</p>
 
     <p>Switch the <span>insertion mode</span> to the <span>secondary
     insertion mode</span>, and reprocess the token.</p>
 
@@ -84256,22 +84255,22 @@ http://lxr.mozilla.org/seamonkey/search?string=nested
   <h4>Display types</h4>
 
   <pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
 
 [hidden], area, audio:not([controls]), base, basefont, command,
 datalist, head, input[type=hidden], link, menu[type=context], meta,
 noembed, noframes, param, rp, script, source, style, title {
   display: none;
 }
 
-address, article, aside, blockquote, body, center, dd, dialog, dir,
-div, dl, dt, figure, footer, form, h1, h2, h3, h4, h5, h6, header,
+address, article, aside, blockquote, body, center, dc, dd, dir, div,<!-- dc and ds are here for speculative purposes to enable future extensions -->
+dl, ds, dt, figure, footer, form, h1, h2, h3, h4, h5, h6, header,
 hgroup, hr, html, legend, listing, menu, nav, ol, p, plaintext, pre,
 section, ul, xmp { display: block; }
 
 table { display: table; }
 caption { display: table-caption; }
 colgroup { display: table-column-group; }
 col { display: table-column; }
 thead { display: table-header-group; }
 tbody { display: table-row-group; }
 tfoot { display: table-footer-group; }
@@ -84330,21 +84329,21 @@ rt { display: ruby-text; }
 
   </div>
 
 
   <div class="impl">
 
   <h4>Margins and padding</h4>
 
   <pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
 
-blockquote, dialog, dir, dl, figure, listing, menu, ol, p, plaintext,
+blockquote, dir, dl, figure, listing, menu, ol, p, plaintext,
 pre, ul, xmp {
   margin-top: 1em; margin-bottom: 1em;
 }
 
 dir dir, dir dl, dir menu, dir ol, dir ul,
 dl dir, dl dl, dl menu, dl ol, dl ul,
 menu dir, menu dl, menu menu, menu ol, menu ul,
 ol dir, ol dl, ol menu, ol ol, ol ul,
 ul dir, ul dl, ul menu, ul ol, ul ul {
   margin-top: 0; margin-bottom: 0;
@@ -85609,21 +85608,21 @@ button { binding: <i title="">button</i>; }</pre>
 
   <pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
 
 details { binding: <i title="">details</i>; }</pre>
 
   <p>When the <i title="">details</i> binding applies to a
   <code>details</code> element, the element is expected to render as a
   'block' box with its 'padding-left' property set to '40px'. The
   element's shadow tree is expected to take a child element that
   matches the selector <code
-  title="">:bound-element&nbsp;>&nbsp;legend:first-child</code> and
+  title="">:bound-element&nbsp;>&nbsp;dt:first-of-type</code> and
   place it in a first 'block' box container, and then take the
   remaining child nodes and place them in a later 'block' box
   container.</p>
 
   <p>The first container is expected to contain at least one line box,
   and that line box is expected to contain a triangle widget,
   horizontally positioned within the left padding of the
   <code>details</code> element. That widget is expected to allow the
   user to request that the details be shown or hidden.</p>
 
@@ -90050,20 +90049,21 @@ interface <span>HTMLDocument</span> {
   Jeff Balogh,
   Jeff Cutsinger,
   Jeff Schiller,
   Jeff Walden,
   Jeffrey Zeldman,
   &#32993;&#24935;&#37586; (Jennifer Braithwaite),
   Jens Bannmann,
   Jens Fendler,
   Jens Lindstr&ouml;m,
   Jens Meiert,
+  Jeremy Keith,
   Jeremy Orlow,
   Jeroen van der Meer,
   Jian Li,
   Jim Jewett,
   Jim Ley,
   Jim Meehan,
   Jjgod Jiang,
   Jo&atilde;o Eiras,
   Joe Clark,
   Joe Gregorio,

|