[imsc] addresses ISSUE-308
authorpal@sandflow.org
Wed, 21 May 2014 16:25:37 -0700
changeset 623 ea1a92310a27
parent 622 620ec029015f
child 624 5abd8c68ee6e
[imsc] addresses ISSUE-308
[imsc] addresses part of ISSUE-311
ttml-ww-profiles/ttml-ww-profiles.html
ttml-ww-profiles/ttml-ww-profiles.source.html
--- a/ttml-ww-profiles/ttml-ww-profiles.html	Wed May 21 16:46:47 2014 +0900
+++ b/ttml-ww-profiles/ttml-ww-profiles.html	Wed May 21 16:25:37 2014 -0700
@@ -217,11 +217,11 @@
   </p>
   <h1 class="title p-name" id="title" property="dcterms:title">TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0</h1>
   
-  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-04-24T21:32:01.000Z" id="w3c-first-public-working-draft-24-april-2014"><abbr title="World Wide Web Consortium">W3C</abbr> First Public Working Draft <time class="dt-published" datetime="2014-04-24">24 April 2014</time></h2>
+  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-05-22T06:21:11.000Z" id="w3c-first-public-working-draft-21-may-2014"><abbr title="World Wide Web Consortium">W3C</abbr> First Public Working Draft <time class="dt-published" datetime="2014-05-21">21 May 2014</time></h2>
   <dl>
     
       <dt>This version:</dt>
-      <dd><a class="u-url" href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140424/">http://www.w3.org/TR/2014/WD-ttml-imsc1-20140424/</a></dd>
+      <dd><a class="u-url" href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140521/">http://www.w3.org/TR/2014/WD-ttml-imsc1-20140521/</a></dd>
       <dt>Latest published version:</dt>
       <dd><a href="http://www.w3.org/TR/ttml-imsc1/">http://www.w3.org/TR/ttml-imsc1/</a></dd>
     
@@ -294,7 +294,7 @@
           
           
             If you wish to make comments regarding this document, please send them to 
-            <a href="mailto:[email protected]?subject=%5Bimsc%5D">[email protected]</a> 
+            <a href="mailto:[email protected]?subject=[imsc]">[email protected]</a> 
             (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
             <a href="http://lists.w3.org/Archives/Public/public-tt/">archives</a>)
               with <code>[imsc]</code> at the start of your email's subject.
@@ -491,8 +491,8 @@
     <section id="related-video-object">
       <h3 aria-level="2" role="heading" id="h3_related-video-object"><span class="secno">4.3 </span>Related Video Object</h3>
 
-      <p>A subtitle document <em class="rfc2119" title="MAY">MAY</em> be associated with a related video object, which <em class="rfc2119" title="SHALL">SHALL</em> consist of a sequence of frames, each a
-      rectangular array of pixels.</p>
+      <p>A subtitle document <em class="rfc2119" title="MAY">MAY</em> be associated with a related video object, which <em class="rfc2119" title="SHALL">SHALL</em> consist of a sequence of image frames, each a
+      rectangular array of pixels, and <em class="rfc2119" title="SHALL">SHALL</em> be considered the <em>Related Media Object</em> defined in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>].</p>
     </section>
 
     <section id="synchronization">
@@ -504,13 +504,17 @@
       <p>A media time expression M <em class="rfc2119" title="SHALL">SHALL</em> correspond to the frame of the related video object with the presentation time that is the
       closest to, but not less, than M.</p>
 
-      <p>If <code>ttp:frameRate</code> is specified, then the product of <code>ttp:frameRate</code> and
-      <code>ttp:frameRateMultiplier</code> <em class="rfc2119" title="SHALL">SHALL</em> be the frame rate of the related video object.</p>
-
       <aside class="example"><div class="example-title"><span>Example 1</span></div>
         A media time expression of 00:00:05.1 corresponds to frame ceiling(5.1 × ( 1000 / 1001 × 30) = 153 of a related video
         object with a frame rate of 1000 / 1001 × 30 ≈ 29.97.
       </aside>
+	  
+	  <p>If <code>ttp:frameRate</code> is specified, then the product of <code>ttp:frameRate</code> and
+      <code>ttp:frameRateMultiplier</code> <em class="rfc2119" title="SHALL">SHALL</em> be the frame rate of the related video object.</p>
+	  
+	    <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_1"><span>Note</span></div><p class="">
+        A document can be made independent of the frame rate of the related video object by never using the <em>frames</em> term in a time expression: as specified in <a href="#common-features" class="sec-ref"><span class="secno">4.8</span> <span class="sec-title">Features</span></a>, <code>ttp:frameRate</code> is required only if the document includes one or more time expressions that uses the <em>frames</em> term.
+      </p></div>
     </section>
 
     <section id="extensions">
@@ -551,7 +555,7 @@
 
         <p><code>ttp:aspectRatio</code> <em class="rfc2119" title="SHALL NOT">SHALL NOT</em> be present if <code>tts:extent</code> is present.<br></p>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_1"><span>Note</span></div><p class="">As specified in Section <a href="#common-features" class="sec-ref"><span class="secno">4.8</span> <span class="sec-title">Features</span></a>, <code>tts:extent</code> is present if the <code>px</code>
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_2"><span>Note</span></div><p class="">As specified in Section <a href="#common-features" class="sec-ref"><span class="secno">4.8</span> <span class="sec-title">Features</span></a>, <code>tts:extent</code> is present if the <code>px</code>
         length measure is used anywhere within the document.</p></div>
 
         <p>Integer pixel positions on the related video object frame computed from real percentage length values <em class="rfc2119" title="SHALL">SHALL</em> use half-up
@@ -598,8 +602,8 @@
         <p>A <code>ttp:progressivelyDecodable</code> attribute is considered to be significant only when specified on the
         <code>tt</code> element.</p>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_2"><span>Note</span></div><p class="">The placement and use of <code>div</code>, <code>region</code> and <code>span</code> that contain time
-        attributes, and (ii) the use of <code>set</code>.</p></div>
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_3"><span>Note</span></div><p class="">The placement and use of <code>div</code>, <code>region</code> and <code>span</code> that contain time
+        attributes, and the use of <code>set</code> are constrained when <code>ttp:progressivelyDecodable="true"</code> .</p></div>
       </section>
 
       <section id="tts-forcedDisplay" typeof="bibo:Chapter" resource="#tts-forcedDisplay" rel="bibo:Chapter">
@@ -654,7 +658,7 @@
           </tbody>
         </table>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_3"><span>Note</span></div><p class="">Although <code>tts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_4"><span>Note</span></div><p class="">Although <code>tts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
         <code>br</code> content element, forcedDisplayMode will apply to a <code>br</code> content element if it is either defined
         on an ancestor content element of the <code>br</code> content element or it is applied to a region element corresponding to
         a region that the <code>br</code> content element is being flowed into.</p></div>
@@ -685,7 +689,7 @@
           </li>
         </ol>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_4"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], the initial value of <code>tts:opacity</code> is "1.0", the initial
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_5"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], the initial value of <code>tts:opacity</code> is "1.0", the initial
         value of <code>tts:showBackground</code> is "always", and the initial value of <code>tts:display</code> is
         "auto"</p></div>
       </section>
@@ -810,7 +814,7 @@
           <tr>
             <td><code>#frameRate</code></td>
 
-            <td>If the document includes any time expression that uses the frame field, the <code>ttp:frameRate</code> attribute
+            <td>If the document includes any time expression that uses the <em>frames</em> term, the <code>ttp:frameRate</code> attribute
             <em class="rfc2119" title="SHALL">SHALL</em> be present on the <code>tt</code> element.</td>
           </tr>
 
@@ -1143,7 +1147,7 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_5"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], a <code>#time-offset-with-frames</code> expression is translated to a media time
+      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_6"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], a <code>#time-offset-with-frames</code> expression is translated to a media time
       M according to M = 3600 · hours + 60 · minutes + seconds + (frames ÷ (<code>ttp:frameRateMultiplier</code> ·
       <code>ttp:frameRate</code>)).</p></div>
     </section>
@@ -1792,7 +1796,7 @@
         P<sub>n-1</sub> at the presentation time of intermediate synchronic document E<sub>n</sub>, making the latter available for
         display.</p>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_6"><span>Note</span></div><p class="">It is possible for the contents of Presentation Buffer P<sub>n-1</sub> to never be displayed. This can
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_7"><span>Note</span></div><p class="">It is possible for the contents of Presentation Buffer P<sub>n-1</sub> to never be displayed. This can
         happen if Presentation Buffer P<sub>n</sub> is copied twice to Presentation Buffer P<sub>n-1</sub> between two consecutive
         video frame boundaries of the related video object.</p></div>
 
@@ -1825,11 +1829,11 @@
           </tbody>
         </table>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_7"><span>Note</span></div><p class="">BDraw effectively sets a limit on fillings regions - for example, assuming that the root container is
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_8"><span>Note</span></div><p class="">BDraw effectively sets a limit on fillings regions - for example, assuming that the root container is
         ultimately rendered at 1920×1080 resolution, a BDraw of 12 s<sup>-1</sup> would correspond to a fill rate of
         1920×1080×12/s=23.7×2<sup>20</sup>pixels s<sup>-1</sup>.</p></div>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_8"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given intermediate synchronic document.</p></div>
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_9"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given intermediate synchronic document.</p></div>
       </section>
 
       <section id="paint-regions" typeof="bibo:Chapter" resource="#paint-regions" rel="bibo:Chapter">
@@ -1841,7 +1845,7 @@
 
         <p>where CLEAR(E<sub>0</sub>) = 0 and CLEAR(E<sub>n | n &gt; 0</sub>) = 1, i.e. the root container in its entirety.</p>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_9"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new intermediate synchronic document requires clearing
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_10"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new intermediate synchronic document requires clearing
         of the root container.</p></div>
 
         <p>PAINT(E<sub>n</sub>) <em class="rfc2119" title="SHALL">SHALL</em> be the normalized area to be painted for all regions that are used in intermediate synchronic
@@ -2092,7 +2096,7 @@
           </tbody>
         </table>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_10"><span>Note</span></div><p class="">NRGA(G<sub>i</sub>) does not take into account glyph decorations (e.g. underline), glyph effects (e.g.
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_11"><span>Note</span></div><p class="">NRGA(G<sub>i</sub>) does not take into account glyph decorations (e.g. underline), glyph effects (e.g.
         outline) or actual glyph aspect ratio. An implementation can determine an actual buffer size needs based on worst-case
         glyph size complexity.</p></div>
 
@@ -2173,10 +2177,10 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_11"><span>Note</span></div><p class="">Implementations can use use fonts other than those specified above. Two fonts with equal metrics can have a
+      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_12"><span>Note</span></div><p class="">Implementations can use use fonts other than those specified above. Two fonts with equal metrics can have a
       different appearance, but flow identically.</p></div>
 
-      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_12"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
+      <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_13"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
     </section>
   </section>
 
--- a/ttml-ww-profiles/ttml-ww-profiles.source.html	Wed May 21 16:46:47 2014 +0900
+++ b/ttml-ww-profiles/ttml-ww-profiles.source.html	Wed May 21 16:25:37 2014 -0700
@@ -194,8 +194,8 @@
     <section>
       <h3>Related Video Object</h3>
 
-      <p>A subtitle document MAY be associated with a related video object, which SHALL consist of a sequence of frames, each a
-      rectangular array of pixels.</p>
+      <p>A subtitle document MAY be associated with a related video object, which SHALL consist of a sequence of image frames, each a
+      rectangular array of pixels, and SHALL be considered the <em>Related Media Object</em> defined in [[!TTML1]].</p>
     </section>
 
     <section>
@@ -207,13 +207,17 @@
       <p>A media time expression M SHALL correspond to the frame of the related video object with the presentation time that is the
       closest to, but not less, than M.</p>
 
-      <p>If <code>ttp:frameRate</code> is specified, then the product of <code>ttp:frameRate</code> and
-      <code>ttp:frameRateMultiplier</code> SHALL be the frame rate of the related video object.</p>
-
       <aside class="example">
         A media time expression of 00:00:05.1 corresponds to frame ceiling(5.1 × ( 1000 / 1001 × 30) = 153 of a related video
         object with a frame rate of 1000 / 1001 × 30 ≈ 29.97.
       </aside>
+	  
+	  <p>If <code>ttp:frameRate</code> is specified, then the product of <code>ttp:frameRate</code> and
+      <code>ttp:frameRateMultiplier</code> SHALL be the frame rate of the related video object.</p>
+	  
+	    <p class="note">
+        A document can be made independent of the frame rate of the related video object by never using the <em>frames</em> term in a time expression: as specified in <a href="#common-features"></a>, <code>ttp:frameRate</code> is required only if the document includes one or more time expressions that uses the <em>frames</em> term.
+      </p>
     </section>
 
     <section>
@@ -303,7 +307,7 @@
         <code>tt</code> element.</p>
 
         <p class='note'>The placement and use of <code>div</code>, <code>region</code> and <code>span</code> that contain time
-        attributes, and (ii) the use of <code>set</code>.</p>
+        attributes, and the use of <code>set</code> are constrained when <code>ttp:progressivelyDecodable="true"</code> .</p>
       </section>
 
       <section id='tts-forcedDisplay'>
@@ -514,7 +518,7 @@
           <tr>
             <td><code>#frameRate</code></td>
 
-            <td>If the document includes any time expression that uses the frame field, the <code>ttp:frameRate</code> attribute
+            <td>If the document includes any time expression that uses the <em>frames</em> term, the <code>ttp:frameRate</code> attribute
             SHALL be present on the <code>tt</code> element.</td>
           </tr>