--- a/ttml-ww-profiles/ttml-ww-profiles.html Thu Jun 05 18:02:30 2014 +0900
+++ b/ttml-ww-profiles/ttml-ww-profiles.html Fri Jun 06 16:23:09 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-06-05T00:00:49.000Z" id="w3c-first-public-working-draft-05-june-2014"><abbr title="World Wide Web Consortium">W3C</abbr> First Public Working Draft <time class="dt-published" datetime="2014-06-05">05 June 2014</time></h2>
+ <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-06-07T06:22:11.000Z" id="w3c-first-public-working-draft-06-june-2014"><abbr title="World Wide Web Consortium">W3C</abbr> First Public Working Draft <time class="dt-published" datetime="2014-06-06">06 June 2014</time></h2>
<dl>
<dt>This version:</dt>
- <dd><a class="u-url" href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140605/">http://www.w3.org/TR/2014/WD-ttml-imsc1-20140605/</a></dd>
+ <dd><a class="u-url" href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140606/">http://www.w3.org/TR/2014/WD-ttml-imsc1-20140606/</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>
@@ -382,6 +382,10 @@
<h3 aria-level="2" role="heading" id="h3_general"><span class="secno">3.1 </span>General</h3>
<p>A subtitle document <em class="rfc2119" title="SHALL NOT">SHALL NOT</em> conform to the Text and Image Profiles simultaneously.</p>
+
+ <p class="NOTE">Some applications require the same subtitle/caption content to be available in both text and image form
+ simultaneously (see [<cite><a class="bibref" href="#bib-WCAG20">WCAG20</a></cite>] for instance). For these applications, two distinct subtitle documents, one conforming to the
+ Text Profile and the other conforming to the Image Profile, can be offered.</p>
</section>
<section id="text-profile">
@@ -601,7 +605,9 @@
<h4 aria-level="3" role="heading" id="h4_ttp-progressivelyDecodable"><span class="secno">4.5.2 </span>ittp:progressivelyDecodable</h4>
<p>A progressively decodable subtitle document is a subtitle document structured to facilitate processing before the
- document is received in its entirety. It shall conform to the following:</p>
+ document is received in its entirety.</p>
+
+ <p>A progressively decodable subtitle document shall conform to the following:</p>
<ol>
<li>elements appear in the document in increasing order according to their resolved begin time;</li>
@@ -645,9 +651,17 @@
<section id="tts-forcedDisplay" typeof="bibo:Chapter" resource="#tts-forcedDisplay" rel="bibo:Chapter">
<h4 aria-level="3" role="heading" id="h4_tts-forcedDisplay"><span class="secno">4.5.3 </span>itts:forcedDisplay</h4>
- <p><code>itts:forcedDisplay</code> signals that a block of subtitle content is identified as <em>Forced</em> subtitle content.
- <em>Forced</em> subtitle content is subtitle content that represents audio (e.g. foreign language) or text (e.g. a sign)
- that is not translated in the audio/video presentation.</p>
+ <p><code>itts:forcedDisplay</code> identifies <em>Forced</em> subtitle content. <em>Forced</em> subtitle content is
+ subtitle content that represents audio (e.g. foreign language) or text (e.g. a sign) that is not translated in the
+ audio/video presentation, e.g. Na'vi language in the movie Avatar. As such <em>Forced</em> subtitle content is useful
+ whether the user has explicitly requested subtitles to be displayed.</p>
+
+ <p>When presenting a subtitle document, a presentation processor <em class="rfc2119" title="SHOULD">SHOULD</em> display content for which the computed value of
+ <code>itts:forcedDisplay</code> is <code>true</code>, regardless of whether the user has explicitly requested display of
+ subtitle content.</p>
+
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_4"><span>Note</span></div><p class="">The algorithm for selecting subtitle and caption tracks based on user preference and content metadata is
+ not specified here.</p></div>
<table class="simple">
<colgroup>
@@ -694,10 +708,10 @@
</tbody>
</table>
- <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_4"><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="4" role="heading" id="h_note_5"><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>
</section>
</section>
@@ -725,7 +739,7 @@
</li>
</ol>
- <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
+ <div class="note"><div class="note-title" aria-level="4" 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>], 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>
@@ -1191,7 +1205,7 @@
</tbody>
</table>
- <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
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_7"><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>
@@ -1862,7 +1876,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_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
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_8"><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>
@@ -1895,11 +1909,11 @@
</tbody>
</table>
- <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
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_9"><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_9"><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_10"><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">
@@ -1911,7 +1925,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_note_10"><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_11"><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
@@ -2162,7 +2176,7 @@
</tbody>
</table>
- <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.
+ <div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_12"><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>
@@ -2243,10 +2257,10 @@
</tbody>
</table>
- <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
+ <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_13"><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_13"><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_14"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
</section>
</section>
@@ -2642,4 +2656,5 @@
</dd><dt id="bib-CEA-708">[CEA-708]</dt><dd rel="dcterms:references"><a href="http://www.ce.org/Standards/Standard-Listings/R4-3-Television-Data-Systems-Subcommittee/CEA-708-D.aspx">Digital Television (DTV) Closed Captioning</a>, ANSI/CEA Standard.
</dd><dt id="bib-SDPUS">[SDPUS]</dt><dd rel="dcterms:references">World Wide Web Consortium (W3C). <a href="http://www.w3.org/TR/ttml10-sdp-us/">TTML Simple Delivery Profile for Closed Captions (US)</a> (W3C Working Group Note, 05 February 2013)
</dd><dt id="bib-SUBM">[SUBM]</dt><dd rel="dcterms:references">World Wide Web Consortium (W3C). <a href="http://www.w3.org/Submission/2013/SUBM-ttml-ww-profiles-20130607/">TTML Text and Image Profiles for Internet Media Subtitles and Captions</a> (Member Submission, 07 June 2013)
+</dd><dt id="bib-WCAG20">[WCAG20]</dt><dd rel="dcterms:references">Ben Caldwell; Michael Cooper; Loretta Guarino Reid; Gregg Vanderheiden et al. <a href="http://www.w3.org/TR/WCAG20/"><cite>Web Content Accessibility Guidelines (WCAG) 2.0</cite></a>. 11 December 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/WCAG20/">http://www.w3.org/TR/WCAG20/</a>
</dd></dl></section></section></body></html>
\ No newline at end of file
--- a/ttml-ww-profiles/ttml-ww-profiles.source.html Thu Jun 05 18:02:30 2014 +0900
+++ b/ttml-ww-profiles/ttml-ww-profiles.source.html Fri Jun 06 16:23:09 2014 -0700
@@ -26,7 +26,8 @@
"MHP" : "ETSI TS 101 812 V1.3.1, Digital Video Broadcasting (DVB); Multimedia Home",
"ST2052-1": "SMPTE ST 2052-1, Timed Text Format (SMPTE-TT)",
"SDPUS": "World Wide Web Consortium (W3C). <a href='http://www.w3.org/TR/ttml10-sdp-us/'>TTML Simple Delivery Profile for Closed Captions (US)</a> (W3C Working Group Note, 05 February 2013)",
- "CLDR": "Unicode Consortium. <a href='http://cldr.unicode.org'>The Common Locale Data Repository Project</a>"
+ "CLDR": "Unicode Consortium. <a href='http://cldr.unicode.org'>The Common Locale Data Repository Project</a>",
+
}
};
</script>
@@ -85,6 +86,10 @@
<h3>General</h3>
<p>A subtitle document SHALL NOT conform to the Text and Image Profiles simultaneously.</p>
+
+ <p class='NOTE'>Some applications require the same subtitle/caption content to be available in both text and image form
+ simultaneously (see [[WCAG20]] for instance). For these applications, two distinct subtitle documents, one conforming to the
+ Text Profile and the other conforming to the Image Profile, can be offered.</p>
</section>
<section>
@@ -304,7 +309,9 @@
<h4>ittp:progressivelyDecodable</h4>
<p>A progressively decodable subtitle document is a subtitle document structured to facilitate processing before the
- document is received in its entirety. It shall conform to the following:</p>
+ document is received in its entirety.</p>
+
+ <p>A progressively decodable subtitle document shall conform to the following:</p>
<ol>
<li>elements appear in the document in increasing order according to their resolved begin time;</li>
@@ -349,9 +356,17 @@
<section id='tts-forcedDisplay'>
<h4>itts:forcedDisplay</h4>
- <p><code>itts:forcedDisplay</code> signals that a block of subtitle content is identified as <em>Forced</em> subtitle content.
- <em>Forced</em> subtitle content is subtitle content that represents audio (e.g. foreign language) or text (e.g. a sign)
- that is not translated in the audio/video presentation.</p>
+ <p><code>itts:forcedDisplay</code> identifies <em>Forced</em> subtitle content. <em>Forced</em> subtitle content is
+ subtitle content that represents audio (e.g. foreign language) or text (e.g. a sign) that is not translated in the
+ audio/video presentation, e.g. Na'vi language in the movie Avatar. As such <em>Forced</em> subtitle content is useful
+ whether the user has explicitly requested subtitles to be displayed.</p>
+
+ <p>When presenting a subtitle document, a presentation processor SHOULD display content for which the computed value of
+ <code>itts:forcedDisplay</code> is <code>true</code>, regardless of whether the user has explicitly requested display of
+ subtitle content.</p>
+
+ <p class='note'>The algorithm for selecting subtitle and caption tracks based on user preference and content metadata is
+ not specified here.</p>
<table class="simple">
<colgroup>
@@ -399,9 +414,9 @@
</table>
<p class='note'>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>
+ <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>
</section>
</section>