--- a/ttml2/spec/ttml2.html Thu Apr 09 09:48:18 2015 -0700
+++ b/ttml2/spec/ttml2.html Thu Apr 09 09:52:57 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/02/19 01:47:13 $<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/04/06 19:40:02 $<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/02/19 01:47:13 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/04/06 19:40:02 $ @@ @@@@ @@@@</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>Latest recommendation:</dt><dd><a href="http://www.w3.org/TR/ttml1/">http://www.w3.org/TR/ttml1/</a></dd><dt>Previous version:</dt><dd>
None
@@ -528,11 +528,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="#d3e38026">Element Derivation</a><br>
- M.2 <a href="#d3e38543">Attribute Derivation</a><br>
+ M.1 <a href="#d3e38147">Element Derivation</a><br>
+ M.2 <a href="#d3e38664">Attribute Derivation</a><br>
N <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- N.1 <a href="#d3e39536">Requirements</a><br>
- N.2 <a href="#d3e39700">Guidelines</a><br>
+ N.1 <a href="#d3e39657">Requirements</a><br>
+ N.2 <a href="#d3e39821">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>
@@ -1121,7 +1121,7 @@
element satisfy their respective element type's content
specifications, all required attributes are present, and the declared
value of each attribute satisfies the type declared by the
-associated <a href="#terms-abstract-document-type">abstract document type</a>.</p><div class="issue"><p class="prefix"><a id="issue-362"></a><b>Issue (issue-362):</b></p><p class="prefix"><b>Attribute Forward Compabitility</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/362">http://www.w3.org/AudioVideo/TT/tracker/issues/362</a></p><p>Enhance step (3) to handle forward compatibility of new attributes introduced into TT namespaces.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a
+associated <a href="#terms-abstract-document-type">abstract document type</a>.</p><div class="issue"><p class="prefix"><a id="issue-362"></a><b>Issue (issue-362):</b></p><p class="prefix"><b>Attribute Forward Compatibility</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/362">http://www.w3.org/AudioVideo/TT/tracker/issues/362</a></p><p>Enhance step (3) to handle forward compatibility of new attributes introduced into TT namespaces.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a
conformant <a href="#terms-document-instance">document instance</a>, a given <a href="#terms-document-instance">document instance</a> may be
constrained by the author or authoring tool to satisfy a more
restrictive definition of validity.</p></div><div class="div2">
@@ -3973,7 +3973,7 @@
<code>style</code> attribute, as well as <a href="#semantics-style-association-referential"><b>10.4.1.2 Referential Styling</b></a> and <a href="#semantics-style-association-chained-referential"><b>10.4.1.3 Chained Referential Styling</b></a>, for
further information on its semantics.</p></div></div><div class="div3">
<h4><a id="style-attribute-backgroundColor"></a>10.2.2 tts:backgroundColor</h4><p>The <code>tts:backgroundColor</code> attribute is used to specify a style property that
-defines the background color of a region or an area generated by content flowed into a region.</p><div class="issue"><p class="prefix"><a id="issue-302"></a><b>Issue (issue-302):</b></p><p class="prefix"><b>Line Area Background Height</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/302">http://www.w3.org/AudioVideo/TT/tracker/issues/302</a></p><p>Fix definition of block progression dimension of background area of a line area. Neither XSL-FO nor CSS are sufficiently precise.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p>This attribute may be specified by any
+defines the background color of a region or an area generated by content flowed into a region.</p><div class="issue"><p class="prefix"><a id="issue-302"></a><b>Issue (issue-302):</b></p><p class="prefix"><b>Line Area Background Height</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/302">http://www.w3.org/AudioVideo/TT/tracker/issues/302</a></p><p>Fix definition of block progression dimension of background area of a line area. Neither XSL-FO nor CSS are sufficiently precise.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p></p><div class="issue"><p class="prefix"><a id="issue-380"></a><b>Issue (issue-380):</b></p><p class="prefix"><b>Paragraph Background Width</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/380">http://www.w3.org/AudioVideo/TT/tracker/issues/380</a></p><p>Improve specificity of background color width determination.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><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-backgroundColor"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -4544,7 +4544,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, continuous</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></p><div class="issue"><p class="prefix"><a id="issue-379a"></a><b>Issue (issue-379a):</b></p><p class="prefix"><b>Ruby Text Size Inheritance</b></p><p><b>Source</b>: <a href="https://www.w3.org/AudioVideo/TT/tracker/issues/379">https://www.w3.org/AudioVideo/TT/tracker/issues/379</a></p><p>Special treatment is needed for inheritance of font size on ruby annotation text.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><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
@@ -4625,7 +4625,7 @@
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.9.7.</p></div></div><div class="div3">
<h4><a id="style-attribute-fontVariantPosition"></a>10.2.20 tts:fontVariantPosition</h4><p>The <code>tts:fontVariantPosition</code> attribute is used to enable the selection
-of typographic subscript and superscript glyphs.</p><p>This attribute may be specified by any
+of typographic subscript and superscript glyphs.</p><div class="issue"><p class="prefix"><a id="issue-374"></a><b>Issue (issue-374):</b></p><p class="prefix"><b>Generalize Font Variation</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/374">http://www.w3.org/AudioVideo/TT/tracker/issues/374</a></p><p>Rename tts:fontVariantPosition to tts:fontVariant and introduce width and ruby variation.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><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-fontVariantPosition"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -4727,7 +4727,7 @@
<h4><a id="style-attribute-lineHeight"></a>10.2.24 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
defines the inter-baseline separation between line areas generated by content flowed into a region.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Exceptionally, the term <em>height</em> in the token <code>lineHeight</code> or the phrase <em>line height</em> refers to
the axis that corresponds with the <em>block progression dimension</em> of an associated line area, which is the vertical axis in
-horizontal writing modes, but is the horizontal axis in vertical writing modes.</p></div><div class="issue"><p class="prefix"><a id="issue-284"></a><b>Issue (issue-284):</b></p><p class="prefix"><b>Normal Line Height Multiplier</b></p><p><b>Source</b>: <a href="https://www.w3.org/AudioVideo/TT/tracker/issues/284">https://www.w3.org/AudioVideo/TT/tracker/issues/284</a></p><p>Re-visit choice of 120% versus 125% for multiplier used in interpreting <code>normal</code> line height.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p>This attribute may be specified by any
+horizontal writing modes, but is the horizontal axis in vertical writing modes.</p></div><div class="issue"><p class="prefix"><a id="issue-284"></a><b>Issue (issue-284):</b></p><p class="prefix"><b>Normal Line Height Multiplier</b></p><p><b>Source</b>: <a href="https://www.w3.org/AudioVideo/TT/tracker/issues/284">https://www.w3.org/AudioVideo/TT/tracker/issues/284</a></p><p>Re-visit choice of 120% versus 125% for multiplier used in interpreting <code>normal</code> line height.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p></p><div class="issue"><p class="prefix"><a id="issue-373"></a><b>Issue (issue-373):</b></p><p class="prefix"><b>Line Height Applies to Span</b></p><p><b>Source</b>: <a href="https://www.w3.org/AudioVideo/TT/tracker/issues/373">https://www.w3.org/AudioVideo/TT/tracker/issues/373</a></p><p>Support for ruby requires use of tts:lineHeight on span.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><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-lineHeight"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -4735,7 +4735,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, continuous</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></p><div class="issue"><p class="prefix"><a id="issue-379b"></a><b>Issue (issue-379b):</b></p><p class="prefix"><b>Ruby Text Size Inheritance</b></p><p><b>Source</b>: <a href="https://www.w3.org/AudioVideo/TT/tracker/issues/379">https://www.w3.org/AudioVideo/TT/tracker/issues/379</a></p><p>Special treatment is needed for inheritance of line height on ruby annotation text.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><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>
@@ -5065,7 +5065,11 @@
<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></p><p>If the value of this attribute is <code>none</code>, then no ruby semantics apply; otherwise, the ruby semantics enumerated by
<a href="#ruby-semantics-mapping-table"><b>Table 8-1 – Ruby Semantics Mapping</b></a> apply.</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><a id="ruby-semantics-mapping-table"></a><table class="common"><caption>Table 8-1 – Ruby Semantics Mapping</caption><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col span="1"><tbody><tr><th>Category</th><th>tts:ruby</th><th>Annotation <a href="#ruby">[Ruby]</a></th><th>CSS display <a href="#cssruby">[CSS Ruby]</a></th></tr><tr><td>Ruby Container</td><td><code>container</code></td><td><code>ruby</code></td><td><code>ruby</code></td></tr><tr><td>Ruby Base Content</td><td><code>base</code></td><td><code>rb</code></td><td><code>ruby-base</code></td></tr><tr><td>Ruby Text Content</td><td><code>text</code></td><td><code>rt</code></td><td><code>ruby-text</code></td></tr><tr><td>Ruby Base Container</td><td><code>baseContainer</code></td><td><code>rbc</code></td><td><code>ruby-base-container</code></td></tr><tr><td>Ruby Text Container</td><td><code>textContainer</code></td><td><code>rtc</code></td><td><code>ruby-text-container</code></td></tr><tr><td>Ruby Fallback Delimiter</td><td><code>delimiter</code></td><td><code>rp</code></td><td><code>none</code> | <code>inline</code></td></tr></tbody></table><p>When using <code>tts:ruby</code>, the following nesting constraints apply:</p><ul><li><p>if the computed value of <code>tts:ruby</code> is <code>container</code>, then the
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>none</code>.</p><a id="ruby-semantics-mapping-table"></a><table class="common"><caption>Table 8-1 – Ruby Semantics Mapping</caption><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col span="1"><tbody><tr><th>Category</th><th>tts:ruby</th><th>Annotation <a href="#ruby">[Ruby]</a></th><th>CSS display <a href="#cssruby">[CSS Ruby]</a></th></tr><tr><td>Ruby Container</td><td><code>container</code></td><td><code>ruby</code></td><td><code>ruby</code></td></tr><tr><td>Ruby Base Content</td><td><code>base</code></td><td><code>rb</code></td><td><code>ruby-base</code></td></tr><tr><td>Ruby Text Content</td><td><code>text</code></td><td><code>rt</code></td><td><code>ruby-text</code></td></tr><tr><td>Ruby Base Container</td><td><code>baseContainer</code></td><td><code>rbc</code></td><td><code>ruby-base-container</code></td></tr><tr><td>Ruby Text Container</td><td><code>textContainer</code></td><td><code>rtc</code></td><td><code>ruby-text-container</code></td></tr><tr><td>Ruby Fallback Delimiter</td><td><code>delimiter</code></td><td><code>rp</code></td><td><code>none</code> | <code>inline</code></td></tr></tbody></table><p>When using <code>tts:ruby</code>, the following nesting constraints apply:</p><table border="1" class="ednote" summary="Editorial note: Proscribe Non-Ruby Span Children in Container"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Proscribe Non-Ruby Span Children in Container</b></td><td align="right" valign="top">2015-02-18</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add constraints to proscribe use of span children of container that do not specify a ruby style, i.e., that
+do not play a role in ruby structure. If used, then such span is ignored for presentation purposes.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Proscribe Extraneous #PCDATA in Container"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Proscribe Extraneous #PCDATA in Container</b></td><td align="right" valign="top">2015-02-18</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add constraints to proscribe #PCDATA node children of container, baseContainer, and textContainer; i.e., permit #PCDATA only
+in base, text, and delimiter. If used, then such data is ignored for presentation purposes.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Proscribe Break Element in Container"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Proscribe Break Element in Container</b></td><td align="right" valign="top">2015-02-18</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add constraint to proscribe use of <code>br</code> element in ruby or its descendants, and, if used, is interpreted as normal
+(collapsible) whitespace.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Proscribe Line Separator and Paragraph Separator Characters in Container"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Proscribe Line Separator and Paragraph Separator Characters in Container</b></td><td align="right" valign="top">2015-02-18</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add constraint to proscribe use of U+2028 (LINE SEPARATOR) and U+2029 (PARAGRAPH SEPARATOR) in ruby or its descendants, and, if used, they are
+interpreted as normal (collapsible) whitespace.</td></tr></table><ul><li><p>if the computed value of <code>tts:ruby</code> is <code>container</code>, then the
computed value of <code>tts:ruby</code> of all ancestor elements is <code>none</code>;</p></li><li><p>if the computed value of <code>tts:ruby</code> is <code>container</code>, then the
computed value of <code>tts:ruby</code> of its first child element is <code>baseContainer</code>
or <code>base</code>;</p></li><li><p>if the computed value of <code>tts:ruby</code> is <code>baseContainer</code>, then the
@@ -5202,6 +5206,7 @@
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>start</code> |
<code>center</code> |
+<code>end</code> |
<code>spaceBetween</code> |
<code>spaceAround</code>
</td></tr><tr><td><em>Initial:</em></td><td><code>spaceAround</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -5210,6 +5215,8 @@
or ruby text annotation is aligned to the start edge of that inline area.
If the value is <code>center</code>, then excess whitespace
is equally distributed before and after the first and last glyphs, respectively.
+If the value of this attribute is <code>end</code>, then the end edge of the first glyph area descendant of an inline area generated from a ruby text container
+or ruby text annotation is aligned to the end edge of that inline area.
If the value is <code>spaceBetween</code>, then excess whitespace
is equally distributed between each glyph area descendant.
If the value is <code>spaceAround</code>, then excess whitespace
@@ -5287,7 +5294,7 @@
§ 7.4.2.</p></div></div><div class="div3">
<h4><a id="style-attribute-textAlign"></a>10.2.35 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
defines how inline areas are aligned within a containing block area in the inline progression
-direction.</p><p>This attribute may be specified by any
+direction.</p><table border="1" class="ednote" summary="Editorial note: Justification in Inline Progression Dimension"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Justification in Inline Progression Dimension</b></td><td align="right" valign="top">2015-04-06</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add <code>justify</code> value to support justification in inline progression dimension.</td></tr></table><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-textAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -6850,7 +6857,7 @@
to an intermediate
synchronic document form,
<em>DOC<sub>inter</sub></em> , according to the
-<span class="strong"><a href="#procedure-construct-intermediate-document">[construct intermediate document]</a></span> procedure:</p><dl><dt class="label"><a id="procedure-construct-intermediate-document"></a>[construct intermediate document]</dt><dd><ol class="enumar"><li><p>perform procedure <span class="strong"><a href="#procedure-process-inline-regions">[process inline regions]</a></span>;</p></li><li><p>for each temporally active region <em>R</em>, replicate the
+<span class="strong"><a href="#procedure-construct-intermediate-document">[construct intermediate document]</a></span> procedure:</p><dl><dt class="label"><a id="procedure-construct-intermediate-document"></a>[construct intermediate document]</dt><dd><p></p><div class="issue"><p class="prefix"><a id="issue-368"></a><b>Issue (issue-368):</b></p><p class="prefix"><b>ISD Construction Prunes <br/> Erroneously</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/368">http://www.w3.org/AudioVideo/TT/tracker/issues/368</a></p><p>Should not prune empty break <br/> elements, or should previously convert to LINE SEPARATOR.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><ol class="enumar"><li><p>perform procedure <span class="strong"><a href="#procedure-process-inline-regions">[process inline regions]</a></span>;</p></li><li><p>for each temporally active region <em>R</em>, replicate the
sub-tree
of <em>DOC<sub>source</sub></em>
headed by the <code>body</code> element;</p></li><li><p>evaluating this sub-tree in a postorder traversal, prune elements if they
@@ -6865,7 +6872,7 @@
which, in turn, implies that the descendants of the pruned element will no longer
be descendants of the element's parent. When <em>prune</em> is used in
reference to an attribute, it means that attribute is to be removed from its
-associated (owning) element node.</p></div></dd><dt class="label"><a id="procedure-associate-region"></a>[associate region]</dt><dd><p></p><div class="issue"><p class="prefix"><a id="issue-341"></a><b>Issue (issue-341):</b></p><p class="prefix"><b>Multiple Descendant Region Ambiguitty</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/341">http://www.w3.org/AudioVideo/TT/tracker/issues/341</a></p><p>Refine step (3) to resolve ambiguity when multiple regions are referenced by descendants.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p></p><table border="1" class="ednote" summary="Editorial note: Inline Region Association"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Inline Region Association</b></td><td align="right" valign="top">2013-08-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define inline region association.</td></tr></table><p>A <a href="#terms-content-element">content element</a> is associated with a region according
+associated (owning) element node.</p></div></dd><dt class="label"><a id="procedure-associate-region"></a>[associate region]</dt><dd><p></p><div class="issue"><p class="prefix"><a id="issue-341"></a><b>Issue (issue-341):</b></p><p class="prefix"><b>Multiple Descendant Region Ambiguity</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/341">http://www.w3.org/AudioVideo/TT/tracker/issues/341</a></p><p>Refine step (3) to resolve ambiguity when multiple regions are referenced by descendants.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p></p><table border="1" class="ednote" summary="Editorial note: Inline Region Association"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Inline Region Association</b></td><td align="right" valign="top">2013-08-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define inline region association.</td></tr></table><p>A <a href="#terms-content-element">content element</a> is associated with a region according
to the following ordered rules, where the first rule satisfied
is used and remaining rules are skipped:</p><ol class="enumar"><li><p>if the element specifies a <a href="#layout-attribute-region"><code>region</code></a> attribute,
then the element is associated with the region referenced by that
@@ -10130,7 +10137,7 @@
August 2002. (See
<a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>.)
</dd></dl></div><div class="div1">
-<h2><a id="requirements"></a>L Requirements (Non-Normative)</h2><p>The Timed Text Markup Language (TTML), also known as the Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring
+<h2><a id="requirements"></a>L Requirements (Non-Normative)</h2><div class="issue"><p class="prefix"><a id="issue-369"></a><b>Issue (issue-369):</b></p><p class="prefix"><b>Requirement Numbers</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/369">http://www.w3.org/AudioVideo/TT/tracker/issues/369</a></p><p>Some R### numbers are incorrect.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p></p><div class="issue"><p class="prefix"><a id="issue-370"></a><b>Issue (issue-370):</b></p><p class="prefix"><b>Review Requirements</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/370">http://www.w3.org/AudioVideo/TT/tracker/issues/370</a></p><p>Update requirements satisfaction to reflect functional enhancements that address prior unsatisfied requirements.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p>The Timed Text Markup Language (TTML), also known as the Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring
Format (TTAF), satisfies a subset of the requirements established by
<a href="#ttaf1-req">[TTAF1-REQ]</a>. The following table enumerates these requirements and
indicates the extent to which they are satisfied by this specification, where
@@ -10143,7 +10150,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="d3e38026"></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="d3e38147"></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
@@ -10200,7 +10207,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="d3e38543"></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="d3e38664"></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
@@ -10292,9 +10299,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="d3e39536"></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="d3e39657"></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="d3e39700"></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="d3e39821"></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">