--- a/ttml2/spec/ttml2.xml Wed Aug 28 13:40:44 2013 -0600
+++ b/ttml2/spec/ttml2.xml Sun Sep 01 11:28:08 2013 -0600
@@ -153,7 +153,7 @@
<note>
<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 <emph>Document Instance</emph>. This use case is not
+as expressed by a Timed Text <loc href="#terms-document-instance">document instance</loc>. This use case is not
explicitly addressed by TTML mechanisms, but may be addressed by some
external multimedia integration technology, such as SMIL.</p>
</note>
@@ -184,7 +184,7 @@
</div2>
<div2 id="example">
<head>Document Example</head>
-<p>A TTML <emph>Document Instance</emph> consists of a <el>tt</el> document element that contains
+<p>A TTML <loc href="#terms-document-instance">document instance</loc> consists of a <el>tt</el> 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>
@@ -285,7 +285,7 @@
</tr>
</tbody>
</table>
-<p>The content of a <emph>Document Instance</emph> is expressed in its
+<p>The content of a <loc href="#terms-document-instance">document instance</loc> 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
@@ -479,7 +479,7 @@
</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 <emph>Document Instance</emph>. Content information
+styling and layout information are separately specified in a <loc href="#terms-document-instance">document instance</loc>. 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>
@@ -525,54 +525,60 @@
<div2 id="terms">
<head>Terminology</head>
<glist>
-<gitem>
-<label>Abstract Document Instance</label>
+<gitem id="terms-abstract-document-instance">
+<label>[abstract document instance]</label>
<def>
<p>An instance of an abstract data set as represented by a
-<emph>Reduced XML Infoset</emph>.</p>
+<loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc>.</p>
</def>
</gitem>
-<gitem>
-<label>Abstract Document Type</label>
+<gitem id="terms-abstract-document-type">
+<label>[abstract document type]</label>
<def>
<p>A set of constraints that defines a class of <emph>XML Information
Sets</emph> <bibref ref="infoset"/>.</p>
</def>
</gitem>
-<gitem>
-<label>Attribute Information Item</label>
+<gitem id="terms-attribute-information-item">
+<label>[attribute information item]</label>
<def>
<p>Each specified or defaulted attribute of an XML document corresponds with an attribute information
item as defined by <bibref ref="infoset"/>, §2.3.</p>
</def>
</gitem>
-<gitem>
-<label>Character Information Item</label>
+<gitem id="terms-character-information-item">
+<label>[character information item]</label>
<def>
<p>Each data character appearing in an XML document corresponds with a character information
item as defined by <bibref ref="infoset"/>, §2.6.</p>
</def>
</gitem>
-<gitem>
-<label>Computed Cell Size</label>
+<gitem id="terms-computed-cell-size">
+<label>[computed cell size]</label>
<def>
-<p>The size (extent) of a cell computed by dividing the width of the <emph>Root Container
-Region</emph> by the column count, i.e., the number of cells in the horizontal axis, and by dividing
-the height of the <emph>Root Container Region</emph> by the row count, i.e., the number of cells in the vertical
+<p>The size (extent) of a cell computed by dividing the width of the <loc href="#terms-root-container-region">root container region</loc>
+by the column count, i.e., the number of cells in the horizontal axis, and by dividing
+the height of the <loc href="#terms-root-container-region">root container region</loc> by the row count, i.e., the number of cells in the vertical
axis, where the column and row counts are determined by the <att>ttp:cellResolution</att> parameter attribute.</p>
</def>
</gitem>
-<gitem>
-<label>Content Processor</label>
+<gitem id="terms-content-element">
+<label>[content element]</label>
+<def>
+<p>Any of the element types defined by the <loc href="#element-vocab-type-content">Content Module</loc>.</p>
+</def>
+</gitem>
+<gitem id="terms-content-processor">
+<label>[content processor]</label>
<def>
<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>
</def>
</gitem>
-<gitem>
-<label>Content Profile</label>
+<gitem id="terms-content-profile">
+<label>[content profile]</label>
<def>
-<p>A collection of features and extensions that are (or may be) employed by
+<p>A collection of <loc href="#terms-feature">features</loc> and <loc href="#terms-extension">extensions</loc> that are (or may be) employed by
Timed Text Markup Language content.</p>
<ednote>
<name>Content Profile</name>
@@ -582,15 +588,15 @@
<p></p>
</def>
</gitem>
-<gitem>
-<label>Content Region</label>
+<gitem id="terms-content-region">
+<label>[content region]</label>
<def>
<p>A logical region into which rendered content is placed when modeling or
performing presentation processing.</p>
</def>
</gitem>
-<gitem>
-<label>Document Instance</label>
+<gitem id="terms-document-instance">
+<label>[document instance]</label>
<def>
<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
@@ -598,131 +604,136 @@
Timed Text document, etc.</p>
</def>
</gitem>
-<gitem>
-<label>Document Interchange Context</label>
+<gitem id="terms-document-interchange-context">
+<label>[document interchange context]</label>
<def>
-<p>The implied context or environment external to a <emph>Content Processor</emph> in
+<p>The implied context or environment external to a <loc href="#terms-content-processor">content processor</loc> 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>
</def>
</gitem>
-<gitem>
-<label>Document Processing Context</label>
+<gitem id="terms-document-processing-context">
+<label>[document processing context]</label>
<def>
-<p>The implied context or environment internal to a <emph>Content Processor</emph> in
+<p>The implied context or environment internal to a <loc href="#terms-content-processor">content processor</loc> 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
-<emph>Synthetic Document Syncbase</emph>.</p>
+<loc href="#terms-synthetic-document-syncbase">synthetic document syncbase</loc>.</p>
</def>
</gitem>
-<gitem>
-<label>Element Information Item</label>
+<gitem id="terms-element-information-item">
+<label>[element information item]</label>
<def>
<p>Each element appearing in an XML document corresponds with an element information
item as defined by <bibref ref="infoset"/>, §2.2.</p>
</def>
</gitem>
-<gitem>
-<label>Exchange Profile</label>
+<gitem id="terms-exchange-profile">
+<label>[exchange profile]</label>
<def>
<p>A profile of content that serves a set of needs for content interchange.</p>
</def>
</gitem>
-<gitem>
-<label>Extension</label>
+<gitem id="terms-extension">
+<label>[extension]</label>
<def>
<p>A syntactic or semantic expression or capability that is defined and
labeled (using a extension designation) in another (public or private)
specification.</p>
</def>
</gitem>
-<gitem>
-<label>Feature</label>
+<gitem id="terms-feature">
+<label>[feature]</label>
<def>
<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>
</def>
</gitem>
-<gitem>
-<label>Inline Animation</label>
+<gitem id="terms-inline-animation">
+<label>[inline animation]</label>
<def>
-<p>An animation specification that is defined inline as an immediate child of
-a <loc href="#element-vocab-type-content">Content</loc> or region element targetted by the animation. There is a one-to-one relation between
-an inline animation element and its parent <loc href="#element-vocab-type-content">Content</loc> or region element.
+<p>An <loc href="#animation-vocabulary-animate"><el>animate</el></loc> or <loc href="#animation-vocabulary-set"><el>set</el></loc> element
+that is defined inline as an immediate child of
+a <loc href="#terms-content-element">content element</loc> or <loc href="#layout-vocabulary-region"><el>region</el></loc> element targetted by the animation.
+There is a one-to-one relation between
+an inline animation element and its parent <loc href="#terms-content-element">content element</loc> or <loc href="#layout-vocabulary-region"><el>region</el></loc> element.
An inline animation does not specify an <att>xlink:href</att> attribute.</p>
</def>
</gitem>
-<gitem>
-<label>Inline Region</label>
+<gitem id="terms-inline-region">
+<label>[inline region]</label>
<def>
-<p>A region specification that is defined inline as an immediate child of
-a <loc href="#element-vocab-type-content">Content</loc> element to be selected into (targetted to) the region.
-There is a one-to-one relation between an inline region element and its
-parent <loc href="#element-vocab-type-content">Content</loc> element. An inline region is assigned its parent element's time interval as its active
+<p>A <loc href="#layout-vocabulary-region"><el>region</el></loc> element that is defined inline as an immediate child of
+a <loc href="#terms-content-element">content element</loc> to be selected into (targetted to) the region.
+There is a one-to-one relation between an inline <loc href="#layout-vocabulary-region"><el>region</el></loc> element and its
+parent <loc href="#terms-content-element">content element</loc>. An inline region is assigned its parent element's time interval as its active
time interval. No <att>region</att> attribute makes reference to an inline region.</p>
</def>
</gitem>
-<gitem>
-<label>Out-of-line Animation</label>
+<gitem id="terms-out-of-line-animation">
+<label>[out-of-line animation]</label>
<def>
-<p>An animation specification that is defined out-of-line from
-the <loc href="#element-vocab-type-content">Content</loc> or region element targetted by the animation. An out-of-line animation appears
-as a child of an <el>animation</el> element in the header (<el>head</el> element)
-of a <emph>Document Instance</emph>, and specifies an <att>xlink:href</att> 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 <loc href="#element-vocab-type-content">Content</loc> or region element.</p>
+<p>An <loc href="#animation-vocabulary-animate"><el>animate</el></loc> or <loc href="#animation-vocabulary-set"><el>set</el></loc> element that is defined out-of-line from
+the <loc href="#terms-content-element">content element</loc> or <loc href="#layout-vocabulary-region"><el>region</el></loc> element targetted by the animation.
+An out-of-line animation appears as a child of an <loc href="#animation-vocabulary-animation"><el>animation</el></loc> element in the header
+(<loc href="#document-structure-vocabulary-head"><el>head</el></loc> element)
+of a <loc href="#terms-document-instance">document instance</loc>, and specifies an <att>xlink:href</att> 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 <loc href="#terms-content-element">content element</loc> or
+<loc href="#layout-vocabulary-region"><el>region</el></loc> element.</p>
</def>
</gitem>
-<gitem>
-<label>Out-of-line Region</label>
+<gitem id="terms-out-of-line-region">
+<label>[out-of-line region]</label>
<def>
-<p>A region specification that is defined out-of-line from
-the <loc href="#element-vocab-type-content">Content</loc> element(s) to be selected into (targetted to) the region. An out-of-line region appears
-as a child of a <el>layout</el> element in the header (<el>head</el> element)
-of a <emph>Document Instance</emph>, and specifies an <att>xml:id</att> attribute
-in order to allow <loc href="#element-vocab-type-content">Content</loc> elements associated with the region by means of a
+<p>A <loc href="#layout-vocabulary-region"><el>region</el></loc> element that is defined out-of-line from
+the <loc href="#terms-content-element">content element(s)</loc> to be selected into (targetted to) the region. An out-of-line region appears
+as a child of a <loc href="#layout-vocabulary-layout"><el>layout</el></loc> element in the header
+(<loc href="#document-structure-vocabulary-head"><el>head</el></loc> element)
+of a <loc href="#terms-document-instance">document instance</loc>, and specifies an <att>xml:id</att> attribute
+in order to allow <loc href="#terms-content-element">content elements</loc> to be associated with the region by means of a
<att>region</att> attribute. There is a one-to-many relationship between an out-of-line region
-and the <loc href="#element-vocab-type-content">Content</loc> element(s) to be selected into (targetted to) the region.</p>
+and the <loc href="#terms-content-element">content element(s)</loc> to be selected into (targetted to) the region.</p>
</def>
</gitem>
-<gitem>
-<label>Presentation Processor</label>
+<gitem id="terms-presentation-processor">
+<label>[presentation processor]</label>
<def>
-<p>A <emph>Content Processor</emph> which purpose is to layout, format, and render,
-i.e., to present, <emph>Timed Text Markup Language</emph> content by applying the presentation semantics
+<p>A <loc href="#terms-content-processor">content processor</loc> which purpose is to layout, format, and render,
+i.e., to present, <loc href="#terms-timed-text-markup-language">Timed Text Markup Language</loc> content by applying the presentation semantics
defined in this specification.</p>
</def>
</gitem>
-<gitem>
-<label>Processor</label>
+<gitem id="terms-processor">
+<label>[processor]</label>
<def>
-<p>See <emph>Content Processor</emph>.</p>
+<p>See <loc href="#terms-content-processor">content processor</loc>.</p>
</def>
</gitem>
-<gitem>
-<label>Processor Profile</label>
+<gitem id="terms-processor-profile">
+<label>[processor profile]</label>
<def>
-<p>A collection of features and extensions that must or may be implemented (supported) by
+<p>A collection of <loc href="#terms-feature">features</loc> and <loc href="#terms-extension">extensions</loc> that must or may be implemented (supported) by
a content processor.</p>
<ednote>
-<name>Processor Profile</name>
+<name>[processor profile]</name>
<date>2013-08-23</date>
<edtext>Need to update and elaborate definition of processor profile based on new profiling mechanisms.</edtext>
</ednote>
<p></p>
</def>
</gitem>
-<gitem>
-<label>Profile Definition Document</label>
+<gitem id="terms-profile-definition-document">
+<label>[profile definition document]</label>
<def>
-<p>A document that defines a specific collection of features and extensions
+<p>A document that defines a specific collection of <loc href="#terms-feature">features</loc> and <loc href="#terms-extension">extensions</loc>
for which support is required or optional in a recipient content
processor.</p>
</def>
</gitem>
-<gitem>
-<label>Region</label>
+<gitem id="terms-region">
+<label>[region]</label>
<def>
<p>A logical construct that models authorial intention regarding
desired or potential presentation processing, and which is represented as
@@ -730,96 +741,96 @@
is composed and rendered during presentation processing.</p>
</def>
</gitem>
-<gitem>
-<label>Reduced XML Infoset</label>
+<gitem id="terms-reduced-xml-infoset">
+<label>[reduced xml infoset]</label>
<def>
<p>An XML Information Set <bibref ref="infoset"/> that satisfies the
constraints specify by <specref ref="reduced-infoset"/>.</p>
</def>
</gitem>
-<gitem>
-<label>Related Media Object</label>
+<gitem id="terms-related-media-object">
+<label>[related media object]</label>
<def>
<p>A (possibly null) media object associated with or otherwise related
-to a <emph>Document Instance</emph>. For example, an aggregate audio/video media
-object for which a <emph>Document Instance</emph> provides caption or subtitle
-information, and with which that <emph>Document Instance</emph> is associated.</p>
+to a <loc href="#terms-document-instance">document instance</loc>. For example, an aggregate audio/video media
+object for which a <loc href="#terms-document-instance">document instance</loc> provides caption or subtitle
+information, and with which that <loc href="#terms-document-instance">document instance</loc> is associated.</p>
</def>
</gitem>
-<gitem>
-<label>Related Media Object Region</label>
+<gitem id="terms-related-media-object-region">
+<label>[related media object region]</label>
<def>
-<p>When a non-null <emph>Related Media Object</emph> exists, the region of this media object,
-expressed in the coordinate system that applies to the <emph>Document Instance</emph> that is associated with the
+<p>When a non-null <loc href="#terms-related-media-object">related media object</loc> exists, the region of this media object,
+expressed in the coordinate system that applies to the <loc href="#terms-document-instance">document instance</loc> that is associated with the
related media object.</p>
</def>
</gitem>
-<gitem>
-<label>Root Container Region</label>
+<gitem id="terms-root-container-region">
+<label>[root container region]</label>
<def>
<p>A logical region that establishes a coordinate system into which
-<emph>Document Instance</emph> content regions are placed and optionally clipped.</p>
+<loc href="terms-content-region">content regions</loc> are placed and optionally clipped.</p>
</def>
</gitem>
-<gitem>
-<label>Root Temporal Extent</label>
+<gitem id="terms-root-temporal-extent">
+<label>[root temporal extent]</label>
<def>
<p>
-The temporal extent (interval) defined by the temporal beginning and ending of a <emph>Document Instance</emph> in relationship with some external application or presentation context.
+The temporal extent (interval) defined by the temporal beginning and ending of a <loc href="#terms-document-instance">document instance</loc> in relationship with some external application or presentation context.
</p>
</def>
</gitem>
-<gitem>
-<label>SMPTE Time Code</label>
+<gitem id="terms-smpte-time-code">
+<label>[smpte time code]</label>
<def>
<p>A time code whose format and semantics are established by <bibref ref="smpte12m"/>,
which may be embedded into or otherwise associated with media content, such
as a broadcast audio/video stream.</p>
</def>
</gitem>
-<gitem>
-<label>Synthetic Document Syncbase</label>
+<gitem id="terms-synthetic-document-syncbase">
+<label>[synthetic document syncbase]</label>
<def>
<p>A document level <xspecref href="http://www.w3.org/TR/2008/REC-SMIL3-20081201/smil30.html#smil-timing-q158">syncbase</xspecref>
<bibref ref="smil3"/>, § 5.7.1, synthesized or otherwise established by
-the <emph>Document Processing Context</emph> in accordance with the
-<emph>Related Media Object</emph> or other processing criteria.</p>
+the <loc href="#terms-document-processing-context">document processing context</loc> in accordance with the
+<loc href="#terms-related-media-object">related media object</loc> or other processing criteria.</p>
</def>
</gitem>
-<gitem>
-<label>Synthetic SMPTE Document Syncbase</label>
+<gitem id="terms-synthetic-smpte-document-syncbase">
+<label>[synthetic smpte document syncbase]</label>
<def>
-<p>A <emph>Synthetic Document Syncbase</emph> constructed from <emph>SMPTE Time
-Code</emph> values embedded in or associated with the <emph>Related Media Object</emph> or
-otherwise determined by the <emph>Document Processing Context</emph>.</p>
+<p>A <loc href="#terms-synthetic-document-syncbase">synthetic document syncbase</loc> constructed from <loc href="#terms-smpte-time-code">smpte time code</loc>
+values embedded in or associated with the <loc href="#terms-related-media-object">related media object</loc> or
+otherwise determined by the <loc href="#terms-document-processing-context">document processing context</loc>.</p>
</def>
</gitem>
-<gitem>
-<label>Timed Text</label>
+<gitem id="terms-timed-text">
+<label>[timed text]</label>
<def>
<p>Textual information that is intrinsically or extrinsically
associated with timing information.</p>
</def>
</gitem>
-<gitem>
-<label>Timed Text Markup Language</label>
+<gitem id="terms-timed-text-markup-language">
+<label>[timed text markup language]</label>
<def>
<p>A content type that represents timed text media for the purpose of
interchange among authoring systems.</p>
</def>
</gitem>
-<gitem>
-<label>Timed Text Authoring System</label>
+<gitem id="terms-timed-text-authoring-system">
+<label>[timed text authoring system]</label>
<def>
<p>A content authoring system capable of importing and exporting
Timed Text Markup Language content.</p>
</def>
</gitem>
-<gitem>
-<label>Transformation Processor</label>
+<gitem id="terms-transformation-processor">
+<label>[transformation processor]</label>
<def>
-<p>A <emph>Content Processor</emph> which purpose is to transform or otherwise rewrite
-<emph>Timed Text Markup Language</emph> content to either <emph>Timed Text Markup Language</emph>
+<p>A <loc href="#terms-content-processor">content processor</loc> which purpose is to transform or otherwise rewrite
+<loc href="#terms-timed-text-markup-language">Timed Text Markup Language</loc> content to either <loc href="#terms-timed-text-markup-language">Timed Text Markup Language</loc>
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
@@ -827,10 +838,10 @@
no further transformation semantics are defined by this specification.</p>
</def>
</gitem>
-<gitem>
-<label>Valid Abstract Document Instance</label>
+<gitem id="terms-valid-abstract-document-instance">
+<label>[valid abstract document instance]</label>
<def>
-<p>An <emph>Abstract Document Instance</emph> which has been assessed for validity
+<p>An <loc href="#terms-abstract-document-instance">abstract document instance</loc> which has been assessed for validity
and found to be valid as defined by <specref ref="doctypes"/>.</p>
</def>
</gitem>
@@ -904,7 +915,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
+<loc href="terms-attribute-information-item">attribute information item</loc> has a built-in simple type definition
defined in <bibref ref="xsd-2"/>, a hyperlink to its definition
therein is given.</p>
<p>The allowed content of the information item is shown as a grammar
@@ -949,12 +960,12 @@
TTML Content and processors.</p>
<div2 id="conformance-content">
<head>Content Conformance</head>
-<p>A TTML <emph>Document Instance</emph> conforms to this specification if the following criteria are
+<p>A TTML <loc href="#terms-document-instance">document instance</loc> conforms to this specification if the following criteria are
satisfied:</p>
<olist>
<item>
-<p>When transporting a <emph>Document Instance</emph> in a <emph>Document Interchange Context</emph> in which a
-Media Type <bibref ref="media-types"/> identifies the content type of the interchanged <emph>Document Instance</emph>, then the specified media type is
+<p>When transporting a <loc href="#terms-document-instance">document instance</loc> in a <loc href="#terms-document-interchange-context">document interchange context</loc> in which a
+Media Type <bibref ref="media-types"/> identifies the content type of the interchanged <loc href="#terms-document-instance">document instance</loc>, then the specified media type is
<code>application/ttml+xml</code> in conformance with <bibref
ref="xml-media"/> § 7, with which an optional
<code>profile</code> parameter may appear, the value of which
@@ -964,22 +975,22 @@
<specref ref="vocabulary-profiles"/>.</p>
</item>
<item>
-<p>The <emph>Document Instance</emph> is or can be represented as a Reduced XML
-Infoset as defined by <specref ref="reduced-infoset"/>.</p>
-</item>
-<item>
-<p>The Reduced XML
-Infoset that corresponds to the <emph>Document Instance</emph> is or can
-be associated with one of the <emph>Abstract Document Types</emph> defined by
+<p>The <loc href="#terms-document-instance">document instance</loc> is or can be represented as a <loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc>
+as defined by <specref ref="reduced-infoset"/>.</p>
+</item>
+<item>
+<p>The <loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc> that
+corresponds to the <loc href="#terms-document-instance">document instance</loc> is or can
+be associated with one of the <loc href="#terms-abstract-document-type">abstract document types</loc> defined by
<specref ref="doctypes"/>.</p>
</item>
<item>
-<p>The <emph>Reduced XML Infoset</emph> that corresponds to the <emph>Document Instance</emph> is a
-<emph>Valid Abstract Document Instance</emph> of the associated
-<emph>Abstract Document Type</emph>.</p>
-</item>
-<item>
-<p>The <emph>Reduced XML Infoset</emph> satisfies all additional mandatory syntactic and
+<p>The <loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc> that corresponds to the <loc href="#terms-document-instance">document instance</loc> is a
+<loc href="#terms-valid-abstract-document-instance">valid abstract document instance</loc> of the associated
+<loc href="#terms-abstract-document-type">abstract document type</loc>.</p>
+</item>
+<item>
+<p>The <loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc> 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
<bibref ref="wcag"/>.</p>
@@ -990,30 +1001,30 @@
<head>Processor Conformance</head>
<div3 id="conformance-generic-processor">
<head>Generic Processor Conformance</head>
-<p>A TTML <emph>Content Processor</emph> conforms to this specification if the following
+<p>A TTML <loc href="#terms-content-processor">content processor</loc> conforms to this specification if the following
generic processor criteria are
satisfied:</p>
<olist>
<item>
<p>The processor provides at least one mechanism for notionally
-instantiating a Reduced XML
-Infoset representation of a conformant <emph>Document Instance</emph>.</p>
+instantiating a <loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc>
+representation of a conformant <loc href="#terms-document-instance">document instance</loc>.</p>
</item>
<item>
<p>If a process does or can perform validation of a candidate
-<emph>Document Instance</emph>, then it provides at least one mechanism to
+<loc href="#terms-document-instance">document instance</loc>, then it provides at least one mechanism to
implicitly or explicitly associate the
-<emph>Reduced XML Infoset</emph> representation
-of a conformant <emph>Document Instance</emph> with one of the
+<loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc> representation
+of a conformant <loc href="#terms-document-instance">document instance</loc> with one of the
<emph>Abstract Document Types</emph> defined by
<specref ref="doctypes"/>.</p>
</item>
<item>
<p>The processor does not <emph>a priori</emph> reject or abort the
-processing of a conformant <emph>Document Instance</emph>
+processing of a conformant <loc href="#terms-document-instance">document instance</loc>
unless the processor does not support some required
(mandatory) feature specified or implied by a TTML profile
-declared to apply to the <emph>Document Instance</emph>.</p>
+declared to apply to the <loc href="#terms-document-instance">document instance</loc>.</p>
</item>
<item>
<p>The processor supports all mandatory processing semantics defined by this specification.</p>
@@ -1039,7 +1050,7 @@
</div3>
<div3 id="conformance-transformation-processor">
<head>Transformation Processor Conformance</head>
-<p>A TTML <emph>Content Processor</emph> is a conformant TTML <emph>Transformation Processor</emph> if
+<p>A TTML <loc href="#terms-content-processor">content processor</loc> is a conformant TTML <loc href="#terms-transformation-processor">transformation processor</loc> if
the following criteria are satisfied:</p>
<olist>
<item>
@@ -1054,7 +1065,7 @@
</div3>
<div3 id="conformance-presentation-processor">
<head>Presentation Processor Conformance</head>
-<p>A TTML <emph>Content Processor</emph> is a conformant TTML <emph>Presentation Processor</emph> if
+<p>A TTML <loc href="#terms-content-processor">content processor</loc> is a conformant TTML <loc href="#terms-presentation-processor">presentation processor</loc> if
the following criteria are satisfied:</p>
<olist>
<item>
@@ -1070,8 +1081,8 @@
</div2>
<div2 id="claims">
<head>Claims</head>
-<p>Any claim of compliance with respect to the conformance of a TTML <emph>Document Instance</emph> or
-<emph>Content Processor</emph> must make
+<p>Any claim of compliance with respect to the conformance of a TTML <loc href="#terms-document-instance">document instance</loc> or
+<loc href="#terms-content-processor">content processor</loc> 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
@@ -1080,7 +1091,7 @@
defined by <specref ref="vocabulary-profiles"/>, 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 <emph>Document Instance</emph> for which a compliance claim is made
+<p>A <loc href="#terms-document-instance">document instance</loc> for which a compliance claim is made
must specify
either (1)
a <att>ttp:profile</att> attribute on its root
@@ -1099,26 +1110,26 @@
<ulist>
<item><p><specref ref="ttml-content-doctype"/></p></item>
</ulist>
-<p>Each <emph>Abstract Document Type</emph> consists of the following constraints:</p>
+<p>Each <loc href="#terms-abstract-document-type">abstract document type</loc> consists of the following constraints:</p>
<ulist>
<item><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></item>
<item><p>a non-empty collection of element types that may appear as the document element</p></item>
</ulist>
-<p>An <emph>Abstract Document Instance</emph> may be assessed in terms of validity,
-and is considered to be a <emph>Valid Abstract Document Instance</emph> if it
+<p>An <loc href="#terms-abstract-document-instance">abstract document instance</loc> may be assessed in terms of validity,
+and is considered to be a <loc href="#terms-valid-abstract-document-instance">valid abstract document instance</loc> if it
satisfies the following condition: if after</p>
<olist>
<item>
<p>pruning all element information
items whose names are not members of the collection of element types defined
-by the associated <emph>Abstract Document Type</emph>, then</p>
+by the associated <loc href="#terms-abstract-document-type">abstract document type</loc>, then</p>
</item>
<item>
<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 <emph>Abstract Document Type</emph>, and then</p>
+is defined as empty in the associated <loc href="#terms-abstract-document-type">abstract document type</loc>, and then</p>
</item>
<item>
<p>pruning all attribute
@@ -1128,32 +1139,32 @@
</item>
</olist>
<p>then the document element is one of the document
-element types permitted by the associated <emph>Abstract Document Type</emph>,
+element types permitted by the associated <loc href="#terms-abstract-document-type">abstract document type</loc>,
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 <emph>Abstract Document Type</emph>.</p>
+associated <loc href="#terms-abstract-document-type">abstract document type</loc>.</p>
<note>
<p>While a conformant processor may not <emph>a priori</emph> reject a
-conformant <emph>Document Instance</emph>, a given <emph>Document Instance</emph> may be
+conformant <loc href="#terms-document-instance">document instance</loc>, a given <loc href="#terms-document-instance">document instance</loc> may be
constrained by the author or authoring tool to satisfy a more
restrictive definition of validity.</p>
</note>
<div2 id="ttml-content-doctype">
<head>TTML Content</head>
-<p>TTML Content is an <emph>Abstract Document Type</emph> of a profile of the Timed Text Markup Language intended
+<p>TTML Content is an <loc href="#terms-abstract-document-type">abstract document type</loc> 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 <specref ref="vocabulary"/>.</p>
<p>This specification references two types of schemas that may be used to validate a superset/subset
-of conformant TTML Content <emph>Document Instances</emph>:</p>
+of conformant TTML Content <loc href="#terms-document-instance">document instances</loc>:</p>
<ulist>
<item><p><specref ref="ttml-schema-rnc"/></p></item>
<item><p><specref ref="ttml-schema-xsd"/></p></item>
</ulist>
-<p>The (root) document element of a TTML Content <emph>Document Instance</emph> must be a
+<p>The (root) document element of a TTML Content <loc href="#terms-document-instance">document instance</loc> must be a
<el>tt</el> element, as defined by <specref
ref="document-structure-vocabulary-tt"/>.</p>
<note role="clarification">
@@ -1170,10 +1181,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 <emph>Document Instance</emph> to be based on an <emph>Abstract Document Instance</emph> from
+formal validity of a <loc href="#terms-document-instance">document instance</loc> to be based on an <loc href="#terms-abstract-document-instance">abstract document instance</loc> 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 <emph>Document Instance</emph> validity.</p>
+of <loc href="#terms-document-instance">document instance</loc> validity.</p>
</note>
</div2>
</div1>
@@ -1195,7 +1206,7 @@
and indicates the default prefix used within this specification and the
normative URI that denotes each namespace.</p>
<note role="explanation">
-<p>In a specific <emph>Document Instance</emph>, it is not required that the default
+<p>In a specific <loc href="#terms-document-instance">document instance</loc>, it is not required that the default
prefixes shown below are used. Any prefix or namespace binding that satisfies the constraints
of XML Namespaces <bibref ref="xmlns10"/> may be used that is associated with the specified namespace URI.</p>
</note>
@@ -1316,11 +1327,11 @@
</note>
<p>All profile designators which have the TT Profile Namespace as a prefix but are otherwise not listed in
<specref ref="profile-vocab-table"/> are reserved for future standardization, and must not be appear in a conformant
-<emph>Document Instance</emph>. Nothwithstanding this constraint, a profile designator is not restricted to the set of designators enumerated
-in <specref ref="profile-vocab-table"/>, but may be any URI that feasibly dereferences a TTML <emph>Profile Definition Document</emph>
+<loc href="#terms-document-instance">document instance</loc>. Nothwithstanding this constraint, a profile designator is not restricted to the set of designators enumerated
+in <specref ref="profile-vocab-table"/>, but may be any URI that feasibly dereferences a TTML <loc href="#terms-profile-definition-document">profile definition document</loc>
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 <emph>Content Processor</emph> in order to process a <emph>Document Instance</emph> is determined either (1) by specifying a
+TTML <loc href="#terms-content-processor">content processor</loc> in order to process a <loc href="#terms-document-instance">document instance</loc> is determined either (1) by specifying a
<att>ttp:profile</att> attribute on the root <el>tt</el> element, as
defined by <specref ref="parameter-attribute-profile"/>, or (2) by
including one or more <el>ttp:profile</el>
@@ -1331,11 +1342,11 @@
href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
attribute should not be specified on the <el>tt</el> element. If both
a <el>ttp:profile</el> element and a <att>ttp:profile</att>
-attribute are present (in a given <emph>Document Instance</emph>), then the
+attribute are present (in a given <loc href="#terms-document-instance">document instance</loc>), then the
<att>ttp:profile</att> attribute must be ignored for the purpose of
determining the declared profile requirements.</p>
<p>If more than one <el>ttp:profile</el> element appears in
-a <emph>Document Instance</emph>, then all specified profiles apply
+a <loc href="#terms-document-instance">document instance</loc>, 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),
@@ -1348,16 +1359,17 @@
<loc href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
attribute nor
<loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
-element is present in a <emph>Document Instance</emph>, and if the <emph>Document
-Interchange Context</emph> does not make an implicit or explicit
+element is present in a <loc href="#terms-document-instance">document instance</loc>, and if the <loc href="#terms-document-interchange-context">document
+interchange context</loc>
+does not make an implicit or explicit
reference to a pre-defined profile or does not specify a <emph>Profile Definition
Document</emph> or another equivalent set of feature designations,
then the DFXP Transformation profile applies.</p>
<note role="elaboration">
-<p>It is not a requirement on a conformant <emph>Document Instance</emph> that a profile be internally
+<p>It is not a requirement on a conformant <loc href="#terms-document-instance">document instance</loc> that a profile be internally
defined by use of a <el>ttp:profile</el> element or internally referenced by a
-<att>ttp:profile</att> attribute. More specifically, it is permitted that the <emph>Document
-Interchange Context</emph> determines the applicable profile through private
+<att>ttp:profile</att> attribute. More specifically, it is permitted that the <loc href="#terms-document-interchange-context">document
+interchange context</loc> 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>
</note>
@@ -1367,12 +1379,12 @@
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 <emph>Profile Definition Document</emph>.
-However, it is not required that a conformant TTML Content Processor be able
+a URI that denotes an externally defined <loc href="#terms-profile-definition-document">profile definition document</loc>.
+However, it is not required that a conformant TTML <loc href="#terms-content-processor">content processor</loc> be able
to dereference such an externally specified profile definition.</p>
<p>In contrast, it is intended that the <el>ttp:profile</el> element be
used when the author wishes to make use of a modified predefined profile or
-wishes to include in the <emph>Document Instance</emph> a non-standard profile definition
+wishes to include in the <loc href="#terms-document-instance">document instance</loc> 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
@@ -1386,13 +1398,13 @@
It is also possible to define a derived profile that is simultaneously subtractive
and additive.</p>
</note>
-<p>If a <emph>Document Instance</emph> makes use of a feature defined by
+<p>If a <loc href="#terms-document-instance">document instance</loc> makes use of a feature defined by
<specref ref="feature-designations"/> and if the intended use of the
document requires the recognition and processing of that feature, then
the document must include a <emph>required feature</emph> or
a <emph>used feature</emph>
specification in one of its declared or
-referenced profiles. If a <emph>Document Instance</emph> makes use
+referenced profiles. If a <loc href="#terms-document-instance">document instance</loc> makes use
of an extension designatable by <specref
ref="extension-designations"/> and if the intended use of the document
requires the recognition and processing of that extension, then the
@@ -1475,7 +1487,7 @@
<item><p><specref ref="animation"/></p></item>
<item><p><specref ref="metadata"/></p></item>
</ulist>
-<p>The core element vocabulary specified for use with a <emph>Document Instance</emph> is enumerated in
+<p>The core element vocabulary specified for use with a <loc href="#terms-document-instance">document instance</loc> is enumerated in
<specref ref="element-vocab-table"/>.</p>
<table id="element-vocab-table" role="common">
<caption>Table 3 – Element Vocabulary</caption>
@@ -1772,10 +1784,10 @@
profiles of TTML, and is not further defined
by this version of this specification.</p>
<p>In addition to standardized extension vocabulary, a conforming
-<emph>Document Instance</emph> may contain arbitrary namespace qualified
+<loc href="#terms-document-instance">document instance</loc> may contain arbitrary namespace qualified
elements that reside in any namespace other than those namespaces
defined for use with this specification. Furthermore, a conforming
-<emph>Document Instance</emph> may contain arbitrary namespace qualified
+<loc href="#terms-document-instance">document instance</loc> 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>
@@ -1789,13 +1801,13 @@
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 <emph>Document Processing Context</emph> by means
+core vocabulary items or for establishing a <loc href="#terms-document-processing-context">document processing context</loc> by means
of which TTML Content can be related to an external environment.</p>
<div2 id="parameter-element-vocabulary">
<head>Parameter Element Vocabulary</head>
<p>The following elements, all defined in the TT Parameter
-Namespace, specify parametric information that applies to a <emph>Document Instance</emph>
-or <emph>Content Processor</emph>:</p>
+Namespace, specify parametric information that applies to a <loc href="#terms-document-instance">document instance</loc>
+or <loc href="#terms-content-processor">content processor</loc>:</p>
<ulist>
<item><p><specref ref="parameter-vocabulary-profile"/></p></item>
<item><p><specref ref="parameter-vocabulary-features"/></p></item>
@@ -1808,12 +1820,12 @@
<p>The <el>ttp:profile</el> 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 <emph>Content Processor</emph> in order to process a
-<emph>Document Instance</emph> that makes (or may make) use of such features and
+may be supported by a <loc href="#terms-content-processor">content processor</loc> in order to process a
+<loc href="#terms-document-instance">document instance</loc> 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 <emph>Document Instance</emph>, and, if it does appear, may result in
-the <emph>Document Instance</emph> being rejected or processing otherwise aborted.</p>
+a <loc href="#terms-document-instance">document instance</loc>, and, if it does appear, may result in
+the <loc href="#terms-document-instance">document instance</loc> being rejected or processing otherwise aborted.</p>
<note role="clarification">
<p>The difference between a <emph>feature</emph> and an
<emph>extension</emph> is where it is defined and how it is labeled:
@@ -1828,22 +1840,22 @@
<p>This specification defines two distinct uses of the <el>ttp:profile</el> element:</p>
<ulist>
<item>
-<p>as a child of the <el>head</el> element within a TTML <emph>Document Instance</emph>;</p>
-</item>
-<item>
-<p>as the root element of a TTML <emph>Profile Definition Document</emph>
+<p>as a child of the <el>head</el> element within a TTML <loc href="#terms-document-instance">document instance</loc>;</p>
+</item>
+<item>
+<p>as the root element of a TTML <loc href="#terms-profile-definition-document">profile definition document</loc>
instance;</p>
</item>
</ulist>
-<p>When a <el>tt:profile</el> element appears within a TTML <emph>Document Instance</emph>,
+<p>When a <el>tt:profile</el> element appears within a TTML <loc href="#terms-document-instance">document instance</loc>,
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 <emph>Document Instance</emph>.
+not be included or otherwise used in a <loc href="#terms-document-instance">document instance</loc>.
In addition, the element indirectly expresses
information about the set of features or extensions that are (or may
-expected to be) used by the <emph>Document Instance</emph>.</p>
-<p>When a <el>tt:profile</el> element is used by a TTML <emph>Profile Definition Document</emph> instance,
+expected to be) used by the <loc href="#terms-document-instance">document instance</loc>.</p>
+<p>When a <el>tt:profile</el> element is used by a TTML <loc href="#terms-profile-definition-document">profile definition document</loc> instance,
it serves to publish a machine
readable specification of a specific TTML profile, of which
this specification defines three such <emph>Profile Definition Documents</emph> in
@@ -1875,7 +1887,7 @@
§3.2.17, and, furthermore, must denote a profile designator in
accordance with <specref ref="vocabulary-profiles"/>. In this case,
the profile designator must refer to (1) a standard, predefined
-<emph>Profile Definition Document</emph> as defined by <specref ref="profiles"/>,
+<loc href="#terms-profile-definition-document">profile definition document</loc> as defined by <specref ref="profiles"/>,
or (2) a feasibly dereferenceable resource representing a valid <emph>Profile Definition
Document</emph> instance. In either case, the referenced profile serves as the
baseline profile of the specifying <el>ttp:profile</el> element.</p>
@@ -1921,18 +1933,18 @@
</item>
</olist>
<p>A conformant TTML processor is not required to be able to
-dereference a <emph>Profile Definition Document</emph> that is not one of the
+dereference a <loc href="#terms-profile-definition-document">profile definition document</loc> that is not one of the
standard, predefined profiles defined by <specref ref="profiles"/>. 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
-<emph>Profile Definition Document</emph>, then it must not further process the
+<loc href="#terms-profile-definition-document">profile definition document</loc>, 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 <emph>Document Instance</emph> due to the inability to
-reference a non-standard <emph>Profile Definition Document</emph>, then some
+processing of a <loc href="#terms-document-instance">document instance</loc> due to the inability to
+reference a non-standard <loc href="#terms-profile-definition-document">profile definition document</loc>, 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>
@@ -2002,7 +2014,7 @@
<p>The <el>ttp:feature</el> element is used to specify
infomation about support and usage requirements for a particular feature.</p>
<p>The children of the <el>ttp:feature</el> element must express a non-empty
-sequence of character information items that adheres to the
+sequence of <loc href="terms-character-information-item">character information items</loc> that adheres to the
<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
§3.2.17.</p>
<table id="elt-syntax-parameter-feature" role="syntax">
@@ -2040,7 +2052,7 @@
specified on the nearest ancestor <el>ttp:features</el> element.</p>
<p>The <att>value</att> 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 <emph>Document Instance</emph>
+process the document, or (2) whether a TTML <loc href="#terms-document-instance">document instance</loc>
must not include or otherwise use the designated feature.
If the value of the <att>value</att> attribute
is <code>optional</code>, then the processor need
@@ -2073,12 +2085,12 @@
<code>use</code> and the TTML processor implementation supports but has disabled
that feature,
or if the <att>value</att> attribute is <code>prohibited</code> and a
-<emph>Document Instance</emph> includes or makes use of the feature,
+<loc href="#terms-document-instance">document instance</loc> 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 <emph>Document Instance</emph> due to the specification of a
+processing of a <loc href="#terms-document-instance">document instance</loc> 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
@@ -2101,7 +2113,7 @@
with the <att>value</att> attribute equal to <code>optional</code>.</p>
<note role="elaboration">
<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 <emph>Document Instance</emph>)
+it is not to be interpreted as meaning the use of that feature (in a <loc href="#terms-document-instance">document instance</loc>)
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>
</note>
@@ -2180,7 +2192,7 @@
<p>The <el>ttp:extension</el> element is used to specify
infomation about support and usage requirements for a particular extension.</p>
<p>The children of the <el>ttp:extension</el> element must express a non-empty
-sequence of character information items that adheres to the
+sequence of <loc href="terms-character-information-item">character information items</loc> that adheres to the
<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
§3.2.17.</p>
<table id="elt-syntax-parameter-extension" role="syntax">
@@ -2215,7 +2227,7 @@
ancestor <el>ttp:extensions</el> element.</p>
<p>The <att>value</att> 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 <emph>Document Instance</emph>
+process the document, or (2) whether a TTML <loc href="#terms-document-instance">document instance</loc>
must not include or otherwise use the designated extension.
If the value of the <att>value</att> attribute
is <code>optional</code>, then the processor need
@@ -2246,7 +2258,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 <emph>Document Instance</emph> due to the specification of a
+processing of a <loc href="#terms-document-instance">document instance</loc> 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
@@ -2268,7 +2280,7 @@
with the <att>value</att> attribute equal to <code>optional</code>.</p>
<note role="elaboration">
<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 <emph>Document Instance</emph>)
+it is not to be interpreted as meaning the use of that extension (in a <loc href="#terms-document-instance">document instance</loc>)
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>
</note>
@@ -2322,7 +2334,7 @@
<div3 id="parameter-attribute-cellResolution">
<head>ttp:cellResolution</head>
<p>The <att>ttp:cellResolution</att> attribute may be used by an author
-to express the number of horizontal and vertical cells into which the <emph>Root Container Region</emph>
+to express the number of horizontal and vertical cells into which the <loc href="#terms-root-container-region">root container region</loc>
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>
@@ -2365,7 +2377,7 @@
the cell's dimension in the inline or block progression dimension applies, respectively.</p>
<note role="example">
<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 <emph>Root Container Region</emph> is 640 by 480, then, assuming top to bottom,
+is 20 by 10, and the extent of the <loc href="#terms-root-container-region">root container region</loc> 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>
</note>
@@ -2506,7 +2518,7 @@
<div3 id="parameter-attribute-frameRate">
<head>ttp:frameRate</head>
<p>The <att>ttp:frameRate</att> attribute is used to specify the frame rate of a related
-media object or the intrinsic frame rate of a <emph>Document Instance</emph> in case it is intended
+media object or the intrinsic frame rate of a <loc href="#terms-document-instance">document instance</loc> 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>
<table id="parameter-attribute-frameRate-syntax" role="syntax">
@@ -2522,7 +2534,7 @@
</tr>
</tbody>
</table>
-<p>The frame rate that applies to a <emph>Document Instance</emph> is used to
+<p>The frame rate that applies to a <loc href="#terms-document-instance">document instance</loc> is used to
interpret time expressions that are expressed in <emph>frames</emph>
as defined by <specref ref="timing-value-timeExpression"/>.</p>
<p>If the <code>media</code> time base applies and the effective frame rate is
@@ -2636,20 +2648,20 @@
expressions may be converted to real time
coordinates by taking into account the computed frame rate
and drop mode as expressed by the <att>ttp:dropMode</att> parameter.
-In this case, the <emph>Content Processor</emph> must create and maintain a
-<emph>Synthetic SMPTE Document Syncbase</emph> within which these time
+In this case, the <loc href="#terms-content-processor">content processor</loc> must create and maintain a
+<loc href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</loc> within which these time
expressions are interpreted as further described in
<specref ref="timing-time-intervals"/>.</p>
<note role="explanation">
<p>When operating with <code>smpte</code> time base and
<code>continuous</code> marker mode, there is an implied time coordinate
-space, the <emph>Synthetic SMPTE Document Syncbase</emph>,
+space, the <loc href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</loc>,
defined by the monotonically increasing (or decreasing)
<bibref ref="smpte12m"/> 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
-<emph>SMPTE Time Code</emph> synchronization events (markers),
-where the <emph>Document Processing Context</emph> emits these events with implied constraints
+<loc href="#terms-smpte-time-code">smpte time code</loc> synchronization events (markers),
+where the <loc href="#terms-document-processing-context">document processing context</loc> 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>
@@ -2669,7 +2681,7 @@
<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 <emph>Document Processing Context</emph>
+synchronization events (markers), where the <loc href="#terms-document-processing-context">document processing context</loc>
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>
@@ -2730,7 +2742,7 @@
<head>ttp:profile</head>
<p>The <att>ttp:profile</att> attribute may be used by a content author
to express the profile of the Timed Text Markup Language (TTML) used
-in a <emph>Document Instance</emph>.</p>
+in a <loc href="#terms-document-instance">document instance</loc>.</p>
<p>If specified, the value of this attribute must adhere to the
<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
§3.2.17, and, further, must specify a
@@ -2743,7 +2755,7 @@
<div3 id="parameter-attribute-subFrameRate">
<head>ttp:subFrameRate</head>
<p>The <att>ttp:subFrameRate</att> attribute is used to specify the sub-frame rate of a related
-media object or the intrinsic sub-frame rate of a <emph>Document Instance</emph> in case it is intended
+media object or the intrinsic sub-frame rate of a <loc href="#terms-document-instance">document instance</loc> 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>
<table id="parameter-attribute-subFrameRate-syntax" role="syntax">
@@ -2759,7 +2771,7 @@
</tr>
</tbody>
</table>
-<p>The sub-frame rate that applies to a <emph>Document Instance</emph> is used to
+<p>The sub-frame rate that applies to a <loc href="#terms-document-instance">document instance</loc> is used to
interpret time expressions that are expressed in <emph>sub-frames</emph>
as defined by <specref ref="timing-value-timeExpression"/>.</p>
<p>If the <code>media</code> time base applies and the effective frame rate is
@@ -2784,7 +2796,7 @@
<div3 id="parameter-attribute-tickRate">
<head>ttp:tickRate</head>
<p>The <att>ttp:tickRate</att> attribute is used to specify the tick rate of a related
-media object or the intrinsic tick rate of content of a <emph>Document Instance</emph> in case it is intended
+media object or the intrinsic tick rate of content of a <loc href="#terms-document-instance">document instance</loc> 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>
<table id="parameter-attribute-tickRate-syntax" role="syntax">
@@ -2800,7 +2812,7 @@
</tr>
</tbody>
</table>
-<p>The tick rate that applies to a <emph>Document Instance</emph> is used to
+<p>The tick rate that applies to a <loc href="#terms-document-instance">document instance</loc> is used to
interpret time expressions that are expressed in <emph>ticks</emph> by
using the <code>t</code> metric as defined by <specref
ref="timing-value-timeExpression"/>.</p>
@@ -2833,7 +2845,7 @@
<head>ttp:timeBase</head>
<p>The <att>ttp:timeBase</att> attribute is used to specify the
temporal coordinate system by means of which time expressions are
-interpreted in a <emph>Document Instance</emph>.</p>
+interpreted in a <loc href="#terms-document-instance">document instance</loc>.</p>
<p>If specified, the value of this attribute must adhere to the following syntax:</p>
<table id="parameter-attribute-timeBase-syntax" role="syntax">
<caption>Syntax Representation – ttp:timeBase</caption>
@@ -2853,8 +2865,8 @@
<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 <emph>Document Instance</emph> is to be synchronized, or it may
-be the content of a <emph>Document Instance</emph> itself in a case where
+content of a <loc href="#terms-document-instance">document instance</loc> is to be synchronized, or it may
+be the content of a <loc href="#terms-document-instance">document instance</loc> itself in a case where
the timed text content is intended to establish an independent time
line.</p>
<note role="explanation">
@@ -2868,7 +2880,7 @@
</note>
<p>If the time base is designated as <code>smpte</code>,
then a time expression denotes a <bibref ref="smpte12m"/> time
-coordinate with which the content of a <emph>Document Instance</emph> is to
+coordinate with which the content of a <loc href="#terms-document-instance">document instance</loc> is to
be synchronized. In this case, the value of the <att>ttp:markerMode</att>
and <att>ttp:dropMode</att> parameters apply, as defined by <specref
ref="parameter-attribute-markerMode"/> and <specref
@@ -2890,7 +2902,7 @@
<p>A <att>ttp:timeBase</att> attribute is considered to be significant only
when specified on the <el>tt</el> element.</p>
<p>When operating with either <code>media</code> or <code>smpte</code>
-time bases, a diachronic presentation of a <emph>Document Instance</emph> may
+time bases, a diachronic presentation of a <loc href="#terms-document-instance">document instance</loc> 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>
@@ -2899,8 +2911,8 @@
based on the passage of real time.</p>
<note role="example">
<p>Due to there being only one time base parameter that applies to a
-given <emph>Document Instance</emph>, the interpretation of time expressions
-is uniform throughout the <emph>Document Instance</emph>.</p>
+given <loc href="#terms-document-instance">document instance</loc>, the interpretation of time expressions
+is uniform throughout the <loc href="#terms-document-instance">document instance</loc>.</p>
</note>
<note role="elaboration">
<p>See <specref ref="time-expression-semantics"/> for further details
@@ -2916,7 +2928,7 @@
<div2 id="content-element-vocabulary">
<head>Content Element Vocabulary</head>
<p>The following elements specify the structure and principal content aspects of a
-<emph>Document Instance</emph>:</p>
+<loc href="#terms-document-instance">document instance</loc>:</p>
<ulist>
<item><p><specref ref="document-structure-vocabulary-tt"/></p></item>
<item><p><specref ref="document-structure-vocabulary-head"/></p></item>
@@ -2928,7 +2940,7 @@
</ulist>
<div3 id="document-structure-vocabulary-tt">
<head>tt</head>
-<p>The <el>tt</el> element serves as the root document element of a <emph>Document Instance</emph>.</p>
+<p>The <el>tt</el> element serves as the root document element of a <loc href="#terms-document-instance">document instance</loc>.</p>
<p>The <el>tt</el> element accepts as its children zero or one <el>head</el> element followed by
zero or one <el>body</el> element.</p>
<table id="elt-syntax-tt" role="syntax">
@@ -2951,27 +2963,27 @@
</tr>
</tbody>
</table>
-<p>The <emph>Root Temporal Extent</emph>, i.e., the time interval over which a <emph>Document Instance</emph> is active, has an implicit duration that is equal to the
+<p>The <loc href="#terms-root-temporal-extent">root temporal extent</loc>, i.e., the time interval over which a <loc href="#terms-document-instance">document instance</loc> is active, has an implicit duration that is equal to the
implicit duration of the <el>body</el> element of the document, if the <el>body</el> element is present, or zero, if the <el>body</el> element is absent.</p>
<p>If the <att>tts:extent</att> attribute is specified on the <el>tt</el>
element, then it must adhere to <specref ref="style-attribute-extent"/>, in which case it
-specifies the spatial extent of the <emph>Root Container Region</emph> in
-which content regions are located and presented. If no <att>tts:extent</att>
-attribute is specified, then the spatial extent of the <emph>Root Container Region</emph> is
-considered to be determined by the <emph>Document Processing Context</emph>.
-The origin of the <emph>Root Container Region</emph> is determined by the <emph>Document Processing Context</emph>.</p>
+specifies the spatial extent of the <loc href="#terms-root-container-region">root container region</loc> in
+which <loc href="terms-content-region">content regions</loc> are located and presented. If no <att>tts:extent</att>
+attribute is specified, then the spatial extent of the <loc href="#terms-root-container-region">root container region</loc> is
+considered to be determined by the <loc href="#terms-document-processing-context">document processing context</loc>.
+The origin of the <loc href="#terms-root-container-region">root container region</loc> is determined by the <loc href="#terms-document-processing-context">document processing context</loc>.</p>
<note role="clarification">
-<p>In the absence of other requirements, and if a <emph>Related Media Object</emph> exists, then it is recommended
-that the <emph>Document Processing Context</emph> determine that:</p>
+<p>In the absence of other requirements, and if a <loc href="#terms-related-media-object">related media object</loc> exists, then it is recommended
+that the <loc href="#terms-document-processing-context">document processing context</loc> determine that:</p>
<ulist>
-<item><p>if no <att>tts:extent</att> is specified on the root <el>tt</el> element, the extent of the <emph>Root Container Region</emph> be
-established as equal to the extent of the <emph>Related Media Object Region</emph>; and</p></item>
-<item><p>the origin of the <emph>Root Container Region</emph> be established so that this region is centered in the
-<emph>Related Media Object Region</emph>.</p></item>
+<item><p>if no <att>tts:extent</att> is specified on the root <el>tt</el> element, the extent of the <loc href="#terms-root-container-region">root container region</loc> be
+established as equal to the extent of the <loc href="#terms-related-media-object-region">related media object region</loc>; and</p></item>
+<item><p>the origin of the <loc href="#terms-root-container-region">root container region</loc> be established so that this region is centered in the
+<loc href="#terms-related-media-object-region">related media object region</loc>.</p></item>
</ulist>
</note>
<note role="elaboration">
-<p>If an author desires to signal the (storage or image) aspect ratio of the <emph>Root Container Region</emph>
+<p>If an author desires to signal the (storage or image) aspect ratio of the <loc href="#terms-root-container-region">root container region</loc>
without specifying its resolution, then this may be accomplished by using metadata specified
in an external namespace, such as <att>m708:aspectRatio</att> as defined in <bibref ref="smpte2052"/>, §5.4.4.
This would permit, for example, the interchange of information that reflects the
@@ -2979,7 +2991,7 @@
</note>
<p>An <att>xml:lang</att> attribute must be specified on the <el>tt</el> element.
If the attribute value is empty, it signifies that there is no default language that applies
-to the text contained within the <emph>Document Instance</emph>.</p>
+to the text contained within the <loc href="#terms-document-instance">document instance</loc>.</p>
<p>If no <att>xml:space</att> attribute is specified upon the <el>tt</el> element, then it must
be considered as if the attribute had been specified with a value of <code>default</code>.</p>
</div3>
@@ -2996,18 +3008,18 @@
followed by zero or one <el>layout</el> element,
followed by zero or one <el>animation</el> element.</p>
<p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the <emph>Document Instance</emph> as a
+element group applies semantically to the <loc href="#terms-document-instance">document instance</loc> as a
whole, and not just the <el>head</el> element.</p>
<p>Any parameters specified by children in the <code>Parameters.class</code>
-element group applies semantically to the <emph>Document Instance</emph> as a
+element group applies semantically to the <loc href="#terms-document-instance">document instance</loc> as a
whole, and not just the <el>head</el> element.</p>
<p>A <el>styling</el> child element is used to specify style constructs
that are referenced from other style constructs, by layout constructs, and by
-<loc href="#element-vocab-type-content">Content</loc> elements.</p>
+<loc href="#terms-content-element">content elements</loc>.</p>
<p>A <el>layout</el> child element is used to specify layout constructs that
-are referenced by <loc href="#element-vocab-type-content">Content</loc> elements.</p>
+are referenced by <loc href="#terms-content-element">content elements</loc>.</p>
<p>An <el>animation</el> child element is used to specify animation constructs that
-target animatable <loc href="#element-vocab-type-content">Content</loc>
+target animatable <loc href="#terms-content-element">content element</loc>
or <loc href="#element-vocab-type-layout">Layout</loc> elements.</p>
<table id="elt-syntax-head" role="syntax">
<caption>XML Representation – Element Information Item: head</caption>
@@ -3029,7 +3041,7 @@
</table>
<p>To the extent that time semantics apply to the content of the
<el>head</el> element, the implied time interval of this element is
-defined to be coterminous with the <emph>Root Temporal Extent</emph>.</p>
+defined to be coterminous with the <loc href="#terms-root-temporal-extent">root temporal extent</loc>.</p>
</div3>
<div3 id="document-structure-vocabulary-body">
<head>body</head>
@@ -3078,26 +3090,26 @@
<p>An author may specify a temporal interval for a <el>body</el> element using
the <att>begin</att>, <att>dur</att>, and <att>end</att> attributes. If the begin point
of this interval remains unspecified, then the begin point is interpreted as the beginning
-point of the <emph>Root Temporal Extent</emph>. Similarly, if the end point of this interval remains unspecified, then the
-end point is interpreted as the ending point of the <emph>Root Temporal Extent</emph>.</p>
+point of the <loc href="#terms-root-temporal-extent">root temporal extent</loc>. Similarly, if the end point of this interval remains unspecified, then the
+end point is interpreted as the ending point of the <loc href="#terms-root-temporal-extent">root temporal extent</loc>.</p>
<note role="explanation">
-<p>A <emph>Document Instance</emph> referenced from a SMIL presentation
+<p>A <loc href="#terms-document-instance">document instance</loc> referenced from a SMIL presentation
is expected to follow the same timing rules as apply to other SMIL media
objects.</p>
</note>
<p>If relative begin or end times are specified on the <el>body</el>
element, then these times are resolved by reference to the beginning and
-ending time of the <emph>Root Temporal Extent</emph>.</p>
-<p>If the <emph>Root Temporal Extent</emph> is shorter than the computed duration of the
+ending time of the <loc href="#terms-root-temporal-extent">root temporal extent</loc>.</p>
+<p>If the <loc href="#terms-root-temporal-extent">root temporal extent</loc> is shorter than the computed duration of the
<el>body</el> element, then the active time interval of a <el>body</el> element is
-truncated to the active end point of the <emph>Root Temporal Extent</emph>.</p>
+truncated to the active end point of the <loc href="#terms-root-temporal-extent">root temporal extent</loc>.</p>
<p>An author may associate a set of style properties with a
<el>body</el> element by means of either the <att>style</att>
attribute or inline style attributes or a combination thereof.</p>
<note role="explanation">
<p>Style properties that are associated with a <el>body</el> element
-in a <emph>Document Instance</emph> are available for style inheritance by
-descendant <loc href="#element-vocab-type-content">Content</loc> elements such as <el>div</el>, <el>p</el>,
+in a <loc href="#terms-document-instance">document instance</loc> are available for style inheritance by
+descendant <loc href="#terms-content-element">content elements</loc> such as <el>div</el>, <el>p</el>,
<el>span</el>
and <el>br</el>.</p>
</note>
@@ -3174,8 +3186,8 @@
<note role="explanation">
<p>Style properties that are associated
with
-a <el>div</el> element in a <emph>Document Instance</emph>
-are available for style inheritance by descendant <loc href="#element-vocab-type-content">Content</loc> elements such as
+a <el>div</el> element in a <loc href="#terms-document-instance">document instance</loc>
+are available for style inheritance by descendant <loc href="#terms-content-element">content elements</loc> such as
<el>div</el>,
<el>p</el>,
<el>span</el>, and
@@ -3239,15 +3251,15 @@
attribute or inline style attributes or a combination thereof.</p>
<note role="explanation">
<p>Style properties that are associated with a <el>p</el> element
-in a <emph>Document Instance</emph> are available for style inheritance by
-descendant <loc href="#element-vocab-type-content">Content</loc> elements such as <el>span</el> and
+in a <loc href="#terms-document-instance">document instance</loc> are available for style inheritance by
+descendant <loc href="#terms-content-element">content elements</loc> such as <el>span</el> and
<el>br</el>.</p>
</note>
<p>If no <att>timeContainer</att> attribute is specified on
a <el>p</el> element, then it must be interpreted as having
<emph>parallel</emph> time containment semantics.</p>
<p>If a sequence of children of a <el>p</el> element
-consists solely of character information items, then that sequence must
+consists solely of <loc href="terms-character-information-item">character information items</loc>, then that sequence must
be considered to be an <emph>anonymous span</emph> for the purpose of
applying style properties that apply to <el>span</el> elements.</p>
<note role="elaboration"><p>The presentation semantics of TTML effectively
@@ -3311,8 +3323,8 @@
attribute or inline style attributes or a combination thereof.</p>
<note role="explanation">
<p>Style properties that are associated with a <el>span</el> element
-in a <emph>Document Instance</emph> are available for style inheritance by
-descendant <loc href="#element-vocab-type-content">Content</loc> elements such as <el>span</el> and
+in a <loc href="#terms-document-instance">document instance</loc> are available for style inheritance by
+descendant <loc href="#terms-content-element">content elements</loc> such as <el>span</el> and
<el>br</el>.</p>
</note>
<p>If no <att>timeContainer</att> attribute is specified on
@@ -3398,7 +3410,7 @@
<p>The <att>xml:space</att> 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 <emph>Document Instance</emph> as
+when performing presentation processing of a <loc href="#terms-document-instance">document instance</loc> as
described by <specref ref="semantics-region-layout-step-2"/>,
processing must occur as
if the following properties were specified on the affected
@@ -3460,8 +3472,8 @@
<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 <emph>Document Instances</emph> in any particular way;
-but an implementation of this model by a TTML Presentation Processor
+model. TTML Processors are not required to present <loc href="#terms-document-instance">document instances</loc> in any particular way;
+but an implementation of this model by a TTML <loc href="#terms-presentation-processor">presentation processor</loc>
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>
@@ -3477,7 +3489,7 @@
<div2 id="styling-element-vocabulary">
<head>Styling Element Vocabulary</head>
<p>The following elements specify the structure and principal styling aspects of a
-<emph>Document Instance</emph>:</p>
+<loc href="#terms-document-instance">document instance</loc>:</p>
<ulist>
<item><p><specref ref="styling-vocabulary-styling"/></p></item>
<item><p><specref ref="styling-vocabulary-style"/></p></item>
@@ -3509,7 +3521,7 @@
</table>
<p>To the extent that time semantics apply to the content of the
<el>styling</el> element, the implied time interval of this element is
-defined to be coterminous with the <emph>Root Temporal Extent</emph>.</p>
+defined to be coterminous with the <loc href="#terms-root-temporal-extent">root temporal extent</loc>.</p>
</div3>
<div3 id="styling-vocabulary-style">
<head>style</head>
@@ -3554,9 +3566,9 @@
<div2 id="styling-attribute-vocabulary">
<head>Styling Attribute Vocabulary</head>
<p>This section defines the <specref ref="style-attribute-style"/> attribute used
-with both style definition elements as well as <loc href="#element-vocab-type-content">Content</loc> elements.</p>
+with both style definition elements as well as <loc href="#terms-content-element">content elements</loc>.</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 <loc href="#element-vocab-type-content">Content</loc> elements
+for use with style definition elements, certain layout elements, and <loc href="#terms-content-element">content elements</loc>
that support inline style specifications:</p>
<ulist>
<item><p><specref ref="style-attribute-backgroundColor"/></p></item>
@@ -3605,7 +3617,7 @@
</note>
<note role="clarification">
<p>A style property may be expressed as a specified attribute on any
-<loc href="#element-vocab-type-content">Content</loc> element type
+<loc href="#terms-content-element">content element</loc> 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
@@ -3800,7 +3812,7 @@
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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the closest supported value.</p>
<note role="elaboration">
<p>In this context, the phrase <emph>closest supported value</emph> means the value for which the Euclidean distance between
the computed border width and the supported border width is minimized.</p>
@@ -3809,7 +3821,7 @@
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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>solid</code>.</p>
<p>If no border color is specified in the value of the <att>tts:border</att> 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>
@@ -3908,9 +3920,9 @@
span.</p>
<p>The initial value of the <att>tts:color</att> 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 <loc href="#terms-presentation-processor">presentation processor</loc>
should use an initial value that is highly contrastive to the
-background color of the <emph>Root Container Region</emph>.</p>
+background color of the <loc href="#terms-root-container-region">root container region</loc>.</p>
<p>The <att>tts:color</att> style is illustrated by the following example.</p>
<table id="style-attribute-color-example-1" role="example">
<caption>Example Fragment – Color</caption>
@@ -4000,7 +4012,7 @@
each character child of a <el>p</el> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>ltr</code>.</p>
<p>The <att>tts:direction</att> style is illustrated by the following example.</p>
<table id="style-attribute-direction-example-1" role="example">
<caption>Example Fragment – Direction</caption>
@@ -4223,7 +4235,7 @@
</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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>before</code>.</p>
<p>The <att>tts:displayAlign</att> style is illustrated by the following example.</p>
<table id="style-attribute-displayAlign-example-1" role="example">
<caption>Example Fragment – Display Align</caption>
@@ -4286,7 +4298,7 @@
<head>tts:extent</head>
<p>The <att>tts:extent</att> attribute is used to specify the
<emph>width</emph> and <emph>height</emph> of a region area
-(which may be the <emph>Root Container Region</emph>).</p>
+(which may be the <loc href="#terms-root-container-region">root container region</loc>).</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
@@ -4319,7 +4331,7 @@
</tr>
<tr>
<td><emph>Percentages:</emph></td>
-<td>relative to width and height of <emph>Root Container Region</emph></td>
+<td>relative to width and height of <loc href="#terms-root-container-region">root container region</loc></td>
</tr>
<tr>
<td><emph>Animatable:</emph></td>
@@ -4333,15 +4345,15 @@
<emph>width</emph>, and the second specification is the <emph>height</emph>.</p>
<p>The <loc href="#style-value-length"><length></loc> 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 <emph>Root Container Region</emph>.</p>
-<p>The extent of the <emph>Root Container Region</emph> is determined either by a
+of the style property must be considered to be the same as the extent of the <loc href="#terms-root-container-region">root container region</loc>.</p>
+<p>The extent of the <loc href="#terms-root-container-region">root container region</loc> is determined either by a
<att>tts:extent</att> specified on the <el>tt</el> element, if
present, or as described by <specref ref="document-structure-vocabulary-tt"/> if not present.
If <att>tts:extent</att> is specified on the <el>tt</el> element, then
the width and height must be expressed in terms of two <loc href="#style-value-length"><length></loc> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the closest supported value.</p>
<note role="elaboration">
<p>In this context, the phrase <emph>closest supported value</emph> means the value for which the Euclidean distance between
the computed extent and the supported extent is minimized.</p>
@@ -4435,7 +4447,7 @@
each character child of a <el>p</el> 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
+<loc href="#terms-presentation-processor">presentation processor</loc> 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>
@@ -4525,7 +4537,7 @@
<td><emph>Percentages:</emph></td>
<td>if not <loc href="#content-vocabulary-span"><el>region</el></loc> element,
then relative to parent element's font size; otherwise, relative to the
-<emph>Computed Cell Size</emph></td>
+<loc href="#terms-computed-cell-size">computed cell size</loc></td>
</tr>
<tr>
<td><emph>Animatable:</emph></td>
@@ -4553,7 +4565,7 @@
each character child of a <el>p</el> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the closest supported value.</p>
<note role="elaboration">
<p>In this context, the phrase <emph>closest supported value</emph> means the value for which the Euclidean distance between
the computed font size and the supported font size is minimized.</p>
@@ -4562,10 +4574,10 @@
<p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
the <emph>cell</emph> length unit as defined by <specref ref="style-value-length"/>.
When a single <length> is expressed using cell units, then it refers to the height of
-the <emph>Computed Cell Size</emph>.
+the <loc href="#terms-computed-cell-size">computed cell size</loc>.
When two <length> values are expressed using cell units, then the first refers to the width of
-the <emph>Computed Cell Size</emph>, and the second refers to the height of the
-<emph>Computed Cell Size</emph>.</p>
+the <loc href="#terms-computed-cell-size">computed cell size</loc>, and the second refers to the height of the
+<loc href="#terms-computed-cell-size">computed cell size</loc>.</p>
</note>
<p>The <att>tts:fontSize</att> style is illustrated by the following example.</p>
<table id="style-attribute-fontSize-example-1" role="example">
@@ -4665,7 +4677,7 @@
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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>normal</code>.</p>
<p>The <att>tts:fontStyle</att> style is illustrated by the following example.</p>
<table id="style-attribute-fontStyle-example-1" role="example">
<caption>Example Fragment – Font Style</caption>
@@ -4757,7 +4769,7 @@
each character child of a <el>p</el> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>normal</code>.</p>
<p>The <att>tts:fontWeight</att> style is illustrated by the following example.</p>
<table id="style-attribute-fontWeight-example-1" role="example">
<caption>Example Fragment – Font Weight</caption>
@@ -4852,7 +4864,7 @@
href="#style-value-length"><length></loc>, 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the closest supported value.</p>
<note role="elaboration">
<p>In this context, the phrase <emph>closest supported value</emph> means the value for which the Euclidean distance between
the computed line height and the supported line height is minimized.</p>
@@ -5034,7 +5046,7 @@
<head>tts:origin</head>
<p>The <att>tts:origin</att> attribute is used to specify the
<emph>x</emph> and <emph>y</emph> coordinates of the origin of a
-region area with respect to the origin of the <emph>Root Container Region</emph>.</p>
+region area with respect to the origin of the <loc href="#terms-root-container-region">root container region</loc>.</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
@@ -5066,7 +5078,7 @@
</tr>
<tr>
<td><emph>Percentages:</emph></td>
-<td>relative to width and height of <emph>Root Container Region</emph></td>
+<td>relative to width and height of <loc href="#terms-root-container-region">root container region</loc></td>
</tr>
<tr>
<td><emph>Animatable:</emph></td>
@@ -5078,9 +5090,9 @@
then they must be interpreted as <emph>x</emph> and <emph>y</emph> coordinates, where the first specification
is the <emph>x</emph> coordinate, and the second specification is the <emph>y</emph> 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 <emph>Root Container Region</emph>.</p>
+of the style property must be considered to be the same as the origin of the <loc href="#terms-root-container-region">root container region</loc>.</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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the closest supported value.</p>
<note role="elaboration">
<p>In this context, the phrase <emph>closest supported value</emph> means the value for which the Euclidean distance between
the computed origin and the supported origin is minimized.</p>
@@ -5180,7 +5192,7 @@
style is <code>noWrap</code>.</p>
</note>
<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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>hidden</code>.</p>
<p>The <att>tts:overflow</att> style is illustrated by the following example.</p>
<table id="style-attribute-overflow-example-1" role="example">
<caption>Example Fragment – Overflow</caption>
@@ -5307,7 +5319,7 @@
after, and start edges, respectively.</p>
<p>The <loc href="#style-value-length"><length></loc> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the closest supported value.</p>
<note role="elaboration">
<p>In this context, the phrase <emph>closest supported value</emph> means the value for which the Euclidean distance between
the computed padding and the supported padding is minimized.</p>
@@ -5415,7 +5427,7 @@
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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>always</code>.</p>
<p>The <att>tts:showBackground</att> style is illustrated by the following example.</p>
<table id="style-attribute-showBackground-example-1" role="example">
<caption>Example Fragment – Show Background</caption>
@@ -5500,7 +5512,7 @@
</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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>start</code>.</p>
<p>The <att>tts:textAlign</att> style is illustrated by the following example.</p>
<table id="style-attribute-textAlign-example-1" role="example">
<caption>Example Fragment – Text Align</caption>
@@ -5607,7 +5619,7 @@
style property, each character child of a <el>p</el> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>none</code>.</p>
<note role="clarification">
<p>The syntax used above in defining the value of this property is based on the
value component syntax defined in <bibref ref="css2"/>, § 1.4.2.1. In essence,
@@ -5727,7 +5739,7 @@
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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>mixed</code>.</p>
<p>The <att>tts:textOrientation</att> style is illustrated by the following
example.</p>
<ednote>
@@ -5802,12 +5814,12 @@
cells is used in a <att>tts:textOutline</att> 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 <emph>Root Container Region</emph> is 640 by 480, then the
+is 20 by 10, and the extent of the <loc href="#terms-root-container-region">root container region</loc> 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>
</note>
<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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>none</code>.</p>
<p>The <att>tts:textOutline</att> style is illustrated by the following
example.</p>
<table id="style-attribute-textOutline-example-1" role="example">
@@ -5901,7 +5913,7 @@
each character child of a <el>p</el> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>normal</code>.</p>
<p>The <att>tts:unicodeBidi</att> style is illustrated by the following example.</p>
<table id="style-attribute-unicodeBidi-example-1" role="example">
<caption>Example Fragment – Unicode Bidirectionality</caption>
@@ -6001,7 +6013,7 @@
<p>The <att>tts:visibility</att> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>visible</code>.</p>
<p>The <att>tts:visibility</att> style is illustrated by the following example.</p>
<table id="style-attribute-visibility-example-1" role="example">
<caption>Example Fragment – Visibility</caption>
@@ -6115,7 +6127,7 @@
each character child of a <el>p</el> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>wrap</code>.</p>
<p>The <att>tts:wrapOption</att> style is illustrated by the following example.</p>
<table id="style-attribute-wrapOption-example-1" role="example">
<caption>Example Fragment – Wrap Option</caption>
@@ -6208,7 +6220,7 @@
</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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>lrtb</code>.</p>
<p>The <att>tts:writingMode</att> style is illustrated by the following example.</p>
<table id="style-attribute-writingMode-example-1" role="example">
<caption>Example Fragment – Writing Mode</caption>
@@ -6314,12 +6326,12 @@
<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 <emph>Document Instance</emph>.</p>
+order is defined as the postorder traversal of a <loc href="#terms-document-instance">document instance</loc>.</p>
<p>The semantics of the value <code>auto</code> are those defined by
<bibref ref="xsl11"/>, § 7.30.18, where the <el>tt</el> 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>
+then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the closest supported value.</p>
<note role="elaboration">
<p>In this context, the phrase <emph>closest supported value</emph> means the value for which the Euclidean distance between
the computed z-index and the supported z-index is minimized.</p>
@@ -6451,7 +6463,7 @@
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,
+<p>If a <loc href="#terms-presentation-processor">presentation processor</loc> does not support a specific,
valid opacity value, then it must interpret it as being equal to the
closest supported value.</p>
<note role="elaboration">
@@ -6584,10 +6596,10 @@
<p>The use of <bibref ref="srgb"/> 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
+example, a <loc href="#terms-presentation-processor">presentation processor</loc> may ultimately convert the SRGB values
used here to the YUV color space for rendition on a television device.</p>
</note>
-<p>If a presentation processor does not support a specific,
+<p>If a <loc href="#terms-presentation-processor">presentation processor</loc> does not support a specific,
valid color or alpha value, then it must interpret it as being equal
to the closest supported value.</p>
<note role="elaboration">
@@ -6857,14 +6869,14 @@
<p>The semantics of the unit of measure <code>c</code> (cell) are
defined by the parameter <specref
ref="parameter-attribute-cellResolution"/>.</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 <emph>Root Container Region</emph>, respectively.
+<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 <loc href="#terms-root-container-region">root container region</loc>, respectively.
For example, the length <code>25vw</code> is interpreted as 25% of the width of
-the <emph>Root Container Region</emph>.</p>
+the <loc href="#terms-root-container-region">root container region</loc>.</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 <emph>Root Container Region</emph>.</p>
+25% of the height of the <loc href="#terms-root-container-region">root container region</loc>.</p>
</div3>
<div3 id="style-value-namedColor">
<head><namedColor></head>
@@ -7005,7 +7017,7 @@
sacrificing locality of reference.</p>
</note>
<note role="explanation">
-<p>A single <loc href="#element-vocab-type-content">Content</loc> element may be associated with style properties by a hybrid mixture of
+<p>A single <loc href="#terms-content-element">content element</loc> 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 <specref ref="semantics-style-association-inline"/>.</p>
</note>
@@ -7051,7 +7063,7 @@
into general and specific sets, which further aids in style specification reuse.</p>
</note>
<note role="explanation">
-<p>A single <loc href="#element-vocab-type-content">Content</loc> element may be associated with style properties by a hybrid mixture of
+<p>A single <loc href="#terms-content-element">content element</loc> 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 <specref ref="semantics-style-association-inline"/>.</p>
</note>
@@ -7116,7 +7128,7 @@
<item><p><loc href="#semantics-style-inheritance-content">region style inheritance</loc></p></item>
</ulist>
<p>For the purpose of determining inherited styles, the element hierarchy of
-an intermediate synchronic document form of a <emph>Document Instance</emph> must be used, where
+an intermediate synchronic document form of a <loc href="#terms-document-instance">document instance</loc> must be used, where
such intermediate forms are defined by <specref ref="semantics-region-layout-step-1"/>.</p>
<note role="explanation">
<p>The intermediate synchronic document form is utilized rather than
@@ -7125,13 +7137,13 @@
</note>
<div4 id="semantics-style-inheritance-content">
<head>Content Style Inheritance</head>
-<p>Style properties are inherited from ancestor <loc href="#element-vocab-type-content">Content</loc> elements
+<p>Style properties are inherited from ancestor <loc href="#terms-content-element">content elements</loc>
within an intermediate synchronic document
-if a style property is not associated with a <loc href="#element-vocab-type-content">Content</loc> element (or
+if a style property is not associated with a <loc href="#terms-content-element">content element</loc> (or
an anonymous span) and the style property is designated as
inheritable.</p>
<note role="clarification">
-<p>The <el>tt</el> element is not a <loc href="#element-vocab-type-content">Content</loc> element;
+<p>The <el>tt</el> element is not a <loc href="#terms-content-element">content element</loc>;
consequently, the <el>body</el> element is the outermost element from which content style inheritance occurs.</p>
</note>
<p>If a style property is determined to require inheritance, then the inherited value must
@@ -7168,10 +7180,10 @@
</div4>
<div4 id="semantics-style-inheritance-region">
<head>Region Style Inheritance</head>
-<p>Style properties are inherited from a region element in the following case:</p>
+<p>Style properties are inherited from a <loc href="#layout-vocabulary-region">region</loc> element in the following case:</p>
<olist>
<item><p>if a style property <emph>P</emph> is not associated with
-a <loc href="#element-vocab-type-content">Content</loc> element
+a <loc href="#terms-content-element">content element</loc>
or an anonymous span <emph>E</emph> and the style
property is designated as inheritable, and</p></item> <item><p>if that
style property <emph>P</emph> is in the computed style
@@ -7258,14 +7270,14 @@
<emph>actual style set</emph> of that element.</p>
<note role="elaboration">
<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 <loc href="#terms-presentation-processor">presentation processor</loc>
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>
</note>
<note role="explanation">
-<p>In general, a TTML presentation processor will not have access
+<p>In general, a TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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>
@@ -7469,7 +7481,7 @@
property <emph>P</emph>, where the initial value of a property is
determined according to the specific property definition found above
in <specref ref="styling-attribute-vocabulary"/>;</p></item>
-<item><p>if the element type of <emph>E</emph> is a <loc href="#element-vocab-type-content">Content</loc> element
+<item><p>if the element type of <emph>E</emph> is a <loc href="#terms-content-element">content element</loc>
type or anonymous span, then set <emph>P′</emph> to the result of
looking up the value of <emph>P</emph> in the computed style set of
the immediate ancestor element of <emph>E</emph>, i.e.,
@@ -7518,7 +7530,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 <loc href="#element-vocab-type-content">Content</loc> element which has a presentation
+context of a layout or <loc href="#terms-content-element">content element</loc> which has a presentation
context, and not in the non-presentation, declaration context
of a <el>set</el> element or a referentiable <el>style</el> element.</p>
</note>
@@ -7535,7 +7547,7 @@
of <emph>E</emph> is not the styling element type <el>style</el>, is
not the layout element type <el>region</el>, is not the animation
element type <el>set</el>, and is not one of the
-<loc href="#element-vocab-type-content">Content</loc> element types <el>body</el>, <el>div</el>, <el>p</el>,
+<loc href="#terms-content-element">content element</loc> types <el>body</el>, <el>div</el>, <el>p</el>,
<el>span</el>, <el>br</el>, or anonymous span, then continue to the
next element in the preorder traversal;</p></item>
<item><p> <phrase role="strong">[resolve computed styles]</phrase>
@@ -7568,7 +7580,7 @@
<div2 id="layout-element-vocabulary">
<head>Layout Element Vocabulary</head>
<p>The following elements specify the structure and principal layout aspects of a
-<emph>Document Instance</emph>:</p>
+<loc href="#terms-document-instance">document instance</loc>:</p>
<ulist>
<item><p><specref ref="layout-vocabulary-layout"/></p></item>
<item><p><specref ref="layout-vocabulary-region"/></p></item>
@@ -7600,7 +7612,7 @@
</table>
<p>To the extent that time semantics apply to the content of the
<el>layout</el> element, the implied time interval of this element is
-defined to be coterminous with the <emph>Root Temporal Extent</emph>.</p>
+defined to be coterminous with the <loc href="#terms-root-temporal-extent">root temporal extent</loc>.</p>
</div3>
<div3 id="layout-vocabulary-region">
<head>region</head>
@@ -7608,10 +7620,10 @@
to be flowed for the purpose of presentation.</p>
<p>A <el>region</el> element may appear as either (1) a child of a
<loc href="#layout-vocabulary-layout">layout</loc> element or (2) a child of block level
-<loc href="#element-vocab-type-content">Content</loc> elements, specifically, of elements
+<loc href="#terms-content-element">content element</loc>, specifically, of elements
in the <loc href="#element-vocab-group-table">Block.class</loc> element group.
-In the former case, the region is referred to as an <emph>Out-of-line Region</emph>, while in the latter
-case, it is referred to as an <emph>Inline Region</emph>.</p>
+In the former case, the region is referred to as an <loc href="#terms-out-of-line-region">out-of-line region</loc>, while in the latter
+case, it is referred to as an <loc href="#terms-inline-region">inline region</loc>.</p>
<p>In addition, and in accordance with
<specref ref="semantics-style-inheritance-region"/>,
the <el>region</el> element may be used to specify inheritable style properties to be
@@ -7655,8 +7667,8 @@
</tr>
</tbody>
</table>
-<p>An out-of-line region may specify one or more of the timing attributes:
-<att>begin</att>, <att>end</att>, <att>dur</att>. An inline region must not
+<p>An <loc href="#terms-out-of-line-region">out-of-line region</loc> may specify one or more of the timing attributes:
+<att>begin</att>, <att>end</att>, <att>dur</att>. An <loc href="#terms-inline-region">inline region</loc> must not
specifiy a timing attribute, and, if specified, must be ignored for the purpose
of presentation processing.</p>
<p>If <att>begin</att> and (or) <att>end</att> attributes are specified on an out-of-line
@@ -7671,7 +7683,7 @@
If a <att>dur</att> attribute is specified on an out-of-line <el>region</el> element, then it
specifies the simple duration of the region.</p>
<p>The active time interval of an inline <el>region</el> element is the
-active time interval of its parent <loc href="#element-vocab-type-content">Content</loc> element.</p>
+active time interval of its parent <loc href="#terms-content-element">content element</loc>.</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>
@@ -7680,16 +7692,16 @@
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
+<p>For example, an author may wish to specify an <loc href="#terms-out-of-line-region">out-of-line region</loc> 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 <emph>Root Container Region</emph>
+region. An author may also wish to move a region within the <loc href="#terms-root-container-region">root container region</loc>
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 <loc href="#element-vocab-type-content">Content</loc> elements,
+<p>In contrast to <loc href="#terms-out-of-line-region">out-of-line regions</loc>, <loc href="#terms-inline-region">inline regions</loc> are specifically bound to
+the temporal context of their parent <loc href="#terms-content-element">content elements</loc>,
and, as such, do not require (or admit) the specification of independent timing.</p>
</note>
<p>If no <att>timeContainer</att> attribute is specified on
@@ -7707,11 +7719,11 @@
</div2>
<div2 id="layout-attribute-vocabulary">
<head>Layout Attribute Vocabulary</head>
-<p>This section defines the <specref ref="layout-attribute-region"/> attribute used with <loc href="#element-vocab-type-content">Content</loc> elements.</p>
+<p>This section defines the <specref ref="layout-attribute-region"/> attribute used with <loc href="#terms-content-element">content elements</loc>.</p>
<div3 id="layout-attribute-region">
<head>region</head>
<p>The <att>region</att> attribute is used to reference a <el>region</el>
-element which defines a space or area into which a <loc href="#element-vocab-type-content">Content</loc> element is intended to be flowed.</p>
+element which defines a space or area into which a <loc href="#terms-content-element">content element</loc> is intended to be flowed.</p>
<p>If specified, the value of a <att>region</att> attribute must
adhere to the <code>IDREF</code> data type defined by <bibref ref="xsd-2"/>,
§ 3.3.9, and, furthermore, this IDREF must reference a <el>region</el> element
@@ -7748,7 +7760,7 @@
</p>
<div3 id="semantics-default-region">
<head>Default Region</head>
-<p>If a <emph>Document Instance</emph> does not specify a
+<p>If a <loc href="#terms-document-instance">document instance</loc> does not specify a
<loc href="#layout-vocabulary-region"><el>region</el></loc> element,
then a <emph>default region</emph> is implied with the following characteristics:</p>
<ulist>
@@ -7756,21 +7768,21 @@
<p>the identity of the default region is considered to be anonymous;</p>
</item>
<item>
-<p>the extent of the default region is the same as the extent of the <emph>Root Container Region</emph>;</p>
-</item>
-<item>
-<p>the temporal interval of the default region is the same as the interval defined by the <emph>Root Temporal Extent</emph>;</p>
+<p>the extent of the default region is the same as the extent of the <loc href="#terms-root-container-region">root container region</loc>;</p>
+</item>
+<item>
+<p>the temporal interval of the default region is the same as the interval defined by the <loc href="#terms-root-temporal-extent">root temporal extent</loc>;</p>
</item>
</ulist>
<p>Furthermore, if no <loc
href="#layout-vocabulary-region"><el>region</el></loc> element is
specified, then the <loc
href="#layout-attribute-region"><att>region</att></loc> attribute must
-not be specified on any <loc href="#element-vocab-type-content">Content</loc> element in the <emph>Document Instance</emph>.</p>
-<p>If a default region is implied for a given <emph>Document Instance</emph>, then
+not be specified on any <loc href="#terms-content-element">content element</loc> in the <loc href="#terms-document-instance">document instance</loc>.</p>
+<p>If a default region is implied for a given <loc href="#terms-document-instance">document instance</loc>, then
the <loc href="#document-structure-vocabulary-body"><el>body</el></loc> element
is implicitly targeted to (associated with) the default region.</p>
-<p>When implying a default region, the <emph>Document Instance</emph> is to be
+<p>When implying a default region, the <loc href="#terms-document-instance">document instance</loc> is to be
treated as if a <loc
href="#layout-vocabulary-region"><el>region</el></loc> element and its
parent <loc href="#layout-vocabulary-layout"><el>layout</el></loc>
@@ -7813,9 +7825,9 @@
<div3 id="semantics-region-layout-step-1">
<head>Intermediate Synchronic Document Construction</head>
<p>For the purposes of performing presentation processing, the active time
-duration of a <emph>Document Instance</emph> is divided into a sequence of time coordinates where at
+duration of a <loc href="#terms-document-instance">document instance</loc> 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 <emph>Document Instance</emph> is mapped from its original, source
+then, at each such time coordinate, a <loc href="#terms-document-instance">document instance</loc> is mapped from its original, source
form, <emph>DOC<sub>source</sub></emph> ,
to an intermediate
synchronic document form,
@@ -7834,7 +7846,7 @@
</item>
<item>
<p>evaluating this sub-tree in a postorder traversal, prune elements if they
-are not a <loc href="#element-vocab-type-content">Content</loc> element, if they are temporally inactive, if they are empty,
+are not a <loc href="#terms-content-element">content element</loc>, if they are temporally inactive, if they are empty,
or if they aren't associated with region <emph>R</emph> according to the
<phrase role="strong">[associate region]</phrase> procedure;</p>
</item>
@@ -7868,7 +7880,7 @@
<date>2013-08-28</date>
<edtext>Define inline region association.</edtext>
</ednote>
-<p>A <loc href="#element-vocab-type-content">Content</loc> element is associated with a region according
+<p>A <loc href="#terms-content-element">content element</loc> is associated with a region according
to the following ordered rules, where the first rule satisfied
is used and remaining rules are skipped:</p>
<olist>
@@ -7895,12 +7907,12 @@
</glist>
<p>The result of performing the processing described above will be a sequence of
<emph>N</emph> intermediate synchronic
-<emph>Document Instances</emph>,
+<loc href="#terms-document-instance">document instances</loc>,
<emph>DOC<sub><phrase>inter<sub>0</sub></phrase></sub></emph> …
<emph>DOC<sub><phrase>inter<sub>N−1</sub></phrase></sub></emph>.</p>
<note id="semantics-smooth-scrolling-recommendation" role="elaboration">
<p>Where an implementation is able to detect significant similarity between two
-adjacent synchronic <emph>Document Instances</emph>,
+adjacent synchronic <loc href="#terms-document-instance">document instances</loc>,
<emph>DOC<sub><phrase>inter<sub>N</sub></phrase></sub></emph>
<emph>DOC<sub><phrase>inter<sub>N−1</sub></phrase></sub></emph>,
then it is preferred that the implementation make the transition between
@@ -7930,7 +7942,7 @@
<item>
<p>perform the following ordered sub-steps to create anonymous spans:</p>
<olist>
-<item><p>for each significant text node in a <loc href="#element-vocab-type-content">Content</loc> element,
+<item><p>for each significant text node in a <loc href="#terms-content-element">content element</loc>,
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></item>
@@ -7951,7 +7963,7 @@
<p>map the <el>tt</el> element to an <el>fo:root</el> element, populated
initially with an <el>fo:layout-master-set</el> element that contains a valid
<el>fo:simple-page-master</el> that, in turn, contains an
-<el>fo:region-body</el> child, where the extent of the <emph>Root Container Region</emph> expressed on the
+<el>fo:region-body</el> child, where the extent of the <loc href="#terms-root-container-region">root container region</loc> expressed on the
<el>tt</el> element is mapped to <att>page-width</att> and
<att>page-height</att> attributes on the <el>fo:simple-page-master</el>
element;</p>
@@ -7973,7 +7985,7 @@
associated with a <att>tts:display</att> style property with the value
<code>none</code>, map the element to a distinct <el>fo:block</el> element,
populating the style properties of <el>fo:block</el> by using the computed
-style set associated with each original TTML <loc href="#element-vocab-type-content">Content</loc> element;</p>
+style set associated with each original TTML <loc href="#terms-content-element">content element</loc>;</p>
</item>
<item>
<p>for the resulting <el>fo:block</el> formatting object
@@ -8014,7 +8026,7 @@
map the element or
sequence of character items to a distinct <el>fo:inline</el> element,
populating the style properties of <el>fo:inline</el> by using the computed
-style set associated with each original TTML <loc href="#element-vocab-type-content">Content</loc> element
+style set associated with each original TTML <loc href="#terms-content-element">content element</loc>
or anonymous span;</p>
</item>
<item>
@@ -8036,7 +8048,7 @@
<p>for each TTML style property attribute in some computed
style set that
has no counterpart in <bibref ref="xsl11"/>, map that attribute directly through
-to the relevant formatting object produced by the input TTML <loc href="#element-vocab-type-content">Content</loc> element to
+to the relevant formatting object produced by the input TTML <loc href="#terms-content-element">content element</loc> to
which the style property applies;</p>
</item>
<item>
@@ -8054,7 +8066,7 @@
the <code>page-viewport-area</code>,
which is generated by <code>fo:page-sequence</code> element by
reference to the sole generated <code>fo:simple-page-master</code>
-element, would correspond to the <emph>Root Container Region</emph> defined
+element, would correspond to the <loc href="#terms-root-container-region">root container region</loc> defined
above in <specref ref="definitions"/>.</p>
</note>
<note role="clarification">
@@ -8065,7 +8077,7 @@
</note>
<note>
<p>Due to the possible presence of TTML style properties or style property values
-in a given <emph>Document Instance</emph> for which there is no <bibref ref="xsl11"/> counterpart,
+in a given <loc href="#terms-document-instance">document instance</loc> for which there is no <bibref ref="xsl11"/> counterpart,
Implementors should recognize that it is the layout model of <bibref ref="xsl11"/> that is being referenced
by this specification, not the requirement to use a compliant <bibref ref="xsl11"/> formatting processor,
since such would not necessarily be sufficient to satisfy the full presentation semantics
@@ -8107,7 +8119,7 @@
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>
<note>
-<p>The intermediate documents shown below are not valid <emph>Document Instances</emph>,
+<p>The intermediate documents shown below are not valid <loc href="#terms-document-instance">document instances</loc>,
but rather, are representations of possible internal processing states used for
didactic purposes.</p>
</note>
@@ -8168,14 +8180,14 @@
</div2>
<div2 id="semantics-line-layout">
<head>Line Layout</head>
-<p>If a profile that applies to a <emph>Document Instance</emph>
+<p>If a profile that applies to a <loc href="#terms-document-instance">document instance</loc>
requires use of the <loc
href="#feature-lineBreak-uax14">#lineBreak-uax14</loc> feature
(i.e., the value attribute for the feature is specified as <code>use</code>), then
the recommendations defined by <loc
href="http://www.unicode.org/reports/tr14/#Algorithm">Line
Breaking Algorithm</loc> <bibref ref="uax14"/> apply when performing
-line layout on the content of the <emph>Document Instance</emph>.</p>
+line layout on the content of the <loc href="#terms-document-instance">document instance</loc>.</p>
</div2>
</div1>
<div1 id="timing">
@@ -8250,7 +8262,7 @@
is used with a <att>dur</att> attribute, it is intended to be interpreted as
a difference between two implied clock time expressions.</p>
</note>
-<p>When a <emph>Document Instance</emph> specifies the use of the
+<p>When a <loc href="#terms-document-instance">document instance</loc> specifies the use of the
<code>smpte</code> time base and <code>discontinuous</code> marker
mode, a (well-formed) <att>dur</att> attribute must not be specified on any
element.</p>
@@ -8462,7 +8474,7 @@
<div2 id="animation-element-vocabulary">
<head>Animation Element Vocabulary</head>
<p>The following elements specify the structure and principal animation aspects of a
-<emph>Document Instance</emph>:</p>
+<loc href="#terms-document-instance">document instance</loc>:</p>
<ulist>
<item><p><specref ref="animation-vocabulary-animation"/></p></item>
<item><p><specref ref="animation-vocabulary-animate"/></p></item>
@@ -8471,7 +8483,7 @@
<div3 id="animation-vocabulary-animation">
<head>animation</head>
<p>The <el>animation</el> element is a container element used to group
-out-of-line animation matter, including metadata that applies to animation matter.</p>
+<loc href="#terms-out-of-line-animation">out-of-line animation</loc> matter, including metadata that applies to animation matter.</p>
<p>The <el>animation</el> 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>
@@ -8495,15 +8507,16 @@
</table>
<p>To the extent that time semantics apply to the content of the
<el>animation</el> element, the implied time interval of this element is
-defined to be coterminous with the <emph>Root Temporal Extent</emph>.</p>
+defined to be coterminous with the <loc href="#terms-root-temporal-extent">root temporal extent</loc>.</p>
</div3>
<div3 id="animation-vocabulary-animate">
<head>animate</head>
<p>The <el>animate</el> element expresses a series of changes (animations) to be applied to a targetted attribute
of a targetted element.</p>
<p>An <el>animate</el> element may appear as either (1) a child of a
-<loc href="#element-vocab-type-content">Content</loc> or <el>region</el> element, referred to as inline animation, or
-(2) a child of an <loc href="#animation-vocabulary-animation">animation</loc> element, referred to as out-of-line animation.
+<loc href="#terms-content-element">content element</loc> or <el>region</el> element, referred to as <loc href="#terms-inline-animation">inline animation</loc>, or
+(2) a child of an <loc href="#animation-vocabulary-animation">animation</loc> element, referred to as
+<loc href="#terms-out-of-line-animation">out-of-line animation</loc>.
In the former case, the targetted element of the animation is the parent of the <el>animate</el> element; in the latter
case, the targetted element is the element referenced by the <att>xlink:href</att> attribute on the
<el>animate</el> element.</p>
@@ -8638,8 +8651,9 @@
<p>The <el>set</el> element expresses one or more a discrete changes (animations) to be applied to targetted attributes
of a targetted element.</p>
<p>A <el>set</el> element may appear as either (1) a child of a
-<loc href="#element-vocab-type-content">Content</loc> or <el>region</el> element, referred to as inline animation, or
-(2) a child of an <loc href="#animation-vocabulary-animation">animation</loc> element, referred to as out-of-line animation.
+<loc href="#terms-content-element">content element</loc> or <el>region</el> element, referred to as <loc href="#terms-inline-animation">inline animation</loc>, or
+(2) a child of an <loc href="#animation-vocabulary-animation">animation</loc> element, referred to as
+<loc href="#terms-out-of-line-animation">out-of-line animation</loc>.
In the former case, the targetted element of the animation is the parent of the <el>set</el> element; in the latter
case, the targetted element is the element referenced by the <att>xlink:href</att> attribute on the
<el>set</el> element.</p>
@@ -8746,10 +8760,10 @@
</tbody>
</table>
<note role="explanation">
-<p>In the above example, the <emph>Root Container Region</emph> is divided into a
+<p>In the above example, the <loc href="#terms-root-container-region">root container region</loc> 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
-<emph>Root Container Region</emph>, with its position varying over time in order to
+<loc href="#terms-root-container-region">root container region</loc>, 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>
</note>
@@ -8917,7 +8931,7 @@
</div3>
<div3 id="animation-value-fragmentIdentifier">
<head><fragmentIdentifier></head>
-<p>A <fragmentIdentifier> expression is used to target (refer to) an animation to a specific element in the same <emph>Document Instance</emph>.</p>
+<p>A <fragmentIdentifier> expression is used to target (refer to) an animation to a specific element in the same <loc href="#terms-document-instance">document instance</loc>.</p>
<table id="fragmentIdentifier-syntax" role="syntax">
<caption>Syntax Representation – <fragmentIdentifier></caption>
<tbody>
@@ -8961,7 +8975,7 @@
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 <emph>Document Instance</emph>,
+<p>A <fragmentIdentifer> expression must refer to an element in the same <loc href="#terms-document-instance">document instance</loc>,
i.e., the fragment component must be a valid IDREF.</p>
</div3>
<div3 id="animation-value-keySplines">
@@ -9120,7 +9134,7 @@
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 <emph>Document Instance</emph>, and (2) arbitrary
+specification for standardized use in a <loc href="#terms-document-instance">document instance</loc>, 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>
<div2 id="metadata-element-vocabulary">
@@ -9129,7 +9143,7 @@
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 <emph>Document Instances</emph>:
+used in a <loc href="#terms-document-instance">document instancea</loc>:
</p>
<ulist>
<item><p><specref ref="metadata-vocabulary-title"/></p></item>
@@ -9172,7 +9186,7 @@
<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 <el>metadata</el> element children on any
-<loc href="#element-vocab-type-content">Content</loc> element type. See specific element
+<loc href="#terms-content-element">content element</loc> type. See specific element
vocabulary definitions for any constraints that apply to such
usage.</p>
</note>
@@ -9404,7 +9418,7 @@
<el>metadata</el> element child of the <el>head</el> element.</p>
<note role="elaboration">
<p>A <el>ttm:agent</el> element instance is typically referenced using a <att>ttm:agent</att>
-attribute on a <loc href="#element-vocab-type-content">Content</loc> element type.</p>
+attribute on a <loc href="#terms-content-element">content element</loc> type.</p>
</note>
<note role="elaboration">
<p>If a character agent is played by multiple actors, then multiple character
@@ -9530,19 +9544,19 @@
<head>Metadata Attribute Vocabulary</head>
<p>This section specifies the following attributes in the TT Metadata Namespace
for use with the <el>metadata</el> element and with certain
-<loc href="#element-vocab-type-content">Content</loc> element types:</p>
+<loc href="#terms-content-element">content element</loc> types:</p>
<ulist>
<item><p><specref ref="metadata-attribute-agent"/></p></item>
<item><p><specref ref="metadata-attribute-role"/></p></item>
</ulist>
<note role="explanation">
-<p>Only certain metadata item attributes may be used with <loc href="#element-vocab-type-content">Content</loc> elements. See
-the definitions of <loc href="#element-vocab-type-content">Content</loc> elements to determine permissible usage.</p>
+<p>Only certain metadata item attributes may be used with <loc href="#terms-content-element">content element</loc>. See
+the definitions of <loc href="#terms-content-element">content elements</loc> to determine permissible usage.</p>
</note>
<div3 id="metadata-attribute-agent">
<head>ttm:agent</head>
<p>The <att>ttm:agent</att> attribute takes an <code>IDREFS</code>
-value, and is used with certain <loc href="#element-vocab-type-content">Content</loc> elements to designate the
+value, and is used with certain <loc href="#terms-content-element">content elements</loc> to designate the
agents that perform or are
involved in the performance of the content.</p>
<p>If specified, a <att>ttm:agent</att> attribute must reference <emph>significant</emph>
@@ -9559,7 +9573,7 @@
<p>The <att>ttm:role</att> attribute may be used by a content author
to express
the roles, functions, or characteristics
-of some <loc href="#element-vocab-type-content">Content</loc> element that is so labeled.</p>
+of some <loc href="#terms-content-element">content element</loc> that is so labeled.</p>
<p>If specified, the value of this attribute must adhere to the following
syntax, where
the syntactic element <emph>S</emph> must adhere to production
@@ -9628,7 +9642,7 @@
<div1 id="reduced-infoset">
<head>Reduced XML Infoset</head>
<p><emph>This appendix is normative.</emph></p>
-<p>For the purposes of this specification, a <emph>Reduced XML Infoset</emph> is
+<p>For the purposes of this specification, a <loc href="#terms-reduced-xml-infoset">reduced xml infoset</loc> is
an XML Information Set <bibref ref="infoset"/> that consists of only the following information items
and information item properties:</p>
<div2 id="reduced-infoset-document">
@@ -9645,8 +9659,9 @@
<item><p><code>[children]</code></p></item>
<item><p><code>[attributes]</code></p></item>
</ulist>
-<p>Child information items <code>[children]</code> are reduced to
-only element and character information items.</p>
+<p>Child information items <code>[children]</code> are reduced to only
+<loc href="terms-element-information-item">element information items</loc> and
+<loc href="terms-character-information-item">character information items</loc>.</p>
</div2>
<div2 id="reduced-infoset-attribute">
<head>Attribute Information Item</head>
@@ -9655,6 +9670,9 @@
<item><p><code>[local name]</code></p></item>
<item><p><code>[normalized value]</code></p></item>
</ulist>
+<note role="elaboration">
+<p>See also <loc href="terms-attribute-information-item">attribute information item</loc>.</p>
+</note>
</div2>
<div2 id="reduced-infoset-character">
<head>Character Information Item</head>
@@ -9663,13 +9681,16 @@
</ulist>
<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>
+<note role="elaboration">
+<p>See also <loc href="terms-character-information-item">character information item</loc>.</p>
+</note>
</div2>
</div1>
<div1 id="schemas">
<head>Schemas</head>
<p><emph>This appendix is normative.</emph></p>
<p>This appendix specifies the following schemas for use with
-<emph>Document Instances</emph>:</p>
+<loc href="#terms-document-instance">document instances</loc>:</p>
<ulist>
<item><p>Relax NG, Compact Syntax (RNC) Schema</p></item>
<item><p>XML Schema Definition (XSD) Schema</p></item>
@@ -9711,7 +9732,7 @@
<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>
+or optional for a transformation or <loc href="#terms-presentation-processor">presentation processor</loc>.</p>
<note>
<p>A TTML processor is said to <emph>implement the transformation semantics</emph> or
<emph>implement the presentation semantics</emph> of feature designation <emph>F</emph>
@@ -9748,7 +9769,7 @@
</ednote>
<div3 id="feature-animation">
<head>#animation</head>
-<p>A TTML transformation processor supports the <code>#animation</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#animation</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <specref ref="animation"/>:</p>
<ulist>
@@ -9756,18 +9777,18 @@
<item><p><loc href="#animation-vocabulary-animate"><el>animate</el></loc></p></item>
<item><p><loc href="#animation-vocabulary-set"><el>set</el></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#animation</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#animation</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p>
</div3>
<div3 id="feature-backgroundColor">
<head>#backgroundColor</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#backgroundColor</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#backgroundColor</code> feature if it (1) implements presentation semantic support
for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
@@ -9778,13 +9799,13 @@
</div3>
<div3 id="feature-backgroundColor-block">
<head>#backgroundColor-block</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#backgroundColor-block</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute when applied to a content element that would generate a
block area during presentation processing.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#backgroundColor-block</code> feature if it (1) implements presentation semantic
support for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
@@ -9796,13 +9817,13 @@
</div3>
<div3 id="feature-backgroundColor-inline">
<head>#backgroundColor-inline</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#backgroundColor-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute when applied to a content element that would generate an
inline area during presentation processing.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#backgroundColor-inline</code> feature if it (1) implements presentation semantic
support for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
@@ -9814,13 +9835,13 @@
</div3>
<div3 id="feature-backgroundColor-region">
<head>#backgroundColor-region</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#backgroundColor-region</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute when applied to a <loc
href="#layout-vocabulary-region"><el>region</el></loc> element.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#backgroundColor-region</code> feature if it (1) implements presentation semantic
support for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
@@ -9846,12 +9867,12 @@
</div3>
<div3 id="feature-border">
<head>#border</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#border</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-border"><att>tts:border</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#border</code> feature if it (1) implements presentation semantic support
for the <loc
href="#style-attribute-border"><att>tts:border</att></loc>
@@ -9867,12 +9888,12 @@
</div3>
<div3 id="feature-cellResolution">
<head>#cellResolution</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#cellResolution</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-cellResolution"><att>ttp:cellResolution</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#cellResolution</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-cellResolution"><att>ttp:cellResolution</att></loc>
@@ -9880,12 +9901,12 @@
</div3>
<div3 id="feature-clockMode">
<head>#clockMode</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#clockMode</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#clockMode</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
@@ -9893,12 +9914,12 @@
</div3>
<div3 id="feature-clockMode-gps">
<head>#clockMode-gps</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#clockMode-gps</code> feature if it recognizes and is capable of
transforming the <code>gps</code> value of the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#clockMode-gps</code> feature if it implements presentation semantic support
for the <code>gps</code> value of the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
@@ -9906,12 +9927,12 @@
</div3>
<div3 id="feature-clockMode-local">
<head>#clockMode-local</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#clockMode-local</code> feature if it recognizes and is capable of
transforming the <code>local</code> value of the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#clockMode-local</code> feature if it implements presentation semantic support
for the <code>local</code> value of the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
@@ -9919,12 +9940,12 @@
</div3>
<div3 id="feature-clockMode-utc">
<head>#clockMode-utc</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#clockMode-utc</code> feature if it recognizes and is capable of
transforming the <code>utc</code> value of the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#clockMode-utc</code> feature if it implements presentation semantic support
for the <code>utc</code> value of the <loc
href="#parameter-attribute-clockMode"><att>ttp:clockMode</att></loc>
@@ -9932,12 +9953,12 @@
</div3>
<div3 id="feature-color">
<head>#color</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#color</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-color"><att>tts:color</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#color</code> feature if it (1) implements presentation semantic support
for the <loc
href="#style-attribute-color"><att>tts:color</att></loc>
@@ -9948,7 +9969,7 @@
</div3>
<div3 id="feature-content">
<head>#content</head>
-<p>A TTML transformation processor supports the <code>#content</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#content</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <specref ref="content"/>:</p>
<ulist>
@@ -9958,13 +9979,13 @@
<item><p><loc href="#content-vocabulary-span"><el>span</el></loc></p></item>
<item><p><loc href="#content-vocabulary-br"><el>br</el></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#content</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#content</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p>
</div3>
<div3 id="feature-core">
<head>#core</head>
-<p>A TTML transformation processor supports the <code>#core</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#core</code>
feature if it recognizes and is capable of transforming the following
core attributes vocabulary defined by <specref ref="content"/>:</p>
<ulist>
@@ -9972,18 +9993,18 @@
<item><p><loc href="#content-attribute-id">@<att>xml:lang</att></loc></p></item>
<item><p><loc href="#content-attribute-id">@<att>xml:space</att></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#core</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#core</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p>
</div3>
<div3 id="feature-direction">
<head>#direction</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#direction</code> feature if it recognizes and is capable of
transforming all defined values of the <loc
href="#style-attribute-direction"><att>tts:direction</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#direction</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-direction"><att>tts:direction</att></loc>
@@ -9991,12 +10012,12 @@
</div3>
<div3 id="feature-display">
<head>#display</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#display</code> feature if it recognizes and is capable of
transforming all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#display</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
@@ -10004,13 +10025,13 @@
</div3>
<div3 id="feature-display-block">
<head>#display-block</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#display-block</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
attribute when applied to a content element that would generate a
block area during presentation processing.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#display-block</code> feature if it implements presentation semantic
support for all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
@@ -10019,13 +10040,13 @@
</div3>
<div3 id="feature-display-inline">
<head>#display-inline</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#display-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
attribute when applied to a content element that would generate an
inline area during presentation processing.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#display-inline</code> feature if it implements presentation semantic
support for all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
@@ -10034,13 +10055,13 @@
</div3>
<div3 id="feature-display-region">
<head>#display-region</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#display-region</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
attribute when applied to a <loc
href="#layout-vocabulary-region"><el>region</el></loc> element.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#display-region</code> feature if it implements presentation semantic
support for all defined values of the <loc
href="#style-attribute-display"><att>tts:display</att></loc>
@@ -10049,12 +10070,12 @@
</div3>
<div3 id="feature-displayAlign">
<head>#displayAlign</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#displayAlign</code> feature if it recognizes and is capable of
transforming all defined values of the <loc
href="#style-attribute-displayAlign"><att>tts:displayAlign</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#displayAlign</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-displayAlign"><att>tts:displayAlign</att></loc>
@@ -10062,12 +10083,12 @@
</div3>
<div3 id="feature-dropMode">
<head>#dropMode</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#dropMode</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#dropMode</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
@@ -10075,12 +10096,12 @@
</div3>
<div3 id="feature-dropMode-dropNTSC">
<head>#dropMode-dropNTSC</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#dropMode-dropNTSC</code> feature if it recognizes and is capable of
transforming the <code>dropNTSC</code> value of the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#dropMode-dropNTSC</code> feature if it implements presentation semantic support
for the <code>dropNTSC</code> value of the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
@@ -10088,12 +10109,12 @@
</div3>
<div3 id="feature-dropMode-dropPAL">
<head>#dropMode-dropPAL</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#dropMode-dropPAL</code> feature if it recognizes and is capable of
transforming the <code>dropPAL</code> value of the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#dropMode-dropPAL</code> feature if it implements presentation semantic support
for the <code>dropPAL</code> value of the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
@@ -10101,12 +10122,12 @@
</div3>
<div3 id="feature-dropMode-nonDrop">
<head>#dropMode-nonDrop</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#dropMode-nonDrop</code> feature if it recognizes and is capable of
transforming the <code>nonDrop</code> value of the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#dropMode-nonDrop</code> feature if it implements presentation semantic support
for the <code>nonDrop</code> value of the <loc
href="#parameter-attribute-dropMode"><att>ttp:dropMode</att></loc>
@@ -10114,12 +10135,12 @@
</div3>
<div3 id="feature-extent">
<head>#extent</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#extent</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-extent"><att>tts:extent</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#extent</code> feature if it implements presentation semantic support for
the <loc
href="#style-attribute-extent"><att>tts:extent</att></loc>
@@ -10127,13 +10148,13 @@
</div3>
<div3 id="feature-extent-region">
<head>#extent-region</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#extent-region</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-extent"><att>tts:extent</att></loc>
attribute when applied to a <loc
href="#layout-vocabulary-region"><el>region</el></loc> element.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#extent-region</code> feature if it implements presentation semantic support for
the <loc
href="#style-attribute-extent"><att>tts:extent</att></loc>
@@ -10142,13 +10163,13 @@
</div3>
<div3 id="feature-extent-root">
<head>#extent-root</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#extent-root</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-extent"><att>tts:extent</att></loc>
attribute when applied to the <loc
href="#document-structure-vocabulary-tt"><el>tt</el></loc> element.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#extent-root</code> feature if it implements presentation semantic support for
the <loc
href="#style-attribute-extent"><att>tts:extent</att></loc>
@@ -10157,12 +10178,12 @@
</div3>
<div3 id="feature-fontFamily">
<head>#fontFamily</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontFamily</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-fontFamily"><att>tts:fontFamily</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontFamily</code> feature if it implements presentation semantic support
for the <loc
href="#style-attribute-fontFamily"><att>tts:fontFamily</att></loc>
@@ -10170,14 +10191,14 @@
</div3>
<div3 id="feature-fontFamily-generic">
<head>#fontFamily-generic</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontFamily-generic</code> feature if it recognizes and is
capable of transforming <loc
href="#style-value-genericFamilyName"><genericFamilyName></loc>
values when used with the <loc
href="#style-attribute-fontFamily"><att>tts:fontFamily</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontFamily-generic</code> feature if it implements presentation semantic
support for <loc
href="#style-value-genericFamilyName"><genericFamilyName></loc>
@@ -10187,14 +10208,14 @@
</div3>
<div3 id="feature-fontFamily-non-generic">
<head>#fontFamily-non-generic</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontFamily-non-generic</code> feature if it recognizes and is
capable of transforming <loc
href="#style-value-familyName"><familyName></loc>
values when used with the <loc
href="#style-attribute-fontFamily"><att>tts:fontFamily</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontFamily-non-generic</code> feature if it implements presentation semantic
support for <loc
href="#style-value-familyName"><familyName></loc>
@@ -10204,12 +10225,12 @@
</div3>
<div3 id="feature-fontSize">
<head>#fontSize</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontSize</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-fontSize"><att>tts:fontSize</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontSize</code> feature if it implements presentation semantic support
for the <loc
href="#style-attribute-fontSize"><att>tts:fontSize</att></loc>
@@ -10217,13 +10238,13 @@
</div3>
<div3 id="feature-fontSize-anamorphic">
<head>#fontSize-anamorphic</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontSize-anamorphic</code> feature if it recognizes and is
capable of transforming values of the <loc
href="#style-attribute-fontSize"><att>tts:fontSize</att></loc>
attribute that consist of two <loc
href="#style-value-length"><length></loc> specifications.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontSize-anamorphic</code> feature if it implements presentation semantic
support for defined values of the <loc
href="#style-attribute-fontSize"><att>tts:fontSize</att></loc>
@@ -10232,13 +10253,13 @@
</div3>
<div3 id="feature-fontSize-isomorphic">
<head>#fontSize-isomorphic</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontSize-isomorphic</code> feature if it recognizes and is
capable of transforming values of the <loc
href="#style-attribute-fontSize"><att>tts:fontSize</att></loc>
attribute that consist of a single <loc
href="#style-value-length"><length></loc> specification.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontSize-isomorphic</code> feature if it implements presentation semantic
support for defined values of the <loc
href="#style-attribute-fontSize"><att>tts:fontSize</att></loc>
@@ -10247,12 +10268,12 @@
</div3>
<div3 id="feature-fontStyle">
<head>#fontStyle</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontStyle</code> feature if it recognizes and is capable of
transforming all defined values of the <loc
href="#style-attribute-fontStyle"><att>tts:fontStyle</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontStyle</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-fontStyle"><att>tts:fontStyle</att></loc>
@@ -10260,12 +10281,12 @@
</div3>
<div3 id="feature-fontStyle-italic">
<head>#fontStyle-italic</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontStyle-italic</code> feature if it recognizes and is
capable of transforming the <code>italic</code> value of the <loc
href="#style-attribute-fontStyle"><att>tts:fontStyle</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontStyle-italic</code> feature if it implements presentation semantic
support for the <code>italic</code> of the <loc
href="#style-attribute-fontStyle"><att>tts:fontStyle</att></loc>
@@ -10273,12 +10294,12 @@
</div3>
<div3 id="feature-fontStyle-oblique">
<head>#fontStyle-oblique</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontStyle-oblique</code> feature if it recognizes and is
capable of transforming the <code>oblique</code> value of the <loc
href="#style-attribute-fontStyle"><att>tts:fontStyle</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontStyle-oblique</code> feature if it implements presentation semantic
support for the <code>oblique</code> of the <loc
href="#style-attribute-fontStyle"><att>tts:fontStyle</att></loc>
@@ -10286,12 +10307,12 @@
</div3>
<div3 id="feature-fontWeight">
<head>#fontWeight</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontWeight</code> feature if it recognizes and is capable of
transforming all defined values of the <loc
href="#style-attribute-fontWeight"><att>tts:fontWeight</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontWeight</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-fontWeight"><att>tts:fontWeight</att></loc>
@@ -10299,12 +10320,12 @@
</div3>
<div3 id="feature-fontWeight-bold">
<head>#fontWeight-bold</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#fontWeight-bold</code> feature if it recognizes and is
capable of transforming <code>bold</code> value of the <loc
href="#style-attribute-fontWeight"><att>tts:fontWeight</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#fontWeight-bold</code> feature if it implements presentation semantic
support for the <code>bold</code> of the <loc
href="#style-attribute-fontWeight"><att>tts:fontWeight</att></loc>
@@ -10312,12 +10333,12 @@
</div3>
<div3 id="feature-frameRate">
<head>#frameRate</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#frameRate</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-frameRate"><att>ttp:frameRate</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#frameRate</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-frameRate"><att>ttp:frameRate</att></loc>
@@ -10325,12 +10346,12 @@
</div3>
<div3 id="feature-frameRateMultiplier">
<head>#frameRateMultiplier</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#frameRateMultiplier</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-frameRateMultiplier"><att>ttp:frameRateMultiplier</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#frameRateMultiplier</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-frameRateMultiplier"><att>ttp:frameRateMultiplier</att></loc>
@@ -10338,7 +10359,7 @@
</div3>
<div3 id="feature-layout">
<head>#layout</head>
-<p>A TTML transformation processor supports the <code>#layout</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#layout</code>
feature if it (1) recognizes and is capable of transforming the following
vocabulary defined by <specref ref="layout"/>:</p>
<ulist>
@@ -10354,17 +10375,17 @@
<item><p><loc
href="#style-attribute-origin"><att>tts:origin</att></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#layout</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#layout</code>
feature if it implements presentation semantic support for the
same vocabulary and features enumerated above.</p>
</div3>
<div3 id="feature-length">
<head>#length</head>
-<p>A TTML transformation processor supports the <code>#length</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#length</code>
feature if it recognizes and is capable of transforming all defined
values of the <loc href="#style-value-length"><length></loc>
style value expression.</p>
-<p>A TTML presentation processor supports the <code>#length</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#length</code>
feature if it implements presentation semantic support for all defined values of
the <loc href="#style-value-length"><length></loc> style value
expression.</p>
@@ -10382,12 +10403,12 @@
</div3>
<div3 id="feature-length-cell">
<head>#length-cell</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-cell</code> feature if it recognizes and is capable of
transforming scalar values of the <loc
href="#style-value-length"><length></loc> style value expression
that use <code>c</code> (cell) units.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-cell</code> feature if it implements presentation semantic support
for scalar values of the <loc
href="#style-value-length"><length></loc> style value expression
@@ -10402,12 +10423,12 @@
</div3>
<div3 id="feature-length-em">
<head>#length-em</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-em</code> feature if it recognizes and is capable of
transforming scalar values of the <loc
href="#style-value-length"><length></loc> style value expression
that use <code>em</code> (EM) units.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-em</code> feature if it implements presentation semantic support
for scalar values of the <loc
href="#style-value-length"><length></loc> style value expression
@@ -10422,12 +10443,12 @@
</div3>
<div3 id="feature-length-integer">
<head>#length-integer</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-integer</code> feature if it recognizes and is
capable of transforming integer values of the <loc
href="#style-value-length"><length></loc> style value
expression.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-integer</code> feature if it implements presentation semantic
support for integer values of the <loc
href="#style-value-length"><length></loc> style value
@@ -10441,12 +10462,12 @@
</div3>
<div3 id="feature-length-negative">
<head>#length-negative</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-negative</code> feature if it recognizes and is
capable of transforming negative values of the <loc
href="#style-value-length"><length></loc> style value
expression.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-negative</code> feature if it implements presentation semantic
support for negative values of the <loc
href="#style-value-length"><length></loc> style value
@@ -10460,12 +10481,12 @@
</div3>
<div3 id="feature-length-percentage">
<head>#length-percentage</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-percentage</code> feature if it recognizes and is
capable of transforming percentage values of the <loc
href="#style-value-length"><length></loc> style value
expression.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-percentage</code> feature if it implements presentation semantic
support for percentage values of the <loc
href="#style-value-length"><length></loc> style value
@@ -10481,12 +10502,12 @@
</div3>
<div3 id="feature-length-pixel">
<head>#length-pixel</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-pixel</code> feature if it recognizes and is capable of
transforming scalar values of the <loc
href="#style-value-length"><length></loc> style value expression
that use <code>px</code> (pixel) units.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-pixel</code> feature if it implements presentation semantic support
for scalar values of the <loc
href="#style-value-length"><length></loc> style value expression
@@ -10501,12 +10522,12 @@
</div3>
<div3 id="feature-length-positive">
<head>#length-positive</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-positive</code> feature if it recognizes and is
capable of transforming positive values of the <loc
href="#style-value-length"><length></loc> style value
expression.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-positive</code> feature if it implements presentation semantic
support for positive values of the <loc
href="#style-value-length"><length></loc> style value
@@ -10526,12 +10547,12 @@
</div3>
<div3 id="feature-length-real">
<head>#length-real</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#length-real</code> feature if it recognizes and is
capable of transforming real values of the <loc
href="#style-value-length"><length></loc> style value
expression.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#length-real</code> feature if it implements presentation semantic
support for real values of the <loc
href="#style-value-length"><length></loc> style value
@@ -10551,22 +10572,22 @@
</div3>
<div3 id="feature-lineBreak-uax14">
<head>#lineBreak-uax14</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#lineBreak-uax14</code> feature if it recognizes and is capable of
transforming requirements expressed by <bibref ref="uax14"/> into its
target document space.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#lineBreak-uax14</code> feature if it implements presentation semantic support
for <bibref ref="uax14"/> as applies to line breaking.</p>
</div3>
<div3 id="feature-lineHeight">
<head>#lineHeight</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#lineHeight</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-lineHeight"><att>tts:lineHeight</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#lineHeight</code> feature if it implements presentation semantic support for
the <loc
href="#style-attribute-lineHeight"><att>tts:lineHeight</att></loc>
@@ -10574,12 +10595,12 @@
</div3>
<div3 id="feature-markerMode">
<head>#markerMode</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#markerMode</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-markerMode"><att>ttp:markerMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#markerMode</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-markerMode"><att>ttp:markerMode</att></loc>
@@ -10587,12 +10608,12 @@
</div3>
<div3 id="feature-markerMode-continuous">
<head>#markerMode-continuous</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#markerMode-continuous</code> feature if it recognizes and is capable of
transforming the <code>continuous</code> value of the <loc
href="#parameter-attribute-markerMode"><att>ttp:markerMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#markerMode-continuous</code> feature if it implements presentation semantic support
for the <code>continuous</code> value of the <loc
href="#parameter-attribute-markerMode"><att>ttp:markerMode</att></loc>
@@ -10600,12 +10621,12 @@
</div3>
<div3 id="feature-markerMode-discontinuous">
<head>#markerMode-discontinuous</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#markerMode-discontinuous</code> feature if it recognizes and is capable of
transforming the <code>discontinuous</code> value of the <loc
href="#parameter-attribute-markerMode"><att>ttp:markerMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#markerMode-discontinuous</code> feature if it implements presentation semantic support
for the <code>discontinuous</code> value of the <loc
href="#parameter-attribute-markerMode"><att>ttp:markerMode</att></loc>
@@ -10613,7 +10634,7 @@
</div3>
<div3 id="feature-metadata">
<head>#metadata</head>
-<p>A TTML transformation processor supports the <code>#metadata</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#metadata</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <specref ref="metadata"/>:</p>
<ulist>
@@ -10627,7 +10648,7 @@
<item><p><loc href="#metadata-attribute-agent">@<att>ttm:agent</att></loc></p></item>
<item><p><loc href="#metadata-attribute-role">@<att>ttm:role</att></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#metadata</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#metadata</code>
feature if it recognizes and is capable of presenting the information
expressed by the same vocabulary enumerated above.</p>
<note role="clarification">
@@ -10639,30 +10660,30 @@
</div3>
<div3 id="feature-nested-div">
<head>#nested-div</head>
-<p>A TTML transformation processor supports the <code>#nested-div</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#nested-div</code>
feature if it recognizes and is capable of transforming nested
<loc href="#content-vocabulary-div"><el>div</el></loc> elements.</p>
-<p>A TTML presentation processor supports the <code>#nested-div</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#nested-div</code>
feature if it implements presentation semantic support for nested
<loc href="#content-vocabulary-div"><el>div</el></loc> elements.</p>
</div3>
<div3 id="feature-nested-span">
<head>#nested-span</head>
-<p>A TTML transformation processor supports the <code>#nested-span</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#nested-span</code>
feature if it recognizes and is capable of transforming nested
<loc href="#content-vocabulary-span"><el>span</el></loc> elements.</p>
-<p>A TTML presentation processor supports the <code>#nested-span</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#nested-span</code>
feature if it implements presentation semantic support for nested
<loc href="#content-vocabulary-span"><el>span</el></loc> elements.</p>
</div3>
<div3 id="feature-opacity">
<head>#opacity</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#opacity</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-opacity"><att>tts:opacity</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#opacity</code> feature if it (1) implements presentation semantic support for
the <loc
href="#style-attribute-opacity"><att>tts:opacity</att></loc>
@@ -10671,12 +10692,12 @@
</div3>
<div3 id="feature-origin">
<head>#origin</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#origin</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-origin"><att>tts:origin</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#origin</code> feature if it implements presentation semantic support for
the <loc
href="#style-attribute-origin"><att>tts:origin</att></loc>
@@ -10684,12 +10705,12 @@
</div3>
<div3 id="feature-overflow">
<head>#overflow</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#overflow</code> feature if it recognizes and is capable of
transforming all defined values of the <loc
href="#style-attribute-overflow"><att>tts:overflow</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#overflow</code> feature if it implements presentation semantic support for
all defined values of the <loc
href="#style-attribute-overflow"><att>tts:overflow</att></loc>
@@ -10697,12 +10718,12 @@
</div3>
<div3 id="feature-overflow-visible">
<head>#overflow-visible</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#overflow-visible</code> feature if it recognizes and is capable of
transforming the <code>visible</code> value of the <loc
href="#style-attribute-overflow"><att>tts:overflow</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#overflow-visible</code> feature if it implements presentation semantic support for
the <code>visible</code> value of the <loc
href="#style-attribute-overflow"><att>tts:overflow</att></loc>
@@ -10710,12 +10731,12 @@
</div3>
<div3 id="feature-padding">
<head>#padding</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#padding</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#padding</code> feature if it implements presentation semantic support for
the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc>
@@ -10723,13 +10744,13 @@
</div3>
<div3 id="feature-padding-1">
<head>#padding-1</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#padding-1</code> feature if it recognizes and is capable of
transforming values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of one <loc
href="#style-value-length"><length></loc> specification.</p>
-<p>A TTML presentation processor supports the <code>#padding-1</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#padding-1</code>
feature if it implements presentation semantic support for values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of one <loc
@@ -10737,13 +10758,13 @@
</div3>
<div3 id="feature-padding-2">
<head>#padding-2</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#padding-2</code> feature if it recognizes and is capable of
transforming values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of two <loc
href="#style-value-length"><length></loc> specification.</p>
-<p>A TTML presentation processor supports the <code>#padding-2</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#padding-2</code>
feature if it implements presentation semantic support for values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of two <loc
@@ -10751,13 +10772,13 @@
</div3>
<div3 id="feature-padding-3">
<head>#padding-3</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#padding-3</code> feature if it recognizes and is capable of
transforming values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of three <loc
href="#style-value-length"><length></loc> specification.</p>
-<p>A TTML presentation processor supports the <code>#padding-3</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#padding-3</code>
feature if it implements presentation semantic support for values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of three <loc
@@ -10765,13 +10786,13 @@
</div3>
<div3 id="feature-padding-4">
<head>#padding-4</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#padding-4</code> feature if it recognizes and is capable of
transforming values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of four <loc
href="#style-value-length"><length></loc> specification.</p>
-<p>A TTML presentation processor supports the <code>#padding-4</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#padding-4</code>
feature if it implements presentation semantic support for values of the <loc
href="#style-attribute-padding"><att>tts:padding</att></loc> attribute
that consist of four <loc
@@ -10779,12 +10800,12 @@
</div3>
<div3 id="feature-pixelAspectRatio">
<head>#pixelAspectRatio</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#pixelAspectRatio</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-pixelAspectRatio"><att>ttp:pixelAspectRatio</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#pixelAspectRatio</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-pixelAspectRatio"><att>ttp:pixelAspectRatio</att></loc>
@@ -10815,7 +10836,7 @@
</div3>
<div3 id="feature-profile">
<head>#profile</head>
-<p>A TTML transformation processor supports the <code>#profile</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#profile</code>
feature if it recognizes and is capable of transforming the
<loc href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
attribute on the <loc
@@ -10834,18 +10855,18 @@
<item><p><loc
href="#parameter-vocabulary-extension"><el>ttp:extension</el></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#profile</code> feature if it implements presentation semantic support
for the same vocabulary specified above.</p>
</div3>
<div3 id="feature-showBackground">
<head>#showBackground</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#showBackground</code> feature if it recognizes and is capable
of transforming all defined values of the <loc
href="#style-attribute-showBackground"><att>tts:showBackground</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#showBackground</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-showBackground"><att>tts:showBackground</att></loc>
@@ -10853,20 +10874,20 @@
</div3>
<div3 id="feature-structure">
<head>#structure</head>
-<p>A TTML transformation processor supports the <code>#structure</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#structure</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <specref ref="content"/>:</p>
<ulist>
<item><p><loc href="#document-structure-vocabulary-tt"><el>tt</el></loc></p></item>
<item><p><loc href="#document-structure-vocabulary-head"><el>head</el></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#structure</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#structure</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p>
</div3>
<div3 id="feature-styling">
<head>#styling</head>
-<p>A TTML transformation processor supports the <code>#styling</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#styling</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <specref ref="styling"/>:</p>
<ulist>
@@ -10874,84 +10895,84 @@
<item><p><loc href="#styling-vocabulary-style"><el>style</el></loc></p></item>
<item><p><loc href="#style-attribute-style">@<att>style</att></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#styling</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#styling</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p>
</div3>
<div3 id="feature-styling-chained">
<head>#styling-chained</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#styling-chained</code> feature if it recognizes and is capable
of transforming chained style association as defined by <specref
ref="semantics-style-association-chained-referential"/>.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#styling-chained</code> feature if it implements presentation semantic
support for chained style association as defined by <specref
ref="semantics-style-association-chained-referential"/>.</p>
</div3>
<div3 id="feature-styling-inheritance-content">
<head>#styling-inheritance-content</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#styling-inheritance</code> feature if it recognizes and is
capable of transforming content style inheritance as defined by
<specref ref="semantics-style-inheritance-content"/>.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#styling-inheritance-content</code> feature if it implements
presentation semantic support for content style inheritance as defined by <specref
ref="semantics-style-inheritance-content"/>.</p>
</div3>
<div3 id="feature-styling-inheritance-region">
<head>#styling-inheritance-region</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#styling-inheritance</code> feature if it recognizes and is
capable of transforming region style inheritance as defined by
<specref ref="semantics-style-inheritance-region"/>.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#styling-inheritance-region</code> feature if it implements
presentation semantic support for region style inheritance as defined by <specref
ref="semantics-style-inheritance-region"/>.</p>
</div3>
<div3 id="feature-styling-inline">
<head>#styling-inline</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#styling-inline</code> feature if it recognizes and is capable
of transforming inline style association as defined by <specref
ref="semantics-style-association-inline"/>.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#styling-inline</code> feature if it implements presentation semantic support
for inline style association as defined by <specref
ref="semantics-style-association-inline"/>.</p>
</div3>
<div3 id="feature-styling-nested">
<head>#styling-nested</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#styling-nested</code> feature if it recognizes and is capable
of transforming nested style association as defined by <specref
ref="semantics-style-association-nested"/>.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#styling-nested</code> feature if it implements presentation semantic support
for nested style association as defined by <specref
ref="semantics-style-association-nested"/>.</p>
</div3>
<div3 id="feature-styling-referential">
<head>#styling-referential</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#styling-referential</code> feature if it recognizes and is capable
of transforming referential style association as defined by <specref
ref="semantics-style-association-referential"/>.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#styling-referential</code> feature if it implements presentation semantic
support for referential style association as defined by <specref
ref="semantics-style-association-referential"/>.</p>
</div3>
<div3 id="feature-subFrameRate">
<head>#subFrameRate</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#subFrameRate</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-subFrameRate"><att>ttp:subFrameRate</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#subFrameRate</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-subFrameRate"><att>ttp:subFrameRate</att></loc>
@@ -10959,12 +10980,12 @@
</div3>
<div3 id="feature-textAlign">
<head>#textAlign</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#textAlign</code> feature if it recognizes and is capable
of transforming all defined values of the <loc
href="#style-attribute-textAlign"><att>tts:textAlign</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#textAlign</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-textAlign"><att>tts:textAlign</att></loc>
@@ -10972,13 +10993,13 @@
</div3>
<div3 id="feature-textAlign-absolute">
<head>#textAlign-absolute</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-textAlign"><att>tts:textAlign</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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 <loc
@@ -10987,13 +11008,13 @@
</div3>
<div3 id="feature-textAlign-relative">
<head>#textAlign-relative</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-textAlign"><att>tts:textAlign</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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 <loc
@@ -11002,12 +11023,12 @@
</div3>
<div3 id="feature-textDecoration">
<head>#textDecoration</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#textDecoration</code> feature if it recognizes and is capable
of transforming all defined values of the <loc
href="#style-attribute-textDecoration"><att>tts:textDecoration</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#textDecoration</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-textDecoration"><att>tts:textDecoration</att></loc>
@@ -11015,13 +11036,13 @@
</div3>
<div3 id="feature-textDecoration-over">
<head>#textDecoration-over</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-textDecoration"><att>tts:textDecoration</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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 <loc
@@ -11030,13 +11051,13 @@
</div3>
<div3 id="feature-textDecoration-through">
<head>#textDecoration-through</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-textDecoration"><att>tts:textDecoration</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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 <loc
@@ -11045,13 +11066,13 @@
</div3>
<div3 id="feature-textDecoration-under">
<head>#textDecoration-under</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-textDecoration"><att>tts:textDecoration</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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 <loc
@@ -11060,12 +11081,12 @@
</div3>
<div3 id="feature-textOrientation">
<head>#textOrientation</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#textOrientation</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-textOrientation"><att>tts:textOrientation</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#textOrientation</code> feature if it implements presentation semantic support
for the <loc
href="#style-attribute-textOrientation"><att>tts:textOrientation</att></loc>
@@ -11073,12 +11094,12 @@
</div3>
<div3 id="feature-textOutline">
<head>#textOutline</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#textOutline</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-textOutline"><att>tts:textOutline</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#textOutline</code> feature if it implements presentation semantic support
for the <loc
href="#style-attribute-textOutline"><att>tts:textOutline</att></loc>
@@ -11086,12 +11107,12 @@
</div3>
<div3 id="feature-textOutline-blurred">
<head>#textOutline-blurred</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#textOutline-blurred</code> feature if it recognizes and is capable of
transforming values of the <loc
href="#style-attribute-textOutline"><att>tts:textOutline</att></loc>
attribute that includes a blur radius specification.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#textOutline-blurred</code> feature if it implements presentation semantic support
for values of the <loc
href="#style-attribute-textOutline"><att>tts:textOutline</att></loc>
@@ -11099,12 +11120,12 @@
</div3>
<div3 id="feature-textOutline-unblurred">
<head>#textOutline-unblurred</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#textOutline-unblurred</code> feature if it recognizes and is capable of
transforming values of the <loc
href="#style-attribute-textOutline"><att>tts:textOutline</att></loc>
attribute that does not include a blur radius specification.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#textOutline-unblurred</code> feature if it implements presentation semantic support
for values of the <loc
href="#style-attribute-textOutline"><att>tts:textOutline</att></loc>
@@ -11112,12 +11133,12 @@
</div3>
<div3 id="feature-tickRate">
<head>#tickRate</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#tickRate</code> feature if it recognizes and is capable of
transforming the <loc
href="#parameter-attribute-tickRate"><att>ttp:tickRate</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#tickRate</code> feature if it implements presentation semantic support
for the <loc
href="#parameter-attribute-tickRate"><att>ttp:tickRate</att></loc>
@@ -11125,13 +11146,13 @@
</div3>
<div3 id="feature-timeBase-clock">
<head>#timeBase-clock</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#timeBase-clock</code> feature if it recognizes and is capable
of transforming the <code>clock</code> value of the <loc
href="#parameter-attribute-timeBase"><att>ttp:timeBase</att></loc>
attribute and if it supports the <loc
href="#feature-clockMode"><code>#clockMode</code></loc> feature.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#timeBase-clock</code> feature if it implements presentation
semantic support for the <code>clock</code> value of the <loc
href="#parameter-attribute-timeBase"><att>ttp:timeBase</att></loc>
@@ -11140,12 +11161,12 @@
</div3>
<div3 id="feature-timeBase-media">
<head>#timeBase-media</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#timeBase-media</code> feature if it recognizes and is capable
of transforming the <code>media</code> value of the <loc
href="#parameter-attribute-timeBase"><att>ttp:timeBase</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#timeBase-media</code> feature if it implements presentation
semantic support for the <code>media</code> value of the <loc
href="#parameter-attribute-timeBase"><att>ttp:timeBase</att></loc>
@@ -11153,13 +11174,13 @@
</div3>
<div3 id="feature-timeBase-smpte">
<head>#timeBase-smpte</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#timeBase-smpte</code> feature if it recognizes and is capable
of transforming the <code>smpte</code> value of the <loc
href="#parameter-attribute-timeBase"><att>ttp:timeBase</att></loc>
attribute and if it supports the <loc
href="#feature-dropMode"><code>#dropMode</code></loc> feature.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#timeBase-smpte</code> feature if it implements presentation
semantic support for the <code>smpte</code> value of the <loc
href="#parameter-attribute-timeBase"><att>ttp:timeBase</att></loc>
@@ -11168,12 +11189,12 @@
</div3>
<div3 id="feature-timeContainer">
<head>#timeContainer</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#timeContainer</code> feature if it recognizes and is capable of
transforming the <loc
href="#timing-attribute-timeContainer"><att>timeContainer</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#timeContainer</code> feature if it implements presentation semantic support
for the <loc
href="#timing-attribute-timeContainer"><att>timeContainer</att></loc>
@@ -11181,7 +11202,7 @@
</div3>
<div3 id="feature-time-clock">
<head>#time-clock</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#time-clock</code> feature if it recognizes and is capable of
transforming all values of the <loc
href="#timing-value-timeExpression"><timeExpression></loc> that
@@ -11190,13 +11211,13 @@
<timeExpression>
: hours ":" minutes ":" seconds ( fraction )?
</eg>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#time-clock</code> feature if it implements presentation
semantic support for the same syntax specified above.</p>
</div3>
<div3 id="feature-time-clock-with-frames">
<head>#time-clock-with-frames</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#time-clock-with-frames</code> feature if it supports the
<loc href="#feature-frameRate"><code>#frameRate</code></loc>,
<loc href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></loc>, and
@@ -11209,14 +11230,14 @@
<timeExpression>
: hours ":" minutes ":" seconds ( fraction | ":" frames ( "." sub-frames )? )?
</eg>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#time-clock-with-frames</code> feature if it implements
presentation semantic support for the same features and syntax
specified above.</p>
</div3>
<div3 id="feature-time-offset">
<head>#time-offset</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#time-offset</code> feature if it recognizes and is capable of
transforming all values of the <loc
href="#timing-value-timeExpression"><timeExpression></loc> that
@@ -11225,13 +11246,13 @@
<timeExpression>
: time-count fraction? ( "h" | "m" | "s" | "ms" )
</eg>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#time-offset</code> feature if it implements presentation
semantic support for the same syntax specified above.</p>
</div3>
<div3 id="feature-time-offset-with-frames">
<head>#time-offset-with-frames</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#time-offset-with-frames</code> feature if it supports the
<loc href="#feature-frameRate"><code>#frameRate</code></loc>,
<loc href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></loc>, and
@@ -11244,14 +11265,14 @@
<timeExpression>
: time-count fraction? "f"
</eg>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#time-offset-with-frames</code> feature if it implements
presentation semantic support for the same features and syntax
specified above.</p>
</div3>
<div3 id="feature-time-offset-with-ticks">
<head>#time-offset-with-ticks</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#time-offset-with-ticks</code> feature if it supports the
<loc href="#feature-tickRate"><code>#tickRate</code></loc> feature
and if it recognizes and is capable of
@@ -11262,13 +11283,13 @@
<timeExpression>
: time-count fraction? "t"
</eg>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#time-offset-with-ticks</code> feature if it implements presentation
semantic support for the same features and syntax specified above.</p>
</div3>
<div3 id="feature-timing">
<head>#timing</head>
-<p>A TTML transformation processor supports the <code>#timing</code>
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the <code>#timing</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <specref ref="timing"/>:</p>
<ulist>
@@ -11276,7 +11297,7 @@
<item><p><loc href="#timing-attribute-dur">@<att>dur</att></loc></p></item>
<item><p><loc href="#timing-attribute-end">@<att>end</att></loc></p></item>
</ulist>
-<p>A TTML presentation processor supports the <code>#timing</code>
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the <code>#timing</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p>
</div3>
@@ -11298,12 +11319,12 @@
</div3>
<div3 id="feature-unicodeBidi">
<head>#unicodeBidi</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#unicodeBidi</code> feature if it recognizes and is capable of
transforming all defined values of the <loc
href="#style-attribute-unicodeBidi"><att>tts:unicodeBidi</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#unicodeBidi</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-unicodeBidi"><att>tts:unicodeBidi</att></loc>
@@ -11311,12 +11332,12 @@
</div3>
<div3 id="feature-visibility">
<head>#visibility</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#visibility</code> feature if it recognizes and is capable
of transforming all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#visibility</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
@@ -11324,13 +11345,13 @@
</div3>
<div3 id="feature-visibility-block">
<head>#visibility-block</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#visibility-block</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
attribute when applied to a content element that would generate a
block area during presentation processing.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#visibility-block</code> feature if it implements presentation semantic
support for all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
@@ -11339,13 +11360,13 @@
</div3>
<div3 id="feature-visibility-inline">
<head>#visibility-inline</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#visibility-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
attribute when applied to a content element that would generate an
inline area during presentation processing.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#visibility-inline</code> feature if it implements presentation semantic
support for all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
@@ -11354,13 +11375,13 @@
</div3>
<div3 id="feature-visibility-region">
<head>#visibility-region</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#visibility-region</code> feature if it recognizes and is
capable of transforming all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
attribute when applied to a <loc
href="#layout-vocabulary-region"><el>region</el></loc> element.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#visibility-region</code> feature if it implements presentation semantic
support for all defined values of the <loc
href="#style-attribute-visibility"><att>tts:visibility</att></loc>
@@ -11369,12 +11390,12 @@
</div3>
<div3 id="feature-wrapOption">
<head>#wrapOption</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#wrapOption</code> feature if it recognizes and is capable
of transforming all defined values of the <loc
href="#style-attribute-wrapOption"><att>tts:wrapOption</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#wrapOption</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-wrapOption"><att>tts:wrapOption</att></loc>
@@ -11382,12 +11403,12 @@
</div3>
<div3 id="feature-writingMode">
<head>#writingMode</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#writingMode</code> feature if it recognizes and is capable
of transforming all defined values of the <loc
href="#style-attribute-writingMode"><att>tts:writingMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#writingMode</code> feature if it implements presentation semantic support
for all defined values of the <loc
href="#style-attribute-writingMode"><att>tts:writingMode</att></loc>
@@ -11395,13 +11416,13 @@
</div3>
<div3 id="feature-writingMode-vertical">
<head>#writingMode-vertical</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-writingMode"><att>tts:writingMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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 <loc
@@ -11410,13 +11431,13 @@
</div3>
<div3 id="feature-writingMode-horizontal">
<head>#writingMode-horizontal</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-writingMode"><att>tts:writingMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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 <loc
@@ -11425,13 +11446,13 @@
</div3>
<div3 id="feature-writingMode-horizontal-lr">
<head>#writingMode-horizontal-lr</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-writingMode"><att>tts:writingMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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
<loc
@@ -11440,13 +11461,13 @@
</div3>
<div3 id="feature-writingMode-horizontal-rl">
<head>#writingMode-horizontal-rl</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> 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 <loc
href="#style-attribute-writingMode"><att>tts:writingMode</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> 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
<loc
@@ -11455,12 +11476,12 @@
</div3>
<div3 id="feature-zIndex">
<head>#zIndex</head>
-<p>A TTML transformation processor supports the
+<p>A TTML <loc href="#terms-transformation-processor">transformation processor</loc> supports the
<code>#zIndex</code> feature if it recognizes and is capable of
transforming the <loc
href="#style-attribute-zIndex"><att>tts:zIndex</att></loc>
attribute.</p>
-<p>A TTML presentation processor supports the
+<p>A TTML <loc href="#terms-presentation-processor">presentation processor</loc> supports the
<code>#zIndex</code> feature if it implements presentation semantic support for
the <loc
href="#style-attribute-zIndex"><att>tts:zIndex</att></loc>
@@ -11473,7 +11494,7 @@
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>
+is optional (O), for transformation and <loc href="#terms-presentation-processor">presentation processor</loc>s.</p>
<table id="feature-support-table" role="common">
<caption>Table D-1 – Feature Support</caption>
<col width="60%"/>
@@ -12069,9 +12090,9 @@
</table>
<p>For the sake of convenience, the following table,
<specref ref="feature-transformation-mandatory-table"/>, enumerates all
-mandatory features for a TTML Transformation Processor, providing additional
+mandatory features for a TTML <loc href="#terms-transformation-processor">transformation processor</loc>, providing additional
comments to summarize the context of usage or the nature of the feature.
-The <emph>Profile Definition Document</emph> that defines the corresponding
+The <loc href="#terms-profile-definition-document">profile definition document</loc> that defines the corresponding
DFXP Transformation Profile is specified in
<specref ref="profile-dfxp-transformation"/>.
</p>
@@ -12134,9 +12155,9 @@
</table>
<p>For the sake of convenience, the following table,
<specref ref="feature-presentation-mandatory-table"/>, enumerates all
-mandatory features for a TTML Presentation Processor, providing additional
+mandatory features for a TTML <loc href="#terms-presentation-processor">presentation processor</loc>, providing additional
comments to summarize the context of usage or the nature of the feature.
-The <emph>Profile Definition Document</emph> that defines the corresponding
+The <loc href="#terms-profile-definition-document">profile definition document</loc> that defines the corresponding
DFXP Presentation Profile is specified in
<specref ref="profile-dfxp-presentation"/>.
</p>
@@ -12245,7 +12266,7 @@
</ulist>
<p>The SDP US profile is defined in
<xspecref href="http://www.w3.org/TR/ttml10-sdp-us/">TTML Simple Delivery Profile for Closed Captions (US)</xspecref>.</p>
-<p>Each TTML profile is defined in terms of a <emph>Profile Definition Document</emph>,
+<p>Each TTML profile is defined in terms of a <loc href="#terms-profile-definition-document">profile definition document</loc>,
which is expressed as an XML document wherein the root element adheres to
<specref ref="parameter-vocabulary-profile"/>.</p>
<div2 id="profile-dfxp-transformation">
@@ -13215,7 +13236,7 @@
</item>
<item>
<p>The <att>style</att> attribute is supported only on
-<loc href="#element-vocab-type-content">Content</loc> elements.</p>
+<loc href="#terms-content-element">content element</loc>.</p>
</item>
<item>
<p>Derived from the use of <code>@requiredExtensions</code>
@@ -13382,7 +13403,7 @@
<td><loc href="#parameter-attribute-profile"><code>ttp:profile</code></loc></td>
<td><emph>none</emph></td>
<td></td>
-<td>expresses profile of TTML used by a <emph>Document Instance</emph></td>
+<td>expresses profile of TTML used by a <loc href="#terms-document-instance">document instance</loc></td>
<td></td>
</tr>
<tr>
@@ -14089,10 +14110,10 @@
</item>
</ulist>
<p>One possible means by which TTML Content may be streamed is to
-partition a <emph>Document Instance</emph>'s information set into
+partition a <loc href="#terms-document-instance">document instance</loc>'s information set into
non-overlapping fragments, where one particular fragment, call it the
<emph>root fragment</emph>, represents the front matter (head) of the
-<emph>Document Instance</emph> as well as its top level structural elements, and
+<loc href="#terms-document-instance">document instance</loc> 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
@@ -14102,7 +14123,7 @@
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 <emph>Document Instance</emph> is
+<p>An example of such a fragmentation of a <loc href="#terms-document-instance">document instance</loc> is
shown in <specref ref="fragment-streaming-graphic"/>.</p>
<table id="fragment-streaming-graphic" role="example-images">
<caption>Figure 3 – Fragment Streaming</caption>
@@ -14121,7 +14142,7 @@
<div1 id="concrete-encoding">
<head>Concrete Encoding</head>
<p><emph>This appendix is normative.</emph></p>
-<p>In the absence of other requirements, a <emph>Document Instance</emph> should be concretely encoded as a
+<p>In the absence of other requirements, a <loc href="#terms-document-instance">document instance</loc> should be concretely encoded as a
well-formed XML 1.0 <bibref ref="xml10"/> document using the UTF-8 character encoding.</p>
<note role="elaboration">
<p>When using XML 1.0 <bibref ref="xml10"/> as the concrete encoding of TTML, only the following named character entities are defined:
@@ -14131,7 +14152,7 @@
<div1 id="time-expression-semantics">
<head>Time Expression Semantics</head>
<p><emph>This appendix is normative.</emph></p>
-<p>This appendix specifies the semantics for interpreting time expressions in <emph>Document Instances</emph>.</p>
+<p>This appendix specifies the semantics for interpreting time expressions in <loc href="#terms-document-instance">document instances</loc>.</p>
<note role="clarification">
<p>The phrase <emph>local real time</emph> as used below is intended to model a virtual real time clock in the document processing context, where
<emph>local</emph> means in the immediate proximity of the implementation of this processing context. The intent
@@ -14140,7 +14161,7 @@
<note role="clarification">
<p>The phrase <emph>play rate</emph> 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 <emph>Related Media Object</emph>. Without loss of generality, the following discussion assumes a fixed play(back) rate. In the case of
+playback of a <loc href="#terms-related-media-object">related media object</loc>. 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>
</note>
<div2 id="time-expression-semantics-clock">
@@ -14193,8 +14214,8 @@
</sitem>
<sitem/>
<sitem>
-and <code>epochOffset</code> and <code>discontinuityOffset</code> are determined once and only once prior to the beginning of the <emph>Root Temporal Extent</emph> such that
-during the period between value determination and the beginning of the <emph>Root Temporal Extent</emph> 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 <loc href="#terms-root-temporal-extent">root temporal extent</loc> such that
+during the period between value determination and the beginning of the <loc href="#terms-root-temporal-extent">root temporal extent</loc> there occurs no local midnight or reference clock base discontinuity.
</sitem>
<sitem/>
</slist>
@@ -14286,7 +14307,7 @@
</sitem>
<sitem/>
<sitem>
-where <code>M ∈ ℜ</code>, <code>0 ≤ M < ∞</code>, <code>M</code> in seconds, with 0 corresponding to the beginning of the <emph>Root Temporal Extent</emph>;
+where <code>M ∈ ℜ</code>, <code>0 ≤ M < ∞</code>, <code>M</code> in seconds, with 0 corresponding to the beginning of the <loc href="#terms-root-temporal-extent">root temporal extent</loc>;
</sitem>
<sitem/>
<sitem>
@@ -14297,7 +14318,7 @@
<sitem>
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
-<emph>Root Temporal Extent</emph> and the local real time at the the beginning of epoch <code>E</code>, expressed in seconds.
+<loc href="#terms-root-temporal-extent">root temporal extent</loc> and the local real time at the the beginning of epoch <code>E</code>, expressed in seconds.
</sitem>
</slist>
</td>
@@ -14329,7 +14350,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 <emph>Root Temporal Extent</emph>; otherwise, if sequential and a prior sibling
+zero (0) if this time container is the <loc href="#terms-root-temporal-extent">root temporal extent</loc>; 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;
</sitem>
@@ -14380,7 +14401,7 @@
<p>If the computed <code>frameRateMultipler</code> ratio is not integral, then <code>effectiveFrameRate</code> will be a non-integral rational.</p>
</note>
<note role="clarification">
-<p>The above formalisms assumes that the <emph>Root Temporal Extent</emph> corresponds with the beginning of a related media object. If
+<p>The above formalisms assumes that the <loc href="#terms-root-temporal-extent">root temporal extent</loc> 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>
</note>
</div2>
@@ -14390,10 +14411,11 @@
as defined by <loc href="#timing-value-timeExpression"><timeExpression></loc>, and their relationship to media time and local real time.</p>
<p>If the computed value of the <att>ttp:markerMode</att> parameter is <code>discontinuous</code>, then there is no direct relationship between
time expressions and media time <phrase role="strong"><code>M</code></phrase> or local real time <phrase role="strong"><code>R</code></phrase>. In
-this case, time expressions refer to synchronization events (markers) emitted by the <emph>Document Processing Context</emph> when <emph>SMPTE Time
-Codes</emph> are encountered in the <emph>Related Media Object</emph>.</p>
+this case, time expressions refer to synchronization events (markers) emitted by the <loc href="#terms-document-processing-context">document processing context</loc>
+when <loc href="#terms-smpte-time-code">smpte time codes</loc>
+are encountered in the <loc href="#terms-related-media-object">related media object</loc>.</p>
<p>Otherwise, if the computed value of the <att>ttp:markerMode</att> 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 <emph>Synthetic SMPTE Document Syncbase</emph>, here referred to as the
+local real time and media time are as described below in terms of a <loc href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</loc>, here referred to as the
SMPTE time base <phrase role="strong"><code>S</code></phrase>.</p>
<table id="time-expressions-and-smpte-time" role="semantics">
<caption>TTML Semantics – Time Expressions and SMPTE Time Relationship</caption>
@@ -14482,7 +14504,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 <emph>Root Temporal Extent</emph>; otherwise, if sequential and a prior sibling
+zero (0) if this time container is the <loc href="#terms-root-temporal-extent">root temporal extent</loc>; 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;
</sitem>
@@ -14525,7 +14547,7 @@
<div2 id="roll-up-example">
<head>Roll-Up Caption Example</head>
<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 <loc href="#terms-presentation-processor">presentation processor</loc> supports
<loc href="#semantics-smooth-scrolling-recommendation">smooth scrolling between adjacent synchronic intermediate document instances</loc>, the transitions, i.e., moving an
old paragraph (line) out and a new paragraph (line) in, will be either smooth or discrete.</p>
<table id="roll-up-example-1-s" role="example">