--- a/ttml2/spec/ttml2.html Mon Jan 05 21:21:37 2015 -0700
+++ b/ttml2/spec/ttml2.html Mon Jan 05 21:21:55 2015 -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: 2015/01/05 23:41:34 $<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: 2015/01/06 04:21:37 $<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: 2015/01/05 23:41:34 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/01/06 04:21:37 $ @@ @@@@ @@@@</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/2013/REC-ttml1-20130924/">http://www.w3.org/TR/2013/REC-ttml1-20130924/</a>
@@ -260,14 +260,15 @@
10.2.31 <a href="#style-attribute-showBackground">tts:showBackground</a><br>
10.2.32 <a href="#style-attribute-textAlign">tts:textAlign</a><br>
10.2.33 <a href="#style-attribute-textDecoration">tts:textDecoration</a><br>
- 10.2.34 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
- 10.2.35 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
- 10.2.36 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
- 10.2.37 <a href="#style-attribute-visibility">tts:visibility</a><br>
- 10.2.38 <a href="#style-attribute-width">tts:width</a><br>
- 10.2.39 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
- 10.2.40 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
- 10.2.41 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
+ 10.2.34 <a href="#style-attribute-textEmphasis">tts:textEmphasis</a><br>
+ 10.2.35 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
+ 10.2.36 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
+ 10.2.37 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
+ 10.2.38 <a href="#style-attribute-visibility">tts:visibility</a><br>
+ 10.2.39 <a href="#style-attribute-width">tts:width</a><br>
+ 10.2.40 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
+ 10.2.41 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
+ 10.2.42 <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>
@@ -275,14 +276,17 @@
10.3.4 <a href="#style-value-borderWidth"><borderWidth></a><br>
10.3.5 <a href="#style-value-color"><color></a><br>
10.3.6 <a href="#style-value-digit"><digit></a><br>
- 10.3.7 <a href="#style-value-familyName"><familyName></a><br>
- 10.3.8 <a href="#style-value-genericFamilyName"><genericFamilyName></a><br>
- 10.3.9 <a href="#style-value-hexDigit"><hexDigit></a><br>
- 10.3.10 <a href="#style-value-integer"><integer></a><br>
- 10.3.11 <a href="#style-value-length"><length></a><br>
- 10.3.12 <a href="#style-value-measure"><measure></a><br>
- 10.3.13 <a href="#style-value-namedColor"><namedColor></a><br>
- 10.3.14 <a href="#style-value-position"><position></a><br>
+ 10.3.7 <a href="#style-value-emphasisColor"><emphasisColor></a><br>
+ 10.3.8 <a href="#style-value-emphasisStyle"><emphasisStyle></a><br>
+ 10.3.9 <a href="#style-value-emphasisPosition"><emphasisPosition></a><br>
+ 10.3.10 <a href="#style-value-familyName"><familyName></a><br>
+ 10.3.11 <a href="#style-value-genericFamilyName"><genericFamilyName></a><br>
+ 10.3.12 <a href="#style-value-hexDigit"><hexDigit></a><br>
+ 10.3.13 <a href="#style-value-integer"><integer></a><br>
+ 10.3.14 <a href="#style-value-length"><length></a><br>
+ 10.3.15 <a href="#style-value-measure"><measure></a><br>
+ 10.3.16 <a href="#style-value-namedColor"><namedColor></a><br>
+ 10.3.17 <a href="#style-value-position"><position></a><br>
10.4 <a href="#semantics-styling">Styling Semantics</a><br>
10.4.1 <a href="#semantics-style-association">Style Association</a><br>
10.4.1.1 <a href="#semantics-style-association-inline">Inline Styling</a><br>
@@ -506,11 +510,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="#d3e35357">Element Derivation</a><br>
- J.2 <a href="#d3e35874">Attribute Derivation</a><br>
+ J.1 <a href="#d3e35734">Element Derivation</a><br>
+ J.2 <a href="#d3e36251">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e36867">Requirements</a><br>
- K.2 <a href="#d3e37031">Guidelines</a><br>
+ K.1 <a href="#d3e37244">Requirements</a><br>
+ K.2 <a href="#d3e37408">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>
@@ -1594,6 +1598,7 @@
<a href="#style-attribute-showBackground">tts:showBackground</a>,
<a href="#style-attribute-textAlign">tts:textAlign</a>,
<a href="#style-attribute-textDecoration">tts:textDecoration</a>,
+<a href="#style-attribute-textEmphasis">tts:textEmphasis</a>,
<a href="#style-attribute-textOrientation">tts:textOrientation</a>,
<a href="#style-attribute-textOutline">tts:textOutline</a>,
<a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a>,
@@ -3874,7 +3879,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-fontKerning"><b>10.2.13 tts:fontKerning</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.14 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.15 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.16 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.17 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.18 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.19 tts:height</b></a></p></li><li><p><a href="#style-attribute-letterSpacing"><b>10.2.20 tts:letterSpacing</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.21 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.22 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.23 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.24 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.25 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.26 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.27 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.28 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.29 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.30 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.31 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.32 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.33 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.34 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.35 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.36 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.37 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.38 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.39 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.40 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.41 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-fontKerning"><b>10.2.13 tts:fontKerning</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.14 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.15 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.16 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.17 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.18 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.19 tts:height</b></a></p></li><li><p><a href="#style-attribute-letterSpacing"><b>10.2.20 tts:letterSpacing</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.21 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.22 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.23 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.24 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.25 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.26 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.27 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.28 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.29 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.30 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.31 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.32 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.33 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textEmphasis"><b>10.2.34 tts:textEmphasis</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.35 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.36 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.37 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.38 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.39 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.40 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.41 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.42 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
@@ -4342,7 +4347,7 @@
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The initial value, <code>default</code>, is a generic font family name, and is
-further described in <a href="#style-value-genericFamilyName"><b>10.3.8 <genericFamilyName></b></a> below.</p></div><p>For the purpose of determining applicability of this style property,
+further described in <a href="#style-value-genericFamilyName"><b>10.3.11 <genericFamilyName></b></a> below.</p></div><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>If a computed value of the property associated with this attribute is not supported, then a
<a href="#terms-presentation-processor">presentation processor</a> must attempt to map the computed font family
@@ -4423,7 +4428,7 @@
the computed font size and the supported font size is minimized. If there are multiple closest supported values equally distant from
the computed value, then the value most distant from 0 (single length specification) or [0,0] (two length specifications) is used,
i.e., the largest font size, is used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
-the <em>cell</em> length unit as defined by <a href="#style-value-length"><b>10.3.11 <length></b></a>.
+the <em>cell</em> length unit as defined by <a href="#style-value-length"><b>10.3.14 <length></b></a>.
When a single <length> is expressed using cell units, then it refers to the height of
the <a href="#terms-computed-cell-size">computed cell size</a>.
When two <length> values are expressed using cell units, then the first refers to the width of
@@ -5249,7 +5254,29 @@
</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.34 tts:textOrientation</h4><p>The <code>tts:textOrientation</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textEmphasis"></a>10.2.34 tts:textEmphasis</h4><p>The <code>tts:textEmphasis</code> attribute is used to specify a style property that
+determines whether and how text emphasis marks are presented on affected content.</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-textEmphasis"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+[
+<a href="#style-value-emphasisStyle"><emphasisStyle></a> ||
+<a href="#style-value-emphasisColor"><emphasisColor></a> ||
+<a href="#style-value-emphasisPosition"><emphasisPosition></a>
+]
+</td></tr><tr><td><em>Initial:</em></td><td><code>none</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<a href="#content-vocabulary-span"><code>span</code></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous (color only)</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
+each character child of a <code>p</code> element is considered to be enclosed in an anonymous
+span.</p><p>If the specified value of this attribute is <code>auto</code>, then it must be interpreted as if
+<code>auto</code> were specified for both emphasis style and emphasis position components.</p><p>If no emphasis style is specified,
+then the emphasis style must be interpreted as if a style of <code>auto</code> were specified.
+If no emphasis color is specified,
+then the emphasis color must be interpreted as if a color of <code>current</code> were specified.
+If no emphasis position is specified,
+then the emphasis position must be interpreted as if a position of <code>auto</code> were specified.</p><table border="1" class="ednote" summary="Editorial note: Text Emphasis Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Emphasis Example</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textEmphasis.</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-decoration">[CSS Text Decoration]</a>, § 3.</p></div></div><div class="div3">
+<h4><a id="style-attribute-textOrientation"></a>10.2.35 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
@@ -5284,7 +5311,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.35 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.36 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
@@ -5333,7 +5360,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.36 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.37 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
@@ -5372,7 +5399,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.37 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.38 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
@@ -5427,7 +5454,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.38 tts:width</h4><p>The <code>tts:width</code> attribute is used to specify the
+<h4><a id="style-attribute-width"></a>10.2.39 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,
@@ -5447,7 +5474,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.39 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.40 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
@@ -5481,7 +5508,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.40 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.41 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
@@ -5532,7 +5559,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.41 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.42 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
@@ -5607,7 +5634,7 @@
</td></tr></tbody></table><p></p><p></p><a id="style-attribute-zIndex-example-1-images"></a><table class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="TTML zIndex style property"></td></tr></tbody></table><div 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.18.</p></div></div></div><div class="div2">
-<h3><a id="styling-style-value-expressions"></a>10.3 Styling Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>10.3.1 <alpha></b></a></p></li><li><p><a href="#style-value-borderColor"><b>10.3.2 <borderColor></b></a></p></li><li><p><a href="#style-value-borderStyle"><b>10.3.3 <borderStyle></b></a></p></li><li><p><a href="#style-value-borderWidth"><b>10.3.4 <borderWidth></b></a></p></li><li><p><a href="#style-value-color"><b>10.3.5 <color></b></a></p></li><li><p><a href="#style-value-digit"><b>10.3.6 <digit></b></a></p></li><li><p><a href="#style-value-familyName"><b>10.3.7 <familyName></b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>10.3.8 <genericFamilyName></b></a></p></li><li><p><a href="#style-value-hexDigit"><b>10.3.9 <hexDigit></b></a></p></li><li><p><a href="#style-value-integer"><b>10.3.10 <integer></b></a></p></li><li><p><a href="#style-value-length"><b>10.3.11 <length></b></a></p></li><li><p><a href="#style-value-measure"><b>10.3.12 <measure></b></a></p></li><li><p><a href="#style-value-namedColor"><b>10.3.13 <namedColor></b></a></p></li><li><p><a href="#style-value-position"><b>10.3.14 <position></b></a></p></li></ul><p>In the syntax representations defined in this section, no
+<h3><a id="styling-style-value-expressions"></a>10.3 Styling Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>10.3.1 <alpha></b></a></p></li><li><p><a href="#style-value-borderColor"><b>10.3.2 <borderColor></b></a></p></li><li><p><a href="#style-value-borderStyle"><b>10.3.3 <borderStyle></b></a></p></li><li><p><a href="#style-value-borderWidth"><b>10.3.4 <borderWidth></b></a></p></li><li><p><a href="#style-value-color"><b>10.3.5 <color></b></a></p></li><li><p><a href="#style-value-digit"><b>10.3.6 <digit></b></a></p></li><li><p><a href="#style-value-emphasisColor"><b>10.3.7 <emphasisColor></b></a></p></li><li><p><a href="#style-value-emphasisStyle"><b>10.3.8 <emphasisStyle></b></a></p></li><li><p><a href="#style-value-emphasisPosition"><b>10.3.9 <emphasisPosition></b></a></p></li><li><p><a href="#style-value-familyName"><b>10.3.10 <familyName></b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>10.3.11 <genericFamilyName></b></a></p></li><li><p><a href="#style-value-hexDigit"><b>10.3.12 <hexDigit></b></a></p></li><li><p><a href="#style-value-integer"><b>10.3.13 <integer></b></a></p></li><li><p><a href="#style-value-length"><b>10.3.14 <length></b></a></p></li><li><p><a href="#style-value-measure"><b>10.3.15 <measure></b></a></p></li><li><p><a href="#style-value-namedColor"><b>10.3.16 <namedColor></b></a></p></li><li><p><a href="#style-value-position"><b>10.3.17 <position></b></a></p></li></ul><p>In the syntax representations defined in this section, no
linear whitespace (LWSP) is implied or permitted between tokens
unless explicitly specified.</p><div class="div3">
<h4><a id="style-value-alpha"></a>10.3.1 <alpha></h4><p>An <alpha> expression is used to express an opacity value,
@@ -5647,8 +5674,8 @@
</pre></div>
</td></tr></tbody></table><p>The interpretation of <code>dotted</code>, <code>dashed</code>, and <code>double</code> are considered
to be implementation dependent.</p><p>If an implementation does not recognize or otherwise distinguish one of these border style values, then
-it must be interpreted as if a style of <code>solid</code> were specified; however, an implementation that
-supports borders must minimally support the <code>none</code> and <code>solid</code> values.</p></div><div class="div3">
+it must be interpreted as if a style of <code>solid</code> were specified; as such, an implementation that
+supports borders must minimally support the <code>solid</code> value.</p></div><div class="div3">
<h4><a id="style-value-borderWidth"></a>10.3.4 <borderWidth></h4><p>A <borderWidth> expression is used to express the width of one
or more borders.</p><a id="borderWidth-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <borderWidth></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -5710,7 +5737,51 @@
: "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9"
</pre></div>
</td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-value-familyName"></a>10.3.7 <familyName></h4><p>A <familyName> expression specifies a font family name.</p><a id="familyName-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <familyName></caption><tbody><tr><td>
+<h4><a id="style-value-emphasisColor"></a>10.3.7 <emphasisColor></h4><p>An <emphasisColor> expression is used to express the color of text
+emphasis marks.</p><a id="emphasisColor-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <emphasisColor></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<emphasisColor>
+ : current
+ | <a href="#style-value-color"><color></a>
+</pre></div>
+</td></tr></tbody></table><dl><dt class="label"><code>current</code></dt><dd><p>Equivalent to the computed value of <a href="#style-attribute-color"><code>tts:color</code></a> of the affected text.</p></dd><dt class="label"><a href="#style-value-color"><color></a></dt><dd><p>The specified color.</p></dd></dl><p>If an implementation does not recognize or otherwise distinguish emphasis color value, then
+it must be interpreted as if a style of <code>current</code> were specified; as such, an implementation that
+supports text emphasis marks must minimally support the <code>current</code> value.</p></div><div class="div3">
+<h4><a id="style-value-emphasisStyle"></a>10.3.8 <emphasisStyle></h4><p>An <emphasisStyle> expression is used to express the style of text
+emphasis marks.</p><a id="emphasisStyle-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <emphasisStyle></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<emphasisStyle>
+ : none
+ | auto
+ | [ filled | open ] || [ circle | dot | sesame ]
+ | <a href="#content-value-quoted-string"><quoted-string></a>
+</pre></div>
+</td></tr></tbody></table><p>The semantics of text emphasis style values are defined as follows:</p><dl><dt class="label"><code>none</code></dt><dd><p>No text emphasis mark.</p></dd><dt class="label"><code>auto</code></dt><dd><p>If a vertical writing mode applies, then equivalent to <code>filled sesame</code>; otherwise,
+equivalent to <code>filled circle</code>.</p></dd><dt class="label"><code>filled</code></dt><dd><p>Emphasis mark is filled with emphasis color.</p></dd><dt class="label"><code>open</code></dt><dd><p>Emphasis mark is not filled, i.e., its outline is stroked with the emphasis color, but it is not filled.</p></dd><dt class="label"><code>circle</code></dt><dd><p>Emphasis mark is a circle. If filled, then equivalent to U+25CF '●'; if open, then equivalent to U+25CB '○'</p></dd><dt class="label"><code>dot</code></dt><dd><p>Emphasis mark is a dot. If filled, then equivalent to U+2022 '•'; if open, then equivalent to U+25E6 '◦'</p></dd><dt class="label"><code>sesame</code></dt><dd><p>Emphasis mark is a sesame. If filled, then equivalent to U+FE45 '﹅'; if open, then equivalent to U+FE46 '﹆'</p></dd><dt class="label"><a href="#content-value-quoted-string"><quoted-string></a></dt><dd><p>Emphasis mark is the first grapheme cluster of string, with remainder of string ignored.</p></dd></dl><p>If only <code>filled</code> or <code>open</code> is specified, then it is equivalent to <code>filled circle</code> and <code>open circle</code>, respectively.</p><p>If only <code>circle</code>, <code>dot</code>, or <code>sesame</code> is specified, then it is equivalent to <code>filled circle</code>, <code>filled dot</code>, and
+<code>filled sesame</code>, respectively.</p><p>If an implementation does not recognize or otherwise distinguish an emphasis style value, then
+it must be interpreted as if a style of <code>auto</code> were specified; as such, an implementation that
+supports text emphasis marks must minimally support the <code>auto</code> value.</p></div><div class="div3">
+<h4><a id="style-value-emphasisPosition"></a>10.3.9 <emphasisPosition></h4><p>An <emphasisPosition> expression is used to express the position of text
+emphasis marks.</p><a id="emphasisPosition-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <emphasisPosition></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<emphasisPosition>
+ : auto
+ | before
+ | after
+ | outside
+</pre></div>
+</td></tr></tbody></table><dl><dt class="label"><code>auto</code></dt><dd><p>If the containing block area consists of exactly two line areas, then equivalent to <code>outside</code>; otherwise,
+equivalent to <code>before</code>.</p></dd><dt class="label"><code>before</code></dt><dd><p>Towards the before edge of the affected glyph areas. If a horizontal writing mode applies, then this is towards the
+top of the glyph areas. If a vertical writing mode applies, then this is either towards the right or left of the glyph
+areas, according to whether <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a> resolves to
+<code>tbrl</code> or <code>tblr</code>, respectively.</p></dd><dt class="label"><code>after</code></dt><dd><p>Towards the after edge of the affected glyph areas. If a horizontal writing mode applies, then this is towards the
+bottom of the glyph areas. If a vertical writing mode applies, then this is either towards the left or right of the glyph
+areas, according to whether <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a> resolves to
+<code>tbrl</code> or <code>tblr</code>, respectively.</p></dd><dt class="label"><code>outside</code></dt><dd><p>Equivalent to <code>before</code> for all but the last affected line area; otherwise, equivalent to <code>after</code>
+for the last affected line area.</p></dd></dl><p>If an implementation does not recognize or otherwise distinguish an emphasis position value, then
+it must be interpreted as if a position of <code>auto</code> were specified; as such, an implementation that
+supports text emphasis marks must minimally support the <code>auto</code> value.</p></div><div class="div3">
+<h4><a id="style-value-familyName"></a>10.3.10 <familyName></h4><p>A <familyName> expression specifies a font family name.</p><a id="familyName-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <familyName></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<familyName>
: unquoted-string
@@ -5766,7 +5837,7 @@
or CSS parser. In particular, a backslash followed by a newline is ignored by CSS, while it is not
ignored by the above syntax. Such an unignored escaped newline would need to be represented using
an equivalent <code>{unicode}</code> escape, such as <code>\a</code>, to order to express in CSS.</p></div></div><div class="div3">
-<h4><a id="style-value-genericFamilyName"></a>10.3.8 <genericFamilyName></h4><p>A <genericFamilyName> expression specifies a font family using a general
+<h4><a id="style-value-genericFamilyName"></a>10.3.11 <genericFamilyName></h4><p>A <genericFamilyName> expression specifies a font family using a general
token that indicates a class of font families.</p><p>The resolution of a generic family name to a concrete font instance is considered to
be implementation dependent, both in the case of content authoring and content interpretation.</p><a id="genericFamilyName-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <genericFamilyName></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -5791,7 +5862,7 @@
an initial value), then its typographic characteristics are considered to be implementation
dependent; however, it is recommended that this default font family be mapped to
an monospaced, sans-serif font.</p></div><div class="div3">
-<h4><a id="style-value-hexDigit"></a>10.3.9 <hexDigit></h4><p>A <hexDigit> is used to express integers and other types of numbers or tokens
+<h4><a id="style-value-hexDigit"></a>10.3.12 <hexDigit></h4><p>A <hexDigit> is used to express integers and other types of numbers or tokens
that employ base 16 arithmetic.</p><p>For the purpose of parsing, a distinction must not be made between lower and upper case.</p><a id="hexDigit-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <hexDigit></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<hexDigit>
@@ -5800,13 +5871,13 @@
| "A" | "B" | "C" | "D" | "E" | "F"
</pre></div>
</td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-value-integer"></a>10.3.10 <integer></h4><p>An <integer> expression is used to express an arbitrary, signed integral value.</p><a id="integer-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <integer></caption><tbody><tr><td>
+<h4><a id="style-value-integer"></a>10.3.13 <integer></h4><p>An <integer> expression is used to express an arbitrary, signed integral value.</p><a id="integer-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <integer></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<integer>
: ( "+" | "-" )? <a href="#style-value-digit"><digit></a>+
</pre></div>
</td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-value-length"></a>10.3.11 <length></h4><p>A <length> expression is used to express either a coordinate component of point
+<h4><a id="style-value-length"></a>10.3.14 <length></h4><p>A <length> expression is used to express either a coordinate component of point
in a cartesian space or a distance between two points in a cartesian space.</p><a id="length-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <length></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<length>
@@ -5863,7 +5934,7 @@
the minimum and maxium of <code>vw</code> and <code>vh</code>, respectively. For example,
the length <code>25vmin</code> is interpreted as the minimum of 25% of the width and
25% of the height of the <a href="#terms-root-container-region">root container region</a>.</p></div><div class="div3">
-<h4><a id="style-value-measure"></a>10.3.12 <measure></h4><p>A <measure> value expresses a distance used to measure an allocation
+<h4><a id="style-value-measure"></a>10.3.15 <measure></h4><p>A <measure> value expresses a distance used to measure an allocation
dimension in either the inline progression direction or the block progression direction, where
the direction that applies is determined by the context of use.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The terms <em>width</em> and <em>height</em> are interpreted in a writing mode relative manner
such that <em>width</em> always corresponds to a measure in the inline
@@ -5888,7 +5959,7 @@
all possible line break positions, i.e., both hard (mandatory) and soft (optional) break points.</p><p>For vertical writing mode, the sense of width and height is reversed.</p></dd><dt class="label"><code>minContent</code></dt><dd><p>For width in a horizontal writing mode, the minimum numeric value that encloses all of the element's content such that lines are broken at
all possible line break positions, i.e., both hard (mandatory) and soft (optional) break points.</p><p>For height in a horizontal writing mode, the minimum numeric value that encloses all of the element's content such that lines are broken only at
hard, i.e., mandatory, break points, even if that means overflowing the parent's width.</p><p>For vertical writing mode, the sense of width and height is reversed.</p></dd><dt class="label"><code><a href="#style-value-length"><length></a></code></dt><dd><p>A non-negative numeric value expressed as a scalar or percentage.</p></dd></dl></div><div class="div3">
-<h4><a id="style-value-namedColor"></a>10.3.13 <namedColor></h4><p>A <namedColor> is used to express an RGBA color with a convenient name, and where the applicable color space is
+<h4><a id="style-value-namedColor"></a>10.3.16 <namedColor></h4><p>A <namedColor> is used to express an RGBA color with a convenient name, and where the applicable color space is
defined by <a href="#srgb">[SRGB]</a>.</p><p>For the purpose of parsing, a distinction must not be made between lower and upper case.</p><a id="namedColor-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <namedColor></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<namedColor>
@@ -5914,7 +5985,7 @@
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>Except for <code>transparent</code>, the set of named colors specified above constitutes a proper
subset of the set of named colors specified by <a href="#svg11">[SVG 1.1]</a>, § 4.2.</p></div></div><div class="div3">
-<h4><a id="style-value-position"></a>10.3.14 <position></h4><p>A <position> expression is used to indirectly determine the origin of an area or an image with respect to a reference area.</p><a id="position-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <position></caption><tbody><tr><td>
+<h4><a id="style-value-position"></a>10.3.17 <position></h4><p>A <position> expression is used to indirectly determine the origin of an area or an image with respect to a reference area.</p><a id="position-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <position></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<position>
: offset-position-h // single component value
@@ -9633,6 +9704,9 @@
</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-decoration"></a>CSS Text Decoration</dt><dd>Elika Etamad (aka fantasai) and Koji Ishii,
+<a href="http://dev.w3.org/csswg/css-text-decor-3/"><cite>CSS Text Decoration Module Level 3</cite></a>, W3C Editor's Draft. (See
+<a href="http://dev.w3.org/csswg/css-text-decor-3/">http://dev.w3.org/csswg/css-text-decor-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>.)
@@ -9700,7 +9774,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="d3e35357"></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="d3e35734"></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
@@ -9757,7 +9831,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="d3e35874"></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="d3e36251"></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
@@ -9849,9 +9923,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="d3e36867"></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="d3e37244"></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="d3e37031"></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="d3e37408"></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">