--- a/spec/ttaf1-dfxp.html Thu May 13 16:27:06 2010 +0000
+++ b/spec/ttaf1-dfxp.html Thu May 13 16:28:18 2010 +0000
@@ -77,8 +77,8 @@
</dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2008/tt/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2008/tt/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/CR-ttaf1-dfxp-20100223/">http://www.w3.org/TR/2010/CR-ttaf1-dfxp-20100223/</a>
</dd><dt>Editor:</dt><dd>Glenn Adams, Samsung Electronics Co., Ltd.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
-<h2><a name="abstract" id="abstract"/>Abstract</h2><p>This document specifies the timed text markup language (TTML) in terms of a
-vocabulary and semantics thereof.</p><p>The timed text markup language is a content type that represents
+<h2><a name="abstract" id="abstract"/>Abstract</h2><p>This document specifies the Timed Text Markup Language (TTML) in terms of a
+vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
timed text media for the purpose of interchange among authoring
systems. Timed text is textual information that is intrinsically or
extrinsically associated with timing information.</p><p>It is intended to be used
@@ -213,7 +213,7 @@
9.3.1 <a href="#semantics-default-region">Default Region</a><br/>
9.3.2 <a href="#semantics-region-layout-step-1">Intermediate Synchronic Document Construction</a><br/>
9.3.3 <a href="#semantics-region-layout-step-2">Synchronic Flow Processing</a><br/>
- 9.3.4 <a href="#semantics-region-layout-example">Elaborated Example</a><br/>
+ 9.3.4 <a href="#semantics-region-layout-example">Elaborated Example (Informative)</a><br/>
9.4 <a href="#semantics-line-layout">Line Layout</a><br/>
10 <a href="#timing">Timing</a><br/>
10.1 <a href="#timing-element-vocabulary">Timing Element Vocabulary</a><br/>
@@ -417,11 +417,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="#d3e17101">Element Derivation</a><br/>
- J.2 <a href="#d3e17580">Attribute Derivation</a><br/>
+ J.1 <a href="#d3e17024">Element Derivation</a><br/>
+ J.2 <a href="#d3e17503">Attribute Derivation</a><br/>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br/>
- K.1 <a href="#d3e18468">Requirements</a><br/>
- K.2 <a href="#d3e18632">Guidelines</a><br/>
+ K.1 <a href="#d3e18391">Requirements</a><br/>
+ K.2 <a href="#d3e18555">Guidelines</a><br/>
L <a href="#streaming">Streaming DFXP Content</a> (Non-Normative)<br/>
M <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br/>
N <a href="#change-history">Change History</a> (Non-Normative)<br/>
@@ -451,7 +451,7 @@
external multimedia integration technology, such as SMIL.</p></div><div class="div2">
<h3><a name="model" id="model"/>1.1 System Model</h3><p>Use of TTML is intended to function in a wider context of Timed Text
Authoring and Distribution mechanisms that are based upon a system
-model, depicted in <a href="#model-graphic"><b>Figure 1 – System Model</b></a>, wherein the timed text makrup language
+model, depicted in <a href="#model-graphic"><b>Figure 1 – System Model</b></a>, wherein the Timed Text Markup Language
serves as a bidirectional interchange format among a heterogeneous collection of
authoring systems, and as a unidirectional interchange format to a
heterogeneous collection of distribution formats after undergoing transcoding
@@ -473,16 +473,16 @@
</pre></div>
</td></tr></tbody></table><p>Document level metadata may specify a document title, description,
and copyright information. In addition, arbitrary metadata drawn from
-other namespaces may be specified.</p><table summary="HTML Table" id="dfxp-example-metadata" class="example"><caption>Example Fragment – DFXP Metadata</caption><tbody><tr><td>
+other namespaces may be specified.</p><table summary="HTML Table" id="dfxp-example-metadata" class="example"><caption>Example Fragment – TTML Metadata</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<metadata xmlns:ttm="http://www.w3.org/ns/ttml#metadata">
- <ttm:title>Timed Text DFXP Example</ttm:title>
+ <ttm:title>Timed Text TTML Example</ttm:title>
<ttm:copyright>The Authors (c) 2006</ttm:copyright>
</metadata>
</pre></div>
</td></tr></tbody></table><p>Styling information may be specified in the form of style specification
-definitions that are referenced by layout and content information.</p><p>In <a href="#dfxp-example-styling"><b>Example Fragment – DFXP Styling</b></a>, four style sets of specifications
-are defined, with one set serving as a collection of default styles.</p><table summary="HTML Table" id="dfxp-example-styling" class="example"><caption>Example Fragment – DFXP Styling</caption><tbody><tr><td>
+definitions that are referenced by layout and content information.</p><p>In <a href="#dfxp-example-styling"><b>Example Fragment – TTML Styling</b></a>, four style sets of specifications
+are defined, with one set serving as a collection of default styles.</p><table summary="HTML Table" id="dfxp-example-styling" class="example"><caption>Example Fragment – TTML Styling</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<styling xmlns:tts="http://www.w3.org/ns/ttml#styling">
<!-- s1 specifies default color, font, and text alignment -->
@@ -504,11 +504,11 @@
is intended to be presented. A region definition may reference one or
more sets of style specifications in order to permit content flowed in the
region to inherit from these styles.
-In <a href="#dfxp-example-layout"><b>Example Fragment – DFXP Layout</b></a>, the region definition makes
+In <a href="#dfxp-example-layout"><b>Example Fragment – TTML Layout</b></a>, the region definition makes
reference to style specification <code>s1</code> which allows all content
flowed into the region to inherit from the region's styles (in the case
that a style is not already explicitly specified on content or inherited
-via the content hierarchy.)</p><table summary="HTML Table" id="dfxp-example-layout" class="example"><caption>Example Fragment – DFXP Layout</caption><tbody><tr><td>
+via the content hierarchy.)</p><table summary="HTML Table" id="dfxp-example-layout" class="example"><caption>Example Fragment – TTML Layout</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<layout xmlns:tts="http://www.w3.org/ns/ttml#styling">
<region xml:id="subtitleArea"
@@ -520,16 +520,16 @@
/>
</layout>
</pre></div>
-</td></tr></tbody></table><p>The content of a DFXP document instance is expressed in its
+</td></tr></tbody></table><p>The content of a TTML document instance is expressed in its
body, which is organized in terms of block and inline text elements.
The hierarchical organization of content elements serves a primary role in
determining both spatial and temporal relationships. For example, in
-<a href="#dfxp-example-body"><b>Example Fragment – DFXP Body</b></a>, each paragraph (<code>p</code> element)
+<a href="#dfxp-example-body"><b>Example Fragment – TTML Body</b></a>, each paragraph (<code>p</code> element)
is flowed into its target region in the specified lexical order; furthermore,
the active time interval of each paragraph is timed in accordance to its
parent or sibling according to the applicable time containment semantics —
in this case, the division parent is interpreted as a parallel time
-container.</p><table summary="HTML Table" id="dfxp-example-body" class="example"><caption>Example Fragment – DFXP Body</caption><tbody><tr><td>
+container.</p><table summary="HTML Table" id="dfxp-example-body" class="example"><caption>Example Fragment – TTML Body</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<body region="subtitleArea">
<div>
@@ -612,20 +612,20 @@
style applied to the second paragraph to override the default color.
Note that the flow order is determined by the lexical order of
elements as they appear in the content hierarchy.</p><table summary="HTML Table" id="dfxp-example-subtitle-9" class="example-images"><caption>Subtitles 9a and 9b – Time Interval [53.5, 58.7)</caption><tbody><tr><td><img src="images/subtitle9.png" alt="Subtitles 9a and 9b"/></td></tr></tbody></table><p>The examples shown above demonstrate the primary types of information that may
-be authored using DFXP: metadata, styling, layout, timing, and content. In typical cases,
+be authored using TTML: metadata, styling, layout, timing, and content. In typical cases,
styling and layout information are separately specified in a document instance. Content information
is expressed in a hierarchical fashion that embodies the organization of both spatial (flow) and
timing information. Content makes direct or indirect references to styling and layout information
and may specify inline overrides to styling.</p></div></div><div class="div1">
<h2><a name="definitions" id="definitions"/>2 Definitions</h2><div class="div2">
-<h3><a name="acronyms" id="acronyms"/>2.1 Acronyms</h3><table class="acronyms" summary="Glossary List"><tr><td class="label"><b>DFXP</b></td><td class="def"><p>Distribution Format Exchange Profile</p></td></tr><tr><td class="label"><b>TT</b></td><td class="def"><p>Timed Text</p></td></tr><tr><td class="label"><b>TT AS</b></td><td class="def"><p>Timed Text Authoring System</p></td></tr><tr><td class="label"><b>TT AF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TT WG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
+<h3><a name="acronyms" id="acronyms"/>2.1 Acronyms</h3><table class="acronyms" summary="Glossary List"><tr><td class="label"><b>DFXP</b></td><td class="def"><p>Distribution Format Exchange Profile</p></td></tr><tr><td class="label"><b>TT</b></td><td class="def"><p>Timed Text</p></td></tr><tr><td class="label"><b>TTML</b></td><td class="def"><p>Timed Text Markup Language</p></td></tr><tr><td class="label"><b>TT AS</b></td><td class="def"><p>Timed Text Authoring System</p></td></tr><tr><td class="label"><b>TT AF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TT WG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
<h3><a name="terms" id="terms"/>2.2 Terminology</h3><dl><dt class="label">Abstract Document Instance</dt><dd><p>An instance of an abstract data set as represented by a
<em>Reduced XML Infoset</em>.</p></dd><dt class="label">Abstract Document Type</dt><dd><p>A set of constraints that defines a class of <em>XML Information
Set</em>s <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label">Attribute Information Item</dt><dd><p>Each specified or defaulted attribute of an XML document corresponds with an attribute information
item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.3.</p></dd><dt class="label">Character Information Item</dt><dd><p>Each data character appearing in an XML document corresponds with a character information
-item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.6.</p></dd><dt class="label">Content Processor</dt><dd><p>A processing system capable of importing (receiving) timed text authoring format
+item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.6.</p></dd><dt class="label">Content Processor</dt><dd><p>A processing system capable of importing (receiving) Timed Text Markup Language
content for the purpose of transforming, presenting, or otherwise processing the content.</p></dd><dt class="label">Content Profile</dt><dd><p>A collection of features and extensions that are (or may be) employed by
-timed text authoring format content.</p></dd><dt class="label">Content Region</dt><dd><p>A logical region into which rendered content is placed when modeling or
+Timed Text Markup Language content.</p></dd><dt class="label">Content Region</dt><dd><p>A logical region into which rendered content is placed when modeling or
performing presentation processing.</p></dd><dt class="label">Element Information Item</dt><dd><p>Each element appearing in an XML document corresponds with an element information
item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.2.</p></dd><dt class="label">Exchange Profile</dt><dd><p>A content profile that serves a set of needs
for content interchange.</p></dd><dt class="label">Extension</dt><dd><p>A syntactic or semantic expression or capability that is defined and
@@ -641,14 +641,14 @@
is composed and rendered during presentation processing.</p></dd><dt class="label">Reduced XML Infoset</dt><dd><p>An XML Information Set <a href="#infoset">[XML InfoSet]</a> that satisfieds the
constraints specify by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></dd><dt class="label">Root Container Region</dt><dd><p>A logical region that establishes a coordinate system into which
content regions are placed and optionally clipped.</p></dd><dt class="label">Timed Text</dt><dd><p>Textual information that is intrinsically or extrinsically
-associated with timing information.</p></dd><dt class="label">Timed Text Authoring Format</dt><dd><p>A content type that represents timed text media for the purpose of
+associated with timing information.</p></dd><dt class="label">Timed Text Markup Language</dt><dd><p>A content type that represents timed text media for the purpose of
interchange among authoring systems.</p></dd><dt class="label">Timed Text Authoring System</dt><dd><p>A content authoring system capable of importing and exporting
-timed text authoring format content.</p></dd></dl></div><div class="div2">
+Timed Text Markup Language content.</p></dd></dl></div><div class="div2">
<h3><a name="conventions" id="conventions"/>2.3 Documentation Conventions</h3><p>Within normative prose in this specification, the words
<em>may</em>, <em>should</em>, and <em>must</em> are
-defined as follows:</p><dl class="conformance-keywords"><dt class="label">may</dt><dd><p>Conforming documents and/or TT AF processors are permitted to,
-but need not behave as described. </p></dd><dt class="label">should</dt><dd><p>Conforming documents and/or TT AF processors are strongly
-recommended to, but need not behave as described.</p></dd><dt class="label">must</dt><dd><p>Conforming documents and/or TT AF processors are required
+defined as follows:</p><dl class="conformance-keywords"><dt class="label">may</dt><dd><p>Conforming documents and/or TTML processors are permitted to,
+but need not behave as described. </p></dd><dt class="label">should</dt><dd><p>Conforming documents and/or TTML processors are strongly
+recommended to, but need not behave as described.</p></dd><dt class="label">must</dt><dd><p>Conforming documents and/or TTML processors are required
to behave as described; otherwise, they are in error. </p></dd></dl><p>All normative syntactic definitions of XML representations and
other related terms are depicted with a light orange background color
and labeled as "XML Representation" or "Syntax Representation", such
@@ -688,8 +688,8 @@
</pre></div>
</td></tr></tbody></table></div></div><div class="div1">
<h2><a name="conformance" id="conformance"/>3 Conformance</h2><p>This section specifies the general conformance requirements for
-TT AF content and processors.</p><div class="div2">
-<h3><a name="conformance-content" id="conformance-content"/>3.1 Content Conformance</h3><p>A TT AF document instance conforms to this specification if the following criteria are
+TTML content and processors.</p><div class="div2">
+<h3><a name="conformance-content" id="conformance-content"/>3.1 Content Conformance</h3><p>A TTML document instance conforms to this specification if the following criteria are
satisfied:</p><ol class="enumar"><li><p>When transporting a document instance in a context in which a MIME
Media Type <a href="#mime-media">[MIME]</a> identifies the content type of the interchanged document
instance, then the specified media type is
@@ -701,7 +701,7 @@
<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p></li><li><p>The document instance is or can be represented as a Reduced XML
Infoset as defined by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></li><li><p>The Reduced XML
Infoset that corresponds to the document instance is or can
-be associated with one of the TT AF Abstract
+be associated with one of the TTML Abstract
Document Types defined by
<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The Reduced XML Infoset that corresponds to the document instance is a
Valid Abstract Document Instance of the associated
@@ -710,39 +710,39 @@
should satisfy the web content accessibility guidelines specified by
<a href="#wcag">[WCAG]</a>.</p></li></ol></div><div class="div2">
<h3><a name="conformance-processor" id="conformance-processor"/>3.2 Processor Conformance</h3><div class="div3">
-<h4><a name="conformance-generic-processor" id="conformance-generic-processor"/>3.2.1 Generic Processor Conformance</h4><p>A TT AF processor conforms to this specification if the following
+<h4><a name="conformance-generic-processor" id="conformance-generic-processor"/>3.2.1 Generic Processor Conformance</h4><p>A TTML processor conforms to this specification if the following
generic processor criteria are
satisfied:</p><ol class="enumar"><li><p>The processor provides at least one mechanism for notionally
instantiating a Reduced XML
-Infoset representation of a conformant TT AF document
-instance.</p></li><li><p>If a process does or can perform validation of a candidate TT AF
+Infoset representation of a conformant TTML document
+instance.</p></li><li><p>If a process does or can perform validation of a candidate TTML
document instance, then it provides at least one mechanism to
implicitly or explicitly associate the
Reduced XML Infoset representation
-of a conformant TT AF document instance with one of the
-TT AF Abstract Document Types defined by
+of a conformant TTML document instance with one of the
+TTML Abstract Document Types defined by
<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The processor does not <em>a priori</em> reject or abort the
-processing of a conformant TT AF document instance
+processing of a conformant TTML document instance
unless the processor does not support some required
-(mandatory) feature specified or implied by a TT AF content profile
+(mandatory) feature specified or implied by a TTML content profile
declared to apply to the document instance.</p></li><li><p>The processor supports all mandatory processing semantics defined by this specification.</p></li><li><p>If the processor supports some optional processing semantics defined by this specification,
then it does so in a manner consistent with the defined semantics.</p></li></ol></div><div class="div3">
-<h4><a name="conformance-transformation-processor" id="conformance-transformation-processor"/>3.2.2 Transformation Processor Conformance</h4><p>A TT AF processor is a conformant TT AF transformation processor if
+<h4><a name="conformance-transformation-processor" id="conformance-transformation-processor"/>3.2.2 Transformation Processor Conformance</h4><p>A TTML processor is a conformant TTML transformation processor if
the following criteria are satisfied:</p><ol class="enumar"><li><p>The processor satisfies all requirements specified by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the DFXP Transformation profile as specified
by <a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a>.</p></li></ol></div><div class="div3">
<h4><a name="conformance-presentation-processor" id="conformance-presentation-processor"/>3.2.3 Presentation Processor Conformance</h4><ol class="enumar"><li><p>The processor satisfies all requirements specified by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the DFXP Presentation profile as specified
by <a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a>.</p></li></ol></div></div><div class="div2">
-<h3><a name="claims" id="claims"/>3.3 Claims</h3><p>Any claim of compliance with respect to TT AF content or processor
+<h3><a name="claims" id="claims"/>3.3 Claims</h3><p>Any claim of compliance with respect to TTML content or processor
conformance must make
reference to an implementation compliance statement (ICS).</p><p>An implementation compliance statement must identify all mandatory
and optional features of this specification that are satisfied by the
content or processor implementation. In particular, the statement must
-identify the utilized or supported TT AF vocabulary profile(s) as
+identify the utilized or supported TTML vocabulary profile(s) as
defined by <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>, and, if a subset or
superset profile is used or supported, then what features are excluded
-or included in the subset or superset profile.</p><p>A TT AF document instance for which a compliance claim is made
+or included in the subset or superset profile.</p><p>A TTML document instance for which a compliance claim is made
must specify
either (1)
a <code>ttp:profile</code> attribute on its root
@@ -753,7 +753,7 @@
a <code>ttp:profile</code> element as a child of the
<code>head</code> element as defined by
<a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p></div></div><div class="div1">
-<h2><a name="doctypes" id="doctypes"/>4 Document Types</h2><p>This section defines the following TT AF Abstract Document Types:</p><ul><li><p><a href="#dfxp-content-doctype"><b>4.1 DFXP Content</b></a></p></li></ul><p>Each abstract document type consists of the following constraints:</p><ul><li><p>a non-empty collection of element types, where each element type consists of a name,
+<h2><a name="doctypes" id="doctypes"/>4 Document Types</h2><p>This section defines the following TTML Abstract Document Types:</p><ul><li><p><a href="#dfxp-content-doctype"><b>4.1 DFXP Content</b></a></p></li></ul><p>Each abstract document type consists of the following constraints:</p><ul><li><p>a non-empty collection of element types, where each element type consists of a name,
a (possibly empty) collection of attributes, and a content specification</p></li><li><p>a non-empty collection of element types that may appear as the document element</p></li></ul><p>An Abstract Document Instance may be assessed in terms of validity,
and is considered to be a Valid Abstract Document Instance if it
satisfies the following condition: if after</p><ol class="enumar"><li><p>pruning all element information
@@ -774,12 +774,12 @@
supported content profile, a given document instance may be
constrained by the author or authoring tool to satisfy a more
restrictive definition of validity.</p></div><div class="div2">
-<h3><a name="dfxp-content-doctype" id="dfxp-content-doctype"/>4.1 DFXP Content</h3><p>DFXP Content is an abstract document type of the Timed Text Authoring Format intended
+<h3><a name="dfxp-content-doctype" id="dfxp-content-doctype"/>4.1 DFXP Content</h3><p>DFXP Content is an abstract document type of a profile of the Timed Text Markup Language intended
to be used for interchange among distribution systems. This document type
is defined in terms of the
element and attribute vocabulary
specified in <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification defines two types of normative schemas that may be used to validate a subset of
-conformant DFXP document instances:</p><ul><li><p><a href="#dfxp-schema-rnc"><b>B.1 Relax NG Schema</b></a></p></li><li><p><a href="#dfxp-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a DFXP document instance must be a
+conformant DFXP Content document instances:</p><ul><li><p><a href="#dfxp-schema-rnc"><b>B.1 Relax NG Schema</b></a></p></li><li><p><a href="#dfxp-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a DFXP Content document instance must be a
<code>tt</code> element, as defined by <a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The schemas included in this specification do not validate all syntactic constraints
defined by this specification. In particular, performing validation with one of the above
referenced schemas may result in a <em>false positive</em> indication of validity.
@@ -788,20 +788,20 @@
when used with a compliant validating
processor.</p><p>In exception to the above statement about false negatives,
if the Relax NG schema included in this specification is used to validate a
-TT AF Document containing elements in a foreign namespace and the <code>xml:id</code>
+TTML Document containing elements in a foreign namespace and the <code>xml:id</code>
attribute is used with any of those (foreign) elements,
then an error will be reported even though such usage is permitted by this
specification. In this case, the false negative arises due
to a specific limitation in expressing wildcard patterns involving <code>xsd:ID</code>
typed attributes in Relax NG schemas.
-Note that this specification defines the formal validity of a TT AF Document to be
+Note that this specification defines the formal validity of a TTML Document to be
based on an abstract document instance from which all foreign namespace elements and
attributes have been removed. Therefore, the exceptional reporting of this false
-negative does not impact the formal assessment of TT AF Document validity.</p></div></div></div><div class="div1">
+negative does not impact the formal assessment of TTML Document validity.</p></div></div></div><div class="div1">
<h2><a name="vocabulary" id="vocabulary"/>5 Vocabulary</h2><p>This section defines the
namespaces, profiles, and vocabulary (as an element an attribute
-catalog) of the Timed Text Authoring Format (TT AF) as follows:</p><ul><li><p><a href="#vocabulary-namespaces"><b>5.1 Namespaces</b></a></p></li><li><p><a href="#vocabulary-profiles"><b>5.2 Profiles</b></a></p></li><li><p><a href="#vocabulary-overview"><b>5.3 Catalog</b></a></p></li></ul><div class="div2">
-<h3><a name="vocabulary-namespaces" id="vocabulary-namespaces"/>5.1 Namespaces</h3><p>The Timed Text Authoring Format (TT AF) employs a number of
+catalog) of the Timed Text Markup Language (TTML) as follows:</p><ul><li><p><a href="#vocabulary-namespaces"><b>5.1 Namespaces</b></a></p></li><li><p><a href="#vocabulary-profiles"><b>5.2 Profiles</b></a></p></li><li><p><a href="#vocabulary-overview"><b>5.3 Catalog</b></a></p></li></ul><div class="div2">
+<h3><a name="vocabulary-namespaces" id="vocabulary-namespaces"/>5.1 Namespaces</h3><p>The Timed Text Markup Language (TTML) employs a number of
namespaces for elements and certain
global attributes. The following table specifies this set of namespaces
and indicates the default prefix used within this specification and the
@@ -814,10 +814,10 @@
future version of this specification). In such cases, the use of the
namespace URI is for purposes other than defining XML vocabulary,
e.g., for designating profiles, features, extensions and for
-dereferencing standard profile definitions.</p></div><p>All TT AF Namespaces are <a href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><em>mutable</em></a>
+dereferencing standard profile definitions.</p></div><p>All TTML Namespaces are <a href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><em>mutable</em></a>
<a href="#nsstate">[NSState]</a>; all undefined names in these namespaces are reserved for future
standardization by the W3C.</p></div><div class="div2">
-<h3><a name="vocabulary-profiles" id="vocabulary-profiles"/>5.2 Profiles</h3><p>The Timed Text Authoring Format (TT AF) employs a number of
+<h3><a name="vocabulary-profiles" id="vocabulary-profiles"/>5.2 Profiles</h3><p>The Timed Text Markup Language (TTML) employs a number of
standard, predefined profiles of its
vocabulary and associated semantics.
The following table specifies this set of
@@ -835,8 +835,8 @@
would be
<code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>.</p></div><p>A profile designator is not restricted to the set of designators enumerated
in <a href="#profile-vocab-table"><b>Table 2 – Profiles</b></a>, but may be any URI that
-feasibly dereferences a TT AF Profile Definition Document.</p><p>The profile of TT AF that must be supported by a
-TT AF content processor in order to process a document
+feasibly dereferences a TTML Profile Definition Document.</p><p>The profile of TTML that must be supported by a
+TTML content processor in order to process a document
instance is specified either (1) by specifying a
<code>ttp:profile</code> attribute on the root <code>tt</code> element, as
defined by <a href="#parameter-attribute-profile"><b>6.2.8 ttp:profile</b></a>, or (2) by
@@ -849,7 +849,7 @@
attribute are present (in a given document instance), then the
<code>ttp:profile</code> attribute must be ignored for the purpose of
determining the declared profile requirements.</p><p>If more than one <code>ttp:profile</code> element appears in
-a TT AF document instance, then all specified profiles apply
+a TTML document instance, then all specified profiles apply
simultaneously. In such a case, if some feature or some extension is
specified by one profile to be used (mandatory and enabled) and by
another profile to be required (mandatory) or optional (voluntary),
@@ -861,16 +861,16 @@
<a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
attribute nor
<a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a>
-element is present in a TT AF document instance, and if the document
+element is present in a TTML document instance, and if the document
interchange context does not specify a profile,
then the DFXP Transformation
profile applies.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is intended that the <code>ttp:profile</code> attribute be used when
the author wishes to reference one of the standard, predefined profiles of
-TT AF content, and does not wish to modify (by supersetting or subsetting)
+TTML content, and does not wish to modify (by supersetting or subsetting)
that profile. This attribute may also be used by an author to indicate the use
of a non-standard profile, in which case the specified profile designator expresses
-a URI that denotes an externally defined TT AF Profile Definition Document.
-However, it is not required that a conformant TT AF content processor be able
+a URI that denotes an externally defined TTML Profile Definition Document.
+However, it is not required that a conformant TTML content processor be able
to dereference such an externally specified profile definition.</p><p>In contrast, it is intended that the <code>ttp:profile</code> element be
used when the author wishes to make use of a modified predefined profile or
wishes to include in the document instance a non-standard profile definition
@@ -883,13 +883,13 @@
is referred to as a <em>subtractive</em> profile; when modified by supersetting, the result
is referred to as an <em>additive</em> profile.
It is also possible to define a derived profile that is simultaneously subtractive
-and additive.</p></div><p>If a TT AF document instance makes use of a feature defined by
+and additive.</p></div><p>If a TTML document instance makes use of a feature defined by
<a href="#feature-designations"><b>D.1 Feature Designations</b></a> and if the intended use of the
document requires the recognition and processing of that feature, then
the document must include a <em>required feature</em> or
a <em>used feature</em>
specification in one of its declared or
-referenced profiles. If a TT AF document instance makes use
+referenced profiles. If a TTML document instance makes use
of an extension designatable by <a href="#extension-designations"><b>E.1 Extension Designations</b></a> and if the intended use of the document
requires the recognition and processing of that extension, then the
document must include a <em>required extension</em> or
@@ -927,15 +927,15 @@
optional as it is defined
in <a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a>). Note also the resetting of the
default XMLNS binding on the <code>profile</code> element to the TT Parameter Namespace.</p></div></div><div class="div2">
-<h3><a name="vocabulary-overview" id="vocabulary-overview"/>5.3 Catalog</h3><p>The vocabulary of the Timed Text Authoring Format (TT AF) is
-defined in the following major catalogs (divisions of vocabulary):</p><ul><li><p><a href="#core-vocabulary-overview"><b>5.3.1 Core Catalog</b></a></p></li><li><p><a href="#extension-vocabulary-overview"><b>5.3.2 Extension Catalog</b></a></p></li></ul><p>The core catalog defines the baseline, core vocabulary of the TT
-AF, and, in particular, the vocabulary of DFXP. The extension catalog
+<h3><a name="vocabulary-overview" id="vocabulary-overview"/>5.3 Catalog</h3><p>The vocabulary of the Timed Text Markup Language (TTML) is
+defined in the following major catalogs (divisions of vocabulary):</p><ul><li><p><a href="#core-vocabulary-overview"><b>5.3.1 Core Catalog</b></a></p></li><li><p><a href="#extension-vocabulary-overview"><b>5.3.2 Extension Catalog</b></a></p></li></ul><p>The core catalog defines the baseline, core vocabulary of TTML,
+and, in particular, the vocabulary of DFXP. The extension catalog
serves as a placeholder for extensions to the core vocabulary defined
by DFXP.</p><div class="div3">
<h4><a name="core-vocabulary-overview" id="core-vocabulary-overview"/>5.3.1 Core Catalog</h4><p>The core vocabulary catalog is intended to satisfy the needs of
DFXP while providing a baseline vocabulary for future profiles. This vocabulary
is divided into distinct categories, specified in detail
-in the following sections:</p><ul><li><p><a href="#parameters"><b>6 Parameters</b></a></p></li><li><p><a href="#content"><b>7 Content</b></a></p></li><li><p><a href="#styling"><b>8 Styling</b></a></p></li><li><p><a href="#layout"><b>9 Layout</b></a></p></li><li><p><a href="#timing"><b>10 Timing</b></a></p></li><li><p><a href="#animation"><b>11 Animation</b></a></p></li><li><p><a href="#metadata"><b>12 Metadata</b></a></p></li></ul><p>The core element vocabulary specified for use with a TT AF document
+in the following sections:</p><ul><li><p><a href="#parameters"><b>6 Parameters</b></a></p></li><li><p><a href="#content"><b>7 Content</b></a></p></li><li><p><a href="#styling"><b>8 Styling</b></a></p></li><li><p><a href="#layout"><b>9 Layout</b></a></p></li><li><p><a href="#timing"><b>10 Timing</b></a></p></li><li><p><a href="#animation"><b>11 Animation</b></a></p></li><li><p><a href="#metadata"><b>12 Metadata</b></a></p></li></ul><p>The core element vocabulary specified for use with a TTML document
instance is enumerated in
<a href="#element-vocab-table"><b>Table 3 – Element Vocabulary</b></a>.</p><table summary="HTML Table" id="element-vocab-table" class="common"><caption>Table 3 – Element Vocabulary</caption><col width="25%" span="1"/><tbody><tr><th>Module</th><th>Elements</th></tr><tr><td>
Animation
@@ -986,7 +986,7 @@
<a href="#styling-vocabulary-styling">styling</a>,
<a href="#styling-vocabulary-style">style</a>
</td></tr></tbody></table><p/><p>Element vocabulary groups that are used in defining content models
-for TT AF element types are enumerated in <a href="#element-vocab-group-table"><b>Table 4 – Element Vocabulary Groups</b></a>.</p><table summary="HTML Table" id="element-vocab-group-table" class="common"><caption>Table 4 – Element Vocabulary Groups</caption><col width="25%" span="1"/><tbody><tr><th>Group</th><th>Elements</th></tr><tr><td>
+for TTML element types are enumerated in <a href="#element-vocab-group-table"><b>Table 4 – Element Vocabulary Groups</b></a>.</p><table summary="HTML Table" id="element-vocab-group-table" class="common"><caption>Table 4 – Element Vocabulary Groups</caption><col width="25%" span="1"/><tbody><tr><th>Group</th><th>Elements</th></tr><tr><td>
Animation.class
</td><td>
<a href="#animation-vocabulary-set">set</a>
@@ -1081,18 +1081,18 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>Only those attributes defined as either (1) global, i.e., namespace qualified, or
(2) shared element-specific, i.e., not namespace qualified but shared across multiple
element types, are listed in <a href="#attribute-vocab-table"><b>Table 5 – Attribute Vocabulary</b></a> above.
-</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>All vocabulary defined by the TT AF consistently makes use of
+</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>All vocabulary defined by TTML consistently makes use of
the so-called <em>lowerCamelCase</em> naming convention. In some cases, this results in the
change of a name when the name was based upon another specification
that used a different naming convention.</p></div></div><div class="div3">
<h4><a name="extension-vocabulary-overview" id="extension-vocabulary-overview"/>5.3.2 Extension Catalog</h4><p>The extension vocabulary catalog is intended for use by future
-profiles of the TT AF, and is not further defined
-by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming TT
-AF document instance may contain arbitrary namespace qualified
+profiles of TTML, and is not further defined
+by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming TTML
+document instance may contain arbitrary namespace qualified
elements that reside in any namespace other than those namespaces
-defined for use with this specification. Furthermore, a conforming TT
-AF document instance may contain arbitrary namespace qualified
-attributes on TT AF defined vocabulary where such attributes reside in
+defined for use with this specification. Furthermore, a conforming TTML
+document instance may contain arbitrary namespace qualified
+attributes on TTML defined vocabulary where such attributes reside in
any namespace other than those defined for use with this
specification.</p></div></div></div><div class="div1">
<h2><a name="parameters" id="parameters"/>6 Parameters</h2><p>This section specifies the <em>parameters</em> matter of the
@@ -1101,15 +1101,15 @@
essential or (2) of significant importance for the purpose of
interpreting the semantics of other types of information expressed by
core vocabulary items or for establishing a processing context by means
-of which TT AF content can be related to an external environment.</p><div class="div2">
+of which TTML content can be related to an external environment.</p><div class="div2">
<h3><a name="parameter-element-vocabulary" id="parameter-element-vocabulary"/>6.1 Parameter Element Vocabulary</h3><p>The following elements, all defined in the TT Parameter
Namespace, specify parametric information that applies to a document
or a content processor:</p><ul><li><p><a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a></p></li><li><p><a href="#parameter-vocabulary-features"><b>6.1.2 ttp:features</b></a></p></li><li><p><a href="#parameter-vocabulary-feature"><b>6.1.3 ttp:feature</b></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><b>6.1.4 ttp:extensions</b></a></p></li><li><p><a href="#parameter-vocabulary-extension"><b>6.1.5 ttp:extension</b></a></p></li></ul><div class="div3">
<h4><a name="parameter-vocabulary-profile" id="parameter-vocabulary-profile"/>6.1.1 ttp:profile</h4><p>The <code>ttp:profile</code> element is used to specify a collection of
used (mandatory and enabled), required (mandatory),
and optional (voluntary) features and extensions that must or
-may be supported by a TT AF content processor in order to process a TT
-AF document that makes use (or may make use) of such features and
+may be supported by a TTML content processor in order to process a TTML
+document that makes use (or may make use) of such features and
extensions.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The difference between a <em>feature</em> and an
<em>extension</em> is where it is defined and how it is labeled:
if defined in this specification (or a future revision thereof) and
@@ -1118,16 +1118,16 @@
and labeled there with an extension designation, then it is considered
to be an extension. In general, features are expected to be defined by
the W3C standards process, while extensions are expected to be defined by
-third parties.</p></div><p>This specification defines two distinct uses of the <code>ttp:profile</code> element:</p><ul><li><p>as a child of the <code>head</code> element within a TT AF document
-instance;</p></li><li><p>as the root element of a TT AF Profile Definition document
-instance;</p></li></ul><p>When a <code>tt:profile</code> element appears within a TT AF document
+third parties.</p></div><p>This specification defines two distinct uses of the <code>ttp:profile</code> element:</p><ul><li><p>as a child of the <code>head</code> element within a TTML document
+instance;</p></li><li><p>as the root element of a TTML Profile Definition document
+instance;</p></li></ul><p>When a <code>tt:profile</code> element appears within a TTML document
instance, its purpose is to express authorial intentions about which
features and extensions must or may be supported by a recipient
content processor. In addition, the element indirectly expresses
information about the set of features or extensions that are (or may
-expected to be) used by the document instance.</p><p>When a <code>tt:profile</code> element is used by a TT AF
+expected to be) used by the document instance.</p><p>When a <code>tt:profile</code> element is used by a TTML
Profile Definition document instance, it serves to publish a machine
-readable specification of a specific TT AF content profile, of which
+readable specification of a specific TTML content profile, of which
this specification defines four such Profile Definition Documents in
<a href="#profiles"><b>F Profiles</b></a>.</p><p>The <code>ttp:profile</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group, followed by
@@ -1146,8 +1146,8 @@
§3.2.17, and, furthermore, must denote a profile designator in
accordance with <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>. In this case,
the profile designator must refer to (1) a standard, predefined
-TT AF Profile Definition Document as defined by <a href="#profiles"><b>F Profiles</b></a>,
-or (2) a dereferenceable resource representing a valid TT AF Profile Definition
+TTML Profile Definition Document as defined by <a href="#profiles"><b>F Profiles</b></a>,
+or (2) a dereferenceable resource representing a valid TTML Profile Definition
document instance. In either case, the referenced profile serves as the
baseline profile of the specifying <code>ttp:profile</code> element.</p><p>If the <code>use</code> attribute is not specified, then the baseline
profile of the <code>ttp:profile</code> element must be considered to be
@@ -1162,32 +1162,32 @@
and extensions of the profile, where merging a feature or extension
entails replacing an existing feature or extension specification, if
it already exists, or adding a new feature or extension specification,
-if it does not yet exist in the profile;</p></li></ol><p>A conformant TT AF processor is not required to be able to
-dereference a TT AF Profile Definition Document that is not one of the
+if it does not yet exist in the profile;</p></li></ol><p>A conformant TTML processor is not required to be able to
+dereference a TTML Profile Definition Document that is not one of the
standard, predefined profiles defined by <a href="#profiles"><b>F Profiles</b></a>. A
-conformant TT AF processor may make use of a built-in, static
+conformant TTML processor may make use of a built-in, static
form of each standard, predefined profile so as not to require
-dereferencing a network resource.</p><p>If a TT AF processor is unable to dereference a non-standard TT AF
+dereferencing a network resource.</p><p>If a TTML processor is unable to dereference a non-standard TTML
Profile Definition Document, then it must not further process the
document without the presence of an explicit override from an end-user
or some implementation specific parameter traceable to an end-user or
-to a user or system configuration setting. If a TT AF processor aborts
-processing of a TT AF document instance due to the inability to
-reference a non-standard TT AF Profile Definition Document, then some
+to a user or system configuration setting. If a TTML processor aborts
+processing of a TTML document instance due to the inability to
+reference a non-standard TTML Profile Definition Document, then some
end-user notification should be given unless the end-user or system
has disabled such a notification, or if the processor does not permit
or entail the intervention of an end-user.</p><p>The <code>ttp:profile</code> element is illustrated by the following example.</p><table summary="HTML Table" id="parameter-vocabulary-profile-example-1" class="example"><caption>Example Fragment – ttp:profile</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:profile use="dfxp-presentation">
<ttp:features xml:base="http://www.w3.org/ns/ttml/feature/">
- <ttp:feature>#rollUp</ttp:feature>
+ <ttp:feature>#text-outline</ttp:feature>
</ttp:features>
</ttp:profile>
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the DFXP presentation profile is used as the
baseline profile. This baseline profile is then supersetted (thus
creating an additive derived profile) by requiring support for
-<code>#rollUp</code> feature.</p></div></div><div class="div3">
+<code>#text-outline</code> feature.</p></div></div><div class="div3">
<h4><a name="parameter-vocabulary-features" id="parameter-vocabulary-features"/>6.1.2 ttp:features</h4><p>The <code>ttp:features</code> element is a container element used to group
infomation about feature support requirements.</p><p>The <code>ttp:features</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group, followed by
@@ -1235,7 +1235,7 @@
defined by <a href="#feature-designations"><b>D.1 Feature Designations</b></a>.</p><p>If
the URI expressed by the content of the <code>ttp:feature</code> element
is a relative URI, then an <code>xml:base</code> attribute should be
-specified on the nearest ancestor <code>ttp:features</code> element.</p><p>The <code>value</code> attribute specifies whether a conforming TT AF
+specified on the nearest ancestor <code>ttp:features</code> element.</p><p>The <code>value</code> attribute specifies whether a conforming TTML
processor must or may implement the designated feature in order to
process the document. If the value of the <code>value</code> attribute
is <code>optional</code>, then the processor need
@@ -1251,17 +1251,17 @@
specified on a <code>ttp:feature</code> element, it is equivalent to
specifying that support for the feature is required.</p></div><p>If the value of the <code>value</code> attribute is
<code>required</code> or <code>use</code>,
-and if the TT AF processor implementation does
+and if the TTML processor implementation does
not support the feature, then it must not further process the document
without the presence of an explicit override from an end-user or some
implementation specific parameter traceable to an end-user or to a
-user or system configuration setting. If a TT AF processor aborts
-processing of a TT AF document instance due to the specification of a
+user or system configuration setting. If a TTML processor aborts
+processing of a TTML document instance due to the specification of a
required, but unsupported feature by this element, then some end-user
notification should be given unless the end-user or system has
disabled such a notification, or if the processor does not permit or
entail the intervention of an end-user.</p><p>If the value of the <code>value</code> attribute is
-<code>optional</code>, and if the TT AF processor implementation does
+<code>optional</code>, and if the TTML processor implementation does
not support the feature, then it may further process the document even
in the case that some use of the feature is present in the document.
In the case of actual use of a feature designated as optional, the
@@ -1285,12 +1285,8 @@
<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). Note that
-the explicit specification of <code>required</code> on the
-<code>value</code> attribute on these two
-<code>ttp:feature</code> elements is not strictly
-necessary, since it is the default value of this
-attribute.</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 name="parameter-vocabulary-extensions" id="parameter-vocabulary-extensions"/>6.1.4 ttp:extensions</h4><p>The <code>ttp:extensions</code> element is a container element used to group
@@ -1340,7 +1336,7 @@
as defined by <a href="#extension-designations"><b>E.1 Extension Designations</b></a>.</p><p>If the URI expressed by the content of the
<code>ttp:feature</code> element is a relative URI, then an
<code>xml:base</code> attribute should be specified on the nearest
-ancestor <code>ttp:extensions</code> element.</p><p>The <code>value</code> attribute specifies whether a conforming TT AF
+ancestor <code>ttp:extensions</code> element.</p><p>The <code>value</code> attribute specifies whether a conforming TTML
processor must or may implement the designated extension in order to
process the document. If the value of the <code>value</code> attribute
is <code>optional</code>, then the processor need
@@ -1356,17 +1352,17 @@
specified on a <code>ttp:extension</code> element, it is equivalent to
specifying that support for the extension is required.</p></div><p>If the value of the <code>value</code> attribute is
<code>required</code> or <code>use</code>,
-and if the TT AF processor implementation does not support the
+and if the TTML processor implementation does not support the
extension, then it must not further process the document without the
presence of an explicit override from an end-user or some
implementation specific parameter traceable to an end-user or to a
-user or system configuration setting. If a TT AF processor aborts
-processing of a TT AF document instance due to the specification of a
+user or system configuration setting. If a TTML processor aborts
+processing of a TTML document instance due to the specification of a
required, but unsupported extension by this element, then some
end-user notification should be given unless the end-user or system
has disabled such a notification, or if the processor does not permit
or entail the intervention of an end-user.</p><p>If the value of the <code>value</code> attribute is
-<code>optional</code>, and if the TT AF processor implementation does
+<code>optional</code>, and if the TTML processor implementation does
not support the extension, then it may further process the document even
in the case that some use of the extension is present in the document.
In the case of actual use of an extension designated as optional, the
@@ -1599,7 +1595,7 @@
order to convert pixel measurements between different pixel aspect
ratios while still maintaining authorial layout intentions.</p></div></div><div class="div3">
<h4><a name="parameter-attribute-profile" id="parameter-attribute-profile"/>6.2.8 ttp:profile</h4><p>The <code>ttp:profile</code> attribute may be used by a content author
-to express the profile of the Timed Text Authoring Format (TT AF) used
+to express the profile of the Timed Text Markup Language (TTML) used
in a document instance.</p><p>If specified, the value of this attribute must adhere to the
<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
§3.2.17, and, further, must specify a
@@ -1783,7 +1779,7 @@
the <code>begin</code>, <code>dur</code>, and <code>end</code> attributes. If the begin point
of this interval remains unspecified, then the begin point is interpreted as the begin
point of the external time interval. Similarly, if the end point of this interval remains unspecified, then the
-end point is interpreted as the end point of the external time interval.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A TT AF document instance referenced from a SMIL presentation
+end point is interpreted as the end point of the external time interval.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A TTML document instance referenced from a SMIL presentation
is expected to follow the same timing rules as apply to other SMIL media
objects.</p></div><p>If relative begin or end times are specified on the <code>body</code>
element, then these times are resolved by reference to the begin and
@@ -1964,10 +1960,13 @@
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 the 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
+
+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 the 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
+
+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
in this specification, the semantics of space collapsing and
preservation as described above should be respected. For other types
@@ -1978,7 +1977,23 @@
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>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 TTML documents 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
<code><?xml-stylesheet ... ?></code> processing instruction is defined
by this specification.</p><div class="div2">
<h3><a name="styling-element-vocabulary" id="styling-element-vocabulary"/>8.1 Styling Element Vocabulary</h3><p>The following elements specify the structure and principal styling aspects of a
@@ -2011,7 +2026,8 @@
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Style namespace</em>}
{<em>any attribute not in default or any TT namespace</em>}>
- <em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*
+
+ <em>Content:</em> EMPTY
</style>
</pre></div>
</td></tr></tbody></table><p>If a <code>style</code> element appears as a descendant of a
@@ -2074,9 +2090,7 @@
How <span <span class="strong">tts:backgroundColor="green"</span>>I wonder</span> where you're at!
</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-backgroundColor-example-1-images" class="example-images"><caption>Example Rendition – Background Color</caption><tbody><tr><td><img src="images/backgroundColor.png" alt="TT AF 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.7.2.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-backgroundColor-example-1-images" 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">
<h4><a name="style-attribute-color" id="style-attribute-color"/>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
@@ -2105,9 +2119,7 @@
I'll try and tell you what I mean.
</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-color-example-1-images" class="example-images"><caption>Example Rendition – Color</caption><tbody><tr><td><img src="images/color.png" alt="DFXP 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.17.1.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-color-example-1-images" class="example-images"><caption>Example Rendition – Color</caption><tbody><tr><td><img src="images/color.png" alt="DFXP color style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-direction" id="style-attribute-direction"/>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
@@ -2143,9 +2155,7 @@
</pre></div>
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-direction-example-1-images" class="example-images"><caption>Example Rendition – Direction</caption><tbody><tr><td>
<img src="images/direction.png" alt="DFXP direction 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.27.1.</p></div></div><div class="div3">
+</td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-display" id="style-attribute-display"/>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
@@ -2171,11 +2181,11 @@
layout and presentation.</p><p>The <code>tts:display</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-display-example-1" class="example"><caption>Example Fragment – Display</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
- <style tts:extent="369px 119px"/>
- <style tts:backgroundColor="black"/>
- <style tts:color="white"/>
- <style tts:displayAlign="before"/>
- <style tts:textAlign="start"/>
+ <style tts:extent="369px 119px"
+ tts:backgroundColor="black"
+ tts:color="white"
+ tts:displayAlign="before"
+ tts:textAlign="start"/>
</region>
...
<div region="r1">
@@ -2207,9 +2217,7 @@
<img src="images/display_3.png" alt="DFXP display style property - [3,4)"/>
</td></tr><tr><td>
<img src="images/display_4.png" alt="DFXP display style property - [4,5)"/>
-</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.5.</p></div></div><div class="div3">
+</td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-displayAlign" id="style-attribute-displayAlign"/>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
@@ -2266,9 +2274,7 @@
<p region="r4">They sent an<br/> answer back to me.</p>
</div>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-displayAlign-example-1-images" class="example-images"><caption>Example Rendition – Display Align</caption><tbody><tr><td><img src="images/displayAlign.png" alt="DFXP 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.13.4.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-displayAlign-example-1-images" class="example-images"><caption>Example Rendition – Display Align</caption><tbody><tr><td><img src="images/displayAlign.png" alt="DFXP displayAlign style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-extent" id="style-attribute-extent"/>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
@@ -2364,9 +2370,7 @@
</p>
</div>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-fontFamily-example-1-images" class="example-images"><caption>Example Rendition – Font Family</caption><tbody><tr><td><img src="images/fontFamily.png" alt="DFXP 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.8.2.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-fontFamily-example-1-images" class="example-images"><caption>Example Rendition – Font Family</caption><tbody><tr><td><img src="images/fontFamily.png" alt="DFXP fontFamily style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-fontSize" id="style-attribute-fontSize"/>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
@@ -2407,9 +2411,7 @@
that is <span <span class="strong">tts:fontSize="24px"</span>>pleasant</span> to drink.
</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-fontSize-example-1-images" class="example-images"><caption>Example Rendition – Font Size</caption><tbody><tr><td><img src="images/fontSize.png" alt="DFXP 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.8.4.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-fontSize-example-1-images" class="example-images"><caption>Example Rendition – Font Size</caption><tbody><tr><td><img src="images/fontSize.png" alt="DFXP fontSize style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-fontStyle" id="style-attribute-fontStyle"/>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
@@ -2449,9 +2451,7 @@
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/><table summary="HTML Table" id="style-attribute-fontStyle-example-1-images" class="example-images"><caption>Example Rendition – Font Style</caption><tbody><tr><td><img src="images/fontStyle.png" alt="DFXP fontStyle style property"/></td></tr></tbody></table><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.8.7.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-fontStyle-example-1-images" class="example-images"><caption>Example Rendition – Font Style</caption><tbody><tr><td><img src="images/fontStyle.png" alt="DFXP fontStyle style property"/></td></tr></tbody></table><p/></div><div class="div3">
<h4><a name="style-attribute-fontWeight" id="style-attribute-fontWeight"/>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
@@ -2489,9 +2489,7 @@
<span <span class="strong">tts:fontWeight="bold"</span>>but said I could not swim.</span>
</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-fontWeight-example-1-images" class="example-images"><caption>Example Rendition – Font Weight</caption><tbody><tr><td><img src="images/fontWeight.png" alt="DFXP 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.8.9.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-fontWeight-example-1-images" class="example-images"><caption>Example Rendition – Font Weight</caption><tbody><tr><td><img src="images/fontWeight.png" alt="DFXP fontWeight style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-lineHeight" id="style-attribute-lineHeight"/>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
@@ -2529,9 +2527,7 @@
"The bitterness of Life.
"</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-lineHeight-example-1-images" class="example-images"><caption>Example Rendition – Line Height</caption><tbody><tr><td><img src="images/lineHeight.png" alt="DFXP lineHeight style property"/></td></tr></tbody></table><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.15.4.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-lineHeight-example-1-images" class="example-images"><caption>Example Rendition – Line Height</caption><tbody><tr><td><img src="images/lineHeight.png" alt="DFXP lineHeight style property"/></td></tr></tbody></table><p/></div><div class="div3">
<h4><a name="style-attribute-opacity" id="style-attribute-opacity"/>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
@@ -2575,9 +2571,7 @@
<img src="images/opacity_3.png" alt="DFXP opacity style property - [3,4)"/>
</td></tr><tr><td>
<img src="images/opacity_4.png" alt="DFXP opacity style property - [4,5)"/>
-</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">
+</td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-origin" id="style-attribute-origin"/>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,
@@ -2674,9 +2668,7 @@
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-overflow-example-1-images" class="example-images"><caption>Example Rendition – Overflow</caption><tbody><tr><td><img src="images/overflow.png" alt="DFXP 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 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.20.2.</p></div></div><div class="div3">
+progression direction as opposed to the inline progression direction.</p></div></div><div class="div3">
<h4><a name="style-attribute-padding" id="style-attribute-padding"/>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
@@ -2719,11 +2711,7 @@
</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><table summary="HTML Table" id="style-attribute-padding-example-1-images" class="example-images"><caption>Example Rendition – Padding</caption><tbody><tr><td>
<img src="images/padding.png" alt="DFXP padding 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.29.15, except that individual shorthand values map to writing
-mode relative padding values as defined by <a href="#xsl11">[XSL 1.1]</a>,
-§ 7.7.31, 7.7.32, 7.7.33, and 7.7.34.</p></div></div><div class="div3">
+</td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-showBackground" id="style-attribute-showBackground"/>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
@@ -2761,9 +2749,7 @@
<style <span class="strong">tts:showBackground="whenActive"</span>/>
</region>
</pre></div>
-</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.1.</p></div></div><div class="div3">
+</td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-textAlign" id="style-attribute-textAlign"/>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
@@ -2805,9 +2791,7 @@
The frumious Bandersnatch!
</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-textAlign-example-1-images" class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="DFXP 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.15.9.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-textAlign-example-1-images" class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="DFXP textAlign style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-textDecoration" id="style-attribute-textDecoration"/>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
@@ -2852,9 +2836,7 @@
</span>
</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-textDecoration-example-1-images" class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="DFXP 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.16.4.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-textDecoration-example-1-images" class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="DFXP textDecoration style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-textOutline" id="style-attribute-textOutline"/>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
@@ -2936,9 +2918,7 @@
</pre></div>
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-unicodeBidi-example-1-images" class="example-images"><caption>Example Rendition – Unicode Bidirectionality</caption><tbody><tr><td>
<img src="images/unicodeBidi.png" alt="DFXP unicodeBidi 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.27.6.</p></div></div><div class="div3">
+</td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-visibility" id="style-attribute-visibility"/>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
@@ -2992,9 +2972,7 @@
<img src="images/visibility_2.png" alt="DFXP visibility style property - [2,3)"/>
</td></tr><tr><td>
<img src="images/visibility_3.png" alt="DFXP visibility style property - [3,4)"/>
-</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.28.8.</p></div></div><div class="div3">
+</td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-wrapOption" id="style-attribute-wrapOption"/>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
@@ -3027,9 +3005,7 @@
A-sitting on a gate.
</p>
</pre></div>
-</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-wrapOption-example-1-images" class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="DFXP 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.15.13.</p></div></div><div class="div3">
+</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-wrapOption-example-1-images" class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="DFXP wrapOption style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-writingMode" id="style-attribute-writingMode"/>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
@@ -3079,9 +3055,7 @@
<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 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.27.7.</p></div></div><div class="div3">
+the Latin script.</p></div></div><div class="div3">
<h4><a name="style-attribute-zIndex" id="style-attribute-zIndex"/>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
@@ -3154,9 +3128,7 @@
And concluded the banquet by...
</p>
</pre></div>
-</td></tr></tbody></table><p/><p/><table summary="HTML Table" id="style-attribute-zIndex-example-1-images" class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="DFXP 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.28.9.</p></div></div></div><div class="div2">
+</td></tr></tbody></table><p/><p/><table summary="HTML Table" id="style-attribute-zIndex-example-1-images" class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="DFXP zIndex style property"/></td></tr></tbody></table></div></div><div class="div2">
<h3><a name="styling-style-value-expressions" id="styling-style-value-expressions"/>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">
<h4><a name="style-value-alpha" id="style-value-alpha"/>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><table summary="HTML Table" id="alpha-style-expression-syntax" class="syntax"><caption>Syntax Representation – <alpha></caption><tbody><tr><td>
@@ -3469,7 +3441,7 @@
layout element.</p><p>Styles are further propagated to content matter
using:
</p><ul><li><p><a href="#semantics-style-inheritance-content">content style inheritance</a></p></li><li><p><a href="#semantics-style-inheritance-content">region style inheritance</a></p></li></ul><p>For the purpose of determining inherited styles, the element hierarchy of
-an intermediate synchronic document form of a DFXP document instance must be used, where
+an intermediate synchronic document form of a TTML document instance must be used, where
such intermediate forms are defined by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate synchronic document form is utilized rather than
the original form in order to facilitate region inheritance
processing.</p></div><div class="div4">
@@ -3809,7 +3781,7 @@
flow in a region.</p></div></div></div><div class="div2">
<h3><a name="semantics-region-layout" id="semantics-region-layout"/>9.3 Region Layout and Presentation</h3><p>This section defines the semantics of region layout and
presentation in terms of a standard processing model as
-follows:</p><ul><li><p><a href="#semantics-default-region"><b>9.3.1 Default Region</b></a></p></li><li><p><a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a></p></li><li><p><a href="#semantics-region-layout-step-2"><b>9.3.3 Synchronic Flow Processing</b></a></p></li><li><p><a href="#semantics-region-layout-example"><b>9.3.4 Elaborated Example</b></a></p></li></ul><p>Any
+follows:</p><ul><li><p><a href="#semantics-default-region"><b>9.3.1 Default Region</b></a></p></li><li><p><a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a></p></li><li><p><a href="#semantics-region-layout-step-2"><b>9.3.3 Synchronic Flow Processing</b></a></p></li><li><p><a href="#semantics-region-layout-example"><b>9.3.4 Elaborated Example (Informative)</b></a></p></li></ul><p>Any
implementation is permitted provided that the externally observable
results are consistent with the results produced by this model.
</p><div class="div3">
@@ -3901,12 +3873,15 @@
<em>DOC<sub><span>inter<sub>N−1</sub></span></sub></em>.</p></div><div class="div3">
<h4><a name="semantics-region-layout-step-2" id="semantics-region-layout-step-2"/>9.3.3 Synchronic Flow Processing</h4><p>Subsequent to performing a temporal (synchronic) slice and subsequent
remapping of regionally selected content hierarchy, the resulting intermediate
- synchronic document is
-subjected to a flow transformation step that produces a rooted flow object tree
-represented as an XSL FO document instance as defined by <a href="#xsl11">[XSL 1.1]</a>,
-and semantically extended by TT AF specific style properties that have no XSL
-FO counterpart.</p><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a> is mapped to an XSL FO document instance,
-<em>F</em>, as follows:</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a content element,
+synchronic document is subjected to a flow transformation step that produces
+a rooted flow object tree
+
+equivalent to
+an XSL FO document instance as defined by <a href="#xsl11">[XSL 1.1]</a>,
+and semantically extended by TTML specific style properties that have no XSL
+FO counterpart.</p><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a> is mapped
+
+to a styled document <em>F</em> consistent with an XSL FO document instance, as follows</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a content element,
synthesize an anonymous span to enclose the text node, substituting
the new anonymous span for the original text node child in its sibling
and parent hierarchy;</p></li><li><p>for each contiguous sequence of anonymous spans, replace the
@@ -3914,26 +3889,26 @@
text nodes representing the individual text node children of the
original sequence of anonymous spans;</p></li><li><p>for each span element whose child is a single anonymous span,
replace the anonymous span with its sequence of child text
-nodes;</p></li></ol></li><li><p>resolve styles according to <a href="#semantics-style-resolution-process-overall"><b>8.4.4.4 Style Resolution Process</b></a>;</p></li><li><p>map the <code>tt</code> element to an <code>fo:root</code> element, populated
+nodes;</p></li></ol></li><li><p>resolve styles according to <a href="#semantics-style-resolution-process-overall"><b>8.4.4.4 Style Resolution Process</b></a>;</p></li><li><p>map the <code>tt</code> element to be equivalent to an <code>fo:root</code> element, populated
initially with an <code>fo:layout-master-set</code> element that contains a valid
<code>fo:simple-page-master</code> that, in turn, contains an
<code>fo:region-body</code> child, where the root container extent expressed on the
<code>tt</code> element is mapped to <code>page-width</code> and
<code>page-height</code> attributes on the <code>fo:simple-page-master</code>
-element;</p></li><li><p>map the <code>layout</code> element to an <code>fo:page-sequence</code> element and a
+element;</p></li><li><p>map the <code>layout</code> element to be equivalent to an <code>fo:page-sequence</code> element and a
child <code>fo:flow</code> element that reference the page master and page region
-defined by the simple page master produced above;</p></li><li><p>map each non-empty <code>region</code> element to an <code>fo:block-container</code>
+defined by the simple page master produced above;</p></li><li><p>map each non-empty <code>region</code> element to be equivalent to an <code>fo:block-container</code>
element with an <code>absolute-position</code> attribute with value
<code>absolute</code>, and where the region's position and extent are mapped to equivalent
<code>top</code>, <code>left</code>, <code>width</code>, and <code>height</code>
attributes;</p></li><li><p>for each <code>body</code>, <code>div</code>, and <code>p</code> element that is not
associated with a <code>tts:display</code> style property with the value
-<code>none</code>, map the element to a distinct <code>fo:block</code> element,
+<code>none</code>, map the element to the equivalent of a distinct <code>fo:block</code> element,
populating the style properties of <code>fo:block</code> by using the computed
-style set associated with each original TT AF content element;</p></li><li><p>for the resulting <code>fo:block</code> formatting object
+style set associated with each original TTML content element;</p></li><li><p>for the resulting <code>fo:block</code> formatting object equivalent
produced in the previous step that corresponds to the <code>body</code>
-element, synthesize and append to the end of its children an empty
-<code>fo:block</code> with the following attributes:
+element, map to be equivalent to appending to the end of its children an empty
+ <code>fo:block</code> with the following attributes:
<code>space-after.optimum</code>, <code>space-after.maximum</code>, and
<code>space-after.conditionality</code>, where the value of the former
two attributes is the height or width of the containing
@@ -3944,35 +3919,36 @@
<code>none</code> and for each anonymous
span that is a child of a <code>p</code> or <code>span</code> element,
map the element or
-sequence of character items to a distinct <code>fo:inline</code> element,
+sequence of character items to be equivalent to a distinct <code>fo:inline</code> element,
populating the style properties of <code>fo:inline</code> by using the computed
-style set associated with each original TT AF content element
+style set associated with each original TTML content element
or anonymous span;</p></li><li><p>for each <code>br</code> element that is not
associated with a <code>tts:display</code> style property with the value
-<code>none</code>, map the element
+<code>none</code>, map the element to be equivalent
to a distinct <code>fo:character</code> element having the following
-properties:</p><ul><li><p><code>character="&#x000A;"</code></p></li><li><p><code>suppress-at-line-break="retain"</code></p></li></ul></li><li><p>for each TT AF style property attribute in some computed
+properties:</p><ul><li><p><code>character="&#x000A;"</code></p></li><li><p><code>suppress-at-line-break="retain"</code></p></li></ul></li><li><p>for each TTML style property attribute in some computed
style set that
has no counterpart in <a href="#xsl11">[XSL 1.1]</a>, map that attribute directly through
-to the relevant formatting object produced by the input TT AF content element to
+to the relevant formatting object produced by the input TTML content element to
which the style property applies;</p></li><li><p>optionally, synthesize a unique <code>id</code> attribute on each resulting
formatting object element that relates that element to the input element that
-resulted in that formatting object element;</p></li></ol><p>For each resulting XSL FO document instance
-<em>DOC<sub>FO</sub></em>,
-if processing
-requires presentation on a visual medium, then apply the formatting semantics
-prescribed by <a href="#xsl11">[XSL 1.1]</a> in order to produce an XSL FO area tree that
-may then be subsequently rendered onto the visual medium.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In the XSL FO area tree produced by formatting
-<em>DOC<sub>FO</sub></em>, the <code>page-viewport-area</code>,
+resulted in that formatting object element;</p></li></ol><p>For each resulting document instance F, if processing requires presentation on a
+ visual medium, then apply formatting and rendering semantics consistent with that
+ prescribed by <a href="#xsl11">[XSL 1.1]</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In an XSL FO area tree produced by formatting <em>F</em> using
+an <a href="#xsl11">[XSL 1.1]</a> formatting processor,
+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, corresponds 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 TT AF style properties
-or style property values in a given DFXP document instance for which
-there is no <a href="#xsl11">[XSL 1.1]</a> counterpart, the use of a compliant <a href="#xsl11">[XSL 1.1]</a> formatting processor
-is not necessarily sufficient to satisfy the presentation
-semantics defined by this specification.</p></div></div><div class="div3">
-<h4><a name="semantics-region-layout-example" id="semantics-region-layout-example"/>9.3.4 Elaborated Example</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><table summary="HTML Table" id="region-mapping-example-1-s" class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
+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 TTML document instance 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
+ by this specification, not the requirement to use a compliant <a href="#xsl11">[XSL 1.1]</a> formatting processor,
+ since such would not necessarily be sufficient to satisfy the full presentation semantics
+ defined by this specification, and would contain a large number of features not needed to
+ implement the presentation semantics of TTML.</p></div></div><div class="div3">
+<h4><a name="semantics-region-layout-example" id="semantics-region-layout-example"/>9.3.4 Elaborated Example (Informative)</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><table summary="HTML Table" id="region-mapping-example-1-s" class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
xmlns="http://www.w3.org/ns/ttml"
xmlns:tts="http://www.w3.org/ns/ttml#styling">
@@ -4061,8 +4037,12 @@
</head>
</tt>
</pre></div>
-</td></tr></tbody></table><p>An XSL FO document instance produced by performing flow processing
-upon the first intermediate document is shown below.</p><table summary="HTML Table" id="region-mapping-example-1-f0" 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><table summary="HTML Table" id="region-mapping-example-1-f0" 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"
@@ -4213,9 +4193,7 @@
</tt>
</pre></div>
</td></tr></tbody></table></div></div><div class="div2">
-<h3><a name="semantics-line-layout" id="semantics-line-layout"/>9.4 Line Layout</h3><p>The semantics of line layout, including line breaking, defined by
-<a href="#xsl11">[XSL 1.1]</a> apply to the performance of the composition and layout of
-lines for presentation processing of a document instance on a visual medium.</p><p>If a profile that applies to a document instance
+<h3><a name="semantics-line-layout" id="semantics-line-layout"/>9.4 Line Layout</h3><p>If a profile that applies to a document instance
requires use of the <a href="#feature-lineBreak-uax14">#lineBreak-uax14</a> feature
(i.e., the value attribute for the feature is specified as <code>use</code>), then
the recommendations defined by <a href="http://www.unicode.org/unicode/reports/tr14/#Algorithm">Line
@@ -4256,7 +4234,7 @@
the value of a <code>dur</code> attribute must adhere to a
<timeExpression> specification as defined by <a href="#timing-value-timeExpression"><b>10.3.1 <timeExpression></b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When the <code>clock-time</code> form of a <timeExpression> specification
is used with a <code>dur</code> attribute, it is intended to be interpreted as
-a difference between two implied clock time expressions.</p></div><p>When a TT AF document instance specifies the use of the
+a difference between two implied clock time expressions.</p></div><p>When a TTML document instance specifies the use of the
<code>smpte</code> time base and <code>discontinuous</code> marker
mode, the <code>dur</code> attribute must not be specified on any
element.</p><p>The semantics of the <code>dur</code> attribute are those defined
@@ -4460,7 +4438,7 @@
represented by metadata takes one of two forms: (1) metadata defined by this
specification for standardized use in a document instance, and (2) arbitrary
metadata defined outside of the scope of this specification, whose use and
-semantics depend entirely upon an application's use of TT AF content.</p><div class="div2">
+semantics depend entirely upon an application's use of TTML content.</p><div class="div2">
<h3><a name="metadata-element-vocabulary" id="metadata-element-vocabulary"/>12.1 Metadata Element Vocabulary</h3><p>The <a href="#metadata-vocabulary-metadata"><b>12.1.1 metadata</b></a> element serves as
a generic container element for grouping metadata information.</p><p>In addition, the following elements, all defined in the TT Metadata Namespace,
provide standard representations for common metadata that is expected to be commonly
@@ -6825,11 +6803,11 @@
<a href="http://www.w3.org/2002/06/registering-mediatype.html">W3CRegMedia</a>.
The information in this appendix is being submitted to the Internet
Engineering Steering Group (IESG) for review, approval, and
-registration with the Internet Assigned Numbers Authority (IANA).</p><dl><dt class="label">MIME media type name:</dt><dd><p>application</p></dd><dt class="label">MIME subtype name:</dt><dd><p>ttml+xml</p></dd><dt class="label">Required parameters:</dt><dd><p>None.</p></dd><dt class="label">Optional parameters:</dt><dd><p>The encoding of a TT AF document must be determined by the XML
+registration with the Internet Assigned Numbers Authority (IANA).</p><dl><dt class="label">MIME media type name:</dt><dd><p>application</p></dd><dt class="label">MIME subtype name:</dt><dd><p>ttml+xml</p></dd><dt class="label">Required parameters:</dt><dd><p>None.</p></dd><dt class="label">Optional parameters:</dt><dd><p>The encoding of a TTML document must be determined by the XML
encoding declaration. This has identical semantics to the
application/xml media type in the case where the charset parameter is
omitted, as specified in <a href="#xml-media">[XML Media]</a>, Sections 8.9,
-8.10 and 8.11.</p><p>The document profile of a TT AF document may be specified using
+8.10 and 8.11.</p><p>The document profile of a TTML document may be specified using
an optional <code>profile</code> parameter, which, if specified,
the value of which must adhere to the syntax and semantics of
<code>ttp:profile</code> parameter defined by
@@ -6840,19 +6818,19 @@
<a href="#xml-media">[XML Media]</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 TT AF and of XML
+processors in constrained environments to fail.</p><p>In addition, because of the extensibility features for TTML and of XML
in general, it is possible that "application/ttml+xml" may describe content
that has security implications beyond those described here. However,
if the processor follows only the normative semantics of the published
-specification, this content will be outside TT AF namespaces and
+specification, this content will be outside TTML namespaces and
may be ignored. Only in the case where the processor recognizes and
processes the additional content, or where further processing of that
content is dispatched to other processors, would security issues
potentially arise. And in that case, they would fall outside the
domain of this registration document.</p></dd><dt class="label">Interoperability considerations:</dt><dd><p>The published specification describes processing semantics that dictate
behavior that must be followed when dealing with, among other things,
-unrecognized elements and attributes, both in TT AF namespaces and in
-other namespaces.</p><p>Because TT AF is extensible, conformant "application/ttml+xml" processors must
+unrecognized elements and attributes, both in TTML namespaces and in
+other namespaces.</p><p>Because TTML is extensible, conformant "application/ttml+xml" processors must
expect that content received is well-formed XML, but it cannot be
guaranteed that the content is valid to a particular DTD or Schema or
that the processor will recognize all of the elements and attributes
@@ -6881,26 +6859,26 @@
for future standardization.</p><p>The following sub-sections define all feature designations, expressed
as relative URIs (fragment identifiers) with respect to the
TT Feature Namespace base URI.</p><div class="div3">
-<h4><a name="feature-animation" id="feature-animation"/>D.1.1 #animation</h4><p>A TT AF transformation processor supports the <code>#animation</code>
+<h4><a name="feature-animation" id="feature-animation"/>D.1.1 #animation</h4><p>A TTML transformation processor supports the <code>#animation</code>
feature if it recognizes and is capable of transforming the following
-vocabulary defined by <a href="#animation"><b>11 Animation</b></a>:</p><ul><li><p><a href="#animation-vocabulary-set"><code>set</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#animation</code>
+vocabulary defined by <a href="#animation"><b>11 Animation</b></a>:</p><ul><li><p><a href="#animation-vocabulary-set"><code>set</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#animation</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor" id="feature-backgroundColor"/>D.1.2 #backgroundColor</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-backgroundColor" id="feature-backgroundColor"/>D.1.2 #backgroundColor</h4><p>A TTML transformation processor supports the
<code>#backgroundColor</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#backgroundColor</code> feature if it (1) implements presentation semantic support
for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute
and (2) is capable of displaying or generating an output display
signal that distinguishes between at least sixteen (16) values of color,
including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor-block" id="feature-backgroundColor-block"/>D.1.3 #backgroundColor-block</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-backgroundColor-block" id="feature-backgroundColor-block"/>D.1.3 #backgroundColor-block</h4><p>A TTML transformation processor supports the
<code>#backgroundColor-block</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that would generate a
-block area during presentation processing.</p><p>A TT AF presentation processor supports the
+block area during presentation processing.</p><p>A TTML presentation processor supports the
<code>#backgroundColor-block</code> feature if it (1) implements presentation semantic
support for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that generates a
@@ -6908,11 +6886,11 @@
and (2) is capable of displaying or generating an output display
signal that distinguishes between at least sixteen (16) values of color,
including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor-inline" id="feature-backgroundColor-inline"/>D.1.4 #backgroundColor-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-backgroundColor-inline" id="feature-backgroundColor-inline"/>D.1.4 #backgroundColor-inline</h4><p>A TTML transformation processor supports the
<code>#backgroundColor-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that would generate an
-inline area during presentation processing.</p><p>A TT AF presentation processor supports the
+inline area during presentation processing.</p><p>A TTML presentation processor supports the
<code>#backgroundColor-inline</code> feature if it (1) implements presentation semantic
support for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that generates an
@@ -6920,10 +6898,10 @@
and (2) is capable of displaying or generating an output display
signal that distinguishes between at least sixteen (16) values of color,
including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor-region" id="feature-backgroundColor-region"/>D.1.5 #backgroundColor-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-backgroundColor-region" id="feature-backgroundColor-region"/>D.1.5 #backgroundColor-region</h4><p>A TTML transformation processor supports the
<code>#backgroundColor-region</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
-attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TT AF presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
<code>#backgroundColor-region</code> feature if it (1) implements presentation semantic
support for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element
@@ -6931,454 +6909,454 @@
signal that distinguishes between at least sixteen (16) values of color,
including all primary and secondary colors of the SRGB color space
.</p></div><div class="div3">
-<h4><a name="feature-bidi" id="feature-bidi"/>D.1.6 #bidi</h4><p>A TT AF processor supports the <code>#bidi</code> feature if it
+<h4><a name="feature-bidi" id="feature-bidi"/>D.1.6 #bidi</h4><p>A TTML processor supports the <code>#bidi</code> feature if it
supports the following features:</p><ul><li><p><a href="#feature-direction"><code>#direction</code></a></p></li><li><p><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></p></li><li><p><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></p></li></ul></div><div class="div3">
-<h4><a name="feature-cellResolution" id="feature-cellResolution"/>D.1.7 #cellResolution</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-cellResolution" id="feature-cellResolution"/>D.1.7 #cellResolution</h4><p>A TTML transformation processor supports the
<code>#cellResolution</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#cellResolution</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode" id="feature-clockMode"/>D.1.8 #clockMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-clockMode" id="feature-clockMode"/>D.1.8 #clockMode</h4><p>A TTML transformation processor supports the
<code>#clockMode</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#clockMode</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode-gps" id="feature-clockMode-gps"/>D.1.9 #clockMode-gps</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-clockMode-gps" id="feature-clockMode-gps"/>D.1.9 #clockMode-gps</h4><p>A TTML transformation processor supports the
<code>#clockMode-gps</code> feature if it recognizes and is capable of
transforming the <code>gps</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#clockMode-gps</code> feature if it implements presentation semantic support
for the <code>gps</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode-local" id="feature-clockMode-local"/>D.1.10 #clockMode-local</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-clockMode-local" id="feature-clockMode-local"/>D.1.10 #clockMode-local</h4><p>A TTML transformation processor supports the
<code>#clockMode-local</code> feature if it recognizes and is capable of
transforming the <code>local</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#clockMode-local</code> feature if it implements presentation semantic support
for the <code>local</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode-utc" id="feature-clockMode-utc"/>D.1.11 #clockMode-utc</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-clockMode-utc" id="feature-clockMode-utc"/>D.1.11 #clockMode-utc</h4><p>A TTML transformation processor supports the
<code>#clockMode-utc</code> feature if it recognizes and is capable of
transforming the <code>utc</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#clockMode-utc</code> feature if it implements presentation semantic support
for the <code>utc</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-color" id="feature-color"/>D.1.12 #color</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-color" id="feature-color"/>D.1.12 #color</h4><p>A TTML transformation processor supports the
<code>#color</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-color"><code>tts:color</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#color</code> feature if it (1) implements presentation semantic support
for the <a href="#style-attribute-color"><code>tts:color</code></a>
attribute
and (2) is capable of displaying or generating an output display
signal that distinguishes between at least sixteen (16) values of color,
including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-content" id="feature-content"/>D.1.13 #content</h4><p>A TT AF transformation processor supports the <code>#content</code>
+<h4><a name="feature-content" id="feature-content"/>D.1.13 #content</h4><p>A TTML transformation processor supports the <code>#content</code>
feature if it recognizes and is capable of transforming the following
-vocabulary defined by <a href="#content"><b>7 Content</b></a>:</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="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#content-vocabulary-br"><code>br</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#content</code>
+vocabulary defined by <a href="#content"><b>7 Content</b></a>:</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="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#content-vocabulary-br"><code>br</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#content</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-core" id="feature-core"/>D.1.14 #core</h4><p>A TT AF transformation processor supports the <code>#core</code>
+<h4><a name="feature-core" id="feature-core"/>D.1.14 #core</h4><p>A TTML transformation processor supports the <code>#core</code>
feature if it recognizes and is capable of transforming the following
-core attributes vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#content-attribute-id">@<code>xml:id</code></a></p></li><li><p><a href="#content-attribute-id">@<code>xml:lang</code></a></p></li><li><p><a href="#content-attribute-id">@<code>xml:space</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#core</code>
+core attributes vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#content-attribute-id">@<code>xml:id</code></a></p></li><li><p><a href="#content-attribute-id">@<code>xml:lang</code></a></p></li><li><p><a href="#content-attribute-id">@<code>xml:space</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#core</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-direction" id="feature-direction"/>D.1.15 #direction</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-direction" id="feature-direction"/>D.1.15 #direction</h4><p>A TTML transformation processor supports the
<code>#direction</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-direction"><code>tts:direction</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#direction</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-direction"><code>tts:direction</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-display" id="feature-display"/>D.1.16 #display</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-display" id="feature-display"/>D.1.16 #display</h4><p>A TTML transformation processor supports the
<code>#display</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#display</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-display-block" id="feature-display-block"/>D.1.17 #display-block</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-display-block" id="feature-display-block"/>D.1.17 #display-block</h4><p>A TTML transformation processor supports the
<code>#display-block</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
attribute when applied to a content element that would generate a
-block area during presentation processing.</p><p>A TT AF presentation processor supports the
+block area during presentation processing.</p><p>A TTML presentation processor supports the
<code>#display-block</code> feature if it implements presentation semantic
support for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
attribute when applied to a content element that generates a
block area.</p></div><div class="div3">
-<h4><a name="feature-display-inline" id="feature-display-inline"/>D.1.18 #display-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-display-inline" id="feature-display-inline"/>D.1.18 #display-inline</h4><p>A TTML transformation processor supports the
<code>#display-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
attribute when applied to a content element that would generate an
-inline area during presentation processing.</p><p>A TT AF presentation processor supports the
+inline area during presentation processing.</p><p>A TTML presentation processor supports the
<code>#display-inline</code> feature if it implements presentation semantic
support for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
attribute when applied to a content element that generates an
inline area.</p></div><div class="div3">
-<h4><a name="feature-display-region" id="feature-display-region"/>D.1.19 #display-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-display-region" id="feature-display-region"/>D.1.19 #display-region</h4><p>A TTML transformation processor supports the
<code>#display-region</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
-attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TT AF presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
<code>#display-region</code> feature if it implements presentation semantic
support for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-displayAlign" id="feature-displayAlign"/>D.1.20 #displayAlign</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-displayAlign" id="feature-displayAlign"/>D.1.20 #displayAlign</h4><p>A TTML transformation processor supports the
<code>#displayAlign</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#displayAlign</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode" id="feature-dropMode"/>D.1.21 #dropMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dropMode" id="feature-dropMode"/>D.1.21 #dropMode</h4><p>A TTML transformation processor supports the
<code>#dropMode</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#dropMode</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode-dropNTSC" id="feature-dropMode-dropNTSC"/>D.1.22 #dropMode-dropNTSC</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dropMode-dropNTSC" id="feature-dropMode-dropNTSC"/>D.1.22 #dropMode-dropNTSC</h4><p>A TTML transformation processor supports the
<code>#dropMode-dropNTSC</code> feature if it recognizes and is capable of
transforming the <code>dropNTSC</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#dropMode-dropNTSC</code> feature if it implements presentation semantic support
for the <code>dropNTSC</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode-dropPAL" id="feature-dropMode-dropPAL"/>D.1.23 #dropMode-dropPAL</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dropMode-dropPAL" id="feature-dropMode-dropPAL"/>D.1.23 #dropMode-dropPAL</h4><p>A TTML transformation processor supports the
<code>#dropMode-dropPAL</code> feature if it recognizes and is capable of
transforming the <code>dropPAL</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#dropMode-dropPAL</code> feature if it implements presentation semantic support
for the <code>dropPAL</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode-nonDrop" id="feature-dropMode-nonDrop"/>D.1.24 #dropMode-nonDrop</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dropMode-nonDrop" id="feature-dropMode-nonDrop"/>D.1.24 #dropMode-nonDrop</h4><p>A TTML transformation processor supports the
<code>#dropMode-nonDrop</code> feature if it recognizes and is capable of
transforming the <code>nonDrop</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#dropMode-nonDrop</code> feature if it implements presentation semantic support
for the <code>nonDrop</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-extent" id="feature-extent"/>D.1.25 #extent</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-extent" id="feature-extent"/>D.1.25 #extent</h4><p>A TTML transformation processor supports the
<code>#extent</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-extent"><code>tts:extent</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#extent</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-extent"><code>tts:extent</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-extent-region" id="feature-extent-region"/>D.1.26 #extent-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-extent-region" id="feature-extent-region"/>D.1.26 #extent-region</h4><p>A TTML transformation processor supports the
<code>#extent-region</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-extent"><code>tts:extent</code></a>
-attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TT AF presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
<code>#extent-region</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-extent"><code>tts:extent</code></a>
attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-extent-root" id="feature-extent-root"/>D.1.27 #extent-root</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-extent-root" id="feature-extent-root"/>D.1.27 #extent-root</h4><p>A TTML transformation processor supports the
<code>#extent-root</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-extent"><code>tts:extent</code></a>
-attribute when applied to the <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element.</p><p>A TT AF presentation processor supports the
+attribute when applied to the <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element.</p><p>A TTML presentation processor supports the
<code>#extent-root</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-extent"><code>tts:extent</code></a>
attribute when applied to a <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-fontFamily" id="feature-fontFamily"/>D.1.28 #fontFamily</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily" id="feature-fontFamily"/>D.1.28 #fontFamily</h4><p>A TTML transformation processor supports the
<code>#fontFamily</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontFamily</code> feature if it implements presentation semantic support
for the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontFamily-generic" id="feature-fontFamily-generic"/>D.1.29 #fontFamily-generic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily-generic" id="feature-fontFamily-generic"/>D.1.29 #fontFamily-generic</h4><p>A TTML transformation processor supports the
<code>#fontFamily-generic</code> feature if it recognizes and is
capable of transforming <a href="#style-value-genericFamilyName"><genericFamilyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontFamily-generic</code> feature if it implements presentation semantic
support for <a href="#style-value-genericFamilyName"><genericFamilyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontFamily-non-generic" id="feature-fontFamily-non-generic"/>D.1.30 #fontFamily-non-generic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily-non-generic" id="feature-fontFamily-non-generic"/>D.1.30 #fontFamily-non-generic</h4><p>A TTML transformation processor supports the
<code>#fontFamily-non-generic</code> feature if it recognizes and is
capable of transforming <a href="#style-value-familyName"><familyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontFamily-non-generic</code> feature if it implements presentation semantic
support for <a href="#style-value-familyName"><familyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontSize" id="feature-fontSize"/>D.1.31 #fontSize</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize" id="feature-fontSize"/>D.1.31 #fontSize</h4><p>A TTML transformation processor supports the
<code>#fontSize</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontSize</code> feature if it implements presentation semantic support
for the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontSize-anamorphic" id="feature-fontSize-anamorphic"/>D.1.32 #fontSize-anamorphic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize-anamorphic" id="feature-fontSize-anamorphic"/>D.1.32 #fontSize-anamorphic</h4><p>A TTML transformation processor supports the
<code>#fontSize-anamorphic</code> feature if it recognizes and is
capable of transforming values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
-attribute that consist of two <a href="#style-value-length"><length></a> specifications.</p><p>A TT AF presentation processor supports the
+attribute that consist of two <a href="#style-value-length"><length></a> specifications.</p><p>A TTML presentation processor supports the
<code>#fontSize-anamorphic</code> feature if it implements presentation semantic
support for defined values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute that consist of two <a href="#style-value-length"><length></a> specifications.</p></div><div class="div3">
-<h4><a name="feature-fontSize-isomorphic" id="feature-fontSize-isomorphic"/>D.1.33 #fontSize-isomorphic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize-isomorphic" id="feature-fontSize-isomorphic"/>D.1.33 #fontSize-isomorphic</h4><p>A TTML transformation processor supports the
<code>#fontSize-isomorphic</code> feature if it recognizes and is
capable of transforming values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
-attribute that consist of a single <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the
+attribute that consist of a single <a href="#style-value-length"><length></a> specification.</p><p>A TTML presentation processor supports the
<code>#fontSize-isomorphic</code> feature if it implements presentation semantic
support for defined values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute that consist of a single <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-fontStyle" id="feature-fontStyle"/>D.1.34 #fontStyle</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle" id="feature-fontStyle"/>D.1.34 #fontStyle</h4><p>A TTML transformation processor supports the
<code>#fontStyle</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontStyle</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontStyle-italic" id="feature-fontStyle-italic"/>D.1.35 #fontStyle-italic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle-italic" id="feature-fontStyle-italic"/>D.1.35 #fontStyle-italic</h4><p>A TTML transformation processor supports the
<code>#fontStyle-italic</code> feature if it recognizes and is
capable of transforming the <code>italic</code> value of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontStyle-italic</code> feature if it implements presentation semantic
support for the <code>italic</code> of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontStyle-oblique" id="feature-fontStyle-oblique"/>D.1.36 #fontStyle-oblique</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle-oblique" id="feature-fontStyle-oblique"/>D.1.36 #fontStyle-oblique</h4><p>A TTML transformation processor supports the
<code>#fontStyle-oblique</code> feature if it recognizes and is
capable of transforming the <code>oblique</code> value of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontStyle-oblique</code> feature if it implements presentation semantic
support for the <code>oblique</code> of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontStyle-reverseOblique" id="feature-fontStyle-reverseOblique"/>D.1.37 #fontStyle-reverseOblique</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle-reverseOblique" id="feature-fontStyle-reverseOblique"/>D.1.37 #fontStyle-reverseOblique</h4><p>A TTML transformation processor supports the
<code>#fontStyle-reverseOblique</code> feature if it recognizes and is
capable of transforming the <code>reverseOblique</code> value of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontStyle-reverseOblique</code> feature if it implements presentation semantic
support for the <code>reverseOblique</code> of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontWeight" id="feature-fontWeight"/>D.1.38 #fontWeight</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontWeight" id="feature-fontWeight"/>D.1.38 #fontWeight</h4><p>A TTML transformation processor supports the
<code>#fontWeight</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontWeight</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontWeight-bold" id="feature-fontWeight-bold"/>D.1.39 #fontWeight-bold</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontWeight-bold" id="feature-fontWeight-bold"/>D.1.39 #fontWeight-bold</h4><p>A TTML transformation processor supports the
<code>#fontWeight-bold</code> feature if it recognizes and is
capable of transforming <code>bold</code> value of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#fontWeight-bold</code> feature if it implements presentation semantic
support for the <code>bold</code> of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-frameRate" id="feature-frameRate"/>D.1.40 #frameRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-frameRate" id="feature-frameRate"/>D.1.40 #frameRate</h4><p>A TTML transformation processor supports the
<code>#frameRate</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#frameRate</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-frameRateMultiplier" id="feature-frameRateMultiplier"/>D.1.41 #frameRateMultiplier</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-frameRateMultiplier" id="feature-frameRateMultiplier"/>D.1.41 #frameRateMultiplier</h4><p>A TTML transformation processor supports the
<code>#frameRateMultiplier</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#frameRateMultiplier</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-layout" id="feature-layout"/>D.1.42 #layout</h4><p>A TT AF transformation processor supports the <code>#layout</code>
+<h4><a name="feature-layout" id="feature-layout"/>D.1.42 #layout</h4><p>A TTML transformation processor supports the <code>#layout</code>
feature if it (1) recognizes and is capable of transforming the following
vocabulary defined by <a href="#layout"><b>9 Layout</b></a>:</p><ul><li><p><a href="#layout-vocabulary-layout"><code>layout</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#layout-attribute-region">@<code>region</code></a></p></li></ul><p>and (2) supports the following attributes when applied to the
-<a href="#layout-vocabulary-region"><code>region</code></a> element:</p><ul><li><p><a href="#style-attribute-extent"><code>tts:extent</code></a></p></li><li><p><a href="#style-attribute-origin"><code>tts:origin</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#layout</code>
+<a href="#layout-vocabulary-region"><code>region</code></a> element:</p><ul><li><p><a href="#style-attribute-extent"><code>tts:extent</code></a></p></li><li><p><a href="#style-attribute-origin"><code>tts:origin</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#layout</code>
feature if it implements presentation semantic support for the
same vocabulary and features enumerated above.</p></div><div class="div3">
-<h4><a name="feature-length" id="feature-length"/>D.1.43 #length</h4><p>A TT AF transformation processor supports the <code>#length</code>
+<h4><a name="feature-length" id="feature-length"/>D.1.43 #length</h4><p>A TTML transformation processor supports the <code>#length</code>
feature if it recognizes and is capable of transforming all defined
values of the <a href="#style-value-length"><length></a>
-style value expression.</p><p>A TT AF presentation processor supports the <code>#length</code>
+style value expression.</p><p>A TTML presentation processor supports the <code>#length</code>
feature if it implements presentation semantic support for all defined values of
the <a href="#style-value-length"><length></a> style value
expression.</p></div><div class="div3">
-<h4><a name="feature-length-cell" id="feature-length-cell"/>D.1.44 #length-cell</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-cell" id="feature-length-cell"/>D.1.44 #length-cell</h4><p>A TTML transformation processor supports the
<code>#length-cell</code> feature if it recognizes and is capable of
transforming scalar values of the <a href="#style-value-length"><length></a> style value expression
-that use <code>c</code> (cell) units.</p><p>A TT AF presentation processor supports the
+that use <code>c</code> (cell) units.</p><p>A TTML presentation processor supports the
<code>#length-cell</code> feature if it implements presentation semantic support
for scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>c</code> (cell) units.</p></div><div class="div3">
-<h4><a name="feature-length-em" id="feature-length-em"/>D.1.45 #length-em</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-em" id="feature-length-em"/>D.1.45 #length-em</h4><p>A TTML transformation processor supports the
<code>#length-em</code> feature if it recognizes and is capable of
transforming scalar values of the <a href="#style-value-length"><length></a> style value expression
-that use <code>em</code> (EM) units.</p><p>A TT AF presentation processor supports the
+that use <code>em</code> (EM) units.</p><p>A TTML presentation processor supports the
<code>#length-em</code> feature if it implements presentation semantic support
for scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>em</code> (EM) units.</p></div><div class="div3">
-<h4><a name="feature-length-integer" id="feature-length-integer"/>D.1.46 #length-integer</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-integer" id="feature-length-integer"/>D.1.46 #length-integer</h4><p>A TTML transformation processor supports the
<code>#length-integer</code> feature if it recognizes and is
capable of transforming integer values of the <a href="#style-value-length"><length></a> style value
-expression.</p><p>A TT AF presentation processor supports the
+expression.</p><p>A TTML presentation processor supports the
<code>#length-integer</code> feature if it implements presentation semantic
support for integer values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-negative" id="feature-length-negative"/>D.1.47 #length-negative</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-negative" id="feature-length-negative"/>D.1.47 #length-negative</h4><p>A TTML transformation processor supports the
<code>#length-negative</code> feature if it recognizes and is
capable of transforming negative values of the <a href="#style-value-length"><length></a> style value
-expression.</p><p>A TT AF presentation processor supports the
+expression.</p><p>A TTML presentation processor supports the
<code>#length-negative</code> feature if it implements presentation semantic
support for negative values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-percentage" id="feature-length-percentage"/>D.1.48 #length-percentage</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-percentage" id="feature-length-percentage"/>D.1.48 #length-percentage</h4><p>A TTML transformation processor supports the
<code>#length-percentage</code> feature if it recognizes and is
capable of transforming percentage values of the <a href="#style-value-length"><length></a> style value
-expression.</p><p>A TT AF presentation processor supports the
+expression.</p><p>A TTML presentation processor supports the
<code>#length-percentage</code> feature if it implements presentation semantic
support for percentage values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-pixel" id="feature-length-pixel"/>D.1.49 #length-pixel</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-pixel" id="feature-length-pixel"/>D.1.49 #length-pixel</h4><p>A TTML transformation processor supports the
<code>#length-pixel</code> feature if it recognizes and is capable of
transforming scalar values of the <a href="#style-value-length"><length></a> style value expression
-that use <code>px</code> (pixel) units.</p><p>A TT AF presentation processor supports the
+that use <code>px</code> (pixel) units.</p><p>A TTML presentation processor supports the
<code>#length-pixel</code> feature if it implements presentation semantic support
for scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>px</code> (pixel) units.</p></div><div class="div3">
-<h4><a name="feature-length-positive" id="feature-length-positive"/>D.1.50 #length-positive</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-positive" id="feature-length-positive"/>D.1.50 #length-positive</h4><p>A TTML transformation processor supports the
<code>#length-positive</code> feature if it recognizes and is
capable of transforming positive values of the <a href="#style-value-length"><length></a> style value
-expression.</p><p>A TT AF presentation processor supports the
+expression.</p><p>A TTML presentation processor supports the
<code>#length-positive</code> feature if it implements presentation semantic
support for positive values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-real" id="feature-length-real"/>D.1.51 #length-real</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-real" id="feature-length-real"/>D.1.51 #length-real</h4><p>A TTML transformation processor supports the
<code>#length-real</code> feature if it recognizes and is
capable of transforming real values of the <a href="#style-value-length"><length></a> style value
-expression.</p><p>A TT AF presentation processor supports the
+expression.</p><p>A TTML presentation processor supports the
<code>#length-real</code> feature if it implements presentation semantic
support for real values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-lineBreak-uax14" id="feature-lineBreak-uax14"/>D.1.52 #lineBreak-uax14</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-lineBreak-uax14" id="feature-lineBreak-uax14"/>D.1.52 #lineBreak-uax14</h4><p>A TTML transformation processor supports the
<code>#lineBreak-uax14</code> feature if it recognizes and is capable of
transforming requirements expressed by <a href="#uax14">[UAX14]</a> into its
-target document space.</p><p>A TT AF presentation processor supports the
+target document space.</p><p>A TTML presentation processor supports the
<code>#lineBreak-uax14</code> feature if it implements presentation semantic support
for <a href="#uax14">[UAX14]</a> as applies to line breaking.</p></div><div class="div3">
-<h4><a name="feature-lineHeight" id="feature-lineHeight"/>D.1.53 #lineHeight</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-lineHeight" id="feature-lineHeight"/>D.1.53 #lineHeight</h4><p>A TTML transformation processor supports the
<code>#lineHeight</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#lineHeight</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-markerMode" id="feature-markerMode"/>D.1.54 #markerMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-markerMode" id="feature-markerMode"/>D.1.54 #markerMode</h4><p>A TTML transformation processor supports the
<code>#markerMode</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#markerMode</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-markerMode-continuous" id="feature-markerMode-continuous"/>D.1.55 #markerMode-continuous</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-markerMode-continuous" id="feature-markerMode-continuous"/>D.1.55 #markerMode-continuous</h4><p>A TTML transformation processor supports the
<code>#markerMode-continuous</code> feature if it recognizes and is capable of
transforming the <code>continuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#markerMode-continuous</code> feature if it implements presentation semantic support
for the <code>continuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-markerMode-discontinuous" id="feature-markerMode-discontinuous"/>D.1.56 #markerMode-discontinuous</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-markerMode-discontinuous" id="feature-markerMode-discontinuous"/>D.1.56 #markerMode-discontinuous</h4><p>A TTML transformation processor supports the
<code>#markerMode-discontinuous</code> feature if it recognizes and is capable of
transforming the <code>discontinuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#markerMode-discontinuous</code> feature if it implements presentation semantic support
for the <code>discontinuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-metadata" id="feature-metadata"/>D.1.57 #metadata</h4><p>A TT AF transformation processor supports the <code>#metadata</code>
+<h4><a name="feature-metadata" id="feature-metadata"/>D.1.57 #metadata</h4><p>A TTML transformation processor supports the <code>#metadata</code>
feature if it recognizes and is capable of transforming the following
-vocabulary defined by <a href="#metadata"><b>12 Metadata</b></a>:</p><ul><li><p><a href="#metadata-vocabulary-metadata"><code>metadata</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:title</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:desc</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:copyright</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:agent</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:name</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:actor</code></a></p></li><li><p><a href="#metadata-attribute-agent">@<code>ttm:agent</code></a></p></li><li><p><a href="#metadata-attribute-role">@<code>ttm:role</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#metadata</code>
+vocabulary defined by <a href="#metadata"><b>12 Metadata</b></a>:</p><ul><li><p><a href="#metadata-vocabulary-metadata"><code>metadata</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:title</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:desc</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:copyright</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:agent</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:name</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:actor</code></a></p></li><li><p><a href="#metadata-attribute-agent">@<code>ttm:agent</code></a></p></li><li><p><a href="#metadata-attribute-role">@<code>ttm:role</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#metadata</code>
feature if it recognizes and is capable of presenting the information
expressed by the same vocabulary enumerated above.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not define a standardized form for the
presentation of metadata information. The presentation or ability to
present metadata information is considered to be implementation
dependent.</p></div></div><div class="div3">
-<h4><a name="feature-nested-div" id="feature-nested-div"/>D.1.58 #nested-div</h4><p>A TT AF transformation processor supports the <code>#nested-div</code>
+<h4><a name="feature-nested-div" id="feature-nested-div"/>D.1.58 #nested-div</h4><p>A TTML transformation processor supports the <code>#nested-div</code>
feature if it recognizes and is capable of transforming nested
-<a href="#content-vocabulary-div"><code>div</code></a> elements.</p><p>A TT AF presentation processor supports the <code>#nested-div</code>
+<a href="#content-vocabulary-div"><code>div</code></a> elements.</p><p>A TTML presentation processor supports the <code>#nested-div</code>
feature if it implements presentation semantic support for nested
<a href="#content-vocabulary-div"><code>div</code></a> elements.</p></div><div class="div3">
-<h4><a name="feature-nested-span" id="feature-nested-span"/>D.1.59 #nested-span</h4><p>A TT AF transformation processor supports the <code>#nested-span</code>
+<h4><a name="feature-nested-span" id="feature-nested-span"/>D.1.59 #nested-span</h4><p>A TTML transformation processor supports the <code>#nested-span</code>
feature if it recognizes and is capable of transforming nested
-<a href="#content-vocabulary-span"><code>span</code></a> elements.</p><p>A TT AF presentation processor supports the <code>#nested-span</code>
+<a href="#content-vocabulary-span"><code>span</code></a> elements.</p><p>A TTML presentation processor supports the <code>#nested-span</code>
feature if it implements presentation semantic support for nested
<a href="#content-vocabulary-span"><code>span</code></a> elements.</p></div><div class="div3">
-<h4><a name="feature-opacity" id="feature-opacity"/>D.1.60 #opacity</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-opacity" id="feature-opacity"/>D.1.60 #opacity</h4><p>A TTML transformation processor supports the
<code>#opacity</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-opacity"><code>tts:opacity</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#opacity</code> feature if it (1) implements presentation semantic support for
the <a href="#style-attribute-opacity"><code>tts:opacity</code></a>
attribute and (2) is capable of displaying or generating an output display
signal that distinguishes between at least eight (8) values of opacity.</p></div><div class="div3">
-<h4><a name="feature-origin" id="feature-origin"/>D.1.61 #origin</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-origin" id="feature-origin"/>D.1.61 #origin</h4><p>A TTML transformation processor supports the
<code>#origin</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-origin"><code>tts:origin</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#origin</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-origin"><code>tts:origin</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-overflow" id="feature-overflow"/>D.1.62 #overflow</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-overflow" id="feature-overflow"/>D.1.62 #overflow</h4><p>A TTML transformation processor supports the
<code>#overflow</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#overflow</code> feature if it implements presentation semantic support for
all defined values of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-overflow-visible" id="feature-overflow-visible"/>D.1.63 #overflow-visible</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-overflow-visible" id="feature-overflow-visible"/>D.1.63 #overflow-visible</h4><p>A TTML transformation processor supports the
<code>#overflow-visible</code> feature if it recognizes and is capable of
transforming the <code>visible</code> value of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#overflow-visible</code> feature if it implements presentation semantic support for
the <code>visible</code> value of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-padding" id="feature-padding"/>D.1.64 #padding</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding" id="feature-padding"/>D.1.64 #padding</h4><p>A TTML transformation processor supports the
<code>#padding</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-padding"><code>tts:padding</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#padding</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-padding"><code>tts:padding</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-padding-1" id="feature-padding-1"/>D.1.65 #padding-1</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-1" id="feature-padding-1"/>D.1.65 #padding-1</h4><p>A TTML transformation processor supports the
<code>#padding-1</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
-that consist of one <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-1</code>
+that consist of one <a href="#style-value-length"><length></a> specification.</p><p>A TTML presentation processor supports the <code>#padding-1</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of one <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-2" id="feature-padding-2"/>D.1.66 #padding-2</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-2" id="feature-padding-2"/>D.1.66 #padding-2</h4><p>A TTML transformation processor supports the
<code>#padding-2</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
-that consist of two <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-2</code>
+that consist of two <a href="#style-value-length"><length></a> specification.</p><p>A TTML presentation processor supports the <code>#padding-2</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of two <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-3" id="feature-padding-3"/>D.1.67 #padding-3</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-3" id="feature-padding-3"/>D.1.67 #padding-3</h4><p>A TTML transformation processor supports the
<code>#padding-3</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
-that consist of three <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-3</code>
+that consist of three <a href="#style-value-length"><length></a> specification.</p><p>A TTML presentation processor supports the <code>#padding-3</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of three <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-4" id="feature-padding-4"/>D.1.68 #padding-4</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-4" id="feature-padding-4"/>D.1.68 #padding-4</h4><p>A TTML transformation processor supports the
<code>#padding-4</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
-that consist of four <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-4</code>
+that consist of four <a href="#style-value-length"><length></a> specification.</p><p>A TTML presentation processor supports the <code>#padding-4</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of four <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-pixelAspectRatio" id="feature-pixelAspectRatio"/>D.1.69 #pixelAspectRatio</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-pixelAspectRatio" id="feature-pixelAspectRatio"/>D.1.69 #pixelAspectRatio</h4><p>A TTML transformation processor supports the
<code>#pixelAspectRatio</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#pixelAspectRatio</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-presentation" id="feature-presentation"/>D.1.70 #presentation</h4><p>A TT AF processor supports the
+<h4><a name="feature-presentation" id="feature-presentation"/>D.1.70 #presentation</h4><p>A TTML processor supports the
<code>#presentation</code> feature if it
(1) satisfies the generic processor criteria defined by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>,
@@ -7386,198 +7364,198 @@
semantics defined by <a href="#semantics-region-layout"><b>9.3 Region Layout and Presentation</b></a> and
<a href="#semantics-line-layout"><b>9.4 Line Layout</b></a>, respectively, and
(3) implements presentation semantics for the following features:</p><ul><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#feature-core"><code>#core</code></a></p></li><li><p><a href="#feature-profile"><code>#profile</code></a></p></li><li><p><a href="#feature-structure"><code>#structure</code></a></p></li><li><p><a href="#feature-time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul><p>
-In addition, a TT AF processor that supports the
+In addition, a TTML processor that supports the
<code>#presentation</code> feature should satisfy the user agent
accessibility guidelines specified by <a href="#uaag">[UAAG]</a>.</p></div><div class="div3">
-<h4><a name="feature-profile" id="feature-profile"/>D.1.71 #profile</h4><p>A TT AF transformation processor supports the <code>#profile</code>
+<h4><a name="feature-profile" id="feature-profile"/>D.1.71 #profile</h4><p>A TTML transformation processor supports the <code>#profile</code>
feature if it recognizes and is capable of transforming the
<a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
attribute on the <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element and
transforming the following vocabulary defined by
-<a href="#parameter-element-vocabulary"><b>6.1 Parameter Element Vocabulary</b></a>:</p><ul><li><p><a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a></p></li><li><p><a href="#parameter-vocabulary-features"><code>ttp:features</code></a></p></li><li><p><a href="#parameter-vocabulary-feature"><code>ttp:feature</code></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><code>ttp:extensions</code></a></p></li><li><p><a href="#parameter-vocabulary-extension"><code>ttp:extension</code></a></p></li></ul><p>A TT AF presentation processor supports the
+<a href="#parameter-element-vocabulary"><b>6.1 Parameter Element Vocabulary</b></a>:</p><ul><li><p><a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a></p></li><li><p><a href="#parameter-vocabulary-features"><code>ttp:features</code></a></p></li><li><p><a href="#parameter-vocabulary-feature"><code>ttp:feature</code></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><code>ttp:extensions</code></a></p></li><li><p><a href="#parameter-vocabulary-extension"><code>ttp:extension</code></a></p></li></ul><p>A TTML presentation processor supports the
<code>#profile</code> feature if it implements presentation semantic support
for the same vocabulary specified above.</p></div><div class="div3">
-<h4><a name="feature-showBackground" id="feature-showBackground"/>D.1.72 #showBackground</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-showBackground" id="feature-showBackground"/>D.1.72 #showBackground</h4><p>A TTML transformation processor supports the
<code>#showBackground</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-showBackground"><code>tts:showBackground</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#showBackground</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-showBackground"><code>tts:showBackground</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-structure" id="feature-structure"/>D.1.73 #structure</h4><p>A TT AF transformation processor supports the <code>#structure</code>
+<h4><a name="feature-structure" id="feature-structure"/>D.1.73 #structure</h4><p>A TTML transformation processor supports the <code>#structure</code>
feature if it recognizes and is capable of transforming the following
-vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><code>tt</code></a></p></li><li><p><a href="#document-structure-vocabulary-head"><code>head</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#structure</code>
+vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><code>tt</code></a></p></li><li><p><a href="#document-structure-vocabulary-head"><code>head</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#structure</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-styling" id="feature-styling"/>D.1.74 #styling</h4><p>A TT AF transformation processor supports the <code>#styling</code>
+<h4><a name="feature-styling" id="feature-styling"/>D.1.74 #styling</h4><p>A TTML transformation processor supports the <code>#styling</code>
feature if it recognizes and is capable of transforming the following
-vocabulary defined by <a href="#styling"><b>8 Styling</b></a>:</p><ul><li><p><a href="#styling-vocabulary-styling"><code>styling</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li><li><p><a href="#style-attribute-style">@<code>style</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#styling</code>
+vocabulary defined by <a href="#styling"><b>8 Styling</b></a>:</p><ul><li><p><a href="#styling-vocabulary-styling"><code>styling</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li><li><p><a href="#style-attribute-style">@<code>style</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#styling</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-styling-chained" id="feature-styling-chained"/>D.1.75 #styling-chained</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-chained" id="feature-styling-chained"/>D.1.75 #styling-chained</h4><p>A TTML transformation processor supports the
<code>#styling-chained</code> feature if it recognizes and is capable
-of transforming chained style association as defined by <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p><p>A TT AF presentation processor supports the
+of transforming chained style association as defined by <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p><p>A TTML presentation processor supports the
<code>#styling-chained</code> feature if it implements presentation semantic
support for chained style association as defined by <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inheritance-content" id="feature-styling-inheritance-content"/>D.1.76 #styling-inheritance-content</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-inheritance-content" id="feature-styling-inheritance-content"/>D.1.76 #styling-inheritance-content</h4><p>A TTML transformation processor supports the
<code>#styling-inheritance</code> feature if it recognizes and is
capable of transforming content style inheritance as defined by
-<a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p><p>A TT AF presentation processor supports the
+<a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p><p>A TTML presentation processor supports the
<code>#styling-inheritance-content</code> feature if it implements
presentation semantic support for content style inheritance as defined by <a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inheritance-region" id="feature-styling-inheritance-region"/>D.1.77 #styling-inheritance-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-inheritance-region" id="feature-styling-inheritance-region"/>D.1.77 #styling-inheritance-region</h4><p>A TTML transformation processor supports the
<code>#styling-inheritance</code> feature if it recognizes and is
capable of transforming region style inheritance as defined by
-<a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p><p>A TT AF presentation processor supports the
+<a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p><p>A TTML presentation processor supports the
<code>#styling-inheritance-region</code> feature if it implements
presentation semantic support for region style inheritance as defined by <a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inline" id="feature-styling-inline"/>D.1.78 #styling-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-inline" id="feature-styling-inline"/>D.1.78 #styling-inline</h4><p>A TTML transformation processor supports the
<code>#styling-inline</code> feature if it recognizes and is capable
-of transforming inline style association as defined by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p><p>A TT AF presentation processor supports the
+of transforming inline style association as defined by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p><p>A TTML presentation processor supports the
<code>#styling-inline</code> feature if it implements presentation semantic support
for inline style association as defined by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-nested" id="feature-styling-nested"/>D.1.79 #styling-nested</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-nested" id="feature-styling-nested"/>D.1.79 #styling-nested</h4><p>A TTML transformation processor supports the
<code>#styling-nested</code> feature if it recognizes and is capable
-of transforming nested style association as defined by <a href="#semantics-style-association-nested"><b>8.4.1.4 Nested Styling</b></a>.</p><p>A TT AF presentation processor supports the
+of transforming nested style association as defined by <a href="#semantics-style-association-nested"><b>8.4.1.4 Nested Styling</b></a>.</p><p>A TTML presentation processor supports the
<code>#styling-nested</code> feature if it implements presentation semantic support
for nested style association as defined by <a href="#semantics-style-association-nested"><b>8.4.1.4 Nested Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-referential" id="feature-styling-referential"/>D.1.80 #styling-referential</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-referential" id="feature-styling-referential"/>D.1.80 #styling-referential</h4><p>A TTML transformation processor supports the
<code>#styling-referential</code> feature if it recognizes and is capable
-of transforming referential style association as defined by <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a>.</p><p>A TT AF presentation processor supports the
+of transforming referential style association as defined by <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a>.</p><p>A TTML presentation processor supports the
<code>#styling-referential</code> feature if it implements presentation semantic
support for referential style association as defined by <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-subFrameRate" id="feature-subFrameRate"/>D.1.81 #subFrameRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-subFrameRate" id="feature-subFrameRate"/>D.1.81 #subFrameRate</h4><p>A TTML transformation processor supports the
<code>#subFrameRate</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#subFrameRate</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign" id="feature-textAlign"/>D.1.82 #textAlign</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign" id="feature-textAlign"/>D.1.82 #textAlign</h4><p>A TTML transformation processor supports the
<code>#textAlign</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textAlign</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign-absolute" id="feature-textAlign-absolute"/>D.1.83 #textAlign-absolute</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign-absolute" id="feature-textAlign-absolute"/>D.1.83 #textAlign-absolute</h4><p>A TTML transformation processor supports the
<code>#textAlign-absolute</code> feature if it recognizes and is
capable of transforming the <code>left</code>, <code>center</code>,
and <code>right</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textAlign-absolute</code> feature if it implements presentation semantic
support for the <code>left</code>, <code>center</code>, and
<code>right</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign-relative" id="feature-textAlign-relative"/>D.1.84 #textAlign-relative</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign-relative" id="feature-textAlign-relative"/>D.1.84 #textAlign-relative</h4><p>A TTML transformation processor supports the
<code>#textAlign-relative</code> feature if it recognizes and is
capable of transforming the <code>start</code>, <code>center</code>,
and <code>end</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textAlign-relative</code> feature if it implements presentation semantic
support for the <code>start</code>, <code>center</code>, and
<code>end</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration" id="feature-textDecoration"/>D.1.85 #textDecoration</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration" id="feature-textDecoration"/>D.1.85 #textDecoration</h4><p>A TTML transformation processor supports the
<code>#textDecoration</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textDecoration</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-over" id="feature-textDecoration-over"/>D.1.86 #textDecoration-over</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-over" id="feature-textDecoration-over"/>D.1.86 #textDecoration-over</h4><p>A TTML transformation processor supports the
<code>#textDecoration-over</code> feature if it recognizes and is
capable of transforming the <code>overline</code> and
<code>noOverline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textDecoration-over</code> feature if it implements
presentation semantic support for the <code>overline</code> and
<code>noOverline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-through" id="feature-textDecoration-through"/>D.1.87 #textDecoration-through</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-through" id="feature-textDecoration-through"/>D.1.87 #textDecoration-through</h4><p>A TTML transformation processor supports the
<code>#textDecoration-through</code> feature if it recognizes and is
capable of transforming the <code>lineThrough</code> and
<code>noLineThrough</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textDecoration-through</code> feature if it implements
presentation semantic support for the <code>lineThrough</code> and
<code>noLineThrough</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-under" id="feature-textDecoration-under"/>D.1.88 #textDecoration-under</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-under" id="feature-textDecoration-under"/>D.1.88 #textDecoration-under</h4><p>A TTML transformation processor supports the
<code>#textDecoration-under</code> feature if it recognizes and is
capable of transforming the <code>underline</code> and
<code>noUnderline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textDecoration-under</code> feature if it implements
presentation semantic support for the <code>underline</code> and
<code>noUnderline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textOutline" id="feature-textOutline"/>D.1.89 #textOutline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textOutline" id="feature-textOutline"/>D.1.89 #textOutline</h4><p>A TTML transformation processor supports the
<code>#textOutline</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#textOutline</code> feature if it implements presentation semantic support
for the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textOutline-blurred" id="feature-textOutline-blurred"/>D.1.90 #textOutline-blurred</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textOutline-blurred" id="feature-textOutline-blurred"/>D.1.90 #textOutline-blurred</h4><p>A TTML transformation processor supports the
<code>#textOutline-blurred</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
-attribute that includes a blur radius specification.</p><p>A TT AF presentation processor supports the
+attribute that includes a blur radius specification.</p><p>A TTML presentation processor supports the
<code>#textOutline-blurred</code> feature if it implements presentation semantic support
for values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
attribute that includes a blur radius specification.</p></div><div class="div3">
-<h4><a name="feature-textOutline-unblurred" id="feature-textOutline-unblurred"/>D.1.91 #textOutline-unblurred</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textOutline-unblurred" id="feature-textOutline-unblurred"/>D.1.91 #textOutline-unblurred</h4><p>A TTML transformation processor supports the
<code>#textOutline-unblurred</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
-attribute that does not include a blur radius specification.</p><p>A TT AF presentation processor supports the
+attribute that does not include a blur radius specification.</p><p>A TTML presentation processor supports the
<code>#textOutline-unblurred</code> feature if it implements presentation semantic support
for values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
attribute that does not include a blur radius specification.</p></div><div class="div3">
-<h4><a name="feature-tickRate" id="feature-tickRate"/>D.1.92 #tickRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-tickRate" id="feature-tickRate"/>D.1.92 #tickRate</h4><p>A TTML transformation processor supports the
<code>#tickRate</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#tickRate</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-timeBase-clock" id="feature-timeBase-clock"/>D.1.93 #timeBase-clock</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-clock" id="feature-timeBase-clock"/>D.1.93 #timeBase-clock</h4><p>A TTML transformation processor supports the
<code>#timeBase-clock</code> feature if it recognizes and is capable
of transforming the <code>clock</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
-attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p><p>A TT AF presentation processor supports the
+attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p><p>A TTML presentation processor supports the
<code>#timeBase-clock</code> feature if it implements presentation
semantic support for the <code>clock</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p></div><div class="div3">
-<h4><a name="feature-timeBase-media" id="feature-timeBase-media"/>D.1.94 #timeBase-media</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-media" id="feature-timeBase-media"/>D.1.94 #timeBase-media</h4><p>A TTML transformation processor supports the
<code>#timeBase-media</code> feature if it recognizes and is capable
of transforming the <code>media</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#timeBase-media</code> feature if it implements presentation
semantic support for the <code>media</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-timeBase-smpte" id="feature-timeBase-smpte"/>D.1.95 #timeBase-smpte</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-smpte" id="feature-timeBase-smpte"/>D.1.95 #timeBase-smpte</h4><p>A TTML transformation processor supports the
<code>#timeBase-smpte</code> feature if it recognizes and is capable
of transforming the <code>smpte</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
-attribute and if it supports the <a href="#feature-dropMode"><code>#dropMode</code></a> feature.</p><p>A TT AF presentation processor supports the
+attribute and if it supports the <a href="#feature-dropMode"><code>#dropMode</code></a> feature.</p><p>A TTML presentation processor supports the
<code>#timeBase-smpte</code> feature if it implements presentation
semantic support for the <code>smpte</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute and if it supports the <a href="#feature-dropMode"><code>#dropMode</code></a> feature.</p></div><div class="div3">
-<h4><a name="feature-timeContainer" id="feature-timeContainer"/>D.1.96 #timeContainer</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeContainer" id="feature-timeContainer"/>D.1.96 #timeContainer</h4><p>A TTML transformation processor supports the
<code>#timeContainer</code> feature if it recognizes and is capable of
transforming the <a href="#timing-attribute-timeContainer"><code>timeContainer</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#timeContainer</code> feature if it implements presentation semantic support
for the <a href="#timing-attribute-timeContainer"><code>timeContainer</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-time-clock" id="feature-time-clock"/>D.1.97 #time-clock</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-clock" id="feature-time-clock"/>D.1.97 #time-clock</h4><p>A TTML transformation processor supports the
<code>#time-clock</code> feature if it recognizes and is capable of
transforming all values of the <a href="#timing-value-timeExpression"><timeExpression></a> that
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
<timeExpression>
: hours ":" minutes ":" seconds ( fraction )?
-</pre></div><p>A TT AF presentation processor supports the
+</pre></div><p>A TTML presentation processor supports the
<code>#time-clock</code> feature if it implements presentation
semantic support for the same syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-time-clock-with-frames" id="feature-time-clock-with-frames"/>D.1.98 #time-clock-with-frames</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-clock-with-frames" id="feature-time-clock-with-frames"/>D.1.98 #time-clock-with-frames</h4><p>A TTML transformation processor supports the
<code>#time-clock-with-frames</code> feature if it supports the
<a href="#feature-frameRate"><code>#frameRate</code></a>,
<a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a>, and
@@ -7587,20 +7565,20 @@
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
<timeExpression>
: hours ":" minutes ":" seconds ( fraction | ":" frames ( "." sub-frames )? )?
-</pre></div><p>A TT AF presentation processor supports the
+</pre></div><p>A TTML presentation processor supports the
<code>#time-clock-with-frames</code> feature if it implements
presentation semantic support for the same features and syntax
specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset" id="feature-time-offset"/>D.1.99 #time-offset</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-offset" id="feature-time-offset"/>D.1.99 #time-offset</h4><p>A TTML transformation processor supports the
<code>#time-offset</code> feature if it recognizes and is capable of
transforming all values of the <a href="#timing-value-timeExpression"><timeExpression></a> that
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
<timeExpression>
: time-count fraction? ( "h" | "m" | "s" | "ms" )
-</pre></div><p>A TT AF presentation processor supports the
+</pre></div><p>A TTML presentation processor supports the
<code>#time-offset</code> feature if it implements presentation
semantic support for the same syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset-with-frames" id="feature-time-offset-with-frames"/>D.1.100 #time-offset-with-frames</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-offset-with-frames" id="feature-time-offset-with-frames"/>D.1.100 #time-offset-with-frames</h4><p>A TTML transformation processor supports the
<code>#time-offset-with-frames</code> feature if it supports the
<a href="#feature-frameRate"><code>#frameRate</code></a>,
<a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a>, and
@@ -7610,11 +7588,11 @@
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
<timeExpression>
: time-count fraction? "f"
-</pre></div><p>A TT AF presentation processor supports the
+</pre></div><p>A TTML presentation processor supports the
<code>#time-offset-with-frames</code> feature if it implements
presentation semantic support for the same features and syntax
specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset-with-ticks" id="feature-time-offset-with-ticks"/>D.1.101 #time-offset-with-ticks</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-offset-with-ticks" id="feature-time-offset-with-ticks"/>D.1.101 #time-offset-with-ticks</h4><p>A TTML transformation processor supports the
<code>#time-offset-with-ticks</code> feature if it supports the
<a href="#feature-tickRate"><code>#tickRate</code></a> feature
and if it recognizes and is capable of
@@ -7622,112 +7600,112 @@
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
<timeExpression>
: time-count fraction? "t"
-</pre></div><p>A TT AF presentation processor supports the
+</pre></div><p>A TTML presentation processor supports the
<code>#time-offset-with-ticks</code> feature if it implements presentation
semantic support for the same features and syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-timing" id="feature-timing"/>D.1.102 #timing</h4><p>A TT AF transformation processor supports the <code>#timing</code>
+<h4><a name="feature-timing" id="feature-timing"/>D.1.102 #timing</h4><p>A TTML transformation processor supports the <code>#timing</code>
feature if it recognizes and is capable of transforming the following
-vocabulary defined by <a href="#timing"><b>10 Timing</b></a>:</p><ul><li><p><a href="#timing-attribute-begin">@<code>begin</code></a></p></li><li><p><a href="#timing-attribute-dur">@<code>dur</code></a></p></li><li><p><a href="#timing-attribute-end">@<code>end</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#timing</code>
+vocabulary defined by <a href="#timing"><b>10 Timing</b></a>:</p><ul><li><p><a href="#timing-attribute-begin">@<code>begin</code></a></p></li><li><p><a href="#timing-attribute-dur">@<code>dur</code></a></p></li><li><p><a href="#timing-attribute-end">@<code>end</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#timing</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-transformation" id="feature-transformation"/>D.1.103 #transformation</h4><p>A TT AF processor supports the
+<h4><a name="feature-transformation" id="feature-transformation"/>D.1.103 #transformation</h4><p>A TTML processor supports the
<code>#transformation</code> feature if it
(1) satisfies the generic processor criteria defined by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a> and
(2) implements transformation semantics for the following features:</p><ul><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#feature-core"><code>#core</code></a></p></li><li><p><a href="#feature-profile"><code>#profile</code></a></p></li><li><p><a href="#feature-structure"><code>#structure</code></a></p></li><li><p><a href="#feature-time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul></div><div class="div3">
-<h4><a name="feature-unicodeBidi" id="feature-unicodeBidi"/>D.1.104 #unicodeBidi</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-unicodeBidi" id="feature-unicodeBidi"/>D.1.104 #unicodeBidi</h4><p>A TTML transformation processor supports the
<code>#unicodeBidi</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#unicodeBidi</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-visibility" id="feature-visibility"/>D.1.105 #visibility</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility" id="feature-visibility"/>D.1.105 #visibility</h4><p>A TTML transformation processor supports the
<code>#visibility</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#visibility</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-visibility-block" id="feature-visibility-block"/>D.1.106 #visibility-block</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-block" id="feature-visibility-block"/>D.1.106 #visibility-block</h4><p>A TTML transformation processor supports the
<code>#visibility-block</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that would generate a
-block area during presentation processing.</p><p>A TT AF presentation processor supports the
+block area during presentation processing.</p><p>A TTML presentation processor supports the
<code>#visibility-block</code> feature if it implements presentation semantic
support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that generates a
block area.</p></div><div class="div3">
-<h4><a name="feature-visibility-inline" id="feature-visibility-inline"/>D.1.107 #visibility-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-inline" id="feature-visibility-inline"/>D.1.107 #visibility-inline</h4><p>A TTML transformation processor supports the
<code>#visibility-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that would generate an
-inline area during presentation processing.</p><p>A TT AF presentation processor supports the
+inline area during presentation processing.</p><p>A TTML presentation processor supports the
<code>#visibility-inline</code> feature if it implements presentation semantic
support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that generates an
inline area.</p></div><div class="div3">
-<h4><a name="feature-visibility-region" id="feature-visibility-region"/>D.1.108 #visibility-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-region" id="feature-visibility-region"/>D.1.108 #visibility-region</h4><p>A TTML transformation processor supports the
<code>#visibility-region</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
-attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TT AF presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
<code>#visibility-region</code> feature if it implements presentation semantic
support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-wrapOption" id="feature-wrapOption"/>D.1.109 #wrapOption</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-wrapOption" id="feature-wrapOption"/>D.1.109 #wrapOption</h4><p>A TTML transformation processor supports the
<code>#wrapOption</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#wrapOption</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode" id="feature-writingMode"/>D.1.110 #writingMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode" id="feature-writingMode"/>D.1.110 #writingMode</h4><p>A TTML transformation processor supports the
<code>#writingMode</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#writingMode</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-vertical" id="feature-writingMode-vertical"/>D.1.111 #writingMode-vertical</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-vertical" id="feature-writingMode-vertical"/>D.1.111 #writingMode-vertical</h4><p>A TTML transformation processor supports the
<code>#writingMode-vertical</code> feature if it recognizes and is
capable of transforming the <code>tbrl</code>, <code>tblr</code>, and
<code>tb</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#writingMode-vertical</code> feature if it implements presentation semantic
support for the <code>tbrl</code>, <code>tblr</code>, and
<code>tb</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal" id="feature-writingMode-horizontal"/>D.1.112 #writingMode-horizontal</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-horizontal" id="feature-writingMode-horizontal"/>D.1.112 #writingMode-horizontal</h4><p>A TTML transformation processor supports the
<code>#writingMode-horizontal</code> feature if it recognizes and is
capable of transforming the <code>lrtb</code>, <code>rltb</code>,
<code>lr</code> and <code>rl</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#writingMode-horizontal</code> feature if it implements presentation semantic
support for the <code>lrtb</code>, <code>rltb</code>, <code>lr</code>
and <code>rl</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal-lr" id="feature-writingMode-horizontal-lr"/>D.1.113 #writingMode-horizontal-lr</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-horizontal-lr" id="feature-writingMode-horizontal-lr"/>D.1.113 #writingMode-horizontal-lr</h4><p>A TTML transformation processor supports the
<code>#writingMode-horizontal</code> feature if it recognizes and is
capable of transforming the <code>lrtb</code> and <code>lr</code>
values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#writingMode-horizontal-lr</code> feature if it implements presentation semantic
support for the <code>lrtb</code> and <code>lr</code> values of the
<a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal-rl" id="feature-writingMode-horizontal-rl"/>D.1.114 #writingMode-horizontal-rl</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-horizontal-rl" id="feature-writingMode-horizontal-rl"/>D.1.114 #writingMode-horizontal-rl</h4><p>A TTML transformation processor supports the
<code>#writingMode-horizontal</code> feature if it recognizes and is
capable of transforming the <code>rltb</code> and <code>rl</code>
values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#writingMode-horizontal-rl</code> feature if it implements presentation semantic
support for the <code>rltb</code> and <code>rl</code> values of the
<a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-zIndex" id="feature-zIndex"/>D.1.115 #zIndex</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-zIndex" id="feature-zIndex"/>D.1.115 #zIndex</h4><p>A TTML transformation processor supports the
<code>#zIndex</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-zIndex"><code>tts:zIndex</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
+attribute.</p><p>A TTML presentation processor supports the
<code>#zIndex</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-zIndex"><code>tts:zIndex</code></a>
attribute.</p></div></div><div class="div2">
@@ -7737,9 +7715,9 @@
whether the feature is mandatory (M) or optional (O) for
transformation and presentation processors.</p><table summary="HTML Table" id="feature-support-table" class="common"><caption>Table E-1 – Feature Support</caption><col width="60%" span="1"/><col width="20%" span="1"/><col width="20%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Transformation</span></td><td><span class="strong">Presentation</span></td></tr><tr><td><a href="#feature-animation"><code>#animation</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor"><code>#backgroundColor</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-block"><code>#backgroundColor-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-inline"><code>#backgroundColor-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-region"><code>#backgroundColor-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-bidi"><code>#bidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-cellResolution"><code>#cellResolution</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode"><code>#clockMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-gps"><code>#clockMode-gps</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-local"><code>#clockMode-local</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-utc"><code>#clockMode-utc</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-color"><code>#color</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-core"><code>#core</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-direction"><code>#direction</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display"><code>#display</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-block"><code>#display-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-inline"><code>#display-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-region"><code>#display-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-displayAlign"><code>#displayAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode"><code>#dropMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-dropNTSC"><code>#dropMode-dropNTSC</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-dropPAL"><code>#dropMode-dropPAL</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-nonDrop"><code>#dropMode-nonDrop</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent"><code>#extent</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent-region"><code>#extent-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent-root"><code>#extent-root</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily"><code>#fontFamily</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-generic"><code>#fontFamily-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-non-generic"><code>#fontFamily-non-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize"><code>#fontSize</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-anamorphic"><code>#fontSize-anamorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle"><code>#fontStyle</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-oblique"><code>#fontStyle-oblique</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-reverseOblique"><code>#fontStyle-reverseOblique</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight"><code>#fontWeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRate"><code>#frameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-layout"><code>#layout</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length"><code>#length</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-cell"><code>#length-cell</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-em"><code>#length-em</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-integer"><code>#length-integer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-negative"><code>#length-negative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-percentage"><code>#length-percentage</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-pixel"><code>#length-pixel</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-real"><code>#length-real</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineBreak-uax14"><code>#lineBreak-uax14</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineHeight"><code>#lineHeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode"><code>#markerMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode-continuous"><code>#markerMode-continuous</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode-discontinuous"><code>#markerMode-discontinuous</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-metadata"><code>#metadata</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-div"><code>#nested-div</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-span"><code>#nested-span</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-opacity"><code>#opacity</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-origin"><code>#origin</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow"><code>#overflow</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow-visible"><code>#overflow-visible</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding"><code>#padding</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-1"><code>#padding-1</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-2"><code>#padding-2</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-3"><code>#padding-3</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-4"><code>#padding-4</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-pixelAspectRatio"><code>#pixelAspectRatio</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td>O</td><td>M</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-rollUp"><code>#rollUp</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-showBackground"><code>#showBackground</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-styling"><code>#styling</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-chained"><code>#styling-chained</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-region"><code>#styling-inheritance-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inline"><code>#styling-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-nested"><code>#styling-nested</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-referential"><code>#styling-referential</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-subFrameRate"><code>#subFrameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign"><code>#textAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-relative"><code>#textAlign-relative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration"><code>#textDecoration</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-over"><code>#textDecoration-over</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-through"><code>#textDecoration-through</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-under"><code>#textDecoration-under</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline"><code>#textOutline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-blurred"><code>#textOutline-blurred</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-unblurred"><code>#textOutline-unblurred</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-tickRate"><code>#tickRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-clock"><code>#timeBase-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-media"><code>#timeBase-media</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-smpte"><code>#timeBase-smpte</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeContainer"><code>#timeContainer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock"><code>#time-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock-with-frames"><code>#time-clock-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset"><code>#time-offset</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-time-offset-with-frames"><code>#time-offset-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset-with-ticks"><code>#time-offset-with-ticks</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timing"><code>#timing</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td>M</td><td>O</td></tr><tr><td><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility"><code>#visibility</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-block"><code>#visibility-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-region"><code>#visibility-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-wrapOption"><code>#wrapOption</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode"><code>#writingMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-vertical"><code>#writingMode-vertical</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-lr"><code>#writingMode-horizontal-lr</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-rl"><code>#writingMode-horizontal-rl</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-zIndex"><code>#zIndex</code></a></td><td>O</td><td>O</td></tr></tbody></table><p>For the sake of convenience, the following table,
<a href="#feature-transformation-mandatory-table"><b>Table E-2 – Mandatory Features - Transformation</b></a>, enumerates all
-mandatory features for a TT AF Transformation Processor, providing additional
+mandatory features for a TTML Transformation Processor, providing additional
comments to summarize the context of usage or the nature of the feature.
-The TT AF Profile Definition Document that defines the corresponding
+The TTML Profile Definition Document that defines the corresponding
DFXP Transformation Profile is specified in
<a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a>.
</p><table summary="HTML Table" id="feature-transformation-mandatory-table" class="common"><caption>Table E-2 – Mandatory Features - Transformation</caption><col width="60%" span="1"/><col width="40%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
@@ -7761,9 +7739,9 @@
<a href="#timing-attribute-end">@<code>end</code></a>
</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td/></tr></tbody></table><p>For the sake of convenience, the following table,
<a href="#feature-presentation-mandatory-table"><b>Table E-3 – Mandatory Features - Presentation</b></a>, enumerates all
-mandatory features for a TT AF Presentation Processor, providing additional
+mandatory features for a TTML Presentation Processor, providing additional
comments to summarize the context of usage or the nature of the feature.
-The TT AF Profile Definition Document that defines the corresponding
+The TTML Profile Definition Document that defines the corresponding
DFXP Presentation Profile is specified in
<a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a>.
</p><table summary="HTML Table" id="feature-presentation-mandatory-table" class="common"><caption>Table E-3 – Mandatory Features - Presentation</caption><col width="60%" span="1"/><col width="40%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
@@ -7786,7 +7764,7 @@
</td></tr></tbody></table></div></div><div class="div1">
<h2><a name="extensions" id="extensions"/>E Extensions</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the syntactic form of extension designations, which are
used to express authorial intent regarding the support for extension
-mechanisms in a TT AF processor.</p><div class="div2">
+mechanisms in a TTML processor.</p><div class="div2">
<h3><a name="extension-designations" id="extension-designations"/>E.1 Extension Designations</h3><p>An extension designation is expressed as a string that adheres to the following
form:</p><div class="exampleInner"><pre>
extension-designation
@@ -7810,7 +7788,7 @@
capable of serving as a base URI used in combination with a
<code>designation</code> token that takes the form of a fragment
identifier.</p></div></div><div class="div1">
-<h2><a name="profiles" id="profiles"/>F Profiles</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following standard TT AF profiles:</p><ul><li><p><a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a></p></li><li><p><a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a></p></li><li><p><a href="#profile-dfxp-full"><b>F.3 DFXP Full Profile</b></a></p></li></ul><p>Each TT AF profile is defined in terms of a TT AF Profile Definition Document,
+<h2><a name="profiles" id="profiles"/>F Profiles</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following standard TTML profiles:</p><ul><li><p><a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a></p></li><li><p><a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a></p></li><li><p><a href="#profile-dfxp-full"><b>F.3 DFXP Full Profile</b></a></p></li></ul><p>Each TTML profile is defined in terms of a TTML Profile Definition Document,
which is expressed as an XML document wherein the root element adheres to
<a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p><div class="div2">
<h3><a name="profile-dfxp-transformation" id="profile-dfxp-transformation"/>F.1 DFXP Transformation Profile</h3><p>The DFXP Transformation Profile is intended to be used to
@@ -8389,7 +8367,7 @@
<a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>.)
</dd></dl></div><div class="div1">
<h2><a name="requirements" id="requirements"/>I Requirements (Non-Normative)</h2><p>The Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring
-Format (TT AF) satisfies a subset of the requirements established by
+Format (TTML) satisfies a subset of the requirements established by
<a href="#ttaf1-req">[TTAF1-REQ]</a>. The following table enumerates these requirements and
indicates the extent to which they are satisfied by this specification, where
<em>S</em> denotes a requirement is satisfied, <em>P</em> denotes
@@ -8398,11 +8376,11 @@
font family, font size, font style, font weight, height, line height, origin,
opacity, overflow, padding (before, after, start, end), text alignment,
text shadow (as outline), visibility, width, writing mode, z-index</td></tr><tr><td>R390</td><td>Style Parameter Symmetry</td><td>S</td><td/></tr><tr><td>R391</td><td>Style Parameter Definitions</td><td>S</td><td/></tr><tr><td>R392</td><td>Style Parameter Shorthands</td><td>S</td><td/></tr><tr><td>R401</td><td>Inline Timing</td><td>S</td><td/></tr><tr><td>R402</td><td>Out-of-Line Timing</td><td>N</td><td/></tr><tr><td>R403</td><td>Synchronization Parameters</td><td>P</td><td>Supports begin, end, dur</td></tr><tr><td>R404</td><td>Synchronization Parameter Value Spaces</td><td>P</td><td>Supports offset values, media marker values (SMPTE 12M), wallclock values</td></tr><tr><td>R405</td><td>Time Containment Semantics</td><td>P</td><td>Supports sequential, parallel</td></tr><tr><td>R500</td><td>Animation Modes</td><td>P</td><td>Supports discrete</td></tr><tr><td>R502</td><td>Highlight Animation</td><td>S</td><td><code><set tts:backgroundColor="..."/></code></td></tr><tr><td>R503</td><td>Fade Transition Animation</td><td>S</td><td><code><set tts:opacity="..."/></code></td></tr><tr><td>R504</td><td>Animated Style Parameters – Aural</td><td>N</td><td/></tr><tr><td>R505</td><td>Animated Style Parameters – Visual</td><td>P</td><td>Supports animating background color, color, display, opacity, origin, visibility</td></tr><tr><td>N506</td><td>Animated Content</td><td>S</td><td/></tr><tr><td>R600</td><td>Metadata Item Association</td><td>S</td><td>See <code>metadata</code>, <code>Metadata.class</code></td></tr><tr><td>R601</td><td>Metadata Item Constituents</td><td>P</td><td>Supports name, value</td></tr><tr><td>R602</td><td>Metadata Item Value Representation</td><td>P</td><td>See <code>metadata</code></td></tr><tr><td>R603</td><td>Metadata Item Extensibility</td><td>S</td><td>See <code>metadata</code></td></tr><tr><td>R604</td><td>Metadata Item Validation</td><td>S</td><td>See <code>metadata</code></td></tr><tr><td>R690</td><td>Dublin Core Preference</td><td>N</td><td>Uses <code>ttm:copyright</code>, <code>ttm:desc</code>, <code>ttm:title</code></td></tr></tbody></table></div><div class="div1">
-<h2><a name="derivation" id="derivation"/>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TT AF
+<h2><a name="derivation" id="derivation"/>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
vocabulary, separately describing derivation of elements and
attributes.</p><div class="div2">
-<h3><a name="d3e17101" id="d3e17101"/>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
-specifies a TT AF element vocabulary item; the second column specifies the
+<h3><a name="d3e17024" id="d3e17024"/>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
+specifies a TTML element vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
the model (if a model is indicated);
@@ -8414,7 +8392,7 @@
details column includes "-@class", which denotes that the
<code>class</code> attribute that is specified for use with the
<code>xhtml:div</code> model element is not specified for use with the
-corresponding TT AF element; in contrast, the details column includes
+corresponding TTML element; in contrast, the details column includes
"+@begin", which denotes that a <code>begin</code> attribute is added
that is not specified for use with the <code>xhtml:div</code> model
element.</p><table summary="HTML Table" id="element-vocab-derivation-table" class="common"><caption>Table K-1 – Elements</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">Element</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="#document-structure-vocabulary-body"><code>tt:body</code></a></td><td><code>xhtml:body</code></td><td><a href="#xhtml10">[XHTML 1.0]</a></td><td>-@class, -@dir, -@lang, -@on*, -@title; +@begin, +@dur, +@end, +@region,
@@ -8456,8 +8434,8 @@
and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e17580" id="d3e17580"/>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
-specifies a TT AF attribute vocabulary item; the second column specifies the
+<h3><a name="d3e17503" id="d3e17503"/>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
+specifies a TTML attribute vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
the model (if a model is indicated);
@@ -8470,14 +8448,14 @@
the details column includes "-excl", which denotes that the
<code>excl</code> value that is specified for use with the
<code>timeContainer</code> model attribute is not specified for use with the
-corresponding TT AF attribute; similarly, an "+<em>value</em>"
+corresponding TTML attribute; similarly, an "+<em>value</em>"
in the details column indicates that the attribute's values have been
-extended to include <em>value</em>.</p><p>Only those attributes that are specified for use on more than one TT AF
+extended to include <em>value</em>.</p><p>Only those attributes that are specified for use on more than one TTML
element type are listed below. Those per-element namespace attributes
-that are uniquely defined for a specific TT AF element type are not
+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 K-1 – Elements</b></a>
-above.</p><table summary="HTML Table" id="attribute-vocab-derivation-table" class="common"><caption>Table K-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/></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/></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>used to attribute agent of content</td><td/></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td/><td>used to attribute role of content</td><td/></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td/><td>expresses uniform grid resolution for cell based coordinates</td><td/></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td/><td>determines how to interpret time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td/><td>expresses integral frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td/><td>used to express non-integral, rational frame rates</td><td/></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td/><td>expresses marker continuity semantics</td><td/></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td/><td>expresses pixel aspect ratio of related media</td><td/></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td/><td>expresses profile of TT AF used by document instance</td><td/></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td/><td>expresses frame counting (drop) modes</td><td/></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td/><td>expresses sub-frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td/><td>used to interpret tick based time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td/><td>used to interpret semantics of time expressions</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/></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/></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/></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>, uses alias <code>reverseOblique</code> for <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/></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/></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/></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/></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/></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/></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><table summary="HTML Table" id="attribute-vocab-derivation-table" class="common"><caption>Table K-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/></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/></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>used to attribute agent of content</td><td/></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td/><td>used to attribute role of content</td><td/></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td/><td>expresses uniform grid resolution for cell based coordinates</td><td/></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td/><td>determines how to interpret time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td/><td>expresses integral frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td/><td>used to express non-integral, rational frame rates</td><td/></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td/><td>expresses marker continuity semantics</td><td/></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td/><td>expresses pixel aspect ratio of related media</td><td/></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td/><td>expresses profile of TTML used by document instance</td><td/></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td/><td>expresses frame counting (drop) modes</td><td/></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td/><td>expresses sub-frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td/><td>used to interpret tick based time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td/><td>used to interpret semantics of time expressions</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/></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/></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/></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>, uses alias <code>reverseOblique</code> for <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/></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/></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/></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/></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/></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/></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>,
@@ -8528,12 +8506,12 @@
<h2><a name="qa" id="qa"/>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
Framework Specifications Guidelines</a> <a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a name="d3e18468" id="d3e18468"/>K.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a name="d3e18391" id="d3e18391"/>K.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
clause</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td/><td/><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td/><td/><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e18632" id="d3e18632"/>K.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td/><td>NO</td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td/><td/><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td/><td>NO</td><td/><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td/><td/><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td/><td/><td/></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a name="d3e18555" id="d3e18555"/>K.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><col width="6%" align="center" span="1"/><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td/><td>NO</td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td/><td/><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td/><td/><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td/><td>NO</td><td/><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td/><td/><td/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td/><td/><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td/><td/><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td/><td/><td/></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
-<a href="#doctypes">TT AF Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
+<a href="#doctypes">TTML Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
<h2><a name="streaming" id="streaming"/>L Streaming DFXP Content (Non-Normative)</h2><p>DFXP Content is designed to support streamability by implementing the
following properties:</p><ul><li><p>can be progressively encoded (i.e., does not require computing
subsequent data prior to sending current data);</p></li><li><p>can be progressively decoded (i.e., does not require forward
@@ -8957,7 +8935,7 @@
* Clarify default flow style semantics [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/84">I-084</a>].
* Clarify default denominator on ttp:frameRateMultiplier [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/85">I-085</a>].
* Add missing style default semantics [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/91">I-091</a>].
-* Clarify mutability of TT AF namespaces [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/94">I-094</a>].
+* Clarify mutability of TTML namespaces [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/94">I-094</a>].
* Clarify constraints on syntax of flow functions [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/103">I-103</a>].
* Clarify interaction between dynamic flow and wrap option processing [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/105">I-105</a>].
* Clarify line breaking semantics [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/106">I-106</a>].