--- a/ttml2/spec/ttml2.html Wed Jan 07 23:59:50 2015 -0700
+++ b/ttml2/spec/ttml2.html Thu Jan 08 00:00:01 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/08 01:44:07 $<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/08 06:59:50 $<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/08 01:44:07 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/01/08 06:59:50 $ @@ @@@@ @@@@</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,16 +260,17 @@
10.2.31 <a href="#style-attribute-rubyPosition">tts:rubyPosition</a><br>
10.2.32 <a href="#style-attribute-showBackground">tts:showBackground</a><br>
10.2.33 <a href="#style-attribute-textAlign">tts:textAlign</a><br>
- 10.2.34 <a href="#style-attribute-textDecoration">tts:textDecoration</a><br>
- 10.2.35 <a href="#style-attribute-textEmphasis">tts:textEmphasis</a><br>
- 10.2.36 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
- 10.2.37 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
- 10.2.38 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
- 10.2.39 <a href="#style-attribute-visibility">tts:visibility</a><br>
- 10.2.40 <a href="#style-attribute-width">tts:width</a><br>
- 10.2.41 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
- 10.2.42 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
- 10.2.43 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
+ 10.2.34 <a href="#style-attribute-textCombine">tts:textCombine</a><br>
+ 10.2.35 <a href="#style-attribute-textDecoration">tts:textDecoration</a><br>
+ 10.2.36 <a href="#style-attribute-textEmphasis">tts:textEmphasis</a><br>
+ 10.2.37 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
+ 10.2.38 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
+ 10.2.39 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
+ 10.2.40 <a href="#style-attribute-visibility">tts:visibility</a><br>
+ 10.2.41 <a href="#style-attribute-width">tts:width</a><br>
+ 10.2.42 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
+ 10.2.43 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
+ 10.2.44 <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>
@@ -287,9 +288,10 @@
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-number"><number></a><br>
- 10.3.18 <a href="#style-value-percentage"><percentage></a><br>
- 10.3.19 <a href="#style-value-position"><position></a><br>
+ 10.3.17 <a href="#style-value-non-negative-integer"><non-negative-integer></a><br>
+ 10.3.18 <a href="#style-value-number"><number></a><br>
+ 10.3.19 <a href="#style-value-percentage"><percentage></a><br>
+ 10.3.20 <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>
@@ -513,11 +515,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="#d3e35893">Element Derivation</a><br>
- J.2 <a href="#d3e36410">Attribute Derivation</a><br>
+ J.1 <a href="#d3e36021">Element Derivation</a><br>
+ J.2 <a href="#d3e36538">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e37403">Requirements</a><br>
- K.2 <a href="#d3e37567">Guidelines</a><br>
+ K.1 <a href="#d3e37531">Requirements</a><br>
+ K.2 <a href="#d3e37695">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>
@@ -1601,6 +1603,7 @@
<a href="#style-attribute-rubyPosition">tts:rubyPosition</a>,
<a href="#style-attribute-showBackground">tts:showBackground</a>,
<a href="#style-attribute-textAlign">tts:textAlign</a>,
+<a href="#style-attribute-textCombine">tts:textCombine</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>,
@@ -3883,7 +3886,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-fontShear"><b>10.2.15 tts:fontShear</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.16 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.17 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.18 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.19 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.20 tts:height</b></a></p></li><li><p><a href="#style-attribute-letterSpacing"><b>10.2.21 tts:letterSpacing</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.22 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.23 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.24 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.25 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.26 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.27 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.28 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.29 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.30 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.31 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.32 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.33 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.34 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textEmphasis"><b>10.2.35 tts:textEmphasis</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.36 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.37 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.38 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.39 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.40 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.41 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.42 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.43 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-fontShear"><b>10.2.15 tts:fontShear</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.16 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.17 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.18 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.19 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.20 tts:height</b></a></p></li><li><p><a href="#style-attribute-letterSpacing"><b>10.2.21 tts:letterSpacing</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.22 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.23 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.24 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.25 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.26 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.27 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.28 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.29 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.30 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.31 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.32 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.33 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textCombine"><b>10.2.34 tts:textCombine</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.35 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textEmphasis"><b>10.2.36 tts:textEmphasis</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.37 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.38 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.39 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.40 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.41 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.42 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.43 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.44 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
@@ -5231,7 +5234,28 @@
</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.34 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textCombine"></a>10.2.34 tts:textCombine</h4><p>When a vertical writing mode applies, the <code>tts:textCombine</code> attribute is used to specify a style property that
+determines whether and how multiple nominally non-combining characters are combined so that their glyph areas
+consume the nominal bounding box of a single em square. If a horizontal writing mode applies, then this property is ignored
+for the purpose of presentation processing.</p><p>Combination processing may make use of one or more techniques to obtain the goal of visual combination into an em square. For
+example, half-width variant forms may be selected, a ligature may be selected, a smaller font size may be applied, etc. At a minimum, an
+implementation that supports this style property must be able to select half-width variant forms if available.</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-textCombine"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+<code>none</code> |
+<code>all</code> |
+[ <code>digits</code> <a href="#style-value-non-negative-integer"><non-negative-integer></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</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>none</code>, then no combination processing applies.
+If the specified value of this attribute is <code>all</code>, then all affected characters should be combined.
+If the specified value of this attribute is <code>digits</code>, then all affected characters should be combined if they are a sequence of a digits which length is
+equal to or less than a specified count, or two (2) if no count is specified.</p><p>Combination must not cross an element boundary, a bidirectional boundary, or a non-glyph area boundary.</p><p>This attribute has no impact on or interaction with the nominal layout of glyph areas that constitute a Unicode combining character sequence.</p><table border="1" class="ednote" summary="Editorial note: Text Combine Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Combine 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:textCombine.</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>, § 9.1.</p></div></div><div class="div3">
+<h4><a id="style-attribute-textDecoration"></a>10.2.35 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
@@ -5280,7 +5304,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-textEmphasis"></a>10.2.35 tts:textEmphasis</h4><p>The <code>tts:textEmphasis</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textEmphasis"></a>10.2.36 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
@@ -5302,7 +5326,7 @@
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.36 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.37 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
@@ -5337,7 +5361,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.37 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.38 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
@@ -5386,7 +5410,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.38 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.39 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
@@ -5425,7 +5449,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.39 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.40 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
@@ -5480,7 +5504,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.40 tts:width</h4><p>The <code>tts:width</code> attribute is used to specify the
+<h4><a id="style-attribute-width"></a>10.2.41 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,
@@ -5500,7 +5524,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.41 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.42 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
@@ -5534,7 +5558,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.42 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.43 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
@@ -5585,7 +5609,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.43 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.44 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
@@ -5660,7 +5684,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-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-number"><b>10.3.17 <number></b></a></p></li><li><p><a href="#style-value-percentage"><b>10.3.18 <percentage></b></a></p></li><li><p><a href="#style-value-position"><b>10.3.19 <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-non-negative-integer"><b>10.3.17 <non-negative-integer></b></a></p></li><li><p><a href="#style-value-number"><b>10.3.18 <number></b></a></p></li><li><p><a href="#style-value-percentage"><b>10.3.19 <percentage></b></a></p></li><li><p><a href="#style-value-position"><b>10.3.20 <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,
@@ -5900,7 +5924,7 @@
<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>+
+ : ( "+" | "-" )? <a href="#style-value-non-negative-integer"><non-negative-integer></a>
</pre></div>
</td></tr></tbody></table></div><div class="div3">
<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
@@ -5992,7 +6016,13 @@
</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-number"></a>10.3.17 <number></h4><p>An <number> expression is used to express an arbitrary, signed integer or real valued number.</p><a id="number-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <number></caption><tbody><tr><td>
+<h4><a id="style-value-non-negative-integer"></a>10.3.17 <non-negative-integer></h4><p>A <non-negative-integer> expression is used to express an arbitrary, non-negative integral value.</p><a id="non-negative-integer-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <non-negative-integer></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<non-negative-integer>
+ : <a href="#style-value-digit"><digit></a>+
+</pre></div>
+</td></tr></tbody></table></div><div class="div3">
+<h4><a id="style-value-number"></a>10.3.18 <number></h4><p>An <number> expression is used to express an arbitrary, signed integer or real valued number.</p><a id="number-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <number></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<number>
: sign? non-negative-number
@@ -6003,23 +6033,20 @@
number
non-negative-number
- : non-negative-integer
+ : <a href="#style-value-non-negative-integer"><non-negative-integer></a>
| non-negative-real
-non-negative-integer
- : <a href="#style-value-digit"><digit></a>+
-
non-negative-real
: <a href="#style-value-digit"><digit></a>* "." <a href="#style-value-digit"><digit></a>+
</pre></div>
</td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-value-percentage"></a>10.3.18 <percentage></h4><p>An <percentage> expression is used to express an arbitrary, signed integral or real valued percentage.</p><a id="percentage-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <percentage></caption><tbody><tr><td>
+<h4><a id="style-value-percentage"></a>10.3.19 <percentage></h4><p>An <percentage> expression is used to express an arbitrary, signed integral or real valued percentage.</p><a id="percentage-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <percentage></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<percentage>
: <a href="#style-value-number"><number></a> "%"
</pre></div>
</td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-value-position"></a>10.3.19 <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.20 <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
@@ -9808,7 +9835,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="d3e35893"></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="d3e36021"></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
@@ -9865,7 +9892,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="d3e36410"></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="d3e36538"></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
@@ -9957,9 +9984,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="d3e37403"></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="d3e37531"></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="d3e37567"></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="d3e37695"></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">