W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2008

html5/pubnotes ChangeLog,1.11,1.12 Overview.html,1.236,1.237 Overview.src.html,1.230,1.231 specgen.xsl,1.19,1.20 style.css,1.61,1.62

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 09 Jun 2008 18:59:53 +0000
To: public-html-commits@w3.org
Message-Id: <E1K5mav-0007JH-Sw@lionel-hutz.w3.org>

Update of /sources/public/html5/pubnotes
In directory hutz:/tmp/cvs-serv27964

Modified Files:
	ChangeLog Overview.html Overview.src.html specgen.xsl 
	style.css 
Log Message:
various tweaks to get ready for publication


Index: specgen.xsl
===================================================================
RCS file: /sources/public/html5/pubnotes/specgen.xsl,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- specgen.xsl	9 Jun 2008 16:21:08 -0000	1.19
+++ specgen.xsl	9 Jun 2008 18:59:51 -0000	1.20
@@ -246,6 +246,35 @@
     </div>
   </xsl:template>
 
+  <xsl:template match="h:*[@id = 'summary']">
+    <div id="summary" class="section">
+      <xsl:apply-templates
+        select="document('summary.html')//h:div[child::*[@id='webarch']]"/>
+    </div>
+  </xsl:template>
+
+  <xsl:template match="h:div[child::*[@id='webarch']]">
+    <xsl:apply-templates/>
+  </xsl:template>
+
+  <xsl:template match="h:h3[@id = 'webarch']">
+    <h2>Summary: Changes impacting Web architecture <a
+        href="#summary">#</a>
+      <xsl:text> </xsl:text><a href="#summary-toc">T</a></h2>
+  </xsl:template>
+
+  <xsl:template match="h:div[child::*[@id='webarch']]/h:p[1]">
+    <p>This section provides a high-level summary of changes
+      introduced by new areas or features of the HTML 5
+      specification that are believed to impact the Web
+      architecture. For more detailed descriptions of the changes,
+      see the sections in this document that follow this one.
+      (Note: The source for this summary is maintained in the <a
+        href="http://www.w3.org/TR/html5-diff/" >HTML 5
+        differences from HTML 4</a> document; the summary was
+      copied from that document into this one.)</p>
+  </xsl:template>
+
   <xsl:template name='revision-note'>
       <xsl:if test='$maturity="ED"'>
         <div class='ednote'>
@@ -469,7 +498,11 @@
     </xsl:choose>
   </xsl:template>
 
-  <xsl:template match='h:h2'>
+  <xsl:template match='h:h2[not(../@id = "abstract")
+    and not(../@id="status")
+    and not(../@id="toc")
+    ]'
+    >
     <xsl:variable name="myid">
       <xsl:value-of select="../@id"/>
     </xsl:variable>
@@ -492,9 +525,11 @@
       <xsl:text> </xsl:text>
       <a class="toc-bak" href="#{$myid}-toc">T</a>
     </xsl:element>
+    <xsl:if test="not($myid = 'fpwd')">
     <p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#{$myid}"
         ><xsl:apply-templates select='node()'/></a>” in the
         specification</p>
+    </xsl:if>
   </xsl:template>
 
   <xsl:template match='h:*[@class="ednote"]'>

Index: ChangeLog
===================================================================
RCS file: /sources/public/html5/pubnotes/ChangeLog,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- ChangeLog	9 Jun 2008 16:21:08 -0000	1.11
+++ ChangeLog	9 Jun 2008 18:59:51 -0000	1.12
@@ -1,3 +1,13 @@
+2008-06-10 03:56  mike
+
+	* Makefile (1.5), summary.html (1.1): made build create
+	  summary.html WF version of anne's html5 html4 differences doc
+
+2008-06-10 01:21  mike
+
+	* ChangeLog (1.11), Overview.html (1.236), Overview.src.html
+	  (1.230), specgen.xsl (1.19), style.css (1.61): added linking
+
 2008-06-09 19:45  mike
 
 	* ChangeLog (1.10), Overview.html (1.235), Overview.src.html

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.236
retrieving revision 1.237
diff -u -d -r1.236 -r1.237
--- Overview.html	9 Jun 2008 16:21:08 -0000	1.236
+++ Overview.html	9 Jun 2008 18:59:51 -0000	1.237
@@ -1,44 +1,29 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<!-- * -->
-<!-- * Note: This file was generated from source at http://dev.w3.org/html5/pubnotes/Overview.src.html -->
-<!-- * Run “make” to regenerate it. -->
-<!-- * -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
   <head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><meta charset="utf-8" /><title>HTML 5 Publication Notes</title>
     <meta content="$Id$" name="revision" />
     <link href="style.css" type="text/css" rel="stylesheet" />
     
     
-    <link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-ED" type="text/css" />
+    <link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" type="text/css" />
   </head><div class="head"><div><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>HTML 5 Publication Notes</h1><h2>
         W3C
-        Editor’s Draft <em>9 June 2008</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a id="latestED" href="http://dev.w3.org/html5/pubnotes/Overview.src.html">http://dev.w3.org/html5/pubnotes/Overview.src.html</a><script type="text/ecmascript">
-                var id = "$Id$";
-                var a = document.getElementById('cvsVersionLink');
-                var xs = id.match(/ ([0-9]\.[0-9.]+) /);
-                if (xs) {
-                  var rev = xs[1];
-                  a.href = "http://dev.w3.org/html5/pubnotes/Overview.src.html?rev=" + rev + String.fromCharCode(38) + "content-type=text/html; charset=utf-8";
-                  a.firstChild.data = a.href;
-                }
-              </script></dd><dt>Latest Published Version:</dt><dd><a href="http://www.w3.org/TR/html5-pubnotes/">http://www.w3.org/TR/html5-pubnotes/</a></dd><dt>Editor:</dt><dd><a href="http://people.w3.org/mike">Michael(tm) Smith</a>, W3C &lt;<a href="mailto:mike@w3.org">mike@w3.org</a>&gt;</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2008 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="htp://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr />
+        Working Draft <em>10 June 2008</em></h2><dl><dt>This Version:</dt><dd><a href="http://www.w3.org/TR/2008/WD-html5-pubnotes-20080610/">http://www.w3.org/TR/2008/WD-html5-pubnotes-20080610/</a></dd><dt>Latest Version:</dt><dd><a href="http://www.w3.org/TR/html5-pubnotes/">http://www.w3.org/TR/html5-pubnotes/</a></dd><dt>Editor:</dt><dd><a href="http://people.w3.org/mike">Michael(tm) Smith</a>, W3C &lt;<a href="mailto:mike@w3.org">mike@w3.org</a>&gt;</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2008 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr />
   <body>
     
     
-    <div style="text-align: center" id="tocjump">[<a href="#toc">skip to Table of Contents</a>]</div>
+    <div style="text-align: center" id="tocjump"><a href="#toc">skip to Table of Contents</a></div>
     <div id="abstract">
-      <h2>Abstract <a class="hash" href="#abstract">#</a> <a class="toc-bak" href="#abstract-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#abstract">Abstract</a>” in the
-        specification</p>
+      <h2>Abstract</h2>
       <p>This document provides supplemental information on the
         current working draft of the HTML 5 specification. It
         primarily documents changes that have been made to the HTML
         5 draft specification since the time of its publication as
         a First Public Working Draft (FPWD).</p>
-    <div class="ednote"><h4 class="ednoteHeader">Editorial note</h4><p>This is revision $Id$.</p></div></div>
+    </div>
     <div id="status">
-      <h2>Status of this Document <a class="hash" href="#status">#</a> <a class="toc-bak" href="#status-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#status">Status of this Document</a>” in the
-        specification</p>
+      <h2>Status of this Document</h2>
     <p><em>
         This section describes the status of this document at the time of
         its publication.  Other documents may supersede this document. A list
@@ -46,7 +31,7 @@
         report can be found in the <a href="http://www.w3.org/TR/">W3C technical
           reports index</a> at http://www.w3.org/TR/.
       </em></p><p>
-        This document is the 9 June 2008 <b>Editor’s Draft</b> of 
+        This document is the 10 June 2008 <b>Working Draft</b> of 
         <cite>HTML 5 Publication Notes</cite>.
       
       Please send comments about this document to
@@ -59,7 +44,7 @@
       You can find the source for the current version of this document in the
       <a href="http://dev.w3.org/html5/pubnotes/Overview.src.html">W3C source repository</a>.
     </p><p>
-          Publication as a Editor’s Draft does not imply endorsement by the
+          Publication as a Working Draft does not imply endorsement by the
           W3C Membership.  This is a draft document and may be updated, replaced
           or obsoleted by other documents at any time. It is inappropriate to cite
           this document as other than work in progress.
@@ -78,20 +63,88 @@
         6 of the W3C Patent Policy</a>.
     </p></div>
     <div id="toc">
-      <h2>Table of Contents <a class="hash" href="#toc">#</a> <a class="toc-bak" href="#toc-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#toc">Table of Contents</a>” in the
-        specification</p>
-    <ul><li id="this_introduction-toc"><a href="#this_introduction">Introduction</a></li><li id="introduction-toc"><a href="#introduction">Section 1, Introduction</a><ul><li id="structure-toc"><a href="#structure">Section 1.2, Structure of this specification</a></li><li id="conformance-toc"><a href="#conformance">Section 1.3, Conformance requirements</a></li><li id="terminology-toc"><a href="#terminology">Section 1.4, Terminology</a></li></ul></li><li id="dom-toc"><a href="#dom">Section 2, The Document Object Model</a><ul><li id="documents-toc"><a href="#documents">Section 2.1, Documents</a></li><li id="elements-toc"><a href="#elements">Section 2.2, Elements</a></li><li id="common0-toc"><a href="#common0">Section 2.3, Common DOM interfaces</a></li><li id="dom-tree-toc"><a href="#dom-tree">Section 2.4, DOM tree accessors</a></li><li id="dynamic-toc"><a href="#dynamic">Section 2.5, Dynamic markup insertion</a></li><li id="apis-in-toc"><a href="#apis-in">Section 2.6, APIs in HTML documents</a></li></ul></li><i id="semantics-toc"><a href="#semantics">Section 3, Semantics and structure of HTML elements</a><ul><li id="common1-toc"><a href="#common1">Section 3.2, Common microsyntaxes</a></li><li id="documents0-toc"><a href="#documents0">Section 3.3, Documents and document fragments</a></li><li id="global-toc"><a href="#global">Section 3.4, Global attributes</a></li><li id="interaction-toc"><a href="#interaction">Section 3.5, Interaction</a></li><li id="the-root-toc"><a href="#the-root">Section 3.6, The root element</a></li><li id="document-toc"><a href="#document">Section 3.7, Document metadata</a><ul><li id="the-base-toc"><a href="#the-base">Section 3.7.3, The base element</a></li><li id="the-link-toc"><a href="#the-link">Section 3.7.4, The link element</a></li><li id="meta-toc"><a href="#meta">Section 3.7.5, The meta element</a></li><li id="the-style0-toc"><a href="#the-style0">Section 3.7.6, The style element</a></li></ul></li><li id="sections-toc"><a href="#sections">Section 3.8, Sections</a><ul><li id="the-bod-toc"><a href="#the-body">Section 3.8.1, The body element</a></li><li id="the-nav-toc"><a href="#the-nav">Section 3.8.3, The nav element</a></li><li id="blockquoteold-toc"><a href="#blockquoteold">Section 3.8.5 [now 3.9.6], The blockquote element</a></li><li id="the-aside-toc"><a href="#the-aside">Section 3.8.6 [now 3.8.5], The aside element</a></li><li id="the-header-toc"><a href="#the-header">Section 3.8.8 [now 3.8.7], The header element</a></li><li id="the-footer-toc"><a href="#the-footer">Section 3.8.9 [now 3.8.8], The footer element</a></li><li id="the-address-toc"><a href="#the-address">Section 3.8.10 [now 3.8.9], The address element</a></li><li id="headings-toc"><a href="#headings">Section 3.8.11 [now 3.8.10], Headings and sections</a></li></ul></li><li id="grouping-toc"><a href="#grouping">Section 3.9, Grouping content</a><ul><li id="the-pre-toc"><a href="#the-pre">Section 3.9.4 [was 3.10.1], The pre element</a></li><li id="the-blockquote-toc"><a href="#the-blockquote">Section 3.9.6 [was 3.8.5], Theblockquote element</a></li><li id="the-ol-toc"><a href="#the-ol">Section 3.9.7 [was 3.11.1], The ol element</a></li><li id="the-ul-toc"><a href="#the-ul">Section 3.9.8 [was 3.11.2], The ul element</a></li><li id="the-li-toc"><a href="#the-li">Section 3.9.9 [was 3.11.3], The li element</a></li><li id="the-dl-toc"><a href="#the-dl">Section 3.9.10 [was 3.11.4], The dl element</a></li><li id="the-dt-toc"><a href="#the-dt">3.9.11 [was 3.11.5], The dt element</a></li></ul></li><li id="text-level-toc"><a href="#text-level">Section 3.10 [was 3.12], Text-level semantics</a><ul><li id="the-a-toc"><a href="#the-a">Section 3.10.1, The a element</a></li><li id="the-q-toc"><a href="#the-q">Section 3.10.2, The q element</a></li><li id="the-cite-toc"><a href="#the-cite">Section 3.10.3, The cite element</a></li><li id="the-mark-toc"><a href="#the-mark">Section 3.10.7, The mark element [was: the m element]</a></li><li id="the-dfn-toc"><a href="#the-dfn">Section 3.10.8, The dfn element</a></li><li id="the-abbr-toc"><a href="#he-abbr">Section 3.10.9, The abbr element</a></li><li id="the-progress-toc"><a href="#the-progress">Section 3.10.11, The progress element</a></li><li id="the-meter-toc"><a href="#the-meter">Section 3.10.12, The meter element</a></li><li id="the-code-toc"><a href="#the-code">Section 3.10.13, The code element</a></li><li id="the-var-toc"><a href="#the-var">Section 3.10.14, The var element</a></li><li id="the-samp-toc"><a href="#the-samp">Section 3.10.15, The samp element</a></li><li id="the-sub-toc"><a href="#the-sub">Section 3.10.17, The sub and sup elements</a></li><li id="the-span-toc"><a href="#the-span">Section 3.10.18, The span element</a></li><li id="the-i-toc"><a href="#the-i">Section 3.10.19, The i element</a></li><li id="the-ruby-toc"><a href="#the-ruby">Section 3.10.22 [new], The ruby element</a></li><li id="the-rt-toc"><a href="#the-rt">Section 3.10.23 [new], The rt element</a></li><li id="the-rp-toc"><a href="#the-rp">Section 3.10.24 [new], The rp element</a></li><li id="usage-toc"><a href="#usag">Section 3.10.25 [new], Usage summary</a></li><li id="footnotes-toc"><a href="#footnotes">Section 3.10.26 [new], Footnotes</a></li></ul></li><li id="edits-toc"><a href="#edits">Section 3.11 [was 3.13], Edits</a><ul><li id="edits0-toc"><a href="#edits0">Section 3.11.4 [new], Edits and paragraphs</a></li><li id="edits1-toc"><a href="#edits1">Section 3.11.5 [new], Edits and lists</a></li></ul></li><li id="embedded0-toc"><a href="#embedded0">Section 3.12 [was 3.14], Embedded content</a><ul><li id="the-figure-toc"><a href="#the-figure">Section 3.12.1, The figure element</a></li><li id="the-img-toc"><a href="#the-img">Section 3.12.2, The img element</a></li><li id="the-iframe-toc"><a href="#the-iframe">Section 3.12.3, The iframe element</a></li><li id="the-embed-toc"><a href="#the-embed">Section 3.12.4, The embed element</a></li><li id="the-object-toc"><a href="#the-object">Section 3.12.5, The object element</a></li><li id="the-param-toc"><a href="#the-param">Section 3.12.6, The param element</a></li><li id="thevideo-toc"><a href="#the-video">Section 3.12.7, The video element</a></li><li id="the-source-toc"><a href="#the-source">Section 3.12.9, The source element</a></li><li id="media-toc"><a href="#media">Section 3.12.10, Media elements</a></li><li id="the-canvas-toc"><a href="#the-canvas">Section 3.12.11, The canvas element</a><ul><li id="the-2d-toc"><a href="#the-2d">Section 3.12.11.1, The 2D context</a></li></ul></li><li id="the-map-toc"><a href="#the-map">Section 3.12.12, The map element</a></li><li id="the-area-toc"><a href="#the-area">Section 3.12.13, The area element</a></li><li id="image-maps-toc"><a href="#image-maps">Section 3.12.14, Image maps</a></li><li id="mathml-toc"><a href="#mathml">Section 3.12.15 [new], MathML</a></li><li id="svg-toc"><a href="#svg">Section 3.12.16 [new], SVG</a></li></ul></li><li id="tabular-toc"><a href="#tabular">Section 3.13 [was 3.15], Tabular data</a><ul><li id="the-table-toc"><a href="#the-table">3.13.2, The table element</a></li><li id="the-colgroup-toc"><a href="#the-clgroup">3.13.4, The colgroup element</a></li><li id="the-col-toc"><a href="#the-col">3.13.5, The col element</a></li><li id="the-tbody-toc"><a href="#the-tbody">3.13.6, The tbody element</a></li><li id="the-thead-toc"><a href="#the-thead">3.13.7, The thead element</a></li><li id="the-tfoot-toc"><a href="#the-tfoot">3.13.8, The tfoot element</a></li><li id="the-tr-toc"><a href="#the-tr">3.13.9, The tr element</a></li><li id="the-td-toc"><a href="#the-td">3.13.10, The td element</a></li><li id="the-th-toc"><a href="#the-th">3.13.11, The th element</a></li><li id="attributes0-toc"><a href="#attributes0">3.13.12 [new], Attributes common to td and th
-              elements</a></li><li id="processing-toc"><a href="#processing">3.13.13, Processing model</a><ul><li id="tableforming-toc"><a href="#tableforming">3.13.13.1, Forming a table</a></li></ul></li></ul></li><li id="forms-toc"><a href="#forms">Section 3.14 [was 3.16], Forms</a></li><li id="scripting0-toc"><a href="#scripting0">Section 3.15 [was 3.17], Scripting</a><ul><li id="script-toc"><a href="#script">Section 3.15.1, The script element</a></li><li id="the-noscript-toc"><a href="#the-noscript">Section 3.15.2, The noscript element</a></li><li id="the-event-source-toc"><a href="#the-event-source">Section 3.15.3, The event-source element</a></li></ul></li><li id="interactive-elements-toc"><a href="#interactive-elements">Section 3.16 [was 3.18], Interactive elements</a><ul><li id="datagrid-toc"><a href="#datagrid">Section 3.16.2, The datagrid element</a></li><li id="menus-toc"><a href="#menus">Section 3.16.4, The menu element</a></li><li id="commands-toc"><a href="#commands">Section 3.16.5, Commands<a></li></ul></li><li id="datatemplate-toc"><a href="#datatemplate">Section 3.17 [was 3.19], Data Templates</a></li><li id="miscellaneous-toc"><a href="#miscellaneous">Section 3.18 [was 3.20], Miscellaneous elements</a></li></ul></li><li id="web-browsers-toc"><a href="#web-browsers">Section 4, Web browsers</a><ul><li id="windows-toc"><a href="#windows">Section 4.1, Browsing context</a></li><li id="the-default0-toc"><a href="#the-default0">Section 4.2, The default view</a></li><li id="origin-toc"><a href="#origin">Section 4.3 [was 4.3.2], Origin</a></li><li id="scripting-toc"><a href="#scripting">Section 4.3 [now 4.4], Scripting</a></li><li id="user-prompts-toc"><a href="#user-prompts">Section 4.4 [now 4.5], User prompts</a></li><li id="browser-toc"><a href="#browser">Section 4.5 [now 4.6], Browser state</a></li><li id="offline-toc"><a href="#offline">Section 4.6 [now 4.7], Offline Web applications</a></li><li id="history-toc"><a href="#history">Section 4.7 [now 4.8], Session history and navigation</a></li><l id="browsing0-toc"><a href="#browsing0">Section 4.9 [new], Browsing the Web</a></li><li id="content-type-sniffing-toc"><a href="#content-type-sniffing">Section 4.9 [now 4.10], Determining the type of a
+      <h2>Table of Contents</h2>
+    <ul><li id="summary-toc"><a href="#summary">Summary: Changes impacting Web architecture</a></li><li id="fpwd-toc"><a href="#fpwd">Changes since the First Public Working Draft</a><ul><li id="introduction-toc"><a href="#introduction">Section 1, Introduction</a><ul><li id="structure-toc"><a href="#structure">Section 1.2, Structure of this specification</a></li><li id="conformance-toc"><a href="#conformance">Section 1.3, Conformance requirements</a></li><li id="terminology-toc"><a href="#terminology">Section 1.4, Terminology</a></li></ul></li><li id="dom-toc"><a href="#dom">Section 2, The Document Object Model</a><ul><li id="documents-toc"><a href="#documents">Section 2.1, Documents</a></li><li id="elements-toc"><a href="#elements">Section 2.2, Elements</a></li><li id="common0-toc"><a href="#common0">Section 2.3, Common DOM interfaces</a></li><li id="dom-tree-toc"><a href="#dom-tree">Section 2.4, DOM tree accessors</a></li><li id="dynamic-toc"><a href="#dynamic">Section 2.5, Dynamic markup insertion</a></l><li id="apis-in-toc"><a href="#apis-in">Section 2.6, APIs in HTML documents</a></li></ul></li><li id="semantics-toc"><a href="#semantics">Section 3, Semantics and structure of HTML elements</a><ul><li id="common1-toc"><a href="#common1">Section 3.2, Common microsyntaxes</a></li><li id="documents0-toc"><a href="#documents0">Section 3.3, Documents and document fragments</a></li><li id="global-toc"><a href="#global">Section 3.4, Global attributes</a></li><li id="interaction-toc"><a href="#interaction">Section 3.5, Interaction</a></li><li id="the-root-toc"><a href="#the-root">Section 3.6, The root element</a></li><li id="document-toc"><a href="#document">Section 3.7, Document metadata</a><ul><li id="the-base-toc"><a href="#the-base">Section 3.7.3, The base element</a></li><li id="the-link-toc"><a href="#the-link">Section 3.7.4, The link element</a></li><li id="meta-toc"><a href="#meta">Section 3.7.5, The meta element</a></li><li id="the-style0-toc"><a href="#the-style0">Section 3.7.6, The style element</a></li</ul></li><li id="sections-toc"><a href="#sections">Section 3.8, Sections</a><ul><li id="the-body-toc"><a href="#the-body">Section 3.8.1, The body element</a></li><li id="the-nav-toc"><a href="#the-nav">Section 3.8.3, The nav element</a></li><li id="blockquoteold-toc"><a href="#blockquoteold">Section 3.8.5 [now 3.9.6], The blockquote element</a></li><li id="the-aside-toc"><a href="#the-aside">Section 3.8.6 [now 3.8.5], The aside element</a></li><li id="the-header-toc"><a href="#the-header">Section 3.8.8 [now 3.8.7], The header element</a></li><li id="the-footer-toc"><a href="#the-footer">Section 3.8.9 [now 3.8.8], The footer element</a></li><li id="the-address-toc"><a href="#the-address">Section 3.8.10 [now 3.8.9], The address element</a></li><li id="headings-toc"><a href="#headings">Section 3.8.11 [now 3.8.10], Headings and sections</a></li></ul></li><li id="grouping-toc"><a href="#grouping">Section 3.9, Grouping content</a><ul><li id="the-pre-toc"><a href="#the-pre">Section 3.9.4 [was 3.10.1], The pre eleent</a></li><li id="the-blockquote-toc"><a href="#the-blockquote">Section 3.9.6 [was 3.8.5], The blockquote element</a></li><li id="the-ol-toc"><a href="#the-ol">Section 3.9.7 [was 3.11.1], The ol element</a></li><li id="the-ul-toc"><a href="#the-ul">Section 3.9.8 [was 3.11.2], The ul element</a></li><li id="the-li-toc"><a href="#the-li">Section 3.9.9 [was 3.11.3], The li element</a></li><li id="the-dl-toc"><a href="#the-dl">Section 3.9.10 [was 3.11.4], The dl element</a></li><li id="the-dt-toc"><a href="#the-dt">Section 3.9.11 [was 3.11.5], The dt element</a></li></ul></li><li id="text-level-toc"><a href="#text-level">Section 3.10 [was 3.12], Text-level semantics</a><ul><li id="the-a-toc"><a href="#the-a">Section 3.10.1, The a element</a></li><li id="the-q-toc"><a href="#the-q">Section 3.10.2, The q element</a></li><li id="the-cite-toc"><a href="#the-cite">Section 3.10.3, The cite element</a></li><li id="the-mark-toc"><a href="#the-mark">Section 3.10.7, The mark element [was: the m element]</a></li><li id=the-dfn-toc"><a href="#the-dfn">Section 3.10.8, The dfn element</a></li><li id="the-abbr-toc"><a href="#the-abbr">Section 3.10.9, The abbr element</a></li><li id="the-progress-toc"><a href="#the-progress">Section 3.10.11, The progress element</a></li><li id="the-meter-toc"><a href="#the-meter">Section 3.10.12, The meter element</a></li><li id="the-code-toc"><a href="#the-code">Section 3.10.13, The code element</a></li><li id="the-var-toc"><a href="#the-var">Section 3.10.14, The var element</a></li><li id="the-samp-toc"><a href="#the-samp">Section 3.10.15, The samp element</a></li><li id="the-sub-toc"><a href="#the-sub">Section 3.10.17, The sub and sup elements</a></li><li id="the-span-toc"><a href="#the-span">Section 3.10.18, The span element</a></li><li id="the-i-toc"><a href="#the-i">Section 3.10.19, The i element</a></li><li id="the-ruby-toc"><a href="#the-ruby">Section 3.10.22 [new], The ruby element</a></li><li id="the-rt-toc"><a href="#the-rt">Section 3.10.23 [new], The rt element</a></li><li id="the-p-toc"><a href="#the-rp">Section 3.10.24 [new], The rp element</a></li><li id="usage-toc"><a href="#usage">Section 3.10.25 [new], Usage summary</a></li><li id="footnotes-toc"><a href="#footnotes">Section 3.10.26 [new], Footnotes</a></li></ul></li><li id="edits-toc"><a href="#edits">Section 3.11 [was 3.13], Edits</a><ul><li id="edits0-toc"><a href="#edits0">Section 3.11.4 [new], Edits and paragraphs</a></li><li id="edits1-toc"><a href="#edits1">Section 3.11.5 [new], Edits and lists</a></li></ul></li><li id="embedded0-toc"><a href="#embedded0">Section 3.12 [was 3.14], Embedded content</a><ul><li id="the-figure-toc"><a href="#the-figure">Section 3.12.1, The figure element</a></li><li id="the-img-toc"><a href="#the-img">Section 3.12.2, The img element</a></li><li id="the-iframe-toc"><a href="#the-iframe">Section 3.12.3, The iframe element</a></li><li id="the-embed-toc"><a href="#the-embed">Section 3.12.4, The embed element</a></li><li id="the-object-toc"><a href="#the-object">Section 3.12.5, The object element<a></li><li id="the-param-toc"><a href="#the-param">Section 3.12.6, The param element</a></li><li id="the-video-toc"><a href="#the-video">Section 3.12.7, The video element</a></li><li id="the-source-toc"><a href="#the-source">Section 3.12.9, The source element</a></li><li id="media-toc"><a href="#media">Section 3.12.10, Media elements</a></li><li id="the-canvas-toc"><a href="#the-canvas">Section 3.12.11, The canvas element</a><ul><li id="the-2d-toc"><a href="#the-2d">Section 3.12.11.1, The 2D context</a></li></ul></li><li id="the-map-toc"><a href="#the-map">Section 3.12.12, The map element</a></li><li id="the-area-toc"><a href="#the-area">Section 3.12.13, The area element</a></li><li id="image-maps-toc"><a href="#image-maps">Section 3.12.14, Image maps</a></li><li id="mathml-toc"><a href="#mathml">Section 3.12.15 [new], MathML</a></li><li id="svg-toc"><a href="#svg">Section 3.12.16 [new], SVG</a></li></ul></li><li id="tabular-toc"><a href="#tabular">Section 3.13 [was 3.15], Tabular data</a><ul><li id="the-tale-toc"><a href="#the-table">Section 3.13.2, The table element</a></li><li id="the-colgroup-toc"><a href="#the-colgroup">Section 3.13.4, The colgroup element</a></li><li id="the-col-toc"><a href="#the-col">Section 3.13.5, The col element</a></li><li id="the-tbody-toc"><a href="#the-tbody">Section 3.13.6, The tbody element</a></li><li id="the-thead-toc"><a href="#the-thead">Section 3.13.7, The thead element</a></li><li id="the-tfoot-toc"><a href="#the-tfoot">Section 3.13.8, The tfoot element</a></li><li id="the-tr-toc"><a href="#the-tr">Section 3.13.9, The tr element</a></li><li id="the-td-toc"><a href="#the-td">Section 3.13.10, The td element</a></li><li id="the-th-toc"><a href="#the-th">Section 3.13.11, The th element</a></li><li id="attributes0-toc"><a href="#attributes0">Section 3.13.12 [new], Attributes common to td and th
+              elements</a></li><li id="processing-toc"><a href="#processing">Section 3.13.13, Processing model</a></li></ul></li><li id="forms-toc"><a href="#forms">Section 3.14 [was 3.16], Forms</a></li><li id="scripting0-toc"><a href="#scripting0">Section 3.15 [was 3.17], Scripting</a><ul><li id="script-toc"><a href="#script">Section 3.15.1, The script element</a></li><li id="the-noscript-toc"><a href="#the-noscript">Section 3.15.2, The noscript element</a></li><li id="the-event-source-toc"><a href="#the-event-source">Section 3.15.3, The event-source element</a></li></ul></li><li id="interactive-elements-toc"><a href="#interactive-elements">Section 3.16 [was 3.18], Interactive elements</a><ul><li id="datagrid-toc"><a href="#datagrid">Section 3.16.2, The datagrid element</a></li><li id="menus-toc"><a href="#menus">Section 3.16.4, The menu element</a></li><li id="commands-toc"><a href="#commands">Section 3.16.5, Commands</a></li></ul></li><li id="datatemplate-toc"><a href="#datatemplate">Section 3.17 [was .19], Data Templates</a></li><li id="miscellaneous-toc"><a href="#miscellaneous">Section 3.18 [was 3.20], Miscellaneous elements</a></li></ul></li><li id="web-browsers-toc"><a href="#web-browsers">Section 4, Web browsers</a><ul><li id="windows-toc"><a href="#windows">Section 4.1, Browsing context</a></li><li id="the-default0-toc"><a href="#the-default0">Section 4.2, The default view</a></li><li id="origin-toc"><a href="#origin">Section 4.3 [was 4.3.2], Origin</a></li><li id="scripting-toc"><a href="#scripting">Section 4.3 [now 4.4], Scripting</a></li><li id="user-prompts-toc"><a href="#user-prompts">Section 4.4 [now 4.5], User prompts</a></li><li id="browser-toc"><a href="#browser">Section 4.5 [now 4.6], Browser state</a></li><li id="offline-toc"><a href="#offline">Section 4.6 [now 4.7], Offline Web applications</a></li><li id="history-toc"><a href="#history">Section 4.7 [now 4.8], Session history and navigation</a></li><li id="browsing0-toc"><a href="#browsing0">Section 4.9 [new], Browsing the Web</a></li>li id="content-type-sniffing-toc"><a href="#content-type-sniffing">Section 4.9 [now 4.10], Determining the type of a
             new resource in a browsing context</a></li><li id="structured-toc"><a href="#structured">Section 4.11 [new], Structured client-side storage</a></li><li id="links-toc"><a href="#links">Section 4.12, Links</a></li><li id="interfaces-toc"><a href="#interfaces">Section 4.13, Interfaces for URI manipulation</a></li></ul></li><li id="editing-toc"><a href="#editing">Section 5, Editing</a><ul><li id="contenteditable-toc"><a href="#contenteditable">Section 5.2, The contenteditable attribute</a></li><li id="dnd-toc"><a href="#dnd">Section 5.3, Drag and drop</a></li><li id="undo-toc"><a href="#undo">Section 5.4, Undo history</a></li><li id="command-toc"><a href="#command">Section 5.5 [now 5.6], Command APIs</a></li><li id="selection-toc"><a href="#selection">Section 5.6 [now 5.5], The text selection APIs</a></li></ul></li><li id="comms-toc"><a href="#comms">Section 6, Communication</a><ul><li id="event1-toc"><a href="#event1">Section 6.1, Event definitions</a></li><li id="server-sent-events-toc"><a href="server-sent-events">Section 6.2, Server-sent DOM events</a></li><li id="network-toc"><a href="#network">Section 6.3, Network connections</a></li><li id="crossDocumentMessages-toc"><a href="#crossDocumentMessages">Section 6.4, Cross-document messaging</a></li></ul></li><li id="repetition-toc"><a href="#repetition">Section 7, Repetition templates</a></li><li id="syntax-toc"><a href="#syntax">Section 8, The HTML syntax</a><ul><li id="writing0-toc"><a href="#writing0">Section 8.1, Writing HTML documents</a></li><li id="parsing-toc"><a href="#parsing">Section 8.2, Parsing HTML documents</a></li><li id="namespaces-toc"><a href="#namespaces">Section 8.3, Namespaces</a></li><li id="serializing-toc"><a href="#serializing">Section 8.4, Serializing HTML fragments</a></li><li id="parsing2-toc"><a href="#parsing2">Section 8.5, Parsing HTML fragments</a></li><li id="named-toc"><a href="#named">Section 8.6, Entities [now "Named character references"]</a></li></ul></li><li id="wsiwyg-toc"><a href="#wsiwyg">Section 9 [now rmoved], WYSIWYG editors</a></li><li id="rendering-toc"><a href="#rendering">Section 10 [now section 9], Rendering and
           user-agent behavior</a></li><li id="no-toc"><a href="#no">Section 11 [now section 10], Things that you
-          can't do with this specification…</a></li><li id="acknowledgements-toc"><a href="#acknowledgements">Acknowledgements</a></li></ul></div>
+          can't do with this specification…</a></li></ul></li><li id="acknowledgements-toc"><a href="#acknowledgements">Acknowledgements</a></li></ul></div>
     <div id="this_sections">
-      <div id="this_introduction" class="section">
-        <h2>Introduction <a class="hash" href="#this_introduction">#</a> <a class="toc-bak" href="#this_introduction-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#this_introduction">Introduction</a>” in the
-        specification</p>
-        <p>This document provides a per-section record of changes
-        to the HTML 5 draft specification since its publication as
-        a First Public Working Draft (FPWD). Note that it
+      <div id="summary" class="section">
+    
+    <h2>Summary: Changes impacting Web architecture <a href="#summary">#</a> <a href="#summary-toc">T</a></h2>
+    
+
+    <p>This section provides a high-level summary of changes
+      introduced by new areas or features of the HTML 5
+      specification that are believed to impact the Web
+      architecture. For more detailed descriptions of the changes,
+      see the sections in this document that follow this one.
+      (Note: The source for this summary is maintained in the <a href="http://www.w3.org/TR/html5-diff/">HTML 5
+        differences from HTML 4</a> document; the summary was
+      copied from that document into this one.)</p>
+
+    <ul>
+     <li>The use of the DOM as a basis for defining the language.</li>
+
+     <li>The concept of browsing contexts.</li>
+
+     <li>The distinction between user agent requirements and authoring
+     requirements.</li>
+
+     <li>The use of imperative definitions rather than abstract definitions
+     with the requirement of black-box equivalence in implementations.</li>
+
+     <li>The new content model concepts (replacing HTML 4's block and
+     inline concepts).</li>
+
+     <li>The focus on accessibility as a built-in concept for new features
+     (such as the <code>irrelevant</code> attribute, the
+     <code>progress</code> element, et cetera) instead of an add-on (like
+     the <code>alt</code> attribute).</li>
+
+     <li>The focus on defining the semantics in detail (e.g. the outline
+     algorithm, replacing the vague semantics in HTML 4).</li>
+
+     <li>The server-sent events feature (the <code>event-source</code>
+     element).</li>
+
+     <li>The <code>datagrid</code> element.</li>
+
+     <li>The <code>menu</code> and <code>command</code> elements.</li>
+
+     <li>The origin concept.</li>
+
+     <li>Offline Web application caches.</li>
+
+     <li>The definition of the browsing context "navigation" algorithm and
+     the related session history traversal algorithms.</li>
+
+     <li>The content-type sniffing and character encoding sniffing.</li>
+
+     <li>The very explicit definition of a parser.</li>
+
+     <li>The two structured storage features.</li>
+
+     <li>The <code>contentEditable</code> feature and the
+     <code>UndoManager</code> feature.</li>
+
+     <li>The Drag and Drop and Copy and Paste architecture.</li>
+
+     <li>The cross-document messaging feature (the
+     <code>postMessage</code> API).</li>
+
+     <li>The new sandboxing features for <code>iframe</code>.</li>
+    </ul>
+    
+    </div>
+      <div id="fpwd" class="section">
+        <h2>Changes since the First Public Working Draft <a class="hash" href="#fpwd">#</a> <a class="toc-bak" href="#fpwd-toc">T</a></h2>
+        <p>This section provides a per-section record of changes
+        to the HTML 5 draft specification after the <a href="http://www.w3.org/TR/2008/WD-html5-20080122/">22
+          January 2008 First Public Working Draft (FPWD)</a> and
+        until
+        the time of publication of this document. Note that it
         documents substantive changes only, and omits editorial
         changes. It is intended to be readable as a “standalone”
         document — meaning that readers are meant to be able to
@@ -99,7 +152,6 @@
         made, without necessarily needing to read the
         specification itself or to read through the entire diff
         document that shows all the changes.</p>
-      </div>
       <div id="introduction" class="section">
         <h2>Section 1, Introduction <a class="hash" href="#introduction">#</a> <a class="toc-bak" href="#introduction-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#introduction">Section 1, Introduction</a>” in the
         specification</p>
@@ -139,7 +191,8 @@
             <li>In the “Conformance checkers” subsection, the text
             of a statement was updated to now read (added text
             highlighted):
-            <blockquote><q><em class="highlight">Automated</em>
+            <blockquote>
+              <p><q><em class="highlight">Automated</em>
                 conformance checkers are exempt from detecting
                 errors that require interpretation of the author’s
                 intent (for example, while a document is
@@ -148,12 +201,14 @@
                 <em class="highlight">running without the input of
                   human judgement</em> do not have to check that
                 blockquote elements only contain quoted
-                material).</q></blockquote>
+                material).</q></p>
+            </blockquote>
             Also, the text of a related statement was updated to
             reference the concept of the <strong>browsing
               context</strong>; the text of that statement now
             reads:
-            <blockquote><q>Conformance checkers must check that
+            <blockquote>
+              <p><q>Conformance checkers must check that
                 the input document conforms when parsed without a
                 browsing context (meaning that no scripts are run,
                 and that the parser’s scripting flag is disabled),
@@ -162,7 +217,8 @@
                 which scripts execute, and that the scripts never
                 cause non-conforming states to occur other than
                 transiently during script execution
-                itself.</q></blockquote></li>
+                itself.</q></p>
+            </blockquote></li>
             <li>In the “Common conformance requirements for APIs
             exposed to JavaScript” subsection, for consistency
             with the Web IDL specification, statements related
@@ -518,24 +574,28 @@
             <li>The <code class="htmlattribute">onstorage</code> attribute
             was added to the list of global attributes.</li>
             <li>The following conformance statement was added:
-            <blockquote><q>custom data attributes (e.g.
+            <blockquote>
+              <p><q>custom data attributes (e.g.
                 data-foldername or data-msgid) can be specified on
                 any HTML element, to store custom data specific to
-                the page.</q></blockquote>
+                the page.</q></p>
+            </blockquote>
             Also, an “Embedding custom non-visible data” subsection
             was added, with conformance criteria related to
             <code class="htmlattribute">data-</code> attributes and
             the associated <code class="domattribute">dataset</code>
             DOM attribute.</li>
             <li>The following conformance statement was added:
-            <blockquote><q>In HTML documents, the html element,
+            <blockquote>
+              <p><q>In HTML documents, the html element,
                 and any other elements in the HTML namespace whose
                 parent element is not in the HTML namespace, may
                 have an <code class="htmlattribute">xmlns</code>
                 attribute specified, if, and only if, it has the
                 exact value
                 “<code>http://www.w3.org/1999/xhtml</code>”. This
-                does not apply to XML documents.</q></blockquote>
+                does not apply to XML documents.</q></p>
+            </blockquote>
             Also, two notes were added regarding the effects of
             the <code class="htmlattribute">xmlns</code> attribute in
             content.</li>
@@ -637,15 +697,19 @@
               <li>Other refinements were made
               to language in this section, including the addition
               of the following statements:
-              <blockquote><q>HTTP semantics must be followed when
+              <blockquote>
+                <p><q>HTTP semantics must be followed when
                   fetching external resources. (For example,
                   redirects must be followed and 404 responses must
                   cause the external resource to not be
-                  applied.)</q></blockquote>
-              <blockquote><q>If no type metadata is specified, but
+                  applied.)</q></p>
+              </blockquote>
+              <blockquote>
+                <p><q>If no type metadata is specified, but
                   the external resource link type has a default type
                   defined, then the user agent must assume that the
-                  resource is of that type.</q></blockquote>
+                  resource is of that type.</q></p>
+              </blockquote>
               </li>
             </ul>
           </div>
@@ -685,10 +749,12 @@
               list of pre-defined values for the 
               <code class="domattribute">name</code>
               attribute, and defined as:
-              <blockquote><q>The value must be a free-form string that
+              <blockquote>
+                <p><q>The value must be a free-form string that
                   describes the page. The value must be appropriate
                   for use in a directory of pages, e.g. in a search
-                  engine.</q></blockquote>
+                  engine.</q></p>
+              </blockquote>
               </li>
               <li>The value 
               <code>application-name</code>
@@ -696,7 +762,8 @@
               list of pre-defined values for the 
               <code class="domattribute">name</code>
               attribute, and defined as:
-              <blockquote><q>The value must be a short free-form
+              <blockquote>
+                <p><q>The value must be a short free-form
                   string that giving the name of the Web application
                   that the page represents. If the page is not a Web
                   application, the application-name metadata name must
@@ -705,7 +772,8 @@
                   the title might include status messages and the like
                   relevant to the status of the page at a particular
                   moment in time instead of just being the name of the
-                  application.</q></blockquote>
+                  application.</q></p>
+              </blockquote>
               </li>
               <li>The
               <code>Content-Type</code> keyword
@@ -753,14 +821,16 @@
         specification</p>
             <p>In this section, an example was added, along with
             the following statement:</p>
-            <blockquote><q>Not all groups of links on a page need
+            <blockquote>
+              <p><q>Not all groups of links on a page need
                 to be in a nav element — only sections that
                 consist of primary navigation blocks are
                 appropriate for the nav element. In particular, it
                 is common for footers to have a list of links to
                 various key parts of a site, but the footer
                 element is more appropriate in such
-                cases.</q></blockquote>
+                cases.</q></p>
+            </blockquote>
           </div>
           <div id="blockquoteold" class="section">
             <h2>Section 3.8.5 [now 3.9.6], The blockquote element <a class="hash" href="#blockquoteold">#</a> <a class="toc-bak" href="#blockquoteold-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#blockquoteold">Section 3.8.5 [now 3.9.6], The blockquote element</a>” in the
@@ -829,9 +899,11 @@
             down in the sectioning hierarchy to become a subsection
             the “Grouping content” section. Also, the following note
             was added:</p>
-            <blockquote><q> In the HTML serialisation, a leading
+            <blockquote>
+              <p><q> In the HTML serialisation, a leading
                 newline character immediately following the pre
-                element start tag is stripped.</q></blockquote>
+                element start tag is stripped.</q></p>
+            </blockquote>
           </div>
           <div id="the-blockquote" class="section">
             <h2>Section 3.9.6 [was 3.8.5], The blockquote element <a class="hash" href="#the-blockquote">#</a> <a class="toc-bak" href="#the-blockquote-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-blockquote">Section 3.9.6 [was 3.8.5], The blockquote element</a>” in the
@@ -921,16 +993,18 @@
             </ul>
           </div>
           <div id="the-dt" class="section">
-            <h2>3.9.11 [was 3.11.5], The dt element <a class="hash" href="#the-dt">#</a> <a class="toc-bak" href="#the-dt-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-dt">3.9.11 [was 3.11.5], The dt element</a>” in the
+            <h2>Section 3.9.11 [was 3.11.5], The dt element <a class="hash" href="#the-dt">#</a> <a class="toc-bak" href="#the-dt-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-dt">Section 3.9.11 [was 3.11.5], The dt element</a>” in the
         specification</p>
             <p>In this section, the following statement was
             added:</p>
-            <blockquote><q>If the dt element is the child of a
+            <blockquote>
+              <p><q>If the dt element is the child of a
                 dialog element, and it further contains a time
                 element, then that time element represents a
                 timestamp for when the associated discourse (dd
                 element) was said, and is not part of the name of
-                the talker.</q></blockquote>
+                the talker.</q></p>
+            </blockquote>
             <p>Also, two examples were added.</p>
           </div>
         </div>
@@ -955,9 +1029,11 @@
             <p>In this section, some wording changes were made,
             four examples were added, and the following statement
             was added:</p>
-            <blockquote><q>Quotation punctuation (such as
+            <blockquote>
+              <p><q>Quotation punctuation (such as
                 quotation marks), if any, must be placed inside
-                the q element.</q></blockquote>
+                the q element.</q></p>
+            </blockquote>
           </div>
           <div id="the-cite" class="section">
             <h2>Section 3.10.3, The cite element <a class="hash" href="#the-cite">#</a> <a class="toc-bak" href="#the-cite-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-cite">Section 3.10.3, The cite element</a>” in the
@@ -967,7 +1043,8 @@
             simply, “The cite element represents a citation: the
             source, or reference, for a quote or statement made in
             the document”, was expanded to read:</p>
-            <blockquote><q>The cite element represents the title
+            <blockquote>
+              <p><q>The cite element represents the title
                 of a work (e.g. a book, a paper, an essay, a poem,
                 a score, a song, a script, a film, a TV show, a
                 game, a sculpture, a painting, a theatre
@@ -975,8 +1052,10 @@
                 exhibition, etc). This can be a work that is being
                 quoted or referenced in detail (i.e. a citation),
                 or it can just be a work that is mentioned in
-                passing.</q></blockquote>
-            <blockquote><q>A person’s name is not the title of a
+                passing.</q></p>
+            </blockquote>
+            <blockquote>
+              <p><q>A person’s name is not the title of a
                 work — even if people call that person a piece of
                 work — and the element must therefore not be used
                 to mark up people’s names. (In some cases, the b
@@ -985,11 +1064,14 @@
                 are keywords rendered with a different style to
                 draw attention to them. In other cases, if an
                 element is really needed, the span element can be
-                used.)</q></blockquote>
-            <blockquote><q>A ship is similarly not a work, and the
+                used.)</q></p>
+            </blockquote>
+            <blockquote>
+              <p><q>A ship is similarly not a work, and the
                 element must not be used to mark up ship names
                 (the i element can be used for that
-                purpose).</q></blockquote>
+                purpose).</q></p>
+            </blockquote>
           </div>
           <div id="the-mark" class="section">
             <h2>Section 3.10.7, The mark element [was: the m element] <a class="hash" href="#the-mark">#</a> <a class="toc-bak" href="#the-mark-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-mark">Section 3.10.7, The mark element [was: the m element]</a>” in the
@@ -1001,7 +1083,8 @@
             meaning of the element, which had read simply, “The m
             element represents a run of text marked or
             highlighted”, was expanded to read:</p>
-            <blockquote><q>The mark element represents a run of
+            <blockquote>
+              <p><q>The mark element represents a run of
                 text in one document marked or highlighted for
                 reference purposes, due to its relevance in
                 another context. When used in a quotation or other
@@ -1016,7 +1099,8 @@
                 of a document, it indicates a part of the document
                 that has been highlighted due to its likely
                 relevance to the user’s current
-                activity.</q></blockquote>
+                activity.</q></p>
+            </blockquote>
           </div>
           <div id="the-dfn" class="section">
             <h2>Section 3.10.8, The dfn element <a class="hash" href="#the-dfn">#</a> <a class="toc-bak" href="#the-dfn-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-dfn">Section 3.10.8, The dfn element</a>” in the
@@ -1196,7 +1280,8 @@
               <li>A refinement was made to one of the
               examples.</li>
               <li>The following note was added:
-              <blockquote><q>Authors are encouraged to use the
+              <blockquote>
+                <p><q>Authors are encouraged to use the
                   class attribute on the i element to identify why
                   the element is being used, so that if the style
                   of a particular use (e.g. dream sequences as
@@ -1204,7 +1289,8 @@
                   a later date, the author doesn’t have to go
                   through the entire document (or series of
                   related documents) annotating each
-                  use.</q></blockquote>
+                  use.</q></p>
+              </blockquote>
               </li>
             </ul>
           </div>
@@ -1329,14 +1415,16 @@
                 be moved away from the main flow of the document
                 without affecting the document’s meaning.</em></li>
               <li>The following statement was added:
-              <blockquote><q>The element can thus be used to
+              <blockquote>
+                <p><q>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.</q></blockquote></li>
+                  appendix.</q></p>
+              </blockquote></li>
               <li>Several examples were added.</li>
             </ul>
           </div>
@@ -1351,33 +1439,41 @@
               obvious textual alternative” to simply, “A key part of
               the content”. The text of that same subsection was
               changed to now read:
-              <blockquote><q>In some cases, the image is a critical
+              <blockquote>
+                <p><q>In some cases, the image is a critical
                   part of the content. This could be the case, for
                   instance, on a page that is part of a photo
                   gallery. The image is the whole point of the page
-                  containing it.</q></blockquote>
+                  containing it.</q></p>
+              </blockquote>
 
-              <blockquote><q>When it is possible for alternative
+              <blockquote>
+                <p><q>When it is possible for alternative
                   text to be provided, for example if the image is
                   part of a series of screenshots in a magazine
                   review, or part of a comic strip, or is a
                   photograph in a blog entry about that photograph,
                   text that conveys can serve as a substitute for
                   the image must be given as the contents of the alt
-                  attribute.</q></blockquote>
+                  attribute.</q></p>
+              </blockquote>
 
-              <blockquote><q>In a rare subset of these cases, there
+              <blockquote>
+                <p><q>In a rare subset of these cases, there
                   might be no alternative text available. This could
                   be the case, for instance, on a photo upload site,
                   if the site has received 8000 photos from a user
                   without the user annotating any of them. In such
                   cases, the alt attribute may be omitted, but the
                   alt attribute should be included, with a useful
-                  value, if at all possible.</q></blockquote>
+                  value, if at all possible.</q></p>
+              </blockquote>
 
-              <blockquote><q>In any case, if an image is a key part
+              <blockquote>
+                <p><q>In any case, if an image is a key part
               of the content, the alt attribute must not be
-              specified with an empty value.</q></blockquote>
+              specified with an empty value.</q></p>
+              </blockquote>
               </li>
               <li>The <code class="htmlattribute">alt</code> text for the
               “Screenshot of a KDE desktop” example was expanded.</li>
@@ -1405,12 +1501,16 @@
                 executing.</q></li>
               <li>Some additional examples were added, prefaced by the
               following text:
-              <blockquote><q>A single image can have different
+              <blockquote>
+                <p><q>A single image can have different
                   appropriate alternative text depending on the
-                  context.</q></blockquote>
-              <blockquote><q> In each of the following cases, the same
+                  context.</q></p>
+              </blockquote>
+              <blockquote>
+                <p><q> In each of the following cases, the same
                   image is used, yet the alt text is different each
-                  time.</q></blockquote>
+                  time.</q></p>
+              </blockquote>
               </li>
             </ul>
           </div>
@@ -1526,13 +1626,15 @@
               and the case when the <strong>sandboxed plugins browsing
                 context flag</strong> is set.</li>
               <li>The following statement was added:
-                <blockquote><q>Whenever
+              <blockquote>
+                <p><q>Whenever
                 the name attribute is set, if the object element
                 has a nested browsing context, its name must be
                 changed to the new value. If the attribute is
                 removed, if the object element has a browsing
                 context, the browsing context name must be set to
-                the empty string.</q></blockquote></li>
+                the empty string.</q></p>
+              </blockquote></li>
               <li>Significant revisions and additions were made to
               the algorithm for checking what the object element
               represents, including a step for checking for the
@@ -1541,7 +1643,8 @@
               for the case where the <code class="htmlattribute">data</code> attribute is
               present.</li>
               <li>The following note was added:
-              <blockquote><q>The object
+              <blockquote>
+                <p><q>The object
                 element can, in certain cases as described above,
                 instantiate third-party handlers. This
                 specification does not define a mechanism for
@@ -1550,7 +1653,8 @@
                 opt to support a plugin mechanism such as the
                 Netscape Plugin API; others may use remote content
                 convertors or have built-in support for certain
-                types.</q></blockquote>
+                types.</q></p>
+              </blockquote>
               </li>
               <li>Two examples were added.</li>
             </ul>
@@ -1607,7 +1711,8 @@
               <code class="domattribute">pixelratio</code>
               DOM attribute were added, including the following
               statement:
-              <blockquote><q>The pixelratio attribute allows the
+              <blockquote>
+                <p><q>The pixelratio attribute allows the
                   author to specify the pixel ratio of anamorphic
                   media resources that do not self-describe their
                   pixel ratio. The attribute value, if specified,
@@ -1619,7 +1724,8 @@
                   the rendered width that gives the correct aspect
                   ratio). The default value, if the attribute is
                   omitted or cannot be parsed, is
-                  1.0.</q></blockquote></li>
+                  1.0.</q></p>
+              </blockquote></li>
             </ul>
           </div>
           <div id="media" class="section">
@@ -1691,17 +1797,21 @@
             made:</p>
             <ul>
               <li>The following statements were added:
-              <blockquote><q>Arguments other than the contextId
+              <blockquote>
+                <p><q>Arguments other than the contextId
                   must be ignored, and must not cause the user
                   agent to raise an exception (as would normally
                   occur if a method was called with the wrong
-                  number of arguments).</q></blockquote>
-              <blockquote><q>If the canvas has no pixels (i.e.
+                  number of arguments).</q></p>
+              </blockquote>
+              <blockquote>
+                <p><q>If the canvas has no pixels (i.e.
                   either its horizontal dimension or its vertical
                   dimension is zero) then the method must return
                   the string “data:,”. (This is the shortest data:
                   URI; it represents the empty string in a
-                  text/plain resource.)</q></blockquote>
+                  text/plain resource.)</q></p>
+              </blockquote>
               </li>
               <li>Some instances of the phrase “with scripting
               enabled” and “with scripting disabled” were changed
@@ -1712,7 +1822,8 @@
               <code class="method">toDataURL()</code> method with
               image types other than PNG was emended to read
               (added text highlighted):
-              <blockquote><q>When trying to use types other than
+              <blockquote>
+                <p><q>When trying to use types other than
                   image/png, authors can check if the image was
                   really returned in the requested format by
                   checking to see if the returned string starts
@@ -1722,7 +1833,8 @@
                   (The one exception to this is if the canvas has
                   either no height or no width, in which case the
                   result might simply be
-                  “data:,”.)</q></blockquote>
+                  “data:,”.)</q></p>
+              </blockquote>
               </li>
               <li>A statement regarding preventing information
               leakage from the
@@ -1768,29 +1880,37 @@
                 <li>A new “Security with canvas elements”
                 subsection was added. It begins with the following
                 statement:
-                <blockquote><q>Information leakage can occur if
+                <blockquote><p>
+                  <q>Information leakage can occur if
                     scripts from one origin are exposed to images
                     from another origin (one that isn’t the
-                    same).</q></blockquote>
-                <blockquote><q>To mitigate this, canvas elements
+                    same).</q></p>
+                </blockquote>
+                <blockquote>
+                  <p><q>To mitigate this, canvas elements
                     are defined to have a flag indicating whether
                     they are origin-clean. All canvas elements
                     must start with their origin-clean set to
-                    true.</q></blockquote>
+                    true.</q></p>
+                </blockquote>
                 It then lists a specific set actions, each of
                 which must cause the <var>origin-clean</var> flag
                 to be set to <code>false</code>. In addition, it
                 includes the following statements:
-                <blockquote><q>Whenever the toDataURL() method of
+                <blockquote>
+                  <p><q>Whenever the toDataURL() method of
                     a canvas element whose origin-clean flag is
                     set to false is called, the method must
                     immediately raise a security
-                    exception.</q></blockquote>
-                <blockquote><q>Whenever the getImageData() method
+                    exception.</q></p>
+                </blockquote>
+                <blockquote>
+                  <p><q>Whenever the getImageData() method
                     of the 2D context of a canvas element whose
                     origin-clean flag is set to false is called,
                     the method must immediately raise a security
-                    exception.</q></blockquote>
+                    exception.</q></p>
+                </blockquote>
                 </li>
               </ul>
             </div>
@@ -1831,49 +1951,61 @@
         specification</p>
             <p>This short section is newly added. It reads in
             whole:</p>
-            <blockquote><q>The math element from the MathML
+            <blockquote>
+              <p><q>The math element from the MathML
                 namespace falls into the embedded content category
                 for the purposes of the content models in this
-                specification.</q></blockquote>
+                specification.</q></p>
+            </blockquote>
 
-            <blockquote><q>User agents must handle text other than
+            <blockquote>
+              <p><q>User agents must handle text other than
                 inter-element whitespace found in MathML elements
                 whose content models do not allow raw text by
                 pretending for the purposes of MathML content
                 models, layout, and rendering that that text is
                 actually wrapped in an mtext element in the MathML
                 namespace. (Such text is not, however,
-                conforming.)</q></blockquote>
+                conforming.)</q></p>
+            </blockquote>
 
-            <blockquote><q>User agents must act as if any MathML element
+            <blockquote>
+              <p><q>User agents must act as if any MathML element
                 whose contents does not match the element’s
                 content model was replaced, for the purposes of
                 MathML layout and rendering, by an merror element
                 in the MathML namespace containing some appropiate
-                error message.</q></blockquote>
+                error message.</q></p>
+            </blockquote>
 
-            <blockquote><q>To enable authors to use MathML tools that only
+            <blockquote>
+              <p><q>To enable authors to use MathML tools that only
                 accept MathML in its XML form, interactive HTML
                 user agents are encouraged to provide a way to
                 export any MathML fragment as a
                 namespace-well-formed XML
-                fragment.</q></blockquote>
+                fragment.</q></p>
+            </blockquote>
           </div>
           <div id="svg" class="section">
             <h2>Section 3.12.16 [new], SVG <a class="hash" href="#svg">#</a> <a class="toc-bak" href="#svg-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#svg">Section 3.12.16 [new], SVG</a>” in the
         specification</p>
             <p>This short section is newly added. It reads in
             whole:</p>
-            <blockquote><q>The svg element from the SVG namespace
+            <blockquote>
+              <p><q>The svg element from the SVG namespace
                 falls into the embedded content category for the
                 purposes of the content models in this
-                specification.</q></blockquote>
+                specification.</q></p>
+            </blockquote>
 
-            <blockquote><q>To enable authors to use SVG tools that only
+            <blockquote>
+              <p><q>To enable authors to use SVG tools that only
                 accept SVG in its XML form, interactive HTML user
                 agents are encouraged to provide a way to export
                 any SVG fragment as a namespace-well-formed XML
-                fragment.</q></blockquote>
+                fragment.</q></p>
+            </blockquote>
           </div>
         </div>
         <div id="tabular" class="section">
@@ -1883,7 +2015,7 @@
           <code class="element">table</code>
           element and its descendant-element hierarchy.</p>
           <div id="the-table" class="section">
-            <h2>3.13.2, The table element <a class="hash" href="#the-table">#</a> <a class="toc-bak" href="#the-table-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-table">3.13.2, The table element</a>” in the
+            <h2>Section 3.13.2, The table element <a class="hash" href="#the-table">#</a> <a class="toc-bak" href="#the-table-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-table">Section 3.13.2, The table element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -1936,7 +2068,7 @@
             </ul>
           </div>
           <div id="the-colgroup" class="section">
-            <h2>3.13.4, The colgroup element <a class="hash" href="#the-colgroup">#</a> <a class="toc-bak" href="#the-colgroup-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-colgroup">3.13.4, The colgroup element</a>” in the
+            <h2>Section 3.13.4, The colgroup element <a class="hash" href="#the-colgroup">#</a> <a class="toc-bak" href="#the-colgroup-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-colgroup">Section 3.13.4, The colgroup element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -1964,7 +2096,7 @@
             </ul>
           </div>
           <div id="the-col" class="section">
-            <h2>3.13.5, The col element <a class="hash" href="#the-col">#</a> <a class="toc-bak" href="#the-col-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-col">3.13.5, The col element</a>” in the
+            <h2>Section 3.13.5, The col element <a class="hash" href="#the-col">#</a> <a class="toc-bak" href="#the-col-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-col">Section 3.13.5, The col element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -1992,7 +2124,7 @@
             </ul>
           </div>
           <div id="the-tbody" class="section">
-            <h2>3.13.6, The tbody element <a class="hash" href="#the-tbody">#</a> <a class="toc-bak" href="#the-tbody-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-tbody">3.13.6, The tbody element</a>” in the
+            <h2>Section 3.13.6, The tbody element <a class="hash" href="#the-tbody">#</a> <a class="toc-bak" href="#the-tbody-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-tbody">Section 3.13.6, The tbody element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -2003,7 +2135,7 @@
             </ul>
           </div>
           <div id="the-thead" class="section">
-            <h2>3.13.7, The thead element <a class="hash" href="#the-thead">#</a> <a class="toc-bak" href="#the-thead-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-thead">3.13.7, The thead element</a>” in the
+            <h2>Section 3.13.7, The thead element <a class="hash" href="#the-thead">#</a> <a class="toc-bak" href="#the-thead-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-thead">Section 3.13.7, The thead element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -2014,7 +2146,7 @@
             </ul>
           </div>
           <div id="the-tfoot" class="section">
-            <h2>3.13.8, The tfoot element <a class="hash" href="#the-tfoot">#</a> <a class="toc-bak" href="#the-tfoot-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-tfoot">3.13.8, The tfoot element</a>” in the
+            <h2>Section 3.13.8, The tfoot element <a class="hash" href="#the-tfoot">#</a> <a class="toc-bak" href="#the-tfoot-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-tfoot">Section 3.13.8, The tfoot element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -2025,7 +2157,7 @@
             </ul>
           </div>
           <div id="the-tr" class="section">
-            <h2>3.13.9, The tr element <a class="hash" href="#the-tr">#</a> <a class="toc-bak" href="#the-tr-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-tr">3.13.9, The tr element</a>” in the
+            <h2>Section 3.13.9, The tr element <a class="hash" href="#the-tr">#</a> <a class="toc-bak" href="#the-tr-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-tr">Section 3.13.9, The tr element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -2052,7 +2184,7 @@
             </ul>
           </div>
           <div id="the-td" class="section">
-            <h2>3.13.10, The td element <a class="hash" href="#the-td">#</a> <a class="toc-bak" href="#the-td-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-td">3.13.10, The td element</a>” in the
+            <h2>Section 3.13.10, The td element <a class="hash" href="#the-td">#</a> <a class="toc-bak" href="#the-td-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-td">Section 3.13.10, The td element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -2091,7 +2223,7 @@
             </ul>
           </div>
           <div id="the-th" class="section">
-            <h2>3.13.11, The th element <a class="hash" href="#the-th">#</a> <a class="toc-bak" href="#the-th-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-th">3.13.11, The th element</a>” in the
+            <h2>Section 3.13.11, The th element <a class="hash" href="#the-th">#</a> <a class="toc-bak" href="#the-th-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#the-th">Section 3.13.11, The th element</a>” in the
         specification</p>
             <p>In this section, the following changes were
             made:</p>
@@ -2105,8 +2237,8 @@
             </ul>
           </div>
           <div id="attributes0" class="section">
-            <h2>3.13.12 [new], Attributes common to td and th
-              elements <a class="hash" href="#attributes0">#</a> <a class="toc-bak" href="#attributes0-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#attributes0">3.13.12 [new], Attributes common to td and th
+            <h2>Section 3.13.12 [new], Attributes common to td and th
+              elements <a class="hash" href="#attributes0">#</a> <a class="toc-bak" href="#attributes0-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#attributes0">Section 3.13.12 [new], Attributes common to td and th
               elements</a>” in the
         specification</p>
             <p>This section is newly added. It provides</p>
@@ -2136,22 +2268,23 @@
             </ul>
           </div>
           <div id="processing" class="section">
-            <h2>3.13.13, Processing model <a class="hash" href="#processing">#</a> <a class="toc-bak" href="#processing-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#processing">3.13.13, Processing model</a>” in the
-        specification</p>
-            <p>Changes were made in the introduction to this
-            section to bring it in alignment with related change
-            made in other parts of the specification.</p>
-            <div id="tableforming" class="section">
-              <h2>3.13.13.1, Forming a table <a class="hash" href="#tableforming">#</a> <a class="toc-bak" href="#tableforming-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#tableforming">3.13.13.1, Forming a table</a>” in the
+            <h2>Section 3.13.13, Processing model <a class="hash" href="#processing">#</a> <a class="toc-bak" href="#processing-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#processing">Section 3.13.13, Processing model</a>” in the
         specification</p>
-              <p>A large number of substantial changes were made to
-              the algorithms in this section; among those changes
-              were the addition of steps related to the <code class="element">tfoot</code> and <code class="element">caption</code> elements, as well as a
+            <p>In this section, the following changes were
+            made:</p>
+            <ul>
+              <li>Changes were made in the introduction to this
+              section to bring it in alignment with related change
+              made in other parts of the specification.</li>
+              <li>A large number of substantive changes were made
+              to the algorithms in the “Forming a table”
+              subsection; among those changes were the addition of
+              steps related to the <code class="element">tfoot</code> and <code class="element">caption</code> elements, as well as a
               number of other changes, including a reformulation and
               refinement of a part of the previous text to form an
               <strong>algorithm for growing downward-growing
-                cells</strong>.</p>
-            </div>
+                cells</strong>.</li>
+            </ul>
           </div>
         </div>
         <div id="forms" class="section">
@@ -2687,13 +2820,15 @@
             subsections.</li>
             <li>In the “Database storage” subsection, the
             following editorial note was added:
-            <blockquote><q>Implementation feedback is requested on
+            <blockquote>
+              <p><q>Implementation feedback is requested on
                 what to do with arguments that are of types that
                 are not supported by the underlying SQL backend.
                 For example, SQLite doesn’t support booleans, so
                 what should the UA do if passed a boolean? The
                 Gears team suggests failing, not silently
-                converting types.</q></blockquote>
+                converting types.</q></p>
+            </blockquote>
             </li>
             <li>Also in the “Database storage” subsection, the
             interface definition for the
@@ -2843,18 +2978,22 @@
             for the user to mark text as having stress emphasis
             and as being important” was removed, and the following
             statements were added:
-            <blockquote><q>In response to a request from a user to
+            <blockquote>
+              <p><q>In response to a request from a user to
                 mark text up in italics, user agents should use
                 the <code class="element">i</code> element to
                 represent the semantic. The <code class="element">em</code> element should be used
                 only if the user agent is sure that the user means
-                to indicate stress emphasis.</q></blockquote>
-            <blockquote><q>In response to a request from a user to
+                to indicate stress emphasis.</q></p>
+            </blockquote>
+            <blockquote>
+              <p><q>In response to a request from a user to
                 mark text up in bold, user agents should use the
                 <code class="element">b</code> element to represent
                 the semantic. The <code class="element">strong</code> element should be
                 used only if the user agent is sure that the user
-                means to indicate importance.</q></blockquote>
+                means to indicate importance.</q></p>
+            </blockquote>
             </li>
             <li>In the “Making entire documents editable”
             subsection, refinements were made to the description
@@ -3072,7 +3211,8 @@
             certain tags can be omitted.</li>
             <li>Also in the “Elements” subsection, the following
             statement was <strong>removed</strong> completely:
-            <blockquote><q>A p element must not contain
+            <blockquote>
+              <p><q>A p element must not contain
                 blockquote, dl, menu, ol, pre, table, or ul
                 elements, even though these elements are
                 technically allowed inside p elements according to
@@ -3080,7 +3220,8 @@
                 specification. (In fact, if one of those elements
                 is put inside a p element in the markup, it will
                 instead imply a p element end tag before
-                it.)</q></blockquote>
+                it.)</q></p>
+            </blockquote>
             </li>
             <li>Also in the “Elements” subsection, the
             definition of <strong>escaping text span</strong> was
@@ -3347,13 +3488,14 @@
           DOM binding.</li>
         </ul>
       </div>
+      </div>
       <div id="acknowledgements" class="section">
         <h2>Acknowledgements <a class="hash" href="#acknowledgements">#</a> <a class="toc-bak" href="#acknowledgements-toc">T</a></h2><p class="spec-link">View “<a href="http://www.w3.org/TR/html5/#acknowledgements">Acknowledgements</a>” in the
         specification</p>
         <p>The following names were added to the list of names in
         the Acknowledgements:</p>
         <blockquote>
-          Adam Barth, Addison Phillips, Adele Peterson, Alastair
+          <p>Adam Barth, Addison Phillips, Adele Peterson, Alastair
           Campbell, Anders Carlsson, Anthony Ricaud, Arphen Lin,
           Ashley Sheridan, Aurelien Levy, Ben Millard, Brian
           Smith, Bruce Miller, Cameron McCormack, Daniel Glazman,
@@ -3369,7 +3511,8 @@
           Hoffmann, Oliver Hunt, Peter Karlsson, Philip TAYLOR,
           Ralf Stoltze, Raphael Champeimont, Rene Saarsoo, Richard
           Ishida, Steve Faulkner, Sunava Dutta, Terrence Wood, Tim
-          Johansson, Wayne Pollock, Yi-An Huang</blockquote>
+          Johansson, Wayne Pollock, Yi-An Huang</p>
+        </blockquote>
       </div>
     </div>
   

Index: style.css
===================================================================
RCS file: /sources/public/html5/pubnotes/style.css,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -d -r1.61 -r1.62
--- style.css	9 Jun 2008 16:21:08 -0000	1.61
+++ style.css	9 Jun 2008 18:59:51 -0000	1.62
@@ -29,12 +29,18 @@
   margin-bottom: 0px;
 }
 
-/* yipes ; guess what section this is */
 #toc > ul > li > ul > li > ul > li > ul > li {
   list-style-type: none;
   margin-top: 0px;
   margin-bottom: 0px;
 }
+
+/* yipes ; guess what section this is */
+#toc > ul > li > ul > li > ul > li > ul > li > ul > li {
+  list-style-type: none;
+  margin-top: 0px;
+  margin-bottom: 0px;
+}
 #toc ul {
   margin-bottom: 0.5em;
 }
@@ -260,20 +266,31 @@
 .htmlattribute {
   color: blueviolet;
 }
+#this_sections > div[class="section"] > h2 {
+  font-size: 25px;
+  font-weight: bold;
+}
 /* h2 at h3 level */
-div[class="section"] > div[class="section"] > h2 {
-  font-size: 19px;
+#this_sections > div[class="section"] > div[class="section"] > h2 {
+  font-size: 22px;
+  font-weight: bold;
 }
 /* h2 at h4 level */
-div[class="section"] > div[class="section"] > div[class="section"] > h2 {
-  font-size: 16px;
+#this_sections > div[class="section"] > div[class="section"] > div[class="section"] > h2 {
+  font-size: 19px;
   font-weight: bold;
 }
-/* h2 at h5 level */
-div[class="section"] > div[class="section"] > div[class="section"] > h2 > div[class="section"] > h2 {
+/* h2 at h6 level */
+#this_sections > div[class="section"] > div[class="section"] > div[class="section"] > div[class="section"] > h2 {
   font-size: 1em;
   font-weight: bold;
 }
+/* h2 at h7 level */
+#this_sections > div[class="section"] > div[class="section"] > div[class="section"] > div[class="section"] > div[class="section"] > h2 {
+  font-size: 1em;
+  font-weight: bold;
+  font-style: italic;
+}
 .highlight {
   background-color: yellow;
   padding: 2px;
@@ -285,3 +302,17 @@
 .spec-link {
   font-style: italic;
 }
+
+#tocjump {
+  font-style: italic;
+}
+
+h2 > a {
+  display: none;
+}
+
+h2:hover > a {
+  display: inline;
+  text-decoration: none;
+}
+

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.230
retrieving revision 1.231
diff -u -d -r1.230 -r1.231
--- Overview.src.html	9 Jun 2008 16:21:08 -0000	1.230
+++ Overview.src.html	9 Jun 2008 18:59:51 -0000	1.231
@@ -21,10 +21,10 @@
     </div>
     <header id=info>
       <h2>Document Metadata</h2>
-      <div id=maturity>ED</div>
+      <div id=maturity>WD</div>
       <div id=versions>
         <div id=source class=url>http://dev.w3.org/html5/pubnotes/Overview.src.html</div>
-        <div id=this class=url>http://www.w3.org/TR/2008/WD-html5-pubnotes-20080523/</div>
+        <div id=this class=url>http://www.w3.org/TR/2008/WD-html5-pubnotes-20080610/</div>
         <div id=latest class=url>http://www.w3.org/TR/html5-pubnotes/</div>
         <!-- * you can have multiple previous URLs -->
         <!-- * <div class="previous url">http://www.w3.org/TR/2008/WD-html5-pubnotes-20080501/</div> -->
@@ -47,7 +47,7 @@
         <div id=comments-archive class=url>http://lists.w3.org/Archives/Public/public-html-comments</div>
       </div>
     </header>
-    <div id=tocjump style="text-align: center">[<a href=#toc>skip to Table of Contents</a>]</div>
+    <div id=tocjump style="text-align: center"><a href=#toc>skip to Table of Contents</a></div>
     <section id=abstract>
       <h2>Abstract</h2>
       <p>This document provides supplemental information on the
@@ -63,11 +63,17 @@
       <h2>Table of Contents</h2>
     </section>
     <div id=this_sections>
-      <section id=this_introduction>
-        <h2>Introduction</h2>
-        <p>This document provides a per-section record of changes
-        to the HTML 5 draft specification since its publication as
-        a First Public Working Draft (FPWD). Note that it
+      <section id=summary>
+        <h2>Summary: Changes impacting Web architecture</h2>
+      </section>
+      <section id=fpwd>
+        <h2>Changes since the First Public Working Draft</h2>
+        <p>This section provides a per-section record of changes
+        to the HTML 5 draft specification after the <a
+          href="http://www.w3.org/TR/2008/WD-html5-20080122/" >22
+          January 2008 First Public Working Draft (FPWD)</a> and
+        until
+        the time of publication of this document. Note that it
         documents substantive changes only, and omits editorial
         changes. It is intended to be readable as a “standalone”
         document — meaning that readers are meant to be able to
@@ -75,7 +81,6 @@
         made, without necessarily needing to read the
         specification itself or to read through the entire diff
         document that shows all the changes.</p>
-      </section>
       <section id=introduction>
         <h2>Section 1, Introduction</h2>
         <p>The “Introduction” section of the specification
@@ -112,7 +117,8 @@
             <li>In the “Conformance checkers” subsection, the text
             of a statement was updated to now read (added text
             highlighted):
-            <blockquote><q><em class=highlight>Automated</em>
+            <blockquote>
+              <p><q><em class=highlight>Automated</em>
                 conformance checkers are exempt from detecting
                 errors that require interpretation of the author’s
                 intent (for example, while a document is
@@ -121,12 +127,14 @@
                 <em class=highlight>running without the input of
                   human judgement</em> do not have to check that
                 blockquote elements only contain quoted
-                material).</q></blockquote>
+                material).</q></p>
+            </blockquote>
             Also, the text of a related statement was updated to
             reference the concept of the <strong>browsing
               context</strong>; the text of that statement now
             reads:
-            <blockquote><q>Conformance checkers must check that
+            <blockquote>
+              <p><q>Conformance checkers must check that
                 the input document conforms when parsed without a
                 browsing context (meaning that no scripts are run,
                 and that the parser’s scripting flag is disabled),
@@ -135,7 +143,8 @@
                 which scripts execute, and that the scripts never
                 cause non-conforming states to occur other than
                 transiently during script execution
-                itself.</q></blockquote></li>
+                itself.</q></p>
+            </blockquote></li>
             <li>In the “Common conformance requirements for APIs
             exposed to JavaScript” subsection, for consistency
             with the Web IDL specification, statements related
@@ -482,24 +491,28 @@
             <li>The <code class=htmlattribute>onstorage</code> attribute
             was added to the list of global attributes.</li>
             <li>The following conformance statement was added:
-            <blockquote><q>custom data attributes (e.g.
+            <blockquote>
+              <p><q>custom data attributes (e.g.
                 data-foldername or data-msgid) can be specified on
                 any HTML element, to store custom data specific to
-                the page.</q></blockquote>
+                the page.</q></p>
+            </blockquote>
             Also, an “Embedding custom non-visible data” subsection
             was added, with conformance criteria related to
             <code class=htmlattribute>data-</code> attributes and
             the associated <code class=domattribute>dataset</code>
             DOM attribute.</li>
             <li>The following conformance statement was added:
-            <blockquote><q>In HTML documents, the html element,
+            <blockquote>
+              <p><q>In HTML documents, the html element,
                 and any other elements in the HTML namespace whose
                 parent element is not in the HTML namespace, may
                 have an <code class=htmlattribute>xmlns</code>
                 attribute specified, if, and only if, it has the
                 exact value
                 “<code>http://www.w3.org/1999/xhtml</code>”. This
-                does not apply to XML documents.</q></blockquote>
+                does not apply to XML documents.</q></p>
+            </blockquote>
             Also, two notes were added regarding the effects of
             the <code class=htmlattribute>xmlns</code> attribute in
             content.</li>
@@ -598,15 +611,19 @@
               <li>Other refinements were made
               to language in this section, including the addition
               of the following statements:
-              <blockquote><q>HTTP semantics must be followed when
+              <blockquote>
+                <p><q>HTTP semantics must be followed when
                   fetching external resources. (For example,
                   redirects must be followed and 404 responses must
                   cause the external resource to not be
-                  applied.)</q></blockquote>
-              <blockquote><q>If no type metadata is specified, but
+                  applied.)</q></p>
+              </blockquote>
+              <blockquote>
+                <p><q>If no type metadata is specified, but
                   the external resource link type has a default type
                   defined, then the user agent must assume that the
-                  resource is of that type.</q></blockquote>
+                  resource is of that type.</q></p>
+              </blockquote>
               </li>
             </ul>
           </section>
@@ -645,10 +662,12 @@
               list of pre-defined values for the 
               <code class=domattribute>name</code>
               attribute, and defined as:
-              <blockquote><q>The value must be a free-form string that
+              <blockquote>
+                <p><q>The value must be a free-form string that
                   describes the page. The value must be appropriate
                   for use in a directory of pages, e.g. in a search
-                  engine.</q></blockquote>
+                  engine.</q></p>
+              </blockquote>
               </li>
               <li>The value 
               <code>application-name</code>
@@ -656,7 +675,8 @@
               list of pre-defined values for the 
               <code class=domattribute>name</code>
               attribute, and defined as:
-              <blockquote><q>The value must be a short free-form
+              <blockquote>
+                <p><q>The value must be a short free-form
                   string that giving the name of the Web application
                   that the page represents. If the page is not a Web
                   application, the application-name metadata name must
@@ -665,7 +685,8 @@
                   the title might include status messages and the like
                   relevant to the status of the page at a particular
                   moment in time instead of just being the name of the
-                  application.</q></blockquote>
+                  application.</q></p>
+              </blockquote>
               </li>
               <li>The
               <code>Content-Type</code> keyword
@@ -709,14 +730,16 @@
             <h2>Section 3.8.3, The nav element</h2>
             <p>In this section, an example was added, along with
             the following statement:</p>
-            <blockquote><q>Not all groups of links on a page need
+            <blockquote>
+              <p><q>Not all groups of links on a page need
                 to be in a nav element — only sections that
                 consist of primary navigation blocks are
                 appropriate for the nav element. In particular, it
                 is common for footers to have a list of links to
                 various key parts of a site, but the footer
                 element is more appropriate in such
-                cases.</q></blockquote>
+                cases.</q></p>
+            </blockquote>
           </section>
           <section id=blockquoteold>
             <h2>Section 3.8.5 [now 3.9.6], The blockquote element</h2>
@@ -777,9 +800,11 @@
             down in the sectioning hierarchy to become a subsection
             the “Grouping content” section. Also, the following note
             was added:</p>
-            <blockquote><q> In the HTML serialisation, a leading
+            <blockquote>
+              <p><q> In the HTML serialisation, a leading
                 newline character immediately following the pre
-                element start tag is stripped.</q></blockquote>
+                element start tag is stripped.</q></p>
+            </blockquote>
           </section>
           <section id=the-blockquote>
             <h2>Section 3.9.6 [was 3.8.5], The blockquote element</h2>
@@ -864,15 +889,17 @@
             </ul>
           </section>
           <section id=the-dt>
-            <h2>3.9.11 [was 3.11.5], The dt element</h2>
+            <h2>Section 3.9.11 [was 3.11.5], The dt element</h2>
             <p>In this section, the following statement was
             added:</p>
-            <blockquote><q>If the dt element is the child of a
+            <blockquote>
+              <p><q>If the dt element is the child of a
                 dialog element, and it further contains a time
                 element, then that time element represents a
                 timestamp for when the associated discourse (dd
                 element) was said, and is not part of the name of
-                the talker.</q></blockquote>
+                the talker.</q></p>
+            </blockquote>
             <p>Also, two examples were added.</p>
           </section>
         </section>
@@ -894,9 +921,11 @@
             <p>In this section, some wording changes were made,
             four examples were added, and the following statement
             was added:</p>
-            <blockquote><q>Quotation punctuation (such as
+            <blockquote>
+              <p><q>Quotation punctuation (such as
                 quotation marks), if any, must be placed inside
-                the q element.</q></blockquote>
+                the q element.</q></p>
+            </blockquote>
           </section>
           <section id=the-cite>
             <h2>Section 3.10.3, The cite element</h2>
@@ -906,7 +935,8 @@
             simply, “The cite element represents a citation: the
             source, or reference, for a quote or statement made in
             the document”, was expanded to read:</p>
-            <blockquote><q>The cite element represents the title
+            <blockquote>
+              <p><q>The cite element represents the title
                 of a work (e.g. a book, a paper, an essay, a poem,
                 a score, a song, a script, a film, a TV show, a
                 game, a sculpture, a painting, a theatre
@@ -914,8 +944,10 @@
                 exhibition, etc). This can be a work that is being
                 quoted or referenced in detail (i.e. a citation),
                 or it can just be a work that is mentioned in
-                passing.</q></blockquote>
-            <blockquote><q>A person’s name is not the title of a
+                passing.</q></p>
+            </blockquote>
+            <blockquote>
+              <p><q>A person’s name is not the title of a
                 work — even if people call that person a piece of
                 work — and the element must therefore not be used
                 to mark up people’s names. (In some cases, the b
@@ -924,11 +956,14 @@
                 are keywords rendered with a different style to
                 draw attention to them. In other cases, if an
                 element is really needed, the span element can be
-                used.)</q></blockquote>
-            <blockquote><q>A ship is similarly not a work, and the
+                used.)</q></p>
+            </blockquote>
+            <blockquote>
+              <p><q>A ship is similarly not a work, and the
                 element must not be used to mark up ship names
                 (the i element can be used for that
-                purpose).</q></blockquote>
+                purpose).</q></p>
+            </blockquote>
           </section>
           <section id=the-mark>
             <h2>Section 3.10.7, The mark element [was: the m element]</h2>
@@ -939,7 +974,8 @@
             meaning of the element, which had read simply, “The m
             element represents a run of text marked or
             highlighted”, was expanded to read:</p>
-            <blockquote><q>The mark element represents a run of
+            <blockquote>
+              <p><q>The mark element represents a run of
                 text in one document marked or highlighted for
                 reference purposes, due to its relevance in
                 another context. When used in a quotation or other
@@ -954,7 +990,8 @@
                 of a document, it indicates a part of the document
                 that has been highlighted due to its likely
                 relevance to the user’s current
-                activity.</q></blockquote>
+                activity.</q></p>
+            </blockquote>
           </section>
           <section id=the-dfn>
             <h2>Section 3.10.8, The dfn element</h2>
@@ -1132,7 +1169,8 @@
               <li>A refinement was made to one of the
               examples.</li>
               <li>The following note was added:
-              <blockquote><q>Authors are encouraged to use the
+              <blockquote>
+                <p><q>Authors are encouraged to use the
                   class attribute on the i element to identify why
                   the element is being used, so that if the style
                   of a particular use (e.g. dream sequences as
@@ -1140,7 +1178,8 @@
                   a later date, the author doesn’t have to go
                   through the entire document (or series of
                   related documents) annotating each
-                  use.</q></blockquote>
+                  use.</q></p>
+              </blockquote>
               </li>
             </ul>
           </section>
@@ -1258,14 +1297,16 @@
                 be moved away from the main flow of the document
                 without affecting the document’s meaning.</em></li>
               <li>The following statement was added:
-              <blockquote><q>The element can thus be used to
+              <blockquote>
+                <p><q>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.</q></blockquote></li>
+                  appendix.</q></p>
+              </blockquote></li>
               <li>Several examples were added.</li>
             </ul>
           </section>
@@ -1279,33 +1320,41 @@
               obvious textual alternative” to simply, “A key part of
               the content”. The text of that same subsection was
               changed to now read:
-              <blockquote><q>In some cases, the image is a critical
+              <blockquote>
+                <p><q>In some cases, the image is a critical
                   part of the content. This could be the case, for
                   instance, on a page that is part of a photo
                   gallery. The image is the whole point of the page
-                  containing it.</q></blockquote>
+                  containing it.</q></p>
+              </blockquote>
 
-              <blockquote><q>When it is possible for alternative
+              <blockquote>
+                <p><q>When it is possible for alternative
                   text to be provided, for example if the image is
                   part of a series of screenshots in a magazine
                   review, or part of a comic strip, or is a
                   photograph in a blog entry about that photograph,
                   text that conveys can serve as a substitute for
                   the image must be given as the contents of the alt
-                  attribute.</q></blockquote>
+                  attribute.</q></p>
+              </blockquote>
 
-              <blockquote><q>In a rare subset of these cases, there
+              <blockquote>
+                <p><q>In a rare subset of these cases, there
                   might be no alternative text available. This could
                   be the case, for instance, on a photo upload site,
                   if the site has received 8000 photos from a user
                   without the user annotating any of them. In such
                   cases, the alt attribute may be omitted, but the
                   alt attribute should be included, with a useful
-                  value, if at all possible.</q></blockquote>
+                  value, if at all possible.</q></p>
+              </blockquote>
 
-              <blockquote><q>In any case, if an image is a key part
+              <blockquote>
+                <p><q>In any case, if an image is a key part
               of the content, the alt attribute must not be
-              specified with an empty value.</q></blockquote>
+              specified with an empty value.</q></p>
+              </blockquote>
               </li>
               <li>The <code class=htmlattribute>alt</code> text for the
               “Screenshot of a KDE desktop” example was expanded.</li>
@@ -1335,12 +1384,16 @@
                 executing.</q></li>
               <li>Some additional examples were added, prefaced by the
               following text:
-              <blockquote><q>A single image can have different
+              <blockquote>
+                <p><q>A single image can have different
                   appropriate alternative text depending on the
-                  context.</q></blockquote>
-              <blockquote><q> In each of the following cases, the same
+                  context.</q></p>
+              </blockquote>
+              <blockquote>
+                <p><q> In each of the following cases, the same
                   image is used, yet the alt text is different each
-                  time.</q></blockquote>
+                  time.</q></p>
+              </blockquote>
               </li>
             </ul>
           </section>
@@ -1453,13 +1506,15 @@
               and the case when the <strong>sandboxed plugins browsing
                 context flag</strong> is set.</li>
               <li>The following statement was added:
-                <blockquote><q>Whenever
+              <blockquote>
+                <p><q>Whenever
                 the name attribute is set, if the object element
                 has a nested browsing context, its name must be
                 changed to the new value. If the attribute is
                 removed, if the object element has a browsing
                 context, the browsing context name must be set to
-                the empty string.</q></blockquote></li>
+                the empty string.</q></p>
+              </blockquote></li>
               <li>Significant revisions and additions were made to
               the algorithm for checking what the object element
               represents, including a step for checking for the
@@ -1470,7 +1525,8 @@
                 class=htmlattribute>data</code> attribute is
               present.</li>
               <li>The following note was added:
-              <blockquote><q>The object
+              <blockquote>
+                <p><q>The object
                 element can, in certain cases as described above,
                 instantiate third-party handlers. This
                 specification does not define a mechanism for
@@ -1479,7 +1535,8 @@
                 opt to support a plugin mechanism such as the
                 Netscape Plugin API; others may use remote content
                 convertors or have built-in support for certain
-                types.</q></blockquote>
+                types.</q></p>
+              </blockquote>
               </li>
               <li>Two examples were added.</li>
             </ul>
@@ -1533,7 +1590,8 @@
               <code class=domattribute>pixelratio</code>
               DOM attribute were added, including the following
               statement:
-              <blockquote><q>The pixelratio attribute allows the
+              <blockquote>
+                <p><q>The pixelratio attribute allows the
                   author to specify the pixel ratio of anamorphic
                   media resources that do not self-describe their
                   pixel ratio. The attribute value, if specified,
@@ -1545,7 +1603,8 @@
                   the rendered width that gives the correct aspect
                   ratio). The default value, if the attribute is
                   omitted or cannot be parsed, is
-                  1.0.</q></blockquote></li>
+                  1.0.</q></p>
+              </blockquote></li>
             </ul>
           </section>
           <section id=media>
@@ -1619,17 +1678,21 @@
             made:</p>
             <ul>
               <li>The following statements were added:
-              <blockquote><q>Arguments other than the contextId
+              <blockquote>
+                <p><q>Arguments other than the contextId
                   must be ignored, and must not cause the user
                   agent to raise an exception (as would normally
                   occur if a method was called with the wrong
-                  number of arguments).</q></blockquote>
-              <blockquote><q>If the canvas has no pixels (i.e.
+                  number of arguments).</q></p>
+              </blockquote>
+              <blockquote>
+                <p><q>If the canvas has no pixels (i.e.
                   either its horizontal dimension or its vertical
                   dimension is zero) then the method must return
                   the string “data:,”. (This is the shortest data:
                   URI; it represents the empty string in a
-                  text/plain resource.)</q></blockquote>
+                  text/plain resource.)</q></p>
+              </blockquote>
               </li>
               <li>Some instances of the phrase “with scripting
               enabled” and “with scripting disabled” were changed
@@ -1640,7 +1703,8 @@
               <code class=method>toDataURL()</code> method with
               image types other than PNG was emended to read
               (added text highlighted):
-              <blockquote><q>When trying to use types other than
+              <blockquote>
+                <p><q>When trying to use types other than
                   image/png, authors can check if the image was
                   really returned in the requested format by
                   checking to see if the returned string starts
@@ -1650,7 +1714,8 @@
                   (The one exception to this is if the canvas has
                   either no height or no width, in which case the
                   result might simply be
-                  “data:,”.)</q></blockquote>
+                  “data:,”.)</q></p>
+              </blockquote>
               </li>
               <li>A statement regarding preventing information
               leakage from the
@@ -1695,29 +1760,37 @@
                 <li>A new “Security with canvas elements”
                 subsection was added. It begins with the following
                 statement:
-                <blockquote><q>Information leakage can occur if
+                <blockquote><p>
+                  <q>Information leakage can occur if
                     scripts from one origin are exposed to images
                     from another origin (one that isn’t the
-                    same).</q></blockquote>
-                <blockquote><q>To mitigate this, canvas elements
+                    same).</q></p>
+                </blockquote>
+                <blockquote>
+                  <p><q>To mitigate this, canvas elements
                     are defined to have a flag indicating whether
                     they are origin-clean. All canvas elements
                     must start with their origin-clean set to
-                    true.</q></blockquote>
+                    true.</q></p>
+                </blockquote>
                 It then lists a specific set actions, each of
                 which must cause the <var>origin-clean</var> flag
                 to be set to <code>false</code>. In addition, it
                 includes the following statements:
-                <blockquote><q>Whenever the toDataURL() method of
+                <blockquote>
+                  <p><q>Whenever the toDataURL() method of
                     a canvas element whose origin-clean flag is
                     set to false is called, the method must
                     immediately raise a security
-                    exception.</q></blockquote>
-                <blockquote><q>Whenever the getImageData() method
+                    exception.</q></p>
+                </blockquote>
+                <blockquote>
+                  <p><q>Whenever the getImageData() method
                     of the 2D context of a canvas element whose
                     origin-clean flag is set to false is called,
                     the method must immediately raise a security
-                    exception.</q></blockquote>
+                    exception.</q></p>
+                </blockquote>
                 </li>
               </ul>
             </section>
@@ -1754,48 +1827,60 @@
             <h2>Section 3.12.15 [new], MathML</h2>
             <p>This short section is newly added. It reads in
             whole:</p>
-            <blockquote><q>The math element from the MathML
+            <blockquote>
+              <p><q>The math element from the MathML
                 namespace falls into the embedded content category
                 for the purposes of the content models in this
-                specification.</q></blockquote>
+                specification.</q></p>
+            </blockquote>
 
-            <blockquote><q>User agents must handle text other than
+            <blockquote>
+              <p><q>User agents must handle text other than
                 inter-element whitespace found in MathML elements
                 whose content models do not allow raw text by
                 pretending for the purposes of MathML content
                 models, layout, and rendering that that text is
                 actually wrapped in an mtext element in the MathML
                 namespace. (Such text is not, however,
-                conforming.)</q></blockquote>
+                conforming.)</q></p>
+            </blockquote>
 
-            <blockquote><q>User agents must act as if any MathML element
+            <blockquote>
+              <p><q>User agents must act as if any MathML element
                 whose contents does not match the element’s
                 content model was replaced, for the purposes of
                 MathML layout and rendering, by an merror element
                 in the MathML namespace containing some appropiate
-                error message.</q></blockquote>
+                error message.</q></p>
+            </blockquote>
 
-            <blockquote><q>To enable authors to use MathML tools that only
+            <blockquote>
+              <p><q>To enable authors to use MathML tools that only
                 accept MathML in its XML form, interactive HTML
                 user agents are encouraged to provide a way to
                 export any MathML fragment as a
                 namespace-well-formed XML
-                fragment.</q></blockquote>
+                fragment.</q></p>
+            </blockquote>
           </section>
           <section id=svg>
             <h2>Section 3.12.16 [new], SVG</h2>
             <p>This short section is newly added. It reads in
             whole:</p>
-            <blockquote><q>The svg element from the SVG namespace
+            <blockquote>
+              <p><q>The svg element from the SVG namespace
                 falls into the embedded content category for the
                 purposes of the content models in this
-                specification.</q></blockquote>
+                specification.</q></p>
+            </blockquote>
 
-            <blockquote><q>To enable authors to use SVG tools that only
+            <blockquote>
+              <p><q>To enable authors to use SVG tools that only
                 accept SVG in its XML form, interactive HTML user
                 agents are encouraged to provide a way to export
                 any SVG fragment as a namespace-well-formed XML
-                fragment.</q></blockquote>
+                fragment.</q></p>
+            </blockquote>
           </section>
         </section>
         <section id=tabular>
@@ -1804,7 +1889,7 @@
           <code class=element>table</code>
           element and its descendant-element hierarchy.</p>
           <section id=the-table>
-            <h2>3.13.2, The table element</h2>
+            <h2>Section 3.13.2, The table element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -1856,7 +1941,7 @@
             </ul>
           </section>
           <section id=the-colgroup>
-            <h2>3.13.4, The colgroup element</h2>
+            <h2>Section 3.13.4, The colgroup element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -1883,7 +1968,7 @@
             </ul>
           </section>
           <section id=the-col>
-            <h2>3.13.5, The col element</h2>
+            <h2>Section 3.13.5, The col element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -1910,7 +1995,7 @@
             </ul>
           </section>
           <section id=the-tbody>
-            <h2>3.13.6, The tbody element</h2>
+            <h2>Section 3.13.6, The tbody element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -1920,7 +2005,7 @@
             </ul>
           </section>
           <section id=the-thead>
-            <h2>3.13.7, The thead element</h2>
+            <h2>Section 3.13.7, The thead element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -1930,7 +2015,7 @@
             </ul>
           </section>
           <section id=the-tfoot>
-            <h2>3.13.8, The tfoot element</h2>
+            <h2>Section 3.13.8, The tfoot element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -1940,7 +2025,7 @@
             </ul>
           </section>
           <section id=the-tr>
-            <h2>3.13.9, The tr element</h2>
+            <h2>Section 3.13.9, The tr element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -1966,7 +2051,7 @@
             </ul>
           </section>
           <section id=the-td>
-            <h2>3.13.10, The td element</h2>
+            <h2>Section 3.13.10, The td element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -2004,7 +2089,7 @@
             </ul>
           </section>
           <section id=the-th>
-            <h2>3.13.11, The th element</h2>
+            <h2>Section 3.13.11, The th element</h2>
             <p>In this section, the following changes were
             made:</p>
             <ul>
@@ -2017,7 +2102,7 @@
             </ul>
           </section>
           <section id=attributes0>
-            <h2>3.13.12 [new], Attributes common to td and th
+            <h2>Section 3.13.12 [new], Attributes common to td and th
               elements</h2>
             <p>This section is newly added. It provides</p>
             <ul>
@@ -2046,22 +2131,24 @@
             </ul>
           </section>
           <section id=processing>
-            <h2>3.13.13, Processing model</h2>
-            <p>Changes were made in the introduction to this
-            section to bring it in alignment with related change
-            made in other parts of the specification.</p>
-            <section id=tableforming>
-              <h2>3.13.13.1, Forming a table</h2>
-              <p>A large number of substantial changes were made to
-              the algorithms in this section; among those changes
-              were the addition of steps related to the <code
+            <h2>Section 3.13.13, Processing model</h2>
+            <p>In this section, the following changes were
+            made:</p>
+            <ul>
+              <li>Changes were made in the introduction to this
+              section to bring it in alignment with related change
+              made in other parts of the specification.</li>
+              <li>A large number of substantive changes were made
+              to the algorithms in the “Forming a table”
+              subsection; among those changes were the addition of
+              steps related to the <code
                 class=element>tfoot</code> and <code
                 class=element>caption</code> elements, as well as a
               number of other changes, including a reformulation and
               refinement of a part of the previous text to form an
               <strong>algorithm for growing downward-growing
-                cells</strong>.</p>
-            </section>
+                cells</strong>.</li>
+            </ul>
           </section>
         </section>
         <section id=forms>
@@ -2593,13 +2680,15 @@
             subsections.</li>
             <li>In the “Database storage” subsection, the
             following editorial note was added:
-            <blockquote><q>Implementation feedback is requested on
+            <blockquote>
+              <p><q>Implementation feedback is requested on
                 what to do with arguments that are of types that
                 are not supported by the underlying SQL backend.
                 For example, SQLite doesn’t support booleans, so
                 what should the UA do if passed a boolean? The
                 Gears team suggests failing, not silently
-                converting types.</q></blockquote>
+                converting types.</q></p>
+            </blockquote>
             </li>
             <li>Also in the “Database storage” subsection, the
             interface definition for the
@@ -2748,20 +2837,24 @@
             for the user to mark text as having stress emphasis
             and as being important” was removed, and the following
             statements were added:
-            <blockquote><q>In response to a request from a user to
+            <blockquote>
+              <p><q>In response to a request from a user to
                 mark text up in italics, user agents should use
                 the <code class=element>i</code> element to
                 represent the semantic. The <code
                   class=element>em</code> element should be used
                 only if the user agent is sure that the user means
-                to indicate stress emphasis.</q></blockquote>
-            <blockquote><q>In response to a request from a user to
+                to indicate stress emphasis.</q></p>
+            </blockquote>
+            <blockquote>
+              <p><q>In response to a request from a user to
                 mark text up in bold, user agents should use the
                 <code class=element>b</code> element to represent
                 the semantic. The <code
                   class=element>strong</code> element should be
                 used only if the user agent is sure that the user
-                means to indicate importance.</q></blockquote>
+                means to indicate importance.</q></p>
+            </blockquote>
             </li>
             <li>In the “Making entire documents editable”
             subsection, refinements were made to the description
@@ -2976,7 +3069,8 @@
             certain tags can be omitted.</li>
             <li>Also in the “Elements” subsection, the following
             statement was <strong>removed</strong> completely:
-            <blockquote><q>A p element must not contain
+            <blockquote>
+              <p><q>A p element must not contain
                 blockquote, dl, menu, ol, pre, table, or ul
                 elements, even though these elements are
                 technically allowed inside p elements according to
@@ -2984,7 +3078,8 @@
                 specification. (In fact, if one of those elements
                 is put inside a p element in the markup, it will
                 instead imply a p element end tag before
-                it.)</q></blockquote>
+                it.)</q></p>
+            </blockquote>
             </li>
             <li>Also in the “Elements” subsection, the
             definition of <strong>escaping text span</strong> was
@@ -3244,12 +3339,13 @@
           DOM binding.</li>
         </ul>
       </section>
+      </section>
       <section id=acknowledgements>
         <h2>Acknowledgements</h2>
         <p>The following names were added to the list of names in
         the Acknowledgements:</p>
         <blockquote>
-          Adam Barth, Addison Phillips, Adele Peterson, Alastair
+          <p>Adam Barth, Addison Phillips, Adele Peterson, Alastair
           Campbell, Anders Carlsson, Anthony Ricaud, Arphen Lin,
           Ashley Sheridan, Aurelien Levy, Ben Millard, Brian
           Smith, Bruce Miller, Cameron McCormack, Daniel Glazman,
@@ -3265,7 +3361,8 @@
           Hoffmann, Oliver Hunt, Peter Karlsson, Philip TAYLOR,
           Ralf Stoltze, Raphael Champeimont, Rene Saarsoo, Richard
           Ishida, Steve Faulkner, Sunava Dutta, Terrence Wood, Tim
-          Johansson, Wayne Pollock, Yi-An Huang</blockquote>
+          Johansson, Wayne Pollock, Yi-An Huang</p>
+        </blockquote>
       </section>
     </div>
   </body>
Received on Monday, 9 June 2008 19:00:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:57 GMT