--- a/ttml10/spec/ttaf1-dfxp.html Fri May 17 21:59:22 2013 -0600
+++ b/ttml10/spec/ttaf1-dfxp.html Fri May 17 22:00:24 2013 -0600
@@ -80,9 +80,9 @@
.strong { font-weight: bold }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/05/15 20:36:23 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/05/18 03:59:22 $<div id="revisions"></div><div class="head">
<h1><a id="title"></a>Timed Text Markup Language (TTML) 1.0 (Second Edition)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/05/15 20:36:23 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/05/18 03:59:22 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ttaf1-dfxp.html">ttaf1-dfxp.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
@@ -392,11 +392,11 @@
H <a href="#other-references">Other References</a> (Non-Normative)<br>
I <a href="#requirements">Requirements</a> (Non-Normative)<br>
J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
- J.1 <a href="#d3e18209">Element Derivation</a><br>
- J.2 <a href="#d3e18688">Attribute Derivation</a><br>
+ J.1 <a href="#d3e18318">Element Derivation</a><br>
+ J.2 <a href="#d3e18797">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e19558">Requirements</a><br>
- K.2 <a href="#d3e19722">Guidelines</a><br>
+ K.1 <a href="#d3e19683">Requirements</a><br>
+ K.2 <a href="#d3e19847">Guidelines</a><br>
L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
M <a href="#concrete-encoding">Concrete Encoding</a> (Non-Normative)<br>
N <a href="#time-expression-semantics">Time Expression Semantics</a> (Non-Normative)<br>
@@ -713,7 +713,7 @@
<h3><a id="conformance-content"></a>3.1 Content Conformance</h3><p>A TTML <em>Document Instance</em> conforms to this specification if the following criteria are
satisfied:</p><ol class="enumar"><li><p>When transporting a <em>Document Instance</em> in a <em>Document Interchange Context</em> in which a
Media Type <a href="#media-types">[Media Types]</a> identifies the content type of the interchanged <em>Document Instance</em>, then the specified media type is
-<code>application/ttml+xml</code> in conformance with <a href="#rfc3023">[XML Media Types]</a> § 7, with which an optional
+<code>application/ttml+xml</code> in conformance with <a href="#xml-media">[XML Media Types]</a> § 7, with which an optional
<code>profile</code> parameter may appear, the value of which
conforms to
a profile designator as
@@ -1319,8 +1319,7 @@
<code>ttp:feature</code> elements in order to
superset the baseline profile (since neither
<code>#fontStyle-italic</code> nor <code>#textDecoration-under</code>
-are required by the DFXP presentation profile).
-</p><p>The effect of this example is to express authorial intentions that
+are required by the DFXP presentation profile).</p><p>The effect of this example is to express authorial intentions that
italic font style and text underlining must be
supported.</p></div></div><div class="div3">
<h4><a id="parameter-vocabulary-extensions"></a>6.1.4 ttp:extensions</h4><p>The <code>ttp:extensions</code> element is a container element used to group
@@ -1430,7 +1429,7 @@
appear between adjacent non-terminal components of a TT Parameter value
unless some other delimiter is permitted and used.</p><div class="div3">
<h4><a id="parameter-attribute-cellResolution"></a>6.2.1 ttp:cellResolution</h4><p>The <code>ttp:cellResolution</code> attribute may be used by an author
-to express the number of horizontal and vertical cells into which the root container region
+to express the number of horizontal and vertical cells into which the <em>Root Container Region</em>
area is divided for the purpose of expressing presentation semantics in terms of
a uniform grid.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-cellResolution-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:cellResolution</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -1453,7 +1452,7 @@
cells expresses a dimension parallel to the inline or block progression dimension,
the cell's dimension in the inline or block progression dimension applies, respectively.
For example, if padding (on all four edges) is specified as 0.1c, the cell resolution
-is 20 by 10, and the root container extent is 640 by 480, then, assuming top to bottom,
+is 20 by 10, and the extent of the <em>Root Container Region</em> is 640 by 480, then, assuming top to bottom,
left to right writing mode, the start and end padding will be 640 / 20 * 0.1 pixels and the
before and after padding will be 480 / 10 * 0.1 pixels.</p></div></div><div class="div3">
<h4><a id="parameter-attribute-clockMode"></a>6.2.2 ttp:clockMode</h4><p>The <code>ttp:clockMode</code> attribute is used to specify the
@@ -2040,19 +2039,17 @@
<h4><a id="content-attribute-lang"></a>7.2.2 xml:lang</h4><p>The <code>xml:lang</code> attribute is used as defined by
<a href="#xml10">[XML 1.0]</a>, §2.12, <em>Language Identification</em>.</p><p>The <code>xml:lang</code> attribute must be specified on the <code>tt</code>
element and may be specified by an instance of any other element type
-in the core vocabulary catalog.</p></div><div class="div3">
+in the core vocabulary catalog except parameter vocabulary.</p></div><div class="div3">
<h4><a id="content-attribute-space"></a>7.2.3 xml:space</h4><p>The <code>xml:space</code> attribute is used as defined by
<a href="#xml10">[XML 1.0]</a>, §2.10, <em>White Space Handling</em>.</p><p>The <code>xml:space</code> attribute may be used with any element in
-the core vocabulary catalog.</p><p>The semantics of the value <code>default</code> are fixed to mean that
+the core vocabulary catalog except parameter vocabulary.</p><p>The semantics of the value <code>default</code> are fixed to mean that
when performing presentation processing of a <em>Document Instance</em> as
described by <a href="#semantics-region-layout-step-2"><b>9.3.3 Synchronic Flow Processing</b></a>,
processing must occur as
if the following properties were specified on the affected
-
elements of an equivalent intermediate XSL-FO document:</p><ul><li><p><code>suppress-at-line-break="auto"</code></p></li><li><p><code>linefeed-treatment="treat-as-space"</code></p></li><li><p><code>white-space-collapse="true"</code></p></li><li><p><code>white-space-treatment="ignore-if-surrounding-linefeed"</code></p></li></ul><p>Similarly, the semantics of the value <code>preserve</code> are fixed to mean that
when performing presentation processing, processing must occur as
if the following properties were specified on the affected
-
elements of an equivalent intermediate XSL-FO document:
</p><ul><li><p><code>suppress-at-line-break="retain"</code></p></li><li><p><code>linefeed-treatment="preserve"</code></p></li><li><p><code>white-space-collapse="false"</code></p></li><li><p><code>white-space-treatment="preserve"</code></p></li></ul><p>When performing other types of processing intended to eventually
result in a visual presentation by means other than those described
@@ -2060,28 +2057,25 @@
preservation as described above should be respected. For other types
of processing, the treatment of the <code>xml:space</code> attribute
is processor dependent, but should respect the semantics described
-above if possible.</p></div></div></div><div class="div1">
+above if possible.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the above four cited XSL-FO properties are defined by
+by <a href="#xsl11">[XSL 1.1]</a>, § 7.17.3, 7.16.7, 7.16.12, and 7.16.8, respectively.</p></div></div></div></div><div class="div1">
<h2><a id="styling"></a>8 Styling</h2><p>This section specifies the <em>styling</em> matter of the core
vocabulary catalog, where
styling is to be understood as a separable layer of information that applies to
content and that denotes authorial intentions about the presentation of
-that content.</p><p>
- Styling attributes are included in TTML to enable authorial intent of presentation
- to be included within a self-contained document. This section describes
- the semantics of style presentation in terms of a standard processing
- model. TTML Processors are not required to present <em>Document Instances</em> in any particular way;
- but an implementation of this model by a TTML Presentation Processor
- that provides externally observable results that are consistent with this model is
- likely to lead to a user experience that closely resembles the experience intended by
- the documents' authors.
- </p><p>
- The semantics of TTML style presentation are described in terms of the model
- in <a href="#xsl11">[XSL 1.1]</a>. The intended effect of the attributes in this section
- are to be compatible with the layout model of XSL. Presentation agents may however
- use any technology to satisfy the authorial intent of the document. In particular
- since <a href="#css2">[CSS2]</a> is a subset of this model, a CSS processor may be used
- for the features that the models have in common.
- </p><p>No normative use of an
+that content.</p><p>Styling attributes are included in TTML to enable authorial intent of presentation
+to be included within a self-contained document. This section describes
+the semantics of style presentation in terms of a standard processing
+model. TTML Processors are not required to present <em>Document Instances</em> in any particular way;
+but an implementation of this model by a TTML Presentation Processor
+that provides externally observable results that are consistent with this model is
+likely to lead to a user experience that closely resembles the experience intended by
+the documents' authors.</p><p>The semantics of TTML style presentation are described in terms of the model
+in <a href="#xsl11">[XSL 1.1]</a>. The effects of the attributes in this section
+are intended to be compatible with the layout and formatting model of XSL; however, Presentation agents
+may use any technology to satisfy the authorial intent of the document. In particular
+since <a href="#css2">[CSS2]</a> is a subset of this model, a CSS processor may be used
+for the features that the models have in common.</p><p>No normative use of an
<code><?xml-stylesheet ... ?></code> processing instruction is defined
by this specification.</p><div class="div2">
<h3><a id="styling-element-vocabulary"></a>8.1 Styling Element Vocabulary</h3><p>The following elements specify the structure and principal styling aspects of a
@@ -2123,10 +2117,7 @@
<a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a> and <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>That is to say, when referential styling is used by an element to
refer to a <code>style</code> element, then the referenced <code>style</code>
element must appear as a descendant of the <code>styling</code> element, and
-not in any other context.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In this version of this specification, the <code>style</code> element is the
-only non-metadata element that is not defined to accept <code>Metadata.class</code>
-children. It is expected that this asymmetry will be corrected in the next
-revision of this specification.</p></div></div></div><div class="div2">
+not in any other context.</p></div></div></div><div class="div2">
<h3><a id="styling-attribute-vocabulary"></a>8.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>8.2.1 style</b></a> attribute used
with both style definition elements as well as content 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 content elements
@@ -2142,12 +2133,8 @@
element type. This capability permits the expression of an inheritable
style property on ancestor elements to which the property
does not apply.</p></div><div class="div3">
-<h4><a id="style-attribute-style"></a>8.2.1 style</h4><p>The <code>style</code> attribute is used
-by referential style association
-to reference one or more <code>style</code>
-elements each of which define a
-specified
-style set.</p><p>The <code>style</code> attribute may be specified by an instance of the following
+<h4><a id="style-attribute-style"></a>8.2.1 style</h4><p>The <code>style</code> attribute is used by referential style association
+to reference one or more <code>style</code> elements each of which define a style (property) set.</p><p>The <code>style</code> attribute may be specified by an instance of the following
element types:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li></ul><p>If specified, the value of a <code>style</code> attribute must
adhere to the <code>IDREFS</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
§ 3.3.10.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See the specific element type definitions that permit use of the
@@ -2182,7 +2169,8 @@
How <span <span class="strong">tts:backgroundColor="green"</span>>I wonder</span> where you're at!
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-backgroundColor-example-1-images"></a><table class="example-images"><caption>Example Rendition – Background Color</caption><tbody><tr><td><img src="images/backgroundColor.png" alt="TTML backgroundColor style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-backgroundColor-example-1-images"></a><table class="example-images"><caption>Example Rendition – Background Color</caption><tbody><tr><td><img src="images/backgroundColor.png" alt="TTML backgroundColor 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.8.2.</p></div></div><div class="div3">
<h4><a id="style-attribute-color"></a>8.2.3 tts:color</h4><p>The <code>tts:color</code> attribute is used to specify a style property that
defines the foreground color of marks associated with an area generated by content flowed into a region.</p><p>This attribute may be specified by any
element type
@@ -2197,7 +2185,7 @@
is considered to be implementation dependent. In the absence of
end-user preference information, a conformant presentation processor
should use an initial value that is highly contrastive to the
-background color of the root container region.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><a id="style-attribute-color-example-1"></a><table class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
+background color of the <em>Root Container Region</em>.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><a id="style-attribute-color-example-1"></a><table class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:backgroundColor="black"/>
@@ -2211,7 +2199,9 @@
I'll try and tell you what I mean.
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-color-example-1-images"></a><table class="example-images"><caption>Example Rendition – Color</caption><tbody><tr><td><img src="images/color.png" alt="TTML color style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-color-example-1-images"></a><table class="example-images"><caption>Example Rendition – Color</caption><tbody><tr><td><img src="images/color.png" alt="TTML color 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.18.1.</p></div></div><div class="div3">
<h4><a id="style-attribute-direction"></a>8.2.4 tts:direction</h4><p>The <code>tts:direction</code> attribute is used to specify a style property that
defines the directionality of an embedding or override according to
the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
@@ -2247,7 +2237,9 @@
</pre></div>
</td></tr></tbody></table><p></p><a id="style-attribute-direction-example-1-images"></a><table class="example-images"><caption>Example Rendition – Direction</caption><tbody><tr><td>
<img src="images/direction.png" alt="TTML direction style property">
-</td></tr></tbody></table></div><div class="div3">
+</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.1.</p></div></div><div class="div3">
<h4><a id="style-attribute-display"></a>8.2.5 tts:display</h4><p>The <code>tts:display</code> attribute is used to specify a style property that
defines whether an element is a candidate for layout and composition
in a region.</p><p>This attribute may be specified by any
@@ -2309,7 +2301,8 @@
<img src="images/display_3.png" alt="TTML display style property - [3,4)">
</td></tr><tr><td>
<img src="images/display_4.png" alt="TTML display style property - [4,5)">
-</td></tr></tbody></table></div><div class="div3">
+</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="#css2">[CSS2]</a>, § 9.2.4.</p></div></div><div class="div3">
<h4><a id="style-attribute-displayAlign"></a>8.2.6 tts:displayAlign</h4><p>The <code>tts:displayAlign</code> attribute is used to specify a style property that
defines the alignment of block areas in the block progression direction.</p><p>This attribute may be specified by any
element type
@@ -2358,10 +2351,12 @@
<p region="r4">They sent an<br/> answer back to me.</p>
</div>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-displayAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Display Align</caption><tbody><tr><td><img src="images/displayAlign.png" alt="TTML displayAlign style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-displayAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Display Align</caption><tbody><tr><td><img src="images/displayAlign.png" alt="TTML displayAlign 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.14.4.</p></div></div><div class="div3">
<h4><a id="style-attribute-extent"></a>8.2.7 tts:extent</h4><p>The <code>tts:extent</code> attribute is used to specify the
<em>width</em> and <em>height</em> of a region area
-(which may be the root container region).</p><p>This attribute may be specified by any
+(which may be the <em>Root Container Region</em>).</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-extent"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -2370,15 +2365,14 @@
</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#document-structure-vocabulary-tt"><code>tt</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 root container region</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <em>Root Container Region</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a>
specifications, then they must be interpreted as <em>width</em>
and <em>height</em>, where the first specification is the
<em>width</em>, and the second specification is the
<em>height</em>, where, if either <em>width</em> or <em>height</em> is negative or zero, then
extent must be considered zero in both inline and block progression dimensions.</p><p>If the value of this attribute is <code>auto</code>, then the initial value
-of the style property must be considered to be the same as the root container extent.
-</p><p>
-The root container extent is determined either by a
+of the style property must be considered to be the same as the extent of the <em>Root Container Region</em>.</p><p>
+The extent of the <em>Root Container Region</em> is determined either by a
<code>tts:extent</code> specified on the <code>tt</code> element, if
present, or by the external authoring context, if not present.
If
@@ -2455,12 +2449,12 @@
</p>
</div>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-fontFamily-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Family</caption><tbody><tr><td><img src="images/fontFamily.png" alt="TTML fontFamily style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-fontFamily-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Family</caption><tbody><tr><td><img src="images/fontFamily.png" alt="TTML fontFamily 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.9.2.</p></div></div><div class="div3">
<h4><a id="style-attribute-fontSize"></a>8.2.9 tts:fontSize</h4><p>The <code>tts:fontSize</code> attribute is used to specify a style property
that defines the font size for glyphs that are selected for glyph areas
-generated by content flowed into a region, where font size is interpreted as a
-scaling transform to the font's design EM square.</p><p>This attribute may be specified by any
-element type
+generated by content flowed into a 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-fontSize"></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>?
@@ -2496,7 +2490,10 @@
that is <span <span class="strong">tts:fontSize="24px"</span>>pleasant</span> to drink.
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-fontSize-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Size</caption><tbody><tr><td><img src="images/fontSize.png" alt="TTML fontSize style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-fontSize-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Size</caption><tbody><tr><td><img src="images/fontSize.png" alt="TTML fontSize 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.9.4. The addition of a second length component to permit specifying font
+width and height independently is an extension introduced by TTML.</p></div></div><div class="div3">
<h4><a id="style-attribute-fontStyle"></a>8.2.10 tts:fontStyle</h4><p>The <code>tts:fontStyle</code> attribute is used to specify a style property that
defines the font style to apply to glyphs that are selected for glyph areas generated
by content flowed into a region, where the mapping from font
@@ -2513,7 +2510,7 @@
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>Use of the value <code>oblique</code>
-denote a shear transformation (at an unspecified
+denotes a shear transformation (at an unspecified
angle) in the inline progression dimension.</p><p>If a specified font style is not available, then a
presentation processor must attempt to map the specified font style
to an available font style that has similar typographic
@@ -2535,7 +2532,9 @@
Take pen and ink, and <span <span class="strong">tts:fontStyle="italic"</span>>write it down.</span>
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-fontStyle-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Style</caption><tbody><tr><td><img src="images/fontStyle.png" alt="TTML fontStyle style property"></td></tr></tbody></table><p></p></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-fontStyle-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Style</caption><tbody><tr><td><img src="images/fontStyle.png" alt="TTML fontStyle style property"></td></tr></tbody></table><p></p><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.9.7.</p></div></div><div class="div3">
<h4><a id="style-attribute-fontWeight"></a>8.2.11 tts:fontWeight</h4><p>The <code>tts:fontWeight</code> attribute is used to specify a style property
that defines the font weight to apply to glyphs that are selected for glyph
areas generated by content flowed into a region, where the mapping from font
@@ -2573,7 +2572,9 @@
<span <span class="strong">tts:fontWeight="bold"</span>>but said I could not swim.</span>
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-fontWeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Weight</caption><tbody><tr><td><img src="images/fontWeight.png" alt="TTML fontWeight style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-fontWeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Weight</caption><tbody><tr><td><img src="images/fontWeight.png" alt="TTML fontWeight 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.9.9.</p></div></div><div class="div3">
<h4><a id="style-attribute-lineHeight"></a>8.2.12 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><p>This attribute may be specified by any
element type
@@ -2611,7 +2612,9 @@
"The bitterness of Life.
"</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-lineHeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Line Height</caption><tbody><tr><td><img src="images/lineHeight.png" alt="TTML lineHeight style property"></td></tr></tbody></table><p></p></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-lineHeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Line Height</caption><tbody><tr><td><img src="images/lineHeight.png" alt="TTML lineHeight style property"></td></tr></tbody></table><p></p><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.4.</p></div></div><div class="div3">
<h4><a id="style-attribute-opacity"></a>8.2.13 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
defines the opacity (or conversely, the transparency)
of marks associated with a region.</p><p>When presented onto a visual medium, the opacity of the region is applied uniformly and on a linear scale
@@ -2655,11 +2658,12 @@
<img src="images/opacity_3.png" alt="TTML opacity style property - [3,4)">
</td></tr><tr><td>
<img src="images/opacity_4.png" alt="TTML opacity style property - [4,5)">
-</td></tr></tbody></table></div><div class="div3">
+</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="#css3-color">[CSS3 Color]</a>,
+§ 3.2.</p></div></div><div class="div3">
<h4><a id="style-attribute-origin"></a>8.2.14 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
<em>x</em> and <em>y</em> coordinates of the origin of a
-region area with respect to the origin of the root container extent,
-if specified, or the external authoring context, if not specified.</p><p>This attribute may be specified by any
+region area with respect to the origin of the <em>Root Container Region</em>.</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-origin"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -2667,11 +2671,10 @@
<a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a>
</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of root container region</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a> specifications,
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <em>Root Container Region</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a> specifications,
then they must be interpreted as <em>x</em> and <em>y</em> coordinates, where the first specification
is the <em>x</em> coordinate, and the second specification is the <em>y</em> coordinate.</p><p>If the value of this attribute is <code>auto</code>, then the initial value
-of the style property must be considered to be the same as the root container
-origin.</p><p>If a specified value of this attribute is not supported,
+of the style property must be considered to be the same as the origin of the <em>Root Container Origin</em>.</p><p>If a specified value of this attribute is not supported,
then a presentation processor must interpret the attribute as if the
value <code>auto</code> were specified.</p><p>The <code>tts:origin</code> style is illustrated by the following example.</p><a id="style-attribute-origin-example-1"></a><table class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -2752,7 +2755,9 @@
</td></tr></tbody></table><p></p><a id="style-attribute-overflow-example-1-images"></a><table class="example-images"><caption>Example Rendition – Overflow</caption><tbody><tr><td><img src="images/overflow.png" alt="TTML overflow style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the <code>tts:noWrap</code> is set to
<code>noWrap</code> to prevent automatic line wrapping (breaking);
if this were not specified, then overflow would occur in the block
-progression direction as opposed to the inline progression direction.</p></div></div><div class="div3">
+progression direction as opposed to the inline progression direction.</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.21.2.</p></div></div><div class="div3">
<h4><a id="style-attribute-padding"></a>8.2.16 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
space on all sides of a region area.</p><p>This attribute may be specified by any
element type
@@ -2795,7 +2800,11 @@
</td></tr></tbody></table><p>When rendering an area to which padding applies, the background color that
applies to the area is rendered into the padded portion of the area.</p><a id="style-attribute-padding-example-1-images"></a><table class="example-images"><caption>Example Rendition – Padding</caption><tbody><tr><td>
<img src="images/padding.png" alt="TTML padding style property">
-</td></tr></tbody></table></div><div class="div3">
+</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.31.15, except that individual shorthand values map to writing
+mode relative padding values as defined by <a href="#xsl11">[XSL 1.1]</a>,
+§ 7.8.31, 7.8.32, 7.8.33, and 7.8.34.</p></div></div><div class="div3">
<h4><a id="style-attribute-showBackground"></a>8.2.17 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
constraints on when the background color of a region is intended to be
presented.</p><p>This attribute may be specified by any
@@ -2810,7 +2819,7 @@
background color of a region is always rendered when performing presentation
processing on a visual medium; if the value is <code>whenActive</code>,
then the background color of a region is rendered only when some
-content is selected into the region.</p><p>If a specified value of this attribute is not supported,
+content is flowed into the region.</p><p>If a specified value of this attribute is not supported,
then a presentation processor must interpret the attribute as if the
value <code>always</code> were specified.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><a id="style-attribute-showBackground-example-1"></a><table class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -2833,7 +2842,9 @@
<style <span class="strong">tts:showBackground="whenActive"</span>/>
</region>
</pre></div>
-</td></tr></tbody></table></div><div class="div3">
+</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="#smil21">[SMIL 2.1]</a>,
+§ 5.3.3.</p></div></div><div class="div3">
<h4><a id="style-attribute-textAlign"></a>8.2.18 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
@@ -2875,7 +2886,9 @@
The frumious Bandersnatch!
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-textAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="TTML textAlign style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-textAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="TTML textAlign 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.9.</p></div></div><div class="div3">
<h4><a id="style-attribute-textDecoration"></a>8.2.19 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
defines a text decoration effect to apply to glyph areas or other inline
areas that are generated by content flowed into a region.</p><p>This attribute may be specified by any
@@ -2923,7 +2936,9 @@
</span>
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-textDecoration-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="TTML textDecoration style property"></td></tr></tbody></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-textDecoration-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="TTML textDecoration 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.17.4.</p></div></div><div class="div3">
<h4><a id="style-attribute-textOutline"></a>8.2.20 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
defines a text outline effect to apply to glyphs that are selected for glyph areas generated
by content flowed into a region.</p><p>This attribute may be specified by any
@@ -2947,7 +2962,7 @@
cells is used in a <code>tts:textOutline</code> value,
the cell's dimension in the block progression dimension applies.
For example, if text outline thickness is specified as 0.1c, the cell resolution
-is 20 by 10, and the root container extent is 640 by 480, then the
+is 20 by 10, and the extent of the <em>Root Container Region</em> is 640 by 480, then the
outline thickness will be a nominal 480 / 10 * 0.1 pixels, i.e., 4.8px,
without taking into account rasterization effects.</p></div><p>If a specified value of this attribute is not supported,
then a presentation processor must interpret the attribute as if the
@@ -3011,7 +3026,9 @@
</pre></div>
</td></tr></tbody></table><p></p><a id="style-attribute-unicodeBidi-example-1-images"></a><table class="example-images"><caption>Example Rendition – Unicode Bidirectionality</caption><tbody><tr><td>
<img src="images/unicodeBidi.png" alt="TTML unicodeBidi style property">
-</td></tr></tbody></table></div><div class="div3">
+</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>8.2.22 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
@@ -3065,7 +3082,9 @@
<img src="images/visibility_2.png" alt="TTML visibility style property - [2,3)">
</td></tr><tr><td>
<img src="images/visibility_3.png" alt="TTML visibility style property - [3,4)">
-</td></tr></tbody></table></div><div class="div3">
+</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-wrapOption"></a>8.2.23 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
@@ -3098,7 +3117,9 @@
A-sitting on a gate.
</p>
</pre></div>
-</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><div class="div3">
+</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>8.2.24 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
@@ -3148,7 +3169,9 @@
<code>tts:direction</code> properties are set to
<code>bidiOverride</code> and <code>rtl</code>, respectively, in order
to override the normally left-to-right directionality of characters in
-the Latin script.</p></div></div><div class="div3">
+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>8.2.25 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
@@ -3220,8 +3243,12 @@
And concluded the banquet by...
</p>
</pre></div>
-</td></tr></tbody></table><p></p><p></p><a id="style-attribute-zIndex-example-1-images"></a><table class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="TTML zIndex style property"></td></tr></tbody></table></div></div><div class="div2">
-<h3><a id="styling-style-value-expressions"></a>8.3 Style Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>8.3.1 <alpha></b></a></p></li><li><p><a href="#style-value-color"><b>8.3.2 <color></b></a></p></li><li><p><a href="#style-value-digit"><b>8.3.3 <digit></b></a></p></li><li><p><a href="#style-value-duration"><b>8.3.4 <duration></b></a></p></li><li><p><a href="#style-value-familyName"><b>8.3.5 <familyName></b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>8.3.6 <genericFamilyName></b></a></p></li><li><p><a href="#style-value-hexDigit"><b>8.3.7 <hexDigit></b></a></p></li><li><p><a href="#style-value-integer"><b>8.3.8 <integer></b></a></p></li><li><p><a href="#style-value-length"><b>8.3.9 <length></b></a></p></li><li><p><a href="#style-value-namedColor"><b>8.3.10 <namedColor></b></a></p></li><li><p><a href="#style-value-quotedString"><b>8.3.11 <quotedString></b></a></p></li><li><p><a href="#style-value-string"><b>8.3.12 <string></b></a></p></li></ul><div class="div3">
+</td></tr></tbody></table><p></p><p></p><a id="style-attribute-zIndex-example-1-images"></a><table class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="TTML zIndex 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.30.18.</p></div></div></div><div class="div2">
+<h3><a id="styling-style-value-expressions"></a>8.3 Style Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>8.3.1 <alpha></b></a></p></li><li><p><a href="#style-value-color"><b>8.3.2 <color></b></a></p></li><li><p><a href="#style-value-digit"><b>8.3.3 <digit></b></a></p></li><li><p><a href="#style-value-duration"><b>8.3.4 <duration></b></a></p></li><li><p><a href="#style-value-familyName"><b>8.3.5 <familyName></b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>8.3.6 <genericFamilyName></b></a></p></li><li><p><a href="#style-value-hexDigit"><b>8.3.7 <hexDigit></b></a></p></li><li><p><a href="#style-value-integer"><b>8.3.8 <integer></b></a></p></li><li><p><a href="#style-value-length"><b>8.3.9 <length></b></a></p></li><li><p><a href="#style-value-namedColor"><b>8.3.10 <namedColor></b></a></p></li><li><p><a href="#style-value-quotedString"><b>8.3.11 <quotedString></b></a></p></li><li><p><a href="#style-value-string"><b>8.3.12 <string></b></a></p></li></ul><p>In the syntax representations defined in this section, no
+linear whitespace (LWSP) is implied or permitted between tokens
+unless explicitly specified.</p><div class="div3">
<h4><a id="style-value-alpha"></a>8.3.1 <alpha></h4><p>An <alpha> expression is used to express an opacity value,
where 0 means fully transparent and 1 means fully opaque.</p><a id="alpha-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <alpha></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -3294,10 +3321,7 @@
| "f" // frames
| "t" // ticks
</pre></div>
-</td></tr></tbody></table><p>It is an error to omit the metric component of a duration.</p><p>When operating with <code>smpte</code> time base and
-<code>discontinuous</code> mode, a duration expression must be
-considered to denote a duration in (local) real-time, independently of the
-governing time base.</p></div><div class="div3">
+</td></tr></tbody></table><p>It is an error to omit the metric component of a duration.</p></div><div class="div3">
<h4><a id="style-value-familyName"></a>8.3.5 <familyName></h4><p>A <familyName> expression specifies a font family name.</p><p>If the name contains a quotation delimiter character,
then it must be expressed as a
<quotedString>. If the name contains a
@@ -3333,7 +3357,7 @@
or <code>monospaceSerif</code>. The generic family names <code>sansSerif</code>
and <code>serif</code> are to be interpreted as equivalent to <code>proportionalSansSerif</code>
and <code>proportionalSerif</code>, respectively.</p><p>If the generic family name <code>default</code> is specified (or implied by
-an initial value), then its typographic characteristics is considered to be implementation
+an initial value), then its typographic characteristics are considered to be implementation
dependent; however, it is recommended that this default font family be mapped to
an monospaced, sans-serif font.</p></div><div class="div3">
<h4><a id="style-value-hexDigit"></a>8.3.7 <hexDigit></h4><p>A <hexDigit> is used to express integers and other types of numbers or tokens
@@ -3490,16 +3514,8 @@
other out-of-line style properties, thus creating a chain of references starting at the
affected element. When expressed in this manner, the association of style information
is referred to as <em>chained referential styling</em>.</p><p>If the same style property is specified in more than one referenced
-style
-set,
-then the last referenced style
-set
-applies, where the order of application starts from
-the affected element and proceeds to referenced style
-sets,
-and, in turn, to subsequent, recursively
-referenced style
-sets.</p><p>A loop in a sequence of chained style references must be considered an error.</p><p>The use of referential styling is restricted to making
+style set, then the last referenced style set applies, where the order of application starts from
+the affected element and proceeds to referenced style sets, and, in turn, to subsequent referenced style sets.</p><p>A loop in a sequence of chained style references must be considered an error.</p><p>The use of referential styling is restricted to making
reference to <code>style</code> element descendants of a <code>styling</code>
element. It is considered an error to reference a <code>style</code>
element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of chained referential styling encourages the grouping of style specifications
@@ -3514,7 +3530,7 @@
<p <span class="strong">style="s2"</span>>Yellow Monospace</p>
</pre></div>
</td></tr></tbody></table></div><div class="div4">
-<h5><a id="semantics-style-association-nested"></a>8.4.1.4 Nested Styling</h5><p>Style properties may be expressed in an nested manner by direct specification of one or
+<h5><a id="semantics-style-association-nested"></a>8.4.1.4 Nested Styling</h5><p>Style properties may be expressed in a nested manner by direct specification of one or
more <code>style</code> element children of the affected element.
When expressed in this manner, the association of style information
is referred to as <em>nested styling</em>.</p><p>Style properties associated by nested styling are afforded a lower priority than inline
@@ -3810,7 +3826,7 @@
</td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
<code>layout</code> element, the implied time interval of this element is
defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
-<h4><a id="layout-vocabulary-region"></a>9.1.2 region</h4><p>The <code>region</code> element is used to define a space or area into which content is
+<h4><a id="layout-vocabulary-region"></a>9.1.2 region</h4><p>The <code>region</code> element is used to define a rectangular space or area into which content is
to be flowed for the purpose of presentation.</p><p>In addition, and in accordance with
<a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>,
the <code>region</code> element may be used to specify inheritable style properties to be
@@ -3849,26 +3865,26 @@
If specified, these begin and end points are relative to the time
interval of the nearest ancestor element associated with a time
interval, irregardless of whether that interval is explicit or implied.</p><p>The nearest ancestor element of a <code>region</code> element that is associated
-with a time interval is the <em>Document Instance</em>'s root <code>tt</code> element.</p><p>If a <code>dur</code> attribute is specified on the <code>region</code> element, then it
+with a time interval is the <code>layout</code> element.</p><p>If a <code>dur</code> attribute is specified on the <code>region</code> element, then it
specifies the simple duration of the region.</p><p>For the purpose of determining the semantics of presentation processing, a
region that is temporally inactive must not produce any visible marks when
presented on a visual medium.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>region</code> element may be associated with a time interval for two
purposes: (1) in order to temporally bound the presentation of the region and
its content, and (2) to provide a temporal context in which animations of region
-styles may be effected.</p><p>For example, an author may wish a region that is otherwise empty, but
+styles may be effected.</p><p>For example, an author may wish to specify a region that is otherwise empty, but
may have a visible background color to be presented starting at some time and
continuing over the region's duration. The simple duration of the region serves
additionally to scope the presentation effects of content that is targeted to the
-region. An author may also wish to move a region within the root container
-extent or change a region's background color by means of animation effects. In
+region. An author may also wish to move a region within the <em>Root Container Region</em>
+or change a region's background color by means of animation effects. In
both of these cases, it is necessary to posit an active time interval for a
region.</p></div><p>If no <code>timeContainer</code> attribute is specified on
a <code>region</code> element, then it must be interpreted as having
<em>parallel</em> time containment semantics.</p><p>If a <a href="#metadata-attribute-role"><code>ttm:role</code></a> attribute is
specified on a <code>region</code> element, then it must adhere to the
-value syntax defined by <a href="#metadata-attribute-role-syntax"><b>Syntax Representation – ttm:role</b></a>, and where the role(s) identified
-by this attribute expresses the semantic role(s) of the region
-independently from the semantic role(s) of any content targeted to
+value syntax defined by <a href="#metadata-attribute-role-syntax"><b>Syntax Representation – ttm:role</b></a>, and where the roles identified
+by this attribute express the semantic roles of the region
+independently from the semantic roles of any content targeted to
(associated with) the region.</p></div></div><div class="div2">
<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with content elements.</p><div class="div3">
<h4><a id="layout-attribute-region"></a>9.2.1 region</h4><p>The <code>region</code> attribute is used to reference a <code>region</code>
@@ -3883,9 +3899,7 @@
</p><div class="div3">
<h4><a id="semantics-default-region"></a>9.3.1 Default Region</h4><p>If a <em>Document Instance</em> does not specify a
<a href="#layout-vocabulary-region"><code>region</code></a> element,
-then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be anonymous;</p></li><li><p>the extent of the default region is the same as the root container
-region;</p></li><li><p>the temporal interval of the default region is the same as temporal
-interval of the <em>Document Instance</em>;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element was
+then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be anonymous;</p></li><li><p>the extent of the default region is the same as the extent of the <em>Root Container Region</em>;</p></li><li><p>the temporal interval of the default region is the same as the interval defined by the <em>Root Temporal Extent</em>;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element is
specified, then the <a href="#layout-attribute-region"><code>region</code></a> attribute must
not be specified on any content element in the <em>Document Instance</em>.</p><p>If a default region is implied for a given <em>Document Instance</em>, then
the <a href="#document-structure-vocabulary-body"><code>body</code></a> element
@@ -3916,12 +3930,13 @@
form, <em>DOC<sub>source</sub></em> ,
to an intermediate
synchronic document form,
-<em>DOC<sub>inter</sub></em> , as follows:</p><ol class="enumar"><li><p>for each temporally active region <em>R</em>, replicate the
+<em>DOC<sub>inter</sub></em> , as follows:</p><dl><dt class="label">[construct intermediate document]</dt><dd><ol class="enumar"><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
are not a content element, if they are temporally inactive, if they are empty,
-or if they aren't associated with region <em>R</em>;</p></li><li><p>if the pruned sub-tree is non-empty, then reparent it to the <em>R</em>
+or if they aren't associated with region <em>R</em> according to the
+<span class="strong">[associate region]</span>;</p></li><li><p>if the pruned sub-tree is non-empty, then reparent it to the <em>R</em>
element;</p></li><li><p>finally, after completing the above steps, prune the original <code>body</code>
element from the intermediate document, then prune all <code>region</code>,
<code>begin</code>, <code>end</code>, and <code>dur</code> attributes, which are no
@@ -3930,7 +3945,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><p>A content element is associated with a region according
+associated (owning) element node.</p></div></dd><dt class="label">[associate region]</dt><dd><p>A content element 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
@@ -3941,7 +3956,7 @@
then the element is associated with the region referenced by that
attribute;</p></li><li><p>if a default region was implied (due to the absence of any
<a href="#layout-vocabulary-region"><code>region</code></a> element),
-then the element is associated with the default region;</p></li><li><p>the element is not associated with any region.</p></li></ol><p>The result of performing the processing described above will be a sequence of
+then the element is associated with the default region;</p></li><li><p>the element is not associated with any region.</p></li></ol></dd></dl><p>The result of performing the processing described above will be a sequence of
<em>N</em> intermediate synchronic
<em>Document Instances</em>,
<em>DOC<sub><span>inter<sub>0</sub></span></sub></em> …
@@ -3973,7 +3988,7 @@
nodes;</p></li></ol></li><li><p>resolve styles according to <a href="#semantics-style-resolution-process-overall"><b>8.4.4.4 Style Resolution Process</b></a>;</p></li><li><p>map the <code>tt</code> element to an <code>fo:root</code> element, populated
initially with an <code>fo:layout-master-set</code> element that contains a valid
<code>fo:simple-page-master</code> that, in turn, contains an
-<code>fo:region-body</code> child, where the root container extent expressed on the
+<code>fo:region-body</code> child, where the extent of the <em>Root Container Region</em> expressed on the
<code>tt</code> element is mapped to <code>page-width</code> and
<code>page-height</code> attributes on the <code>fo:simple-page-master</code>
element;</p></li><li><p>map the <code>layout</code> element to an <code>fo:page-sequence</code> element and a
@@ -4031,7 +4046,7 @@
the <code>page-viewport-area</code>,
which is generated by <code>fo:page-sequence</code> element by
reference to the sole generated <code>fo:simple-page-master</code>
-element, would correspond to the <em>root container region</em> defined
+element, would correspond to the <em>Root Container Region</em> defined
above in <a href="#definitions"><b>2 Definitions</b></a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Due to the possible presence of TTML style properties or style property values
in a given <em>Document Instance</em> for which there is no <a href="#xsl11">[XSL 1.1]</a> counterpart,
Implementors should recognize that it is the layout model of <a href="#xsl11">[XSL 1.1]</a> that is being referenced
@@ -4087,13 +4102,13 @@
</tt>
</pre></div>
</td></tr></tbody></table><p>In the above document, the content hierarchy consists of two divisions, each
-containing two paragraphs. This content is targeted (selected into) one of two
+containing two paragraphs. This content is targeted (associated with) one of two
non-overlapping regions that are styled identically except for their position
and their foreground colors, the latter of which is inherited by and applies to
the (and, in this case, anonymous) spans reparented into the regions.</p><p>The following, first intermediate document shows the synchronic state at time
interval [0,1), during which time only division <code>d1</code> is temporally active,
and where paragraphs <code>p1</code> and <code>p2</code> (and their ancestors)
-are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate documents shown below are not valid <em>Document Instances</em>,
+are associated with regions <code>r1</code> and <code>r2</code>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate documents shown below are not valid <em>Document Instances</em>,
but rather, are representations of possible internal processing states used for
didactic purposes.</p></div><a id="region-mapping-example-1-i0"></a><table class="example"><caption>Example – Intermediate Document – [0s,1s)</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
@@ -4135,12 +4150,9 @@
</head>
</tt>
</pre></div>
-</td></tr></tbody></table><p>
-
- An XSL FO document instance that would yield rendering consistent with TTML, and
- which may be produced by performing flow processing upon the first intermediate
- document is illustrated below.
-</p><a id="region-mapping-example-1-f0"></a><table class="example"><caption>Example – XSL FO Document – [0s,1s)</caption><tbody><tr><td>
+</td></tr></tbody></table><p>An XSL FO document instance that would yield rendering consistent with TTML, and
+which may be produced by performing flow processing upon the first intermediate
+document is illustrated below.</p><a id="region-mapping-example-1-f0"></a><table class="example"><caption>Example – XSL FO Document – [0s,1s)</caption><tbody><tr><td>
<div class="exampleInner"><pre><fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
<fo:layout-master-set>
<fo:simple-page-master master-name="m1"
@@ -4209,9 +4221,9 @@
</td></tr></tbody></table><p>The following, second intermediate document shows the synchronic state at
time interval [1,2), at which time both divisions <code>d1</code> and
<code>d2</code> are temporally active, and where paragraphs <code>p1</code> and
-<code>p4</code> (and their ancestors) are selected into region <code>r1</code>
+<code>p4</code> (and their ancestors) are associated with region <code>r1</code>
and paragraphs <code>p2</code> and <code>p3</code> (and their ancestors) are
-selected into region <code>r2</code>.</p><a id="region-mapping-example-1-i1"></a><table class="example"><caption>Example – Intermediate Document – [1s,2s)</caption><tbody><tr><td>
+associated with region <code>r2</code>.</p><a id="region-mapping-example-1-i1"></a><table class="example"><caption>Example – Intermediate Document – [1s,2s)</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
xmlns="http://www.w3.org/ns/ttml"
xmlns:tts="http://www.w3.org/ns/ttml#styling">
@@ -4260,7 +4272,7 @@
</td></tr></tbody></table><p>The following, third intermediate document shows the synchronic state at time
interval [2,3), at which time only division <code>d2</code> is temporally active,
and where paragraphs <code>p4</code> and <code>p3</code> (and their ancestors)
-are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><a id="region-mapping-example-1-i2"></a><table class="example"><caption>Example – Intermediate Document – [2s,3s)</caption><tbody><tr><td>
+are associated with regions <code>r1</code> and <code>r2</code>, respectively.</p><a id="region-mapping-example-1-i2"></a><table class="example"><caption>Example – Intermediate Document – [2s,3s)</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
xmlns="http://www.w3.org/ns/ttml"
xmlns:tts="http://www.w3.org/ns/ttml#styling">
@@ -4527,10 +4539,10 @@
<body region="r1">...</body>
</tt>
</pre></div>
-</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the root container region is divided into a
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the <em>Root Container Region</em> is divided into a
cell grid of 40 columns and 16 rows. A region, <code>r1</code>, with
dimensions of 24 columns and 2 rows is then positioned within the
-root container region, with its position varying over time in order to
+<em>Root Container Region</em>, with its position varying over time in order to
create an effect of moving the region, which may be desirable so as
to avoid obscuring characters in an underlying video with captions.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>set</code> element
are based upon that defined by <a href="#smil21">[SMIL 2.1]</a>,
@@ -4852,9 +4864,9 @@
<code>ttp:profile</code> parameter defined by
Section
<a href="#parameter-attribute-profile"><b>6.2.8 ttp:profile</b></a>
-of the published specification.</p></dd></dl></dd><dt class="label">Encoding considerations:</dt><dd><p>Same for application/xml, except constrained to either UTF-8 or UTF-16. See <a href="#xml-media">[XML Media]</a>, Section
+of the published specification.</p></dd></dl></dd><dt class="label">Encoding considerations:</dt><dd><p>Same for application/xml, except constrained to either UTF-8 or UTF-16. See <a href="#xml-media">[XML Media Types]</a>, Section
3.2.</p></dd><dt class="label">Security considerations:</dt><dd><p>As with other XML types and as noted in
-<a href="#xml-media">[XML Media]</a>
+<a href="#xml-media">[XML Media Types]</a>
Section 10, repeated expansion of maliciously constructed XML entities
can be used to consume large amounts of memory, which may cause XML
processors in constrained environments to fail.</p><p>In addition, because of the extensibility features for TTML and of XML
@@ -6253,10 +6265,13 @@
</pre></div></div></div><div class="div1">
<h2><a id="references"></a>G References</h2><p><em>This appendix is normative.</em></p><dl><dt class="label"><a id="css2"></a>CSS2</dt><dd>Bert Bos et al.,
-<a href="http://www.w3.org/TR/1998/REC-CSS2-19980512/"><cite>Cascading
-Style Sheets, Level 2</cite></a>, W3C Recommendation, 12
-May 1998. (See
-<a href="http://www.w3.org/TR/1998/REC-CSS2-19980512/">http://www.w3.org/TR/1998/REC-CSS2-19980512/</a>.)
+<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/"><cite>Cascading
+Style Sheets, Level 2 Revision 1</cite></a>, W3C Recommendation, 07 June 2011.
+(See <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/">http://www.w3.org/TR/2011/REC-CSS2-20110607/</a>.)
+</dd><dt class="label"><a id="css3-color"></a>CSS3 Color</dt><dd>Tantek Çelik and Chris Lilley,
+<a href="http://www.w3.org/TR/2011/REC-css3-color-20110607/"><cite>CSS Color
+Module Level 3</cite></a>, W3C Recommendation, 07 June 2011. (See
+<a href="http://www.w3.org/TR/2011/REC-css3-color-20110607/">http://www.w3.org/TR/2011/REC-css3-color-20110607/</a>.)
</dd><dt class="label"><a id="gps"></a>GPS</dt><dd>
<a href="http://tycho.usno.navy.mil/gpsinfo.html"><cite>Global
Positioning System</cite></a>, US Naval Observatory.
@@ -6290,14 +6305,14 @@
Agent Accessibility Guidelines 1.0</cite></a>, W3C Recommendation, 17
December 2002. (See
<a href="http://www.w3.org/TR/2002/REC-UAAG10-20021217/">http://www.w3.org/TR/2002/REC-UAAG10-20021217/</a>.)
+</dd><dt class="label"><a id="uax14"></a>UAX14</dt><dd>Asmus Freytag, <a href="http://www.unicode.org/reports/tr14/tr14-17.html"><cite>Line Breaking
+Properties</cite></a>, Unicode Consortium, 29 August 2005. (See
+<a href="http://www.unicode.org/reports/tr14/tr14-17.html">http://www.unicode.org/reports/tr14/tr14-17.html</a>.)
</dd><dt class="label"><a id="utc"></a>UTC</dt><dd>
Recommendation TF.460,
<a href="http://www.itu.int/"><cite>Standard-Frequency and Time-Signal
Emissions</cite></a>, International
Telecommunciations Union, Radio Sector (ITU-R).
-</dd><dt class="label"><a id="uax14"></a>UAX14</dt><dd>Asmus Freytag, <a href="http://www.unicode.org/reports/tr14/tr14-17.html"><cite>Line Breaking
-Properties</cite></a>, Unicode Consortium, 29 August 2005. (See
-<a href="http://www.unicode.org/reports/tr14/tr14-17.html">http://www.unicode.org/reports/tr14/tr14-17.html</a>.)
</dd><dt class="label"><a id="wcag"></a>WCAG</dt><dd>Ben Caldwell, et al., Eds.,
<a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/"><cite>Web
Content Accessibility Guidelines (WCAG) 2.0</cite></a>, W3C Recommendation, 11 December 2008. (See
@@ -6318,16 +6333,12 @@
<a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/"><cite>xml:id Version 1.0</cite></a>,
W3C Recommendation, 09 September 2005. (See
<a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/">http://www.w3.org/TR/2005/REC-xml-id-20050909/</a>.)
-</dd><dt class="label"><a id="xml-media"></a>XML Media</dt><dd>Makato Murata, Simon St. Laurent,
-Kan Khon, Eds., <a href="http://www.rfc-editor.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>,
-RFC 3023, January 2001, IETF.(See
-<a href="http://www.rfc-editor.org/rfc/rfc3023.txt">http://www.rfc-editor.org/rfc/rfc3023.txt</a>.)
</dd><dt class="label"><a id="infoset"></a>XML InfoSet</dt><dd>John Cowan and Richard Tobin, Eds.,
<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>XML Information Set (Second Edition)</cite></a>,
W3C Recommendation, 04 February 2004. (See
<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</a>.)
-</dd><dt class="label"><a id="rfc3023"></a>XML Media Types</dt><dd>Makato Murata, et al.,
-<a href="http://www.rfc-editor.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>,
+</dd><dt class="label"><a id="xml-media"></a>XML Media Types</dt><dd>Makato Murata, Simon St. Laurent,
+Kan Khon, Eds., <a href="http://www.rfc-editor.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>,
RFC 3023, January 2001, IETF.(See
<a href="http://www.rfc-editor.org/rfc/rfc3023.txt">http://www.rfc-editor.org/rfc/rfc3023.txt</a>.)
</dd><dt class="label"><a id="xmlns10"></a>XML Namespaces 1.0</dt><dd>Tim Bray, et al.
@@ -6361,10 +6372,6 @@
CEA-708-D,
<a href="http://www.ce.org/"><cite>Digital Television (DTV) Closed Captioning</cite></a>, CEA Standard,
Consumer Electronics Association (CEA).
-</dd><dt class="label"><a id="css3-color"></a>CSS3 Color</dt><dd>Tantek Çelik and Chris Lilley,
-<a href="http://www.w3.org/TR/2003/CR-css3-color-20030514/"><cite>CSS3 Color
-Module</cite></a>, W3C Candidate Recommendation, 14 May 2003. (See
-<a href="http://www.w3.org/TR/2003/CR-css3-color-20030514/">http://www.w3.org/TR/2003/CR-css3-color-20030514/</a>.)
</dd><dt class="label"><a id="dcmes"></a>DCMES 1.1</dt><dd>Dublin Core Metadata Initiative,
<a href="http://dublincore.org/documents/dces/"><cite>Dublin Core Metadata Element Set, Version 1.1: Reference Description</cite></a>. (See
<a href="http://dublincore.org/documents/dces/">http://dublincore.org/documents/dces/</a>.)
@@ -6418,7 +6425,7 @@
<h2><a id="derivation"></a>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
vocabulary, separately describing derivation of elements and
attributes.</p><div class="div2">
-<h3><a id="d3e18209"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
+<h3><a id="d3e18318"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
specifies a TTML element vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
@@ -6473,7 +6480,7 @@
and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e18688"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
+<h3><a id="d3e18797"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
specifies a TTML attribute vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
@@ -6494,7 +6501,7 @@
that are uniquely defined for a specific TTML element type are not
listed below, but are considered to be part of the specific element
type's derivation described in <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
-above.</p><a id="attribute-vocab-derivation-table"></a><table class="common"><caption>Table J-2 – Attributes</caption><col width="20%" span="1"><col width="17%" span="1"><col width="13%" align="center" span="1"><col width="40%" span="1"><col width="10%" align="center" span="1"><tbody><tr><td><span class="strong">Attribute</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#timing-attribute-begin"><code>begin</code></a></td><td><code>begin</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-dur"><code>dur</code></a></td><td><code>dur</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-end"><code>end</code></a></td><td><code>end</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#layout-attribute-region"><code>region</code></a></td><td><code>master-reference</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>conceptual derivation</td><td></td></tr><tr><td><a href="#style-attribute-style"><code>style</code></a></td><td><code>class</code></td><td><a href="#css2">[CSS2]</a></td><td>dereferences style specification(s) directly</td><td></td></tr><tr><td><a href="#timing-attribute-timeContainer"><code>timeContainer</code></a></td><td><code>timeContainer</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>-excl, -none; no default attribute value</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td></td><td>used to attribute agent of content</td><td></td></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td></td><td>used to attribute role of content</td><td></td></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td></td><td>expresses uniform grid resolution for cell based coordinates</td><td></td></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td></td><td>determines how to interpret time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td></td><td>expresses integral frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td></td><td>used to express non-integral, rational frame rates</td><td></td></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td></td><td>expresses marker continuity semantics</td><td></td></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td></td><td>expresses pixel aspect ratio of related media</td><td></td></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td></td><td>expresses profile of TTML used by a <em>Document Instance</em></td><td></td></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td></td><td>expresses frame counting (drop) modes</td><td></td></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td></td><td>expresses sub-frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td></td><td>used to interpret tick based time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td></td><td>used to interpret semantics of time expressions</td><td></td></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only <code>auto</code>, <code>none</code></td><td></td></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-bolder</code>, <code>-lighter</code>, <code>-<number></code></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-<number></code>, <code>-<space></code></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-auto</code>, <code>-error-if-overflow</code>;</td><td>8</td></tr><tr><td><a href="#style-attribute-padding"><code>tts:padding</code></a></td><td><code>padding</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>9</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,10,13</td></tr><tr><td><a href="#style-attribute-textOutline"><code>tts:textOutline</code></a></td><td><code>text-shadow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>11,13</td></tr><tr><td><a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a></td><td><code>unicode-bidi</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-visibility"><code>tts:visibility</code></a></td><td><code>visibility</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-collapse</code></td><td></td></tr><tr><td><a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a></td><td><code>wrap-option</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-writingMode"><code>tts:writingMode</code></a></td><td><code>writing-mode</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>+tblr</code></td><td>1</td></tr><tr><td><a href="#style-attribute-zIndex"><code>tts:zIndex</code></a></td><td><code>z-index</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#content-attribute-id"><code>xml:id</code></a></td><td><code>xml:id</code></td><td><a href="#xmlid">[XML ID]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-lang"><code>xml:lang</code></a></td><td><code>xml:lang</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-space"><code>xml:space</code></a></td><td><code>xml:space</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>see notes</td><td>12</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Attribute name and/or value(s) are normalized to use
+above.</p><a id="attribute-vocab-derivation-table"></a><table class="common"><caption>Table J-2 – Attributes</caption><col width="20%" span="1"><col width="17%" span="1"><col width="13%" align="center" span="1"><col width="40%" span="1"><col width="10%" align="center" span="1"><tbody><tr><td><span class="strong">Attribute</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#timing-attribute-begin"><code>begin</code></a></td><td><code>begin</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-dur"><code>dur</code></a></td><td><code>dur</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-end"><code>end</code></a></td><td><code>end</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#layout-attribute-region"><code>region</code></a></td><td><code>master-reference</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>conceptual derivation</td><td></td></tr><tr><td><a href="#style-attribute-style"><code>style</code></a></td><td><code>class</code></td><td><a href="#css2">[CSS2]</a></td><td>dereferences style specification(s) directly</td><td></td></tr><tr><td><a href="#timing-attribute-timeContainer"><code>timeContainer</code></a></td><td><code>timeContainer</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>-excl, -none; no default attribute value</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td></td><td>used to attribute agent of content</td><td></td></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td></td><td>used to attribute role of content</td><td></td></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td></td><td>expresses uniform grid resolution for cell based coordinates</td><td></td></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td></td><td>determines how to interpret time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td></td><td>expresses integral frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td></td><td>used to express non-integral, rational frame rates</td><td></td></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td></td><td>expresses marker continuity semantics</td><td></td></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td></td><td>expresses pixel aspect ratio of related media</td><td></td></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td></td><td>expresses profile of TTML used by a <em>Document Instance</em></td><td></td></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td></td><td>expresses frame counting (drop) modes</td><td></td></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td></td><td>expresses sub-frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td></td><td>used to interpret tick based time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td></td><td>used to interpret semantics of time expressions</td><td></td></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only <code>auto</code>, <code>none</code></td><td></td></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a></td><td><code>font-style</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-backslant</code></td><td>1</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-bolder</code>, <code>-lighter</code>, <code>-<number></code></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-<number></code>, <code>-<space></code></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-auto</code>, <code>-error-if-overflow</code></td><td>8</td></tr><tr><td><a href="#style-attribute-padding"><code>tts:padding</code></a></td><td><code>padding</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>9</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,10,13</td></tr><tr><td><a href="#style-attribute-textOutline"><code>tts:textOutline</code></a></td><td><code>text-shadow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>11,13</td></tr><tr><td><a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a></td><td><code>unicode-bidi</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-visibility"><code>tts:visibility</code></a></td><td><code>visibility</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-collapse</code></td><td></td></tr><tr><td><a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a></td><td><code>wrap-option</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-writingMode"><code>tts:writingMode</code></a></td><td><code>writing-mode</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>+tblr</code></td><td>1</td></tr><tr><td><a href="#style-attribute-zIndex"><code>tts:zIndex</code></a></td><td><code>z-index</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#content-attribute-id"><code>xml:id</code></a></td><td><code>xml:id</code></td><td><a href="#xmlid">[XML ID]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-lang"><code>xml:lang</code></a></td><td><code>xml:lang</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-space"><code>xml:space</code></a></td><td><code>xml:space</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>see notes</td><td>12</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Attribute name and/or value(s) are normalized to use
<em>lowerCamelCase</em> naming convention.</p></li><li><p>Restricted to expressing a clock value that denotes one of the
following in accordance to whether the parameter expressed by the
<code>ttp:timeBase</code> attribute is <code>media</code>, <code>smpte</code>,
@@ -6545,9 +6552,9 @@
<h2><a id="qa"></a>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
Framework Specifications Guidelines</a> <a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e19558"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a id="d3e19683"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
clause</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e19722"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e19847"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
TTML <a href="#doctypes">Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">