SDP-US Editorial (*) - attempt to consistently use presentation processor instead of player or just processor
authorGlenn Adams <glenn@skynav.com>
Thu, 18 Oct 2012 14:38:05 +0700
changeset 3035553a4cbae5f
parent 302 ceef1819f7c5
child 304 0680fc6d2a3f
SDP-US Editorial (*) - attempt to consistently use presentation processor instead of player or just processor
ttml10-sdp-us/Overview.html
     1.1 --- a/ttml10-sdp-us/Overview.html	Thu Oct 18 14:24:29 2012 +0700
     1.2 +++ b/ttml10-sdp-us/Overview.html	Thu Oct 18 14:38:05 2012 +0700
     1.3 @@ -296,7 +296,7 @@
     1.4  </head>
     1.5  <body>
     1.6  <section id='abstract'>
     1.7 -<p>TTML 1.0 [[!TTML10]] provides many features to satisfy captioning and subtitling requirements, not all of which are intended for end user display. Requirements have been identified by key video and content communities to define an interoperable delivery profile using the core features specifically designed for online presentation of TTML. Such a profile allows the community of TTML users to construct constrained presentation engines for TTML. This document defines the behavior expected of a presentation processor using the player constraints for such an online delivery profile.</p>
     1.8 +<p>TTML 1.0 [[!TTML10]] provides many features to satisfy captioning and subtitling requirements, not all of which are intended for end user display. Requirements have been identified by key video and content communities to define an interoperable delivery profile using the core features specifically designed for online presentation of TTML. Such a profile allows the community of TTML users to construct constrained presentation engines for TTML. This document defines the behavior expected of a TTML content player using the presentation processor constraints for such an online delivery profile.</p>
     1.9  <p></p>
    1.10  <p>The Simple Online Delivery profile is focused on streamlined delivery of closed captions on the Internet. This interoperability profile supports core TTML features to deliver content originating legacy formats such as CEA-608 and -708 content, and is targeted primarily for delivery in US markets.</p>
    1.11  <p>The Simple Delivery Profile for Closed Captions focuses interoperability using [[!TTML10]] to support delivery of closed captions for video content. Other profiles based on [[!TTML10]] may target other types of subtitles such as on-screen text or graphics. This interoperability profile is a proper subset of [[!TTML10]] intended to support features required for US Government closed captioning requirements for online presentation.</p>
    1.12 @@ -311,7 +311,7 @@
    1.13  </section>
    1.14  <section id='conformance'>
    1.15  <h3>Simple Delivery Profile for Closed Captions</h3>
    1.16 -<p>This profile identifies the content and player constraints for closed captioning using TTML. To conform to this profile, a presentation engine MUST:</p>
    1.17 +<p>This profile identifies the content and presentation processor constraints for closed captioning using TTML. To conform to this profile, a presentation engine MUST:</p>
    1.18  <ul>
    1.19  <li>Satisfy the requirements specified by Section 3.2.1 Generic Processor Conformance [TTML] that are required to implement:
    1.20  <ul>
    1.21 @@ -360,7 +360,7 @@
    1.22  <section id='SimpleProfile'>
    1.23  <h2>Simple Delivery Profile for Closed Captions</h2>
    1.24  <p>This profile represents a minimum set of required functionality using specified TTML features to deliver closed captions for online-delivery. This profile does not preclude optional features from use.</p>
    1.25 -<p>The functionality is described in how it constrains the use of TTML features and how a processor provides those captions. An example implementing this constrained profile exists in <a href="#Features_in_TTML_1.0_Used">Profile designator</a>; error handling behavior is found in <a href="#error_handling">Error Handling</a>.</p>
    1.26 +<p>The functionality is described in how it constrains the use of TTML features and how a presentation processor provides those captions. An example implementing this constrained profile exists in <a href="#Features_in_TTML_1.0_Used">Profile designator</a>; error handling behavior is found in <a href="#error_handling">Error Handling</a>.</p>
    1.27  <section id='Use_of_TTML_Constrained_Feature_Template'>
    1.28  <h3>Use of TTML Constrained Feature Template</h3>
    1.29  <p>This profile identifies functionality in the context of the required [[!TTML10]] features used and applies constraints. Each function is defined by:</p>
    1.30 @@ -397,7 +397,7 @@
    1.31  </section>
    1.32  <section class='Structural_Constraints'>
    1.33  <h3>Structural Constraints</h3>
    1.34 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
    1.35 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
    1.36  <p data-transform='constraint'>A document MUST contain both a head and body element</p>
    1.37  <p data-transform='constraint'>A document MUST contain both a styling and a layout element.</p>
    1.38  <p data-transform='constraint'>A document MUST NOT use a div element inside a div element.</p>
    1.39 @@ -465,7 +465,7 @@
    1.40  </section>
    1.41  <section class='Core_Constraints'>
    1.42  <h4>Constraints</h4>
    1.43 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
    1.44 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
    1.45  <p data-transform='constraint'>A document MUST contain only the following elements:</p>
    1.46  <ul>
    1.47  <li><code>tt</code></li>
    1.48 @@ -534,7 +534,7 @@
    1.49  </section>
    1.50  <section class='Core_Constraints'>
    1.51  <h4>Constraints</h4>
    1.52 -<p data-transform='constraint'>Processors MUST support the capability to present documents referencing this profile using the following URI: <dfn>http://www.w3.org/TR/profile/simple-delivery</dfn></p>
    1.53 +<p data-transform='constraint'>Presentation processors MUST support the capability to present documents referencing this profile using the following URI: <dfn>http://www.w3.org/TR/profile/simple-delivery</dfn></p>
    1.54  <div class="note"><p>See also <a href="#conformance">Conformance</a></p></div>
    1.55  <div class="note"><p>The use attribute could indicate the geographical region for which the profile is used. For example, specific styling capabilities could be used in a particular geographical region. See also <a href="#other_constraints">Other Constraints</a>.</p></div>
    1.56  </section>
    1.57 @@ -596,14 +596,14 @@
    1.58  </section>
    1.59  <section class='Core_Constraints'>
    1.60  <h4>Constraints</h4>
    1.61 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
    1.62 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
    1.63  <p data-transform='constraint'>The backgroundColor MUST be expressed in #rrggbbaa format exclusively using the <dfn>&lt;hexdigit&gt;</dfn> style value expression.</p>
    1.64  <p data-transform='constraint'>The backgroundColor MUST support the colors outlined in <a href="#color-values">Color Values</a>.</p>
    1.65  <div class="note"><p>These colors are identical to those identified in the CEA708-D, Section 8.8 [RBG resolution of 4 bits for each primary (03)].</p></div>
    1.66  <p data-transform='constraint'>The alpha component of backgroundColor MUST support the opacity values outlined in <a href="#color-values">Color Values</a> .</p>
    1.67  <p data-transform='constraint'>The alpha component of backgroundColor for a region MUST be 00.</p>
    1.68 -<p data-transform='constraint'>The player MUST allow the user to specify a backgroundColor for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</p>
    1.69 -<p data-transform='constraint'>The player MUST allow the user to specify a backgroundColor for p and span elements to allow for semi-transparent and transparent opacities.</p>
    1.70 +<p data-transform='constraint'>The presentation processor MUST allow the user to specify a backgroundColor for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</p>
    1.71 +<p data-transform='constraint'>The presentation processor MUST allow the user to specify a backgroundColor for p and span elements to allow for semi-transparent and transparent opacities.</p>
    1.72  </section>
    1.73  </section>
    1.74  <section id='Constrained_TTML_Feature_color'>
    1.75 @@ -630,13 +630,13 @@
    1.76  </section>
    1.77  <section class='Core_Constraints'>
    1.78  <h4>Constraints</h4>
    1.79 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
    1.80 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
    1.81  <p data-transform='constraint'>The color MUST be expressed in #rrggbbaa format exclusively using the <dfn>&lt;hexdigit&gt;</dfn> style value expression.</p>
    1.82  <p data-transform='constraint'>The color MUST support the colors outlined in <a href="#color-values">Color Values</a>.</p>
    1.83  <div class="note"><p>These colors are identical to those identified in the CEA708-D, Section 8.8 [RBG resolution of 4 bits for each primary (03)].</p></div>
    1.84  <p data-transform='constraint'>The alpha component of color MUST support the opacity values outlined in <a href="#color-values">Color Values</a> .</p>
    1.85 -<p data-transform='constraint'>The player MUST allow the user to specify a color for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</p>
    1.86 -<p data-transform='constraint'>The player MUST allow the user to specify a color for p and span elements to allow for semi-transparent and transparent opacities.</p>
    1.87 +<p data-transform='constraint'>The presentation processor MUST allow the user to specify a color for p and span elements based on a minimum of an 8-color palette of white, black, red, green, blue, yellow, magenta, and cyan (See Minimum Color List in <a href="#color-values">Color Values</a> ).</p>
    1.88 +<p data-transform='constraint'>The presentation processor MUST allow the user to specify a color for p and span elements to allow for semi-transparent and transparent opacities.</p>
    1.89  </section>
    1.90  </section>
    1.91  <section id='Constrained_TTML_Feature_display_region'>
    1.92 @@ -851,7 +851,7 @@
    1.93  </section>
    1.94  <section class='Core_Constraints'>
    1.95  <h4>Constraints</h4>
    1.96 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
    1.97 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
    1.98  <p data-transform='constraint'>The document MUST use the tts:fontFamily attribute using only the following values:</p>
    1.99  <ul>
   1.100  <li>default</li>
   1.101 @@ -864,7 +864,7 @@
   1.102  <li>smallCaps</li>
   1.103  </ul>
   1.104  <div class="note"><p>Values of tts:fontFamily that do not not correspond to generic font family names in [[!TTML10]], such as <code>casual</code>, <code>cursive</code> and <code>smallCaps</code>, may be used. These are to be interpreted as local font names, which, if not available, the <code>default</code> font family is to be used.</p></div>
   1.105 -<p data-transform='constraint'>A player MUST map the generic font names to fonts as follows</p>
   1.106 +<p data-transform='constraint'>A presentation processor MUST map the generic font names to fonts as follows</p>
   1.107  <table>
   1.108  <tr>
   1.109  <th>Style Value</th>
   1.110 @@ -912,9 +912,9 @@
   1.111  <td>Similar to Engravers Gothic</td>
   1.112  </tr>
   1.113  </table>
   1.114 -<p data-transform='constraint'>The player MUST allow the user to specify a generic fontFamily for the document using the values shown in the preceding table.</p>
   1.115 -<p data-transform='constraint'>The player MUST allow the user to specify character edge attributes and types for the generic fontFamily names for the values shown in the preceding table.</p>
   1.116 -<div class="note"><p>Player and Unicode code point support is defined in <a href="#code-points">Code Point support</a></p></div>
   1.117 +<p data-transform='constraint'>The presentation processor MUST allow the user to specify a generic fontFamily for the document using the values shown in the preceding table.</p>
   1.118 +<p data-transform='constraint'>The presentation processor MUST allow the user to specify character edge attributes and types for the generic fontFamily names for the values shown in the preceding table.</p>
   1.119 +<div class="note"><p>Presentation processor and Unicode code point support is defined in <a href="#code-points">Code Point support</a></p></div>
   1.120  <div class="note"><p>Text outline can be specified using a style property to apply to characters selected for specific areas for content flowed into a region. Text outline applies a specific character edge to content. For example, when the textOutline style property is used, a type of shadow or thickness can be applied to content.</p></div>
   1.121  </section>
   1.122  </section>
   1.123 @@ -943,7 +943,7 @@
   1.124  </section>
   1.125  <section class='Core_Constraints'>
   1.126  <h4>Constraints</h4>
   1.127 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.128 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.129  <p data-transform='constraint'>document MUST only specify tts:fontSize(s) using a value of 50%, 75%, 100%, 150% or 200%.</p>
   1.130  <div class="note"><p>Use of a fontSize of less than 75% (i.e. 50%) could result in unreadable content for a user.</p></div>
   1.131  <div class="note"><p>Specifying a fontSize is used for a document could allow the user to select a preferred fontSize.</p></div>
   1.132 @@ -951,8 +951,8 @@
   1.133  <section>
   1.134  <!-- <p data-transform='example'>Example to show how to specify an initial font.</p> -->
   1.135  <!-- div data-include=example3.xml'></div --></section>
   1.136 -<p data-transform='constraint'>The default font height of the player MUST be 5% of the root container height</p>
   1.137 -<div class="note"><p>This is equivalent to one cell using the default grid. A player is however not required to support the grid metric.</p></div>
   1.138 +<p data-transform='constraint'>The default font height of the presentation processor MUST be 5% of the root container height</p>
   1.139 +<div class="note"><p>This is equivalent to one cell using the default grid. A presentation processor is however not required to support the grid metric.</p></div>
   1.140  </section>
   1.141  </section>
   1.142  <section id='Constrained_TTML_Feature_display_display_fontStyle_italic'>
   1.143 @@ -979,7 +979,7 @@
   1.144  </section>
   1.145  <section class='Core_Constraints'>
   1.146  <h4>Constraints</h4>
   1.147 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.148 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.149  <p data-transform='constraint'>The capability MUST exist for the user to specify the italic style for the font families identified in this profile.</p>
   1.150  </section>
   1.151  </section>
   1.152 @@ -1074,7 +1074,7 @@
   1.153  </section>
   1.154  <section class='Core_Constraints'>
   1.155  <h4>Constraints</h4>
   1.156 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.157 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.158  <p data-transform='constraint'>Styles MUST be applied either by reference or through use of inline styling.</p>
   1.159  <p data-transform='constraint'>Styles MUST be applied with a single style element using the style attribute.</p>
   1.160  <p data-transform='constraint'>Style elements MUST NOT reference other styles.</p>
   1.161 @@ -1187,7 +1187,7 @@
   1.162  </section>
   1.163  <section class='Core_Constraints'>
   1.164  <h4>Constraints</h4>
   1.165 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.166 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.167  <p data-transform='constraint'>The tts:textDecoration-under attribute MUST support the constraints identified in this profile.</p>
   1.168  <p data-transform='constraint'>The capability MUST exist for the user to specify the underline decoration for the font families identified in this profile.</p>
   1.169  </section>
   1.170 @@ -1216,7 +1216,7 @@
   1.171  </section>
   1.172  <section class='Core_Constraints'>
   1.173  <h4>Constraints</h4>
   1.174 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.175 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.176  <p data-transform='constraint'>Character edge attributes MUST be expressed using textOutline-unblurred based on the settings identified in CEA-708-D, Section 8.5.8.</p>
   1.177  <p data-transform='constraint'>A text outline MUST be expressed using textOutline-unblurred of up to 10% thickness.</p>
   1.178  <p data-transform='constraint'>The user MUST be able to specify character edge and type attributes using tts:textOutline attribute.</p>
   1.179 @@ -1283,7 +1283,7 @@
   1.180  </section>
   1.181  <section class='Core_Constraints'>
   1.182  <h4>Constraints</h4>
   1.183 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.184 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.185  <p data-transform='constraint'>Active region(s) MUST NOT overlap.</p>
   1.186  <p data-transform='constraint'>No more than 4 region(s) MUST be active concurrently.</p>
   1.187  <p data-transform='constraint'>No more than four lines of text MUST be selected into all active regions at any given time.</p>
   1.188 @@ -1314,7 +1314,7 @@
   1.189  </section>
   1.190  <section class='Core_Constraints'>
   1.191  <h4>Constraints</h4>
   1.192 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.193 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.194  <p data-transform='constraint'>At most 32 characters MUST be present in any displayed text line.</p>
   1.195  <p data-transform='constraint'>At most one p element MUST be selected into a region at a time.</p>
   1.196  <div class="note"><p>The style properites of region and the content selected for the region impact how selected text flows into a region (i.e. selected text may flow outside of the region such as on a mobile device).</p></div>
   1.197 @@ -1352,10 +1352,10 @@
   1.198  </section>
   1.199  <section class='Core_Constraints'>
   1.200  <h4>Constraints</h4>
   1.201 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.202 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.203  <p data-transform='constraint'>Timing MUST be expressed in the hh:mm:ss.ms or hh:mm:ss:ff format used in the timeExpression.</p>
   1.204  <p data-transform='constraint'>Timing MUST be expressed in the same format throughout the document.</p>
   1.205 -<p data-transform='constraint'>Processors MUST support durations (dur) on the p and span elements, and MAY (but need not) support on other element types;
   1.206 +<p data-transform='constraint'>Presentation processors MUST support durations (dur) on the p and span elements, and MAY (but need not) support on other element types;
   1.207  as such, a document SHOULD NOT use a duration on an element type other than p or span.</p>
   1.208  <p data-transform='constraint'>For timing in hh:mm:ss.ms, the following format MUST be used:</p>
   1.209  <ul>
   1.210 @@ -1457,7 +1457,7 @@
   1.211  </section>
   1.212  <section class='Core_Constraints'>
   1.213  <h4>Constraints</h4>
   1.214 -<p>Processors MUST support the capability to present documents where the following constraints apply:</p>
   1.215 +<p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
   1.216  <p data-transform='constraint'>The set element MUST only animate the region or span element.</p>
   1.217  <p data-transform='constraint'>The use of set elements applied to a region element MUST only animate the tts:display, tts:origin or tts:extent attribute.</p>
   1.218  <p data-transform='constraint'>The use of set elements applied to a span element MUST only animate the tts:color attribute.</p>
   1.219 @@ -1632,9 +1632,9 @@
   1.220  </section>
   1.221  <section class='appendix'>
   1.222  <h2>Code points</h2>
   1.223 -<p data-transform='constraint'>Players SHOULD provide font glyph coverage for all characters in the &#8220;ISO 8859-1 Latin-1&#8221; space and those for ANSI INCITS 4 when mapped onto Unicode code points (see table).</p>
   1.224 -<p class="note">A player follows the semantics expected for use of Unicode code points as stated in this section. The exact glyph is player dependent.</p>
   1.225 -<p data-transform='constraint'>Players SHOULD support the C0, G0, C1, and G1 code sets mapped onto Unicode as in the following table. See CEA 708, Section 7.1 including Table 11.</p>
   1.226 +<p data-transform='constraint'>Presentation processors SHOULD provide font glyph coverage for all characters in the &#8220;ISO 8859-1 Latin-1&#8221; space and those for ANSI INCITS 4 when mapped onto Unicode code points (see table).</p>
   1.227 +<p class="note">A presentation processor follows the semantics expected for use of Unicode code points as stated in this section. The exact glyph is presentation processor dependent.</p>
   1.228 +<p data-transform='constraint'>Presentation processors SHOULD support the C0, G0, C1, and G1 code sets mapped onto Unicode as in the following table. See CEA 708, Section 7.1 including Table 11.</p>
   1.229  <table style="border-collapse: collapse;width:630pt; width:835px;border:0">
   1.230  <colgroup>
   1.231  <col style="width:38pt; width:51px" />
   1.232 @@ -2647,11 +2647,11 @@
   1.233  <td class="style2" style="width:49px"></td>
   1.234  </tr>
   1.235  </table>
   1.236 -<p data-transform='constraint'>Players MAY support the extended G2 characters sets that map onto Unicode code points (See table).</p>
   1.237 -Players may also provide Glyph coverage for additional Unicode code points
   1.238 +<p data-transform='constraint'>Presentation processors MAY support the extended G2 characters sets that map onto Unicode code points (See table).</p>
   1.239 +Presentation processors may also provide Glyph coverage for additional Unicode code points
   1.240  <section class='color_values'>
   1.241  <h2>Color values</h2>
   1.242 -<p>For color values of the form #rrggbbaa, players MUST support combinations where the rr, gg, bb components may be either 00 or ff; and the aa component may be 00, 54, A8 or FF. e.g: #00ffff54. Additionally players SHOULD support values for rr, gg, and bb of 54 or A8, and MAY support all possible values between 00 to ff.</p>
   1.243 +<p>For color values of the form #rrggbbaa, presentation processors MUST support combinations where the rr, gg, bb components may be either 00 or ff; and the aa component may be 00, 54, A8 or FF. e.g: #00ffff54. Additionally presentation processors SHOULD support values for rr, gg, and bb of 54 or A8, and MAY support all possible values between 00 to ff.</p>
   1.244  <table>
   1.245  <tr>
   1.246  <th>Color</th>