HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
51019835Remove a paragraph from the W3C version by request of the chairs. Add a list of differences between the versions of the spec to the WHATWG version now that there's more than a few. Add a paragraph to the W3C version mentioning this. Make it easier to keep track of what is in what version of the spec when editing.2010-06-05 05:55
@@ -10,21 +10,21 @@
  !    - element, attribute, content model, and interface indexes
  !    - section for the element itself
  !
  !-->
 <!--START validation-->
 <!--START complete--><!--START epub-->
 <!--START html--><!--START w3c-html-->
 
   <h2 id="introduction">Introduction</h2>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--VERSION-->
 
   <h3>Is this HTML5?</h3>
 
   <p><i>This section is non-normative.</i></p>
 
 <!--END complete--><!--END epub-->
 
   <p>In short: Yes.</p>
 
   <p>In more length: "HTML5" has at various times been used to refer
@@ -35,80 +35,105 @@
   <p>This specification actually now defines the next generation of
   HTML after HTML5. HTML5 reached Last Call at the WHATWG in October
   2009, and shortly after we started working on some experimental new
   features that are not as stable as the rest of the
   specification. The stability of sections is annotated in the
   margin.</p>
 
   <p>The W3C has also been working on HTML in conjunction with the
   WHATWG; at the W3C, this document has been split into several parts,
   and the occasional informative paragraph or example has been removed
-  for technical reasons. For all intents and purposes, however, the
-  W3C HTML specifications and this specification are equivalent (and
-  they are in fact all generated from the same source document).</p>
+  for technical or editorial reasons. For all intents and purposes,
+  however, the W3C HTML specifications and this specification are
+  equivalent (and they are in fact all generated from the same source
+  document). The minor differences are:</p>
+
+  <ul class="brief">
+
+   <li>Instead of this section, the W3C version has a different
+   paragraph explaining the difference between the W3C and WHATWG
+   versions of HTML.</li>
+
+   <li>The W3C version refers to the technology as HTML5, rather than
+   just HTML.</li>
+
+   <li>Examples that use features from HTML5 are not present in the
+   W3C version since the W3C version is published as HTML4 due to W3C
+   publication policies.</li>
+
+   <li>The W3C version includes a redundant and inconsistent reference
+   to the WCAG document.</li>
+
+   <li>The W3C version omits a paragraph of implementation advice for
+   political reasons.</li>
+
+  </ul>
 
   <p>Features that are considered part of the next generation of HTML
-  beyond HTML5 currently consist of only:</p>
+  beyond HTML5 (and that are therefore not included in the W3C version
+  of HTML5) currently consist of:</p>
 
   <ul class="brief">
    <li>The <code>device</code> element.</li>
    <li>The <code title="attr-hyperlink-ping">ping</code> attribute and related <span>hyperlink auditing</span> features.</li>
+   <li>The <span>timed track</span> model for <span title="media element">media elements</span>, the <span>WebSRT</span> format, and related features.</li>
   </ul>
 
-  <p>Features that are part of HTML5 (and this specification) but that
-  are either currently, or have been in the past, published as
-  separate specifications:</p>
+  <p>Features that are part of HTML (and this specification) but that
+  are currently published as separate specifications as well, and are
+  not included in the W3C HTML5 specification, consist of:</p>
 
   <ul class="brief">
    <li><a href="#2dcontext">Canvas 2D Graphics Context</a>
    <li><a href="#microdata">Microdata</a>
    <li><a href="#mdvocabs">Microdata vocabularies</a>
    <li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)
    <li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)
-   <li><a href="#forms">Forms</a> (previously known as Web Forms 2)
   </ul>
 
+  <p>The <a href="#forms">forms</a> part of this specification was
+  previously published separately in a specification known as Web
+  Forms 2.</p>
+
   <p>Features that are not currently in this document that were in the
   past considered part of HTML5, or that were never part of HTML5 but
   have been referred to as part of HTML5 in the media, include:</p>
 
   <ul class="brief">
    <li><a href="http://www.whatwg.org/specs/web-workers/current-work/">Web Workers</a>
    <li><a href="http://dev.w3.org/html5/webstorage/">Web Storage</a>
    <li><a href="http://dev.w3.org/html5/websockets/">WebSocket API</a>
    <li><a href="http://www.whatwg.org/specs/web-socket-protocol/">WebSocket protocol</a>
 <!--
    <li><a href="http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol">WebSocket protocol</a>
 -->
    <li><a href="http://dev.w3.org/html5/eventsource/">Server-sent Events</a>
    <li><a href="http://dev.w3.org/html5/webdatabase/">Web SQL Database</a>
    <li><a href="http://dev.w3.org/geo/api/spec-source.html">Geolocation API</a>
    <li><a href="http://www.w3.org/TR/SVG/">SVG</a>
    <li><a href="http://www.w3.org/TR/MathML/">MathML</a>
    <li><a href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/">XMLHttpRequest</a>
   </ul>
 
-
-<!--START complete--><!--START epub-->
 <!--END html-->
+<!--START complete--><!--START epub-->
 
   <p>No, although it does contain everything that is part of HTML5. If
   you want only HTML5, please see <a
   href="http://www.whatwg.org/html">the HTML specification</a>.</p>
 
   <p><em>This</em> specification contains everything that the WHATWG
   is actively working on. For more details, please see the <a
   href="http://wiki.whatwg.org/wiki/FAQ#What_are_the_various_versions_of_the_spec.3F">the
   relevant FAQ entry</a>.</p>
 
-<!--START html-->
-<!--START w3c-html-->
+<!--START html--><!--START w3c-html--><!--VERSION-->
 
 
   <h3>Background</h3>
 
   <p><i>This section is non-normative.</i></p>
 
   <p>The World Wide Web's markup language has always been HTML. HTML
   was primarily designed as a language for semantically describing
   scientific documents, although its general design and adaptations
   over the years have enabled it to be used to describe a number of
@@ -256,20 +281,33 @@
 
   <p>In 2006, the W3C indicated an interest to participate in the
   development of HTML5 after all, and in 2007 formed a working group
   chartered to work with the WHATWG on the development of the HTML5
   specification. Apple, Mozilla, and Opera allowed the W3C to publish
   the specification under the W3C copyright, while keeping a version
   with the less restrictive license on the WHATWG site.</p>
 
   <p>Since then, both groups have been working together.</p>
 
+<!--END complete--><!--END epub--><!--END html--><!--w3c-html--><!--VERSION-->
+
+  <p>The specification published by the WHATWG is not identical to
+  this specification. The main differences are that the WHATWG version
+  includes features not included in this W3C version: some features
+  have been omitted as they are considered part of future revisions of
+  HTML, not HTML5; and other features are omitted because at the W3C
+  they are published as separate specifications. There are also some
+  minor differences. For an exact list of differences, please see the
+  WHATWG specification.</p>
+
+<!--START complete--><!--START epub--><!--START html--><!--w3c-html--><!--VERSION-->
+
   <p>A separate document has been published by the W3C HTML working
   group to document the differences between this specification and the
   language described in the HTML4 specification. <a
   href="#refsHTMLDIFF">[HTMLDIFF]</a></p>
 
 
 
 
   <h3>Design notes</h3>
 
@@ -345,43 +383,43 @@
 
   <p>The first such concrete syntax is the HTML syntax. This is the
   format suggested for most authors. It is compatible with most legacy
   Web browsers. If a document is transmitted with an <span>HTML MIME
   type</span>, such as <code>text/html</code>, then it will be
   processed as an HTML document by Web browsers.
 
   <!--END html--><!--END complete--><!--END epub-->
   This specification defines version 5 of the HTML syntax, known as
   "HTML5".
-  <!--START html--><!--START complete--><!--START epub--><!--END w3c-html-->
+  <!--START html--><!--START complete--><!--START epub--><!--END w3c-html--><!--VERSION-->
   This specification defines the latest HTML syntax, known simply as
   "HTML".
-  <!--START w3c-html-->
+  <!--START w3c-html--><!--VERSION-->
 
   </p>
 
   <p>The second concrete syntax is the XHTML syntax, which is an
   application of XML. When a document is transmitted with an <span>XML
   MIME type</span>, such as <code>application/xhtml+xml</code>, then
   it is treated as an XML document by Web browsers, to be parsed by an
   XML processor. Authors are reminded that the processing for XML and
   HTML differs; in particular, even minor syntax errors will prevent a
   document labeled as XML from being rendered fully, whereas they
   would be ignored in the HTML syntax.
 
   <!--END html--><!--END complete--><!--END epub-->
   This specification defines version 5 of the XHTML syntax, known as
   "XHTML5".
-  <!--START html--><!--START complete--><!--START epub--><!--END w3c-html-->
+  <!--START html--><!--START complete--><!--START epub--><!--END w3c-html--><!--VERSION-->
   This specification defines the latest XHTML syntax, known simply as
   "XHTML".
-  <!--START w3c-html-->
+  <!--START w3c-html--><!--VERSION-->
 
   </p>
 
   <p>The DOM, the HTML syntax, and XML cannot all represent the same
   content. For example, namespaces cannot be represented using the
   HTML syntax, but they are supported in the DOM and in XML.
   Similarly, documents that use the <code>noscript</code> feature can
   be represented using the HTML syntax, but cannot be represented with
   the DOM or in XML. Comments that contain the string "<code
   title="">--&gt;</code>" can be represented in the DOM but not in the
@@ -412,35 +450,35 @@
    concepts used in defining elements.</dd>
 
 
    <dt><a href="#semantics">The elements of HTML</a></dt>
 
    <dd>Each element has a predefined meaning, which is explained in
    this section. Rules for authors on how to use the element<span
    class="impl">, along with user agent requirements for how to handle
    each element,</span> are also given.</dd>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <dt><a href="#microdata">Microdata</a></dt>
 
    <dd>This specification introduces a mechanism for adding
    machine-readable annotations to documents, so that tools can
    extract trees of name/value pairs from the document. This section
    describes this mechanism<span class="impl"> and some algorithms
    that can be used to convert HTML documents into other
    formats</span>.
 
    This section also defines some Microdata vocabularies for contact
    information, calendar events, and licensing works.
 
    </dd>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
 
    <dt><a href="#browsers">Loading Web pages</a></dt>
 
    <dd>HTML documents do not exist in a vacuum &mdash; this section
    defines many of the features that affect environments that deal
    with multiple pages.</dd>
 
    <dt><a href="#webappapis">Web application APIs</a></dt>
 
    <dd>This section introduces basic features for scripting of
@@ -459,32 +497,32 @@
    JavaScript.</dd>
 <!--START html--><!--START w3c-html-->
 
 <!--END html--><!--END w3c-html-->
    <dt><a href="#webstorage">Web storage</a></dt>
 
    <dd>This specification defines a client-side storage mechanism
    based on name-value pairs.</dd>
 <!--START html--><!--START w3c-html-->
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--POSTMSG-->
    <dt><a href="#comms">The communication APIs</a></dt>
 
    <dd>This section describes some mechanisms that applications
    written in HTML can use to communicate with other applications from
    different domains running on the same client.
 <!--END html-->
    It also introduces a server-push event stream mechanism, and a
    two-way full-duplex socket protocol for scripts.
 <!--START html-->
    </dd>
-<!--START w3c-html-->
+<!--START w3c-html--><!--POSTMSG-->
 
 
    <dt><a href="#syntax">The HTML syntax</a></dt>
    <dt><a href="#xhtml">The XHTML syntax</a></dt>
 
    <dd>All of these features would be for naught if they couldn't be
    represented in a serialized form and sent to other people, and so
    these sections define the syntaxes of HTML, along with rules for
    how to parse content using those syntaxes.</dd>
 
@@ -1849,25 +1887,25 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
     context</span> in which scripts execute, and that the scripts
     never cause non-conforming states to occur other than transiently
     during script execution itself. (This is only a "SHOULD" and not a
     "MUST" requirement because it has been proven to be impossible. <a
     href="#refsCOMPUTABLE">[COMPUTABLE]</a>)</p>
 
     <!--END html--><!--END complete--><!--END epub-->
     <p>The term "HTML5 validator" can be used to refer to a
     conformance checker that itself conforms to the applicable
     requirements of this specification.</p>
-    <!--START html--><!--START complete--><!--START epub--><!--END w3c-html-->
+    <!--START html--><!--START complete--><!--START epub--><!--END w3c-html--><!--VERSION-->
     <p>The term "HTML validator" can be used to refer to a
     conformance checker that itself conforms to the applicable
     requirements of this specification.</p>
-    <!--START w3c-html-->
+    <!--START w3c-html--><!--VERSION-->
 
     <div class="note">
 
      <p>XML DTDs cannot express all the conformance requirements of
      this specification. Therefore, a validating XML processor and a
      DTD cannot constitute a conformance checker. Also, since neither
      of the two authoring formats defined in this specification are
      applications of SGML, a validating SGML system cannot constitute
      a conformance checker either.</p>
 
@@ -4808,27 +4846,27 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    number.</p></li>
 
    <li><p>Return <var title="">result</var>.</p>
 
   </ol>
 
   </div>
 
   <hr>
 
-  <!--END w3c-html-->
+  <!--END w3c-html--><!--2DCANVAS-->
 
   <p class="note">The <span title="canvas-context-2d">2D graphics
   context</span> has a separate color syntax that also handles
   opacity.</p>
 
-  <!--START w3c-html-->
+  <!--START w3c-html--><!--2DCANVAS-->
 
 
   <h4>Space-separated tokens</h4>
 
   <p>A <dfn>set of space-separated tokens</dfn> is a string containing
   zero or more words separated by one or more <span title="space
   character">space characters</span>, where words consist of any
   string of one or more characters, none of which are <span
   title="space character">space characters</span>.</p>
 
@@ -6839,21 +6877,21 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E..
 
    <li><p>Remove <var title="">element</var> from its parent
    node.</p></li>
 
   </ol>
 
   <!-- see also http://ln.hixie.ch/?start=1161042744&count=1 -->
 
   </div>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
   <div data-component="HTML Microdata (editor: Ian Hickson)">
 <!--START microdata-->
 <!--FIXUP microdata -1-->
   <h5>HTMLPropertiesCollection</h5>
 <!--FIXUP microdata +1-->
 
   <p>The <code>HTMLPropertiesCollection</code> interface represents a
   <span title="collections">collection</span> of elements that add
   name-value pairs to a particular <span
   title="concept-item">item</span> in the <span>microdata</span>
@@ -6947,21 +6985,21 @@ interface <dfn>PropertyNodeList</dfn> : <span>NodeList</span> {
   title="dom-PropertyNodeList-values"><code>values</code></dfn>
   IDL attribute on the <code>PropertyNodeList</code> object, on
   getting, must return a newly constructed array whose values are the
   values obtained from the <code
   title="dom-itemValue">itemValue</code> DOM property of each of the
   elements represented by the object, in <span>tree order</span>.</p>
 
   </div>
 <!--END microdata-->
   </div><!--data-component-->
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
 
 
   <h4>DOMTokenList</h4>
 
   <p>The <code>DOMTokenList</code> interface represents an interface
   to an underlying string that consists of a <span>set of
   space-separated tokens</span>.</p>
 
   <p class="note"><code>DOMTokenList</code> objects are always
   <span>case-sensitive</span>, even when the underlying string might
@@ -7635,21 +7673,21 @@ interface <dfn>HTMLDocument</dfn> {
            attribute <span>HTMLElement</span> <span title="dom-document-body">body</span>;
   readonly attribute <span>HTMLHeadElement</span> <span title="dom-document-head">head</span>;
   readonly attribute <span>HTMLCollection</span> <span title="dom-document-images">images</span>;
   readonly attribute <span>HTMLCollection</span> <span title="dom-document-embeds">embeds</span>;
   readonly attribute <span>HTMLCollection</span> <span title="dom-document-plugins">plugins</span>;
   readonly attribute <span>HTMLCollection</span> <span title="dom-document-links">links</span>;
   readonly attribute <span>HTMLCollection</span> <span title="dom-document-forms">forms</span>;
   readonly attribute <span>HTMLCollection</span> <span title="dom-document-scripts">scripts</span>;
   NodeList <span title="dom-document-getElementsByName">getElementsByName</span>(in DOMString elementName);
   NodeList <span title="dom-document-getElementsByClassName">getElementsByClassName</span>(in DOMString classNames);
-<!--END w3c-html-->  NodeList <span title="dom-document-getItems">getItems</span>(in optional DOMString typeNames); // <span>microdata</span> <!--WARNING: ALSO DUPLICATED IN MICRODATA SECTION--><!--START w3c-html-->
+<!--END w3c-html--><!--MD-->  NodeList <span title="dom-document-getItems">getItems</span>(in optional DOMString typeNames); // <span>microdata</span> <!--WARNING: ALSO DUPLICATED IN MICRODATA SECTION--><!--START w3c-html--><!--MD-->
 
   // <span>dynamic markup insertion</span>
            attribute DOMString <span title="dom-innerHTML">innerHTML</span>;
   <span>HTMLDocument</span> <span title="dom-document-open">open</span>(in optional DOMString type, in optional DOMString replace);
   <span>WindowProxy</span> <span title="dom-document-open">open</span>(in DOMString url, in DOMString name, in DOMString features, in optional boolean replace);
   void <span title="dom-document-close">close</span>();
   void <span title="dom-document-write">write</span>(in DOMString... text);
   void <span title="dom-document-writeln">writeln</span>(in DOMString... text);
 
   // <span>user interaction</span>
@@ -8769,29 +8807,29 @@ interface <dfn>DOMHTMLImplementation</dfn> {
 
   // <span>metadata attributes</span>
            attribute DOMString <span title="dom-id">id</span>;
            attribute DOMString <span title="dom-title">title</span>;
            attribute DOMString <span title="dom-lang">lang</span>;
            attribute DOMString <span title="dom-dir">dir</span>;
            attribute <span>DOMString</span> <span title="dom-className">className</span>;
   readonly attribute <span>DOMTokenList</span> <span title="dom-classList">classList</span>;
   readonly attribute <span>DOMStringMap</span> <span title="dom-dataset">dataset</span>;
 
-<!--END w3c-html-->  // <span>microdata</span> <!--WARNING: ALSO DUPLICATED IN MICRODATA SECTION-->
+<!--END w3c-html--><!--MD-->  // <span>microdata</span> <!--WARNING: ALSO DUPLICATED IN MICRODATA SECTION-->
            attribute boolean <span title="dom-itemScope">itemScope</span>;
            attribute DOMString <span title="dom-itemType">itemType</span>;
            attribute DOMString <span title="dom-itemId">itemId</span>;
   [PutForwards=<span title="dom-DOMSettableTokenList-value">value</span>] readonly attribute <span>DOMSettableTokenList</span> <span title="dom-itemRef">itemRef</span>;
   [PutForwards=<span title="dom-DOMSettableTokenList-value">value</span>] readonly attribute <span>DOMSettableTokenList</span> <span title="dom-itemProp">itemProp</span>;
   readonly attribute <span>HTMLPropertiesCollection</span> <span title="dom-properties">properties</span>;
            attribute any <span title="dom-itemValue">itemValue</span>;
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
   // <span>user interaction</span>
            attribute boolean <span title="dom-hidden">hidden</span>;
   void <span title="dom-click">click</span>();
   void <span title="dom-scrollIntoView">scrollIntoView</span>();
   void <span title="dom-scrollIntoView">scrollIntoView</span>(in boolean top);
            attribute long <span title="dom-tabindex">tabIndex</span>;
   void <span title="dom-focus">focus</span>();
   void <span title="dom-blur">blur</span>();
            attribute DOMString <span title="dom-accessKey">accessKey</span>;
   readonly attribute DOMString <span title="dom-accessKeyLabel">accessKeyLabel</span>;
@@ -8894,27 +8932,27 @@ interface <dfn>HTMLUnknownElement</dfn> : <span>HTMLElement</span> { };</pre>
 
   <ul class="brief">
    <li><code title="attr-accesskey">accesskey</code></li>
    <li><code title="attr-class">class</code></li>
    <li><code title="attr-contenteditable">contenteditable</code></li>
    <li><code title="attr-contextmenu">contextmenu</code></li>
    <li><code title="attr-dir">dir</code></li>
    <li><code title="attr-draggable">draggable</code></li>
    <li><code title="attr-hidden">hidden</code></li>
    <li><code title="attr-id">id</code></li>
-<!--END w3c-html--><!--WARNING: ALSO DUPLICATED IN MICRODATA SECTION -->
+<!--END w3c-html--><!--MD--><!--WARNING: ALSO DUPLICATED IN MICRODATA SECTION -->
    <li><code title="attr-itemid">itemid</code></li>
    <li><code title="attr-itemprop">itemprop</code></li>
    <li><code title="attr-itemref">itemref</code></li>
    <li><code title="attr-itemscope">itemscope</code></li>
    <li><code title="attr-itemtype">itemtype</code></li>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <li><code title="attr-lang">lang</code></li>
    <li><code title="attr-spellcheck">spellcheck</code></li>
    <li><code title="attr-style">style</code></li>
    <li><code title="attr-tabindex">tabindex</code></li>
    <li><code title="attr-title">title</code></li>
   </ul>
 
   <hr>
 
   <p>The following <span>event handler content attributes</span> may
@@ -9941,30 +9979,30 @@ background: transparent">blue&lt;/span>.&lt;/p></pre>
    <li><code>hgroup</code></li>
    <li><code>hr</code></li>
    <li><code>i</code></li>
    <li><code>iframe</code></li>
    <li><code>img</code></li>
    <li><code>input</code></li>
    <li><code>ins</code></li>
    <li><code>kbd</code></li>
    <li><code>keygen</code></li>
    <li><code>label</code></li>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <li><code>link</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present)</li>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <li><code>map</code></li>
    <li><code>mark</code></li>
    <li><code>math</code></li>
    <li><code>menu</code></li>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <li><code>meta</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present)</li>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <li><code>meter</code></li>
    <li><code>nav</code></li>
    <li><code>noscript</code></li>
    <li><code>object</code></li>
    <li><code>ol</code></li>
    <li><code>output</code></li>
    <li><code>p</code></li>
    <li><code>pre</code></li>
    <li><code>progress</code></li>
    <li><code>q</code></li>
@@ -10075,29 +10113,29 @@ background: transparent">blue&lt;/span>.&lt;/p></pre>
    <li><code>em</code></li>
    <li><code>embed</code></li>
    <li><code>i</code></li>
    <li><code>iframe</code></li>
    <li><code>img</code></li>
    <li><code>input</code></li>
    <li><code>ins</code> (if it contains only <span>phrasing content</span>)</li>
    <li><code>kbd</code></li>
    <li><code>keygen</code></li>
    <li><code>label</code></li>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <li><code>link</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present)</li>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <li><code>map</code> (if it contains only <span>phrasing content</span>)</li>
    <li><code>mark</code></li>
    <li><code>math</code></li>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <li><code>meta</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present)</li>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <li><code>meter</code></li>
    <li><code>noscript</code></li>
    <li><code>object</code></li>
    <li><code>output</code></li>
    <li><code>progress</code></li>
    <li><code>q</code></li>
    <li><code>ruby</code></li>
    <li><code>samp</code></li>
    <li><code>script</code></li>
    <li><code>select</code></li>
@@ -12364,30 +12402,30 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
   </div>
 
 
 
 
   <h4>The <dfn><code>link</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Metadata content</span>.</dd>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <dd>If the <code title="attr-itemprop">itemprop</code> attribute is present: <span>flow content</span>.</dd>
    <dd>If the <code title="attr-itemprop">itemprop</code> attribute is present: <span>phrasing content</span>.</dd>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>metadata content</span> is expected.</dd>
    <dd>In a <code>noscript</code> element that is a child of a <code>head</code> element.</dd>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <dd>If the <code title="attr-itemprop">itemprop</code> attribute is present: where <span>phrasing content</span> is expected.</dd>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <dt>Content model:</dt>
    <dd>Empty.</dd>
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dd><code title="attr-link-href">href</code></dd>
    <dd><code title="attr-link-rel">rel</code></dd>
    <dd><code title="attr-link-media">media</code></dd>
    <dd><code title="attr-link-hreflang">hreflang</code></dd>
    <dd><code title="attr-link-type">type</code></dd>
    <dd><code title="attr-link-sizes">sizes</code></dd>
@@ -12411,25 +12449,25 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
   <p>The <code>link</code> element allows authors to link their
   document to other resources.</p>
 
   <p>The destination of the link(s) is given by the <dfn
   title="attr-link-href"><code>href</code></dfn> attribute, which must
   be present and must contain a <span>valid non-empty URL potentially
   surrounded by spaces</span>. <span class="impl">If the <code
   title="attr-link-href">href</code> attribute is absent, then the
   element does not define a link.</span></p>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
   <p>A <code>link</code> element must have either a <code
   title="attr-link-rel">rel</code> attribute, or an <code
   title="attr-itemprop">itemprop</code> attribute, or both.</p>
-<!--START w3c-html--><!--END html--><!--END complete--><!--END epub-->
+<!--START w3c-html--><!--MD--><!--END html--><!--END complete--><!--END epub-->
   <p>A <code>link</code> element must have <code
   title="attr-link-rel">rel</code> attribute.</p>
 <!--START html--><!--START complete--><!--START epub-->
 
   <p>The types of link indicated (the relationships) are given by the
   value of the <dfn title="attr-link-rel"><code>rel</code></dfn>
   attribute, which, if present, must have a value that is a <span>set
   of space-separated tokens</span>. The <a href="#linkTypes">allowed
   values and their meanings</a> are defined in a later section. <span
   class="impl">If the <code title="attr-link-rel">rel</code> attribute
@@ -12795,33 +12833,33 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
 
 
 
 
 
   <h4 id="meta">The <dfn><code>meta</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Metadata content</span>.</dd>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <dd>If the <code title="attr-itemprop">itemprop</code> attribute is present: <span>flow content</span>.</dd>
    <dd>If the <code title="attr-itemprop">itemprop</code> attribute is present: <span>phrasing content</span>.</dd>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <dt>Contexts in which this element may be used:</dt>
    <dd>If the <code title="attr-meta-charset">charset</code> attribute is present, or if the element's <code title="attr-meta-http-equiv">http-equiv</code> attribute is in the <span title="attr-meta-http-equiv-content-type">Encoding declaration state</span>: in a <code>head</code> element.</dd>
    <dd>If the <code title="attr-meta-http-equiv">http-equiv</code> attribute is present but not in the <span title="attr-meta-http-equiv-content-type">Encoding declaration state</span>: in a <code>head</code> element.</dd>
    <dd>If the <code title="attr-meta-http-equiv">http-equiv</code> attribute is present but not in the <span title="attr-meta-http-equiv-content-type">Encoding declaration state</span>: in a <code>noscript</code> element that is a child of a <code>head</code> element.</dd>
    <dd>If the <code title="attr-meta-name">name</code> attribute is present: where <span>metadata content</span> is expected.</dd>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
    <dd>If the <code title="attr-itemprop">itemprop</code> attribute is present: where <span>metadata content</span> is expected.</dd>
    <dd>If the <code title="attr-itemprop">itemprop</code> attribute is present: where <span>phrasing content</span> is expected.</dd>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
    <dt>Content model:</dt>
    <dd>Empty.</dd>
    <dt>Content attributes:</dt>
    <dd><span>Global attributes</span></dd>
    <dd><code title="attr-meta-name">name</code></dd>
    <dd><code title="attr-meta-http-equiv">http-equiv</code></dd>
    <dd><code title="attr-meta-content">content</code></dd>
    <dd><code title="attr-meta-charset">charset</code></dd>
    <dt>DOM interface:</dt>
    <dd>
@@ -12840,34 +12878,34 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
 
   <p>The <code>meta</code> element can represent document-level
   metadata with the <code title="attr-meta-name">name</code>
   attribute, pragma directives with the <code
   title="attr-meta-http-equiv">http-equiv</code> attribute, and the
   file's <span>character encoding declaration</span> when an HTML
   document is serialized to string form (e.g. for transmission over
   the network or for disk storage) with the <code
   title="attr-meta-charset">charset</code> attribute.</p>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
   <p>Exactly one of the <code title="attr-meta-name">name</code>,
   <code title="attr-meta-http-equiv">http-equiv</code>, <code
   title="attr-meta-charset">charset</code>, and <code
   title="attr-itemprop">itemprop</code> attributes must be
   specified.</p>
 
   <p>If either <code title="attr-meta-name">name</code>, <code
   title="attr-meta-http-equiv">http-equiv</code>, or <code
   title="attr-itemprop">itemprop</code> is specified, then the <code
   title="attr-meta-content">content</code> attribute must also be
   specified. Otherwise, it must be omitted.</p>
 <!--END html--><!--END complete--><!--END epub-->
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
   <p>Exactly one of the <code title="attr-meta-name">name</code>,
   <code title="attr-meta-http-equiv">http-equiv</code>, and <code
   title="attr-meta-charset">charset</code> attributes must be
   specified.</p>
 
   <p>If either <code title="attr-meta-name">name</code> or <code
   title="attr-meta-http-equiv">http-equiv</code> is specified, then
   the <code title="attr-meta-content">content</code> attribute must
   also be specified. Otherwise, it must be omitted.</p>
 <!--START html--><!--START complete--><!--START epub-->
@@ -20928,20 +20966,21 @@ interface <dfn>HTMLImageElement</dfn> : <span>HTMLElement</span> {
   with an SVG root element), animated bitmaps (APNGs, animated GIFs),
   animated vector graphics (XML files with an SVG root element that
   use declarative SMIL animation), and so forth. However, this also
   precludes SVG files with script, multipage PDF files, interactive
   MNG files, HTML documents, plain text documents, and so forth.</p>
 
   <p>The requirements on the <code title="attr-img-alt">alt</code>
   attribute's value are described <a href="#alt">in the next
   section</a>.
   <!--END complete--><!--END epub--><!--END html-->
+  <!-- only included in w3c-html--><!--WCAG-->
   For guidance on accessibility requirements for text alternatives
   authors are encouraged to also consult
   <a href="http://www.w3.org/TR/WCAG20/">WCAG 2.0</a>.
   <a href="#refsWCAG">[WCAG]</a>
   <!--START complete--><!--START epub--><!--START html-->
   </p>
 
   <p>The <code>img</code> must not be used as a layout tool. In
   particular, <code>img</code> elements should not be used to display
   transparent images, as they rarely convey meaning and rarely add
@@ -21191,26 +21230,31 @@ interface <dfn>HTMLImageElement</dfn> : <span>HTMLElement</span> {
   </dl>
 
   <p>The <code title="attr-img-alt">alt</code> attribute does not
   represent advisory information. User agents must not present the
   contents of the <code title="attr-img-alt">alt</code> attribute in
   the same way as content of the <code title="attr-title">title</code>
   attribute.</p>
 
   <p>User agents may always provide the user with the option to
   display any image, or to prevent any image from being
-  displayed. User agents may also apply heuristics to help the user
-  make use of the image when the user is unable to see it, e.g. due to
-  a visual disability or because they are using a text terminal with
-  no graphics capabilities. Such heuristics could include, for
-  instance, optical character recognition (OCR) of text found within
-  the image.</p>
+  displayed.
+
+  <!--END w3c-html--><!--POLITICS-->
+  User agents may also apply heuristics to help the user make use of
+  the image when the user is unable to see it, e.g. due to a visual
+  disability or because they are using a text terminal with no
+  graphics capabilities. Such heuristics could include, for instance,
+  optical character recognition (OCR) of text found within the image.
+  <!--START w3c-html--><!--POLITICS-->
+
+  </p>
 
   <p class="warning">While user agents are encouraged to repair cases
   of missing <code title="attr-img-alt">alt</code> attributes, authors
   must not rely on such behavior. <a href="#alt">Requirements for
   providing text to act as an alternative for images</a> are described
   in detail below.</p>
 
   <p>The <em>contents</em> of <code>img</code> elements, if any, are
   ignored for the purposes of rendering.</p>
 
@@ -29382,32 +29426,32 @@ CueEvent
    <dd>
 
     <p>Returns an object that exposes an API for drawing on the canvas.</p>
 
     <p>Returns null if the given context ID is not supported.</p>
 
    </dd>
 
   </dl>
 
-  <!--END w3c-html-->
+  <!--END w3c-html--><!--2DCONTEXT-->
 
   <p>This specification only defines one context, with the name "<code
   title="canvas-context-2d">2d</code>". <span class="impl">If <code
   title="dom-canvas-getContext">getContext()</code> is called with
   that exact string for its <var title="">contextId</var> argument,
   then the UA must return a reference to an object implementing
   <code>CanvasRenderingContext2D</code>. Other specifications may
   define their own contexts, which would return different
   objects.</span></p>
 
-  <!--START w3c-html-->
+  <!--START w3c-html--><!--2DCONTEXT-->
   <!--END complete--><!--END epub--><!--END html-->
   <p>Contexts are defined by other specifications, for example the 2D
   Context specification. <a href="#refs2DCONTEXT">[2DCONTEXT]</a></p>
   <!--START complete--><!--START epub--><!--START html-->
 
   <div class="impl">
 
   <p>Vendors may also define experimental contexts using the syntax
   <code><var title="">vendorname</var>-<var
   title="">context</var></code>, for example, <code>moz-3d</code>.</p>
@@ -29524,21 +29568,21 @@ CueEvent
 
   <p>Other arguments must be ignored and must not cause the user agent
   to raise an exception. A future version of this specification will
   probably define other parameters to be passed to <code
   title="dom-canvas-toDataURL">toDataURL()</code> to allow authors to
   more carefully control compression settings, image metadata,
   etc.</p>
 
   </div>
 
-  <!--END w3c-html-->
+  <!--END w3c-html--><!--2DCONTEXT-->
 
   <div data-component="HTML Canvas 2D Context (editor: Ian Hickson)">
 
   <h5 id="2dcontext">The 2D context</h5>
 
   <!-- v2: we're on v4. suggestions for next version are marked v5. -->
 
   <p>When the <code title="dom-canvas-getContext">getContext()</code>
   method of a <code>canvas</code> element is invoked with <dfn
   title="canvas-context-2d"><code>2d</code></dfn> as the argument, a
@@ -32931,21 +32975,21 @@ function AddCloud(data, x, y) { ... }</pre>
    context.fillRect(0, 0, context.canvas.width, context.canvas.height);
  }
  setInterval(blank, 40);
 
 &lt;/script></pre>
 
   <!--END 2dcontext-->
 
   </div><!--data-component-->
 
-  <!--START w3c-html-->
+  <!--START w3c-html--><!--2DCONTEXT-->
 
   <div class="impl">
 
   <h5>Color spaces and color correction</h5>
 
   <p>The <code>canvas</code> APIs must perform color correction at
   only two points: when rendering images with their own gamma
   correction and color space information onto the canvas, to convert
   the image to the color space used by the canvas (e.g. using the 2D
   Context's <code title="dom-context-2d-drawImage">drawImage()</code>
@@ -36826,21 +36870,21 @@ the cell that corresponds to the values of the two dice.
      <td>$ 11,145
      <td>$  8,154
      <td>$  5,598
    <tfoot>
     <tr>
      <th>Gross margin percentage
      <td>34.3%
      <td>34.0%
      <td>29.0%
   </table>
-<!--START w3c-html-->
+<!--START w3c-html--><!--HTML4POLICE-->
 
   <hr>
 
   <p>The following shows how one might mark up the operating expenses
   table from lower on the same page of that document:</p>
 
   <pre>&lt;table>
  &lt;colgroup> &lt;col>
  &lt;colgroup> &lt;col> &lt;col> &lt;col>
  &lt;thead>
@@ -52958,21 +53002,21 @@ interface <dfn>DataGridListener</dfn> {
 
    <li>Otherwise, if the element does not have a defined
    <span>activation behavior</span>, <span>fire a <code
    title="event-click">click</code> event</span> at the element.</li>
 
   </ol>
 
   </div>
 
 
-<!--END w3c-html--><!--START html-device-->
+<!--END w3c-html--><!--DEVICE--><!--START html-device-->
 
   <h4 id="devices">The <dfn><code>device</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
    <dd><span>Phrasing content</span>.</dd>
    <dd><span>Interactive content</span>.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <span>phrasing content</span> is expected.</dd>
@@ -53187,21 +53231,21 @@ local.onconnect = function (event) {
 };</pre>
 
   </div>
 
   <p class="warning">To prevent network sniffing from allowing a
   fourth party to establish a connection to a peer using the
   information sent out-of-band to the other peer and thus spoofing the
   client, the configuration information should always be transmitted
   using an encrypted connection.</p>
 
-<!--END html-device--><!--START w3c-html-->
+<!--END html-device--><!--START w3c-html--><!--DEVICE-->
 
 
 
 
   <h3 id="links">Links</h3>
 
 
   <h4>Hyperlink elements</h4>
 
   <p>The <code>a</code>, <code>area</code>, and <code>link</code>
@@ -55430,21 +55474,21 @@ contradict people?
   <p class="note">This specification does not define when an element
   matches the <code title="selector-hover">:hover</code>, <code
   title="selector-focus">:focus</code>, or <code
   title="selector-lang()">:lang()</code> dynamic pseudo-classes, as
   those are all defined in sufficient detail in a language-agnostic
   fashion in the Selectors specification. <a
   href="#refsSELECTORS">[SELECTORS]</a></p>
 
   </div>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
 
 
   <div data-component="HTML Microdata (editor: Ian Hickson)">
 
   <h2 id="microdata"><dfn>Microdata</dfn></h2>
 
 <!-- v2
 
   * <itemref itemprop="foo" src="url#id"> to import the item with
     id="id" from url into the current microdata block as the value of
@@ -59997,29 +60041,24 @@ END:VCARD</pre>
 &lt;/figure></pre>
 
   </div>
 
 <!--END work-->
 
 <!--END vocabs-->
 
 <!--START microdata-->
 
-<!--START w3c-html-->
-
   <div class="impl">
 
   <h3>Converting HTML to other formats</h3>
 
-<!--END w3c-html-->
-
-
   <h4>JSON</h4>
 
   <p>Given a list of nodes <var title="">nodes</var> in a
   <code>Document</code>, a user agent must run the following algorithm
   to <dfn title="extracting JSON">extract the microdata from those
   nodes into a JSON form</dfn>:</p>
 
   <ol>
 
    <li><p>Let <var title="">result</var> be an empty object.</p></li>
@@ -61177,21 +61216,21 @@ _:n2  hcard:adr%20street-address "Avenue Q" ;
 
   <p class="note">The above algorithm does not guarantee that the
   output will be a conforming Atom feed. In particular, if
   insufficient information is provided in the document (e.g. if the
   document does not have any <code title="">&lt;meta name="author"
   content="..."></code> elements), then the output will not be
   conforming.</p>
 
   <p>The <dfn>Atom namespace</dfn> is: <code>http://www.w3.org/2005/Atom</code></p>
 
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
 <!--START microdata-->
 
   </div>
 
 <!--END microdata-->
 
 
 
   <h2 id="browsers">Loading Web pages</h2>
 
@@ -61785,23 +61824,23 @@ interface <dfn>Window</dfn> {
   readonly attribute <span>Navigator</span> <span title="dom-navigator">navigator</span>; <!-- IE also has window.clientInformation === window.navigator -->
   readonly attribute <span>ApplicationCache</span> <span title="dom-applicationCache">applicationCache</span>;
 
   // user prompts
   void <span title="dom-alert">alert</span>(in DOMString message);
   boolean <span title="dom-confirm">confirm</span>(in DOMString message);
   DOMString <span title="dom-prompt">prompt</span>(in DOMString message, in optional DOMString default);
   void <span title="dom-print">print</span>();
   any <span title="dom-showModalDialog">showModalDialog</span>(in DOMString url, in optional any argument<!--, in optional DOMString features-->);
 
-<!--END w3c-html-->  // <span>cross-document messaging</span>
+<!--END w3c-html--><!--POSTMSG-->  // <span>cross-document messaging</span>
   void <span title="dom-window-postMessage">postMessage</span>(in any message, in DOMString targetOrigin, in optional <span>MessagePortArray</span> ports);
-<!--START w3c-html-->
+<!--START w3c-html--><!--POSTMSG-->
   // <span>event handler IDL attributes</span>
            attribute <span>Function</span> <span title="handler-onabort">onabort</span>;
            attribute <span>Function</span> <span title="handler-window-onafterprint">onafterprint</span>;
            attribute <span>Function</span> <span title="handler-window-onbeforeprint">onbeforeprint</span>;
            attribute <span>Function</span> <span title="handler-window-onbeforeunload">onbeforeunload</span>;
            attribute <span>Function</span> <span title="handler-window-onblur">onblur</span>;
            attribute <span>Function</span> <span title="handler-oncanplay">oncanplay</span>;
            attribute <span>Function</span> <span title="handler-oncanplaythrough">oncanplaythrough</span>;
            attribute <span>Function</span> <span title="handler-onchange">onchange</span>;
            attribute <span>Function</span> <span title="handler-onclick">onclick</span>;
@@ -73549,36 +73588,36 @@ interface <dfn>NavigatorAbilities</dfn> {
     title="dom-DragEvent-dataTransfer">dataTransfer</code> member's
     <code title="dom-datatransfer-files">files</code> attribute's
     <code>FileList</code> object. (Dragging files can only happen from
     outside a <span>browsing context</span>, for example from a file
     system manager application, and thus the <code
     title="event-dragstart">dragstart</code> event is actually implied
     in this case.)</p>
 
    </li>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
 
    <li>
 
     <p>The user agent must take the <span>list of dragged nodes</span>
     and <span title="extracting JSON">extract the microdata from those
     nodes into a JSON form</span>, and then must add the resulting
     string to the <code
     title="dom-DragEvent-dataTransfer">dataTransfer</code> member,
     associated with the <code
     title="">application/microdata+json</code> format.</p>
 
    </li>
 
 <!--END complete--><!--END epub--><!--END html-->
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
 
    <li>Perform <dfn>drag-and-drop initialization steps</dfn> defined
    in other relevant specificaations.</li>
 
 <!--START complete--><!--START epub--><!--START html-->
 
 <!-- v2: deal with multiple vCards -->
 <!--
    <li>
 
@@ -77128,21 +77167,20 @@ interface <dfn>WorkerUtils</dfn> {
   must be the empty string, the <code
   title="dom-MessageEvent-origin">origin</code> attribute must be the
   empty string, the <code
   title="dom-MessageEvent-source">source</code> attribute must be
   null, and the <code title="dom-MessageEvent-ports">ports</code>
   attribute must be null.</p>
 
   </div>
 
   <!--END html-->
-
   <!--END postmsg-->
 
   </div><!--data-component-->
 
 
 
   <h3 id="server-sent-events"><dfn>Server-sent events</dfn></h3>
 
   <div data-component="Server-Sent Events (editor: Ian Hickson)">
 
@@ -95850,45 +95888,49 @@ fieldset {
   changes, and are expected to disappear when the user does not need
   them.</p>
 
   <p>When a <code>video</code> element represents a poster frame or
   frame of video, the poster frame or frame of video is expected to be
   rendered at the largest size that maintains the aspect ratio of that
   poster frame or frame of video without being taller or wider than
   the <code>video</code> element itself, and is expected to be
   centered in the <code>video</code> element.</p>
 
+<!--END w3c-html--><!--TT-->
   <p class="XXX">pointer to rendering model for timed tracks</p>
+<!--START w3c-html--><!--TT-->
 
   <p class="note">Resizing <code>video</code> and <code>canvas</code>
   elements does not interrupt video playback or clear the canvas.</p>
 
   <hr>
 
   <p>The following CSS rules are expected to apply:</p>
 
   <pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
 
 iframe { border: 2px inset; }</pre>
 
   </div>
 
 
+<!--END w3c-html--><!--TT-->
   <div class="impl">
 
   <h4>Timed tracks</h4>
 
   <p class="XXX">rendering model for timed tracks</p>
 
   <p class="XXX">CSS extensions</p>
 
   </div>
+<!--START w3c-html--><!--TT-->
 
 
   <div class="impl">
 
   <h4>Images</h4>
 
   <p>When an <code>img</code> element or an <code>input</code> element
   when its <code title="attr-input-type">type</code> attribute is in
   the <span title="attr-input-type-image">Image Button</span> state
   <span>represents</span> an image, it is expected to be treated as a
@@ -99596,20 +99638,21 @@ interface <span>HTMLDocument</span> {
    <dt>Author:</dt>
    <dd>Ian Hickson &lt;ian@hixie.ch></dd>
    <dt>Change controller:</dt>
    <dd>WHATWG</dd>
   </dl>
 
   <p>Fragment identifiers have no meaning with
   <code>text/ping</code> resources.</p>
 <!--START w3c-html--><!--PING-->
 
+<!--END w3c-html--><!--TT-->
   <h3><dfn><code>text/srt</code></dfn></h3>
 
   <p>This registration is for community review and will be submitted
   to the IESG for review, approval, and registration with IANA.</p>
 
   <!--
    To: ietf-types@iana.org
    Subject: Registration of media type text/cues
   -->
 
@@ -99666,24 +99709,25 @@ interface <span>HTMLDocument</span> {
    <dt>Restrictions on usage:</dt>
    <dd>No restrictions apply.</dd>
    <dt>Author:</dt>
    <dd>Ian Hickson &lt;ian@hixie.ch></dd>
    <dt>Change controller:</dt>
    <dd>WHATWG</dd>
   </dl>
 
   <p>Fragment identifiers have no meaning with
   <code>text/srt</code> resources.</p>
+<!--START w3c-html--><!--TT-->
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD--><!--START microdata-->
 
-<!--END complete--><!--END epub--><!--END html--><!--START microdata-->
+<!--END complete--><!--END epub--><!--END html-->
   <h4><dfn><code>application/microdata+json</code></dfn></h4>
 <!--START complete--><!--START epub--><!--START html--><!--END microdata-->
   <h3><dfn><code>application/microdata+json</code></dfn></h3>
 <!--START microdata-->
 
   <p>This registration is for community review and will be submitted
   to the IESG for review, approval, and registration with IANA.</p>
 
   <!--
    To: ietf-types@iana.org
@@ -99746,21 +99790,21 @@ interface <span>HTMLDocument</span> {
    <dd>Ian Hickson &lt;ian@hixie.ch></dd>
    <dt>Change controller:</dt>
    <dd>WHATWG</dd>
   </dl>
 
   <p>Fragment identifiers used with
   <code>application/microdata+json</code> resources have the same
   semantics as when used with <code>application/json</code>. <a
   href="#refsJSON">[JSON]</a></p>
 
-<!--END microdata--><!--START w3c-html-->
+<!--END microdata--><!--START w3c-html--><!--MD-->
 
 <!--END w3c-html--><!--PING-->
   <h3><dfn title="http-ping-from"><code>Ping-From</code></dfn></h3>
 
   <p>This section describes a header field for registration in the
   Permanent Message Header Field Registry.  <a
   href="#refsRFC3864">[RFC3864]</a></p>
 
   <dl>
    <dt>Header field name</dt>
@@ -101353,24 +101397,24 @@ interface <span>HTMLDocument</span> {
       <code>table</code>;
       <code>textarea</code>;
       <code>time</code>;
       <code>ul</code>;
       <code>var</code>;
       <code>video</code>;
       <code>wbr</code>;
       <span title="text content">Text</span>
      <td>
       <code>area</code> (if it is a descendant of a <code>map</code> element);
-      <!--END w3c-html-->
+      <!--END w3c-html--><!--MD-->
       <code>link</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present);
       <code>meta</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present);
-      <!--START w3c-html-->
+      <!--START w3c-html--><!--MD-->
       <code>style</code> (if the <code title="attr-style-scoped">scoped</code> attribute is present)
 
     <tr>
      <td> <span>Sectioning content</span>
      <td>
       <code>article</code>;
       <code>aside</code>;
       <code>nav</code>;
       <code>section</code>
      <td>
@@ -101435,27 +101479,27 @@ interface <span>HTMLDocument</span> {
       <code>time</code>;
       <code>var</code>;
       <code>video</code>;
       <code>wbr</code>;
       <span title="text content">Text</span>
      <td>
       <code>a</code> (if it contains only <span>phrasing content</span>);
       <code>area</code> (if it is a descendant of a  <code>map</code> element);
       <code>del</code> (if it contains only <span>phrasing content</span>);
       <code>ins</code> (if it contains only <span>phrasing content</span>);
-      <!--END w3c-html-->
+      <!--END w3c-html--><!--MD-->
       <code>link</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present);
-      <!--START w3c-html-->
+      <!--START w3c-html--><!--MD-->
       <code>map</code> (if it contains only <span>phrasing content</span>)<!--
-      --><!--END w3c-html--><!--
+      --><!--END w3c-html--><!--MD--><!--
       -->; <code>meta</code> (if the <code title="attr-itemprop">itemprop</code> attribute is present)<!--
-      --><!--START w3c-html--><!--
+      --><!--START w3c-html--><!--MD--><!--
       -->
 
     <tr>
      <td> <span>Embedded content</span>
      <td>
       <code>audio</code>
       <code>canvas</code>
       <code>embed</code>
       <code>iframe</code>
       <code>img</code>
@@ -101900,21 +101944,21 @@ interface <span>HTMLDocument</span> {
     <tr>
      <th> <code title="">id</code>
      <td> <span title="attr-id">HTML elements</span>
      <td> The element's <span title="concept-id">ID</span>
      <td> <a href="#attribute-text">Text</a>*
     <tr>
      <th> <code title="">ismap</code>
      <td> <code title="attr-img-ismap">img</code>
      <td> Whether the image is a server-side image map
      <td> <span>Boolean attribute</span>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
     <tr>
      <th> <code title="">itemid</code>
      <td> <span title="attr-itemid">HTML elements</span>
      <td> <span>Global identifier</span> for a microdata item
      <td> <span>Valid URL potentially surrounded by spaces</span>
     <tr>
      <th> <code title="">itemprop</code>
      <td> <span title="attr-itemprop">HTML elements</span>
      <td> <span>Property names</span> of a microdata item
      <td> <span>Unordered set of unique space-separated tokens</span> consisting of <span title="absolute URL">valid absolute URLs</span>, <span title="defined property name">defined property names</span>, or text*
@@ -101926,21 +101970,21 @@ interface <span>HTMLDocument</span> {
     <tr>
      <th> <code title="">itemscope</code>
      <td> <span title="attr-itemscope">HTML elements</span>
      <td> Introduces a microdata item
      <td> <span>Boolean attribute</span>
     <tr>
      <th> <code title="">itemtype</code>
      <td> <span title="attr-itemtype">HTML elements</span>
      <td> <span>Item type</span> of a microdata item
      <td> <span title="absolute URL">Valid absolute URL</span>*
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
     <tr>
      <th> <code title="">keytype</code>
      <td> <code title="attr-keygen-keytype">keygen</code>
      <td> The type of cryptographic key to generate
      <td> <a href="#attribute-text">Text</a>*
 <!--END w3c-html--><!--TT-->
     <tr>
      <th> <code title="">kind</code>
      <td> <code title="attr-track-kind">track</code>
      <td> The type of timed track
@@ -103479,25 +103523,24 @@ interface <span>HTMLDocument</span> {
      <td> <code title="event-unload">unload</code>
      <td> <code>Event</code>
      <td> Fired at the <code>Window</code> object when the page is going away
 
   </table>
 
   <p class="note">See also <a href="#mediaevents">media element
   events</a>, <a href="#appcacheevents">application cache events</a>,
   and <a href="#dndevents">drag-and-drop events</a>.</p>
 
-<!--END w3c-html-->
+<!--END w3c-html--><!--END html-->
 
 
-<!--START complete--><!--START epub-->
-
+<!--START complete--><!--START epub--><!--START html-->
 <!--START html-device--><!--START microdata--><!--START 2dcontext--><!--START postmsg--><!--START w3c-html-->
 <!--START websocket-api--><!--START storage--><!--START database--><!--START eventsource--><!--START workers-->
 <!--START whatwg-workers--><!--START vocabs--><!--START vCard--><!--START vEvent--><!--START work-->
 
   <h2 class="no-num" id="references">References</h2><!--REFS-->
 
   <p>All references are normative unless marked "Non-normative".</p>
 
   <!-- Dates are only included for standards older than the Web, because the newer ones keep changing. -->
 

|