--- a/ttml2/spec/ttml2.html Sat Jan 17 09:09:39 2015 -0700
+++ b/ttml2/spec/ttml2.html Sat Jan 17 09:09:49 2015 -0700
@@ -83,9 +83,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: 2015/01/15 02:16:11 $<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: 2015/01/17 16:09:39 $<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: 2015/01/15 02:16:11 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/01/17 16:09:39 $ @@ @@@@ @@@@</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/2013/REC-ttml1-20130924/">http://www.w3.org/TR/2013/REC-ttml1-20130924/</a>
@@ -271,12 +271,13 @@
10.2.37 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
10.2.38 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
10.2.39 <a href="#style-attribute-textShadow">tts:textShadow</a><br>
- 10.2.40 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
- 10.2.41 <a href="#style-attribute-visibility">tts:visibility</a><br>
- 10.2.42 <a href="#style-attribute-width">tts:width</a><br>
- 10.2.43 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
- 10.2.44 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
- 10.2.45 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
+ 10.2.40 <a href="#style-attribute-translate">tts:translate</a><br>
+ 10.2.41 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
+ 10.2.42 <a href="#style-attribute-visibility">tts:visibility</a><br>
+ 10.2.43 <a href="#style-attribute-width">tts:width</a><br>
+ 10.2.44 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
+ 10.2.45 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
+ 10.2.46 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
10.3 <a href="#styling-style-value-expressions">Styling Value Expressions</a><br>
10.3.1 <a href="#style-value-alpha"><alpha></a><br>
10.3.2 <a href="#style-value-borderColor"><borderColor></a><br>
@@ -528,11 +529,11 @@
K <a href="#other-references">Other References</a> (Non-Normative)<br>
L <a href="#requirements">Requirements</a> (Non-Normative)<br>
M <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
- M.1 <a href="#d3e37615">Element Derivation</a><br>
- M.2 <a href="#d3e38132">Attribute Derivation</a><br>
+ M.1 <a href="#d3e37778">Element Derivation</a><br>
+ M.2 <a href="#d3e38295">Attribute Derivation</a><br>
N <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- N.1 <a href="#d3e39125">Requirements</a><br>
- N.2 <a href="#d3e39289">Guidelines</a><br>
+ N.1 <a href="#d3e39288">Requirements</a><br>
+ N.2 <a href="#d3e39452">Guidelines</a><br>
O <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
P <a href="#common-styling">Common Caption Style Examples</a> (Non-Normative)<br>
P.1 <a href="#pop-on-example">Pop-On Caption Example</a><br>
@@ -1617,6 +1618,7 @@
<a href="#style-attribute-textOrientation">tts:textOrientation</a>,
<a href="#style-attribute-textOutline">tts:textOutline</a>,
<a href="#style-attribute-textShadow">tts:textShadow</a>,
+<a href="#style-attribute-translate">tts:translate</a>,
<a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a>,
<a href="#style-attribute-visibility">tts:visibility</a>,
<a href="#style-attribute-width">tts:width</a>,
@@ -3054,10 +3056,14 @@
: forced
| mediaAspectRatio
| mediaLanguage
+ | stereoLeft
+ | stereoRight
| userLanguage
</pre></div>
</td></tr></tbody></table><dl><dt class="label"><a id="bound-parameter-forced"></a><code>forced</code></dt><dd><p>Evaluates to a boolean value that denotes if the <a href="#terms-content-processor">content processor</a> is operating with
-<a href="#terms-forced-subtitle">forced subtitles</a> enabled.</p></dd><dt class="label"><a id="bound-parameter-mediaAspectRatio"></a><code>mediaAspectRatio</code></dt><dd><p>Evaluates to a numeric value equal to the aspect ratio of the <a href="#terms-related-media-object">related media object</a>.</p></dd><dt class="label"><a id="bound-parameter-mediaLanguage"></a><code>mediaLanguage</code></dt><dd><p>Evaluates to a string value equal to the (primary) language of the <a href="#terms-related-media-object">related media object</a>.</p></dd><dt class="label"><a id="bound-parameter-userLanguage"></a><code>userLanguage</code></dt><dd><p>Evaluates to a string value equal to the (primary) language of the user as determined by the
+<a href="#terms-forced-subtitle">forced subtitles</a> enabled.</p></dd><dt class="label"><a id="bound-parameter-mediaAspectRatio"></a><code>mediaAspectRatio</code></dt><dd><p>Evaluates to a numeric value equal to the aspect ratio of the <a href="#terms-related-media-object">related media object</a>.</p></dd><dt class="label"><a id="bound-parameter-mediaLanguage"></a><code>mediaLanguage</code></dt><dd><p>Evaluates to a string value equal to the (primary) language of the <a href="#terms-related-media-object">related media object</a>.</p></dd><dt class="label"><a id="bound-parameter-stereoLeft"></a><code>stereoLeft</code></dt><dd><p>Evaluates to a boolean value that denotes if the <a href="#terms-content-processor">content processor</a> is processing the
+left image of a stereo presentation.</p></dd><dt class="label"><a id="bound-parameter-stereoRight"></a><code>stereoRight</code></dt><dd><p>Evaluates to a boolean value that denotes if the <a href="#terms-content-processor">content processor</a> is processing the
+right image of a stereo presentation.</p></dd><dt class="label"><a id="bound-parameter-userLanguage"></a><code>userLanguage</code></dt><dd><p>Evaluates to a string value equal to the (primary) language of the user as determined by the
<a href="#terms-document-processing-context">document processing context</a>.</p></dd></dl></div><div class="div3">
<h4><a id="content-value-condition"></a>8.3.3 <condition></h4><p>A <condition> value is used to specify an expression that evaluates to a binary value
which is used to determine if the semantics of a
@@ -3924,7 +3930,7 @@
<h3><a id="styling-attribute-vocabulary"></a>10.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>10.2.1 style</b></a> attribute used
with certain animation elements, <a href="#terms-content-element">content elements</a>, certain layout elements, and style definition elements.</p><p>In addition, this section specifies the following attributes in the TT Style Namespace
for use with style definition elements, certain layout elements, and <a href="#terms-content-element">content elements</a>
-that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>10.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-backgroundImage"><b>10.2.3 tts:backgroundImage</b></a></p></li><li><p><a href="#style-attribute-backgroundPosition"><b>10.2.4 tts:backgroundPosition</b></a></p></li><li><p><a href="#style-attribute-backgroundRepeat"><b>10.2.5 tts:backgroundRepeat</b></a></p></li><li><p><a href="#style-attribute-border"><b>10.2.6 tts:border</b></a></p></li><li><p><a href="#style-attribute-color"><b>10.2.7 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>10.2.8 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>10.2.9 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>10.2.10 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>10.2.11 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>10.2.12 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontKerning"><b>10.2.13 tts:fontKerning</b></a></p></li><li><p><a href="#style-attribute-fontShear"><b>10.2.15 tts:fontShear</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.14 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.16 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.17 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.18 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.19 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.20 tts:height</b></a></p></li><li><p><a href="#style-attribute-letterSpacing"><b>10.2.21 tts:letterSpacing</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.22 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.23 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.24 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.25 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.26 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.27 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.28 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.29 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.30 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.31 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.32 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.33 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textCombine"><b>10.2.34 tts:textCombine</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.35 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textEmphasis"><b>10.2.36 tts:textEmphasis</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.37 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.38 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-textShadow"><b>10.2.39 tts:textShadow</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.40 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.41 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.42 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.43 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.44 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.45 tts:zIndex</b></a></p></li></ul><table border="1" class="ednote" summary="Editorial note: Additional Border Styling Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Border Styling Attributes</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:borderColor</code>, <code>tts:borderStyle</code>, and <code>tts:borderWidth</code>
+that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>10.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-backgroundImage"><b>10.2.3 tts:backgroundImage</b></a></p></li><li><p><a href="#style-attribute-backgroundPosition"><b>10.2.4 tts:backgroundPosition</b></a></p></li><li><p><a href="#style-attribute-backgroundRepeat"><b>10.2.5 tts:backgroundRepeat</b></a></p></li><li><p><a href="#style-attribute-border"><b>10.2.6 tts:border</b></a></p></li><li><p><a href="#style-attribute-color"><b>10.2.7 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>10.2.8 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>10.2.9 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>10.2.10 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>10.2.11 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>10.2.12 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontKerning"><b>10.2.13 tts:fontKerning</b></a></p></li><li><p><a href="#style-attribute-fontShear"><b>10.2.15 tts:fontShear</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.14 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.16 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.17 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.18 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.19 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.20 tts:height</b></a></p></li><li><p><a href="#style-attribute-letterSpacing"><b>10.2.21 tts:letterSpacing</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.22 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.23 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.24 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.25 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.26 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.27 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.28 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.29 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.30 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.31 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.32 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.33 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textCombine"><b>10.2.34 tts:textCombine</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.35 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textEmphasis"><b>10.2.36 tts:textEmphasis</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.37 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.38 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-textShadow"><b>10.2.39 tts:textShadow</b></a></p></li><li><p><a href="#style-attribute-translate"><b>10.2.40 tts:translate</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.41 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.42 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.43 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.44 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.45 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.46 tts:zIndex</b></a></p></li></ul><table border="1" class="ednote" summary="Editorial note: Additional Border Styling Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Border Styling Attributes</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:borderColor</code>, <code>tts:borderStyle</code>, and <code>tts:borderWidth</code>
in order to provide a means to independently express styling of the four different borders (top, right, bottom, left). As currently specified, i.e., with only the
<code>tts:border</code> attribute, one can only express the four borders using the same color, style, and width.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Clip, Origin, Size"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Clip, Origin, Size</b></td><td align="right" valign="top">2014-11-27</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:backgroundClip</code>,
<code>tts:backgroundOrigin</code>, and
@@ -5467,7 +5473,26 @@
span.</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>none</code>.</p><table border="1" class="ednote" summary="Editorial note: Text Shadow Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Shadow Example</b></td><td align="right" valign="top">2015-01-08</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textShadow.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
that defined by <a href="#css3-decoration">[CSS Text Decoration]</a>, § 4.</p></div></div><div class="div3">
-<h4><a id="style-attribute-unicodeBidi"></a>10.2.40 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-translate"></a>10.2.40 tts:translate</h4><p>The <code>tts:translate</code> attribute is used to specify <em>x</em> and <em>y</em> translations (offsets) of a
+region area with respect to the nominal (untranslated) origin of the region.</p><p>This attribute may be specified by any element type
+that permits use of attributes in the TT Style Namespace; however, this attribute applies
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-translate"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+<a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a>
+</td></tr><tr><td><em>Initial:</em></td><td><code>0px 0px</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<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, 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> offsets, where the first specification
+is the <em>x</em> offset, and the second specification is the <em>y</em> offset, and where negative values mean to the right or bottom of the affected
+region, respectively</p><p>If a <code>tts:translate</code> attribute is specified on a <code>div</code> or <code>p</code> element, then that specification must be considered to be
+equivalent to specifying an anonymous <a href="#terms-inline-region">inline region</a> child of the <code>div</code> or <code>p</code> element, where the
+translation of the corresponding region, also referred to as an <a href="#terms-implied-inline-region">implied inline region</a>, is equal to the
+value of this attribute.</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 closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+the computed translate and the supported translate is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value least distant from [0,0], i.e., closest to the coordinate space origin, is used.</p></div><table border="1" class="ednote" summary="Editorial note: Translate Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Translate Example</b></td><td align="right" valign="top">2015-01-17</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:translate.</td></tr></table></div><div class="div3">
+<h4><a id="style-attribute-unicodeBidi"></a>10.2.41 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
defines a directional embedding or override according to
the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
element type
@@ -5506,7 +5531,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.29.6.</p></div></div><div class="div3">
-<h4><a id="style-attribute-visibility"></a>10.2.41 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-visibility"></a>10.2.42 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
defines whether generated areas are visible or not when rendered on a visual
presentation medium.</p><p>This attribute may be specified by any
element type
@@ -5561,7 +5586,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.30.17.</p></div></div><div class="div3">
-<h4><a id="style-attribute-width"></a>10.2.42 tts:width</h4><p>The <code>tts:width</code> attribute is used to specify the
+<h4><a id="style-attribute-width"></a>10.2.43 tts:width</h4><p>The <code>tts:width</code> attribute is used to specify the
<em>width</em> of an area generated by content flowed into a region.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <em>width</em> is interpreted in a writing mode relative manner
such that <em>width</em> always corresponds to a measure in the inline
progression direction. Therefore, in horizontal writing modes, <em>width</em> expresses a horizontal measure,
@@ -5581,7 +5606,7 @@
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If a <a href="#style-value-measure"><measure></a> is expressed as a <a href="#style-value-length"><length></a> value, then it must be non-negative.</p><p>The <code>tts:width</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Width Percentage"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Width Percentage</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify resolution of percentage value.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Width Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Width Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:width.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.15.14, and <a href="#css3-box">[CSS Box Model]</a>, § 9</p></div></div><div class="div3">
-<h4><a id="style-attribute-wrapOption"></a>10.2.43 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-wrapOption"></a>10.2.44 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
defines whether or not automatic line wrapping (breaking) applies within the context of
the affected element.</p><p>This attribute may be specified by any
element type
@@ -5615,7 +5640,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-wrapOption-example-1-images"></a><table class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="TTML wrapOption style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.16.13.</p></div></div><div class="div3">
-<h4><a id="style-attribute-writingMode"></a>10.2.44 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-writingMode"></a>10.2.45 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
defines the block and inline progression directions to be used for the purpose of
stacking block and inline areas within a region area.</p><p>This attribute may be specified by any
element type
@@ -5666,7 +5691,7 @@
the Latin script.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.29.7.</p></div></div><div class="div3">
-<h4><a id="style-attribute-zIndex"></a>10.2.45 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-zIndex"></a>10.2.46 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
defines the front-to-back ordering of region areas in the case that they overlap.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -10090,7 +10115,7 @@
<h2><a id="derivation"></a>M Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
vocabulary, separately describing derivation of elements and
attributes.</p><table border="1" class="ednote" summary="Editorial note: Update Derivation"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Update Derivation</b></td><td align="right" valign="top">2015-01-14</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Update derivation tables to include new vocabulary added in TTML2.</td></tr></table><div class="div2">
-<h3><a id="d3e37615"></a>M.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table M-1 – Elements</b></a>
+<h3><a id="d3e37778"></a>M.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table M-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
@@ -10147,7 +10172,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="d3e38132"></a>M.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table M-2 – Attributes</b></a>
+<h3><a id="d3e38295"></a>M.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table M-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
@@ -10239,9 +10264,9 @@
<h2><a id="qa"></a>N 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="d3e39125"></a>N.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table N-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="d3e39288"></a>N.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table N-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="d3e39289"></a>N.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table N-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-profiling">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="d3e39452"></a>N.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table N-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-profiling">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>M 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">