SDP-US Technical (7.2.2) - Issue 192
authorGlenn Adams <glenn@skynav.com>
Sun, 11 Nov 2012 18:31:01 -0700
changeset 3075f223c89fac6
parent 306 b119224bba98
child 308 fa62712e44f7
SDP-US Technical (7.2.2) - Issue 192
ttml10-sdp-us/Overview.html
ttml10-sdp-us/Overview.src.html
     1.1 --- a/ttml10-sdp-us/Overview.html	Sun Nov 11 17:09:33 2012 -0700
     1.2 +++ b/ttml10-sdp-us/Overview.html	Sun Nov 11 18:31:01 2012 -0700
     1.3 @@ -1509,8 +1509,12 @@
     1.4  <section class="Core_Constraints" id="constraints-22">
     1.5  <h4><span class="secno">7.2.2 </span>Constraints</h4>
     1.6  <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
     1.7 -<div><div class="numbered" title="R0041">At most 32 characters <em class="rfc2119" title="must">must</em> be present in any displayed text line.</div></div>
     1.8 -<div><div class="numbered" title="R0042">At most one p element <em class="rfc2119" title="must">must</em> be selected into a region at a time.</div></div>
     1.9 +<div><div class="numbered" title="R0041">If the aspect ratio of the root container is 4:3 (16:9), then, respectively, more than 38 (42) characters <em class="rfc2119" title="must not">must not</em> be
    1.10 +present in any displayed text line.</div></div>
    1.11 +<div><div class="numbered" title="R0042">If the aspect ratio of the root container is 4:3 (16:9), then, respectively, more than 152 (168) characters <em class="rfc2119" title="must not">must not</em> be
    1.12 +present in all displayed text lines.</div></div>
    1.13 +<div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>These requirements accommodate content originated in Europe but displayed in the US, as well as content displayed using 16:9 format.</p></div></div>
    1.14 +<div><div class="numbered" title="R0043">At most one p element <em class="rfc2119" title="must">must</em> be selected into a region at a time.</div></div>
    1.15  <div class="note"><div class="note-title"><span>Note</span></div><div class=""><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></div>
    1.16  <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Constraining one p element to a region logically places content from two different speakers to different region(s).</p></div></div>
    1.17  <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>When a document author wants to construct a single phrase from a speaker with more than one line in a region, the br within a p element can be used. This construction adheres to the constraints in this section. For example for one speaker with more than one line:</p></div></div>
    1.18 @@ -1545,17 +1549,17 @@
    1.19  <section class="Core_Constraints" id="constraints-23">
    1.20  <h4><span class="secno">8.1.2 </span>Constraints</h4>
    1.21  <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
    1.22 -<div><div class="numbered" title="R0043">Timing <em class="rfc2119" title="must">must</em> be expressed in the hh:mm:ss.ms or hh:mm:ss:ff format used in the timeExpression.</div></div>
    1.23 -<div><div class="numbered" title="R0044">Timing <em class="rfc2119" title="must">must</em> be expressed in the same format throughout the document.</div></div>
    1.24 -<div><div class="numbered" title="R0045">Presentation processors <em class="rfc2119" title="must">must</em> support durations (dur) on the p and span elements, and <em class="rfc2119" title="may">may</em> (but need not) support on other element types;
    1.25 +<div><div class="numbered" title="R0044">Timing <em class="rfc2119" title="must">must</em> be expressed in the hh:mm:ss.ms or hh:mm:ss:ff format used in the timeExpression.</div></div>
    1.26 +<div><div class="numbered" title="R0045">Timing <em class="rfc2119" title="must">must</em> be expressed in the same format throughout the document.</div></div>
    1.27 +<div><div class="numbered" title="R0046">Presentation processors <em class="rfc2119" title="must">must</em> support durations (dur) on the p and span elements, and <em class="rfc2119" title="may">may</em> (but need not) support on other element types;
    1.28  as such, a document <em class="rfc2119" title="should not">should not</em> use a duration on an element type other than p or span.</div></div>
    1.29 -<div><div class="numbered" title="R0046">For timing in hh:mm:ss.ms, the following format <em class="rfc2119" title="must">must</em> be used:</div></div>
    1.30 +<div><div class="numbered" title="R0047">For timing in hh:mm:ss.ms, the following format <em class="rfc2119" title="must">must</em> be used:</div></div>
    1.31  <ul>
    1.32  <li>Exactly 2 digits <em class="rfc2119" title="must">must</em> be used in each of the hours, minutes, and second components (include leading zeros).</li>
    1.33  <li>Exactly 3 decimal places <em class="rfc2119" title="must">must</em> be used for the milliseconds component (include zeros).</li>
    1.34  </ul>
    1.35  <div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example" style="font-family: Segoe UI; font-size: 13pt; color: black; background: white;"><span style="color:blue;">&lt;</span><span style="color:#a31515;">p</span><span style="color:blue;"> </span><span style="color:red;">begin</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:01.000</span>'<span style="color:blue;"> </span><span style="color:red;">end</span><span style="color:blue;">=</span>'<span style="color:blue;">00:00:11.123</span>'<span style="color:blue;"> </span><span style="color:red;">region</span><span style="color:blue;">=</span>"<span style="color:blue;">r1</span>"<span style="color:blue;"> &gt;</span>Test<span style="color:blue;">&lt;/</span><span style="color:#a31515;">p</span><span style="color:blue;">&gt;</span></pre></div>
    1.36 -<div><div class="numbered" title="R0047">For timing in hh:mm:ss.ms, the following format <em class="rfc2119" title="must">must</em> be used:</div></div>
    1.37 +<div><div class="numbered" title="R0048">For timing in hh:mm:ss.ms, the following format <em class="rfc2119" title="must">must</em> be used:</div></div>
    1.38  <ul>
    1.39  <li>Exactly 2 digits <em class="rfc2119" title="must">must</em> be used in each of the hours, minutes, second, and frame components (include leading zeros).</li>
    1.40  <li>A ttp:frameRate attribute <em class="rfc2119" title="must">must</em> be present on the root element.</li>
    1.41 @@ -1646,10 +1650,10 @@
    1.42  <section class="Core_Constraints" id="constraints-26">
    1.43  <h4><span class="secno">8.4.2 </span>Constraints</h4>
    1.44  <p>Presentation processors <em class="rfc2119" title="must">must</em> support the capability to present documents where the following constraints apply:</p>
    1.45 -<div><div class="numbered" title="R0048">The set element <em class="rfc2119" title="must">must</em> only animate the region or span element.</div></div>
    1.46 -<div><div class="numbered" title="R0049">The use of set elements applied to a region element <em class="rfc2119" title="must">must</em> only animate the tts:display, tts:origin or tts:extent attribute.</div></div>
    1.47 -<div><div class="numbered" title="R0050">The use of set elements applied to a span element <em class="rfc2119" title="must">must</em> only animate the tts:color attribute.</div></div>
    1.48 -<div><div class="numbered" title="R0051">No more than 6 set elements <em class="rfc2119" title="must">must</em> be used within a given element</div></div>
    1.49 +<div><div class="numbered" title="R0049">The set element <em class="rfc2119" title="must">must</em> only animate the region or span element.</div></div>
    1.50 +<div><div class="numbered" title="R0050">The use of set elements applied to a region element <em class="rfc2119" title="must">must</em> only animate the tts:display, tts:origin or tts:extent attribute.</div></div>
    1.51 +<div><div class="numbered" title="R0051">The use of set elements applied to a span element <em class="rfc2119" title="must">must</em> only animate the tts:color attribute.</div></div>
    1.52 +<div><div class="numbered" title="R0052">No more than 6 set elements <em class="rfc2119" title="must">must</em> be used within a given element</div></div>
    1.53  <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Animation is constrained to the scenarios where the region needs to be moved – i.e. when the “snap” display effect is required.</p></div></div>
    1.54  <div class="note"><div class="note-title"><span>Note</span></div><div class=""><p>Animation is constrained to the scenarios to change the foreground color of content when flashing text is required.</p></div></div>
    1.55  </section>
    1.56 @@ -1825,9 +1829,9 @@
    1.57  </section>
    1.58  <section class="appendix" id="code-points">
    1.59  <!--OddPage--><h2><span class="secno">C. </span>Code points</h2>
    1.60 -<div><div class="numbered" title="R0052">Presentation processors <em class="rfc2119" title="should">should</em> provide font glyph coverage for all characters in the “ISO 8859-1 Latin-1” space and those for ANSI INCITS 4 when mapped onto Unicode code points (see table).</div></div>
    1.61 +<div><div class="numbered" title="R0053">Presentation processors <em class="rfc2119" title="should">should</em> provide font glyph coverage for all characters in the “ISO 8859-1 Latin-1” space and those for ANSI INCITS 4 when mapped onto Unicode code points (see table).</div></div>
    1.62  <div class="note"><div class="note-title"><span>Note</span></div><p class="">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></div>
    1.63 -<div><div class="numbered" title="R0053">Presentation processors <em class="rfc2119" title="should">should</em> 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.</div></div>
    1.64 +<div><div class="numbered" title="R0054">Presentation processors <em class="rfc2119" title="should">should</em> 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.</div></div>
    1.65  <table style="border-collapse: collapse;width:630pt; width:835px;border:0">
    1.66  <colgroup>
    1.67  <col style="width:38pt; width:51px">
    1.68 @@ -2840,7 +2844,7 @@
    1.69  <td class="style2" style="width:49px"></td>
    1.70  </tr>
    1.71  </tbody></table>
    1.72 -<div><div class="numbered" title="R0054">Presentation processors <em class="rfc2119" title="may">may</em> support the extended G2 characters sets that map onto Unicode code points (See table).</div></div>
    1.73 +<div><div class="numbered" title="R0055">Presentation processors <em class="rfc2119" title="may">may</em> support the extended G2 characters sets that map onto Unicode code points (See table).</div></div>
    1.74  Presentation processors may also provide Glyph coverage for additional Unicode code points
    1.75  <section class="color_values" id="color-values">
    1.76  <h3><span class="secno">C.1 </span>Color values</h3>
    1.77 @@ -2894,4 +2898,4 @@
    1.78  
    1.79  <section id="references" class="appendix"><!--OddPage--><h2><span class="secno">D. </span>References</h2><section id="normative-references"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
    1.80  </dd><dt id="bib-TTML10">[TTML10]</dt><dd><em>Reference not found.</em>
    1.81 -</dd></dl></section></section><div id="respec-err" style="position: fixed; width: 350px; top: 10px; right: 10px; border: 3px double rgb(255, 0, 0); background-color: rgb(255, 255, 255); display: none; background-position: initial initial; background-repeat: initial initial; " class="removeOnSave"><p style="float: right; margin: 2px; text-decoration: none">[<a href="#">x</a>]</p><ul style="clear: both"><li style="color: #c00">Got 1 tokens looking like a reference, not in biblio DB: </li><li style="color: #c00">Bad ref: TTML10, count = 1</li></ul></div></body></html>
    1.82 \ No newline at end of file
    1.83 +</dd></dl></section></section></body></html>
    1.84 \ No newline at end of file
     2.1 --- a/ttml10-sdp-us/Overview.src.html	Sun Nov 11 17:09:33 2012 -0700
     2.2 +++ b/ttml10-sdp-us/Overview.src.html	Sun Nov 11 18:31:01 2012 -0700
     2.3 @@ -1319,7 +1319,11 @@
     2.4  <section class='Core_Constraints'>
     2.5  <h4>Constraints</h4>
     2.6  <p>Presentation processors MUST support the capability to present documents where the following constraints apply:</p>
     2.7 -<div data-transform='constraint'>At most 32 characters MUST be present in any displayed text line.</div>
     2.8 +<div data-transform='constraint'>If the aspect ratio of the root container is 4:3 (16:9), then, respectively, more than 38 (42) characters MUST NOT be
     2.9 +present in any displayed text line.</div>
    2.10 +<div data-transform='constraint'>If the aspect ratio of the root container is 4:3 (16:9), then, respectively, more than 152 (168) characters MUST NOT be
    2.11 +present in all displayed text lines.</div>
    2.12 +<div class="note"><p>These requirements accommodate content originated in Europe but displayed in the US, as well as content displayed using 16:9 format.</p></div>
    2.13  <div data-transform='constraint'>At most one p element MUST be selected into a region at a time.</div>
    2.14  <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>
    2.15  <div class="note"><p>Constraining one p element to a region logically places content from two different speakers to different region(s).</p></div>