--- a/ttml2/spec/ttml2.html Fri Aug 01 12:23:46 2014 +0200
+++ b/ttml2/spec/ttml2.html Fri Aug 01 12:24:20 2014 +0200
@@ -82,9 +82,9 @@
.obsoleted { background-color: #f26d7d }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2014/07/31 04:10:32 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2014/08/01 03:08:50 $<div id="revisions"></div><div class="head">
<h1><a id="title"></a>Timed Text Markup Language 2 (TTML2)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/07/31 04:10:32 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/08/01 03:08:50 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ttml2.html">ttml2.html</a>
</dd><dt>Latest version:</dt><dd><a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8">https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.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>
@@ -254,7 +254,7 @@
9.3.2 <a href="#semantics-inline-regions">Inline Regions</a><br>
9.3.3 <a href="#semantics-region-layout-step-1">Intermediate Synchronic Document Construction</a><br>
9.3.4 <a href="#semantics-region-layout-step-2">Synchronic Flow Processing</a><br>
- 9.3.5 <a href="#semantics-region-layout-example">Elaborated Example (Informative)</a><br>
+ 9.3.5 <a href="#semantics-region-layout-example">Elaborated Example (Non-Normative)</a><br>
9.4 <a href="#semantics-line-layout">Line Layout</a><br>
10 <a href="#timing">Timing</a><br>
10.1 <a href="#timing-element-vocabulary">Timing Element Vocabulary</a><br>
@@ -278,11 +278,9 @@
11.3.2 <a href="#animation-value-animationValueList"><animationValueList></a><br>
11.3.3 <a href="#animation-value-calcMode"><calcMode></a><br>
11.3.4 <a href="#animation-value-fill"><fill></a><br>
- 11.3.5 <a href="#animation-value-fragmentIdentifier"><fragmentIdentifier></a><br>
- 11.3.6 <a href="#animation-value-keySplines"><keySplines></a><br>
- 11.3.7 <a href="#animation-value-keyTimes"><keyTimes></a><br>
- 11.3.8 <a href="#animation-value-qualifiedName"><qualifiedName></a><br>
- 11.3.9 <a href="#animation-value-repeatCount"><repeatCount></a><br>
+ 11.3.5 <a href="#animation-value-keySplines"><keySplines></a><br>
+ 11.3.6 <a href="#animation-value-keyTimes"><keyTimes></a><br>
+ 11.3.7 <a href="#animation-value-repeatCount"><repeatCount></a><br>
12 <a href="#metadata">Metadata</a><br>
12.1 <a href="#metadata-element-vocabulary">Metadata Element Vocabulary</a><br>
12.1.1 <a href="#metadata-vocabulary-metadata">metadata</a><br>
@@ -435,11 +433,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="#d3e25238">Element Derivation</a><br>
- J.2 <a href="#d3e25755">Attribute Derivation</a><br>
+ J.1 <a href="#d3e25233">Element Derivation</a><br>
+ J.2 <a href="#d3e25750">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e26748">Requirements</a><br>
- K.2 <a href="#d3e26912">Guidelines</a><br>
+ K.1 <a href="#d3e26743">Requirements</a><br>
+ K.2 <a href="#d3e26907">Guidelines</a><br>
L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
M <a href="#concrete-encoding">Concrete Encoding</a><br>
N <a href="#time-expression-semantics">Time Expression Semantics</a><br>
@@ -756,7 +754,9 @@
the <a href="#terms-document-processing-context">document processing context</a> in accordance with the
<a href="#terms-related-media-object">related media object</a> or other processing criteria.</p></dd><dt class="label"><a id="terms-synthetic-smpte-document-syncbase"></a>[synthetic smpte document syncbase]</dt><dd><p>A <a href="#terms-synthetic-document-syncbase">synthetic document syncbase</a> constructed from <a href="#terms-smpte-time-code">smpte time code</a>
values embedded in or associated with the <a href="#terms-related-media-object">related media object</a> or
-otherwise determined by the <a href="#terms-document-processing-context">document processing context</a>.</p></dd><dt class="label"><a id="terms-timed-text"></a>[timed text]</dt><dd><p>Textual information that is intrinsically or extrinsically
+otherwise determined by the <a href="#terms-document-processing-context">document processing context</a>.</p></dd><dt class="label"><a id="terms-temporally-active"></a>[temporally active]</dt><dd><p>A syntactic or semantic feature, e.g., an element or the presentation of an element, is
+<em>temporally active</em> when the current time of selected time base intersects with the
+active time interval of the feature.</p></dd><dt class="label"><a id="terms-temporally-active-region"></a>[temporally active]</dt><dd><p>A <a href="#terms-region">region</a> that is <a href="#terms-temporally-active">temporally active</a>.</p></dd><dt class="label"><a id="terms-timed-text"></a>[timed text]</dt><dd><p>Textual information that is intrinsically or extrinsically
associated with timing information.</p></dd><dt class="label"><a id="terms-timed-text-markup-language"></a>[timed text markup language]</dt><dd><p>A content type that represents timed text media for the purpose of
interchange among authoring systems.</p></dd><dt class="label"><a id="terms-timed-text-authoring-system"></a>[timed text authoring system]</dt><dd><p>A content authoring system capable of importing and exporting
Timed Text Markup Language content.</p></dd><dt class="label"><a id="terms-top-level-profile"></a>[top-level profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined by a <code>ttp:profile</code> element that appears as a child
@@ -880,11 +880,11 @@
<h4><a id="conformance-transformation-processor"></a>3.2.2 Transformation Processor Conformance</h4><p>A TTML <a href="#terms-content-processor">content processor</a> is a conformant TTML <a href="#terms-transformation-processor">transformation processor</a> if
the following criteria are satisfied:</p><ol class="enumar"><li><p>The processor satisfies all requirements specified by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the TTML Transformation profile as specified
-by <a href="#profile-ttml2-transformation"><b>F.1 TTML2 Transformation Profile</b></a>.</p></li></ol></div><div class="div3">
+by <a href="#profile-ttml2-transformation"><b>F.1 TTML2 Transformation Profile</b></a>.</p></li></ol><table border="1" class="ednote" summary="Editorial note: Mandatory Support for DFXP Transformation Profile"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Mandatory Support for DFXP Transformation Profile</b></td><td align="right" valign="top">2014-07-31</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Should we also require support for DFXP Transformation Profile?</td></tr></table></div><div class="div3">
<h4><a id="conformance-presentation-processor"></a>3.2.3 Presentation Processor Conformance</h4><p>A TTML <a href="#terms-content-processor">content processor</a> is a conformant TTML <a href="#terms-presentation-processor">presentation processor</a> if
the following criteria are satisfied:</p><ol class="enumar"><li><p>The processor satisfies all requirements specified by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the TTML Presentation profile as specified
-by <a href="#profile-ttml2-presentation"><b>F.2 TTML2 Presentation Profile</b></a>.</p></li></ol></div></div><div class="div2">
+by <a href="#profile-ttml2-presentation"><b>F.2 TTML2 Presentation Profile</b></a>.</p></li></ol><table border="1" class="ednote" summary="Editorial note: Mandatory Support for DFXP Presentation Profile"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Mandatory Support for DFXP Presentation Profile</b></td><td align="right" valign="top">2014-07-31</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Should we also require support for DFXP Presentation Profile?</td></tr></table></div></div><div class="div2">
<h3><a id="claims"></a>3.3 Claims</h3><p>Any claim of compliance with respect to the conformance of a TTML <a href="#terms-document-instance">document instance</a> or
<a href="#terms-content-processor">content processor</a> must make
reference to an implementation compliance statement (ICS).</p><p>An implementation compliance statement must identify all mandatory
@@ -2735,7 +2735,7 @@
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>,
<a href="#content-vocabulary-span"><code>span</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><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>The <code>tts:backgroundColor</code> style is illustrated by the following example.</p><a id="style-attribute-backgroundColor-example-1"></a><table class="example"><caption>Example Fragment – Background Color</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -2770,7 +2770,7 @@
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>,
<a href="#content-vocabulary-span"><code>span</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous (color and width only)</td></tr></tbody></table><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 no border width is specified in the value of the <code>tts:border</code> property,
then the border width must be interpreted as if a width of
@@ -2807,7 +2807,7 @@
<a href="#style-value-color"><color></a>
</td></tr><tr><td><em>Initial:</em></td><td>see prose</td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#content-vocabulary-span"><code>span</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><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>The initial value of the <code>tts:color</code> property
is considered to be implementation dependent. In the absence of
@@ -2994,7 +2994,7 @@
<a href="#content-vocabulary-div"><code>div</code></a>,
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a>
specifications, then they must be interpreted as <em>width</em>
and <em>height</em>, where the first specification is the
<em>width</em>, and the second specification is the <em>height</em>.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express extent must be non-negative.</p><p>If the value of this attribute is <code>auto</code>, then the computed value
@@ -3089,7 +3089,7 @@
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>if not <a href="#content-vocabulary-span"><code>region</code></a> element,
then relative to parent element's font size; otherwise, relative to the
-<a href="#terms-computed-cell-size">computed cell size</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a single <a href="#style-value-length"><length></a> value is specified, then this length applies
+<a href="#terms-computed-cell-size">computed cell size</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If a single <a href="#style-value-length"><length></a> value is specified, then this length applies
equally to horizontal and vertical scaling of a glyph's EM square; if two
<a href="#style-value-length"><length></a> values are specified, then the first expresses the horizontal
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
@@ -3215,7 +3215,7 @@
<a href="#style-value-length"><length></a>
</td></tr><tr><td><em>Initial:</em></td><td><code>normal</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#content-vocabulary-p"><code>p</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute is <code>normal</code>, then the
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If the value of this attribute is <code>normal</code>, then the
computed value of this style property is determined as follows:</p><ol class="enumar"><li><p>
Let <em>P</em> be the <code>p</code> element to which this style property applies.
</p></li><li><p>
@@ -3285,7 +3285,7 @@
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>,
<a href="#content-vocabulary-span"><code>span</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>The <code>tts:opacity</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Enhance Opacity Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Enhance Opacity Example</b></td><td align="right" valign="top">2013-08-26</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Enhance opacity example to demonstrate opacity on content elements.</td></tr></table><p></p><a id="style-attribute-opacity-example-1"></a><table class="example"><caption>Example Fragment – Opacity</caption><tbody><tr><td>
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>The <code>tts:opacity</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Enhance Opacity Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Enhance Opacity Example</b></td><td align="right" valign="top">2013-08-26</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Enhance opacity example to demonstrate opacity on content elements.</td></tr></table><p></p><a id="style-attribute-opacity-example-1"></a><table class="example"><caption>Example Fragment – Opacity</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1" dur="5s">
<set begin="0s" dur="1s" <span class="strong">tts:opacity="1.00"</span>/>
@@ -3329,7 +3329,7 @@
<a href="#content-vocabulary-div"><code>div</code></a>,
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a> specifications,
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a> specifications,
then they must be interpreted as <em>x</em> and <em>y</em> coordinates, where the first specification
is the <em>x</em> coordinate, and the second specification is the <em>y</em> coordinate.</p><p>If the value of this attribute is <code>auto</code>, then the computed value
of the style property must be considered to be the same as the origin of the <a href="#terms-root-container-region">root container region</a>.</p><p>If a <code>tts:origin</code> attribute is specified on a <code>div</code> or <code>p</code> element, then that specification must be considered to be
@@ -3434,7 +3434,7 @@
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>,
<a href="#content-vocabulary-span"><code>span</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of containing region</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of one <a href="#style-value-length"><length></a> specification,
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of containing region</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If the value of this attribute consists of one <a href="#style-value-length"><length></a> specification,
then that length applies to all edges of the affected areas. If the value
consists of two <a href="#style-value-length"><length></a> specifications, then the first applies to the
before and after edges, and the second applies to the start and end edges.
@@ -3485,7 +3485,9 @@
background color of a region is always rendered when performing presentation
processing on a visual medium; if the value is <code>whenActive</code>,
then the background color of a region is rendered only when some
-content is flowed into the region.</p><p>If a computed value of the property associated with this attribute is not supported,
+content is flowed into the region.</p><p>A region satisfies the <code>whenActive</code> case if (1) it is a
+<a href="#terms-temporally-active-region">temporally active region</a> and (2) content is selected into the region,
+where that content is also <a href="#terms-temporally-active">temporally active</a>.</p><p>If a computed value of the property associated with this attribute is not supported,
then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>always</code>.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><a id="style-attribute-showBackground-example-1"></a><table class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -3649,7 +3651,7 @@
<a href="#style-value-length"><length></a>?
</td></tr><tr><td><em>Initial:</em></td><td><code>none</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#content-vocabulary-span"><code>span</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><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>The value of this attribute consists of an optional <a href="#style-value-color"><color></a> term
followed by one or two <a href="#style-value-length"><length></a> terms. If a <em>color</em> term is
@@ -3874,7 +3876,7 @@
<a href="#style-value-integer"><integer></a>
</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If two areas are associated with the same Z-index value, then, if those areas
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous (over integral values only)</td></tr></tbody></table><p>If two areas are associated with the same Z-index value, then, if those areas
overlap in space, the area(s) generated by lexically subsequent elements must be
rendered over area(s) generated by lexically prior elements, where lexical
order is defined as the postorder traversal of a <a href="#terms-document-instance">document instance</a>.</p><p>The semantics of the value <code>auto</code> are those defined by
@@ -4691,7 +4693,7 @@
flow in a region.</p></div></div></div><div class="div2">
<h3><a id="semantics-region-layout"></a>9.3 Region Layout and Presentation</h3><p>This section defines the semantics of region layout and
presentation in terms of a standard processing model as
-follows:</p><ul><li><p><a href="#semantics-default-region"><b>9.3.1 Default Region</b></a></p></li><li><p><a href="#semantics-inline-regions"><b>9.3.2 Inline Regions</b></a></p></li><li><p><a href="#semantics-region-layout-step-1"><b>9.3.3 Intermediate Synchronic Document Construction</b></a></p></li><li><p><a href="#semantics-region-layout-step-2"><b>9.3.4 Synchronic Flow Processing</b></a></p></li><li><p><a href="#semantics-region-layout-example"><b>9.3.5 Elaborated Example (Informative)</b></a></p></li></ul><p>Any
+follows:</p><ul><li><p><a href="#semantics-default-region"><b>9.3.1 Default Region</b></a></p></li><li><p><a href="#semantics-inline-regions"><b>9.3.2 Inline Regions</b></a></p></li><li><p><a href="#semantics-region-layout-step-1"><b>9.3.3 Intermediate Synchronic Document Construction</b></a></p></li><li><p><a href="#semantics-region-layout-step-2"><b>9.3.4 Synchronic Flow Processing</b></a></p></li><li><p><a href="#semantics-region-layout-example"><b>9.3.5 Elaborated Example (Non-Normative)</b></a></p></li></ul><p>Any
implementation is permitted provided that the externally observable
results are consistent with the results produced by this model.
</p><div class="div3">
@@ -4989,7 +4991,7 @@
to satisfy alignment in the block progression dimension. For example, this assures that
the background color associated with the <code>body</code> element, if not <code>transparent</code>,
will fill the containing region wholly.</p></div></div><div class="div3">
-<h4><a id="semantics-region-layout-example"></a>9.3.5 Elaborated Example (Informative)</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><a id="region-mapping-example-1-s"></a><table class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
+<h4><a id="semantics-region-layout-example"></a>9.3.5 Elaborated Example (Non-Normative)</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><a id="region-mapping-example-1-s"></a><table class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
xmlns="http://www.w3.org/ns/ttml"
xmlns:tts="http://www.w3.org/ns/ttml#styling">
@@ -5411,7 +5413,12 @@
core vocabulary catalog, where
animation is to be understood as a separable layer of information that combines
timing and styling in order to denote authorial intention about (temporally) dynamic
-styling of content.</p><div class="div2">
+styling of content.</p><table border="1" class="ednote" summary="Editorial note: Out-of-Line Animation Time Containment"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Out-of-Line Animation Time Containment</b></td><td align="right" valign="top">2014-07-31</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Support ability for author to declare whether a referenced out-of-line animation's timing is relative
+to its <code>animation</code> container element's timing or relative to the referring element's timing.
+For example, add an <code>@animateTimeContainer</code> attribute optionally used with the newly defined
+<code>@animate</code> attribute, where value can be <code>normal</code> (the default value) or <code>self</code>, and where <code>normal</code>
+means timing is with respect to the out-of-line animation element's ancestor <code>animation</code> container and <code>self</code> means timing is
+with respect to the referring element.</td></tr></table><div class="div2">
<h3><a id="animation-element-vocabulary"></a>11.1 Animation Element Vocabulary</h3><p>The following elements specify the structure and principal animation aspects of a
<a href="#terms-document-instance">document instance</a>:</p><ul><li><p><a href="#animation-vocabulary-animation"><b>11.1.1 animation</b></a></p></li><li><p><a href="#animation-vocabulary-animate"><b>11.1.2 animate</b></a></p></li><li><p><a href="#animation-vocabulary-set"><b>11.1.3 set</b></a></p></li></ul><div class="div3">
<h4><a id="animation-vocabulary-animation"></a>11.1.1 animation</h4><p>The <code>animation</code> element is a container element used to group
@@ -5604,7 +5611,7 @@
which has a <a href="#animation-vocabulary-animation"><code>animation</code></a> element as an ancestor.</p><p>A given IDREF must not appear more than one time in the value of an <code>animate</code>
attribute.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See the specific element type definitions that permit use of the
<code>animate</code> attribute.</p></div></div></div><div class="div2">
-<h3><a id="animation-value-expressions"></a>11.3 Animation Value Expressions</h3><p>Animation attribute values include the use of the following expressions:</p><ul><li><p><a href="#animation-value-animationValue"><b>11.3.1 <animationValue></b></a></p></li><li><p><a href="#animation-value-animationValueList"><b>11.3.2 <animationValueList></b></a></p></li><li><p><a href="#animation-value-calcMode"><b>11.3.3 <calcMode></b></a></p></li><li><p><a href="#animation-value-fill"><b>11.3.4 <fill></b></a></p></li><li><p><a href="#animation-value-fragmentIdentifier"><b>11.3.5 <fragmentIdentifier></b></a></p></li><li><p><a href="#animation-value-keySplines"><b>11.3.6 <keySplines></b></a></p></li><li><p><a href="#animation-value-keyTimes"><b>11.3.7 <keyTimes></b></a></p></li><li><p><a href="#animation-value-qualifiedName"><b>11.3.8 <qualifiedName></b></a></p></li><li><p><a href="#animation-value-repeatCount"><b>11.3.9 <repeatCount></b></a></p></li></ul><div class="div3">
+<h3><a id="animation-value-expressions"></a>11.3 Animation Value Expressions</h3><p>Animation attribute values include the use of the following expressions:</p><ul><li><p><a href="#animation-value-animationValue"><b>11.3.1 <animationValue></b></a></p></li><li><p><a href="#animation-value-animationValueList"><b>11.3.2 <animationValueList></b></a></p></li><li><p><a href="#animation-value-calcMode"><b>11.3.3 <calcMode></b></a></p></li><li><p><a href="#animation-value-fill"><b>11.3.4 <fill></b></a></p></li><li><p><a href="#animation-value-keySplines"><b>11.3.5 <keySplines></b></a></p></li><li><p><a href="#animation-value-keyTimes"><b>11.3.6 <keyTimes></b></a></p></li><li><p><a href="#animation-value-repeatCount"><b>11.3.7 <repeatCount></b></a></p></li></ul><div class="div3">
<h4><a id="animation-value-animationValue"></a>11.3.1 <animationValue></h4><p>An <animationValue> expression is used to specify the starting (initial), intermediate,
or ending (final) of the attribute targeted by the animation.</p><a id="animationValue-syntax"></a><table class="syntax"><caption>Syntax Representation – <animationValue></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -5612,7 +5619,8 @@
: string
</pre></div>
</td></tr></tbody></table><p>The syntax of an <animationValue> expression must satisfy all syntax
-requirements that apply to the attribute targeted by the animation.</p><p>The semantics of an <animationValue> expression are those defined by
+requirements that apply to the attribute targeted by the animation.</p><table border="1" class="ednote" summary="Editorial note: Improve Syntax of AnimationValue"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Improve Syntax of AnimationValue</b></td><td align="right" valign="top">2014-07-31</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Enhance detail of syntax of <animationValue> in order to prevent appearance of an unquoted or unescaped semicolon,
+which is used as a delimiter between animation values in <animationValueList>.</td></tr></table><p>The semantics of an <animationValue> expression are those defined by
<a href="#svg11">[SVG 1.1]</a>, §19.2.9.</p></div><div class="div3">
<h4><a id="animation-value-animationValueList"></a>11.3.2 <animationValueList></h4><p>An <animationValueList> expression is used to specify a list of animation values that sequentially
apply to the attribute targeted by the animation, wherein each pair of values is separated by a SEMICOLON (U+003B) character
@@ -5641,41 +5649,7 @@
</pre></div>
</td></tr></tbody></table><p>The semantics of a <fill> expression are those defined by
<a href="#svg11">[SVG 1.1]</a>, §19.2.8.</p></div><div class="div3">
-<h4><a id="animation-value-fragmentIdentifier"></a>11.3.5 <fragmentIdentifier></h4><p>A <fragmentIdentifier> expression is used to target (refer to) an animation to a specific element in the same <a href="#terms-document-instance">document instance</a>.</p><a id="fragmentIdentifier-syntax"></a><table class="syntax"><caption>Syntax Representation – <fragmentIdentifier></caption><tbody><tr><td>
-<div class="exampleInner"><pre>
-<fragmentIdentifier>
- : "#" fragment
-
-fragment
- : uric+
-
-uric
- : reserved
- | unreserved
- | escaped
-
-reserved
- : [;/?:@&=+$,]
-
-unreserved
- : [a-zA-Z]
- | [0-9]
- | [-_.!~*'()]
-
-escaped
- : "%" hex hex
-
-hex
- : [0-9a-fA-F]
-</pre></div>
-</td></tr></tbody></table><p>Except for the constraints on syntax and semantics that follow below, the semantics of a <fragmentIdentifier>
-expression are those defined to apply to an "<iri>" expression in <a href="#svg11">[SVG 1.1]</a>, §19.2.4.</p><p>A <fragmentIdentifer> must adhere
-to the <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>. Furthermore, it
-must adhere to the fragment identifer syntax defined by <a href="#uri">[URI]</a>,
-Section 4.1, and is a strict subset thereof, since at least one character must appear in
-the fragment component.</p><p>No linear white-space (LWSP) is permitted to appear within a fragment identifier.</p><p>A <fragmentIdentifer> expression must refer to an element in the same <a href="#terms-document-instance">document instance</a>,
-i.e., the fragment component must be a valid IDREF.</p></div><div class="div3">
-<h4><a id="animation-value-keySplines"></a>11.3.6 <keySplines></h4><p>An <keySplines> expression is used to specify a list of Bezier control points that control the pacing of an
+<h4><a id="animation-value-keySplines"></a>11.3.5 <keySplines></h4><p>An <keySplines> expression is used to specify a list of Bezier control points that control the pacing of an
animation, wherein each pair of values is separated by a SEMICOLON (U+003B) character
optionally surrounded by linear white-space (LWSP) characters.</p><a id="keySplines-syntax"></a><table class="syntax"><caption>Syntax Representation – <keySplines></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -5704,7 +5678,7 @@
</pre></div>
</td></tr></tbody></table><p>The semantics of a <keySplines> expression are those defined by
<a href="#svg11">[SVG 1.1]</a>, §19.2.9, as apply to the <code>keySplines</code> attribute.</p></div><div class="div3">
-<h4><a id="animation-value-keyTimes"></a>11.3.7 <keyTimes></h4><p>An <keyTimes> expression is used to specify a list of relative time values that control the pacing of an
+<h4><a id="animation-value-keyTimes"></a>11.3.6 <keyTimes></h4><p>An <keyTimes> expression is used to specify a list of relative time values that control the pacing of an
animation, wherein each pair of values is separated by a SEMICOLON (U+003B) character
optionally surrounded by linear white-space (LWSP) characters.</p><a id="keyTimes-syntax"></a><table class="syntax"><caption>Syntax Representation – <keyTimes></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -5724,24 +5698,7 @@
</pre></div>
</td></tr></tbody></table><p>The semantics of a <keyTimes> expression are those defined by
<a href="#svg11">[SVG 1.1]</a>, §19.2.9, as apply to the <code>keyTimes</code> attribute.</p></div><div class="div3">
-<h4><a id="animation-value-qualifiedName"></a>11.3.8 <qualifiedName></h4><p>A <qualifiedName> expression is used to specify the attribute targeted by the animation.</p><a id="qualifiedName-syntax"></a><table class="syntax"><caption>Syntax Representation – <qualifiedName></caption><tbody><tr><td>
-<div class="exampleInner"><pre>
-<qualifiedName>
- : prefix ":" local
- | local
-
-prefix
- : <em>nmchar</em>+
-
-local
- : <em>nmchar</em>+
-</pre></div>
-</td></tr></tbody></table><p>The syntactic element <em><code>nmchar</code></em> is to be interpreted according
-to the <code>NameChar</code> production defined by <a href="#xml10">[XML 1.0]</a> §2.3,
-except that the COLON (U+003A) character is excluded.</p><p>The semantics of a <qualifiedName> expression are those defined by
-<a href="#svg11">[SVG 1.1]</a>, §19.2.5, as applying to an <code>attributeName</code> attribute
-according to an implied <code>attributeType</code> of <code>XML</code>.</p></div><div class="div3">
-<h4><a id="animation-value-repeatCount"></a>11.3.9 <repeatCount></h4><p>A <repeatCount> expression is used to determine the number of iterations of a repeated animation.</p><a id="repeatCount-syntax"></a><table class="syntax"><caption>Syntax Representation – <repeatCount></caption><tbody><tr><td>
+<h4><a id="animation-value-repeatCount"></a>11.3.7 <repeatCount></h4><p>A <repeatCount> expression is used to determine the number of iterations of a repeated animation.</p><a id="repeatCount-syntax"></a><table class="syntax"><caption>Syntax Representation – <repeatCount></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<repeatCount>
: count
@@ -6042,13 +5999,13 @@
specification takes precedence.</p><div class="div2">
<h3><a id="ttml-schema-rnc"></a>B.1 Relax NG Compact (RNC) Schema</h3><p>A Relax NG Compact Syntax (RNC) <a href="#rng">[RELAX NG]</a> based schema
for TTML Content is available at <a href="rnc/schema.zip">ZIP
-Archive</a>. This schema does not normatively define the validity
+Archive</a>. This schema is to be considered non-normative for the purpose of defining the validity
of Timed Text Markup Language content as defined by this specification.
In particular, the formal validity of TTML Content
is defined by <a href="#conformance-content"><b>3.1 Content Conformance</b></a>.</p></div><div class="div2">
<h3><a id="ttml-schema-xsd"></a>B.2 XML Schema Definition (XSD) Schema</h3><p>A W3C XML Schema Definition (XSD) <a href="#xsd-1">[XML Schema Part 1]</a> based schema
for TTML Content is available at <a href="xsd/schema.zip">ZIP
-Archive</a>. This schema does not normatively define the validity
+Archive</a>. This schema is to be considered non-normative for the purpose of defining the validity
of Timed Text Markup Language content as defined by this specification.
In particular, the formal validity of TTML Content
is defined by <a href="#conformance-content"><b>3.1 Content Conformance</b></a>.</p></div></div><div class="div1">
@@ -7647,7 +7604,7 @@
<h2><a id="derivation"></a>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 id="d3e25238"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
+<h3><a id="d3e25233"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-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
@@ -7704,7 +7661,7 @@
and <code>@version</code> on the <code>svg:svg</code> element.</p></li><li><p>Conceptually derived from existing <code>tt:layout</code> element,
which is a generic container for layout specifications, but for use
in defining animation specifications that apply to targeted elements.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e25755"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
+<h3><a id="d3e25750"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-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
@@ -7796,9 +7753,9 @@
<h2><a id="qa"></a>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 id="d3e26748"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-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 id="d3e26743"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-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></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></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></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></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></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></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></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></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></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></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></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></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></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 id="d3e26912"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-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></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></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></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><td>NO</td><td></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><td></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></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></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></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></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></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></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><td>NO</td><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></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></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></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></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></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></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></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></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></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></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></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 id="d3e26907"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-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></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></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></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><td>NO</td><td></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><td></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></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></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></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></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></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></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><td>NO</td><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></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></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></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></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></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></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></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></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></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></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></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
TTML <a href="#doctypes">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">
--- a/ttml2/spec/ttml2.xml Fri Aug 01 12:23:46 2014 +0200
+++ b/ttml2/spec/ttml2.xml Fri Aug 01 12:24:20 2014 +0200
@@ -949,6 +949,20 @@
otherwise determined by the <loc href="#terms-document-processing-context">document processing context</loc>.</p>
</def>
</gitem>
+<gitem id="terms-temporally-active">
+<label>[temporally active]</label>
+<def>
+<p>A syntactic or semantic feature, e.g., an element or the presentation of an element, is
+<emph>temporally active</emph> when the current time of selected time base intersects with the
+active time interval of the feature.</p>
+</def>
+</gitem>
+<gitem id="terms-temporally-active-region">
+<label>[temporally active]</label>
+<def>
+<p>A <loc href="#terms-region">region</loc> that is <loc href="#terms-temporally-active">temporally active</loc>.</p>
+</def>
+</gitem>
<gitem id="terms-timed-text">
<label>[timed text]</label>
<def>
@@ -1248,6 +1262,11 @@
by <specref ref="profile-ttml2-transformation"/>.</p>
</item>
</olist>
+<ednote>
+<name>Mandatory Support for DFXP Transformation Profile</name>
+<date>2014-07-31</date>
+<edtext>Should we also require support for DFXP Transformation Profile?</edtext>
+</ednote>
</div3> <!-- conformance-transformation-processor -->
<div3 id="conformance-presentation-processor">
@@ -1264,6 +1283,11 @@
by <specref ref="profile-ttml2-presentation"/>.</p>
</item>
</olist>
+<ednote>
+<name>Mandatory Support for DFXP Presentation Profile</name>
+<date>2014-07-31</date>
+<edtext>Should we also require support for DFXP Presentation Profile?</edtext>
+</ednote>
</div3> <!-- conformance-presentation-processor -->
</div2> <!-- conformance-processor -->
@@ -5079,7 +5103,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -5171,7 +5195,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous (color and width only)</td>
</tr>
</tbody>
</table>
@@ -5282,7 +5306,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -5708,7 +5732,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -5925,7 +5949,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -6239,7 +6263,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -6385,7 +6409,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -6502,7 +6526,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -6729,7 +6753,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -6852,6 +6876,9 @@
processing on a visual medium; if the value is <code>whenActive</code>,
then the background color of a region is rendered only when some
content is flowed into the region.</p>
+<p>A region satisfies the <code>whenActive</code> case if (1) it is a
+<loc href="#terms-temporally-active-region">temporally active region</loc> and (2) content is selected into the region,
+where that content is also <loc href="#terms-temporally-active">temporally active</loc>.</p>
<p>If a computed value of the property associated with this attribute is not supported,
then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>always</code>.</p>
<p>The <att>tts:showBackground</att> style is illustrated by the following example.</p>
@@ -7227,7 +7254,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous</td>
</tr>
</tbody>
</table>
@@ -7751,7 +7778,7 @@
</tr>
<tr>
<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td>discrete, continuous (over integral values only)</td>
</tr>
</tbody>
</table>
@@ -9823,7 +9850,7 @@
</note>
</div3>
<div3 id="semantics-region-layout-example">
-<head>Elaborated Example (Informative)</head>
+<head>Elaborated Example (Non-Normative)</head>
<p>An example of the processing steps described above is elaborated below, starting with <specref
ref="region-mapping-example-1-s"/>.</p>
<table id="region-mapping-example-1-s" role="example">
@@ -10206,6 +10233,16 @@
animation is to be understood as a separable layer of information that combines
timing and styling in order to denote authorial intention about (temporally) dynamic
styling of content.</p>
+<ednote>
+<name>Out-of-Line Animation Time Containment</name>
+<date>2014-07-31</date>
+<edtext>Support ability for author to declare whether a referenced out-of-line animation's timing is relative
+to its <el>animation</el> container element's timing or relative to the referring element's timing.
+For example, add an <code>@animateTimeContainer</code> attribute optionally used with the newly defined
+<code>@animate</code> attribute, where value can be <code>normal</code> (the default value) or <code>self</code>, and where <code>normal</code>
+means timing is with respect to the out-of-line animation element's ancestor <el>animation</el> container and <code>self</code> means timing is
+with respect to the referring element.</edtext>
+</ednote>
<div2 id="animation-element-vocabulary">
<head>Animation Element Vocabulary</head>
<p>The following elements specify the structure and principal animation aspects of a
@@ -10571,10 +10608,8 @@
<item><p><specref ref="animation-value-animationValueList"/></p></item>
<item><p><specref ref="animation-value-calcMode"/></p></item>
<item><p><specref ref="animation-value-fill"/></p></item>
-<item><p><specref ref="animation-value-fragmentIdentifier"/></p></item>
<item><p><specref ref="animation-value-keySplines"/></p></item>
<item><p><specref ref="animation-value-keyTimes"/></p></item>
-<item><p><specref ref="animation-value-qualifiedName"/></p></item>
<item><p><specref ref="animation-value-repeatCount"/></p></item>
</ulist>
<div3 id="animation-value-animationValue">
@@ -10596,6 +10631,12 @@
</table>
<p>The syntax of an <animationValue> expression must satisfy all syntax
requirements that apply to the attribute targeted by the animation.</p>
+<ednote>
+<name>Improve Syntax of AnimationValue</name>
+<date>2014-07-31</date>
+<edtext>Enhance detail of syntax of <animationValue> in order to prevent appearance of an unquoted or unescaped semicolon,
+which is used as a delimiter between animation values in <animationValueList>.</edtext>
+</ednote>
<p>The semantics of an <animationValue> expression are those defined by
<bibref ref="svg11"/>, §19.2.9.</p>
</div3>
@@ -10663,55 +10704,6 @@
<p>The semantics of a <fill> expression are those defined by
<bibref ref="svg11"/>, §19.2.8.</p>
</div3>
-<div3 id="animation-value-fragmentIdentifier">
-<head><fragmentIdentifier></head>
-<p>A <fragmentIdentifier> expression is used to target (refer to) an animation to a specific element in the same <loc href="#terms-document-instance">document instance</loc>.</p>
-<table id="fragmentIdentifier-syntax" role="syntax">
-<caption>Syntax Representation – <fragmentIdentifier></caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-<fragmentIdentifier>
- : "#" fragment
-
-fragment
- : uric+
-
-uric
- : reserved
- | unreserved
- | escaped
-
-reserved
- : [;/?:@&=+$,]
-
-unreserved
- : [a-zA-Z]
- | [0-9]
- | [-_.!~*'()]
-
-escaped
- : "%" hex hex
-
-hex
- : [0-9a-fA-F]
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>Except for the constraints on syntax and semantics that follow below, the semantics of a <fragmentIdentifier>
-expression are those defined to apply to an "<iri>" expression in <bibref ref="svg11"/>, §19.2.4.</p>
-<p>A <fragmentIdentifer> must adhere
-to the <code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>. Furthermore, it
-must adhere to the fragment identifer syntax defined by <bibref ref="uri"/>,
-Section 4.1, and is a strict subset thereof, since at least one character must appear in
-the fragment component.</p>
-<p>No linear white-space (LWSP) is permitted to appear within a fragment identifier.</p>
-<p>A <fragmentIdentifer> expression must refer to an element in the same <loc href="#terms-document-instance">document instance</loc>,
-i.e., the fragment component must be a valid IDREF.</p>
-</div3>
<div3 id="animation-value-keySplines">
<head><keySplines></head>
<p>An <keySplines> expression is used to specify a list of Bezier control points that control the pacing of an
@@ -10785,36 +10777,6 @@
<p>The semantics of a <keyTimes> expression are those defined by
<bibref ref="svg11"/>, §19.2.9, as apply to the <att>keyTimes</att> attribute.</p>
</div3>
-<div3 id="animation-value-qualifiedName">
-<head><qualifiedName></head>
-<p>A <qualifiedName> expression is used to specify the attribute targeted by the animation.</p>
-<table id="qualifiedName-syntax" role="syntax">
-<caption>Syntax Representation – <qualifiedName></caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-<qualifiedName>
- : prefix ":" local
- | local
-
-prefix
- : <emph>nmchar</emph>+
-
-local
- : <emph>nmchar</emph>+
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The syntactic element <emph><code>nmchar</code></emph> is to be interpreted according
-to the <code>NameChar</code> production defined by <bibref ref="xml10"/> §2.3,
-except that the COLON (U+003A) character is excluded.</p>
-<p>The semantics of a <qualifiedName> expression are those defined by
-<bibref ref="svg11"/>, §19.2.5, as applying to an <code>attributeName</code> attribute
-according to an implied <code>attributeType</code> of <code>XML</code>.</p>
-</div3>
<div3 id="animation-value-repeatCount">
<head><repeatCount></head>
<p>A <repeatCount> expression is used to determine the number of iterations of a repeated animation.</p>
@@ -11422,7 +11384,7 @@
<head>Relax NG Compact (RNC) Schema</head>
<p>A Relax NG Compact Syntax (RNC) <bibref ref="rng"/> based schema
for TTML Content is available at <loc href="rnc/schema.zip">ZIP
-Archive</loc>. This schema does not normatively define the validity
+Archive</loc>. This schema is to be considered non-normative for the purpose of defining the validity
of Timed Text Markup Language content as defined by this specification.
In particular, the formal validity of TTML Content
is defined by <specref ref="conformance-content"/>.</p>
@@ -11431,7 +11393,7 @@
<head>XML Schema Definition (XSD) Schema</head>
<p>A W3C XML Schema Definition (XSD) <bibref ref="xsd-1"/> based schema
for TTML Content is available at <loc href="xsd/schema.zip">ZIP
-Archive</loc>. This schema does not normatively define the validity
+Archive</loc>. This schema is to be considered non-normative for the purpose of defining the validity
of Timed Text Markup Language content as defined by this specification.
In particular, the formal validity of TTML Content
is defined by <specref ref="conformance-content"/>.</p>