[html5] r7048 - [e] (0) Yet more polishing of the media timeline phraseology. Affected topics: V [...]

whatwg at whatwg.org whatwg at whatwg.org
Wed Apr 4 11:56:03 PDT 2012


Author: ianh
Date: 2012-04-04 11:56:01 -0700 (Wed, 04 Apr 2012)
New Revision: 7048

Modified:
   complete.html
   index
   source
Log:
[e] (0) Yet more polishing of the media timeline phraseology.
Affected topics: Video and Audio

Modified: complete.html
===================================================================
--- complete.html	2012-04-03 17:07:40 UTC (rev 7047)
+++ complete.html	2012-04-04 18:56:01 UTC (rev 7048)
@@ -240,7 +240,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 3 April 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 4 April 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -29382,14 +29382,15 @@
   <p><dfn id=defineTimeline title="establish the media
   timeline">Establishing the media timeline</dfn>: If the <a href=#media-resource>media
   resource</a> somehow specifies an explicit timeline whose origin
-  is not negative, then the <a href=#media-timeline>media timeline</a> should be that
-  timeline. (Whether the <a href=#media-resource>media resource</a> can specify a
-  timeline or not depends on the <a href=#media-resource title="media resource">media
-  resource's</a> format.) If the <a href=#media-resource>media resource</a>
-  specifies an explicit start time <em>and date</em>, then that time
-  and date should be considered the zero point in the <a href=#media-timeline>media
-  timeline</a>; the <a href=#timeline-offset>timeline offset</a> will be the time
-  and date, exposed using the <code title=dom-media-startDate><a href=#dom-media-startdate>startDate</a></code> attribute.</p>
+  is not negative (i.e. gives each frame a specific time offset and
+  gives the first frame a zero or positive offset), then the
+  <a href=#media-timeline>media timeline</a> should be that timeline. (Whether the
+  <a href=#media-resource>media resource</a> can specify a timeline or not depends on
+  the <a href=#media-resource title="media resource">media resource's</a> format.) If
+  the <a href=#media-resource>media resource</a> specifies an explicit start time
+  <em>and date</em>, then that time and date should be considered the
+  zero point in the <a href=#media-timeline>media timeline</a>; the <a href=#timeline-offset>timeline
+  offset</a> will be the time and date, exposed using the <code title=dom-media-startDate><a href=#dom-media-startdate>startDate</a></code> attribute.</p>
 
   <p>If the <a href=#media-resource>media resource</a> has a discontinuous timeline,
   the user agent must extend the timeline used at the start of the
@@ -29410,26 +29411,28 @@
   have an explicit timeline, the zero time on the <a href=#media-timeline>media
   timeline</a> should correspond to the first frame of the
   <a href=#media-resource>media resource</a>. In the even rarer case of a <a href=#media-resource>media
-  resource</a> with no explicit timings ofd any kind, the user
-  agent must determine the time for each frame.</p>
+  resource</a> with no explicit timings of any kind, not even frame
+  durations, the user agent must itself determine the time for each
+  frame in a user-agent-defined manner.</p>
 
   <p class=note>An example of a file format with no explicit
-  timeline but with explicit timings is the Animated GIF format. An
-  example of a file format with no explicit timings at all is the
-  JPEG-push format (<code title="">multipart/x-mixed-replace</code>
-  with JPEG frames, often used as the format for MJPEG streams).</p>
+  timeline but with explicit frame durations is the Animated GIF
+  format. An example of a file format with no explicit timings at all
+  is the JPEG-push format (<code title="">multipart/x-mixed-replace</code> with JPEG frames, often
+  used as the format for MJPEG streams).</p>
 
-  <p>If, even in the absence of timing information, the user agent
-  will be able to seek to an earlier point than the first frame
-  originally provided by the server, then the zero time should
-  correspond to the earliest seekable time of the <a href=#media-resource>media
-  resource</a>; otherwise, it should correspond to the first frame
-  received from the server (the point in the <a href=#media-resource>media
+  <p>If, in the case of a resource with no timing information, the
+  user agent will nonetheless be able to seek to an earlier point than
+  the first frame originally provided by the server, then the zero
+  time should correspond to the earliest seekable time of the
+  <a href=#media-resource>media resource</a>; otherwise, it should correspond to the
+  first frame received from the server (the point in the <a href=#media-resource>media
   resource</a> at which the user agent began receiving the
   stream).</p>
 
-  <p class=note>At the time of writing, no format without an
-  explicit <a href=#media-timeline>media timeline</a> supported seeking.</p>
+  <p class=note>At the time of writing, there is no known format
+  that lacks explicit frame time offsets yet still supports seeking to
+  a frame before the first frame sent by the server.</p>
 
   <div class=example>
 

Modified: index
===================================================================
--- index	2012-04-03 17:07:40 UTC (rev 7047)
+++ index	2012-04-04 18:56:01 UTC (rev 7048)
@@ -240,7 +240,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 3 April 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 4 April 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -29382,14 +29382,15 @@
   <p><dfn id=defineTimeline title="establish the media
   timeline">Establishing the media timeline</dfn>: If the <a href=#media-resource>media
   resource</a> somehow specifies an explicit timeline whose origin
-  is not negative, then the <a href=#media-timeline>media timeline</a> should be that
-  timeline. (Whether the <a href=#media-resource>media resource</a> can specify a
-  timeline or not depends on the <a href=#media-resource title="media resource">media
-  resource's</a> format.) If the <a href=#media-resource>media resource</a>
-  specifies an explicit start time <em>and date</em>, then that time
-  and date should be considered the zero point in the <a href=#media-timeline>media
-  timeline</a>; the <a href=#timeline-offset>timeline offset</a> will be the time
-  and date, exposed using the <code title=dom-media-startDate><a href=#dom-media-startdate>startDate</a></code> attribute.</p>
+  is not negative (i.e. gives each frame a specific time offset and
+  gives the first frame a zero or positive offset), then the
+  <a href=#media-timeline>media timeline</a> should be that timeline. (Whether the
+  <a href=#media-resource>media resource</a> can specify a timeline or not depends on
+  the <a href=#media-resource title="media resource">media resource's</a> format.) If
+  the <a href=#media-resource>media resource</a> specifies an explicit start time
+  <em>and date</em>, then that time and date should be considered the
+  zero point in the <a href=#media-timeline>media timeline</a>; the <a href=#timeline-offset>timeline
+  offset</a> will be the time and date, exposed using the <code title=dom-media-startDate><a href=#dom-media-startdate>startDate</a></code> attribute.</p>
 
   <p>If the <a href=#media-resource>media resource</a> has a discontinuous timeline,
   the user agent must extend the timeline used at the start of the
@@ -29410,26 +29411,28 @@
   have an explicit timeline, the zero time on the <a href=#media-timeline>media
   timeline</a> should correspond to the first frame of the
   <a href=#media-resource>media resource</a>. In the even rarer case of a <a href=#media-resource>media
-  resource</a> with no explicit timings ofd any kind, the user
-  agent must determine the time for each frame.</p>
+  resource</a> with no explicit timings of any kind, not even frame
+  durations, the user agent must itself determine the time for each
+  frame in a user-agent-defined manner.</p>
 
   <p class=note>An example of a file format with no explicit
-  timeline but with explicit timings is the Animated GIF format. An
-  example of a file format with no explicit timings at all is the
-  JPEG-push format (<code title="">multipart/x-mixed-replace</code>
-  with JPEG frames, often used as the format for MJPEG streams).</p>
+  timeline but with explicit frame durations is the Animated GIF
+  format. An example of a file format with no explicit timings at all
+  is the JPEG-push format (<code title="">multipart/x-mixed-replace</code> with JPEG frames, often
+  used as the format for MJPEG streams).</p>
 
-  <p>If, even in the absence of timing information, the user agent
-  will be able to seek to an earlier point than the first frame
-  originally provided by the server, then the zero time should
-  correspond to the earliest seekable time of the <a href=#media-resource>media
-  resource</a>; otherwise, it should correspond to the first frame
-  received from the server (the point in the <a href=#media-resource>media
+  <p>If, in the case of a resource with no timing information, the
+  user agent will nonetheless be able to seek to an earlier point than
+  the first frame originally provided by the server, then the zero
+  time should correspond to the earliest seekable time of the
+  <a href=#media-resource>media resource</a>; otherwise, it should correspond to the
+  first frame received from the server (the point in the <a href=#media-resource>media
   resource</a> at which the user agent began receiving the
   stream).</p>
 
-  <p class=note>At the time of writing, no format without an
-  explicit <a href=#media-timeline>media timeline</a> supported seeking.</p>
+  <p class=note>At the time of writing, there is no known format
+  that lacks explicit frame time offsets yet still supports seeking to
+  a frame before the first frame sent by the server.</p>
 
   <div class=example>
 

Modified: source
===================================================================
--- source	2012-04-03 17:07:40 UTC (rev 7047)
+++ source	2012-04-04 18:56:01 UTC (rev 7048)
@@ -31906,14 +31906,15 @@
   <p><dfn id="defineTimeline" title="establish the media
   timeline">Establishing the media timeline</dfn>: If the <span>media
   resource</span> somehow specifies an explicit timeline whose origin
-  is not negative, then the <span>media timeline</span> should be that
-  timeline. (Whether the <span>media resource</span> can specify a
-  timeline or not depends on the <span title="media resource">media
-  resource's</span> format.) If the <span>media resource</span>
-  specifies an explicit start time <em>and date</em>, then that time
-  and date should be considered the zero point in the <span>media
-  timeline</span>; the <span>timeline offset</span> will be the time
-  and date, exposed using the <code
+  is not negative (i.e. gives each frame a specific time offset and
+  gives the first frame a zero or positive offset), then the
+  <span>media timeline</span> should be that timeline. (Whether the
+  <span>media resource</span> can specify a timeline or not depends on
+  the <span title="media resource">media resource's</span> format.) If
+  the <span>media resource</span> specifies an explicit start time
+  <em>and date</em>, then that time and date should be considered the
+  zero point in the <span>media timeline</span>; the <span>timeline
+  offset</span> will be the time and date, exposed using the <code
   title="dom-media-startDate">startDate</code> attribute.</p>
 
   <p>If the <span>media resource</span> has a discontinuous timeline,
@@ -31935,26 +31936,29 @@
   have an explicit timeline, the zero time on the <span>media
   timeline</span> should correspond to the first frame of the
   <span>media resource</span>. In the even rarer case of a <span>media
-  resource</span> with no explicit timings ofd any kind, the user
-  agent must determine the time for each frame.</p>
+  resource</span> with no explicit timings of any kind, not even frame
+  durations, the user agent must itself determine the time for each
+  frame in a user-agent-defined manner.</p>
 
   <p class="note">An example of a file format with no explicit
-  timeline but with explicit timings is the Animated GIF format. An
-  example of a file format with no explicit timings at all is the
-  JPEG-push format (<code title="">multipart/x-mixed-replace</code>
-  with JPEG frames, often used as the format for MJPEG streams).</p>
+  timeline but with explicit frame durations is the Animated GIF
+  format. An example of a file format with no explicit timings at all
+  is the JPEG-push format (<code
+  title="">multipart/x-mixed-replace</code> with JPEG frames, often
+  used as the format for MJPEG streams).</p>
 
-  <p>If, even in the absence of timing information, the user agent
-  will be able to seek to an earlier point than the first frame
-  originally provided by the server, then the zero time should
-  correspond to the earliest seekable time of the <span>media
-  resource</span>; otherwise, it should correspond to the first frame
-  received from the server (the point in the <span>media
+  <p>If, in the case of a resource with no timing information, the
+  user agent will nonetheless be able to seek to an earlier point than
+  the first frame originally provided by the server, then the zero
+  time should correspond to the earliest seekable time of the
+  <span>media resource</span>; otherwise, it should correspond to the
+  first frame received from the server (the point in the <span>media
   resource</span> at which the user agent began receiving the
   stream).</p>
 
-  <p class="note">At the time of writing, no format without an
-  explicit <span>media timeline</span> supported seeking.</p>
+  <p class="note">At the time of writing, there is no known format
+  that lacks explicit frame time offsets yet still supports seeking to
+  a frame before the first frame sent by the server.</p>
 
   <div class="example">
 




More information about the Commit-Watchers mailing list