Mercurial > hg > ttml / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset
Merge
authorpal@sandflow.org
Wed, 16 Jul 2014 21:12:06 -0700
changeset 655 f05f203d7c11
parent 654 fb65791a33af (current diff)
parent 650 0332a03866a6 (diff)
child 658 903bb9a370cb
child 662 f82b25ca25b7
Merge 
--- a/ttml2/spec/ttml2-changes.html	Wed Jul 16 21:09:07 2014 -0700
+++ b/ttml2/spec/ttml2-changes.html	Wed Jul 16 21:12:06 2014 -0700
@@ -227,13 +227,13 @@
 <span class="strong">Editorial Changes</span>
 
 * In 2.2, add definitions: "anonymous profile", "baseline profile",
-  "content profile", "default profile", "designated profile", "enclosing document
-  instance", "extension specification", "feature specification",
-  "fragment identifier", "implied inline region", "inline animation",
-  "inline region", "nested profile", "nesting profile", "non-nesting profile",
-  "out-of-line animation", "out-of-line region", "profile",
-  "profile designator", "profile fragment identifier", "profile specification",
-  "top-level profile", "undesignated profile".
+  "content profile", "default processor profile", "designated profile",
+  "enclosing document instance", "extension specification",
+  "feature specification", "fragment identifier", "implied inline region",
+  "inline animation", "inline region", "nested profile", "nesting profile",
+  "non-nesting profile", "out-of-line animation", "out-of-line region",
+  "profile", "profile designator", "profile fragment identifier",
+  "profile specification", "top-level profile", "undesignated profile".
 
 * In 2.2, refine definition of "out-of-line region" to better account for
   default region implication.
--- a/ttml2/spec/ttml2.html	Wed Jul 16 21:09:07 2014 -0700
+++ b/ttml2/spec/ttml2.html	Wed Jul 16 21:12:06 2014 -0700
@@ -82,9 +82,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/07/10 15:05:04 $<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/07/17 02:02:18 $<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/07/10 15:05:04 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/07/17 02:02:18 $ @@ @@@@ @@@@</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>
@@ -437,11 +437,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>
-&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e25166">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e25683">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e25237">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e25754">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e26676">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e26840">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e26747">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e26911">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>
@@ -663,7 +663,11 @@
 axis, where the column and row counts are determined by the <code>ttp:cellResolution</code> parameter attribute.</p></dd><dt class="label"><a id="terms-content-element"></a>[content element]</dt><dd><p>Any of the element types defined by the <a href="#element-vocab-type-content">Content Module</a>.</p></dd><dt class="label"><a id="terms-content-processor"></a>[content processor]</dt><dd><p>A processing system capable of importing (receiving) Timed Text Markup Language
 content for the purpose of transforming, presenting, or otherwise processing the content.</p></dd><dt class="label"><a id="terms-content-profile"></a>[content profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must not, must, or may be employed by
 Timed Text Markup Language content.</p><p></p></dd><dt class="label"><a id="terms-content-region"></a>[content region]</dt><dd><p>A logical region into which rendered content is placed when modeling or
-performing presentation processing.</p></dd><dt class="label"><a id="terms-default-region"></a>[default region]</dt><dd><p>A default <a href="#terms-out-of-line-region">out-of-line region</a> that is implied in the absence of
+performing presentation processing.</p></dd><dt class="label"><a id="terms-default-profile"></a>[default processor profile]</dt><dd><p>A default <a href="#terms-processor-profile">processor profile</a> used to compute an
+<a href="#terms-effective-processor-profile">effective processor profile</a> in the absence of a declared or inferred
+<a href="#terms-processor-profile">processor profile</a>, where this default processor profile is determined by
+the <a href="#semantics-procedure-construct-default-processor-profile"><span class="strong">construct default processor profile</span></a>
+procedure.</p></dd><dt class="label"><a id="terms-default-region"></a>[default region]</dt><dd><p>A default <a href="#terms-out-of-line-region">out-of-line region</a> that is implied in the absence of
 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
@@ -984,7 +988,8 @@
 processors to avoid processing content that cannot be processed in a manner that meets the requirements of the content author.</p><p>Processor profiles are declared by using (1) the <a href="#parameter-attribute-processorProfiles"><code>ttp:processorProfiles</code></a>
 attribute on the root <code>tt</code> element, (2) one or more <a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a>
 elements of type <code>processor</code>, or (3) a combination of these two mechanisms.
-If not declared, a processor profile is inferred from content profile or from a default processor profile.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not a requirement on a conformant <a href="#terms-document-instance">document instance</a> that a processor profile be internally
+If not declared, a processor profile is inferred from a declared content profile or from a
+<a href="#terms-default-profile">default profile</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not a requirement on a conformant <a href="#terms-document-instance">document instance</a> that a processor profile be internally
 declared by use of a <a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a> element or internally referenced by a
 <a href="#parameter-attribute-processorProfiles"><code>ttp:processorProfiles</code></a> attribute. More specifically, it is
 permitted that the <a href="#terms-document-interchange-context">document
@@ -1143,18 +1148,33 @@
 <a href="#terms-processor-profile">processor profile</a> or with a <a href="#terms-content-profile">content profile</a>
 from which a <a href="#terms-processor-profile">processor profile</a> can be inferred, then the
 <a href="#terms-default-processor-profile">default processor profile</a> is that <a href="#terms-processor-profile">processor profile</a>;</p></li><li><p>otherwise, if the <a href="#terms-content-processor">content processor</a> is primarily characterized as a
-<a href="#terms-presentation-processor">presentation processor</a>, then:</p><ol class="enumla"><li><p>if the <a href="#parameter-attribute-version"><code>ttp:version</code></a> is not specified on the root <code>tt</code> element or
-if its computed value of this parameter is <code>1</code> (one), then the <a href="#terms-default-processor-profile">default processor profile</a> is
+<a href="#terms-presentation-processor">presentation processor</a>, then:</p><ol class="enumla"><li><p>if the <a href="#parameter-attribute-version"><code>ttp:version</code></a> attribute is not specified on the root <code>tt</code> element or
+if the computed value of its parameter property is <code>1</code> (one), then the <a href="#terms-default-processor-profile">default processor profile</a> is
 the <a href="#semantics-profile-state-profile">profile</a> constructed by interning the DFXP Presentation profile
-(<code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>);</p></li><li><p>otherwise, the <a href="#terms-default-processor-profile">default processor profile</a> is
+(<code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>);</p></li><li><p>otherwise,
+if the computed value of the <a href="#parameter-attribute-version"><code>ttp:version</code></a> parameter property is <code>2</code> (two),
+the <a href="#terms-default-processor-profile">default processor profile</a> is
 the <a href="#semantics-profile-state-profile">profile</a> constructed by interning the TTML2 Presentation profile
-(<code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>);</p></li></ol></li><li><p>otherwise, if the <a href="#terms-content-processor">content processor</a> is primarily characterized as a
-<a href="#terms-transformation-processor">transformation processor</a>, then:</p><ol class="enumla"><li><p>if the <a href="#parameter-attribute-version"><code>ttp:version</code></a> is not specified on the root <code>tt</code> element or
-if its computed value of this parameter is <code>1</code> (one), then the <a href="#terms-default-processor-profile">default processor profile</a> is
+(<code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>);</p></li><li><p>otherwise,
+the <a href="#terms-default-processor-profile">default processor profile</a> is
+the <a href="#semantics-profile-state-profile">profile</a> constructed by interning a TTML presentation profile
+associated with the computed value of <a href="#parameter-attribute-version"><code>ttp:version</code></a>,
+if one is known, or, if not known, then the most recently defined presentation profile;</p></li></ol></li><li><p>otherwise, if the <a href="#terms-content-processor">content processor</a> is primarily characterized as a
+<a href="#terms-transformation-processor">transformation processor</a>, then:</p><ol class="enumla"><li><p>if the <a href="#parameter-attribute-version"><code>ttp:version</code></a> attribute is not specified on the root <code>tt</code> element or
+if the computed value of its parameter property is <code>1</code> (one), then the <a href="#terms-default-processor-profile">default processor profile</a> is
 the <a href="#semantics-profile-state-profile">profile</a> constructed by interning the DFXP Transformation profile
-(<code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code>);</p></li><li><p>otherwise, the <a href="#terms-default-processor-profile">default processor profile</a> is
+(<code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code>);</p></li><li><p>otherwise,
+if the computed value of the <a href="#parameter-attribute-version"><code>ttp:version</code></a> parameter property is <code>2</code> (two),
+the <a href="#terms-default-processor-profile">default processor profile</a> is
 the <a href="#semantics-profile-state-profile">profile</a> constructed by interning the TTML2 Transformation profile
-(<code>http://www.w3.org/ns/ttml/profile/ttml2-transformation</code>);</p></li></ol></li></ol></dd></dl></div></div></div><div class="div2">
+(<code>http://www.w3.org/ns/ttml/profile/ttml2-transformation</code>);</p></li><li><p>otherwise,
+the <a href="#terms-default-processor-profile">default processor profile</a> is
+the <a href="#semantics-profile-state-profile">profile</a> constructed by interning a TTML transformation profile
+associated with the computed value of <a href="#parameter-attribute-version"><code>ttp:version</code></a>,
+if one is known, or, if not known, then the most recently defined TTML transformation profile;</p></li></ol></li></ol><div class="note"><p class="prefix"><b>Note:</b></p><p>A <a href="#terms-content-processor">content processor</a> intended to be used with
+one or more distinct versions of TTML greater than version 2 (TTML2) may choose a
+<a href="#terms-default-processor-profile">default processor profile</a> based upon
+a future version of a TTML presentation or transformation profile.</p></div></dd></dl></div></div></div><div class="div2">
 <h3><a id="vocabulary-overview"></a>5.3 Catalog</h3><p>The vocabulary of the Timed Text Markup Language (TTML) is
 defined in the following major catalogs (divisions of vocabulary):</p><ul><li><p><a href="#core-vocabulary-overview"><b>5.3.1 Core Catalog</b></a></p></li><li><p><a href="#extension-vocabulary-overview"><b>5.3.2 Extension Catalog</b></a></p></li></ul><p>The core catalog defines the baseline, core vocabulary of TTML,
 and, in particular, the vocabulary of TTML Content. The extension catalog
@@ -7633,7 +7653,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="d3e25166"></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="d3e25237"></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
@@ -7690,7 +7710,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 targetted elements.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e25683"></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="d3e25754"></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
@@ -7782,9 +7802,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>&nbsp;<a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e26676"></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="d3e26747"></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="d3e26840"></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="d3e26911"></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">
--- a/ttml2/spec/ttml2.xml	Wed Jul 16 21:09:07 2014 -0700
+++ b/ttml2/spec/ttml2.xml	Wed Jul 16 21:12:06 2014 -0700
@@ -608,6 +608,16 @@
 performing presentation processing.</p>
 </def>
 </gitem>
+<gitem id="terms-default-profile">
+<label>[default processor profile]</label>
+<def>
+<p>A default <loc href="#terms-processor-profile">processor profile</loc> used to compute an
+<loc href="#terms-effective-processor-profile">effective processor profile</loc> in the absence of a declared or inferred
+<loc href="#terms-processor-profile">processor profile</loc>, where this default processor profile is determined by
+the <loc href="#semantics-procedure-construct-default-processor-profile"><phrase role="strong">construct default processor profile</phrase></loc>
+procedure.</p>
+</def>
+</gitem>
 <gitem id="terms-default-region">
 <label>[default region]</label>
 <def>
@@ -1493,7 +1503,8 @@
 <p>Processor profiles are declared by using (1) the <loc href="#parameter-attribute-processorProfiles"><att>ttp:processorProfiles</att></loc>
 attribute on the root <el>tt</el> element, (2) one or more <loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
 elements of type <code>processor</code>, or (3) a combination of these two mechanisms.
-If not declared, a processor profile is inferred from content profile or from a default processor profile.</p>
+If not declared, a processor profile is inferred from a declared content profile or from a
+<loc href="#terms-default-profile">default profile</loc>.</p>
 
 <note role="elaboration">
 <p>It is not a requirement on a conformant <loc href="#terms-document-instance">document instance</loc> that a processor profile be internally
@@ -2044,16 +2055,25 @@
 <loc href="#terms-presentation-processor">presentation processor</loc>, then:</p>
 <olist>
 <item>
-<p>if the <loc href="#parameter-attribute-version"><att>ttp:version</att></loc> is not specified on the root <el>tt</el> element or
-if its computed value of this parameter is <code>1</code> (one), then the <loc href="#terms-default-processor-profile">default processor profile</loc> is
+<p>if the <loc href="#parameter-attribute-version"><att>ttp:version</att></loc> attribute is not specified on the root <el>tt</el> element or
+if the computed value of its parameter property is <code>1</code> (one), then the <loc href="#terms-default-processor-profile">default processor profile</loc> is
 the <loc href="#semantics-profile-state-profile">profile</loc> constructed by interning the DFXP Presentation profile
 (<code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>);</p>
 </item>
 <item>
-<p>otherwise, the <loc href="#terms-default-processor-profile">default processor profile</loc> is
+<p>otherwise,
+if the computed value of the <loc href="#parameter-attribute-version"><att>ttp:version</att></loc> parameter property is <code>2</code> (two),
+the <loc href="#terms-default-processor-profile">default processor profile</loc> is
 the <loc href="#semantics-profile-state-profile">profile</loc> constructed by interning the TTML2 Presentation profile
 (<code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>);</p>
 </item>
+<item>
+<p>otherwise,
+the <loc href="#terms-default-processor-profile">default processor profile</loc> is
+the <loc href="#semantics-profile-state-profile">profile</loc> constructed by interning a TTML presentation profile
+associated with the computed value of <loc href="#parameter-attribute-version"><att>ttp:version</att></loc>,
+if one is known, or, if not known, then the most recently defined presentation profile;</p>
+</item>
 </olist>
 </item>
 
@@ -2062,19 +2082,34 @@
 <loc href="#terms-transformation-processor">transformation processor</loc>, then:</p>
 <olist>
 <item>
-<p>if the <loc href="#parameter-attribute-version"><att>ttp:version</att></loc> is not specified on the root <el>tt</el> element or
-if its computed value of this parameter is <code>1</code> (one), then the <loc href="#terms-default-processor-profile">default processor profile</loc> is
+<p>if the <loc href="#parameter-attribute-version"><att>ttp:version</att></loc> attribute is not specified on the root <el>tt</el> element or
+if the computed value of its parameter property is <code>1</code> (one), then the <loc href="#terms-default-processor-profile">default processor profile</loc> is
 the <loc href="#semantics-profile-state-profile">profile</loc> constructed by interning the DFXP Transformation profile
 (<code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code>);</p>
 </item>
 <item>
-<p>otherwise, the <loc href="#terms-default-processor-profile">default processor profile</loc> is
+<p>otherwise,
+if the computed value of the <loc href="#parameter-attribute-version"><att>ttp:version</att></loc> parameter property is <code>2</code> (two),
+the <loc href="#terms-default-processor-profile">default processor profile</loc> is
 the <loc href="#semantics-profile-state-profile">profile</loc> constructed by interning the TTML2 Transformation profile
 (<code>http://www.w3.org/ns/ttml/profile/ttml2-transformation</code>);</p>
 </item>
+<item>
+<p>otherwise,
+the <loc href="#terms-default-processor-profile">default processor profile</loc> is
+the <loc href="#semantics-profile-state-profile">profile</loc> constructed by interning a TTML transformation profile
+associated with the computed value of <loc href="#parameter-attribute-version"><att>ttp:version</att></loc>,
+if one is known, or, if not known, then the most recently defined TTML transformation profile;</p>
+</item>
 </olist>
 </item>
 </olist>
+<note role="explanation">
+<p>A <loc href="#terms-content-processor">content processor</loc> intended to be used with
+one or more distinct versions of TTML greater than version 2 (TTML2) may choose a
+<loc href="#terms-default-processor-profile">default processor profile</loc> based upon
+a future version of a TTML presentation or transformation profile.</p>
+</note>
 </def>
 </gitem>
 </glist>
ttml

Hosted by W3C Systems Team, please report bugs to sysreq@w3.org