--- a/ttml10/spec/acknowledgements-current.txt Wed May 01 22:59:16 2013 -0700
+++ b/ttml10/spec/acknowledgements-current.txt Thu May 02 21:36:21 2013 -0700
@@ -39,4 +39,5 @@
Patrick Schmitz,
David Singer,
Craig Smithpeters,
+Andreas Tai,
and Mohamed Zergaoui.
--- a/ttml10/spec/acknowledgements.xml Wed May 01 22:59:16 2013 -0700
+++ b/ttml10/spec/acknowledgements.xml Thu May 02 21:36:21 2013 -0700
@@ -12,4 +12,5 @@
and example images of style properties), Sean Hayes (advanced profile
concepts, including applicative timing), Eric Hodge (timing),
Thierry Michel (metadata), and Dave Singer (animation, scrolling).</p>
+<p>The Working Group dedicates this specification to our colleague David Kirby.</p>
</inform-div1>
--- a/ttml10/spec/ttaf1-dfxp.html Wed May 01 22:59:16 2013 -0700
+++ b/ttml10/spec/ttaf1-dfxp.html Thu May 02 21:36:21 2013 -0700
@@ -86,9 +86,9 @@
.diff-del { color: red; text-decoration: line-through; background-color: #99FF99; }
.diff-chg { background-color: #99FF99; }
q.diff-off {}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"/></head><body>Last Modified: $Date: 2013/05/02 05:57:02 $<div id="revisions"/><div class="head">
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"/></head><body>Last Modified: $Date$<div id="revisions"/><div class="head">
<h1><a name="title" id="title"/>Timed Text Markup Language (TTML) 1.0 (Second Edition)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"/>Editors' copy $Date: 2013/05/02 05:57:02 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a name="w3c-doctype" id="w3c-doctype"/>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ttaf1-dfxp.html">ttaf1-dfxp.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10/spec/ttaf1-dfxp.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>
@@ -266,7 +266,7 @@
B <a href="#schemas">Schemas</a><br/>
B.1 <a href="#dfxp-schema-rnc">Relax NG Schema</a><br/>
B.2 <a href="#dfxp-schema-xsd">XML Schema Definition (XSD) Schema</a><br/>
-C <a href="#media-type-registration">Media Type Registration</a><br/>
+C <a href="#media-types-registration">Media Type Registration</a><br/>
D <a href="#features">Features</a><br/>
D.1 <a href="#feature-designations">Feature Designations</a><br/>
D.1.1 <a href="#feature-animation">#animation</a><br/>
@@ -394,11 +394,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="#d3e17360">Element Derivation</a><br/>
- J.2 <a href="#d3e17839">Attribute Derivation</a><br/>
+ J.1 <a href="#d3e17370">Element Derivation</a><br/>
+ J.2 <a href="#d3e17849">Attribute Derivation</a><br/>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br/>
- K.1 <a href="#d3e18707">Requirements</a><br/>
- K.2 <a href="#d3e18871">Guidelines</a><br/>
+ K.1 <a href="#d3e18717">Requirements</a><br/>
+ K.2 <a href="#d3e18881">Guidelines</a><br/>
L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br/>
M <a href="#concrete-encoding">Concrete Encoding</a> (Non-Normative)<br/>
N <a href="#time-expression-semantics">Time Expression Semantics</a> (Non-Normative)<br/>
@@ -692,8 +692,8 @@
<h2><a name="conformance" id="conformance"/>3 Conformance</h2><p>This section specifies the general conformance requirements for
TTML content and processors.</p><div class="div2">
<h3><a name="conformance-content" id="conformance-content"/>3.1 Content Conformance</h3><p>A TTML document instance conforms to this specification if the following criteria are
-satisfied:</p><ol class="enumar"><li><p>When transporting a document instance in a context in which a MIME
-Media Type <a href="#mime-media">[MIME]</a> identifies the content type of the interchanged document
+satisfied:</p><ol class="enumar"><li><p>When transporting a document instance in a context in which a
+Media Type <a href="#media-types">[Media Types]</a> identifies the content type of the interchanged document
instance, then the specified media type is
<code>application/ttml+xml</code> in conformance with <a href="#rfc3023">[XML Media Types]</a> § 7, with which an optional
<code>profile</code> parameter may appear, the value of which
@@ -1428,9 +1428,9 @@
glyph areas is
coordinated with this grid. Such alignment is possible, but
requires the use of a monospaced font and a font size whose EM square exactly
-matches the cell size.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>When a <a href="#style-value-length"><length></a> expressed in
-cells applies to a dimension parallel to the inline or block progression dimension,
-a cell's dimension in the inline or block progression dimension applies, respectively.
+matches the cell size.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Except when indicated otherwise, when a <a href="#style-value-length"><length></a> expressed in
+cells expresses a dimension parallel to the inline or block progression dimension,
+the cell's dimension in the inline or block progression dimension applies, respectively.
For example, if padding (on all four edges) is specified as 0.1c, the cell resolution
is 20 by 10, and the root container extent is 640 by 480, then, assuming top to bottom,
left to right writing mode, the start and end padding will be 640 / 20 * 0.1 pixels and the
@@ -2910,7 +2910,13 @@
present, then it denotes the outline color; if no <em>color</em> term is
present, the computed value of the <code>tts:color</code> applies. The first
<em>length</em> term denotes the outline thickness and the second length
-term, if present, indicates the blur radius.</p><p>If a specified value of this attribute is not supported,
+term, if present, indicates the blur radius.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When a <a href="#style-value-length"><length></a> expressed in
+cells is used in a <code>tts:textOutline</code> value,
+the cell's dimension in the block progression dimension applies.
+For example, if text outline thickness is specified as 0.1c, the cell resolution
+is 20 by 10, and the root container extent is 640 by 480, then the
+outline thickness will be a nominal 480 / 10 * 0.1 pixels, i.e., 4.8px,
+without taking into account rasterization effects.</p></div><p>If a specified value of this attribute is not supported,
then a presentation processor must interpret the attribute as if the
value <code>none</code> were specified.</p><p>The <code>tts:textOutline</code> style is illustrated by the following
example.</p><table summary="HTML Table" id="style-attribute-textOutline-example-1" class="example"><caption>Example Fragment – Text Outline</caption><tbody><tr><td>
@@ -4796,7 +4802,7 @@
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 name="media-type-registration" id="media-type-registration"/>C Media Type Registration</h2><p><em>This appendix is normative.</em></p><p>This appendix registers a new MIME media type,
+<h2><a name="media-types-registration" id="media-types-registration"/>C Media Type Registration</h2><p><em>This appendix is normative.</em></p><p>This appendix registers a new media type,
"application/ttml+xml" in conformance with
<a href="http://www.ietf.org/rfc/rfc4288.txt">BCP 13</a> and
<a href="http://www.w3.org/2002/06/registering-mediatype.html">W3CRegMedia</a>.
@@ -6187,7 +6193,7 @@
and associated APIs for HTML and XHTML</cite></a>, W3C Candidate Recommendation, 17
December 2012. (See
<a href="http://www.w3.org/TR/2012/CR-html5-20121217//">http://www.w3.org/TR/2012/CR-html5-20121217//</a>.)
-</dd><dt class="label"><a name="mime-media" id="mime-media"/>MIME</dt><dd>Ned Freed and Nathaniel Borenstein,
+</dd><dt class="label"><a name="media-types" id="media-types"/>Media Types</dt><dd>Ned Freed and Nathaniel Borenstein,
<a href="http://www.rfc-editor.org/rfc/rfc2046.txt"><cite>Multipurpose Internet
Mail Extensions (MIME) Part Two: Media Types</cite></a>,
RFC 2046, November 1996, IETF.(See
@@ -6343,7 +6349,7 @@
<h2><a name="derivation" id="derivation"/>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 name="d3e17360" id="d3e17360"/>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
+<h3><a name="d3e17370" id="d3e17370"/>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-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
@@ -6398,7 +6404,7 @@
and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e17839" id="d3e17839"/>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
+<h3><a name="d3e17849" id="d3e17849"/>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-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
@@ -6470,9 +6476,9 @@
<h2><a name="qa" id="qa"/>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 name="d3e18707" id="d3e18707"/>K.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-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 name="d3e18717" id="d3e18717"/>K.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-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/></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/></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/></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/></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/></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/></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/></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/></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/></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/></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/></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>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>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 name="d3e18871" id="d3e18871"/>K.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-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/></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/></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/></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>NO</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/></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/></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/></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>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/></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>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/></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>NO</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/></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/></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/></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/></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/></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/></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/></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>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>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>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/></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 name="d3e18881" id="d3e18881"/>K.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-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/></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/></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/></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>NO</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/></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/></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/></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>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/></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>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/></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>NO</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/></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/></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/></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/></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/></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/></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/></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>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>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>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/></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
<a href="#doctypes">TTML 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">
@@ -6816,10 +6822,11 @@
Patrick Schmitz,
David Singer,
Craig Smithpeters,
+Andreas Tai,
and Mohamed Zergaoui.
</p><p>The editor wishes to especially acknowledge the following contributions
by members: Micheal Dolan (SMPTE time codes, streaming; SMPTE liaison), David
Kirby (introductory example document; SMPTE time codes, descriptive metadata; EBU/AAF liaison), Geoff Freed (styling
and example images of style properties), Sean Hayes (advanced profile
concepts, including applicative timing), Eric Hodge (timing),
-Thierry Michel (metadata), and Dave Singer (animation, scrolling).</p></div></div></body></html>
\ No newline at end of file
+Thierry Michel (metadata), and Dave Singer (animation, scrolling).</p><p>The Working Group dedicates this specification to our colleague David Kirby.</p></div></div></body></html>
\ No newline at end of file
--- a/ttml10/spec/ttaf1-dfxp.xml Wed May 01 22:59:16 2013 -0700
+++ b/ttml10/spec/ttaf1-dfxp.xml Thu May 02 21:36:21 2013 -0700
@@ -834,8 +834,8 @@
satisfied:</p>
<olist>
<item>
-<p>When transporting a document instance in a context in which a MIME
-Media Type <bibref ref="mime-media"/> identifies the content type of the interchanged document
+<p>When transporting a document instance in a context in which a
+Media Type <bibref ref="media-types"/> identifies the content type of the interchanged document
instance, then the specified media type is
<code>application/ttml+xml</code> in conformance with <bibref
ref="rfc3023"/> § 7, with which an optional
@@ -2169,10 +2169,10 @@
requires the use of a monospaced font and a font size whose EM square exactly
matches the cell size.</p>
</note>
-<note role="explanation">
-<p>When a <loc href="#style-value-length"><length></loc> expressed in
-cells applies to a dimension parallel to the inline or block progression dimension,
-a cell's dimension in the inline or block progression dimension applies, respectively.
+<note role="elaboration">
+<p>Except when indicated otherwise, when a <loc href="#style-value-length"><length></loc> expressed in
+cells expresses a dimension parallel to the inline or block progression dimension,
+the cell's dimension in the inline or block progression dimension applies, respectively.
For example, if padding (on all four edges) is specified as 0.1c, the cell resolution
is 20 by 10, and the root container extent is 640 by 480, then, assuming top to bottom,
left to right writing mode, the start and end padding will be 640 / 20 * 0.1 pixels and the
@@ -5358,6 +5358,15 @@
present, the computed value of the <att>tts:color</att> applies. The first
<emph>length</emph> term denotes the outline thickness and the second length
term, if present, indicates the blur radius.</p>
+<note role="elaboration">
+<p>When a <loc href="#style-value-length"><length></loc> expressed in
+cells is used in a <att>tts:textOutline</att> value,
+the cell's dimension in the block progression dimension applies.
+For example, if text outline thickness is specified as 0.1c, the cell resolution
+is 20 by 10, and the root container extent is 640 by 480, then the
+outline thickness will be a nominal 480 / 10 * 0.1 pixels, i.e., 4.8px,
+without taking into account rasterization effects.</p>
+</note>
<p>If a specified value of this attribute is not supported,
then a presentation processor must interpret the attribute as if the
value <code>none</code> were specified.</p>
@@ -8661,10 +8670,10 @@
is defined by <specref ref="conformance-content"/>.</p>
</div2>
</div1>
-<div1 id="media-type-registration">
+<div1 id="media-types-registration">
<head>Media Type Registration</head>
<p><emph>This appendix is normative.</emph></p>
-<p>This appendix registers a new MIME media type,
+<p>This appendix registers a new media type,
"application/ttml+xml" in conformance with
<loc href="http://www.ietf.org/rfc/rfc4288.txt">BCP 13</loc> and
<loc
@@ -11296,7 +11305,7 @@
December 2012. (See
<xspecref href="http://www.w3.org/TR/2012/CR-html5-20121217//">http://www.w3.org/TR/2012/CR-html5-20121217//</xspecref>.)
</bibl>
-<bibl id="mime-media" key="MIME">Ned Freed and Nathaniel Borenstein,
+<bibl id="media-types" key="Media Types">Ned Freed and Nathaniel Borenstein,
<titleref
href="http://www.rfc-editor.org/rfc/rfc2046.txt">Multipurpose Internet
Mail Extensions (MIME) Part Two: Media Types</titleref>,