[html5] r5302 - [e] (0) referenced spec name change update Fixing http://www.w3.org/Bugs/Public/ [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Aug 16 14:47:16 PDT 2010
Author: ianh
Date: 2010-08-16 14:47:15 -0700 (Mon, 16 Aug 2010)
New Revision: 5302
Modified:
complete.html
index
source
Log:
[e] (0) referenced spec name change update
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9682
Modified: complete.html
===================================================================
--- complete.html 2010-08-16 21:38:59 UTC (rev 5301)
+++ complete.html 2010-08-16 21:47:15 UTC (rev 5302)
@@ -6449,27 +6449,27 @@
<p>The <dfn id=content-type title=Content-Type>Content-Type metadata</dfn> of a
resource must be obtained and interpreted in a manner consistent
- with the requirements of the Content-Type Processing Model
+ with the requirements of the Media Type Sniffing
specification. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p>The <dfn id=content-type-sniffing-0 title="Content-Type sniffing">sniffed type of a
resource</dfn> must be found in a manner consistent with the
- requirements given in the Content-Type Processing Model
+ requirements given in the Media Type Sniffing
specification for finding the <i>sniffed-type</i> of the relevant
sequence of octets. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing: image">rules for sniffing
images specifically</dfn> and the <dfn id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:
text or binary">rules for distingushing if a resource is text or
- binary</dfn> are also defined in the Content-Type Processing Model
+ binary</dfn> are also defined in the Media Type Sniffing
specification. Both sets of rules return a <a href=#mime-type>MIME type</a> as
their result. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p class=warning>It is imperative that the rules in the
- Content-Type Processing Model specification be followed
+ Media Type Sniffing specification be followed
exactly. When a user agent uses different heuristics for content
type detection than the server expects, security problems can
- occur. For more details, see the Content-Type Processing Model
+ occur. For more details, see the Media Type Sniffing
specification. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p>The <dfn id=algorithm-for-extracting-an-encoding-from-a-content-type>algorithm for extracting an encoding from a
@@ -91270,7 +91270,7 @@
<dl><dt>Magic number(s):</dt>
<dd>No sequence of bytes can uniquely identify an HTML
document. More information on detecting HTML documents is
- available in the Content-Type Processing Model specification. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></dd>
+ available in the Media Type Sniffing 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
@@ -94857,8 +94857,8 @@
N. Poppelier. W3C.</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.</dd>
+ <dd><cite><a href=http://tools.ietf.org/html/draft-abarth-mime-sniff>Media
+ Type Sniffing</a></cite>, A. Barth, I. Hickson. IETF.</dd>
<dt id=refsMQ>[MQ]</dt>
<!--
Modified: index
===================================================================
--- index 2010-08-16 21:38:59 UTC (rev 5301)
+++ index 2010-08-16 21:47:15 UTC (rev 5302)
@@ -1319,7 +1319,7 @@
-->
<li><a href=http://dev.w3.org/html5/eventsource/>Server-sent Events</a>
<li><a href=http://dev.w3.org/html5/webdatabase/>Web SQL Database</a>
- <li><a href=http://tools.ietf.org/html/draft-abarth-mime-sniff>Content-Type Processing Model</a>
+ <li><a href=http://tools.ietf.org/html/draft-abarth-mime-sniff>Media Type Sniffing</a>
<li><a href=http://tools.ietf.org/html/draft-abarth-origin>The Web Origin Concept</a>
<li><a href=http://dev.w3.org/geo/api/spec-source.html>Geolocation API</a>
<li><a href=http://www.w3.org/TR/SVG/>SVG</a>
@@ -6373,27 +6373,27 @@
<p>The <dfn id=content-type title=Content-Type>Content-Type metadata</dfn> of a
resource must be obtained and interpreted in a manner consistent
- with the requirements of the Content-Type Processing Model
+ with the requirements of the Media Type Sniffing
specification. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p>The <dfn id=content-type-sniffing-0 title="Content-Type sniffing">sniffed type of a
resource</dfn> must be found in a manner consistent with the
- requirements given in the Content-Type Processing Model
+ requirements given in the Media Type Sniffing
specification for finding the <i>sniffed-type</i> of the relevant
sequence of octets. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing: image">rules for sniffing
images specifically</dfn> and the <dfn id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:
text or binary">rules for distingushing if a resource is text or
- binary</dfn> are also defined in the Content-Type Processing Model
+ binary</dfn> are also defined in the Media Type Sniffing
specification. Both sets of rules return a <a href=#mime-type>MIME type</a> as
their result. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p class=warning>It is imperative that the rules in the
- Content-Type Processing Model specification be followed
+ Media Type Sniffing specification be followed
exactly. When a user agent uses different heuristics for content
type detection than the server expects, security problems can
- occur. For more details, see the Content-Type Processing Model
+ occur. For more details, see the Media Type Sniffing
specification. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
<p>The <dfn id=algorithm-for-extracting-an-encoding-from-a-content-type>algorithm for extracting an encoding from a
@@ -84372,7 +84372,7 @@
<dl><dt>Magic number(s):</dt>
<dd>No sequence of bytes can uniquely identify an HTML
document. More information on detecting HTML documents is
- available in the Content-Type Processing Model specification. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></dd>
+ available in the Media Type Sniffing 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
@@ -88104,8 +88104,8 @@
N. Poppelier. W3C.</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.</dd>
+ <dd><cite><a href=http://tools.ietf.org/html/draft-abarth-mime-sniff>Media
+ Type Sniffing</a></cite>, A. Barth, I. Hickson. IETF.</dd>
<dt id=refsMQ>[MQ]</dt>
<!--
Modified: source
===================================================================
--- source 2010-08-16 21:38:59 UTC (rev 5301)
+++ source 2010-08-16 21:47:15 UTC (rev 5302)
@@ -109,7 +109,7 @@
-->
<li><a href="http://dev.w3.org/html5/eventsource/">Server-sent Events</a>
<li><a href="http://dev.w3.org/html5/webdatabase/">Web SQL Database</a>
- <li><a href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Content-Type Processing Model</a>
+ <li><a href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Media Type Sniffing</a>
<li><a href="http://tools.ietf.org/html/draft-abarth-origin">The Web Origin Concept</a>
<li><a href="http://dev.w3.org/geo/api/spec-source.html">Geolocation API</a>
<li><a href="http://www.w3.org/TR/SVG/">SVG</a>
@@ -6034,27 +6034,27 @@
<p>The <dfn title="Content-Type">Content-Type metadata</dfn> of a
resource must be obtained and interpreted in a manner consistent
- with the requirements of the Content-Type Processing Model
+ with the requirements of the Media Type Sniffing
specification. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
<p>The <dfn title="Content-Type sniffing">sniffed type of a
resource</dfn> must be found in a manner consistent with the
- requirements given in the Content-Type Processing Model
+ requirements given in the Media Type Sniffing
specification for finding the <i>sniffed-type</i> of the relevant
sequence of octets. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
<p>The <dfn title="Content-Type sniffing: image">rules for sniffing
images specifically</dfn> and the <dfn title="Content-Type sniffing:
text or binary">rules for distingushing if a resource is text or
- binary</dfn> are also defined in the Content-Type Processing Model
+ binary</dfn> are also defined in the Media Type Sniffing
specification. Both sets of rules return a <span>MIME type</span> as
their result. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
<p class="warning">It is imperative that the rules in the
- Content-Type Processing Model specification be followed
+ Media Type Sniffing specification be followed
exactly. When a user agent uses different heuristics for content
type detection than the server expects, security problems can
- occur. For more details, see the Content-Type Processing Model
+ occur. For more details, see the Media Type Sniffing
specification. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
<p>The <dfn>algorithm for extracting an encoding from a
@@ -104251,7 +104251,7 @@
<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
+ available in the Media Type Sniffing specification. <a
href="#refsMIMESNIFF">[MIMESNIFF]</a></dd>
<dt>File extension(s):</dt>
<dd>"<code title="">html</code>" and "<code title="">htm</code>"
@@ -108807,8 +108807,8 @@
<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.</dd>
+ href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Media
+ Type Sniffing</a></cite>, A. Barth, I. Hickson. IETF.</dd>
<dt id="refsMQ">[MQ]</dt>
<!--
More information about the Commit-Watchers
mailing list