Mercurial > hg > ttml / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset
[ttml10se, ttml11] regenerate EDs
authorGlenn Adams <glenn@skynav.com>
Tue, 16 Jul 2013 10:58:37 -0600
changeset 454 f0fc1a84cf31
parent 453 0355e9473d7e
child 455 ee40990f59b8
[ttml10se, ttml11] regenerate EDs
ttml10/spec/ttaf1-dfxp.html
ttml11/spec/ttml11.html 
--- a/ttml10/spec/ttaf1-dfxp.html	Tue Jul 16 10:56:19 2013 -0600
+++ b/ttml10/spec/ttaf1-dfxp.html	Tue Jul 16 10:58:37 2013 -0600
@@ -80,9 +80,9 @@
 .strong { font-weight: bold }
 .reqattr { font-weight: bold }
 .optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/07/12 11:53:41 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/07/16 16:56:19 $<div id="revisions"></div><div class="head">
 <h1><a id="title"></a>Timed Text Markup Language (TTML) 1.0 (Second Edition)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/07/12 11:53:41 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/07/16 16:56:19 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
 <a href="ttaf1-dfxp.html">ttaf1-dfxp.html</a>
 </dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
 <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
@@ -392,11 +392,11 @@
 H <a href="#other-references">Other References</a> (Non-Normative)<br>
 I <a href="#requirements">Requirements</a> (Non-Normative)<br>
 J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e18642">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e19121">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e18739">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e19221">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e20007">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e20171">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e20107">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e20271">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>
@@ -978,11 +978,11 @@
 TTML while providing a baseline vocabulary for future profiles. This vocabulary
 is divided into distinct categories, specified in detail
 in the following sections:</p><ul><li><p><a href="#parameters"><b>6 Parameters</b></a></p></li><li><p><a href="#content"><b>7 Content</b></a></p></li><li><p><a href="#styling"><b>8 Styling</b></a></p></li><li><p><a href="#layout"><b>9 Layout</b></a></p></li><li><p><a href="#timing"><b>10 Timing</b></a></p></li><li><p><a href="#animation"><b>11 Animation</b></a></p></li><li><p><a href="#metadata"><b>12 Metadata</b></a></p></li></ul><p>The core element vocabulary specified for use with a <em>Document Instance</em> is enumerated in
-<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>
+<a href="#element-vocab-table"><b>Table 3 – Element Vocabulary</b></a>.</p><a id="element-vocab-table"></a><table class="common"><caption>Table 3 – Element Vocabulary</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Module</th><th>Elements</th></tr><tr id="element-vocab-type-animation"><td>
 Animation
 </td><td>
 <a href="#animation-vocabulary-set">set</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-content"><td>
 Content
 </td><td>
 <a href="#document-structure-vocabulary-body">body</a>,
@@ -990,24 +990,24 @@
 <a href="#content-vocabulary-p">p</a>,
 <a href="#content-vocabulary-span">span</a>,
 <a href="#content-vocabulary-br">br</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-document"><td>
 Document
 </td><td>
 <a href="#document-structure-vocabulary-tt">tt</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-head"><td>
 Head
 </td><td>
 <a href="#document-structure-vocabulary-head">head</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-layout"><td>
 Layout
 </td><td>
 <a href="#layout-vocabulary-layout">layout</a>,
 <a href="#layout-vocabulary-region">region</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-metadata"><td>
 Metadata
 </td><td>
 <a href="#metadata-vocabulary-metadata">metadata</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-metadata-items"><td>
 Metadata Items
 </td><td>
 <a href="#metadata-vocabulary-actor">ttm:actor</a>,
@@ -1016,12 +1016,12 @@
 <a href="#metadata-vocabulary-desc">ttm:desc</a>,
 <a href="#metadata-vocabulary-name">ttm:name</a>,
 <a href="#metadata-vocabulary-title">ttm:title</a>
-</td></tr><tr><td>Parameter Items</td><td><a href="#parameter-vocabulary-profile">ttp:profile</a>,
+</td></tr><tr id="element-vocab-type-parameter-items"><td>Parameter Items</td><td><a href="#parameter-vocabulary-profile">ttp:profile</a>,
 <a href="#parameter-vocabulary-features">ttp:features</a>,
 <a href="#parameter-vocabulary-feature">ttp:feature</a>,
 <a href="#parameter-vocabulary-extensions">ttp:extensions</a>,
 <a href="#parameter-vocabulary-extension">ttp:extension</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-styling"><td>
 Styling
 </td><td>
 <a href="#styling-vocabulary-styling">styling</a>,
@@ -1833,8 +1833,8 @@
 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 id="elt-syntax-head"></a><table class="syntax"><caption>XML Representation – Element Information Item: head</caption><tbody><tr><td>
+<a href="#element-vocab-type-content">Content</a> elements.</p><p>A <code>layout</code> child element is used to specify layout constructs that
+are referenced by <a href="#element-vocab-type-content">Content</a> elements.</p><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
@@ -1888,7 +1888,7 @@
 <code>body</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>body</code> element
 in a <em>Document Instance</em> are available for style inheritance by
-descendant content elements such as <code>div</code>, <code>p</code>,
+descendant <a href="#element-vocab-type-content">Content</a> 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
@@ -1937,7 +1937,7 @@
 the <code>style</code> attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated
 with
 a <code>div</code> element in a <em>Document Instance</em>
-are available for style inheritance by descendant content elements such as
+are available for style inheritance by descendant <a href="#element-vocab-type-content">Content</a> elements such as
 <code>div</code>, 
 <code>p</code>,
 <code>span</code>, and
@@ -1977,7 +1977,7 @@
 <code>p</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>p</code> element
 in a <em>Document Instance</em> are available for style inheritance by
-descendant content elements such as <code>span</code> and
+descendant <a href="#element-vocab-type-content">Content</a> 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
 <em>parallel</em> time containment semantics.</p><p>If a sequence of children of a <code>p</code> element
@@ -2023,7 +2023,7 @@
 <code>span</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>span</code> element
 in a <em>Document Instance</em> are available for style inheritance by
-descendant content elements such as <code>span</code> and
+descendant <a href="#element-vocab-type-content">Content</a> 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">
@@ -2135,8 +2135,8 @@
 element must appear as a descendant of the <code>styling</code> element, and
 not in any other context.</p></div></div></div><div class="div2">
 <h3><a id="styling-attribute-vocabulary"></a>8.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>8.2.1 style</b></a> attribute used
-with both style definition elements as well as 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
+with both style definition elements as well as <a href="#element-vocab-type-content">Content</a> elements.</p><p>In addition, this section specifies the following attributes in the TT Style Namespace
+for use with style definition elements, certain layout elements, and <a href="#element-vocab-type-content">Content</a> elements
 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
@@ -2144,8 +2144,9 @@
 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
-properties.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A style property may be expressed as a specified attribute on any content
-element type independently of whether the property applies to that
+properties.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A style property may be expressed as a specified attribute on any
+<a href="#element-vocab-type-content">Content</a> element type
+independently of whether the property applies to that
 element type. This capability permits the expression of an inheritable
 style property on ancestor elements to which the property
 does not apply.</p></div><div class="div3">
@@ -2471,12 +2472,13 @@
 <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>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to parent element's font size, or if no parent element, then relative to the <em>Computed Cell Size</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a single <a href="#style-value-length">&lt;length&gt;</a> value is specified, then this length applies
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to parent element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a single <a href="#style-value-length">&lt;length&gt;</a> value is specified, then this length applies
 equally to horizontal and vertical scaling of a glyph's EM square; if two
 <a href="#style-value-length">&lt;length&gt;</a> values are specified, then the first expresses the horizontal
 scaling and the second expresses vertical scaling.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Use of independent horizontal and vertical font sizes is expected to be used
 with cell based units in order to denote fonts that are two rows in height and
-one column in width.</p></div><p>If horizontal and vertical sizes are expressed independently, then the
+one column in width.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A glyph's EM square is conventionally defined as the EM square of the font that contains the glyph. That is,
+glyphs do not have an EM square that is distinct from their font's EM square.</p></div><p>If horizontal and vertical sizes are expressed independently, then the
 units of the <a href="#style-value-length">&lt;length&gt;</a> values must be the same.</p><p>The <a href="#style-value-length">&lt;length&gt;</a> value(s) used to express font size must be non-negative.</p><p>For the purpose of determining applicability of this style property,
 each character child of a <code>p</code> element is considered to be enclosed in an anonymous
 span.</p><p>If a specified value of this attribute is not supported,
@@ -2484,15 +2486,7 @@
 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>.
 When a single &lt;length&gt; is expressed using cell units, then it refers to the height of
-the <em>Computed Cell Size</em>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>As specified above, the use of percentage units to express font size are interpreted as
-relative to <em>Computed Cell Size</em> when there is no parent element. For example, if cell resolution
-is 32 by 15, and the extent of the <em>Root Container Region</em> is 640 by 480, then the
-<em>Computed Cell Size</em> is [20px, 32px], i.e., 640px/32 (width) and 480px/15 (height). Consequently, if
-<code>tts:fontSize</code> were specified as 75% on the root <code>tt</code> element, then this would
-be equivalent to specifying 24px, i.e., 32px cell height * 75%.
-If two length expressions (independent horizontal and vertical font scaling) were specified, e.g.,
-"80% 75%", then this would be equivalent to specifying "16px 24px", i.e., 80% of 20px cell width is
-16px, and 75% of 32px cell height is 24px.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
+the <em>Computed Cell Size</em>.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="299px 97px"/&gt;
@@ -2608,7 +2602,8 @@
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute is <code>normal</code>, then the
 computed value of the style property must be considered to be the same
 as the largest font size that applies to any
-descendant element.</p><p>If specified as a <a href="#style-value-length">&lt;length&gt;</a>, then the length must
+descendant element in the intermediate synchronic document as determined by
+<a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a>.</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 id="style-attribute-lineHeight-example-1"></a><table class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
@@ -3551,7 +3546,7 @@
 reference to <code>style</code> element descendants of a <code>styling</code>
 element. It is considered an error to reference a <code>style</code>
 element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of referential styling encourages the reuse of style specifications while
-sacrificing locality of reference.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single content element may be associated with style properties by a hybrid mixture of
+sacrificing locality of reference.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#element-vocab-type-content">Content</a> 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 id="style-association-example-2"></a><table class="example"><caption>Example – Referential Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -3573,7 +3568,7 @@
 reference to <code>style</code> element descendants of a <code>styling</code>
 element. It is considered an error to reference a <code>style</code>
 element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of chained referential styling encourages the grouping of style specifications
-into general and specific sets, which further aids in style specification reuse.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single content element may be associated with style properties by a hybrid mixture of
+into general and specific sets, which further aids in style specification reuse.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#element-vocab-type-content">Content</a> 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 id="style-association-example-3"></a><table class="example"><caption>Example – Chained Referential Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -3607,11 +3602,12 @@
 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 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 <a href="#element-vocab-type-content">Content</a> elements
 within an intermediate synchronic document
-if a style property is not associated with a content element (or
+if a style property is not associated with a <a href="#element-vocab-type-content">Content</a> element (or
 an anonymous span) and the style property is designated as
-inheritable.</p><p>If a style property is determined to require inheritance, then the inherited value must
+inheritable.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code>tt</code> element is not a <a href="#element-vocab-type-content">Content</a> element;
+consequently, the <code>body</code> element is the outermost element from which content style inheritance occurs.</p></div><p>If a style property is determined to require inheritance, then the inherited value must
 be the value of the same named style property in the computed
 style set of the
 element's immediate ancestor element
@@ -3632,8 +3628,8 @@
 style
 set of the <code>span</code> element.</p></div></div><div class="div4">
 <h5><a id="semantics-style-inheritance-region"></a>8.4.2.2 Region Style Inheritance</h5><p>Style properties are inherited from a region element in the following case:</p><ol class="enumar"><li><p>if a style property <em>P</em> is not associated with
-a content
-element or an anonymous span <em>E</em> and the style
+a <a href="#element-vocab-type-content">Content</a> element
+or an anonymous span <em>E</em> and the style
 property is designated as inheritable, and</p></li><li><p>if that
 style property <em>P</em> is in the computed style
 set of region
@@ -3807,7 +3803,7 @@
 type <code>region</code>, then set <em>P′</em> to the initial value of
 property <em>P</em>, where the initial value of a property is
 determined according to the specific property definition found above
-in <a href="#styling-attribute-vocabulary"><b>8.2 Styling Attribute Vocabulary</b></a>;</p></li><li><p>if the element type of <em>E</em> is a content element
+in <a href="#styling-attribute-vocabulary"><b>8.2 Styling Attribute Vocabulary</b></a>;</p></li><li><p>if the element type of <em>E</em> is a <a href="#element-vocab-type-content">Content</a> element
 type or anonymous span, then set <em>P′</em> to the result of
 looking up the value of <em>P</em> in the computed style set of
 the immediate ancestor element of <em>E</em>, i.e.,
@@ -3834,7 +3830,7 @@
 relative value expressions remain relative; consequently, the
 resolution of relative value expressions (that may be assigned by
 means of referential style association) always takes place in the
-context of a layout or content element which has a presentation
+context of a layout or <a href="#element-vocab-type-content">Content</a> 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 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
@@ -3844,7 +3840,7 @@
 sub-steps:</p><ol class="enumar"><li><p><span class="strong">[filter]</span> if the element type
 of <em>E</em> is not the styling element type <code>style</code>, is
 not the layout element type <code>region</code>, and is not one of the
-content element types <code>body</code>, <code>div</code>, <code>p</code>,
+<a href="#element-vocab-type-content">Content</a> element types <code>body</code>, <code>div</code>, <code>p</code>,
 <code>span</code>, <code>br</code>, or anonymous span, then continue to the
 next element in the preorder traversal;</p></li><li><p> <span class="strong">[resolve computed styles]</span>
 determine (obtain) the computed style set <em>CSS</em> of
@@ -3945,9 +3941,9 @@
 by this attribute express the semantic roles of the region
 independently from the semantic roles of any content targeted to
 (associated with) the region.</p></div></div><div class="div2">
-<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with content elements.</p><div class="div3">
+<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with <a href="#element-vocab-type-content">Content</a> 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>If specified, the value of a <code>region</code> attribute must
+element which defines a space or area into which a <a href="#element-vocab-type-content">Content</a> element is intended to be flowed.</p><p>If specified, the value of a <code>region</code> attribute must
 adhere to the <code>IDREF</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
 § 3.3.9, and, furthermore, this IDREF must reference a <code>region</code> element
 which has a <code>layout</code> element as an ancestor.</p><p>The <code>region</code> attribute may be specified by an instance of the following
@@ -3963,7 +3959,7 @@
 <a href="#layout-vocabulary-region"><code>region</code></a> element,
 then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be anonymous;</p></li><li><p>the extent of the default region is the same as the extent of the <em>Root Container Region</em>;</p></li><li><p>the temporal interval of the default region is the same as the interval defined by the <em>Root Temporal Extent</em>;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element is
 specified, then the <a href="#layout-attribute-region"><code>region</code></a> attribute must
-not be specified on any content element in the <em>Document Instance</em>.</p><p>If a default region is implied for a given <em>Document Instance</em>, then
+not be specified on any <a href="#element-vocab-type-content">Content</a> element in the <em>Document Instance</em>.</p><p>If a default region is implied for a given <em>Document Instance</em>, then
 the <a href="#document-structure-vocabulary-body"><code>body</code></a> element
 is implicitly targeted to (associated with) the default region.</p><p>When implying a default region, the <em>Document Instance</em> is to be
 treated as if a <a href="#layout-vocabulary-region"><code>region</code></a> element and its
@@ -3997,7 +3993,7 @@
 sub-tree
  of <em>DOC<sub>source</sub></em>
 headed by the <code>body</code> element;</p></li><li><p>evaluating this sub-tree in a postorder traversal, prune elements if they
-are not a content element, if they are temporally inactive, if they are empty,
+are not a <a href="#element-vocab-type-content">Content</a> element, if they are temporally inactive, if they are empty,
 or if they aren't associated with region <em>R</em> according to the
 <span class="strong">[associate region]</span> procedure;</p></li><li><p>if the pruned sub-tree is non-empty, then reparent it to the <em>R</em>
 element;</p></li><li><p>finally, after completing the above steps, prune the original <code>body</code>
@@ -4008,7 +4004,7 @@
 which, in turn, implies that the descendants of the pruned element will no longer
 be descendants of the element's parent. When <em>prune</em> is used in
 reference to an attribute, it means that attribute is to be removed from its
-associated (owning) element node.</p></div></dd><dt class="label">[associate region]</dt><dd><p>A content element is associated with a region according
+associated (owning) element node.</p></div></dd><dt class="label">[associate region]</dt><dd><p>A <a href="#element-vocab-type-content">Content</a> element is associated with a region according
 to the following ordered rules, where the first rule satisfied
 is used and remaining rules are skipped:</p><ol class="enumar"><li><p>if the element specifies a <a href="#layout-attribute-region"><code>region</code></a> attribute,
 then the element is associated with the region referenced by that
@@ -4040,7 +4036,7 @@
 TTML. An actual implementation of this algorithm is not required to create or process
 XSL-FO representations. In particular, it is possible to implement these semantics
 using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a> is mapped 
-to an XSL FO document instance, <em>F</em>, as follows:</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a content element,
+to an XSL FO document instance, <em>F</em>, as follows:</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a <a href="#element-vocab-type-content">Content</a> element,
 synthesize an anonymous span to enclose the text node, substituting
 the new anonymous span for the original text node child in its sibling
 and parent hierarchy;</p></li><li><p>for each contiguous sequence of anonymous spans, replace the
@@ -4064,7 +4060,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 <a href="#element-vocab-type-content">Content</a> 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>,
@@ -4091,7 +4087,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 <a href="#element-vocab-type-content">Content</a> 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
@@ -4099,7 +4095,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 <a href="#element-vocab-type-content">Content</a> 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 
@@ -4547,8 +4543,8 @@
 styling of content.</p><div class="div2">
 <h3><a id="animation-element-vocabulary"></a>11.1 Animation Element Vocabulary</h3><p>The following elements specify the structure and principal animation aspects of a
 <em>Document Instance</em>:</p><ul><li><p><a href="#animation-vocabulary-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
+<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
+<a href="#element-vocab-type-content">Content</a> 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 id="elt-syntax-set"></a><table class="syntax"><caption>XML Representation – Element Information Item: set</caption><tbody><tr><td>
@@ -4646,7 +4642,7 @@
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The meaning of a specific metadata item must be evaluated in the
 context where it appears. The core vocabulary catalog permits an
 arbitrary number of <code>metadata</code> element children on any
-content element type except for the <code>tt</code> element. See specific element
+<a href="#element-vocab-type-content">Content</a> element type. See specific element
 vocabulary definitions for any constraints that apply to such
 usage.</p></div><p>The use of document metadata is illustrated by the following example.</p><a id="metadata-vocabulary-metadata-example-1"></a><table class="example"><caption>Example Fragment – Document Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -4760,7 +4756,7 @@
 specifies the agent that plays the role of the actor.</p><p>A <code>ttm:agent</code> metadata item is considered to be significant only
 when specified as a child of the <code>head</code> element or as a child of a
 <code>metadata</code> element child of the <code>head</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>ttm:agent</code> element instance is typically referenced using a <code>ttm:agent</code>
-attribute on a 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
+attribute on a <a href="#element-vocab-type-content">Content</a> element type.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If a character agent is played by multiple actors, then multiple character
 agents may be specified (and referenced) wherein different definitions of the
 character specify different actors.</p></div><p>The use of agent metadata is illustrated by the following example.</p><a id="metadata-vocabulary-agent-example-1"></a><table class="example"><caption>Example Fragment – Agent Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -4831,10 +4827,11 @@
 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 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">
+for use with the <code>metadata</code> element and with certain
+<a href="#element-vocab-type-content">Content</a> element types:</p><ul><li><p><a href="#metadata-attribute-agent"><b>12.2.1 ttm:agent</b></a></p></li><li><p><a href="#metadata-attribute-role"><b>12.2.2 ttm:role</b></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Only certain metadata item attributes may be used with <a href="#element-vocab-type-content">Content</a> elements. See
+the definitions of <a href="#element-vocab-type-content">Content</a> elements to determine permissible usage.</p></div><div class="div3">
 <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
+value, and is used with certain <a href="#element-vocab-type-content">Content</a> 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 <em>significant</em>
 <code>ttm:agent</code> element instances that appear
@@ -4844,7 +4841,7 @@
 <h4><a id="metadata-attribute-role"></a>12.2.2 ttm:role</h4><p>The <code>ttm:role</code> attribute may be used by a content author
 to express
 the roles, functions, or characteristics
-of some content element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
+of some <a href="#element-vocab-type-content">Content</a> element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
 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;§
@@ -6487,7 +6484,7 @@
 <h2><a id="derivation"></a>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
 vocabulary, separately describing derivation of elements and
 attributes.</p><div class="div2">
-<h3><a id="d3e18642"></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="d3e18739"></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
@@ -6537,12 +6534,12 @@
 <code>svg:set</code> are replaced by the
 direct expression of the target attribute name and value by use of a
 <code>tts:*</code> attribute.</p></li><li><p>CSS style specification syntax is mapped to XML by use of
-attributes defined in the TT Style Namespace.</p></li><li><p>The <code>xml:id</code> attribute is defined for use on all element types.</p></li><li><p>The <code>style</code> attribute is supported only on content
-elements.</p></li><li><p>Derived from the use of <code>@requiredExtensions</code>
+attributes defined in the TT Style Namespace.</p></li><li><p>The <code>xml:id</code> attribute is defined for use on all element types.</p></li><li><p>The <code>style</code> attribute is supported only on
+<a href="#element-vocab-type-content">Content</a> elements.</p></li><li><p>Derived from the use of <code>@requiredExtensions</code>
 and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
 but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
 and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e19121"></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="d3e19221"></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
@@ -6614,9 +6611,9 @@
 <h2><a id="qa"></a>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
 requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
 Framework Specifications Guidelines</a>&nbsp;<a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e20007"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a id="d3e20107"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
 clause</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e20171"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e20271"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
 specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
 Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
 TTML <a href="#doctypes">Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
--- a/ttml11/spec/ttml11.html	Tue Jul 16 10:56:19 2013 -0600
+++ b/ttml11/spec/ttml11.html	Tue Jul 16 10:58:37 2013 -0600
@@ -80,9 +80,9 @@
 .strong { font-weight: bold }
 .reqattr { font-weight: bold }
 .optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/07/12 11:53:41 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/07/16 16:56:19 $<div id="revisions"></div><div class="head">
 <h1><a id="title"></a>Timed Text Markup Language (TTML) 1.1</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/07/12 11:53:41 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/07/16 16:56:19 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
 <a href="ttml11.html">ttml11.html</a>
 </dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml11/spec/ttml11.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml11/spec/ttml11.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
 <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
@@ -392,11 +392,11 @@
 H <a href="#other-references">Other References</a> (Non-Normative)<br>
 I <a href="#requirements">Requirements</a> (Non-Normative)<br>
 J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e18671">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e19150">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e18768">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e19250">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e20036">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e20200">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e20136">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e20300">Guidelines</a><br>
 L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
 M <a href="#concrete-encoding">Concrete Encoding</a><br>
 N <a href="#time-expression-semantics">Time Expression Semantics</a><br>
@@ -978,11 +978,11 @@
 TTML while providing a baseline vocabulary for future profiles. This vocabulary
 is divided into distinct categories, specified in detail
 in the following sections:</p><ul><li><p><a href="#parameters"><b>6 Parameters</b></a></p></li><li><p><a href="#content"><b>7 Content</b></a></p></li><li><p><a href="#styling"><b>8 Styling</b></a></p></li><li><p><a href="#layout"><b>9 Layout</b></a></p></li><li><p><a href="#timing"><b>10 Timing</b></a></p></li><li><p><a href="#animation"><b>11 Animation</b></a></p></li><li><p><a href="#metadata"><b>12 Metadata</b></a></p></li></ul><p>The core element vocabulary specified for use with a <em>Document Instance</em> is enumerated in
-<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>
+<a href="#element-vocab-table"><b>Table 3 – Element Vocabulary</b></a>.</p><a id="element-vocab-table"></a><table class="common"><caption>Table 3 – Element Vocabulary</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Module</th><th>Elements</th></tr><tr id="element-vocab-type-animation"><td>
 Animation
 </td><td>
 <a href="#animation-vocabulary-set">set</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-content"><td>
 Content
 </td><td>
 <a href="#document-structure-vocabulary-body">body</a>,
@@ -990,24 +990,24 @@
 <a href="#content-vocabulary-p">p</a>,
 <a href="#content-vocabulary-span">span</a>,
 <a href="#content-vocabulary-br">br</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-document"><td>
 Document
 </td><td>
 <a href="#document-structure-vocabulary-tt">tt</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-head"><td>
 Head
 </td><td>
 <a href="#document-structure-vocabulary-head">head</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-layout"><td>
 Layout
 </td><td>
 <a href="#layout-vocabulary-layout">layout</a>,
 <a href="#layout-vocabulary-region">region</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-metadata"><td>
 Metadata
 </td><td>
 <a href="#metadata-vocabulary-metadata">metadata</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-metadata-items"><td>
 Metadata Items
 </td><td>
 <a href="#metadata-vocabulary-actor">ttm:actor</a>,
@@ -1016,12 +1016,12 @@
 <a href="#metadata-vocabulary-desc">ttm:desc</a>,
 <a href="#metadata-vocabulary-name">ttm:name</a>,
 <a href="#metadata-vocabulary-title">ttm:title</a>
-</td></tr><tr><td>Parameter Items</td><td><a href="#parameter-vocabulary-profile">ttp:profile</a>,
+</td></tr><tr id="element-vocab-type-parameter-items"><td>Parameter Items</td><td><a href="#parameter-vocabulary-profile">ttp:profile</a>,
 <a href="#parameter-vocabulary-features">ttp:features</a>,
 <a href="#parameter-vocabulary-feature">ttp:feature</a>,
 <a href="#parameter-vocabulary-extensions">ttp:extensions</a>,
 <a href="#parameter-vocabulary-extension">ttp:extension</a>
-</td></tr><tr><td>
+</td></tr><tr id="element-vocab-type-styling"><td>
 Styling
 </td><td>
 <a href="#styling-vocabulary-styling">styling</a>,
@@ -1866,8 +1866,8 @@
 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 id="elt-syntax-head"></a><table class="syntax"><caption>XML Representation – Element Information Item: head</caption><tbody><tr><td>
+<a href="#element-vocab-type-content">Content</a> elements.</p><p>A <code>layout</code> child element is used to specify layout constructs that
+are referenced by <a href="#element-vocab-type-content">Content</a> elements.</p><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
@@ -1921,7 +1921,7 @@
 <code>body</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>body</code> element
 in a <em>Document Instance</em> are available for style inheritance by
-descendant content elements such as <code>div</code>, <code>p</code>,
+descendant <a href="#element-vocab-type-content">Content</a> 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
@@ -1970,7 +1970,7 @@
 the <code>style</code> attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated
 with
 a <code>div</code> element in a <em>Document Instance</em>
-are available for style inheritance by descendant content elements such as
+are available for style inheritance by descendant <a href="#element-vocab-type-content">Content</a> elements such as
 <code>div</code>, 
 <code>p</code>,
 <code>span</code>, and
@@ -2010,7 +2010,7 @@
 <code>p</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>p</code> element
 in a <em>Document Instance</em> are available for style inheritance by
-descendant content elements such as <code>span</code> and
+descendant <a href="#element-vocab-type-content">Content</a> 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
 <em>parallel</em> time containment semantics.</p><p>If a sequence of children of a <code>p</code> element
@@ -2056,7 +2056,7 @@
 <code>span</code> element by means of either the <code>style</code>
 attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated with a <code>span</code> element
 in a <em>Document Instance</em> are available for style inheritance by
-descendant content elements such as <code>span</code> and
+descendant <a href="#element-vocab-type-content">Content</a> 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">
@@ -2172,8 +2172,8 @@
 element must appear as a descendant of the <code>styling</code> element, and
 not in any other context.</p></div></div></div><div class="div2">
 <h3><a id="styling-attribute-vocabulary"></a>8.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>8.2.1 style</b></a> attribute used
-with both style definition elements as well as 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
+with both style definition elements as well as <a href="#element-vocab-type-content">Content</a> elements.</p><p>In addition, this section specifies the following attributes in the TT Style Namespace
+for use with style definition elements, certain layout elements, and <a href="#element-vocab-type-content">Content</a> elements
 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
@@ -2181,8 +2181,9 @@
 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
-properties.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A style property may be expressed as a specified attribute on any content
-element type independently of whether the property applies to that
+properties.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A style property may be expressed as a specified attribute on any
+<a href="#element-vocab-type-content">Content</a> element type
+independently of whether the property applies to that
 element type. This capability permits the expression of an inheritable
 style property on ancestor elements to which the property
 does not apply.</p></div><div class="div3">
@@ -2508,12 +2509,13 @@
 <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>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to parent element's font size, or if no parent element, then relative to the <em>Computed Cell Size</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a single <a href="#style-value-length">&lt;length&gt;</a> value is specified, then this length applies
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to parent element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If a single <a href="#style-value-length">&lt;length&gt;</a> value is specified, then this length applies
 equally to horizontal and vertical scaling of a glyph's EM square; if two
 <a href="#style-value-length">&lt;length&gt;</a> values are specified, then the first expresses the horizontal
 scaling and the second expresses vertical scaling.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Use of independent horizontal and vertical font sizes is expected to be used
 with cell based units in order to denote fonts that are two rows in height and
-one column in width.</p></div><p>If horizontal and vertical sizes are expressed independently, then the
+one column in width.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A glyph's EM square is conventionally defined as the EM square of the font that contains the glyph. That is,
+glyphs do not have an EM square that is distinct from their font's EM square.</p></div><p>If horizontal and vertical sizes are expressed independently, then the
 units of the <a href="#style-value-length">&lt;length&gt;</a> values must be the same.</p><p>The <a href="#style-value-length">&lt;length&gt;</a> value(s) used to express font size must be non-negative.</p><p>For the purpose of determining applicability of this style property,
 each character child of a <code>p</code> element is considered to be enclosed in an anonymous
 span.</p><p>If a specified value of this attribute is not supported,
@@ -2521,15 +2523,7 @@
 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>.
 When a single &lt;length&gt; is expressed using cell units, then it refers to the height of
-the <em>Computed Cell Size</em>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>As specified above, the use of percentage units to express font size are interpreted as
-relative to <em>Computed Cell Size</em> when there is no parent element. For example, if cell resolution
-is 32 by 15, and the extent of the <em>Root Container Region</em> is 640 by 480, then the
-<em>Computed Cell Size</em> is [20px, 32px], i.e., 640px/32 (width) and 480px/15 (height). Consequently, if
-<code>tts:fontSize</code> were specified as 75% on the root <code>tt</code> element, then this would
-be equivalent to specifying 24px, i.e., 32px cell height * 75%.
-If two length expressions (independent horizontal and vertical font scaling) were specified, e.g.,
-"80% 75%", then this would be equivalent to specifying "16px 24px", i.e., 80% of 20px cell width is
-16px, and 75% of 32px cell height is 24px.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
+the <em>Computed Cell Size</em>.</p></div><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><a id="style-attribute-fontSize-example-1"></a><table class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="299px 97px"/&gt;
@@ -2645,7 +2639,8 @@
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute is <code>normal</code>, then the
 computed value of the style property must be considered to be the same
 as the largest font size that applies to any
-descendant element.</p><p>If specified as a <a href="#style-value-length">&lt;length&gt;</a>, then the length must
+descendant element in the intermediate synchronic document as determined by
+<a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a>.</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 id="style-attribute-lineHeight-example-1"></a><table class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
@@ -3588,7 +3583,7 @@
 reference to <code>style</code> element descendants of a <code>styling</code>
 element. It is considered an error to reference a <code>style</code>
 element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of referential styling encourages the reuse of style specifications while
-sacrificing locality of reference.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single content element may be associated with style properties by a hybrid mixture of
+sacrificing locality of reference.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#element-vocab-type-content">Content</a> 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 id="style-association-example-2"></a><table class="example"><caption>Example – Referential Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -3610,7 +3605,7 @@
 reference to <code>style</code> element descendants of a <code>styling</code>
 element. It is considered an error to reference a <code>style</code>
 element that is a descendant of a <code>layout</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of chained referential styling encourages the grouping of style specifications
-into general and specific sets, which further aids in style specification reuse.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single content element may be associated with style properties by a hybrid mixture of
+into general and specific sets, which further aids in style specification reuse.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A single <a href="#element-vocab-type-content">Content</a> 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 id="style-association-example-3"></a><table class="example"><caption>Example – Chained Referential Styling</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -3644,11 +3639,12 @@
 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 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 <a href="#element-vocab-type-content">Content</a> elements
 within an intermediate synchronic document
-if a style property is not associated with a content element (or
+if a style property is not associated with a <a href="#element-vocab-type-content">Content</a> element (or
 an anonymous span) and the style property is designated as
-inheritable.</p><p>If a style property is determined to require inheritance, then the inherited value must
+inheritable.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code>tt</code> element is not a <a href="#element-vocab-type-content">Content</a> element;
+consequently, the <code>body</code> element is the outermost element from which content style inheritance occurs.</p></div><p>If a style property is determined to require inheritance, then the inherited value must
 be the value of the same named style property in the computed
 style set of the
 element's immediate ancestor element
@@ -3669,8 +3665,8 @@
 style
 set of the <code>span</code> element.</p></div></div><div class="div4">
 <h5><a id="semantics-style-inheritance-region"></a>8.4.2.2 Region Style Inheritance</h5><p>Style properties are inherited from a region element in the following case:</p><ol class="enumar"><li><p>if a style property <em>P</em> is not associated with
-a content
-element or an anonymous span <em>E</em> and the style
+a <a href="#element-vocab-type-content">Content</a> element
+or an anonymous span <em>E</em> and the style
 property is designated as inheritable, and</p></li><li><p>if that
 style property <em>P</em> is in the computed style
 set of region
@@ -3846,7 +3842,7 @@
 type <code>region</code>, then set <em>P′</em> to the initial value of
 property <em>P</em>, where the initial value of a property is
 determined according to the specific property definition found above
-in <a href="#styling-attribute-vocabulary"><b>8.2 Styling Attribute Vocabulary</b></a>;</p></li><li><p>if the element type of <em>E</em> is a content element
+in <a href="#styling-attribute-vocabulary"><b>8.2 Styling Attribute Vocabulary</b></a>;</p></li><li><p>if the element type of <em>E</em> is a <a href="#element-vocab-type-content">Content</a> element
 type or anonymous span, then set <em>P′</em> to the result of
 looking up the value of <em>P</em> in the computed style set of
 the immediate ancestor element of <em>E</em>, i.e.,
@@ -3873,7 +3869,7 @@
 relative value expressions remain relative; consequently, the
 resolution of relative value expressions (that may be assigned by
 means of referential style association) always takes place in the
-context of a layout or content element which has a presentation
+context of a layout or <a href="#element-vocab-type-content">Content</a> element which has a presentation
 context, and not in the non-presentation, declaration context
 of a <code>set</code> element or a referentiable <code>style</code> element.</p></div></div><div class="div4">
 <h5><a id="semantics-style-resolution-process-overall"></a>8.4.4.4 Style Resolution Process</h5><p>The top-level style resolution process is defined as follows: using
@@ -3884,7 +3880,7 @@
 of <em>E</em> is not the styling element type <code>style</code>, is
 not the layout element type <code>region</code>, is not the animation
 element type <code>set</code>, and is not one of the
-content element types <code>body</code>, <code>div</code>, <code>p</code>,
+<a href="#element-vocab-type-content">Content</a> element types <code>body</code>, <code>div</code>, <code>p</code>,
 <code>span</code>, <code>br</code>, or anonymous span, then continue to the
 next element in the preorder traversal;</p></li><li><p> <span class="strong">[resolve computed styles]</span>
 determine (obtain) the computed style set <em>CSS</em> of
@@ -3981,9 +3977,9 @@
 by this attribute express the semantic roles of the region
 independently from the semantic roles of any content targeted to
 (associated with) the region.</p></div></div><div class="div2">
-<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with content elements.</p><div class="div3">
+<h3><a id="layout-attribute-vocabulary"></a>9.2 Layout Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with <a href="#element-vocab-type-content">Content</a> 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>If specified, the value of a <code>region</code> attribute must
+element which defines a space or area into which a <a href="#element-vocab-type-content">Content</a> element is intended to be flowed.</p><p>If specified, the value of a <code>region</code> attribute must
 adhere to the <code>IDREF</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
 § 3.3.9, and, furthermore, this IDREF must reference a <code>region</code> element
 which has a <code>layout</code> element as an ancestor.</p><p>The <code>region</code> attribute may be specified by an instance of the following
@@ -3999,7 +3995,7 @@
 <a href="#layout-vocabulary-region"><code>region</code></a> element,
 then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be anonymous;</p></li><li><p>the extent of the default region is the same as the extent of the <em>Root Container Region</em>;</p></li><li><p>the temporal interval of the default region is the same as the interval defined by the <em>Root Temporal Extent</em>;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element is
 specified, then the <a href="#layout-attribute-region"><code>region</code></a> attribute must
-not be specified on any content element in the <em>Document Instance</em>.</p><p>If a default region is implied for a given <em>Document Instance</em>, then
+not be specified on any <a href="#element-vocab-type-content">Content</a> element in the <em>Document Instance</em>.</p><p>If a default region is implied for a given <em>Document Instance</em>, then
 the <a href="#document-structure-vocabulary-body"><code>body</code></a> element
 is implicitly targeted to (associated with) the default region.</p><p>When implying a default region, the <em>Document Instance</em> is to be
 treated as if a <a href="#layout-vocabulary-region"><code>region</code></a> element and its
@@ -4033,7 +4029,7 @@
 sub-tree
  of <em>DOC<sub>source</sub></em>
 headed by the <code>body</code> element;</p></li><li><p>evaluating this sub-tree in a postorder traversal, prune elements if they
-are not a content element, if they are temporally inactive, if they are empty,
+are not a <a href="#element-vocab-type-content">Content</a> element, if they are temporally inactive, if they are empty,
 or if they aren't associated with region <em>R</em> according to the
 <span class="strong">[associate region]</span> procedure;</p></li><li><p>if the pruned sub-tree is non-empty, then reparent it to the <em>R</em>
 element;</p></li><li><p>finally, after completing the above steps, prune the original <code>body</code>
@@ -4044,7 +4040,7 @@
 which, in turn, implies that the descendants of the pruned element will no longer
 be descendants of the element's parent. When <em>prune</em> is used in
 reference to an attribute, it means that attribute is to be removed from its
-associated (owning) element node.</p></div></dd><dt class="label">[associate region]</dt><dd><p>A content element is associated with a region according
+associated (owning) element node.</p></div></dd><dt class="label">[associate region]</dt><dd><p>A <a href="#element-vocab-type-content">Content</a> element is associated with a region according
 to the following ordered rules, where the first rule satisfied
 is used and remaining rules are skipped:</p><ol class="enumar"><li><p>if the element specifies a <a href="#layout-attribute-region"><code>region</code></a> attribute,
 then the element is associated with the region referenced by that
@@ -4076,7 +4072,7 @@
 TTML. An actual implementation of this algorithm is not required to create or process
 XSL-FO representations. In particular, it is possible to implement these semantics
 using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a> is mapped 
-to an XSL FO document instance, <em>F</em>, as follows:</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a content element,
+to an XSL FO document instance, <em>F</em>, as follows:</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a <a href="#element-vocab-type-content">Content</a> element,
 synthesize an anonymous span to enclose the text node, substituting
 the new anonymous span for the original text node child in its sibling
 and parent hierarchy;</p></li><li><p>for each contiguous sequence of anonymous spans, replace the
@@ -4100,7 +4096,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 <a href="#element-vocab-type-content">Content</a> 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>,
@@ -4127,7 +4123,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 <a href="#element-vocab-type-content">Content</a> 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
@@ -4135,7 +4131,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 <a href="#element-vocab-type-content">Content</a> 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 
@@ -4583,8 +4579,8 @@
 styling of content.</p><div class="div2">
 <h3><a id="animation-element-vocabulary"></a>11.1 Animation Element Vocabulary</h3><p>The following elements specify the structure and principal animation aspects of a
 <em>Document Instance</em>:</p><ul><li><p><a href="#animation-vocabulary-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
+<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
+<a href="#element-vocab-type-content">Content</a> 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 id="elt-syntax-set"></a><table class="syntax"><caption>XML Representation – Element Information Item: set</caption><tbody><tr><td>
@@ -4685,7 +4681,7 @@
 </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The meaning of a specific metadata item must be evaluated in the
 context where it appears. The core vocabulary catalog permits an
 arbitrary number of <code>metadata</code> element children on any
-content element type except for the <code>tt</code> element. See specific element
+<a href="#element-vocab-type-content">Content</a> element type. See specific element
 vocabulary definitions for any constraints that apply to such
 usage.</p></div><p>The use of document metadata is illustrated by the following example.</p><a id="metadata-vocabulary-metadata-example-1"></a><table class="example"><caption>Example Fragment – Document Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -4799,7 +4795,7 @@
 specifies the agent that plays the role of the actor.</p><p>A <code>ttm:agent</code> metadata item is considered to be significant only
 when specified as a child of the <code>head</code> element or as a child of a
 <code>metadata</code> element child of the <code>head</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>ttm:agent</code> element instance is typically referenced using a <code>ttm:agent</code>
-attribute on a 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
+attribute on a <a href="#element-vocab-type-content">Content</a> element type.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If a character agent is played by multiple actors, then multiple character
 agents may be specified (and referenced) wherein different definitions of the
 character specify different actors.</p></div><p>The use of agent metadata is illustrated by the following example.</p><a id="metadata-vocabulary-agent-example-1"></a><table class="example"><caption>Example Fragment – Agent Metadata</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -4870,10 +4866,11 @@
 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 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">
+for use with the <code>metadata</code> element and with certain
+<a href="#element-vocab-type-content">Content</a> element types:</p><ul><li><p><a href="#metadata-attribute-agent"><b>12.2.1 ttm:agent</b></a></p></li><li><p><a href="#metadata-attribute-role"><b>12.2.2 ttm:role</b></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Only certain metadata item attributes may be used with <a href="#element-vocab-type-content">Content</a> elements. See
+the definitions of <a href="#element-vocab-type-content">Content</a> elements to determine permissible usage.</p></div><div class="div3">
 <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
+value, and is used with certain <a href="#element-vocab-type-content">Content</a> 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 <em>significant</em>
 <code>ttm:agent</code> element instances that appear
@@ -4883,7 +4880,7 @@
 <h4><a id="metadata-attribute-role"></a>12.2.2 ttm:role</h4><p>The <code>ttm:role</code> attribute may be used by a content author
 to express
 the roles, functions, or characteristics
-of some content element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
+of some <a href="#element-vocab-type-content">Content</a> element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
 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;§
@@ -6491,7 +6488,7 @@
 <h2><a id="derivation"></a>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
 vocabulary, separately describing derivation of elements and
 attributes.</p><div class="div2">
-<h3><a id="d3e18671"></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="d3e18768"></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
@@ -6541,12 +6538,12 @@
 <code>svg:set</code> are replaced by the
 direct expression of the target attribute name and value by use of a
 <code>tts:*</code> attribute.</p></li><li><p>CSS style specification syntax is mapped to XML by use of
-attributes defined in the TT Style Namespace.</p></li><li><p>The <code>xml:id</code> attribute is defined for use on all element types.</p></li><li><p>The <code>style</code> attribute is supported only on content
-elements.</p></li><li><p>Derived from the use of <code>@requiredExtensions</code>
+attributes defined in the TT Style Namespace.</p></li><li><p>The <code>xml:id</code> attribute is defined for use on all element types.</p></li><li><p>The <code>style</code> attribute is supported only on
+<a href="#element-vocab-type-content">Content</a> elements.</p></li><li><p>Derived from the use of <code>@requiredExtensions</code>
 and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
 but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
 and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e19150"></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="d3e19250"></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
@@ -6618,9 +6615,9 @@
 <h2><a id="qa"></a>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
 requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
 Framework Specifications Guidelines</a>&nbsp;<a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e20036"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a id="d3e20136"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
 clause</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e20200"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e20300"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
 specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
 Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
 TTML <a href="#doctypes">Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
ttml

Hosted by W3C Systems Team, please report bugs to sysreq@w3.org