hixie: Be more pedantic about 'codecs'. (whatwg r5544)

hixie: Be more pedantic about 'codecs'. (whatwg r5544)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4430&r2=1.4431&f=h
http://html5.org/tools/web-apps-tracker?from=5543&to=5544

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4430
retrieving revision 1.4431
diff -u -d -r1.4430 -r1.4431
--- Overview.html 28 Sep 2010 23:56:50 -0000 1.4430
+++ Overview.html 29 Sep 2010 00:07:54 -0000 1.4431
@@ -313,7 +313,7 @@
 
    <h1>HTML5</h1>
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-28-september-2010">Editor's Draft 28 September 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-29-september-2010">Editor's Draft 29 September 2010</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -419,7 +419,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 28 September 2010 Editor's Draft.
+  This specification is the 29 September 2010 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
   actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
   group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -20935,8 +20935,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><div class="example">
+  parameter, which certain MIME types define, might be necessary to
+  specify exactly how the resource is encoded. <a href="#refsRFC4281">[RFC4281]</a><div class="example">
 
    <p>The following list shows some examples of how to use the <code title="">codecs=</code> MIME parameter in the <code title="attr-source-type"><a href="#attr-source-type">type</a></code> attribute.</p>
 
@@ -21258,8 +21258,9 @@
   resource</a>, the <code title="attr-media-src"><a href="#attr-media-src">src</a></code>
   attribute, or <code><a href="#the-source-element">source</a></code> elements. The attribute overrides
   the elements.<h5 id="mime-types"><span class="secno">4.8.9.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>Types are usually somewhat incomplete descriptions; for example
+  <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>Types are usually somewhat incomplete descriptions; for example
   "<code title="">video/mpeg</code>" doesn't say anything except what
   the container type is, and even a type like "<code title="">video/mp4; codecs="avc1.42E01E,
   mp4a.40.2"</code>" doesn't include information like the actual
@@ -21280,7 +21281,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>.<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>
+  <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.<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>
 
    <dd>
 
@@ -21301,7 +21303,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><div class="example">
 
@@ -21670,10 +21673,10 @@
 
      <li><p>&#8987; 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>&#8987; 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
@@ -21831,10 +21834,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

Received on Wednesday, 29 September 2010 00:08:51 UTC