Skip to content
Browse files

[] (0) Add references. Define MIME type. Define valid MIME type.

git-svn-id: http://svn.whatwg.org/webapps@3580 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent 92f6ec7 commit 74578286fc1d1443d63029682998457d1717799d @Hixie Hixie committed
Showing with 1,592 additions and 450 deletions.
  1. +771 −220 index
  2. +821 −230 source
View
991 index
@@ -82,7 +82,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft-standard-—-date:-01-jan-1901>Draft Standard — 9 August 2009</h2>
+ <h2 class="no-num no-toc" id=draft-standard-—-date:-01-jan-1901>Draft Standard — 11 August 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -188,12 +188,12 @@
<ol>
<li><a href=#terminology><span class=secno>2.1 </span>Terminology</a>
<ol>
- <li><a href=#xml><span class=secno>2.1.1 </span>XML</a></li>
- <li><a href=#dom-trees><span class=secno>2.1.2 </span>DOM trees</a></li>
- <li><a href=#scripting-0><span class=secno>2.1.3 </span>Scripting</a></li>
- <li><a href=#plugins><span class=secno>2.1.4 </span>Plugins</a></li>
- <li><a href=#character-encodings><span class=secno>2.1.5 </span>Character encodings</a></li>
- <li><a href=#resources><span class=secno>2.1.6 </span>Resources</a></ol></li>
+ <li><a href=#resources><span class=secno>2.1.1 </span>Resources</a></li>
+ <li><a href=#xml><span class=secno>2.1.2 </span>XML</a></li>
+ <li><a href=#dom-trees><span class=secno>2.1.3 </span>DOM trees</a></li>
+ <li><a href=#scripting-0><span class=secno>2.1.4 </span>Scripting</a></li>
+ <li><a href=#plugins><span class=secno>2.1.5 </span>Plugins</a></li>
+ <li><a href=#character-encodings><span class=secno>2.1.6 </span>Character encodings</a></ol></li>
<li><a href=#conformance-requirements><span class=secno>2.2 </span>Conformance requirements</a>
<ol>
<li><a href=#dependencies><span class=secno>2.2.1 </span>Dependencies</a></li>
@@ -1282,9 +1282,9 @@
<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><a href=#text/html>text/html</a></code>, then it will be processed as an "HTML5"
- document by Web browsers.</p>
+ browsers. If a document is transmitted with the <a href=#mime-type>MIME
+ type</a> <code><a href=#text/html>text/html</a></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 <a href=#xml-mime-type>XML MIME
@@ -1625,7 +1625,38 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
must continue from where it left off in calling B.</p>
- <h4 id=xml><span class=secno>2.1.1 </span>XML</h4>
+ <h4 id=resources><span class=secno>2.1.1 </span>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 id=mime-type>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 id=valid-mime-type>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 id=xml><span class=secno>2.1.2 </span>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
@@ -1661,12 +1692,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
not an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string
"<code title="">xml</code>". <a href=#refsXML>[XML]</a></p>
- <p>The term <dfn id=xml-mime-type>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 href=#refsRFC3023>[RFC3023]</a></p>
+ <p>The term <dfn id=xml-mime-type>XML MIME type</dfn> is used to refer to the <a href=#mime-type title="MIME type">MIME types</a> <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 id=dom-trees><span class=secno>2.1.2 </span>DOM trees</h4>
+ <h4 id=dom-trees><span class=secno>2.1.3 </span>DOM trees</h4>
<p>The term <dfn id=root-element>root element</dfn>, when not explicitly qualified
as referring to the document's root element, means the furthest
@@ -1717,7 +1748,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
an attribute to a value it already has does not change it.</p>
- <h4 id=scripting-0><span class=secno>2.1.3 </span>Scripting</h4>
+ <h4 id=scripting-0><span class=secno>2.1.4 </span>Scripting</h4>
<p>The construction "a <code>Foo</code> object", where
<code>Foo</code> is actually an interface, is sometimes used instead
@@ -1739,7 +1770,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
specifications. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
- <h4 id=plugins><span class=secno>2.1.4 </span>Plugins</h4>
+ <h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
<p>The term <dfn id=plugin>plugin</dfn> is used to mean any content handler
for Web content types that are either not supported by the user
@@ -1771,7 +1802,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
agent.</p>
- <h4 id=character-encodings><span class=secno>2.1.5 </span>Character encodings</h4>
+ <h4 id=character-encodings><span class=secno>2.1.6 </span>Character encodings</h4>
<p>An <dfn id=ascii-compatible-character-encoding>ASCII-compatible character encoding</dfn> is a
single-byte or variable-length encoding in which the bytes 0x09,
@@ -1796,34 +1827,6 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
-->
- <h4 id=resources><span class=secno>2.1.6 </span>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 id=conformance-requirements><span class=secno>2.2 </span>Conformance requirements</h3>
@@ -2101,7 +2104,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<p id=authors-using-html>Documents that use <a href=#syntax>the HTML
syntax</a>, if they are served over the wire (e.g. by HTTP) must
- be labeled with the <code><a href=#text/html>text/html</a></code> MIME type.</p>
+ be labeled with the <code><a href=#text/html>text/html</a></code> <a href=#mime-type>MIME
+ type</a>.</p>
<p class=impl id=entity-references>The language in this
specification assumes that the user agent expands all entity
@@ -2133,7 +2137,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<p>Implementations that support <a href=#the-xhtml-syntax>the XHTML syntax</a> 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>
+ serialization with namespaces. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a></p>
</dd>
@@ -2183,10 +2187,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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, <a href=#willful-violation title="willful violation">despite it being an
- officially obsoleted type</a> according to RFC 4329. <a href=#refsRFC4329>[RFC4329]</a></p>
+ JavaScript is more widely known. Similarly, the <a href=#mime-type>MIME
+ type</a> used to refer to JavaScript in this specification is
+ <code title="">text/javascript</code>, since that is the most
+ commonly used type, <a href=#willful-violation title="willful violation">despite it
+ being an officially obsoleted type</a> according to RFC
+ 4329. <a href=#refsRFC4329>[RFC4329]</a></p>
</dd>
@@ -2276,7 +2282,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<p>Comparing two strings in a <dfn id=compatibility-caseless>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>
+ operation to compare the two strings. <a href=#refsUNICODE>[UNICODE]</a></p>
<div class=impl>
@@ -4821,8 +4827,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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/
- -->
+ is not, then the string is not valid; abort these steps. <a href=#refsPSL>[PSL]</a></p>
</li>
@@ -5527,10 +5532,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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>
@@ -8395,8 +8400,8 @@ Transport Protocol"&gt;HTTP&lt;/abbr&gt; today.&lt;/p&gt;</pre>
<p>The <dfn id=attr-lang title=attr-lang><code>lang</code></dfn> attribute (in
no namespace) specifies the primary <dfn id=language>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 id=attr-xml-lang title=attr-xml-lang><code title="">lang</code></dfn>
attribute in the <a href=#xml-namespace>XML namespace</a> is defined in XML. <a href=#refsXML>[XML]</a></p>
@@ -10979,8 +10984,9 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
attribute on hyperlink elements</a>.</p>
<p>The <dfn id=attr-link-type 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 <a href=#mime-type>MIME type</a> of the linked resource. It is purely advisory.
+ The value must be a <a href=#valid-mime-type>valid MIME type</a>, optionally with
+ parameters.</p>
<p>For <a href=#external-resource-link title="external resource link">external resource
links</a>, the <code title=attr-link-type><a href=#attr-link-type>type</a></code> attribute
@@ -10990,9 +10996,9 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
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 <a href=#mime-type>MIME type</a> 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 <a href=#mime-type>MIME type</a> for the given link relationship, then the UA should
<a href=#fetch>fetch</a> 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
@@ -11040,7 +11046,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
<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 <a href=#mime-type>MIME type</a> for CSS style
sheets).</p>
<p>For files B and C, it would then check the actual types returned
@@ -11496,7 +11502,7 @@ people expect to have work and what is necessary.
<p>For <code><a href=#meta>meta</a></code> elements with an <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute in the
<a href=#attr-meta-http-equiv-content-language title=attr-meta-http-equiv-content-language>Content
Language state</a>, the <code title=attr-meta-content><a href=#attr-meta-content>content</a></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
@@ -11847,7 +11853,7 @@ people expect to have work and what is necessary.
<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>
@@ -11909,9 +11915,10 @@ people expect to have work and what is necessary.
model</a>. The element does not <a href=#represents title=represents>represent</a> content for the user.</p>
<p>If the <dfn id=attr-style-type 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 <a href=#valid-mime-type>valid MIME type</a>,
+ 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>
@@ -12209,10 +12216,9 @@ people expect to have work and what is necessary.
<p>The <dfn id=attr-script-type 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 <a href=#valid-mime-type>valid MIME
+ type</a>, 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 id=attr-script-src title=attr-script-src><code>src</code></dfn>
attribute, if specified, gives the address of the external script
@@ -12817,13 +12823,13 @@ o............A....e
<div class=impl>
<p>A user agent is said to <dfn id=support-the-scripting-language>support the scripting language</dfn>
- if <var><a href="#the-script-block's-type">the script block's type</a></var> matches the MIME type of a
+ if <var><a href="#the-script-block's-type">the script block's type</a></var> matches the <a href=#mime-type>MIME type</a> 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 <a href=#mime-type title="MIME type">MIME
+ types</a> and the languages to which they refer:</p>
<dl>
@@ -12852,7 +12858,8 @@ o............A....e
<div class=impl>
- <p>User agents may support other MIME types and other languages.</p>
+ <p>User agents may support other <a href=#mime-type title="MIME type">MIME
+ types</a> and other languages.</p>
<!-- this paragraph is also present in the <style> section -->
<p>When examining types to determine if they support the language,
@@ -20383,14 +20390,12 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
present, must contain a <a href=#valid-url>valid URL</a>.</p>
<p>The <dfn id=attr-embed-type 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><a href=#attr-embed-type>type</a></code>
- attribute and the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute
- are present, then the <code title=attr-embed-type><a href=#attr-embed-type>type</a></code>
- attribute must specify the same type as the <a href=#content-type title=Content-Type>explicit Content-Type metadata</a> of the
- resource given by the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code>
- attribute. <a href=#refsRFC2046>[RFC2046]</a></p>
+ attribute, if present, gives the <a href=#mime-type>MIME type</a> of the plugin to
+ instantiate. The value must be a <a href=#valid-mime-type>valid MIME type</a>,
+ optionally with parameters. If both the <code title=attr-embed-type><a href=#attr-embed-type>type</a></code> attribute and the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute are present, then the
+ <code title=attr-embed-type><a href=#attr-embed-type>type</a></code> attribute must specify the
+ same type as the <a href=#content-type title=Content-Type>explicit Content-Type
+ metadata</a> of the resource given by the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute.</p>
<div class=impl>
@@ -20600,8 +20605,8 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
<p>The <dfn id=attr-object-type 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 <a href=#valid-mime-type>valid MIME type</a>,
+ optionally with parameters.</p>
<p>One or both of the <code title=attr-object-data><a href=#attr-object-data>data</a></code> and
<code title=attr-object-type><a href=#attr-object-type>type</a></code> attributes must be
@@ -21508,9 +21513,9 @@ interface <dfn id=htmlaudioelement>HTMLAudioElement</dfn> : <a href=#htmlmediael
attribute gives the type of the <a href=#media-resource>media resource</a>, to help
the user agent determine if it can play this <a href=#media-resource>media
resource</a> 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 href=#refsRFC4281>[RFC4281]</a></p>
+ a <a href=#valid-mime-type>valid MIME type</a>. 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>
@@ -21899,7 +21904,8 @@ interface <dfn id=cuerangecallback>CueRangeCallback</dfn> {
<h5 id=mime-types><span class=secno>4.8.10.3 </span>MIME types</h5>
<p>A <a href=#media-resource>media resource</a> 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 href=#refsRFC4281>[RFC4281]</a>.</p>
+ <em>type</em>, specifically a <a href=#mime-type>MIME type</a>, 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
@@ -21915,7 +21921,7 @@ interface <dfn id=cuerangecallback>CueRangeCallback</dfn> {
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 <a href=#mime-type>MIME type</a> "<code title="">application/octet-stream</code>" is
never <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot
render</a>. User agents must treat that type as equivalent to the
lack of any explicit <a href=#content-type title=Content-Type>Content-Type
@@ -22327,7 +22333,7 @@ interface <dfn id=cuerangecallback>CueRangeCallback</dfn> {
below.</li>
<li><p>⌛ If <var title="">candidate</var> has a <code title=attr-source-type><a href=#attr-source-type>type</a></code> attribute whose value, when
- parsed as a MIME type (including any codecs described by the
+ parsed as a <a href=#mime-type>MIME type</a> (including any codecs described by the
<code title="">codec</code> parameter), represents <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type
that the user agent knows it cannot render</a>, then end the
<a href=#synchronous-section>synchronous section</a>, and jump down to the <i title="">failed</i> step below.</li>
@@ -22491,7 +22497,7 @@ interface <dfn id=cuerangecallback>CueRangeCallback</dfn> {
fetch the resource</dt>
<dt>If the <a href=#media-resource>media resource</a> is found to have <a href=#content-type title=Content-Type>Content-Type metadata</a> that, when
- parsed as a MIME type (including any codecs described by the
+ parsed as a <a href=#mime-type>MIME type</a> (including any codecs described by the
<code title="">codec</code> parameter), represents <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type
that the user agent knows it cannot render</a> (even if the
actual <a href=#media-data>media data</a> is in a supported format)</dt>
@@ -24472,10 +24478,10 @@ interface <dfn id=cuerangecallback>CueRangeCallback</dfn> {
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><a href=#dom-canvas-todataurl>toDataURL(<var title="">type</var>)</a></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
+ <p>When the <code title=dom-canvas-toDataURL><a href=#dom-canvas-todataurl>toDataURL(<var title="">type</var>)</a></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 <a href=#mime-type title="MIME
+ type">MIME types</a> 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
@@ -25074,10 +25080,6 @@ idea from Mihai:
<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><a href=#dom-context-2d-globalcompositeoperation>globalCompositeOperation</a></code>
@@ -26323,7 +26325,7 @@ notes on what would need to be defined for dashed lines:
<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>
+ to another as described by the relevant CSS specifications.) <a 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
@@ -27060,8 +27062,8 @@ v4DVT (also check for '- -' bits in the part above) -->
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
@@ -27953,15 +27955,6 @@ function AddCloud(data, x, y) { ... }</pre>
<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
@@ -31477,7 +31470,7 @@ interface <dfn id=htmlformelement>HTMLFormElement</dfn> : <a href=#htmlelement>H
<tr>
<td> <dfn id=attr-input-type-file-keyword title=attr-input-type-file-keyword><code>file</code></dfn>
<td> <a href=#file-upload-state title=attr-input-type-file>File Upload</a>
- <td> Zero or more files each with a MIME type and optionally a file name
+ <td> Zero or more files each with a <a href=#mime-type>MIME type</a> and optionally a file name
<td> A label and a button
<tr>
<td> <dfn id=attr-input-type-submit-keyword title=attr-input-type-submit-keyword><code>submit</code></dfn>
@@ -34798,9 +34791,9 @@ interface <dfn id=htmlformelement>HTMLFormElement</dfn> : <a href=#htmlelement>H
<dd>Indicates that image files are accepted.</dd>
- <dt>A valid MIME type, with no parameters</dt>
+ <dt>A <a href=#valid-mime-type>valid MIME type</a>, 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>
@@ -45440,7 +45433,7 @@ document.body.appendChild(outer);</pre>
<p>The <a href=#concept-property-value title=concept-property-value>value</a> 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 <a href=#concept-item title=concept-item>item</a> with zero or more <code title=md-vcard-tel-type><a href=#md-vcard-tel-type>type</a></code> properties and exactly one
- <code title=md-vcard-tel-value><a href=#md-vcard-tel-value>value</a></code> property. <a href=#refsE163>[E.163]</a> <a href=#X.121>[X.121]</a></p>
+ <code title=md-vcard-tel-value><a href=#md-vcard-tel-value>value</a></code> property. <a href=#refsE163>[E163]</a> <a href=#refsX121>[X121]</a></p>
<p>If no <code title=md-vcard-tel-type><a href=#md-vcard-tel-type>type</a></code> properties
are present within an <a href=#concept-item title=concept-item>item</a> that
@@ -45482,7 +45475,7 @@ document.body.appendChild(outer);</pre>
<p>The <a href=#concept-property-value title=concept-property-value>value</a> 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>
+ the CCITT specifications E.163 and X.121. <a href=#refsE163>[E163]</a> <a href=#refsX121>[X121]</a></p>
<p>Exactly one property with the name <code title=md-vcard-tel-value><a href=#md-vcard-tel-value>value</a></code> must be present within the
<a href=#concept-item title=concept-item>item</a> that forms the <a href=#concept-property-value title=concept-property-value>value</a> of a <code title=md-vcard-tel><a href=#md-vcard-tel>tel</a></code> property of an <a href=#concept-item title=concept-item>item</a> with the type <code title=md-vcard><a href=#md-vcard>vcard</a></code>.</p>
@@ -50296,8 +50289,7 @@ interface <dfn id=window>Window</dfn> {
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><a href=#security_err>SECURITY_ERR</a></code> exception and abort these steps. <a href=#refsPSL>[PSL]</a></p> <!-- [PSL]
- http://publicsuffix.org/ -->
+ <code><a href=#security_err>SECURITY_ERR</a></code> exception and abort these steps. <a href=#refsPSL>[PSL]</a></p>
<p>Suffixes must be compared after applying the IDNA ToASCII
algorithm to them, with both the AllowUnassigned and
@@ -50945,12 +50937,6 @@ interface <dfn id=window>Window</dfn> {
<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></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>
@@ -52422,7 +52408,7 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
such a link, he is given the opportunity to use that Web
site. Analogously, the <dfn id=dom-navigator-registercontenthandler 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 <a href=#mime-type>MIME type</a>. 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,
@@ -52496,11 +52482,11 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
<dd>
- <p>A MIME type, such as <code>model/vrml</code> or
- <code>text/richtext</code>. The MIME type must be compared in an
- <a href=#ascii-case-insensitive>ASCII case-insensitive</a> 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 <a href=#mime-type>MIME type</a>, such as <code>model/vrml</code> or
+ <code>text/richtext</code>. The <a href=#mime-type>MIME type</a> must be
+ compared in an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> 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
@@ -52509,7 +52495,7 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
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 <a href=#mime-type>MIME type</a> used by the
user agent <em>after</em> the sniffing algorithms have been
applied.</p>
@@ -52554,7 +52540,7 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
<pre>&lt;a href="chickenkïwi.soup"&gt;Download our Chicken Kïwi soup!&lt;/a&gt;</pre>
<p>...then, assuming this <code>chickenkïwi.soup</code> file
- was served with the MIME type <code>application/x-soup</code>,
+ was served with the <a href=#mime-type>MIME type</a> <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>
@@ -52744,7 +52730,7 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
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" <a href=#mime-type>MIME type</a>, then it might display a dialog
as follows:</p>
<pre>||[ Unknown File Type ]|||||||||||||||||||||||||||||||||||||||
@@ -53190,8 +53176,8 @@ style/default.css</pre>
<h5 id=writing-cache-manifests><span class=secno>6.9.3.2 </span>Writing cache manifests</h5>
<p>Manifests must be served using the
- <code><a href=#text/cache-manifest>text/cache-manifest</a></code> MIME type. All resources served
- using the <code><a href=#text/cache-manifest>text/cache-manifest</a></code> MIME type must follow the
+ <code><a href=#text/cache-manifest>text/cache-manifest</a></code> <a href=#mime-type>MIME type</a>. All resources served
+ using the <code><a href=#text/cache-manifest>text/cache-manifest</a></code> <a href=#mime-type>MIME type</a> must follow the
syntax of application cache manifests, as described in this
section.</p>
@@ -53202,7 +53188,7 @@ style/default.css</pre>
CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.</p>
<p class=note>This is a <a href=#willful-violation title="willful violation">willful
- double violation</a> of RFC2046, which requires all <code title="">text/*</code> types to support an open-ended set of
+ double violation</a> 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
@@ -53722,7 +53708,7 @@ style/default.css</pre>
<p><i>Fetching the manifest</i>: <a href=#fetch>Fetch</a> 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 <a href=#mime-type>MIME type</a>
<code><a href=#text/cache-manifest>text/cache-manifest</a></code>, parse <var title="">manifest</var> according to the <a href=#parse-a-manifest title="parse a
manifest">rules for parsing manifests</a>, obtaining a list of
<a href=#concept-appcache-explicit title=concept-appcache-explicit>explicit entries</a>,
@@ -53789,7 +53775,7 @@ style/default.css</pre>
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 <a href=#mime-type>MIME type</a> other
than <code><a href=#text/cache-manifest>text/cache-manifest</a></code>, then run the <a href=#cache-failure-steps>cache
failure steps</a>.</p>
@@ -56137,11 +56123,12 @@ style/default.css</pre>
<p><dfn id=the-indicated-part-of-the-document>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 <a href=#xml-mime-type title="XML MIME type">XML MIME types</a> is the responsibility of
- RFC3023).</p>
+ defined by the specification that defines the <a href=#mime-type>MIME type</a>
+ used by the <code>Document</code> (for example, the processing of
+ fragment identifiers for <a href=#xml-mime-type title="XML MIME type">XML MIME
+ types</a> is the responsibility of RFC3023).</p>
- <p>For HTML documents (and the <code><a href=#text/html>text/html</a></code> MIME type),
+ <p>For HTML documents (and the <code><a href=#text/html>text/html</a></code> <a href=#mime-type>MIME type</a>),
the following processing model must be followed to determine what
<a href=#the-indicated-part-of-the-document>the indicated part of the document</a> is.</p>
@@ -56465,7 +56452,7 @@ style/default.css</pre>
<p>The <dfn id=attr-hyperlink-hreflang 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 — upon fetching the resource, user agents must
use only language information associated with the resource to
@@ -56473,13 +56460,12 @@ style/default.css</pre>
resource.</span></p>
<p>The <dfn id=attr-hyperlink-type 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><a href=#attr-hyperlink-type>type</a></code>
- attribute authoritative — 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 <a href=#mime-type>MIME type</a> of the linked
+ resource. It is purely advisory. The value must be a <a href=#valid-mime-type>valid
+ MIME type</a>, optionally with parameters. <span class=impl>User agents must not consider the <code title=attr-hyperlink-type><a href=#attr-hyperlink-type>type</a></code> attribute authoritative
+ — 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>
@@ -56567,7 +56553,7 @@ style/default.css</pre>
<p>For URLs that are HTTP URLs, the requests must be performed by
<a href=#fetch title=fetch>fetching</a> the specified URLs using the
- POST method, with an entity body with the MIME type <code title="">text/ping</code> consisting of the four-character string
+ POST method, with an entity body with the <a href=#mime-type>MIME type</a> <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>
@@ -59797,11 +59783,11 @@ style/default.css</pre>
};</pre>
<p><code><a href=#datatransfer>DataTransfer</a></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,
- <a href=#case-sensitive>case-sensitive</a>, strings, and the empty string is a
- valid format string.</p>
+ associated with a unique format. Formats are generally given by
+ <a href=#mime-type title="MIME type">MIME types</a>, with some values
+ special-cased for legacy reasons. For the purposes of this API,
+ however, the format strings are opaque, <a href=#case-sensitive>case-sensitive</a>,
+ strings, and the empty string is a valid format string.</p>
<dl class=domintro>
@@ -64047,9 +64033,7 @@ interface <dfn id=messageport>MessagePort</dfn> {
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 <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a>
- <i>tentative</i>, and abort these steps. <a href=#refsUNIVCHARDET>[UNIVCHARDET]</a></li> <!--
- http://www.mozilla.org/projects/intl/UniversalCharsetDetection.html
- -->
+ <i>tentative</i>, and abort these steps. <a href=#refsUNIVCHARDET>[UNIVCHARDET]</a></li>
<li><p>Otherwise, return an implementation-defined or
user-specified default character encoding, with the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a>
@@ -75884,7 +75868,7 @@ time:empty { binding: <i title="">time</i>; }</pre>
<dd><p>Use <code><a href=#the-object-element>object</a></code> instead of <code><a href=#the-embed-element>embed</a></code> when fallback is necessary.</dd>
<dt><dfn id=plaintext><code>plaintext</code></dfn><dt>
- <dd><p>Use the "<code>text/plain</code>" MIME type instead.</dd>
+ <dd><p>Use the "<code>text/plain</code>" <a href=#mime-type>MIME type</a> instead.</dd>
<dt><dfn id=basefont><code>basefont</code></dfn></dt>
<dt><dfn id=big><code>big</code></dfn></dt>
@@ -77415,7 +77399,7 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<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>
+ available in the Content-Type Processing Model specification. <a 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
@@ -77473,7 +77457,7 @@ interface <a href=#htmldocument>HTMLDocument</a> {
type asserts that the resource is an XML document that likely has
a root element from the <a href=#html-namespace-0>HTML namespace</a>. 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>
+ in XML specification, and this specification. <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>
@@ -77503,7 +77487,8 @@ interface <a href=#htmldocument>HTMLDocument</a> {
</dl>
<p>Fragment identifiers used with <code><a href=#application/xhtml+xml>application/xhtml+xml</a></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 <a href=#xml-mime-type>XML MIME
+ type</a>. <a href=#refsRFC3023>[RFC3023]</a></p>
<h3 id=text/cache-manifest><span class=secno>13.3 </span><dfn><code>text/cache-manifest</code></dfn></h3>
@@ -77775,61 +77760,627 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<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 à 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ü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. Ç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 Ç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. Ç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 — 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 — 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 — Information interchange — 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 — 8-bit single-byte coded graphic
+ character sets — 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ö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. Ç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ö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. Ç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 — Colour measurement
+ and management — Part 2-1: Colour management — Default RGB colour
+ space — 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ö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 — 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 — Information Technology — ASN.1 Encoding Rules —
+ 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 id=acknowledgements>Acknowledgements</h2> <!-- ACKS -->
View
1,051 source
@@ -251,9 +251,9 @@
<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
@@ -609,6 +609,39 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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
@@ -648,10 +681,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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>
@@ -794,35 +827,6 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
-->
- <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>
@@ -1108,7 +1112,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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
@@ -1141,7 +1146,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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>
@@ -1193,12 +1198,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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>
@@ -1291,7 +1296,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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">
@@ -4084,8 +4089,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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>
@@ -4824,10 +4828,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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>
@@ -7875,8 +7879,8 @@ Transport Protocol">HTTP&lt;/abbr> today.&lt;/p></pre>
<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
@@ -10599,9 +10603,9 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
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
@@ -10611,9 +10615,9 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
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
@@ -10668,7 +10672,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
<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
@@ -11158,8 +11162,8 @@ people expect to have work and what is necessary.
<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
@@ -11544,7 +11548,7 @@ people expect to have work and what is necessary.
<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>
@@ -11607,11 +11611,10 @@ people expect to have work and what is necessary.
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">
@@ -11940,11 +11943,11 @@ people expect to have work and what is necessary.
<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
@@ -12600,13 +12603,13 @@ o............A....e
<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>
@@ -12635,7 +12638,8 @@ o............A....e
<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,
@@ -20468,15 +20472,15 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
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">
@@ -20704,8 +20708,8 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
<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
@@ -21677,9 +21681,9 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
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">
@@ -22088,9 +22092,8 @@ interface <dfn>CueRangeCallback</dfn> {
<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
@@ -22108,7 +22111,7 @@ interface <dfn>CueRangeCallback</dfn> {
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
@@ -22574,7 +22577,7 @@ interface <dfn>CueRangeCallback</dfn> {
<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
@@ -22761,7 +22764,7 @@ interface <dfn>CueRangeCallback</dfn> {
<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>
@@ -24927,11 +24930,11 @@ interface <dfn>CueRangeCallback</dfn> {
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
@@ -25580,10 +25583,6 @@ idea from Mihai:
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
@@ -27003,7 +27002,7 @@ notes on what would need to be defined for dashed lines:
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
@@ -27851,10 +27850,9 @@ v4DVT (also check for '- -' bits in the part above) -->
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>
@@ -28898,15 +28896,6 @@ function AddCloud(data, x, y) { ... }</pre>
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
@@ -32739,7 +32728,7 @@ interface <dfn>HTMLFormElement</dfn> : <span>HTMLElement</span> {
<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>
@@ -36395,9 +36384,9 @@ interface <dfn>HTMLFormElement</dfn> : <span>HTMLElement</span> {
<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>
@@ -48126,7 +48115,7 @@ document.body.appendChild(outer);</pre>
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
@@ -48187,7 +48176,7 @@ document.body.appendChild(outer);</pre>
<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
@@ -53590,8 +53579,7 @@ interface <dfn>Window</dfn> {
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
@@ -54272,12 +54260,6 @@ interface <dfn>Window</dfn> {
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>
@@ -55864,7 +55846,7 @@ interface <dfn>NavigatorAbilities</dfn> {
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
@@ -55940,11 +55922,11 @@ interface <dfn>NavigatorAbilities</dfn> {
<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
@@ -55953,7 +55935,7 @@ interface <dfn>NavigatorAbilities</dfn> {
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>
@@ -56004,7 +55986,7 @@ interface <dfn>NavigatorAbilities</dfn> {
<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>
@@ -56203,7 +56185,7 @@ interface <dfn>NavigatorAbilities</dfn> {
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 ]|||||||||||||||||||||||||||||||||||||||
@@ -56653,8 +56635,8 @@ 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>
@@ -56665,7 +56647,7 @@ style/default.css</pre>
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
@@ -57238,7 +57220,7 @@ style/default.css</pre>
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
@@ -57318,7 +57300,7 @@ style/default.css</pre>
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>
@@ -59864,12 +59846,12 @@ style/default.css</pre>
<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>
@@ -61937,7 +61919,7 @@ interface <dfn>SQLTransactionSync</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
@@ -61945,14 +61927,14 @@ interface <dfn>SQLTransactionSync</dfn> {
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">
@@ -62046,7 +62028,7 @@ interface <dfn>SQLTransactionSync</dfn> {
<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
@@ -65514,11 +65496,11 @@ interface <dfn>SQLTransactionSync</dfn> {
};</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">
@@ -69693,12 +69675,12 @@ interface <dfn>EventSource</dfn> {
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
@@ -69709,7 +69691,7 @@ interface <dfn>EventSource</dfn> {
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
@@ -69791,7 +69773,7 @@ interface <dfn>EventSource</dfn> {