Binary file ttml2/spec/rnc/schema.zip has changed
--- a/ttml2/spec/ttml2-changes.html Wed Oct 28 18:09:44 2015 +0900
+++ b/ttml2/spec/ttml2-changes.html Thu Oct 29 07:39:58 2015 +0900
@@ -52,7 +52,9 @@
'resources',
'font',
'image',
+ 'initial',
'source',
+ 'resources',
and
'ttm:item
to Table 5-3.
--- a/ttml2/spec/ttml2.html Wed Oct 28 18:09:44 2015 +0900
+++ b/ttml2/spec/ttml2.html Thu Oct 29 07:39:58 2015 +0900
@@ -83,9 +83,9 @@
.obsoleted { background-color: #f26d7d }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2015/08/07 15:56:59 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2015/10/28 22:38:31 $<div id="revisions"></div><div class="head">
<h1><a id="title"></a>Timed Text Markup Language 2 (TTML2)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/08/07 15:56:59 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/10/28 22:38:31 $ @@ @@@@ @@@@</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>Latest recommendation:</dt><dd><a href="http://www.w3.org/TR/ttml1/">http://www.w3.org/TR/ttml1/</a></dd><dt>Previous version:</dt><dd>
None
@@ -535,11 +535,11 @@
K <a href="#other-references">Other References</a> (Non-Normative)<br>
L <a href="#requirements">Requirements</a> (Non-Normative)<br>
M <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
- M.1 <a href="#d3e38419">Element Derivation</a><br>
- M.2 <a href="#d3e38936">Attribute Derivation</a><br>
+ M.1 <a href="#d3e38438">Element Derivation</a><br>
+ M.2 <a href="#d3e38955">Attribute Derivation</a><br>
N <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- N.1 <a href="#d3e39929">Requirements</a><br>
- N.2 <a href="#d3e40093">Guidelines</a><br>
+ N.1 <a href="#d3e39948">Requirements</a><br>
+ N.2 <a href="#d3e40112">Guidelines</a><br>
O <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
P <a href="#common-styling">Common Caption Style Examples</a> (Non-Normative)<br>
P.1 <a href="#pop-on-example">Pop-On Caption Example</a><br>
@@ -4250,7 +4250,8 @@
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.29.1.</p></div></div><div class="div3">
<h4><a id="style-attribute-disparity"></a>10.2.10 tts:disparity</h4><p>The <code>tts:disparity</code> attribute is used to specify the binocular disparity to be applied
-in order to simulate stereopsis (stereoscopic depth).</p><p>This attribute may be specified by any element type
+in order to simulate stereopsis (stereoscopic depth). A disparity of zero corresponds to the plane of display; a negative value corresponds to depths in front
+ of the plane of display; and a positive value corresponds to depths behind the plane of display. See <a href="#stereoscopy">[STEREO]</a> for an introduction to stereoscopy, and <a href="#smiththreed">[SMITH]</a> for details on the relationship between disparity and perceived depth.</p><p>This attribute may be specified by any element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><a id="style-property-details-disparity"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-length"><length></a>
@@ -4258,8 +4259,7 @@
<a href="#content-vocabulary-div"><code>div</code></a>,
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes (see prose)</td></tr><tr><td><em>Percentages:</em></td><td>relative to width of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If specified, the value of this attribute consists of a <a href="#style-value-length"><length></a> specification, the computed value
-of which is evenly divided along the horizontal axis between left and right stereoscopic images.</p><p>If a <code>tts:disparity</code> attribute is specified on a <code>div</code> or <code>p</code> element, then that specification must be considered to be
+</td></tr><tr><td><em>Inherited:</em></td><td>yes (see prose)</td></tr><tr><td><em>Percentages:</em></td><td>relative to width of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>When rendering a region on the right (left) image of a stereoscopic image pair, the center of the region shall be offset along the horizontal axis by a value equal to ½ (-½) the computed value of <code>tts:disparity</code>.</p><p><code>tts:disparity</code> is ignored unless rendering onto a stereoscopic image pair.</p><p>The author should ensure that the perceived depth of a region is positioned in front of any object in the scene during the entire time the region is visible. The stereoscopic effect will be broken if an object in the scene is perceived to be in front of the region.</p><p>If a <code>tts:disparity</code> attribute is specified on a <code>div</code> or <code>p</code> element, then that specification must be considered to be
equivalent to specifying an anonymous <a href="#terms-inline-region">inline region</a> child of the <code>div</code> or <code>p</code> element, where the
disparity of the corresponding region, also referred to as an <a href="#terms-implied-inline-region">implied inline region</a>, is equal to the
value of this attribute.</p><p>If applicable, inheritance of disparity occurs only by means of <a href="#semantics-style-inheritance-root"><b>10.4.2.3 Root Style Inheritance</b></a>, whether the inheriting region is
@@ -4268,19 +4268,20 @@
or an <a href="#terms-implied-inline-region">implied inline region</a>.</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 closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
the computed disparity and the supported disparity is minimized. If there are multiple closest supported values equally distant from
-the computed value, then the value least distant from 0 is used.</p></div><p>The <code>tts:disparity</code> style is illustrated by the following example.</p><a id="style-attribute-disparity-example-1"></a><table class="example"><caption>Example Fragment – Disparity</caption><tbody><tr><td>
+the computed value, then the value least distant from 0 is used.</p></div><p>The <code>tts:disparity</code> style is illustrated by the following example fragment and rendition. Note that, in typical television scenarios, disparity ranges from -1% to 2% of screen width. This example, which uses a disparity of 5%, exaggerates the effects of disparity for clarity of illustration.</p><a id="style-attribute-disparity-example-1"></a><table class="example"><caption>Example Fragment – Disparity</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
- <style tts:extent="30% 10%"/>
- <style tts:position="center bottom 10%"/>
- <style <span class="strong">tts:disparity="0.7%"</span>/>
+ <style tts:extent="80% 10%"/>
+ <style tts:origin="10% 10%"/>
+ <style <span class="strong">tts:disparity="5%"</span>/>
+ ...
</region>
...
<p region="r1">
- 3D Text Sample
+ Stereoscopic
</p>
</pre></div>
-</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Disparity Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Disparity Example</b></td><td align="right" valign="top">2015-01-17</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example image of tts:disparity.</td></tr></table></div><div class="div3">
+</td></tr></tbody></table><p></p><a id="style-attribute-disparity-example-1-images"></a><table class="example-images"><caption>Example Rendition – Disparity (Left and Right images of a stereoscopic pair)</caption><tbody><tr><td><img src="images/disparity1.png" alt="TTML disparity style property"></td></tr></tbody></table></div><div class="div3">
<h4><a id="style-attribute-display"></a>10.2.11 tts:display</h4><p>The <code>tts:display</code> attribute is used to specify a style property that
defines whether an element is a candidate for layout and composition
in a region.</p><p>This attribute may be specified by any
@@ -10155,6 +10156,7 @@
Requirements for Analog Television Receivers</cite></a>,
United States Code of Federal Regulations, Title 47, Volume 1, Part 79, § 79.101. (See
<a href="http://www.gpo.gov/fdsys/pkg/CFR-2012-title47-vol4/pdf/CFR-2012-title47-vol4-sec79-101.pdf">http://www.gpo.gov/fdsys/pkg/CFR-2012-title47-vol4/pdf/CFR-2012-title47-vol4-sec79-101.pdf</a>.)
+</dd><dt class="label"><a id="smiththreed"></a>SMITH</dt><dd>Smith, Michael D.; Malia, Jason, <a href="http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7271939&isnumber=7271882"><cite>Controlling Miniaturization in Stereoscopic 3D Imagery</cite></a>, in Motion Imaging Journal, SMPTE , vol.124, no.3, pp.50-58, April 2015 doi: 10.5594/j18531
</dd><dt class="label"><a id="cea608e"></a>CEA-608-E</dt><dd>
EIA/CEA-608-E,
<a href="http://www.ce.org/"><cite>Line 21 Data
@@ -10208,6 +10210,7 @@
<a href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html"><cite>The Disposition
of Names in an XML Namespace</cite></a>, TAG Finding, 9 January 2006. (See
<a href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html">http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09</a>.)
+</dd><dt class="label"><a id="stereoscopy"></a>STEREO</dt><dd><a href="https://en.wikipedia.org/wiki/Stereoscopy"><cite>Stereoscopy</cite></a>, Wikipedia.
</dd><dt class="label"><a id="qaf-sg"></a>QAF SG</dt><dd>Karl Dubost, et al.,
<a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/"><cite>QA
Framework: Specifications Guidelines</cite></a>, W3C Recommendation, 17
@@ -10256,7 +10259,7 @@
<h2><a id="derivation"></a>M Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
vocabulary, separately describing derivation of elements and
attributes.</p><table border="1" class="ednote" summary="Editorial note: Update Derivation"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Update Derivation</b></td><td align="right" valign="top">2015-01-14</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Update derivation tables to include new vocabulary added in TTML2.</td></tr></table><div class="div2">
-<h3><a id="d3e38419"></a>M.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table M-1 – Elements</b></a>
+<h3><a id="d3e38438"></a>M.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table M-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
@@ -10313,7 +10316,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="d3e38936"></a>M.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table M-2 – Attributes</b></a>
+<h3><a id="d3e38955"></a>M.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table M-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
@@ -10405,9 +10408,9 @@
<h2><a id="qa"></a>N 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="d3e39929"></a>N.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table N-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="d3e39948"></a>N.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table N-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="d3e40093"></a>N.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table N-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiling">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e40112"></a>N.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table N-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiling">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>M 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 Oct 28 18:09:44 2015 +0900
+++ b/ttml2/spec/ttml2.xml Thu Oct 29 07:39:58 2015 +0900
@@ -8186,7 +8186,8 @@
<div3 id="style-attribute-disparity">
<head>tts:disparity</head>
<p>The <att>tts:disparity</att> attribute is used to specify the binocular disparity to be applied
-in order to simulate stereopsis (stereoscopic depth).</p>
+in order to simulate stereopsis (stereoscopic depth). A disparity of zero corresponds to the plane of display; a negative value corresponds to depths in front
+ of the plane of display; and a positive value corresponds to depths behind the plane of display. See <bibref ref="stereoscopy"/> for an introduction to stereoscopy, and <bibref ref="smiththreed"/> for details on the relationship between disparity and perceived depth.</p>
<p>This attribute may be specified by any element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
@@ -8226,8 +8227,9 @@
</tr>
</tbody>
</table>
-<p>If specified, the value of this attribute consists of a <loc href="#style-value-length"><length></loc> specification, the computed value
-of which is evenly divided along the horizontal axis between left and right stereoscopic images.</p>
+<p>When rendering a region on the right (left) image of a stereoscopic image pair, the center of the region shall be offset along the horizontal axis by a value equal to ½ (-½) the computed value of <att>tts:disparity</att>.</p>
+<p><att>tts:disparity</att> is ignored unless rendering onto a stereoscopic image pair.</p>
+<p>The author should ensure that the perceived depth of a region is positioned in front of any object in the scene during the entire time the region is visible. The stereoscopic effect will be broken if an object in the scene is perceived to be in front of the region.</p>
<p>If a <att>tts:disparity</att> attribute is specified on a <el>div</el> or <el>p</el> element, then that specification must be considered to be
equivalent to specifying an anonymous <loc href="#terms-inline-region">inline region</loc> child of the <el>div</el> or <el>p</el> element, where the
disparity of the corresponding region, also referred to as an <loc href="#terms-implied-inline-region">implied inline region</loc>, is equal to the
@@ -8243,7 +8245,7 @@
the computed disparity and the supported disparity is minimized. If there are multiple closest supported values equally distant from
the computed value, then the value least distant from 0 is used.</p>
</note>
-<p>The <att>tts:disparity</att> style is illustrated by the following example.</p>
+<p>The <att>tts:disparity</att> style is illustrated by the following example fragment and rendition. Note that, in typical television scenarios, disparity ranges from -1% to 2% of screen width. This example, which uses a disparity of 5%, exaggerates the effects of disparity for clarity of illustration.</p>
<table id="style-attribute-disparity-example-1" role="example">
<caption>Example Fragment – Disparity</caption>
<tbody>
@@ -8251,13 +8253,14 @@
<td>
<eg xml:space="preserve">
<region xml:id="r1">
- <style tts:extent="30% 10%"/>
- <style tts:position="center bottom 10%"/>
- <style <phrase role="strong">tts:disparity="0.7%"</phrase>/>
+ <style tts:extent="80% 10%"/>
+ <style tts:origin="10% 10%"/>
+ <style <phrase role="strong">tts:disparity="5%"</phrase>/>
+ ...
</region>
...
<p region="r1">
- 3D Text Sample
+ Stereoscopic
</p>
</eg>
</td>
@@ -8265,11 +8268,14 @@
</tbody>
</table>
<p></p>
-<ednote>
-<name>Disparity Example</name>
-<date>2015-01-17</date>
-<edtext>Insert example image of tts:disparity.</edtext>
-</ednote>
+<table id="style-attribute-disparity-example-1-images" role="example-images">
+<caption>Example Rendition – Disparity (Left and Right images of a stereoscopic pair)</caption>
+<tbody>
+<tr>
+<td><graphic source="images/disparity1.png" alt="TTML disparity style property"/></td>
+</tr>
+</tbody>
+</table>
</div3>
<div3 id="style-attribute-display">
<head>tts:display</head>
@@ -20514,6 +20520,9 @@
United States Code of Federal Regulations, Title 47, Volume 1, Part 79, § 79.101. (See
<xspecref href="http://www.gpo.gov/fdsys/pkg/CFR-2012-title47-vol4/pdf/CFR-2012-title47-vol4-sec79-101.pdf">http://www.gpo.gov/fdsys/pkg/CFR-2012-title47-vol4/pdf/CFR-2012-title47-vol4-sec79-101.pdf</xspecref>.)
</bibl>
+<bibl id="smiththreed" key="SMITH">Smith, Michael D.; Malia, Jason, <titleref
+href="http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7271939&isnumber=7271882">Controlling Miniaturization in Stereoscopic 3D Imagery</titleref>, in Motion Imaging Journal, SMPTE , vol.124, no.3, pp.50-58, April 2015 doi: 10.5594/j18531
+</bibl>
<bibl id="cea608e" key="CEA-608-E">
EIA/CEA-608-E,
<titleref href="http://www.ce.org/">Line 21 Data
@@ -20584,6 +20593,8 @@
of Names in an XML Namespace</titleref>, TAG Finding, 9 January 2006. (See
<xspecref href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html">http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09</xspecref>.)
</bibl>
+<bibl id="stereoscopy" key="STEREO"><titleref href="https://en.wikipedia.org/wiki/Stereoscopy">Stereoscopy</titleref>, Wikipedia.
+</bibl>
<bibl id="qaf-sg" key="QAF SG">Karl Dubost, et al.,
<titleref
href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
Binary file ttml2/spec/xsd/schema.zip has changed