--- a/ttml2/spec/ttml2.html Sun Sep 01 11:28:08 2013 -0600
+++ b/ttml2/spec/ttml2.html Sun Sep 01 11:28:22 2013 -0600
@@ -80,9 +80,9 @@
.strong { font-weight: bold }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/08/28 19:40:32 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/09/01 17:28:08 $<div id="revisions"></div><div class="head">
<h1><a id="title"></a>Timed Text Markup Language 2 (TTML2)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/08/28 19:40:32 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/09/01 17:28:08 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ttml2.html">ttml2.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
@@ -415,11 +415,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="#d3e20498">Element Derivation</a><br>
- J.2 <a href="#d3e21015">Attribute Derivation</a><br>
+ J.1 <a href="#d3e21440">Element Derivation</a><br>
+ J.2 <a href="#d3e21957">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e21995">Requirements</a><br>
- K.2 <a href="#d3e22159">Guidelines</a><br>
+ K.1 <a href="#d3e22937">Requirements</a><br>
+ K.2 <a href="#d3e23101">Guidelines</a><br>
L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
M <a href="#concrete-encoding">Concrete Encoding</a><br>
N <a href="#time-expression-semantics">Time Expression Semantics</a><br>
@@ -446,7 +446,7 @@
streamability of content, as described in <a href="#streaming"><b>L Streaming TTML Content</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While TTML is not expressly designed for direct (embedded) integration into an
HTML or a SMIL document instance, such integration is not precluded.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In some contexts of use, it may be appropriate to employ
animated content to depict sign language representations of the same content
-as expressed by a Timed Text <em>Document Instance</em>. This use case is not
+as expressed by a Timed Text <a href="#terms-document-instance">document instance</a>. This use case is not
explicitly addressed by TTML mechanisms, but may be addressed by some
external multimedia integration technology, such as SMIL.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In previous drafts of this specification, TTML was referred to as DFXP (Distribution
Format Exchange Profile). This latter term is retained for historical reasons in
@@ -460,7 +460,7 @@
heterogeneous collection of distribution formats after undergoing transcoding
or compilation to the target distribution formats as required, and where one
particular distribution format is TTML (labeled as "DFXP" in the figure).</p><a id="model-graphic"></a><table class="example-images"><caption>Figure 1 – System Model</caption><tbody><tr><td><img src="images/model.png" alt="System Model"></td></tr></tbody></table></div><div class="div2">
-<h3><a id="example"></a>1.2 Document Example</h3><p>A TTML <em>Document Instance</em> consists of a <code>tt</code> document element that contains
+<h3><a id="example"></a>1.2 Document Example</h3><p>A TTML <a href="#terms-document-instance">document instance</a> consists of a <code>tt</code> document element that contains
a header and a body, where the header specifies document level metadata, styling
definitions and layout definitions, and the body specifies text content intermixed
with references to style and layout information and inline styling and timing information.</p><a id="ttml-example-document-structure"></a><table class="example"><caption>Example Fragment – TTML Document Structure</caption><tbody><tr><td>
@@ -525,7 +525,7 @@
/>
</layout>
</pre></div>
-</td></tr></tbody></table><p>The content of a <em>Document Instance</em> is expressed in its
+</td></tr></tbody></table><p>The content of a <a href="#terms-document-instance">document instance</a> 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
@@ -623,87 +623,92 @@
Note that the flow order is determined by the lexical order of
elements as they appear in the content hierarchy.</p><a id="ttml-example-subtitle-9"></a><table 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 TTML: metadata, styling, layout, timing, and content. In typical cases,
-styling and layout information are separately specified in a <em>Document Instance</em>. Content information
+styling and layout information are separately specified in a <a href="#terms-document-instance">document instance</a>. 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 id="definitions"></a>2 Definitions</h2><div class="div2">
<h3><a id="acronyms"></a>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>TTAF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TTWG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
-<h3><a id="terms"></a>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
-Sets</em> <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">Computed Cell Size</dt><dd><p>The size (extent) of a cell computed by dividing the width of the <em>Root Container
-Region</em> by the column count, i.e., the number of cells in the horizontal axis, and by dividing
-the height of the <em>Root Container Region</em> by the row count, i.e., the number of cells in the vertical
-axis, where the column and row counts are determined by the <code>ttp:cellResolution</code> parameter attribute.</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 Markup Language content.</p><table border="1" class="ednote" summary="Editorial note: Content Profile"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Content Profile</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update and elaborate definition of content profile based on new profiling mechanisms.</td></tr></table><p></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">Document Instance</dt><dd><p>A concrete realization of a Timed Text Markup Language document, where the concrete form
+<h3><a id="terms"></a>2.2 Terminology</h3><dl><dt class="label"><a id="terms-abstract-document-instance"></a>[abstract document instance]</dt><dd><p>An instance of an abstract data set as represented by a
+<a href="#terms-reduced-xml-infoset">reduced xml infoset</a>.</p></dd><dt class="label"><a id="terms-abstract-document-type"></a>[abstract document type]</dt><dd><p>A set of constraints that defines a class of <em>XML Information
+Sets</em> <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label"><a id="terms-attribute-information-item"></a>[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"><a id="terms-character-information-item"></a>[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"><a id="terms-computed-cell-size"></a>[computed cell size]</dt><dd><p>The size (extent) of a cell computed by dividing the width of the <a href="#terms-root-container-region">root container region</a>
+by the column count, i.e., the number of cells in the horizontal axis, and by dividing
+the height of the <a href="#terms-root-container-region">root container region</a> by the row count, i.e., the number of cells in the vertical
+axis, where the column and row counts are determined by the <code>ttp:cellResolution</code> parameter attribute.</p></dd><dt class="label"><a id="terms-content-element"></a>[content element]</dt><dd><p>Any of the element types defined by the <a href="#element-vocab-type-content">Content Module</a>.</p></dd><dt class="label"><a id="terms-content-processor"></a>[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"><a id="terms-content-profile"></a>[content profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that are (or may be) employed by
+Timed Text Markup Language content.</p><table border="1" class="ednote" summary="Editorial note: Content Profile"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Content Profile</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update and elaborate definition of content profile based on new profiling mechanisms.</td></tr></table><p></p></dd><dt class="label"><a id="terms-content-region"></a>[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"><a id="terms-document-instance"></a>[document instance]</dt><dd><p>A concrete realization of a Timed Text Markup Language document, where the concrete form
is specific to the context of reference. For example, a sequence of bytes that represents an
XML serialization of a Timed Text document, an internal, parsed representation of such a
-Timed Text document, etc.</p></dd><dt class="label">Document Interchange Context</dt><dd><p>The implied context or environment external to a <em>Content Processor</em> in
+Timed Text document, etc.</p></dd><dt class="label"><a id="terms-document-interchange-context"></a>[document interchange context]</dt><dd><p>The implied context or environment external to a <a href="#terms-content-processor">content processor</a> in
which document interchange occurs, and in which out-of-band protocols or specifications
-may define certain behavioral defaults, such as an implied profile.</p></dd><dt class="label">Document Processing Context</dt><dd><p>The implied context or environment internal to a <em>Content Processor</em> in
+may define certain behavioral defaults, such as an implied profile.</p></dd><dt class="label"><a id="terms-document-processing-context"></a>[document processing context]</dt><dd><p>The implied context or environment internal to a <a href="#terms-content-processor">content processor</a> in
which document processing occurs, and in which out-of-band protocols or specifications
may define certain behavioral defaults, such as the establishment or creation of a
-<em>Synthetic Document Syncbase</em>.</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 profile of content 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
+<a href="#terms-synthetic-document-syncbase">synthetic document syncbase</a>.</p></dd><dt class="label"><a id="terms-element-information-item"></a>[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"><a id="terms-exchange-profile"></a>[exchange profile]</dt><dd><p>A profile of content that serves a set of needs for content interchange.</p></dd><dt class="label"><a id="terms-extension"></a>[extension]</dt><dd><p>A syntactic or semantic expression or capability that is defined and
labeled (using a extension designation) in another (public or private)
-specification.</p></dd><dt class="label">Feature</dt><dd><p>A syntactic or semantic expression or capability that is defined and
+specification.</p></dd><dt class="label"><a id="terms-feature"></a>[feature]</dt><dd><p>A syntactic or semantic expression or capability that is defined and
labeled (using a feature designation) in this specification (or a
-future revision of this specification).</p></dd><dt class="label">Inline Animation</dt><dd><p>An animation specification that is defined inline as an immediate child of
-a <a href="#element-vocab-type-content">Content</a> or region element targetted by the animation. There is a one-to-one relation between
-an inline animation element and its parent <a href="#element-vocab-type-content">Content</a> or region element.
-An inline animation does not specify an <code>xlink:href</code> attribute.</p></dd><dt class="label">Inline Region</dt><dd><p>A region specification that is defined inline as an immediate child of
-a <a href="#element-vocab-type-content">Content</a> element to be selected into (targetted to) the region.
-There is a one-to-one relation between an inline region element and its
-parent <a href="#element-vocab-type-content">Content</a> element. An inline region is assigned its parent element's time interval as its active
-time interval. No <code>region</code> attribute makes reference to an inline region.</p></dd><dt class="label">Out-of-line Animation</dt><dd><p>An animation specification that is defined out-of-line from
-the <a href="#element-vocab-type-content">Content</a> or region element targetted by the animation. An out-of-line animation appears
-as a child of an <code>animation</code> element in the header (<code>head</code> element)
-of a <em>Document Instance</em>, and specifies an <code>xlink:href</code> attribute
-in order to associate it with an element to be animated. There is a one-to-one relation between
-an out-of-line animation element and a <a href="#element-vocab-type-content">Content</a> or region element.</p></dd><dt class="label">Out-of-line Region</dt><dd><p>A region specification that is defined out-of-line from
-the <a href="#element-vocab-type-content">Content</a> element(s) to be selected into (targetted to) the region. An out-of-line region appears
-as a child of a <code>layout</code> element in the header (<code>head</code> element)
-of a <em>Document Instance</em>, and specifies an <code>xml:id</code> attribute
-in order to allow <a href="#element-vocab-type-content">Content</a> elements associated with the region by means of a
+future revision of this specification).</p></dd><dt class="label"><a id="terms-inline-animation"></a>[inline animation]</dt><dd><p>An <a href="#animation-vocabulary-animate"><code>animate</code></a> or <a href="#animation-vocabulary-set"><code>set</code></a> element
+that is defined inline as an immediate child of
+a <a href="#terms-content-element">content element</a> or <a href="#layout-vocabulary-region"><code>region</code></a> element targetted by the animation.
+There is a one-to-one relation between
+an inline animation element and its parent <a href="#terms-content-element">content element</a> or <a href="#layout-vocabulary-region"><code>region</code></a> element.
+An inline animation does not specify an <code>xlink:href</code> attribute.</p></dd><dt class="label"><a id="terms-inline-region"></a>[inline region]</dt><dd><p>A <a href="#layout-vocabulary-region"><code>region</code></a> element that is defined inline as an immediate child of
+a <a href="#terms-content-element">content element</a> to be selected into (targetted to) the region.
+There is a one-to-one relation between an inline <a href="#layout-vocabulary-region"><code>region</code></a> element and its
+parent <a href="#terms-content-element">content element</a>. An inline region is assigned its parent element's time interval as its active
+time interval. No <code>region</code> attribute makes reference to an inline region.</p></dd><dt class="label"><a id="terms-out-of-line-animation"></a>[out-of-line animation]</dt><dd><p>An <a href="#animation-vocabulary-animate"><code>animate</code></a> or <a href="#animation-vocabulary-set"><code>set</code></a> element that is defined out-of-line from
+the <a href="#terms-content-element">content element</a> or <a href="#layout-vocabulary-region"><code>region</code></a> element targetted by the animation.
+An out-of-line animation appears as a child of an <a href="#animation-vocabulary-animation"><code>animation</code></a> element in the header
+(<a href="#document-structure-vocabulary-head"><code>head</code></a> element)
+of a <a href="#terms-document-instance">document instance</a>, and specifies an <code>xlink:href</code> attribute
+that associates it with the element to be animated. There is a one-to-one relation between
+an out-of-line animation element and a <a href="#terms-content-element">content element</a> or
+<a href="#layout-vocabulary-region"><code>region</code></a> element.</p></dd><dt class="label"><a id="terms-out-of-line-region"></a>[out-of-line region]</dt><dd><p>A <a href="#layout-vocabulary-region"><code>region</code></a> element that is defined out-of-line from
+the <a href="#terms-content-element">content element(s)</a> to be selected into (targetted to) the region. An out-of-line region appears
+as a child of a <a href="#layout-vocabulary-layout"><code>layout</code></a> element in the header
+(<a href="#document-structure-vocabulary-head"><code>head</code></a> element)
+of a <a href="#terms-document-instance">document instance</a>, and specifies an <code>xml:id</code> attribute
+in order to allow <a href="#terms-content-element">content elements</a> to be associated with the region by means of a
<code>region</code> attribute. There is a one-to-many relationship between an out-of-line region
-and the <a href="#element-vocab-type-content">Content</a> element(s) to be selected into (targetted to) the region.</p></dd><dt class="label">Presentation Processor</dt><dd><p>A <em>Content Processor</em> which purpose is to layout, format, and render,
-i.e., to present, <em>Timed Text Markup Language</em> content by applying the presentation semantics
-defined in this specification.</p></dd><dt class="label">Processor</dt><dd><p>See <em>Content Processor</em>.</p></dd><dt class="label">Processor Profile</dt><dd><p>A collection of features and extensions that must or may be implemented (supported) by
-a content processor.</p><table border="1" class="ednote" summary="Editorial note: Processor Profile"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Processor Profile</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update and elaborate definition of processor profile based on new profiling mechanisms.</td></tr></table><p></p></dd><dt class="label">Profile Definition Document</dt><dd><p>A document that defines a specific collection of features and extensions
+and the <a href="#terms-content-element">content element(s)</a> to be selected into (targetted to) the region.</p></dd><dt class="label"><a id="terms-presentation-processor"></a>[presentation processor]</dt><dd><p>A <a href="#terms-content-processor">content processor</a> which purpose is to layout, format, and render,
+i.e., to present, <a href="#terms-timed-text-markup-language">Timed Text Markup Language</a> content by applying the presentation semantics
+defined in this specification.</p></dd><dt class="label"><a id="terms-processor"></a>[processor]</dt><dd><p>See <a href="#terms-content-processor">content processor</a>.</p></dd><dt class="label"><a id="terms-processor-profile"></a>[processor profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must or may be implemented (supported) by
+a content processor.</p><table border="1" class="ednote" summary="Editorial note: [processor profile]"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: [processor profile]</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update and elaborate definition of processor profile based on new profiling mechanisms.</td></tr></table><p></p></dd><dt class="label"><a id="terms-profile-definition-document"></a>[profile definition document]</dt><dd><p>A document that defines a specific collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a>
for which support is required or optional in a recipient content
-processor.</p></dd><dt class="label">Region</dt><dd><p>A logical construct that models authorial intention regarding
+processor.</p></dd><dt class="label"><a id="terms-region"></a>[region]</dt><dd><p>A logical construct that models authorial intention regarding
desired or potential presentation processing, and which is represented as
a rectangular area of a presentation surface into which content
-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 satisfies the
-constraints specify by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></dd><dt class="label">Related Media Object</dt><dd><p>A (possibly null) media object associated with or otherwise related
-to a <em>Document Instance</em>. For example, an aggregate audio/video media
-object for which a <em>Document Instance</em> provides caption or subtitle
-information, and with which that <em>Document Instance</em> is associated.</p></dd><dt class="label">Related Media Object Region</dt><dd><p>When a non-null <em>Related Media Object</em> exists, the region of this media object,
-expressed in the coordinate system that applies to the <em>Document Instance</em> that is associated with the
-related media object.</p></dd><dt class="label">Root Container Region</dt><dd><p>A logical region that establishes a coordinate system into which
-<em>Document Instance</em> content regions are placed and optionally clipped.</p></dd><dt class="label">Root Temporal Extent</dt><dd><p>
-The temporal extent (interval) defined by the temporal beginning and ending of a <em>Document Instance</em> in relationship with some external application or presentation context.
-</p></dd><dt class="label">SMPTE Time Code</dt><dd><p>A time code whose format and semantics are established by <a href="#smpte12m">[SMPTE 12M]</a>,
+is composed and rendered during presentation processing.</p></dd><dt class="label"><a id="terms-reduced-xml-infoset"></a>[reduced xml infoset]</dt><dd><p>An XML Information Set <a href="#infoset">[XML InfoSet]</a> that satisfies the
+constraints specify by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></dd><dt class="label"><a id="terms-related-media-object"></a>[related media object]</dt><dd><p>A (possibly null) media object associated with or otherwise related
+to a <a href="#terms-document-instance">document instance</a>. For example, an aggregate audio/video media
+object for which a <a href="#terms-document-instance">document instance</a> provides caption or subtitle
+information, and with which that <a href="#terms-document-instance">document instance</a> is associated.</p></dd><dt class="label"><a id="terms-related-media-object-region"></a>[related media object region]</dt><dd><p>When a non-null <a href="#terms-related-media-object">related media object</a> exists, the region of this media object,
+expressed in the coordinate system that applies to the <a href="#terms-document-instance">document instance</a> that is associated with the
+related media object.</p></dd><dt class="label"><a id="terms-root-container-region"></a>[root container region]</dt><dd><p>A logical region that establishes a coordinate system into which
+<a href="terms-content-region">content regions</a> are placed and optionally clipped.</p></dd><dt class="label"><a id="terms-root-temporal-extent"></a>[root temporal extent]</dt><dd><p>
+The temporal extent (interval) defined by the temporal beginning and ending of a <a href="#terms-document-instance">document instance</a> in relationship with some external application or presentation context.
+</p></dd><dt class="label"><a id="terms-smpte-time-code"></a>[smpte time code]</dt><dd><p>A time code whose format and semantics are established by <a href="#smpte12m">[SMPTE 12M]</a>,
which may be embedded into or otherwise associated with media content, such
-as a broadcast audio/video stream.</p></dd><dt class="label">Synthetic Document Syncbase</dt><dd><p>A document level <a href="http://www.w3.org/TR/2008/REC-SMIL3-20081201/smil30.html#smil-timing-q158">syncbase</a>
+as a broadcast audio/video stream.</p></dd><dt class="label"><a id="terms-synthetic-document-syncbase"></a>[synthetic document syncbase]</dt><dd><p>A document level <a href="http://www.w3.org/TR/2008/REC-SMIL3-20081201/smil30.html#smil-timing-q158">syncbase</a>
<a href="#smil3">[SMIL 3.0]</a>, § 5.7.1, synthesized or otherwise established by
-the <em>Document Processing Context</em> in accordance with the
-<em>Related Media Object</em> or other processing criteria.</p></dd><dt class="label">Synthetic SMPTE Document Syncbase</dt><dd><p>A <em>Synthetic Document Syncbase</em> constructed from <em>SMPTE Time
-Code</em> values embedded in or associated with the <em>Related Media Object</em> or
-otherwise determined by the <em>Document Processing Context</em>.</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 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 Markup Language content.</p></dd><dt class="label">Transformation Processor</dt><dd><p>A <em>Content Processor</em> which purpose is to transform or otherwise rewrite
-<em>Timed Text Markup Language</em> content to either <em>Timed Text Markup Language</em>
+the <a href="#terms-document-processing-context">document processing context</a> in accordance with the
+<a href="#terms-related-media-object">related media object</a> or other processing criteria.</p></dd><dt class="label"><a id="terms-synthetic-smpte-document-syncbase"></a>[synthetic smpte document syncbase]</dt><dd><p>A <a href="#terms-synthetic-document-syncbase">synthetic document syncbase</a> constructed from <a href="#terms-smpte-time-code">smpte time code</a>
+values embedded in or associated with the <a href="#terms-related-media-object">related media object</a> or
+otherwise determined by the <a href="#terms-document-processing-context">document processing context</a>.</p></dd><dt class="label"><a id="terms-timed-text"></a>[timed text]</dt><dd><p>Textual information that is intrinsically or extrinsically
+associated with timing information.</p></dd><dt class="label"><a id="terms-timed-text-markup-language"></a>[timed text markup language]</dt><dd><p>A content type that represents timed text media for the purpose of
+interchange among authoring systems.</p></dd><dt class="label"><a id="terms-timed-text-authoring-system"></a>[timed text authoring system]</dt><dd><p>A content authoring system capable of importing and exporting
+Timed Text Markup Language content.</p></dd><dt class="label"><a id="terms-transformation-processor"></a>[transformation processor]</dt><dd><p>A <a href="#terms-content-processor">content processor</a> which purpose is to transform or otherwise rewrite
+<a href="#terms-timed-text-markup-language">Timed Text Markup Language</a> content to either <a href="#terms-timed-text-markup-language">Timed Text Markup Language</a>
or to another (arbitrary) content format. An example of the first is a processor that removes
or rewrites TTML features so as to conform to a profile of TTML. An example of the latter is
a processor that translates TTML into a completely different timed text format. Because this
specification does not otherwise define a target profile or format for transformation processing,
-no further transformation semantics are defined by this specification.</p></dd><dt class="label">Valid Abstract Document Instance</dt><dd><p>An <em>Abstract Document Instance</em> which has been assessed for validity
+no further transformation semantics are defined by this specification.</p></dd><dt class="label"><a id="terms-valid-abstract-document-instance"></a>[valid abstract document instance]</dt><dd><p>An <a href="#terms-abstract-document-instance">abstract document instance</a> which has been assessed for validity
and found to be valid as defined by <a href="#doctypes"><b>4 Document Types</b></a>.</p></dd></dl></div><div class="div2">
<h3><a id="conventions"></a>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
@@ -735,7 +740,7 @@
information item has an enumerated type definition, the values are
shown separated by vertical bars, as for <code>size</code> above; if
there is a default value, it is shown following a colon. Where an
-attribute information item has a built-in simple type definition
+<a href="terms-attribute-information-item">attribute information item</a> has a built-in simple type definition
defined in <a href="#xsd-2">[XML Schema Part 2]</a>, a hyperlink to its definition
therein is given.</p><p>The allowed content of the information item is shown as a grammar
fragment, using the Kleene operators <code>?</code>, <code>*</code>
@@ -761,40 +766,40 @@
</td></tr></tbody></table></div></div><div class="div1">
<h2><a id="conformance"></a>3 Conformance</h2><p>This section specifies the general conformance requirements for
TTML Content and processors.</p><div class="div2">
-<h3><a id="conformance-content"></a>3.1 Content Conformance</h3><p>A TTML <em>Document Instance</em> conforms to this specification if the following criteria are
-satisfied:</p><ol class="enumar"><li><p>When transporting a <em>Document Instance</em> in a <em>Document Interchange Context</em> in which a
-Media Type <a href="#media-types">[Media Types]</a> identifies the content type of the interchanged <em>Document Instance</em>, then the specified media type is
+<h3><a id="conformance-content"></a>3.1 Content Conformance</h3><p>A TTML <a href="#terms-document-instance">document instance</a> conforms to this specification if the following criteria are
+satisfied:</p><ol class="enumar"><li><p>When transporting a <a href="#terms-document-instance">document instance</a> in a <a href="#terms-document-interchange-context">document interchange context</a> in which a
+Media Type <a href="#media-types">[Media Types]</a> identifies the content type of the interchanged <a href="#terms-document-instance">document instance</a>, then the specified media type is
<code>application/ttml+xml</code> in conformance with <a href="#xml-media">[XML Media Types]</a> § 7, with which an optional
<code>profile</code> parameter may appear, the value of which
conforms to
a profile designator as
defined by
-<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p></li><li><p>The <em>Document Instance</em> 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 <em>Document Instance</em> is or can
-be associated with one of the <em>Abstract Document Types</em> defined by
-<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The <em>Reduced XML Infoset</em> that corresponds to the <em>Document Instance</em> is a
-<em>Valid Abstract Document Instance</em> of the associated
-<em>Abstract Document Type</em>.</p></li><li><p>The <em>Reduced XML Infoset</em> satisfies all additional mandatory syntactic and
+<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p></li><li><p>The <a href="#terms-document-instance">document instance</a> is or can be represented as a <a href="#terms-reduced-xml-infoset">reduced xml infoset</a>
+as defined by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></li><li><p>The <a href="#terms-reduced-xml-infoset">reduced xml infoset</a> that
+corresponds to the <a href="#terms-document-instance">document instance</a> is or can
+be associated with one of the <a href="#terms-abstract-document-type">abstract document types</a> defined by
+<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The <a href="#terms-reduced-xml-infoset">reduced xml infoset</a> that corresponds to the <a href="#terms-document-instance">document instance</a> is a
+<a href="#terms-valid-abstract-document-instance">valid abstract document instance</a> of the associated
+<a href="#terms-abstract-document-type">abstract document type</a>.</p></li><li><p>The <a href="#terms-reduced-xml-infoset">reduced xml infoset</a> satisfies all additional mandatory syntactic and
semantic constraints defined by this specification. In addition, this Infoset
should satisfy the web content accessibility guidelines specified by
<a href="#wcag">[WCAG]</a>.</p></li></ol></div><div class="div2">
<h3><a id="conformance-processor"></a>3.2 Processor Conformance</h3><div class="div3">
-<h4><a id="conformance-generic-processor"></a>3.2.1 Generic Processor Conformance</h4><p>A TTML <em>Content Processor</em> conforms to this specification if the following
+<h4><a id="conformance-generic-processor"></a>3.2.1 Generic Processor Conformance</h4><p>A TTML <a href="#terms-content-processor">content processor</a> 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 <em>Document Instance</em>.</p></li><li><p>If a process does or can perform validation of a candidate
-<em>Document Instance</em>, then it provides at least one mechanism to
+instantiating a <a href="#terms-reduced-xml-infoset">reduced xml infoset</a>
+representation of a conformant <a href="#terms-document-instance">document instance</a>.</p></li><li><p>If a process does or can perform validation of a candidate
+<a href="#terms-document-instance">document instance</a>, then it provides at least one mechanism to
implicitly or explicitly associate the
-<em>Reduced XML Infoset</em> representation
-of a conformant <em>Document Instance</em> with one of the
+<a href="#terms-reduced-xml-infoset">reduced xml infoset</a> representation
+of a conformant <a href="#terms-document-instance">document instance</a> with one of the
<em>Abstract Document Types</em> 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 <em>Document Instance</em>
+processing of a conformant <a href="#terms-document-instance">document instance</a>
unless the processor does not support some required
(mandatory) feature specified or implied by a TTML profile
-declared to apply to the <em>Document Instance</em>.</p></li><li><p>The processor supports all mandatory processing semantics defined by this specification.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>mandatory semantics</em> refers to all explicit use of the conformance
+declared to apply to the <a href="#terms-document-instance">document instance</a>.</p></li><li><p>The processor supports all mandatory processing semantics defined by this specification.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>mandatory semantics</em> refers to all explicit use of the conformance
key phrases <span class="strong">must</span> and <span class="strong">must not</span> as well as any
declarative statement that can be reasonably inferred from such key phrases. For example, these
mandatory semantics include support for all features marked as mandatory in <a href="#feature-support"><b>D.2 Feature Support</b></a>.</p></div></li><li><p>If the processor supports some optional processing semantics defined by this specification,
@@ -803,23 +808,23 @@
<span class="strong">may</span>, and <span class="strong">may not</span>,
as well as any declarative statement that can be reasonably inferred from such key phrases. For example, these
optional semantics include support for all features marked as optional in <a href="#feature-support"><b>D.2 Feature Support</b></a>.</p></div></li></ol></div><div class="div3">
-<h4><a id="conformance-transformation-processor"></a>3.2.2 Transformation Processor Conformance</h4><p>A TTML <em>Content Processor</em> is a conformant TTML <em>Transformation Processor</em> if
+<h4><a id="conformance-transformation-processor"></a>3.2.2 Transformation Processor Conformance</h4><p>A TTML <a href="#terms-content-processor">content processor</a> is a conformant TTML <a href="#terms-transformation-processor">transformation processor</a> if
the following criteria are satisfied:</p><ol class="enumar"><li><p>The processor satisfies all requirements specified by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the 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 id="conformance-presentation-processor"></a>3.2.3 Presentation Processor Conformance</h4><p>A TTML <em>Content Processor</em> is a conformant TTML <em>Presentation Processor</em> if
+<h4><a id="conformance-presentation-processor"></a>3.2.3 Presentation Processor Conformance</h4><p>A TTML <a href="#terms-content-processor">content processor</a> is a conformant TTML <a href="#terms-presentation-processor">presentation processor</a> if
the following criteria are satisfied:</p><ol class="enumar"><li><p>The processor satisfies all requirements specified by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the 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 id="claims"></a>3.3 Claims</h3><p>Any claim of compliance with respect to the conformance of a TTML <em>Document Instance</em> or
-<em>Content Processor</em> must make
+<h3><a id="claims"></a>3.3 Claims</h3><p>Any claim of compliance with respect to the conformance of a TTML <a href="#terms-document-instance">document instance</a> or
+<a href="#terms-content-processor">content processor</a> must make
reference to an implementation compliance statement (ICS).</p><p>An implementation compliance statement must identify all mandatory
and optional features of this specification that are satisfied by the
document instance or the content processor implementation. In particular, the statement must
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 <em>Document Instance</em> for which a compliance claim is made
+or included in the subset or superset profile.</p><p>A <a href="#terms-document-instance">document instance</a> for which a compliance claim is made
must specify
either (1)
a <code>ttp:profile</code> attribute on its root
@@ -830,32 +835,32 @@
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 id="doctypes"></a>4 Document Types</h2><p>This section defines the following TTML <em>Abstract Document Types</em>:</p><ul><li><p><a href="#ttml-content-doctype"><b>4.1 TTML Content</b></a></p></li></ul><p>Each <em>Abstract Document Type</em> 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 <em>Abstract Document Instance</em> may be assessed in terms of validity,
-and is considered to be a <em>Valid Abstract Document Instance</em> if it
+<h2><a id="doctypes"></a>4 Document Types</h2><p>This section defines the following TTML <em>Abstract Document Types</em>:</p><ul><li><p><a href="#ttml-content-doctype"><b>4.1 TTML Content</b></a></p></li></ul><p>Each <a href="#terms-abstract-document-type">abstract document type</a> 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 <a href="#terms-abstract-document-instance">abstract document instance</a> may be assessed in terms of validity,
+and is considered to be a <a href="#terms-valid-abstract-document-instance">valid abstract document instance</a> if it
satisfies the following condition: if after</p><ol class="enumar"><li><p>pruning all element information
items whose names are not members of the collection of element types defined
-by the associated <em>Abstract Document Type</em>, then</p></li><li><p>pruning character
+by the associated <a href="#terms-abstract-document-type">abstract document type</a>, then</p></li><li><p>pruning character
information item children from any remaining element in case that all
character children of the element denote XML whitespace characters and the element's type
-is defined as empty in the associated <em>Abstract Document Type</em>, and then</p></li><li><p>pruning all attribute
+is defined as empty in the associated <a href="#terms-abstract-document-type">abstract document type</a>, and then</p></li><li><p>pruning all attribute
information items having expanded names such that the namespace URI of the
expanded names are not listed in <a href="#namespace-vocab-table"><b>Table 1 – Namespaces</b></a>,</p></li></ol><p>then the document element is one of the document
-element types permitted by the associated <em>Abstract Document Type</em>,
+element types permitted by the associated <a href="#terms-abstract-document-type">abstract document type</a>,
the descendants of the document
element satisfy their respective element type's content
specifications, all required attributes are present, and the declared
value of each attribute satisfies the type declared by the
-associated <em>Abstract Document Type</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a
-conformant <em>Document Instance</em>, a given <em>Document Instance</em> may be
+associated <a href="#terms-abstract-document-type">abstract document type</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a
+conformant <a href="#terms-document-instance">document instance</a>, a given <a href="#terms-document-instance">document instance</a> may be
constrained by the author or authoring tool to satisfy a more
restrictive definition of validity.</p></div><div class="div2">
-<h3><a id="ttml-content-doctype"></a>4.1 TTML Content</h3><p>TTML Content is an <em>Abstract Document Type</em> of a profile of the Timed Text Markup Language intended
+<h3><a id="ttml-content-doctype"></a>4.1 TTML Content</h3><p>TTML Content is an <a href="#terms-abstract-document-type">abstract document type</a> 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 references two types of schemas that may be used to validate a superset/subset
-of conformant TTML Content <em>Document Instances</em>:</p><ul><li><p><a href="#ttml-schema-rnc"><b>B.1 Relax NG Compact (RNC) Schema</b></a></p></li><li><p><a href="#ttml-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a TTML Content <em>Document Instance</em> must be a
+of conformant TTML Content <a href="#terms-document-instance">document instances</a>:</p><ul><li><p><a href="#ttml-schema-rnc"><b>B.1 Relax NG Compact (RNC) Schema</b></a></p></li><li><p><a href="#ttml-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a TTML Content <a href="#terms-document-instance">document instance</a> 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 referenced by this specification do not validate all syntactic constraints
defined by this specification, and, as such, represent a superset of conformant
TTML Content. In particular, performing validation with one of the above
@@ -868,10 +873,10 @@
a foreign namespace, thus representing a subset of conformant TTML Content. This is
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 <em>Document Instance</em> to be based on an <em>Abstract Document Instance</em> from
+formal validity of a <a href="#terms-document-instance">document instance</a> to be based on an <a href="#terms-abstract-document-instance">abstract document instance</a> 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 <em>Document Instance</em> validity.</p></div></div></div><div class="div1">
+of <a href="#terms-document-instance">document instance</a> validity.</p></div></div></div><div class="div1">
<h2><a id="vocabulary"></a>5 Vocabulary</h2><p>This section defines the
namespaces, profiles, and vocabulary (as an element and attribute
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">
@@ -879,7 +884,7 @@
XML Namespaces <a href="#xmlns10">[XML Namespaces 1.0]</a> 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
-normative URI that denotes each namespace.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In a specific <em>Document Instance</em>, it is not required that the default
+normative URI that denotes each namespace.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In a specific <a href="#terms-document-instance">document instance</a>, it is not required that the default
prefixes shown below are used. Any prefix or namespace binding that satisfies the constraints
of XML Namespaces <a href="#xmlns10">[XML Namespaces 1.0]</a> may be used that is associated with the specified namespace URI.</p></div><a id="namespace-vocab-table"></a><table class="common"><caption>Table 1 – Namespaces</caption><col width="30%" span="1"><col span="1"><col span="1"><tbody><tr><th>Name</th><th>Prefix</th><th>Value</th></tr><tr><td>TT</td><td><code>tt:</code></td><td><code>http://www.w3.org/ns/ttml</code></td></tr><tr><td>TT Parameter</td><td><code>ttp:</code></td><td><code>http://www.w3.org/ns/ttml#parameter</code></td></tr><tr><td>TT Style</td><td><code>tts:</code></td><td><code>http://www.w3.org/ns/ttml#styling</code></td></tr><tr><td>TT Metadata</td><td><code>ttm:</code></td><td><code>http://www.w3.org/ns/ttml#metadata</code></td></tr><tr><td>TT Profile</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/profile/</code></td></tr><tr><td>TT Feature</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/feature/</code></td></tr><tr><td>TT Extension</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/extension/</code></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If a reference to an element type is used in this specification and the name
of the element type is not namespace qualified, then the TT Namespace applies.</p><p>For certain namespaces defined above, the default prefix
@@ -909,10 +914,10 @@
would be
<code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>.</p></div><p>All profile designators which have the TT Profile Namespace as a prefix but are otherwise not listed in
<a href="#profile-vocab-table"><b>Table 2 – Profiles</b></a> are reserved for future standardization, and must not be appear in a conformant
-<em>Document Instance</em>. Nothwithstanding this constraint, 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 TTML <em>Profile Definition Document</em>
+<a href="#terms-document-instance">document instance</a>. Nothwithstanding this constraint, 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 TTML <a href="#terms-profile-definition-document">profile definition document</a>
provided it does not use the TT Profile Namespace as a prefix.</p><p>The profile of TTML that must be supported by a
-TTML <em>Content Processor</em> in order to process a <em>Document Instance</em> is determined either (1) by specifying a
+TTML <a href="#terms-content-processor">content processor</a> in order to process a <a href="#terms-document-instance">document instance</a> is determined 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
including one or more <code>ttp:profile</code>
@@ -921,10 +926,10 @@
descendant of the <code>tt</code> element, then the <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
attribute should not be specified on the <code>tt</code> element. If both
a <code>ttp:profile</code> element and a <code>ttp:profile</code>
-attribute are present (in a given <em>Document Instance</em>), then the
+attribute are present (in a given <a href="#terms-document-instance">document instance</a>), 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 <em>Document Instance</em>, then all specified profiles apply
+a <a href="#terms-document-instance">document instance</a>, then all specified profiles apply
simultaneously. In such a case, if some feature or some extension is
specified by one profile to be <code>used</code> (mandatory and enabled) and by
another profile to be <code>required</code> (mandatory) or <code>optional</code> (voluntary),
@@ -936,25 +941,26 @@
<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 <em>Document Instance</em>, and if the <em>Document
-Interchange Context</em> does not make an implicit or explicit
+element is present in a <a href="#terms-document-instance">document instance</a>, and if the <a href="#terms-document-interchange-context">document
+interchange context</a>
+does not make an implicit or explicit
reference to a pre-defined profile or does not specify a <em>Profile Definition
Document</em> or another equivalent set of feature designations,
-then the DFXP Transformation profile applies.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not a requirement on a conformant <em>Document Instance</em> that a profile be internally
+then the DFXP Transformation profile applies.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not a requirement on a conformant <a href="#terms-document-instance">document instance</a> that a profile be internally
defined by use of a <code>ttp:profile</code> element or internally referenced by a
-<code>ttp:profile</code> attribute. More specifically, it is permitted that the <em>Document
-Interchange Context</em> determines the applicable profile through private
+<code>ttp:profile</code> attribute. More specifically, it is permitted that the <a href="#terms-document-interchange-context">document
+interchange context</a> determines the applicable profile through private
agreement, out-of-band protocol, or common use (between sender and receiver) of a profile defined
by an external specification.</p></div><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
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 <em>Profile Definition Document</em>.
-However, it is not required that a conformant TTML Content Processor be able
+a URI that denotes an externally defined <a href="#terms-profile-definition-document">profile definition document</a>.
+However, it is not required that a conformant TTML <a href="#terms-content-processor">content processor</a> 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 <em>Document Instance</em> a non-standard profile definition
+wishes to include in the <a href="#terms-document-instance">document instance</a> a non-standard profile definition
not based upon one of the predefined profiles.</p><p>A predefined profile is supersetted by specifying some feature or extension to
be <code>required</code> (mandatory) that was either not specified in the underlying, baseline
profile or was specified as <code>optional</code> (voluntary) in the baseline profile.
@@ -964,13 +970,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 <em>Document Instance</em> makes use of a feature defined by
+and additive.</p></div><p>If a <a href="#terms-document-instance">document instance</a> 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 <em>Document Instance</em> makes use
+referenced profiles. If a <a href="#terms-document-instance">document instance</a> 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
@@ -1016,7 +1022,7 @@
<h4><a id="core-vocabulary-overview"></a>5.3.1 Core Catalog</h4><p>The core vocabulary catalog is intended to satisfy the needs of
TTML 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 <em>Document Instance</em> is enumerated in
+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 <a href="#terms-document-instance">document instance</a> is enumerated in
<a href="#element-vocab-table"><b>Table 3 – Element Vocabulary</b></a>.</p><a id="element-vocab-table"></a><table class="common"><caption>Table 3 – Element Vocabulary</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Module</th><th>Elements</th></tr><tr id="element-vocab-type-animation"><td>
Animation
</td><td>
@@ -1177,10 +1183,10 @@
<h4><a id="extension-vocabulary-overview"></a>5.3.2 Extension Catalog</h4><p>The extension vocabulary catalog is intended for use by future
profiles of TTML, and is not further defined
by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming
-<em>Document Instance</em> may contain arbitrary namespace qualified
+<a href="#terms-document-instance">document instance</a> may contain arbitrary namespace qualified
elements that reside in any namespace other than those namespaces
defined for use with this specification. Furthermore, a conforming
-<em>Document Instance</em> may contain arbitrary namespace qualified
+<a href="#terms-document-instance">document instance</a> 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">
@@ -1189,20 +1195,20 @@
parameters are to be understood as information that is either (1)
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 <em>Document Processing Context</em> by means
+core vocabulary items or for establishing a <a href="#terms-document-processing-context">document processing context</a> by means
of which TTML Content can be related to an external environment.</p><div class="div2">
<h3><a id="parameter-element-vocabulary"></a>6.1 Parameter Element Vocabulary</h3><p>The following elements, all defined in the TT Parameter
-Namespace, specify parametric information that applies to a <em>Document Instance</em>
-or <em>Content Processor</em>:</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">
+Namespace, specify parametric information that applies to a <a href="#terms-document-instance">document instance</a>
+or <a href="#terms-content-processor">content processor</a>:</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 id="parameter-vocabulary-profile"></a>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 <em>Content Processor</em> in order to process a
-<em>Document Instance</em> that makes (or may make) use of such features and
+may be supported by a <a href="#terms-content-processor">content processor</a> in order to process a
+<a href="#terms-document-instance">document instance</a> that makes (or may make) use of such features and
extensions. In addition, a feature or extension may be specified as
prohibited, in which case it must not appear (be specified) in
-a <em>Document Instance</em>, and, if it does appear, may result in
-the <em>Document Instance</em> being rejected or processing otherwise aborted.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The difference between a <em>feature</em> and an
+a <a href="#terms-document-instance">document instance</a>, and, if it does appear, may result in
+the <a href="#terms-document-instance">document instance</a> being rejected or processing otherwise aborted.</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
labeled with a feature designation in <a href="#features"><b>D Features</b></a>, then
@@ -1210,15 +1216,15 @@
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 TTML <em>Document Instance</em>;</p></li><li><p>as the root element of a TTML <em>Profile Definition Document</em>
-instance;</p></li></ul><p>When a <code>tt:profile</code> element appears within a TTML <em>Document Instance</em>,
+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 <a href="#terms-document-instance">document instance</a>;</p></li><li><p>as the root element of a TTML <a href="#terms-profile-definition-document">profile definition document</a>
+instance;</p></li></ul><p>When a <code>tt:profile</code> element appears within a TTML <a href="#terms-document-instance">document instance</a>,
its purpose is to express authorial intentions about which
features and extensions must or may be supported by a recipient
content processor, as well as which features and extensions must
-not be included or otherwise used in a <em>Document Instance</em>.
+not be included or otherwise used in a <a href="#terms-document-instance">document instance</a>.
In addition, the element indirectly expresses
information about the set of features or extensions that are (or may
-expected to be) used by the <em>Document Instance</em>.</p><p>When a <code>tt:profile</code> element is used by a TTML <em>Profile Definition Document</em> instance,
+expected to be) used by the <a href="#terms-document-instance">document instance</a>.</p><p>When a <code>tt:profile</code> element is used by a TTML <a href="#terms-profile-definition-document">profile definition document</a> instance,
it serves to publish a machine
readable specification of a specific TTML profile, of which
this specification defines three such <em>Profile Definition Documents</em> in
@@ -1240,7 +1246,7 @@
§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
-<em>Profile Definition Document</em> as defined by <a href="#profiles"><b>F Profiles</b></a>,
+<a href="#terms-profile-definition-document">profile definition document</a> as defined by <a href="#profiles"><b>F Profiles</b></a>,
or (2) a feasibly dereferenceable resource representing a valid <em>Profile Definition
Document</em> 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
@@ -1266,17 +1272,17 @@
and extensions of the profile, where merging a feature or extension
entails applying the combination method in accordance with the specified
(or default) <code>combine</code> attribute value.</p></li></ol><p>A conformant TTML processor is not required to be able to
-dereference a <em>Profile Definition Document</em> that is not one of the
+dereference a <a href="#terms-profile-definition-document">profile definition document</a> that is not one of the
standard, predefined profiles defined by <a href="#profiles"><b>F Profiles</b></a>. Furthermore,
a 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 TTML processor is unable to dereference a non-standard
-<em>Profile Definition Document</em>, then it must not further process the
+<a href="#terms-profile-definition-document">profile definition document</a>, 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 TTML processor aborts
-processing of a <em>Document Instance</em> due to the inability to
-reference a non-standard <em>Profile Definition Document</em>, then some
+processing of a <a href="#terms-document-instance">document instance</a> due to the inability to
+reference a non-standard <a href="#terms-profile-definition-document">profile definition document</a>, 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><a id="parameter-vocabulary-profile-example-1"></a><table class="example"><caption>Example Fragment – ttp:profile</caption><tbody><tr><td>
@@ -1316,7 +1322,7 @@
by child <code>ttp:feature</code> elements.</p></div><div class="div3">
<h4><a id="parameter-vocabulary-feature"></a>6.1.3 ttp:feature</h4><p>The <code>ttp:feature</code> element is used to specify
infomation about support and usage requirements for a particular feature.</p><p>The children of the <code>ttp:feature</code> element must express a non-empty
-sequence of character information items that adheres to the
+sequence of <a href="terms-character-information-item">character information items</a> that adheres to the
<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
§3.2.17.</p><a id="elt-syntax-parameter-feature"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:feature</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -1343,7 +1349,7 @@
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 (1) whether a conforming TTML
processor must or may implement the designated feature in order to
-process the document, or (2) whether a TTML <em>Document Instance</em>
+process the document, or (2) whether a TTML <a href="#terms-document-instance">document instance</a>
must not include or otherwise use the designated feature.
If the value of the <code>value</code> attribute
is <code>optional</code>, then the processor need
@@ -1369,12 +1375,12 @@
<code>use</code> and the TTML processor implementation supports but has disabled
that feature,
or if the <code>value</code> attribute is <code>prohibited</code> and a
-<em>Document Instance</em> includes or makes use of the feature,
+<a href="#terms-document-instance">document instance</a> includes or makes use of 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 TTML processor aborts
-processing of a <em>Document Instance</em> due to the specification of a
+processing of a <a href="#terms-document-instance">document instance</a> due to the specification of a
required, but unsupported feature by this element, or due to the presence
or use of a prohibited feature, then some end-user
notification should be given unless the end-user or system has
@@ -1393,7 +1399,7 @@
otherwise valid.</p><p>If some defined (i.e., standardized) or otherwise well known feature is not specified by
a <code>ttp:feature</code> element in a given profile, then it must be interpreted as if the feature were specified
with the <code>value</code> attribute equal to <code>optional</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In particular, if some feature is not present in a profile definition, then
-it is not to be interpreted as meaning the use of that feature (in a <em>Document Instance</em>)
+it is not to be interpreted as meaning the use of that feature (in a <a href="#terms-document-instance">document instance</a>)
is disallowed or otherwise prohibited. If a feature is intended to be disallowed by a profile, then
it should be specified using the <code>prohibited</code> value.</p></div><p>The <code>ttp:feature</code> element is illustrated by the following example.</p><a id="parameter-vocabulary-feature-example-1"></a><table class="example"><caption>Example Fragment – ttp:feature</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -1440,7 +1446,7 @@
by child <code>ttp:extension</code> elements.</p></div><div class="div3">
<h4><a id="parameter-vocabulary-extension"></a>6.1.5 ttp:extension</h4><p>The <code>ttp:extension</code> element is used to specify
infomation about support and usage requirements for a particular extension.</p><p>The children of the <code>ttp:extension</code> element must express a non-empty
-sequence of character information items that adheres to the
+sequence of <a href="terms-character-information-item">character information items</a> that adheres to the
<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
§3.2.17.</p><a id="elt-syntax-parameter-extension"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:extension</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -1464,7 +1470,7 @@
<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 (1) whether a conforming TTML
processor must or may implement the designated extension in order to
-process the document, or (2) whether a TTML <em>Document Instance</em>
+process the document, or (2) whether a TTML <a href="#terms-document-instance">document instance</a>
must not include or otherwise use the designated extension.
If the value of the <code>value</code> attribute
is <code>optional</code>, then the processor need
@@ -1490,7 +1496,7 @@
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 TTML processor aborts
-processing of a <em>Document Instance</em> due to the specification of a
+processing of a <a href="#terms-document-instance">document instance</a> 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
@@ -1508,7 +1514,7 @@
otherwise valid.</p><p>If some well known extension is not specified by
a <code>ttp:extension</code> element in a given profile, then it must be interpreted as if the extension were specified
with the <code>value</code> attribute equal to <code>optional</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In particular, if some extension is not present in a profile definition, then
-it is not to be interpreted as meaning the use of that extension (in a <em>Document Instance</em>)
+it is not to be interpreted as meaning the use of that extension (in a <a href="#terms-document-instance">document instance</a>)
is disallowed or otherwise prohibited. If an extension is intended to be disallowed by a profile, then
it should be specified using the <code>prohibited</code> value.</p></div><p>The <code>ttp:extension</code> element is illustrated by the following example.</p><a id="parameter-vocabulary-extension-example-1"></a><table class="example"><caption>Example Fragment – ttp:extension</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -1528,7 +1534,7 @@
appear between adjacent non-terminal components of a TT Parameter value
unless some other delimiter is permitted and used.</p><div class="div3">
<h4><a id="parameter-attribute-cellResolution"></a>6.2.1 ttp:cellResolution</h4><p>The <code>ttp:cellResolution</code> attribute may be used by an author
-to express the number of horizontal and vertical cells into which the <em>Root Container Region</em>
+to express the number of horizontal and vertical cells into which the <a href="#terms-root-container-region">root container region</a>
area is divided for the purpose of expressing presentation semantics in terms of
a uniform grid.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-cellResolution-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:cellResolution</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -1550,7 +1556,7 @@
matches the cell size.</p></div><p>Except where indicated otherwise, when a <a href="#style-value-length"><length></a> expressed in
cells denotes a dimension parallel to the inline or block progression dimension,
the cell's dimension in the inline or block progression dimension applies, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>For example, if padding (on all four edges) is specified as 0.1c, the cell resolution
-is 20 by 10, and the extent of the <em>Root Container Region</em> is 640 by 480, then, assuming top to bottom,
+is 20 by 10, and the extent of the <a href="#terms-root-container-region">root container region</a> is 640 by 480, then, assuming top to bottom,
left to right writing mode, the start and end padding will be (640 / 20) * 0.1 pixels and the
before and after padding will be (480 / 10) * 0.1 pixels.</p></div></div><div class="div3">
<h4><a id="parameter-attribute-clockMode"></a>6.2.2 ttp:clockMode</h4><p>The <code>ttp:clockMode</code> attribute is used to specify the
@@ -1640,13 +1646,13 @@
frames/second. The M/PAL system is used primarily in Brazil.</p></div><p>If not specified, then <code>nonDrop</code> must be assumed to apply.</p><p>A <code>ttp:dropMode</code> attribute is considered to be significant only
when specified on the <code>tt</code> element.</p></div><div class="div3">
<h4><a id="parameter-attribute-frameRate"></a>6.2.4 ttp:frameRate</h4><p>The <code>ttp:frameRate</code> attribute is used to specify the frame rate of a related
-media object or the intrinsic frame rate of a <em>Document Instance</em> in case it is intended
+media object or the intrinsic frame rate of a <a href="#terms-document-instance">document instance</a> in case it is intended
to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-frameRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:frameRate</caption><tbody><tr><td>
<div class="exampleInner"><pre>
ttp:frameRate
: <a href="#style-value-digit"><digit></a>+ // <em>value</em> > 0
</pre></div>
-</td></tr></tbody></table><p>The frame rate that applies to a <em>Document Instance</em> is used to
+</td></tr></tbody></table><p>The frame rate that applies to a <a href="#terms-document-instance">document instance</a> is used to
interpret time expressions that are expressed in <em>frames</em>
as defined by <a href="#timing-value-timeExpression"><b>10.3.1 <timeExpression></b></a>.</p><p>If the <code>media</code> time base applies and the effective frame rate is
integral, then a frame is interpreted as a division of a second of media
@@ -1709,18 +1715,18 @@
expressions may be converted to real time
coordinates by taking into account the computed frame rate
and drop mode as expressed by the <code>ttp:dropMode</code> parameter.
-In this case, the <em>Content Processor</em> must create and maintain a
-<em>Synthetic SMPTE Document Syncbase</em> within which these time
+In this case, the <a href="#terms-content-processor">content processor</a> must create and maintain a
+<a href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</a> within which these time
expressions are interpreted as further described in
<a href="#timing-time-intervals"><b>10.4 Time Intervals</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When operating with <code>smpte</code> time base and
<code>continuous</code> marker mode, there is an implied time coordinate
-space, the <em>Synthetic SMPTE Document Syncbase</em>,
+space, the <a href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</a>,
defined by the monotonically increasing (or decreasing)
<a href="#smpte12m">[SMPTE 12M]</a> time coordinates, while taking into account
the computed frame rate and drop mode. All time expressions are interpreted
in relationship to this time coordinate space based upon
-<em>SMPTE Time Code</em> synchronization events (markers),
-where the <em>Document Processing Context</em> emits these events with implied constraints
+<a href="#terms-smpte-time-code">smpte time code</a> synchronization events (markers),
+where the <a href="#terms-document-processing-context">document processing context</a> emits these events with implied constraints
regarding time coordinate monoticity and resynchronization in
the presence of dropped frames.</p><p>Use of <code>continuous</code> marker mode with the <code>smpte</code>
time base is different from using the <code>media</code> time base
@@ -1735,7 +1741,7 @@
expression of a duration must be considered to be invalid.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When operating with <code>smpte</code> time base and
<code>discontinuous</code> marker mode, there is no effective time coordinate
space; rather, all time expressions are interpreted as labeled
-synchronization events (markers), where the <em>Document Processing Context</em>
+synchronization events (markers), where the <a href="#terms-document-processing-context">document processing context</a>
emits these events, which, when they correspond with time
expressions that denote the same label, cause a temporal interval to
begin or end accordingly.</p><p>An additional side-effect of operating in <code>discontinuous</code>
@@ -1771,7 +1777,7 @@
ratios while still maintaining authorial layout intentions.</p></div></div><div class="div3">
<h4><a id="parameter-attribute-profile"></a>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 Markup Language (TTML) used
-in a <em>Document Instance</em>.</p><p>If specified, the value of this attribute must adhere to the
+in a <a href="#terms-document-instance">document instance</a>.</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
profile designator in accordance with
@@ -1779,13 +1785,13 @@
attribute is considered to be significant only when specified on the
<code>tt</code> element.</p></div><div class="div3">
<h4><a id="parameter-attribute-subFrameRate"></a>6.2.9 ttp:subFrameRate</h4><p>The <code>ttp:subFrameRate</code> attribute is used to specify the sub-frame rate of a related
-media object or the intrinsic sub-frame rate of a <em>Document Instance</em> in case it is intended
+media object or the intrinsic sub-frame rate of a <a href="#terms-document-instance">document instance</a> in case it is intended
to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-subFrameRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:subFrameRate</caption><tbody><tr><td>
<div class="exampleInner"><pre>
ttp:subFrameRate
: <a href="#style-value-digit"><digit></a>+ // <em>value</em> > 0
</pre></div>
-</td></tr></tbody></table><p>The sub-frame rate that applies to a <em>Document Instance</em> is used to
+</td></tr></tbody></table><p>The sub-frame rate that applies to a <a href="#terms-document-instance">document instance</a> is used to
interpret time expressions that are expressed in <em>sub-frames</em>
as defined by <a href="#timing-value-timeExpression"><b>10.3.1 <timeExpression></b></a>.</p><p>If the <code>media</code> time base applies and the effective frame rate is
integral, a sub-frame is interpreted as a division of a frame of media
@@ -1798,13 +1804,13 @@
when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The sub-frame is sometimes referred to as a <em>field</em> in
the context of synchronization with an interlaced video media object.</p></div></div><div class="div3">
<h4><a id="parameter-attribute-tickRate"></a>6.2.10 ttp:tickRate</h4><p>The <code>ttp:tickRate</code> attribute is used to specify the tick rate of a related
-media object or the intrinsic tick rate of content of a <em>Document Instance</em> in case it is intended
+media object or the intrinsic tick rate of content of a <a href="#terms-document-instance">document instance</a> in case it is intended
to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-tickRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:tickRate</caption><tbody><tr><td>
<div class="exampleInner"><pre>
ttp:tickRate
: <a href="#style-value-digit"><digit></a>+ // <em>value</em> > 0
</pre></div>
-</td></tr></tbody></table><p>The tick rate that applies to a <em>Document Instance</em> is used to
+</td></tr></tbody></table><p>The tick rate that applies to a <a href="#terms-document-instance">document instance</a> is used to
interpret time expressions that are expressed in <em>ticks</em> by
using the <code>t</code> metric as defined by <a href="#timing-value-timeExpression"><b>10.3.1 <timeExpression></b></a>.</p><p>If the <code>media</code> time base applies,
a tick is interpreted as an integral division of a second of media
@@ -1824,7 +1830,7 @@
when specified on the <code>tt</code> element.</p></div><div class="div3">
<h4><a id="parameter-attribute-timeBase"></a>6.2.11 ttp:timeBase</h4><p>The <code>ttp:timeBase</code> attribute is used to specify the
temporal coordinate system by means of which time expressions are
-interpreted in a <em>Document Instance</em>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-timeBase-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:timeBase</caption><tbody><tr><td>
+interpreted in a <a href="#terms-document-instance">document instance</a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-timeBase-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:timeBase</caption><tbody><tr><td>
<div class="exampleInner"><pre>
ttp:timeBase
: "media"
@@ -1834,8 +1840,8 @@
</td></tr></tbody></table><p>If the time base is designated as <code>media</code>, then a time
expression denotes a coordinate in some media object's time line,
where the media object may be an external media object with which the
-content of a <em>Document Instance</em> is to be synchronized, or it may
-be the content of a <em>Document Instance</em> itself in a case where
+content of a <a href="#terms-document-instance">document instance</a> is to be synchronized, or it may
+be the content of a <a href="#terms-document-instance">document instance</a> itself in a case where
the timed text content is intended to establish an independent time
line.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When using a media time base, if that time base is paused or
scaled positively or negatively, i.e., the media play rate is
@@ -1845,7 +1851,7 @@
controlling an external
media time base is outside the scope of this specification.</p></div><p>If the time base is designated as <code>smpte</code>,
then a time expression denotes a <a href="#smpte12m">[SMPTE 12M]</a> time
-coordinate with which the content of a <em>Document Instance</em> is to
+coordinate with which the content of a <a href="#terms-document-instance">document instance</a> is to
be synchronized. In this case, the value of the <code>ttp:markerMode</code>
and <code>ttp:dropMode</code> parameters apply, as defined by <a href="#parameter-attribute-markerMode"><b>6.2.6 ttp:markerMode</b></a> and <a href="#parameter-attribute-dropMode"><b>6.2.3 ttp:dropMode</b></a>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When the time base is designated as <code>smpte</code>,
every time expression denotes a media marker value akin to that
@@ -1858,21 +1864,21 @@
time lines.</p><p>If not specified, the default time base must be considered to be
<code>media</code>.</p><p>A <code>ttp:timeBase</code> attribute is considered to be significant only
when specified on the <code>tt</code> element.</p><p>When operating with either <code>media</code> or <code>smpte</code>
-time bases, a diachronic presentation of a <em>Document Instance</em> may
+time bases, a diachronic presentation of a <a href="#terms-document-instance">document instance</a> may
be subject to transformations of the controlling time line, such as
temporal reversal, dilation (expansion), or constriction
(compression); however, when operating with the <code>clock</code>
time base, no transformations are permitted, and diachronic
presentation proceeds on a linear, monotonically increasing time line
based on the passage of real time.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Due to there being only one time base parameter that applies to a
-given <em>Document Instance</em>, the interpretation of time expressions
-is uniform throughout the <em>Document Instance</em>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#time-expression-semantics"><b>N Time Expression Semantics</b></a> for further details
+given <a href="#terms-document-instance">document instance</a>, the interpretation of time expressions
+is uniform throughout the <a href="#terms-document-instance">document instance</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#time-expression-semantics"><b>N Time Expression Semantics</b></a> for further details
on the interpretation of time expressions according to the designated time base.</p></div></div></div></div><div class="div1">
<h2><a id="content"></a>7 Content</h2><p>This section specifies the <em>content</em> matter of the core
vocabulary catalog.</p><div class="div2">
<h3><a id="content-element-vocabulary"></a>7.1 Content Element Vocabulary</h3><p>The following elements specify the structure and principal content aspects of a
-<em>Document Instance</em>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a></p></li><li><p><a href="#document-structure-vocabulary-head"><b>7.1.2 head</b></a></p></li><li><p><a href="#document-structure-vocabulary-body"><b>7.1.3 body</b></a></p></li><li><p><a href="#content-vocabulary-div"><b>7.1.4 div</b></a></p></li><li><p><a href="#content-vocabulary-p"><b>7.1.5 p</b></a></p></li><li><p><a href="#content-vocabulary-span"><b>7.1.6 span</b></a></p></li><li><p><a href="#content-vocabulary-br"><b>7.1.7 br</b></a></p></li></ul><div class="div3">
-<h4><a id="document-structure-vocabulary-tt"></a>7.1.1 tt</h4><p>The <code>tt</code> element serves as the root document element of a <em>Document Instance</em>.</p><p>The <code>tt</code> element accepts as its children zero or one <code>head</code> element followed by
+<a href="#terms-document-instance">document instance</a>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a></p></li><li><p><a href="#document-structure-vocabulary-head"><b>7.1.2 head</b></a></p></li><li><p><a href="#document-structure-vocabulary-body"><b>7.1.3 body</b></a></p></li><li><p><a href="#content-vocabulary-div"><b>7.1.4 div</b></a></p></li><li><p><a href="#content-vocabulary-p"><b>7.1.5 p</b></a></p></li><li><p><a href="#content-vocabulary-span"><b>7.1.6 span</b></a></p></li><li><p><a href="#content-vocabulary-br"><b>7.1.7 br</b></a></p></li></ul><div class="div3">
+<h4><a id="document-structure-vocabulary-tt"></a>7.1.1 tt</h4><p>The <code>tt</code> element serves as the root document element of a <a href="#terms-document-instance">document instance</a>.</p><p>The <code>tt</code> element accepts as its children zero or one <code>head</code> element followed by
zero or one <code>body</code> element.</p><a id="elt-syntax-tt"></a><table class="syntax"><caption>XML Representation – Element Information Item: tt</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<tt
@@ -1885,23 +1891,23 @@
<em>Content:</em> <a href="#document-structure-vocabulary-head">head</a>?, <a href="#document-structure-vocabulary-body">body</a>?
</tt>
</pre></div>
-</td></tr></tbody></table><p>The <em>Root Temporal Extent</em>, i.e., the time interval over which a <em>Document Instance</em> is active, has an implicit duration that is equal to the
+</td></tr></tbody></table><p>The <a href="#terms-root-temporal-extent">root temporal extent</a>, i.e., the time interval over which a <a href="#terms-document-instance">document instance</a> is active, has an implicit duration that is equal to the
implicit duration of the <code>body</code> element of the document, if the <code>body</code> element is present, or zero, if the <code>body</code> element is absent.</p><p>If the <code>tts:extent</code> attribute is specified on the <code>tt</code>
element, then it must adhere to <a href="#style-attribute-extent"><b>8.2.8 tts:extent</b></a>, in which case it
-specifies the spatial extent of the <em>Root Container Region</em> in
-which content regions are located and presented. If no <code>tts:extent</code>
-attribute is specified, then the spatial extent of the <em>Root Container Region</em> is
-considered to be determined by the <em>Document Processing Context</em>.
-The origin of the <em>Root Container Region</em> is determined by the <em>Document Processing Context</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In the absence of other requirements, and if a <em>Related Media Object</em> exists, then it is recommended
-that the <em>Document Processing Context</em> determine that:</p><ul><li><p>if no <code>tts:extent</code> is specified on the root <code>tt</code> element, the extent of the <em>Root Container Region</em> be
-established as equal to the extent of the <em>Related Media Object Region</em>; and</p></li><li><p>the origin of the <em>Root Container Region</em> be established so that this region is centered in the
-<em>Related Media Object Region</em>.</p></li></ul></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If an author desires to signal the (storage or image) aspect ratio of the <em>Root Container Region</em>
+specifies the spatial extent of the <a href="#terms-root-container-region">root container region</a> in
+which <a href="terms-content-region">content regions</a> are located and presented. If no <code>tts:extent</code>
+attribute is specified, then the spatial extent of the <a href="#terms-root-container-region">root container region</a> is
+considered to be determined by the <a href="#terms-document-processing-context">document processing context</a>.
+The origin of the <a href="#terms-root-container-region">root container region</a> is determined by the <a href="#terms-document-processing-context">document processing context</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In the absence of other requirements, and if a <a href="#terms-related-media-object">related media object</a> exists, then it is recommended
+that the <a href="#terms-document-processing-context">document processing context</a> determine that:</p><ul><li><p>if no <code>tts:extent</code> is specified on the root <code>tt</code> element, the extent of the <a href="#terms-root-container-region">root container region</a> be
+established as equal to the extent of the <a href="#terms-related-media-object-region">related media object region</a>; and</p></li><li><p>the origin of the <a href="#terms-root-container-region">root container region</a> be established so that this region is centered in the
+<a href="#terms-related-media-object-region">related media object region</a>.</p></li></ul></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If an author desires to signal the (storage or image) aspect ratio of the <a href="#terms-root-container-region">root container region</a>
without specifying its resolution, then this may be accomplished by using metadata specified
in an external namespace, such as <code>m708:aspectRatio</code> as defined in <a href="#smpte2052">[SMPTE 2052-11]</a>, §5.4.4.
This would permit, for example, the interchange of information that reflects the
the semantics of <a href="#cea708e">[CEA-708-E]</a> , §4.5 “Caption Service Metadata”, “ASPECT RATIO”.</p></div><p>An <code>xml:lang</code> attribute must be specified on the <code>tt</code> element.
If the attribute value is empty, it signifies that there is no default language that applies
-to the text contained within the <em>Document Instance</em>.</p><p>If no <code>xml:space</code> attribute is specified upon the <code>tt</code> element, then it must
+to the text contained within the <a href="#terms-document-instance">document instance</a>.</p><p>If no <code>xml:space</code> attribute is specified upon the <code>tt</code> element, then it must
be considered as if the attribute had been specified with a value of <code>default</code>.</p></div><div class="div3">
<h4><a id="document-structure-vocabulary-head"></a>7.1.2 head</h4><p>The <code>head</code> element is a container element used to group
header matter, including metadata,
@@ -1912,14 +1918,14 @@
followed by zero or one <code>styling</code> element,
followed by zero or one <code>layout</code> element,
followed by zero or one <code>animation</code> element.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the <em>Document Instance</em> as a
+element group applies semantically to the <a href="#terms-document-instance">document instance</a> as a
whole, and not just the <code>head</code> element.</p><p>Any parameters specified by children in the <code>Parameters.class</code>
-element group applies semantically to the <em>Document Instance</em> as a
+element group applies semantically to the <a href="#terms-document-instance">document instance</a> as a
whole, and not just the <code>head</code> element.</p><p>A <code>styling</code> child element is used to specify style constructs
that are referenced from other style constructs, by layout constructs, and by
-<a href="#element-vocab-type-content">Content</a> elements.</p><p>A <code>layout</code> child element is used to specify layout constructs that
-are referenced by <a href="#element-vocab-type-content">Content</a> elements.</p><p>An <code>animation</code> child element is used to specify animation constructs that
-target animatable <a href="#element-vocab-type-content">Content</a>
+<a href="#terms-content-element">content elements</a>.</p><p>A <code>layout</code> child element is used to specify layout constructs that
+are referenced by <a href="#terms-content-element">content elements</a>.</p><p>An <code>animation</code> child element is used to specify animation constructs that
+target animatable <a href="#terms-content-element">content element</a>
or <a href="#element-vocab-type-layout">Layout</a> elements.</p><a id="elt-syntax-head"></a><table class="syntax"><caption>XML Representation – Element Information Item: head</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<head
@@ -1932,7 +1938,7 @@
</pre></div>
</td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
<code>head</code> element, the implied time interval of this element is
-defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
+defined to be coterminous with the <a href="#terms-root-temporal-extent">root temporal extent</a>.</p></div><div class="div3">
<h4><a id="document-structure-vocabulary-body"></a>7.1.3 body</h4><p>The <code>body</code> element functions as a logical container and a temporal
structuring element for a sequence of textual content units represented as
logical divisions.</p><p>The <code>body</code> element accepts as its children zero or more
@@ -1963,18 +1969,18 @@
</td></tr></tbody></table><p>An author may specify a temporal interval for a <code>body</code> element using
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 beginning
-point of the <em>Root Temporal Extent</em>. Similarly, if the end point of this interval remains unspecified, then the
-end point is interpreted as the ending point of the <em>Root Temporal Extent</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <em>Document Instance</em> referenced from a SMIL presentation
+point of the <a href="#terms-root-temporal-extent">root temporal extent</a>. Similarly, if the end point of this interval remains unspecified, then the
+end point is interpreted as the ending point of the <a href="#terms-root-temporal-extent">root temporal extent</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <a href="#terms-document-instance">document instance</a> 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 beginning and
-ending time of the <em>Root Temporal Extent</em>.</p><p>If the <em>Root Temporal Extent</em> is shorter than the computed duration of the
+ending time of the <a href="#terms-root-temporal-extent">root temporal extent</a>.</p><p>If the <a href="#terms-root-temporal-extent">root temporal extent</a> is shorter than the computed duration of the
<code>body</code> element, then the active time interval of a <code>body</code> element is
-truncated to the active end point of the <em>Root Temporal Extent</em>.</p><p>An author may associate a set of style properties with a
+truncated to the active end point of the <a href="#terms-root-temporal-extent">root temporal extent</a>.</p><p>An author may associate a set of style properties with a
<code>body</code> element by means of either the <code>style</code>
attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>body</code> element
-in a <em>Document Instance</em> are available for style inheritance by
-descendant <a href="#element-vocab-type-content">Content</a> elements such as <code>div</code>, <code>p</code>,
+in a <a href="#terms-document-instance">document instance</a> are available for style inheritance by
+descendant <a href="#terms-content-element">content elements</a> such as <code>div</code>, <code>p</code>,
<code>span</code>
and <code>br</code>.</p></div><p>If no <code>timeContainer</code> attribute is specified on a
<code>body</code> element, then it must be interpreted as having
@@ -2024,8 +2030,8 @@
</td></tr></tbody></table><p>An author may associate a set of style properties with a <code>div</code> element by means of either
the <code>style</code> attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated
with
-a <code>div</code> element in a <em>Document Instance</em>
-are available for style inheritance by descendant <a href="#element-vocab-type-content">Content</a> elements such as
+a <code>div</code> element in a <a href="#terms-document-instance">document instance</a>
+are available for style inheritance by descendant <a href="#terms-content-element">content elements</a> such as
<code>div</code>,
<code>p</code>,
<code>span</code>, and
@@ -2066,12 +2072,12 @@
</td></tr></tbody></table><p>An author may associate a set of style properties with a
<code>p</code> element by means of either the <code>style</code>
attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>p</code> element
-in a <em>Document Instance</em> are available for style inheritance by
-descendant <a href="#element-vocab-type-content">Content</a> elements such as <code>span</code> and
+in a <a href="#terms-document-instance">document instance</a> are available for style inheritance by
+descendant <a href="#terms-content-element">content elements</a> such as <code>span</code> and
<code>br</code>.</p></div><p>If no <code>timeContainer</code> attribute is specified on
a <code>p</code> element, then it must be interpreted as having
<em>parallel</em> time containment semantics.</p><p>If a sequence of children of a <code>p</code> element
-consists solely of character information items, then that sequence must
+consists solely of <a href="terms-character-information-item">character information items</a>, then that sequence must
be considered to be an <em>anonymous span</em> for the purpose of
applying style properties that apply to <code>span</code> elements.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The presentation semantics of TTML effectively
implies that a <code>p</code> element constitutes a line break. In particular,
@@ -2112,8 +2118,8 @@
</td></tr></tbody></table><p>An author may associate a set of style properties with a
<code>span</code> element by means of either the <code>style</code>
attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>span</code> element
-in a <em>Document Instance</em> are available for style inheritance by
-descendant <a href="#element-vocab-type-content">Content</a> elements such as <code>span</code> and
+in a <a href="#terms-document-instance">document instance</a> are available for style inheritance by
+descendant <a href="#terms-content-element">content elements</a> such as <code>span</code> and
<code>br</code>.</p></div><p>If no <code>timeContainer</code> attribute is specified on
a <code>span</code> element, then it must be interpreted as having
<em>parallel</em> time containment semantics.</p></div><div class="div3">
@@ -2158,7 +2164,7 @@
<h4><a id="content-attribute-space"></a>7.2.3 xml:space</h4><p>The <code>xml:space</code> attribute is used as defined by
<a href="#xml10">[XML 1.0]</a>, §2.10, <em>White Space Handling</em>.</p><p>The <code>xml:space</code> attribute may be used with any element in
the core vocabulary catalog except parameter vocabulary.</p><p>The semantics of the value <code>default</code> are fixed to mean that
-when performing presentation processing of a <em>Document Instance</em> as
+when performing presentation processing of a <a href="#terms-document-instance">document instance</a> as
described by <a href="#semantics-region-layout-step-2"><b>9.3.4 Synchronic Flow Processing</b></a>,
processing must occur as
if the following properties were specified on the affected
@@ -2181,8 +2187,8 @@
that content.</p><p>Styling attributes are included in TTML to enable authorial intent of presentation
to be included within a self-contained document. This section describes
the semantics of style presentation in terms of a standard processing
-model. TTML Processors are not required to present <em>Document Instances</em> in any particular way;
-but an implementation of this model by a TTML Presentation Processor
+model. TTML Processors are not required to present <a href="#terms-document-instance">document instances</a> in any particular way;
+but an implementation of this model by a TTML <a href="#terms-presentation-processor">presentation processor</a>
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
@@ -2194,7 +2200,7 @@
<code><?xml-stylesheet ... ?></code> processing instruction is defined
by this specification.</p><div class="div2">
<h3><a id="styling-element-vocabulary"></a>8.1 Styling Element Vocabulary</h3><p>The following elements specify the structure and principal styling aspects of a
-<em>Document Instance</em>:</p><ul><li><p><a href="#styling-vocabulary-styling"><b>8.1.1 styling</b></a></p></li><li><p><a href="#styling-vocabulary-style"><b>8.1.2 style</b></a></p></li></ul><div class="div3">
+<a href="#terms-document-instance">document instance</a>:</p><ul><li><p><a href="#styling-vocabulary-styling"><b>8.1.1 styling</b></a></p></li><li><p><a href="#styling-vocabulary-style"><b>8.1.2 style</b></a></p></li></ul><div class="div3">
<h4><a id="styling-vocabulary-styling"></a>8.1.1 styling</h4><p>The <code>styling</code> element is a container element used to group
styling matter, including metadata that applies to styling matter.</p><p>The <code>styling</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group, followed by
@@ -2210,7 +2216,7 @@
</pre></div>
</td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
<code>styling</code> element, the implied time interval of this element is
-defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
+defined to be coterminous with the <a href="#terms-root-temporal-extent">root temporal extent</a>.</p></div><div class="div3">
<h4><a id="styling-vocabulary-style"></a>8.1.2 style</h4><p>The <code>style</code> element is used to define
a set of style specifications expressed as a
specified style set in accordance with
@@ -2234,8 +2240,8 @@
element must appear as a descendant of the <code>styling</code> element, and
not in any other context.</p></div></div></div><div class="div2">
<h3><a id="styling-attribute-vocabulary"></a>8.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>8.2.1 style</b></a> attribute used
-with both style definition elements as well as <a href="#element-vocab-type-content">Content</a> elements.</p><p>In addition, this section specifies the following attributes in the TT Style Namespace
-for use with style definition elements, certain layout elements, and <a href="#element-vocab-type-content">Content</a> elements
+with both style definition elements as well as <a href="#terms-content-element">content elements</a>.</p><p>In addition, this section specifies the following attributes in the TT Style Namespace
+for use with style definition elements, certain layout elements, and <a href="#terms-content-element">content elements</a>
that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>8.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-border"><b>8.2.3 tts:border</b></a></p></li><li><p><a href="#style-attribute-color"><b>8.2.4 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>8.2.5 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>8.2.6 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>8.2.7 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>8.2.8 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>8.2.9 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>8.2.10 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>8.2.11 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>8.2.12 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>8.2.13 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>8.2.14 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>8.2.15 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>8.2.16 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>8.2.17 tts:padding</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>8.2.18 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>8.2.19 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>8.2.20 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>8.2.21 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>8.2.22 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>8.2.23 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>8.2.24 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>8.2.25 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>8.2.26 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>8.2.27 tts:zIndex</b></a></p></li></ul><table border="1" class="ednote" summary="Editorial note: Additional Border Styling Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Border Styling Attributes</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:borderColor</code>, <code>tts:borderStyle</code>, and <code>tts:borderWidth</code>
in order to provide a means to independently express styling of the four different borders (top, right, bottom, left). As currently specified, i.e., with only the
<code>tts:border</code> attribute, one can only express the four borders using the same color, style, and width.</td></tr></table><p>Unless explicitly stated otherwise, linear white-space (LWSP) must
@@ -2245,7 +2251,7 @@
are based upon like-named properties defined by <a href="#xsl11">[XSL 1.1]</a>.
This convention is likewise extended to token values of such
properties.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A style property may be expressed as a specified attribute on any
-<a href="#element-vocab-type-content">Content</a> element type
+<a href="#terms-content-element">content element</a> type
independently of whether the property applies to that
element type. This capability permits the expression of an inheritable
style property on ancestor elements to which the property
@@ -2319,11 +2325,11 @@
span.</p><p>If no border width is specified in the value of the <code>tts:border</code> property,
then the border width must be interpreted as if a width of
<code>medium</code> were specified.</p><p>If a computed value of the border width associated with this attribute is not supported,
-then a presentation processor must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed border width and the supported border width is minimized.</p></div><p>If no border style is specified in the value of the <code>tts:border</code> property,
then the border style must be interpreted as if a style of
<code>none</code> were specified.</p><p>If a computed value of the border style associated with this attribute is not supported,
-then a presentation processor must use the value <code>solid</code>.</p><p>If no border color is specified in the value of the <code>tts:border</code> property,
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>solid</code>.</p><p>If no border color is specified in the value of the <code>tts:border</code> property,
then the border color must be interpreted as if a color equal
to the computed value of the element's <code>tts:color</code> property were specified.</p><p>The <code>tts:border</code> style is illustrated by the following example.</p><a id="style-attribute-border-example-1"></a><table class="example"><caption>Example Fragment – Background Color</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -2354,9 +2360,9 @@
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>The initial value of the <code>tts:color</code> property
is considered to be implementation dependent. In the absence of
-end-user preference information, a conformant presentation processor
+end-user preference information, a conformant <a href="#terms-presentation-processor">presentation processor</a>
should use an initial value that is highly contrastive to the
-background color of the <em>Root Container Region</em>.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><a id="style-attribute-color-example-1"></a><table class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
+background color of the <a href="#terms-root-container-region">root container region</a>.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><a id="style-attribute-color-example-1"></a><table class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:backgroundColor="black"/>
@@ -2389,7 +2395,7 @@
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>ltr</code>.</p><p>The <code>tts:direction</code> style is illustrated by the following example.</p><a id="style-attribute-direction-example-1"></a><table class="example"><caption>Example Fragment – Direction</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>ltr</code>.</p><p>The <code>tts:direction</code> style is illustrated by the following example.</p><a id="style-attribute-direction-example-1"></a><table class="example"><caption>Example Fragment – Direction</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="265px 84px"/>
@@ -2487,7 +2493,7 @@
</td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>before</code>.</p><p>The <code>tts:displayAlign</code> style is illustrated by the following example.</p><a id="style-attribute-displayAlign-example-1"></a><table class="example"><caption>Example Fragment – Display Align</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>before</code>.</p><p>The <code>tts:displayAlign</code> style is illustrated by the following example.</p><a id="style-attribute-displayAlign-example-1"></a><table class="example"><caption>Example Fragment – Display Align</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="128px 66px" tts:origin="0px 0px"
@@ -2526,7 +2532,7 @@
§ 7.14.4.</p></div></div><div class="div3">
<h4><a id="style-attribute-extent"></a>8.2.8 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 <em>Root Container Region</em>).</p><p>This attribute may be specified by any
+(which may be the <a href="#terms-root-container-region">root container region</a>).</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><a id="style-property-details-extent"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -2535,17 +2541,17 @@
</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#document-structure-vocabulary-tt"><code>tt</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <em>Root Container Region</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a>
specifications, then they must be interpreted as <em>width</em>
and <em>height</em>, where the first specification is the
<em>width</em>, and the second specification is the <em>height</em>.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express extent must be non-negative.</p><p>If the value of this attribute is <code>auto</code>, then the computed value
-of the style property must be considered to be the same as the extent of the <em>Root Container Region</em>.</p><p>The extent of the <em>Root Container Region</em> is determined either by a
+of the style property must be considered to be the same as the extent of the <a href="#terms-root-container-region">root container region</a>.</p><p>The extent of the <a href="#terms-root-container-region">root container region</a> is determined either by a
<code>tts:extent</code> specified on the <code>tt</code> element, if
present, or as described by <a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a> if not present.
If <code>tts:extent</code> is specified on the <code>tt</code> element, then
the width and height must be expressed in terms of two <a href="#style-value-length"><length></a> specifications,
and these specifications must be expressed as non-percentage, definite lengths using pixel units.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed extent and the supported extent is minimized.</p></div><p>The <code>tts:extent</code> style is illustrated by the following example.</p><a id="style-attribute-extent-example-1"></a><table class="example"><caption>Example Fragment – Extent</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -2579,7 +2585,7 @@
further described in <a href="#style-value-genericFamilyName"><b>8.3.9 <genericFamilyName></b></a> below.</p></div><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a computed value of the property associated with this attribute is not supported, then a
-presentation processor must attempt to map the computed font family
+<a href="#terms-presentation-processor">presentation processor</a> must attempt to map the computed font family
to a supported font family that has similar typographic
characteristics, or, in the absence of such a mapping, it must
use the value <code>default</code>.</p><p>The <code>tts:fontFamily</code> style is illustrated by the following example.</p><a id="style-attribute-fontFamily-example-1"></a><table class="example"><caption>Example Fragment – Font Family</caption><tbody><tr><td>
@@ -2621,7 +2627,7 @@
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>if not <a href="#content-vocabulary-span"><code>region</code></a> element,
then relative to parent element's font size; otherwise, relative to the
-<em>Computed Cell Size</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a single <a href="#style-value-length"><length></a> value is specified, then this length applies
+<a href="#terms-computed-cell-size">computed cell size</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a single <a href="#style-value-length"><length></a> value is specified, then this length applies
equally to horizontal and vertical scaling of a glyph's EM square; if two
<a href="#style-value-length"><length></a> values are specified, then the first expresses the horizontal
scaling and the second expresses vertical scaling.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Use of independent horizontal and vertical font sizes is expected to be used
@@ -2631,14 +2637,14 @@
units of the <a href="#style-value-length"><length></a> values must be the same.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express font size must be non-negative.</p><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed font size and the supported font size is minimized.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
the <em>cell</em> length unit as defined by <a href="#style-value-length"><b>8.3.12 <length></b></a>.
When a single <length> is expressed using cell units, then it refers to the height of
-the <em>Computed Cell Size</em>.
+the <a href="#terms-computed-cell-size">computed cell size</a>.
When two <length> values are expressed using cell units, then the first refers to the width of
-the <em>Computed Cell Size</em>, and the second refers to the height of the
-<em>Computed Cell Size</em>.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
+the <a href="#terms-computed-cell-size">computed cell size</a>, and the second refers to the height of the
+<a href="#terms-computed-cell-size">computed cell size</a>.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="299px 97px"/>
@@ -2679,7 +2685,7 @@
span.</p><p>Use of the value <code>oblique</code>
denotes a shear transformation (at an unspecified
angle) in the inline progression dimension.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>normal</code>.</p><p>The <code>tts:fontStyle</code> style is illustrated by the following example.</p><a id="style-attribute-fontStyle-example-1"></a><table class="example"><caption>Example Fragment – Font Style</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>normal</code>.</p><p>The <code>tts:fontStyle</code> style is illustrated by the following example.</p><a id="style-attribute-fontStyle-example-1"></a><table class="example"><caption>Example Fragment – Font Style</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="331px 84px"/>
@@ -2713,7 +2719,7 @@
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>normal</code>.</p><p>The <code>tts:fontWeight</code> style is illustrated by the following example.</p><a id="style-attribute-fontWeight-example-1"></a><table class="example"><caption>Example Fragment – Font Weight</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>normal</code>.</p><p>The <code>tts:fontWeight</code> style is illustrated by the following example.</p><a id="style-attribute-fontWeight-example-1"></a><table class="example"><caption>Example Fragment – Font Weight</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="376px 95px"/>
@@ -2749,7 +2755,7 @@
descendant elements in the intermediate synchronic document as determined by
<a href="#semantics-region-layout-step-1"><b>9.3.3 Intermediate Synchronic Document Construction</b></a>.</p><p>If specified as a <a href="#style-value-length"><length></a>, then the length must
be non-negative.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed line height and the supported line height is minimized.</p></div><p>The <code>tts:lineHeight</code> style is illustrated by the following example.</p><a id="style-attribute-lineHeight-example-1"></a><table class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -2829,7 +2835,7 @@
§ 3.2.</p></div></div><div class="div3">
<h4><a id="style-attribute-origin"></a>8.2.15 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 <em>Root Container Region</em>.</p><p>This attribute may be specified by any
+region area with respect to the origin of the <a href="#terms-root-container-region">root container region</a>.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><a id="style-property-details-origin"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
@@ -2837,11 +2843,11 @@
<a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a>
</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <em>Root Container Region</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a> specifications,
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a> specifications,
then they must be interpreted as <em>x</em> and <em>y</em> coordinates, where the first specification
is the <em>x</em> coordinate, and the second specification is the <em>y</em> coordinate.</p><p>If the value of this attribute is <code>auto</code>, then the computed value
-of the style property must be considered to be the same as the origin of the <em>Root Container Region</em>.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+of the style property must be considered to be the same as the origin of the <a href="#terms-root-container-region">root container region</a>.</p><p>If a computed value of the property associated with this attribute is not supported,
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed origin and the supported origin is minimized.</p></div><p>The <code>tts:origin</code> style is illustrated by the following example.</p><a id="style-attribute-origin-example-1"></a><table class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -2881,7 +2887,7 @@
region if the value of the <code>tts:overflow</code> style that applies to the
region is <code>visible</code> and if the applicable <code>tts:wrapOption</code>
style is <code>noWrap</code>.</p></div><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>hidden</code>.</p><p>The <code>tts:overflow</code> style is illustrated by the following example.</p><a id="style-attribute-overflow-example-1"></a><table class="example"><caption>Example Fragment – Overflow</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>hidden</code>.</p><p>The <code>tts:overflow</code> style is illustrated by the following example.</p><a id="style-attribute-overflow-example-1"></a><table class="example"><caption>Example Fragment – Overflow</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="232px 40px"/>
@@ -2947,7 +2953,7 @@
to the after edge.
If four <a href="#style-value-length"><length></a> specifications are provided, then they apply to before, end,
after, and start edges, respectively.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express padding must be non-negative.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed padding and the supported padding is minimized.</p></div><p>The <code>tts:padding</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Enhance Padding Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Enhance Padding Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Enhance padding example to demonstrate padding on content elements.</td></tr></table><p></p><a id="style-attribute-padding-example-1"></a><table class="example"><caption>Example Fragment – Padding</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -2989,7 +2995,7 @@
processing on a visual medium; if the value is <code>whenActive</code>,
then the background color of a region is rendered only when some
content is flowed into the region.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>always</code>.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><a id="style-attribute-showBackground-example-1"></a><table class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>always</code>.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><a id="style-attribute-showBackground-example-1"></a><table class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:origin="0px 0px"/>
@@ -3027,7 +3033,7 @@
</td></tr><tr><td><em>Initial:</em></td><td><code>start</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#content-vocabulary-p"><code>p</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>start</code>.</p><p>The <code>tts:textAlign</code> style is illustrated by the following example.</p><a id="style-attribute-textAlign-example-1"></a><table class="example"><caption>Example Fragment – Text Align</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>start</code>.</p><p>The <code>tts:textAlign</code> style is illustrated by the following example.</p><a id="style-attribute-textAlign-example-1"></a><table class="example"><caption>Example Fragment – Text Align</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="355px 43px"/>
@@ -3076,7 +3082,7 @@
</td></tr><tr><td><em>Initial:</em></td><td><code>none</code></td></tr><tr><td><em>Applies to:</em></td><td><a href="#content-vocabulary-span"><code>span</code></a></td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this
style property, each character child of a <code>p</code> element is
considered to be enclosed in an anonymous span.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>none</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The syntax used above in defining the value of this property is based on the
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>none</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The syntax used above in defining the value of this property is based on the
value component syntax defined in <a href="#css2">[CSS2]</a>, § 1.4.2.1. In essence,
one or more of the values separated by <code>||</code> may appear in the property
value in any order, such as <code>"noUnderline overline lineThrough"</code>.</p></div><p>The <code>tts:textDecoration</code> style is illustrated by the following example.</p><a id="style-attribute-textDecoration-example-1"></a><table class="example"><caption>Example Fragment – Text Decoration</caption><tbody><tr><td>
@@ -3132,7 +3138,7 @@
90° counter-clockwise, according to whether the writing mode is
<code>tbrl</code> or <code>tblr</code>, respectively. Glyphs from vertical scripts are not
affected.</p><p>If a vertical writing mode does not apply, then this style property has no effect.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>mixed</code>.</p><p>The <code>tts:textOrientation</code> style is illustrated by the following
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>mixed</code>.</p><p>The <code>tts:textOrientation</code> style is illustrated by the following
example.</p><table border="1" class="ednote" summary="Editorial note: Text Orientation Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Orientation Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of text orientation.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#css3-wm">[CSS Writing Modes Level 3]</a>,
§ 5.1.</p></div></div><div class="div3">
@@ -3159,10 +3165,10 @@
cells is used in a <code>tts:textOutline</code> value,
the cell's dimension in the block progression dimension applies.
For example, if text outline thickness is specified as 0.1c, the cell resolution
-is 20 by 10, and the extent of the <em>Root Container Region</em> is 640 by 480, then the
+is 20 by 10, and the extent of the <a href="#terms-root-container-region">root container region</a> is 640 by 480, then the
outline thickness will be a nominal 480 / 10 * 0.1 pixels, i.e., 4.8px,
without taking into account rasterization effects.</p></div><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>none</code>.</p><p>The <code>tts:textOutline</code> style is illustrated by the following
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>none</code>.</p><p>The <code>tts:textOutline</code> style is illustrated by the following
example.</p><a id="style-attribute-textOutline-example-1"></a><table class="example"><caption>Example Fragment – Text Outline</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -3202,7 +3208,7 @@
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>normal</code>.</p><p>The <code>tts:unicodeBidi</code> style is illustrated by the following example.</p><a id="style-attribute-unicodeBidi-example-1"></a><table class="example"><caption>Example Fragment – Unicode Bidirectionality</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>normal</code>.</p><p>The <code>tts:unicodeBidi</code> style is illustrated by the following example.</p><a id="style-attribute-unicodeBidi-example-1"></a><table class="example"><caption>Example Fragment – Unicode Bidirectionality</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="265px 84px"/>
@@ -3244,7 +3250,7 @@
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>The <code>tts:visibility</code> style has no affect on content layout or
composition, but merely determines whether composed content is visible or not.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>visible</code>.</p><p>The <code>tts:visibility</code> style is illustrated by the following example.</p><a id="style-attribute-visibility-example-1"></a><table class="example"><caption>Example Fragment – Visibility</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>visible</code>.</p><p>The <code>tts:visibility</code> style is illustrated by the following example.</p><a id="style-attribute-visibility-example-1"></a><table class="example"><caption>Example Fragment – Visibility</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="398px 121px"/>
@@ -3292,7 +3298,7 @@
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>wrap</code>.</p><p>The <code>tts:wrapOption</code> style is illustrated by the following example.</p><a id="style-attribute-wrapOption-example-1"></a><table class="example"><caption>Example Fragment – Wrap Option</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>wrap</code>.</p><p>The <code>tts:wrapOption</code> style is illustrated by the following example.</p><a id="style-attribute-wrapOption-example-1"></a><table class="example"><caption>Example Fragment – Wrap Option</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="192px 117px"/>
@@ -3329,7 +3335,7 @@
</td></tr><tr><td><em>Initial:</em></td><td><code>lrtb</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the value <code>lrtb</code>.</p><p>The <code>tts:writingMode</code> style is illustrated by the following example.</p><a id="style-attribute-writingMode-example-1"></a><table class="example"><caption>Example Fragment – Writing Mode</caption><tbody><tr><td>
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>lrtb</code>.</p><p>The <code>tts:writingMode</code> style is illustrated by the following example.</p><a id="style-attribute-writingMode-example-1"></a><table class="example"><caption>Example Fragment – Writing Mode</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="50px 570px"/>
@@ -3376,10 +3382,10 @@
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If two areas are associated with the same Z-index value, then, if those areas
overlap in space, the area(s) generated by lexically subsequent elements must be
rendered over area(s) generated by lexically prior elements, where lexical
-order is defined as the postorder traversal of a <em>Document Instance</em>.</p><p>The semantics of the value <code>auto</code> are those defined by
+order is defined as the postorder traversal of a <a href="#terms-document-instance">document instance</a>.</p><p>The semantics of the value <code>auto</code> are those defined by
<a href="#xsl11">[XSL 1.1]</a>, § 7.30.18, where the <code>tt</code> element
is considered to establish the root stacking context.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a presentation processor must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed z-index and the supported z-index is minimized.</p></div><p>The <code>tts:zIndex</code> style is illustrated by the following example.</p><a id="style-attribute-zIndex-example-1"></a><table class="example"><caption>Example Fragment – Z Index</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -3454,7 +3460,7 @@
then it must be interpreted as equal to 0.0; similarly, if the value
represented is greater than 1.0, then it must be interpreted as
1.0. The value NaN must be interpreted as 0.0.</p><p>A specified value for <alpha> should not be <code>NaN</code>,
-less than 0, or greater than 1.</p><p>If a presentation processor does not support a specific,
+less than 0, or greater than 1.</p><p>If a <a href="#terms-presentation-processor">presentation processor</a> does not support a specific,
valid opacity value, then it must interpret it as being equal to the
closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed opacity and the supported opacity is minimized.</p></div></div><div class="div3">
@@ -3528,8 +3534,8 @@
the composition function.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of <a href="#srgb">[SRGB]</a> for the stated semantics of
composition is not meant to prevent an actual processor from using some
other color space either for internal or external purposes. For
-example, a presentation processor may ultimately convert the SRGB values
-used here to the YUV color space for rendition on a television device.</p></div><p>If a presentation processor does not support a specific,
+example, a <a href="#terms-presentation-processor">presentation processor</a> may ultimately convert the SRGB values
+used here to the YUV color space for rendition on a television device.</p></div><p>If a <a href="#terms-presentation-processor">presentation processor</a> does not support a specific,
valid color or alpha value, then it must interpret it as being equal
to the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed color or alpha and the supported color or alpha in the RGB color space is minimized.</p></div></div><div class="div3">
@@ -3698,13 +3704,13 @@
scaled font when used to specify lengths in the inline progression
direction and equal to the block progression dimension of the scaled
font when used to specify lengths in the block progression direction.</p><p>The semantics of the unit of measure <code>c</code> (cell) are
-defined by the parameter <a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a>.</p><p>The unit of measure <code>vw</code> and <code>vh</code> are defined as
-one percent (1%) of the width and height of the <em>Root Container Region</em>, respectively.
+defined by the parameter <a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a>.</p><p>The units of measure <code>vw</code> and <code>vh</code> are defined as
+one percent (1%) of the width and height of the <a href="#terms-root-container-region">root container region</a>, respectively.
For example, the length <code>25vw</code> is interpreted as 25% of the width of
-the <em>Root Container Region</em>.</p><p>The units of measure <code>vmin</code> and <code>vmax</code> are defined as
+the <a href="#terms-root-container-region">root container region</a>.</p><p>The units of measure <code>vmin</code> and <code>vmax</code> are defined as
the minimum and maxium of <code>vw</code> and <code>vh</code>, respectively. For example,
the length <code>25vmin</code> is interpreted as the minimum of 25% of the width and
-25% of the height of the <em>Root Container Region</em>.</p></div><div class="div3">
+25% of the height of the <a href="#terms-root-container-region">root container region</a>.</p></div><div class="div3">
<h4><a id="style-value-namedColor"></a>8.3.13 <namedColor></h4><p>A <namedColor> is used to express an RGBA color with a convenient name, and where the applicable color space is
defined by <a href="#srgb">[SRGB]</a>.</p><p>For the purpose of parsing, a distinction must not be made between lower and upper case.</p><a id="namedColor-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <namedColor></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -3766,7 +3772,7 @@
reference to <code>style</code> element descendants of a <code>styling</code>
element. It is considered an error to reference a <code>style</code>
element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of referential styling encourages the reuse of style specifications while
-sacrificing locality of reference.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#element-vocab-type-content">Content</a> element may be associated with style properties by a hybrid mixture of
+sacrificing locality of reference.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#terms-content-element">content element</a> may be associated with style properties by a hybrid mixture of
inline and referential styling, in which case inline styling is given priority as described above
by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><a id="style-association-example-2"></a><table class="example"><caption>Example – Referential Styling</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -3788,7 +3794,7 @@
reference to <code>style</code> element descendants of a <code>styling</code>
element. It is considered an error to reference a <code>style</code>
element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of chained referential styling encourages the grouping of style specifications
-into general and specific sets, which further aids in style specification reuse.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#element-vocab-type-content">Content</a> element may be associated with style properties by a hybrid mixture of
+into general and specific sets, which further aids in style specification reuse.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#terms-content-element">content element</a> may be associated with style properties by a hybrid mixture of
inline, referential styling, and chained referential styling, in which case inline styling is
given priority as described above by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><a id="style-association-example-3"></a><table class="example"><caption>Example – Chained Referential Styling</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -3818,15 +3824,15 @@
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 <em>Document Instance</em> must be used, where
+an intermediate synchronic document form of a <a href="#terms-document-instance">document instance</a> must be used, where
such intermediate forms are defined by <a href="#semantics-region-layout-step-1"><b>9.3.3 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">
-<h5><a id="semantics-style-inheritance-content"></a>8.4.2.1 Content Style Inheritance</h5><p>Style properties are inherited from ancestor <a href="#element-vocab-type-content">Content</a> elements
+<h5><a id="semantics-style-inheritance-content"></a>8.4.2.1 Content Style Inheritance</h5><p>Style properties are inherited from ancestor <a href="#terms-content-element">content elements</a>
within an intermediate synchronic document
-if a style property is not associated with a <a href="#element-vocab-type-content">Content</a> element (or
+if a style property is not associated with a <a href="#terms-content-element">content element</a> (or
an anonymous span) and the style property is designated as
-inheritable.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code>tt</code> element is not a <a href="#element-vocab-type-content">Content</a> element;
+inheritable.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code>tt</code> element is not a <a href="#terms-content-element">content element</a>;
consequently, the <code>body</code> element is the outermost element from which content style inheritance occurs.</p></div><p>If a style property is determined to require inheritance, then the inherited value must
be the value of the same named style property in the computed
style set of the
@@ -3847,8 +3853,8 @@
specified
style
set of the <code>span</code> element.</p></div></div><div class="div4">
-<h5><a id="semantics-style-inheritance-region"></a>8.4.2.2 Region Style Inheritance</h5><p>Style properties are inherited from a region element in the following case:</p><ol class="enumar"><li><p>if a style property <em>P</em> is not associated with
-a <a href="#element-vocab-type-content">Content</a> element
+<h5><a id="semantics-style-inheritance-region"></a>8.4.2.2 Region Style Inheritance</h5><p>Style properties are inherited from a <a href="#layout-vocabulary-region">region</a> element in the following case:</p><ol class="enumar"><li><p>if a style property <em>P</em> is not associated with
+a <a href="#terms-content-element">content element</a>
or an anonymous span <em>E</em> and the style
property is designated as inheritable, and</p></li><li><p>if that
style property <em>P</em> is in the computed style
@@ -3900,11 +3906,11 @@
process are referred to as <em>actual values</em>. The set of all
actual style properties of a given element is referred to as the
<em>actual style set</em> of that element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>More than one set of actual values may be produced during the
-process of presentation. For example, a TTML presentation processor
+process of presentation. For example, a TTML <a href="#terms-presentation-processor">presentation processor</a>
device may output an RGBA component video signal which is then
further transformed by an NTSC or PAL television to produce a final
image. In this case, both color and dimensions may further be modified
-prior to presentation.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In general, a TTML presentation processor will not have access
+prior to presentation.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In general, a TTML <a href="#terms-presentation-processor">presentation processor</a> will not have access
to actual style set values; as a consequence, no further use or reference
to actual values is made below when formally describing the style
resolution process.</p></div></div></div><div class="div3">
@@ -4025,7 +4031,7 @@
type <code>region</code>, then set <em>P′</em> to the initial value of
property <em>P</em>, where the initial value of a property is
determined according to the specific property definition found above
-in <a href="#styling-attribute-vocabulary"><b>8.2 Styling Attribute Vocabulary</b></a>;</p></li><li><p>if the element type of <em>E</em> is a <a href="#element-vocab-type-content">Content</a> element
+in <a href="#styling-attribute-vocabulary"><b>8.2 Styling Attribute Vocabulary</b></a>;</p></li><li><p>if the element type of <em>E</em> is a <a href="#terms-content-element">content element</a>
type or anonymous span, then set <em>P′</em> to the result of
looking up the value of <em>P</em> in the computed style set of
the immediate ancestor element of <em>E</em>, i.e.,
@@ -4052,7 +4058,7 @@
relative value expressions remain relative; consequently, the
resolution of relative value expressions (that may be assigned by
means of referential style association) always takes place in the
-context of a layout or <a href="#element-vocab-type-content">Content</a> element which has a presentation
+context of a layout or <a href="#terms-content-element">content element</a> which has a presentation
context, and not in the non-presentation, declaration context
of a <code>set</code> element or a referentiable <code>style</code> element.</p></div></div><div class="div4">
<h5><a id="semantics-style-resolution-process-overall"></a>8.4.4.4 Style Resolution Process</h5><p>The top-level style resolution process is defined as follows: using
@@ -4063,7 +4069,7 @@
of <em>E</em> is not the styling element type <code>style</code>, is
not the layout element type <code>region</code>, is not the animation
element type <code>set</code>, and is not one of the
-<a href="#element-vocab-type-content">Content</a> element types <code>body</code>, <code>div</code>, <code>p</code>,
+<a href="#terms-content-element">content element</a> types <code>body</code>, <code>div</code>, <code>p</code>,
<code>span</code>, <code>br</code>, or anonymous span, then continue to the
next element in the preorder traversal;</p></li><li><p> <span class="strong">[resolve computed styles]</span>
determine (obtain) the computed style set <em>CSS</em> of
@@ -4082,7 +4088,7 @@
in which the style
matter is not embedded (inlined).</p></div><div class="div2">
<h3><a id="layout-element-vocabulary"></a>9.1 Layout Element Vocabulary</h3><p>The following elements specify the structure and principal layout aspects of a
-<em>Document Instance</em>:</p><ul><li><p><a href="#layout-vocabulary-layout"><b>9.1.1 layout</b></a></p></li><li><p><a href="#layout-vocabulary-region"><b>9.1.2 region</b></a></p></li></ul><div class="div3">
+<a href="#terms-document-instance">document instance</a>:</p><ul><li><p><a href="#layout-vocabulary-layout"><b>9.1.1 layout</b></a></p></li><li><p><a href="#layout-vocabulary-region"><b>9.1.2 region</b></a></p></li></ul><div class="div3">
<h4><a id="layout-vocabulary-layout"></a>9.1.1 layout</h4><p>The <code>layout</code> element is a container element used to group
out-of-line layout matter, including metadata that applies to layout matter.</p><p>The <code>layout</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group, followed by
@@ -4098,14 +4104,14 @@
</pre></div>
</td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
<code>layout</code> element, the implied time interval of this element is
-defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
+defined to be coterminous with the <a href="#terms-root-temporal-extent">root temporal extent</a>.</p></div><div class="div3">
<h4><a id="layout-vocabulary-region"></a>9.1.2 region</h4><p>The <code>region</code> element is used to define a rectangular space or area into which content is
to be flowed for the purpose of presentation.</p><p>A <code>region</code> element may appear as either (1) a child of a
<a href="#layout-vocabulary-layout">layout</a> element or (2) a child of block level
-<a href="#element-vocab-type-content">Content</a> elements, specifically, of elements
+<a href="#terms-content-element">content element</a>, specifically, of elements
in the <a href="#element-vocab-group-table">Block.class</a> element group.
-In the former case, the region is referred to as an <em>Out-of-line Region</em>, while in the latter
-case, it is referred to as an <em>Inline Region</em>.</p><p>In addition, and in accordance with
+In the former case, the region is referred to as an <a href="#terms-out-of-line-region">out-of-line region</a>, while in the latter
+case, it is referred to as an <a href="#terms-inline-region">inline region</a>.</p><p>In addition, and in accordance with
<a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>,
the <code>region</code> element may be used to specify inheritable style properties to be
inherited by content that is flowed into it.</p><p>The <code>region</code> element accepts as its children zero or more
@@ -4137,8 +4143,8 @@
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Animation.class</a>*, <a href="#styling-vocabulary-style">style</a>*
</region>
</pre></div>
-</td></tr></tbody></table><p>An out-of-line region may specify one or more of the timing attributes:
-<code>begin</code>, <code>end</code>, <code>dur</code>. An inline region must not
+</td></tr></tbody></table><p>An <a href="#terms-out-of-line-region">out-of-line region</a> may specify one or more of the timing attributes:
+<code>begin</code>, <code>end</code>, <code>dur</code>. An <a href="#terms-inline-region">inline region</a> must not
specifiy a timing attribute, and, if specified, must be ignored for the purpose
of presentation processing.</p><p>If <code>begin</code> and (or) <code>end</code> attributes are specified on an out-of-line
<code>region</code> element, then they specify the beginning and (or) ending points
@@ -4151,20 +4157,20 @@
with a time interval is the <code>layout</code> element.
If a <code>dur</code> attribute is specified on an out-of-line <code>region</code> element, then it
specifies the simple duration of the region.</p><p>The active time interval of an inline <code>region</code> element is the
-active time interval of its parent <a href="#element-vocab-type-content">Content</a> element.</p><p>For the purpose of determining the semantics of presentation processing, a
+active time interval of its parent <a href="#terms-content-element">content element</a>.</p><p>For the purpose of determining the semantics of presentation processing, a
region that is temporally inactive must not produce any visible marks when
presented on a visual medium.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>An out-of-line <code>region</code> element may be associated with a time interval for two
purposes: (1) in order to temporally bound the presentation of the region and
its content, and (2) to provide a temporal context in which animations of region
-styles may be effected.</p><p>For example, an author may wish to specify an out-of-line region that is otherwise empty, but
+styles may be effected.</p><p>For example, an author may wish to specify an <a href="#terms-out-of-line-region">out-of-line region</a> that is otherwise empty, but
may have a visible background color to be presented starting at some time and
continuing over the region's duration. The simple duration of the region serves
additionally to scope the presentation effects of content that is targeted to the
-region. An author may also wish to move a region within the <em>Root Container Region</em>
+region. An author may also wish to move a region within the <a href="#terms-root-container-region">root container region</a>
or change a region's background color by means of animation effects. In
both of these cases, it is necessary to posit an active time interval for a
-region.</p><p>In contrast to out-of-line regions, inline regions are specifically bound to
-the temporal context of their parent <a href="#element-vocab-type-content">Content</a> elements,
+region.</p><p>In contrast to <a href="#terms-out-of-line-region">out-of-line regions</a>, <a href="#terms-inline-region">inline regions</a> are specifically bound to
+the temporal context of their parent <a href="#terms-content-element">content elements</a>,
and, as such, do not require (or admit) the specification of independent timing.</p></div><p>If no <code>timeContainer</code> attribute is specified on
a <code>region</code> element, then it must be interpreted as having
<em>parallel</em> time containment semantics.</p><p>If a <a href="#metadata-attribute-role"><code>ttm:role</code></a> attribute is
@@ -4173,9 +4179,9 @@
by this attribute express the semantic roles of the region
independently from the semantic roles of any content targeted to
(associated with) the region.</p></div></div><div class="div2">
-<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with <a href="#element-vocab-type-content">Content</a> elements.</p><div class="div3">
+<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with <a href="#terms-content-element">content elements</a>.</p><div class="div3">
<h4><a id="layout-attribute-region"></a>9.2.1 region</h4><p>The <code>region</code> attribute is used to reference a <code>region</code>
-element which defines a space or area into which a <a href="#element-vocab-type-content">Content</a> element is intended to be flowed.</p><p>If specified, the value of a <code>region</code> attribute must
+element which defines a space or area into which a <a href="#terms-content-element">content element</a> is intended to be flowed.</p><p>If specified, the value of a <code>region</code> attribute must
adhere to the <code>IDREF</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
§ 3.3.9, and, furthermore, this IDREF must reference a <code>region</code> element
which has a <code>layout</code> element as an ancestor.</p><p>The <code>region</code> attribute may be specified by an instance of the following
@@ -4187,13 +4193,13 @@
implementation is permitted provided that the externally observable
results are consistent with the results produced by this model.
</p><div class="div3">
-<h4><a id="semantics-default-region"></a>9.3.1 Default Region</h4><p>If a <em>Document Instance</em> does not specify a
+<h4><a id="semantics-default-region"></a>9.3.1 Default Region</h4><p>If a <a href="#terms-document-instance">document instance</a> does not specify a
<a href="#layout-vocabulary-region"><code>region</code></a> element,
-then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be anonymous;</p></li><li><p>the extent of the default region is the same as the extent of the <em>Root Container Region</em>;</p></li><li><p>the temporal interval of the default region is the same as the interval defined by the <em>Root Temporal Extent</em>;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element is
+then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be anonymous;</p></li><li><p>the extent of the default region is the same as the extent of the <a href="#terms-root-container-region">root container region</a>;</p></li><li><p>the temporal interval of the default region is the same as the interval defined by the <a href="#terms-root-temporal-extent">root temporal extent</a>;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element is
specified, then the <a href="#layout-attribute-region"><code>region</code></a> attribute must
-not be specified on any <a href="#element-vocab-type-content">Content</a> element in the <em>Document Instance</em>.</p><p>If a default region is implied for a given <em>Document Instance</em>, then
+not be specified on any <a href="#terms-content-element">content element</a> in the <a href="#terms-document-instance">document instance</a>.</p><p>If a default region is implied for a given <a href="#terms-document-instance">document instance</a>, then
the <a href="#document-structure-vocabulary-body"><code>body</code></a> element
-is implicitly targeted to (associated with) the default region.</p><p>When implying a default region, the <em>Document Instance</em> is to be
+is implicitly targeted to (associated with) the default region.</p><p>When implying a default region, the <a href="#terms-document-instance">document instance</a> is to be
treated as if a <a href="#layout-vocabulary-region"><code>region</code></a> element and its
parent <a href="#layout-vocabulary-layout"><code>layout</code></a>
element were specified in a <a href="#document-structure-vocabulary-head"><code>head</code></a>
@@ -4215,9 +4221,9 @@
the implied <code>region</code> element.</p></div></div><div class="div3">
<h4><a id="semantics-inline-regions"></a>9.3.2 Inline Regions</h4><p><span class="tbd">To Be Defined</span></p></div><div class="div3">
<h4><a id="semantics-region-layout-step-1"></a>9.3.3 Intermediate Synchronic Document Construction</h4><p>For the purposes of performing presentation processing, the active time
-duration of a <em>Document Instance</em> is divided into a sequence of time coordinates where at
+duration of a <a href="#terms-document-instance">document instance</a> is divided into a sequence of time coordinates where at
each time coordinate, some element becomes temporally active or inactive,
-then, at each such time coordinate, a <em>Document Instance</em> is mapped from its original, source
+then, at each such time coordinate, a <a href="#terms-document-instance">document instance</a> is mapped from its original, source
form, <em>DOC<sub>source</sub></em> ,
to an intermediate
synchronic document form,
@@ -4226,7 +4232,7 @@
sub-tree
of <em>DOC<sub>source</sub></em>
headed by the <code>body</code> element;</p></li><li><p>evaluating this sub-tree in a postorder traversal, prune elements if they
-are not a <a href="#element-vocab-type-content">Content</a> element, if they are temporally inactive, if they are empty,
+are not a <a href="#terms-content-element">content element</a>, if they are temporally inactive, if they are empty,
or if they aren't associated with region <em>R</em> according to the
<span class="strong">[associate region]</span> procedure;</p></li><li><p>if the pruned sub-tree is non-empty, then reparent it to the <em>R</em>
element;</p></li><li><p>finally, after completing the above steps, prune the original <code>body</code>
@@ -4237,7 +4243,7 @@
which, in turn, implies that the descendants of the pruned element will no longer
be descendants of the element's parent. When <em>prune</em> is used in
reference to an attribute, it means that attribute is to be removed from its
-associated (owning) element node.</p></div></dd><dt class="label">[associate region]</dt><dd><p></p><table border="1" class="ednote" summary="Editorial note: Inline Region Association"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Inline Region Association</b></td><td align="right" valign="top">2013-08-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define inline region association.</td></tr></table><p>A <a href="#element-vocab-type-content">Content</a> element is associated with a region according
+associated (owning) element node.</p></div></dd><dt class="label">[associate region]</dt><dd><p></p><table border="1" class="ednote" summary="Editorial note: Inline Region Association"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Inline Region Association</b></td><td align="right" valign="top">2013-08-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define inline region association.</td></tr></table><p>A <a href="#terms-content-element">content element</a> is associated with a region according
to the following ordered rules, where the first rule satisfied
is used and remaining rules are skipped:</p><ol class="enumar"><li><p>if the element specifies a <a href="#layout-attribute-region"><code>region</code></a> attribute,
then the element is associated with the region referenced by that
@@ -4250,10 +4256,10 @@
<a href="#layout-vocabulary-region"><code>region</code></a> element),
then the element is associated with the default region;</p></li><li><p>the element is not associated with any region.</p></li></ol></dd></dl><p>The result of performing the processing described above will be a sequence of
<em>N</em> intermediate synchronic
-<em>Document Instances</em>,
+<a href="#terms-document-instance">document instances</a>,
<em>DOC<sub><span>inter<sub>0</sub></span></sub></em> …
<em>DOC<sub><span>inter<sub>N−1</sub></span></sub></em>.</p><div class="note" id="semantics-smooth-scrolling-recommendation"><p class="prefix"><b>Note:</b></p><p>Where an implementation is able to detect significant similarity between two
-adjacent synchronic <em>Document Instances</em>,
+adjacent synchronic <a href="#terms-document-instance">document instances</a>,
<em>DOC<sub><span>inter<sub>N</sub></span></sub></em>
<em>DOC<sub><span>inter<sub>N−1</sub></span></sub></em>,
then it is preferred that the implementation make the transition between
@@ -4269,7 +4275,7 @@
TTML. An actual implementation of this algorithm is not required to create or process
XSL-FO representations. In particular, it is possible to implement these semantics
using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>9.3.3 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 <a href="#element-vocab-type-content">Content</a> element,
+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 <a href="#terms-content-element">content element</a>,
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
@@ -4280,7 +4286,7 @@
nodes;</p></li></ol></li><li><p>resolve styles according to <a href="#semantics-style-resolution-process-overall"><b>8.4.4.4 Style Resolution Process</b></a>;</p></li><li><p>map the <code>tt</code> element to an <code>fo:root</code> element, populated
initially with an <code>fo:layout-master-set</code> element that contains a valid
<code>fo:simple-page-master</code> that, in turn, contains an
-<code>fo:region-body</code> child, where the extent of the <em>Root Container Region</em> expressed on the
+<code>fo:region-body</code> child, where the extent of the <a href="#terms-root-container-region">root container region</a> 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
@@ -4293,7 +4299,7 @@
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,
populating the style properties of <code>fo:block</code> by using the computed
-style set associated with each original TTML <a href="#element-vocab-type-content">Content</a> element;</p></li><li><p>for the resulting <code>fo:block</code> formatting object
+style set associated with each original TTML <a href="#terms-content-element">content element</a>;</p></li><li><p>for the resulting <code>fo:block</code> formatting object
produced in the previous step that corresponds to the <code>body</code>
element, perform the following ordered sub-steps:</p><ol class="enumla"><li><p>if the <code>display-align</code> style property of this <code>fo:block</code>
has the value <code>center</code> or <code>after</code>,
@@ -4320,7 +4326,7 @@
map the element or
sequence of character items 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 TTML <a href="#element-vocab-type-content">Content</a> element
+style set associated with each original TTML <a href="#terms-content-element">content element</a>
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 to
@@ -4328,7 +4334,7 @@
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 TTML <a href="#element-vocab-type-content">Content</a> element to
+to the relevant formatting object produced by the input TTML <a href="#terms-content-element">content element</a> 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 document instance F, if processing requires presentation on a
@@ -4338,12 +4344,12 @@
the <code>page-viewport-area</code>,
which is generated by <code>fo:page-sequence</code> element by
reference to the sole generated <code>fo:simple-page-master</code>
-element, would correspond to the <em>Root Container Region</em> defined
+element, would correspond to the <a href="#terms-root-container-region">root container region</a> defined
above in <a href="#definitions"><b>2 Definitions</b></a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>When mapping a <code>region</code> element to <code>fo:block-container</code>, it may
be necessary to use a negative offset as a value for one or more of the
<code>top</code>, <code>left</code>, <code>bottom</code>, and <code>right</code>
XSL-FO properties in case the region extends outside of its containing block.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Due to the possible presence of TTML style properties or style property values
-in a given <em>Document Instance</em> for which there is no <a href="#xsl11">[XSL 1.1]</a> counterpart,
+in a given <a href="#terms-document-instance">document instance</a> 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
@@ -4403,7 +4409,7 @@
the (and, in this case, anonymous) spans reparented into the regions.</p><p>The following, first intermediate document shows the synchronic state for time
interval [0,1), during which time only division <code>d1</code> is temporally active,
and where paragraphs <code>p1</code> and <code>p2</code> (and their ancestors)
-are associated with regions <code>r1</code> and <code>r2</code>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate documents shown below are not valid <em>Document Instances</em>,
+are associated with regions <code>r1</code> and <code>r2</code>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate documents shown below are not valid <a href="#terms-document-instance">document instances</a>,
but rather, are representations of possible internal processing states used for
didactic purposes.</p></div><a id="region-mapping-example-1-i0"></a><table class="example"><caption>Example – Intermediate Document – [0s,1s)</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
@@ -4608,12 +4614,12 @@
</tt>
</pre></div>
</td></tr></tbody></table></div></div><div class="div2">
-<h3><a id="semantics-line-layout"></a>9.4 Line Layout</h3><p>If a profile that applies to a <em>Document Instance</em>
+<h3><a id="semantics-line-layout"></a>9.4 Line Layout</h3><p>If a profile that applies to a <a href="#terms-document-instance">document instance</a>
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/reports/tr14/#Algorithm">Line
Breaking Algorithm</a> <a href="#uax14">[UAX14]</a> apply when performing
-line layout on the content of the <em>Document Instance</em>.</p></div></div><div class="div1">
+line layout on the content of the <a href="#terms-document-instance">document instance</a>.</p></div></div><div class="div1">
<h2><a id="timing"></a>10 Timing</h2><p>This section specifies the <em>timing</em> matter of the core
vocabulary catalog, where
timing is to be understood as a separable layer of information that applies to
@@ -4649,7 +4655,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 <em>Document Instance</em> specifies the use of the
+a difference between two implied clock time expressions.</p></div><p>When a <a href="#terms-document-instance">document instance</a> specifies the use of the
<code>smpte</code> time base and <code>discontinuous</code> marker
mode, a (well-formed) <code>dur</code> attribute must not be specified on any
element.</p><p>The semantics of the <code>dur</code> attribute are those defined
@@ -4778,9 +4784,9 @@
timing and styling in order to denote authorial intention about (temporally) dynamic
styling of content.</p><div class="div2">
<h3><a id="animation-element-vocabulary"></a>11.1 Animation Element Vocabulary</h3><p>The following elements specify the structure and principal animation aspects of a
-<em>Document Instance</em>:</p><ul><li><p><a href="#animation-vocabulary-animation"><b>11.1.1 animation</b></a></p></li><li><p><a href="#animation-vocabulary-animate"><b>11.1.2 animate</b></a></p></li><li><p><a href="#animation-vocabulary-set"><b>11.1.3 set</b></a></p></li></ul><div class="div3">
+<a href="#terms-document-instance">document instance</a>:</p><ul><li><p><a href="#animation-vocabulary-animation"><b>11.1.1 animation</b></a></p></li><li><p><a href="#animation-vocabulary-animate"><b>11.1.2 animate</b></a></p></li><li><p><a href="#animation-vocabulary-set"><b>11.1.3 set</b></a></p></li></ul><div class="div3">
<h4><a id="animation-vocabulary-animation"></a>11.1.1 animation</h4><p>The <code>animation</code> element is a container element used to group
-out-of-line animation matter, including metadata that applies to animation matter.</p><p>The <code>animation</code> element accepts as its children zero or more
+<a href="#terms-out-of-line-animation">out-of-line animation</a> matter, including metadata that applies to animation matter.</p><p>The <code>animation</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group, followed by
zero or more elements in the <code>Animation.class</code> element group.</p><a id="elt-syntax-animation"></a><table class="syntax"><caption>XML Representation – Element Information Item: animation</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -4794,11 +4800,12 @@
</pre></div>
</td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
<code>animation</code> element, the implied time interval of this element is
-defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
+defined to be coterminous with the <a href="#terms-root-temporal-extent">root temporal extent</a>.</p></div><div class="div3">
<h4><a id="animation-vocabulary-animate"></a>11.1.2 animate</h4><p>The <code>animate</code> element expresses a series of changes (animations) to be applied to a targetted attribute
of a targetted element.</p><p>An <code>animate</code> element may appear as either (1) a child of a
-<a href="#element-vocab-type-content">Content</a> or <code>region</code> element, referred to as inline animation, or
-(2) a child of an <a href="#animation-vocabulary-animation">animation</a> element, referred to as out-of-line animation.
+<a href="#terms-content-element">content element</a> or <code>region</code> element, referred to as <a href="#terms-inline-animation">inline animation</a>, or
+(2) a child of an <a href="#animation-vocabulary-animation">animation</a> element, referred to as
+<a href="#terms-out-of-line-animation">out-of-line animation</a>.
In the former case, the targetted element of the animation is the parent of the <code>animate</code> element; in the latter
case, the targetted element is the element referenced by the <code>xlink:href</code> attribute on the
<code>animate</code> element.</p><p>The targetted attribute (property) is specified by the <code>attributeName</code> attribute.</p><p>The <code>animate</code> element accepts as its children zero or more
@@ -4875,8 +4882,9 @@
§19.2.12, which, in turn, is based upon <a href="#smil3">[SMIL 3.0]</a>, §12.</p></div></div><div class="div3">
<h4><a id="animation-vocabulary-set"></a>11.1.3 set</h4><p>The <code>set</code> element expresses one or more a discrete changes (animations) to be applied to targetted attributes
of a targetted element.</p><p>A <code>set</code> element may appear as either (1) a child of a
-<a href="#element-vocab-type-content">Content</a> or <code>region</code> element, referred to as inline animation, or
-(2) a child of an <a href="#animation-vocabulary-animation">animation</a> element, referred to as out-of-line animation.
+<a href="#terms-content-element">content element</a> or <code>region</code> element, referred to as <a href="#terms-inline-animation">inline animation</a>, or
+(2) a child of an <a href="#animation-vocabulary-animation">animation</a> element, referred to as
+<a href="#terms-out-of-line-animation">out-of-line animation</a>.
In the former case, the targetted element of the animation is the parent of the <code>set</code> element; in the latter
case, the targetted element is the element referenced by the <code>xlink:href</code> attribute on the
<code>set</code> element.</p><p>The targetted attributes of a <code>set</code> element are specified using attributes in the TT Style namespace.</p><p>The <code>set</code> element accepts as its children zero or more
@@ -4940,10 +4948,10 @@
<body region="r1">...</body>
</tt>
</pre></div>
-</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the <em>Root Container Region</em> is divided into a
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the <a href="#terms-root-container-region">root container region</a> is divided into a
cell grid of 40 columns and 16 rows. A region, <code>r1</code>, with
dimensions of 24 columns and 2 rows is then positioned within the
-<em>Root Container Region</em>, with its position varying over time in order to
+<a href="#terms-root-container-region">root container region</a>, with its position varying over time in order to
create an effect of moving the region, which may be desirable so as
to avoid obscuring characters in an underlying video with captions.</p></div><p></p><table border="1" class="ednote" summary="Editorial note: Set Example Images"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Set Example Images</b></td><td align="right" valign="top">2013-08-25</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert animated SVG images of set examples.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>set</code> element
are based upon that defined by <a href="#svg11">[SVG 1.1]</a>,
@@ -5004,7 +5012,7 @@
</pre></div>
</td></tr></tbody></table><p>The semantics of a <fill> expression are those defined by
<a href="#svg11">[SVG 1.1]</a>, §19.2.8.</p></div><div class="div3">
-<h4><a id="animation-value-fragmentIdentifier"></a>11.3.7 <fragmentIdentifier></h4><p>A <fragmentIdentifier> expression is used to target (refer to) an animation to a specific element in the same <em>Document Instance</em>.</p><a id="fragmentIdentifier-syntax"></a><table class="syntax"><caption>Syntax Representation – <fragmentIdentifier></caption><tbody><tr><td>
+<h4><a id="animation-value-fragmentIdentifier"></a>11.3.7 <fragmentIdentifier></h4><p>A <fragmentIdentifier> expression is used to target (refer to) an animation to a specific element in the same <a href="#terms-document-instance">document instance</a>.</p><a id="fragmentIdentifier-syntax"></a><table class="syntax"><caption>Syntax Representation – <fragmentIdentifier></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<fragmentIdentifier>
: "#" fragment
@@ -5036,7 +5044,7 @@
to the <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>. Furthermore, it
must adhere to the fragment identifer syntax defined by <a href="#uri">[URI]</a>,
Section 4.1, and is a strict subset thereof, since at least one character must appear in
-the fragment component.</p><p>No linear white-space (LWSP) is permitted to appear within a fragment identifier.</p><p>A <fragmentIdentifer> expression must refer to an element in the same <em>Document Instance</em>,
+the fragment component.</p><p>No linear white-space (LWSP) is permitted to appear within a fragment identifier.</p><p>A <fragmentIdentifer> expression must refer to an element in the same <a href="#terms-document-instance">document instance</a>,
i.e., the fragment component must be a valid IDREF.</p></div><div class="div3">
<h4><a id="animation-value-keySplines"></a>11.3.8 <keySplines></h4><p>An <keySplines> expression is used to specify a list of Bezier control points that control the pacing of an
animation, wherein each pair of values is separated by a SEMICOLON (U+003B) character
@@ -5129,13 +5137,13 @@
parameters, content,
style, layout, timing, and even metadata itself, where the information
represented by metadata takes one of two forms: (1) metadata defined by this
-specification for standardized use in a <em>Document Instance</em>, and (2) arbitrary
+specification for standardized use in a <a href="#terms-document-instance">document instance</a>, and (2) arbitrary
metadata defined outside of the scope of this specification, whose use and
semantics depend entirely upon an application's use of TTML Content.</p><div class="div2">
<h3><a id="metadata-element-vocabulary"></a>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 metadata that is expected to be commonly
-used in a <em>Document Instances</em>:
+used in a <a href="#terms-document-instance">document instancea</a>:
</p><ul><li><p><a href="#metadata-vocabulary-title"><b>12.1.2 ttm:title</b></a></p></li><li><p><a href="#metadata-vocabulary-desc"><b>12.1.3 ttm:desc</b></a></p></li><li><p><a href="#metadata-vocabulary-copyright"><b>12.1.4 ttm:copyright</b></a></p></li><li><p><a href="#metadata-vocabulary-agent"><b>12.1.5 ttm:agent</b></a></p></li><li><p><a href="#metadata-vocabulary-name"><b>12.1.6 ttm:name</b></a></p></li><li><p><a href="#metadata-vocabulary-actor"><b>12.1.7 ttm:actor</b></a></p></li></ul><div class="div3">
<h4><a id="metadata-vocabulary-metadata"></a>12.1.1 metadata</h4><p>The <code>metadata</code> element functions as a generic container for metadata
information.</p><p>Metadata information may be expressed with a <code>metadata</code> element by specifying
@@ -5157,7 +5165,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The meaning of a specific metadata item must be evaluated in the
context where it appears. The core vocabulary catalog permits an
arbitrary number of <code>metadata</code> element children on any
-<a href="#element-vocab-type-content">Content</a> element type. See specific element
+<a href="#terms-content-element">content element</a> type. See specific element
vocabulary definitions for any constraints that apply to such
usage.</p></div><p>The use of document metadata is illustrated by the following example.</p><a id="metadata-vocabulary-metadata-example-1"></a><table class="example"><caption>Example Fragment – Document Metadata</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -5271,7 +5279,7 @@
specifies the agent that plays the role of the actor.</p><p>A <code>ttm:agent</code> metadata item is considered to be significant only
when specified as a child of the <code>head</code> element or as a child of a
<code>metadata</code> element child of the <code>head</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>ttm:agent</code> element instance is typically referenced using a <code>ttm:agent</code>
-attribute on a <a href="#element-vocab-type-content">Content</a> element type.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If a character agent is played by multiple actors, then multiple character
+attribute on a <a href="#terms-content-element">content element</a> type.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If a character agent is played by multiple actors, then multiple character
agents may be specified (and referenced) wherein different definitions of the
character specify different actors.</p></div><p>The use of agent metadata is illustrated by the following example.</p><a id="metadata-vocabulary-agent-example-1"></a><table class="example"><caption>Example Fragment – Agent Metadata</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -5343,10 +5351,10 @@
<a href="#metadata-vocabulary-agent-example-1"><b>Example Fragment – Agent Metadata</b></a>.</p></div></div><div class="div2">
<h3><a id="metadata-attribute-vocabulary"></a>12.2 Metadata Attribute Vocabulary</h3><p>This section specifies the following attributes in the TT Metadata Namespace
for use with the <code>metadata</code> element and with certain
-<a href="#element-vocab-type-content">Content</a> element types:</p><ul><li><p><a href="#metadata-attribute-agent"><b>12.2.1 ttm:agent</b></a></p></li><li><p><a href="#metadata-attribute-role"><b>12.2.2 ttm:role</b></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Only certain metadata item attributes may be used with <a href="#element-vocab-type-content">Content</a> elements. See
-the definitions of <a href="#element-vocab-type-content">Content</a> elements to determine permissible usage.</p></div><div class="div3">
+<a href="#terms-content-element">content element</a> types:</p><ul><li><p><a href="#metadata-attribute-agent"><b>12.2.1 ttm:agent</b></a></p></li><li><p><a href="#metadata-attribute-role"><b>12.2.2 ttm:role</b></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Only certain metadata item attributes may be used with <a href="#terms-content-element">content element</a>. See
+the definitions of <a href="#terms-content-element">content elements</a> to determine permissible usage.</p></div><div class="div3">
<h4><a id="metadata-attribute-agent"></a>12.2.1 ttm:agent</h4><p>The <code>ttm:agent</code> attribute takes an <code>IDREFS</code>
-value, and is used with certain <a href="#element-vocab-type-content">Content</a> elements to designate the
+value, and is used with certain <a href="#terms-content-element">content elements</a> to designate the
agents that perform or are
involved in the performance of the content.</p><p>If specified, a <code>ttm:agent</code> attribute must reference <em>significant</em>
<code>ttm:agent</code> element instances.</p><p>The same IDREF, <em>ID</em>, should not appear more than once in the value of a <code>ttm:agent</code> attribute.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This constraint is intended to discourage the use of redundant agent references.</p></div><p>An example of the <code>ttm:agent</code> attribute is shown above in
@@ -5354,7 +5362,7 @@
<h4><a id="metadata-attribute-role"></a>12.2.2 ttm:role</h4><p>The <code>ttm:role</code> attribute may be used by a content author
to express
the roles, functions, or characteristics
-of some <a href="#element-vocab-type-content">Content</a> element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
+of some <a href="#terms-content-element">content element</a> that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
syntax, where
the syntactic element <em>S</em> must adhere to production
[3] <code>S</code> as defined by <a href="#xml10">[XML 1.0]</a> §
@@ -5396,17 +5404,18 @@
a registry for role values is available at
<a href="http://www.w3.org/wiki/TTML/RoleRegistry">http://www.w3.org/wiki/TTML/RoleRegistry</a>
in order to promote interoperability and collision avoidance.</p></div></div></div></div></div><div class="back"><div class="div1">
-<h2><a id="reduced-infoset"></a>A Reduced XML Infoset</h2><p><em>This appendix is normative.</em></p><p>For the purposes of this specification, a <em>Reduced XML Infoset</em> is
+<h2><a id="reduced-infoset"></a>A Reduced XML Infoset</h2><p><em>This appendix is normative.</em></p><p>For the purposes of this specification, a <a href="#terms-reduced-xml-infoset">reduced xml infoset</a> is
an XML Information Set <a href="#infoset">[XML InfoSet]</a> that consists of only the following information items
and information item properties:</p><div class="div2">
<h3><a id="reduced-infoset-document"></a>A.1 Document Information Item</h3><ul><li><p><code>[document element]</code></p></li></ul></div><div class="div2">
-<h3><a id="reduced-infoset-element"></a>A.2 Element Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[children]</code></p></li><li><p><code>[attributes]</code></p></li></ul><p>Child information items <code>[children]</code> are reduced to
-only element and character information items.</p></div><div class="div2">
-<h3><a id="reduced-infoset-attribute"></a>A.3 Attribute Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[normalized value]</code></p></li></ul></div><div class="div2">
+<h3><a id="reduced-infoset-element"></a>A.2 Element Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[children]</code></p></li><li><p><code>[attributes]</code></p></li></ul><p>Child information items <code>[children]</code> are reduced to only
+<a href="terms-element-information-item">element information items</a> and
+<a href="terms-character-information-item">character information items</a>.</p></div><div class="div2">
+<h3><a id="reduced-infoset-attribute"></a>A.3 Attribute Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[normalized value]</code></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>See also <a href="terms-attribute-information-item">attribute information item</a>.</p></div></div><div class="div2">
<h3><a id="reduced-infoset-character"></a>A.4 Character Information Item</h3><ul><li><p><code>[character code]</code></p></li></ul><p>Contiguous character information items are not required to be represented distinctly,
-but may be aggregated (chunked) into a sequence of character codes (i.e., a character string).</p></div></div><div class="div1">
+but may be aggregated (chunked) into a sequence of character codes (i.e., a character string).</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See also <a href="terms-character-information-item">character information item</a>.</p></div></div></div><div class="div1">
<h2><a id="schemas"></a>B Schemas</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following schemas for use with
-<em>Document Instances</em>:</p><ul><li><p>Relax NG, Compact Syntax (RNC) Schema</p></li><li><p>XML Schema Definition (XSD) Schema</p></li></ul><p>In any case where a schema specified by this appendix differs from the
+<a href="#terms-document-instance">document instances</a>:</p><ul><li><p>Relax NG, Compact Syntax (RNC) Schema</p></li><li><p>XML Schema Definition (XSD) Schema</p></li></ul><p>In any case where a schema specified by this appendix differs from the
normative definitions of document type, element type, or attribute type
as defined by the body of this specification, then the body of this
specification takes precedence.</p><div class="div2">
@@ -5428,7 +5437,7 @@
<h2><a id="features"></a>D Features</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies (1) a set of feature designations, each of which
labels one or more syntactic and/or semantic features defined by this
specification, and (2) for each designated feature, whether the feature is mandatory
-or optional for a transformation or presentation processor.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A TTML processor is said to <em>implement the transformation semantics</em> or
+or optional for a transformation or <a href="#terms-presentation-processor">presentation processor</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A TTML processor is said to <em>implement the transformation semantics</em> or
<em>implement the presentation semantics</em> of feature designation <em>F</em>
if it satisfies the requirements of this appendix with respect to the definition of
feature designation <em>F</em> as pertains to transformation or
@@ -5450,26 +5459,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><table border="1" class="ednote" summary="Editorial note: #animation subset features"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: #animation subset features</b></td><td align="right" valign="top">2013-08-26</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add fine grained subset features of #animation.</td></tr></table><div class="div3">
-<h4><a id="feature-animation"></a>D.1.1 #animation</h4><p>A TTML transformation processor supports the <code>#animation</code>
+<h4><a id="feature-animation"></a>D.1.1 #animation</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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-animation"><code>animation</code></a></p></li><li><p><a href="#animation-vocabulary-animate"><code>animate</code></a></p></li><li><p><a href="#animation-vocabulary-set"><code>set</code></a></p></li></ul><p>A TTML 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-animation"><code>animation</code></a></p></li><li><p><a href="#animation-vocabulary-animate"><code>animate</code></a></p></li><li><p><a href="#animation-vocabulary-set"><code>set</code></a></p></li></ul><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-backgroundColor"></a>D.1.2 #backgroundColor</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor"></a>D.1.2 #backgroundColor</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-backgroundColor-block"></a>D.1.3 #backgroundColor-block</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor-block"></a>D.1.3 #backgroundColor-block</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+block area during presentation processing.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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
@@ -5477,11 +5486,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 id="feature-backgroundColor-inline"></a>D.1.4 #backgroundColor-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor-inline"></a>D.1.4 #backgroundColor-inline</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+inline area during presentation processing.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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
@@ -5489,10 +5498,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 id="feature-backgroundColor-region"></a>D.1.5 #backgroundColor-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor-region"></a>D.1.5 #backgroundColor-region</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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
@@ -5502,271 +5511,271 @@
.</p></div><div class="div3">
<h4><a id="feature-bidi"></a>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 id="feature-border"></a>D.1.7 #border</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-border"></a>D.1.7 #border</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> supports the
<code>#border</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-border"><code>tts:border</code></a>
-attribute.</p><p>A TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> supports the
<code>#border</code> feature if it (1) implements presentation semantic support
for the <a href="#style-attribute-border"><code>tts:border</code></a>
attribute
and (2) is capable of displaying or generating an output display
signal that distinguishes between at least sixteen (16) values of border colors,
including all primary and secondary colors of the SRGB color space.</p><table border="1" class="ednote" summary="Editorial note: Features related to tts:border"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Features related to tts:border</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add additional border related features.</td></tr></table></div><div class="div3">
-<h4><a id="feature-cellResolution"></a>D.1.8 #cellResolution</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-cellResolution"></a>D.1.8 #cellResolution</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-clockMode"></a>D.1.9 #clockMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode"></a>D.1.9 #clockMode</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-clockMode-gps"></a>D.1.10 #clockMode-gps</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode-gps"></a>D.1.10 #clockMode-gps</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-clockMode-local"></a>D.1.11 #clockMode-local</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode-local"></a>D.1.11 #clockMode-local</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-clockMode-utc"></a>D.1.12 #clockMode-utc</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode-utc"></a>D.1.12 #clockMode-utc</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-color"></a>D.1.13 #color</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-color"></a>D.1.13 #color</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-content"></a>D.1.14 #content</h4><p>A TTML transformation processor supports the <code>#content</code>
+<h4><a id="feature-content"></a>D.1.14 #content</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-core"></a>D.1.15 #core</h4><p>A TTML transformation processor supports the <code>#core</code>
+<h4><a id="feature-core"></a>D.1.15 #core</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-direction"></a>D.1.16 #direction</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-direction"></a>D.1.16 #direction</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-display"></a>D.1.17 #display</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display"></a>D.1.17 #display</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-display-block"></a>D.1.18 #display-block</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display-block"></a>D.1.18 #display-block</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+block area during presentation processing.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-display-inline"></a>D.1.19 #display-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display-inline"></a>D.1.19 #display-inline</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+inline area during presentation processing.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-display-region"></a>D.1.20 #display-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display-region"></a>D.1.20 #display-region</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-displayAlign"></a>D.1.21 #displayAlign</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-displayAlign"></a>D.1.21 #displayAlign</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-dropMode"></a>D.1.22 #dropMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode"></a>D.1.22 #dropMode</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-dropMode-dropNTSC"></a>D.1.23 #dropMode-dropNTSC</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode-dropNTSC"></a>D.1.23 #dropMode-dropNTSC</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-dropMode-dropPAL"></a>D.1.24 #dropMode-dropPAL</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode-dropPAL"></a>D.1.24 #dropMode-dropPAL</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-dropMode-nonDrop"></a>D.1.25 #dropMode-nonDrop</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode-nonDrop"></a>D.1.25 #dropMode-nonDrop</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-extent"></a>D.1.26 #extent</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-extent"></a>D.1.26 #extent</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-extent-region"></a>D.1.27 #extent-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-extent-region"></a>D.1.27 #extent-region</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-extent-root"></a>D.1.28 #extent-root</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-extent-root"></a>D.1.28 #extent-root</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute when applied to the <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontFamily"></a>D.1.29 #fontFamily</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontFamily"></a>D.1.29 #fontFamily</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontFamily-generic"></a>D.1.30 #fontFamily-generic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontFamily-generic"></a>D.1.30 #fontFamily-generic</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontFamily-non-generic"></a>D.1.31 #fontFamily-non-generic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontFamily-non-generic"></a>D.1.31 #fontFamily-non-generic</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontSize"></a>D.1.32 #fontSize</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontSize"></a>D.1.32 #fontSize</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontSize-anamorphic"></a>D.1.33 #fontSize-anamorphic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontSize-anamorphic"></a>D.1.33 #fontSize-anamorphic</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute that consist of two <a href="#style-value-length"><length></a> specifications.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontSize-isomorphic"></a>D.1.34 #fontSize-isomorphic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontSize-isomorphic"></a>D.1.34 #fontSize-isomorphic</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute that consist of a single <a href="#style-value-length"><length></a> specification.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontStyle"></a>D.1.35 #fontStyle</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontStyle"></a>D.1.35 #fontStyle</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontStyle-italic"></a>D.1.36 #fontStyle-italic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontStyle-italic"></a>D.1.36 #fontStyle-italic</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontStyle-oblique"></a>D.1.37 #fontStyle-oblique</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontStyle-oblique"></a>D.1.37 #fontStyle-oblique</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontWeight"></a>D.1.38 #fontWeight</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontWeight"></a>D.1.38 #fontWeight</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-fontWeight-bold"></a>D.1.39 #fontWeight-bold</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontWeight-bold"></a>D.1.39 #fontWeight-bold</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-frameRate"></a>D.1.40 #frameRate</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-frameRate"></a>D.1.40 #frameRate</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-frameRateMultiplier"></a>D.1.41 #frameRateMultiplier</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-frameRateMultiplier"></a>D.1.41 #frameRateMultiplier</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-layout"></a>D.1.42 #layout</h4><p>A TTML transformation processor supports the <code>#layout</code>
+<h4><a id="feature-layout"></a>D.1.42 #layout</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-length"></a>D.1.43 #length</h4><p>A TTML transformation processor supports the <code>#length</code>
+<h4><a id="feature-length"></a>D.1.43 #length</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the <code>#length</code>
+style value expression.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length</code> is intended to imply support for the following features:
@@ -5778,10 +5787,10 @@
<code>#length-em</code>,
<code>#length-percentage</code>, and
<code>#length-pixel</code>.</p></div></div><div class="div3">
-<h4><a id="feature-length-cell"></a>D.1.44 #length-cell</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-cell"></a>D.1.44 #length-cell</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+that use <code>c</code> (cell) units.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-cell</code> does not, by itself, imply support for
@@ -5789,10 +5798,10 @@
<code>#length-real</code>,
<code>#length-positive</code>, or
<code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-length-em"></a>D.1.45 #length-em</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-em"></a>D.1.45 #length-em</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+that use <code>em</code> (EM) units.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-em</code> does not, by itself, imply support for
@@ -5800,30 +5809,30 @@
<code>#length-real</code>,
<code>#length-positive</code>, or
<code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-length-integer"></a>D.1.46 #length-integer</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-integer"></a>D.1.46 #length-integer</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+expression.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-integer</code> does not, by itself, imply support for
<code>#length-positive</code> or
<code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-length-negative"></a>D.1.47 #length-negative</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-negative"></a>D.1.47 #length-negative</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+expression.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-negative</code> does not, by itself, imply support for
<code>#length-integer</code> or
<code>#length-real</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-length-percentage"></a>D.1.48 #length-percentage</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-percentage"></a>D.1.48 #length-percentage</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+expression.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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.
@@ -5832,10 +5841,10 @@
<code>#length-real</code>,
<code>#length-positive</code>, or
<code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-length-pixel"></a>D.1.49 #length-pixel</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-pixel"></a>D.1.49 #length-pixel</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+that use <code>px</code> (pixel) units.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-pixel</code> does not, by itself, imply support for
@@ -5843,10 +5852,10 @@
<code>#length-real</code>,
<code>#length-positive</code>, or
<code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-length-positive"></a>D.1.50 #length-positive</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-positive"></a>D.1.50 #length-positive</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+expression.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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.
@@ -5855,10 +5864,10 @@
expressions.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-positive</code> does not, by itself, imply support for
<code>#length-integer</code> or
<code>#length-real</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-length-real"></a>D.1.51 #length-real</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-real"></a>D.1.51 #length-real</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+expression.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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.
@@ -5867,122 +5876,122 @@
expressions as well as real valued expressions.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-real</code> does not, by itself, imply support for
<code>#length-positive</code> or
<code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a id="feature-lineBreak-uax14"></a>D.1.52 #lineBreak-uax14</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-lineBreak-uax14"></a>D.1.52 #lineBreak-uax14</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+target document space.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-lineHeight"></a>D.1.53 #lineHeight</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-lineHeight"></a>D.1.53 #lineHeight</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-markerMode"></a>D.1.54 #markerMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-markerMode"></a>D.1.54 #markerMode</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-markerMode-continuous"></a>D.1.55 #markerMode-continuous</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-markerMode-continuous"></a>D.1.55 #markerMode-continuous</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-markerMode-discontinuous"></a>D.1.56 #markerMode-discontinuous</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-markerMode-discontinuous"></a>D.1.56 #markerMode-discontinuous</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-metadata"></a>D.1.57 #metadata</h4><p>A TTML transformation processor supports the <code>#metadata</code>
+<h4><a id="feature-metadata"></a>D.1.57 #metadata</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-nested-div"></a>D.1.58 #nested-div</h4><p>A TTML transformation processor supports the <code>#nested-div</code>
+<h4><a id="feature-nested-div"></a>D.1.58 #nested-div</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the <code>#nested-div</code>
+<a href="#content-vocabulary-div"><code>div</code></a> elements.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-nested-span"></a>D.1.59 #nested-span</h4><p>A TTML transformation processor supports the <code>#nested-span</code>
+<h4><a id="feature-nested-span"></a>D.1.59 #nested-span</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the <code>#nested-span</code>
+<a href="#content-vocabulary-span"><code>span</code></a> elements.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-opacity"></a>D.1.60 #opacity</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-opacity"></a>D.1.60 #opacity</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-origin"></a>D.1.61 #origin</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-origin"></a>D.1.61 #origin</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-overflow"></a>D.1.62 #overflow</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-overflow"></a>D.1.62 #overflow</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-overflow-visible"></a>D.1.63 #overflow-visible</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-overflow-visible"></a>D.1.63 #overflow-visible</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-padding"></a>D.1.64 #padding</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding"></a>D.1.64 #padding</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-padding-1"></a>D.1.65 #padding-1</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-1"></a>D.1.65 #padding-1</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the <code>#padding-1</code>
+that consist of one <a href="#style-value-length"><length></a> specification.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-padding-2"></a>D.1.66 #padding-2</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-2"></a>D.1.66 #padding-2</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the <code>#padding-2</code>
+that consist of two <a href="#style-value-length"><length></a> specification.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-padding-3"></a>D.1.67 #padding-3</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-3"></a>D.1.67 #padding-3</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the <code>#padding-3</code>
+that consist of three <a href="#style-value-length"><length></a> specification.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-padding-4"></a>D.1.68 #padding-4</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-4"></a>D.1.68 #padding-4</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the <code>#padding-4</code>
+that consist of four <a href="#style-value-length"><length></a> specification.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-pixelAspectRatio"></a>D.1.69 #pixelAspectRatio</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-pixelAspectRatio"></a>D.1.69 #pixelAspectRatio</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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">
@@ -5997,202 +6006,202 @@
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 id="feature-profile"></a>D.1.71 #profile</h4><p>A TTML transformation processor supports the <code>#profile</code>
+<h4><a id="feature-profile"></a>D.1.71 #profile</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-showBackground"></a>D.1.72 #showBackground</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-showBackground"></a>D.1.72 #showBackground</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-structure"></a>D.1.73 #structure</h4><p>A TTML transformation processor supports the <code>#structure</code>
+<h4><a id="feature-structure"></a>D.1.73 #structure</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-styling"></a>D.1.74 #styling</h4><p>A TTML transformation processor supports the <code>#styling</code>
+<h4><a id="feature-styling"></a>D.1.74 #styling</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-styling-chained"></a>D.1.75 #styling-chained</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-chained"></a>D.1.75 #styling-chained</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-styling-inheritance-content"></a>D.1.76 #styling-inheritance-content</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-inheritance-content"></a>D.1.76 #styling-inheritance-content</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+<a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-styling-inheritance-region"></a>D.1.77 #styling-inheritance-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-inheritance-region"></a>D.1.77 #styling-inheritance-region</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+<a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-styling-inline"></a>D.1.78 #styling-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-inline"></a>D.1.78 #styling-inline</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-styling-nested"></a>D.1.79 #styling-nested</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-nested"></a>D.1.79 #styling-nested</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-styling-referential"></a>D.1.80 #styling-referential</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-referential"></a>D.1.80 #styling-referential</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-subFrameRate"></a>D.1.81 #subFrameRate</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-subFrameRate"></a>D.1.81 #subFrameRate</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textAlign"></a>D.1.82 #textAlign</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textAlign"></a>D.1.82 #textAlign</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textAlign-absolute"></a>D.1.83 #textAlign-absolute</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textAlign-absolute"></a>D.1.83 #textAlign-absolute</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textAlign-relative"></a>D.1.84 #textAlign-relative</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textAlign-relative"></a>D.1.84 #textAlign-relative</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textDecoration"></a>D.1.85 #textDecoration</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration"></a>D.1.85 #textDecoration</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textDecoration-over"></a>D.1.86 #textDecoration-over</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration-over"></a>D.1.86 #textDecoration-over</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textDecoration-through"></a>D.1.87 #textDecoration-through</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration-through"></a>D.1.87 #textDecoration-through</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textDecoration-under"></a>D.1.88 #textDecoration-under</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration-under"></a>D.1.88 #textDecoration-under</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textOrientation"></a>D.1.89 #textOrientation</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textOrientation"></a>D.1.89 #textOrientation</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> supports the
<code>#textOrientation</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-textOrientation"><code>tts:textOrientation</code></a>
-attribute.</p><p>A TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> supports the
<code>#textOrientation</code> feature if it implements presentation semantic support
for the <a href="#style-attribute-textOrientation"><code>tts:textOrientation</code></a>
attribute.</p></div><div class="div3">
-<h4><a id="feature-textOutline"></a>D.1.90 #textOutline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textOutline"></a>D.1.90 #textOutline</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textOutline-blurred"></a>D.1.91 #textOutline-blurred</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textOutline-blurred"></a>D.1.91 #textOutline-blurred</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute that includes a blur radius specification.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-textOutline-unblurred"></a>D.1.92 #textOutline-unblurred</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textOutline-unblurred"></a>D.1.92 #textOutline-unblurred</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute that does not include a blur radius specification.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-tickRate"></a>D.1.93 #tickRate</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-tickRate"></a>D.1.93 #tickRate</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-timeBase-clock"></a>D.1.94 #timeBase-clock</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeBase-clock"></a>D.1.94 #timeBase-clock</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-timeBase-media"></a>D.1.95 #timeBase-media</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeBase-media"></a>D.1.95 #timeBase-media</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-timeBase-smpte"></a>D.1.96 #timeBase-smpte</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeBase-smpte"></a>D.1.96 #timeBase-smpte</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute and if it supports the <a href="#feature-dropMode"><code>#dropMode</code></a> feature.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-timeContainer"></a>D.1.97 #timeContainer</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeContainer"></a>D.1.97 #timeContainer</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-time-clock"></a>D.1.98 #time-clock</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-clock"></a>D.1.98 #time-clock</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+</pre></div><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-time-clock-with-frames"></a>D.1.99 #time-clock-with-frames</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-clock-with-frames"></a>D.1.99 #time-clock-with-frames</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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
@@ -6202,20 +6211,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 TTML presentation processor supports the
+</pre></div><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-time-offset"></a>D.1.100 #time-offset</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-offset"></a>D.1.100 #time-offset</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+</pre></div><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-time-offset-with-frames"></a>D.1.101 #time-offset-with-frames</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-offset-with-frames"></a>D.1.101 #time-offset-with-frames</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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
@@ -6225,11 +6234,11 @@
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
<timeExpression>
: time-count fraction? "f"
-</pre></div><p>A TTML presentation processor supports the
+</pre></div><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-time-offset-with-ticks"></a>D.1.102 #time-offset-with-ticks</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-offset-with-ticks"></a>D.1.102 #time-offset-with-ticks</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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
@@ -6237,12 +6246,12 @@
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
<timeExpression>
: time-count fraction? "t"
-</pre></div><p>A TTML presentation processor supports the
+</pre></div><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-timing"></a>D.1.103 #timing</h4><p>A TTML transformation processor supports the <code>#timing</code>
+<h4><a id="feature-timing"></a>D.1.103 #timing</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML 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 <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-transformation"></a>D.1.104 #transformation</h4><p>A TTML processor supports the
@@ -6250,99 +6259,99 @@
(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 the transformation semantics of 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 id="feature-unicodeBidi"></a>D.1.105 #unicodeBidi</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-unicodeBidi"></a>D.1.105 #unicodeBidi</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-visibility"></a>D.1.106 #visibility</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility"></a>D.1.106 #visibility</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-visibility-block"></a>D.1.107 #visibility-block</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility-block"></a>D.1.107 #visibility-block</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+block area during presentation processing.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-visibility-inline"></a>D.1.108 #visibility-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility-inline"></a>D.1.108 #visibility-inline</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+inline area during presentation processing.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-visibility-region"></a>D.1.109 #visibility-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility-region"></a>D.1.109 #visibility-region</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-wrapOption"></a>D.1.110 #wrapOption</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-wrapOption"></a>D.1.110 #wrapOption</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-writingMode"></a>D.1.111 #writingMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode"></a>D.1.111 #writingMode</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-writingMode-vertical"></a>D.1.112 #writingMode-vertical</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-vertical"></a>D.1.112 #writingMode-vertical</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-writingMode-horizontal"></a>D.1.113 #writingMode-horizontal</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-horizontal"></a>D.1.113 #writingMode-horizontal</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-writingMode-horizontal-lr"></a>D.1.114 #writingMode-horizontal-lr</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-horizontal-lr"></a>D.1.114 #writingMode-horizontal-lr</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-writingMode-horizontal-rl"></a>D.1.115 #writingMode-horizontal-rl</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-horizontal-rl"></a>D.1.115 #writingMode-horizontal-rl</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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 id="feature-zIndex"></a>D.1.116 #zIndex</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-zIndex"></a>D.1.116 #zIndex</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> 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 TTML presentation processor supports the
+attribute.</p><p>A TTML <a href="#terms-presentation-processor">presentation processor</a> 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">
@@ -6350,11 +6359,11 @@
enumerates every defined feature designation (expressed without the TT
Feature Namespace), and, for each designated feature, specifies
whether the feature must be implemented, i.e., is mandatory (M), or may be implemented, i.e.,
-is optional (O), for transformation and presentation processors.</p><a id="feature-support-table"></a><table class="common"><caption>Table D-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-border"><code>#border</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-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-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-textOrientation"><code>#textOrientation</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,
+is optional (O), for transformation and <a href="#terms-presentation-processor">presentation processor</a>s.</p><a id="feature-support-table"></a><table class="common"><caption>Table D-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-border"><code>#border</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-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-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-textOrientation"><code>#textOrientation</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 D-2 – Mandatory Features - Transformation</b></a>, enumerates all
-mandatory features for a TTML Transformation Processor, providing additional
+mandatory features for a TTML <a href="#terms-transformation-processor">transformation processor</a>, providing additional
comments to summarize the context of usage or the nature of the feature.
-The <em>Profile Definition Document</em> that defines the corresponding
+The <a href="#terms-profile-definition-document">profile definition document</a> that defines the corresponding
DFXP Transformation Profile is specified in
<a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a>.
</p><a id="feature-transformation-mandatory-table"></a><table class="common"><caption>Table D-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>
@@ -6376,9 +6385,9 @@
<a href="#timing-attribute-end">@<code>end</code></a>
</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td></td></tr></tbody></table><p>For the sake of convenience, the following table,
<a href="#feature-presentation-mandatory-table"><b>Table D-3 – Mandatory Features - Presentation</b></a>, enumerates all
-mandatory features for a TTML Presentation Processor, providing additional
+mandatory features for a TTML <a href="#terms-presentation-processor">presentation processor</a>, providing additional
comments to summarize the context of usage or the nature of the feature.
-The <em>Profile Definition Document</em> that defines the corresponding
+The <a href="#terms-profile-definition-document">profile definition document</a> that defines the corresponding
DFXP Presentation Profile is specified in
<a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a>.
</p><a id="feature-presentation-mandatory-table"></a><table class="common"><caption>Table D-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>
@@ -6426,7 +6435,7 @@
<code>designation</code> token that takes the form of a fragment
identifier.</p></div></div><div class="div1">
<h2><a id="profiles"></a>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>The SDP US profile is defined in
-<a href="http://www.w3.org/TR/ttml10-sdp-us/">TTML Simple Delivery Profile for Closed Captions (US)</a>.</p><p>Each TTML profile is defined in terms of a <em>Profile Definition Document</em>,
+<a href="http://www.w3.org/TR/ttml10-sdp-us/">TTML Simple Delivery Profile for Closed Captions (US)</a>.</p><p>Each TTML profile is defined in terms of a <a href="#terms-profile-definition-document">profile definition document</a>,
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 id="profile-dfxp-transformation"></a>F.1 DFXP Transformation Profile</h3><p>The DFXP Transformation Profile is intended to be used to
@@ -6994,7 +7003,7 @@
<h2><a id="derivation"></a>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
vocabulary, separately describing derivation of elements and
attributes.</p><div class="div2">
-<h3><a id="d3e20498"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
+<h3><a id="d3e21440"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
specifies a TTML element vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
@@ -7045,13 +7054,13 @@
direct expression of the target attribute name and value by use of a
<code>tts:*</code> attribute.</p></li><li><p>CSS style specification syntax is mapped to XML by use of
attributes defined in the TT Style Namespace.</p></li><li><p>The <code>xml:id</code> attribute is defined for use on all element types.</p></li><li><p>The <code>style</code> attribute is supported only on
-<a href="#element-vocab-type-content">Content</a> elements.</p></li><li><p>Derived from the use of <code>@requiredExtensions</code>
+<a href="#terms-content-element">content element</a>.</p></li><li><p>Derived from the use of <code>@requiredExtensions</code>
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><li><p>Conceptually derived from existing <code>tt:layout</code> element,
which is a generic container for layout specifications, but for use
in defining animation specifications that apply to targetted elements.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e21015"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
+<h3><a id="d3e21957"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
specifies a TTML attribute vocabulary item; the second column specifies the
syntactic and/or semantic model on which the vocabulary item is based;
the third column specifies the reference that defines
@@ -7076,7 +7085,7 @@
-<code>excl</code>,
-<code>none</code>;
no default attribute value
-</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td></td><td>used to attribute agent of content</td><td></td></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td></td><td>used to attribute role of content</td><td></td></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td></td><td>expresses uniform grid resolution for cell based coordinates</td><td></td></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td></td><td>determines how to interpret time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td></td><td>expresses integral frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td></td><td>used to express non-integral, rational frame rates</td><td></td></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td></td><td>expresses marker continuity semantics</td><td></td></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td></td><td>expresses pixel aspect ratio of related media</td><td></td></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td></td><td>expresses profile of TTML used by a <em>Document Instance</em></td><td></td></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td></td><td>expresses frame counting (drop) modes</td><td></td></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td></td><td>expresses sub-frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td></td><td>used to interpret tick based time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td></td><td>used to interpret semantics of time expressions</td><td></td></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-border"><code>tts:border</code></a></td><td><code>border</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only <code>auto</code>, <code>none</code></td><td></td></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a></td><td><code>font-style</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code>backslant</code></td><td>1</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code>bolder</code>, -<code>lighter</code>, -<code><number></code></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code><number></code>, -<code><space></code></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td>-<code>inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code>auto</code>, -<code>error-if-overflow</code></td><td></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>8</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil3">[SMIL 3.0]</a></td><td>-<code>inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,9,12</td></tr><tr><td><a href="#style-attribute-textOrientation"><code>tts:textOrientation</code></a></td><td><code>text-orientation</code></td><td><a href="#css3-wm">[CSS Writing Modes Level 3]</a></td><td>
+</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td></td><td>used to attribute agent of content</td><td></td></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td></td><td>used to attribute role of content</td><td></td></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td></td><td>expresses uniform grid resolution for cell based coordinates</td><td></td></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td></td><td>determines how to interpret time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td></td><td>expresses integral frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td></td><td>used to express non-integral, rational frame rates</td><td></td></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td></td><td>expresses marker continuity semantics</td><td></td></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td></td><td>expresses pixel aspect ratio of related media</td><td></td></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td></td><td>expresses profile of TTML used by a <a href="#terms-document-instance">document instance</a></td><td></td></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td></td><td>expresses frame counting (drop) modes</td><td></td></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td></td><td>expresses sub-frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td></td><td>used to interpret tick based time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td></td><td>used to interpret semantics of time expressions</td><td></td></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-border"><code>tts:border</code></a></td><td><code>border</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only <code>auto</code>, <code>none</code></td><td></td></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a></td><td><code>font-style</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code>backslant</code></td><td>1</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code>bolder</code>, -<code>lighter</code>, -<code><number></code></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code><number></code>, -<code><space></code></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td>-<code>inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code>, -<code>auto</code>, -<code>error-if-overflow</code></td><td></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>8</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil3">[SMIL 3.0]</a></td><td>-<code>inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<code>inherit</code></td><td>1,9,12</td></tr><tr><td><a href="#style-attribute-textOrientation"><code>tts:textOrientation</code></a></td><td><code>text-orientation</code></td><td><a href="#css3-wm">[CSS Writing Modes Level 3]</a></td><td>
-<code>inherit</code>,
-<code>sideways-left</code>,
-<code>sideways-right</code>,
@@ -7143,9 +7152,9 @@
<h2><a id="qa"></a>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
Framework Specifications Guidelines</a> <a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e21995"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a id="d3e22937"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
clause</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e22159"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e23101"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
TTML <a href="#doctypes">Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
@@ -7158,10 +7167,10 @@
possible a temporal ordering of content that follows temporal
presentation order;</p></li><li><p>constrains content models to prevent arbitrary nested content
structures;</p></li></ul><p>One possible means by which TTML Content may be streamed is to
-partition a <em>Document Instance</em>'s information set into
+partition a <a href="#terms-document-instance">document instance</a>'s information set into
non-overlapping fragments, where one particular fragment, call it the
<em>root fragment</em>, represents the front matter (head) of the
-<em>Document Instance</em> as well as its top level structural elements, and
+<a href="#terms-document-instance">document instance</a> as well as its top level structural elements, and
other fragments represent content whose time intervals are expected to
be active in parallel.</p><p>In applications that require arbitrary (random) entry into a
stream, i.e., the property of being able to start reading data at an
@@ -7169,17 +7178,17 @@
transmitted (inserted) into the stream in order to permit a decoder to
resynchronize and acquire sufficient structural information in the
information set in order to interpret subsequent content
-fragments.</p><p>An example of such a fragmentation of a <em>Document Instance</em> is
+fragments.</p><p>An example of such a fragmentation of a <a href="#terms-document-instance">document instance</a> is
shown in <a href="#fragment-streaming-graphic"><b>Figure 3 – Fragment Streaming</b></a>.</p><a id="fragment-streaming-graphic"></a><table class="example-images"><caption>Figure 3 – Fragment Streaming</caption><col span="1"><tbody><tr><td><img src="images/streaming.png" alt="Fragment Streaming"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not define a transport buffer model or a decoder
capabilities model.</p></div></div><div class="div1">
-<h2><a id="concrete-encoding"></a>M Concrete Encoding</h2><p><em>This appendix is normative.</em></p><p>In the absence of other requirements, a <em>Document Instance</em> should be concretely encoded as a
+<h2><a id="concrete-encoding"></a>M Concrete Encoding</h2><p><em>This appendix is normative.</em></p><p>In the absence of other requirements, a <a href="#terms-document-instance">document instance</a> should be concretely encoded as a
well-formed XML 1.0 <a href="#xml10">[XML 1.0]</a> document using the UTF-8 character encoding.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When using XML 1.0 <a href="#xml10">[XML 1.0]</a> as the concrete encoding of TTML, only the following named character entities are defined:
<code>&amp;</code>, <code>&lt;</code>, and <code>&gt;</code>.</p></div></div><div class="div1">
-<h2><a id="time-expression-semantics"></a>N Time Expression Semantics</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the semantics for interpreting time expressions in <em>Document Instances</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>local real time</em> as used below is intended to model a virtual real time clock in the document processing context, where
+<h2><a id="time-expression-semantics"></a>N Time Expression Semantics</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the semantics for interpreting time expressions in <a href="#terms-document-instance">document instances</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>local real time</em> as used below is intended to model a virtual real time clock in the document processing context, where
<em>local</em> means in the immediate proximity of the implementation of this processing context. The intent
of defining relationships with this virtual clock is to establish a locally valid physical realization of time for didactic purposes.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>play rate</em> as used below is intended to model a (possibly variable) parameter in the document processing context wherein
the rate of playback (or interpretation) of time may artificially dilated or narrowed, for example, when slowing down or speeding up the rate of
-playback of a <em>Related Media Object</em>. Without loss of generality, the following discussion assumes a fixed play(back) rate. In the case of
+playback of a <a href="#terms-related-media-object">related media object</a>. Without loss of generality, the following discussion assumes a fixed play(back) rate. In the case of
variable play rates, appropriate adjustments may need to be made to the resulting computations.</p></div><div class="div2">
<h3><a id="time-expression-semantics-clock"></a>N.1 Clock Time Base</h3><p>When operating with the <code>clock</code> time base, the following semantics apply for interpreting time expressions,
as defined by <a href="#timing-value-timeExpression"><timeExpression></a>, and their relationship to media time and local real time.</p><p>The clock time base <span class="strong"><code>C</code></span> is related to local real time <span class="strong"><code>R</code></span>
@@ -7207,8 +7216,8 @@
and where the value of <code>discontinuityOffset</code> is equal to the sum of leap seconds (and fractions thereof) that have been added (or subtracted) since the
most immediately prior midnight in the reference clock base;
<br><br>
-and <code>epochOffset</code> and <code>discontinuityOffset</code> are determined once and only once prior to the beginning of the <em>Root Temporal Extent</em> such that
-during the period between value determination and the beginning of the <em>Root Temporal Extent</em> there occurs no local midnight or reference clock base discontinuity.
+and <code>epochOffset</code> and <code>discontinuityOffset</code> are determined once and only once prior to the beginning of the <a href="#terms-root-temporal-extent">root temporal extent</a> such that
+during the period between value determination and the beginning of the <a href="#terms-root-temporal-extent">root temporal extent</a> there occurs no local midnight or reference clock base discontinuity.
<br></p></blockquote>
</td></tr></tbody></table><p>Time value expressions, as denoted by a <a href="#timing-value-timeExpression"><timeExpression></a>, are related to
clock time <span class="strong"><code>C</code></span> as follows:</p><a id="time-expressions-and-clock-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and Clock Time Relationship</caption><tbody><tr><td>
@@ -7242,14 +7251,14 @@
<blockquote><p><br>
<code>R = playRate * M + epochOffset</code>
<br><br>
-where <code>M ∈ ℜ</code>, <code>0 ≤ M < ∞</code>, <code>M</code> in seconds, with 0 corresponding to the beginning of the <em>Root Temporal Extent</em>;
+where <code>M ∈ ℜ</code>, <code>0 ≤ M < ∞</code>, <code>M</code> in seconds, with 0 corresponding to the beginning of the <a href="#terms-root-temporal-extent">root temporal extent</a>;
<br><br>
<code>playRate ∈ ℜ</code>, <code>−∞ < playRate < ∞</code>, <code>playRate</code> is unit-less, and where the value of
<code>playRate</code> is determined by the document processing context;
<br><br>
and <code>epochOffset ∈ ℜ</code>, <code>0 ≤ epochOffset < ∞</code>, <code>epochOffset</code> in seconds, with 0 corresponding to the beginning of
an epoch <code>E</code>, and where the value of <code>epochOffset</code> is the difference between the local real time at the beginning of the
-<em>Root Temporal Extent</em> and the local real time at the the beginning of epoch <code>E</code>, expressed in seconds.
+<a href="#terms-root-temporal-extent">root temporal extent</a> and the local real time at the the beginning of epoch <code>E</code>, expressed in seconds.
</p></blockquote>
</td></tr></tbody></table><p>Time value expressions, as denoted by a <a href="#timing-value-timeExpression"><timeExpression></a>, are related to
media time <span class="strong"><code>M</code></span> in accordance to the
@@ -7265,7 +7274,7 @@
parallel (<code>par</code>) or sequential (<code>seq</code>) semantics: if parallel or if sequential and no prior sibling
timed element exists, then <code>referenceBegin</code>
is the media time that corresponds to the beginning of the nearest ancestor time container or
-zero (0) if this time container is the <em>Root Temporal Extent</em>; otherwise, if sequential and a prior sibling
+zero (0) if this time container is the <a href="#terms-root-temporal-extent">root temporal extent</a>; otherwise, if sequential and a prior sibling
timed element exists, then <code>referenceBegin</code> is the media time that corresponds to the active end of the
immediate prior sibling timed element;
<br><br>
@@ -7290,14 +7299,15 @@
<br><br>
and <code>tickRate</code> is the computed value of the <code>ttp:tickRate</code> parameter;
<br></p></blockquote>
-</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If the computed <code>frameRateMultipler</code> ratio is not integral, then <code>effectiveFrameRate</code> will be a non-integral rational.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The above formalisms assumes that the <em>Root Temporal Extent</em> corresponds with the beginning of a related media object. If
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If the computed <code>frameRateMultipler</code> ratio is not integral, then <code>effectiveFrameRate</code> will be a non-integral rational.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The above formalisms assumes that the <a href="#terms-root-temporal-extent">root temporal extent</a> corresponds with the beginning of a related media object. If
this assumption doesn't hold, then an additional offset that accounts for the difference may be introduced when computing media time <code>M</code>.</p></div></div><div class="div2">
<h3><a id="time-expression-semantics-smpte"></a>N.3 SMPTE Time Base</h3><p>When operating with the <code>smpte</code> time base, the following semantics apply for interpreting time expressions,
as defined by <a href="#timing-value-timeExpression"><timeExpression></a>, and their relationship to media time and local real time.</p><p>If the computed value of the <code>ttp:markerMode</code> parameter is <code>discontinuous</code>, then there is no direct relationship between
time expressions and media time <span class="strong"><code>M</code></span> or local real time <span class="strong"><code>R</code></span>. In
-this case, time expressions refer to synchronization events (markers) emitted by the <em>Document Processing Context</em> when <em>SMPTE Time
-Codes</em> are encountered in the <em>Related Media Object</em>.</p><p>Otherwise, if the computed value of the <code>ttp:markerMode</code> parameter is <code>continuous</code>, then the relationships between time expressions and
-local real time and media time are as described below in terms of a <em>Synthetic SMPTE Document Syncbase</em>, here referred to as the
+this case, time expressions refer to synchronization events (markers) emitted by the <a href="#terms-document-processing-context">document processing context</a>
+when <a href="#terms-smpte-time-code">smpte time codes</a>
+are encountered in the <a href="#terms-related-media-object">related media object</a>.</p><p>Otherwise, if the computed value of the <code>ttp:markerMode</code> parameter is <code>continuous</code>, then the relationships between time expressions and
+local real time and media time are as described below in terms of a <a href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</a>, here referred to as the
SMPTE time base <span class="strong"><code>S</code></span>.</p><a id="time-expressions-and-smpte-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and SMPTE Time Relationship</caption><tbody><tr><td>
<blockquote><p><br>
<code>S = (countedFrames - droppedFrames + (subFrames / subFrameRate)) / effectiveFrameRate</code>
@@ -7340,7 +7350,7 @@
parallel (<code>par</code>) or sequential (<code>seq</code>) semantics: if parallel or if sequential and no prior sibling
timed element exists, then <code>referenceBegin</code>
is the SMPTE time that corresponds to the beginning of the nearest ancestor time container or
-zero (0) if this time container is the <em>Root Temporal Extent</em>; otherwise, if sequential and a prior sibling
+zero (0) if this time container is the <a href="#terms-root-temporal-extent">root temporal extent</a>; otherwise, if sequential and a prior sibling
timed element exists, then <code>referenceBegin</code> is the SMPTE time that corresponds to the active end of the
immediate prior sibling timed element;
<br></p></blockquote>
@@ -7373,7 +7383,7 @@
</pre></div>
</td></tr></tbody></table></div><div class="div2">
<h3><a id="roll-up-example"></a>O.2 Roll-Up Caption Example</h3><p>An example of roll-up captions. Roll-up effects are achieved by using overlapped time intervals, where zero, one, or two paragraphs appear in the region
-at a given time. Each paragraph consumes a single row (line) of the region since no wrapping occurs. Depending on whether a presentation processor supports
+at a given time. Each paragraph consumes a single row (line) of the region since no wrapping occurs. Depending on whether a <a href="#terms-presentation-processor">presentation processor</a> supports
<a href="#semantics-smooth-scrolling-recommendation">smooth scrolling between adjacent synchronic intermediate document instances</a>, the transitions, i.e., moving an
old paragraph (line) out and a new paragraph (line) in, will be either smooth or discrete.</p><a id="roll-up-example-1-s"></a><table class="example"><caption>Example – Roll-Up Captions</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt ttp:cellResolution="60 20" xml:lang="en" xmlns="http://www.w3.org/ns/ttml"