[html5] r5544 - [e] (0) Be more pedantic about 'codecs'. Fixing http://www.w3.org/Bugs/Public/sh [...]

whatwg at whatwg.org whatwg at whatwg.org
Tue Sep 28 17:07:51 PDT 2010


Author: ianh
Date: 2010-09-28 17:07:50 -0700 (Tue, 28 Sep 2010)
New Revision: 5544

Modified:
   complete.html
   index
   source
Log:
[e] (0) Be more pedantic about 'codecs'.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10202

Modified: complete.html
===================================================================
--- complete.html	2010-09-28 23:56:14 UTC (rev 5543)
+++ complete.html	2010-09-29 00:07:50 UTC (rev 5544)
@@ -211,7 +211,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Draft Standard — 28 September 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard — 29 September 2010</h2>
    </hgroup><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>-->
@@ -24212,8 +24212,8 @@
   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 <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>
+  parameter, which certain MIME types define, might be necessary to
+  specify exactly how the resource is encoded. <a href=#refsRFC4281>[RFC4281]</a></p>
 
   <div class=example>
 
@@ -24750,8 +24750,9 @@
   <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 <a href=#mime-type>MIME type</a>, optionally
-  with a <code title="">codecs</code> parameter. <a href=#refsRFC4281>[RFC4281]</a></p>
+  <em>type</em>, specifically a <a href=#mime-type>MIME type</a>, in some cases
+  with a <code title="">codecs</code> parameter. (Whether the <code title="">codecs</code> parameter is allowed or not depends on the
+  MIME type.) <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
@@ -24780,7 +24781,8 @@
   "<code>application/octet-stream</code>" when used <em>with</em>
   parameters, e.g.
   "<code>application/octet-stream;codecs=theora</code>", <em>is</em>
-  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>.</p>
+  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>,
+  since that parameter is not defined for that type.</p>
 
   <dl class=domintro><dt><var title="">media</var> . <code title=dom-navigator-canPlayType><a href=#dom-navigator-canplaytype>canPlayType</a></code>(<var title="">type</var>)</dt>
 
@@ -24803,7 +24805,8 @@
   and it must return "<code title="">maybe</code>" otherwise.
   Implementors are encouraged to return "<code title="">maybe</code>"
   unless the type can be confidently established as being supported or
-  not. Generally, a user agent should never return "<code title="">probably</code>" if the type doesn't have a <code title="">codecs</code> parameter.</p>
+  not. Generally, a user agent should never return "<code title="">probably</code>" for a type that allows the <code title="">codecs</code> parameter if that parameter is not
+  present.</p>
 
   </div>
 
@@ -25198,10 +25201,10 @@
 
      <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 <a href=#mime-type>MIME type</a> (including any codecs
-     described by the <code title="">codecs</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>
+     described by the <code title="">codecs</code> parameter, for
+     types that define that 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>
 
      <li><p>⌛ If <var title="">candidate</var> has a <code title=attr-source-media><a href=#attr-source-media>media</a></code> attribute whose value does
      not <a href=#matches-the-environment title="matches the environment">match the
@@ -25363,10 +25366,10 @@
 
      <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 <a href=#mime-type>MIME type</a> (including any codecs
-     described by the <code title="">codecs</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>
+     described by the <code title="">codecs</code> parameter, if the
+     parameter is defined for that type), 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>
 
      <dt>If the <a href=#media-data>media data</a> can be fetched but is found by
      inspection to be in an unsupported format, or can otherwise not

Modified: index
===================================================================
--- index	2010-09-28 23:56:14 UTC (rev 5543)
+++ index	2010-09-29 00:07:50 UTC (rev 5544)
@@ -215,7 +215,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>HTML5 (including next generation additions still in development)</h1>
-    <h2 class="no-num no-toc">Draft Standard — 28 September 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard — 29 September 2010</h2>
    </hgroup><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>-->
@@ -24192,8 +24192,8 @@
   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 <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>
+  parameter, which certain MIME types define, might be necessary to
+  specify exactly how the resource is encoded. <a href=#refsRFC4281>[RFC4281]</a></p>
 
   <div class=example>
 
@@ -24730,8 +24730,9 @@
   <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 <a href=#mime-type>MIME type</a>, optionally
-  with a <code title="">codecs</code> parameter. <a href=#refsRFC4281>[RFC4281]</a></p>
+  <em>type</em>, specifically a <a href=#mime-type>MIME type</a>, in some cases
+  with a <code title="">codecs</code> parameter. (Whether the <code title="">codecs</code> parameter is allowed or not depends on the
+  MIME type.) <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
@@ -24760,7 +24761,8 @@
   "<code>application/octet-stream</code>" when used <em>with</em>
   parameters, e.g.
   "<code>application/octet-stream;codecs=theora</code>", <em>is</em>
-  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>.</p>
+  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>,
+  since that parameter is not defined for that type.</p>
 
   <dl class=domintro><dt><var title="">media</var> . <code title=dom-navigator-canPlayType><a href=#dom-navigator-canplaytype>canPlayType</a></code>(<var title="">type</var>)</dt>
 
@@ -24783,7 +24785,8 @@
   and it must return "<code title="">maybe</code>" otherwise.
   Implementors are encouraged to return "<code title="">maybe</code>"
   unless the type can be confidently established as being supported or
-  not. Generally, a user agent should never return "<code title="">probably</code>" if the type doesn't have a <code title="">codecs</code> parameter.</p>
+  not. Generally, a user agent should never return "<code title="">probably</code>" for a type that allows the <code title="">codecs</code> parameter if that parameter is not
+  present.</p>
 
   </div>
 
@@ -25178,10 +25181,10 @@
 
      <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 <a href=#mime-type>MIME type</a> (including any codecs
-     described by the <code title="">codecs</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>
+     described by the <code title="">codecs</code> parameter, for
+     types that define that 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>
 
      <li><p>⌛ If <var title="">candidate</var> has a <code title=attr-source-media><a href=#attr-source-media>media</a></code> attribute whose value does
      not <a href=#matches-the-environment title="matches the environment">match the
@@ -25343,10 +25346,10 @@
 
      <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 <a href=#mime-type>MIME type</a> (including any codecs
-     described by the <code title="">codecs</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>
+     described by the <code title="">codecs</code> parameter, if the
+     parameter is defined for that type), 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>
 
      <dt>If the <a href=#media-data>media data</a> can be fetched but is found by
      inspection to be in an unsupported format, or can otherwise not

Modified: source
===================================================================
--- source	2010-09-28 23:56:14 UTC (rev 5543)
+++ source	2010-09-29 00:07:50 UTC (rev 5544)
@@ -26003,8 +26003,8 @@
   the user agent determine if it can play this <span>media
   resource</span> before fetching it. If specified, its value must be
   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
+  parameter, which certain MIME types define, might be necessary to
+  specify exactly how the resource is encoded. <a
   href="#refsRFC4281">[RFC4281]</a></p>
 
   <div class="example">
@@ -26613,9 +26613,10 @@
   <h5>MIME types</h5>
 
   <p>A <span>media resource</span> can be described in terms of its
-  <em>type</em>, specifically a <span>MIME type</span>, optionally
-  with a <code title="">codecs</code> parameter. <a
-  href="#refsRFC4281">[RFC4281]</a></p>
+  <em>type</em>, specifically a <span>MIME type</span>, in some cases
+  with a <code title="">codecs</code> parameter. (Whether the <code
+  title="">codecs</code> parameter is allowed or not depends on the
+  MIME type.) <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
@@ -26645,7 +26646,8 @@
   "<code>application/octet-stream</code>" when used <em>with</em>
   parameters, e.g.
   "<code>application/octet-stream;codecs=theora</code>", <em>is</em>
-  <span>a type that the user agent knows it cannot render</span>.</p>
+  <span>a type that the user agent knows it cannot render</span>,
+  since that parameter is not defined for that type.</p>
 
   <dl class="domintro">
 
@@ -26675,8 +26677,9 @@
   Implementors are encouraged to return "<code title="">maybe</code>"
   unless the type can be confidently established as being supported or
   not. Generally, a user agent should never return "<code
-  title="">probably</code>" if the type doesn't have a <code
-  title="">codecs</code> parameter.</p>
+  title="">probably</code>" for a type that allows the <code
+  title="">codecs</code> parameter if that parameter is not
+  present.</p>
 
   </div>
 
@@ -27162,10 +27165,11 @@
      <li><p>&#x231B; If <var title="">candidate</var> has a <code
      title="attr-source-type">type</code> attribute whose value, when
      parsed as a <span>MIME type</span> (including any codecs
-     described by the <code title="">codecs</code> parameter),
-     represents <span>a type that the user agent knows it cannot
-     render</span>, then end the <span>synchronous section</span>, and
-     jump down to the <i title="">failed</i> step below.</p></li>
+     described by the <code title="">codecs</code> parameter, for
+     types that define that parameter), represents <span>a type that
+     the user agent knows it cannot render</span>, then end the
+     <span>synchronous section</span>, and jump down to the <i
+     title="">failed</i> step below.</p></li>
 
      <li><p>&#x231B; If <var title="">candidate</var> has a <code
      title="attr-source-media">media</code> attribute whose value does
@@ -27360,10 +27364,10 @@
      <dt>If the <span>media resource</span> is found to have <span
      title="Content-Type">Content-Type metadata</span> that, when
      parsed as a <span>MIME type</span> (including any codecs
-     described by the <code title="">codecs</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>
+     described by the <code title="">codecs</code> parameter, if the
+     parameter is defined for that type), represents <span>a type that
+     the user agent knows it cannot render</span> (even if the actual
+     <span>media data</span> is in a supported format)</dt>
 
      <dt>If the <span>media data</span> can be fetched but is found by
      inspection to be in an unsupported format, or can otherwise not




More information about the Commit-Watchers mailing list