--- a/ttml2/spec/ttml2.html Mon Nov 03 10:46:10 2014 +0800
+++ b/ttml2/spec/ttml2.html Mon Nov 03 10:46:23 2014 +0800
@@ -83,9 +83,9 @@
.obsoleted { background-color: #f26d7d }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2014/10/04 20:05:40 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2014/11/03 02:46:10 $<div id="revisions"></div><div class="head">
<h1><a id="title"></a>Timed Text Markup Language 2 (TTML2)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/10/04 20:05:40 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/11/03 02:46:10 $ @@ @@@@ @@@@</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>
@@ -113,14 +113,16 @@
2.2 <a href="#terms">Terminology</a><br>
2.3 <a href="#conventions">Documentation Conventions</a><br>
3 <a href="#conformance">Conformance</a><br>
- 3.1 <a href="#conformance-content">Content Conformance</a><br>
+ 3.1 <a href="#conformance-content">Document Conformance</a><br>
3.2 <a href="#conformance-processor">Processor Conformance</a><br>
3.2.1 <a href="#conformance-generic-processor">Generic Processor Conformance</a><br>
3.2.2 <a href="#conformance-transformation-processor">Transformation Processor Conformance</a><br>
3.2.3 <a href="#conformance-presentation-processor">Presentation Processor Conformance</a><br>
3.3 <a href="#claims">Claims</a><br>
4 <a href="#doctypes">Document Types</a><br>
- 4.1 <a href="#ttml-content-doctype">TTML Content</a><br>
+ 4.1 <a href="#ttml-content-doctype">TTML Content Document Type</a><br>
+ 4.2 <a href="#ttml-intermediate-doctype">TTML Intermediate Document Type</a><br>
+ 4.3 <a href="#ttml-profile-doctype">TTML Profile Document Type</a><br>
5 <a href="#vocabulary">Vocabulary</a><br>
5.1 <a href="#vocabulary-namespaces">Namespaces</a><br>
5.2 <a href="#vocabulary-profiles">Profiles</a><br>
@@ -312,7 +314,7 @@
B <a href="#schemas">Schemas</a><br>
B.1 <a href="#ttml-schema-rnc">Relax NG Compact (RNC) Schema</a><br>
B.2 <a href="#ttml-schema-xsd">XML Schema Definition (XSD) Schema</a><br>
-C <a href="#isd">Intermediate Synchronic Document Syntax</a><br>
+C <a href="#isd">Intermediate Document Syntax</a><br>
C.1 <a href="#isd-vocabulary">ISD Vocabulary</a><br>
C.1.1 <a href="#isd-vocabulary-sequence">isd:sequence</a><br>
C.1.2 <a href="#isd-vocabulary-isd">isd:isd</a><br>
@@ -451,11 +453,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="#d3e27863">Element Derivation</a><br>
- J.2 <a href="#d3e28380">Attribute Derivation</a><br>
+ J.1 <a href="#d3e28106">Element Derivation</a><br>
+ J.2 <a href="#d3e28623">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e29373">Requirements</a><br>
- K.2 <a href="#d3e29537">Guidelines</a><br>
+ K.1 <a href="#d3e29616">Requirements</a><br>
+ K.2 <a href="#d3e29780">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>
@@ -665,7 +667,7 @@
timing information. Content makes direct or indirect references to styling and layout information
and may specify inline overrides to styling.</p></div></div><div class="div1">
<h2><a id="definitions"></a>2 Definitions</h2><div class="div2">
-<h3><a id="acronyms"></a>2.1 Acronyms</h3><table class="acronyms" summary="Glossary List"><tr><td class="label"><b>DFXP</b></td><td class="def"><p>Distribution Format Exchange Profile</p></td></tr><tr><td class="label"><b>ISD</b></td><td class="def"><p>Intermedia Synchronic Document</p></td></tr><tr><td class="label"><b>TT</b></td><td class="def"><p>Timed Text</p></td></tr><tr><td class="label"><b>TTML</b></td><td class="def"><p>Timed Text Markup Language</p></td></tr><tr><td class="label"><b>TTAF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TTWG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
+<h3><a id="acronyms"></a>2.1 Acronyms</h3><table class="acronyms" summary="Glossary List"><tr><td class="label"><b>DFXP</b></td><td class="def"><p>Distribution Format Exchange Profile</p></td></tr><tr><td class="label"><b>ISD</b></td><td class="def"><p>Intermediate Synchronic Document</p></td></tr><tr><td class="label"><b>TT</b></td><td class="def"><p>Timed Text</p></td></tr><tr><td class="label"><b>TTML</b></td><td class="def"><p>Timed Text Markup Language</p></td></tr><tr><td class="label"><b>TTAF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TTWG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
<h3><a id="terms"></a>2.2 Terminology</h3><dl><dt class="label"><a id="terms-abstract-document-instance"></a>[abstract document instance]</dt><dd><p>An instance of an abstract data set as represented by a
<a href="#terms-reduced-xml-infoset">reduced xml infoset</a>.</p></dd><dt class="label"><a id="terms-abstract-document-type"></a>[abstract document type]</dt><dd><p>A set of constraints that defines a class of <em>XML Information
Sets</em> <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label"><a id="terms-anonymous-profile"></a>[anonymous profile]</dt><dd><p>See <a href="#terms-undesignated-profile">undesignated profile</a>.</p></dd><dt class="label"><a id="terms-attribute-information-item"></a>[attribute information item]</dt><dd><p>Each specified or defaulted attribute of an XML document corresponds with an attribute information
@@ -685,10 +687,7 @@
an explicitly specified out-of-line <a href="#layout-vocabulary-region"><code>region</code></a> element, i.e.,
when no <a href="#layout-vocabulary-region"><code>region</code></a> element is specified as a child of
a <a href="#layout-vocabulary-layout"><code>layout</code></a> element.</p></dd><dt class="label"><a id="terms-designated-profile"></a>[designated profile]</dt><dd><p>A <a href="#terms-profile">profile</a> that is associated with a <a href="#terms-profile-designator">profile designator</a> by
-means of a <code>designator</code> attribute or prose text in a specification of profile.</p></dd><dt class="label"><a id="terms-document-instance"></a>[document instance]</dt><dd><p>A concrete realization of a Timed Text Markup Language document, where the concrete form
-is specific to the context of reference. For example, a sequence of bytes that represents an
-XML serialization of a Timed Text document, an internal, parsed representation of such a
-Timed Text document, etc.</p></dd><dt class="label"><a id="terms-document-interchange-context"></a>[document interchange context]</dt><dd><p>The implied context or environment external to a <a href="#terms-content-processor">content processor</a> in
+means of a <code>designator</code> attribute or prose text in a specification of profile.</p></dd><dt class="label"><a id="terms-document-instance"></a>[document instance]</dt><dd><p>A <a href="#terms-timed-text-document-instance">timed text document instance</a>.</p></dd><dt class="label"><a id="terms-document-interchange-context"></a>[document interchange context]</dt><dd><p>The implied context or environment external to a <a href="#terms-content-processor">content processor</a> in
which document interchange occurs, and in which out-of-band protocols or specifications
may define certain behavioral defaults, such as an implied profile.</p></dd><dt class="label"><a id="terms-document-processing-context"></a>[document processing context]</dt><dd><p>The implied context or environment internal to a <a href="#terms-content-processor">content processor</a> in
which document processing occurs, and in which out-of-band protocols or specifications
@@ -725,9 +724,16 @@
or <a href="#style-attribute-origin">tts:origin</a> style attribute on a <a href="#terms-content-element">content element</a>.
There is a one-to-one relation between an inline <a href="#layout-vocabulary-region"><code>region</code></a> element and its
parent <a href="#terms-content-element">content element</a>. An inline region is assigned its parent element's time interval as its active
-time interval. No <code>region</code> attribute makes reference to an inline region.</p></dd><dt class="label"><a id="terms-intermediate-synchronic-document"></a>[intermediate synchronic document]</dt><dd><p>An abstract or concrete representation of the static content, styling, and layout of a source TTML <a href="#terms-document-instance">document instance</a>
-during a non-overlapping temporal interval that intersects with the source document's <a href="#terms-root-temporal-extent">root temporal extent</a>.</p></dd><dt class="label"><a id="terms-intermediate-synchronic-document-sequence"></a>[intermediate synchronic document sequence]</dt><dd><p>An abstract or concrete representation of a sequence of <a href="#terms-intermediate-synchronic-document">intermediate synchronic document</a> instances
-that effectively represent the content, styling, layout, and timing of a source TTML <a href="#terms-document-instance">document instance</a>.</p></dd><dt class="label"><a id="terms-intermediate-synchronic-document-sequence-syntax"></a>[intermediate synchronic document sequence syntax]</dt><dd><p>A formalism for use in the concrete representation of an <a href="#terms-intermediate-synchronic-document-sequence">intermediate synchronic document sequence</a>.</p></dd><dt class="label"><a id="terms-nested-profile"></a>[nested profile]</dt><dd><p>A constituent <a href="#terms-profile">profile</a> of a <a href="#terms-nesting-profile">nesting profile</a>, i.e., one of the
+time interval. No <code>region</code> attribute makes reference to an inline region.</p></dd><dt class="label"><a id="terms-intermediate-synchronic-document"></a>[intermediate synchronic document]</dt><dd><p>A <a href="#terms-timed-text-intermediate-document">timed text intermediate document</a> or a
+<a href="#terms-timed-text-intermediate-document-instance">timed text intermediate document instance</a>, according to the context of use,
+where the root (document) element is an <code>isd:isd</code> element, and which represents a
+non-overlapping temporal interval that intersects with the content, styling, layout, and timing of a source
+<a href="#terms-timed-text-content-document">timed text content document</a>.</p></dd><dt class="label"><a id="terms-intermediate-synchronic-document-sequence"></a>[intermediate synchronic document sequence]</dt><dd><p>A <a href="#terms-timed-text-intermediate-document">timed text intermediate document</a> or a
+<a href="#terms-timed-text-intermediate-document-instance">timed text intermediate document instance</a>, according to the context of use,
+where the root (document) element is an <code>isd:sequence</code> element, and which represents a
+sequence of <a href="#terms-intermediate-synchronic-document">intermediate synchronic document</a> instances
+that effectively represent the content, styling, layout, and timing of a source <a href="#terms-timed-text-content-document">timed text content document</a>.</p></dd><dt class="label"><a id="terms-intermediate-document-syntax"></a>[intermediate document syntax]</dt><dd><p>A formalism for use in the concrete representation of an <a href="#terms-intermediate-synchronic-document-sequence">intermediate synchronic document sequence</a> or
+an <a href="#terms-intermediate-synchronic-document">intermediate synchronic document</a>.</p></dd><dt class="label"><a id="terms-nested-profile"></a>[nested profile]</dt><dd><p>A constituent <a href="#terms-profile">profile</a> of a <a href="#terms-nesting-profile">nesting profile</a>, i.e., one of the
descendant <code>ttp:profile</code> element(s) of a higher level (ancestor) <code>ttp:profile</code> element. A given <code>ttp:profile</code> may serve
as both a <a href="#terms-nested-profile">nested profile</a> and a <a href="#terms-nesting-profile">nesting profile</a>.</p></dd><dt class="label"><a id="terms-nesting-profile"></a>[nesting profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined by making reference to one or more child <code>ttp:profile</code> element(s), wherein a
profile combination method determines how profile specifications from the multiple child <code>ttp:profile</code> element(s) are combined.</p></dd><dt class="label"><a id="terms-non-nesting-profile"></a>[non-nesting profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined without making reference to one or more child <code>ttp:profile</code> element(s); that is,
@@ -751,8 +757,8 @@
<a href="#terms-out-of-line-region">out-of-line region</a> is specified explicitly.</p></dd><dt class="label"><a id="terms-presentation-processor"></a>[presentation processor]</dt><dd><p>A <a href="#terms-content-processor">content processor</a> which purpose is to layout, format, and render,
i.e., to present, <a href="#terms-timed-text-markup-language">Timed Text Markup Language</a> content by applying the presentation semantics
defined in this specification.</p></dd><dt class="label"><a id="terms-processor"></a>[processor]</dt><dd><p>See <a href="#terms-content-processor">content processor</a>.</p></dd><dt class="label"><a id="terms-processor-profile"></a>[processor profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must or may be implemented (supported) by
-a content processor.</p></dd><dt class="label"><a id="terms-profile"></a>[profile]</dt><dd><p>A <a href="#terms-content-profile">content profile</a> or <a href="#terms-processor-profile">processor profile</a>.</p></dd><dt class="label"><a id="terms-profile-definition-document"></a>[profile definition document]</dt><dd><p>A document that formally specifies a <a href="#terms-profile">profile</a>, where such document is a valid TTML document instance
-which has a root element type of <code>ttp:profile</code>.</p></dd><dt class="label"><a id="terms-profile-designator"></a>[profile designator]</dt><dd><p>An absolute URI used to label or reference an externally defined <a href="#terms-profile">profile</a>, where
+a content processor.</p></dd><dt class="label"><a id="terms-profile"></a>[profile]</dt><dd><p>A <a href="#terms-content-profile">content profile</a> or <a href="#terms-processor-profile">processor profile</a>.</p></dd><dt class="label"><a id="terms-profile-definition-document"></a>[profile definition document]</dt><dd><p>A <a href="#terms-timed-text-profile-document">timed text profile document</a> or a
+<a href="#terms-timed-text-profile-document-instance">timed text profile document instance</a>, according to the context of use.</p></dd><dt class="label"><a id="terms-profile-designator"></a>[profile designator]</dt><dd><p>An absolute URI used to label or reference an externally defined <a href="#terms-profile">profile</a>, where
external refers to being external to a <a href="#terms-document-instance">document instance</a>.</p></dd><dt class="label"><a id="terms-profile-fragment-identifier"></a>[profile fragment identifier]</dt><dd><p>A <a href="#terms-fragment-identifier">fragment identifier</a> used to label or reference an internally defined <a href="#terms-profile">profile</a>, where
internal refers to being internal to a <a href="#terms-document-instance">document instance</a>.</p></dd><dt class="label"><a id="terms-profile-specification"></a>[profile specification]</dt><dd><p>A <a href="#terms-feature-specification">feature specification</a> or an <a href="#terms-extension-specification">extension specification</a>
or the internal state representation thereof.</p></dd><dt class="label"><a id="terms-region"></a>[region]</dt><dd><p>A logical construct that models authorial intention regarding
@@ -777,9 +783,22 @@
otherwise determined by the <a href="#terms-document-processing-context">document processing context</a>.</p></dd><dt class="label"><a id="terms-temporally-active"></a>[temporally active]</dt><dd><p>A syntactic or semantic feature, e.g., an element or the presentation of an element, is
<em>temporally active</em> when the current time of selected time base intersects with the
active time interval of the feature.</p></dd><dt class="label"><a id="terms-temporally-active-region"></a>[temporally active region]</dt><dd><p>A <a href="#terms-region">region</a> that is <a href="#terms-temporally-active">temporally active</a>.</p></dd><dt class="label"><a id="terms-timed-text"></a>[timed text]</dt><dd><p>Textual information that is intrinsically or extrinsically
-associated with timing information.</p></dd><dt class="label"><a id="terms-timed-text-markup-language"></a>[timed text markup language]</dt><dd><p>A content type that represents timed text media for the purpose of
-interchange among authoring systems.</p></dd><dt class="label"><a id="terms-timed-text-authoring-system"></a>[timed text authoring system]</dt><dd><p>A content authoring system capable of importing and exporting
-Timed Text Markup Language content.</p></dd><dt class="label"><a id="terms-top-level-profile"></a>[top-level profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined by a <code>ttp:profile</code> element that appears as a child
+associated with timing information.</p></dd><dt class="label"><a id="terms-timed-text-authoring-system"></a>[timed text authoring system]</dt><dd><p>A content authoring system capable of importing and exporting
+Timed Text Markup Language content.</p></dd><dt class="label"><a id="terms-timed-text-content-document"></a>[timed text content document]</dt><dd><p>An abstract document that is purported or confirmed to be a
+<a href="#terms-valid-abstract-document-instance">valid abstract document instance</a> of
+the <a href="#ttml-content-doctype">TTML Content Document Type</a>.</p></dd><dt class="label"><a id="terms-timed-text-content-document-instance"></a>[timed text content document instance]</dt><dd><p>A concrete realization of a <a href="#terms-timed-text-content-document">timed text content document</a>,
+about which see <a href="#concrete-encoding"><b>M Concrete Encoding</b></a>.</p></dd><dt class="label"><a id="terms-timed-text-document-instance"></a>[timed text document instance]</dt><dd><p>A concrete realization of a
+<a href="#terms-timed-text-markup-language-document">timed text markup language document</a>,
+where the concrete form is specific to the context of reference.
+Also referred to as a <a href="#terms-document-instance">TTML document instance</a>
+or simply <a href="#terms-document-instance">document instance</a>.</p></dd><dt class="label"><a id="terms-timed-text-intermediate-document"></a>[timed text intermediate document]</dt><dd><p>An abstract document that is purported or confirmed to be a
+<a href="#terms-valid-abstract-document-instance">valid abstract document instance</a> of
+the <a href="#ttml-intermediate-doctype">TTML Intermediate Document Type</a>.</p></dd><dt class="label"><a id="terms-timed-text-intermediate-document-instance"></a>[timed text intermediate document instance]</dt><dd><p>A concrete realization of a <a href="#terms-timed-text-intermediate-document">timed text intermediate document</a>,
+about which see <a href="#concrete-encoding"><b>M Concrete Encoding</b></a>.</p></dd><dt class="label"><a id="terms-timed-text-markup-language"></a>[timed text markup language]</dt><dd><p>A content type that represents timed text content, intermediate representations of this content, or profiles of this content or content processors.</p></dd><dt class="label"><a id="terms-timed-text-markup-language-document"></a>[timed text markup language document]</dt><dd><p>An abstract document that is purported or confirmed to be a
+<a href="#terms-valid-abstract-document-instance">valid abstract document instance</a>.</p></dd><dt class="label"><a id="terms-timed-text-profile-document"></a>[timed text profile document]</dt><dd><p>An abstract document that is purported or confirmed to be a
+<a href="#terms-valid-abstract-document-instance">valid abstract document instance</a> of
+the <a href="#ttml-profile-doctype">TTML Profile Document Type</a>.</p></dd><dt class="label"><a id="terms-timed-text-profile-document-instance"></a>[timed text profile document instance]</dt><dd><p>A concrete realization of a <a href="#terms-timed-text-profile-document">timed text profile document</a>,
+about which see <a href="#concrete-encoding"><b>M Concrete Encoding</b></a>.</p></dd><dt class="label"><a id="terms-top-level-profile"></a>[top-level profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined by a <code>ttp:profile</code> element that appears as a child
of the <code>head</code> element.</p></dd><dt class="label"><a id="terms-transformation-processor"></a>[transformation processor]</dt><dd><p>A <a href="#terms-content-processor">content processor</a> which purpose is to transform or otherwise rewrite
<a href="#terms-timed-text-markup-language">Timed Text Markup Language</a> content to either <a href="#terms-timed-text-markup-language">Timed Text Markup Language</a>
or to another (arbitrary) content format. An example of the first is a processor that removes
@@ -854,8 +873,8 @@
</pre></div>
</td></tr></tbody></table></div></div><div class="div1">
<h2><a id="conformance"></a>3 Conformance</h2><p>This section specifies the general conformance requirements for
-TTML Content and processors.</p><div class="div2">
-<h3><a id="conformance-content"></a>3.1 Content Conformance</h3><p>A TTML <a href="#terms-document-instance">document instance</a> conforms to this specification if the following criteria are
+TTML documents and processors.</p><div class="div2">
+<h3><a id="conformance-content"></a>3.1 Document Conformance</h3><p>A <a href="#terms-timed-text-document-instance">timed text document instance</a> conforms to this specification if the following criteria are
satisfied:</p><ol class="enumar"><li><p>When transporting a <a href="#terms-document-instance">document instance</a> in a <a href="#terms-document-interchange-context">document interchange context</a> in which a
Media Type <a href="#media-types">[Media Types]</a> identifies the content type of the interchanged <a href="#terms-document-instance">document instance</a>, then the specified media type is
<code>application/ttml+xml</code> in conformance with <a href="#xml-media">[XML Media Types]</a> § 7, with which an optional
@@ -870,7 +889,7 @@
<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The <a href="#terms-reduced-xml-infoset">reduced xml infoset</a> that corresponds to the <a href="#terms-document-instance">document instance</a> is a
<a href="#terms-valid-abstract-document-instance">valid abstract document instance</a> of the associated
<a href="#terms-abstract-document-type">abstract document type</a>.</p></li><li><p>The <a href="#terms-reduced-xml-infoset">reduced xml infoset</a> satisfies all additional mandatory syntactic and
-semantic constraints defined by this specification. In addition, this Infoset
+semantic constraints defined by this specification. In addition, this infoset
should satisfy the web content accessibility guidelines specified by
<a href="#wcag">[WCAG]</a>.</p></li></ol></div><div class="div2">
<h3><a id="conformance-processor"></a>3.2 Processor Conformance</h3><div class="div3">
@@ -926,7 +945,7 @@
<a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>. In addition, it must specify a
<code>ttp:version</code> attribute on its root <code>tt</code> element if it requires
support for a <a href="#terms-feature">feature</a> not defined by <a href="#ttml1">[TTML1]</a>.</p></div></div><div class="div1">
-<h2><a id="doctypes"></a>4 Document Types</h2><p>This section defines the following TTML <em>Abstract Document Types</em>:</p><ul><li><p><a href="#ttml-content-doctype"><b>4.1 TTML Content</b></a></p></li></ul><p>Each <a href="#terms-abstract-document-type">abstract document type</a> consists of the following constraints:</p><ul><li><p>a non-empty collection of element types, where each element type consists of a name,
+<h2><a id="doctypes"></a>4 Document Types</h2><p>This section defines the following TTML <em>Abstract Document Types</em>:</p><ul><li><p><a href="#ttml-content-doctype"><b>4.1 TTML Content Document Type</b></a></p></li><li><p><a href="#ttml-intermediate-doctype"><b>4.2 TTML Intermediate Document Type</b></a></p></li><li><p><a href="#ttml-profile-doctype"><b>4.3 TTML Profile Document Type</b></a></p></li></ul><p>Each <a href="#terms-abstract-document-type">abstract document type</a> consists of the following constraints:</p><ul><li><p>a non-empty collection of element types, where each element type consists of a name,
a (possibly empty) collection of attributes, and a content specification</p></li><li><p>a non-empty collection of element types that may appear as the document element</p></li></ul><p>An <a href="#terms-abstract-document-instance">abstract document instance</a> may be assessed in terms of validity,
and is considered to be a <a href="#terms-valid-abstract-document-instance">valid abstract document instance</a> if it
satisfies the following condition: if after</p><ol class="enumar"><li><p>pruning all element information
@@ -946,12 +965,10 @@
conformant <a href="#terms-document-instance">document instance</a>, a given <a href="#terms-document-instance">document instance</a> may be
constrained by the author or authoring tool to satisfy a more
restrictive definition of validity.</p></div><div class="div2">
-<h3><a id="ttml-content-doctype"></a>4.1 TTML Content</h3><p>TTML Content is an <a href="#terms-abstract-document-type">abstract document type</a> of a profile of the Timed Text Markup Language intended
-to be used for interchange among distribution systems. This document type
-is defined in terms of the
-element and attribute vocabulary
-specified in <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification references two types of schemas that may be used to validate a superset/subset
-of conformant TTML Content <a href="#terms-document-instance">document instances</a>:</p><ul><li><p><a href="#ttml-schema-rnc"><b>B.1 Relax NG Compact (RNC) Schema</b></a></p></li><li><p><a href="#ttml-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a TTML Content <a href="#terms-document-instance">document instance</a> must be a
+<h3><a id="ttml-content-doctype"></a>4.1 TTML Content Document Type</h3><p>The TTML Content Document Type is an <a href="#terms-abstract-document-type">abstract document type</a> of a profile
+of the Timed Text Markup Language intended to be used for interchange among distribution systems. This document type
+is defined in terms of the element and attribute vocabulary specified in <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification references two types of schemas that may be used to validate a superset/subset
+of <a href="#terms-timed-text-content-document-instance">timed text content document instances</a>:</p><ul><li><p><a href="#ttml-schema-rnc"><b>B.1 Relax NG Compact (RNC) Schema</b></a></p></li><li><p><a href="#ttml-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a TTML Content <a href="#terms-document-instance">document instance</a> must be a
<code>tt</code> element, as defined by <a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The schemas referenced by this specification do not validate all syntactic constraints
defined by this specification, and, as such, represent a superset of conformant
TTML Content. In particular, performing validation with one of the above
@@ -967,7 +984,25 @@
formal validity of a <a href="#terms-document-instance">document instance</a> to be based on an <a href="#terms-abstract-document-instance">abstract document instance</a> from
which all foreign namespace elements and attributes have been removed. Therefore, the
exceptional reporting of this false negative does not impact the formal assessment
-of <a href="#terms-document-instance">document instance</a> validity.</p></div></div></div><div class="div1">
+of <a href="#terms-document-instance">document instance</a> validity.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A conforming <a href="#conformance-generic-processor">Generic Processor</a> is required to support the ingestion and processing
+of a <a href="#terms-timed-text-content-document">timed text content document</a>.</p></div></div><div class="div2">
+<h3><a id="ttml-intermediate-doctype"></a>4.2 TTML Intermediate Document Type</h3><p>The TTML Intermediate Document Type is an <a href="#terms-abstract-document-type">abstract document type</a> intended
+to be used to represent the content of a
+<a href="#terms-timed-text-content-document">timed text content document</a>
+in such a manner that all discrete animation, styling, and timing information is denoted in
+a non-hierarchical (flat), temporally linear manner. This document type is defined in terms of the element and attribute vocabulary
+specified in <a href="#isd"><b>C Intermediate Document Syntax</b></a> and <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification references two types of schemas that may be used to validate
+<a href="#terms-timed-text-intermediate-document-instance">timed text intermediate document instances</a>:</p><ul><li><p><a href="#ttml-schema-rnc"><b>B.1 Relax NG Compact (RNC) Schema</b></a></p></li><li><p><a href="#ttml-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a TTML Intermediate Synchronic <a href="#terms-document-instance">document instance</a> must be an
+<code>isd:sequence</code> or <code>isd:isd</code> element, as defined by <a href="#isd"><b>C Intermediate Document Syntax</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A conforming <a href="#conformance-generic-processor">Generic Processor</a> is not required to support the ingestion or processing
+of a <a href="#terms-timed-text-intermediate-document">timed text intermediate document</a>.</p></div></div><div class="div2">
+<h3><a id="ttml-profile-doctype"></a>4.3 TTML Profile Document Type</h3><p>The TTML Profile Document Type is an <a href="#terms-abstract-document-type">abstract document type</a> intended
+to be used for defining and communicating constraints on the support or use of TTML features or extensions. This document type
+is defined in terms of the element and attribute vocabulary specified in <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification references two types of schemas that may be used to validate
+<a href="#terms-timed-text-profile-document-instance">timed text profile document instances</a>:</p><ul><li><p><a href="#ttml-schema-rnc"><b>B.1 Relax NG Compact (RNC) Schema</b></a></p></li><li><p><a href="#ttml-schema-xsd"><b>B.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a TTML Profile <a href="#terms-document-instance">document instance</a> must be a
+<code>ttp:profile</code> element, as defined by <a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A conforming <a href="#conformance-generic-processor">Generic Processor</a> is recommended, but not required to support the ingestion or processing
+of a <a href="#terms-timed-text-profile-document">timed text profile document</a>. However, a <a href="#terms-content-processor">content processor</a>
+that claims to support the <code>http://www.w3.org/ns/ttml/feature/#profile</code> feature is required to support this (ingestion and processing of
+a <a href="#terms-timed-text-profile-document">timed text profile document</a>).</p></div></div></div><div class="div1">
<h2><a id="vocabulary"></a>5 Vocabulary</h2><p>This section defines the
namespaces, profiles, and vocabulary (as an element and attribute
catalog) of the Timed Text Markup Language (TTML) as follows:</p><ul><li><p><a href="#vocabulary-namespaces"><b>5.1 Namespaces</b></a></p></li><li><p><a href="#vocabulary-profiles"><b>5.2 Profiles</b></a></p></li><li><p><a href="#vocabulary-overview"><b>5.3 Catalog</b></a></p></li></ul><div class="div2">
@@ -3617,7 +3652,7 @@
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</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></p><p>If the value of this attribute is <code>none</code>, then no ruby semantics apply; otherwise, the ruby semantics enumerated by
<a href="#ruby-semantics-mapping-table"><b>Table 8-1 – Ruby Semantics Mapping</b></a> apply.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>none</code>.</p><a id="ruby-semantics-mapping-table"></a><table class="common"><caption>Table 8-1 – Ruby Semantics Mapping</caption><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col span="1"><tbody><tr><th>Category</th><th>tts:ruby</th><th>Annotation <a href="#ruby">[Ruby]</a></th><th>CSS display <a href="#cssruby">[CSS Ruby]</a></th></tr><tr><td>Ruby Container</td><td><code>container</code></td><td><code>ruby</code></td><td><code>ruby</code></td></tr><tr><td>Ruby Base Content</td><td><code>base</code></td><td><code>rb</code></td><td><code>ruby-base</code></td></tr><tr><td>Ruby Text Content</td><td><code>text</code></td><td><code>rt</code></td><td><code>ruby-text</code></td></tr><tr><td>Ruby Base Container</td><td><code>baseContainer</code></td><td><code>rbc</code></td><td><code>ruby-base-container</code></td></tr><tr><td>Ruby Text Container</td><td><code>textContainer</code></td><td><code>rtc</code></td><td><code>ruby-text-container</code></td></tr><tr><td>Ruby Fallback Delimiter</td><td><code>delimiter</code></td><td><code>rp</code></td><td><code>none</code></td></tr></tbody></table><p>When using <code>tts:ruby</code>, the following nesting constraints apply:</p><ul><li><p>if the computed value of <code>tts:ruby</code> is <code>container</code>, then the
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>none</code>.</p><a id="ruby-semantics-mapping-table"></a><table class="common"><caption>Table 8-1 – Ruby Semantics Mapping</caption><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col width="25%" span="1"><col span="1"><tbody><tr><th>Category</th><th>tts:ruby</th><th>Annotation <a href="#ruby">[Ruby]</a></th><th>CSS display <a href="#cssruby">[CSS Ruby]</a></th></tr><tr><td>Ruby Container</td><td><code>container</code></td><td><code>ruby</code></td><td><code>ruby</code></td></tr><tr><td>Ruby Base Content</td><td><code>base</code></td><td><code>rb</code></td><td><code>ruby-base</code></td></tr><tr><td>Ruby Text Content</td><td><code>text</code></td><td><code>rt</code></td><td><code>ruby-text</code></td></tr><tr><td>Ruby Base Container</td><td><code>baseContainer</code></td><td><code>rbc</code></td><td><code>ruby-base-container</code></td></tr><tr><td>Ruby Text Container</td><td><code>textContainer</code></td><td><code>rtc</code></td><td><code>ruby-text-container</code></td></tr><tr><td>Ruby Fallback Delimiter</td><td><code>delimiter</code></td><td><code>rp</code></td><td><code>none</code> | <code>inline</code></td></tr></tbody></table><p>When using <code>tts:ruby</code>, the following nesting constraints apply:</p><ul><li><p>if the computed value of <code>tts:ruby</code> is <code>container</code>, then the
computed value of <code>tts:ruby</code> of all ancestor elements is <code>none</code>;</p></li><li><p>if the computed value of <code>tts:ruby</code> is <code>container</code>, then the
computed value of <code>tts:ruby</code> of its first child element is <code>baseContainer</code>
or <code>base</code>;</p></li><li><p>if the computed value of <code>tts:ruby</code> is <code>baseContainer</code>, then the
@@ -3649,7 +3684,9 @@
computed value of <code>tts:ruby</code> of exactly one sibling is <code>delimiter</code>;</p></li><li><p>if the computed value of <code>tts:ruby</code> is <code>delimiter</code>, then the
computed value of <code>tts:ruby</code> of no descendant element is not <code>none</code>;</p></li></ul><p>A validating processor must treat a violation of any of the above constraints as an error.
For the purpose of presentation processing, the violation of any of these constraints should result in fallback (inline)
-presentation of ruby text annotations, where fallback annotation presentation is considered to be implementation dependent.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above listed constraints are intended to be interpreted as specifying the following nesting model:</p><div class="exampleInner"><pre>
+presentation of ruby text annotations.</p><p>When performing normal presentation processing of ruby text annotations, delimiter content must not generate any
+inline areas. When performing fallback presentation of ruby, both delimiter and non-delimiter ruby (base and text) content
+must generate normal inline areas.</p><p>If a presentation processor does not support ruby presentation, then it must perform fallback ruby presentaton.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above listed constraints are intended to be interpreted as specifying the following nesting model:</p><div class="exampleInner"><pre>
container
: base text
| base delimiter text delimiter
@@ -6335,15 +6372,16 @@
Archive</a>. This schema is to be considered non-normative for the purpose of defining the validity
of Timed Text Markup Language content as defined by this specification.
In particular, the formal validity of TTML Content
-is defined by <a href="#conformance-content"><b>3.1 Content Conformance</b></a>.</p></div><div class="div2">
+is defined by <a href="#conformance-content"><b>3.1 Document Conformance</b></a>.</p></div><div class="div2">
<h3><a id="ttml-schema-xsd"></a>B.2 XML Schema Definition (XSD) Schema</h3><p>A W3C XML Schema Definition (XSD) <a href="#xsd-1">[XML Schema Part 1]</a> based schema
for TTML Content is available at <a href="xsd/schema.zip">ZIP
Archive</a>. This schema is to be considered non-normative for the purpose of defining the validity
of Timed Text Markup Language content as defined by this specification.
In particular, the formal validity of TTML Content
-is defined by <a href="#conformance-content"><b>3.1 Content Conformance</b></a>.</p></div></div><div class="div1">
-<h2><a id="isd"></a>C Intermediate Synchronic Document Syntax</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the syntactic elements and structure of a TTML Intermediate Synchronic Document (ISD) Sequence and its
-constituent TTML Intermediate Synchronic Document (ISD) instances. An ISD instance may be represented as a standalone document instance or
+is defined by <a href="#conformance-content"><b>3.1 Document Conformance</b></a>.</p></div></div><div class="div1">
+<h2><a id="isd"></a>C Intermediate Document Syntax</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the syntactic elements and structure of a
+<a href="#terms-timed-text-intermediate-document">timed text intermediate document</a>.
+An ISD instance may be represented as a standalone document instance or
in a collection represented as an ISD Sequence instance.</p><p>All ISD related vocabulary is defined in the TTML ISD Namespace, defined here as <code>http://www.w3.org/ns/ttml#isd</code>,
where the recommended prefix is <code>isd</code>.</p><p>A TTML <a href="#terms-intermediate-synchronic-document">Intermediate Synchronic Document</a>, in short, an <em>ISD</em> or <em>ISD instance</em>,
represents a discrete, temporally non-overlapping interval, an <em>ISD interval</em>,
@@ -8116,7 +8154,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="d3e27863"></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="d3e28106"></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
@@ -8173,7 +8211,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="d3e28380"></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="d3e28623"></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
@@ -8265,9 +8303,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="d3e29373"></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="d3e29616"></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="d3e29537"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e29780"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>J Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
TTML <a href="#doctypes">Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">