--- a/ttml-ww-profiles/ttml-ww-profiles.html Thu Jun 11 07:24:07 2015 -0700
+++ b/ttml-ww-profiles/ttml-ww-profiles.html Thu Jun 11 07:47:17 2015 -0700
@@ -485,6 +485,8 @@
words, it is not considered an error for a <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> (<a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a>) to conform to a
profile defined in this specification without also conforming to the DFXP Presentation Profile (DFXP Transformation
Profile).</p></div>
+
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note2"><span>Note</span></div><p class="">This specification does not specify <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> or <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> behavior when processing or transforming a non-conformant <a href="#dfn-document-instance" class="internalDFN">Document Instance</a>.</p></div>
</section>
<section id="profiles" typeof="bibo:Chapter" resource="#profiles" property="bibo:hasPart">
@@ -501,7 +503,7 @@
<a href="#dfn-document-instance" class="internalDFN">Document Instance</a> such that, when image content is encountered, assistive technologies have access to its corresponding text
form. The method by which this association is made is left to each application.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note2"><span>Note</span></div><p class="">The <code>ittm:altText</code> element specified <a href="#ttm-altText" class="sec-ref"><span class="secno">6.7.4</span> <span class="sec-title">ittm:altText</span></a> also allows text equivalent
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note3"><span>Note</span></div><p class="">The <code>ittm:altText</code> element specified <a href="#ttm-altText" class="sec-ref"><span class="secno">6.7.4</span> <span class="sec-title">ittm:altText</span></a> also allows text equivalent
string to be associated with an image, e.g. to support indexation of the content and also facilitate quality checking of the
document during authoring.</p></div>
@@ -691,7 +693,7 @@
<p>A <a href="#dfn-document-instance" class="internalDFN">Document Instance</a> <em class="rfc2119" title="SHOULD">SHOULD</em> be authored assuming strict clipping of content that falls out of region areas, regardless of
the computed value of <code>tts:overflow</code> for the region.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note3"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], <code>tts:overflow</code> has no effect on the extent of the region, and hence
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note4"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], <code>tts:overflow</code> has no effect on the extent of the region, and hence
the total normalized drawing area S(En) at <a href="#paint-regions" class="sec-ref"><span class="secno">9.3</span> <span class="sec-title">Paint Regions</span></a>.</p></div>
</section>
@@ -701,7 +703,7 @@
<p>A <a href="#dfn-document-instance" class="internalDFN">Document Instance</a> <em class="rfc2119" title="MAY">MAY</em> be associated with a <dfn id="dfn-related-video-object">related video object</dfn>, 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 <a href="#dfn-related-media-object" class="internalDFN">Related Media Object</a>.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note4"><span>Note</span></div><p class="">While this specification contains specific provisions when a <a href="#dfn-document-instance" class="internalDFN">Document Instance</a> is associated with a <a href="#dfn-related-video-object" class="internalDFN">related video object</a>, it does not prevent the use of a <a href="#dfn-document-instance" class="internalDFN">Document Instance</a> with other kinds of <a href="#dfn-related-media-object" class="internalDFN">Related Media Object</a>, e.g. an audio object.</p></div>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note5"><span>Note</span></div><p class="">While this specification contains specific provisions when a <a href="#dfn-document-instance" class="internalDFN">Document Instance</a> is associated with a <a href="#dfn-related-video-object" class="internalDFN">related video object</a>, it does not prevent the use of a <a href="#dfn-document-instance" class="internalDFN">Document Instance</a> with other kinds of <a href="#dfn-related-media-object" class="internalDFN">Related Media Object</a>, e.g. an audio object.</p></div>
</section>
<section id="synchronization" typeof="bibo:Chapter" resource="#synchronization" property="bibo:hasPart">
@@ -719,7 +721,7 @@
object with a frame rate of 1000 / 1001 × 30 ≈ 29.97.
</aside>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note5"><span>Note</span></div><p class="">In typical scenario, the same video program (the <a href="#dfn-related-video-object" class="internalDFN">related video object</a>) will be used for <a href="#dfn-document-instance" class="internalDFN">Document Instance</a>
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note6"><span>Note</span></div><p class="">In typical scenario, the same video program (the <a href="#dfn-related-video-object" class="internalDFN">related video object</a>) will be used for <a href="#dfn-document-instance" class="internalDFN">Document Instance</a>
authoring, delivery and user playback. The mapping from media time expression to <a href="#dfn-related-video-object" class="internalDFN">related video object</a> above allows the author
to precisely associate subtitle video content with video frames, e.g. around scene transitions. In circumstances where the
video program is downsampled during delivery, the application can specify that, at playback, the relative video object be
@@ -858,7 +860,7 @@
...
</tt></pre></div>
- <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note6"><span>Note</span></div><div class="">
+ <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note7"><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>
@@ -970,17 +972,17 @@
...</pre></div>
- <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note7"><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-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
"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-note8"><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-note9"><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-note9"><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-note10"><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>
@@ -1024,7 +1026,7 @@
</div>
...</pre></div>
- <div class="note"><div class="note-title" aria-level="5" role="heading" id="h-note10"><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-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>
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>
@@ -1525,7 +1527,7 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note11"><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-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
M according to M = 3600 · hours + 60 · minutes + seconds + (frames ÷ (<code>ttp:frameRateMultiplier</code> ·
<code>ttp:frameRate</code>)).</p></div>
</section>
@@ -1557,7 +1559,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 <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-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
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">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">Document Instance</a>.</p></div>
@@ -1576,7 +1578,7 @@
<p>When processing glyphs that match the combinations of computed font family and code point listed in <a href="#reference-fonts" class="sec-ref"><span class="secno">A.</span> <span class="sec-title">Reference Fonts</span></a>, e.g. during layout, a <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> or <a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a> <em class="rfc2119" title="SHALL">SHALL</em> use glyph metrics equal to the metrics of the specified reference font, unless the glyph is not defined by the reference font.</p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note13"><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>
+ <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 with equal metrics can have a different appearance, but flow identically.</p></div>
</section>
@@ -1896,7 +1898,7 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note14"><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-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>
</section>
</section>
@@ -1925,7 +1927,7 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note15"><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-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
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">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">Document Instance</a>.</p></div>
@@ -1969,7 +1971,7 @@
<p></p>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note16"><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-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>
</section>
<section id="features-1" typeof="bibo:Chapter" resource="#features-1" property="bibo:hasPart">
@@ -2231,7 +2233,7 @@
P<sub>n-1</sub> at the presentation time of <a href="#dfn-intermediate-synchronic-document" class="internalDFN">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-note17"><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-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
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">related video object</a>.</p></div>
@@ -2264,11 +2266,11 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note18"><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-note19"><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-note19"><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">intermediate synchronic document</a>.</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">intermediate synchronic document</a>.</p></div>
</section>
<section id="paint-regions" typeof="bibo:Chapter" resource="#paint-regions" property="bibo:hasPart">
@@ -2281,7 +2283,7 @@
<p>where CLEAR(E<sub>0</sub>) = 0 and CLEAR(E<sub>n | n > 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-note20"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new <a href="#dfn-intermediate-synchronic-document" class="internalDFN">intermediate synchronic document</a> requires
+ <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">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
@@ -2540,7 +2542,7 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h-note21"><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-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.
outline) or actual glyph aspect ratio. An implementation can determine an actual buffer size needs based on worst-case
glyph size complexity.</p></div>
@@ -2616,7 +2618,7 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="3" role="heading" id="h-note22"><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-note23"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
</section>