[ttml10se] further clarifications, editorial fixes; remove duplication name/id attrs in generated html; add XSD validation target; fix textDecoration schema data type
authorGlenn Adams <glenn@skynav.com>
Mon, 13 May 2013 11:31:28 -0600
changeset 386 fc0adc7a8384
parent 385 8e405352e8ea
child 387 ff85d1234ecb
[ttml10se] further clarifications, editorial fixes; remove duplication name/id attrs in generated html; add XSD validation target; fix textDecoration schema data type
ttml10/spec/build.xml
ttml10/spec/rnc/schema.zip
ttml10/spec/rnc/ttaf1-dfxp-datatypes.rnc
ttml10/spec/statusper.xml
ttml10/spec/ttaf1-dfxp.html
ttml10/spec/ttaf1-dfxp.xml
ttml10/spec/ttml-changes.html
ttml10/spec/xmlspec.xsl
ttml10/spec/xsd/schema.zip
ttml10/spec/xsd/ttaf1-dfxp-bindings.xjb
ttml10/spec/xsd/ttaf1-dfxp-datatypes.xsd
--- a/ttml10/spec/build.xml	Thu May 09 23:43:07 2013 -0600
+++ b/ttml10/spec/build.xml	Mon May 13 11:31:28 2013 -0600
@@ -9,13 +9,15 @@
     <property name="htmlOutputDir" value="./"/>
     <property name="stylesheet" value="xmlspec-ttaf1-dfxp.xsl"/>
     <property name="glossary" value="extract-glist.xsl"/>
-	<property name="generateBPlist" value="generateBPlist.xsl"/>
+    <property name="generateBPlist" value="generateBPlist.xsl"/>
     <property name="diffformat" value="diffspec.xsl"/>
     <property name="last-public-draft" value="20070706"/>
     
     <property name="jing.jar" value="${basedir}/jing/jing.jar"/>
     <property name="rnc.dir" value="${basedir}/rnc"/>
     <property name="rnc.schema" value="${rnc.dir}/ttaf1-dfxp.rnc"/>
+    <property name="xsd.dir" value="${basedir}/xsd"/>
+    <property name="xsd.schema" value="${xsd.dir}/ttaf1-dfxp.xsd"/>
     <property name="profiles.dir" value="${basedir}/profiles"/>
 
     <patternset id="escapable">
@@ -47,6 +49,43 @@
         </java>
     </target>
 
+    <target name="generate-schema-archive-rnc" description="Generate DFXP's RNC Schema archive." depends="validate-schema-rnc">
+        <zip destfile="${rnc.dir}/schema.zip">
+            <fileset dir="${rnc.dir}">
+                <include name="*.rnc"/>
+            </fileset>
+        </zip>
+    </target>
+
+    <target name="create-xsd-bindings" description="Create JAXB Bindings for DFXP's XSD Schema.">
+        <exec executable="xjc" dir="xsd">
+          <arg value="-quiet"/>
+          <arg value="-b"/>
+          <arg value="ttaf1-dfxp-bindings.xjb"/>
+          <arg value="ttaf1-dfxp.xsd"/>
+        </exec>
+    </target>
+
+    <target name="delete-xsd-bindings" description="Delete JAXB Bindings for DFXP's XSD Schema.">
+        <delete includeemptydirs="true">
+          <fileset dir="xsd/org"/>
+        </delete>
+    </target>
+
+    <target name="validate-schema-xsd" description="Validates DFXP's XSD Schema using JAXB tool set." depends="create-xsd-bindings, delete-xsd-bindings"/>
+
+    <target name="generate-schema-archive-xsd" description="Generate DFXP's XSD Schema archive." depends="validate-schema-xsd">
+        <zip destfile="${xsd.dir}/schema.zip">
+            <fileset dir="${xsd.dir}">
+                <include name="*.xsd"/>
+            </fileset>
+        </zip>
+    </target>
+
+    <target name="validate-schemas" description="Validate DFXP schemas" depends="validate-schema-rnc, validate-schema-xsd"/>
+
+    <target name="generate-schema-archives" description="Generate DFXP schema archives" depends="generate-schema-archive-rnc, generate-schema-archive-xsd"/>
+
     <target name="validate-profile-transformation" description="Validates transformation profile.">
         <java fork="true" jar="${jing.jar}">
             <arg value="-c"/>
@@ -153,7 +192,7 @@
         <pathelement location="${basedir}/DiffMk.properties"/>
     </path>
     <target name="generateXMLdiff">
-  <java classname="com.sun.xtc.diffmk.DiffMk" fork="true">
+        <java classname="com.sun.xtc.diffmk.DiffMk" fork="true">
             <arg value="-doctype"/>
             <arg value="xmlspec"/>
             <arg value="-diff"/>
@@ -174,7 +213,6 @@
             <arg value="diffspec.xsl"/>
         </java>
     </target>
-
     <target name="postprocess-diff">
       <java fork="true" classname="net.sf.saxon.Transform">
             <classpath refid="saxon8.classpath"/>
@@ -196,12 +234,12 @@
     </target>
 
     <target name="generate" description="Generate the specification without updating changelog and acknowledgments sections"
-	    depends="validate-tt-specs,html">
+	    depends="generate-schema-archives,validate-tt-specs,html">
       <echo>WARNING: changelog.xml and acknowledgments.xml MAY be out of date. Use "main" target if necessary.</echo>
     </target>
     
     <target name="sg" description="Shortened generation of the specification without updating changelog and acknowledgments sections, but without rebuilding escapes."
-	    depends="validate-tt-specs-dont-build-escapes,html">
+	    depends="generate-schema-archives,validate-tt-specs-dont-build-escapes,html">
       <echo>WARNING: changelog.xml and acknowledgments.xml MAY be out of date. Use "main" target if necessary.</echo>
     </target>
 
Binary file ttml10/spec/rnc/schema.zip has changed
--- a/ttml10/spec/rnc/ttaf1-dfxp-datatypes.rnc	Thu May 09 23:43:07 2013 -0600
+++ b/ttml10/spec/rnc/ttaf1-dfxp-datatypes.rnc	Mon May 13 11:31:28 2013 -0600
@@ -121,7 +121,7 @@
   "transcription"
 
 TTAF.Opacity.datatype =
-  string
+  TTAF.Alpha.datatype
 
 TTAF.Origin.datatype =
   string
@@ -157,13 +157,7 @@
   "end"
 
 TTAF.TextDecoration.datatype =
-  "none" |
-  "underline" |
-  "noUnderline" |
-  "overline" |
-  "noOverline" |
-  "lineThrough" |
-  "noLineThrough"
+  string
 
 TTAF.TextOutline.datatype =
   string
--- a/ttml10/spec/statusper.xml	Thu May 09 23:43:07 2013 -0600
+++ b/ttml10/spec/statusper.xml	Mon May 13 11:31:28 2013 -0600
@@ -42,15 +42,15 @@
 <p>Please report errors in and submit comments on this document to the
 W3C Timed Text public comments mailing list,
 <loc href="mailto:public-tt-comments@w3.org">public-tt-comments@w3.org</loc>.
-It will be very helpful if you include the string "[TTML10SE]" in the
+Please include the string <code>[ttml10se]</code> at the beginning of the
 subject line of your report. Each email message should contain only one
 error report. Archives of the comments and responses are available at
 <loc href="http://lists.w3.org/Archives/Public/public-tt-comments/">http://lists.w3.org/Archives/Public/public-tt-comments/</loc>.</p>
 
-<p>An updated implementation report will be made available at
-<loc href="http://www.w3.org/2009/05/dfxp-results.html">implementation report</loc>,
-but the decision of the Director to transition this document to Proposed Edited
-Recommendation did not depend on the existence of that report.</p>
+<p>An updated <loc href="http://www.w3.org/2009/05/dfxp-results.html">implementation
+report</loc>  will be made available, but the decision of the Director to transition
+this document to Proposed Edited Recommendation did not depend on the existence of that
+report.</p>
 
 <p>The Timed Text Working Group plans to submit this specification for
 consideration as a W3C Recommendation (Second Edition) as soon as the Working
--- a/ttml10/spec/ttaf1-dfxp.html	Thu May 09 23:43:07 2013 -0600
+++ b/ttml10/spec/ttaf1-dfxp.html	Mon May 13 11:31:28 2013 -0600
@@ -80,15 +80,15 @@
 .strong { font-weight: bold }
 .reqattr { font-weight: bold }
 .optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/05/10 04:54:33 $<div id="revisions"></div><div class="head">
-<h1><a name="title" id="title"></a>Timed Text Markup Language (TTML) 1.0 (Second Edition)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date: 2013/05/10 04:54:33 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date$<div id="revisions"></div><div class="head">
+<h1><a id="title"></a>Timed Text Markup Language (TTML) 1.0 (Second Edition)</h1>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
 <a href="ttaf1-dfxp.html">ttaf1-dfxp.html</a>
 </dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
 <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
 </dd><dt>Editor:</dt><dd>Glenn Adams, Cox Communications, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p>Please refer to the <a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttml-issues.html">errata</a> for this document, which may
       include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ttaf1-dfxp"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
-<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>This document specifies the Timed Text Markup Language (TTML) in terms of a
+<h2><a id="abstract"></a>Abstract</h2><p>This document specifies the Timed Text Markup Language (TTML) in terms of a
 vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
 timed text media for the purpose of interchange among authoring
 systems. Timed text is textual information that is intrinsically or
@@ -96,13 +96,13 @@
 for the purpose of transcoding or exchanging timed text information
 among legacy distribution content formats presently in use for
 subtitling and captioning functions.</p><p>In addition to being used for interchange among legacy distribution content
-formats, TTML content may be used directly as a distribution format,
+formats, TTML Content may be used directly as a distribution format,
 for example, providing a standard content format to reference from a <code>&lt;track&gt;</code>
 element in an HTML5 document, or a <code>&lt;text&gt;</code> or 
-<code>&lt;textstream&gt;</code> media object element in a <a href="#smil21">[SMIL 2.1]</a> document.</p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editor's copy that has
+<code>&lt;textstream&gt;</code> media element in a <a href="#smil21">[SMIL 2.1]</a> document.</p></div><div>
+<h2><a id="status"></a>Status of this Document</h2><p><strong>This document is an editor's copy that has
         no official standing.</strong></p><p></p></div><div class="toc">
-<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br>
+<h2><a id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#model">System Model</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#example">Document Example</a><br>
 2 <a href="#definitions">Definitions</a><br>
@@ -117,7 +117,7 @@
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.3 <a href="#conformance-presentation-processor">Presentation Processor Conformance</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#claims">Claims</a><br>
 4 <a href="#doctypes">Document Types</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#dfxp-content-doctype">DFXP Content</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#ttml-content-doctype">TTML Content</a><br>
 5 <a href="#vocabulary">Vocabulary</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#vocabulary-namespaces">Namespaces</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#vocabulary-profiles">Profiles</a><br>
@@ -256,14 +256,14 @@
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;12.2.1 <a href="#metadata-attribute-agent">ttm:agent</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;12.2.2 <a href="#metadata-attribute-role">ttm:role</a><br>
 </p>
-<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#reduced-infoset">Reduced XML Infoset</a><br>
+<h3><a id="appendices"></a>Appendices</h3><p class="toc">A <a href="#reduced-infoset">Reduced XML Infoset</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#reduced-infoset-document">Document Information Item</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;A.2 <a href="#reduced-infoset-element">Element Information Item</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;A.3 <a href="#reduced-infoset-attribute">Attribute Information Item</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;A.4 <a href="#reduced-infoset-character">Character Information Item</a><br>
 B <a href="#schemas">Schemas</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#dfxp-schema-rnc">Relax NG Schema</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#dfxp-schema-xsd">XML Schema Definition (XSD) Schema</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#ttml-schema-rnc">Relax NG Compact (RNC) Schema</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#ttml-schema-xsd">XML Schema Definition (XSD) Schema</a><br>
 C <a href="#media-types-registration">Media Type Registration</a><br>
 D <a href="#features">Features</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;D.1 <a href="#feature-designations">Feature Designations</a><br>
@@ -392,11 +392,11 @@
 H <a href="#other-references">Other References</a> (Non-Normative)<br>
 I <a href="#requirements">Requirements</a> (Non-Normative)<br>
 J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e17572">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e18051">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e18212">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e18691">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e18919">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e19083">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e19561">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e19725">Guidelines</a><br>
 L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
 M <a href="#concrete-encoding">Concrete Encoding</a> (Non-Normative)<br>
 N <a href="#time-expression-semantics">Time Expression Semantics</a> (Non-Normative)<br>
@@ -409,35 +409,39 @@
 &nbsp;&nbsp;&nbsp;&nbsp;O.3 <a href="#paint-on-example">Paint-On Caption Example</a><br>
 P <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br>
 </p></div><hr><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"></a>1 Introduction</h2><p><em>Unless specified otherwise, this section and its sub-sections are non-normative.</em></p><p>The Timed Text Markup Language (TTML) 1.0
+<h2><a id="intro"></a>1 Introduction</h2><p><em>Unless specified otherwise, this section and its sub-sections are non-normative.</em></p><p>The Timed Text Markup Language (TTML) 1.0
 provides a standardized representation of a particular subset of
 textual information with which stylistic, layout, and timing semantics are associated by
-an author or an authoring system for the purpose of interchange and potential presentation.</p><p>TTML is expressly designed to meet only a limited set of requirements
+an author or an authoring system for the purpose of interchange and processing.</p><p>TTML is expressly designed to meet only a limited set of requirements
 established by <a href="#ttaf1-req">[TTAF1-REQ]</a>, and summarized in <a href="#requirements"><b>I Requirements</b></a>. In particular, only those requirements which service the
 need of performing interchange with existing, legacy distribution systems are
 satisfied.</p><p>In addition to being used for interchange among legacy distribution content
-formats, TTML content may be used directly as a distribution format, providing, for
+formats, TTML Content may be used directly as a distribution format (as implied by
+the acronym DFXP), providing, for
 example, a standard content format to reference from a <code>&lt;track&gt;</code>
 element in an HTML5 document, or a <code>&lt;text&gt;</code> or 
 <code>&lt;textstream&gt;</code> media element in a <a href="#smil21">[SMIL 2.1]</a> document. Certain properties of TTML support
-streamability of content, as described in <a href="#streaming"><b>L Streaming TTML Content</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While TTML was not expressly designed for direct (embedded) integration into a
-SMIL document instance, such integration is not precluded.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In some contexts of use, it may be appropriate to employ
+streamability of content, as described in <a href="#streaming"><b>L Streaming TTML Content</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While TTML was not expressly designed for direct (embedded) integration into an
+HTML or a SMIL document instance, such integration is not precluded.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In some contexts of use, it may be appropriate to employ
 animated content to depict sign language representations of the same content
-as expressed by a Timed Text document instance. This use case is not
+as expressed by a Timed Text <em>Document Instance</em>. This use case is not
 explicitly addressed by TTML mechanisms, but may be addressed by some
-external multimedia integration technology, such as SMIL.</p></div><div class="div2">
-<h3><a name="model" id="model"></a>1.1 System Model</h3><p>Use of TTML is intended to function in a wider context of Timed Text
-Authoring and Distribution mechanisms that are based upon a system
-model, depicted in <a href="#model-graphic"><b>Figure 1 – System Model</b></a>, wherein the Timed Text Markup Language
+external multimedia integration technology, such as SMIL.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In previous drafts of this specification, TTML was referred to as DFXP (Distribution
+Format Exchange Profile). This latter term is retained for historical reasons in
+certain contexts, such as profile names and designators, and the short name
+<code>ttaf1-dfxp</code> used in URLs to refer to this specification.</p></div><div class="div2">
+<h3><a id="model"></a>1.1 System Model</h3><p>Use of TTML is intended to function in a wider context of Timed Text
+Authoring and Distribution mechanisms that are based upon the system
+model depicted in <a href="#model-graphic"><b>Figure 1 – System Model</b></a>, wherein the Timed Text Markup Language
 serves as a bidirectional interchange format among a heterogeneous collection of
 authoring systems, and as a unidirectional interchange format to a
 heterogeneous collection of distribution formats after undergoing transcoding
 or compilation to the target distribution formats as required, and where one
-particular distribution format is TTML.</p><a name="model-graphic" id="model-graphic"></a><table class="example-images"><caption>Figure 1 – System Model</caption><tbody><tr><td><img src="images/model.png" alt="System Model"></td></tr></tbody></table></div><div class="div2">
-<h3><a name="example" id="example"></a>1.2 Document Example</h3><p>A TTML document instance consists of a <code>tt</code> document element that contains
+particular distribution format is TTML (labeled as "DFXP" in the figure).</p><a id="model-graphic"></a><table class="example-images"><caption>Figure 1 – System Model</caption><tbody><tr><td><img src="images/model.png" alt="System Model"></td></tr></tbody></table></div><div class="div2">
+<h3><a id="example"></a>1.2 Document Example</h3><p>A TTML <em>Document Instance</em> consists of a <code>tt</code> document element that contains
 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 timing information.</p><a name="dfxp-example-document-structure" id="dfxp-example-document-structure"></a><table class="example"><caption>Example Fragment – TTML Document Structure</caption><tbody><tr><td>
+with references to style and layout information and inline styling and timing information.</p><a id="ttml-example-document-structure"></a><table class="example"><caption>Example Fragment – TTML Document Structure</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"&gt;
   &lt;head&gt;
@@ -450,7 +454,7 @@
 </pre></div>
 </td></tr></tbody></table><p>Document level metadata may specify a document title, description,
 and copyright information. In addition, arbitrary metadata drawn from
-other namespaces may be specified.</p><a name="dfxp-example-metadata" id="dfxp-example-metadata"></a><table class="example"><caption>Example Fragment – TTML Metadata</caption><tbody><tr><td>
+other namespaces may be specified.</p><a id="ttml-example-metadata"></a><table class="example"><caption>Example Fragment – TTML Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;metadata xmlns:ttm="http://www.w3.org/ns/ttml#metadata"&gt;
   &lt;ttm:title&gt;Timed Text TTML Example&lt;/ttm:title&gt;
@@ -458,8 +462,9 @@
 &lt;/metadata&gt;
 </pre></div>
 </td></tr></tbody></table><p>Styling information may be specified in the form of style specification
-definitions that are referenced by layout and content information.</p><p>In <a href="#dfxp-example-styling"><b>Example Fragment – TTML Styling</b></a>, four style sets of specifications
-are defined, with one set serving as a collection of default styles.</p><a name="dfxp-example-styling" id="dfxp-example-styling"></a><table class="example"><caption>Example Fragment – TTML Styling</caption><tbody><tr><td>
+definitions that are referenced by layout and content information,
+specified inline with content information, or both.</p><p>In <a href="#ttml-example-styling"><b>Example Fragment – TTML Styling</b></a>, four style sets of specifications
+are defined, with one set serving as a collection of default styles.</p><a id="ttml-example-styling"></a><table class="example"><caption>Example Fragment – TTML Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;styling xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
   &lt;!-- s1 specifies default color, font, and text alignment --&gt;
@@ -481,11 +486,12 @@
 is intended to be presented. A region definition may reference one or
 more sets of style specifications in order to permit content flowed in the
 region to inherit from these styles.
-In <a href="#dfxp-example-layout"><b>Example Fragment – TTML Layout</b></a>, the region definition makes
-reference to style specification <code>s1</code> which allows all content
-flowed into the region to inherit from the region's styles (in the case
+In <a href="#ttml-example-layout"><b>Example Fragment – TTML Layout</b></a>, the region definition makes
+reference to style specification <code>s1</code> augmented by specific inline
+styles which, together, allow content flowed into the region to inherit
+from the region's styles (in the case
 that a style is not already explicitly specified on content or inherited
-via the content hierarchy.)</p><a name="dfxp-example-layout" id="dfxp-example-layout"></a><table class="example"><caption>Example Fragment – TTML Layout</caption><tbody><tr><td>
+via the content hierarchy.)</p><a id="ttml-example-layout"></a><table class="example"><caption>Example Fragment – TTML Layout</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;layout xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
   &lt;region xml:id="subtitleArea"
@@ -497,16 +503,16 @@
   /&gt;
 &lt;/layout&gt;  
 </pre></div>
-</td></tr></tbody></table><p>The content of a TTML document instance is expressed in its
+</td></tr></tbody></table><p>The content of a <em>Document Instance</em> is expressed in its
 body, which is organized in terms of block and inline text elements.
 The hierarchical organization of content elements serves a primary role in
 determining both spatial and temporal relationships. For example, in
-<a href="#dfxp-example-body"><b>Example Fragment – TTML Body</b></a>, each paragraph (<code>p</code> element)
+<a href="#ttml-example-body"><b>Example Fragment – TTML Body</b></a>, each paragraph (<code>p</code> element)
 is flowed into its target region in the specified lexical order; furthermore,
 the active time interval of each paragraph is timed in accordance to its
 parent or sibling according to the applicable time containment semantics —
-in this case, the division parent is interpreted as a parallel time
-container.</p><a name="dfxp-example-body" id="dfxp-example-body"></a><table class="example"><caption>Example Fragment – TTML Body</caption><tbody><tr><td>
+in this case, the division parent is interpreted (by default) as a parallel time
+container.</p><a id="ttml-example-body"></a><table class="example"><caption>Example Fragment – TTML Body</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;body region="subtitleArea"&gt;
   &lt;div&gt;
@@ -551,14 +557,14 @@
   &lt;/div&gt;    
 &lt;/body&gt;
 </pre></div>
-</td></tr></tbody></table><p>The first subtitle <a href="#dfxp-example-subtitle-1"><b>Subtitle 1 – Time Interval [0.76, 3.45)</b></a> is
+</td></tr></tbody></table><p>The first subtitle <a href="#ttml-example-subtitle-1"><b>Subtitle 1 – Time Interval [0.76, 3.45)</b></a> is
 presented during the time interval 0.76 to 3.45 seconds.
 This
 subtitle inherits its font family, font size,
 foreground color, and text alignment from the region into which it is
 presented. Since no region is explicitly specified on the paragraph,
 the nearest ancestor that specifies a region determines the
-region. Note also that content is presented
+targeted region. Note also that content is presented
 at the bottom (after edge) of the containing region due to the <code>tts:displayAlign="after"</code>
 being specified on the region definition.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The notation "[<em>X</em>,<em>Y</em>]" denotes a closed
 interval from <em>X</em> to <em>Y</em>, including
@@ -572,43 +578,46 @@
 "(<em>X</em>,<em>Y</em>)" denotes an open
 interval from <em>X</em> to <em>Y</em>, not including
 <em>X</em> or <em>Y</em>.
-</p></div><a name="dfxp-example-subtitle-1" id="dfxp-example-subtitle-1"></a><table class="example-images"><caption>Subtitle 1 – Time Interval [0.76, 3.45)</caption><tbody><tr><td><img src="images/subtitle1.png" alt="Subtitle 1"></td></tr></tbody></table><p>The second subtitle continues with the default style, except that it contains
-two lines of text with an intervening author-specified line break. Note the effects of
+</p></div><a id="ttml-example-subtitle-1"></a><table class="example-images"><caption>Subtitle 1 – Time Interval [0.76, 3.45)</caption><tbody><tr><td><img src="images/subtitle1.png" alt="Subtitle 1"></td></tr></tbody></table><p>The second subtitle continues with the default style, except that it contains
+two lines of text with an intervening author-specified line break. Note the affect of
 the use of <code>tts:textAlign="center"</code> to specify the paragraph's alignment
-in the inline progression direction.</p><a name="dfxp-example-subtitle-2" id="dfxp-example-subtitle-2"></a><table class="example-images"><caption>Subtitle 2 – Time Interval [5.0, 10.0)</caption><tbody><tr><td><img src="images/subtitle2.png" alt="Subtitle 2"></td></tr></tbody></table><p>The third subtitle continues, using a variant style which overrides the default style's
-foreground color with a different color.</p><a name="dfxp-example-subtitle-3" id="dfxp-example-subtitle-3"></a><table class="example-images"><caption>Subtitle 3 – Time Interval [10.0, 16.0)</caption><tbody><tr><td><img src="images/subtitle3.png" alt="Subtitle 3"></td></tr></tbody></table><p>The fourth subtitle reverts to the default style.</p><a name="dfxp-example-subtitle-4" id="dfxp-example-subtitle-4"></a><table class="example-images"><caption>Subtitle 4 – Time Interval [17.2, 23.0)</caption><tbody><tr><td><img src="images/subtitle4.png" alt="Subtitle 4"></td></tr></tbody></table><p>The fifth subtitle continues, again using a variant style which
-overrides the default style's foreground color with a different color.</p><a name="dfxp-example-subtitle-5" id="dfxp-example-subtitle-5"></a><table class="example-images"><caption>Subtitle 5 – Time Interval [23.0, 27.0)</caption><tbody><tr><td><img src="images/subtitle5.png" alt="Subtitle 5"></td></tr></tbody></table><p>During the next active time interval, two distinct subtitles are simultaneously active, with
-the paragraph expressing each subtitle using a different style that overrides color and paragraph
+in the inline progression direction.</p><a id="ttml-example-subtitle-2"></a><table class="example-images"><caption>Subtitle 2 – Time Interval [5.0, 10.0)</caption><tbody><tr><td><img src="images/subtitle2.png" alt="Subtitle 2"></td></tr></tbody></table><p>The third subtitle continues, using a variant style which overrides the default style's
+foreground color with a different color.</p><a id="ttml-example-subtitle-3"></a><table class="example-images"><caption>Subtitle 3 – Time Interval [10.0, 16.0)</caption><tbody><tr><td><img src="images/subtitle3.png" alt="Subtitle 3"></td></tr></tbody></table><p>The fourth subtitle reverts to the default style.</p><a id="ttml-example-subtitle-4"></a><table class="example-images"><caption>Subtitle 4 – Time Interval [17.2, 23.0)</caption><tbody><tr><td><img src="images/subtitle4.png" alt="Subtitle 4"></td></tr></tbody></table><p>The fifth subtitle continues, again using a variant style which
+overrides the default style's foreground color with a different color.</p><a id="ttml-example-subtitle-5"></a><table class="example-images"><caption>Subtitle 5 – Time Interval [23.0, 27.0)</caption><tbody><tr><td><img src="images/subtitle5.png" alt="Subtitle 5"></td></tr></tbody></table><p>During the next active time interval, two distinct subtitles are simultaneously active, with
+the paragraphs expressing each subtitle using different styles that override color and paragraph
 text alignment of the default style. Note that the flow order is determined by the lexical
-order of elements as they appear in the content hierarchy.</p><a name="dfxp-example-subtitle-6" id="dfxp-example-subtitle-6"></a><table class="example-images"><caption>Subtitles 6a and 6b – Time Interval [28.0, 34.6)</caption><tbody><tr><td><img src="images/subtitle6.png" alt="Subtitles 6a and 6b"></td></tr></tbody></table><p>The next subtitle is specified in a similar manner using
-a style override to give a paragraph right (end) justified in the
-inline progression direction.</p><a name="dfxp-example-subtitle-7" id="dfxp-example-subtitle-7"></a><table class="example-images"><caption>Subtitle 7 – Time Interval [34.6, 45.0)</caption><tbody><tr><td><img src="images/subtitle7.png" alt="Subtitles 7a and 7b"></td></tr></tbody></table><p>The eighth subtitle uses the same style override as the previous
+order of elements as they appear in the content hierarchy.</p><a id="ttml-example-subtitle-6"></a><table class="example-images"><caption>Subtitles 6a and 6b – Time Interval [28.0, 34.6)</caption><tbody><tr><td><img src="images/subtitle6.png" alt="Subtitles 6a and 6b"></td></tr></tbody></table><p>The next subtitle is specified in a similar manner using
+a style override to give the paragraph right (end) justification in the
+inline progression direction.</p><a id="ttml-example-subtitle-7"></a><table class="example-images"><caption>Subtitle 7 – Time Interval [34.6, 45.0)</caption><tbody><tr><td><img src="images/subtitle7.png" alt="Subtitles 7a and 7b"></td></tr></tbody></table><p>The eighth subtitle uses the same style override as the previous
 subtitle in order to maintain the right (end) justification of the
-paragraph.</p><a name="dfxp-example-subtitle-8" id="dfxp-example-subtitle-8"></a><table class="example-images"><caption>Subtitle 8 – Time Interval [47.3, 49.0)</caption><tbody><tr><td><img src="images/subtitle8.png" alt="Subtitle 8"></td></tr></tbody></table><p>During the final (ninth) active time interval, two distinct
+paragraph.</p><a id="ttml-example-subtitle-8"></a><table class="example-images"><caption>Subtitle 8 – Time Interval [47.3, 49.0)</caption><tbody><tr><td><img src="images/subtitle8.png" alt="Subtitle 8"></td></tr></tbody></table><p>During the final (ninth) active time interval, two distinct
 subtitles are again simultaneously active, but with a different
 style applied to the second paragraph to override the default color.
 Note that the flow order is determined by the lexical order of
-elements as they appear in the content hierarchy.</p><a name="dfxp-example-subtitle-9" id="dfxp-example-subtitle-9"></a><table class="example-images"><caption>Subtitles 9a and 9b – Time Interval [53.5, 58.7)</caption><tbody><tr><td><img src="images/subtitle9.png" alt="Subtitles 9a and 9b"></td></tr></tbody></table><p>The examples shown above demonstrate the primary types of information that may
+elements as they appear in the content hierarchy.</p><a id="ttml-example-subtitle-9"></a><table class="example-images"><caption>Subtitles 9a and 9b – Time Interval [53.5, 58.7)</caption><tbody><tr><td><img src="images/subtitle9.png" alt="Subtitles 9a and 9b"></td></tr></tbody></table><p>The examples shown above demonstrate the primary types of information that may
 be authored using TTML: metadata, styling, layout, timing, and content. In typical cases,
-styling and layout information are separately specified in a document instance. Content information
+styling and layout information are separately specified in a <em>Document Instance</em>. Content information
 is expressed in a hierarchical fashion that embodies the organization of both spatial (flow) and
 timing information. Content makes direct or indirect references to styling and layout information
 and may specify inline overrides to styling.</p></div></div><div class="div1">
-<h2><a name="definitions" id="definitions"></a>2 Definitions</h2><div class="div2">
-<h3><a name="acronyms" id="acronyms"></a>2.1 Acronyms</h3><table class="acronyms" summary="Glossary List"><tr><td class="label"><b>DFXP</b></td><td class="def"><p>Distribution Format Exchange Profile</p></td></tr><tr><td class="label"><b>TT</b></td><td class="def"><p>Timed Text</p></td></tr><tr><td class="label"><b>TTML</b></td><td class="def"><p>Timed Text Markup Language</p></td></tr><tr><td class="label"><b>TT AS</b></td><td class="def"><p>Timed Text Authoring System</p></td></tr><tr><td class="label"><b>TT AF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TT WG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
-<h3><a name="terms" id="terms"></a>2.2 Terminology</h3><dl><dt class="label">Abstract Document Instance</dt><dd><p>An instance of an abstract data set as represented by a
+<h2><a id="definitions"></a>2 Definitions</h2><div class="div2">
+<h3><a id="acronyms"></a>2.1 Acronyms</h3><table class="acronyms" summary="Glossary List"><tr><td class="label"><b>DFXP</b></td><td class="def"><p>Distribution Format Exchange Profile</p></td></tr><tr><td class="label"><b>TT</b></td><td class="def"><p>Timed Text</p></td></tr><tr><td class="label"><b>TTML</b></td><td class="def"><p>Timed Text Markup Language</p></td></tr><tr><td class="label"><b>TT AS</b></td><td class="def"><p>Timed Text Authoring System</p></td></tr><tr><td class="label"><b>TT AF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TT WG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
+<h3><a id="terms"></a>2.2 Terminology</h3><dl><dt class="label">Abstract Document Instance</dt><dd><p>An instance of an abstract data set as represented by a
 <em>Reduced XML Infoset</em>.</p></dd><dt class="label">Abstract Document Type</dt><dd><p>A set of constraints that defines a class of <em>XML Information
-Set</em>s <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label">Attribute Information Item</dt><dd><p>Each specified or defaulted attribute  of an XML document corresponds with an attribute information
+Sets</em> <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label">Attribute Information Item</dt><dd><p>Each specified or defaulted attribute  of an XML document corresponds with an attribute information
 item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.3.</p></dd><dt class="label">Character Information Item</dt><dd><p>Each data character appearing in an XML document corresponds with a character information
 item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.6.</p></dd><dt class="label">Content Processor</dt><dd><p>A processing system capable of importing (receiving) Timed Text Markup Language
 content for the purpose of transforming, presenting, or otherwise processing the content.</p></dd><dt class="label">Content Profile</dt><dd><p>A collection of features and extensions that are (or may be) employed by
 Timed Text Markup Language content.</p></dd><dt class="label">Content Region</dt><dd><p>A logical region into which rendered content is placed when modeling or
-performing presentation processing.</p></dd><dt class="label">Document Interchange Context</dt><dd><p>The implied context or environment external to a <em>Content Processor</em> in
+performing presentation processing.</p></dd><dt class="label">Document Instance</dt><dd><p>A concrete realization of a Timed Text Markup Language document, where the concrete form
+is specific to the context of reference. For example, a sequence of bytes that represents an
+XML serialization of a Timed Text document, an internal, parsed representation of such a
+Timed Text document, etc.</p></dd><dt class="label">Document Interchange Context</dt><dd><p>The implied context or environment external to a <em>Content Processor</em> in
 which document interchange occurs, and in which out-of-band protocols or specifications
 may define certain behavioral defaults, such as an implied <em>Content Profile</em>.</p></dd><dt class="label">Document Processing Context</dt><dd><p>The implied context or environment internal to a <em>Content Processor</em> in
 which document processing occurs, and in which out-of-band protocols or specifications
 may define certain behavioral defaults, such as the establishment or creation of a
-<em>Synthetic Syncbase</em>.</p></dd><dt class="label">Element Information Item</dt><dd><p>Each element appearing in an XML document corresponds with an element information
+<em>Synthetic Document Syncbase</em>.</p></dd><dt class="label">Element Information Item</dt><dd><p>Each element appearing in an XML document corresponds with an element information
 item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.2.</p></dd><dt class="label">Exchange Profile</dt><dd><p>A content profile that serves a set of needs
 for content interchange.</p></dd><dt class="label">Extension</dt><dd><p>A syntactic or semantic expression or capability that is defined and
 labeled (using a extension designation) in another (public or private)
@@ -622,16 +631,17 @@
 processor.</p></dd><dt class="label">Region</dt><dd><p>A logical construct that models authorial intention regarding
 desired or potential presentation processing, and which is represented as
 a rectangular area of a presentation surface into which content
-is composed and rendered during presentation processing.</p></dd><dt class="label">Reduced XML Infoset</dt><dd><p>An XML Information Set <a href="#infoset">[XML InfoSet]</a> that satisfieds the
+is composed and rendered during presentation processing.</p></dd><dt class="label">Reduced XML Infoset</dt><dd><p>An XML Information Set <a href="#infoset">[XML InfoSet]</a> that satisfies the
 constraints specify by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></dd><dt class="label">Related Media Object</dt><dd><p>A (possibly null) media object associated with or otherwise related
-to a TTML document instance. For example, an aggregate audio/video media
-object for which a TTML document instance provides caption or subtitle
-information, and with which that TTML document instance is associated.</p></dd><dt class="label">Root Container Region</dt><dd><p>A logical region that establishes a coordinate system into which
-TTML document instance content regions are placed and optionally clipped.</p></dd><dt class="label">Root Temporal Extent</dt><dd><p>
-The temporal extent (interval) defined by the temporal beginning and ending of a TTML document instance in relationship with some external application or presentation context.
-</p></dd><dt class="label">SMPTE Time Code</dt><dd><p>A time code whose format and semantics is established by <a href="#smpte12m">[SMPTE 12M]</a>
+to a <em>Document Instance</em>. For example, an aggregate audio/video media
+object for which a <em>Document Instance</em> provides caption or subtitle
+information, and with which that <em>Document Instance</em> is associated.</p></dd><dt class="label">Root Container Region</dt><dd><p>A logical region that establishes a coordinate system into which
+<em>Document Instance</em> content regions are placed and optionally clipped.</p></dd><dt class="label">Root Temporal Extent</dt><dd><p>
+The temporal extent (interval) defined by the temporal beginning and ending of a <em>Document Instance</em> in relationship with some external application or presentation context.
+</p></dd><dt class="label">SMPTE Time Code</dt><dd><p>A time code whose format and semantics are established by <a href="#smpte12m">[SMPTE 12M]</a>,
 which may be embedded into or otherwise associated with media content, such
-as a broadcast audio/video stream.</p></dd><dt class="label">Synthetic Document Syncbase</dt><dd><p>A document level syncbase synthesized or otherwise established by
+as a broadcast audio/video stream.</p></dd><dt class="label">Synthetic Document Syncbase</dt><dd><p>A document level <a href="http://www.w3.org/TR/2005/REC-SMIL2-20051213/smil-timing.html#Timing-Syncbases">syncbase</a>
+<a href="#smil21">[SMIL 2.1]</a>, § 10.7.1, synthesized or otherwise established by
 the <em>Document Processing Context</em> in accordance with the
 <em>Related Media Object</em> or other processing criteria.</p></dd><dt class="label">Synthetic SMPTE Document Syncbase</dt><dd><p>A <em>Synthetic Document Syncbase</em> constructed from <em>SMPTE Time
 Code</em> values embedded in or associated with the <em>Related Media Object</em> or
@@ -644,16 +654,26 @@
 or rewrites TTML features so as to conform to a profile of TTML. An example of the latter is
 a processor that translates TTML into a completely different timed text format. Because this
 specification does not otherwise define a target profile or format for transformation processing,
-no further transformation semantics are defined by this specification.</p></dd></dl></div><div class="div2">
-<h3><a name="conventions" id="conventions"></a>2.3 Documentation Conventions</h3><p>Within normative prose in this specification, the words
+no further transformation semantics are defined by this specification.</p></dd><dt class="label">Valid Abstract Document Instance</dt><dd><p>An <em>Abstract Document Instance</em> which has been assessed for validity
+and found to be valid as defined by <a href="#doctypes"><b>4 Document Types</b></a>.</p></dd></dl></div><div class="div2">
+<h3><a id="conventions"></a>2.3 Documentation Conventions</h3><p>Within normative prose in this specification, the words
 <em>may</em>, <em>should</em>, and <em>must</em> are
 defined as follows:</p><dl class="conformance-keywords"><dt class="label">may</dt><dd><p>Conforming documents and/or TTML processors are permitted to,
 but need not behave as described. </p></dd><dt class="label">should</dt><dd><p>Conforming documents and/or TTML processors are strongly
 recommended to, but need not behave as described.</p></dd><dt class="label">must</dt><dd><p>Conforming documents and/or TTML processors are required
-to behave as described; otherwise, they are in error. </p></dd></dl><p>All normative syntactic definitions of XML representations and
-other related terms are depicted with a light orange background color
+to behave as described; otherwise, they are in error. </p></dd></dl><p>If normative specification language takes an imperative form,
+then it is to be treated as if the term <span class="strong">must</span>
+applies. Furthermore, if normative language takes a declarative form,
+and this language is governed by <span class="strong">must</span>,
+then it is also to be treated as if the term <span class="strong">must</span>
+applies.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>For example, the phrases "treat X as an error" and "consider X
+as an error" are to be read as mandatory requirements in the context of use. Similarly, if the specification
+prose is "X must apply", "X applies", or "X is mandatory", and "X" is further defined as "X is Y and Z",
+then, by transitive closure, this last declarative phrase is to be read as "Y is mandatory" and
+"Z is mandatory" in the context of use.</p></div><p>All normative syntactic definitions of XML representations and
+other related terms are depicted with a light yellow-orange background color
 and labeled as "XML Representation" or "Syntax Representation", such
-as in the following:</p><a name="elt-syntax-example" id="elt-syntax-example"></a><table class="syntax"><caption>XML Representation – Element Information Item: example</caption><tbody><tr><td>
+as in the following:</p><a id="elt-syntax-example"></a><table class="syntax"><caption>XML Representation – Element Information Item: example</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;example
   <span class="reqattr">count</span> = integer
@@ -676,7 +696,7 @@
 header contains the expression "Non-Normative", then the entirety
 of the section or appendix is considered non-normative.</p><p>All paragraphs marked as a <span class="strong">Note</span> are considered non-normative.</p><p>Example code fragments are depicted with a light blue-green
 background color and labeled as "Example Fragment", such as in
-the following:</p><a name="example-fragment-1" id="example-fragment-1"></a><table class="example"><caption>Example Fragment – Sample</caption><tbody><tr><td>
+the following:</p><a id="example-fragment-1"></a><table class="example"><caption>Example Fragment – Sample</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"&gt;
   &lt;head&gt;
@@ -688,45 +708,42 @@
 &lt;/tt&gt;
 </pre></div>
 </td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="conformance" id="conformance"></a>3 Conformance</h2><p>This section specifies the general conformance requirements for
-TTML content and processors.</p><div class="div2">
-<h3><a name="conformance-content" id="conformance-content"></a>3.1 Content Conformance</h3><p>A TTML document instance conforms to this specification if the following criteria are
-satisfied:</p><ol class="enumar"><li><p>When transporting a document instance in a context in which a
-Media Type <a href="#media-types">[Media Types]</a> identifies the content type of the interchanged document
-instance, then the specified media type is
+<h2><a id="conformance"></a>3 Conformance</h2><p>This section specifies the general conformance requirements for
+TTML Content and processors.</p><div class="div2">
+<h3><a id="conformance-content"></a>3.1 Content Conformance</h3><p>A TTML <em>Document Instance</em> conforms to this specification if the following criteria are
+satisfied:</p><ol class="enumar"><li><p>When transporting a <em>Document Instance</em> in a <em>Document Interchange Context</em> in which a
+Media Type <a href="#media-types">[Media Types]</a> identifies the content type of the interchanged <em>Document Instance</em>, then the specified media type is
 <code>application/ttml+xml</code> in conformance with <a href="#rfc3023">[XML Media Types]</a> § 7, with which an optional
 <code>profile</code> parameter may appear, the value of which
 conforms to
 a profile designator as
 defined by
-<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p></li><li><p>The document instance is or can be represented as a Reduced XML
+<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p></li><li><p>The <em>Document Instance</em> is or can be represented as a Reduced XML
 Infoset as defined by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></li><li><p>The Reduced XML
-Infoset that corresponds to the document instance is or can
-be associated with one of the TTML Abstract
-Document Types defined by
-<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The Reduced XML Infoset that corresponds to the document instance is a
-Valid Abstract Document Instance of the associated
-Abstract Document Type.</p></li><li><p>The Reduced XML Infoset satisfies all additional mandatory syntactic and
+Infoset that corresponds to the <em>Document Instance</em> is or can
+be associated with one of the <em>Abstract Document Types</em> defined by
+<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The <em>Reduced XML Infoset</em> that corresponds to the <em>Document Instance</em> is a
+<em>Valid Abstract Document Instance</em> of the associated
+<em>Abstract Document Type</em>.</p></li><li><p>The <em>Reduced XML Infoset</em> satisfies all additional mandatory syntactic and
 semantic constraints defined by this specification. In addition, this Infoset
 should satisfy the web content accessibility guidelines specified by
 <a href="#wcag">[WCAG]</a>.</p></li></ol></div><div class="div2">
-<h3><a name="conformance-processor" id="conformance-processor"></a>3.2 Processor Conformance</h3><div class="div3">
-<h4><a name="conformance-generic-processor" id="conformance-generic-processor"></a>3.2.1 Generic Processor Conformance</h4><p>A TTML processor conforms to this specification if the following
+<h3><a id="conformance-processor"></a>3.2 Processor Conformance</h3><div class="div3">
+<h4><a id="conformance-generic-processor"></a>3.2.1 Generic Processor Conformance</h4><p>A TTML <em>Content Processor</em> conforms to this specification if the following
 generic processor criteria are
 satisfied:</p><ol class="enumar"><li><p>The processor provides at least one mechanism for notionally
 instantiating a Reduced XML
-Infoset representation of a conformant TTML document
-instance.</p></li><li><p>If a process does or can perform validation of a candidate TTML
-document instance, then it provides at least one mechanism to
+Infoset representation of a conformant <em>Document Instance</em>.</p></li><li><p>If a process does or can perform validation of a candidate 
+<em>Document Instance</em>, then it provides at least one mechanism to
 implicitly or explicitly associate the
-Reduced XML Infoset representation
-of a conformant TTML document instance with one of the
-TTML Abstract Document Types defined by
+<em>Reduced XML Infoset</em> representation
+of a conformant <em>Document Instance</em> with one of the
+<em>Abstract Document Types</em> defined by
 <a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The processor does not <em>a priori</em> reject or abort the
-processing of a conformant TTML document instance
+processing of a conformant <em>Document Instance</em>
 unless the processor does not support some required
-(mandatory) feature specified or implied by a TTML content profile
-declared to apply to the document instance.</p></li><li><p>The processor supports all mandatory processing semantics defined by this specification.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>mandatory semantics</em> refers to all explicit use of the conformance
+(mandatory) feature specified or implied by a TTML Content profile
+declared to apply to the <em>Document Instance</em>.</p></li><li><p>The processor supports all mandatory processing semantics defined by this specification.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>mandatory semantics</em> refers to all explicit use of the conformance
 key phrases <span class="strong">must</span> and <span class="strong">must not</span> as well as any
 declarative statement that can be reasonably inferred from such key phrases. For example, these
 mandatory semantics include support for all features marked as mandatory in <a href="#feature-support"><b>D.2 Feature Support</b></a>.</p></div></li><li><p>If the processor supports some optional processing semantics defined by this specification,
@@ -735,22 +752,23 @@
 <span class="strong">may</span>, and <span class="strong">may not</span>,
 as well as any declarative statement that can be reasonably inferred from such key phrases. For example, these
 optional semantics include support for all features marked as optional in <a href="#feature-support"><b>D.2 Feature Support</b></a>.</p></div></li></ol></div><div class="div3">
-<h4><a name="conformance-transformation-processor" id="conformance-transformation-processor"></a>3.2.2 Transformation Processor Conformance</h4><p>A TTML processor is a conformant TTML transformation processor if
+<h4><a id="conformance-transformation-processor"></a>3.2.2 Transformation Processor Conformance</h4><p>A TTML <em>Content Processor</em> is a conformant TTML <em>Transformation Processor</em> if
 the following criteria are satisfied:</p><ol class="enumar"><li><p>The processor satisfies all requirements specified by
 <a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the DFXP Transformation profile as specified
 by <a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a>.</p></li></ol></div><div class="div3">
-<h4><a name="conformance-presentation-processor" id="conformance-presentation-processor"></a>3.2.3 Presentation Processor Conformance</h4><ol class="enumar"><li><p>The processor satisfies all requirements specified by
+<h4><a id="conformance-presentation-processor"></a>3.2.3 Presentation Processor Conformance</h4><p>A TTML <em>Content Processor</em> is a conformant TTML <em>Presentation Processor</em> if
+the following criteria are satisfied:</p><ol class="enumar"><li><p>The processor satisfies all requirements specified by
 <a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the DFXP Presentation profile as specified
 by <a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a>.</p></li></ol></div></div><div class="div2">
-<h3><a name="claims" id="claims"></a>3.3 Claims</h3><p>Any claim of compliance with respect to TTML content or processor
-conformance must make
+<h3><a id="claims"></a>3.3 Claims</h3><p>Any claim of compliance with respect to the conformance of a TTML <em>Document Instance</em> or
+<em>Content Processor</em> must make
 reference to an implementation compliance statement (ICS).</p><p>An implementation compliance statement must identify all mandatory
 and optional features of this specification that are satisfied by the
-content or processor implementation. In particular, the statement must
+document instance or the content processor implementation. In particular, the statement must
 identify the utilized or supported TTML vocabulary profile(s) as
 defined by <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>, and, if a subset or
 superset profile is used or supported, then what features are excluded
-or included in the subset or superset profile.</p><p>A TTML document instance for which a compliance claim is made
+or included in the subset or superset profile.</p><p>A <em>Document Instance</em> for which a compliance claim is made
 must specify
 either (1)
 a <code>ttp:profile</code> attribute on its root
@@ -761,61 +779,59 @@
 a <code>ttp:profile</code> element as a child of the
 <code>head</code> element as defined by
 <a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p></div></div><div class="div1">
-<h2><a name="doctypes" id="doctypes"></a>4 Document Types</h2><p>This section defines the following TTML Abstract Document Types:</p><ul><li><p><a href="#dfxp-content-doctype"><b>4.1 DFXP Content</b></a></p></li></ul><p>Each abstract document type consists of the following constraints:</p><ul><li><p>a non-empty collection of element types, where each element type consists of a name,
-a (possibly empty) collection of attributes, and a content specification</p></li><li><p>a non-empty collection of element types that may appear as the document element</p></li></ul><p>An Abstract Document Instance may be assessed in terms of validity,
-and is considered to be a Valid Abstract Document Instance if it
+<h2><a id="doctypes"></a>4 Document Types</h2><p>This section defines the following TTML <em>Abstract Document Types</em>:</p><ul><li><p><a href="#ttml-content-doctype"><b>4.1 TTML Content</b></a></p></li></ul><p>Each <em>Abstract Document Type</em> consists of the following constraints:</p><ul><li><p>a non-empty collection of element types, where each element type consists of a name,
+a (possibly empty) collection of attributes, and a content specification</p></li><li><p>a non-empty collection of element types that may appear as the document element</p></li></ul><p>An <em>Abstract Document Instance</em> may be assessed in terms of validity,
+and is considered to be a <em>Valid Abstract Document Instance</em> if it
 satisfies the following condition: if after</p><ol class="enumar"><li><p>pruning all element information
 items whose names are not members of the collection of element types defined
-by the associated abstract document type, then</p></li><li><p>pruning character
+by the associated <em>Abstract Document Type</em>, then</p></li><li><p>pruning character
 information item children from any remaining element in case that all
 character children of the element denote XML whitespace characters and the element's type
-is defined as empty in the associated Abstract Document Type, and then</p></li><li><p>pruning all attribute
+is defined as empty in the associated <em>Abstract Document Type</em>, and then</p></li><li><p>pruning all attribute
 information items having expanded names such that the namespace URI of the
 expanded names are not listed in <a href="#namespace-vocab-table"><b>Table 1 – Namespaces</b></a>,</p></li></ol><p>then the document element is one of the document
-element types permitted by the associated abstract document type,
+element types permitted by the associated <em>Abstract Document Type</em>,
 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 abstract document type.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a
-conformant document instance that adheres to a
-supported content profile, a given document instance may be
+associated <em>Abstract Document Type</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a
+conformant <em>Document Instance</em> that adheres to a
+supported content profile, a given <em>Document Instance</em> may be
 constrained by the author or authoring tool to satisfy a more
 restrictive definition of validity.</p></div><div class="div2">
-<h3><a name="dfxp-content-doctype" id="dfxp-content-doctype"></a>4.1 DFXP Content</h3><p>DFXP Content is an abstract document type of a profile of the Timed Text Markup Language intended
+<h3><a id="ttml-content-doctype"></a>4.1 TTML Content</h3><p>TTML Content is an <em>Abstract Document Type</em> of a profile of the Timed Text Markup Language intended
 to be used for interchange among distribution systems. This document type
 is defined in terms of the
 element and attribute vocabulary
-specified in <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification defines two types of schemas that may be used to validate a subset of
-conformant DFXP Content document instances:</p><ul><li><p><a href="#dfxp-schema-rnc"><b>B.1 Relax NG Schema</b></a></p></li><li><p><a href="#dfxp-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a DFXP Content document instance must be a
-<code>tt</code> element, as defined by <a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The schemas included in this specification do not validate all syntactic constraints
-defined by this specification. In particular, performing validation with one of the above
+specified in <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification references two types of schemas that may be used to validate a superset/subset
+of conformant TTML Content <em>Document Instances</em>:</p><ul><li><p><a href="#ttml-schema-rnc"><b>B.1 Relax NG Compact (RNC) Schema</b></a></p></li><li><p><a href="#ttml-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a TTML Content <em>Document Instance</em> must be a
+<code>tt</code> element, as defined by <a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The schemas referenced by this specification do not validate all syntactic constraints
+defined by this specification, and, as such, represent a superset of conformant
+TTML Content. In particular, performing validation with one of the above
 referenced schemas may result in a <em>false positive</em> indication of validity.
-However, with one exception, their
-use will not produce a <em>false negative</em> indication of validity
-when used with a compliant validating
-processor.</p><p>In exception to the above statement about false negatives,
-if the Relax NG schema included in this specification is used to validate a
-TTML Document containing elements in a foreign namespace and the <code>xml:id</code>
-attribute is used with any of those (foreign) elements,
-then an error will be reported even though such usage is permitted by this
-specification. In this case, the false negative arises due
-to a specific limitation in expressing wildcard patterns involving <code>xsd:ID</code>
-typed attributes in Relax NG schemas.
-Note that this specification defines the formal validity of a TTML Document to be
-based on an abstract document instance from which all foreign namespace elements and
-attributes have been removed. Therefore, the exceptional reporting of this false
-negative does not impact the formal assessment of TTML Document validity.</p></div></div></div><div class="div1">
-<h2><a name="vocabulary" id="vocabulary"></a>5 Vocabulary</h2><p>This section defines the
-namespaces, profiles, and vocabulary (as an element an attribute
+For example, both the RNC and XSD schemas specify
+that a <code>tts:fontFamily</code> attribute must
+satisfy the <code>xs:string</code> XSD data type; however, this data type is a superset
+of the values permitted to be used with the <code>tts:fontFamily</code> attribute.</p><p>In addition, the RNC schema may produce a <em>false negative</em>
+indication of validity when using the <code>xml:id</code> attribute with an element in
+a foreign namespace, thus representing a subset of conformant TTML Content. This is
+due to a specific limitation in expressing wildcard patterns involving <code>xsd:ID</code>
+typed attributes in Relax NG schemas. Note that this specification defines the
+formal validity of a <em>Document Instance</em> to be based on an <em>Abstract Document Instance</em> from
+which all foreign namespace elements and attributes have been removed. Therefore, the
+exceptional reporting of this false negative does not impact the formal assessment
+of <em>Document Instance</em> validity.</p></div></div></div><div class="div1">
+<h2><a id="vocabulary"></a>5 Vocabulary</h2><p>This section defines the
+namespaces, profiles, and vocabulary (as an element and attribute
 catalog) of the Timed Text Markup Language (TTML) as follows:</p><ul><li><p><a href="#vocabulary-namespaces"><b>5.1 Namespaces</b></a></p></li><li><p><a href="#vocabulary-profiles"><b>5.2 Profiles</b></a></p></li><li><p><a href="#vocabulary-overview"><b>5.3 Catalog</b></a></p></li></ul><div class="div2">
-<h3><a name="vocabulary-namespaces" id="vocabulary-namespaces"></a>5.1 Namespaces</h3><p>The Timed Text Markup Language (TTML) employs a number of
-namespaces for elements and certain
+<h3><a id="vocabulary-namespaces"></a>5.1 Namespaces</h3><p>The Timed Text Markup Language (TTML) employs a number of
+XML Namespaces <a href="#xmlns10">[XML Namespaces 1.0]</a> for elements and certain
 global attributes. The following table specifies this set of namespaces
 and indicates the default prefix used within this specification and the
-normative URI that denotes each namespace.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In a specific document instance, it is not required that the default
+normative URI that denotes each namespace.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In a specific <em>Document Instance</em>, it is not required that the default
 prefixes shown below are used. Any prefix or namespace binding that satisfies the constraints
-of XML Namespaces may be used that is associated with the specified namespace URI.</p></div><a name="namespace-vocab-table" id="namespace-vocab-table"></a><table class="common"><caption>Table 1 – Namespaces</caption><col width="30%" span="1"><col span="1"><col span="1"><tbody><tr><th>Name</th><th>Prefix</th><th>Value</th></tr><tr><td>TT</td><td><code>tt:</code></td><td><code>http://www.w3.org/ns/ttml</code></td></tr><tr><td>TT Parameter</td><td><code>ttp:</code></td><td><code>http://www.w3.org/ns/ttml#parameter</code></td></tr><tr><td>TT Style</td><td><code>tts:</code></td><td><code>http://www.w3.org/ns/ttml#styling</code></td></tr><tr><td>TT Metadata</td><td><code>ttm:</code></td><td><code>http://www.w3.org/ns/ttml#metadata</code></td></tr><tr><td>TT Profile</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/profile/</code></td></tr><tr><td>TT Feature</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/feature/</code></td></tr><tr><td>TT Extension</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/extension/</code></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If a reference to an element type is used in this specification and the name
+of XML Namespaces <a href="#xmlns10">[XML Namespaces 1.0]</a>  may be used that is associated with the specified namespace URI.</p></div><a id="namespace-vocab-table"></a><table class="common"><caption>Table 1 – Namespaces</caption><col width="30%" span="1"><col span="1"><col span="1"><tbody><tr><th>Name</th><th>Prefix</th><th>Value</th></tr><tr><td>TT</td><td><code>tt:</code></td><td><code>http://www.w3.org/ns/ttml</code></td></tr><tr><td>TT Parameter</td><td><code>ttp:</code></td><td><code>http://www.w3.org/ns/ttml#parameter</code></td></tr><tr><td>TT Style</td><td><code>tts:</code></td><td><code>http://www.w3.org/ns/ttml#styling</code></td></tr><tr><td>TT Metadata</td><td><code>ttm:</code></td><td><code>http://www.w3.org/ns/ttml#metadata</code></td></tr><tr><td>TT Profile</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/profile/</code></td></tr><tr><td>TT Feature</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/feature/</code></td></tr><tr><td>TT Extension</td><td><em>none</em></td><td><code>http://www.w3.org/ns/ttml/extension/</code></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If a reference to an element type is used in this specification and the name
 of the element type is not namespace qualified, then the TT Namespace applies.</p><p>For certain namespaces defined above, the default prefix
 is specified as <em>none</em> if no XML vocabulary is defined in
 the namespace by this specification (nor expected to be defined in a
@@ -825,7 +841,7 @@
 dereferencing standard profile definitions.</p></div><p>All TTML Namespaces are <a href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><em>mutable</em></a>
 <a href="#nsstate">[NSState]</a>; all undefined names in these namespaces are reserved for future
 standardization by the W3C.</p></div><div class="div2">
-<h3><a name="vocabulary-profiles" id="vocabulary-profiles"></a>5.2 Profiles</h3><p>The Timed Text Markup Language (TTML) employs a number of
+<h3><a id="vocabulary-profiles"></a>5.2 Profiles</h3><p>The Timed Text Markup Language (TTML) employs a number of
 standard, predefined profiles of its
 vocabulary and associated semantics.
 The following table specifies this set of
@@ -834,7 +850,7 @@
 and designator for each
 predefined profile,
 and where each of these profiles is formally elaborated in
-<a href="#profiles"><b>F Profiles</b></a>.</p><a name="profile-vocab-table" id="profile-vocab-table"></a><table class="common"><caption>Table 2 – Profiles</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Name</th><th>Designator</th></tr><tr><td>DFXP Transformation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code></td></tr><tr><td>DFXP Presentation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code></td></tr><tr><td>DFXP Full</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-full</code></td></tr></tbody></table><p></p><p>A profile designator must adhere to the
+<a href="#profiles"><b>F Profiles</b></a>.</p><a id="profile-vocab-table"></a><table class="common"><caption>Table 2 – Profiles</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Name</th><th>Designator</th></tr><tr><td>DFXP Transformation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code></td></tr><tr><td>DFXP Presentation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code></td></tr><tr><td>DFXP Full</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-full</code></td></tr></tbody></table><p></p><p>A profile designator must adhere to the
 <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
 §3.2.17. If the profile designator is expressed as a relative URI,
 then it must be absolutized by using the TT Profile Namespace value as
@@ -843,9 +859,8 @@
 would be
 <code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>.</p></div><p>A profile designator is not restricted to the set of designators enumerated
 in <a href="#profile-vocab-table"><b>Table 2 – Profiles</b></a>, but may be any URI that
-feasibly dereferences a TTML Profile Definition Document.</p><p>The profile of TTML that must be supported by a
-TTML content processor in order to process a document
-instance is specified either (1) by specifying a
+feasibly dereferences a TTML <em>Profile Definition Document</em>.</p><p>The profile of TTML that must be supported by a
+TTML <em>Content Processor</em> in order to process a <em>Document Instance</em> is determined either (1) by specifying a
 <code>ttp:profile</code> attribute on the root <code>tt</code> element, as
 defined by <a href="#parameter-attribute-profile"><b>6.2.8 ttp:profile</b></a>, or (2) by
 including one or more <code>ttp:profile</code>
@@ -854,10 +869,10 @@
 descendant of the <code>tt</code> element, then the <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
 attribute should not be specified on the <code>tt</code> element. If both
 a <code>ttp:profile</code> element and a <code>ttp:profile</code>
-attribute are present (in a given document instance), then the
+attribute are present (in a given <em>Document Instance</em>), then the
 <code>ttp:profile</code> attribute must be ignored for the purpose of
 determining the declared profile requirements.</p><p>If more than one <code>ttp:profile</code> element appears in
-a TTML document instance, then all specified profiles apply
+a <em>Document Instance</em>, then all specified profiles apply
 simultaneously.  In such a case, if some feature or some extension is
 specified by one profile to be used (mandatory and enabled) and by
 another profile to be required (mandatory) or optional (voluntary),
@@ -869,25 +884,25 @@
 <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
 attribute nor
 <a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a>
-element is present in a TTML document instance, and if the Document
-Interchange Context does not make an implicit or explicit
-reference to a pre-defined Content Profile or does not specify a Profile Definition
-Document or another equivalent set of feature designations,
-then the DFXP Transformation profile applies.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not a requirement on a conformant document instance that a <em>Content Profile</em> be internally
+element is present in a <em>Document Instance</em>, and if the <em>Document
+Interchange Context</em> does not make an implicit or explicit
+reference to a pre-defined Content Profile or does not specify a <em>Profile Definition
+Document</em> or another equivalent set of feature designations,
+then the DFXP Transformation profile applies.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not a requirement on a conformant <em>Document Instance</em> that a <em>Content Profile</em> be internally
 defined by use of a <code>ttp:profile</code> element or internally referenced by a
 <code>ttp:profile</code> attribute. More specifically, it is permitted that the <em>Document
 Interchange Context</em> determines the applicable <em>Content Profile</em> through private
 agreement, out-of-band protocol, or common use (between sender and receiver) of a profile defined
 by an external specification.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>It is intended that the <code>ttp:profile</code> attribute be used when
 the author wishes to reference one of the standard, predefined profiles of
-TTML content, and does not wish to modify (by supersetting or subsetting)
+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 TTML Profile Definition Document.
-However, it is not required that a conformant TTML content processor be able
+a URI that denotes an externally defined <em>Profile Definition Document</em>.
+However, it is not required that a conformant TTML Content processor be able
 to dereference such an externally specified profile definition.</p><p>In contrast, it is intended that the <code>ttp:profile</code> element be
 used when the author wishes to make use of a modified predefined profile or
-wishes to include in the document instance a non-standard profile definition
+wishes to include in the <em>Document Instance</em> 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 required (mandatory) that was either not specified in the underlying, baseline
 profile or was specified as optional (voluntary) in the baseline profile.
@@ -897,13 +912,13 @@
 is referred to as a <em>subtractive</em> profile; when modified by supersetting, the result
 is referred to as an <em>additive</em> profile.
 It is also possible to define a derived profile that is simultaneously subtractive
-and additive.</p></div><p>If a TTML document instance makes use of a feature defined by
+and additive.</p></div><p>If a <em>Document Instance</em> makes use of a feature defined by
 <a href="#feature-designations"><b>D.1 Feature Designations</b></a> and if the intended use of the
 document requires the recognition and processing of that feature, then
 the document must include a <em>required feature</em> or
 a <em>used feature</em>
 specification in one of its declared or
-referenced profiles.  If a TTML document instance makes use
+referenced profiles.  If a <em>Document Instance</em> makes use
 of an extension designatable by <a href="#extension-designations"><b>E.1 Extension Designations</b></a> and if the intended use of the document
 requires the recognition and processing of that extension, then the
 document must include a <em>required extension</em> or
@@ -922,7 +937,7 @@
 respectively.</p></div><p>An example of an author defined
 additive, derived profile of the DFXP Presentation
 profile is shown
-below in <a href="#dfxp-example-sub-profile"><b>Example Fragment – DFXP Additive Profile</b></a>.</p><a name="dfxp-example-sub-profile" id="dfxp-example-sub-profile"></a><table class="example"><caption>Example Fragment – DFXP Additive Profile</caption><tbody><tr><td>
+below in <a href="#ttml-example-sub-profile"><b>Example Fragment – DFXP Additive Profile</b></a>.</p><a id="ttml-example-sub-profile"></a><table class="example"><caption>Example Fragment – DFXP Additive Profile</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"&gt;
  &lt;head&gt;
@@ -941,17 +956,16 @@
 optional as it is defined
 in <a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a>). Note also the resetting of the
 default XMLNS binding on the <code>profile</code> element to the TT Parameter Namespace.</p></div></div><div class="div2">
-<h3><a name="vocabulary-overview" id="vocabulary-overview"></a>5.3 Catalog</h3><p>The vocabulary of the Timed Text Markup Language (TTML) is
+<h3><a id="vocabulary-overview"></a>5.3 Catalog</h3><p>The vocabulary of the Timed Text Markup Language (TTML) is
 defined in the following major catalogs (divisions of vocabulary):</p><ul><li><p><a href="#core-vocabulary-overview"><b>5.3.1 Core Catalog</b></a></p></li><li><p><a href="#extension-vocabulary-overview"><b>5.3.2 Extension Catalog</b></a></p></li></ul><p>The core catalog defines the baseline, core vocabulary of TTML,
-and, in particular, the vocabulary of DFXP Content. The extension catalog
+and, in particular, the vocabulary of TTML Content. The extension catalog
 serves as a placeholder for extensions to the core vocabulary defined
 by TTML.</p><div class="div3">
-<h4><a name="core-vocabulary-overview" id="core-vocabulary-overview"></a>5.3.1 Core Catalog</h4><p>The core vocabulary catalog is intended to satisfy the needs of
+<h4><a id="core-vocabulary-overview"></a>5.3.1 Core Catalog</h4><p>The core vocabulary catalog is intended to satisfy the needs of
 TTML while providing a baseline vocabulary for future profiles. This vocabulary
 is divided into distinct categories, specified in detail
-in the following sections:</p><ul><li><p><a href="#parameters"><b>6 Parameters</b></a></p></li><li><p><a href="#content"><b>7 Content</b></a></p></li><li><p><a href="#styling"><b>8 Styling</b></a></p></li><li><p><a href="#layout"><b>9 Layout</b></a></p></li><li><p><a href="#timing"><b>10 Timing</b></a></p></li><li><p><a href="#animation"><b>11 Animation</b></a></p></li><li><p><a href="#metadata"><b>12 Metadata</b></a></p></li></ul><p>The core element vocabulary specified for use with a TTML document
-instance is enumerated in
-<a href="#element-vocab-table"><b>Table 3 – Element Vocabulary</b></a>.</p><a name="element-vocab-table" id="element-vocab-table"></a><table class="common"><caption>Table 3 – Element Vocabulary</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Module</th><th>Elements</th></tr><tr><td>
+in the following sections:</p><ul><li><p><a href="#parameters"><b>6 Parameters</b></a></p></li><li><p><a href="#content"><b>7 Content</b></a></p></li><li><p><a href="#styling"><b>8 Styling</b></a></p></li><li><p><a href="#layout"><b>9 Layout</b></a></p></li><li><p><a href="#timing"><b>10 Timing</b></a></p></li><li><p><a href="#animation"><b>11 Animation</b></a></p></li><li><p><a href="#metadata"><b>12 Metadata</b></a></p></li></ul><p>The core element vocabulary specified for use with a <em>Document Instance</em> is enumerated in
+<a href="#element-vocab-table"><b>Table 3 – Element Vocabulary</b></a>.</p><a id="element-vocab-table"></a><table class="common"><caption>Table 3 – Element Vocabulary</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Module</th><th>Elements</th></tr><tr><td>
 Animation
 </td><td>
 <a href="#animation-vocabulary-set">set</a>
@@ -1000,7 +1014,7 @@
 <a href="#styling-vocabulary-styling">styling</a>,
 <a href="#styling-vocabulary-style">style</a>
 </td></tr></tbody></table><p></p><p>Element vocabulary groups that are used in defining content models
-for TTML element types are enumerated in <a href="#element-vocab-group-table"><b>Table 4 – Element Vocabulary Groups</b></a>.</p><a name="element-vocab-group-table" id="element-vocab-group-table"></a><table class="common"><caption>Table 4 – Element Vocabulary Groups</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Group</th><th>Elements</th></tr><tr><td>
+for TTML element types are enumerated in <a href="#element-vocab-group-table"><b>Table 4 – Element Vocabulary Groups</b></a>.</p><a id="element-vocab-group-table"></a><table class="common"><caption>Table 4 – Element Vocabulary Groups</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Group</th><th>Elements</th></tr><tr><td>
 Animation.class
 </td><td>
 <a href="#animation-vocabulary-set">set</a>
@@ -1025,7 +1039,7 @@
 <a href="#metadata-vocabulary-title">ttm:title</a>
 </td></tr><tr><td>Parameters.class</td><td><a href="#parameter-vocabulary-profile">ttp:profile</a></td></tr></tbody></table><p></p><p>The attribute vocabulary specified for use with the core vocabulary
 catalog is enumerated in
-<a href="#attribute-vocab-table"><b>Table 5 – Attribute Vocabulary</b></a>.</p><a name="attribute-vocab-table" id="attribute-vocab-table"></a><table class="common"><caption>Table 5 – Attribute Vocabulary</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Module</th><th>Attributes</th></tr><tr><td>
+<a href="#attribute-vocab-table"><b>Table 5 – Attribute Vocabulary</b></a>.</p><a id="attribute-vocab-table"></a><table class="common"><caption>Table 5 – Attribute Vocabulary</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Module</th><th>Attributes</th></tr><tr><td>
 Core Attributes
 </td><td>
 <a href="#content-attribute-id">xml:id</a>,
@@ -1099,31 +1113,31 @@
 the so-called <em>lowerCamelCase</em> naming convention. In some cases, this results in the
 change of a name when the name was based upon another specification
 that used a different naming convention.</p></div></div><div class="div3">
-<h4><a name="extension-vocabulary-overview" id="extension-vocabulary-overview"></a>5.3.2 Extension Catalog</h4><p>The extension vocabulary catalog is intended for use by future
+<h4><a id="extension-vocabulary-overview"></a>5.3.2 Extension Catalog</h4><p>The extension vocabulary catalog is intended for use by future
 profiles of TTML, and is not further defined
-by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming TTML
-document instance may contain arbitrary namespace qualified
+by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming 
+<em>Document Instance</em> may contain arbitrary namespace qualified
 elements that reside in any namespace other than those namespaces
-defined for use with this specification. Furthermore, a conforming TTML
-document instance may contain arbitrary namespace qualified
+defined for use with this specification. Furthermore, a conforming 
+<em>Document Instance</em> may contain arbitrary namespace qualified
 attributes on TTML defined vocabulary where such attributes reside in
 any namespace other than those defined for use with this
 specification.</p></div></div></div><div class="div1">
-<h2><a name="parameters" id="parameters"></a>6 Parameters</h2><p>This section specifies the <em>parameters</em> matter of the
+<h2><a id="parameters"></a>6 Parameters</h2><p>This section specifies the <em>parameters</em> matter of the
 core vocabulary catalog, where
 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 processing context by means
-of which TTML content can be related to an external environment.</p><div class="div2">
-<h3><a name="parameter-element-vocabulary" id="parameter-element-vocabulary"></a>6.1 Parameter Element Vocabulary</h3><p>The following elements, all defined in the TT Parameter
-Namespace, specify parametric information that applies to a document
-or a content processor:</p><ul><li><p><a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a></p></li><li><p><a href="#parameter-vocabulary-features"><b>6.1.2 ttp:features</b></a></p></li><li><p><a href="#parameter-vocabulary-feature"><b>6.1.3 ttp:feature</b></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><b>6.1.4 ttp:extensions</b></a></p></li><li><p><a href="#parameter-vocabulary-extension"><b>6.1.5 ttp:extension</b></a></p></li></ul><div class="div3">
-<h4><a name="parameter-vocabulary-profile" id="parameter-vocabulary-profile"></a>6.1.1 ttp:profile</h4><p>The <code>ttp:profile</code> element is used to specify a collection of
+core vocabulary items or for establishing a <em>Document Processing Context</em> by means
+of which TTML Content can be related to an external environment.</p><div class="div2">
+<h3><a id="parameter-element-vocabulary"></a>6.1 Parameter Element Vocabulary</h3><p>The following elements, all defined in the TT Parameter
+Namespace, specify parametric information that applies to a <em>Document Instance</em>
+or <em>Content Processor</em>:</p><ul><li><p><a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a></p></li><li><p><a href="#parameter-vocabulary-features"><b>6.1.2 ttp:features</b></a></p></li><li><p><a href="#parameter-vocabulary-feature"><b>6.1.3 ttp:feature</b></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><b>6.1.4 ttp:extensions</b></a></p></li><li><p><a href="#parameter-vocabulary-extension"><b>6.1.5 ttp:extension</b></a></p></li></ul><div class="div3">
+<h4><a id="parameter-vocabulary-profile"></a>6.1.1 ttp:profile</h4><p>The <code>ttp:profile</code> element is used to specify a collection of
 used (mandatory and enabled), required (mandatory),
 and optional (voluntary) features and extensions that must or
-may be supported by a TTML content processor in order to process a TTML
-document that makes use (or may make use) of such features and
+may be supported by a <em>Content Processor</em> in order to process a
+<em>Document Instance</em> that makes (or may make) use of such features and
 extensions.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The difference between a <em>feature</em> and an
 <em>extension</em> is where it is defined and how it is labeled:
 if defined in this specification (or a future revision thereof) and
@@ -1132,21 +1146,20 @@
 and labeled there with an extension designation, then it is considered
 to be an extension. In general, features are expected to be defined by
 the W3C standards process, while extensions are expected to be defined by
-third parties.</p></div><p>This specification defines two distinct uses of the <code>ttp:profile</code> element:</p><ul><li><p>as a child of the <code>head</code> element within a TTML document
-instance;</p></li><li><p>as the root element of a TTML Profile Definition document
-instance;</p></li></ul><p>When a <code>tt:profile</code> element appears within a TTML document
-instance, its purpose is to express authorial intentions about which
+third parties.</p></div><p>This specification defines two distinct uses of the <code>ttp:profile</code> element:</p><ul><li><p>as a child of the <code>head</code> element within a TTML <em>Document Instance</em>;</p></li><li><p>as the root element of a TTML <em>Profile Definition Document</em>
+instance;</p></li></ul><p>When a <code>tt:profile</code> element appears within a TTML <em>Document Instance</em>,
+its purpose is to express authorial intentions about which
 features and extensions must or may be supported by a recipient
 content processor. In addition, the element indirectly expresses
 information about the set of features or extensions that are (or may
-expected to be) used by the document instance.</p><p>When a <code>tt:profile</code> element is used by a TTML
-Profile Definition document instance, it serves to publish a machine
-readable specification of a specific TTML content profile, of which
-this specification defines three such Profile Definition Documents in
+expected to be) used by the <em>Document Instance</em>.</p><p>When a <code>tt:profile</code> element is used by a TTML <em>Profile Definition Document</em> instance,
+it serves to publish a machine
+readable specification of a specific TTML Content profile, of which
+this specification defines three such <em>Profile Definition Documents</em> in
 <a href="#profiles"><b>F Profiles</b></a>.</p><p>The <code>ttp:profile</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group, followed by
 zero or more <code>ttp:features</code> elements, followed by
-zero or more <code>ttp:extensions</code> elements.</p><a name="elt-syntax-parameter-profile" id="elt-syntax-parameter-profile"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:profile</caption><tbody><tr><td>
+zero or more <code>ttp:extensions</code> elements.</p><a id="elt-syntax-parameter-profile"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:profile</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:profile
   use = string
@@ -1160,9 +1173,9 @@
 §3.2.17, and, furthermore, must denote a profile designator in
 accordance with <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>. In this case,
 the profile designator must refer to (1) a standard, predefined
-TTML Profile Definition Document as defined by <a href="#profiles"><b>F Profiles</b></a>,
-or (2) a dereferenceable resource representing a valid TTML Profile Definition
-document instance. In either case, the referenced profile serves as the
+<em>Profile Definition Document</em> as defined by <a href="#profiles"><b>F Profiles</b></a>,
+or (2) a feasibly dereferenceable resource representing a valid <em>Profile Definition
+Document</em> instance. In either case, the referenced profile serves as the
 baseline profile of the specifying <code>ttp:profile</code> element.</p><p>If the <code>use</code> attribute is not specified, then the baseline
 profile of the <code>ttp:profile</code> element must be considered to be
 the empty (null) profile, i.e., a profile definition containing no
@@ -1177,20 +1190,20 @@
 entails replacing an existing feature or extension specification, if
 it already exists, or adding a new feature or extension specification,
 if it does not yet exist in the profile;</p></li></ol><p>A conformant TTML processor is not required to be able to
-dereference a TTML Profile Definition Document that is not one of the
-standard, predefined profiles defined by <a href="#profiles"><b>F Profiles</b></a>.  A
-conformant TTML processor may make use of a built-in, static
+dereference a <em>Profile Definition Document</em> that is not one of the
+standard, predefined profiles defined by <a href="#profiles"><b>F Profiles</b></a>.  Furthermore,
+a conformant TTML processor may make use of a built-in, static
 form of each standard, predefined profile so as not to require
-dereferencing a network resource.</p><p>If a TTML processor is unable to dereference a non-standard TTML
-Profile Definition Document, then it must not further process the
+dereferencing a network resource.</p><p>If a TTML processor is unable to dereference a non-standard
+<em>Profile Definition Document</em>, then it must not further process the
 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 TTML document instance due to the inability to
-reference a non-standard TTML Profile Definition Document, then some
+processing of a <em>Document Instance</em> due to the inability to
+reference a non-standard <em>Profile Definition Document</em>, then some
 end-user notification should be given unless the end-user or system
 has disabled such a notification, or if the processor does not permit
-or entail the intervention of an end-user.</p><p>The <code>ttp:profile</code> element is illustrated by the following example.</p><a name="parameter-vocabulary-profile-example-1" id="parameter-vocabulary-profile-example-1"></a><table class="example"><caption>Example Fragment – ttp:profile</caption><tbody><tr><td>
+or entail the intervention of an end-user.</p><p>The <code>ttp:profile</code> element is illustrated by the following example.</p><a id="parameter-vocabulary-profile-example-1"></a><table class="example"><caption>Example Fragment – ttp:profile</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:profile use="dfxp-presentation"&gt;
   &lt;ttp:features xml:base="http://www.w3.org/ns/ttml/feature/"&gt;
@@ -1202,10 +1215,10 @@
 baseline profile. This baseline profile is then supersetted (thus
 creating an additive derived profile) by requiring support for
 <code>#text-outline</code> feature.</p></div></div><div class="div3">
-<h4><a name="parameter-vocabulary-features" id="parameter-vocabulary-features"></a>6.1.2 ttp:features</h4><p>The <code>ttp:features</code> element is a container element used to group
+<h4><a id="parameter-vocabulary-features"></a>6.1.2 ttp:features</h4><p>The <code>ttp:features</code> element is a container element used to group
 infomation about feature support requirements.</p><p>The <code>ttp:features</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group, followed by
-zero or more <code>ttp:feature</code> elements.</p><a name="elt-syntax-parameter-features" id="elt-syntax-parameter-features"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:features</caption><tbody><tr><td>
+zero or more <code>ttp:feature</code> elements.</p><a id="elt-syntax-parameter-features"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:features</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:features
   xml:base = string : <em>TT Feature Namespace</em>
@@ -1225,11 +1238,11 @@
 value applies, which is the TT Feature Namespace.</p><p>The <code>xml:base</code> attribute is
 used to permit the abbreviation of feature designation URIs expressed
 by child <code>ttp:feature</code> elements.</p></div><div class="div3">
-<h4><a name="parameter-vocabulary-feature" id="parameter-vocabulary-feature"></a>6.1.3 ttp:feature</h4><p>The <code>ttp:feature</code> element is used to specify
+<h4><a id="parameter-vocabulary-feature"></a>6.1.3 ttp:feature</h4><p>The <code>ttp:feature</code> element is used to specify
 infomation about support requirements for a particular feature.</p><p>The children of the <code>ttp:feature</code> element must express a non-empty
 sequence of character information items that adheres to the
 <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
-§3.2.17.</p><a name="elt-syntax-parameter-feature" id="elt-syntax-parameter-feature"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:feature</caption><tbody><tr><td>
+§3.2.17.</p><a id="elt-syntax-parameter-feature"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:feature</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:feature
   value = (optional|required|use) : required
@@ -1265,13 +1278,15 @@
 item definition. Therefore, if a <code>value</code> attribute is not
 specified on a <code>ttp:feature</code> element, it is equivalent to
 specifying that support for the feature is required.</p></div><p>If the value of the <code>value</code> attribute is
-<code>required</code> or <code>use</code>,
-and if the TTML processor implementation does
-not support the feature, then it must not further process the document
+<code>required</code> or <code>use</code>
+and the TTML processor implementation does
+not support the feature, or if the <code>value</code> attribute is
+<code>use</code> and the TTML processor implementation supports but has disabled
+that 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 TTML document instance due to the specification of a
+processing of a <em>Document Instance</em> due to the specification of a
 required, but unsupported feature by this element, then some end-user
 notification should be given unless the end-user or system has
 disabled such a notification, or if the processor does not permit or
@@ -1289,8 +1304,8 @@
 valid.</p><p>If some defined (i.e., standardized) or otherwise well known feature is not specified by
 a <code>ttp:feature</code> element in a given profile, then it must be interpreted as if the feature were specified
 with the <code>value</code> attribute equal to <code>optional</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In particular, if some feature is not present in a profile definition, then
-it is not to be interpreted as meaning the use of that feature (in a document instance)
-is disallowed or otherwise prohibited.</p></div><p>The <code>ttp:feature</code> element is illustrated by the following example.</p><a name="parameter-vocabulary-feature-example-1" id="parameter-vocabulary-feature-example-1"></a><table class="example"><caption>Example Fragment – ttp:feature</caption><tbody><tr><td>
+it is not to be interpreted as meaning the use of that feature (in a <em>Document Instance</em>)
+is disallowed or otherwise prohibited.</p></div><p>The <code>ttp:feature</code> element is illustrated by the following example.</p><a id="parameter-vocabulary-feature-example-1"></a><table class="example"><caption>Example Fragment – ttp:feature</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:profile use="http://www.w3.org/ns/ttml/profile/dfxp-presentation"&gt;
   &lt;ttp:features xml:base="http://www.w3.org/ns/ttml/feature/"&gt;
@@ -1308,10 +1323,10 @@
 </p><p>The effect of this example is to express authorial intentions that
 italic font style and text underlining must be
 supported.</p></div></div><div class="div3">
-<h4><a name="parameter-vocabulary-extensions" id="parameter-vocabulary-extensions"></a>6.1.4 ttp:extensions</h4><p>The <code>ttp:extensions</code> element is a container element used to group
+<h4><a id="parameter-vocabulary-extensions"></a>6.1.4 ttp:extensions</h4><p>The <code>ttp:extensions</code> element is a container element used to group
 infomation about extension support requirements.</p><p>The <code>ttp:extensions</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group, followed by
-zero or more <code>ttp:extension</code> elements.</p><a name="elt-syntax-parameter-extensions" id="elt-syntax-parameter-extensions"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:extensions</caption><tbody><tr><td>
+zero or more <code>ttp:extension</code> elements.</p><a id="elt-syntax-parameter-extensions"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:extensions</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:extensions
   xml:base = string : <em>TT Extension Namespace</em>
@@ -1331,11 +1346,11 @@
 value applies, which is the TT Extension Namespace.</p><p>The <code>xml:base</code> attribute is
 used to permit the abbreviation of feature designation URIs expressed
 by child <code>ttp:extension</code> elements.</p></div><div class="div3">
-<h4><a name="parameter-vocabulary-extension" id="parameter-vocabulary-extension"></a>6.1.5 ttp:extension</h4><p>The <code>ttp:extension</code> element is used to specify
+<h4><a id="parameter-vocabulary-extension"></a>6.1.5 ttp:extension</h4><p>The <code>ttp:extension</code> element is used to specify
 infomation about support requirements for a particular extension.</p><p>The children of the <code>ttp:extension</code> element must express a non-empty
 sequence of character information items that adheres to the
 <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
-§3.2.17.</p><a name="elt-syntax-parameter-extension" id="elt-syntax-parameter-extension"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:extension</caption><tbody><tr><td>
+§3.2.17.</p><a id="elt-syntax-parameter-extension"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttp:extension</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:extension
   value = (optional|required|use) : required
@@ -1370,13 +1385,15 @@
 item definition. Therefore, if a <code>value</code> attribute is not
 specified on a <code>ttp:extension</code> element, it is equivalent to
 specifying that support for the extension is required.</p></div><p>If the value of the <code>value</code> attribute is
-<code>required</code> or <code>use</code>,
-and if the TTML processor implementation does not support the
-extension, then it must not further process the document without the
+<code>required</code> or <code>use</code>
+and the TTML processor implementation does
+not support the extension, or if the <code>value</code> attribute is
+<code>use</code> and the TTML processor implementation supports but has disabled
+that extension, then it must not further process the document without the
 presence of an explicit override from an end-user or some
 implementation specific parameter traceable to an end-user or to a
 user or system configuration setting.  If a TTML processor aborts
-processing of a TTML document instance due to the specification of a
+processing of a <em>Document Instance</em> 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
@@ -1391,10 +1408,14 @@
 presence or reference to an optional extension by a document must not be
 considered to be a violation of document validity or a barrier to
 further processing if the syntactic expression is well-formed and
-valid.</p><p>The <code>ttp:extension</code> element is illustrated by the following example.</p><a name="parameter-vocabulary-extension-example-1" id="parameter-vocabulary-extension-example-1"></a><table class="example"><caption>Example Fragment – ttp:extension</caption><tbody><tr><td>
+valid.</p><p>If some well known extension is not specified by
+a <code>ttp:extension</code> element in a given profile, then it must be interpreted as if the extension were specified
+with the <code>value</code> attribute equal to <code>optional</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In particular, if some extension is not present in a profile definition, then
+it is not to be interpreted as meaning the use of that extension (in a <em>Document Instance</em>)
+is disallowed or otherwise prohibited.</p></div><p>The <code>ttp:extension</code> element is illustrated by the following example.</p><a id="parameter-vocabulary-extension-example-1"></a><table class="example"><caption>Example Fragment – ttp:extension</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttp:profile use="http://www.w3.org/ns/ttml/profile/dfxp-transformation"&gt;
-  &lt;ttp:extensions xml:base="http://foo.bar.example.org/ttaf1/extension/"&gt;
+  &lt;ttp:extensions xml:base="http://example.org/ttaf1/extension/"&gt;
     <span class="strong">&lt;ttp:extension value="use"&gt;#prefilter-by-language&lt;/ttp:extension&gt;</span>
   &lt;/ttp:extensions&gt;
 &lt;/ttp:profile&gt;
@@ -1404,13 +1425,14 @@
 specifying that support and use is required for a private extension
 defined in a third party namespace.</p><p>The effect of this example is to express authorial intentions that
 a recipient processor must support the DFXP transformation profile and
-must also support and use an extension defined by a third party.</p></div></div></div><div class="div2">
-<h3><a name="parameter-attribute-vocabulary" id="parameter-attribute-vocabulary"></a>6.2 Parameter Attribute Vocabulary</h3><p>The following attributes are defined in the TT Parameter Namespace.</p><ul><li><p><a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a></p></li><li><p><a href="#parameter-attribute-clockMode"><b>6.2.2 ttp:clockMode</b></a></p></li><li><p><a href="#parameter-attribute-dropMode"><b>6.2.3 ttp:dropMode</b></a></p></li><li><p><a href="#parameter-attribute-frameRate"><b>6.2.4 ttp:frameRate</b></a></p></li><li><p><a href="#parameter-attribute-frameRateMultiplier"><b>6.2.5 ttp:frameRateMultiplier</b></a></p></li><li><p><a href="#parameter-attribute-markerMode"><b>6.2.6 ttp:markerMode</b></a></p></li><li><p><a href="#parameter-attribute-pixelAspectRatio"><b>6.2.7 ttp:pixelAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-profile"><b>6.2.8 ttp:profile</b></a></p></li><li><p><a href="#parameter-attribute-subFrameRate"><b>6.2.9 ttp:subFrameRate</b></a></p></li><li><p><a href="#parameter-attribute-tickRate"><b>6.2.10 ttp:tickRate</b></a></p></li><li><p><a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) may
-appear between tokens of a value of a TT Parameter.</p><div class="div3">
-<h4><a name="parameter-attribute-cellResolution" id="parameter-attribute-cellResolution"></a>6.2.1 ttp:cellResolution</h4><p>The <code>ttp:cellResolution</code> attribute may be used by an author
+must also support and enable an extension defined by a third party.</p></div></div></div><div class="div2">
+<h3><a id="parameter-attribute-vocabulary"></a>6.2 Parameter Attribute Vocabulary</h3><p>The following attributes are defined in the TT Parameter Namespace.</p><ul><li><p><a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a></p></li><li><p><a href="#parameter-attribute-clockMode"><b>6.2.2 ttp:clockMode</b></a></p></li><li><p><a href="#parameter-attribute-dropMode"><b>6.2.3 ttp:dropMode</b></a></p></li><li><p><a href="#parameter-attribute-frameRate"><b>6.2.4 ttp:frameRate</b></a></p></li><li><p><a href="#parameter-attribute-frameRateMultiplier"><b>6.2.5 ttp:frameRateMultiplier</b></a></p></li><li><p><a href="#parameter-attribute-markerMode"><b>6.2.6 ttp:markerMode</b></a></p></li><li><p><a href="#parameter-attribute-pixelAspectRatio"><b>6.2.7 ttp:pixelAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-profile"><b>6.2.8 ttp:profile</b></a></p></li><li><p><a href="#parameter-attribute-subFrameRate"><b>6.2.9 ttp:subFrameRate</b></a></p></li><li><p><a href="#parameter-attribute-tickRate"><b>6.2.10 ttp:tickRate</b></a></p></li><li><p><a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) must
+appear between adjacent non-terminal components of a TT Parameter value
+unless some other delimiter is permitted and used.</p><div class="div3">
+<h4><a id="parameter-attribute-cellResolution"></a>6.2.1 ttp:cellResolution</h4><p>The <code>ttp:cellResolution</code> attribute may be used by an author
 to express the number of horizontal and vertical cells into which the root container region
 area is divided for the purpose of expressing presentation semantics in terms of
-a uniform grid.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-cellResolution-syntax" id="parameter-attribute-cellResolution-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:cellResolution</caption><tbody><tr><td>
+a uniform grid.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-cellResolution-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:cellResolution</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:cellResolution
   : columns rows                            // <em>columns</em> != 0; <em>rows</em> != 0
@@ -1434,10 +1456,10 @@
 is 20 by 10, and the root container extent is 640 by 480, then, assuming top to bottom,
 left to right writing mode, the start and end padding will be 640 / 20 * 0.1 pixels and the
 before and after padding will be 480 / 10 * 0.1 pixels.</p></div></div><div class="div3">
-<h4><a name="parameter-attribute-clockMode" id="parameter-attribute-clockMode"></a>6.2.2 ttp:clockMode</h4><p>The <code>ttp:clockMode</code> attribute is used to specify the
+<h4><a id="parameter-attribute-clockMode"></a>6.2.2 ttp:clockMode</h4><p>The <code>ttp:clockMode</code> attribute is used to specify the
 interpretation of time expressions as real-time time coordinates when
 operating with time base of <code>clock</code> as defined by <a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#timing-time-value-expressions"><b>10.3 Time Value Expressions</b></a> for the
-specification of time expression syntax.</p></div><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-clockMode-syntax" id="parameter-attribute-clockMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:clockMode</caption><tbody><tr><td>
+specification of time expression syntax and semantics.</p></div><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-clockMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:clockMode</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:clockMode
   : "local"
@@ -1463,11 +1485,11 @@
 tolerance of TAI.</p></div><p>If not specified, the value of this parameter must be considered
 to be <code>utc</code>.</p><p>A <code>ttp:clockMode</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a name="parameter-attribute-dropMode" id="parameter-attribute-dropMode"></a>6.2.3 ttp:dropMode</h4><p>The <code>ttp:dropMode</code> attribute is used to specify
+<h4><a id="parameter-attribute-dropMode"></a>6.2.3 ttp:dropMode</h4><p>The <code>ttp:dropMode</code> attribute is used to specify
 constraints on the interpretation and use of frame counts
 that correspond with <a href="#smpte12m">[SMPTE 12M]</a> time coordinates when operating
 with time base of <code>smpte</code> as defined by
-<a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-dropMode-syntax" id="parameter-attribute-dropMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:dropMode</caption><tbody><tr><td>
+<a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-dropMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:dropMode</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:dropMode
   : "dropNTSC"
@@ -1520,28 +1542,30 @@
 code, which uses PAL modulation with the NTSC frame rate of ~29.97
 frames/second. The M/PAL system is used primarily in Brazil.</p></div><p>If not specified, then <code>nonDrop</code> must be assumed to apply.</p><p>A <code>ttp:dropMode</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a name="parameter-attribute-frameRate" id="parameter-attribute-frameRate"></a>6.2.4 ttp:frameRate</h4><p>The <code>ttp:frameRate</code> attribute is used to specify the frame rate of a related
-media object or the intrinsic frame rate of a document instance in case it is intended
-to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-frameRate-syntax" id="parameter-attribute-frameRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:frameRate</caption><tbody><tr><td>
+<h4><a id="parameter-attribute-frameRate"></a>6.2.4 ttp:frameRate</h4><p>The <code>ttp:frameRate</code> attribute is used to specify the frame rate of a related
+media object or the intrinsic frame rate of a <em>Document Instance</em> in case it is intended
+to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-frameRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:frameRate</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:frameRate
   : <a href="#style-value-digit">&lt;digit&gt;</a>+                                // <em>value</em> &gt; 0
 </pre></div>
-</td></tr></tbody></table><p>The frame rate that applies to a document instance is used to
+</td></tr></tbody></table><p>The frame rate that applies to a <em>Document Instance</em> is used to
 interpret time expressions that are expressed in <em>frames</em>
-as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>A frame is interpreted as a division of a second of media
+as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>If the <code>media</code> time base applies and the effective frame rate is
+integral, then a frame is interpreted as a division of a second of media
 time, such that if the frame rate is specified as <em>F</em>, then
 a second of media time is divided into <em>F</em> intervals of
 equal duration, where each interval is labeled as frame <em>f</em>,
-with <em>f</em> ∈ [0…<em>F−1</em>].</p><p>If not specified, the frame rate must be considered to be equal to some
+with <em>f</em> ∈ [0…<em>F−1</em>].</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#time-expression-semantics-media"><b>N.2 Media Time Base</b></a> for further details
+on the interpretation of time expressions for the <code>media</code> time base.</p></div><p>If not specified, the frame rate must be considered to be equal to some
 application defined frame rate, or if no application defined frame rate applies,
 then thirty (30) frames per second. If specified, then the frame rate must
 be greater than zero (0).</p><p>A <code>ttp:frameRate</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a name="parameter-attribute-frameRateMultiplier" id="parameter-attribute-frameRateMultiplier"></a>6.2.5 ttp:frameRateMultiplier</h4><p>The <code>ttp:frameRateMultiplier</code> attribute is used to
+<h4><a id="parameter-attribute-frameRateMultiplier"></a>6.2.5 ttp:frameRateMultiplier</h4><p>The <code>ttp:frameRateMultiplier</code> attribute is used to
 specify a multiplier to be applied to the frame rate specified by a
 <code>ttp:frameRate</code> attribute in order to compute the effective
-frame rate.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-frameRateMultiplier-syntax" id="parameter-attribute-frameRateMultiplier-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:frameRateMultiplier</caption><tbody><tr><td>
+frame rate.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-frameRateMultiplier-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:frameRateMultiplier</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:frameRateMultiplier
   : numerator denominator                   // <em>numerator</em> != 0; <em>denominator</em> != 0
@@ -1561,11 +1585,11 @@
 second. Other frame rate multipliers apply to different regions of
 usage and video format standards.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Except in the case of PAL/M, the frame rate multiplier used for synchronizing with PAL
 formatted video objects at 25 frames per second is nominally 1:1.</p></div></div><div class="div3">
-<h4><a name="parameter-attribute-markerMode" id="parameter-attribute-markerMode"></a>6.2.6 ttp:markerMode</h4><p>The <code>ttp:markerMode</code> attribute is used to specify
+<h4><a id="parameter-attribute-markerMode"></a>6.2.6 ttp:markerMode</h4><p>The <code>ttp:markerMode</code> attribute is used to specify
 constraints on the interpretation and use of time expressions
 that correspond with <a href="#smpte12m">[SMPTE 12M]</a> time coordinates when operating
 with time base of <code>smpte</code> as defined by
-<a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-markerMode-syntax" id="parameter-attribute-markerMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:markerMode</caption><tbody><tr><td>
+<a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-markerMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:markerMode</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:markerMode
   : "continuous"
@@ -1633,9 +1657,9 @@
 example, two consecutive frames labeled as <code>10:00:00:00</code>
 and <code>10:00:01:00</code>.
 </p></div></div><div class="div3">
-<h4><a name="parameter-attribute-pixelAspectRatio" id="parameter-attribute-pixelAspectRatio"></a>6.2.7 ttp:pixelAspectRatio</h4><p>The <code>ttp:pixelAspectRatio</code> attribute may be used by a content author
+<h4><a id="parameter-attribute-pixelAspectRatio"></a>6.2.7 ttp:pixelAspectRatio</h4><p>The <code>ttp:pixelAspectRatio</code> attribute may be used by a content author
 to express the aspect ratio of non-square pixels in the production of content that
-makes use of pixel coordinates.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-pixelAspectRatio-syntax" id="parameter-attribute-pixelAspectRatio-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:pixelAspectRatio</caption><tbody><tr><td>
+makes use of pixel coordinates.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-pixelAspectRatio-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:pixelAspectRatio</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:pixelAspectRatio
   : width height                            // <em>width</em> != 0; <em>height</em> != 0
@@ -1648,46 +1672,50 @@
 when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This parameter may be used by a content transcoder or translator in
 order to convert pixel measurements between different pixel aspect
 ratios while still maintaining authorial layout intentions.</p></div></div><div class="div3">
-<h4><a name="parameter-attribute-profile" id="parameter-attribute-profile"></a>6.2.8 ttp:profile</h4><p>The <code>ttp:profile</code> attribute may be used by a content author
+<h4><a id="parameter-attribute-profile"></a>6.2.8 ttp:profile</h4><p>The <code>ttp:profile</code> attribute may be used by a content author
 to express the profile of the Timed Text Markup Language (TTML) used
-in a document instance.</p><p>If specified, the value of this attribute must adhere to the
+in a <em>Document Instance</em>.</p><p>If specified, the value of this attribute must adhere to the
 <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
 §3.2.17, and, further, must specify a
 profile designator in accordance with
 <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p><p>A <code>ttp:profile</code>
 attribute is considered to be significant only when specified on the
 <code>tt</code> element.</p></div><div class="div3">
-<h4><a name="parameter-attribute-subFrameRate" id="parameter-attribute-subFrameRate"></a>6.2.9 ttp:subFrameRate</h4><p>The <code>ttp:subFrameRate</code> attribute is used to specify the sub-frame rate of a related
-media object or the intrinsic sub-frame rate of a document instance in case it is intended
-to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-subFrameRate-syntax" id="parameter-attribute-subFrameRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:subFrameRate</caption><tbody><tr><td>
+<h4><a id="parameter-attribute-subFrameRate"></a>6.2.9 ttp:subFrameRate</h4><p>The <code>ttp:subFrameRate</code> attribute is used to specify the sub-frame rate of a related
+media object or the intrinsic sub-frame rate of a <em>Document Instance</em> in case it is intended
+to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-subFrameRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:subFrameRate</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:subFrameRate
   : <a href="#style-value-digit">&lt;digit&gt;</a>+                                // <em>value</em> &gt; 0
 </pre></div>
-</td></tr></tbody></table><p>The sub-frame rate that applies to a document instance is used to
+</td></tr></tbody></table><p>The sub-frame rate that applies to a <em>Document Instance</em> is used to
 interpret time expressions that are expressed in <em>sub-frames</em>
-as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>A sub-frame is interpreted as a division of a frame of media
+as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>If the <code>media</code> time base applies and the effective frame rate is
+integral, a sub-frame is interpreted as a division of a frame of media
 time, such that if the sub-frame rate is specified as <em>S</em>, then
 a frame of media time is divided into <em>S</em> intervals of
 equal duration, where each interval is labeled as sub-frame <em>s</em>,
-with <em>s</em> ∈ [0…<em>S−1</em>].</p><p>If not specified, the sub-frame rate must be considered to be
+with <em>s</em> ∈ [0…<em>S−1</em>].</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#time-expression-semantics-media"><b>N.2 Media Time Base</b></a> for further details
+on the interpretation of time expressions for the <code>media</code> time base.</p></div><p>If not specified, the sub-frame rate must be considered to be
 equal to one (1). If specified, then the sub-frame rate must be greater than zero (0).</p><p>A <code>ttp:subFrameRate</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The sub-frame is sometimes referred to as a <em>field</em> in
 the context of synchronization with an interlaced video media object.</p></div></div><div class="div3">
-<h4><a name="parameter-attribute-tickRate" id="parameter-attribute-tickRate"></a>6.2.10 ttp:tickRate</h4><p>The <code>ttp:tickRate</code> attribute is used to specify the tick rate of a related
-media object or the intrinsic tick rate of content of a document instance in case it is intended
-to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-tickRate-syntax" id="parameter-attribute-tickRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:tickRate</caption><tbody><tr><td>
+<h4><a id="parameter-attribute-tickRate"></a>6.2.10 ttp:tickRate</h4><p>The <code>ttp:tickRate</code> attribute is used to specify the tick rate of a related
+media object or the intrinsic tick rate of content of a <em>Document Instance</em> in case it is intended
+to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-tickRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:tickRate</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:tickRate
   : <a href="#style-value-digit">&lt;digit&gt;</a>+                                // <em>value</em> &gt; 0
 </pre></div>
-</td></tr></tbody></table><p>The tick rate that applies to a document instance is used to
+</td></tr></tbody></table><p>The tick rate that applies to a <em>Document Instance</em> is used to
 interpret time expressions that are expressed in <em>ticks</em> by
-using the <code>t</code> metric as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>A tick is interpreted as an integral division of a second of media
+using the <code>t</code> metric as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>If the <code>media</code> time base applies,
+a tick is interpreted as an integral division of a second of media
 time, such that if the tick rate is specified as <em>T</em>, then
 a second of media time is divided into <em>T</em> intervals of
 equal duration, where each interval is labeled as tick <em>t</em>,
-with <em>t</em> ∈ [0…<em>T−1</em>].</p><p>If not specified, then if a frame rate is specified, the tick rate
+with <em>t</em> ∈ [0…<em>T−1</em>].</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#time-expression-semantics-media"><b>N.2 Media Time Base</b></a> for further details
+on the interpretation of time expressions for the <code>media</code> time base.</p></div><p>If not specified, then if a frame rate is specified, the tick rate
 must be considered to be the effective frame rate multiplied by the
 sub-frame rate (i.e., ticks are interpreted as sub-frames); or, if no
 frame rate is specified, the tick rate must be considered to be one (1)
@@ -1697,9 +1725,9 @@
 use of fixed point arithmetic rather than fractional (and potentially
 inexact) expressions of seconds.</p></div><p>A <code>ttp:tickRate</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a name="parameter-attribute-timeBase" id="parameter-attribute-timeBase"></a>6.2.11 ttp:timeBase</h4><p>The <code>ttp:timeBase</code> attribute is used to specify the
+<h4><a id="parameter-attribute-timeBase"></a>6.2.11 ttp:timeBase</h4><p>The <code>ttp:timeBase</code> attribute is used to specify the
 temporal coordinate system by means of which time expressions are
-interpreted in a document instance.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a name="parameter-attribute-timeBase-syntax" id="parameter-attribute-timeBase-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:timeBase</caption><tbody><tr><td>
+interpreted in a <em>Document Instance</em>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-timeBase-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:timeBase</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:timeBase
   : "media"
@@ -1709,17 +1737,18 @@
 </td></tr></tbody></table><p>If the time base is designated as <code>media</code>, then a time
 expression denotes a coordinate in some media object's time line,
 where the media object may be an external media object with which the
-content of a document instance is to be synchronized, or it may
-be the content of a document instance itself in a case where
+content of a <em>Document Instance</em> is to be synchronized, or it may
+be the content of a <em>Document Instance</em> itself in a case where
 the timed text content is intended to establish an independent time
 line.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When using a media time base, if that time base is paused or
-scaled positively or negatively, then it is expected that the
+scaled positively or negatively, i.e., the media play rate is
+not unity, then it is expected that the
 presentation of associated Timed Text content will be similarly
 paused, accelerated, or decelerated, respectively. The means for
 controlling an external
 media time base is outside the scope of this specification.</p></div><p>If the time base is designated as <code>smpte</code>,
 then a time expression denotes a <a href="#smpte12m">[SMPTE 12M]</a> time
-coordinate with which the content of a document instance is to
+coordinate with which the content of a <em>Document Instance</em> is to
 be synchronized.  In this case, the value of the <code>ttp:markerMode</code> 
 and <code>ttp:dropMode</code> parameters apply, as defined by <a href="#parameter-attribute-markerMode"><b>6.2.6 ttp:markerMode</b></a> and <a href="#parameter-attribute-dropMode"><b>6.2.3 ttp:dropMode</b></a>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When the time base is designated as <code>smpte</code>,
 every time expression denotes a media marker value akin to that
@@ -1732,25 +1761,22 @@
 time lines.</p><p>If not specified, the default time base must be considered to be
 <code>media</code>.</p><p>A <code>ttp:timeBase</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p><p>When operating with either <code>media</code> or <code>smpte</code>
-time bases, a diachronic presentation of a document instance may
+time bases, a diachronic presentation of a <em>Document Instance</em> may
 be subject to transformations of the controlling time line, such as
 temporal reversal, dilation (expansion), or constriction
 (compression); however, when operating with the <code>clock</code>
 time base, no transformations are permitted, and diachronic
 presentation proceeds on a linear, monotonically increasing time line
 based on the passage of real time.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Due to there being only one time base parameter that applies to a
-given document instance, the interpretation of time expressions
-is uniform throughout the document instance.</p></div><p>When operating with the <code>clock</code> time base,
-the expression <em>media time</em> as used in this specification is
-to be interpreted as the real-time clock selected by
-<a href="#parameter-attribute-clockMode"><b>6.2.2 ttp:clockMode</b></a>.</p></div></div></div><div class="div1">
-<h2><a name="content" id="content"></a>7 Content</h2><p>This section specifies the <em>content</em> matter of the core
+given <em>Document Instance</em>, the interpretation of time expressions
+is uniform throughout the <em>Document Instance</em>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#time-expression-semantics"><b>N Time Expression Semantics</b></a> for further details
+on the interpretation of time expressions according to the designated time base.</p></div></div></div></div><div class="div1">
+<h2><a id="content"></a>7 Content</h2><p>This section specifies the <em>content</em> matter of the core
 vocabulary catalog.</p><div class="div2">
-<h3><a name="content-element-vocabulary" id="content-element-vocabulary"></a>7.1 Content Element Vocabulary</h3><p>The following elements specify the structure and principal content aspects of a
-document instance:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a></p></li><li><p><a href="#document-structure-vocabulary-head"><b>7.1.2 head</b></a></p></li><li><p><a href="#document-structure-vocabulary-body"><b>7.1.3 body</b></a></p></li><li><p><a href="#content-vocabulary-div"><b>7.1.4 div</b></a></p></li><li><p><a href="#content-vocabulary-p"><b>7.1.5 p</b></a></p></li><li><p><a href="#content-vocabulary-span"><b>7.1.6 span</b></a></p></li><li><p><a href="#content-vocabulary-br"><b>7.1.7 br</b></a></p></li></ul><div class="div3">
-<h4><a name="document-structure-vocabulary-tt" id="document-structure-vocabulary-tt"></a>7.1.1 tt</h4><p>The <code>tt</code> element serves as the root document element of a document
-instance.</p><p>The <code>tt</code> element accepts as its children zero or one <code>head</code> element followed by
-zero or one <code>body</code> element.</p><a name="elt-syntax-tt" id="elt-syntax-tt"></a><table class="syntax"><caption>XML Representation – Element Information Item: tt</caption><tbody><tr><td>
+<h3><a id="content-element-vocabulary"></a>7.1 Content Element Vocabulary</h3><p>The following elements specify the structure and principal content aspects of a
+<em>Document Instance</em>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a></p></li><li><p><a href="#document-structure-vocabulary-head"><b>7.1.2 head</b></a></p></li><li><p><a href="#document-structure-vocabulary-body"><b>7.1.3 body</b></a></p></li><li><p><a href="#content-vocabulary-div"><b>7.1.4 div</b></a></p></li><li><p><a href="#content-vocabulary-p"><b>7.1.5 p</b></a></p></li><li><p><a href="#content-vocabulary-span"><b>7.1.6 span</b></a></p></li><li><p><a href="#content-vocabulary-br"><b>7.1.7 br</b></a></p></li></ul><div class="div3">
+<h4><a id="document-structure-vocabulary-tt"></a>7.1.1 tt</h4><p>The <code>tt</code> element serves as the root document element of a <em>Document Instance</em>.</p><p>The <code>tt</code> element accepts as its children zero or one <code>head</code> element followed by
+zero or one <code>body</code> element.</p><a id="elt-syntax-tt"></a><table class="syntax"><caption>XML Representation – Element Information Item: tt</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;tt
   <a href="#style-attribute-extent">tts:extent</a> = string
@@ -1762,22 +1788,24 @@
   <em>Content:</em> <a href="#document-structure-vocabulary-head">head</a>?, <a href="#document-structure-vocabulary-body">body</a>?
 &lt;/tt&gt;
 </pre></div>
-</td></tr></tbody></table><p>The <em>Root Temporal Extent</em>, i.e., the time interval over which a document instance is active, has an implicit duration that is equal to the
-implicit duration of the <code>body</code> element of the document, if present, or zero, if not present.</p><p>If the <code>tts:extent</code> attribute is specified on the <code>tt</code>
+</td></tr></tbody></table><p>The <em>Root Temporal Extent</em>, i.e., the time interval over which a <em>Document Instance</em> is active, has an implicit duration that is equal to the
+implicit duration of the <code>body</code> element of the document, if the <code>body</code> element is present, or zero, if the <code>body</code> element is absent.</p><p>If the <code>tts:extent</code> attribute is specified on the <code>tt</code>
 element, then it must adhere to <a href="#style-attribute-extent"><b>8.2.7 tts:extent</b></a>, in which case it
-specifies the spatial extent of the root container region in
+specifies the spatial extent of the <em>Root Container Region</em> in
 which content regions are located and presented. If no <code>tts:extent</code>
-attribute is specified, then the spatial extent of the root container region is
-considered to be determined by the external authoring or presentation
-context. The root container origin is determined by the <em>Document Processing Context</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>If an author desires to signal the (storage or image) aspect ratio of the root container
-region without specifying its resolution, then this may be accomplished by using metadata specified
+attribute is specified, then the spatial extent of the <em>Root Container Region</em> is
+considered to be determined by the <em>Document Processing Context</em>.
+The origin of the <em>Root Container Region</em> is determined by the <em>Document Processing Context</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>If an author desires to signal the (storage or image) aspect ratio of the <em>Root Container Region</em>
+without specifying its resolution, then this may be accomplished by using metadata specified
 in an external namespace, such as <code>m708:aspectRatio</code> as defined in <a href="#smpte2052">[SMPTE 2052-11]</a>, §5.4.4.
 This would permit, for example, the interchange of information that reflects the
-the semantics of <a href="#cea708d">[CEA-708-D]</a> , §4.5 “Caption Service Metadata”, “ASPECT RATIO”.</p></div><p>An <code>xml:lang</code> attribute must be specified on the <code>tt</code> element.
+the semantics of <a href="#cea708d">[CEA-708-D]</a> , §4.5 “Caption Service Metadata”, “ASPECT RATIO”.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In the absence of other requirements, and if a <em>Related Media Object</em> exists, then it is recommended
+that the origin of the <em>Root Container Region</em> be established so that it is centered in the region within
+which the <em>Related Media Object</em> is presented.</p></div><p>An <code>xml:lang</code> attribute must be specified on the <code>tt</code> element.
 If the attribute value is empty, it signifies that there is no default language that applies
-to the text contained within the document instance.</p><p>If no <code>xml:space</code> attribute is specified upon the <code>tt</code> element, then it must
+to the text contained within the <em>Document Instance</em>.</p><p>If no <code>xml:space</code> attribute is specified upon the <code>tt</code> element, then it must
 be considered as if the attribute had been specified with a value of <code>default</code>.</p></div><div class="div3">
-<h4><a name="document-structure-vocabulary-head" id="document-structure-vocabulary-head"></a>7.1.2 head</h4><p>The <code>head</code> element is a container element used to group
+<h4><a id="document-structure-vocabulary-head"></a>7.1.2 head</h4><p>The <code>head</code> element is a container element used to group
 header matter, including metadata,
 profile, styling, and layout information.</p><p>The <code>head</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group,
@@ -1785,13 +1813,13 @@
 <code>Parameters.class</code> element group,
 followed by zero or one <code>styling</code> element,
 followed by zero or one <code>layout</code> element.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the document instance as a
+element group applies semantically to the <em>Document Instance</em> as a
 whole, and not just the <code>head</code> element.</p><p>Any parameters specified by children in the <code>Parameters.class</code>
-element group applies semantically to the document instance as a
+element group applies semantically to the <em>Document Instance</em> as a
 whole, and not just the <code>head</code> element.</p><p>A <code>styling</code> child element is used to specify style constructs
 that are referenced from other style constructs, by layout constructs, and by
 content elements.</p><p>A <code>layout</code> child element is used to specify layout constructs that
-are referenced by content elements.</p><a name="elt-syntax-head" id="elt-syntax-head"></a><table class="syntax"><caption>XML Representation – Element Information Item: head</caption><tbody><tr><td>
+are referenced by content elements.</p><a id="elt-syntax-head"></a><table class="syntax"><caption>XML Representation – Element Information Item: head</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;head
   <a href="#content-attribute-id">xml:id</a> = ID
@@ -1804,7 +1832,7 @@
 </td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
 <code>head</code> element, the implied time interval of this element is
 defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
-<h4><a name="document-structure-vocabulary-body" id="document-structure-vocabulary-body"></a>7.1.3 body</h4><p>The <code>body</code> element functions as a logical container and a temporal
+<h4><a id="document-structure-vocabulary-body"></a>7.1.3 body</h4><p>The <code>body</code> element functions as a logical container and a temporal
 structuring element for a sequence of textual content units represented as
 logical divisions.</p><p>The <code>body</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group,
@@ -1813,7 +1841,7 @@
 followed by
 zero or more <code>div</code> elements.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
 element group applies semantically to the <code>body</code> element and its descendants as a whole.</p><p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <code>body</code> element.</p><a name="elt-syntax-body" id="elt-syntax-body"></a><table class="syntax"><caption>XML Representation – Element Information Item: body</caption><tbody><tr><td>
+element group apply semantically to the <code>body</code> element.</p><a id="elt-syntax-body"></a><table class="syntax"><caption>XML Representation – Element Information Item: body</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;body
   <a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>
@@ -1835,7 +1863,7 @@
 the <code>begin</code>, <code>dur</code>, and <code>end</code> attributes. If the begin point
 of this interval remains unspecified, then the begin point is interpreted as the beginning
 point of the <em>Root Temporal Extent</em>. Similarly, if the end point of this interval remains unspecified, then the
-end point is interpreted as the ending point of the <em>Root Temporal Extent</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A TTML document instance referenced from a SMIL presentation
+end point is interpreted as the ending point of the <em>Root Temporal Extent</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <em>Document Instance</em> referenced from a SMIL presentation
 is expected to follow the same timing rules as apply to other SMIL media
 objects.</p></div><p>If relative begin or end times are specified on the <code>body</code>
 element, then these times are resolved by reference to the beginning and
@@ -1844,14 +1872,14 @@
 truncated to the active end point of the <em>Root Temporal Extent</em>.</p><p>An author may associate a set of style properties with a
 <code>body</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>body</code> element
-in a document instance are available for style inheritance by
+in a <em>Document Instance</em> are available for style inheritance by
 descendant content elements such as <code>div</code>, <code>p</code>,
 <code>span</code>
 and <code>br</code>.</p></div><p>If no <code>timeContainer</code> attribute is specified on a
 <code>body</code> element, then it must be interpreted as having
 <em>parallel</em>
 time containment semantics.</p></div><div class="div3">
-<h4><a name="content-vocabulary-div" id="content-vocabulary-div"></a>7.1.4 div</h4><p>The <code>div</code> element functions as a logical container and a temporal
+<h4><a id="content-vocabulary-div"></a>7.1.4 div</h4><p>The <code>div</code> element functions as a logical container and a temporal
 structuring element for a sequence of textual content units represented as
 logical sub-divisions or paragraphs.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When rendered on a continuous (non-paged) visual presentation medium,
 a <code>div</code> element is expected to generate
@@ -1872,7 +1900,7 @@
 <code>div</code> or 
 <code>p</code> elements.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
 element group applies semantically to the <code>div</code> element and its descendants as a whole.</p><p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <code>div</code> element.</p><a name="elt-syntax-div" id="elt-syntax-div"></a><table class="syntax"><caption>XML Representation – Element Information Item: div</caption><tbody><tr><td>
+element group apply semantically to the <code>div</code> element.</p><a id="elt-syntax-div"></a><table class="syntax"><caption>XML Representation – Element Information Item: div</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;div
   <a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>
@@ -1893,7 +1921,7 @@
 </td></tr></tbody></table><p>An author may associate a set of style properties with a <code>div</code> element by means of either
 the <code>style</code> attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated
 with
-a <code>div</code> element in a document instance
+a <code>div</code> element in a <em>Document Instance</em>
 are available for style inheritance by descendant content elements such as
 <code>div</code>, 
 <code>p</code>,
@@ -1901,18 +1929,18 @@
 <code>br</code>.</p></div><p>If no <code>timeContainer</code> attribute is specified on
 a <code>div</code> element, then it must be interpreted as having
 <em>parallel</em> time containment semantics.</p></div><div class="div3">
-<h4><a name="content-vocabulary-p" id="content-vocabulary-p"></a>7.1.5 p</h4><p>A <code>p</code> element represents a logical paragraph, serving as
+<h4><a id="content-vocabulary-p"></a>7.1.5 p</h4><p>A <code>p</code> element represents a logical paragraph, serving as
 a transition between block level and inline level formatting semantics.</p><p>The <code>p</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group,
 followed by zero or more
 elements in the <code>Animation.class</code> element group,
 followed by
-zero or more
-<code>span</code> element,
-<code>br</code> element,
-or text nodes interpreted as anonymous spans.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
+zero or more intermixed
+<code>span</code> elements,
+<code>br</code> elements,
+or text nodes interpreted as an anonymous spans.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
 element group applies semantically to the <code>p</code> element and its descendants as a whole.</p><p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <code>p</code> element.</p><a name="elt-syntax-p" id="elt-syntax-p"></a><table class="syntax"><caption>XML Representation – Element Information Item: p</caption><tbody><tr><td>
+element group apply semantically to the <code>p</code> element.</p><a id="elt-syntax-p"></a><table class="syntax"><caption>XML Representation – Element Information Item: p</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;p
   <a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>
@@ -1933,7 +1961,7 @@
 </td></tr></tbody></table><p>An author may associate a set of style properties with a
 <code>p</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>p</code> element
-in a document instance are available for style inheritance by
+in a <em>Document Instance</em> are available for style inheritance by
 descendant content elements such as <code>span</code> and
 <code>br</code>.</p></div><p>If no <code>timeContainer</code> attribute is specified on
 a <code>p</code> element, then it must be interpreted as having
@@ -1945,7 +1973,7 @@
 it is associated with a block-stacking constraint both before the first
 generated line area and after the last generated line area. See
 <a href="#semantics-region-layout-step-2"><b>9.3.3 Synchronic Flow Processing</b></a> for further details.</p></div></div><div class="div3">
-<h4><a name="content-vocabulary-span" id="content-vocabulary-span"></a>7.1.6 span</h4><p>The <code>span</code> element functions as a logical container and a temporal
+<h4><a id="content-vocabulary-span"></a>7.1.6 span</h4><p>The <code>span</code> element functions as a logical container and a temporal
 structuring element for a sequence of textual content units having inline
 level formatting semantics.</p><p>When presented on a visual medium, a <code>span</code> element is intended to
 generate a sequence of inline areas, each containing one or more glyph areas.</p><p>The <code>span</code> element accepts as its children zero or more
@@ -1953,12 +1981,12 @@
 followed by zero or more
 elements in the <code>Animation.class</code> element group,
 followed by
-zero or more
+zero or more intermixed
 <code>span</code> elements,
 <code>br</code> elements,
 or text nodes interpreted as anonymous spans.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
 element group applies semantically to the <code>span</code> element and its descendants as a whole.</p><p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <code>span</code> element.</p><a name="elt-syntax-span" id="elt-syntax-span"></a><table class="syntax"><caption>XML Representation – Element Information Item: span</caption><tbody><tr><td>
+element group apply semantically to the <code>span</code> element.</p><a id="elt-syntax-span"></a><table class="syntax"><caption>XML Representation – Element Information Item: span</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;span
   <a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>
@@ -1979,12 +2007,12 @@
 </td></tr></tbody></table><p>An author may associate a set of style properties with a
 <code>span</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>span</code> element
-in a document instance are available for style inheritance by
+in a <em>Document Instance</em> are available for style inheritance by
 descendant content elements such as <code>span</code> and
 <code>br</code>.</p></div><p>If no <code>timeContainer</code> attribute is specified on
 a <code>span</code> element, then it must be interpreted as having
 <em>parallel</em> time containment semantics.</p></div><div class="div3">
-<h4><a name="content-vocabulary-br" id="content-vocabulary-br"></a>7.1.7 br</h4><p>The <code>br</code> element denotes an explicit line break.</p><a name="elt-syntax-br" id="elt-syntax-br"></a><table class="syntax"><caption>XML Representation – Element Information Item: br</caption><tbody><tr><td>
+<h4><a id="content-vocabulary-br"></a>7.1.7 br</h4><p>The <code>br</code> element denotes an explicit line break.</p><a id="elt-syntax-br"></a><table class="syntax"><caption>XML Representation – Element Information Item: br</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;br
   <a href="#style-attribute-style">style</a> = IDREFS
@@ -2001,22 +2029,22 @@
 interpreted as a forced line break.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The visual presentation of a <code>br</code> element is
 intended to produce the same effect as the control character
 <code>CR</code> (U+000D)
-followed by the control code <code>NL</code> (U+000A) when presented on a teletype device.
+followed by the control code <code>LF</code> (U+000A) when presented on a teletype device.
 Therefore, two <code>br</code> elements in sequence will produce a
 different effect than a single <code>br</code> element.</p></div></div></div><div class="div2">
-<h3><a name="content-attribute-vocabulary" id="content-attribute-vocabulary"></a>7.2 Content Attribute Vocabulary</h3><p>This section defines the following common attributes used with many or all element types
+<h3><a id="content-attribute-vocabulary"></a>7.2 Content Attribute Vocabulary</h3><p>This section defines the following common attributes used with many or all element types
 in the core vocabulary catalog:</p><ul><li><p><a href="#content-attribute-id"><b>7.2.1 xml:id</b></a></p></li><li><p><a href="#content-attribute-lang"><b>7.2.2 xml:lang</b></a></p></li><li><p><a href="#content-attribute-space"><b>7.2.3 xml:space</b></a></p></li></ul><div class="div3">
-<h4><a name="content-attribute-id" id="content-attribute-id"></a>7.2.1 xml:id</h4><p>The <code>xml:id</code> attribute is used as defined by
+<h4><a id="content-attribute-id"></a>7.2.1 xml:id</h4><p>The <code>xml:id</code> attribute is used as defined by
 <a href="#xmlid">[XML ID]</a>.</p><p>The <code>xml:id</code> attribute may be used with any element in the
 core vocabulary catalog.</p></div><div class="div3">
-<h4><a name="content-attribute-lang" id="content-attribute-lang"></a>7.2.2 xml:lang</h4><p>The <code>xml:lang</code> attribute is used as defined by
+<h4><a id="content-attribute-lang"></a>7.2.2 xml:lang</h4><p>The <code>xml:lang</code> attribute is used as defined by
 <a href="#xml10">[XML 1.0]</a>, §2.12, <em>Language Identification</em>.</p><p>The <code>xml:lang</code> attribute must be specified on the <code>tt</code>
 element and may be specified by an instance of any other element type
 in the core vocabulary catalog.</p></div><div class="div3">
-<h4><a name="content-attribute-space" id="content-attribute-space"></a>7.2.3 xml:space</h4><p>The <code>xml:space</code> attribute is used as defined by
+<h4><a id="content-attribute-space"></a>7.2.3 xml:space</h4><p>The <code>xml:space</code> attribute is used as defined by
 <a href="#xml10">[XML 1.0]</a>, §2.10, <em>White Space Handling</em>.</p><p>The <code>xml:space</code> attribute may be used with any element in
 the core vocabulary catalog.</p><p>The semantics of the value <code>default</code> are fixed to mean that
-when performing presentation processing of a document instance as
+when performing presentation processing of a <em>Document Instance</em> as
 described by <a href="#semantics-region-layout-step-2"><b>9.3.3 Synchronic Flow Processing</b></a>,
 processing must occur as
 if the following properties were specified on the affected
@@ -2033,7 +2061,7 @@
 of processing, the treatment of the <code>xml:space</code> attribute
 is processor dependent, but should respect the semantics described
 above if possible.</p></div></div></div><div class="div1">
-<h2><a name="styling" id="styling"></a>8 Styling</h2><p>This section specifies the <em>styling</em> matter of the core
+<h2><a id="styling"></a>8 Styling</h2><p>This section specifies the <em>styling</em> matter of the core
 vocabulary catalog, where
 styling is to be understood as a separable layer of information that applies to
 content and that denotes authorial intentions about the presentation of
@@ -2041,7 +2069,7 @@
     Styling attributes are included in TTML to enable authorial intent of presentation
     to be included within a self-contained document. This section describes
     the semantics of style presentation in terms of a standard processing
-    model. TTML Processors are not required to present TTML documents in any particular way; 
+    model. TTML Processors are not required to present <em>Document Instances</em> in any particular way; 
     but an implementation of this model by a TTML Presentation Processor
     that provides externally observable results that are consistent with this model is
     likely to lead to a user experience that closely resembles the experience intended by
@@ -2056,12 +2084,12 @@
   </p><p>No normative use of an
 <code>&lt;?xml-stylesheet ... ?&gt;</code> processing instruction is defined
 by this specification.</p><div class="div2">
-<h3><a name="styling-element-vocabulary" id="styling-element-vocabulary"></a>8.1 Styling Element Vocabulary</h3><p>The following elements specify the structure and principal styling aspects of a
-document instance:</p><ul><li><p><a href="#styling-vocabulary-styling"><b>8.1.1 styling</b></a></p></li><li><p><a href="#styling-vocabulary-style"><b>8.1.2 style</b></a></p></li></ul><div class="div3">
-<h4><a name="styling-vocabulary-styling" id="styling-vocabulary-styling"></a>8.1.1 styling</h4><p>The <code>styling</code> element is a container element used to group
+<h3><a id="styling-element-vocabulary"></a>8.1 Styling Element Vocabulary</h3><p>The following elements specify the structure and principal styling aspects of a
+<em>Document Instance</em>:</p><ul><li><p><a href="#styling-vocabulary-styling"><b>8.1.1 styling</b></a></p></li><li><p><a href="#styling-vocabulary-style"><b>8.1.2 style</b></a></p></li></ul><div class="div3">
+<h4><a id="styling-vocabulary-styling"></a>8.1.1 styling</h4><p>The <code>styling</code> element is a container element used to group
 styling matter, including metadata that applies to styling matter.</p><p>The <code>styling</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group, followed by
-zero or more <code>style</code> elements.</p><a name="elt-syntax-styling" id="elt-syntax-styling"></a><table class="syntax"><caption>XML Representation – Element Information Item: styling</caption><tbody><tr><td>
+zero or more <code>style</code> elements.</p><a id="elt-syntax-styling"></a><table class="syntax"><caption>XML Representation – Element Information Item: styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;styling
   <a href="#content-attribute-id">xml:id</a> = ID
@@ -2074,10 +2102,10 @@
 </td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
 <code>styling</code> element, the implied time interval of this element is
 defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
-<h4><a name="styling-vocabulary-style" id="styling-vocabulary-style"></a>8.1.2 style</h4><p>The <code>style</code> element is used to define
+<h4><a id="styling-vocabulary-style"></a>8.1.2 style</h4><p>The <code>style</code> element is used to define
 a set of style specifications expressed as a
 specified style set in accordance with
-<a href="#semantics-style-resolution-processing-sss"><b>8.4.4.2 Specified Style Set Processing</b></a>.</p><p>The <code>style</code> element accepts as its children zero or more <code>metadata</code> elements.</p><a name="elt-syntax-style" id="elt-syntax-style"></a><table class="syntax"><caption>XML Representation – Element Information Item: style</caption><tbody><tr><td>
+<a href="#semantics-style-resolution-processing-sss"><b>8.4.4.2 Specified Style Set Processing</b></a>.</p><p>The <code>style</code> element accepts as its children zero or more <code>metadata</code> elements.</p><a id="elt-syntax-style"></a><table class="syntax"><caption>XML Representation – Element Information Item: style</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;style
   <a href="#style-attribute-style">style</a> = IDREFS
@@ -2086,8 +2114,7 @@
   <a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
   {<em>any attribute in TT Style namespace</em>}
   {<em>any attribute not in default or any TT namespace</em>}&gt;
-  
-  <em>Content:</em> EMPTY
+ <em>Content:</em> EMPTY
 &lt;/style&gt;
 </pre></div>
 </td></tr></tbody></table><p>If a <code>style</code> element appears as a descendant of a
@@ -2096,14 +2123,17 @@
 <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a> and <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>That is to say, when referential styling is used by an element to
 refer to a <code>style</code> element, then the referenced <code>style</code>
 element must appear as a descendant of the <code>styling</code> element, and
-not in any other context.</p></div></div></div><div class="div2">
-<h3><a name="styling-attribute-vocabulary" id="styling-attribute-vocabulary"></a>8.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>8.2.1 style</b></a> attribute used
+not in any other context.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In this version of this specification, the <code>style</code> element is the
+only non-metadata element that is not defined to accept <code>Metadata.class</code>
+children. It is expected that this asymmetry will be corrected in the next
+revision of this specification.</p></div></div></div><div class="div2">
+<h3><a id="styling-attribute-vocabulary"></a>8.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>8.2.1 style</b></a> attribute used
 with both style definition elements as well as content elements.</p><p>In addition, this section specifies the following attributes in the TT Style Namespace
 for use with style definition elements, certain layout elements, and content elements
-that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>8.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-color"><b>8.2.3 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>8.2.4 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>8.2.5 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>8.2.6 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>8.2.7 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>8.2.8 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>8.2.9 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>8.2.10 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>8.2.11 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>8.2.12 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>8.2.13 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>8.2.14 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>8.2.15 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>8.2.16 tts:padding</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>8.2.17 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>8.2.18 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>8.2.19 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>8.2.20 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>8.2.21 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>8.2.22 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>8.2.23 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>8.2.24 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>8.2.25 tts:zIndex</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) may
-appear between tokens of a value of a TT
+that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>8.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-color"><b>8.2.3 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>8.2.4 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>8.2.5 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>8.2.6 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>8.2.7 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>8.2.8 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>8.2.9 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>8.2.10 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>8.2.11 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>8.2.12 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>8.2.13 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>8.2.14 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>8.2.15 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>8.2.16 tts:padding</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>8.2.17 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>8.2.18 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>8.2.19 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>8.2.20 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>8.2.21 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>8.2.22 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>8.2.23 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>8.2.24 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>8.2.25 tts:zIndex</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) must
+appear between adjacent non-terminal components of a value of a TT
 Style or TT Style Extension
-Property.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification makes use of <em>lowerCamelCased</em> local
+Property value unless some other delimiter is permitted and used.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification makes use of <em>lowerCamelCased</em> local
 names for style attributes that
 are based upon like-named properties defined by <a href="#xsl11">[XSL 1.1]</a>.
 This convention is likewise extended to token values of such
@@ -2112,20 +2142,22 @@
 element type. This capability permits the expression of an inheritable
 style property on ancestor elements to which the property
 does not apply.</p></div><div class="div3">
-<h4><a name="style-attribute-style" id="style-attribute-style"></a>8.2.1 style</h4><p>The <code>style</code> attribute is used
+<h4><a id="style-attribute-style"></a>8.2.1 style</h4><p>The <code>style</code> attribute is used
 by referential style association
 to reference one or more <code>style</code>
 elements each of which define a
 specified
 style set.</p><p>The <code>style</code> attribute may be specified by an instance of the following
-element types:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>See the specific element type definitions that permit use of the
+element types:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li></ul><p>If specified, the value of a <code>style</code> attribute must
+adhere to the <code>IDREFS</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
+§ 3.3.10.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See the specific element type definitions that permit use of the
 <code>style</code> attribute, as well as <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a> and <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>, for
 further information on its semantics.</p></div></div><div class="div3">
-<h4><a name="style-attribute-backgroundColor" id="style-attribute-backgroundColor"></a>8.2.2 tts:backgroundColor</h4><p>The <code>tts:backgroundColor</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-backgroundColor"></a>8.2.2 tts:backgroundColor</h4><p>The <code>tts:backgroundColor</code> attribute is used to specify a style property that
 defines the background color of a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-backgroundColor" id="style-property-details-backgroundColor"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-backgroundColor"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <a href="#style-value-color">&lt;color&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td><code>transparent</code></td></tr><tr><td><em>Applies to:</em></td><td>
 <a href="#document-structure-vocabulary-body"><code>body</code></a>,
@@ -2135,7 +2167,7 @@
 <a href="#content-vocabulary-span"><code>span</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
 each character child of a <code>p</code> element is considered to be enclosed in an anonymous
-span.</p><p>The <code>tts:backgroundColor</code> style is illustrated by the following example.</p><a name="style-attribute-backgroundColor-example-1" id="style-attribute-backgroundColor-example-1"></a><table class="example"><caption>Example Fragment – Background Color</caption><tbody><tr><td>
+span.</p><p>The <code>tts:backgroundColor</code> style is illustrated by the following example.</p><a id="style-attribute-backgroundColor-example-1"></a><table class="example"><caption>Example Fragment – Background Color</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="306px 114px"/&gt;
@@ -2150,12 +2182,12 @@
   How &lt;span <span class="strong">tts:backgroundColor="green"</span>&gt;I wonder&lt;/span&gt; where you're at!
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-backgroundColor-example-1-images" id="style-attribute-backgroundColor-example-1-images"></a><table class="example-images"><caption>Example Rendition – Background Color</caption><tbody><tr><td><img src="images/backgroundColor.png" alt="TTML backgroundColor style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-color" id="style-attribute-color"></a>8.2.3 tts:color</h4><p>The <code>tts:color</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-backgroundColor-example-1-images"></a><table class="example-images"><caption>Example Rendition – Background Color</caption><tbody><tr><td><img src="images/backgroundColor.png" alt="TTML backgroundColor style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-color"></a>8.2.3 tts:color</h4><p>The <code>tts:color</code> attribute is used to specify a style property that
 defines the foreground color of marks associated with an area generated by content flowed into a region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-color" id="style-property-details-color"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-color"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <a href="#style-value-color">&lt;color&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td>see prose</td></tr><tr><td><em>Applies to:</em></td><td>
 <a href="#content-vocabulary-span"><code>span</code></a>
@@ -2165,7 +2197,7 @@
 is considered to be implementation dependent. In the absence of
 end-user preference information, a conformant presentation processor
 should use an initial value that is highly contrastive to the
-background color of the root container region.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><a name="style-attribute-color-example-1" id="style-attribute-color-example-1"></a><table class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
+background color of the root container region.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><a id="style-attribute-color-example-1"></a><table class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:backgroundColor="black"/&gt;
@@ -2179,13 +2211,13 @@
   I'll try and tell you what I mean.
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-color-example-1-images" id="style-attribute-color-example-1-images"></a><table class="example-images"><caption>Example Rendition – Color</caption><tbody><tr><td><img src="images/color.png" alt="TTML color style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-direction" id="style-attribute-direction"></a>8.2.4 tts:direction</h4><p>The <code>tts:direction</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-color-example-1-images"></a><table class="example-images"><caption>Example Rendition – Color</caption><tbody><tr><td><img src="images/color.png" alt="TTML color style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-direction"></a>8.2.4 tts:direction</h4><p>The <code>tts:direction</code> attribute is used to specify a style property that
 defines the directionality of an embedding or override according to
 the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-direction" id="style-property-details-direction"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-direction"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>ltr</code> |
 <code>rtl</code>
 </td></tr><tr><td><em>Initial:</em></td><td>
@@ -2196,7 +2228,7 @@
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
 each character child of a <code>p</code> element is considered to be enclosed in an anonymous
 span.</p><p>If a specified value of this attribute is not supported,
-then a presentation processor must ignore the attribute.</p><p>The <code>tts:direction</code> style is illustrated by the following example.</p><a name="style-attribute-direction-example-1" id="style-attribute-direction-example-1"></a><table class="example"><caption>Example Fragment – Direction</caption><tbody><tr><td>
+then a presentation processor must ignore the attribute.</p><p>The <code>tts:direction</code> style is illustrated by the following example.</p><a id="style-attribute-direction-example-1"></a><table class="example"><caption>Example Fragment – Direction</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="265px 84px"/&gt;
@@ -2213,15 +2245,15 @@
   &lt;span tts:unicodeBidi="bidiOverride" <span class="strong">tts:direction="rtl"</span>&gt;where the tourists snore.&lt;/span&gt;
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-direction-example-1-images" id="style-attribute-direction-example-1-images"></a><table class="example-images"><caption>Example Rendition – Direction</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><a id="style-attribute-direction-example-1-images"></a><table class="example-images"><caption>Example Rendition – Direction</caption><tbody><tr><td>
 <img src="images/direction.png" alt="TTML direction style property">
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-display" id="style-attribute-display"></a>8.2.5 tts:display</h4><p>The <code>tts:display</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-display"></a>8.2.5 tts:display</h4><p>The <code>tts:display</code> attribute is used to specify a style property that
 defines whether an element is a candidate for layout and composition
 in a region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-display" id="style-property-details-display"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-display"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>auto</code> |
 <code>none</code>
 </td></tr><tr><td><em>Initial:</em></td><td>
@@ -2238,7 +2270,7 @@
 then the affected element is a candidate for region layout and
 presentation; however, if the value is <code>none</code>, then the
 affected element and its descendants must be considered ineligible for region
-layout and presentation.</p><p>The <code>tts:display</code> style is illustrated by the following example.</p><a name="style-attribute-display-example-1" id="style-attribute-display-example-1"></a><table class="example"><caption>Example Fragment – Display</caption><tbody><tr><td>
+layout and presentation.</p><p>The <code>tts:display</code> style is illustrated by the following example.</p><a id="style-attribute-display-example-1"></a><table class="example"><caption>Example Fragment – Display</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="369px 119px"
@@ -2267,7 +2299,7 @@
   &lt;/p&gt;
 &lt;/div&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-display-example-1-images" id="style-attribute-display-example-1-images"></a><table class="example-images"><caption>Example Rendition – Display</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><a id="style-attribute-display-example-1-images"></a><table class="example-images"><caption>Example Rendition – Display</caption><tbody><tr><td>
 <img src="images/display_0.png" alt="TTML display style property - [0,1)">
 </td></tr><tr><td>
 <img src="images/display_1.png" alt="TTML display style property - [1,2)">
@@ -2278,11 +2310,11 @@
 </td></tr><tr><td>
 <img src="images/display_4.png" alt="TTML display style property - [4,5)">
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-displayAlign" id="style-attribute-displayAlign"></a>8.2.6 tts:displayAlign</h4><p>The <code>tts:displayAlign</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-displayAlign"></a>8.2.6 tts:displayAlign</h4><p>The <code>tts:displayAlign</code> attribute is used to specify a style property that
 defines the alignment of block areas in the block progression direction.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-displayAlign" id="style-property-details-displayAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-displayAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>before</code> |
 <code>center</code> |
 <code>after</code>
@@ -2292,7 +2324,7 @@
 <a href="#layout-vocabulary-region"><code>region</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>before</code> were specified.</p><p>The <code>tts:displayAlign</code> style is illustrated by the following example.</p><a name="style-attribute-displayAlign-example-1" id="style-attribute-displayAlign-example-1"></a><table class="example"><caption>Example Fragment – Display Align</caption><tbody><tr><td>
+value <code>before</code> were specified.</p><p>The <code>tts:displayAlign</code> style is illustrated by the following example.</p><a id="style-attribute-displayAlign-example-1"></a><table class="example"><caption>Example Fragment – Display Align</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="128px 66px" tts:origin="0px 0px"
@@ -2326,13 +2358,13 @@
   &lt;p region="r4"&gt;They sent an&lt;br/&gt; answer back to me.&lt;/p&gt;
 &lt;/div&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-displayAlign-example-1-images" id="style-attribute-displayAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Display Align</caption><tbody><tr><td><img src="images/displayAlign.png" alt="TTML displayAlign style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-extent" id="style-attribute-extent"></a>8.2.7 tts:extent</h4><p>The <code>tts:extent</code> attribute is used to specify the
+</td></tr></tbody></table><p></p><a id="style-attribute-displayAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Display Align</caption><tbody><tr><td><img src="images/displayAlign.png" alt="TTML displayAlign style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-extent"></a>8.2.7 tts:extent</h4><p>The <code>tts:extent</code> attribute is used to specify the
 <em>width</em> and <em>height</em> of a region area
 (which may be the root container region).</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-extent" id="style-property-details-extent"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-extent"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>auto</code> |
 <a href="#style-value-length">&lt;length&gt;</a> <a href="#style-value-length">&lt;length&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -2360,7 +2392,7 @@
 these specifications must be expressed as non-percentage,
 definite lengths using pixel units.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>auto</code> were specified.</p><p>The <code>tts:extent</code> style is illustrated by the following example.</p><a name="style-attribute-extent-example-1" id="style-attribute-extent-example-1"></a><table class="example"><caption>Example Fragment – Extent</caption><tbody><tr><td>
+value <code>auto</code> were specified.</p><p>The <code>tts:extent</code> style is illustrated by the following example.</p><a id="style-attribute-extent-example-1"></a><table class="example"><caption>Example Fragment – Extent</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style <span class="strong">tts:extent="330px 122px"</span>/&gt;
@@ -2377,13 +2409,13 @@
   I must sugar my hair."
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-extent-example-1-images" id="style-attribute-extent-example-1-images"></a><table class="example-images"><caption>Example Rendition – Extent</caption><tbody><tr><td><img src="images/extent.png" alt="TTML extent style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-fontFamily" id="style-attribute-fontFamily"></a>8.2.8 tts:fontFamily</h4><p>The <code>tts:fontFamily</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-extent-example-1-images"></a><table class="example-images"><caption>Example Rendition – Extent</caption><tbody><tr><td><img src="images/extent.png" alt="TTML extent style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-fontFamily"></a>8.2.8 tts:fontFamily</h4><p>The <code>tts:fontFamily</code> attribute is used to specify a style property that
 defines the font family from which glyphs are selected for glyph areas generated
 by content flowed into a region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-fontFamily" id="style-property-details-fontFamily"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-fontFamily"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 (<a href="#style-value-familyName">&lt;familyName&gt;</a> | <a href="#style-value-genericFamilyName">&lt;genericFamilyName&gt;</a>)
 (<code>","</code>
 &nbsp;(<a href="#style-value-familyName">&lt;familyName&gt;</a> | <a href="#style-value-genericFamilyName">&lt;genericFamilyName&gt;</a>))*
@@ -2397,7 +2429,7 @@
 to an available font family that has similar typographic
 characteristics, or, in the absence of such a mapping, it must
 interpret the font family as if the value <code>default</code> were
-specified.</p><p>The <code>tts:fontFamily</code> style is illustrated by the following example.</p><a name="style-attribute-fontFamily-example-1" id="style-attribute-fontFamily-example-1"></a><table class="example"><caption>Example Fragment – Font Family</caption><tbody><tr><td>
+specified.</p><p>The <code>tts:fontFamily</code> style is illustrated by the following example.</p><a id="style-attribute-fontFamily-example-1"></a><table class="example"><caption>Example Fragment – Font Family</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="474px 146px"/&gt;
@@ -2423,14 +2455,14 @@
   &lt;/p&gt;
 &lt;/div&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-fontFamily-example-1-images" id="style-attribute-fontFamily-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Family</caption><tbody><tr><td><img src="images/fontFamily.png" alt="TTML fontFamily style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-fontSize" id="style-attribute-fontSize"></a>8.2.9 tts:fontSize</h4><p>The <code>tts:fontSize</code> attribute is used to specify a style property
+</td></tr></tbody></table><p></p><a id="style-attribute-fontFamily-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Family</caption><tbody><tr><td><img src="images/fontFamily.png" alt="TTML fontFamily style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-fontSize"></a>8.2.9 tts:fontSize</h4><p>The <code>tts:fontSize</code> attribute is used to specify a style property
 that defines the font size for glyphs that are selected for glyph areas
 generated by content flowed into a region, where font size is interpreted as a
 scaling transform to the font's design EM square.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-fontSize" id="style-property-details-fontSize"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-fontSize"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <a href="#style-value-length">&lt;length&gt;</a> <a href="#style-value-length">&lt;length&gt;</a>?
 </td></tr><tr><td><em>Initial:</em></td><td><code>1c</code></td></tr><tr><td><em>Applies to:</em></td><td>
 <a href="#content-vocabulary-span"><code>span</code></a>
@@ -2445,7 +2477,7 @@
 span.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
 value <code>1c</code> were specified.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
-the <em>cell</em> length unit as defined by <a href="#style-value-length"><b>8.3.9 &lt;length&gt;</b></a>.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a name="style-attribute-fontSize-example-1" id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
+the <em>cell</em> length unit as defined by <a href="#style-value-length"><b>8.3.9 &lt;length&gt;</b></a>.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="299px 97px"/&gt;
@@ -2464,15 +2496,15 @@
   that is &lt;span <span class="strong">tts:fontSize="24px"</span>&gt;pleasant&lt;/span&gt; to drink.
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-fontSize-example-1-images" id="style-attribute-fontSize-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Size</caption><tbody><tr><td><img src="images/fontSize.png" alt="TTML fontSize style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-fontStyle" id="style-attribute-fontStyle"></a>8.2.10 tts:fontStyle</h4><p>The <code>tts:fontStyle</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-fontSize-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Size</caption><tbody><tr><td><img src="images/fontSize.png" alt="TTML fontSize style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-fontStyle"></a>8.2.10 tts:fontStyle</h4><p>The <code>tts:fontStyle</code> attribute is used to specify a style property that
 defines the font style to apply to glyphs that are selected for glyph areas generated
 by content flowed into a region, where the mapping from font
 style value to specific font face or style parameterization is not determined
 by this specification.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-fontStyle" id="style-property-details-fontStyle"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-fontStyle"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>normal</code> |
 <code>italic</code> |
 <code>oblique</code>
@@ -2487,7 +2519,7 @@
 to an available font style that has similar typographic
 characteristics, or, in the absence of such a mapping, it must
 interpret the font style as if the value <code>normal</code> were
-specified.</p><p>The <code>tts:fontStyle</code> style is illustrated by the following example.</p><a name="style-attribute-fontStyle-example-1" id="style-attribute-fontStyle-example-1"></a><table class="example"><caption>Example Fragment – Font Style</caption><tbody><tr><td>
+specified.</p><p>The <code>tts:fontStyle</code> style is illustrated by the following example.</p><a id="style-attribute-fontStyle-example-1"></a><table class="example"><caption>Example Fragment – Font Style</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="331px 84px"/&gt;
@@ -2503,15 +2535,15 @@
   Take pen and ink, and &lt;span <span class="strong">tts:fontStyle="italic"</span>&gt;write it down.&lt;/span&gt;
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-fontStyle-example-1-images" id="style-attribute-fontStyle-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Style</caption><tbody><tr><td><img src="images/fontStyle.png" alt="TTML fontStyle style property"></td></tr></tbody></table><p></p></div><div class="div3">
-<h4><a name="style-attribute-fontWeight" id="style-attribute-fontWeight"></a>8.2.11 tts:fontWeight</h4><p>The <code>tts:fontWeight</code> attribute is used to specify a style property
+</td></tr></tbody></table><p></p><a id="style-attribute-fontStyle-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Style</caption><tbody><tr><td><img src="images/fontStyle.png" alt="TTML fontStyle style property"></td></tr></tbody></table><p></p></div><div class="div3">
+<h4><a id="style-attribute-fontWeight"></a>8.2.11 tts:fontWeight</h4><p>The <code>tts:fontWeight</code> attribute is used to specify a style property
 that defines the font weight to apply to glyphs that are selected for glyph
 areas generated by content flowed into a region, where the mapping from font
 weight value to specific font face or weight parameterization is not determined
 by this specification.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-fontWeight" id="style-property-details-fontWeight"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-fontWeight"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>normal</code> |
 <code>bold</code>
 </td></tr><tr><td><em>Initial:</em></td><td><code>normal</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -2523,7 +2555,7 @@
 to an available font weight that has similar typographic
 characteristics, or, in the absence of such a mapping, it must
 interpret the font weight as if the value <code>normal</code> were
-specified.</p><p>The <code>tts:fontWeight</code> style is illustrated by the following example.</p><a name="style-attribute-fontWeight-example-1" id="style-attribute-fontWeight-example-1"></a><table class="example"><caption>Example Fragment – Font Weight</caption><tbody><tr><td>
+specified.</p><p>The <code>tts:fontWeight</code> style is illustrated by the following example.</p><a id="style-attribute-fontWeight-example-1"></a><table class="example"><caption>Example Fragment – Font Weight</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="376px 95px"/&gt;
@@ -2541,12 +2573,12 @@
   &lt;span <span class="strong">tts:fontWeight="bold"</span>&gt;but said I could not swim.&lt;/span&gt;
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-fontWeight-example-1-images" id="style-attribute-fontWeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Weight</caption><tbody><tr><td><img src="images/fontWeight.png" alt="TTML fontWeight style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-lineHeight" id="style-attribute-lineHeight"></a>8.2.12 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-fontWeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Weight</caption><tbody><tr><td><img src="images/fontWeight.png" alt="TTML fontWeight style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-lineHeight"></a>8.2.12 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
 defines the inter-baseline separation between line areas generated by content flowed into a region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-lineHeight" id="style-property-details-lineHeight"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-lineHeight"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>normal</code> |
 <a href="#style-value-length">&lt;length&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td><code>normal</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -2557,7 +2589,7 @@
 descendant element.</p><p>If specified as a <a href="#style-value-length">&lt;length&gt;</a>, then the length must
 be non-negative.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>normal</code> were specified.</p><p>The <code>tts:lineHeight</code> style is illustrated by the following example.</p><a name="style-attribute-lineHeight-example-1" id="style-attribute-lineHeight-example-1"></a><table class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
+value <code>normal</code> were specified.</p><p>The <code>tts:lineHeight</code> style is illustrated by the following example.</p><a id="style-attribute-lineHeight-example-1"></a><table class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="255px 190px"/&gt;
@@ -2579,22 +2611,22 @@
   "The bitterness of Life.
 "&lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-lineHeight-example-1-images" id="style-attribute-lineHeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Line Height</caption><tbody><tr><td><img src="images/lineHeight.png" alt="TTML lineHeight style property"></td></tr></tbody></table><p></p></div><div class="div3">
-<h4><a name="style-attribute-opacity" id="style-attribute-opacity"></a>8.2.13 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-lineHeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Line Height</caption><tbody><tr><td><img src="images/lineHeight.png" alt="TTML lineHeight style property"></td></tr></tbody></table><p></p></div><div class="div3">
+<h4><a id="style-attribute-opacity"></a>8.2.13 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
 defines the opacity (or conversely, the transparency)
 of marks associated with a region.</p><p>When presented onto a visual medium, the opacity of the region is applied uniformly and on a linear scale
 to all marks produced by content targeted to the
 region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-opacity" id="style-property-details-opacity"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-opacity"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <a href="#style-value-alpha">&lt;alpha&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td>
 <code>1.0</code>
 </td></tr><tr><td><em>Applies to:</em></td><td>
 <a href="#layout-vocabulary-region"><code>region</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>An <a href="#style-value-alpha">&lt;alpha&gt;</a> value greater
-than 1.0 must be considered equivalent to an <a href="#style-value-alpha">&lt;alpha&gt;</a> value of 1.0.</p><p>The <code>tts:opacity</code> style is illustrated by the following example.</p><a name="style-attribute-opacity-example-1" id="style-attribute-opacity-example-1"></a><table class="example"><caption>Example Fragment – Opacity</caption><tbody><tr><td>
+than 1.0 must be considered equivalent to an <a href="#style-value-alpha">&lt;alpha&gt;</a> value of 1.0.</p><p>The <code>tts:opacity</code> style is illustrated by the following example.</p><a id="style-attribute-opacity-example-1"></a><table class="example"><caption>Example Fragment – Opacity</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1" dur="5s"&gt;
   &lt;set begin="0s" dur="1s" <span class="strong">tts:opacity="1.00"</span>/&gt;
@@ -2613,7 +2645,7 @@
   The sun was shining on the sea
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-opacity-example-1-images" id="style-attribute-opacity-example-1-images"></a><table class="example-images"><caption>Example Rendition – Opacity</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><a id="style-attribute-opacity-example-1-images"></a><table class="example-images"><caption>Example Rendition – Opacity</caption><tbody><tr><td>
 <img src="images/opacity_0.png" alt="TTML opacity style property - [0,1)">
 </td></tr><tr><td>
 <img src="images/opacity_1.png" alt="TTML opacity style property - [1,2)">
@@ -2624,13 +2656,13 @@
 </td></tr><tr><td>
 <img src="images/opacity_4.png" alt="TTML opacity style property - [4,5)">
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-origin" id="style-attribute-origin"></a>8.2.14 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
+<h4><a id="style-attribute-origin"></a>8.2.14 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
 <em>x</em> and <em>y</em> coordinates of the origin of a
 region area with respect to the origin of the root container extent,
 if specified, or the external authoring context, if not specified.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-origin" id="style-property-details-origin"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-origin"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>auto</code> |
 <a href="#style-value-length">&lt;length&gt;</a> <a href="#style-value-length">&lt;length&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -2641,7 +2673,7 @@
 of the style property must be considered to be the same as the root container
 origin.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>auto</code> were specified.</p><p>The <code>tts:origin</code> style is illustrated by the following example.</p><a name="style-attribute-origin-example-1" id="style-attribute-origin-example-1"></a><table class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
+value <code>auto</code> were specified.</p><p>The <code>tts:origin</code> style is illustrated by the following example.</p><a id="style-attribute-origin-example-1"></a><table class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style <span class="strong">tts:origin="40px 40px"</span>/&gt;
@@ -2658,13 +2690,13 @@
    To simper at a table-cloth!"
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-origin-example-1-images" id="style-attribute-origin-example-1-images"></a><table class="example-images"><caption>Example Rendition – Origin</caption><tbody><tr><td><img src="images/origin.png" alt="TTML origin style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-overflow" id="style-attribute-overflow"></a>8.2.15 tts:overflow</h4><p>The <code>tts:overflow</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-origin-example-1-images"></a><table class="example-images"><caption>Example Rendition – Origin</caption><tbody><tr><td><img src="images/origin.png" alt="TTML origin style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-overflow"></a>8.2.15 tts:overflow</h4><p>The <code>tts:overflow</code> attribute is used to specify a style property that
 defines whether a region area is clipped or not if the descendant areas of the region overflow
 its extent.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-overflow" id="style-property-details-overflow"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-overflow"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>visible</code> |
 <code>hidden</code>
 </td></tr><tr><td><em>Initial:</em></td><td><code>hidden</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -2681,7 +2713,7 @@
 region is <code>visible</code> and if the applicable <code>tts:wrapOption</code>
 style is <code>noWrap</code>.</p></div><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>hidden</code> were specified.</p><p>The <code>tts:overflow</code> style is illustrated by the following example.</p><a name="style-attribute-overflow-example-1" id="style-attribute-overflow-example-1"></a><table class="example"><caption>Example Fragment – Overflow</caption><tbody><tr><td>
+value <code>hidden</code> were specified.</p><p>The <code>tts:overflow</code> style is illustrated by the following example.</p><a id="style-attribute-overflow-example-1"></a><table class="example"><caption>Example Fragment – Overflow</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="232px 40px"/&gt;
@@ -2717,15 +2749,15 @@
   And all of us are fat!"
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-overflow-example-1-images" id="style-attribute-overflow-example-1-images"></a><table class="example-images"><caption>Example Rendition – Overflow</caption><tbody><tr><td><img src="images/overflow.png" alt="TTML overflow style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the <code>tts:noWrap</code> is set to
+</td></tr></tbody></table><p></p><a id="style-attribute-overflow-example-1-images"></a><table class="example-images"><caption>Example Rendition – Overflow</caption><tbody><tr><td><img src="images/overflow.png" alt="TTML overflow style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the <code>tts:noWrap</code> is set to
 <code>noWrap</code> to prevent automatic line wrapping (breaking);
 if this were not specified, then overflow would occur in the block
 progression direction as opposed to the inline progression direction.</p></div></div><div class="div3">
-<h4><a name="style-attribute-padding" id="style-attribute-padding"></a>8.2.16 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
+<h4><a id="style-attribute-padding"></a>8.2.16 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
 space on all sides of a region area.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-padding" id="style-property-details-padding"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-padding"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <a href="#style-value-length">&lt;length&gt;</a> |
 <a href="#style-value-length">&lt;length&gt;</a> <a href="#style-value-length">&lt;length&gt;</a> |
 <a href="#style-value-length">&lt;length&gt;</a> <a href="#style-value-length">&lt;length&gt;</a> <a href="#style-value-length">&lt;length&gt;</a> |
@@ -2742,7 +2774,7 @@
 If four <a href="#style-value-length">&lt;length&gt;</a> specifications are provided, then they apply to before, end,
 after, and start edges, respectively.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>0px</code> were specified.</p><p>The <code>tts:padding</code> style is illustrated by the following example.</p><a name="style-attribute-padding-example-1" id="style-attribute-padding-example-1"></a><table class="example"><caption>Example Fragment – Padding</caption><tbody><tr><td>
+value <code>0px</code> were specified.</p><p>The <code>tts:padding</code> style is illustrated by the following example.</p><a id="style-attribute-padding-example-1"></a><table class="example"><caption>Example Fragment – Padding</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="446px 104px"/&gt;
@@ -2761,15 +2793,15 @@
 &lt;/p&gt;
 </pre></div>
 </td></tr></tbody></table><p>When rendering an area to which padding applies, the background color that
-applies to the area is rendered into the padded portion of the area.</p><a name="style-attribute-padding-example-1-images" id="style-attribute-padding-example-1-images"></a><table class="example-images"><caption>Example Rendition – Padding</caption><tbody><tr><td>
+applies to the area is rendered into the padded portion of the area.</p><a id="style-attribute-padding-example-1-images"></a><table class="example-images"><caption>Example Rendition – Padding</caption><tbody><tr><td>
 <img src="images/padding.png" alt="TTML padding style property">
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-showBackground" id="style-attribute-showBackground"></a>8.2.17 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
+<h4><a id="style-attribute-showBackground"></a>8.2.17 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
 constraints on when the background color of a region is intended to be
 presented.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-showBackground" id="style-property-details-showBackground"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-showBackground"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>always</code> |
 <code>whenActive</code>
 </td></tr><tr><td><em>Initial:</em></td><td><code>always</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -2780,7 +2812,7 @@
 then the background color of a region is rendered only when some
 content is selected into the region.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>always</code> were specified.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><a name="style-attribute-showBackground-example-1" id="style-attribute-showBackground-example-1"></a><table class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
+value <code>always</code> were specified.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><a id="style-attribute-showBackground-example-1"></a><table class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:origin="0px 0px"/&gt;
@@ -2802,12 +2834,12 @@
 &lt;/region&gt;
 </pre></div>
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-textAlign" id="style-attribute-textAlign"></a>8.2.18 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textAlign"></a>8.2.18 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
 defines how inline areas are aligned within a containing block area in the inline progression
 direction.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-textAlign" id="style-property-details-textAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-textAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>left</code> |
 <code>center</code> |
 <code>right</code> |
@@ -2817,7 +2849,7 @@
 <a href="#content-vocabulary-p"><code>p</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>start</code> were specified.</p><p>The <code>tts:textAlign</code> style is illustrated by the following example.</p><a name="style-attribute-textAlign-example-1" id="style-attribute-textAlign-example-1"></a><table class="example"><caption>Example Fragment – Text Align</caption><tbody><tr><td>
+value <code>start</code> were specified.</p><p>The <code>tts:textAlign</code> style is illustrated by the following example.</p><a id="style-attribute-textAlign-example-1"></a><table class="example"><caption>Example Fragment – Text Align</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="355px 43px"/&gt;
@@ -2843,13 +2875,13 @@
   The frumious Bandersnatch!
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-textAlign-example-1-images" id="style-attribute-textAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="TTML textAlign style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-textDecoration" id="style-attribute-textDecoration"></a>8.2.19 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-textAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="TTML textAlign style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-textDecoration"></a>8.2.19 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
 defines a text decoration effect to apply to glyph areas or other inline
 areas that are generated by content flowed into a region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-textDecoration" id="style-property-details-textDecoration"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-textDecoration"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>none</code> |
 [ [
 <code>underline</code> |
@@ -2865,7 +2897,10 @@
 style property, each character child of a <code>p</code> element is
 considered to be enclosed in an anonymous span.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>none</code> were specified.</p><p>The <code>tts:textDecoration</code> style is illustrated by the following example.</p><a name="style-attribute-textDecoration-example-1" id="style-attribute-textDecoration-example-1"></a><table class="example"><caption>Example Fragment – Text Decoration</caption><tbody><tr><td>
+value <code>none</code> were specified.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The syntax used above in defining the value of this property is based on the
+value component syntax defined in <a href="#css2">[CSS2]</a>, § 1.4.2.1. In essence,
+one or more of the values separated by <code>||</code> may appear in the property
+value in any order, such as <code>"noUnderline overline lineThrough"</code>.</p></div><p>The <code>tts:textDecoration</code> style is illustrated by the following example.</p><a id="style-attribute-textDecoration-example-1"></a><table class="example"><caption>Example Fragment – Text Decoration</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="385px 82px"/&gt;
@@ -2888,13 +2923,13 @@
   &lt;/span&gt;
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-textDecoration-example-1-images" id="style-attribute-textDecoration-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="TTML textDecoration style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-textOutline" id="style-attribute-textOutline"></a>8.2.20 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-textDecoration-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="TTML textDecoration style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-textOutline"></a>8.2.20 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
 defines a text outline effect to apply to glyphs that are selected for glyph areas generated
 by content flowed into a region.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-textOutline" id="style-property-details-textOutline"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-textOutline"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>none</code> |
 <a href="#style-value-color">&lt;color&gt;</a>?
 <a href="#style-value-length">&lt;length&gt;</a>
@@ -2917,7 +2952,7 @@
 without taking into account rasterization effects.</p></div><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
 value <code>none</code> were specified.</p><p>The <code>tts:textOutline</code> style is illustrated by the following
-example.</p><a name="style-attribute-textOutline-example-1" id="style-attribute-textOutline-example-1"></a><table class="example"><caption>Example Fragment – Text Outline</caption><tbody><tr><td>
+example.</p><a id="style-attribute-textOutline-example-1"></a><table class="example"><caption>Example Fragment – Text Outline</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:backgroundColor="transparent"/&gt;
@@ -2938,13 +2973,13 @@
   With gently smiling jaws!
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-textOutline-example-1-images" id="style-attribute-textOutline-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Outline</caption><tbody><tr><td><img src="images/textOutline.png" alt="backgroundColor style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-unicodeBidi" id="style-attribute-unicodeBidi"></a>8.2.21 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-textOutline-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Outline</caption><tbody><tr><td><img src="images/textOutline.png" alt="backgroundColor style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-unicodeBidi"></a>8.2.21 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
 defines a directional embedding or override according to
 the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-unicodeBidi" id="style-property-details-unicodeBidi"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-unicodeBidi"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>normal</code> |
 <code>embed</code> |
 <code>bidiOverride</code>
@@ -2957,7 +2992,7 @@
 each character child of a <code>p</code> element is considered to be enclosed in an anonymous
 span.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>normal</code> were specified.</p><p>The <code>tts:unicodeBidi</code> style is illustrated by the following example.</p><a name="style-attribute-unicodeBidi-example-1" id="style-attribute-unicodeBidi-example-1"></a><table class="example"><caption>Example Fragment – Unicode Bidirectionality</caption><tbody><tr><td>
+value <code>normal</code> were specified.</p><p>The <code>tts:unicodeBidi</code> style is illustrated by the following example.</p><a id="style-attribute-unicodeBidi-example-1"></a><table class="example"><caption>Example Fragment – Unicode Bidirectionality</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="265px 84px"/&gt;
@@ -2974,15 +3009,15 @@
   &lt;span <span class="strong">tts:unicodeBidi="bidiOverride"</span> tts:direction="rtl"&gt;where the tourists snore.&lt;/span&gt;
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-unicodeBidi-example-1-images" id="style-attribute-unicodeBidi-example-1-images"></a><table class="example-images"><caption>Example Rendition – Unicode Bidirectionality</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><a id="style-attribute-unicodeBidi-example-1-images"></a><table class="example-images"><caption>Example Rendition – Unicode Bidirectionality</caption><tbody><tr><td>
 <img src="images/unicodeBidi.png" alt="TTML unicodeBidi style property">
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-visibility" id="style-attribute-visibility"></a>8.2.22 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-visibility"></a>8.2.22 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
 defines whether generated areas are visible or not when rendered on a visual
 presentation medium.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-visibility" id="style-property-details-visibility"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-visibility"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>visible</code> |
 <code>hidden</code>
 </td></tr><tr><td><em>Initial:</em></td><td>
@@ -2998,7 +3033,7 @@
 span.</p><p>The <code>tts:visibility</code> style has no affect on content layout or
 composition, but merely determines whether composed content is visible or not.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>visible</code> were specified.</p><p>The <code>tts:visibility</code> style is illustrated by the following example.</p><a name="style-attribute-visibility-example-1" id="style-attribute-visibility-example-1"></a><table class="example"><caption>Example Fragment – Visibility</caption><tbody><tr><td>
+value <code>visible</code> were specified.</p><p>The <code>tts:visibility</code> style is illustrated by the following example.</p><a id="style-attribute-visibility-example-1"></a><table class="example"><caption>Example Fragment – Visibility</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="398px 121px"/&gt;
@@ -3022,7 +3057,7 @@
   &lt;/span&gt;
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-visibility-example-1-images" id="style-attribute-visibility-example-1-images"></a><table class="example-images"><caption>Example Rendition – Visibility</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><a id="style-attribute-visibility-example-1-images"></a><table class="example-images"><caption>Example Rendition – Visibility</caption><tbody><tr><td>
 <img src="images/visibility_0.png" alt="TTML visibility style property - [0,1)">
 </td></tr><tr><td>
 <img src="images/visibility_1.png" alt="TTML visibility style property - [1,2)">
@@ -3031,12 +3066,12 @@
 </td></tr><tr><td>
 <img src="images/visibility_3.png" alt="TTML visibility style property - [3,4)">
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-wrapOption" id="style-attribute-wrapOption"></a>8.2.23 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-wrapOption"></a>8.2.23 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
 defines whether or not automatic line wrapping (breaking) applies within the context of
 the affected element.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-wrapOption" id="style-property-details-wrapOption"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-wrapOption"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>wrap</code> |
 <code>noWrap</code>
 </td></tr><tr><td><em>Initial:</em></td><td><code>wrap</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -3045,7 +3080,7 @@
 each character child of a <code>p</code> element is considered to be enclosed in an anonymous
 span.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>wrap</code> were specified.</p><p>The <code>tts:wrapOption</code> style is illustrated by the following example.</p><a name="style-attribute-wrapOption-example-1" id="style-attribute-wrapOption-example-1"></a><table class="example"><caption>Example Fragment – Wrap Option</caption><tbody><tr><td>
+value <code>wrap</code> were specified.</p><p>The <code>tts:wrapOption</code> style is illustrated by the following example.</p><a id="style-attribute-wrapOption-example-1"></a><table class="example"><caption>Example Fragment – Wrap Option</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="192px 117px"/&gt;
@@ -3063,13 +3098,13 @@
   A-sitting on a gate.
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-wrapOption-example-1-images" id="style-attribute-wrapOption-example-1-images"></a><table class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="TTML wrapOption style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-attribute-writingMode" id="style-attribute-writingMode"></a>8.2.24 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
+</td></tr></tbody></table><p></p><a id="style-attribute-wrapOption-example-1-images"></a><table class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="TTML wrapOption style property"></td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-attribute-writingMode"></a>8.2.24 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
 defines the block and inline progression directions to be used for the purpose of
 stacking block and inline areas within a region area.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-writingMode" id="style-property-details-writingMode"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-writingMode"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>lrtb</code> |
 <code>rltb</code> |
 <code>tbrl</code> |
@@ -3081,7 +3116,7 @@
 <a href="#layout-vocabulary-region"><code>region</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>lrtb</code> were specified.</p><p>The <code>tts:writingMode</code> style is illustrated by the following example.</p><a name="style-attribute-writingMode-example-1" id="style-attribute-writingMode-example-1"></a><table class="example"><caption>Example Fragment – Writing Mode</caption><tbody><tr><td>
+value <code>lrtb</code> were specified.</p><p>The <code>tts:writingMode</code> style is illustrated by the following example.</p><a id="style-attribute-writingMode-example-1"></a><table class="example"><caption>Example Fragment – Writing Mode</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="50px 570px"/&gt;
@@ -3108,17 +3143,17 @@
   I sometimes search the grassy knolls for the wheels of Hansom-cabs.
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a name="style-attribute-writingMode-example-1-images" id="style-attribute-writingMode-example-1-images"></a><table class="example-images"><caption>Example Rendition – Writing Mode</caption><tbody><tr><td><img src="images/writingMode.png" alt="TTML writingMode style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the second paragraph in the above example that targets region
+</td></tr></tbody></table><p></p><a id="style-attribute-writingMode-example-1-images"></a><table class="example-images"><caption>Example Rendition – Writing Mode</caption><tbody><tr><td><img src="images/writingMode.png" alt="TTML writingMode style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the second paragraph in the above example that targets region
 <code>r2</code>, the <code>tts:unicodeBidi</code> and
 <code>tts:direction</code> properties are set to
 <code>bidiOverride</code> and <code>rtl</code>, respectively, in order
 to override the normally left-to-right directionality of characters in
 the Latin script.</p></div></div><div class="div3">
-<h4><a name="style-attribute-zIndex" id="style-attribute-zIndex"></a>8.2.25 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-zIndex"></a>8.2.25 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
 defines the front-to-back ordering of region areas in the case that they overlap.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p><a name="style-property-details-zIndex" id="style-property-details-zIndex"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-zIndex"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>auto</code> |
 <a href="#style-value-integer">&lt;integer&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -3126,12 +3161,11 @@
 </td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If two areas are associated with the same Z-index value, then, if those areas
 overlap in space, the area(s) generated by lexically subsequent elements must be
 rendered over area(s) generated by lexically prior elements, where lexical
-order is defined as the postorder traversal of a document
-instance.</p><p>The semantics of the value <code>auto</code> are those defined by
+order is defined as the postorder traversal of a <em>Document Instance</em>.</p><p>The semantics of the value <code>auto</code> are those defined by
 <a href="#xsl11">[XSL 1.1]</a>, § 7.30.18, where the <code>tt</code> element
 is considered to establish the root stacking context.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
-value <code>auto</code> were specified.</p><p>The <code>tts:zIndex</code> style is illustrated by the following example.</p><a name="style-attribute-zIndex-example-1" id="style-attribute-zIndex-example-1"></a><table class="example"><caption>Example Fragment – Z Index</caption><tbody><tr><td>
+value <code>auto</code> were specified.</p><p>The <code>tts:zIndex</code> style is illustrated by the following example.</p><a id="style-attribute-zIndex-example-1"></a><table class="example"><caption>Example Fragment – Z Index</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:origin="0px 0px"/&gt;
@@ -3186,10 +3220,10 @@
   And concluded the banquet by...
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><p></p><a name="style-attribute-zIndex-example-1-images" id="style-attribute-zIndex-example-1-images"></a><table class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="TTML zIndex style property"></td></tr></tbody></table></div></div><div class="div2">
-<h3><a name="styling-style-value-expressions" id="styling-style-value-expressions"></a>8.3 Style Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>8.3.1 &lt;alpha&gt;</b></a></p></li><li><p><a href="#style-value-color"><b>8.3.2 &lt;color&gt;</b></a></p></li><li><p><a href="#style-value-digit"><b>8.3.3 &lt;digit&gt;</b></a></p></li><li><p><a href="#style-value-duration"><b>8.3.4 &lt;duration&gt;</b></a></p></li><li><p><a href="#style-value-familyName"><b>8.3.5 &lt;familyName&gt;</b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>8.3.6 &lt;genericFamilyName&gt;</b></a></p></li><li><p><a href="#style-value-hexDigit"><b>8.3.7 &lt;hexDigit&gt;</b></a></p></li><li><p><a href="#style-value-integer"><b>8.3.8 &lt;integer&gt;</b></a></p></li><li><p><a href="#style-value-length"><b>8.3.9 &lt;length&gt;</b></a></p></li><li><p><a href="#style-value-namedColor"><b>8.3.10 &lt;namedColor&gt;</b></a></p></li><li><p><a href="#style-value-quotedString"><b>8.3.11 &lt;quotedString&gt;</b></a></p></li><li><p><a href="#style-value-string"><b>8.3.12 &lt;string&gt;</b></a></p></li></ul><div class="div3">
-<h4><a name="style-value-alpha" id="style-value-alpha"></a>8.3.1 &lt;alpha&gt;</h4><p>An &lt;alpha&gt; expression is used to express an opacity value,
-where	0 means fully transparent and 1 means fully opaque.</p><a name="alpha-style-expression-syntax" id="alpha-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;alpha&gt;</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><p></p><a id="style-attribute-zIndex-example-1-images"></a><table class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="TTML zIndex style property"></td></tr></tbody></table></div></div><div class="div2">
+<h3><a id="styling-style-value-expressions"></a>8.3 Style Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>8.3.1 &lt;alpha&gt;</b></a></p></li><li><p><a href="#style-value-color"><b>8.3.2 &lt;color&gt;</b></a></p></li><li><p><a href="#style-value-digit"><b>8.3.3 &lt;digit&gt;</b></a></p></li><li><p><a href="#style-value-duration"><b>8.3.4 &lt;duration&gt;</b></a></p></li><li><p><a href="#style-value-familyName"><b>8.3.5 &lt;familyName&gt;</b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>8.3.6 &lt;genericFamilyName&gt;</b></a></p></li><li><p><a href="#style-value-hexDigit"><b>8.3.7 &lt;hexDigit&gt;</b></a></p></li><li><p><a href="#style-value-integer"><b>8.3.8 &lt;integer&gt;</b></a></p></li><li><p><a href="#style-value-length"><b>8.3.9 &lt;length&gt;</b></a></p></li><li><p><a href="#style-value-namedColor"><b>8.3.10 &lt;namedColor&gt;</b></a></p></li><li><p><a href="#style-value-quotedString"><b>8.3.11 &lt;quotedString&gt;</b></a></p></li><li><p><a href="#style-value-string"><b>8.3.12 &lt;string&gt;</b></a></p></li></ul><div class="div3">
+<h4><a id="style-value-alpha"></a>8.3.1 &lt;alpha&gt;</h4><p>An &lt;alpha&gt; expression is used to express an opacity value,
+where	0 means fully transparent and 1 means fully opaque.</p><a id="alpha-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;alpha&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;alpha&gt;
   : <em>float</em>
@@ -3203,11 +3237,11 @@
 1.0. The value NaN must be interpreted as 0.0.</p><p>If a presentation processor does not support a specific,
 valid opacity value, then it must interpret it as being equal to the
 closest supported value.</p></div><div class="div3">
-<h4><a name="style-value-color" id="style-value-color"></a>8.3.2 &lt;color&gt;</h4><p>A &lt;color&gt; expression is used to specify a named color, exact RGB color triple,
+<h4><a id="style-value-color"></a>8.3.2 &lt;color&gt;</h4><p>A &lt;color&gt; expression is used to specify a named color, exact RGB color triple,
 or exact RGBA color tuple, where the alpha component, if expressed,
 is maximum (255) at 100% opacity
 and minimum (0) at 0% opacity, and where the applicable color space is
-defined by <a href="#srgb">[SRGB]</a>.</p><a name="color-style-expression-syntax" id="color-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;color&gt;</caption><tbody><tr><td>
+defined by <a href="#srgb">[SRGB]</a>.</p><a id="color-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;color&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;color&gt;
   : "#" rrggbb
@@ -3243,13 +3277,13 @@
 used here to the YUV color space for rendition on a television device.</p></div><p>If a presentation processor does not support a specific,
 valid color or alpha value, then it must interpret it as being equal
 to the closest supported value.</p></div><div class="div3">
-<h4><a name="style-value-digit" id="style-value-digit"></a>8.3.3 &lt;digit&gt;</h4><p>A &lt;digit&gt; is used to express integers and other types of numbers or tokens.</p><a name="digit-style-expression-syntax" id="digit-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;digit&gt;</caption><tbody><tr><td>
+<h4><a id="style-value-digit"></a>8.3.3 &lt;digit&gt;</h4><p>A &lt;digit&gt; is used to express integers and other types of numbers or tokens.</p><a id="digit-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;digit&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;digit&gt;
   : "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9"
 </pre></div>
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-value-duration" id="style-value-duration"></a>8.3.4 &lt;duration&gt;</h4><p>A &lt;duration&gt; expression is used to express a temporal duration value.</p><a name="duration-style-expression-syntax" id="duration-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;duration&gt;</caption><tbody><tr><td>
+<h4><a id="style-value-duration"></a>8.3.4 &lt;duration&gt;</h4><p>A &lt;duration&gt; expression is used to express a temporal duration value.</p><a id="duration-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;duration&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;duration&gt;
   : <a href="#style-value-digit">&lt;digit&gt;</a>+ ( "." <a href="#style-value-digit">&lt;digit&gt;</a>+ )? metric
@@ -3264,22 +3298,22 @@
 <code>discontinuous</code> mode, a duration expression must be
 considered to denote a duration in (local) real-time, independently of the
 governing time base.</p></div><div class="div3">
-<h4><a name="style-value-familyName" id="style-value-familyName"></a>8.3.5 &lt;familyName&gt;</h4><p>A &lt;familyName&gt; expression specifies a font family name.</p><p>If the name contains a quotation delimiter character,
+<h4><a id="style-value-familyName"></a>8.3.5 &lt;familyName&gt;</h4><p>A &lt;familyName&gt; expression specifies a font family name.</p><p>If the name contains a quotation delimiter character,
 then it must be expressed as a
 &lt;quotedString&gt;. If the name contains a
 whitespace character,
 then it should be expressed as a
 &lt;quotedString&gt;; however, if it is expressed as a &lt;string&gt;, then it
-must not contain a <code>COMMA</code> ',' character.</p><a name="familyName-style-expression-syntax" id="familyName-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;familyName&gt;</caption><tbody><tr><td>
+must not contain a <code>COMMA</code> ',' character.</p><a id="familyName-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;familyName&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;familyName&gt;
   : <a href="#style-value-string">&lt;string&gt;</a>
   | <a href="#style-value-quotedString">&lt;quotedString&gt;</a>
 </pre></div>
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-value-genericFamilyName" id="style-value-genericFamilyName"></a>8.3.6 &lt;genericFamilyName&gt;</h4><p>A &lt;genericFamilyName&gt; expression specifies a font family using a general
+<h4><a id="style-value-genericFamilyName"></a>8.3.6 &lt;genericFamilyName&gt;</h4><p>A &lt;genericFamilyName&gt; expression specifies a font family using a general
 token that indicates a class of font families.</p><p>The resolution of a generic family name to a concrete font instance is considered to
-be implementation dependent, both in the case of content authoring and content interpretation.</p><a name="genericFamilyName-style-expression-syntax" id="genericFamilyName-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;genericFamilyName&gt;</caption><tbody><tr><td>
+be implementation dependent, both in the case of content authoring and content interpretation.</p><a id="genericFamilyName-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;genericFamilyName&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;genericFamilyName&gt;
   : "default"
@@ -3302,8 +3336,8 @@
 an initial value), then its typographic characteristics is considered to be implementation
 dependent; however, it is recommended that this default font family be mapped to
 an monospaced, sans-serif font.</p></div><div class="div3">
-<h4><a name="style-value-hexDigit" id="style-value-hexDigit"></a>8.3.7 &lt;hexDigit&gt;</h4><p>A &lt;hexDigit&gt; is used to express integers and other types of numbers or tokens
-that employ base 16 arithmetic.</p><p>For the purpose of parsing, no distinction must be made between lower and upper case.</p><a name="hexDigit-style-expression-syntax" id="hexDigit-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;hexDigit&gt;</caption><tbody><tr><td>
+<h4><a id="style-value-hexDigit"></a>8.3.7 &lt;hexDigit&gt;</h4><p>A &lt;hexDigit&gt; is used to express integers and other types of numbers or tokens
+that employ base 16 arithmetic.</p><p>For the purpose of parsing, no distinction must be made between lower and upper case.</p><a id="hexDigit-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;hexDigit&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;hexDigit&gt;
   : <a href="#style-value-digit">&lt;digit&gt;</a>
@@ -3311,14 +3345,14 @@
   | "A" | "B" | "C" | "D" | "E" | "F"
 </pre></div>
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-value-integer" id="style-value-integer"></a>8.3.8 &lt;integer&gt;</h4><p>An &lt;integer&gt; expression is used to express an arbitrary, signed integral value.</p><a name="integer-style-expression-syntax" id="integer-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;integer&gt;</caption><tbody><tr><td>
+<h4><a id="style-value-integer"></a>8.3.8 &lt;integer&gt;</h4><p>An &lt;integer&gt; expression is used to express an arbitrary, signed integral value.</p><a id="integer-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;integer&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;integer&gt;
   : ( "+" | "-" )? <a href="#style-value-digit">&lt;digit&gt;</a>+
 </pre></div>
 </td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-value-length" id="style-value-length"></a>8.3.9 &lt;length&gt;</h4><p>A &lt;length&gt; expression is used to express either a coordinate component of point
-in a cartesian space or a distance between two points in a cartesian space.</p><a name="length-style-expression-syntax" id="length-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;length&gt;</caption><tbody><tr><td>
+<h4><a id="style-value-length"></a>8.3.9 &lt;length&gt;</h4><p>A &lt;length&gt; expression is used to express either a coordinate component of point
+in a cartesian space or a distance between two points in a cartesian space.</p><a id="length-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;length&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;length&gt;
   : scalar
@@ -3364,8 +3398,8 @@
 direction and equal to the block progression dimension of the scaled
 font when used to specify lengths in the block progression direction.</p><p>The semantics of the unit of measure <code>c</code> (cell) are
 defined by the parameter <a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a>.</p></div><div class="div3">
-<h4><a name="style-value-namedColor" id="style-value-namedColor"></a>8.3.10 &lt;namedColor&gt;</h4><p>A &lt;namedColor&gt; is used to express an RGBA color with a convenient name, and where the applicable color space is
-defined by <a href="#srgb">[SRGB]</a>.</p><p>For the purpose of parsing, no distinction must be made between lower and upper case.</p><a name="namedColor-style-expression-syntax" id="namedColor-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;namedColor&gt;</caption><tbody><tr><td>
+<h4><a id="style-value-namedColor"></a>8.3.10 &lt;namedColor&gt;</h4><p>A &lt;namedColor&gt; is used to express an RGBA color with a convenient name, and where the applicable color space is
+defined by <a href="#srgb">[SRGB]</a>.</p><p>For the purpose of parsing, no distinction must be made between lower and upper case.</p><a id="namedColor-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;namedColor&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;namedColor&gt;
   : "transparent"                           // #00000000
@@ -3390,9 +3424,9 @@
 </pre></div>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>Except for <code>transparent</code>, the set of named colors specified above constitutes a proper
 subset of the set of named colors specified by <a href="#svg11">[SVG 1.1]</a>, § 4.2.</p></div></div><div class="div3">
-<h4><a name="style-value-quotedString" id="style-value-quotedString"></a>8.3.11 &lt;quotedString&gt;</h4><p>A &lt;quotedString&gt; is used to express a delimited string that may contain
+<h4><a id="style-value-quotedString"></a>8.3.11 &lt;quotedString&gt;</h4><p>A &lt;quotedString&gt; is used to express a delimited string that may contain
 a whitespace or a quotation delimiter character. Two types of quotation delimiters
-are provided in order to accommodate strings that contain the other delimiter.</p><a name="quotedString-style-expression-syntax" id="quotedString-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;quotedString&gt;</caption><tbody><tr><td>
+are provided in order to accommodate strings that contain the other delimiter.</p><a id="quotedString-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;quotedString&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;quotedString&gt;
   : "\"" ( <em>char</em> - { "\"" } )* "\""
@@ -3401,8 +3435,8 @@
 </td></tr></tbody></table><p>In the above syntax representation, the syntactic element <em><code>char</code></em> must adhere to production
 [2] <code>Char</code> as defined by <a href="#xml10">[XML 1.0]</a>&nbsp;§
 2.2.</p></div><div class="div3">
-<h4><a name="style-value-string" id="style-value-string"></a>8.3.12 &lt;string&gt;</h4><p>A &lt;string&gt; expression consists of a sequence of characters where no character
-is a quotation delimiter character.</p><a name="string-style-expression-syntax" id="string-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;string&gt;</caption><tbody><tr><td>
+<h4><a id="style-value-string"></a>8.3.12 &lt;string&gt;</h4><p>A &lt;string&gt; expression consists of a sequence of characters where no character
+is a quotation delimiter character.</p><a id="string-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;string&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;string&gt;
   : ( <em>char</em> - { "\"" | "\'" } )+
@@ -3410,20 +3444,20 @@
 </td></tr></tbody></table><p>In the above syntax representation, the syntactic element <em><code>char</code></em> must adhere to production
 [2] <code>Char</code> as defined by <a href="#xml10">[XML 1.0]</a>&nbsp;§
 2.2.</p></div></div><div class="div2">
-<h3><a name="semantics-style-resolution" id="semantics-style-resolution"></a>8.4 Style Resolution</h3><p>This section defines the semantics of style resolution in terms of
+<h3><a id="semantics-style-resolution"></a>8.4 Style Resolution</h3><p>This section defines the semantics of style resolution in terms of
 a standard processing model as follows:</p><ul><li><p><a href="#semantics-style-association"><b>8.4.1 Style Association</b></a></p></li><li><p><a href="#semantics-style-inheritance"><b>8.4.2 Style Inheritance</b></a></p></li><li><p><a href="#semantics-style-resolution-value-categories"><b>8.4.3 Style Resolution Value Categories</b></a></p></li><li><p><a href="#semantics-style-resolution-processing"><b>8.4.4 Style Resolution Processing</b></a></p></li></ul><p>Any implementation of this model is permitted provided that the
 externally observable results are consistent with the results produced
 by this model.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of style resolution employed here are based upon
 <a href="#xsl11">[XSL 1.1]</a>, § 5.</p></div><div class="div3">
-<h4><a name="semantics-style-association" id="semantics-style-association"></a>8.4.1 Style Association</h4><p>Style association is a sub-process of <a href="#semantics-style-resolution-processing"><b>8.4.4 Style Resolution Processing</b></a> used to determine the
+<h4><a id="semantics-style-association"></a>8.4.1 Style Association</h4><p>Style association is a sub-process of <a href="#semantics-style-resolution-processing"><b>8.4.4 Style Resolution Processing</b></a> used to determine the
 specified style set of each content and
 layout element.</p><p>Style matter may be associated with content
  and layout matter in a number of ways:</p><ul><li><p><a href="#semantics-style-association-inline">inline styling</a></p></li><li><p><a href="#semantics-style-association-referential">referential styling</a></p></li><li><p><a href="#semantics-style-association-chained-referential">chained referential styling</a></p></li></ul><p>In addition to the above, style matter may be associated with layout matter using:</p><ul><li><p><a href="#semantics-style-association-nested">nested styling</a></p></li></ul><div class="div4">
-<h5><a name="semantics-style-association-inline" id="semantics-style-association-inline"></a>8.4.1.1 Inline Styling</h5><p>Style properties may be expressed in an inline manner by direct
+<h5><a id="semantics-style-association-inline"></a>8.4.1.1 Inline Styling</h5><p>Style properties may be expressed in an inline manner by direct
 specification of an attribute from the TT Style Namespace on the
 affected element. When expressed in this manner, the association of
 style information is referred to as <em>inline styling</em>.</p><p>Style properties associated by inline styling are afforded a higher priority than all other
-forms of style association.</p><a name="style-association-example-1" id="style-association-example-1"></a><table class="example"><caption>Example – Inline Styling</caption><tbody><tr><td>
+forms of style association.</p><a id="style-association-example-1"></a><table class="example"><caption>Example – Inline Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;p <span class="strong">tts:color="white"</span>&gt;White 1&nbsp;&lt;span <span class="strong">tts:color="yellow"</span>&gt;Yellow&lt;/span&gt;&nbsp;White 2&lt;/p&gt;
 </pre></div>
@@ -3431,7 +3465,7 @@
 <code>" White 2"</code>, which are interpreted as anonymous spans, are not
 associated with a color style property; rather, they inherit their color style
 from their parent <code>p</code> element as described in <a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a> below.  </p></div></div><div class="div4">
-<h5><a name="semantics-style-association-referential" id="semantics-style-association-referential"></a>8.4.1.2 Referential Styling</h5><p>Style properties may be expressed in an out-of-line manner and referenced by the
+<h5><a id="semantics-style-association-referential"></a>8.4.1.2 Referential Styling</h5><p>Style properties may be expressed in an out-of-line manner and referenced by the
 affected element using the <code>style</code> attribute. When expressed in this manner,
 the association of style information is referred to as <em>referential styling</em>.</p><p>If a <code>style</code> attribute specifies multiple references, then those references are
 evaluated in the specified order, and that order applies to resolution of the value of a
@@ -3441,7 +3475,7 @@
 element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of referential styling encourages the reuse of style specifications while
 sacrificing locality of reference.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single content element may be associated with style properties by a hybrid mixture of
 inline and referential styling, in which case inline styling is given priority as described above
-by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><a name="style-association-example-2" id="style-association-example-2"></a><table class="example"><caption>Example – Referential Styling</caption><tbody><tr><td>
+by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><a id="style-association-example-2"></a><table class="example"><caption>Example – Referential Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;style <span class="strong">xml:id="s1"</span> tts:color="white"/&gt;
 &lt;style <span class="strong">xml:id="s2"</span> tts:color="yellow"/&gt;
@@ -3452,7 +3486,7 @@
 <code>" White 2"</code>, which are interpreted as anonymous spans, are not
 associated with a color style property; rather, they inherit their color style
 from their parent <code>p</code> element as described in <a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a> below.</p></div></div><div class="div4">
-<h5><a name="semantics-style-association-chained-referential" id="semantics-style-association-chained-referential"></a>8.4.1.3 Chained Referential Styling</h5><p>Style properties may be expressed in an out-of-line manner and may themselves reference
+<h5><a id="semantics-style-association-chained-referential"></a>8.4.1.3 Chained Referential Styling</h5><p>Style properties may be expressed in an out-of-line manner and may themselves reference
 other out-of-line style properties, thus creating a chain of references starting at the
 affected element. When expressed in this manner, the association of style information
 is referred to as <em>chained referential styling</em>.</p><p>If the same style property is specified in more than one referenced
@@ -3471,7 +3505,7 @@
 element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of chained referential styling encourages the grouping of style specifications
 into general and specific sets, which further aids in style specification reuse.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single content element may be associated with style properties by a hybrid mixture of
 inline, referential styling, and chained referential styling, in which case inline styling is
-given priority as described above by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><a name="style-association-example-3" id="style-association-example-3"></a><table class="example"><caption>Example – Chained Referential Styling</caption><tbody><tr><td>
+given priority as described above by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><a id="style-association-example-3"></a><table class="example"><caption>Example – Chained Referential Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;style <span class="strong">xml:id="s1"</span> tts:color="white" tts:fontFamily="monospaceSerif"/&gt;
 &lt;style <span class="strong">xml:id="s2"</span> <span class="strong">style="s1"</span> tts:color="yellow"/&gt;
@@ -3480,11 +3514,11 @@
 &lt;p <span class="strong">style="s2"</span>&gt;Yellow Monospace&lt;/p&gt;
 </pre></div>
 </td></tr></tbody></table></div><div class="div4">
-<h5><a name="semantics-style-association-nested" id="semantics-style-association-nested"></a>8.4.1.4 Nested Styling</h5><p>Style properties may be expressed in an nested manner by direct specification of one or
+<h5><a id="semantics-style-association-nested"></a>8.4.1.4 Nested Styling</h5><p>Style properties may be expressed in an nested manner by direct specification of one or
 more <code>style</code> element children of the affected element.
 When expressed in this manner, the association of style information
 is referred to as <em>nested styling</em>.</p><p>Style properties associated by nested styling are afforded a lower priority than inline
-styling but with higher priority than referential styling.</p><a name="style-association-example-4" id="style-association-example-4"></a><table class="example"><caption>Example – Nested Styling</caption><tbody><tr><td>
+styling but with higher priority than referential styling.</p><a id="style-association-example-4"></a><table class="example"><caption>Example – Nested Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   <span class="strong">&lt;style tts:extent="128px 66px"/&gt;</span>
@@ -3494,16 +3528,16 @@
 </pre></div>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In this version of this specification, nested styling applies only
 to the <code>region</code> element.</p></div></div></div><div class="div3">
-<h4><a name="semantics-style-inheritance" id="semantics-style-inheritance"></a>8.4.2 Style Inheritance</h4><p>Style inheritance is a sub-process of <a href="#semantics-style-resolution-processing"><b>8.4.4 Style Resolution Processing</b></a> used to determine the
+<h4><a id="semantics-style-inheritance"></a>8.4.2 Style Inheritance</h4><p>Style inheritance is a sub-process of <a href="#semantics-style-resolution-processing"><b>8.4.4 Style Resolution Processing</b></a> used to determine the
 specified style set of each content and
 layout element.</p><p>Styles are further propagated to content matter
 using:
 </p><ul><li><p><a href="#semantics-style-inheritance-content">content style inheritance</a></p></li><li><p><a href="#semantics-style-inheritance-content">region style inheritance</a></p></li></ul><p>For the purpose of determining inherited styles, the element hierarchy of
-an intermediate synchronic document form of a TTML document instance must be used, where
+an intermediate synchronic document form of a <em>Document Instance</em> must be used, where
 such intermediate forms are defined by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate synchronic document form is utilized rather than
 the original form in order to facilitate region inheritance
 processing.</p></div><div class="div4">
-<h5><a name="semantics-style-inheritance-content" id="semantics-style-inheritance-content"></a>8.4.2.1 Content Style Inheritance</h5><p>Style properties are inherited from ancestor content elements
+<h5><a id="semantics-style-inheritance-content"></a>8.4.2.1 Content Style Inheritance</h5><p>Style properties are inherited from ancestor content elements
 within an intermediate synchronic document
 if a style property is not associated with a content element (or
 an anonymous span) and the style property is designated as
@@ -3511,7 +3545,7 @@
 be the value of the same named style property in the computed
 style set of the
 element's immediate ancestor element
-within the applicable intermediate synchronic document.</p><a name="style-inheritance-example-2" id="style-inheritance-example-2"></a><table class="example"><caption>Example – Content Style Inheritance</caption><tbody><tr><td>
+within the applicable intermediate synchronic document.</p><a id="style-inheritance-example-2"></a><table class="example"><caption>Example – Content Style Inheritance</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;p <span class="strong">tts:fontFamily="monospaceSansSerif"</span>&gt;
   &lt;span tts:color="yellow"&gt;Yellow Monospace&lt;/span&gt;
@@ -3527,7 +3561,7 @@
 specified
 style
 set of the <code>span</code> element.</p></div></div><div class="div4">
-<h5><a name="semantics-style-inheritance-region" id="semantics-style-inheritance-region"></a>8.4.2.2 Region Style Inheritance</h5><p>Style properties are inherited from a region element in the following case:</p><ol class="enumar"><li><p>if a style property <em>P</em> is not associated with
+<h5><a id="semantics-style-inheritance-region"></a>8.4.2.2 Region Style Inheritance</h5><p>Style properties are inherited from a region element in the following case:</p><ol class="enumar"><li><p>if a style property <em>P</em> is not associated with
 a content
 element or an anonymous span <em>E</em> and the style
 property is designated as inheritable, and</p></li><li><p>if that
@@ -3535,7 +3569,7 @@
 set of region
 <em>R</em>,
 and</p></li><li><p>if that element <em>E</em> is flowed into (presented within) region
-<em>R</em>.</p></li></ol><a name="style-inheritance-example-3" id="style-inheritance-example-3"></a><table class="example"><caption>Example – Region Style Inheritance</caption><tbody><tr><td>
+<em>R</em>.</p></li></ol><a id="style-inheritance-example-3"></a><table class="example"><caption>Example – Region Style Inheritance</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region <span class="strong">xml:id="r1"</span>&gt;
 &nbsp;&nbsp;&lt;style tts:color="yellow"/&gt;
@@ -3548,14 +3582,14 @@
 items <code>Yellow Monospace</code> effectively inherits the <code>tts:color</code>
 and <code>tts:fontFamily</code> styles specified on the <code>region</code>
 element into which the <code>p</code> element is flowed (presented).</p></div></div></div><div class="div3">
-<h4><a name="semantics-style-resolution-value-categories" id="semantics-style-resolution-value-categories"></a>8.4.3 Style Resolution Value Categories</h4><p>During style resolution, layout, and presentation processing,
+<h4><a id="semantics-style-resolution-value-categories"></a>8.4.3 Style Resolution Value Categories</h4><p>During style resolution, layout, and presentation processing,
 three categories of style property values are distinguished as
 follows:</p><ul><li><p><a href="#semantics-style-resolved-value-category-specified">specified values</a></p></li><li><p><a href="#semantics-style-resolved-value-category-computed">computed values</a></p></li><li><p><a href="#semantics-style-resolved-value-category-actual">actual values</a></p></li></ul><div class="div4">
-<h5><a name="semantics-style-resolved-value-category-specified" id="semantics-style-resolved-value-category-specified"></a>8.4.3.1 Specified Values</h5><p>Values of style properties that are associated with or inherited
+<h5><a id="semantics-style-resolved-value-category-specified"></a>8.4.3.1 Specified Values</h5><p>Values of style properties that are associated with or inherited
 by an element or anonymous span are referred to as <em>specified values</em>. The
 set of all specified style properties of a given element is referred to
 as the <em>specified style set</em> of that element.</p></div><div class="div4">
-<h5><a name="semantics-style-resolved-value-category-computed" id="semantics-style-resolved-value-category-computed"></a>8.4.3.2 Computed Values</h5><p>When style properties are specified using relative value expressions,
+<h5><a id="semantics-style-resolved-value-category-computed"></a>8.4.3.2 Computed Values</h5><p>When style properties are specified using relative value expressions,
 such as a named color, a relative unit (e.g., cell), or a percentage, then
 they need to be further resolved into absolute units, such as an RGB triple,
 pixels, etc.</p><p>During the style resolution process, all specified style values are
@@ -3568,7 +3602,7 @@
 such as percentage, require evaluating the expression in the immediate
 (local) context of reference, and not in a distant (remote) context of
 reference where the related (resolving) expression is not available.</p></div><div class="div4">
-<h5><a name="semantics-style-resolved-value-category-actual" id="semantics-style-resolved-value-category-actual"></a>8.4.3.3 Actual Values</h5><p>During the actual presentation process, other transformations occur
+<h5><a id="semantics-style-resolved-value-category-actual"></a>8.4.3.3 Actual Values</h5><p>During the actual presentation process, other transformations occur
 that map some value expressions to concrete, physical values. For example,
 the colors of computed style values are further subjected to closest color
 approximation and gamma correction
@@ -3588,16 +3622,16 @@
 to actual style set values; as a consequence, no further use or reference
 to actual values is made below when formally describing the style
 resolution process.</p></div></div></div><div class="div3">
-<h4><a name="semantics-style-resolution-processing" id="semantics-style-resolution-processing"></a>8.4.4 Style Resolution Processing</h4><p>The process of style resolution is defined herein as the procedure
+<h4><a id="semantics-style-resolution-processing"></a>8.4.4 Style Resolution Processing</h4><p>The process of style resolution is defined herein as the procedure
 (and results thereof) for resolving (determining) the computed values
 of all style properties that apply to content and layout elements:</p><ul><li><p><a href="#semantics-style-resolution-processing-definitions"><b>8.4.4.1 Conceptual Definitions</b></a></p></li><li><p><a href="#semantics-style-resolution-processing-sss"><b>8.4.4.2 Specified Style Set Processing</b></a></p></li><li><p><a href="#semantics-style-resolution-processing-css"><b>8.4.4.3 Computed Style Set Processing</b></a></p></li><li><p><a href="#semantics-style-resolution-process-overall"><b>8.4.4.4 Style Resolution Process</b></a></p></li></ul><p>The process described here forms an integral sub-process of
 <a href="#semantics-region-layout"><b>9.3 Region Layout and Presentation</b></a>.</p><div class="div4">
-<h5><a name="semantics-style-resolution-processing-definitions" id="semantics-style-resolution-processing-definitions"></a>8.4.4.1 Conceptual Definitions</h5><p>For the purpose of interpreting the style resolution processing
+<h5><a id="semantics-style-resolution-processing-definitions"></a>8.4.4.1 Conceptual Definitions</h5><p>For the purpose of interpreting the style resolution processing
 model specified below, the following conceptual definitions apply:</p><dl><dt class="label">[style property]</dt><dd><p>a style property, <em>P</em>, is considered to consist of a
 tuple <code>[name, value]</code>, where the name of the
 property is a tuple <code>[namespace value,
 unqualified name]</code> and the value of the property is a
-tuple <code>[category, type, value expression]</code></p><a name="conceptual-definition-example-style-property" id="conceptual-definition-example-style-property"></a><table class="example"><caption>Example – conceptual style property</caption><tbody><tr><td>
+tuple <code>[category, type, value expression]</code></p><a id="conceptual-definition-example-style-property"></a><table class="example"><caption>Example – conceptual style property</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 [
   ["http://www.w3.org/ns/ttml#styling", "color"],
@@ -3609,7 +3643,7 @@
 identical name, where by "identical name" is meant equality of
 namespace value of name tuple and unqualified name of name tuple;</p><p>in a specified style (property) set, the category of each style
 property is "specified"; a specified style (property) set of an
-element <em>E</em> is referred to as <em>SSS(E)</em>;</p><a name="conceptual-definition-example-specified-style-set" id="conceptual-definition-example-specified-style-set"></a><table class="example"><caption>Example – conceptual (specified) style (property) set</caption><tbody><tr><td>
+element <em>E</em> is referred to as <em>SSS(E)</em>;</p><a id="conceptual-definition-example-specified-style-set"></a><table class="example"><caption>Example – conceptual (specified) style (property) set</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 {
   [
@@ -3632,7 +3666,7 @@
 </pre></div>
 </td></tr></tbody></table><p>in a computed style (property) set, the category of each style
 property is either "specified" or "computed"; a computed style (property) set of an element
-<em>E</em> is referred to as <em>CSS(E)</em>;</p><a name="conceptual-definition-example-computed-style-set" id="conceptual-definition-example-computed-style-set"></a><table class="example"><caption>Example – conceptual (computed) style (property) set</caption><tbody><tr><td>
+<em>E</em> is referred to as <em>CSS(E)</em>;</p><a id="conceptual-definition-example-computed-style-set"></a><table class="example"><caption>Example – conceptual (computed) style (property) set</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 {
   [
@@ -3665,7 +3699,7 @@
 follows: for each style property <em>P<sub>new</sub></em> in
 <em>SS<sub>new</sub></em>, merge <em>P<sub>new</sub></em> into
 <em>SS<sub>old</sub></em>;</p></dd></dl></div><div class="div4">
-<h5><a name="semantics-style-resolution-processing-sss" id="semantics-style-resolution-processing-sss"></a>8.4.4.2 Specified Style Set Processing</h5><p>The specified style set <em>SSS</em> of an element or
+<h5><a id="semantics-style-resolution-processing-sss"></a>8.4.4.2 Specified Style Set Processing</h5><p>The specified style set <em>SSS</em> of an element or
 anonymous span <em>E</em>,
 <em>SSS(E)</em>, is determined according to the following ordered
 rules:</p><ol class="enumar"><li><p><span class="strong">[initialization]</span> initialize
@@ -3710,7 +3744,7 @@
 <em>CSS(PARENT(E))</em>;</p></li><li><p>if the value of <em>P′</em> is not undefined, then merge
 <em>P′</em> into the specified style set of <em>E</em>,
 <em>SSS(E)</em>.</p></li></ol></li></ol></div><div class="div4">
-<h5><a name="semantics-style-resolution-processing-css" id="semantics-style-resolution-processing-css"></a>8.4.4.3 Computed Style Set Processing</h5><p>The computed style set <em>CSS</em> of an element or
+<h5><a id="semantics-style-resolution-processing-css"></a>8.4.4.3 Computed Style Set Processing</h5><p>The computed style set <em>CSS</em> of an element or
 anonymous span <em>E</em>,
 <em>CSS(E)</em>, is determined according to the following ordered
 rules:</p><ol class="enumar"><li><p><span class="strong">[resolve specified styles]</span>
@@ -3733,7 +3767,7 @@
 context of a layout or content element which has a presentation
 context, and not in the non-presentation, declaration context
 of a referentiable <code>style</code> element.</p></div></div><div class="div4">
-<h5><a name="semantics-style-resolution-process-overall" id="semantics-style-resolution-process-overall"></a>8.4.4.4 Style Resolution Process</h5><p>The top-level style resolution process is defined as follows: using
+<h5><a id="semantics-style-resolution-process-overall"></a>8.4.4.4 Style Resolution Process</h5><p>The top-level style resolution process is defined as follows: using
 a preorder traversal of each element and anonymous span,
 <em>E</em>, of an intermediate synchronic document,
 <em>DOC<sub>inter</sub></em>, perform the following ordered
@@ -3746,7 +3780,7 @@
 determine (obtain) the computed style set <em>CSS</em> of
 <em>E</em>, namely, <em>CSS(E)</em>, in accordance with
 <a href="#semantics-style-resolution-processing-css"><b>8.4.4.3 Computed Style Set Processing</b></a>.</p></li></ol></div></div></div></div><div class="div1">
-<h2><a name="layout" id="layout"></a>9 Layout</h2><p>This section specifies the <em>layout</em> matter of the core
+<h2><a id="layout"></a>9 Layout</h2><p>This section specifies the <em>layout</em> matter of the core
 vocabulary catalog, where
 layout is to be understood as a separable layer of information that applies to
 content and that denotes authorial intentions about the presentation of
@@ -3758,12 +3792,12 @@
 exists – use of referential styling –
 in which the style
 matter is not embedded (inlined).</p></div><div class="div2">
-<h3><a name="layout-element-vocabulary" id="layout-element-vocabulary"></a>9.1 Layout Element Vocabulary</h3><p>The following elements specify the structure and principal layout aspects of a
-document instance:</p><ul><li><p><a href="#layout-vocabulary-layout"><b>9.1.1 layout</b></a></p></li><li><p><a href="#layout-vocabulary-region"><b>9.1.2 region</b></a></p></li></ul><div class="div3">
-<h4><a name="layout-vocabulary-layout" id="layout-vocabulary-layout"></a>9.1.1 layout</h4><p>The <code>layout</code> element is a container element used to group
+<h3><a id="layout-element-vocabulary"></a>9.1 Layout Element Vocabulary</h3><p>The following elements specify the structure and principal layout aspects of a
+<em>Document Instance</em>:</p><ul><li><p><a href="#layout-vocabulary-layout"><b>9.1.1 layout</b></a></p></li><li><p><a href="#layout-vocabulary-region"><b>9.1.2 region</b></a></p></li></ul><div class="div3">
+<h4><a id="layout-vocabulary-layout"></a>9.1.1 layout</h4><p>The <code>layout</code> element is a container element used to group
 layout matter, including metadata that applies to layout matter.</p><p>The <code>layout</code> element accepts as its children zero or more
 elements in the <code>Metadata.class</code> element group, followed by
-zero or more <code>region</code> elements.</p><a name="elt-syntax-layout" id="elt-syntax-layout"></a><table class="syntax"><caption>XML Representation – Element Information Item: layout</caption><tbody><tr><td>
+zero or more <code>region</code> elements.</p><a id="elt-syntax-layout"></a><table class="syntax"><caption>XML Representation – Element Information Item: layout</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;layout
   <a href="#content-attribute-id">xml:id</a> = ID
@@ -3776,7 +3810,7 @@
 </td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
 <code>layout</code> element, the implied time interval of this element is
 defined to be coterminous with the <em>Root Temporal Extent</em>.</p></div><div class="div3">
-<h4><a name="layout-vocabulary-region" id="layout-vocabulary-region"></a>9.1.2 region</h4><p>The <code>region</code> element is used to define a space or area into which content is
+<h4><a id="layout-vocabulary-region"></a>9.1.2 region</h4><p>The <code>region</code> element is used to define a space or area into which content is
 to be flowed for the purpose of presentation.</p><p>In addition, and in accordance with
 <a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>, 
 the <code>region</code> element may be used to specify inheritable style properties to be
@@ -3791,7 +3825,7 @@
 element group apply semantically to the <code>region</code> element.
 Any <code>style</code> child element must be considered a local style
 definition that applies only to the containing <code>region</code>
-element, i.e., does not apply for resolving referential styling.</p><a name="elt-syntax-region" id="elt-syntax-region"></a><table class="syntax"><caption>XML Representation – Element Information Item: region</caption><tbody><tr><td>
+element, i.e., does not apply for resolving referential styling.</p><a id="elt-syntax-region"></a><table class="syntax"><caption>XML Representation – Element Information Item: region</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region
   <a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>
@@ -3815,7 +3849,7 @@
 If specified, these begin and end points are relative to the time
 interval of the nearest ancestor element associated with a time
 interval, irregardless of whether that interval is explicit or implied.</p><p>The nearest ancestor element of a <code>region</code> element that is associated
-with a time interval is the document instance's root <code>tt</code> element.</p><p>If a <code>dur</code> attribute is specified on the <code>region</code> element, then it
+with a time interval is the <em>Document Instance</em>'s root <code>tt</code> element.</p><p>If a <code>dur</code> attribute is specified on the <code>region</code> element, then it
 specifies the simple duration of the region.</p><p>For the purpose of determining the semantics of presentation processing, a
 region that is temporally inactive must not produce any visible marks when
 presented on a visual medium.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>region</code> element may be associated with a time interval for two
@@ -3836,33 +3870,32 @@
 by this attribute expresses the semantic role(s) of the region
 independently from the semantic role(s) of any content targeted to
 (associated with) the region.</p></div></div><div class="div2">
-<h3><a name="layout-attribute-vocabulary" id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with content elements.</p><div class="div3">
-<h4><a name="layout-attribute-region" id="layout-attribute-region"></a>9.2.1 region</h4><p>The <code>region</code> attribute is used to reference a <code>region</code>
+<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with content elements.</p><div class="div3">
+<h4><a id="layout-attribute-region"></a>9.2.1 region</h4><p>The <code>region</code> attribute is used to reference a <code>region</code>
 element which defines a space or area into which a content element is intended to be flowed.</p><p>The <code>region</code> attribute may be specified by an instance of the following
 element types:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#semantics-region-layout"><b>9.3 Region Layout and Presentation</b></a> below for further information on content
 flow in a region.</p></div></div></div><div class="div2">
-<h3><a name="semantics-region-layout" id="semantics-region-layout"></a>9.3 Region Layout and Presentation</h3><p>This section defines the semantics of region layout and
+<h3><a id="semantics-region-layout"></a>9.3 Region Layout and Presentation</h3><p>This section defines the semantics of region layout and
 presentation in terms of a standard processing model as
 follows:</p><ul><li><p><a href="#semantics-default-region"><b>9.3.1 Default Region</b></a></p></li><li><p><a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a></p></li><li><p><a href="#semantics-region-layout-step-2"><b>9.3.3 Synchronic Flow Processing</b></a></p></li><li><p><a href="#semantics-region-layout-example"><b>9.3.4 Elaborated Example (Informative)</b></a></p></li></ul><p>Any
 implementation is permitted provided that the externally observable
 results are consistent with the results produced by this model.
 </p><div class="div3">
-<h4><a name="semantics-default-region" id="semantics-default-region"></a>9.3.1 Default Region</h4><p>If a TTML document instance does not specify a
+<h4><a id="semantics-default-region"></a>9.3.1 Default Region</h4><p>If a <em>Document Instance</em> does not specify a
 <a href="#layout-vocabulary-region"><code>region</code></a> element,
 then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be anonymous;</p></li><li><p>the extent of the default region is the same as the root container
 region;</p></li><li><p>the temporal interval of the default region is the same as temporal
-interval of the document instance;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element was
+interval of the <em>Document Instance</em>;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element was
 specified, then the <a href="#layout-attribute-region"><code>region</code></a> attribute must
-not be specified on any content element in the document
-instance.</p><p>If a default region is implied for a given document instance, then
+not be specified on any content element in the <em>Document Instance</em>.</p><p>If a default region is implied for a given <em>Document Instance</em>, then
 the <a href="#document-structure-vocabulary-body"><code>body</code></a> element
-is implicitly targeted to (associated with) the default region.</p><p>When implying a default region, the document instance is to be
+is implicitly targeted to (associated with) the default region.</p><p>When implying a default region, the <em>Document Instance</em> is to be
 treated as if a <a href="#layout-vocabulary-region"><code>region</code></a> element and its
 parent <a href="#layout-vocabulary-layout"><code>layout</code></a>
 element were specified in a <a href="#document-structure-vocabulary-head"><code>head</code></a>
 element, and a matching <a href="#layout-attribute-region"><code>region</code></a> attribute were
 specified on the <a href="#document-structure-vocabulary-body"><code>body</code></a> element
-as shown in the following example:</p><a name="semantics-default-region-example" id="semantics-default-region-example"></a><table class="example"><caption>Example – Implied Default Region</caption><tbody><tr><td>
+as shown in the following example:</p><a id="semantics-default-region-example"></a><table class="example"><caption>Example – Implied Default Region</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"&gt;
   &lt;head&gt;
@@ -3876,11 +3909,10 @@
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, a default <code>region</code> element and <code>region</code>
 attribute are implied. In addition, a <code>layout</code> container element is implied for
 the implied <code>region</code> element.</p></div></div><div class="div3">
-<h4><a name="semantics-region-layout-step-1" id="semantics-region-layout-step-1"></a>9.3.2 Intermediate Synchronic Document Construction</h4><p>For the purposes of performing presentation processing, the active time
-duration of a document instance is divided into a sequence of time coordinates where at
+<h4><a id="semantics-region-layout-step-1"></a>9.3.2 Intermediate Synchronic Document Construction</h4><p>For the purposes of performing presentation processing, the active time
+duration of a <em>Document Instance</em> is divided into a sequence of time coordinates where at
 each time coordinate, some element becomes temporally active or inactive,
-then, at each such time coordinate, a document
-instance is mapped from its original, source
+then, at each such time coordinate, a <em>Document Instance</em> is mapped from its original, source
 form, <em>DOC<sub>source</sub></em> , 
 to an intermediate
 synchronic document form,
@@ -3911,16 +3943,16 @@
 <a href="#layout-vocabulary-region"><code>region</code></a> element),
 then the element is associated with the default region;</p></li><li><p>the element is not associated with any region.</p></li></ol><p>The result of performing the processing described above will be a sequence of
 <em>N</em> intermediate  synchronic
-document instances,
+<em>Document Instances</em>,
 <em>DOC<sub><span>inter<sub>0</sub></span></sub></em> …
 <em>DOC<sub><span>inter<sub>N−1</sub></span></sub></em>.</p><div class="note" id="semantics-smooth-scrolling-recommendation"><p class="prefix"><b>Note:</b></p><p>Where an implementation is able to detect significant similarity between two
-adjacent synchronic document instances,
+adjacent synchronic <em>Document Instances</em>,
 <em>DOC<sub><span>inter<sub>N</sub></span></sub></em>
 <em>DOC<sub><span>inter<sub>N−1</sub></span></sub></em>,
 then it is preferred that the implementation make the transition between
 presenting the two instances as smooth as possible, e.g., as described
 by <a href="#cea608c">[CEA-608-C]</a>, § C.3.</p></div></div><div class="div3">
-<h4><a name="semantics-region-layout-step-2" id="semantics-region-layout-step-2"></a>9.3.3 Synchronic Flow Processing</h4><p>Subsequent to performing a temporal (synchronic) slice and subsequent
+<h4><a id="semantics-region-layout-step-2"></a>9.3.3 Synchronic Flow Processing</h4><p>Subsequent to performing a temporal (synchronic) slice and subsequent
 remapping of regionally selected content hierarchy, the resulting intermediate
 synchronic document is subjected to a flow transformation step that produces 
 a rooted flow object tree represented as an XSL FO document instance as defined by <a href="#xsl11">[XSL 1.1]</a>,
@@ -3954,7 +3986,7 @@
 associated with a <code>tts:display</code> style property with the value
 <code>none</code>, map the element to a distinct <code>fo:block</code> element,
 populating the style properties of <code>fo:block</code> by using the computed
-style set associated with each original TTML content element;</p></li><li><p>for the resulting <code>fo:block</code> formatting object
+style set associated with each original TTML Content element;</p></li><li><p>for the resulting <code>fo:block</code> formatting object
 produced in the previous step that corresponds to the <code>body</code>
 element, perform the following ordered sub-steps:</p><ol class="enumla"><li><p>if the <code>display-align</code> style property of this <code>fo:block</code>
 has the value <code>center</code> or <code>after</code>,
@@ -3981,7 +4013,7 @@
 map the element or
 sequence of character items to a distinct <code>fo:inline</code> element,
 populating the style properties of <code>fo:inline</code> by using the computed
-style set associated with each original TTML content element
+style set associated with each original TTML Content element
 or anonymous span;</p></li><li><p>for each <code>br</code> element that is not
 associated with a <code>tts:display</code> style property with the value
 <code>none</code>, map the element to
@@ -3989,7 +4021,7 @@
 properties:</p><ul><li><p><code>character="&amp;#x000A;"</code></p></li><li><p><code>suppress-at-line-break="retain"</code></p></li></ul></li><li><p>for each TTML style property attribute in some computed
 style set that
 has no counterpart in <a href="#xsl11">[XSL 1.1]</a>, map that attribute directly through
-to the relevant formatting object produced by the input TTML content element to
+to the relevant formatting object produced by the input TTML Content element to
 which the style property applies;</p></li><li><p>optionally, synthesize a unique <code>id</code> attribute on each resulting
 formatting object element that relates that element to the input element that
 resulted in that formatting object element;</p></li></ol><p>For each resulting document instance F, if processing requires presentation on a 
@@ -4001,7 +4033,7 @@
 reference to the sole generated <code>fo:simple-page-master</code>
 element, would correspond to the <em>root container region</em> defined
 above in <a href="#definitions"><b>2 Definitions</b></a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Due to the possible presence of TTML style properties or style property values
-in a given TTML document instance for which there is no <a href="#xsl11">[XSL 1.1]</a> counterpart,
+in a given <em>Document Instance</em> for which there is no <a href="#xsl11">[XSL 1.1]</a> counterpart,
 Implementors should recognize that it is the layout model of <a href="#xsl11">[XSL 1.1]</a> that is being referenced
 by this specification, not the requirement to use a compliant <a href="#xsl11">[XSL 1.1]</a> formatting processor,
 since such would not necessarily be sufficient to satisfy the full presentation semantics
@@ -4014,7 +4046,7 @@
 to satisfy alignment in the block progression dimension. For example, this assures that
 the background color associated with the <code>body</code> element, if not <code>transparent</code>,
  will fill the containing region wholly.</p></div></div><div class="div3">
-<h4><a name="semantics-region-layout-example" id="semantics-region-layout-example"></a>9.3.4 Elaborated Example (Informative)</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><a name="region-mapping-example-1-s" id="region-mapping-example-1-s"></a><table class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
+<h4><a id="semantics-region-layout-example"></a>9.3.4 Elaborated Example (Informative)</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><a id="region-mapping-example-1-s"></a><table class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
 <div class="exampleInner"><pre>&lt;tt tts:extent="640px 480px" xml:lang="en"
   xmlns="http://www.w3.org/ns/ttml"
   xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
@@ -4061,9 +4093,9 @@
 the (and, in this case, anonymous) spans reparented into the regions.</p><p>The following, first intermediate document shows the synchronic state at time
 interval [0,1), during which time only division <code>d1</code> is temporally active,
 and where paragraphs <code>p1</code> and <code>p2</code> (and their ancestors)
-are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate documents shown below are not valid TTML document instances,
+are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate documents shown below are not valid <em>Document Instances</em>,
 but rather, are representations of possible internal processing states used for
-didactic purposes.</p></div><a name="region-mapping-example-1-i0" id="region-mapping-example-1-i0"></a><table class="example"><caption>Example – Intermediate Document – [0s,1s)</caption><tbody><tr><td>
+didactic purposes.</p></div><a id="region-mapping-example-1-i0"></a><table class="example"><caption>Example – Intermediate Document – [0s,1s)</caption><tbody><tr><td>
 <div class="exampleInner"><pre>&lt;tt tts:extent="640px 480px" xml:lang="en"
   xmlns="http://www.w3.org/ns/ttml"
   xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
@@ -4108,7 +4140,7 @@
   An XSL FO document instance that would yield rendering consistent with TTML, and 
   which may be produced by performing flow processing upon the first intermediate 
   document is illustrated below.
-</p><a name="region-mapping-example-1-f0" id="region-mapping-example-1-f0"></a><table class="example"><caption>Example – XSL FO Document – [0s,1s)</caption><tbody><tr><td>
+</p><a id="region-mapping-example-1-f0"></a><table class="example"><caption>Example – XSL FO Document – [0s,1s)</caption><tbody><tr><td>
 <div class="exampleInner"><pre>&lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"&gt;
   &lt;fo:layout-master-set&gt;
     &lt;fo:simple-page-master master-name="m1"
@@ -4179,7 +4211,7 @@
 <code>d2</code> are temporally active, and where paragraphs <code>p1</code> and
 <code>p4</code> (and their ancestors) are selected into region <code>r1</code>
 and paragraphs <code>p2</code> and <code>p3</code> (and their ancestors) are
-selected into region <code>r2</code>.</p><a name="region-mapping-example-1-i1" id="region-mapping-example-1-i1"></a><table class="example"><caption>Example – Intermediate Document – [1s,2s)</caption><tbody><tr><td>
+selected into region <code>r2</code>.</p><a id="region-mapping-example-1-i1"></a><table class="example"><caption>Example – Intermediate Document – [1s,2s)</caption><tbody><tr><td>
 <div class="exampleInner"><pre>&lt;tt tts:extent="640px 480px" xml:lang="en"
   xmlns="http://www.w3.org/ns/ttml"
   xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
@@ -4228,7 +4260,7 @@
 </td></tr></tbody></table><p>The following, third intermediate document shows the synchronic state at time
 interval [2,3), at which time only division <code>d2</code> is temporally active,
 and where paragraphs <code>p4</code> and <code>p3</code> (and their ancestors)
-are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><a name="region-mapping-example-1-i2" id="region-mapping-example-1-i2"></a><table class="example"><caption>Example – Intermediate Document – [2s,3s)</caption><tbody><tr><td>
+are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><a id="region-mapping-example-1-i2"></a><table class="example"><caption>Example – Intermediate Document – [2s,3s)</caption><tbody><tr><td>
 <div class="exampleInner"><pre>&lt;tt tts:extent="640px 480px" xml:lang="en"
   xmlns="http://www.w3.org/ns/ttml"
   xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
@@ -4269,29 +4301,29 @@
 &lt;/tt&gt;
 </pre></div>
 </td></tr></tbody></table></div></div><div class="div2">
-<h3><a name="semantics-line-layout" id="semantics-line-layout"></a>9.4 Line Layout</h3><p>If a profile that applies to a document instance
+<h3><a id="semantics-line-layout"></a>9.4 Line Layout</h3><p>If a profile that applies to a <em>Document Instance</em>
 requires use of the <a href="#feature-lineBreak-uax14">#lineBreak-uax14</a> feature
 (i.e., the value attribute for the feature is specified as <code>use</code>), then
 the recommendations defined by <a href="http://www.unicode.org/reports/tr14/#Algorithm">Line
 Breaking Algorithm</a> <a href="#uax14">[UAX14]</a> apply when performing
-line layout on the content of the document instance.</p></div></div><div class="div1">
-<h2><a name="timing" id="timing"></a>10 Timing</h2><p>This section specifies the <em>timing</em> matter of the core
+line layout on the content of the <em>Document Instance</em>.</p></div></div><div class="div1">
+<h2><a id="timing"></a>10 Timing</h2><p>This section specifies the <em>timing</em> matter of the core
 vocabulary catalog, where
 timing is to be understood as a separable layer of information that applies to
 content and that denotes authorial intentions about the temporal presentation of
 that content.</p><div class="div2">
-<h3><a name="timing-element-vocabulary" id="timing-element-vocabulary"></a>10.1 Timing Element Vocabulary</h3><p>No timing related element vocabulary is defined for use in the core
+<h3><a id="timing-element-vocabulary"></a>10.1 Timing Element Vocabulary</h3><p>No timing related element vocabulary is defined for use in the core
 vocabulary catalog.</p></div><div class="div2">
-<h3><a name="timing-attribute-vocabulary" id="timing-attribute-vocabulary"></a>10.2 Timing Attribute Vocabulary</h3><p>This section defines the following basic timing attributes for use with timed elements:</p><ul><li><p><a href="#timing-attribute-begin"><b>10.2.1 begin</b></a></p></li><li><p><a href="#timing-attribute-end"><b>10.2.2 end</b></a></p></li><li><p><a href="#timing-attribute-dur"><b>10.2.3 dur</b></a></p></li></ul><p>In addition, this section defines the <a href="#timing-attribute-timeContainer"><b>10.2.4 timeContainer</b></a> attribute for use with timed elements
+<h3><a id="timing-attribute-vocabulary"></a>10.2 Timing Attribute Vocabulary</h3><p>This section defines the following basic timing attributes for use with timed elements:</p><ul><li><p><a href="#timing-attribute-begin"><b>10.2.1 begin</b></a></p></li><li><p><a href="#timing-attribute-end"><b>10.2.2 end</b></a></p></li><li><p><a href="#timing-attribute-dur"><b>10.2.3 dur</b></a></p></li></ul><p>In addition, this section defines the <a href="#timing-attribute-timeContainer"><b>10.2.4 timeContainer</b></a> attribute for use with timed elements
 that serve simultaneously as timing containers.</p><div class="div3">
-<h4><a name="timing-attribute-begin" id="timing-attribute-begin"></a>10.2.1 begin</h4><p>The <code>begin</code> attribute is used to specify the begin
+<h4><a id="timing-attribute-begin"></a>10.2.1 begin</h4><p>The <code>begin</code> attribute is used to specify the begin
 point of a temporal interval associated with a timed element. If
 specified, the value of a <code>begin</code> attribute must adhere to
 a &lt;timeExpression&gt; specification as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>The begin point of a temporal interval is included in the
 interval; i.e., the interval is left-wise closed.</p><p>The semantics of the <code>begin</code> attribute are those defined
 by <a href="#smil21">[SMIL 2.1]</a>, § 10.4.1,
 while taking into account any overriding semantics defined by this specification.</p></div><div class="div3">
-<h4><a name="timing-attribute-end" id="timing-attribute-end"></a>10.2.2 end</h4><p>The <code>end</code> attribute is used to specify the ending point
+<h4><a id="timing-attribute-end"></a>10.2.2 end</h4><p>The <code>end</code> attribute is used to specify the ending point
 of a temporal interval associated with a timed element. If
 specified, the value of an <code>end</code> attribute must adhere to a
 &lt;timeExpression&gt; specification as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><p>The ending point of a temporal interval is not included in the
@@ -4305,12 +4337,12 @@
 as [300f,310f).</p></div><p>The semantics of the <code>end</code> attribute are those defined
 by <a href="#smil21">[SMIL 2.1]</a>, § 10.4.1,
 while taking into account any overriding semantics defined by this specification.</p></div><div class="div3">
-<h4><a name="timing-attribute-dur" id="timing-attribute-dur"></a>10.2.3 dur</h4><p>The <code>dur</code> attribute is used to specify the duration of a
+<h4><a id="timing-attribute-dur"></a>10.2.3 dur</h4><p>The <code>dur</code> attribute is used to specify the duration of a
 temporal interval associated with a timed element. If specified,
 the value of a <code>dur</code> attribute must adhere to a
 &lt;timeExpression&gt; specification as defined by <a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When the <code>clock-time</code> form of a &lt;timeExpression&gt; specification
 is used with a <code>dur</code> attribute, it is intended to be interpreted as
-a difference between two implied clock time expressions.</p></div><p>When a TTML document instance specifies the use of the
+a difference between two implied clock time expressions.</p></div><p>When a <em>Document Instance</em> specifies the use of the
 <code>smpte</code> time base and <code>discontinuous</code> marker
 mode, the <code>dur</code> attribute must not be specified on any
 element.</p><p>The semantics of the <code>dur</code> attribute are those defined
@@ -4320,7 +4352,7 @@
 <code>end</code> and <code>dur</code> attributes is equal to the lesser of the value of
 the <code>dur</code> attribute and the difference between the value of the
 <code>end</code> attribute and the element's begin time.</p></div></div><div class="div3">
-<h4><a name="timing-attribute-timeContainer" id="timing-attribute-timeContainer"></a>10.2.4 timeContainer</h4><p>The <code>timeContainer</code> attribute is used to specify a local temporal
+<h4><a id="timing-attribute-timeContainer"></a>10.2.4 timeContainer</h4><p>The <code>timeContainer</code> attribute is used to specify a local temporal
 context by means of which timed child elements are temporally situated.</p><p>If specified, the value of a <code>timeContainer</code> attribute must be one
 of the following:</p><ul><li><p><code>par</code></p></li><li><p><code>seq</code></p></li></ul><p>If the time container semantics of an element instance is <code>par</code>,
 then the temporal intervals of child elements are considered to apply in
@@ -4341,13 +4373,16 @@
 has time container semantics, then <code>par</code> time container semantics must apply.</p><p>Time container semantics applies only to the following element types:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li></ul><p>The semantics of parallel and sequential time
 containment are those defined by <a href="#smil21">[SMIL 2.1]</a>, § 10.4.2,
 while taking into account any overriding semantics defined by this specification.</p></div></div><div class="div2">
-<h3><a name="timing-time-value-expressions" id="timing-time-value-expressions"></a>10.3 Time Value Expressions</h3><p>Timing attribute values include the use of the following expressions:</p><ul><li><p><a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a></p></li></ul><div class="div3">
-<h4><a name="timing-value-timeExpression" id="timing-value-timeExpression"></a>10.3.1 &lt;timeExpression&gt;</h4><p>A &lt;timeExpression&gt; is used to specify a coordinate along
+<h3><a id="timing-time-value-expressions"></a>10.3 Time Value Expressions</h3><p>Timing attribute values include the use of the following expressions:</p><ul><li><p><a href="#timing-value-timeExpression"><b>10.3.1 &lt;timeExpression&gt;</b></a></p></li></ul><div class="div3">
+<h4><a id="timing-value-timeExpression"></a>10.3.1 &lt;timeExpression&gt;</h4><p>A &lt;timeExpression&gt; is used to specify a coordinate within
 some time base, where the applicable time base is determined by the
 <code>ttp:timeBase</code> parameter, and where the semantics defined
-by <a href="#time-expression-semantics"><b>N Time Expression Semantics</b></a> apply.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a>, <a href="#parameter-attribute-frameRate"><b>6.2.4 ttp:frameRate</b></a>, <a href="#parameter-attribute-subFrameRate"><b>6.2.9 ttp:subFrameRate</b></a>, and <a href="#parameter-attribute-tickRate"><b>6.2.10 ttp:tickRate</b></a> for further information on
-explicit specification of time base, frame rate, sub-frame rate, and
-tick rate.</p></div><a name="timeExpression-syntax" id="timeExpression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;timeExpression&gt;</caption><tbody><tr><td>
+by <a href="#time-expression-semantics"><b>N Time Expression Semantics</b></a> apply.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See
+<a href="#parameter-attribute-frameRate"><b>6.2.4 ttp:frameRate</b></a>,
+<a href="#parameter-attribute-subFrameRate"><b>6.2.9 ttp:subFrameRate</b></a>,
+<a href="#parameter-attribute-tickRate"><b>6.2.10 ttp:tickRate</b></a>, and
+<a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a> for further information on
+explicit specification of frame rate, sub-frame rate, tick rate, and time base.</p></div><a id="timeExpression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;timeExpression&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;timeExpression&gt;
   : clock-time
@@ -4405,7 +4440,7 @@
 sub-frame rate determined by the <code>ttp:subFrameRate</code> parameter as defined by <a href="#parameter-attribute-subFrameRate"><b>6.2.9 ttp:subFrameRate</b></a>.
 It is considered an error if a <em>sub-frames</em> term is specified
 when the <code>clock</code> time base applies.</p></div></div><div class="div2">
-<h3><a name="timing-time-intervals" id="timing-time-intervals"></a>10.4 Time Intervals</h3><p>The semantics of time containment, durations, and intervals defined by
+<h3><a id="timing-time-intervals"></a>10.4 Time Intervals</h3><p>The semantics of time containment, durations, and intervals defined by
 <a href="#smil21">[SMIL 2.1]</a> apply to the interpretation of like-named timed elements and timing
 vocabulary defined by this specification, given the following
 constraints:</p><ul><li><p>The implicit duration of an anonymous span is defined as follows: if
@@ -4430,18 +4465,18 @@
 expressions are considered to be equivalent to either offset
 based timing or event based timing in <a href="#smil21">[SMIL 2.1]</a>, where the specific semantics of
 <a href="#time-expression-semantics-smpte"><b>N.3 SMPTE Time Base</b></a> apply.</p></li></ul></div></div><div class="div1">
-<h2><a name="animation" id="animation"></a>11 Animation</h2><p>This section specifies the <em>animation</em> matter of the
+<h2><a id="animation"></a>11 Animation</h2><p>This section specifies the <em>animation</em> matter of the
 core vocabulary catalog, where
 animation is to be understood as a separable layer of information that combines
 timing and styling in order to denote authorial intention about (temporally) dynamic
 styling of content.</p><div class="div2">
-<h3><a name="animation-element-vocabulary" id="animation-element-vocabulary"></a>11.1 Animation Element Vocabulary</h3><p>The following elements specify the structure and principal animation aspects of a
-document instance:</p><ul><li><p><a href="#animation-vocabulary-set"><b>11.1.1 set</b></a></p></li></ul><div class="div3">
-<h4><a name="animation-vocabulary-set" id="animation-vocabulary-set"></a>11.1.1 set</h4><p>The <code>set</code> element is used as a child element of a content
+<h3><a id="animation-element-vocabulary"></a>11.1 Animation Element Vocabulary</h3><p>The following elements specify the structure and principal animation aspects of a
+<em>Document Instance</em>:</p><ul><li><p><a href="#animation-vocabulary-set"><b>11.1.1 set</b></a></p></li></ul><div class="div3">
+<h4><a id="animation-vocabulary-set"></a>11.1.1 set</h4><p>The <code>set</code> element is used as a child element of a content
 element or a <code>region</code> element
 in order to express a discrete change of some style parameter value
 that applies over some time interval.</p><p>The <code>set</code> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group.</p><a name="elt-syntax-set" id="elt-syntax-set"></a><table class="syntax"><caption>XML Representation – Element Information Item: set</caption><tbody><tr><td>
+elements in the <code>Metadata.class</code> element group.</p><a id="elt-syntax-set"></a><table class="syntax"><caption>XML Representation – Element Information Item: set</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;set
   <a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>
@@ -4457,7 +4492,7 @@
 </pre></div>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of multiple <code>set</code> element children may be used to effect fade and
 position transitions.</p></div><p>An example of using the <code>set</code> element to animate content
-styling is illustrated below:</p><a name="animation-vocabulary-set-example-1" id="animation-vocabulary-set-example-1"></a><table class="example"><caption>Example Fragment – Content Style Animation</caption><tbody><tr><td>
+styling is illustrated below:</p><a id="animation-vocabulary-set-example-1"></a><table class="example"><caption>Example Fragment – Content Style Animation</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ...
 &lt;p dur="5s" tts:color="yellow"&gt;
@@ -4471,7 +4506,7 @@
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the foreground color of the content "Text
 with Flashing Colors" is animated from yellow, to red, to green, to
 red, then back to yellow over a 5 second period.</p></div><p>An example of using the <code>set</code> element to animate region
-styling is illustrated below:</p><a name="animation-vocabulary-set-example-2" id="animation-vocabulary-set-example-2"></a><table class="example"><caption>Example Fragment – Region Style Animation</caption><tbody><tr><td>
+styling is illustrated below:</p><a id="animation-vocabulary-set-example-2"></a><table class="example"><caption>Example Fragment – Region Style Animation</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"
     xmlns:ttp="http://www.w3.org/ns/ttml#parameter"
@@ -4500,23 +4535,23 @@
 to avoid obscuring characters in an underlying video with captions.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>set</code> element
 are based upon that defined by <a href="#smil21">[SMIL 2.1]</a>,
 § 3.6.2.</p></div></div></div><div class="div2">
-<h3><a name="animation-attribute-vocabulary" id="animation-attribute-vocabulary"></a>11.2 Animation Attribute Vocabulary</h3><p>No animation related attribute vocabulary is defined for use in the
+<h3><a id="animation-attribute-vocabulary"></a>11.2 Animation Attribute Vocabulary</h3><p>No animation related attribute vocabulary is defined for use in the
 core vocabulary catalog.</p></div></div><div class="div1">
-<h2><a name="metadata" id="metadata"></a>12 Metadata</h2><p>This section specifies the <em>metadata</em> matter of the core
+<h2><a id="metadata"></a>12 Metadata</h2><p>This section specifies the <em>metadata</em> matter of the core
 vocabulary catalog, where
 metadata is to be understood as a separable layer of information that applies to
 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 document instance, and (2) arbitrary
+specification for standardized use in a <em>Document Instance</em>, and (2) arbitrary
 metadata defined outside of the scope of this specification, whose use and
-semantics depend entirely upon an application's use of TTML content.</p><div class="div2">
-<h3><a name="metadata-element-vocabulary" id="metadata-element-vocabulary"></a>12.1 Metadata Element Vocabulary</h3><p>The <a href="#metadata-vocabulary-metadata"><b>12.1.1 metadata</b></a> element serves as
+semantics depend entirely upon an application's use of TTML Content.</p><div class="div2">
+<h3><a id="metadata-element-vocabulary"></a>12.1 Metadata Element Vocabulary</h3><p>The <a href="#metadata-vocabulary-metadata"><b>12.1.1 metadata</b></a> element serves as
 a generic container element for grouping metadata information.</p><p>In addition, the following elements, all defined in the TT Metadata Namespace,
 provide standard representations for common metadata that is expected to be commonly
-used in a document instances:
+used in a <em>Document Instances</em>:
 </p><ul><li><p><a href="#metadata-vocabulary-title"><b>12.1.2 ttm:title</b></a></p></li><li><p><a href="#metadata-vocabulary-desc"><b>12.1.3 ttm:desc</b></a></p></li><li><p><a href="#metadata-vocabulary-copyright"><b>12.1.4 ttm:copyright</b></a></p></li><li><p><a href="#metadata-vocabulary-agent"><b>12.1.5 ttm:agent</b></a></p></li><li><p><a href="#metadata-vocabulary-name"><b>12.1.6 ttm:name</b></a></p></li><li><p><a href="#metadata-vocabulary-actor"><b>12.1.7 ttm:actor</b></a></p></li></ul><div class="div3">
-<h4><a name="metadata-vocabulary-metadata" id="metadata-vocabulary-metadata"></a>12.1.1 metadata</h4><p>The <code>metadata</code> element functions as a generic container for metadata
+<h4><a id="metadata-vocabulary-metadata"></a>12.1.1 metadata</h4><p>The <code>metadata</code> element functions as a generic container for metadata
 information.</p><p>Metadata information may be expressed by a <code>metadata</code> element
 in one of two (non-mutually exclusive) manners: (1) by specifying one
 or more metadata attributes on the <code>metadata</code>
@@ -4524,7 +4559,7 @@
 or more child elements
 in the <code>metadata</code> element
 that express metadata. Both types of metadata
-are referred to in this document as <em>metadata items</em>.</p><a name="elt-syntax-metadata" id="elt-syntax-metadata"></a><table class="syntax"><caption>XML Representation – Element Information Item: metadata</caption><tbody><tr><td>
+are referred to in this document as <em>metadata items</em>.</p><a id="elt-syntax-metadata"></a><table class="syntax"><caption>XML Representation – Element Information Item: metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;metadata
   <a href="#content-attribute-id">xml:id</a> = ID
@@ -4541,7 +4576,7 @@
 content element type except for the
 <code>tt</code> element. See specific element
 vocabulary definitions for any constraints that apply to such
-usage.</p></div><p>The use of document metadata is illustrated by the following example.</p><a name="metadata-vocabulary-metadata-example-1" id="metadata-vocabulary-metadata-example-1"></a><table class="example"><caption>Example Fragment – Document Metadata</caption><tbody><tr><td>
+usage.</p></div><p>The use of document metadata is illustrated by the following example.</p><a id="metadata-vocabulary-metadata-example-1"></a><table class="example"><caption>Example Fragment – Document Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ...
 &lt;head&gt;
@@ -4552,7 +4587,7 @@
 &lt;/head&gt;
 ...
 </pre></div>
-</td></tr></tbody></table><p></p><p>The use of element metadata is illustrated by the following example.</p><a name="metadata-vocabulary-metadata-example-2" id="metadata-vocabulary-metadata-example-2"></a><table class="example"><caption>Example Fragment – Element Metadata</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><p>The use of element metadata is illustrated by the following example.</p><a id="metadata-vocabulary-metadata-example-2"></a><table class="example"><caption>Example Fragment – Element Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ...
 &lt;div&gt;
@@ -4563,10 +4598,10 @@
 &lt;/div&gt;
 ...
 </pre></div>
-</td></tr></tbody></table><p></p><p>The use of metadata attribute items is illustrated by the following example.</p><a name="metadata-vocabulary-metadata-example-3" id="metadata-vocabulary-metadata-example-3"></a><table class="example"><caption>Example Fragment – Foreign Metadata Attribute Items</caption><tbody><tr><td>
+</td></tr></tbody></table><p></p><p>The use of metadata attribute items is illustrated by the following example.</p><a id="metadata-vocabulary-metadata-example-3"></a><table class="example"><caption>Example Fragment – Foreign Metadata Attribute Items</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ...
-&lt;div xmlns:ext="http://foo.bar.example.org/ttaf1#metadata"&gt;
+&lt;div xmlns:ext="http://example.org/ttaf1#metadata"&gt;
   &lt;metadata ext:ednote="remove this division prior to publishing"/&gt;
 &lt;/div&gt;
 ...
@@ -4577,7 +4612,7 @@
 attribute may also be expressed directly on the <code>div</code> element;
 however, in this case the author wishes to segregate certain metadata
 attributes by expressing them indirectly on <code>metadata</code>
-elements.</p></div><p></p><p>The use of foreign element metadata is illustrated by the following example.</p><a name="metadata-vocabulary-metadata-example-4" id="metadata-vocabulary-metadata-example-4"></a><table class="example"><caption>Example Fragment – Foreign Element Metadata</caption><tbody><tr><td>
+elements.</p></div><p></p><p>The use of foreign element metadata is illustrated by the following example.</p><a id="metadata-vocabulary-metadata-example-4"></a><table class="example"><caption>Example Fragment – Foreign Element Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ...
 &lt;metadata
@@ -4592,8 +4627,8 @@
 </pre></div>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, a number of elements defined by the Dublin
 Core metadata vocabulary are used to express document level metadata.</p></div><p></p></div><div class="div3">
-<h4><a name="metadata-vocabulary-title" id="metadata-vocabulary-title"></a>12.1.2 ttm:title</h4><p>The <code>ttm:title</code> element is used to express a human-readable title of
-a specific element instance.</p><a name="elt-syntax-metadata-title" id="elt-syntax-metadata-title"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:title</caption><tbody><tr><td>
+<h4><a id="metadata-vocabulary-title"></a>12.1.2 ttm:title</h4><p>The <code>ttm:title</code> element is used to express a human-readable title of
+a specific element instance.</p><a id="elt-syntax-metadata-title"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:title</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttm:title
   <a href="#content-attribute-id">xml:id</a> = ID
@@ -4606,8 +4641,8 @@
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:title</code> element is defined by this specification.</p></div><p>Examples of the <code>ttm:title</code> element are shown above in
 <a href="#metadata-vocabulary-metadata-example-1"><b>Example Fragment – Document Metadata</b></a> and
 <a href="#metadata-vocabulary-metadata-example-2"><b>Example Fragment – Element Metadata</b></a>.</p></div><div class="div3">
-<h4><a name="metadata-vocabulary-desc" id="metadata-vocabulary-desc"></a>12.1.3 ttm:desc</h4><p>The <code>ttm:desc</code> element is used to express a human-readable description of
-a specific element instance.</p><a name="elt-syntax-metadata-desc" id="elt-syntax-metadata-desc"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:desc</caption><tbody><tr><td>
+<h4><a id="metadata-vocabulary-desc"></a>12.1.3 ttm:desc</h4><p>The <code>ttm:desc</code> element is used to express a human-readable description of
+a specific element instance.</p><a id="elt-syntax-metadata-desc"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:desc</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttm:desc
   <a href="#content-attribute-id">xml:id</a> = ID
@@ -4620,9 +4655,9 @@
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:desc</code> element is defined by this specification.</p></div><p>Examples of the <code>ttm:desc</code> element are shown above in
 <a href="#metadata-vocabulary-metadata-example-1"><b>Example Fragment – Document Metadata</b></a> and
 <a href="#metadata-vocabulary-metadata-example-2"><b>Example Fragment – Element Metadata</b></a>.</p></div><div class="div3">
-<h4><a name="metadata-vocabulary-copyright" id="metadata-vocabulary-copyright"></a>12.1.4 ttm:copyright</h4><p>The <code>ttm:copyright</code> element is used to express a human-readable copyright that
+<h4><a id="metadata-vocabulary-copyright"></a>12.1.4 ttm:copyright</h4><p>The <code>ttm:copyright</code> element is used to express a human-readable copyright that
 applies to some scoping level.</p><p>A copyright statement that applies to a document as a whole should appear as a
-child of the <code>head</code> element.</p><a name="elt-syntax-metadata-copyright" id="elt-syntax-metadata-copyright"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:copyright</caption><tbody><tr><td>
+child of the <code>head</code> element.</p><a id="elt-syntax-metadata-copyright"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:copyright</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttm:copyright
   <a href="#content-attribute-id">xml:id</a> = ID
@@ -4633,10 +4668,10 @@
 &lt;/ttm:copyright&gt;
 </pre></div>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:copyright</code> element is defined by this specification.</p></div></div><div class="div3">
-<h4><a name="metadata-vocabulary-agent" id="metadata-vocabulary-agent"></a>12.1.5 ttm:agent</h4><p>The <code>ttm:agent</code> element is used to define an agent for the purpose of associating
+<h4><a id="metadata-vocabulary-agent"></a>12.1.5 ttm:agent</h4><p>The <code>ttm:agent</code> element is used to define an agent for the purpose of associating
 content information with an agent who is involved in the production or expression of that content.</p><p>The <code>ttm:agent</code> element accepts as its children zero or more <code>ttm:name</code> elements followed by
 zero or one <code>ttm:actor</code> element.</p><p>At least one <code>ttm:name</code> element child should be specified that expresses a name for the
-agent, whether it be the name of a person, character, group, or organization.</p><a name="elt-syntax-metadata-agent" id="elt-syntax-metadata-agent"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:agent</caption><tbody><tr><td>
+agent, whether it be the name of a person, character, group, or organization.</p><a id="elt-syntax-metadata-agent"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:agent</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttm:agent
   <span class="reqattr">type</span> = (<em>person</em>|<em>character</em>|<em>group</em>|<em>organization</em>|<em>other</em>)
@@ -4655,7 +4690,7 @@
 <code>metadata</code> element child of the <code>head</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>ttm:agent</code> element instance is typically referenced using a <code>ttm:agent</code>
 attribute on a content element.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If a character agent is played by multiple actors, then multiple character
 agents may be specified (and referenced) wherein different definitions of the
-character specify different actors.</p></div><p>The use of agent metadata is illustrated by the following example.</p><a name="metadata-vocabulary-agent-example-1" id="metadata-vocabulary-agent-example-1"></a><table class="example"><caption>Example Fragment – Agent Metadata</caption><tbody><tr><td>
+character specify different actors.</p></div><p>The use of agent metadata is illustrated by the following example.</p><a id="metadata-vocabulary-agent-example-1"></a><table class="example"><caption>Example Fragment – Agent Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 
 &lt;tt xml:lang="en" xmlns="http://www.w3.org/ns/ttml" xmlns:ttm="http://www.w3.org/ns/ttml#metadata"&gt;
@@ -4691,8 +4726,8 @@
 the <code>ttm:agent</code> metadata items are specified as immediate
 children of the document's <code>head</code> element rather than being
 placed in a container <code>metadata</code> element.</p></div></div><div class="div3">
-<h4><a name="metadata-vocabulary-name" id="metadata-vocabulary-name"></a>12.1.6 ttm:name</h4><p>The <code>ttm:name</code> element is used to specify a name of a person, character,
-group, or organization.</p><a name="elt-syntax-metadata-name" id="elt-syntax-metadata-name"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:name</caption><tbody><tr><td>
+<h4><a id="metadata-vocabulary-name"></a>12.1.6 ttm:name</h4><p>The <code>ttm:name</code> element is used to specify a name of a person, character,
+group, or organization.</p><a id="elt-syntax-metadata-name"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:name</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttm:name
   <span class="reqattr">type</span> = (<em>full</em>|<em>family</em>|<em>given</em>|<em>alias</em>|<em>other</em>)
@@ -4707,8 +4742,8 @@
 if specified, must have one of the following values:</p><ul><li><p><code>full</code></p></li><li><p><code>family</code></p></li><li><p><code>given</code></p></li><li><p><code>alias</code></p></li><li><p><code>other</code></p></li></ul><p>The relationship between the type of a name and the syntactic expression of the name
 is not defined by this specification.</p><p>Two examples of the <code>ttm:name</code> element are shown above in
 <a href="#metadata-vocabulary-agent-example-1"><b>Example Fragment – Agent Metadata</b></a>.</p></div><div class="div3">
-<h4><a name="metadata-vocabulary-actor" id="metadata-vocabulary-actor"></a>12.1.7 ttm:actor</h4><p>The <code>ttm:actor</code> element is used to link the definition of a (role-based) character
-agent with another agent that portrays the character.</p><a name="elt-syntax-metadata-actor" id="elt-syntax-metadata-actor"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:actor</caption><tbody><tr><td>
+<h4><a id="metadata-vocabulary-actor"></a>12.1.7 ttm:actor</h4><p>The <code>ttm:actor</code> element is used to link the definition of a (role-based) character
+agent with another agent that portrays the character.</p><a id="elt-syntax-metadata-actor"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:actor</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;ttm:actor
   <span class="reqattr">agent</span> = IDREF
@@ -4723,25 +4758,25 @@
 reference a <code>ttm:agent</code> element that denotes the person,
 group, or organization acting the part of a character.</p><p>An example of the <code>ttm:actor</code> element is shown above in
 <a href="#metadata-vocabulary-agent-example-1"><b>Example Fragment – Agent Metadata</b></a>.</p></div></div><div class="div2">
-<h3><a name="metadata-attribute-vocabulary" id="metadata-attribute-vocabulary"></a>12.2 Metadata Attribute Vocabulary</h3><p>This section specifies the following attributes in the TT Metadata Namespace
+<h3><a id="metadata-attribute-vocabulary"></a>12.2 Metadata Attribute Vocabulary</h3><p>This section specifies the following attributes in the TT Metadata Namespace
 for use with the <code>metadata</code> element and with certain content elements:</p><ul><li><p><a href="#metadata-attribute-agent"><b>12.2.1 ttm:agent</b></a></p></li><li><p><a href="#metadata-attribute-role"><b>12.2.2 ttm:role</b></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Only certain metadata item attributes may be used with content elements. See
 the definitions of content elements to determine permissible usage.</p></div><div class="div3">
-<h4><a name="metadata-attribute-agent" id="metadata-attribute-agent"></a>12.2.1 ttm:agent</h4><p>The <code>ttm:agent</code> attribute takes an <code>IDREFS</code>
+<h4><a id="metadata-attribute-agent"></a>12.2.1 ttm:agent</h4><p>The <code>ttm:agent</code> attribute takes an <code>IDREFS</code>
 value, and is used with certain content elements to designate the
 agents that perform or are
 involved in the performance of the content.</p><p>If specified, a <code>ttm:agent</code> attribute must reference
 <code>ttm:agent</code> element instances that appear
-as a descendent of the same document instance as
+as a descendent of the same <em>Document Instance</em> as
 that of the referring element.</p><p>An example of the <code>ttm:agent</code> attribute is shown above in
 <a href="#metadata-vocabulary-agent-example-1"><b>Example Fragment – Agent Metadata</b></a>.</p></div><div class="div3">
-<h4><a name="metadata-attribute-role" id="metadata-attribute-role"></a>12.2.2 ttm:role</h4><p>The <code>ttm:role</code> attribute may be used by a content author
+<h4><a id="metadata-attribute-role"></a>12.2.2 ttm:role</h4><p>The <code>ttm:role</code> attribute may be used by a content author
 to express
 the roles, functions, or characteristics
 of some content element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
 syntax, where
 the syntactic element <em>S</em> must adhere to production
 [3] <code>S</code> as defined by <a href="#xml10">[XML 1.0]</a>&nbsp;§
-2.3:</p><a name="metadata-attribute-role-syntax" id="metadata-attribute-role-syntax"></a><table class="syntax"><caption>Syntax Representation – ttm:role</caption><tbody><tr><td>
+2.3:</p><a id="metadata-attribute-role-syntax"></a><table class="syntax"><caption>Syntax Representation – ttm:role</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttm:role
   role ( <em>S</em> role )*
@@ -4773,40 +4808,45 @@
   : { XML NameChar }    // XML 1.1 Production [4a]
 </pre></div>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>All values of <code>ttm:role</code> that do not start with the prefix
-<code>x-</code> are reserved for future standardization.</p></div></div></div></div></div><div class="back"><div class="div1">
-<h2><a name="reduced-infoset" id="reduced-infoset"></a>A Reduced XML Infoset</h2><p><em>This appendix is normative.</em></p><p>For the purposes of this specification, a Reduced XML Infoset is
+<code>x-</code> are reserved for future standardization.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If using a custom <code>x-</code> prefixed form of <code>ttm:role</code>, it
+is recommended that an organization unique infix be used as well in order to
+prevent collisions. For example, <code>x-example-org-custom-role</code>. Furthermore,
+a registry for role values is available at
+<a href="http://www.w3.org/wiki/TTML/RoleRegistry">http://www.w3.org/wiki/TTML/RoleRegistry</a>
+in order to promote interoperability and collision avoidance.</p></div></div></div></div></div><div class="back"><div class="div1">
+<h2><a id="reduced-infoset"></a>A Reduced XML Infoset</h2><p><em>This appendix is normative.</em></p><p>For the purposes of this specification, a <em>Reduced XML Infoset</em> is
 an XML Information Set <a href="#infoset">[XML InfoSet]</a> that consists of only the following information items
 and information item properties:</p><div class="div2">
-<h3><a name="reduced-infoset-document" id="reduced-infoset-document"></a>A.1 Document Information Item</h3><ul><li><p><code>[document element]</code></p></li></ul></div><div class="div2">
-<h3><a name="reduced-infoset-element" id="reduced-infoset-element"></a>A.2 Element Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[children]</code></p></li><li><p><code>[attributes]</code></p></li></ul><p>Child information items <code>[children]</code> are reduced to 
+<h3><a id="reduced-infoset-document"></a>A.1 Document Information Item</h3><ul><li><p><code>[document element]</code></p></li></ul></div><div class="div2">
+<h3><a id="reduced-infoset-element"></a>A.2 Element Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[children]</code></p></li><li><p><code>[attributes]</code></p></li></ul><p>Child information items <code>[children]</code> are reduced to 
 only element and character information items.</p></div><div class="div2">
-<h3><a name="reduced-infoset-attribute" id="reduced-infoset-attribute"></a>A.3 Attribute Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[normalized value]</code></p></li></ul></div><div class="div2">
-<h3><a name="reduced-infoset-character" id="reduced-infoset-character"></a>A.4 Character Information Item</h3><ul><li><p><code>[character code]</code></p></li></ul><p>Contiguous character information items are not required to be represented distinctly,
+<h3><a id="reduced-infoset-attribute"></a>A.3 Attribute Information Item</h3><ul><li><p><code>[namespace URI]</code></p></li><li><p><code>[local name]</code></p></li><li><p><code>[normalized value]</code></p></li></ul></div><div class="div2">
+<h3><a id="reduced-infoset-character"></a>A.4 Character Information Item</h3><ul><li><p><code>[character code]</code></p></li></ul><p>Contiguous character information items are not required to be represented distinctly,
 but may be aggregated (chunked) into a sequence of character codes (i.e., a character string).</p></div></div><div class="div1">
-<h2><a name="schemas" id="schemas"></a>B Schemas</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following schemas for use with
-DFXP Content document instances:</p><ul><li><p>Relax NG, Compact Syntax (RNC) Schema</p></li><li><p>XML Schema Definition (XSD) Schema</p></li></ul><p>In any case where a schema specified by this appendix differs from the
+<h2><a id="schemas"></a>B Schemas</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following schemas for use with
+<em>Document Instances</em>:</p><ul><li><p>Relax NG, Compact Syntax (RNC) Schema</p></li><li><p>XML Schema Definition (XSD) Schema</p></li></ul><p>In any case where a schema specified by this appendix differs from the
 normative definitions of document type, element type, or attribute type
 as defined by the body of this specification, then the body of this
 specification takes precedence.</p><div class="div2">
-<h3><a name="dfxp-schema-rnc" id="dfxp-schema-rnc"></a>B.1 Relax NG Schema</h3><p>A Relax NG Compact Syntax (RNC) <a href="#rng">[RELAX NG]</a> based schema
+<h3><a id="ttml-schema-rnc"></a>B.1 Relax NG Compact (RNC) Schema</h3><p>A Relax NG Compact Syntax (RNC) <a href="#rng">[RELAX NG]</a> based schema
 for TTML Content is available at <a href="rnc/schema.zip">ZIP
 Archive</a>. This schema does not normatively define the validity
 of Timed Text Markup Language content as defined by this specification.
-In particular, the formal validity of TTML content
+In particular, the formal validity of TTML Content
 is defined by <a href="#conformance-content"><b>3.1 Content Conformance</b></a>.</p></div><div class="div2">
-<h3><a name="dfxp-schema-xsd" id="dfxp-schema-xsd"></a>B.2 XML Schema Definition (XSD) Schema</h3><p>A W3C XML Schema Definition (XSD) <a href="#xsd-1">[XML Schema Part 1]</a> based schema
+<h3><a id="ttml-schema-xsd"></a>B.2 XML Schema Definition (XSD) Schema</h3><p>A W3C XML Schema Definition (XSD) <a href="#xsd-1">[XML Schema Part 1]</a> based schema
 for TTML Content is available at <a href="xsd/schema.zip">ZIP
 Archive</a>. This schema does not normatively define the validity
 of Timed Text Markup Language content as defined by this specification.
-In particular, the formal validity of TTML content
+In particular, the formal validity of TTML Content
 is defined by <a href="#conformance-content"><b>3.1 Content Conformance</b></a>.</p></div></div><div class="div1">
-<h2><a name="media-types-registration" id="media-types-registration"></a>C Media Type Registration</h2><p><em>This appendix is normative.</em></p><p>This appendix registers a new media type,
+<h2><a id="media-types-registration"></a>C Media Type Registration</h2><p><em>This appendix is normative.</em></p><p>This appendix registers a new media type,
 "application/ttml+xml" in conformance with
 <a href="http://www.ietf.org/rfc/rfc4288.txt">BCP 13</a> and
 <a href="http://www.w3.org/2002/06/registering-mediatype.html">W3CRegMedia</a>.
 The information in this appendix is being submitted to the Internet
 Engineering Steering Group (IESG) for review, approval, and
-registration with the Internet Assigned Numbers Authority (IANA).</p><dl><dt class="label">Type name:</dt><dd><p>application</p></dd><dt class="label">Subtype name:</dt><dd><p>ttml+xml</p></dd><dt class="label">Required parameters:</dt><dd><p>None.</p></dd><dt class="label">Optional parameters:</dt><dd><dl><dt class="label">charset</dt><dd><p>If specified, the <code>charset</code> parameter must match the XML encoding declaration, or if absent, the actual encoding.</p></dd><dt class="label">profile</dt><dd><p>The document profile of a TTML document may be specified using
+registration with the Internet Assigned Numbers Authority (IANA).</p><dl><dt class="label">Type name:</dt><dd><p>application</p></dd><dt class="label">Subtype name:</dt><dd><p>ttml+xml</p></dd><dt class="label">Required parameters:</dt><dd><p>None.</p></dd><dt class="label">Optional parameters:</dt><dd><dl><dt class="label">charset</dt><dd><p>If specified, the <code>charset</code> parameter must match the XML encoding declaration, or if absent, the actual encoding.</p></dd><dt class="label">profile</dt><dd><p>The document profile of a <em>Document Instance</em> may be specified using
 an optional <code>profile</code> parameter, which, if specified,
 the value of which must adhere to the syntax and semantics of
 <code>ttp:profile</code> parameter defined by
@@ -4839,7 +4879,7 @@
 Registration of the Timed Text Markup Language (TTML) 1.0 specification:
 <a href="http://www.w3.org/TR/ttaf1-dfxp/">Timed Text Markup Language (TTML) 1.0</a>.</p></dd><dt class="label">Applications that use this media type:</dt><dd><p>    TTML is used in the television industry for the purpose of authoring, transcoding and exchanging timed text information and for delivering captions for television material repurposed for the internet.</p><p>There is partial and full support of TTML in components used by several Web browsers plugins, and in a number of caption authoring tools.</p></dd><dt class="label">Additional information:</dt><dd><dl><dt class="label">Magic number(s):</dt><dd></dd><dt class="label">File extension(s):</dt><dd><p>.ttml</p></dd><dt class="label">Macintosh file type code(s):</dt><dd><p>"TTML"</p></dd><dt class="label">Fragment identifiers:</dt><dd><p>For documents labeled as application/ttml+xml, the fragment identifier notation is intended to be used with xml:id attributes, as described in section 7.2.1 of the <a href="http://www.w3.org/TR/ttaf1-dfxp/">Timed Text Markup Language (TTML) 1.0</a> specification.</p></dd></dl></dd><dt class="label">Person &amp; email address to contact for further information:</dt><dd><p>Timed Text Working Group (public-tt@w3.org)</p></dd><dt class="label">Intended usage:</dt><dd><p>COMMON</p></dd><dt class="label">Restrictions on usage:</dt><dd><p>None</p></dd><dt class="label">Author:</dt><dd><p>The published specification is a work product of the World Wide Web
 Consortium's Timed Text (TT) Working Group.</p></dd><dt class="label">Change controller:</dt><dd><p>The W3C has change control over this specification.</p></dd></dl></div><div class="div1">
-<h2><a name="features" id="features"></a>D Features</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies (1) a set of feature designations, each of which
+<h2><a id="features"></a>D Features</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies (1) a set of feature designations, each of which
 labels one or more syntactic and/or semantic features defined by this
 specification, and (2) for each designated feature, whether the feature is mandatory
 or optional for a transformation or presentation processor.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A TTML processor is said to <em>implement the transformation semantics</em> or
@@ -4847,7 +4887,7 @@
 if it satisfies the requirements of this appendix with respect to the definition of
 feature designation <em>F</em> as pertains to transformation or
 presentation processing, respectively.</p></div><div class="div2">
-<h3><a name="feature-designations" id="feature-designations"></a>D.1 Feature Designations</h3><p>A feature designation is expressed as a string that adheres to the following
+<h3><a id="feature-designations"></a>D.1 Feature Designations</h3><p>A feature designation is expressed as a string that adheres to the following
 form:</p><div class="exampleInner"><pre>
 feature-designation
   : feature-namespace designation
@@ -4864,12 +4904,12 @@
 for future standardization.</p><p>The following sub-sections define all feature designations, expressed
 as relative URIs (fragment identifiers) with respect to the 
 TT Feature Namespace base URI.</p><div class="div3">
-<h4><a name="feature-animation" id="feature-animation"></a>D.1.1 #animation</h4><p>A TTML transformation processor supports the <code>#animation</code>
+<h4><a id="feature-animation"></a>D.1.1 #animation</h4><p>A TTML transformation processor supports the <code>#animation</code>
 feature if it recognizes and is capable of transforming the following
 vocabulary defined by <a href="#animation"><b>11 Animation</b></a>:</p><ul><li><p><a href="#animation-vocabulary-set"><code>set</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#animation</code>
 feature if it implements presentation semantic support for the
 same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor" id="feature-backgroundColor"></a>D.1.2 #backgroundColor</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor"></a>D.1.2 #backgroundColor</h4><p>A TTML transformation processor supports the
 <code>#backgroundColor</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
 attribute.</p><p>A TTML presentation processor supports the
@@ -4879,7 +4919,7 @@
 and (2) is capable of displaying or generating an output display
 signal that distinguishes between at least sixteen (16) values of color,
 including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor-block" id="feature-backgroundColor-block"></a>D.1.3 #backgroundColor-block</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor-block"></a>D.1.3 #backgroundColor-block</h4><p>A TTML transformation processor supports the
 <code>#backgroundColor-block</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
 attribute when applied to a content element that would generate a
@@ -4891,7 +4931,7 @@
 and (2) is capable of displaying or generating an output display
 signal that distinguishes between at least sixteen (16) values of color,
 including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor-inline" id="feature-backgroundColor-inline"></a>D.1.4 #backgroundColor-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor-inline"></a>D.1.4 #backgroundColor-inline</h4><p>A TTML transformation processor supports the
 <code>#backgroundColor-inline</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
 attribute when applied to a content element that would generate an
@@ -4903,7 +4943,7 @@
 and (2) is capable of displaying or generating an output display
 signal that distinguishes between at least sixteen (16) values of color,
 including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-backgroundColor-region" id="feature-backgroundColor-region"></a>D.1.5 #backgroundColor-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-backgroundColor-region"></a>D.1.5 #backgroundColor-region</h4><p>A TTML transformation processor supports the
 <code>#backgroundColor-region</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
 attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
@@ -4914,44 +4954,44 @@
 signal that distinguishes between at least sixteen (16) values of color,
 including all primary and secondary colors of the SRGB color space
 .</p></div><div class="div3">
-<h4><a name="feature-bidi" id="feature-bidi"></a>D.1.6 #bidi</h4><p>A TTML processor supports the <code>#bidi</code> feature if it
+<h4><a id="feature-bidi"></a>D.1.6 #bidi</h4><p>A TTML processor supports the <code>#bidi</code> feature if it
 supports the following features:</p><ul><li><p><a href="#feature-direction"><code>#direction</code></a></p></li><li><p><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></p></li><li><p><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></p></li></ul></div><div class="div3">
-<h4><a name="feature-cellResolution" id="feature-cellResolution"></a>D.1.7 #cellResolution</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-cellResolution"></a>D.1.7 #cellResolution</h4><p>A TTML transformation processor supports the
 <code>#cellResolution</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#cellResolution</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode" id="feature-clockMode"></a>D.1.8 #clockMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode"></a>D.1.8 #clockMode</h4><p>A TTML transformation processor supports the
 <code>#clockMode</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#clockMode</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode-gps" id="feature-clockMode-gps"></a>D.1.9 #clockMode-gps</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode-gps"></a>D.1.9 #clockMode-gps</h4><p>A TTML transformation processor supports the
 <code>#clockMode-gps</code> feature if it recognizes and is capable of
 transforming the <code>gps</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#clockMode-gps</code> feature if it implements presentation semantic support
 for the <code>gps</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode-local" id="feature-clockMode-local"></a>D.1.10 #clockMode-local</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode-local"></a>D.1.10 #clockMode-local</h4><p>A TTML transformation processor supports the
 <code>#clockMode-local</code> feature if it recognizes and is capable of
 transforming the <code>local</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#clockMode-local</code> feature if it implements presentation semantic support
 for the <code>local</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-clockMode-utc" id="feature-clockMode-utc"></a>D.1.11 #clockMode-utc</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-clockMode-utc"></a>D.1.11 #clockMode-utc</h4><p>A TTML transformation processor supports the
 <code>#clockMode-utc</code> feature if it recognizes and is capable of
 transforming the <code>utc</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#clockMode-utc</code> feature if it implements presentation semantic support
 for the <code>utc</code> value of the <a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-color" id="feature-color"></a>D.1.12 #color</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-color"></a>D.1.12 #color</h4><p>A TTML transformation processor supports the
 <code>#color</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-color"><code>tts:color</code></a>
 attribute.</p><p>A TTML presentation processor supports the
@@ -4961,31 +5001,31 @@
 and (2) is capable of displaying or generating an output display
 signal that distinguishes between at least sixteen (16) values of color,
 including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
-<h4><a name="feature-content" id="feature-content"></a>D.1.13 #content</h4><p>A TTML transformation processor supports the <code>#content</code>
+<h4><a id="feature-content"></a>D.1.13 #content</h4><p>A TTML transformation processor supports the <code>#content</code>
 feature if it recognizes and is capable of transforming the following
 vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#content-vocabulary-br"><code>br</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#content</code>
 feature if it implements presentation semantic support for the
 same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-core" id="feature-core"></a>D.1.14 #core</h4><p>A TTML transformation processor supports the <code>#core</code>
+<h4><a id="feature-core"></a>D.1.14 #core</h4><p>A TTML transformation processor supports the <code>#core</code>
 feature if it recognizes and is capable of transforming the following
 core attributes vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#content-attribute-id">@<code>xml:id</code></a></p></li><li><p><a href="#content-attribute-id">@<code>xml:lang</code></a></p></li><li><p><a href="#content-attribute-id">@<code>xml:space</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#core</code>
 feature if it implements presentation semantic support for the
 same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-direction" id="feature-direction"></a>D.1.15 #direction</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-direction"></a>D.1.15 #direction</h4><p>A TTML transformation processor supports the
 <code>#direction</code> feature if it recognizes and is capable of
 transforming all defined values of the <a href="#style-attribute-direction"><code>tts:direction</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#direction</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-direction"><code>tts:direction</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-display" id="feature-display"></a>D.1.16 #display</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display"></a>D.1.16 #display</h4><p>A TTML transformation processor supports the
 <code>#display</code> feature if it recognizes and is capable of
 transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#display</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-display-block" id="feature-display-block"></a>D.1.17 #display-block</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display-block"></a>D.1.17 #display-block</h4><p>A TTML transformation processor supports the
 <code>#display-block</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute when applied to a content element that would generate a
@@ -4994,7 +5034,7 @@
 support for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute when applied to a content element that generates a
 block area.</p></div><div class="div3">
-<h4><a name="feature-display-inline" id="feature-display-inline"></a>D.1.18 #display-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display-inline"></a>D.1.18 #display-inline</h4><p>A TTML transformation processor supports the
 <code>#display-inline</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute when applied to a content element that would generate an
@@ -5003,77 +5043,77 @@
 support for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute when applied to a content element that generates an
 inline area.</p></div><div class="div3">
-<h4><a name="feature-display-region" id="feature-display-region"></a>D.1.19 #display-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-display-region"></a>D.1.19 #display-region</h4><p>A TTML transformation processor supports the
 <code>#display-region</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
 <code>#display-region</code> feature if it implements presentation semantic
 support for all defined values of the <a href="#style-attribute-display"><code>tts:display</code></a>
 attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-displayAlign" id="feature-displayAlign"></a>D.1.20 #displayAlign</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-displayAlign"></a>D.1.20 #displayAlign</h4><p>A TTML transformation processor supports the
 <code>#displayAlign</code> feature if it recognizes and is capable of
 transforming all defined values of the <a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#displayAlign</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode" id="feature-dropMode"></a>D.1.21 #dropMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode"></a>D.1.21 #dropMode</h4><p>A TTML transformation processor supports the
 <code>#dropMode</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#dropMode</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode-dropNTSC" id="feature-dropMode-dropNTSC"></a>D.1.22 #dropMode-dropNTSC</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode-dropNTSC"></a>D.1.22 #dropMode-dropNTSC</h4><p>A TTML transformation processor supports the
 <code>#dropMode-dropNTSC</code> feature if it recognizes and is capable of
 transforming the <code>dropNTSC</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#dropMode-dropNTSC</code> feature if it implements presentation semantic support
 for the <code>dropNTSC</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode-dropPAL" id="feature-dropMode-dropPAL"></a>D.1.23 #dropMode-dropPAL</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode-dropPAL"></a>D.1.23 #dropMode-dropPAL</h4><p>A TTML transformation processor supports the
 <code>#dropMode-dropPAL</code> feature if it recognizes and is capable of
 transforming the <code>dropPAL</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#dropMode-dropPAL</code> feature if it implements presentation semantic support
 for the <code>dropPAL</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-dropMode-nonDrop" id="feature-dropMode-nonDrop"></a>D.1.24 #dropMode-nonDrop</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-dropMode-nonDrop"></a>D.1.24 #dropMode-nonDrop</h4><p>A TTML transformation processor supports the
 <code>#dropMode-nonDrop</code> feature if it recognizes and is capable of
 transforming the <code>nonDrop</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#dropMode-nonDrop</code> feature if it implements presentation semantic support
 for the <code>nonDrop</code> value of the <a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-extent" id="feature-extent"></a>D.1.25 #extent</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-extent"></a>D.1.25 #extent</h4><p>A TTML transformation processor supports the
 <code>#extent</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-extent"><code>tts:extent</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#extent</code> feature if it implements presentation semantic support for
 the <a href="#style-attribute-extent"><code>tts:extent</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-extent-region" id="feature-extent-region"></a>D.1.26 #extent-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-extent-region"></a>D.1.26 #extent-region</h4><p>A TTML transformation processor supports the
 <code>#extent-region</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-extent"><code>tts:extent</code></a>
 attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
 <code>#extent-region</code> feature if it implements presentation semantic support for
 the <a href="#style-attribute-extent"><code>tts:extent</code></a>
 attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-extent-root" id="feature-extent-root"></a>D.1.27 #extent-root</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-extent-root"></a>D.1.27 #extent-root</h4><p>A TTML transformation processor supports the
 <code>#extent-root</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-extent"><code>tts:extent</code></a>
 attribute when applied to the <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element.</p><p>A TTML presentation processor supports the
 <code>#extent-root</code> feature if it implements presentation semantic support for
 the <a href="#style-attribute-extent"><code>tts:extent</code></a>
 attribute when applied to a <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-fontFamily" id="feature-fontFamily"></a>D.1.28 #fontFamily</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontFamily"></a>D.1.28 #fontFamily</h4><p>A TTML transformation processor supports the
 <code>#fontFamily</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#fontFamily</code> feature if it implements presentation semantic support
 for the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontFamily-generic" id="feature-fontFamily-generic"></a>D.1.29 #fontFamily-generic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontFamily-generic"></a>D.1.29 #fontFamily-generic</h4><p>A TTML transformation processor supports the
 <code>#fontFamily-generic</code> feature if it recognizes and is
 capable of transforming <a href="#style-value-genericFamilyName">&lt;genericFamilyName&gt;</a>
 values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
@@ -5082,7 +5122,7 @@
 support for <a href="#style-value-genericFamilyName">&lt;genericFamilyName&gt;</a>
 values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontFamily-non-generic" id="feature-fontFamily-non-generic"></a>D.1.30 #fontFamily-non-generic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontFamily-non-generic"></a>D.1.30 #fontFamily-non-generic</h4><p>A TTML transformation processor supports the
 <code>#fontFamily-non-generic</code> feature if it recognizes and is
 capable of transforming <a href="#style-value-familyName">&lt;familyName&gt;</a>
 values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
@@ -5091,83 +5131,83 @@
 support for <a href="#style-value-familyName">&lt;familyName&gt;</a>
 values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontSize" id="feature-fontSize"></a>D.1.31 #fontSize</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontSize"></a>D.1.31 #fontSize</h4><p>A TTML transformation processor supports the
 <code>#fontSize</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#fontSize</code> feature if it implements presentation semantic support
 for the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontSize-anamorphic" id="feature-fontSize-anamorphic"></a>D.1.32 #fontSize-anamorphic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontSize-anamorphic"></a>D.1.32 #fontSize-anamorphic</h4><p>A TTML transformation processor supports the
 <code>#fontSize-anamorphic</code> feature if it recognizes and is
 capable of transforming values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
 attribute that consist of two <a href="#style-value-length">&lt;length&gt;</a> specifications.</p><p>A TTML presentation processor supports the
 <code>#fontSize-anamorphic</code> feature if it implements presentation semantic
 support for defined values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
 attribute that consist of two <a href="#style-value-length">&lt;length&gt;</a> specifications.</p></div><div class="div3">
-<h4><a name="feature-fontSize-isomorphic" id="feature-fontSize-isomorphic"></a>D.1.33 #fontSize-isomorphic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontSize-isomorphic"></a>D.1.33 #fontSize-isomorphic</h4><p>A TTML transformation processor supports the
 <code>#fontSize-isomorphic</code> feature if it recognizes and is
 capable of transforming values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
 attribute that consist of a single <a href="#style-value-length">&lt;length&gt;</a> specification.</p><p>A TTML presentation processor supports the
 <code>#fontSize-isomorphic</code> feature if it implements presentation semantic
 support for defined values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
 attribute that consist of a single <a href="#style-value-length">&lt;length&gt;</a> specification.</p></div><div class="div3">
-<h4><a name="feature-fontStyle" id="feature-fontStyle"></a>D.1.34 #fontStyle</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontStyle"></a>D.1.34 #fontStyle</h4><p>A TTML transformation processor supports the
 <code>#fontStyle</code> feature if it recognizes and is capable of
 transforming all defined values of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#fontStyle</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontStyle-italic" id="feature-fontStyle-italic"></a>D.1.35 #fontStyle-italic</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontStyle-italic"></a>D.1.35 #fontStyle-italic</h4><p>A TTML transformation processor supports the
 <code>#fontStyle-italic</code> feature if it recognizes and is
 capable of transforming the <code>italic</code> value of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#fontStyle-italic</code> feature if it implements presentation semantic
 support for the <code>italic</code> of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontStyle-oblique" id="feature-fontStyle-oblique"></a>D.1.36 #fontStyle-oblique</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontStyle-oblique"></a>D.1.36 #fontStyle-oblique</h4><p>A TTML transformation processor supports the
 <code>#fontStyle-oblique</code> feature if it recognizes and is
 capable of transforming the <code>oblique</code> value of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#fontStyle-oblique</code> feature if it implements presentation semantic
 support for the <code>oblique</code> of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontWeight" id="feature-fontWeight"></a>D.1.37 #fontWeight</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontWeight"></a>D.1.37 #fontWeight</h4><p>A TTML transformation processor supports the
 <code>#fontWeight</code> feature if it recognizes and is capable of
 transforming all defined values of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#fontWeight</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-fontWeight-bold" id="feature-fontWeight-bold"></a>D.1.38 #fontWeight-bold</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-fontWeight-bold"></a>D.1.38 #fontWeight-bold</h4><p>A TTML transformation processor supports the
 <code>#fontWeight-bold</code> feature if it recognizes and is
 capable of transforming <code>bold</code> value of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#fontWeight-bold</code> feature if it implements presentation semantic
 support for the <code>bold</code> of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-frameRate" id="feature-frameRate"></a>D.1.39 #frameRate</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-frameRate"></a>D.1.39 #frameRate</h4><p>A TTML transformation processor supports the
 <code>#frameRate</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#frameRate</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-frameRateMultiplier" id="feature-frameRateMultiplier"></a>D.1.40 #frameRateMultiplier</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-frameRateMultiplier"></a>D.1.40 #frameRateMultiplier</h4><p>A TTML transformation processor supports the
 <code>#frameRateMultiplier</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#frameRateMultiplier</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-layout" id="feature-layout"></a>D.1.41 #layout</h4><p>A TTML transformation processor supports the <code>#layout</code>
+<h4><a id="feature-layout"></a>D.1.41 #layout</h4><p>A TTML transformation processor supports the <code>#layout</code>
 feature if it (1) recognizes and is capable of transforming the following
 vocabulary defined by <a href="#layout"><b>9 Layout</b></a>:</p><ul><li><p><a href="#layout-vocabulary-layout"><code>layout</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#layout-attribute-region">@<code>region</code></a></p></li></ul><p>and (2) supports the following attributes when applied to the
 <a href="#layout-vocabulary-region"><code>region</code></a> element:</p><ul><li><p><a href="#style-attribute-extent"><code>tts:extent</code></a></p></li><li><p><a href="#style-attribute-origin"><code>tts:origin</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#layout</code>
 feature if it implements presentation semantic support for the
 same vocabulary and features enumerated above.</p></div><div class="div3">
-<h4><a name="feature-length" id="feature-length"></a>D.1.42 #length</h4><p>A TTML transformation processor supports the <code>#length</code>
+<h4><a id="feature-length"></a>D.1.42 #length</h4><p>A TTML transformation processor supports the <code>#length</code>
 feature if it recognizes and is capable of transforming all defined
 values of the <a href="#style-value-length">&lt;length&gt;</a>
 style value expression.</p><p>A TTML presentation processor supports the <code>#length</code>
@@ -5182,7 +5222,7 @@
 <code>#length-em</code>,
 <code>#length-percentage</code>, and
 <code>#length-pixel</code>.</p></div></div><div class="div3">
-<h4><a name="feature-length-cell" id="feature-length-cell"></a>D.1.43 #length-cell</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-cell"></a>D.1.43 #length-cell</h4><p>A TTML transformation processor supports the
 <code>#length-cell</code> feature if it recognizes and is capable of
 transforming scalar values of the <a href="#style-value-length">&lt;length&gt;</a> style value expression
 that use <code>c</code> (cell) units.</p><p>A TTML presentation processor supports the
@@ -5193,7 +5233,7 @@
 <code>#length-real</code>,
 <code>#length-positive</code>, or
 <code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-length-em" id="feature-length-em"></a>D.1.44 #length-em</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-em"></a>D.1.44 #length-em</h4><p>A TTML transformation processor supports the
 <code>#length-em</code> feature if it recognizes and is capable of
 transforming scalar values of the <a href="#style-value-length">&lt;length&gt;</a> style value expression
 that use <code>em</code> (EM) units.</p><p>A TTML presentation processor supports the
@@ -5204,7 +5244,7 @@
 <code>#length-real</code>,
 <code>#length-positive</code>, or
 <code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-length-integer" id="feature-length-integer"></a>D.1.45 #length-integer</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-integer"></a>D.1.45 #length-integer</h4><p>A TTML transformation processor supports the
 <code>#length-integer</code> feature if it recognizes and is
 capable of transforming integer values of the <a href="#style-value-length">&lt;length&gt;</a> style value
 expression.</p><p>A TTML presentation processor supports the
@@ -5214,7 +5254,7 @@
 </p><div class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-integer</code> does not, by itself, imply support for
 <code>#length-positive</code> or
 <code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-length-negative" id="feature-length-negative"></a>D.1.46 #length-negative</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-negative"></a>D.1.46 #length-negative</h4><p>A TTML transformation processor supports the
 <code>#length-negative</code> feature if it recognizes and is
 capable of transforming negative values of the <a href="#style-value-length">&lt;length&gt;</a> style value
 expression.</p><p>A TTML presentation processor supports the
@@ -5224,7 +5264,7 @@
 </p><div class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-negative</code> does not, by itself, imply support for
 <code>#length-integer</code> or
 <code>#length-real</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-length-percentage" id="feature-length-percentage"></a>D.1.47 #length-percentage</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-percentage"></a>D.1.47 #length-percentage</h4><p>A TTML transformation processor supports the
 <code>#length-percentage</code> feature if it recognizes and is
 capable of transforming percentage values of the <a href="#style-value-length">&lt;length&gt;</a> style value
 expression.</p><p>A TTML presentation processor supports the
@@ -5236,7 +5276,7 @@
 <code>#length-real</code>,
 <code>#length-positive</code>, or
 <code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-length-pixel" id="feature-length-pixel"></a>D.1.48 #length-pixel</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-pixel"></a>D.1.48 #length-pixel</h4><p>A TTML transformation processor supports the
 <code>#length-pixel</code> feature if it recognizes and is capable of
 transforming scalar values of the <a href="#style-value-length">&lt;length&gt;</a> style value expression
 that use <code>px</code> (pixel) units.</p><p>A TTML presentation processor supports the
@@ -5247,7 +5287,7 @@
 <code>#length-real</code>,
 <code>#length-positive</code>, or
 <code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-length-positive" id="feature-length-positive"></a>D.1.49 #length-positive</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-positive"></a>D.1.49 #length-positive</h4><p>A TTML transformation processor supports the
 <code>#length-positive</code> feature if it recognizes and is
 capable of transforming positive values of the <a href="#style-value-length">&lt;length&gt;</a> style value
 expression.</p><p>A TTML presentation processor supports the
@@ -5259,7 +5299,7 @@
 expressions.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-positive</code> does not, by itself, imply support for
 <code>#length-integer</code> or
 <code>#length-real</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-length-real" id="feature-length-real"></a>D.1.50 #length-real</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-length-real"></a>D.1.50 #length-real</h4><p>A TTML transformation processor supports the
 <code>#length-real</code> feature if it recognizes and is
 capable of transforming real values of the <a href="#style-value-length">&lt;length&gt;</a> style value
 expression.</p><p>A TTML presentation processor supports the
@@ -5271,41 +5311,41 @@
 expressions as well as real valued expressions.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Support for <code>#length-real</code> does not, by itself, imply support for
 <code>#length-positive</code> or
 <code>#length-negative</code> features.</p></div></div><div class="div3">
-<h4><a name="feature-lineBreak-uax14" id="feature-lineBreak-uax14"></a>D.1.51 #lineBreak-uax14</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-lineBreak-uax14"></a>D.1.51 #lineBreak-uax14</h4><p>A TTML transformation processor supports the
 <code>#lineBreak-uax14</code> feature if it recognizes and is capable of
 transforming requirements expressed by <a href="#uax14">[UAX14]</a> into its
 target document space.</p><p>A TTML presentation processor supports the
 <code>#lineBreak-uax14</code> feature if it implements presentation semantic support
 for <a href="#uax14">[UAX14]</a> as applies to line breaking.</p></div><div class="div3">
-<h4><a name="feature-lineHeight" id="feature-lineHeight"></a>D.1.52 #lineHeight</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-lineHeight"></a>D.1.52 #lineHeight</h4><p>A TTML transformation processor supports the
 <code>#lineHeight</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#lineHeight</code> feature if it implements presentation semantic support for
 the <a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-markerMode" id="feature-markerMode"></a>D.1.53 #markerMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-markerMode"></a>D.1.53 #markerMode</h4><p>A TTML transformation processor supports the
 <code>#markerMode</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#markerMode</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-markerMode-continuous" id="feature-markerMode-continuous"></a>D.1.54 #markerMode-continuous</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-markerMode-continuous"></a>D.1.54 #markerMode-continuous</h4><p>A TTML transformation processor supports the
 <code>#markerMode-continuous</code> feature if it recognizes and is capable of
 transforming the <code>continuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#markerMode-continuous</code> feature if it implements presentation semantic support
 for the <code>continuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-markerMode-discontinuous" id="feature-markerMode-discontinuous"></a>D.1.55 #markerMode-discontinuous</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-markerMode-discontinuous"></a>D.1.55 #markerMode-discontinuous</h4><p>A TTML transformation processor supports the
 <code>#markerMode-discontinuous</code> feature if it recognizes and is capable of
 transforming the <code>discontinuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#markerMode-discontinuous</code> feature if it implements presentation semantic support
 for the <code>discontinuous</code> value of the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-metadata" id="feature-metadata"></a>D.1.56 #metadata</h4><p>A TTML transformation processor supports the <code>#metadata</code>
+<h4><a id="feature-metadata"></a>D.1.56 #metadata</h4><p>A TTML transformation processor supports the <code>#metadata</code>
 feature if it recognizes and is capable of transforming the following
 vocabulary defined by <a href="#metadata"><b>12 Metadata</b></a>:</p><ul><li><p><a href="#metadata-vocabulary-metadata"><code>metadata</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:title</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:desc</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:copyright</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:agent</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:name</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:actor</code></a></p></li><li><p><a href="#metadata-attribute-agent">@<code>ttm:agent</code></a></p></li><li><p><a href="#metadata-attribute-role">@<code>ttm:role</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#metadata</code>
 feature if it recognizes and is capable of presenting the information
@@ -5313,17 +5353,17 @@
 presentation of metadata information. The presentation or ability to
 present metadata information is considered to be implementation
 dependent.</p></div></div><div class="div3">
-<h4><a name="feature-nested-div" id="feature-nested-div"></a>D.1.57 #nested-div</h4><p>A TTML transformation processor supports the <code>#nested-div</code>
+<h4><a id="feature-nested-div"></a>D.1.57 #nested-div</h4><p>A TTML transformation processor supports the <code>#nested-div</code>
 feature if it recognizes and is capable of transforming nested
 <a href="#content-vocabulary-div"><code>div</code></a> elements.</p><p>A TTML presentation processor supports the <code>#nested-div</code>
 feature if it implements presentation semantic support for nested
 <a href="#content-vocabulary-div"><code>div</code></a> elements.</p></div><div class="div3">
-<h4><a name="feature-nested-span" id="feature-nested-span"></a>D.1.58 #nested-span</h4><p>A TTML transformation processor supports the <code>#nested-span</code>
+<h4><a id="feature-nested-span"></a>D.1.58 #nested-span</h4><p>A TTML transformation processor supports the <code>#nested-span</code>
 feature if it recognizes and is capable of transforming nested
 <a href="#content-vocabulary-span"><code>span</code></a> elements.</p><p>A TTML presentation processor supports the <code>#nested-span</code>
 feature if it implements presentation semantic support for nested
 <a href="#content-vocabulary-span"><code>span</code></a> elements.</p></div><div class="div3">
-<h4><a name="feature-opacity" id="feature-opacity"></a>D.1.59 #opacity</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-opacity"></a>D.1.59 #opacity</h4><p>A TTML transformation processor supports the
 <code>#opacity</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-opacity"><code>tts:opacity</code></a>
 attribute.</p><p>A TTML presentation processor supports the
@@ -5331,66 +5371,66 @@
 the <a href="#style-attribute-opacity"><code>tts:opacity</code></a>
 attribute and (2) is capable of displaying or generating an output display
 signal that distinguishes between at least eight (8) values of opacity.</p></div><div class="div3">
-<h4><a name="feature-origin" id="feature-origin"></a>D.1.60 #origin</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-origin"></a>D.1.60 #origin</h4><p>A TTML transformation processor supports the
 <code>#origin</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-origin"><code>tts:origin</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#origin</code> feature if it implements presentation semantic support for
 the <a href="#style-attribute-origin"><code>tts:origin</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-overflow" id="feature-overflow"></a>D.1.61 #overflow</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-overflow"></a>D.1.61 #overflow</h4><p>A TTML transformation processor supports the
 <code>#overflow</code> feature if it recognizes and is capable of
 transforming all defined values of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#overflow</code> feature if it implements presentation semantic support for
 all defined values of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-overflow-visible" id="feature-overflow-visible"></a>D.1.62 #overflow-visible</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-overflow-visible"></a>D.1.62 #overflow-visible</h4><p>A TTML transformation processor supports the
 <code>#overflow-visible</code> feature if it recognizes and is capable of
 transforming the <code>visible</code> value of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#overflow-visible</code> feature if it implements presentation semantic support for
 the <code>visible</code> value of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-padding" id="feature-padding"></a>D.1.63 #padding</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding"></a>D.1.63 #padding</h4><p>A TTML transformation processor supports the
 <code>#padding</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-padding"><code>tts:padding</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#padding</code> feature if it implements presentation semantic support for
 the <a href="#style-attribute-padding"><code>tts:padding</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-padding-1" id="feature-padding-1"></a>D.1.64 #padding-1</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-1"></a>D.1.64 #padding-1</h4><p>A TTML transformation processor supports the
 <code>#padding-1</code> feature if it recognizes and is capable of
 transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of one <a href="#style-value-length">&lt;length&gt;</a> specification.</p><p>A TTML presentation processor supports the <code>#padding-1</code>
 feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of one <a href="#style-value-length">&lt;length&gt;</a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-2" id="feature-padding-2"></a>D.1.65 #padding-2</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-2"></a>D.1.65 #padding-2</h4><p>A TTML transformation processor supports the
 <code>#padding-2</code> feature if it recognizes and is capable of
 transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of two <a href="#style-value-length">&lt;length&gt;</a> specification.</p><p>A TTML presentation processor supports the <code>#padding-2</code>
 feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of two <a href="#style-value-length">&lt;length&gt;</a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-3" id="feature-padding-3"></a>D.1.66 #padding-3</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-3"></a>D.1.66 #padding-3</h4><p>A TTML transformation processor supports the
 <code>#padding-3</code> feature if it recognizes and is capable of
 transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of three <a href="#style-value-length">&lt;length&gt;</a> specification.</p><p>A TTML presentation processor supports the <code>#padding-3</code>
 feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of three <a href="#style-value-length">&lt;length&gt;</a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-4" id="feature-padding-4"></a>D.1.67 #padding-4</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-padding-4"></a>D.1.67 #padding-4</h4><p>A TTML transformation processor supports the
 <code>#padding-4</code> feature if it recognizes and is capable of
 transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of four <a href="#style-value-length">&lt;length&gt;</a> specification.</p><p>A TTML presentation processor supports the <code>#padding-4</code>
 feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
 that consist of four <a href="#style-value-length">&lt;length&gt;</a> specification.</p></div><div class="div3">
-<h4><a name="feature-pixelAspectRatio" id="feature-pixelAspectRatio"></a>D.1.68 #pixelAspectRatio</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-pixelAspectRatio"></a>D.1.68 #pixelAspectRatio</h4><p>A TTML transformation processor supports the
 <code>#pixelAspectRatio</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#pixelAspectRatio</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-presentation" id="feature-presentation"></a>D.1.69 #presentation</h4><p>A TTML processor supports the
+<h4><a id="feature-presentation"></a>D.1.69 #presentation</h4><p>A TTML processor supports the
 <code>#presentation</code> feature if it
 (1) satisfies the generic processor criteria defined by 
 <a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>,
@@ -5401,7 +5441,7 @@
 In addition, a TTML processor that supports the
 <code>#presentation</code> feature should satisfy the user agent
 accessibility guidelines specified by <a href="#uaag">[UAAG]</a>.</p></div><div class="div3">
-<h4><a name="feature-profile" id="feature-profile"></a>D.1.70 #profile</h4><p>A TTML transformation processor supports the <code>#profile</code>
+<h4><a id="feature-profile"></a>D.1.70 #profile</h4><p>A TTML transformation processor supports the <code>#profile</code>
 feature if it recognizes and is capable of transforming the
 <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
 attribute on the <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element and
@@ -5409,70 +5449,70 @@
 <a href="#parameter-element-vocabulary"><b>6.1 Parameter Element Vocabulary</b></a>:</p><ul><li><p><a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a></p></li><li><p><a href="#parameter-vocabulary-features"><code>ttp:features</code></a></p></li><li><p><a href="#parameter-vocabulary-feature"><code>ttp:feature</code></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><code>ttp:extensions</code></a></p></li><li><p><a href="#parameter-vocabulary-extension"><code>ttp:extension</code></a></p></li></ul><p>A TTML presentation processor supports the
 <code>#profile</code> feature if it implements presentation semantic support
 for the same vocabulary specified above.</p></div><div class="div3">
-<h4><a name="feature-showBackground" id="feature-showBackground"></a>D.1.71 #showBackground</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-showBackground"></a>D.1.71 #showBackground</h4><p>A TTML transformation processor supports the
 <code>#showBackground</code> feature if it recognizes and is capable
 of transforming all defined values of the <a href="#style-attribute-showBackground"><code>tts:showBackground</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#showBackground</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-showBackground"><code>tts:showBackground</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-structure" id="feature-structure"></a>D.1.72 #structure</h4><p>A TTML transformation processor supports the <code>#structure</code>
+<h4><a id="feature-structure"></a>D.1.72 #structure</h4><p>A TTML transformation processor supports the <code>#structure</code>
 feature if it recognizes and is capable of transforming the following
 vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><code>tt</code></a></p></li><li><p><a href="#document-structure-vocabulary-head"><code>head</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#structure</code>
 feature if it implements presentation semantic support for the
 same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-styling" id="feature-styling"></a>D.1.73 #styling</h4><p>A TTML transformation processor supports the <code>#styling</code>
+<h4><a id="feature-styling"></a>D.1.73 #styling</h4><p>A TTML transformation processor supports the <code>#styling</code>
 feature if it recognizes and is capable of transforming the following
 vocabulary defined by <a href="#styling"><b>8 Styling</b></a>:</p><ul><li><p><a href="#styling-vocabulary-styling"><code>styling</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li><li><p><a href="#style-attribute-style">@<code>style</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#styling</code>
 feature if it implements presentation semantic support for the
 same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-styling-chained" id="feature-styling-chained"></a>D.1.74 #styling-chained</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-chained"></a>D.1.74 #styling-chained</h4><p>A TTML transformation processor supports the
 <code>#styling-chained</code> feature if it recognizes and is capable
 of transforming chained style association as defined by <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p><p>A TTML presentation processor supports the
 <code>#styling-chained</code> feature if it implements presentation semantic
 support for chained style association as defined by <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inheritance-content" id="feature-styling-inheritance-content"></a>D.1.75 #styling-inheritance-content</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-inheritance-content"></a>D.1.75 #styling-inheritance-content</h4><p>A TTML transformation processor supports the
 <code>#styling-inheritance</code> feature if it recognizes and is
 capable of transforming content style inheritance as defined by
 <a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p><p>A TTML presentation processor supports the
 <code>#styling-inheritance-content</code> feature if it implements
 presentation semantic support for content style inheritance as defined by <a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inheritance-region" id="feature-styling-inheritance-region"></a>D.1.76 #styling-inheritance-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-inheritance-region"></a>D.1.76 #styling-inheritance-region</h4><p>A TTML transformation processor supports the
 <code>#styling-inheritance</code> feature if it recognizes and is
 capable of transforming region style inheritance as defined by
 <a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p><p>A TTML presentation processor supports the
 <code>#styling-inheritance-region</code> feature if it implements
 presentation semantic support for region style inheritance as defined by <a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inline" id="feature-styling-inline"></a>D.1.77 #styling-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-inline"></a>D.1.77 #styling-inline</h4><p>A TTML transformation processor supports the
 <code>#styling-inline</code> feature if it recognizes and is capable
 of transforming inline style association as defined by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p><p>A TTML presentation processor supports the
 <code>#styling-inline</code> feature if it implements presentation semantic support
 for inline style association as defined by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-nested" id="feature-styling-nested"></a>D.1.78 #styling-nested</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-nested"></a>D.1.78 #styling-nested</h4><p>A TTML transformation processor supports the
 <code>#styling-nested</code> feature if it recognizes and is capable
 of transforming nested style association as defined by <a href="#semantics-style-association-nested"><b>8.4.1.4 Nested Styling</b></a>.</p><p>A TTML presentation processor supports the
 <code>#styling-nested</code> feature if it implements presentation semantic support
 for nested style association as defined by <a href="#semantics-style-association-nested"><b>8.4.1.4 Nested Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-referential" id="feature-styling-referential"></a>D.1.79 #styling-referential</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-styling-referential"></a>D.1.79 #styling-referential</h4><p>A TTML transformation processor supports the
 <code>#styling-referential</code> feature if it recognizes and is capable
 of transforming referential style association as defined by <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a>.</p><p>A TTML presentation processor supports the
 <code>#styling-referential</code> feature if it implements presentation semantic
 support for referential style association as defined by <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-subFrameRate" id="feature-subFrameRate"></a>D.1.80 #subFrameRate</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-subFrameRate"></a>D.1.80 #subFrameRate</h4><p>A TTML transformation processor supports the
 <code>#subFrameRate</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#subFrameRate</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign" id="feature-textAlign"></a>D.1.81 #textAlign</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textAlign"></a>D.1.81 #textAlign</h4><p>A TTML transformation processor supports the
 <code>#textAlign</code> feature if it recognizes and is capable
 of transforming all defined values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#textAlign</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign-absolute" id="feature-textAlign-absolute"></a>D.1.82 #textAlign-absolute</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textAlign-absolute"></a>D.1.82 #textAlign-absolute</h4><p>A TTML transformation processor supports the
 <code>#textAlign-absolute</code> feature if it recognizes and is
 capable of transforming the <code>left</code>, <code>center</code>,
 and <code>right</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
@@ -5481,7 +5521,7 @@
 support for the <code>left</code>, <code>center</code>, and
 <code>right</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign-relative" id="feature-textAlign-relative"></a>D.1.83 #textAlign-relative</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textAlign-relative"></a>D.1.83 #textAlign-relative</h4><p>A TTML transformation processor supports the
 <code>#textAlign-relative</code> feature if it recognizes and is
 capable of transforming the <code>start</code>, <code>center</code>,
 and <code>end</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
@@ -5490,14 +5530,14 @@
 support for the <code>start</code>, <code>center</code>, and
 <code>end</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration" id="feature-textDecoration"></a>D.1.84 #textDecoration</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration"></a>D.1.84 #textDecoration</h4><p>A TTML transformation processor supports the
 <code>#textDecoration</code> feature if it recognizes and is capable
 of transforming all defined values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#textDecoration</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-over" id="feature-textDecoration-over"></a>D.1.85 #textDecoration-over</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration-over"></a>D.1.85 #textDecoration-over</h4><p>A TTML transformation processor supports the
 <code>#textDecoration-over</code> feature if it recognizes and is
 capable of transforming the <code>overline</code> and
 <code>noOverline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
@@ -5506,7 +5546,7 @@
 presentation semantic support for the <code>overline</code> and
 <code>noOverline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-through" id="feature-textDecoration-through"></a>D.1.86 #textDecoration-through</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration-through"></a>D.1.86 #textDecoration-through</h4><p>A TTML transformation processor supports the
 <code>#textDecoration-through</code> feature if it recognizes and is
 capable of transforming the <code>lineThrough</code> and
 <code>noLineThrough</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
@@ -5515,7 +5555,7 @@
 presentation semantic support for the <code>lineThrough</code> and
 <code>noLineThrough</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-under" id="feature-textDecoration-under"></a>D.1.87 #textDecoration-under</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textDecoration-under"></a>D.1.87 #textDecoration-under</h4><p>A TTML transformation processor supports the
 <code>#textDecoration-under</code> feature if it recognizes and is
 capable of transforming the <code>underline</code> and
 <code>noUnderline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
@@ -5524,63 +5564,63 @@
 presentation semantic support for the <code>underline</code> and
 <code>noUnderline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textOutline" id="feature-textOutline"></a>D.1.88 #textOutline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textOutline"></a>D.1.88 #textOutline</h4><p>A TTML transformation processor supports the
 <code>#textOutline</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#textOutline</code> feature if it implements presentation semantic support
 for the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-textOutline-blurred" id="feature-textOutline-blurred"></a>D.1.89 #textOutline-blurred</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textOutline-blurred"></a>D.1.89 #textOutline-blurred</h4><p>A TTML transformation processor supports the
 <code>#textOutline-blurred</code> feature if it recognizes and is capable of
 transforming values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
 attribute that includes a blur radius specification.</p><p>A TTML presentation processor supports the
 <code>#textOutline-blurred</code> feature if it implements presentation semantic support
 for values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
 attribute that includes a blur radius specification.</p></div><div class="div3">
-<h4><a name="feature-textOutline-unblurred" id="feature-textOutline-unblurred"></a>D.1.90 #textOutline-unblurred</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-textOutline-unblurred"></a>D.1.90 #textOutline-unblurred</h4><p>A TTML transformation processor supports the
 <code>#textOutline-unblurred</code> feature if it recognizes and is capable of
 transforming values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
 attribute that does not include a blur radius specification.</p><p>A TTML presentation processor supports the
 <code>#textOutline-unblurred</code> feature if it implements presentation semantic support
 for values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
 attribute that does not include a blur radius specification.</p></div><div class="div3">
-<h4><a name="feature-tickRate" id="feature-tickRate"></a>D.1.91 #tickRate</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-tickRate"></a>D.1.91 #tickRate</h4><p>A TTML transformation processor supports the
 <code>#tickRate</code> feature if it recognizes and is capable of
 transforming the <a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#tickRate</code> feature if it implements presentation semantic support
 for the <a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-timeBase-clock" id="feature-timeBase-clock"></a>D.1.92 #timeBase-clock</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeBase-clock"></a>D.1.92 #timeBase-clock</h4><p>A TTML transformation processor supports the
 <code>#timeBase-clock</code> feature if it recognizes and is capable
 of transforming the <code>clock</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
 attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p><p>A TTML presentation processor supports the
 <code>#timeBase-clock</code> feature if it implements presentation
 semantic support for the <code>clock</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
 attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p></div><div class="div3">
-<h4><a name="feature-timeBase-media" id="feature-timeBase-media"></a>D.1.93 #timeBase-media</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeBase-media"></a>D.1.93 #timeBase-media</h4><p>A TTML transformation processor supports the
 <code>#timeBase-media</code> feature if it recognizes and is capable
 of transforming the <code>media</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#timeBase-media</code> feature if it implements presentation
 semantic support for the <code>media</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-timeBase-smpte" id="feature-timeBase-smpte"></a>D.1.94 #timeBase-smpte</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeBase-smpte"></a>D.1.94 #timeBase-smpte</h4><p>A TTML transformation processor supports the
 <code>#timeBase-smpte</code> feature if it recognizes and is capable
 of transforming the <code>smpte</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
 attribute and if it supports the <a href="#feature-dropMode"><code>#dropMode</code></a> feature.</p><p>A TTML presentation processor supports the
 <code>#timeBase-smpte</code> feature if it implements presentation
 semantic support for the <code>smpte</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
 attribute and if it supports the <a href="#feature-dropMode"><code>#dropMode</code></a> feature.</p></div><div class="div3">
-<h4><a name="feature-timeContainer" id="feature-timeContainer"></a>D.1.95 #timeContainer</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-timeContainer"></a>D.1.95 #timeContainer</h4><p>A TTML transformation processor supports the
 <code>#timeContainer</code> feature if it recognizes and is capable of
 transforming the <a href="#timing-attribute-timeContainer"><code>timeContainer</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#timeContainer</code> feature if it implements presentation semantic support
 for the <a href="#timing-attribute-timeContainer"><code>timeContainer</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-time-clock" id="feature-time-clock"></a>D.1.96 #time-clock</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-clock"></a>D.1.96 #time-clock</h4><p>A TTML transformation processor supports the
 <code>#time-clock</code> feature if it recognizes and is capable of
 transforming all values of the <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a> that
 satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
@@ -5589,7 +5629,7 @@
 </pre></div><p>A TTML presentation processor supports the
 <code>#time-clock</code> feature if it implements presentation
 semantic support for the same syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-time-clock-with-frames" id="feature-time-clock-with-frames"></a>D.1.97 #time-clock-with-frames</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-clock-with-frames"></a>D.1.97 #time-clock-with-frames</h4><p>A TTML transformation processor supports the
 <code>#time-clock-with-frames</code> feature if it supports the
 <a href="#feature-frameRate"><code>#frameRate</code></a>,
 <a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a>, and
@@ -5603,7 +5643,7 @@
 <code>#time-clock-with-frames</code> feature if it implements
 presentation semantic support for the same features and syntax
 specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset" id="feature-time-offset"></a>D.1.98 #time-offset</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-offset"></a>D.1.98 #time-offset</h4><p>A TTML transformation processor supports the
 <code>#time-offset</code> feature if it recognizes and is capable of
 transforming all values of the <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a> that
 satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
@@ -5612,7 +5652,7 @@
 </pre></div><p>A TTML presentation processor supports the
 <code>#time-offset</code> feature if it implements presentation
 semantic support for the same syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset-with-frames" id="feature-time-offset-with-frames"></a>D.1.99 #time-offset-with-frames</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-offset-with-frames"></a>D.1.99 #time-offset-with-frames</h4><p>A TTML transformation processor supports the
 <code>#time-offset-with-frames</code> feature if it supports the
 <a href="#feature-frameRate"><code>#frameRate</code></a>,
 <a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a>, and
@@ -5626,7 +5666,7 @@
 <code>#time-offset-with-frames</code> feature if it implements
 presentation semantic support for the same features and syntax
 specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset-with-ticks" id="feature-time-offset-with-ticks"></a>D.1.100 #time-offset-with-ticks</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-time-offset-with-ticks"></a>D.1.100 #time-offset-with-ticks</h4><p>A TTML transformation processor supports the
 <code>#time-offset-with-ticks</code> feature if it supports the 
 <a href="#feature-tickRate"><code>#tickRate</code></a> feature
 and if it recognizes and is capable of
@@ -5637,31 +5677,31 @@
 </pre></div><p>A TTML presentation processor supports the
 <code>#time-offset-with-ticks</code> feature if it implements presentation
 semantic support for the same features and syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-timing" id="feature-timing"></a>D.1.101 #timing</h4><p>A TTML transformation processor supports the <code>#timing</code>
+<h4><a id="feature-timing"></a>D.1.101 #timing</h4><p>A TTML transformation processor supports the <code>#timing</code>
 feature if it recognizes and is capable of transforming the following
 vocabulary defined by <a href="#timing"><b>10 Timing</b></a>:</p><ul><li><p><a href="#timing-attribute-begin">@<code>begin</code></a></p></li><li><p><a href="#timing-attribute-dur">@<code>dur</code></a></p></li><li><p><a href="#timing-attribute-end">@<code>end</code></a></p></li></ul><p>A TTML presentation processor supports the <code>#timing</code>
 feature if it implements presentation semantic support for the
 same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-transformation" id="feature-transformation"></a>D.1.102 #transformation</h4><p>A TTML processor supports the
+<h4><a id="feature-transformation"></a>D.1.102 #transformation</h4><p>A TTML processor supports the
 <code>#transformation</code> feature if it
 (1) satisfies the generic processor criteria defined by 
 <a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a> and
 (2) implements the transformation semantics of the following features:</p><ul><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#feature-core"><code>#core</code></a></p></li><li><p><a href="#feature-profile"><code>#profile</code></a></p></li><li><p><a href="#feature-structure"><code>#structure</code></a></p></li><li><p><a href="#feature-time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul></div><div class="div3">
-<h4><a name="feature-unicodeBidi" id="feature-unicodeBidi"></a>D.1.103 #unicodeBidi</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-unicodeBidi"></a>D.1.103 #unicodeBidi</h4><p>A TTML transformation processor supports the
 <code>#unicodeBidi</code> feature if it recognizes and is capable of
 transforming all defined values of the <a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#unicodeBidi</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-visibility" id="feature-visibility"></a>D.1.104 #visibility</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility"></a>D.1.104 #visibility</h4><p>A TTML transformation processor supports the
 <code>#visibility</code> feature if it recognizes and is capable
 of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#visibility</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-visibility-block" id="feature-visibility-block"></a>D.1.105 #visibility-block</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility-block"></a>D.1.105 #visibility-block</h4><p>A TTML transformation processor supports the
 <code>#visibility-block</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute when applied to a content element that would generate a
@@ -5670,7 +5710,7 @@
 support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute when applied to a content element that generates a
 block area.</p></div><div class="div3">
-<h4><a name="feature-visibility-inline" id="feature-visibility-inline"></a>D.1.106 #visibility-inline</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility-inline"></a>D.1.106 #visibility-inline</h4><p>A TTML transformation processor supports the
 <code>#visibility-inline</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute when applied to a content element that would generate an
@@ -5679,28 +5719,28 @@
 support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute when applied to a content element that generates an
 inline area.</p></div><div class="div3">
-<h4><a name="feature-visibility-region" id="feature-visibility-region"></a>D.1.107 #visibility-region</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-visibility-region"></a>D.1.107 #visibility-region</h4><p>A TTML transformation processor supports the
 <code>#visibility-region</code> feature if it recognizes and is
 capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TTML presentation processor supports the
 <code>#visibility-region</code> feature if it implements presentation semantic
 support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
 attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-wrapOption" id="feature-wrapOption"></a>D.1.108 #wrapOption</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-wrapOption"></a>D.1.108 #wrapOption</h4><p>A TTML transformation processor supports the
 <code>#wrapOption</code> feature if it recognizes and is capable
 of transforming all defined values of the <a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#wrapOption</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode" id="feature-writingMode"></a>D.1.109 #writingMode</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode"></a>D.1.109 #writingMode</h4><p>A TTML transformation processor supports the
 <code>#writingMode</code> feature if it recognizes and is capable
 of transforming all defined values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#writingMode</code> feature if it implements presentation semantic support
 for all defined values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-vertical" id="feature-writingMode-vertical"></a>D.1.110 #writingMode-vertical</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-vertical"></a>D.1.110 #writingMode-vertical</h4><p>A TTML transformation processor supports the
 <code>#writingMode-vertical</code> feature if it recognizes and is
 capable of transforming the <code>tbrl</code>, <code>tblr</code>, and
 <code>tb</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -5709,7 +5749,7 @@
 support for the <code>tbrl</code>, <code>tblr</code>, and
 <code>tb</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal" id="feature-writingMode-horizontal"></a>D.1.111 #writingMode-horizontal</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-horizontal"></a>D.1.111 #writingMode-horizontal</h4><p>A TTML transformation processor supports the
 <code>#writingMode-horizontal</code> feature if it recognizes and is
 capable of transforming the <code>lrtb</code>, <code>rltb</code>,
 <code>lr</code> and <code>rl</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -5718,7 +5758,7 @@
 support for the <code>lrtb</code>, <code>rltb</code>, <code>lr</code>
 and <code>rl</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal-lr" id="feature-writingMode-horizontal-lr"></a>D.1.112 #writingMode-horizontal-lr</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-horizontal-lr"></a>D.1.112 #writingMode-horizontal-lr</h4><p>A TTML transformation processor supports the
 <code>#writingMode-horizontal</code> feature if it recognizes and is
 capable of transforming the <code>lrtb</code> and <code>lr</code>
 values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -5727,7 +5767,7 @@
 support for the <code>lrtb</code> and <code>lr</code> values of the
 <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal-rl" id="feature-writingMode-horizontal-rl"></a>D.1.113 #writingMode-horizontal-rl</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-writingMode-horizontal-rl"></a>D.1.113 #writingMode-horizontal-rl</h4><p>A TTML transformation processor supports the
 <code>#writingMode-horizontal</code> feature if it recognizes and is
 capable of transforming the <code>rltb</code> and <code>rl</code>
 values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -5736,25 +5776,25 @@
 support for the <code>rltb</code> and <code>rl</code> values of the
 <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
 attribute.</p></div><div class="div3">
-<h4><a name="feature-zIndex" id="feature-zIndex"></a>D.1.114 #zIndex</h4><p>A TTML transformation processor supports the
+<h4><a id="feature-zIndex"></a>D.1.114 #zIndex</h4><p>A TTML transformation processor supports the
 <code>#zIndex</code> feature if it recognizes and is capable of
 transforming the <a href="#style-attribute-zIndex"><code>tts:zIndex</code></a>
 attribute.</p><p>A TTML presentation processor supports the
 <code>#zIndex</code> feature if it implements presentation semantic support for
 the <a href="#style-attribute-zIndex"><code>tts:zIndex</code></a>
 attribute.</p></div></div><div class="div2">
-<h3><a name="feature-support" id="feature-support"></a>D.2 Feature Support</h3><p>The following table, <a href="#feature-support-table"><b>Table D-1 – Feature Support</b></a>,
+<h3><a id="feature-support"></a>D.2 Feature Support</h3><p>The following table, <a href="#feature-support-table"><b>Table D-1 – Feature Support</b></a>,
 enumerates every defined feature designation (expressed without the TT
 Feature Namespace), and, for each designated feature, specifies
 whether the feature must be implemented, i.e., is mandatory (M), or may be implemented, i.e.,
-is optional (O), for transformation and presentation processors.</p><a name="feature-support-table" id="feature-support-table"></a><table class="common"><caption>Table D-1 – Feature Support</caption><col width="60%" span="1"><col width="20%" span="1"><col width="20%" span="1"><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Transformation</span></td><td><span class="strong">Presentation</span></td></tr><tr><td><a href="#feature-animation"><code>#animation</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor"><code>#backgroundColor</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-block"><code>#backgroundColor-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-inline"><code>#backgroundColor-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-region"><code>#backgroundColor-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-bidi"><code>#bidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-cellResolution"><code>#cellResolution</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode"><code>#clockMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-gps"><code>#clockMode-gps</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-local"><code>#clockMode-local</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-utc"><code>#clockMode-utc</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-color"><code>#color</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-core"><code>#core</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-direction"><code>#direction</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display"><code>#display</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-block"><code>#display-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-inline"><code>#display-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-region"><code>#display-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-displayAlign"><code>#displayAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode"><code>#dropMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-dropNTSC"><code>#dropMode-dropNTSC</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-dropPAL"><code>#dropMode-dropPAL</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-nonDrop"><code>#dropMode-nonDrop</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent"><code>#extent</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent-region"><code>#extent-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent-root"><code>#extent-root</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily"><code>#fontFamily</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-generic"><code>#fontFamily-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-non-generic"><code>#fontFamily-non-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize"><code>#fontSize</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-anamorphic"><code>#fontSize-anamorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle"><code>#fontStyle</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-oblique"><code>#fontStyle-oblique</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight"><code>#fontWeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRate"><code>#frameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-layout"><code>#layout</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length"><code>#length</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-cell"><code>#length-cell</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-em"><code>#length-em</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-integer"><code>#length-integer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-negative"><code>#length-negative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-percentage"><code>#length-percentage</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-pixel"><code>#length-pixel</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-real"><code>#length-real</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineBreak-uax14"><code>#lineBreak-uax14</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineHeight"><code>#lineHeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode"><code>#markerMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode-continuous"><code>#markerMode-continuous</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode-discontinuous"><code>#markerMode-discontinuous</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-metadata"><code>#metadata</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-div"><code>#nested-div</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-span"><code>#nested-span</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-opacity"><code>#opacity</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-origin"><code>#origin</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow"><code>#overflow</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow-visible"><code>#overflow-visible</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding"><code>#padding</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-1"><code>#padding-1</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-2"><code>#padding-2</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-3"><code>#padding-3</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-4"><code>#padding-4</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-pixelAspectRatio"><code>#pixelAspectRatio</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td>O</td><td>M</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-showBackground"><code>#showBackground</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-styling"><code>#styling</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-chained"><code>#styling-chained</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-region"><code>#styling-inheritance-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inline"><code>#styling-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-nested"><code>#styling-nested</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-referential"><code>#styling-referential</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-subFrameRate"><code>#subFrameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign"><code>#textAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-relative"><code>#textAlign-relative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration"><code>#textDecoration</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-over"><code>#textDecoration-over</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-through"><code>#textDecoration-through</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-under"><code>#textDecoration-under</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline"><code>#textOutline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-blurred"><code>#textOutline-blurred</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-unblurred"><code>#textOutline-unblurred</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-tickRate"><code>#tickRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-clock"><code>#timeBase-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-media"><code>#timeBase-media</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-smpte"><code>#timeBase-smpte</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeContainer"><code>#timeContainer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock"><code>#time-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock-with-frames"><code>#time-clock-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset"><code>#time-offset</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-time-offset-with-frames"><code>#time-offset-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset-with-ticks"><code>#time-offset-with-ticks</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timing"><code>#timing</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td>M</td><td>O</td></tr><tr><td><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility"><code>#visibility</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-block"><code>#visibility-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-region"><code>#visibility-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-wrapOption"><code>#wrapOption</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode"><code>#writingMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-vertical"><code>#writingMode-vertical</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-lr"><code>#writingMode-horizontal-lr</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-rl"><code>#writingMode-horizontal-rl</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-zIndex"><code>#zIndex</code></a></td><td>O</td><td>O</td></tr></tbody></table><p>For the sake of convenience, the following table,
+is optional (O), for transformation and presentation processors.</p><a id="feature-support-table"></a><table class="common"><caption>Table D-1 – Feature Support</caption><col width="60%" span="1"><col width="20%" span="1"><col width="20%" span="1"><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Transformation</span></td><td><span class="strong">Presentation</span></td></tr><tr><td><a href="#feature-animation"><code>#animation</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor"><code>#backgroundColor</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-block"><code>#backgroundColor-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-inline"><code>#backgroundColor-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-region"><code>#backgroundColor-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-bidi"><code>#bidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-cellResolution"><code>#cellResolution</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode"><code>#clockMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-gps"><code>#clockMode-gps</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-local"><code>#clockMode-local</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode-utc"><code>#clockMode-utc</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-color"><code>#color</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-core"><code>#core</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-direction"><code>#direction</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display"><code>#display</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-block"><code>#display-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-inline"><code>#display-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-region"><code>#display-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-displayAlign"><code>#displayAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode"><code>#dropMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-dropNTSC"><code>#dropMode-dropNTSC</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-dropPAL"><code>#dropMode-dropPAL</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dropMode-nonDrop"><code>#dropMode-nonDrop</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent"><code>#extent</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent-region"><code>#extent-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent-root"><code>#extent-root</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily"><code>#fontFamily</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-generic"><code>#fontFamily-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-non-generic"><code>#fontFamily-non-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize"><code>#fontSize</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-anamorphic"><code>#fontSize-anamorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle"><code>#fontStyle</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-oblique"><code>#fontStyle-oblique</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight"><code>#fontWeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRate"><code>#frameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-layout"><code>#layout</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length"><code>#length</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-cell"><code>#length-cell</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-em"><code>#length-em</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-integer"><code>#length-integer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-negative"><code>#length-negative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-percentage"><code>#length-percentage</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-pixel"><code>#length-pixel</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-real"><code>#length-real</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineBreak-uax14"><code>#lineBreak-uax14</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineHeight"><code>#lineHeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode"><code>#markerMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode-continuous"><code>#markerMode-continuous</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode-discontinuous"><code>#markerMode-discontinuous</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-metadata"><code>#metadata</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-div"><code>#nested-div</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-span"><code>#nested-span</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-opacity"><code>#opacity</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-origin"><code>#origin</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow"><code>#overflow</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow-visible"><code>#overflow-visible</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding"><code>#padding</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-1"><code>#padding-1</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-2"><code>#padding-2</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-3"><code>#padding-3</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-4"><code>#padding-4</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-pixelAspectRatio"><code>#pixelAspectRatio</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td>O</td><td>M</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-showBackground"><code>#showBackground</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-styling"><code>#styling</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-chained"><code>#styling-chained</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-region"><code>#styling-inheritance-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inline"><code>#styling-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-nested"><code>#styling-nested</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-referential"><code>#styling-referential</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-subFrameRate"><code>#subFrameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign"><code>#textAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-relative"><code>#textAlign-relative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration"><code>#textDecoration</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-over"><code>#textDecoration-over</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-through"><code>#textDecoration-through</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-under"><code>#textDecoration-under</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline"><code>#textOutline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-blurred"><code>#textOutline-blurred</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-unblurred"><code>#textOutline-unblurred</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-tickRate"><code>#tickRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-clock"><code>#timeBase-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-media"><code>#timeBase-media</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-smpte"><code>#timeBase-smpte</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeContainer"><code>#timeContainer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock"><code>#time-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock-with-frames"><code>#time-clock-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset"><code>#time-offset</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-time-offset-with-frames"><code>#time-offset-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset-with-ticks"><code>#time-offset-with-ticks</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timing"><code>#timing</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td>M</td><td>O</td></tr><tr><td><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility"><code>#visibility</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-block"><code>#visibility-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-region"><code>#visibility-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-wrapOption"><code>#wrapOption</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode"><code>#writingMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-vertical"><code>#writingMode-vertical</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-lr"><code>#writingMode-horizontal-lr</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-rl"><code>#writingMode-horizontal-rl</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-zIndex"><code>#zIndex</code></a></td><td>O</td><td>O</td></tr></tbody></table><p>For the sake of convenience, the following table,
 <a href="#feature-transformation-mandatory-table"><b>Table D-2 – Mandatory Features - Transformation</b></a>, enumerates all
 mandatory features for a TTML Transformation Processor, providing additional
 comments to summarize the context of usage or the nature of the feature.
-The TTML Profile Definition Document that defines the corresponding
+The <em>Profile Definition Document</em> that defines the corresponding
 DFXP Transformation Profile is specified in
 <a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a>.
-</p><a name="feature-transformation-mandatory-table" id="feature-transformation-mandatory-table"></a><table class="common"><caption>Table D-2 – Mandatory Features - Transformation</caption><col width="60%" span="1"><col width="40%" span="1"><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
+</p><a id="feature-transformation-mandatory-table"></a><table class="common"><caption>Table D-2 – Mandatory Features - Transformation</caption><col width="60%" span="1"><col width="40%" span="1"><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
 <a href="#document-structure-vocabulary-body"><code>body</code></a>,
 <a href="#content-vocabulary-div"><code>div</code></a>,
 <a href="#content-vocabulary-p"><code>p</code></a>,
@@ -5775,10 +5815,10 @@
 <a href="#feature-presentation-mandatory-table"><b>Table D-3 – Mandatory Features - Presentation</b></a>, enumerates all
 mandatory features for a TTML Presentation Processor, providing additional
 comments to summarize the context of usage or the nature of the feature.
-The TTML Profile Definition Document that defines the corresponding
+The <em>Profile Definition Document</em> that defines the corresponding
 DFXP Presentation Profile is specified in
 <a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a>.
-</p><a name="feature-presentation-mandatory-table" id="feature-presentation-mandatory-table"></a><table class="common"><caption>Table D-3 – Mandatory Features - Presentation</caption><col width="60%" span="1"><col width="40%" span="1"><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
+</p><a id="feature-presentation-mandatory-table"></a><table class="common"><caption>Table D-3 – Mandatory Features - Presentation</caption><col width="60%" span="1"><col width="40%" span="1"><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
 <a href="#document-structure-vocabulary-body"><code>body</code></a>,
 <a href="#content-vocabulary-div"><code>div</code></a>,
 <a href="#content-vocabulary-p"><code>p</code></a>,
@@ -5796,10 +5836,10 @@
 <a href="#timing-attribute-dur">@<code>dur</code></a>,
 <a href="#timing-attribute-end">@<code>end</code></a>
 </td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="extensions" id="extensions"></a>E Extensions</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the syntactic form of extension designations, which are
+<h2><a id="extensions"></a>E Extensions</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the syntactic form of extension designations, which are
 used to express authorial intent regarding the support for extension
 mechanisms in a TTML processor.</p><div class="div2">
-<h3><a name="extension-designations" id="extension-designations"></a>E.1 Extension Designations</h3><p>An extension designation is expressed as a string that adheres to the following
+<h3><a id="extension-designations"></a>E.1 Extension Designations</h3><p>An extension designation is expressed as a string that adheres to the following
 form:</p><div class="exampleInner"><pre>
 extension-designation
   : extension-namespace designation
@@ -5822,10 +5862,10 @@
 capable of serving as a base URI used in combination with a
 <code>designation</code> token that takes the form of a fragment
 identifier.</p></div></div><div class="div1">
-<h2><a name="profiles" id="profiles"></a>F Profiles</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following standard TTML profiles:</p><ul><li><p><a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a></p></li><li><p><a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a></p></li><li><p><a href="#profile-dfxp-full"><b>F.3 DFXP Full Profile</b></a></p></li></ul><p>Each TTML profile is defined in terms of a TTML Profile Definition Document,
+<h2><a id="profiles"></a>F Profiles</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following standard TTML profiles:</p><ul><li><p><a href="#profile-dfxp-transformation"><b>F.1 DFXP Transformation Profile</b></a></p></li><li><p><a href="#profile-dfxp-presentation"><b>F.2 DFXP Presentation Profile</b></a></p></li><li><p><a href="#profile-dfxp-full"><b>F.3 DFXP Full Profile</b></a></p></li></ul><p>Each TTML profile is defined in terms of a <em>Profile Definition Document</em>,
 which is expressed as an XML document wherein the root element adheres to
 <a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p><div class="div2">
-<h3><a name="profile-dfxp-transformation" id="profile-dfxp-transformation"></a>F.1 DFXP Transformation Profile</h3><p>The DFXP Transformation Profile is intended to be used to
+<h3><a id="profile-dfxp-transformation"></a>F.1 DFXP Transformation Profile</h3><p>The DFXP Transformation Profile is intended to be used to
 express minimum compliance for transformation processing.</p><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8"?&gt;
 &lt;!-- this file defines the "dfxp-transformation" profile of ttaf1 --&gt;
 &lt;profile xmlns="http://www.w3.org/ns/ttml#parameter"&gt;
@@ -5954,7 +5994,7 @@
 &lt;/profile&gt;
 
 </pre></div></div><div class="div2">
-<h3><a name="profile-dfxp-presentation" id="profile-dfxp-presentation"></a>F.2 DFXP Presentation Profile</h3><p>The DFXP Presentation Profile is intended to be used to
+<h3><a id="profile-dfxp-presentation"></a>F.2 DFXP Presentation Profile</h3><p>The DFXP Presentation Profile is intended to be used to
 express minimum compliance for presentation processing.</p><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8"?&gt;
 &lt;!-- this file defines the "dfxp-presentation" profile of ttaf1-dfxp --&gt;
 &lt;profile xmlns="http://www.w3.org/ns/ttml#parameter"&gt;
@@ -6083,7 +6123,7 @@
 &lt;/profile&gt;
 
 </pre></div></div><div class="div2">
-<h3><a name="profile-dfxp-full" id="profile-dfxp-full"></a>F.3 DFXP Full Profile</h3><p>The DFXP Full Profile is intended to be used to
+<h3><a id="profile-dfxp-full"></a>F.3 DFXP Full Profile</h3><p>The DFXP Full Profile is intended to be used to
 express maximum compliance for both transformation and presentation processing.</p><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8"?&gt;
 &lt;!-- this file defines the "dfxp-full" profile of ttaf1-dfxp --&gt;
 &lt;profile xmlns="http://www.w3.org/ns/ttml#parameter"&gt;
@@ -6212,173 +6252,173 @@
 &lt;/profile&gt;
 
 </pre></div></div></div><div class="div1">
-<h2><a name="references" id="references"></a>G References</h2><p><em>This appendix is normative.</em></p><dl><dt class="label"><a name="css2" id="css2"></a>CSS2</dt><dd>Bert Bos et al.,
+<h2><a id="references"></a>G References</h2><p><em>This appendix is normative.</em></p><dl><dt class="label"><a id="css2"></a>CSS2</dt><dd>Bert Bos et al.,
 <a href="http://www.w3.org/TR/1998/REC-CSS2-19980512/"><cite>Cascading
 Style Sheets, Level 2</cite></a>, W3C Recommendation, 12
 May 1998. (See
 <a href="http://www.w3.org/TR/1998/REC-CSS2-19980512/">http://www.w3.org/TR/1998/REC-CSS2-19980512/</a>.)
-</dd><dt class="label"><a name="gps" id="gps"></a>GPS</dt><dd>
+</dd><dt class="label"><a id="gps"></a>GPS</dt><dd>
 <a href="http://tycho.usno.navy.mil/gpsinfo.html"><cite>Global
 Positioning System</cite></a>, US Naval Observatory.
 (See
 <a href="http://tycho.usno.navy.mil/gpsinfo.html">http://tycho.usno.navy.mil/gpsinfo.html</a>.)
-</dd><dt class="label"><a name="media-types" id="media-types"></a>Media Types</dt><dd>Ned Freed and Nathaniel Borenstein,  
+</dd><dt class="label"><a id="media-types"></a>Media Types</dt><dd>Ned Freed and Nathaniel Borenstein,  
 <a href="http://www.rfc-editor.org/rfc/rfc2046.txt"><cite>Multipurpose Internet
 Mail Extensions (MIME) Part Two: Media Types</cite></a>,
 RFC 2046, November 1996, IETF.(See
 <a href="http://www.rfc-editor.org/rfc/rfc2046.txt">http://www.rfc-editor.org/rfc/rfc2046.txt</a>.)
-</dd><dt class="label"><a name="rng" id="rng"></a>RELAX NG</dt><dd>ISO/IEC 19757-2,
+</dd><dt class="label"><a id="rng"></a>RELAX NG</dt><dd>ISO/IEC 19757-2,
 <a href="http://www.iso.org/"><cite>Information technology – Document
 Schema Definition Language (DSDL) – Part 2: Regular-grammar-based validation – RELAX NG</cite></a>,
 International Organization for Standardization (ISO).
-</dd><dt class="label"><a name="smil21" id="smil21"></a>SMIL 2.1</dt><dd>Dick Bultermann, et al.,
+</dd><dt class="label"><a id="smil21"></a>SMIL 2.1</dt><dd>Dick Bultermann, et al.,
 <a href="http://www.w3.org/TR/2005/REC-SMIL2-20051213/"><cite>Synchronized
 Multimedia Integration Language (SMIL 2.1)</cite></a>,
 W3C Recommendation, 13 December 2005. (See
 <a href="http://www.w3.org/TR/2005/REC-SMIL2-20051213/">http://www.w3.org/TR/2005/REC-SMIL2-20051213/</a>.)
-</dd><dt class="label"><a name="smpte12m" id="smpte12m"></a>SMPTE 12M</dt><dd>ANSI/SMPTE 12M,
+</dd><dt class="label"><a id="smpte12m"></a>SMPTE 12M</dt><dd>ANSI/SMPTE 12M,
 <a href="https://www.smpte.org/"><cite>Television, Audio and Film –
 Time and Control Code</cite></a>, SMPTE Standard.
-</dd><dt class="label"><a name="srgb" id="srgb"></a>SRGB</dt><dd>IEC 61966-2-1,
+</dd><dt class="label"><a id="srgb"></a>SRGB</dt><dd>IEC 61966-2-1,
 <a href="http://www.iec.ch/"><cite>Multimedia
 systems and equipment – Colour measurement and management
 – Part 2-1: Colour management – Default RGB colour space
 – sRGB</cite></a>, International Electrotechnical
 Commission (IEC).
-</dd><dt class="label"><a name="uaag" id="uaag"></a>UAAG</dt><dd>Ian Jacobs, Jon Gunderson, and Eric Hansen, Eds.,
+</dd><dt class="label"><a id="uaag"></a>UAAG</dt><dd>Ian Jacobs, Jon Gunderson, and Eric Hansen, Eds.,
 <a href="http://www.w3.org/TR/2002/REC-UAAG10-20021217/"><cite>User
 Agent Accessibility Guidelines 1.0</cite></a>, W3C Recommendation, 17
 December 2002. (See
 <a href="http://www.w3.org/TR/2002/REC-UAAG10-20021217/">http://www.w3.org/TR/2002/REC-UAAG10-20021217/</a>.)
-</dd><dt class="label"><a name="utc" id="utc"></a>UTC</dt><dd>
+</dd><dt class="label"><a id="utc"></a>UTC</dt><dd>
 Recommendation TF.460,
 <a href="http://www.itu.int/"><cite>Standard-Frequency and Time-Signal
 Emissions</cite></a>, International
 Telecommunciations Union, Radio Sector (ITU-R).
-</dd><dt class="label"><a name="uax14" id="uax14"></a>UAX14</dt><dd>Asmus Freytag, <a href="http://www.unicode.org/reports/tr14/tr14-17.html"><cite>Line Breaking
+</dd><dt class="label"><a id="uax14"></a>UAX14</dt><dd>Asmus Freytag, <a href="http://www.unicode.org/reports/tr14/tr14-17.html"><cite>Line Breaking
 Properties</cite></a>, Unicode Consortium, 29 August 2005. (See
 <a href="http://www.unicode.org/reports/tr14/tr14-17.html">http://www.unicode.org/reports/tr14/tr14-17.html</a>.)
-</dd><dt class="label"><a name="wcag" id="wcag"></a>WCAG</dt><dd>Ben Caldwell, et al., Eds.,
+</dd><dt class="label"><a id="wcag"></a>WCAG</dt><dd>Ben Caldwell, et al., Eds.,
 <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/"><cite>Web
 Content Accessibility Guidelines (WCAG) 2.0</cite></a>, W3C Recommendation, 11 December 2008. (See
 <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/">http://www.w3.org/TR/2008/REC-WCAG20-20081211/</a>.)
-</dd><dt class="label"><a name="xml10" id="xml10"></a>XML 1.0</dt><dd>Tim Bray, et al.
+</dd><dt class="label"><a id="xml10"></a>XML 1.0</dt><dd>Tim Bray, et al.
 <a href="http://www.w3.org/TR/2008/REC-xml-20081126/"><cite>Extensible Markup Language (XML)
 1.0 (Fifth Edition)</cite></a>, W3C Recommendation, 26 November 2008. (See
 <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>.)
-</dd><dt class="label"><a name="xml11" id="xml11"></a>XML 1.1</dt><dd>Tim Bray, et al.
+</dd><dt class="label"><a id="xml11"></a>XML 1.1</dt><dd>Tim Bray, et al.
 <a href="http://www.w3.org/TR/2006/REC-xml11-20060816/"><cite>Extensible Markup Language (XML)
 1.1 (Second Edition)</cite></a>, W3C Recommendation, 16 August 2006, edited in place 29 September 2006. (See
 <a href="http://www.w3.org/TR/2006/REC-xml11-20060816/">http://www.w3.org/TR/2006/REC-xml11-20060816/</a>.)
-</dd><dt class="label"><a name="xmlbase" id="xmlbase"></a>XML Base</dt><dd>Jonathan Marsh and Richard Tobin, Eds.,
+</dd><dt class="label"><a id="xmlbase"></a>XML Base</dt><dd>Jonathan Marsh and Richard Tobin, Eds.,
 <a href="http://www.w3.org/TR/2009/REC-xmlbase-20090128/"><cite>XML Base (Second Edition)</cite></a>,
 W3C Recommendation, 28 January 2009. (See
 <a href="http://www.w3.org/TR/2009/REC-xmlbase-20090128/">http://www.w3.org/TR/2009/REC-xmlbase-20090128/</a>.)
-</dd><dt class="label"><a name="xmlid" id="xmlid"></a>XML ID</dt><dd>Jonathan Marsh, Daniel Veillard, Norman Walsh, Eds.,
+</dd><dt class="label"><a id="xmlid"></a>XML ID</dt><dd>Jonathan Marsh, Daniel Veillard, Norman Walsh, Eds.,
 <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/"><cite>xml:id Version 1.0</cite></a>,
 W3C Recommendation, 09 September 2005. (See
 <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/">http://www.w3.org/TR/2005/REC-xml-id-20050909/</a>.)
-</dd><dt class="label"><a name="xml-media" id="xml-media"></a>XML Media</dt><dd>Makato Murata, Simon St. Laurent,
+</dd><dt class="label"><a id="xml-media"></a>XML Media</dt><dd>Makato Murata, Simon St. Laurent,
 Kan Khon, Eds., <a href="http://www.rfc-editor.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>,
 RFC 3023, January 2001, IETF.(See
 <a href="http://www.rfc-editor.org/rfc/rfc3023.txt">http://www.rfc-editor.org/rfc/rfc3023.txt</a>.)
-</dd><dt class="label"><a name="infoset" id="infoset"></a>XML InfoSet</dt><dd>John Cowan and Richard Tobin, Eds.,
+</dd><dt class="label"><a id="infoset"></a>XML InfoSet</dt><dd>John Cowan and Richard Tobin, Eds.,
 <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>XML Information Set (Second Edition)</cite></a>,
 W3C Recommendation, 04 February 2004. (See
 <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</a>.)
-</dd><dt class="label"><a name="rfc3023" id="rfc3023"></a>XML Media Types</dt><dd>Makato Murata, et al.,
+</dd><dt class="label"><a id="rfc3023"></a>XML Media Types</dt><dd>Makato Murata, et al.,
 <a href="http://www.rfc-editor.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>,
 RFC 3023, January 2001, IETF.(See
 <a href="http://www.rfc-editor.org/rfc/rfc3023.txt">http://www.rfc-editor.org/rfc/rfc3023.txt</a>.)
-</dd><dt class="label"><a name="xmlns10" id="xmlns10"></a>XML Namespaces 1.0</dt><dd>Tim Bray, et al.
+</dd><dt class="label"><a id="xmlns10"></a>XML Namespaces 1.0</dt><dd>Tim Bray, et al.
 <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/"><cite>Namespaces
 in XML 1.0 (Third Edition)</cite></a>, W3C Recommendation, 8 December 2009. (See
 <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/">http://www.w3.org/TR/2009/REC-xml-names-20091208/</a>.)
-</dd><dt class="label"><a name="xsd-1" id="xsd-1"></a>XML Schema Part 1</dt><dd>Henry S. Thompson, David Beech,
+</dd><dt class="label"><a id="xsd-1"></a>XML Schema Part 1</dt><dd>Henry S. Thompson, David Beech,
 Murray Maloney, Noah Mendelsohn, Eds.,
 <a href="http://www.w3.org/TR/xmlschema-1/"><cite>XML Schema Part 1: Structures</cite></a>,
 W3C Recommendation, 28 October 2004. (See
 <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.)
-</dd><dt class="label"><a name="xsd-2" id="xsd-2"></a>XML Schema Part 2</dt><dd>Paul Biron and Ashok Malhotra,
+</dd><dt class="label"><a id="xsd-2"></a>XML Schema Part 2</dt><dd>Paul Biron and Ashok Malhotra,
 <a href="http://www.w3.org/TR/xmlschema-2/"><cite>XML Schema Part 2: Datatypes</cite></a>,
 W3C Recommendation, 28 October 2004. (See
 <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.)
-</dd><dt class="label"><a name="xsl11" id="xsl11"></a>XSL 1.1</dt><dd>Anders Berglund,
+</dd><dt class="label"><a id="xsl11"></a>XSL 1.1</dt><dd>Anders Berglund,
 <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/"><cite>Extensible Stylesheet Language (XSL) Version 1.1</cite></a>,
 W3C Recommendation, 05 December 2006. (See
 <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/">http://www.w3.org/TR/2006/REC-xsl11-20061205/</a>.)
 </dd></dl></div><div class="div1">
-<h2><a name="other-references" id="other-references"></a>H Other References (Non-Normative)</h2><dl><dt class="label"><a name="ccreq" id="ccreq"></a>CC-DECODER-REQ</dt><dd><a href="http://www.gpo.gov/fdsys/pkg/CFR-2005-title47-vol1/xml/CFR-2005-title47-vol1-sec15-119.xml"><cite>Closed Caption Decoder
+<h2><a id="other-references"></a>H Other References (Non-Normative)</h2><dl><dt class="label"><a id="ccreq"></a>CC-DECODER-REQ</dt><dd><a href="http://www.gpo.gov/fdsys/pkg/CFR-2005-title47-vol1/xml/CFR-2005-title47-vol1-sec15-119.xml"><cite>Closed Caption Decoder
 Requirements for Analog Television</cite></a>,
 United States Code of Federal Regulations, Title 47, Volume 1, Part 15, § 15.119. (See
 <a href="http://www.gpo.gov/fdsys/pkg/CFR-2005-title47-vol1/xml/CFR-2005-title47-vol1-sec15-119.xml">http://www.gpo.gov/fdsys/pkg/CFR-2005-title47-vol1/xml/CFR-2005-title47-vol1-sec15-119.xml</a>.)
-</dd><dt class="label"><a name="cea608c" id="cea608c"></a>CEA-608-C</dt><dd>
+</dd><dt class="label"><a id="cea608c"></a>CEA-608-C</dt><dd>
 EIA/CEA-608-C,
 <a href="http://www.ce.org/"><cite>Line 21 Data
 Services</cite></a>, EIA/CEA Standard,
 Consumer Electronics Association (CEA).
-</dd><dt class="label"><a name="cea708d" id="cea708d"></a>CEA-708-D</dt><dd>
+</dd><dt class="label"><a id="cea708d"></a>CEA-708-D</dt><dd>
 CEA-708-D,
 <a href="http://www.ce.org/"><cite>Digital Television (DTV) Closed Captioning</cite></a>, CEA Standard,
 Consumer Electronics Association (CEA).
-</dd><dt class="label"><a name="css3-color" id="css3-color"></a>CSS3 Color</dt><dd>Tantek Çelik and Chris Lilley,
+</dd><dt class="label"><a id="css3-color"></a>CSS3 Color</dt><dd>Tantek Çelik and Chris Lilley,
 <a href="http://www.w3.org/TR/2003/CR-css3-color-20030514/"><cite>CSS3 Color
 Module</cite></a>, W3C Candidate Recommendation, 14 May 2003. (See
 <a href="http://www.w3.org/TR/2003/CR-css3-color-20030514/">http://www.w3.org/TR/2003/CR-css3-color-20030514/</a>.)
-</dd><dt class="label"><a name="dcmes" id="dcmes"></a>DCMES 1.1</dt><dd>Dublin Core Metadata Initiative,
+</dd><dt class="label"><a id="dcmes"></a>DCMES 1.1</dt><dd>Dublin Core Metadata Initiative,
 <a href="http://dublincore.org/documents/dces/"><cite>Dublin Core Metadata Element Set, Version 1.1: Reference Description</cite></a>. (See
 <a href="http://dublincore.org/documents/dces/">http://dublincore.org/documents/dces/</a>.)
-</dd><dt class="label"><a name="mpeg7-5" id="mpeg7-5"></a>MPEG7-5</dt><dd>
+</dd><dt class="label"><a id="mpeg7-5"></a>MPEG7-5</dt><dd>
 ISO/IEC 15938-5,
 <a href="http://www.iso.org/"><cite>Information technology – Multimedia content description
 interface – Part 5: Multimedia description schemes</cite></a>,
 International Organization for Standardization (ISO).
-</dd><dt class="label"><a name="nsstate" id="nsstate"></a>NSState</dt><dd>Norman Walsh, Ed.,
+</dd><dt class="label"><a id="nsstate"></a>NSState</dt><dd>Norman Walsh, Ed.,
 <a href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html"><cite>The Disposition
 of Names in an XML Namespace</cite></a>, TAG Finding, 9 January 2006. (See
 <a href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html">http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09</a>.)
-</dd><dt class="label"><a name="qaf-sg" id="qaf-sg"></a>QAF SG</dt><dd>Karl Dubost, et al.,
+</dd><dt class="label"><a id="qaf-sg"></a>QAF SG</dt><dd>Karl Dubost, et al.,
 <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/"><cite>QA
 Framework: Specifications Guidelines</cite></a>, W3C Recommendation, 17
 August 2005. (See
 <a href="http://www.w3.org/TR/qaframe-spec/">http://www.w3.org/TR/qaframe-spec/</a>.)
-</dd><dt class="label"><a name="smpte170m" id="smpte170m"></a>SMPTE 170M</dt><dd>ANSI/SMPTE 170M, 
+</dd><dt class="label"><a id="smpte170m"></a>SMPTE 170M</dt><dd>ANSI/SMPTE 170M, 
 <a href="http://www.smpte.org/"><cite>Television – Composite Analog Video
 Signal – NTSC for Studio Applications</cite></a>, SMPTE Standard.
-</dd><dt class="label"><a name="smpte2052" id="smpte2052"></a>SMPTE 2052-11</dt><dd>SMPTE 2052-11,
+</dd><dt class="label"><a id="smpte2052"></a>SMPTE 2052-11</dt><dd>SMPTE 2052-11,
 <a href="http://www.smpte.org/"><cite>Conversion from CEA-708 Caption Data to SMPTE-TT</cite></a>,
 SMPTE Recommended Practice.
-</dd><dt class="label"><a name="svg11" id="svg11"></a>SVG 1.1</dt><dd>Jon Ferraiolo, Jun Fujisawa, Dean Jackson, Eds.,
+</dd><dt class="label"><a id="svg11"></a>SVG 1.1</dt><dd>Jon Ferraiolo, Jun Fujisawa, Dean Jackson, Eds.,
 <a href="http://www.w3.org/TR/2003/REC-SVG11-20030114/"><cite>Scalable
 Vector Graphics (SVG) 1.1 Specification</cite></a>, W3C Recommendation, 14
 January 2003. (See
 <a href="http://www.w3.org/TR/2003/REC-SVG11-20030114/">http://www.w3.org/TR/2003/REC-SVG11-20030114/</a>.)
-</dd><dt class="label"><a name="ttaf1-req" id="ttaf1-req"></a>TTAF1-REQ</dt><dd>Glenn Adams, Ed.,
+</dd><dt class="label"><a id="ttaf1-req"></a>TTAF1-REQ</dt><dd>Glenn Adams, Ed.,
 <a href="http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/"><cite>Timed Text (TT) Authoring Format 1.0 Use
 Cases and Requirements</cite></a>,
 W3C Working Group Note, 27 April 2006. (See
 <a href="http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/">http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/</a>.)
-</dd><dt class="label"><a name="xhtml10" id="xhtml10"></a>XHTML 1.0</dt><dd>Steven Pemberton, et al.,
+</dd><dt class="label"><a id="xhtml10"></a>XHTML 1.0</dt><dd>Steven Pemberton, et al.,
 <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/"><cite>XHTML™ 1.0,
 The Extensible Hypertext Markup Language (Second Edition)</cite></a>,
 W3C Recommendation, 01
 August 2002. (See
 <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>.)
 </dd></dl></div><div class="div1">
-<h2><a name="requirements" id="requirements"></a>I Requirements (Non-Normative)</h2><p>The Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring
+<h2><a id="requirements"></a>I Requirements (Non-Normative)</h2><p>The Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring
 Format (TTML) satisfies a subset of the requirements established by
 <a href="#ttaf1-req">[TTAF1-REQ]</a>. The following table enumerates these requirements and
 indicates the extent to which they are satisfied by this specification, where
 <em>S</em> denotes a requirement is satisfied, <em>P</em> denotes
 a requirement is partially satisfied, and <em>N</em> denotes a
-requirement is not satisfied.</p><a name="requirements-table" id="requirements-table"></a><table class="common"><caption>Table I-1 – Requirement Satisfaction</caption><col width="10%" span="1"><col width="40%" span="1"><col width="10%" span="1"><col span="1"><tbody><tr><th>ID</th><th>Name</th><th>Status</th><th>Comments</th></tr><tr><td>R100</td><td>Specification Format</td><td>S</td><td></td></tr><tr><td>R101</td><td>Specification Modularity</td><td>S</td><td></td></tr><tr><td>R102</td><td>Specification Organization</td><td>S</td><td></td></tr><tr><td>R103</td><td>Core and Periphery</td><td>S</td><td>TT extension namespaces</td></tr><tr><td>R104</td><td>Evolution of Core</td><td>S</td><td>TT extension namespaces</td></tr><tr><td>R105</td><td>Ownership of Core</td><td>S</td><td>TT namespaces</td></tr><tr><td>R106</td><td>Surjection of Core</td><td>S</td><td></td></tr><tr><td>R107</td><td>Evolution of Periphery</td><td>S</td><td>TT extension namespaces</td></tr><tr><td>R108</td><td>Ownership of Periphery</td><td>S</td><td>Non-TT namespaces</td></tr><tr><td>R109</td><td>Transformation</td><td>S</td><td>Supports 3GPP, QText, RealText, SAMI</td></tr><tr><td>R110</td><td>Streamable Transformation</td><td>S</td><td>Progressive decoding</td></tr><tr><td>R111</td><td>Accessibility – Content</td><td>S</td><td>Alternative document instances</td></tr><tr><td>R112</td><td>Accessibility – Authoring System</td><td>S</td><td></td></tr><tr><td>R200</td><td>Authorability</td><td>S</td><td></td></tr><tr><td>R201</td><td>Multiple Natural Languages</td><td>S</td><td>Alternative document instances</td></tr><tr><td>R202</td><td>Natural Language Coverage</td><td>S</td><td>Unicode 4.0</td></tr><tr><td>R203</td><td>Natural Language Association Granularity</td><td>S</td><td>See <code>xml:lang</code></td></tr><tr><td>R204</td><td>Minimum Character Representability</td><td>S</td><td>Unicode 4.0</td></tr><tr><td>R205</td><td>Intrinsic and Extrinsic Text Content</td><td>P</td><td>Intrinsic only</td></tr><tr><td>R206</td><td>Markup Association</td><td>P</td><td>Intrinsic only</td></tr><tr><td>R207</td><td>Conditional Content</td><td>N</td><td></td></tr><tr><td>R208</td><td>Flowed Text</td><td>S</td><td></td></tr><tr><td>R209</td><td>Logical Flowed Text Vocabulary</td><td>S</td><td></td></tr><tr><td>R210</td><td>Presentational Flowed Text Vocabulary</td><td>S</td><td>Implied mapping from logical flowed text.</td></tr><tr><td>R211</td><td>Flowed Text Vocabulary Relationship</td><td>S</td><td></td></tr><tr><td>R212</td><td>Flowed Text Vocabulary Separation</td><td>N</td><td></td></tr><tr><td>R213</td><td>Non-Flowed Text</td><td>N</td><td></td></tr><tr><td>R214</td><td>Non-Flowed Text Vocabulary</td><td>N</td><td></td></tr><tr><td>R215</td><td>Hybrid Flowed and Non-Flowed Text</td><td>N</td><td></td></tr><tr><td>R216</td><td>Hyperlinking</td><td>N</td><td>Can support via XLink</td></tr><tr><td>R217</td><td>Embedded Graphics</td><td>N</td><td></td></tr><tr><td>R218</td><td>Non-Embedded Graphics</td><td>N</td><td></td></tr><tr><td>R219</td><td>Embedded Fonts</td><td>N</td><td></td></tr><tr><td>R220</td><td>Non-Embedded Fonts</td><td>N</td><td></td></tr><tr><td>R221</td><td>Descriptive Vocabulary</td><td>S</td><td>See <code>ttm:agent</code>, <code>ttm:role</code></td></tr><tr><td>R222</td><td>Embedded Audio</td><td>N</td><td></td></tr><tr><td>R223</td><td>Non-Embedded Audio</td><td>N</td><td></td></tr><tr><td>R290</td><td>Markup Format</td><td>S</td><td></td></tr><tr><td>R291</td><td>Markup Format and Unicode Interaction</td><td>S</td><td></td></tr><tr><td>R292</td><td>Extrinsic Resource References</td><td>N</td><td>No extrinsic references</td></tr><tr><td>R293</td><td>Schema Validity Specification</td><td>S</td><td></td></tr><tr><td>R300</td><td>Inline Styling</td><td>S</td><td></td></tr><tr><td>R301</td><td>Inline Styling Form</td><td>P</td><td>Inline and referential styling</td></tr><tr><td>R301</td><td>Out-of-Line Styling</td><td>N</td><td></td></tr><tr><td>R301</td><td>Out-of-Line Styling Form</td><td>N</td><td></td></tr><tr><td>R304</td><td>Styling Prioritization</td><td>S</td><td></td></tr><tr><td>R305</td><td>Style Parameters – Aural</td><td>N</td><td></td></tr><tr><td>R306</td><td>Style Parameters – Visual</td><td>P</td><td>Supports absolute position, background color, color, display none, display alignment,
+requirement is not satisfied.</p><a id="requirements-table"></a><table class="common"><caption>Table I-1 – Requirement Satisfaction</caption><col width="10%" span="1"><col width="40%" span="1"><col width="10%" span="1"><col span="1"><tbody><tr><th>ID</th><th>Name</th><th>Status</th><th>Comments</th></tr><tr><td>R100</td><td>Specification Format</td><td>S</td><td></td></tr><tr><td>R101</td><td>Specification Modularity</td><td>S</td><td></td></tr><tr><td>R102</td><td>Specification Organization</td><td>S</td><td></td></tr><tr><td>R103</td><td>Core and Periphery</td><td>S</td><td>TT extension namespaces</td></tr><tr><td>R104</td><td>Evolution of Core</td><td>S</td><td>TT extension namespaces</td></tr><tr><td>R105</td><td>Ownership of Core</td><td>S</td><td>TT namespaces</td></tr><tr><td>R106</td><td>Surjection of Core</td><td>S</td><td></td></tr><tr><td>R107</td><td>Evolution of Periphery</td><td>S</td><td>TT extension namespaces</td></tr><tr><td>R108</td><td>Ownership of Periphery</td><td>S</td><td>Non-TT namespaces</td></tr><tr><td>R109</td><td>Transformation</td><td>S</td><td>Supports 3GPP, QText, RealText, SAMI</td></tr><tr><td>R110</td><td>Streamable Transformation</td><td>S</td><td>Progressive decoding</td></tr><tr><td>R111</td><td>Accessibility – Content</td><td>S</td><td>Alternative document instances</td></tr><tr><td>R112</td><td>Accessibility – Authoring System</td><td>S</td><td></td></tr><tr><td>R200</td><td>Authorability</td><td>S</td><td></td></tr><tr><td>R201</td><td>Multiple Natural Languages</td><td>S</td><td>Alternative document instances</td></tr><tr><td>R202</td><td>Natural Language Coverage</td><td>S</td><td>Unicode 4.0</td></tr><tr><td>R203</td><td>Natural Language Association Granularity</td><td>S</td><td>See <code>xml:lang</code></td></tr><tr><td>R204</td><td>Minimum Character Representability</td><td>S</td><td>Unicode 4.0</td></tr><tr><td>R205</td><td>Intrinsic and Extrinsic Text Content</td><td>P</td><td>Intrinsic only</td></tr><tr><td>R206</td><td>Markup Association</td><td>P</td><td>Intrinsic only</td></tr><tr><td>R207</td><td>Conditional Content</td><td>N</td><td></td></tr><tr><td>R208</td><td>Flowed Text</td><td>S</td><td></td></tr><tr><td>R209</td><td>Logical Flowed Text Vocabulary</td><td>S</td><td></td></tr><tr><td>R210</td><td>Presentational Flowed Text Vocabulary</td><td>S</td><td>Implied mapping from logical flowed text.</td></tr><tr><td>R211</td><td>Flowed Text Vocabulary Relationship</td><td>S</td><td></td></tr><tr><td>R212</td><td>Flowed Text Vocabulary Separation</td><td>N</td><td></td></tr><tr><td>R213</td><td>Non-Flowed Text</td><td>N</td><td></td></tr><tr><td>R214</td><td>Non-Flowed Text Vocabulary</td><td>N</td><td></td></tr><tr><td>R215</td><td>Hybrid Flowed and Non-Flowed Text</td><td>N</td><td></td></tr><tr><td>R216</td><td>Hyperlinking</td><td>N</td><td>Can support via XLink</td></tr><tr><td>R217</td><td>Embedded Graphics</td><td>N</td><td></td></tr><tr><td>R218</td><td>Non-Embedded Graphics</td><td>N</td><td></td></tr><tr><td>R219</td><td>Embedded Fonts</td><td>N</td><td></td></tr><tr><td>R220</td><td>Non-Embedded Fonts</td><td>N</td><td></td></tr><tr><td>R221</td><td>Descriptive Vocabulary</td><td>S</td><td>See <code>ttm:agent</code>, <code>ttm:role</code></td></tr><tr><td>R222</td><td>Embedded Audio</td><td>N</td><td></td></tr><tr><td>R223</td><td>Non-Embedded Audio</td><td>N</td><td></td></tr><tr><td>R290</td><td>Markup Format</td><td>S</td><td></td></tr><tr><td>R291</td><td>Markup Format and Unicode Interaction</td><td>S</td><td></td></tr><tr><td>R292</td><td>Extrinsic Resource References</td><td>N</td><td>No extrinsic references</td></tr><tr><td>R293</td><td>Schema Validity Specification</td><td>S</td><td></td></tr><tr><td>R300</td><td>Inline Styling</td><td>S</td><td></td></tr><tr><td>R301</td><td>Inline Styling Form</td><td>P</td><td>Inline and referential styling</td></tr><tr><td>R301</td><td>Out-of-Line Styling</td><td>N</td><td></td></tr><tr><td>R301</td><td>Out-of-Line Styling Form</td><td>N</td><td></td></tr><tr><td>R304</td><td>Styling Prioritization</td><td>S</td><td></td></tr><tr><td>R305</td><td>Style Parameters – Aural</td><td>N</td><td></td></tr><tr><td>R306</td><td>Style Parameters – Visual</td><td>P</td><td>Supports absolute position, background color, color, display none, display alignment,
 font family, font size, font style, font weight, height, line height, origin,
 opacity, overflow, padding (before, after, start, end), text alignment,
 text shadow (as outline), visibility, width, writing mode, z-index</td></tr><tr><td>R390</td><td>Style Parameter Symmetry</td><td>S</td><td></td></tr><tr><td>R391</td><td>Style Parameter Definitions</td><td>S</td><td></td></tr><tr><td>R392</td><td>Style Parameter Shorthands</td><td>S</td><td></td></tr><tr><td>R401</td><td>Inline Timing</td><td>S</td><td></td></tr><tr><td>R402</td><td>Out-of-Line Timing</td><td>N</td><td></td></tr><tr><td>R403</td><td>Synchronization Parameters</td><td>P</td><td>Supports begin, end, dur</td></tr><tr><td>R404</td><td>Synchronization Parameter Value Spaces</td><td>P</td><td>Supports offset values, media marker values (SMPTE 12M), wall-clock values</td></tr><tr><td>R405</td><td>Time Containment Semantics</td><td>P</td><td>Supports sequential, parallel</td></tr><tr><td>R500</td><td>Animation Modes</td><td>P</td><td>Supports discrete</td></tr><tr><td>R502</td><td>Highlight Animation</td><td>S</td><td><code>&lt;set tts:backgroundColor="..."/&gt;</code></td></tr><tr><td>R503</td><td>Fade Transition Animation</td><td>S</td><td><code>&lt;set tts:opacity="..."/&gt;</code></td></tr><tr><td>R504</td><td>Animated Style Parameters – Aural</td><td>N</td><td></td></tr><tr><td>R505</td><td>Animated Style Parameters – Visual</td><td>P</td><td>Supports animating background color, color, display, opacity, origin, visibility</td></tr><tr><td>N506</td><td>Animated Content</td><td>S</td><td></td></tr><tr><td>R600</td><td>Metadata Item Association</td><td>S</td><td>See <code>metadata</code>, <code>Metadata.class</code></td></tr><tr><td>R601</td><td>Metadata Item Constituents</td><td>P</td><td>Supports name, value</td></tr><tr><td>R602</td><td>Metadata Item Value Representation</td><td>P</td><td>See <code>metadata</code></td></tr><tr><td>R603</td><td>Metadata Item Extensibility</td><td>S</td><td>See <code>metadata</code></td></tr><tr><td>R604</td><td>Metadata Item Validation</td><td>S</td><td>See <code>metadata</code></td></tr><tr><td>R690</td><td>Dublin Core Preference</td><td>N</td><td>Uses <code>ttm:copyright</code>, <code>ttm:desc</code>, <code>ttm:title</code></td></tr></tbody></table></div><div class="div1">
-<h2><a name="derivation" id="derivation"></a>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
+<h2><a id="derivation"></a>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
 vocabulary, separately describing derivation of elements and
 attributes.</p><div class="div2">
-<h3><a name="d3e17572" id="d3e17572"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
+<h3><a id="d3e18212"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
 specifies a TTML element vocabulary item; the second column specifies the
 syntactic and/or semantic model on which the vocabulary item is based;
 the third column specifies the reference that defines
@@ -6394,7 +6434,7 @@
 corresponding TTML element; in contrast, the details column includes
 "+@begin", which denotes that a <code>begin</code> attribute is added
 that is not specified for use with the <code>xhtml:div</code> model
-element.</p><a name="element-vocab-derivation-table" id="element-vocab-derivation-table"></a><table class="common"><caption>Table J-1 – Elements</caption><col width="20%" span="1"><col width="17%" span="1"><col width="13%" align="center" span="1"><col width="40%" span="1"><col width="10%" align="center" span="1"><tbody><tr><td><span class="strong">Element</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#document-structure-vocabulary-body"><code>tt:body</code></a></td><td><code>xhtml:body</code></td><td><a href="#xhtml10">[XHTML 1.0]</a></td><td>-@class, -@dir, -@lang, -@on*, -@title; +@begin, +@dur, +@end, +@region,
+element.</p><a id="element-vocab-derivation-table"></a><table class="common"><caption>Table J-1 – Elements</caption><col width="20%" span="1"><col width="17%" span="1"><col width="13%" align="center" span="1"><col width="40%" span="1"><col width="10%" align="center" span="1"><tbody><tr><td><span class="strong">Element</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#document-structure-vocabulary-body"><code>tt:body</code></a></td><td><code>xhtml:body</code></td><td><a href="#xhtml10">[XHTML 1.0]</a></td><td>-@class, -@dir, -@lang, -@on*, -@title; +@begin, +@dur, +@end, +@region,
 +@timeContainer, +@ttm:*, +@tts:*; content model
 subsetted to zero or more division (div) children, and supersetted by
 optional metadata and animation children</td><td>1,2</td></tr><tr><td><a href="#content-vocabulary-br"><code>tt:br</code></a></td><td><code>xhtml:br</code></td><td><a href="#xhtml10">[XHTML 1.0]</a></td><td>-@class, -@title; +@ttm:*, +@tts:*, +@xml:lang, +@xml:space;
@@ -6433,7 +6473,7 @@
 and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
 but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
 and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e18051" id="d3e18051"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
+<h3><a id="d3e18691"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
 specifies a TTML attribute vocabulary item; the second column specifies the
 syntactic and/or semantic model on which the vocabulary item is based;
 the third column specifies the reference that defines
@@ -6454,7 +6494,7 @@
 that are uniquely defined for a specific TTML element type are not
 listed below, but are considered to be part of the specific element
 type's derivation described in <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
-above.</p><a name="attribute-vocab-derivation-table" id="attribute-vocab-derivation-table"></a><table class="common"><caption>Table J-2 – Attributes</caption><col width="20%" span="1"><col width="17%" span="1"><col width="13%" align="center" span="1"><col width="40%" span="1"><col width="10%" align="center" span="1"><tbody><tr><td><span class="strong">Attribute</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#timing-attribute-begin"><code>begin</code></a></td><td><code>begin</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-dur"><code>dur</code></a></td><td><code>dur</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-end"><code>end</code></a></td><td><code>end</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#layout-attribute-region"><code>region</code></a></td><td><code>master-reference</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>conceptual derivation</td><td></td></tr><tr><td><a href="#style-attribute-style"><code>style</code></a></td><td><code>class</code></td><td><a href="#css2">[CSS2]</a></td><td>dereferences style specification(s) directly</td><td></td></tr><tr><td><a href="#timing-attribute-timeContainer"><code>timeContainer</code></a></td><td><code>timeContainer</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>-excl, -none; no default attribute value</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td></td><td>used to attribute agent of content</td><td></td></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td></td><td>used to attribute role of content</td><td></td></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td></td><td>expresses uniform grid resolution for cell based coordinates</td><td></td></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td></td><td>determines how to interpret time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td></td><td>expresses integral frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td></td><td>used to express non-integral, rational frame rates</td><td></td></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td></td><td>expresses marker continuity semantics</td><td></td></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td></td><td>expresses pixel aspect ratio of related media</td><td></td></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td></td><td>expresses profile of TTML used by document instance</td><td></td></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td></td><td>expresses frame counting (drop) modes</td><td></td></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td></td><td>expresses sub-frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td></td><td>used to interpret tick based time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td></td><td>used to interpret semantics of time expressions</td><td></td></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only <code>auto</code>, <code>none</code></td><td></td></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-bolder</code>, <code>-lighter</code>, <code>-&lt;number&gt;</code></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-&lt;number&gt;</code>, <code>-&lt;space&gt;</code></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-auto</code>, <code>-error-if-overflow</code>;</td><td>8</td></tr><tr><td><a href="#style-attribute-padding"><code>tts:padding</code></a></td><td><code>padding</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>9</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,10,13</td></tr><tr><td><a href="#style-attribute-textOutline"><code>tts:textOutline</code></a></td><td><code>text-shadow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>11,13</td></tr><tr><td><a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a></td><td><code>unicode-bidi</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-visibility"><code>tts:visibility</code></a></td><td><code>visibility</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-collapse</code></td><td></td></tr><tr><td><a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a></td><td><code>wrap-option</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-writingMode"><code>tts:writingMode</code></a></td><td><code>writing-mode</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>+tblr</code></td><td>1</td></tr><tr><td><a href="#style-attribute-zIndex"><code>tts:zIndex</code></a></td><td><code>z-index</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#content-attribute-id"><code>xml:id</code></a></td><td><code>xml:id</code></td><td><a href="#xmlid">[XML ID]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-lang"><code>xml:lang</code></a></td><td><code>xml:lang</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-space"><code>xml:space</code></a></td><td><code>xml:space</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>see notes</td><td>12</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Attribute name and/or value(s) are normalized to use
+above.</p><a id="attribute-vocab-derivation-table"></a><table class="common"><caption>Table J-2 – Attributes</caption><col width="20%" span="1"><col width="17%" span="1"><col width="13%" align="center" span="1"><col width="40%" span="1"><col width="10%" align="center" span="1"><tbody><tr><td><span class="strong">Attribute</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#timing-attribute-begin"><code>begin</code></a></td><td><code>begin</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-dur"><code>dur</code></a></td><td><code>dur</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-end"><code>end</code></a></td><td><code>end</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#layout-attribute-region"><code>region</code></a></td><td><code>master-reference</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>conceptual derivation</td><td></td></tr><tr><td><a href="#style-attribute-style"><code>style</code></a></td><td><code>class</code></td><td><a href="#css2">[CSS2]</a></td><td>dereferences style specification(s) directly</td><td></td></tr><tr><td><a href="#timing-attribute-timeContainer"><code>timeContainer</code></a></td><td><code>timeContainer</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>-excl, -none; no default attribute value</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td></td><td>used to attribute agent of content</td><td></td></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td></td><td>used to attribute role of content</td><td></td></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td></td><td>expresses uniform grid resolution for cell based coordinates</td><td></td></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td></td><td>determines how to interpret time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td></td><td>expresses integral frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td></td><td>used to express non-integral, rational frame rates</td><td></td></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td></td><td>expresses marker continuity semantics</td><td></td></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td></td><td>expresses pixel aspect ratio of related media</td><td></td></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td></td><td>expresses profile of TTML used by <em>Document Instance</em></td><td></td></tr><tr><td><a href="#parameter-attribute-dropMode"><code>ttp:dropMode</code></a></td><td><em>none</em></td><td></td><td>expresses frame counting (drop) modes</td><td></td></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td></td><td>expresses sub-frame rate</td><td></td></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td></td><td>used to interpret tick based time expressions</td><td></td></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td></td><td>used to interpret semantics of time expressions</td><td></td></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only <code>auto</code>, <code>none</code></td><td></td></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-bolder</code>, <code>-lighter</code>, <code>-&lt;number&gt;</code></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-&lt;number&gt;</code>, <code>-&lt;space&gt;</code></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td></td></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-auto</code>, <code>-error-if-overflow</code>;</td><td>8</td></tr><tr><td><a href="#style-attribute-padding"><code>tts:padding</code></a></td><td><code>padding</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>9</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td><code>-inherit</code></td><td></td></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1,10,13</td></tr><tr><td><a href="#style-attribute-textOutline"><code>tts:textOutline</code></a></td><td><code>text-shadow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>11,13</td></tr><tr><td><a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a></td><td><code>unicode-bidi</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-visibility"><code>tts:visibility</code></a></td><td><code>visibility</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>-collapse</code></td><td></td></tr><tr><td><a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a></td><td><code>wrap-option</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#style-attribute-writingMode"><code>tts:writingMode</code></a></td><td><code>writing-mode</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code>, <code>+tblr</code></td><td>1</td></tr><tr><td><a href="#style-attribute-zIndex"><code>tts:zIndex</code></a></td><td><code>z-index</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><code>-inherit</code></td><td>1</td></tr><tr><td><a href="#content-attribute-id"><code>xml:id</code></a></td><td><code>xml:id</code></td><td><a href="#xmlid">[XML ID]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-lang"><code>xml:lang</code></a></td><td><code>xml:lang</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>complies with model</td><td></td></tr><tr><td><a href="#content-attribute-space"><code>xml:space</code></a></td><td><code>xml:space</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>see notes</td><td>12</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Attribute name and/or value(s) are normalized to use
 <em>lowerCamelCase</em> naming convention.</p></li><li><p>Restricted to expressing a clock value that denotes one of the
 following in accordance to whether the parameter expressed by the
 <code>ttp:timeBase</code> attribute is <code>media</code>, <code>smpte</code>,
@@ -6502,28 +6542,28 @@
 <code>default</code>, which is defined in terms of whitespace
 normalization. Semantics of preservation and default normalization are
 defined in terms of presentation semantics by <a href="#content-attribute-space"><b>7.2.3 xml:space</b></a>.</p></li><li><p>Defined to be inheritable.</p></li></ol></div></div></div><div class="div1">
-<h2><a name="qa" id="qa"></a>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
+<h2><a id="qa"></a>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
 requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
 Framework Specifications Guidelines</a>&nbsp;<a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a name="d3e18919" id="d3e18919"></a>K.1 Requirements</h3><a name="qa-framework-requirements-table" id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a id="d3e19561"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
 clause</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e19083" id="d3e19083"></a>K.2 Guidelines</h3><a name="qa-framework-guidelines-table" id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e19725"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
 specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
 Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
-<a href="#doctypes">TTML Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
-<h2><a name="streaming" id="streaming"></a>L Streaming TTML Content (Non-Normative)</h2><p>TTML Content is designed to support streamability by implementing the
+TTML <a href="#doctypes">Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
+<h2><a id="streaming"></a>L Streaming TTML Content (Non-Normative)</h2><p>TTML Content is designed to support streamability by implementing the
 following properties:</p><ul><li><p>can be progressively encoded (i.e., does not require computing
 subsequent data prior to sending current data);</p></li><li><p>can be progressively decoded (i.e., does not require forward
 references, but uses only reverse references when necessary);</p></li><li><p>does not require dereferencing (and subsequent loading) of any
-resources other than TTML content (i.e., no embedded URIs);</p></li><li><p>does not support alternative content forms (e.g., different
+resources other than TTML Content (i.e., no embedded URIs);</p></li><li><p>does not support alternative content forms (e.g., different
 language, graphics formats, time bases) in a single document;</p></li><li><p>has timing structure compiled into inline format that makes
 possible a temporal ordering of content that follows temporal
 presentation order;</p></li><li><p>constrains content models to prevent arbitrary nested content
 structures;</p></li></ul><p>One possible means by which TTML Content may be streamed is to
-partition a TTML document instance's information set into
+partition a <em>Document Instance</em>'s information set into
 non-overlapping fragments, where one particular fragment, call it the
 <em>root fragment</em>, represents the front matter (head) of the
-document instance as well as its top level structural elements, and
+<em>Document Instance</em> as well as its top level structural elements, and
 other fragments represent content whose time intervals are expected to
 be active in parallel.</p><p>In applications that require arbitrary (random) entry into a
 stream, i.e., the property of being able to start reading data at an
@@ -6531,21 +6571,21 @@
 transmitted (inserted) into the stream in order to permit a decoder to
 resynchronize and acquire sufficient structural information in the
 information set in order to interpret subsequent content
-fragments.</p><p>An example of such a fragmentation of a TTML document instance is
-shown in <a href="#fragment-streaming-graphic"><b>Figure 3 – Fragment Streaming</b></a>.</p><a name="fragment-streaming-graphic" id="fragment-streaming-graphic"></a><table class="example-images"><caption>Figure 3 – Fragment Streaming</caption><col span="1"><tbody><tr><td><img src="images/streaming.png" alt="Fragment Streaming"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not define a transport buffer model or a decoder
+fragments.</p><p>An example of such a fragmentation of a <em>Document Instance</em> is
+shown in <a href="#fragment-streaming-graphic"><b>Figure 3 – Fragment Streaming</b></a>.</p><a id="fragment-streaming-graphic"></a><table class="example-images"><caption>Figure 3 – Fragment Streaming</caption><col span="1"><tbody><tr><td><img src="images/streaming.png" alt="Fragment Streaming"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not define a transport buffer model or a decoder
 capabilities model.</p></div></div><div class="div1">
-<h2><a name="concrete-encoding" id="concrete-encoding"></a>M Concrete Encoding (Non-Normative)</h2><p>In the absence of other requirements, it is recommended that a TTML document be concretely encoded as a
+<h2><a id="concrete-encoding"></a>M Concrete Encoding (Non-Normative)</h2><p>In the absence of other requirements, it is recommended that a <em>Document Instance</em> be concretely encoded as a
 well-formed XML 1.0 <a href="#xml10">[XML 1.0]</a> document using the UTF-8 character encoding.</p></div><div class="div1">
-<h2><a name="time-expression-semantics" id="time-expression-semantics"></a>N Time Expression Semantics (Non-Normative)</h2><p>This appendix describes the intended semantics for interpreting time expressions in TTML documents.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is expected that the information in this appendix will be elevated to normative status in a future revision of this specification.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>local real time</em> as used below is intended to model a virtual real time clock in the document processing context, where
+<h2><a id="time-expression-semantics"></a>N Time Expression Semantics (Non-Normative)</h2><p>This appendix describes the intended semantics for interpreting time expressions in <em>Document Instances</em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is expected that the information in this appendix will be elevated to normative status in a future revision of this specification.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>local real time</em> as used below is intended to model a virtual real time clock in the document processing context, where
 <em>local</em> means in the immediate proximity of the implementation of this processing context. The intent
 of defining relationships with this virtual clock is to establish a locally valid physical realization of time for didactic purposes.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The phrase <em>play rate</em> as used below is intended to model a (possibly variable) parameter in the document processing context wherein
 the rate of playback (or interpretation) of time may artificially dilated or narrowed, for example, when speeding up or slowing down the rate of
 playback of a <em>Related Media Object</em>. Without loss of generality, the following discussion assumes a fixed play(back) rate. In the case of
 variable play rates, appropriate adjustments may need to be made to the resulting computations.</p></div><div class="div2">
-<h3><a name="time-expression-semantics-clock" id="time-expression-semantics-clock"></a>N.1 Clock Time Base</h3><p>When operating with the <code>clock</code> time base, the following semantics should be applied for interpreting time expressions,
+<h3><a id="time-expression-semantics-clock"></a>N.1 Clock Time Base</h3><p>When operating with the <code>clock</code> time base, the following semantics should be applied for interpreting time expressions,
 as defined by <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>, and their relationship to media time and local real time.</p><p>The clock time base <span class="strong"><code>C</code></span> is related to local real time <span class="strong"><code>R</code></span>
 expressed in an arbitrary (implementation defined) epoch <span class="strong"><code>E</code></span>
-as follows:</p><a name="clock-time-and-real-time" id="clock-time-and-real-time"></a><table class="semantics"><caption>TTML Semantics – Clock Time and Real Time Relationship</caption><tbody><tr><td>
+as follows:</p><a id="clock-time-and-real-time"></a><table class="semantics"><caption>TTML Semantics – Clock Time and Real Time Relationship</caption><tbody><tr><td>
 <blockquote><p>
 <code>R = C + epochOffset + discontinuityOffset</code>
 <br><br>
@@ -6572,7 +6612,7 @@
 during the period between value determination and the beginning of the <em>Root Temporal Extent</em> there occurs no local midnight or reference clock base discontinuity.
 <br></p></blockquote>
 </td></tr></tbody></table><p>Time value expressions, as denoted by a <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>, are related to
-clock time <span class="strong"><code>C</code></span> as follows:</p><a name="time-expressions-and-clock-time" id="time-expressions-and-clock-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and Clock Time Relationship</caption><tbody><tr><td>
+clock time <span class="strong"><code>C</code></span> as follows:</p><a id="time-expressions-and-clock-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and Clock Time Relationship</caption><tbody><tr><td>
 <blockquote><p>
 If a time expression uses the <em>clock-time</em> form or an <em>offset-time</em> form that doesn't use the ticks (<code>t</code>) metric, then:
 <br><br>
@@ -6588,7 +6628,7 @@
 <code>C = ticks / tickRate</code>
 <br></p></blockquote>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The <em>frames</em> and <em>sub-frames</em> terms and the frames (<code>f</code>) metric of time expressions do not apply when using
-the <code>clock</code> time base.</p></div><p>The clock time base <span class="strong"><code>C</code></span> is independent of media time <span class="strong"><code>M</code></span>:</p><a name="clock-time-and-media-time" id="clock-time-and-media-time"></a><table class="semantics"><caption>TTML Semantics – Clock Time and Media Time Relationship</caption><tbody><tr><td>
+the <code>clock</code> time base.</p></div><p>The clock time base <span class="strong"><code>C</code></span> is independent of media time <span class="strong"><code>M</code></span>:</p><a id="clock-time-and-media-time"></a><table class="semantics"><caption>TTML Semantics – Clock Time and Media Time Relationship</caption><tbody><tr><td>
 <blockquote><p>
 <code>M ¬∝ C</code>
 <br></p></blockquote>
@@ -6597,9 +6637,9 @@
 will continue to advance according to the natural progression of clock time in direct proportion to the reference clock base. Furthermore, if the media play rate changes
 during playback, presentation timing is not affected.
 </p></div></div><div class="div2">
-<h3><a name="time-expression-semantics-media" id="time-expression-semantics-media"></a>N.2 Media Time Base</h3><p>When operating with the <code>media</code> time base, the following semantics should be applied for interpreting time expressions,
+<h3><a id="time-expression-semantics-media"></a>N.2 Media Time Base</h3><p>When operating with the <code>media</code> time base, the following semantics should be applied for interpreting time expressions,
 as defined by <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>, and their relationship to media time and local real time.</p><p>The media time base <span class="strong"><code>M</code></span> is related to local real time <span class="strong"><code>R</code></span>
-expressed in an arbitrary (implementation defined) epoch <span class="strong"><code>E</code></span> as follows:</p><a name="media-time-and-real-time" id="media-time-and-real-time"></a><table class="semantics"><caption>TTML Semantics – Media Time and Real Time Relationship</caption><tbody><tr><td>
+expressed in an arbitrary (implementation defined) epoch <span class="strong"><code>E</code></span> as follows:</p><a id="media-time-and-real-time"></a><table class="semantics"><caption>TTML Semantics – Media Time and Real Time Relationship</caption><tbody><tr><td>
 <blockquote><p>
 <code>R = playRate * M + epochOffset</code>
 <br><br>
@@ -6614,7 +6654,7 @@
 </p></blockquote>
 </td></tr></tbody></table><p>Time value expressions, as denoted by a <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>, are related to
 media time <span class="strong"><code>M</code></span> in accordance to the
-<code>ttp:frameRate</code>, <code>ttp:subFrameRate</code>, and <code>ttp:frameRateMultipler</code> parameters as follows:</p><a name="time-expressions-and-media-time" id="time-expressions-and-media-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and Media Time Relationship</caption><tbody><tr><td>
+<code>ttp:frameRate</code>, <code>ttp:subFrameRate</code>, and <code>ttp:frameRateMultipler</code> parameters as follows:</p><a id="time-expressions-and-media-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and Media Time Relationship</caption><tbody><tr><td>
 <blockquote><p>
 If a time expression uses a <em>clock-time</em> form or an <em>offset-time</em> form that doesn't use the ticks (<code>t</code>) metric, then:
 <br><br>
@@ -6648,13 +6688,13 @@
 <br></p></blockquote>
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If the computed <code>frameRateMultipler</code> ratio is not integral, then <code>effectiveFrameRate</code> will be a non-integral rational.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The above formalisms assumes that the <em>Root Temporal Extent</em> corresponds with the beginning of a related media object. If
 this assumption doesn't hold, then an additional offset that accounts for the difference may be introduced when computing media time <code>M</code>.</p></div></div><div class="div2">
-<h3><a name="time-expression-semantics-smpte" id="time-expression-semantics-smpte"></a>N.3 SMPTE Time Base</h3><p>When operating with the <code>smpte</code> time base, the following semantics should be applied for interpreting time expressions,
+<h3><a id="time-expression-semantics-smpte"></a>N.3 SMPTE Time Base</h3><p>When operating with the <code>smpte</code> time base, the following semantics should be applied for interpreting time expressions,
 as defined by <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>, and their relationship to media time and local real time.</p><p>If the computed value of the <code>ttp:markerMode</code> parameter is <code>discontinuous</code>, then there is no direct relationship between
 time expressions and media time <span class="strong"><code>M</code></span> or local real time <span class="strong"><code>R</code></span>. In
 this case, time expressions refer to synchronization events (markers) emitted by the <em>Document Processing Context</em> when <em>SMPTE Time
 Codes</em> are encountered in the <em>Related Media Object</em>.</p><p>Otherwise, if the computed value of the <code>ttp:markerMode</code> parameter is <code>continuous</code>, then the relationships between time expressions and
 local real time and media time are as described below in terms of a <em>Synthetic SMPTE Document Syncbase</em>, here referred to as the
-SMPTE time base <span class="strong"><code>S</code></span>.</p><a name="time-expressions-and-smpte-time" id="time-expressions-and-smpte-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and SMPTE Time Relationship</caption><tbody><tr><td>
+SMPTE time base <span class="strong"><code>S</code></span>.</p><a id="time-expressions-and-smpte-time"></a><table class="semantics"><caption>TTML Semantics – Time Expressions and SMPTE Time Relationship</caption><tbody><tr><td>
 <blockquote><p>
 <code>S = (countedFrames - droppedFrames + (subFrames / subFrameRate)) / effectiveFrameRate</code>
 <br><br>where<br><br>
@@ -6688,7 +6728,7 @@
 dropped according to <a href="#parameter-attribute-dropMode"><b>6.2.3 ttp:dropMode</b></a>, then that time expression
 should be considered to be invalid for purposes of validation assessment.
 <br></p></blockquote>
-</td></tr></tbody></table><p>The SMPTE time base <span class="strong"><code>S</code></span> is related to the media time base <span class="strong"><code>M</code></span> as follows:</p><a name="smpte-time-and-media-time" id="smpte-time-and-media-time"></a><table class="semantics"><caption>TTML Semantics – SMPTE Time and Media Time Relationship</caption><tbody><tr><td>
+</td></tr></tbody></table><p>The SMPTE time base <span class="strong"><code>S</code></span> is related to the media time base <span class="strong"><code>M</code></span> as follows:</p><a id="smpte-time-and-media-time"></a><table class="semantics"><caption>TTML Semantics – SMPTE Time and Media Time Relationship</caption><tbody><tr><td>
 <blockquote><p>
 <code>M = containerBegin + S</code>