[imsc] further change re ISSUE-418
authorplemieux
Fri, 30 Oct 2015 13:49:59 +0900
changeset 1002 2cd6f1c06e57
parent 1001 b441821f14cf
child 1003 708f521a6550
[imsc] further change re ISSUE-418
ttml-ww-profiles/ttml-ww-profiles.html
ttml-ww-profiles/ttml-ww-profiles.source.html
--- a/ttml-ww-profiles/ttml-ww-profiles.html	Fri Oct 30 12:02:46 2015 +0900
+++ b/ttml-ww-profiles/ttml-ww-profiles.html	Fri Oct 30 13:49:59 2015 +0900
@@ -872,6 +872,11 @@
 </pre>
 <p>In other words, <code>tts:extent</code>, when present on the <code>tt</code> element, determines the size of <code>"px"</code> units relative to the root container. <code>ttp:aspectRatio</code> is independently used to map the root container to the <a href="#dfn-related-video-object" class="internalDFN" data-link-type="dfn">Related Video Object</a>.
 </p></aside>
+
+<div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note7"><span>Note</span></div><p class="">
+The <code>ittp:aspectRatio</code> parameter effectively defines the intended display aspect ratio (DAR) of the root container, while
+ the <code>tts:extent</code> style property on the root element effectively defines the intended storage aspect ratio (SAR) of the root container.
+</p></div>
     </section>
       <section id="ttp-progressivelyDecodable" typeof="bibo:Chapter" resource="#ttp-progressivelyDecodable" property="bibo:hasPart">
         <h4 id="h-ttp-progressivelydecodable" resource="#h-ttp-progressivelydecodable"><span property="xhv:role" resource="xhv:heading"><span class="secno">6.7.2 </span>ittp:progressivelyDecodable</span></h4>
@@ -934,7 +939,7 @@
  ...
 &lt;/tt&gt;</pre></div>
 
-        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note7"><span>Note</span></div><div class="">
+        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note8"><span>Note</span></div><div class="">
           <p>[<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>] specifies explicitly referencing of elements identified using <code>xml:id</code> in the following
           circumstances:</p>
 
@@ -1045,17 +1050,17 @@
 ...</pre></div>
 
 
-        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note8"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], the background of a region can be visible even if the computed value of <code>tts:visibility</code> equals
+        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note9"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], the background of a region can be visible even if the computed value of <code>tts:visibility</code> equals
         "hidden" for all active content within. The background of a region for which <code>itts:forcedDisplay</code> equals "true" can therefore remain visible even if <code>itts:forcedDisplay</code> equals "false" for all active
         content elements within the region and <code>displayForcedOnlyMode</code> equals "true". Authors can avoid this situation, for instance, by ensuring that content
         elements and the regions that they are flowed into always have the same value of <code>itts:forcedDisplay</code>.</p></div>
 
-        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note9"><span>Note</span></div><p class="">Although <code>itts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
+        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note10"><span>Note</span></div><p class="">Although <code>itts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
         <code>br</code> content element, <code>itts:forcedDisplay</code> 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>
 
-        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note10"><span>Note</span></div><p class="">It is expected that the functionality of <code>itts:forcedDisplay</code> will be mapped to a conditional
+        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note11"><span>Note</span></div><p class="">It is expected that the functionality of <code>itts:forcedDisplay</code> will be mapped to a conditional
         style construct in a future revision of this specification.</p></div>
       </section>
 
@@ -1099,7 +1104,7 @@
 &lt;/div&gt;
 ...</pre></div>
 
-        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note11"><span>Note</span></div><p class="">In contrast to the common use of <code>alt</code> attributes in [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>], the <code>ittm:altText</code>
+        <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note12"><span>Note</span></div><p class="">In contrast to the common use of <code>alt</code> attributes in [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>], the <code>ittm:altText</code>
         attribute content is not intended to be displayed in place of the element if the element is not loaded. The
         <code>ittm:altText</code> attribute content can however be read and used by assistive technologies.</p></div>
       </section>
@@ -1665,7 +1670,7 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note12"><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="4" role="heading" id="h-note13"><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>
@@ -1697,7 +1702,7 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note13"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">6.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
+      <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note14"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">6.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
       not required by this profile. The profile designator specified above is intended to be generally used to signal conformance
       of a <a href="#dfn-document-instance" class="internalDFN" data-link-type="dfn">Document Instance</a> to the profile. The details of such signaling depends on the application, and can, for instance, use
       metadata structures out-of-band of the <a href="#dfn-document-instance" class="internalDFN" data-link-type="dfn">Document Instance</a>.</p></div>
@@ -1719,7 +1724,7 @@
 			<a href="#reference-fonts" class="sec-ref"><span class="secno">A.</span> <span class="sec-title">Reference Fonts</span></a>, a processor <em class="rfc2119" title="SHALL">SHALL</em> use a font that generates a glyph sequence whose dimension is substantially
 			identical to the glyph sequence that would have been generated by one of the specified reference fonts.</p>
 			
-			<div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note14"><span>Note</span></div><p class="">Implementations can use fonts other than those specified in <a href="#reference-fonts" class="sec-ref"><span class="secno">A.</span> <span class="sec-title">Reference Fonts</span></a>. Two fonts 
+			<div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note15"><span>Note</span></div><p class="">Implementations can use fonts other than those specified in <a href="#reference-fonts" class="sec-ref"><span class="secno">A.</span> <span class="sec-title">Reference Fonts</span></a>. Two fonts 
 			with equal metrics can have a different appearance, but flow identically.</p></div>
 			
     </section>
@@ -2109,7 +2114,7 @@
         </tbody>
       </table>
 			
-			<div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note15"><span>Note</span></div><p class="">In contrast to this specification, [<cite><a class="bibref" href="#bib-EBU-TT-D">EBU-TT-D</a></cite>] specifies that the attributes <code>ebutts:linePadding</code> and <code>ebutts:multiRowAlign</code> are allowed only on the <code>style</code> element.</p></div>
+			<div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note16"><span>Note</span></div><p class="">In contrast to this specification, [<cite><a class="bibref" href="#bib-EBU-TT-D">EBU-TT-D</a></cite>] specifies that the attributes <code>ebutts:linePadding</code> and <code>ebutts:multiRowAlign</code> are allowed only on the <code>style</code> element.</p></div>
 			
     </section>
   </section>
@@ -2138,7 +2143,7 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note16"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">6.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
+      <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note17"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">6.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
       not required by this profile. The profile designator specified above is intended to be generally used to signal conformance
       of a <a href="#dfn-document-instance" class="internalDFN" data-link-type="dfn">Document Instance</a> to the profile. The details of such signaling depends on the application, and can, for instance, use
       metadata structures out-of-band of the <a href="#dfn-document-instance" class="internalDFN" data-link-type="dfn">Document Instance</a>.</p></div>
@@ -2178,7 +2183,7 @@
 			
 			<p></p>
 			
-			<div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note17"><span>Note</span></div><p class="">In [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], <code>tts:extent</code> and <code>tts:origin</code> do not apply to <code>div</code> elements. In order to individually position multiple <code>div</code> elements, each <code>div</code> can be associated with a distinct <code>region</code> with the desired <code>tts:extent</code> and <code>tts:origin</code>.</p></div>
+			<div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note18"><span>Note</span></div><p class="">In [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], <code>tts:extent</code> and <code>tts:origin</code> do not apply to <code>div</code> elements. In order to individually position multiple <code>div</code> elements, each <code>div</code> can be associated with a distinct <code>region</code> with the desired <code>tts:extent</code> and <code>tts:origin</code>.</p></div>
     </section>
 
     <section id="features-1" typeof="bibo:Chapter" resource="#features-1" property="bibo:hasPart">
@@ -2517,7 +2522,7 @@
         P<sub>n-1</sub> at the presentation time of <a href="#dfn-intermediate-synchronic-document" class="internalDFN" data-link-type="dfn">intermediate synchronic document</a> 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-note18"><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-note19"><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 <a href="#dfn-related-video-object" class="internalDFN" data-link-type="dfn">Related Video Object</a>.</p></div>
 
@@ -2550,11 +2555,11 @@
           </tbody>
         </table>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note19"><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-note20"><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-note20"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given <a href="#dfn-intermediate-synchronic-document" class="internalDFN" data-link-type="dfn">intermediate synchronic document</a>.</p></div>
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note21"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given <a href="#dfn-intermediate-synchronic-document" class="internalDFN" data-link-type="dfn">intermediate synchronic document</a>.</p></div>
       </section>
 
       <section id="paint-regions" typeof="bibo:Chapter" resource="#paint-regions" property="bibo:hasPart">
@@ -2567,7 +2572,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-note21"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new <a href="#dfn-intermediate-synchronic-document" class="internalDFN" data-link-type="dfn">intermediate synchronic document</a> requires
+        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note22"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new <a href="#dfn-intermediate-synchronic-document" class="internalDFN" data-link-type="dfn">intermediate synchronic document</a> 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
@@ -2826,7 +2831,7 @@
           </tbody>
         </table>
 
-        <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note22"><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-note23"><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>
 
--- a/ttml-ww-profiles/ttml-ww-profiles.source.html	Fri Oct 30 12:02:46 2015 +0900
+++ b/ttml-ww-profiles/ttml-ww-profiles.source.html	Fri Oct 30 13:49:59 2015 +0900
@@ -503,6 +503,11 @@
 </pre>
 <p>In other words, <code>tts:extent</code>, when present on the <code>tt</code> element, determines the size of <code>"px"</code> units relative to the root container. <code>ttp:aspectRatio</code> is independently used to map the root container to the <a>Related Video Object</a>.
 </aside>
+
+<p class='note'>
+The <code>ittp:aspectRatio</code> parameter effectively defines the intended display aspect ratio (DAR) of the root container, while
+ the <code>tts:extent</code> style property on the root element effectively defines the intended storage aspect ratio (SAR) of the root container.
+</p>
     </section>
       <section id='ttp-progressivelyDecodable'>
         <h4>ittp:progressivelyDecodable</h4>