HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
3580Add references. Define MIME type. Define valid MIME type.2009-08-11 00:57
@@ -244,23 +244,23 @@
 
   <p>The in-memory representation is known as "DOM5 HTML", or "the
   DOM" for short.</p>
 
   <p>There are various concrete syntaxes that can be used to transmit
   resources that use this abstract language, two of which are defined
   in this specification.</p>
 
   <p>The first such concrete syntax is "HTML5". This is the format
   recommended for most authors. It is compatible with all legacy Web
-  browsers. If a document is transmitted with the MIME type
-  <code>text/html</code>, then it will be processed as an "HTML5"
-  document by Web browsers.</p>
+  browsers. If a document is transmitted with the <span>MIME
+  type</span> <code>text/html</code>, then it will be processed as an
+  "HTML5" document by Web browsers.</p>
 
   <p>The second concrete syntax uses XML, and is known as
   "XHTML5". When a document is transmitted with an <span>XML MIME
   type</span>, such as <code>application/xhtml+xml</code>, then it is
   processed by an XML processor by Web browsers, and treated as an
   "XHTML5" document. Authors are reminded that the processing for XML
   and HTML differs; in particular, even minor syntax errors will
   prevent an XML document from being rendered fully, whereas they
   would be ignored in the "HTML5" syntax.</p>
 
@@ -602,20 +602,53 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   sometimes be used when referring to the way a document is rendered
   to the user. These terms are not meant to imply a visual medium;
   they must be considered to apply to other media in equivalent
   ways.</p>
 
   <p>When an algorithm B says to return to another algorithm A, it
   implies that A called B. Upon returning to A, the implementation
   must continue from where it left off in calling B.</p>
 
 
+  <h4>Resources</h4>
+
+  <p>The specification uses the term <dfn title="">supported</dfn>
+  when referring to whether a user agent has an implementation capable
+  of decoding the semantics of an external resource. A format or type
+  is said to be <i>supported</i> if the implementation can process an
+  external resource of that format or type without critical aspects of
+  the resource being ignored. Whether a specific resource is
+  <i>supported</i> can depend on what features of the resource's
+  format are in use.</p>
+
+  <p class="example">For example, a PNG image would be considered to
+  be in a supported format if its pixel data could be decoded and
+  rendered, even if, unbeknownst to the implementation, the image
+  actually also contained animation data.</p>
+
+  <p class="example">A MPEG4 video file would not be considered to be
+  in a supported format if the compression format used was not
+  supported, even if the implementation could determine the dimensions
+  of the movie from the file's metadata.</p>
+
+  <p>The term <dfn>MIME type</dfn> is used to refer to what is
+  sometimes called an <i>Internet media type</i> in protocol
+  literature. The term <i>media type</i> in this specification is used
+  to refer to the type of media intended for presentation, as used by
+  the CSS specifications. <a href="#refsRFC2046">[RFC2046]</a> <a
+  href="#refsMQ">[MQ]</a></p>
+
+  <p>A string is a <dfn>valid MIME type</dfn> if it matches the <code
+  title="">media-type</code> token defined in section 3.7 "Media
+  Types" of RFC 2616. <a href="#refsHTTP">[HTTP]</a></p>
+
+
   <h4>XML</h4>
 
   <p id="html-namespace">To ease migration from HTML to XHTML, UAs
   conforming to this specification will place elements in HTML in the
   <code>http://www.w3.org/1999/xhtml</code> namespace, at least for
   the purposes of the DOM and CSS. The term "<dfn>elements in the HTML
   namespace</dfn>", or "<dfn>HTML elements</dfn>" for short, when used
   in this specification, thus refers to both HTML and XHTML
   elements.</p>
 
@@ -641,24 +674,24 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    <dd><code>http://www.w3.org/2000/svg</code></dd>
   </dl>
 
   <p>Attribute names are said to be <dfn>XML-compatible</dfn> if they
   match the <a href="http://www.w3.org/TR/REC-xml/#NT-Name"><code
   title="">Name</code></a> production defined in XML, they contain no
   U+003A COLON (:) characters, and their first three characters are
   not an <span>ASCII case-insensitive</span> match for the string
   "<code title="">xml</code>". <a href="#refsXML">[XML]</a></p>
 
-  <p>The term <dfn>XML MIME type</dfn> is used to refer to the MIME
-  types <code title="">text/xml</code>, <code
-  title="">application/xml</code>, and any MIME type ending with the
-  four characters "<code title="">+xml</code>". <a
+  <p>The term <dfn>XML MIME type</dfn> is used to refer to the <span
+  title="MIME type">MIME types</span> <code title="">text/xml</code>,
+  <code title="">application/xml</code>, and any MIME type ending with
+  the four characters "<code title="">+xml</code>". <a
   href="#refsRFC3023">[RFC3023]</a></p>
 
 
   <h4>DOM trees</h4>
 
   <p>The term <dfn>root element</dfn>, when not explicitly qualified
   as referring to the document's root element, means the furthest
   ancestor element node of whatever node is being discussed, or the
   node itself if it has no ancestors. When the node is a part of the
   document, then that is indeed the document's root element; however,
@@ -787,49 +820,20 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   encodings as UTF-7, UTF-16, HZ-GB-2312, GSM03.38, and EBCDIC
   variants.</p>
 
   <!--
    We'll have to change that if anyone comes up with a way to have a
    document that is valid as two different encodings at once, with
    different <meta charset> elements applying in each case.
   -->
 
 
-  <h4>Resources</h4>
-
-  <p>The specification uses the term <dfn title="">supported</dfn> when referring
-  to whether a user agent has an implementation capable of decoding
-  the semantics of an external resource. A format or type is said to
-  be <i>supported</i> if the implementation can process an external
-  resource of that format or type without critical aspects of the
-  resource being ignored. Whether a specific resource is
-  <i>supported</i> can depend on what features of the resource's
-  format are in use.</p>
-
-  <p class="example">For example, a PNG image would be considered to
-  be in a supported format if its pixel data could be decoded and
-  rendered, even if, unbeknownst to the implementation, the image
-  actually also contained animation data.</p>
-
-  <p class="example">A MPEG4 video file would not be considered to be
-  in a supported format if the compression format used was not
-  supported, even if the implementation could determine the dimensions
-  of the movie from the file's metadata.</p>
-
-  <p>The term <i>MIME type</i> is used to refer to what is sometimes
-  called an <i>Internet media type</i> in protocol literature. The
-  term <i>media type</i> in this specification is used to refer to the
-  type of media intended for presentation, as used by the CSS
-  specifications. <a href="#refsRFC2046">[RFC2046]</a> <a
-  href="#refsMQ">[MQ]</a></p>
-
-
 
 
   <h3>Conformance requirements</h3>
 
   <p>All diagrams, examples, and notes in this specification are
   non-normative, as are all sections explicitly marked non-normative.
   Everything else in this specification is normative.</p>
 
   <p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
   NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
@@ -1101,21 +1105,22 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   <p id="authors-using-xhtml">XML documents that use elements or
   attributes from the <span>HTML namespace</span> and that are served
   over the wire (e.g. by HTTP) must be sent using an <span>XML MIME
   type</span> such as <code>application/xml</code> or
   <code>application/xhtml+xml</code> and must not be served as
   <code>text/html</code>. <a href="#refsRFC3023">[RFC3023]</a></p>
 
   <p id="authors-using-html">Documents that use <span>the HTML
   syntax</span>, if they are served over the wire (e.g. by HTTP) must
-  be labeled with the <code>text/html</code> MIME type.</p>
+  be labeled with the <code>text/html</code> <span>MIME
+  type</span>.</p>
 
   <p id="entity-references" class="impl">The language in this
   specification assumes that the user agent expands all entity
   references, and therefore does not include entity reference nodes in
   the DOM. If user agents do include entity reference nodes in the
   DOM, then user agents must handle them as if they were fully
   expanded when implementing this specification. For example, if a
   requirement talks about an element's child text nodes, then any text
   nodes that are children of an entity reference that is a child of
   that element would be used as well. Entity references to unknown
@@ -1134,21 +1139,21 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   <dl>
 
    <dt>XML</dt>
 
    <dd>
 
     <p>Implementations that support <span>the XHTML syntax</span> must
     support some version of XML, as well as its corresponding
     namespaces specification, because that syntax uses an XML
     serialization with namespaces. <a href="#refsXML">[XML]</a> <a
-    href="#refsXMLNAMES">[XMLNAMES]</a></p>
+    href="#refsXMLNS">[XMLNS]</a></p>
 
    </dd>
 
    <dt>DOM</dt>
 
    <dd>
 
     <p>The Document Object Model (DOM) is a representation &mdash; a
     model &mdash; of a document and its content. The DOM is not just
     an API; the conformance criteria of HTML implementations are
@@ -1186,26 +1191,26 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    <dt>JavaScript</dt>
 
    <dd>
 
     <p>Some parts of the language described by this specification only
     support JavaScript as the underlying scripting language. <a
     href="#refsECMA262">[ECMA262]</a></p>
 
     <p class="note">The term "JavaScript" is used to refer to ECMA262,
     rather than the official term ECMAScript, since the term
-    JavaScript is more widely known. Similarly, the MIME type used to
-    refer to JavaScript in this specification is <code
-    title="">text/javascript</code>, since that is the most commonly
-    used type, <span title="willful violation">despite it being an
-    officially obsoleted type</span> according to RFC 4329. <a
-    href="#refsRFC4329">[RFC4329]</a></p>
+    JavaScript is more widely known. Similarly, the <span>MIME
+    type</span> used to refer to JavaScript in this specification is
+    <code title="">text/javascript</code>, since that is the most
+    commonly used type, <span title="willful violation">despite it
+    being an officially obsoleted type</span> according to RFC
+    4329. <a href="#refsRFC4329">[RFC4329]</a></p>
 
    </dd>
 
    <dt id="mq">Media Queries</dt>
 
    <dd>
 
     <p>Implementations must support some version of the Media Queries
     language. <a href="#refsMQ">[MQ]</a></p>
 
@@ -1284,21 +1289,21 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   <p>Comparing two strings in an <dfn>ASCII case-insensitive</dfn>
   manner means comparing them exactly, code point for code point, except
   that the characters in the range U+0041 .. U+005A (i.e. LATIN
   CAPITAL LETTER A to LATIN CAPITAL LETTER Z) and the corresponding
   characters in the range U+0061 .. U+007A (i.e. LATIN SMALL LETTER A
   to LATIN SMALL LETTER Z) are considered to also match.</p>
 
   <p>Comparing two strings in a <dfn>compatibility caseless</dfn>
   manner means using the Unicode <i>compatibility caseless match</i>
   operation to compare the two strings. <a
-  href="#refsUNICODECASE">[UNICODECASE]</a></p>
+  href="#refsUNICODE">[UNICODE]</a></p>
 
 
   <div class="impl">
 
   <p><dfn title="converted to ASCII uppercase">Converting a string to
   ASCII uppercase</dfn> means replacing all characters in the range
   U+0061 .. U+007A (i.e. LATIN SMALL LETTER A to LATIN SMALL LETTER Z)
   with the corresponding characters in the range U+0041 .. U+005A
   (i.e. LATIN CAPITAL LETTER A to LATIN CAPITAL LETTER Z).</p>
 
@@ -4077,22 +4082,21 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
     href="#refsRFC3490">[RFC3490]</a></p>
 
    </li>
 
    <li>
 
     <p>Check that the end of the resulting string matches a suffix in
     the Public Suffix List, and that there is at least one domain
     label before the matching substring. If it does not, or if there
     is not, then the string is not valid; abort these steps. <a
-    href="#refsPSL">[PSL]</a></p> <!-- [PSL] http://publicsuffix.org/
-    -->
+    href="#refsPSL">[PSL]</a></p>
 
    </li>
 
    <li>
 
     <p>Check that the domain name up to the label before the prefix
     that was matched in the previous string is a registered domain
     name.</p>
 
    </li>
@@ -4817,24 +4821,24 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
          <a href="#refsRFC1345">[RFC1345]</a>
          <a href="#refsGBK">[GBK]</a>
     <tr> <td> GB_2312-80 <td> GBK <td>
          <a href="#refsRFC1345">[RFC1345]</a>
          <a href="#refsGBK">[GBK]</a>
     <tr> <td> ISO-8859-1 <td> windows-1252 <td>
          <a href="#refsRFC1345">[RFC1345]</a>
          <a href="#refsWIN1252">[WIN1252]</a>
     <tr> <td> ISO-8859-9 <td> windows-1254 <td>
          <a href="#refsRFC1345">[RFC1345]</a>
-         <a href="#refsWin1254">[WIN1254]</a>
+         <a href="#refsWIN1254">[WIN1254]</a>
     <tr> <td> ISO-8859-11 <td> windows-874 <td>
          <a href="#refsISO885911">[ISO885911]</a>
-         <a href="#refsWin874">[WIN874]</a>
+         <a href="#refsWIN874">[WIN874]</a>
     <tr> <td> KS_C_5601-1987 <td> windows-949 <td>
          <a href="#refsRFC1345">[RFC1345]</a>
          <a href="#refsWIN949">[WIN949]</a>
     <tr> <td> Shift_JIS <td> windows-31J <td>
          <a href="#refsSHIFTJIS">[SHIFTJIS]</a>
          <a href="#refsWIN31J">[WIN31J]</a>
     <tr> <td> TIS-620 <td> windows-874 <td>
          <a href="#refsTIS620">[TIS620]</a>
          <a href="#refsWIN874">[WIN874]</a>
     <tr> <td> US-ASCII <td> windows-1252 <td>
@@ -7868,22 +7872,22 @@ Transport Protocol">HTTP&lt;/abbr> today.&lt;/p></pre>
   </div>
 
 
 
   <h5>The <code title="attr-lang">lang</code> and <code
   title="attr-xml-lang">xml:lang</code> attributes</h5>
 
   <p>The <dfn title="attr-lang"><code>lang</code></dfn> attribute (in
   no namespace) specifies the primary <dfn>language</dfn> for the
   element's contents and for any of the element's attributes that
-  contain text. Its value must be a valid RFC 3066 language code, or
-  the empty string. <a href="#refsRFC3066">[RFC3066]</a></p>
+  contain text. Its value must be a valid BCP 47 language code, or
+  the empty string. <a href="#refsBCP47">[BCP47]</a></p>
 
   <p>The <dfn title="attr-xml-lang"><code title="">lang</code></dfn>
   attribute in the <span>XML namespace</span> is defined in XML. <a
   href="#refsXML">[XML]</a></p>
 
   <p>If these attributes are omitted from an element, then the
   language of this element is the same as the language of its parent
   element, if any. Setting the attribute to the empty string indicates
   that the primary language is unknown.</p> <!-- UA conformance
   requires for this are below -->
@@ -10592,35 +10596,35 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   title="attr-link-media">media</code> attribute is omitted, is
   <code>all</code>, meaning that by default links apply to all
   media.</p>
 
   <p>The <dfn title="attr-link-hreflang"><code>hreflang</code></dfn>
   attribute on the <code>link</code> element has the same semantics as
   the <span title="attr-hyperlink-hreflang"><code>hreflang</code>
   attribute on hyperlink elements</span>.</p>
 
   <p>The <dfn title="attr-link-type"><code>type</code></dfn> attribute
-  gives the MIME type of the linked resource. It is purely advisory.
-  The value must be a valid MIME type, optionally with parameters. <a
-  href="#refsRFC2046">[RFC2046]</a></p>
+  gives the <span>MIME type</span> of the linked resource. It is purely advisory.
+  The value must be a <span>valid MIME type</span>, optionally with
+  parameters.</p>
 
   <p>For <span title="external resource link">external resource
   links</span>, the <code title="attr-link-type">type</code> attribute
   is used as a hint to user agents so that they can avoid fetching
   resources they do not support. <span class="impl">If the attribute
   is present, then the user agent must assume that the resource is of
   the given type. If the attribute is omitted, but the external
   resource link type has a default type defined, then the user agent
   must assume that the resource is of that type. If the UA does not
-  support the given MIME type for the given link relationship, then
+  support the given <span>MIME type</span> for the given link relationship, then
   the UA should not fetch the resource; if the UA does support the
-  given MIME type for the given link relationship, then the UA should
+  given <span>MIME type</span> for the given link relationship, then the UA should
   <span>fetch</span> the resource. If the attribute is omitted, and
   the external resource link type does not have a default type
   defined, but the user agent would fetch the resource if the type was
   known and supported, then the user agent should <span>fetch</span>
   the resource under the assumption that it will be
   supported.</span></p>
 
   <div class="impl">
 
   <p>User agents must not consider the <code
@@ -10661,21 +10665,21 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   <div class="example">
 
    <p>If a document contains style sheet links labeled as follows:</p>
 
    <pre>&lt;link rel="stylesheet" href="A" type="text/plain"&gt;
 &lt;link rel="stylesheet" href="B" type="text/css"&gt;
 &lt;link rel="stylesheet" href="C"&gt;</pre>
 
    <p>...then a compliant UA that supported only CSS style sheets
    would fetch the B and C files, and skip the A file (since
-   <code>text/plain</code> is not the MIME type for CSS style
+   <code>text/plain</code> is not the <span>MIME type</span> for CSS style
    sheets).</p>
 
    <p>For files B and C, it would then check the actual types returned
    by the server. For those that are sent as <code>text/css</code>, it
    would apply the styles, but for those labeled as
    <code>text/plain</code>, or any other type, it would not.</p>
 
    <p>If one the two files was returned without a
    <span>Content-Type</span> metadata, or with a syntactically
    incorrect type like <code
@@ -11151,22 +11155,22 @@ people expect to have work and what is necessary.
 
     </ol>
 
     </div>
 
     <p>For <code>meta</code> elements with an <code
     title="attr-meta-http-equiv">http-equiv</code> attribute in the
     <span title="attr-meta-http-equiv-content-language">Content
     Language state</span>, the <code
     title="attr-meta-content">content</code> attribute must have a
-    value consisting of a valid RFC 3066 language code. <a
-    href="#refsRFC3066">[RFC3066]</a></p>
+    value consisting of a valid BCP 47 language code. <a
+    href="#refsBCP47">[BCP47]</a></p>
 
     <p class="note">This pragma is not exactly equivalent to the HTTP
     <code>Content-Language</code> header, for instance it only
     supports one language. <a href="#refsHTTP">[HTTP]</a></p>
 
    </dd>
 
    <dt><dfn title="attr-meta-http-equiv-content-type">Encoding declaration state</dfn> (<code title="">http-equiv="content-type"</code>)
 
    <dd>
@@ -11537,21 +11541,21 @@ people expect to have work and what is necessary.
   ISO-2022<!-- http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422
   -->, and encodings based on EBCDIC. Authors should not use
   UTF-32. Authors must not use the CESU-8, UTF-7, BOCU-1 and SCSU
   encodings.
   <a href="#refsRFC1345">[RFC1345]</a><!-- for the JIS types -->
   <a href="#refsRFC1468">[RFC1468]</a><!-- ISO-2022-JP -->
   <a href="#refsRFC2237">[RFC2237]</a><!-- ISO-2022-JP-1 -->
   <a href="#refsRFC1554">[RFC1554]</a><!-- ISO-2022-JP-2 -->
   <a href="#refsRFC1922">[RFC1922]</a><!-- ISO-2022-CN and ISO-2022-CN-EXT -->
   <a href="#refsRFC1557">[RFC1557]</a><!-- ISO-2022-KR -->
-  <a href="#refsUTF32">[UTF32]</a>
+  <a href="#refsUNICODE">[UNICODE]</a>
   <a href="#refsCESU8">[CESU8]</a>
   <a href="#refsUTF7">[UTF7]</a>
   <a href="#refsBOCU1">[BOCU1]</a>
   <a href="#refsSCSU">[SCSU]</a>
   <!-- no idea what to reference for EBCDIC, so... -->
   </p>
 
   <p>Authors are encouraged to use UTF-8. Conformance checkers may
   advise against authors using legacy encodings.</p>
 
@@ -11600,25 +11604,24 @@ people expect to have work and what is necessary.
    </dd>
   </dl>
 
   <p>The <code>style</code> element allows authors to embed style
   information in their documents. The <code>style</code> element is
   one of several inputs to the <span>styling processing
   model</span>. The element does not <span
   title="represents">represent</span> content for the user.</p>
 
   <p>If the <dfn title="attr-style-type"><code>type</code></dfn>
-  attribute is given, it must contain a valid MIME type, optionally
-  with parameters, that designates a styling language. <a
-  href="#refsRFC2046">[RFC2046]</a> If the attribute is absent, the
-  type defaults to <code>text/css</code>. <a
-  href="#refsRFC2318">[RFC2138]</a></p>
+  attribute is given, it must contain a <span>valid MIME type</span>,
+  optionally with parameters, that designates a styling language. If
+  the attribute is absent, the type defaults to
+  <code>text/css</code>. <a href="#refsRFC2318">[RFC2318]</a></p>
 
   <div class="impl">
 
   <!-- this paragraph is also present in the <script> section -->
   <p>When examining types to determine if they support the language,
   user agents must not ignore unknown MIME parameters &mdash; types
   with unknown parameters must be assumed to be unsupported.</p>
 
   </div>
 
@@ -11933,25 +11936,25 @@ people expect to have work and what is necessary.
   language.</p>
 
   <p>When used to include data blocks, the data must be embedded
   inline, the format of the data must be given using the <code
   title="attr-script-type">type</code> attribute, and the <code
   title="attr-script-src">src</code> attribute must not be
   specified.</p>
 
   <p>The <dfn title="attr-script-type"><code>type</code></dfn>
   attribute gives the language of the script or format of the data. If
-  the attribute is present, its value must be a valid MIME type,
-  optionally with parameters. The <code title="">charset</code>
-  parameter must not be specified. (The default, which is used if the
-  attribute is absent, is "<code title="">text/javascript</code>".) <a
-  href="#refsRFC2046">[RFC2046]</a></p>
+  the attribute is present, its value must be a <span>valid MIME
+  type</span>, optionally with parameters. The <code
+  title="">charset</code> parameter must not be specified. (The
+  default, which is used if the attribute is absent, is "<code
+  title="">text/javascript</code>".)</p>
 
   <p>The <dfn title="attr-script-src"><code>src</code></dfn>
   attribute, if specified, gives the address of the external script
   resource to use. The value of the attribute must be a <span>valid
   URL</span> identifying a script resource of the type given by the
   <code title="attr-script-type">type</code> attribute, if the
   attribute is present, or of the type "<code
   title="">text/javascript</code>", if the attribute is absent.</p>
 
   <p>The <dfn title="attr-script-charset"><code>charset</code></dfn>
@@ -12593,27 +12596,27 @@ o............A....e
   execute at all.</p>
 
 
 
 
   <h5 id="scriptingLanguages">Scripting languages</h5>
 
   <div class="impl">
 
   <p>A user agent is said to <dfn>support the scripting language</dfn>
-  if <var>the script block's type</var> matches the MIME type of a
+  if <var>the script block's type</var> matches the <span>MIME type</span> of a
   scripting language that the user agent implements.</p>
 
   </div>
 
-  <p>The following lists some MIME types and the languages to which
-  they refer:</p>
+  <p>The following lists some <span title="MIME type">MIME
+  types</span> and the languages to which they refer:</p>
 
   <dl>
 
    <dt><code>application/ecmascript</code></dt>
    <dt><code>application/javascript</code></dt>
    <dt><code>application/x-ecmascript</code></dt>
    <dt><code>application/x-javascript</code></dt>
    <dt><code>text/ecmascript</code></dt>
    <dt><code>text/javascript</code></dt>
    <dt><code>text/javascript1.0</code></dt>
@@ -12628,21 +12631,22 @@ o............A....e
    <dt><code>text/x-javascript</code></dt>
    <dd>JavaScript. <a href="#refsECMA262">[ECMA262]</a></dd>
 
    <dt><code>text/javascript;e4x=1</code></dt>
    <dd>JavaScript with ECMAScript for XML. <a href="#refsECMA357">[ECMA357]</a></dd>
 
   </dl>
 
   <div class="impl">
 
-  <p>User agents may support other MIME types and other languages.</p>
+  <p>User agents may support other <span title="MIME type">MIME
+  types</span> and other languages.</p>
 
   <!-- this paragraph is also present in the <style> section -->
   <p>When examining types to determine if they support the language,
   user agents must not ignore unknown MIME parameters &mdash; types
   with unknown parameters must be assumed to be unsupported.</p>
 
   </div>
 
 
   <h5><dfn title="script documentation">Inline documentation for external scripts</dfn></h5>
@@ -20461,29 +20465,29 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
 
   <p>The <code>embed</code> element <span>represents</span> an
   integration point for an external (typically non-HTML) application
   or interactive content.</p>
 
   <p>The <dfn title="attr-embed-src"><code>src</code></dfn> attribute
   gives the address of the resource being embedded. The attribute, if
   present, must contain a <span>valid URL</span>.</p>
 
   <p>The <dfn title="attr-embed-type"><code>type</code></dfn>
-  attribute, if present, gives the MIME type of the plugin to
-  instantiate. The value must be a valid MIME type, optionally with
-  parameters. If both the <code title="attr-embed-type">type</code>
-  attribute and the <code title="attr-embed-src">src</code> attribute
-  are present, then the <code title="attr-embed-type">type</code>
-  attribute must specify the same type as the <span
-  title="Content-Type">explicit Content-Type metadata</span> of the
-  resource given by the <code title="attr-embed-src">src</code>
-  attribute. <a href="#refsRFC2046">[RFC2046]</a></p>
+  attribute, if present, gives the <span>MIME type</span> of the plugin to
+  instantiate. The value must be a <span>valid MIME type</span>,
+  optionally with parameters. If both the <code
+  title="attr-embed-type">type</code> attribute and the <code
+  title="attr-embed-src">src</code> attribute are present, then the
+  <code title="attr-embed-type">type</code> attribute must specify the
+  same type as the <span title="Content-Type">explicit Content-Type
+  metadata</span> of the resource given by the <code
+  title="attr-embed-src">src</code> attribute.</p>
 
   <div class="impl">
 
   <p>When the element is created with neither a <code
   title="attr-embed-src">src</code> attribute nor a <code
   title="attr-embed-type">type</code> attribute, and when attributes
   are removed such that neither attribute is present on the element
   anymore, and when the element has a <span>media element</span>
   ancestor, and when the element has an ancestor <code>object</code>
   element that is <em>not</em> showing its <span>fallback
@@ -20697,22 +20701,22 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
   be treated as an image, as a <span>nested browsing context</span>,
   or as an external resource to be processed by a
   <span>plugin</span>.</p>
 
   <p>The <dfn title="attr-object-data"><code>data</code></dfn>
   attribute, if present, specifies the address of the resource. If
   present, the attribute must be a <span>valid URL</span>.</p>
 
   <p>The <dfn title="attr-object-type"><code>type</code></dfn>
   attribute, if present, specifies the type of the resource. If
-  present, the attribute must be a valid MIME type, optionally with
-  parameters. <a href="#refsRFC2046">[RFC2046]</a></p>
+  present, the attribute must be a <span>valid MIME type</span>,
+  optionally with parameters.</p>
 
   <p>One or both of the <code title="attr-object-data">data</code> and
   <code title="attr-object-type">type</code> attributes must be
   present.</p>
 
   <p>The <dfn title="attr-object-name"><code>name</code></dfn>
   attribute, if present, must be a <span>valid browsing context
   name</span>. The given value is used to name the <span>nested
   browsing context</span>, if applicable.</p>
 
@@ -21670,23 +21674,23 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
   title="represents">represent</span> anything on its own.</p>
 
   <p>The <dfn title="attr-source-src"><code>src</code></dfn> attribute
   gives the address of the <span>media resource</span>. The value must
   be a <span>valid URL</span>. This attribute must be present.</p>
 
   <p>The <dfn title="attr-source-type"><code>type</code></dfn>
   attribute gives the type of the <span>media resource</span>, to help
   the user agent determine if it can play this <span>media
   resource</span> before fetching it. If specified, its value must be
-  a MIME type. The <code title="">codecs</code> parameter may be
-  specified and might be necessary to specify exactly how the resource
-  is encoded. <a href="#refsRFC2046">[RFC2046]</a> <a
+  a <span>valid MIME type</span>. The <code title="">codecs</code>
+  parameter may be specified and might be necessary to specify exactly
+  how the resource is encoded. <a
   href="#refsRFC4281">[RFC4281]</a></p>
 
   <div class="example">
 
    <p>The following list shows some examples of how to use the <code
    title="">codecs=</code> MIME parameter in the <code
    title="attr-source-type">type</code> attribute.</p>
 
    <dl>
 
@@ -22081,41 +22085,40 @@ interface <dfn>CueRangeCallback</dfn> {
   <p class="note">There are two ways to specify a <span>media
   resource</span>, the <code title="attr-media-src">src</code>
   attribute, or <code>source</code> elements. The attribute overrides
   the elements.</p>
 
 
 
   <h5>MIME types</h5>
 
   <p>A <span>media resource</span> can be described in terms of its
-  <em>type</em>, specifically a MIME type, optionally with a <code
-  title="">codecs</code> parameter. <a
-  href="#refsRFC2046">[RFC2046]</a> <a
+  <em>type</em>, specifically a <span>MIME type</span>, optionally
+  with a <code title="">codecs</code> parameter. <a
   href="#refsRFC4281">[RFC4281]</a>.</p>
 
   <p>Types are usually somewhat incomplete descriptions; for example
   "<code title="">video/mpeg</code>" doesn't say anything except what
   the container type is, and even a type like "<code
   title="">video/mp4; codecs=&quot;avc1.42E01E,
   mp4a.40.2&quot;</code>" doesn't include information like the actual
   bitrate (only the maximum bitrate). Thus, given a type, a user agent
   can often only know whether it <em>might</em> be able to play
   media of that type (with varying levels of confidence), or whether
   it definitely <em>cannot</em> play media of that type.</p>
 
   <p><dfn>A type that the user agent knows it cannot render</dfn> is
   one that describes a resource that the user agent definitely does
   not support, for example because it doesn't recognize the container
   type, or it doesn't support the listed codecs.</p>
 
-  <p>The MIME type "<code title="">application/octet-stream</code>" is
+  <p>The <span>MIME type</span> "<code title="">application/octet-stream</code>" is
   never <span>a type that the user agent knows it cannot
   render</span>. User agents must treat that type as equivalent to the
   lack of any explicit <span title="Content-Type">Content-Type
   metadata</span> when it is used to label a potential <span>media
   resource</span>.</p>
 
   <dl class="domintro">
 
    <dt><var title="">media</var> . <code title="dom-navigator-canPlayType">canPlayType</code>(<var title="">type</var>)</dt>
 
@@ -22567,21 +22570,21 @@ interface <dfn>CueRangeCallback</dfn> {
      changed.</p> <!-- i.e. changing xml:base or <base> after src=""
      has no effect -->
 
      <li><p>&#x231B; If <var title="">absolute URL</var> was not
      obtained successfully, then end the <span>synchronous
      section</span>, and jump down to the <i title="">failed</i> step
      below.</p></li>
 
      <li><p>&#x231B; If <var title="">candidate</var> has a <code
      title="attr-source-type">type</code> attribute whose value, when
-     parsed as a MIME type (including any codecs described by the
+     parsed as a <span>MIME type</span> (including any codecs described by the
      <code title="">codec</code> parameter), represents <span>a type
      that the user agent knows it cannot render</span>, then end the
      <span>synchronous section</span>, and jump down to the <i
      title="">failed</i> step below.</p></li>
 
      <li><p>&#x231B; If <var title="">candidate</var> has a <code
      title="attr-source-media">media</code> attribute whose value,
      when processed according to the rules for <a href="#mq">media
      queries</a>, does not match the current environment, then end the
      <span>synchronous section</span>, and jump down to the <i
@@ -22754,21 +22757,21 @@ interface <dfn>CueRangeCallback</dfn> {
     substeps from the following list:</p>
 
     <dl class="switch">
 
      <dt>If the <span>media data</span> cannot be fetched at all, due
      to network errors, causing the user agent to give up trying to
      fetch the resource</dt>
 
      <dt>If the <span>media resource</span> is found to have <span
      title="Content-Type">Content-Type metadata</span> that, when
-     parsed as a MIME type (including any codecs described by the
+     parsed as a <span>MIME type</span> (including any codecs described by the
      <code title="">codec</code> parameter), represents <span>a type
      that the user agent knows it cannot render</span> (even if the
      actual <span>media data</span> is in a supported format)</dt>
 
      <dt>If the <span>media data</span> can be fetched but is found by
      inspection to be in an unsupported format, or can otherwise not
      be rendered at all</dt>
 
      <dd>
 
@@ -24920,25 +24923,25 @@ interface <dfn>CueRangeCallback</dfn> {
   title="">data:</code> URL containing a representation of the image
   as a PNG file. <a href="#refsPNG">[PNG]</a>.</p>
 
   <p>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 "<code title="">data:,</code>". (This is the shortest <code
   title="">data:</code> URL; it represents the empty string in a <code
   title="">text/plain</code> resource.)</p>
 
   <p>When the <code title="dom-canvas-toDataURL">toDataURL(<var
-  title="">type</var>)</code> method, when called with one
-  <em>or more</em> arguments, must return a <code
-  title="">data:</code> URL containing a representation of the image
-  in the format given by <var title="">type</var>. The possible values
-  are MIME types with no parameters, for example
+  title="">type</var>)</code> method, when called with one <em>or
+  more</em> arguments, must return a <code title="">data:</code> URL
+  containing a representation of the image in the format given by <var
+  title="">type</var>. The possible values are <span title="MIME
+  type">MIME types</span> with no parameters, for example
   <code>image/png</code>, <code>image/jpeg</code>, or even maybe
   <code>image/svg+xml</code> if the implementation actually keeps
   enough information to reliably render an SVG image from the
   canvas.</p>
 
   <p>For image types that do not support an alpha channel, the image
   must be composited onto a solid black background using the
   source-over operator, and the resulting image must be the one used
   to create the <code title="">data:</code> URL.</p>
 
@@ -25573,24 +25576,20 @@ idea from Mihai:
 
   <p>These values are all case-sensitive &mdash; they must be used
   exactly as shown. User agents must not recognize values that are not
   a <span>case-sensitive</span> match for one of the values given
   above.</p>
 
   <p>The operators in the above list must be treated as described by
   the Porter-Duff operator given at the start of their description
   (e.g. <var title="">A</var> over <var title="">B</var>). <a
   href="#refsPORTERDUFF">[PORTERDUFF]</a></p>
-  <!--
-        <dd id="refsPORTERDUFF">[PORTERDUFF]</dd>
-        <dd><cite>Compositing Digital Images</cite>, SIGGRAPH '84: Proceedings of the 11th annual conference on Computer graphics and interactive techniques, Volume 18, Number 3, T. Porter, T Duff. ACM Press, July 1984. ISBN 0-89791-138-5.</dd>
-  -->
 
   <p>On setting, if the user agent does not recognize the specified
   value, it must be ignored, leaving the value of <code
   title="dom-context-2d-globalCompositeOperation">globalCompositeOperation</code>
   unaffected.</p>
 
   <p>When the context is created, the <code
   title="dom-context-2d-globalCompositeOperation">globalCompositeOperation</code>
   attribute must initially have the value
   <code>source-over</code>.</p>
@@ -26996,21 +26995,21 @@ notes on what would need to be defined for dashed lines:
   property-independent stylesheet syntax like 'inherit' or 'initial'),
   then it must be ignored, without assigning a new font value. <a
   href="#refsCSS">[CSS]</a></p>
 
   <p>Font names must be interpreted in the context of the
   <code>canvas</code> element's stylesheets; any fonts embedded using
   <code title="">@font-face</code> must therefore be available once
   they are loaded. (If a font is referenced before it is fully loaded,
   then it must be treated as if it was an unknown font, falling back
   to another as described by the relevant CSS specifications.) <a
-  href="#refsCSSWEBFONTS">[CSSWEBFONTS]</a></p>
+  href="#refsCSSFONTS">[CSSFONTS]</a></p>
 
   <p>Only vector fonts should be used by the user agent; if a user
   agent were to use bitmap fonts then transformations would likely
   make the font look very ugly.</p>
 
   <p>On getting, the <code title="dom-context-2d-font">font</code>
   attribute must return the <span title="serializing a CSS
   value">serialized form</span> of the current font of the context
   (with no 'line-height' component). <a
   href="#refsCSSOM">[CSSOM]</a></p>
@@ -27844,24 +27843,23 @@ v4DVT (also check for '- -' bits in the part above) -->
   title="dom-CanvasPixelArray-set">indexed to modify an indexed
   property</dfn> <var title="">index</var> with value <var
   title="">value</var>, the value of the <var title="">index</var>th
   component in the array must be set to <var title="">value</var>. JS
   <code>undefined</code> values must be converted to zero. Other
   values must first be converted to numbers using JavaScript's
   ToNumber algorithm, and if the result is a NaN value, then the value
   must be converted to zero. If the result is less than 0, it must be
   clamped to zero. If the result is more than 255, it must be clamped
   to 255. If the number is not an integer, it should be rounded to the
-  nearest integer using the IEEE 754r
-  <i>convertToIntegerTiesToEven</i> rounding mode. <a
-  href="#refsECMA262">[ECMA262]</a> <a
-  href="#refsIEEE754R">[IEEE754R]</a></p>
+  nearest integer using the IEEE 754 <i>convertToIntegerTiesToEven</i>
+  rounding mode. <a href="#refsECMA262">[ECMA262]</a> <a
+  href="#refsIEEE754">[IEEE754]</a></p>
 
   <p class="note">The width and height (<var title="">w</var> and <var
   title="">h</var>) might be different from the <var title="">sw</var>
   and <var title="">sh</var> arguments to the above methods, e.g. if
   the canvas is backed by a high-resolution bitmap, or if the <var
   title="">sw</var> and <var title="">sh</var> arguments are
   negative.</p>
 
   <p>The <dfn
   title="dom-context-2d-putImageData"><code>putImageData(<var
@@ -28891,29 +28889,20 @@ function AddCloud(data, x, y) { ... }</pre>
       image, for all integer values of <var title="">i</var> from 0 to
       <span>(<var title="">N</var>/2)-1</span>, where <var
       title="">N</var> is the number of items in <var
       title="">coords</var>.</p>
 
       <p>The shape is a polygon whose vertices are given by <var
       title="">the coordinates</var>, and whose interior is
       established using the even-odd rule. <a
       href="#refsGRAPHICS">[GRAPHICS]</a></p>
 
-      <!-- If anyone has this book ("Computer Graphics: Principles and
-           Practice in C"), please check page 34 or so and see if it
-           makes any references to literature in the bibliographic
-           section to define the "even-odd" rule for polygon filling
-           and hit testing.
-        <dd id="refsGRAPHICS">[GRAPHICS]</dd>
-        <dd>(Non-normative) <cite>Computer Graphics: Principles and Practice in C</cite>, Second Edition, J. Foley, A. van Dam, S. Feiner, J. Hughes. Addison-Wesley, July 1995. ISBN 0-201-84840-6.</dd>
-      -->
-
       <!--
         browsers implement the even-odd rule / even winding rule:
         http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E%0A%3Cimg%20usemap%3D%22%23x%22%20src%3D%22/resources/images/sample%22%3E%0A%3Cmap%20name%3D%22x%22%3E%0A%20%20%3Carea%20shape%3Dpolygon%20coords%3D%220%2C0%200%2C100%20100%2C100%20100%2C2%201%2C2%202%2C1%202%2C99%2099%2C99%2099%2C0%22%20href%3Da%3E%0A%3C/map%3E%0A
        -->
 
      </dd>
 
      <dt><span title="attr-area-shape-rect">Rectangle state</span></dt>
 
      <dd>
@@ -32732,21 +32721,21 @@ interface <dfn>HTMLFormElement</dfn> : <span>HTMLElement</span> {
      <td> A set of zero or more values from a predefined list
      <td> A checkbox
     <tr>
      <td> <dfn title="attr-input-type-radio-keyword"><code>radio</code></dfn>
      <td> <span title="attr-input-type-radio">Radio Button</span>
      <td> An enumerated value
      <td> A radio button
     <tr>
      <td> <dfn title="attr-input-type-file-keyword"><code>file</code></dfn>
      <td> <span title="attr-input-type-file">File Upload</span>
-     <td> Zero or more files each with a MIME type and optionally a file name
+     <td> Zero or more files each with a <span>MIME type</span> and optionally a file name
      <td> A label and a button
     <tr>
      <td> <dfn title="attr-input-type-submit-keyword"><code>submit</code></dfn>
      <td> <span title="attr-input-type-submit">Submit Button</span>
      <td> An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission
      <td> A button
     <tr>
      <td> <dfn title="attr-input-type-image-keyword"><code>image</code></dfn>
      <td> <span title="attr-input-type-image">Image Button</span>
      <td> A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission
@@ -36388,23 +36377,23 @@ interface <dfn>HTMLFormElement</dfn> : <span>HTMLElement</span> {
    <dd>Indicates that sound files are accepted.</dd>
 
    <dt>The string <code title="">video/*</code></dt>
 
    <dd>Indicates that video files are accepted.</dd>
 
    <dt>The string <code title="">image/*</code></dt>
 
    <dd>Indicates that image files are accepted.</dd>
 
-   <dt>A valid MIME type, with no parameters</dt>
+   <dt>A <span>valid MIME type</span>, with no parameters</dt>
 
-   <dd>Indicates that files of the specified type are accepted. <a href="#refsRFC2046">[RFC2046]</a></dd>
+   <dd>Indicates that files of the specified type are accepted.</dd>
 
   </dl>
 
   <p>The tokens must not be <span>ASCII case-insensitive</span>
   matches for any of the other tokens (i.e. duplicates are not
   allowed). <span class="impl">To obtain the list of tokens from the
   attribute, the user agent must <span title="split a string on
   commas">split the attribute value on commas</span>.</span></p>
 
   <div class="impl">
@@ -48119,21 +48108,21 @@ document.body.appendChild(outer);</pre>
    <dd>
 
     <p>Gives the telephone number of the person or organization.</p>
 
     <p>The <span title="concept-property-value">value</span> must be
     either text that can be interpreted as a telephone number as
     defined in the CCITT specifications E.163 and X.121, or an <span
     title="concept-item">item</span> with zero or more <code
     title="md-vcard-tel-type">type</code> properties and exactly one
     <code title="md-vcard-tel-value">value</code> property. <a
-    href="#refsE163">[E.163]</a> <a href="#X.121">[X.121]</a></p>
+    href="#refsE163">[E163]</a> <a href="#refsX121">[X121]</a></p>
 
     <p>If no <code title="md-vcard-tel-type">type</code> properties
     are present within an <span title="concept-item">item</span> that
     forms the <span title="concept-property-value">value</span> of a
     <code title="md-vcard-tel">tel</code> property of an <span
     title="concept-item">item</span> with the type <code
     title="md-vcard">vcard</code>, or if the <span
     title="concept-property-value">value</span> of such a <code
     title="md-vcard-tel">tel</code> property is text, then the <span
     title="telephone type strings">telephone type string</span> <code
@@ -48180,21 +48169,21 @@ document.body.appendChild(outer);</pre>
    <dt><dfn title="md-vcard-tel-value"><code>value</code></dfn> (inside <code title="md-vcard-tel">tel</code>)</dt>
 
    <dd>
 
     <p>Gives the actual telephone number of the person or
     organization.</p>
 
     <p>The <span title="concept-property-value">value</span> must be
     text that can be interpreted as a telephone number as defined in
     the CCITT specifications E.163 and X.121. <a
-    href="#refsE163">[E.163]</a> <a href="#X.121">[X.121]</a></p>
+    href="#refsE163">[E163]</a> <a href="#refsX121">[X121]</a></p>
 
     <p>Exactly one property with the name <code
     title="md-vcard-tel-value">value</code> must be present within the
     <span title="concept-item">item</span> that forms the <span
     title="concept-property-value">value</span> of a <code
     title="md-vcard-tel">tel</code> property of an <span
     title="concept-item">item</span> with the type <code
     title="md-vcard">vcard</code>.</p>
 
    </dd>
@@ -53583,22 +53572,21 @@ interface <dfn>Window</dfn> {
 
      </li>
 
      <li>
 
       <p>If <var title="">new value</var> matches a suffix in the
       Public Suffix List, or, if <var title="">new value</var>,
       prefixed by a U+002E FULL STOP ("."), matches the end of a
       suffix in the Public Suffix List, then throw a
       <code>SECURITY_ERR</code> exception and abort these steps. <a
-      href="#refsPSL">[PSL]</a></p> <!-- [PSL]
-      http://publicsuffix.org/ -->
+      href="#refsPSL">[PSL]</a></p>
 
       <p>Suffixes must be compared after applying the IDNA ToASCII
       algorithm to them, with both the AllowUnassigned and
       UseSTD3ASCIIRules flags set, in an <span>ASCII
       case-insensitive</span> manner. <a
       href="#refsRFC3490">[RFC3490]</a></p>
 
      </li>
 
     </ol>
@@ -54265,26 +54253,20 @@ interface <dfn>Window</dfn> {
   title="concept-js-deref">dereferenced</dfn>, the user agent must run
   the following steps:</p>
 
   <ol>
 
    <li><p>Let the script source be the string obtained using the
    content retrieval operation defined for <code
    title="">javascript:</code> URLs. <a
    href="#refsJSURL">[JSURL]</a></p></li>
 
-<!--
-JSURL: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.txt and
-       http://www.websitedev.de/ietf/draft-hoehrmann-javascript-scheme-00.txt should be as stable as it gets,
-       http://ietfreport.isoc.org/idref/draft-hoehrmann-javascript-scheme/ for the latest version
--->
-
    <li>
 
     <p>Use the appropriate step from the following list:</p>
 
     <dl>
 
      <dt>If a <span>browsing context</span> is being <span
      title="navigate">navigated</span> to a <code>javascript:</code>
      URL, and the <span>active document</span> of that browsing
      context has the <span>same origin</span> as the script given by
@@ -55857,21 +55839,21 @@ interface <dfn>NavigatorAbilities</dfn> {
   <p>The <dfn
   title="dom-navigator-registerProtocolHandler"><code>registerProtocolHandler()</code></dfn>
   method allows Web sites to register themselves as possible handlers
   for particular schemes. For example, an online fax service could
   register itself as a handler of the <code>fax:</code> scheme (<a
   href="#refsRFC2806">[RFC2806]</a>), so that if the user clicks on
   such a link, he is given the opportunity to use that Web
   site. Analogously, the <dfn
   title="dom-navigator-registerContentHandler"><code>registerContentHandler()</code></dfn>
   method allows Web sites to register themselves as possible handlers
-  for content in a particular MIME type. For example, the same online
+  for content in a particular <span>MIME type</span>. For example, the same online
   fax service could register itself as a handler for
   <code>image/g3fax</code> files (<a
   href="#refsRFC1494">[RFC1494]</a>), so that if the user has no
   native application capable of handling G3 Facsimile byte streams,
   his Web browser can instead suggest he use that site to view the
   image.</p>
 
   <dl class="domintro">
 
    <dt><var title="">window</var> . <code title="dom-navigator">navigator</code> . <code title="dom-navigator-registerProtocolHandler">registerProtocolHandler</code>(<var title="">scheme</var>, <var title="">url</var>, <var title="">title</var>)</dt>
@@ -55933,34 +55915,34 @@ interface <dfn>NavigatorAbilities</dfn> {
 
     <p class="note">This feature is not intended to be used with
     non-standard protocols.</p>
 
    </dd>
 
    <dt><var title="">mimeType</var> (<code title="dom-navigator-registerContentHandler">registerContentHandler()</code> only)</dt>
 
    <dd>
 
-    <p>A MIME type, such as <code>model/vrml</code> or
-    <code>text/richtext</code>. The MIME type must be compared in an
-    <span>ASCII case-insensitive</span> manner by user agents for the
-    purposes of comparing with MIME types of documents that they
-    consider against the list of registered handlers.</p>
+    <p>A <span>MIME type</span>, such as <code>model/vrml</code> or
+    <code>text/richtext</code>. The <span>MIME type</span> must be
+    compared in an <span>ASCII case-insensitive</span> manner by user
+    agents for the purposes of comparing with MIME types of documents
+    that they consider against the list of registered handlers.</p>
 
     <p>User agents must compare the given values only to the MIME
     type/subtype parts of content types, not to the complete type
     including parameters. Thus, if <var title="">mimeType</var> values
     passed to this method include characters such as commas or
     whitespace, or include MIME parameters, then the handler being
     registered will never be used.</p>
 
-    <p class="note">The type is compared to the MIME type used by the
+    <p class="note">The type is compared to the <span>MIME type</span> used by the
     user agent <em>after</em> the sniffing algorithms have been
     applied.</p>
 
    </dd>
 
 
    <dt><var title="">url</var></dt>
 
    <dd>
 
@@ -55997,21 +55979,21 @@ interface <dfn>NavigatorAbilities</dfn> {
 
      <pre>navigator.registerContentHandler('application/x-soup', 'soup?url=%s', 'SoupWeb&trade;')</pre>
 
      <p>...and then, much later, while visiting <code
      title="">http://www.example.net/</code>, clicked on a link such
      as:</p>
 
      <pre>&lt;a href="chickenk&#xEF;wi.soup">Download our Chicken K&#xEF;wi soup!&lt;/a></pre>
 
      <p>...then, assuming this <code>chickenk&#xEF;wi.soup</code> file
-     was served with the MIME type <code>application/x-soup</code>,
+     was served with the <span>MIME type</span> <code>application/x-soup</code>,
      the UA might navigate to the following URL:</p>
 
      <pre>http://example.com/soup?url=http://www.example.net/chickenk%C3%AFwi.soup</pre>
 
      <p>This site could then fetch the <code>chickenk&#xEF;wi.soup</code>
      file and do whatever it is that it does with soup (synthesize it
      and ship it to the user, or whatever).</p>
 
     </div>
 
@@ -56196,21 +56178,21 @@ interface <dfn>NavigatorAbilities</dfn> {
   method as its first argument (<var title="">mimeType</var>),
   "http://kittens.example.org/?show=%s" was the second argument (<var
   title="">url</var>), and "Kittens-at-work displayer" was the third
   argument (<var title="">title</var>).</p>
 
   <p>If the user clicks the Cancel button, then nothing further
   happens. If the user clicks the "Trust" button, then the handler is
   remembered.</p>
 
   <p>When the user then attempts to fetch a URL that uses the
-  "application/x-meowmeow" MIME type, then it might display a dialog
+  "application/x-meowmeow" <span>MIME type</span>, then it might display a dialog
   as follows:</p>
 
   <pre>||[ Unknown File Type ]|||||||||||||||||||||||||||||||||||||||
 |                                                            |
 | You have attempted to access:                              |
 |                                                            |
 |    data:application/x-meowmeow;base64,S2l0dGVucyBhcmUgd    |
 |    GhlIGN1dGVzdCE%3D                                       |
 |                                                            |
 | How would you like FerretBrowser to handle this resource?  |
@@ -56646,33 +56628,33 @@ NETWORK:
 comm.cgi
 
 # here is another set of files to cache, this time just the CSS file.
 CACHE:
 style/default.css</pre>
 
 
   <h5>Writing cache manifests</h5>
 
   <p>Manifests must be served using the
-  <code>text/cache-manifest</code> MIME type. All resources served
-  using the <code>text/cache-manifest</code> MIME type must follow the
+  <code>text/cache-manifest</code> <span>MIME type</span>. All resources served
+  using the <code>text/cache-manifest</code> <span>MIME type</span> must follow the
   syntax of application cache manifests, as described in this
   section.</p>
 
   <p>An application cache manifest is a text file, whose text is
   encoded using UTF-8. Data in application cache manifests is
   line-based. Newlines must be represented by U+000A LINE FEED (LF)
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.</p>
 
   <p class="note">This is a <span title="willful violation">willful
-  double violation</span> of RFC2046, which requires all <code
+  double violation</span> of RFC 2046, which requires all <code
   title="">text/*</code> types to support an open-ended set of
   character encodings and only allows CRLF line breaks. These
   requirements, however, are outdated; UTF-8 is now widely used, such
   that supporting other encodings is no longer necessary, and use of
   CR, LF, and CRLF line breaks is commonly supported and indeed
   sometimes CRLF is <em>not</em> supported by text editors. <a
   href="#refsRFC2046">[RFC2046]</a></p> <!-- also RFC 2045 for charset
   -->
 
   <p>The first line of an application cache manifest must consist of
@@ -57231,21 +57213,21 @@ style/default.css</pre>
    should be the display of some sort of user interface indicating to
    the user that the user agent is checking for the availability of
    updates.</p></li>
 
    <li>
 
     <p><i>Fetching the manifest</i>: <span>Fetch</span> the resource
     from <var title="">manifest URL</var>, and let <var
     title="">manifest</var> be that resource.</p>
 
-    <p>If the resource is labeled with the MIME type
+    <p>If the resource is labeled with the <span>MIME type</span>
     <code>text/cache-manifest</code>, parse <var
     title="">manifest</var> according to the <span title="parse a
     manifest">rules for parsing manifests</span>, obtaining a list of
     <span title="concept-appcache-explicit">explicit entries</span>,
     <span title="concept-appcache-fallback">fallback entries</span>
     and the <span title="concept-appcache-fallback-ns">fallback
     namespaces</span> that map to them, entries for the <span
     title="concept-appcache-onlinewhitelist">online whitelist</span>,
     and a value for the <span
     title="concept-appcache-onlinewhitelist-wildcard">online whitelist
@@ -57311,21 +57293,21 @@ style/default.css</pre>
    </li>
 
    <li>
 
     <p>Otherwise, if <i>fetching the manifest</i> fails in some other
     way (e.g. the server returns another 4xx or 5xx response <span
     title="concept-http-equivalent-codes">or equivalent</span>, or
     there is a DNS error, or the connection times out, or the user
     cancels the download, or the parser for manifests fails when
     checking the magic signature), or if the server returned a
-    redirect, or if the resource is labeled with a MIME type other
+    redirect, or if the resource is labeled with a <span>MIME type</span> other
     than <code>text/cache-manifest</code>, then run the <span>cache
     failure steps</span>.</p>
 
    </li>
 
    <li>
 
     <p>If this is an <span title="concept-appcache-upgrade">upgrade
     attempt</span> and the newly downloaded <var
     title="">manifest</var> is byte-for-byte identical to the manifest
@@ -59857,26 +59839,26 @@ style/default.css</pre>
   <p>When the user agent is required to <dfn>scroll to the fragment
   identifier</dfn>, it must change the scrolling position of the
   document, or perform some other action, such that <span>the
   indicated part of the document</span> is brought to the user's
   attention. If there is no indicated part, then the user agent must
   not scroll anywhere.</p>
 
   <p><dfn>The indicated part of the document</dfn> is the one that the
   fragment identifier, if any, identifies. The semantics of the
   fragment identifier in terms of mapping it to a specific DOM Node is
-  defined by the MIME type specification of the document's MIME Type
-  (for example, the processing of fragment identifiers for <span
-  title="XML MIME type">XML MIME types</span> is the responsibility of
-  RFC3023).</p>
+  defined by the specification that defines the <span>MIME type</span>
+  used by the <code>Document</code> (for example, the processing of
+  fragment identifiers for <span title="XML MIME type">XML MIME
+  types</span> is the responsibility of RFC3023).</p>
 
-  <p>For HTML documents (and the <code>text/html</code> MIME type),
+  <p>For HTML documents (and the <code>text/html</code> <span>MIME type</span>),
   the following processing model must be followed to determine what
   <span>the indicated part of the document</span> is.</p>
 
   <ol>
 
    <li><p><span title="parse a url">Parse</span> the <span>URL</span>,
    and let <var title="">fragid</var> be the <span
    title="url-fragment">&lt;fragment&gt;</span> component of the
    URL.</p></li><!-- parsing can't fail, since we checked earlier on
    when navigating -->
@@ -61930,36 +61912,36 @@ interface <dfn>SQLTransactionSync</dfn> {
   attribute describes for which media the target document was
   designed. It is purely advisory. The value must be a valid <a
   href="#mq">media query</a>. <a href="#refsMQ">[MQ]</a> The default,
   if the <code title="attr-hyperlink-media">media</code> attribute is
   omitted, is <code>all</code>.</p>
 
   <p>The <dfn
   title="attr-hyperlink-hreflang"><code>hreflang</code></dfn>
   attribute on hyperlink elements, if present, gives the language of
   the linked resource. It is purely advisory. The value must be a
-  valid RFC 3066 language code. <a href="#refsRFC3066">[RFC3066]</a>
+  valid BCP 47 language code. <a href="#refsBCP47">[BCP47]</a>
   <span class="impl">User agents must not consider this attribute
   authoritative &mdash; upon fetching the resource, user agents must
   use only language information associated with the resource to
   determine its language, not metadata included in the link to the
   resource.</span></p>
 
   <p>The <dfn title="attr-hyperlink-type"><code>type</code></dfn>
-  attribute, if present, gives the MIME type of the linked
-  resource. It is purely advisory. The value must be a valid MIME
-  type, optionally with parameters. <a
-  href="#refsRFC2046">[RFC2046]</a> <span class="impl">User agents
-  must not consider the <code title="attr-hyperlink-type">type</code>
-  attribute authoritative &mdash; upon fetching the resource, user
-  agents must not use metadata included in the link to the resource to
-  determine its type.</span></p>
+  attribute, if present, gives the <span>MIME type</span> of the linked
+  resource. It is purely advisory. The value must be a <span>valid
+  MIME type</span>, optionally with parameters. <span
+  class="impl">User agents must not consider the <code
+  title="attr-hyperlink-type">type</code> attribute authoritative
+  &mdash; upon fetching the resource, user agents must not use
+  metadata included in the link to the resource to determine its
+  type.</span></p>
 
 
   <div class="impl">
 
   <h4><dfn>Following hyperlinks</dfn></h4>
 
   <p>When a user <em>follows a hyperlink</em>, the user agent must
   <span title="resolve a url">resolve</span> the <span>URL</span>
   given by the <code title="attr-hyperlink-href">href</code> attribute
   of that hyperlink, relative to the hyperlink element, and if that is
@@ -62039,21 +62021,21 @@ interface <dfn>SQLTransactionSync</dfn> {
   <p>User agents should allow the user to adjust this behavior, for
   example in conjunction with a setting that disables the sending of
   HTTP <code title="http-referer">Referer</code> (sic) headers. Based
   on the user's preferences, UAs may either <span>ignore</span> the
   <code title="attr-hyperlink-ping">ping</code> attribute altogether,
   or selectively ignore URLs in the list (e.g. ignoring any
   third-party URLs).</p>
 
   <p>For URLs that are HTTP URLs, the requests must be performed by
   <span title="fetch">fetching</span> the specified URLs using the
-  POST method, with an entity body with the MIME type <code
+  POST method, with an entity body with the <span>MIME type</span> <code
   title="">text/ping</code> consisting of the four-character string
   "<code title="">PING</code>". All relevant cookie and HTTP
   authentication headers must be included in the request. Which other
   headers are required depends on the URLs involved.</p>
 
   <dl class="switch">
 
    <dt>If both the <span title="the document's address">address</span>
    of the <code>Document</code> object containing the hyperlink being
    audited and the ping URL have the <span>same origin</span></dt>
@@ -65507,25 +65489,25 @@ interface <dfn>SQLTransactionSync</dfn> {
   void <span title="dom-DataTransfer-clearData">clearData</span>(optional in DOMString format);
   void <span title="dom-DataTransfer-setData">setData</span>(in DOMString format, in DOMString data);
   DOMString <span title="dom-DataTransfer-getData">getData</span>(in DOMString format);
   readonly attribute <span>FileList</span> <span title="dom-DataTransfer-files">files</span>;
 
   void <span title="dom-DataTransfer-setDragImage">setDragImage</span>(in Element image, in long x, in long y);
   void <span title="dom-DataTransfer-addElement">addElement</span>(in Element element);
 };</pre>
 
   <p><code>DataTransfer</code> objects can hold pieces of data, each
-  associated with a unique format. Formats are generally given by MIME
-  types, with some values special-cased for legacy reasons. For the
-  purposes of this API, however, the format strings are opaque,
-  <span>case-sensitive</span>, strings, and the empty string is a
-  valid format string.</p>
+  associated with a unique format. Formats are generally given by
+  <span title="MIME type">MIME types</span>, with some values
+  special-cased for legacy reasons. For the purposes of this API,
+  however, the format strings are opaque, <span>case-sensitive</span>,
+  strings, and the empty string is a valid format string.</p>
 
   <dl class="domintro">
 
    <dt><var title="">dataTransfer</var> . <code title="dom-DataTransfer-dropEffect">dropEffect</code> [ = <var title="">value</var> ]</dt>
 
    <dd>
 
     <p>Returns the kind of operation that is currently selected. If
     the kind of operation isn't one of those that is allowed by the
     <code title="dom-DataTransfer-effectAllowed">effectAllowed</code>
@@ -69686,37 +69668,37 @@ interface <dfn>EventSource</dfn> {
 
   <p>As data is received, the <span title="concept-task">tasks</span>
   queued by the <span>networking task source</span> to handle the data
   must act as follows.</p>
 
   <p>HTTP 200 OK responses with a <span>Content-Type</span> header
   specifying the type <code>text/event-stream</code> must be processed
   line by line <a href="#event-stream-interpretation">as described
   below</a>.</p>
 
-  <p>When a successful response with a supported MIME type is
+  <p>When a successful response with a supported <span>MIME type</span> is
   received, such that the user agent begins parsing the contents of
   the stream, the user agent must <span>announce the
   connection</span>.</p>
 
-  <p>If such a resource (with the correct MIME type) completes loading
+  <p>If such a resource (with the correct <span>MIME type</span>) completes loading
   (i.e. the entire HTTP response body is received or the connection
   itself closes), the user agent must <span>reset the
   connection</span>. This doesn't apply for the error cases that are
   listed below.</p>
 
   <p>HTTP 200 OK responses that have a <span>Content-Type</span> other
   than <code>text/event-stream</code> (or some other supported type)
   must cause the user agent to <span>fail the connection</span>.</p>
 
   <p>HTTP 204 No Content, and 205 Reset Content responses are
-  equivalent to 200 OK responses with the right MIME type but no
+  equivalent to 200 OK responses with the right <span>MIME type</span> but no
   content, and thus must <span>reset the connection</span>.</p>
 
   <p>Other HTTP response codes in the 2xx range <!--201 Created, 202
   Accepted, 203 Non-Authoritative Information, and 206 Partial
   Content-->must similarly <span>reset the connection</span>. They
   are, however, likely to indicate an error has occurred somewhere and
   may cause the user agent to emit a warning.</p>
 
   <p>HTTP 301 Moved Permanently responses must cause the user agent to
   reconnect using the new server specified URL instead of the
@@ -69784,21 +69766,21 @@ interface <dfn>EventSource</dfn> {
   <hr>
 
   <p>The <span>task source</span> for any <span
   title="concept-task">tasks</span> that are <span title="queue a
   task">queued</span> by <code>EventSource</code> objects is the
   <dfn>remote event task source</dfn>.</p>
 
 
   <h4>Parsing an event stream</h4>
 
-  <p>This event stream format's MIME type is
+  <p>This event stream format's <span>MIME type</span> is
   <code>text/event-stream</code>.</p>
 
   <p>The event stream format is as described by the <code
   title="">stream</code> production of the following ABNF, the
   character set for which is Unicode. <a
   href="#refsABNF">[ABNF]</a></p>
 
   <pre>stream        = [ bom ] *event
 event         = *( comment / field ) end-of-line
 comment       = colon *any-char end-of-line
@@ -74160,23 +74142,21 @@ interface <dfn>MessagePort</dfn> {
    visited, then return that encoding, with the <span
    title="concept-encoding-confidence">confidence</span>
    <i>tentative</i>, and abort these steps.</p></li>
 
    <li><p>The user agent may attempt to autodetect the character
    encoding from applying frequency analysis or other algorithms to
    the data stream. If autodetection succeeds in determining a
    character encoding, then return that encoding, with the <span
    title="concept-encoding-confidence">confidence</span>
    <i>tentative</i>, and abort these steps. <a
-   href="#refsUNIVCHARDET">[UNIVCHARDET]</a></p></li> <!--
-   http://www.mozilla.org/projects/intl/UniversalCharsetDetection.html
-   -->
+   href="#refsUNIVCHARDET">[UNIVCHARDET]</a></p></li>
 
    <li><p>Otherwise, return an implementation-defined or
    user-specified default character encoding, with the <span
    title="concept-encoding-confidence">confidence</span>
    <i>tentative</i>. In non-legacy environments, the more
    comprehensive <code title="">UTF-8</code> encoding is
    recommended. Due to its use in legacy content, <code
    title="">windows-1252</code> is recommended as a default in
    predominantly Western demographics instead. Since these encodings
    can in many cases be distinguished by inspection, a user agent may
@@ -84312,21 +84292,21 @@ time:empty { binding: <i title="">time</i>; }</pre>
    <dd><p>Use an explicit <code>form</code> and <span title="attr-input-type-text">text field</span> combination instead.</p></dd>
 
    <dt><dfn><code>listing</code></dfn><dt>
    <dt><dfn><code>xmp</code></dfn><dt>
    <dd><p>Use <code>pre</code> and <code>code</code> instead.</p></dd>
 
    <dt><dfn><code>noembed</code></dfn></dt>
    <dd><p>Use <code>object</code> instead of <code>embed</code> when fallback is necessary.</p></dd>
 
    <dt><dfn><code>plaintext</code></dfn><dt>
-   <dd><p>Use the "<code>text/plain</code>" MIME type instead.</p></dd>
+   <dd><p>Use the "<code>text/plain</code>" <span>MIME type</span> instead.</p></dd>
 
    <dt><dfn><code>basefont</code></dfn></dt>
    <dt><dfn><code>big</code></dfn></dt>
    <dt><dfn><code>blink</code></dfn></dt>
    <dt><dfn><code>center</code></dfn></dt>
    <dt><dfn><code>font</code></dfn></dt>
    <dt><code>marquee</code></dt>
    <dt><dfn><code>s</code></dfn></dt>
    <dt><dfn><code>spacer</code></dfn></dt>
    <dt><dfn><code>strike</code></dfn></dt>
@@ -85965,21 +85945,21 @@ interface <span>HTMLDocument</span> {
     Web browsers, tools for processing Web content, HTML authoring
     tools, search engines, validators.
    </dd>
    <dt>Additional information:</dt>
    <dd>
     <dl>
      <dt>Magic number(s):</dt>
      <dd>No sequence of bytes can uniquely identify an HTML
      document. More information on detecting HTML documents is
      available in the Content-Type Processing Model specification. <a
-     href="#MIMESNIFF">[MIMESNIFF]</a></dd>
+     href="#refsMIMESNIFF">[MIMESNIFF]</a></dd>
      <dt>File extension(s):</dt>
      <dd>"<code title="">html</code>" and "<code title="">htm</code>"
      are commonly, but certainly not exclusively, used as the
      extension for HTML documents.</dd>
      <dt>Macintosh file type code(s):</dt>
      <dd><code title="">TEXT</code></dd>
     </dl>
    </dd>
    <dt>Person &amp; email address to contact for further information:</dt>
    <dd>Ian Hickson &lt;ian@hixie.ch></dd>
@@ -86024,21 +86004,21 @@ interface <span>HTMLDocument</span> {
    <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
    <dt>Interoperability considerations:</dt>
    <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
    <dt>Published specification:</dt>
    <dd>
     Labeling a resource with the <code>application/xhtml+xml</code>
     type asserts that the resource is an XML document that likely has
     a root element from the <span>HTML namespace</span>. As such, the
     relevant specifications are the XML specification, the Namespaces
     in XML specification, and this specification. <a
-    href="#refsXML">[XML]</a> <a href="#refsXMLNAMES">[XMLNAMES]</a>
+    href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a>
    </dd>
    <dt>Applications that use this media type:</dt>
    <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
    <dt>Additional information:</dt>
    <dd>
     <dl>
      <dt>Magic number(s):</dt>
      <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
      <dt>File extension(s):</dt>
      <dd>"<code title="">xhtml</code>" and "<code title="">xht</code>"
@@ -86054,22 +86034,22 @@ interface <span>HTMLDocument</span> {
    <dd>Common</dd>
    <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>W3C and WHATWG</dd>
   </dl>
 
   <p>Fragment identifiers used with <code>application/xhtml+xml</code>
-  resources have the same semantics as with any XML MIME type. <a
-  href="#refsRFC3023">[RFC3023]</a></p>
+  resources have the same semantics as with any <span>XML MIME
+  type</span>. <a href="#refsRFC3023">[RFC3023]</a></p>
 
 
   <h3><dfn><code>text/cache-manifest</code></dfn></h3>
 
   <!--
    To: ietf-types@iana.org
    Subject: Registration of media type text/cache-manifest
   -->
 
   <dl>
@@ -86330,75 +86310,686 @@ interface <span>HTMLDocument</span> {
     <tr> 
      <td> <code title="event-load">load</code>
     <tr>
      <td colspan=1 class="XXX"> ...
   </table>
 
 
 
   <h2 class="no-num" id="references">References</h2>
 
-  <p class="XXX">This section will be written in a future draft.</p>
-
-  <!-- XXX check that #refsRFC([0-9]+) is always for [RFC\1] -->
-
-  <!-- REFS
-
-  [ABNF] http://www.ietf.org/rfc/std/std68.txt
-  [BEZIER] Paul de Casteljau, Courbes &agrave; p&ocirc;les, INPI, 1959
-  [BIG5] Institute for Information Industry, "Chinese Coded Character Set in Computer ", March, 1984
-  [BOCU1] http://www.unicode.org/notes/tn6/
-  [CESU8] http://www.unicode.org/unicode/reports/tr26
-  [COMPUTABLE] On computable numbers, with an application to the Entscheidungsproblem. Alan M. Turing. In Proceedings of the London Mathematical Society, series 2, volume 42, pages 230-265. London Mathematical Society, 1937. http://www.turingarchive.org/browse.php/B/12 (referenced: 2007-03-03)
-  [CSS] CSS 2.1
-  [CSSCOLOR] CSS3 Color
-  [CSSOM] CSS Object Model
-  [CSSUI] CSS3 UI
-  [CSSWEBFONTS] CSS3 Web Fonts
-  [E.163] Recommendation E.163 - Numbering Plan for The International Telephone Service, CCITT Blue Book, Fascicle II.2, pp.  128-134, November, 1988.
-  [EUCKR] Korea Industrial Standards Association, "Hangul Unix Environment," Korean Industrial Standard, 1992, Ref. No. KS C 5861-1992.
-  [GBK] http://www.iana.org/assignments/charset-reg/GBK
-
-  <dd id="refsGREGORIAN">[GREGORIAN]</dd>
-  <dd>(Non-normative) <cite>Inter Gravissimas</cite>, A. Lilius, C. Clavius. Gregory XIII Papal Bulls, February 1582.</dd>
-
-  [IANACHARSET] http://www.iana.org/assignments/character-sets
-  [ISO885911] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263
-  [MIMESNIFF] http://tools.ietf.org/html/draft-abarth-mime-sniff
-  [OPENSEARCH] http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
-  [RFC1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.
-  [SCSU] http://www.unicode.org/unicode/reports/tr6/
-  [SELECTORS]
-  [SHIFTJIS] JIS X0208:1997
-  [TIS620] http://www.iana.org/assignments/charset-reg/tis-620 OR http://www.nectec.or.th/it-standards/std620/std620.htm
-  [UNICODECASE] Unicode Standard Annex #21, Case Mappings
-  [UTF32] http://www.unicode.org/unicode/reports/tr19/
-  [UTF7] http://www.ietf.org/rfc/rfc2152.txt
-  [UTS22] http://unicode.org/reports/tr22/#Charset_Alias_Matching
-  [WAVE] http://en.wikipedia.org/wiki/WAV ?
-  [WEBADDRESSES] http://www.w3.org/html/wg/href/draft (for now) (but only for now, for now)
-  [WIN1252] http://www.microsoft.com/globaldev/reference/sbcs/1252.htm OR http://msdn.microsoft.com/en-us/goglobal/cc305145.aspx
-  [WIN1254] http://www.microsoft.com/globaldev/reference/sbcs/1254.htm OR http://msdn.microsoft.com/en-us/goglobal/cc305147.aspx
-  [WIN31J] CP932 http://www.microsoft.com/globaldev/reference/dbcs/932.mspx OR http://msdn.microsoft.com/en-us/goglobal/cc305152.aspx
-  [WIN874] http://www.microsoft.com/globaldev/reference/sbcs/874.mspx
-  [WIN874] http://www.microsoft.com/globaldev/reference/sbcs/874.mspx OR http://msdn.microsoft.com/en-us/goglobal/cc305142.aspx
-  [WIN949] http://www.microsoft.com/globaldev/reference/dbcs/949.mspx OR http://msdn.microsoft.com/en-us/goglobal/cc305154.aspx
-  [X.121] Recommendation X.121 - International Numbering Plan for Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, November, 1988.
-  [X690] http://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf
-
- XXX * take references to "valid mime type" / RFC2046 and make them
-       mean something. (2046 doesn't define anything like that, and
-       2045's definition doesn't really help either, since it's part
-       of something else, and doesn't mention whitespace, etc.)
- XXX * reference [UTC] in the various places that use it.
+  <dl>
+
+   <dt id="refsGRAPHICS">[GRAPHICS]</dt>
+   <dd>(Non-normative) <cite>Computer Graphics: Principles and
+   Practice in C</cite>, Second Edition, J. Foley, A. van Dam,
+   S. Feiner, J. Hughes. Addison-Wesley, July 1995. ISBN
+   0-201-84840-6.</dd>
+   <!--
+   If anyone has this book ("Computer Graphics: Principles and Practice in C"),
+   please check page 34 or so and see if it makes any references to literature in
+   the bibliographic section to define the "even-odd" rule for polygon filling and
+   hit testing.
+   -->
+
+   <dt id="refsGREGORIAN">[GREGORIAN]</dt>
+   <dd>(Non-normative) <cite>Inter Gravissimas</cite>, A. Lilius,
+   C. Clavius. Gregory XIII Papal Bulls, February 1582.</dd>
+
+   <dt id="refsABNF">[ABNF]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/std/std68.txt">Augmented
+   BNF for Syntax Specifications: ABNF</a></cite>, D. Crocker,
+   P. Overell. IETF, January 2008.</dd>
+
+   <dt id="refsATOM">[ATOM]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.ietf.org/rfc/rfc4287.txt">The Atom Syndication
+   Format</a></cite>, M. Nottingham, R. Sayre. IETF, December
+   2005.</dd>
+
+   <dt id="refsBECSS">[BECSS]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/becss/">Behavioral
+   Extensions to CSS</a></cite>, I. Hickson. W3C, October 2007.</dd>
+
+   <dt id="refsBEZIER">[BEZIER]</dt>
+   <dd><cite>Courbes &agrave; poles</cite>, Paul de Casteljau. INPI, 1959.</dd>
+
+   <dt id="refsBIDI">[BIDI]</dt>
+   <dd><cite><a href="http://www.unicode.org/reports/tr9/">UAX #9: Unicode
+   Bidirectional Algorithm</a></cite>, M. Davis. Unicode Consortium,
+   March 2008.</dd>
+
+   <dt id="refsBIG5">[BIG5]</dt>
+   <dd>(Non-normative) <cite>Chinese Coded Character Set in Computer</cite>. Institute
+   for Information Industry, March 1984.</dd>
+
+   <dt id="refsBOCU1">[BOCU1]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.unicode.org/notes/tn6/">UTN #6: BOCU-1:
+   MIME-Compatible Unicode Compression</a></cite>, M. Scherer,
+   M. Davis. Unicode Consortium, February 2006.</dd>
+
+   <dt id="refsCESU8">[CESU8]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.unicode.org/reports/tr26/">UTR #26: Compatibility
+   Encoding Scheme For UTF-16: 8-BIT (CESU-8)</a></cite>,
+   T. Phipps. Unicode Consortium, April 2002.</dd>
+
+   <dt id="refsCHARMOD">[CHARMOD]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.w3.org/TR/charmod/">Character Model for the World
+   Wide Web 1.0: Fundamentals</a></cite>, M. D&uuml;rst, F. Yergeau,
+   R. Ishida, M. Wolf, T. Texin. W3C, February 2005.</dd>
+
+   <dt id="refsCOMPUTABLE">[COMPUTABLE]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.turingarchive.org/browse.php/B/12">On computable
+   numbers, with an application to the
+   Entscheidungsproblem</a></cite>, A. Turing. In <cite>Proceedings of
+   the London Mathematical Society</cite>, series 2, volume 42, pages
+   230-265. London Mathematical Society, 1937.  Retrieved on
+   2007-03-03.</dd>
+
+   <dt id="refsCOOKIES">[COOKIES]</dt>
+   <!--
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2965.txt">HTTP State Management
+   Mechanism</a></cite>, D. Kristol, L. Montulli. IETF, October 2000.</dd>
+   -->
+   <dd><cite><a
+   href="http://tools.ietf.org/html/draft-abarth-cookie">HTTP State
+   Management Mechanism</a></cite>, A. Barth. IETF, August 2009.</dd>
+
+   <dt id="refsCORS">[CORS]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/cors/">Cross-Origin
+   Resource Sharing</a></cite>, A. van Kesteren. W3C, March 2009.</dd>
+   -->
+   <dd><cite><a
+   href="http://dev.w3.org/2006/waf/access-control/">Cross-Origin
+   Resource Sharing</a></cite>, A. Kesteren.  W3C, June 2009.</dd>
+
+   <dt id="refsCSS">[CSS]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/CSS/">Cascading Style Sheets Level 2
+   Revision 1</a></cite>, B. Bos, T. &Ccedil;elik, I.
+   Hickson, H. Lie. W3C, April 2009.</dd>
+
+   <dt id="refsCSSCOLOR">[CSSCOLOR]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/css3-color/">CSS Color
+   Module Level 3</a></cite>, T. &Ccedil;elik, C. Lilley, L.
+   Baron. W3C, July 2008.</dd>
+   -->
+   <dd><cite><a href="http://dev.w3.org/csswg/css3-color/">CSS Color
+   Module Level 3</a></cite>, Tantek &Ccedil;elik, C. Lilley, L.
+   Baron. W3C, August 2008.</dd>
+
+   <dt id="refsCSSOM">[CSSOM]</dt>
+   <dd><cite><a href="http://dev.w3.org/csswg/cssom/">Cascading Style Sheets
+   Object Model (CSSOM)</a></cite>, A. van Kesteren. W3C, December 2007.</dd>
+
+   <dt id="refsCSSUI">[CSSUI]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/css3-ui/">CSS3 Basic User
+   Interface Module</a></cite>, T. &Ccedil;elik. W3C, May 2004.</dd>
+
+   <dt id="refsCSSFONTS">[CSSFONTS]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/css3-fonts/">CSS Fonts
+   Module Level 3</a></cite>, J. Daggett. W3C, June 2009.</dd>
+
+   <dt id="refsDOM2HTML">[DOM2HTML]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document Object Model
+   (DOM) Level 2 HTML Specification</a></cite>, J. Stenback, P. Le
+   Hegaret, A. Le Hors. W3C, January 2003.</dd>
+
+   <dt id="refsDOMCORE">[DOMCORE]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/DOM-Level-3-Core/">Document
+   Object Model (DOM) Level 3 Core Specification</a></cite>, A. Le
+   Hors, P. Le Hegaret, L. Wood, G. Nicol, J. Robie, M. Champion,
+   S. Byrnes. W3C, April 2004.</dd>
+   <!--
+   <dd><cite><a href="http://simon.html5.org/specs/web-dom-core">Web
+   DOM Core</a></cite>, S. Pieters. W3C, June 2009.</dd>
+   -->
+
+   <dt id="refsDOMEVENTS">[DOMEVENTS]</dt>
+   <!--
+   <dd><cite><a
+   href="http://www.w3.org/TR/DOM-Level-3-Events/">Document Object
+   Model (DOM) Level 3 Events Specification</a></cite>,
+   B. H&ouml;hrmann, P. Le Hegaret, T. Pixley. W3C, December
+   2007.</dd>
+   -->
+   <dd><cite><a
+   href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html">Document
+   Object Model (DOM) Level 3 Events Specification</a></cite>,
+   D. Schepers. W3C, July 2009.</dd>
+
+   <dt id="refsDOMRANGE">[DOMRANGE]</dt>
+   <dd><cite><a
+   href="http://www.w3.org/TR/DOM-Level-2-Traversal-Range/">Document
+   Object Model (DOM) Level 2 Traversal and Range
+   Specification</a></cite>, J.  Kesselman, J. Robie, M. Champion,
+   P. Sharpe, V. Apparao, L.  Wood. W3C, November 2000.</dd>
+
+   <dt id="refsDOMVIEWS">[DOMVIEWS]</dt>
+   <dd><cite><a
+   href="http://www.w3.org/TR/DOM-Level-2-Views/">Document Object
+   Model (DOM) Level 2 Views Specification</a></cite>, A. Le Hors, L.
+   Cable. W3C, November 2000.</dd>
+
+   <dt id="refsE163">[E163]</dt>
+   <dd><cite>Recommendation E.163 &mdash; Numbering Plan for The International
+   Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November
+   1988.</dd>
+
+   <dt id="refsECMA262">[ECMA262]</dt>
+   <dd><cite><a
+   href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript
+   Language Specification</a></cite>. ECMA, December 1999.</dd>
+
+   <dt id="refsECMA357">[ECMA357]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.ecma-international.org/publications/standards/Ecma-357.htm">ECMAScript
+   for XML (E4X) Specification</a></cite>. ECMA, December 2005.</dd>
+
+   <dt id="refsEUCKR">[EUCKR]</dt>
+   <dd><cite>Hangul Unix Environment</cite>. Korea Industrial
+   Standards Association, 1992. Ref. No. KS C 5861-1992.</dd>
+
+   <dt id="refsEVENTSOURCE">[EVENTSOURCE]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/eventsource/">Server-Sent
+   Events</a></cite>, I. Hickson. W3C, April 2009.</dd>
+   -->
+   <dd><cite><a
+   href="http://dev.w3.org/html5/eventsource/">Server-Sent
+   Events</a></cite>, I. Hickson. W3C, July 2009.</dd>
+
+   <dt id="refsFILEAPI">[FILEAPI]</dt>
+   <dd><cite><a
+   href="http://dev.w3.org/2006/webapi/FileUpload/publish/FileAPI.html">File
+   API</a></cite>, A. Ranganathan. W3C, August 2009.</dd>
+
+   <dt id="refsGBK">[GBK]</dt>
+   <dd><cite>Chinese Internal Code Specification</cite>. Chinese IT
+   Standardization Technical Committee, December 1995.</dd>
+   <!-- http://www.iana.org/assignments/charset-reg/GBK -->
+
+   <dt id="refsHTML4">[HTML4]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.w3.org/TR/html4/">HTML 4.01
+   Specification</a></cite>, D. Raggett, A. Le Hors, I. Jacobs.  W3C,
+   December 1999.</dd>
+
+   <dt id="refsHTML5">[HTML5]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/html5/">HTML 5</a></cite>,
+   I. Hickson, D. Hyatt. W3C, April 2009.</dd>
+   <dd><cite><a href="http://www.w3.org/html/wg/html5/">HTML
+   5</a></cite>, I. Hickson, D. Hyatt. W3C, August 2009.</dd>
+   -->
+   <dd><cite><a
+   href="http://www.whatwg.org/specs/web-apps/current-work/">HTML
+   5</a></cite>, I. Hickson. WHATWG, August 2009.</dd>
+
+   <dt id="refsHTMLDIFF">[HTMLDIFF]</dt>
+   <!--
+   <dd>(Non-normative) <cite><a
+   href="http://www.w3.org/TR/html5-diff/">HTML 5 differences from
+   HTML 4</a></cite>, A. van Kesteren. W3C, April 2009.</dd>
+   -->
+   <dd>(Non-normative) <cite><a
+   href="http://dev.w3.org/html5/html4-differences/">HTML 5
+   differences from HTML 4</a></cite>, A. van Kesteren.  W3C, August
+   2009.</dd>
+
+   <dt id="refsHTTP">[HTTP]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext
+   Transfer Protocol &mdash; HTTP/1.1</a></cite>, R. Fielding, J. Gettys,
+   J. Mogul, H.  Frystyk, L. Masinter, P. Leach, T. Berners-Lee. IETF,
+   June 1999.</dd>
+
+   <dt id="refsIANACHARSET">[IANACHARSET]</dt>
+   <dd><cite><a
+   href="http://www.iana.org/assignments/character-sets">Character
+   Sets</a></cite>. IANA, May 2007.</dd>
+
+   <dt id="refsIEEE754">[IEEE754]</dt>
+   <dd><cite><a
+   href="http://ieeexplore.ieee.org/servlet/opac?punumber=4610933">IEEE
+   Standard for Floating-Point Arithmetic (IEEE 754)</a></cite>. IEEE,
+   August 2008. ISBN 978-0-7381-5753-5.</dd>
+
+   <dt id="refsISO8601">[ISO8601]</dt>
+   <dd><cite><a href="http://isotc.iso.org/livelink/livelink/4021199/ISO_8601_2004_E.zip?func=doc.Fetch&amp;nodeid=4021199">ISO8601: Data elements and interchange formats &mdash; Information interchange &mdash; Representation of dates and times</a></cite>. ISO, December 2004.</dd>
+
+   <dt id="refsISO885911">[ISO885911]</dt>
+   <dd><cite><a
+   href="http://anubis.dkuug.dk/jtc1/sc2/open/02n3333.pdf">ISO-8859-11:
+   Information technology &mdash; 8-bit single-byte coded graphic
+   character sets &mdash; Part 11: Latin/Thai
+   alphabet</a></cite>. ISO, October 1999.</dd>
+
+   <dt id="refsJSON">[JSON]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc4627.txt">The
+   application/json Media Type for JavaScript Object Notation
+   (JSON)</a></cite>, D. Crockford. IETF, July 2006.</dd>
+
+   <dt id="refsJSURL">[JSURL]</dt>
+   <dd><cite><a
+   href="http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme">The
+   'javascript' resource identifier scheme</a></cite>,
+   B. H&ouml;hrmann. IETF, November 2006.</dd>
+
+   <dt id="refsMAILTO">[MAILTO]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2368.txt">The mailto URL
+   scheme</a></cite>, P. Hoffman, L. Masinter, J. Zawinski.
+   IETF, July 1998.</dd>
+
+   <dt id="refsMATHML">[MATHML]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/MathML/">Mathematical
+   Markup Language (MathML)</a></cite>, D. Carlisle, P. Ion, R. Miner,
+   N. Poppelier. W3C, October 2003.</dd>
+
+   <dt id="refsMIMESNIFF">[MIMESNIFF]</dt>
+   <dd><cite><a
+   href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Content-Type
+   Processing Model</a></cite>, A. Barth, I. Hickson. IETF,
+   May 2009.</dd>
+
+   <dt id="refsMQ">[MQ]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/css3-mediaqueries/">Media
+   Queries</a></cite>, H. Lie, T.  &Ccedil;elik, D. Glazman, A. van
+   Kesteren. W3C, April 2009.</dd>
+   -->
+   <dd><cite><a
+   href="http://dev.w3.org/csswg/css3-mediaqueries/">Media
+   Queries</a></cite>, H. Lie, T.  &Ccedil;elik, D. Glazman, A. van
+   Kesteren. W3C, July 2009.</dd>
+
+   <dt id="refsNPAPI">[NPAPI]</dt>
+   <dd>(Non-normative) <cite><a
+   href="https://developer.mozilla.org/en/Gecko_Plugin_API_Reference">Gecko
+   Plugin API Reference</a></cite>. Mozilla, November 2008.</dd>
+
+   <dt id="refsOPENSEARCH">[OPENSEARCH]</dt>
+   <dd><cite><a
+   href="http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML">Autodiscovery
+   in HTML/XHTML</a></cite>. In <cite>OpenSearch 1.1 Draft 4</cite>,
+   Section 4.6.2. OpenSearch.org.</dd>
+
+   <dt id="refsPINGBACK">[PINGBACK]</dt>
+   <dd><cite><a
+   href="http://www.hixie.ch/specs/pingback/pingback">Pingback
+   1.0</a></cite>, Stuart Langridge, I. Hickson. January 2007.</dd>
+
+   <dt id="refsPNG">[PNG]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/PNG/">Portable Network
+   Graphics (PNG) Specification</a></cite>, D. Duce. W3C, November
+   2003.</dd>
+
+   <dt id="refsPORTERDUFF">[PORTERDUFF]</dt>
+   <dd><cite><a
+   href="http://keithp.com/~keithp/porterduff/p253-porter.pdf">Compositing
+   Digital Images</a></cite>, T. Porter, T. Duff. In <cite>Computer
+   graphics</cite>, volume 18, number 3, pp. 253-259. ACM Press, July
+   1984.</dd>
+
+   <dt id="refsPROGRESS">[PROGRESS]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/progress-events/">Progress
+   Events</a></cite>, C. McCathieNevile. W3C, May 2008.</dd>
+   -->
+   <dd><cite><a
+   href="http://dev.w3.org/2006/webapi/progress/Progress.html">Progress
+   Events</a></cite>, C. McCathieNevile. W3C, March 2009.</dd>
+
+   <dt id="refsPSL">[PSL]</dt>
+   <dd><cite><a href="http://publicsuffix.org/">Public Suffix List</a></cite>.
+   Mozilla Foundation.</dd>
+
+   <dt id="refsRFC1345">[RFC1345]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc1345.txt">Character Mnemonics
+   and Character Sets</a></cite>, K. Simonsen. IETF, June 1992.</dd>
+
+   <dt id="refsRFC1468">[RFC1468]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc1468.txt">Japanese Character
+   Encoding for Internet Messages</a></cite>, J. Murai, M. Crispin, E. van der
+   Poel. IETF, June 1993.</dd>
+
+   <dt id="refsRFC1494">[RFC1494]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.ietf.org/rfc/rfc1494.txt">Equivalences between
+   1988 X.400 and RFC-822 Message Bodies</a></cite>, H. Alvestrand,
+   S. Thompson. IETF, August 1993.</dd>
+
+   <dt id="refsRFC1554">[RFC1554]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc1554.txt">ISO-2022-JP-2:
+   Multilingual Extension of ISO-2022-JP</a></cite>, M. Ohta, K. Handa. IETF,
+   December 1993.</dd>
+
+   <dt id="refsRFC1557">[RFC1557]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc1557.txt">Korean Character
+   Encoding for Internet Messages</a></cite>, U. Choi, K. Chon, H. Park. IETF,
+   December 1993.</dd>
+
+   <dt id="refsRFC1922">[RFC1922]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc1922.txt">Chinese Character
+   Encoding for Internet Messages</a></cite>, HF. Zhu, DY. Hu, ZG. Wang, TC. Kao,
+   WCH. Chang, M. Crispin. IETF, March 1996.</dd>
+
+   <dt id="refsRFC2045">[RFC2045]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet
+   Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite>,
+   N. Freed, N. Borenstein. IETF, November 1996.</dd>
+
+   <dt id="refsRFC2046">[RFC2046]</dt>
+   <dd><cite><a
+   href="http://www.ietf.org/rfc/rfc2046.txt">Multipurpose Internet
+   Mail Extensions (MIME) Part Two: Media Types</a></cite>, N. Freed,
+   N.  Borenstein. IETF, November 1996.</dd> <!-- for text/plain and
+   "Internet Media type"; not for definition of "valid MIME type". -->
+
+   <dt id="refsRFC2109">[RFC2109]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2109.txt">HTTP State Management
+   Mechanism</a></cite>, D. Kristol, L. Montulli. IETF, February 1997.</dd>
+
+   <dt id="refsRFC2119">[RFC2119]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in
+   RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF, March
+   1997.</dd>
+
+   <dt id="refsRFC2318">[RFC2318]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2318.txt">The
+   text/css Media Type</a></cite>, H. Lie, B. Bos, C. Lilley. IETF,
+   March 1998.</dd>
+
+   <dt id="refsRFC2237">[RFC2237]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2237.txt">Japanese Character
+   Encoding for Internet Messages</a></cite>, K. Tamaru. IETF, November
+   1997.</dd>
+
+   <dt id="refsRFC2246">[RFC2246]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2246.txt">The TLS Protocol
+   Version 1.0</a></cite>, T. Dierks, C. Allen. IETF, January 1999.</dd>
+
+   <dt id="refsRFC2388">[RFC2388]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2388.txt">Returning Values from
+   Forms: multipart/form-data</a></cite>, L. Masinter. IETF, August 1998.</dd>
+
+   <dt id="refsRFC2426">[RFC2426]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2426.txt">vCard MIME Directory
+   Profile</a></cite>, F. Dawson, T. Howes. IETF, September 1998.</dd>
+
+   <dt id="refsRFC2445">[RFC2445]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2445.txt">Internet Calendaring
+   and Scheduling Core Object Specification (iCalendar)</a></cite>, F. Dawson, D.
+   Stenerson. IETF, November 1998.</dd>
+
+   <dt id="refsRFC2459">[RFC2459]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2459.txt">Internet X.509 Public
+   Key Infrastructure Certificate and CRL Profile</a></cite>, R. Housley, W.
+   Ford, W. Polk, D. Solo. IETF, January 1999.</dd>
+
+   <dt id="refsRFC2483">[RFC2483]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2483.txt">URI Resolution
+   Services Necessary for URN Resolution</a></cite>, M. Mealling, R. Daniel.
+   IETF, January 1999.</dd>
+
+   <dt id="refsRFC2646">[RFC2646]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2646.txt">The Text/Plain Format
+   Parameter</a></cite>, R. Gellens. IETF, August 1999.</dd>
+
+   <dt id="refsRFC2806">[RFC2806]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.ietf.org/rfc/rfc2806.txt">URLs for Telephone
+   Calls</a></cite>, A. Vaha-Sipila. IETF, April 2000.</dd>
+
+   <dt id="refsRFC3023">[RFC3023]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc3023.txt">XML Media
+   Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn. IETF, January 2001.</dd>
+
+   <dt id="refsBCP47">[BCP47]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/bcp/bcp47.txt">Tags for
+   Identifying Languages; Matching of Language Tags</a></cite>,
+   A. Phillips, M. Davis. IETF, September 2006.</dd>
+
+   <dt id="refsRFC3490">[RFC3490]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc3490.txt">Internationalizing
+   Domain Names in Applications (IDNA)</a></cite>, P. Faltstrom, P. Hoffman, A.
+   Costello. IETF, March 2003.</dd>
+
+   <dt id="refsRFC3548">[RFC3548]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc3548.txt">The Base16, Base32,
+   and Base64 Data Encodings</a></cite>, S. Josefsson. IETF, July
+   2003.</dd>
+
+   <dt id="refsRFC3986">[RFC3986]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource
+   Identifier (URI): Generic Syntax</a></cite>, T. Berners-Lee, R. Fielding, L.
+   Masinter. IETF, January 2005.</dd>
+
+   <dt id="refsRFC3987">[RFC3987]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized
+   Resource Identifiers (IRIs)</a></cite>, M. Duerst, M. Suignard. IETF, January
+   2005.</dd>
+
+   <dt id="refsRFC4281">[RFC4281]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc4281.txt">The Codecs Parameter
+   for "Bucket" Media Types</a></cite>, R. Gellens, D. Singer, P. Frojdh. IETF,
+   November 2005.</dd>
+
+   <dt id="refsRFC4329">[RFC4329]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.ietf.org/rfc/rfc4329.txt">Scripting Media
+   Types</a></cite>, B. H&ouml;hrmann. IETF, April 2006.</dd>
+
+   <dt id="refsRFC4770">[RFC4770]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc4770.txt">vCard Extensions for
+   Instant Messaging (IM)</a></cite>, C. Jennings, J. Reschke. IETF,
+   January 2007.</dd>
+
+   <dt id="refsRFC5322">[RFC5322]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc5322.txt">Internet Message
+   Format</a></cite>, P. Resnick. IETF, October 2008.</dd>
+
+   <dt id="refsSCSU">[SCSU]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.unicode.org/reports/tr6/">UTR #6: A Standard
+   Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler,
+   C. Wicksteed, M. Davis, A. Freytag, M. Scherer. Unicode Consortium,
+   May 2005.</dd>
+
+   <dt id="refsSELECTORS">[SELECTORS]</dt>
+   <dd><cite><a
+   href="http://www.w3.org/TR/css3-selectors">Selectors</a></cite>,
+   T. &Ccedil;elik, E. Etemad, D.  Glazman, I. Hickson, P. Linss,
+   J. Williams. W3C, March 2009.</dd>
+
+   <dt id="refsSHIFTJIS">[SHIFTJIS]</dt>
+   <dd><cite>JIS X0208: 7-bit and 8-bit double byte coded KANJI sets
+   for information interchange</cite>. Japanese Standards Association,
+   1997.</dd>
+
+   <dt id="refsSQL">[SQL]</dt>
+   <dd>The precise dialect has not yet been specified.</dd>
+
+   <dt id="refsSRGB">[SRGB]</dt>
+   <dd><cite><a
+   href="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408!OpenDocument&amp;Click=">IEC
+   61966-2-1: Multimedia systems and equipment &mdash; Colour measurement
+   and management &mdash; Part 2-1: Colour management &mdash; Default RGB colour
+   space &mdash; sRGB</a></cite>. IEC, October 1999.</dd>
+
+   <dt id="refsSVG">[SVG]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/SVGTiny12/">Scalable Vector
+   Graphics (SVG) Tiny 1.2 Specification</a></cite>, O. Andersson,
+   R. Berjon, E. Dahltr&ouml;m, A. Emmons, J. Ferraiolo, A. Grasso,
+   V. Hardy, S. Hayman, D. Jackson, C. Lilley, C. McCormack,
+   A. Neumann, C. Northway, A. Quint, N. Ramani, D. Schepers,
+   A. Shellshear. W3C, December 2008.</dd>
+
+   <dt id="refsTIS620">[TIS620]</dt>
+   <dd><cite><a
+   href="http://www.nectec.or.th/it-standards/std620/std620.htm">UDC
+   681.3.04:003.62</a></cite>. Thai Industrial Standards Institute,
+   Ministry of Industry, Royal Thai Government, 1990. ISBN
+   974-606-153-4.</dd>
+
+   <dt id="refsUNICODE">[UNICODE]</dt>
+   <dd><cite><a href="http://www.unicode.org/versions/">The Unicode Standard</a></cite>. Unicode Consortium, 2007.</dd>
+
+   <dt id="refsUNIVCHARDET">[UNIVCHARDET]</dt>
+   <dd>(Non-normative) <cite><a
+   href="http://www.mozilla.org/projects/intl/UniversalCharsetDetection.html">A
+   composite approach to language/encoding
+   detection</a></cite>. S. Li, K. Momoi. Netscape, September 2001. In
+   <cite>Proceedings of the 19th International Unicode
+   Conference</cite>.</dd>
+
+   <dt id="refsUTF7">[UTF7]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc2152.txt">UTF-7: A
+   Mail-Safe Transformation Format of Unicode</a></cite>,
+   D. Goldsmith, M. Davis. IETF, May 1997.</dd>
+
+   <dt id="refsUTS22">[UTS22]</dt>
+   <dd><cite><a
+   href="http://www.unicode.org/reports/tr22/#Charset_Alias_Matching">Charset
+   Alias Matching</a></cite>. In <cite><a
+   href="http://www.unicode.org/reports/tr22/">UTS #22: Character
+   Mapping Markup Language (CharMapML)</a></cite>, M. Davis,
+   M. Scherer. Unicode Consortium, June 2006.</dd>
+
+ <!--CODECS
+   <dt id="refsWAVE">WAVE</dt>
+   <dd>http://en.wikipedia.org/wiki/WAV? </dd>
+ -->
+
+   <dt id="refsWEBADDRESSES">[WEBADDRESSES]</dt>
+   <dd><cite><a href="http://www.w3.org/html/wg/href/draft">Web
+   addresses in HTML 5</a></cite>, D. Connolly,
+   C. Sperberg-McQueen. March 2009.</dd>
+
+   <dt id="refsWEBDATABASE">[WEBDATABASE]</dt>
+   <dd><cite><a href="http://dev.w3.org/html5/webdatabase/">Web
+   Database</a></cite>, I. Hickson. W3C, July
+   2009.</dd>
+
+   <dt id="refsWEBIDL">[WEBIDL]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/WebIDL/">Web
+   IDL</a></cite>, C. McCormack. W3C, December 2008.</dd>
+   -->
+   <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
+   IDL</a></cite>, C. McCormack. W3C, July 2009.</dd>
+
+   <dt id="refsWEBLINK">[WEBLINK]</dt>
+   <dd><cite><a
+   href="http://tools.ietf.org/html/draft-nottingham-http-link-header">Web
+   Linking</a></cite>, M. Nottingham. IETF, July 2009.</dd>
+
+   <dt id="refsWEBSOCKET">[WEBSOCKET]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/websockets/">The Web Sockets
+   API</a></cite>, I. Hickson. W3C, April
+   2009.</dd>
+   -->
+   <dd><cite><a href="http://dev.w3.org/html5/websockets/">The Web Sockets
+   API</a></cite>, I. Hickson. W3C, August
+   2009.</dd>
+
+   <dt id="refsWHATWGWIKI">[WHATWGWIKI]</dt>
+   <dd><cite><a href="http://wiki.whatwg.org/">The WHATWG Wiki</a></cite>. WHATWG.</dd>
+
+   <dt id="refsWIN1252">[WIN1252]</dt>
+   <dd><cite><a href="http://www.microsoft.com/globaldev/reference/sbcs/1252.htm">Windows 1252</a></cite>. Microsoft.</dd>
+
+   <dt id="refsWIN1254">[WIN1254]</dt>
+   <dd><cite><a href="http://www.microsoft.com/globaldev/reference/sbcs/1254.htm">Windows 1254</a></cite>. Microsoft.</dd>
+
+   <dt id="refsWIN31J">[WIN31J]</dt>
+   <dd><cite><a href="http://www.microsoft.com/globaldev/reference/dbcs/932.mspx">Windows Codepage 932</a></cite>. Microsoft.</dd>
+
+   <dt id="refsWIN874">[WIN874]</dt>
+   <dd><cite><a href="http://www.microsoft.com/globaldev/reference/sbcs/874.mspx">Windows 874</a></cite>. Microsoft.</dd>
+
+   <dt id="refsWIN949">[WIN949]</dt>
+   <dd><cite><a href="http://www.microsoft.com/globaldev/reference/dbcs/949.mspx">Windows Codepage 949</a></cite>. Microsoft.</dd>
+
+   <dt id="refsX121">[X121]</dt>
+   <dd><cite>Recommendation X.121 &mdash; International Numbering Plan for
+   Public Data Networks</cite>, CCITT Blue Book, Fascicle VIII.3,
+   pp. 317-332, November 1988.</dd>
+
+   <dt id="refsX690">[X690]</dt>
+   <dd><cite><a
+   href="http://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf">Recommendation
+   X.690 &mdash; Information Technology &mdash; ASN.1 Encoding Rules &mdash;
+   Specification of Basic Encoding Rules (BER), Canonical Encoding
+   Rules (CER), and Distinguished Encoding Rules
+   (DER)</a></cite>. International Telecommunication Union, July
+   2002.</dd>
+
+   <dt id="refsXHR">[XHR]</dt>
+   <!--
+   <dd><cite><a href="http://www.w3.org/TR/XMLHttpRequest/">The XMLHttpRequest
+   Object</a></cite>, A. van Kesteren. W3C, April
+   2008.</dd>
+   -->
+   <dd><cite><a
+   href="http://dev.w3.org/2006/webapi/XMLHttpRequest/"><code>XMLHttpRequest</code></a></cite>,
+   A. van Kesteren. W3C, June 2009.</dd>
+
+   <dt id="refsXHTML10">[XHTML10]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/xhtml1/">XHTML(TM) 1.0 The
+   Extensible HyperText Markup Language (Second Edition)</a></cite>. W3C,
+   August 2002.</dd>
+
+   <dt id="refsXHTML11">[XHTML11]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/xhtml11/">XHTML(TM) 1.1 -
+   Module-based XHTML</a></cite>, M. Altheim, S. McCarron. W3C,
+   May 2001.</dd>
+
+   <dt id="refsXHTMLMOD">[XHTMLMOD]</dt>
+   <dd><cite><a
+   href="http://www.w3.org/TR/xhtml-modularization">Modularization of
+   XHTML(TM)</a></cite>, M. Altheim, F. Boumphrey, S. Dooley, S.
+   McCarron, S. Schnitzenbaumer, T. Wugofski. W3C, April 2001.</dd>
+
+   <dt id="refsXML">[XML]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/xml/">Extensible Markup
+   Language</a></cite>, T. Bray, J. Paoli, C. Sperberg-McQueen,
+   E. Maler, F. Yergeau. W3C, November 2008.</dd>
+
+   <dt id="refsXMLBASE">[XMLBASE]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/xmlbase/">XML
+   Base</a></cite>, J. Marsh, R. Tobin. W3C, January 2009.</dd>
+
+   <dt id="refsXMLNS">[XMLNS]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/xml-names/">Namespaces in
+   XML</a></cite>, T. Bray, D. Hollander, A. Layman, R. Tobin. W3C,
+   August 2006.</dd>
+
+   <dt id="refsXPATH10">[XPATH10]</dt>
+   <dd><cite><a
+   href="http://www.w3.org/TR/1999/REC-xpath-19991116">XML Path
+   Language (XPath) Version 1.0</a></cite>, J. Clark, S. DeRose. W3C,
+   November 1999.</dd>
+
+   <dt id="refsXSLT10">[XSLT10]</dt>
+   <dd><cite><a href="http://www.w3.org/TR/1999/REC-xslt-19991116">XSL
+   Transformations (XSLT) Version 1.0</a></cite>, J. Clark. W3C,
+   November 1999.</dd>
+
+  </dl>
 
-  -->
 
 
   <h2 class="no-num">Acknowledgements</h2> <!-- ACKS -->
 
   <p>Thanks to
 
   Aankhen,
   Aaron Boodman,
   Aaron Leventhal,
   Adam Barth,

|