--- a/ttml2/spec/ttml2.html Mon Jan 05 11:56:45 2015 -0700
+++ b/ttml2/spec/ttml2.html Mon Jan 05 11:58:25 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 09:36:30 $<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/05 18:56:45 $<div id="revisions"></div><div class="head">
<h1><a id="title"></a>Timed Text Markup Language 2 (TTML2)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/01/05 09:36:30 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/01/05 18:56:45 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ttml2.html">ttml2.html</a>
</dd><dt>Latest version:</dt><dd><a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8">https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
@@ -505,11 +505,11 @@
H <a href="#other-references">Other References</a> (Non-Normative)<br>
I <a href="#requirements">Requirements</a> (Non-Normative)<br>
J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
- J.1 <a href="#d3e35235">Element Derivation</a><br>
- J.2 <a href="#d3e35752">Attribute Derivation</a><br>
+ J.1 <a href="#d3e35237">Element Derivation</a><br>
+ J.2 <a href="#d3e35754">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e36745">Requirements</a><br>
- K.2 <a href="#d3e36909">Guidelines</a><br>
+ K.1 <a href="#d3e36747">Requirements</a><br>
+ K.2 <a href="#d3e36911">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>
@@ -4542,7 +4542,7 @@
<a href="#embedded-content-vocabulary-image"><code>image</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If a <a href="#style-value-measure"><measure></a> is expressed as a <a href="#style-value-length"><length></a> value, then it must be non-negative.</p><p>The <code>tts:height</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Height Percentage"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Height Percentage</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify resolution of percentage value.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Height Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Height Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:height.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
-§ 7.15.14, and <a href="#css3-box">[CSS Box Model]</a>, § 9</p></div></div><div class="div3">
+§ 7.15.6, and <a href="#css3-box">[CSS Box Model]</a>, § 9</p></div></div><div class="div3">
<h4><a id="style-attribute-letterSpacing"></a>10.2.19 tts:letterSpacing</h4><p>The <code>tts:letterSpacing</code> attribute is used to specify a style property that
increases or decreases the nominal distance between glyph areas.</p><p>Letter spacing has no affect at the beginning or ending of a line area, and must not
be applied to zero-width glyphs. Furthermore, letter spacing must not cause normally connected glyphs,
@@ -5841,7 +5841,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 expression is used to express a distance used to measure an allocation
+<h4><a id="style-value-measure"></a>10.3.12 <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
@@ -5858,9 +5858,10 @@
| minContent
| <a href="#style-value-length"><length></a>
</pre></div>
-</td></tr></tbody></table><p>The semantics of measure values are defined as follows:</p><dl><dt class="label"><code>auto</code></dt><dd><p>As determined by <a href="#semantics-style-automatic-measure-calculation"><b>10.4.5 Automatic Measure Calculation</b></a>.</p></dd><dt class="label"><code>available</code></dt><dd><p>For width in a horizontal writing mode, the numeric value equal to the width of the parent containing block's height less
-the current element's combined border and padding width.</p><p>For height in a horizontal writing mode, the numeric value equal to the height of the parent containing block's height less
-the current element's combined border and padding height.</p></dd><dt class="label"><code>fitContent</code></dt><dd><p>A numeric value equal to the maximum of the values of (1) <code>minContent</code> and (2) the minimum of values of <code>maxContent</code> and <code>available</code>.</p></dd><dt class="label"><code>maxContent</code></dt><dd><p>For width in a horizontal writing mode, the maximum numeric value that encloses all of the element's content such that lines are broken only at
+</td></tr></tbody></table><p>The semantics of measure values are defined as follows:</p><dl><dt class="label"><code>auto</code></dt><dd><p>As determined by <a href="#semantics-style-automatic-measure-calculation"><b>10.4.5 Automatic Measure Calculation</b></a>.</p></dd><dt class="label"><code>available</code></dt><dd><p>For width in a horizontal writing mode, the numeric value equal to the width of the parent containing block's width less
+the current element's combined border and padding width.
+For height in a horizontal writing mode, the numeric value equal to the height of the parent containing block's height less
+the current element's combined border and padding height.</p><p>For vertical writing mode, the sense of width and height is reversed.</p></dd><dt class="label"><code>fitContent</code></dt><dd><p>A numeric value equal to the maximum of the values of (1) <code>minContent</code> and (2) the minimum of values of <code>maxContent</code> and <code>available</code>.</p></dd><dt class="label"><code>maxContent</code></dt><dd><p>For width in a horizontal writing mode, the maximum 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 height in a horizontal writing mode, the maximum 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 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
@@ -7756,17 +7757,17 @@
<a href="http://www.w3.org/wiki/TTML/RoleRegistry">http://www.w3.org/wiki/TTML/RoleRegistry</a>
in order to promote interoperability and collision avoidance.</p></div></div></div><div class="div2">
<h3><a id="metadata-value-expressions"></a>14.3 Metadata Value Expressions</h3><p>Metadata vocabulary may make use of the following expressions:</p><ul><li><p><a href="#metadata-value-item-name"><b>14.3.1 <item-name></b></a></p></li></ul><div class="div3">
-<h4><a id="metadata-value-item-name"></a>14.3.1 <item-name></h4><p>A <item-name> expression is used to specify the name of a metadata item expressed with a
+<h4><a id="metadata-value-item-name"></a>14.3.1 <item-name></h4><p>An <item-name> expression is used to specify the name of a metadata item expressed with a
<a href="#metadata-vocabulary-item">ttm:item</a> element.</p><a id="item-name-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <item-name></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<item-name>
: <a href="#metadata-value-named-item"><named-item></a>
- | <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
- | <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
-</pre></div>
-</td></tr></tbody></table><p>If an item name expression takes the form of an <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>,
-then it must express an absolute URI.</p><p>All values of <item-name> that do not take the form of (1) an absolute URI or (2) a token that has the prefix <code>x-</code>
-are reserved for future standardization by the W3C.</p></div><div class="div3">
+ | <a href="http://www.w3.org/TR/xmlschema-2/#QName">xsd:QName</a>
+</pre></div>
+</td></tr></tbody></table><p>If an item name expression takes the form of a qualified name (<a href="http://www.w3.org/TR/xmlschema-2/#QName">xsd:QName</a>),
+then the prefix of that qualified name must have been declared in a namespace declaration as specified by <a href="#xmlns10">[XML Namespaces 1.0]</a>.</p><p>All values of <item-name> that do not take the form of qualified name (<a href="http://www.w3.org/TR/xmlschema-2/#QName">xsd:QName</a>)
+are reserved for future standardization by the W3C.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is intended that all item names defined by this specification are unqualified (without a prefix), whereas those defined by
+external specifications are qualified (with a prefix).</p></div></div><div class="div3">
<h4><a id="metadata-value-named-item"></a>14.3.2 <named-item></h4><p>A <named-item> value is one of an enumerated collection of named metadata items associated with a value by
a <a href="#metadata-vocabulary-item"><code>ttm:item</code></a> element.</p><a id="named-item-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <named-item></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -7784,12 +7785,12 @@
| cea708TransformMode
| cea708TransformOrigin
| cea708TransformTimingThreshold
+ | creationCountryOfOrigin
| creationDate
- | creationCountryOfOrigin
+ | creationSystem
| editor
| editorContact
| maximumCharactersPerRow
- | originatingSystem
| originalEpisodeTitle
| originalFileName
| originalProgramTitle
@@ -7822,13 +7823,13 @@
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#positiveInteger">xsd:positiveInteger</a> and is less than 32.</p></dd><dt class="label"><a id="named-item-cea708TransformMode"></a><code>cea708TransformMode</code></dt><dd><p>One of the token values <code>enhanced</code> or <code>preserved</code>.</p></dd><dt class="label"><a id="named-item-cea708TransformOrigin"></a><code>cea708TransformOrigin</code></dt><dd><p>Either the token <code>none</code> or an <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>,
where the latter expresses a CEA-708 transformation source format.</p></dd><dt class="label"><a id="named-item-cea708TransformTimingThreshold"></a><code>cea708TransformTimingThreshold</code></dt><dd><p>A real number that expresses a threshold parameter used to suppress the inclusion of temporary timed states when
transforming amongst a CEA-708 caption service and a <a href="#terms-timed-text-content-document">timed text content document</a>,
-where the value adheres to <a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:float</a>.</p></dd><dt class="label"><a id="named-item-creationDate"></a><code>creationDate</code></dt><dd><p>A date that expresses the creation date of this document, where the value
-adheres to <a href="http://www.w3.org/TR/xmlschema-2/#date">xsd:date</a>.</p></dd><dt class="label"><a id="named-item-creationCountryOfOrigin"></a><code>creationCountryOfOrigin</code></dt><dd><p>A string that expresses a the country or origin code associated with this document, where the value
+where the value adheres to <a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:float</a>.</p></dd><dt class="label"><a id="named-item-creationCountryOfOrigin"></a><code>creationCountryOfOrigin</code></dt><dd><p>A string that expresses a the country or origin code associated with this document, where the value
+adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-creationDate"></a><code>creationDate</code></dt><dd><p>A date that expresses the creation date of this document, where the value
+adheres to <a href="http://www.w3.org/TR/xmlschema-2/#date">xsd:date</a>.</p></dd><dt class="label"><a id="named-item-creationSystem"></a><code>creationSystem</code></dt><dd><p>A free form string expressing the software and version used to create the document, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-editor"></a><code>editor</code></dt><dd><p>A string that expresses the name of one or more editors, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-editorContact"></a><code>editorContact</code></dt><dd><p>A string that expresses the contact details of one or more editors, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-maximumCharactersPerRow"></a><code>maximumCharactersPerRow</code></dt><dd><p>A non-negative integer that expresses the maximum number of characters per row (line) used in this document, where the value
-adheres to <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>.</p></dd><dt class="label"><a id="named-item-originatingSystem"></a><code>originatingSystem</code></dt><dd><p>A free form string expressing the software and version used to create the document, where the value
-adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-originalEpisodeTitle"></a><code>originalEpisodeTitle</code></dt><dd><p>A string that expresses the episode title in the original language, where the value
+adheres to <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>.</p></dd><dt class="label"><a id="named-item-originalEpisodeTitle"></a><code>originalEpisodeTitle</code></dt><dd><p>A string that expresses the episode title in the original language, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-originalFileName"></a><code>originalFileName</code></dt><dd><p>A string that expresses the original file name of a <a href="#terms-data-resource">data resource</a>, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p><p>A <code>originalFileName</code> item may specified as a descendant element of a <a href="#embedded-content-vocabulary-data">data</a> element
in order to associate the <a href="#terms-data-resource">data resource</a> represented by that <a href="#embedded-content-vocabulary-data">data</a> element
@@ -9677,7 +9678,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="d3e35235"></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="d3e35237"></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
@@ -9734,7 +9735,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="d3e35752"></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="d3e35754"></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
@@ -9826,9 +9827,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="d3e36745"></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="d3e36747"></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="d3e36909"></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="d3e36911"></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">