ttml10/spec/ttaf1-dfxp.xml
changeset 227 5b9abdec7634
parent 225 b2cfc61cf0ff
child 228 d5caeadc62e3
     1.1 --- a/ttml10/spec/ttaf1-dfxp.xml	Fri Feb 24 00:35:39 2012 -0700
     1.2 +++ b/ttml10/spec/ttaf1-dfxp.xml	Thu Mar 01 01:47:03 2012 -0700
     1.3 @@ -96,7 +96,7 @@
     1.4  <authlist id="editors" role="editor">
     1.5  <author>
     1.6  <name>Glenn Adams</name>
     1.7 -<affiliation>Samsung Electronics Co., Ltd.</affiliation>
     1.8 +<affiliation>Cox Communications, Inc.</affiliation>
     1.9  </author>
    1.10  </authlist>
    1.11  <authlist id="contributors" role="contributor">
    1.12 @@ -4055,7 +4055,7 @@
    1.13  one column in width.</p>
    1.14  </note>
    1.15  <p>If horizontal and vertical sizes are expressed independently, then the
    1.16 -metrics of the <loc href="#style-value-length">&lt;length&gt;</loc> values must be the same.</p>
    1.17 +units of the <loc href="#style-value-length">&lt;length&gt;</loc> values must be the same.</p>
    1.18  <p>The <loc href="#style-value-length">&lt;length&gt;</loc> value(s) used to express font size must be non-negative.</p>
    1.19  <p>For the purpose of determining applicability of this style property,
    1.20  each character child of a <el>p</el> element is considered to be enclosed in an anonymous
    1.21 @@ -7178,14 +7178,17 @@
    1.22  <p>Subsequent to performing a temporal (synchronic) slice and subsequent
    1.23  remapping of regionally selected content hierarchy, the resulting intermediate
    1.24  synchronic document is subjected to a flow transformation step that produces 
    1.25 -a rooted flow object tree
    1.26 -<!-- changed for future CSS compatibility 
    1.27 -represented as 
    1.28 --->
    1.29 -equivalent to
    1.30 +a rooted flow object tree represented as 
    1.31  an XSL FO document instance as defined by <bibref ref="xsl11"/>,
    1.32  and semantically extended by TTML specific style properties that have no XSL
    1.33  FO counterpart.</p>
    1.34 +<note>
    1.35 +<p>In this section, the use of XSL FO is intended to be conceptual only, employed
    1.36 +solely for the purpose of defining the normative presentation semantics of
    1.37 +TTML. An actual implementation of this algorithm is not required to create or process
    1.38 +XSL FO representations. In particular, it is possible to implement these semantics
    1.39 +using alternative presentation models, such as Cascading Style Sheets (CSS).</p>
    1.40 +</note>
    1.41  <p>Each intermediate synchronic  document produced by <specref
    1.42  ref="semantics-region-layout-step-1"/> is mapped 
    1.43  <!-- changed for future CSS compatibility 
    1.44 @@ -7214,7 +7217,7 @@
    1.45  ref="semantics-style-resolution-process-overall"/>;</p>
    1.46  </item>
    1.47  <item>
    1.48 -<p>map the <el>tt</el> element to be equivalent to an <el>fo:root</el> element, populated
    1.49 +<p>map the <el>tt</el> element to an <el>fo:root</el> element, populated
    1.50  initially with an <el>fo:layout-master-set</el> element that contains a valid
    1.51  <el>fo:simple-page-master</el> that, in turn, contains an
    1.52  <el>fo:region-body</el> child, where the root container extent expressed on the
    1.53 @@ -7223,12 +7226,12 @@
    1.54  element;</p>
    1.55  </item>
    1.56  <item>
    1.57 -<p>map the <el>layout</el> element to be equivalent to an <el>fo:page-sequence</el> element and a
    1.58 +<p>map the <el>layout</el> element to an <el>fo:page-sequence</el> element and a
    1.59  child <el>fo:flow</el> element that reference the page master and page region
    1.60  defined by the simple page master produced above;</p>
    1.61  </item>
    1.62  <item>
    1.63 -<p>map each non-empty <el>region</el> element to be equivalent to an <el>fo:block-container</el>
    1.64 +<p>map each non-empty <el>region</el> element to an <el>fo:block-container</el>
    1.65  element with an <att>absolute-position</att> attribute with value
    1.66  <code>absolute</code>, and where the region's position and extent are mapped to equivalent
    1.67  <att>top</att>, <att>left</att>, <att>width</att>, and <att>height</att>
    1.68 @@ -7237,14 +7240,14 @@
    1.69  <item>
    1.70  <p>for each <el>body</el>, <el>div</el>, and <el>p</el> element that is not
    1.71  associated with a <att>tts:display</att> style property with the value
    1.72 -<code>none</code>, map the element to the equivalent of a distinct <el>fo:block</el> element,
    1.73 +<code>none</code>, map the element to a distinct <el>fo:block</el> element,
    1.74  populating the style properties of <el>fo:block</el> by using the computed
    1.75  style set associated with each original TTML content element;</p>
    1.76  </item>
    1.77  <item>
    1.78 -<p>for the resulting <el>fo:block</el> formatting object equivalent
    1.79 +<p>for the resulting <el>fo:block</el> formatting object
    1.80  produced in the previous step that corresponds to the <el>body</el>
    1.81 -element, map to be equivalent to appending to the end of its children an empty
    1.82 +element, synthesize and append to the end of its children an empty
    1.83    <el>fo:block</el> with the following attributes:
    1.84  <att>space-after.optimum</att>, <att>space-after.maximum</att>, and
    1.85  <att>space-after.conditionality</att>, where the value of the former
    1.86 @@ -7259,7 +7262,7 @@
    1.87  <code>none</code> and for each anonymous
    1.88  span that is a child of a <el>p</el> or <el>span</el> element,
    1.89  map the element or
    1.90 -sequence of character items to be equivalent to a distinct <el>fo:inline</el> element,
    1.91 +sequence of character items to a distinct <el>fo:inline</el> element,
    1.92  populating the style properties of <el>fo:inline</el> by using the computed
    1.93  style set associated with each original TTML content element
    1.94  or anonymous span;</p>
    1.95 @@ -7267,8 +7270,8 @@
    1.96  <item>
    1.97  <p>for each <el>br</el> element that is not
    1.98  associated with a <att>tts:display</att> style property with the value
    1.99 -<code>none</code>, map the element to be equivalent
   1.100 -to a distinct <el>fo:character</el> element having the following
   1.101 +<code>none</code>, map the element to
   1.102 +a distinct <el>fo:character</el> element having the following
   1.103  properties:</p>
   1.104  <ulist>
   1.105  <item>