implement actions 43, 45; update latest revision reference to HG repo; update editor affiliation
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/.hgignore Thu Mar 01 01:47:03 2012 -0700
@@ -0,0 +1,3 @@
+syntax: glob
+*~
+*.esc
--- a/ttml10/spec/entitiesedcopy.dtd Fri Feb 24 00:35:39 2012 -0700
+++ b/ttml10/spec/entitiesedcopy.dtd Thu Mar 01 01:47:03 2012 -0700
@@ -19,7 +19,7 @@
<!ENTITY w3c-designation "&prefix;.html">
-<!ENTITY w3c.tr.latest "http://dev.w3.org/cvsweb/~checkout~/2008/tt/spec">
+<!ENTITY w3c.tr.latest "http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec">
<!-- Latest version links. don't touch -->
<!ENTITY latest "&w3c.tr.latest;/&w3c-designation;?content-type=text/html;charset=utf-8">
--- a/ttml10/spec/ttaf1-dfxp.html Fri Feb 24 00:35:39 2012 -0700
+++ b/ttml10/spec/ttaf1-dfxp.html Thu Mar 01 01:47:03 2012 -0700
@@ -76,7 +76,7 @@
<a href="ttaf1-dfxp.html">ttaf1-dfxp.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
-</dd><dt>Editor:</dt><dd>Glenn Adams, Samsung Electronics Co., Ltd.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+</dd><dt>Editor:</dt><dd>Glenn Adams, Cox Communications, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>This document specifies the Timed Text Markup Language (TTML) in terms of a
vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
timed text media for the purpose of interchange among authoring
@@ -416,11 +416,11 @@
H <a href="#other-references">Other References</a> (Non-Normative)<br/>
I <a href="#requirements">Requirements</a> (Non-Normative)<br/>
J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br/>
- J.1 <a href="#d3e17026">Element Derivation</a><br/>
- J.2 <a href="#d3e17505">Attribute Derivation</a><br/>
+ J.1 <a href="#d3e17027">Element Derivation</a><br/>
+ J.2 <a href="#d3e17506">Attribute Derivation</a><br/>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br/>
- K.1 <a href="#d3e18373">Requirements</a><br/>
- K.2 <a href="#d3e18537">Guidelines</a><br/>
+ K.1 <a href="#d3e18374">Requirements</a><br/>
+ K.2 <a href="#d3e18538">Guidelines</a><br/>
L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br/>
M <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br/>
</p></div><hr/><div class="body"><div class="div1">
@@ -2370,7 +2370,7 @@
scaling and the second expresses vertical scaling.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Use of independent horizontal and vertical font sizes is expected to be used
with cell based metrics in order to denote fonts that are two rows in height and
one column in width.</p></div><p>If horizontal and vertical sizes are expressed independently, then the
-metrics of the <a href="#style-value-length"><length></a> values must be the same.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express font size must be non-negative.</p><p>For the purpose of determining applicability of this style property,
+units of the <a href="#style-value-length"><length></a> values must be the same.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express font size must be non-negative.</p><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a specified value of this attribute is not supported,
then a presentation processor must interpret the attribute as if the
@@ -3856,12 +3856,14 @@
<h4><a name="semantics-region-layout-step-2" id="semantics-region-layout-step-2"/>9.3.3 Synchronic Flow Processing</h4><p>Subsequent to performing a temporal (synchronic) slice and subsequent
remapping of regionally selected content hierarchy, the resulting intermediate
synchronic document is subjected to a flow transformation step that produces
-a rooted flow object tree
-
-equivalent to
+a rooted flow object tree represented as
an XSL FO document instance as defined by <a href="#xsl11">[XSL 1.1]</a>,
and semantically extended by TTML specific style properties that have no XSL
-FO counterpart.</p><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a> is mapped
+FO counterpart.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this section, the use of XSL FO is intended to be conceptual only, employed
+solely for the purpose of defining the normative presentation semantics of
+TTML. An actual implementation of this algorithm is not required to create or process
+XSL FO representations. In particular, it is possible to implement these semantics
+using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a> is mapped
to a styled document <em>F</em> consistent with an XSL FO document instance, as follows</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a content element,
synthesize an anonymous span to enclose the text node, substituting
@@ -3871,25 +3873,25 @@
text nodes representing the individual text node children of the
original sequence of anonymous spans;</p></li><li><p>for each span element whose child is a single anonymous span,
replace the anonymous span with its sequence of child text
-nodes;</p></li></ol></li><li><p>resolve styles according to <a href="#semantics-style-resolution-process-overall"><b>8.4.4.4 Style Resolution Process</b></a>;</p></li><li><p>map the <code>tt</code> element to be equivalent to an <code>fo:root</code> element, populated
+nodes;</p></li></ol></li><li><p>resolve styles according to <a href="#semantics-style-resolution-process-overall"><b>8.4.4.4 Style Resolution Process</b></a>;</p></li><li><p>map the <code>tt</code> element to an <code>fo:root</code> element, populated
initially with an <code>fo:layout-master-set</code> element that contains a valid
<code>fo:simple-page-master</code> that, in turn, contains an
<code>fo:region-body</code> child, where the root container extent expressed on the
<code>tt</code> element is mapped to <code>page-width</code> and
<code>page-height</code> attributes on the <code>fo:simple-page-master</code>
-element;</p></li><li><p>map the <code>layout</code> element to be equivalent to an <code>fo:page-sequence</code> element and a
+element;</p></li><li><p>map the <code>layout</code> element to an <code>fo:page-sequence</code> element and a
child <code>fo:flow</code> element that reference the page master and page region
-defined by the simple page master produced above;</p></li><li><p>map each non-empty <code>region</code> element to be equivalent to an <code>fo:block-container</code>
+defined by the simple page master produced above;</p></li><li><p>map each non-empty <code>region</code> element to an <code>fo:block-container</code>
element with an <code>absolute-position</code> attribute with value
<code>absolute</code>, and where the region's position and extent are mapped to equivalent
<code>top</code>, <code>left</code>, <code>width</code>, and <code>height</code>
attributes;</p></li><li><p>for each <code>body</code>, <code>div</code>, and <code>p</code> element that is not
associated with a <code>tts:display</code> style property with the value
-<code>none</code>, map the element to the equivalent of a distinct <code>fo:block</code> element,
+<code>none</code>, map the element to a distinct <code>fo:block</code> element,
populating the style properties of <code>fo:block</code> by using the computed
-style set associated with each original TTML content element;</p></li><li><p>for the resulting <code>fo:block</code> formatting object equivalent
+style set associated with each original TTML content element;</p></li><li><p>for the resulting <code>fo:block</code> formatting object
produced in the previous step that corresponds to the <code>body</code>
-element, map to be equivalent to appending to the end of its children an empty
+element, synthesize and append to the end of its children an empty
<code>fo:block</code> with the following attributes:
<code>space-after.optimum</code>, <code>space-after.maximum</code>, and
<code>space-after.conditionality</code>, where the value of the former
@@ -3901,13 +3903,13 @@
<code>none</code> and for each anonymous
span that is a child of a <code>p</code> or <code>span</code> element,
map the element or
-sequence of character items to be equivalent to a distinct <code>fo:inline</code> element,
+sequence of character items to a distinct <code>fo:inline</code> element,
populating the style properties of <code>fo:inline</code> by using the computed
style set associated with each original TTML content element
or anonymous span;</p></li><li><p>for each <code>br</code> element that is not
associated with a <code>tts:display</code> style property with the value
-<code>none</code>, map the element to be equivalent
-to a distinct <code>fo:character</code> element having the following
+<code>none</code>, map the element to
+a distinct <code>fo:character</code> element having the following
properties:</p><ul><li><p><code>character="&#x000A;"</code></p></li><li><p><code>suppress-at-line-break="retain"</code></p></li></ul></li><li><p>for each TTML style property attribute in some computed
style set that
has no counterpart in <a href="#xsl11">[XSL 1.1]</a>, map that attribute directly through
@@ -5763,7 +5765,8 @@
# .......................................................................
# .......................................................................
-# .......................................................................</pre></div></div><div class="div4">
+# .......................................................................
+</pre></div></div><div class="div4">
<h5><a name="rnc-dfxp-timing-attribs-module" id="rnc-dfxp-timing-attribs-module"/>B.1.2.17 Timing Attributes Module</h5><div class="exampleInner"><pre># .......................................................................
# TT-AF 1.0 DFXP Timing Attributes Module ...............................
# .......................................................................
@@ -8306,7 +8309,7 @@
<h2><a name="derivation" id="derivation"/>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
vocabulary, separately describing derivation of elements and
attributes.</p><div class="div2">
-<h3><a name="d3e17026" id="d3e17026"/>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
+<h3><a name="d3e17027" id="d3e17027"/>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
specifies a TTML element vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
@@ -8361,7 +8364,7 @@
and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e17505" id="d3e17505"/>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
+<h3><a name="d3e17506" id="d3e17506"/>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
specifies a TTML attribute vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
@@ -8433,9 +8436,9 @@
<h2><a name="qa" id="qa"/>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
Framework Specifications Guidelines</a> <a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a name="d3e18373" id="d3e18373"/>K.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a name="d3e18374" id="d3e18374"/>K.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
clause</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td/><td/><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td/><td/><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e18537" id="d3e18537"/>K.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td/><td>NO</td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td/><td/><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td/><td>NO</td><td/><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td/><td/><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td/><td/><td/></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a name="d3e18538" id="d3e18538"/>K.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td/><td>NO</td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td/><td/><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td/><td>NO</td><td/><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td/><td/><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td/><td/><td/></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
<a href="#doctypes">TTML Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
@@ -8485,4 +8488,4 @@
Philipp Hoschka, W3C (leader, Interaction Domain);
Chris Lilley, W3C (chair, SVG WG).
</p><p>The editor wishes to especially acknowledge the following contributions
-by non-members: John Birch (dynamic flow).</p></div></div></body></html>
+by non-members: John Birch (dynamic flow).</p></div></div></body></html>
\ No newline at end of file
--- a/ttml10/spec/ttaf1-dfxp.xml Fri Feb 24 00:35:39 2012 -0700
+++ b/ttml10/spec/ttaf1-dfxp.xml Thu Mar 01 01:47:03 2012 -0700
@@ -96,7 +96,7 @@
<authlist id="editors" role="editor">
<author>
<name>Glenn Adams</name>
-<affiliation>Samsung Electronics Co., Ltd.</affiliation>
+<affiliation>Cox Communications, Inc.</affiliation>
</author>
</authlist>
<authlist id="contributors" role="contributor">
@@ -4055,7 +4055,7 @@
one column in width.</p>
</note>
<p>If horizontal and vertical sizes are expressed independently, then the
-metrics of the <loc href="#style-value-length"><length></loc> values must be the same.</p>
+units of the <loc href="#style-value-length"><length></loc> values must be the same.</p>
<p>The <loc href="#style-value-length"><length></loc> value(s) used to express font size must be non-negative.</p>
<p>For the purpose of determining applicability of this style property,
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
@@ -7178,14 +7178,17 @@
<p>Subsequent to performing a temporal (synchronic) slice and subsequent
remapping of regionally selected content hierarchy, the resulting intermediate
synchronic document is subjected to a flow transformation step that produces
-a rooted flow object tree
-<!-- changed for future CSS compatibility
-represented as
--->
-equivalent to
+a rooted flow object tree represented as
an XSL FO document instance as defined by <bibref ref="xsl11"/>,
and semantically extended by TTML specific style properties that have no XSL
FO counterpart.</p>
+<note>
+<p>In this section, the use of XSL FO is intended to be conceptual only, employed
+solely for the purpose of defining the normative presentation semantics of
+TTML. An actual implementation of this algorithm is not required to create or process
+XSL FO representations. In particular, it is possible to implement these semantics
+using alternative presentation models, such as Cascading Style Sheets (CSS).</p>
+</note>
<p>Each intermediate synchronic document produced by <specref
ref="semantics-region-layout-step-1"/> is mapped
<!-- changed for future CSS compatibility
@@ -7214,7 +7217,7 @@
ref="semantics-style-resolution-process-overall"/>;</p>
</item>
<item>
-<p>map the <el>tt</el> element to be equivalent to an <el>fo:root</el> element, populated
+<p>map the <el>tt</el> element to an <el>fo:root</el> element, populated
initially with an <el>fo:layout-master-set</el> element that contains a valid
<el>fo:simple-page-master</el> that, in turn, contains an
<el>fo:region-body</el> child, where the root container extent expressed on the
@@ -7223,12 +7226,12 @@
element;</p>
</item>
<item>
-<p>map the <el>layout</el> element to be equivalent to an <el>fo:page-sequence</el> element and a
+<p>map the <el>layout</el> element to an <el>fo:page-sequence</el> element and a
child <el>fo:flow</el> element that reference the page master and page region
defined by the simple page master produced above;</p>
</item>
<item>
-<p>map each non-empty <el>region</el> element to be equivalent to an <el>fo:block-container</el>
+<p>map each non-empty <el>region</el> element to an <el>fo:block-container</el>
element with an <att>absolute-position</att> attribute with value
<code>absolute</code>, and where the region's position and extent are mapped to equivalent
<att>top</att>, <att>left</att>, <att>width</att>, and <att>height</att>
@@ -7237,14 +7240,14 @@
<item>
<p>for each <el>body</el>, <el>div</el>, and <el>p</el> element that is not
associated with a <att>tts:display</att> style property with the value
-<code>none</code>, map the element to the equivalent of a distinct <el>fo:block</el> element,
+<code>none</code>, map the element to a distinct <el>fo:block</el> element,
populating the style properties of <el>fo:block</el> by using the computed
style set associated with each original TTML content element;</p>
</item>
<item>
-<p>for the resulting <el>fo:block</el> formatting object equivalent
+<p>for the resulting <el>fo:block</el> formatting object
produced in the previous step that corresponds to the <el>body</el>
-element, map to be equivalent to appending to the end of its children an empty
+element, synthesize and append to the end of its children an empty
<el>fo:block</el> with the following attributes:
<att>space-after.optimum</att>, <att>space-after.maximum</att>, and
<att>space-after.conditionality</att>, where the value of the former
@@ -7259,7 +7262,7 @@
<code>none</code> and for each anonymous
span that is a child of a <el>p</el> or <el>span</el> element,
map the element or
-sequence of character items to be equivalent to a distinct <el>fo:inline</el> element,
+sequence of character items to a distinct <el>fo:inline</el> element,
populating the style properties of <el>fo:inline</el> by using the computed
style set associated with each original TTML content element
or anonymous span;</p>
@@ -7267,8 +7270,8 @@
<item>
<p>for each <el>br</el> element that is not
associated with a <att>tts:display</att> style property with the value
-<code>none</code>, map the element to be equivalent
-to a distinct <el>fo:character</el> element having the following
+<code>none</code>, map the element to
+a distinct <el>fo:character</el> element having the following
properties:</p>
<ulist>
<item>