html5/spec acknowledgements.html,1.1039,1.1040 spec.html,1.1248,1.1249 video.html,1.890,1.891 from Michael Smith via cvs-syncmail on 2010-09-29 (public-html-commits@w3.org from September 2010)

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 29 Sep 2010 00:16:36 +0000
To: public-html-commits@w3.org
Message-Id: <E1P0kLc-0003zd-TQ@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv15327

Modified Files:
	acknowledgements.html spec.html video.html 
Log Message:
Be more pedantic about 'codecs'. (whatwg r5544)

[updated by splitter]


Index: acknowledgements.html
===================================================================
RCS file: /sources/public/html5/spec/acknowledgements.html,v
retrieving revision 1.1039
retrieving revision 1.1040
diff -u -d -r1.1039 -r1.1040
--- acknowledgements.html	24 Sep 2010 22:16:41 -0000	1.1039
+++ acknowledgements.html	29 Sep 2010 00:16:34 -0000	1.1040
@@ -673,6 +673,7 @@
   Martin D&#252;rst,
   Martin Honnen,
   Martin Kutschker,
+  Martin Nilsson,
   Martin Thomson,
   Masataka Yakura,
   Mathieu Henri,

Index: video.html
===================================================================
RCS file: /sources/public/html5/spec/video.html,v
retrieving revision 1.890
retrieving revision 1.891
diff -u -d -r1.890 -r1.891
--- video.html	24 Sep 2010 22:16:49 -0000	1.890
+++ video.html	29 Sep 2010 00:16:34 -0000	1.891
@@ -724,8 +724,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="infrastructure.html#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="references.html#refsRFC4281">[RFC4281]</a></p><div class="example">
+  parameter, which certain MIME types define, might be necessary to
+  specify exactly how the resource is encoded. <a href="references.html#refsRFC4281">[RFC4281]</a></p><div class="example">
 
    <p>The following list shows some examples of how to use the <code title="">codecs=</code> MIME parameter in the <code title="attr-source-type"><a href="#attr-source-type">type</a></code> attribute.</p>
 
@@ -1047,8 +1047,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.</p><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="infrastructure.html#mime-type">MIME type</a>, optionally
-  with a <code title="">codecs</code> parameter. <a href="references.html#refsRFC4281">[RFC4281]</a></p><p>Types are usually somewhat incomplete descriptions; for example
+  <em>type</em>, specifically a <a href="infrastructure.html#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="references.html#refsRFC4281">[RFC4281]</a></p><p>Types are usually somewhat incomplete descriptions; for example
   "<code title="">video/mpeg</code>" doesn't say anything except what
   the container type is, and even a type like "<code title="">video/mp4; codecs="avc1.42E01E,
   mp4a.40.2"</code>" doesn't include information like the actual
@@ -1069,7 +1070,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><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.</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>
 
    <dd>
 
@@ -1090,7 +1092,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">
 
@@ -1459,10 +1462,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="infrastructure.html#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="webappapis.html#synchronous-section">synchronous section</a>, 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 <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="webappapis.html#synchronous-section">synchronous section</a>, and jump down to the <i title="">failed</i> step below.</p></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="common-microsyntaxes.html#matches-the-environment" title="matches the environment">match the
@@ -1620,10 +1623,10 @@
 
      <dt>If the <a href="#media-resource">media resource</a> is found to have <a href="fetching-resources.html#content-type" title="Content-Type">Content-Type metadata</a> that, when
      parsed as a <a href="infrastructure.html#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

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1248
retrieving revision 1.1249
diff -u -d -r1.1248 -r1.1249
--- spec.html	28 Sep 2010 23:47:03 -0000	1.1248
+++ spec.html	29 Sep 2010 00:16:34 -0000	1.1249
@@ -317,7 +317,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>
@@ -338,7 +338,7 @@
     <a href="Overview.html">single page HTML</a>,
     <a href="spec.html">multipage HTML</a>,
     <a href="author/">web developer edition</a>.
-This is revision 1.4429.
+This is revision 1.4431.
    </p> 
      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2010 <a href="http://www.w3.org/"><abbr title="World Wide
@@ -423,7 +423,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
Received on Wednesday, 29 September 2010 00:16:38 UTC