--- a/ttml2/spec/ttml2.html Sun Nov 30 20:10:45 2014 -0700
+++ b/ttml2/spec/ttml2.html Sun Nov 30 20:10:56 2014 -0700
@@ -83,9 +83,9 @@
.obsoleted { background-color: #f26d7d }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2014/12/01 02:22:18 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2014/12/01 03:10:45 $<div id="revisions"></div><div class="head">
<h1><a id="title"></a>Timed Text Markup Language 2 (TTML2)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/12/01 02:22:18 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/12/01 03:10:45 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ttml2.html">ttml2.html</a>
</dd><dt>Latest version:</dt><dd><a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8">https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
@@ -245,27 +245,28 @@
10.2.16 <a href="#style-attribute-fontVariantPosition">tts:fontVariantPosition</a><br>
10.2.17 <a href="#style-attribute-fontWeight">tts:fontWeight</a><br>
10.2.18 <a href="#style-attribute-height">tts:height</a><br>
- 10.2.19 <a href="#style-attribute-lineHeight">tts:lineHeight</a><br>
- 10.2.20 <a href="#style-attribute-opacity">tts:opacity</a><br>
- 10.2.21 <a href="#style-attribute-origin">tts:origin</a><br>
- 10.2.22 <a href="#style-attribute-overflow">tts:overflow</a><br>
- 10.2.23 <a href="#style-attribute-padding">tts:padding</a><br>
- 10.2.24 <a href="#style-attribute-position">tts:position</a><br>
- 10.2.25 <a href="#style-attribute-ruby">tts:ruby</a><br>
- 10.2.26 <a href="#style-attribute-rubyAlign">tts:rubyAlign</a><br>
- 10.2.27 <a href="#style-attribute-rubyOffset">tts:rubyOffset</a><br>
- 10.2.28 <a href="#style-attribute-rubyPosition">tts:rubyPosition</a><br>
- 10.2.29 <a href="#style-attribute-showBackground">tts:showBackground</a><br>
- 10.2.30 <a href="#style-attribute-textAlign">tts:textAlign</a><br>
- 10.2.31 <a href="#style-attribute-textDecoration">tts:textDecoration</a><br>
- 10.2.32 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
- 10.2.33 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
- 10.2.34 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
- 10.2.35 <a href="#style-attribute-visibility">tts:visibility</a><br>
- 10.2.36 <a href="#style-attribute-width">tts:width</a><br>
- 10.2.37 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
- 10.2.38 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
- 10.2.39 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
+ 10.2.19 <a href="#style-attribute-letterSpacing">tts:letterSpacing</a><br>
+ 10.2.20 <a href="#style-attribute-lineHeight">tts:lineHeight</a><br>
+ 10.2.21 <a href="#style-attribute-opacity">tts:opacity</a><br>
+ 10.2.22 <a href="#style-attribute-origin">tts:origin</a><br>
+ 10.2.23 <a href="#style-attribute-overflow">tts:overflow</a><br>
+ 10.2.24 <a href="#style-attribute-padding">tts:padding</a><br>
+ 10.2.25 <a href="#style-attribute-position">tts:position</a><br>
+ 10.2.26 <a href="#style-attribute-ruby">tts:ruby</a><br>
+ 10.2.27 <a href="#style-attribute-rubyAlign">tts:rubyAlign</a><br>
+ 10.2.28 <a href="#style-attribute-rubyOffset">tts:rubyOffset</a><br>
+ 10.2.29 <a href="#style-attribute-rubyPosition">tts:rubyPosition</a><br>
+ 10.2.30 <a href="#style-attribute-showBackground">tts:showBackground</a><br>
+ 10.2.31 <a href="#style-attribute-textAlign">tts:textAlign</a><br>
+ 10.2.32 <a href="#style-attribute-textDecoration">tts:textDecoration</a><br>
+ 10.2.33 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
+ 10.2.34 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
+ 10.2.35 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
+ 10.2.36 <a href="#style-attribute-visibility">tts:visibility</a><br>
+ 10.2.37 <a href="#style-attribute-width">tts:width</a><br>
+ 10.2.38 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
+ 10.2.39 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
+ 10.2.40 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
10.3 <a href="#styling-style-value-expressions">Styling Value Expressions</a><br>
10.3.1 <a href="#style-value-alpha"><alpha></a><br>
10.3.2 <a href="#style-value-borderColor"><borderColor></a><br>
@@ -504,11 +505,11 @@
H <a href="#other-references">Other References</a> (Non-Normative)<br>
I <a href="#requirements">Requirements</a> (Non-Normative)<br>
J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
- J.1 <a href="#d3e34860">Element Derivation</a><br>
- J.2 <a href="#d3e35377">Attribute Derivation</a><br>
+ J.1 <a href="#d3e35000">Element Derivation</a><br>
+ J.2 <a href="#d3e35517">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e36370">Requirements</a><br>
- K.2 <a href="#d3e36534">Guidelines</a><br>
+ K.1 <a href="#d3e36510">Requirements</a><br>
+ K.2 <a href="#d3e36674">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>
@@ -1561,6 +1562,7 @@
<a href="#style-attribute-fontVariantPosition">tts:fontVariantPosition</a>,
<a href="#style-attribute-fontWeight">tts:fontWeight</a>,
<a href="#style-attribute-height">tts:height</a>,
+<a href="#style-attribute-letterSpacing">tts:letterSpacing</a>,
<a href="#style-attribute-lineHeight">tts:lineHeight</a>,
<a href="#style-attribute-opacity">tts:opacity</a>,
<a href="#style-attribute-origin">tts:origin</a>,
@@ -2648,7 +2650,7 @@
in an external namespace, such as <code>m708:aspectRatio</code> as defined in <a href="#smpte2052">[SMPTE 2052-11]</a>, §5.4.4.
This would permit, for example, the interchange of information that reflects the
the semantics of <a href="#cea708e">[CEA-708-E]</a> , §4.5 “Caption Service Metadata”, “ASPECT RATIO”.</p></div><p>If the <a href="#style-attribute-position"><code>tts:position</code></a> attribute is specified on the <code>tt</code>
-element, then it must adhere to <a href="#style-attribute-position"><b>10.2.24 tts:position</b></a>, in which case it
+element, then it must adhere to <a href="#style-attribute-position"><b>10.2.25 tts:position</b></a>, in which case it
specifies the position of the <a href="#terms-root-container-region">root container region</a> relative to a reference positioning area.</p><p>Except for the <code>tts:extent</code> and <code>tts:position</code> attributes described above, an attribute in the TT Style Namespace should not
be specified on the <code>tt</code> element unless it denotes an inheritable style property, in which case such inheritable style property is available
for <a href="#semantics-style-inheritance-root">root style inheritance</a>. If a non-inheritable style property is specified, then
@@ -3855,7 +3857,7 @@
<h3><a id="styling-attribute-vocabulary"></a>10.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>10.2.1 style</b></a> attribute used
with certain animation elements, <a href="#terms-content-element">content elements</a>, certain layout elements, and style definition 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="#terms-content-element">content elements</a>
-that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>10.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-backgroundImage"><b>10.2.3 tts:backgroundImage</b></a></p></li><li><p><a href="#style-attribute-backgroundPosition"><b>10.2.4 tts:backgroundPosition</b></a></p></li><li><p><a href="#style-attribute-backgroundRepeat"><b>10.2.5 tts:backgroundRepeat</b></a></p></li><li><p><a href="#style-attribute-border"><b>10.2.6 tts:border</b></a></p></li><li><p><a href="#style-attribute-color"><b>10.2.7 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>10.2.8 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>10.2.9 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>10.2.10 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>10.2.11 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>10.2.12 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.13 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.14 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.15 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.16 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.17 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.18 tts:height</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.19 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.20 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.21 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.22 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.23 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.24 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.25 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.26 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.27 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.28 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.29 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.30 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.31 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.32 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.33 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.34 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.35 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.36 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.37 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.38 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.39 tts:zIndex</b></a></p></li></ul><table border="1" class="ednote" summary="Editorial note: Additional Border Styling Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Border Styling Attributes</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:borderColor</code>, <code>tts:borderStyle</code>, and <code>tts:borderWidth</code>
+that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>10.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-backgroundImage"><b>10.2.3 tts:backgroundImage</b></a></p></li><li><p><a href="#style-attribute-backgroundPosition"><b>10.2.4 tts:backgroundPosition</b></a></p></li><li><p><a href="#style-attribute-backgroundRepeat"><b>10.2.5 tts:backgroundRepeat</b></a></p></li><li><p><a href="#style-attribute-border"><b>10.2.6 tts:border</b></a></p></li><li><p><a href="#style-attribute-color"><b>10.2.7 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>10.2.8 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>10.2.9 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>10.2.10 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>10.2.11 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>10.2.12 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.13 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.14 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.15 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.16 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.17 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.18 tts:height</b></a></p></li><li><p><a href="#style-attribute-letterSpacing"><b>10.2.19 tts:letterSpacing</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.20 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.21 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.22 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.23 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.24 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.25 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.26 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.27 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.28 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.29 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.30 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.31 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.32 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.33 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.34 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.35 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.36 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.37 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.38 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.39 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.40 tts:zIndex</b></a></p></li></ul><table border="1" class="ednote" summary="Editorial note: Additional Border Styling Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Border Styling Attributes</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:borderColor</code>, <code>tts:borderStyle</code>, and <code>tts:borderWidth</code>
in order to provide a means to independently express styling of the four different borders (top, right, bottom, left). As currently specified, i.e., with only the
<code>tts:border</code> attribute, one can only express the four borders using the same color, style, and width.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Clip, Origin, Size"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Clip, Origin, Size</b></td><td align="right" valign="top">2014-11-27</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:backgroundClip</code>,
<code>tts:backgroundOrigin</code>, and
@@ -4525,7 +4527,38 @@
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If a <a href="#style-value-measure"><measure></a> is expressed as a <a href="#style-value-length"><length></a> value, then it must be non-negative.</p><p>The <code>tts:height</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Height Percentage"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Height Percentage</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify resolution of percentage value.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Height Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Height Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:height.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.15.14, and <a href="#css3-box">[CSS Box Model]</a>, § 9</p></div></div><div class="div3">
-<h4><a id="style-attribute-lineHeight"></a>10.2.19 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-letterSpacing"></a>10.2.19 tts:letterSpacing</h4><p>The <code>tts:letterSpacing</code> attribute is used to specify a style property that
+increases or decreases the nominal distance between glyph areas.</p><p>Letter spacing has no affect at the beginning or ending of a line area, and must not
+be applied to zero-width glyphs. Furthermore, letter spacing must not cause normally connected glyphs,
+e.g., as used in cursive scripts or with cursive fonts, to become disconnected.</p><p>Letter spacing is applied independently from kerning and justification. Depending upon the font(s) in use,
+the script(s) being presented, and the capabilities of a presentation processor, either or both kerning and
+justification may be applied in addition to letter spacing.</p><p>This attribute may be specified by any
+element type
+that permits use of attributes in the TT Style Namespace; however, this attribute applies
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-letterSpacing"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+<code>normal</code> |
+<a href="#style-value-length"><length></a>
+</td></tr><tr><td><em>Initial:</em></td><td><code>normal</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>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
+each character child of a <code>p</code> element is considered to be enclosed in an anonymous
+span.</p><p>The value <code>normal</code> corresponds to specifying a <a href="#style-value-length"><length></a> value of zero (0),
+i.e., neither expand nor compress adjacent glyph spacing.</p><p>If a <a href="#style-value-length"><length></a> value is expressed as a positive scalar (not a percentage),
+then the spaces between adjacent glyphs are expanded by an additional amount equal to that scalar value.
+If expressed as a negative scalar,
+then the spaces between adjacent glyphs are compressed by an additional amount equal to that scalar value, possibly resulting
+in overlapping glyph areas, up to a maximum amount that results in the origin of a subsequent glyph being equal to the
+origin of its preceding glyph.</p><p>If a <a href="#style-value-length"><length></a> value is expressed as a percentage, then that
+percentage is to be interpreted as relative to the value implied by <code>normal</code> letter spacing.
+Negative percentage values are not permitted.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>For example, a value of 100% is interpreted as equal to <code>normal</code> letter spacing, while
+50% is interpreted as half of normal letter spacing and 200% is interpreted as double normal spacing.</p></div><p>If a computed value of the letter spacing associated with this attribute is not supported,
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the one-dimensional Euclidean distance between
+the computed letter spacing and the supported letter spacing is minimized. If there are multiple closest supported values equally distant from
+the computed value for a given edge, then the value least distant from 0 is used.</p></div><p>The <code>tts:letterSpacing</code> style is illustrated by the following
+example.</p><table border="1" class="ednote" summary="Editorial note: Letter Spacing Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Letter Spacing Example</b></td><td align="right" valign="top">2014-11-30</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:letterSpacing.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
+represented by this attribute are based upon that defined by <a href="#css3-text">[CSS Text]</a>,
+§ 8.2.</p></div></div><div class="div3">
+<h4><a id="style-attribute-lineHeight"></a>10.2.20 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
defines the inter-baseline separation between line areas generated by content flowed into a region.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -4587,7 +4620,7 @@
allocation rectangle of a line be consistent with the <span class="strong">per-inline-height-rectangle</span>
as defined by <a href="#xsl11">[XSL 1.1]</a>, § 4.5, i.e., that a CSS-style line box stacking strategy be used.
</p></div></div><div class="div3">
-<h4><a id="style-attribute-opacity"></a>10.2.20 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-opacity"></a>10.2.21 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
defines the opacity (or conversely, the transparency)
of marks associated with a region or an area generated by content flowed into a region.</p><p>When presented onto a visual medium, the opacity of the region is applied uniformly and on a linear scale
to all marks produced by content targeted to the
@@ -4636,7 +4669,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#css3-color">[CSS3 Color]</a>,
§ 3.2.</p></div></div><div class="div3">
-<h4><a id="style-attribute-origin"></a>10.2.21 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
+<h4><a id="style-attribute-origin"></a>10.2.22 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
<em>x</em> and <em>y</em> coordinates of the origin of a
region area with respect to the origin of the <a href="#terms-root-container-region">root container region</a>.</p><p>If both <code>tts:origin</code> and <a href="#style-attribute-position"><code>tts:position</code></a> attributes are
specified on an element, then the <code>tts:origin</code> attribute must be ignored for the purpose of presentation processing.</p><p>This attribute may be specified by any
@@ -4676,7 +4709,7 @@
</p>
</pre></div>
</td></tr></tbody></table><p></p><a id="style-attribute-origin-example-1-images"></a><table class="example-images"><caption>Example Rendition – Origin</caption><tbody><tr><td><img src="images/origin.png" alt="TTML origin style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-attribute-overflow"></a>10.2.22 tts:overflow</h4><p>The <code>tts:overflow</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-overflow"></a>10.2.23 tts:overflow</h4><p>The <code>tts:overflow</code> attribute is used to specify a style property that
defines whether a region area is clipped or not if the descendant areas of the region overflow
its extent.</p><p>This attribute may be specified by any
element type
@@ -4736,7 +4769,7 @@
progression direction as opposed to the inline progression direction.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.21.2.</p></div></div><div class="div3">
-<h4><a id="style-attribute-padding"></a>10.2.23 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
+<h4><a id="style-attribute-padding"></a>10.2.24 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
space on one or more sides of a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -4793,7 +4826,7 @@
§ 7.31.15, except that individual shorthand values map to writing
mode relative padding values as defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.8.31, 7.8.32, 7.8.33, and 7.8.34.</p></div></div><div class="div3">
-<h4><a id="style-attribute-position"></a>10.2.24 tts:position</h4><p>The <code>tts:position</code> attribute is used as an alternative way to specify the position
+<h4><a id="style-attribute-position"></a>10.2.25 tts:position</h4><p>The <code>tts:position</code> attribute is used as an alternative way to specify the position
of a region area with respect the <a href="#terms-root-container-region">root container region</a>.</p><p>If both <code>tts:position</code> and <a href="#style-attribute-origin"><code>tts:origin</code></a> attributes are
specified on an element, then the <code>tts:origin</code> attribute must be ignored for the purpose of presentation processing.</p><p>This attribute may be specified by any element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -4840,7 +4873,7 @@
</pre></div>
</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Border Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Border Example Image</b></td><td align="right" valign="top">2011-11-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of position example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
the <code>background-position</code> property defined by <a href="#css3-bb">[CSS Backgrounds and Borders]</a>, § 3.6.</p></div></div><div class="div3">
-<h4><a id="style-attribute-ruby"></a>10.2.25 tts:ruby</h4><p>The <code>tts:ruby</code> attribute is used to specify the application of ruby
+<h4><a id="style-attribute-ruby"></a>10.2.26 tts:ruby</h4><p>The <code>tts:ruby</code> attribute is used to specify the application of ruby
styling.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-ruby"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>none</code> |
@@ -4987,7 +5020,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-ruby-example-2-images"></a><table class="example-images"><caption>Example Rendition – Complex Ruby</caption><tbody><tr><td><img src="images/ruby_2.png" alt="TTML ruby style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#ruby">[Ruby]</a> and <a href="#cssruby">[CSS Ruby]</a>. See also
<a href="#jlreq">[JLREQ]</a>, §3.3, for further information.</p></div></div><div class="div3">
-<h4><a id="style-attribute-rubyAlign"></a>10.2.26 tts:rubyAlign</h4><p>The <code>tts:rubyAlign</code> attribute is used to specify the position of ruby text within the inline area generated by the ruby text container annotation.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
+<h4><a id="style-attribute-rubyAlign"></a>10.2.27 tts:rubyAlign</h4><p>The <code>tts:rubyAlign</code> attribute is used to specify the position of ruby text within the inline area generated by the ruby text container annotation.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>start</code> |
<code>center</code> |
@@ -5006,7 +5039,7 @@
then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>spaceAround</code>.</p><table border="1" class="ednote" summary="Editorial note: Ruby Align Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Ruby Align Example</b></td><td align="right" valign="top">2014-09-20</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add example source and rendering of tts:rubyAlign.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#cssruby">[CSS Ruby]</a>, §4.3, and the examples and example
renderings shown there apply.</p></div></div><div class="div3">
-<h4><a id="style-attribute-rubyOffset"></a>10.2.27 tts:rubyOffset</h4><p>The <code>tts:rubyOffset</code> attribute is used to specify the offset (distance) of ruby text with respect to its associated ruby base
+<h4><a id="style-attribute-rubyOffset"></a>10.2.28 tts:rubyOffset</h4><p>The <code>tts:rubyOffset</code> attribute is used to specify the offset (distance) of ruby text with respect to its associated ruby base
in the block progression dimension.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyOffset"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-length"><length></a>
@@ -5016,7 +5049,7 @@
generated by a ruby text container (explicit or implied) and padding edge <em>E<sub>2</sub></em> of the inline area generated by a ruby base container (explicit or implied), where
<em>E<sub>1</sub></em> and <em>E<sub>2</sub></em> are perpendicular to the block progression direction and are (or would be) adjacent in the absence of
such an offset.</p><p>Negative length expressions are permitted.</p><table border="1" class="ednote" summary="Editorial note: Ruby Offset Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Ruby Offset Example</b></td><td align="right" valign="top">2014-10-02</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add example source and rendering of tts:rubyOffset.</td></tr></table></div><div class="div3">
-<h4><a id="style-attribute-rubyPosition"></a>10.2.28 tts:rubyPosition</h4><p>The <code>tts:rubyPosition</code> attribute is used to specify the position of ruby text in the block progression dimension
+<h4><a id="style-attribute-rubyPosition"></a>10.2.29 tts:rubyPosition</h4><p>The <code>tts:rubyPosition</code> attribute is used to specify the position of ruby text in the block progression dimension
with respect to its associated ruby base.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyPosition"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>before</code> |
@@ -5033,7 +5066,7 @@
then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>before</code>.</p><a id="rubyPosition-semantics-mapping-table"></a><table class="common"><caption>Table 8-2 – Ruby Position Semantics Mapping by Writing Mode</caption><col width="20%" span="1"><col width="20%" span="1"><col width="20%" span="1"><col width="20%" span="1"><col width="20%" span="1"><col span="1"><tbody><tr><th>tts:rubyPosition</th><th><code>lrtb</code></th><th><code>rltb</code></th><th><code>tbrl</code></th><th><code>tblr</code></th></tr><tr><td><code>before</code></td><td><code>over</code></td><td><code>over</code></td><td><code>right</code></td><td><code>left</code></td></tr><tr><td><code>after</code></td><td><code>under</code></td><td><code>under</code></td><td><code>left</code></td><td><code>right</code></td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Ruby Position Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Ruby Position Example</b></td><td align="right" valign="top">2014-09-20</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add example source and rendering of tts:rubyPosition.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#cssruby">[CSS Ruby]</a>, §4.1, and the examples and example
renderings shown there apply modulo the mappings defined above.</p></div></div><div class="div3">
-<h4><a id="style-attribute-showBackground"></a>10.2.29 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
+<h4><a id="style-attribute-showBackground"></a>10.2.30 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
constraints on when the background color of a region is intended to be
presented.</p><p>This attribute may be specified by any
element type
@@ -5074,7 +5107,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#smil3">[SMIL 3.0]</a>,
§ 7.4.2.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textAlign"></a>10.2.30 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textAlign"></a>10.2.31 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
defines how inline areas are aligned within a containing block area in the inline progression
direction.</p><p>This attribute may be specified by any
element type
@@ -5125,7 +5158,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-textAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="TTML textAlign style property"></td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Text Align on Span Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Align on Span Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of use of tts:textAlign on a span element.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.16.9.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textDecoration"></a>10.2.31 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textDecoration"></a>10.2.32 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
defines a text decoration effect to apply to glyph areas or other inline
areas that are generated by content flowed into a region.</p><p>This attribute may be specified by any
element type
@@ -5174,7 +5207,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-textDecoration-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="TTML textDecoration style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.17.4.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textOrientation"></a>10.2.32 tts:textOrientation</h4><p>The <code>tts:textOrientation</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textOrientation"></a>10.2.33 tts:textOrientation</h4><p>The <code>tts:textOrientation</code> attribute is used to specify a style property that
defines a text orientation to apply to glyphs that are selected for glyph areas generated
by content flowed into a region to which a vertical writing mode applies.</p><p>This attribute may be specified by any
element type
@@ -5209,7 +5242,7 @@
example.</p><table border="1" class="ednote" summary="Editorial note: Text Orientation Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Orientation Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textOrientation.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#css3-wm">[CSS Writing Modes]</a>,
§ 5.1.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textOutline"></a>10.2.33 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textOutline"></a>10.2.34 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
defines a text outline effect to apply to glyphs that are selected for glyph areas generated
by content flowed into a region.</p><p>This attribute may be specified by any
element type
@@ -5258,7 +5291,7 @@
</p>
</pre></div>
</td></tr></tbody></table><p></p><a id="style-attribute-textOutline-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Outline</caption><tbody><tr><td><img src="images/textOutline.png" alt="textOutline style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-attribute-unicodeBidi"></a>10.2.34 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-unicodeBidi"></a>10.2.35 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
defines a directional embedding or override according to
the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
element type
@@ -5297,7 +5330,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.29.6.</p></div></div><div class="div3">
-<h4><a id="style-attribute-visibility"></a>10.2.35 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-visibility"></a>10.2.36 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
defines whether generated areas are visible or not when rendered on a visual
presentation medium.</p><p>This attribute may be specified by any
element type
@@ -5352,7 +5385,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.30.17.</p></div></div><div class="div3">
-<h4><a id="style-attribute-width"></a>10.2.36 tts:width</h4><p>The <code>tts:width</code> attribute is used to specify the
+<h4><a id="style-attribute-width"></a>10.2.37 tts:width</h4><p>The <code>tts:width</code> attribute is used to specify the
<em>width</em> of an area generated by content flowed into a region.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <em>width</em> is interpreted in a writing mode relative manner
such that <em>width</em> always corresponds to a measure in the inline
progression direction. Therefore, in horizontal writing modes, <em>width</em> expresses a horizontal measure,
@@ -5372,7 +5405,7 @@
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If a <a href="#style-value-measure"><measure></a> is expressed as a <a href="#style-value-length"><length></a> value, then it must be non-negative.</p><p>The <code>tts:width</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Width Percentage"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Width Percentage</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify resolution of percentage value.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Width Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Width Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:width.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.15.14, and <a href="#css3-box">[CSS Box Model]</a>, § 9</p></div></div><div class="div3">
-<h4><a id="style-attribute-wrapOption"></a>10.2.37 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-wrapOption"></a>10.2.38 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
defines whether or not automatic line wrapping (breaking) applies within the context of
the affected element.</p><p>This attribute may be specified by any
element type
@@ -5406,7 +5439,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-wrapOption-example-1-images"></a><table class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="TTML wrapOption style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.16.13.</p></div></div><div class="div3">
-<h4><a id="style-attribute-writingMode"></a>10.2.38 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-writingMode"></a>10.2.39 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
defines the block and inline progression directions to be used for the purpose of
stacking block and inline areas within a region area.</p><p>This attribute may be specified by any
element type
@@ -5457,7 +5490,7 @@
the Latin script.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.29.7.</p></div></div><div class="div3">
-<h4><a id="style-attribute-zIndex"></a>10.2.39 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-zIndex"></a>10.2.40 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
defines the front-to-back ordering of region areas in the case that they overlap.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -9554,6 +9587,9 @@
<a href="http://dev.w3.org/csswg/css-ruby-1/"><cite>CSS Ruby Layout Module Level 1</cite></a>
W3C Editor's Draft.
(See <a href="http://dev.w3.org/csswg/css-ruby-1/">http://dev.w3.org/csswg/css-ruby-1/</a>.)
+</dd><dt class="label"><a id="css3-text"></a>CSS Text</dt><dd>Elika Etamad (aka fantasai) and Koji Ishii,
+<a href="http://dev.w3.org/csswg/css-text-3/"><cite>CSS Text Module Level 3</cite></a>, W3C Editor's Draft. (See
+<a href="http://dev.w3.org/csswg/css-text-3/">http://dev.w3.org/csswg/css-text-3/</a>.)
</dd><dt class="label"><a id="css3-wm"></a>CSS Writing Modes</dt><dd>Elika Etamad and Koji Ishii,
<a href="http://dev.w3.org/csswg/css-writing-modes-3/"><cite>CSS Writing Modes Level 3</cite></a>, W3C Editor's Draft. (See
<a href="http://dev.w3.org/csswg/css-writing-modes-3/">http://dev.w3.org/csswg/css-writing-modes-3/</a>.)
@@ -9621,7 +9657,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="d3e34860"></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="d3e35000"></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
@@ -9678,7 +9714,7 @@
and <code>@version</code> on the <code>svg:svg</code> element.</p></li><li><p>Conceptually derived from existing <code>tt:layout</code> element,
which is a generic container for layout specifications, but for use
in defining animation specifications that apply to targeted elements.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e35377"></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="d3e35517"></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
@@ -9770,9 +9806,9 @@
<h2><a id="qa"></a>K QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
Framework Specifications Guidelines</a> <a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e36370"></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="d3e36510"></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="d3e36534"></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-profiling">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="d3e36674"></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-profiling">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">