[ttml1] complete changes of name to ttml1
authorGlenn Adams <glenn@skynav.com>
Fri, 23 Aug 2013 12:05:59 -0600
changeset 470 87793ae8ba55
parent 469 9396362eae8c
child 471 53d6d7d55614
[ttml1] complete changes of name to ttml1
ttml1/spec/rnc/schema.zip
ttml1/spec/ttml1-changes.html
ttml1/spec/ttml1.html
ttml1/spec/ttml1.xml
ttml1/spec/xsd/schema.zip
Binary file ttml1/spec/rnc/schema.zip has changed
--- a/ttml1/spec/ttml1-changes.html	Thu Aug 22 10:59:12 2013 -0600
+++ b/ttml1/spec/ttml1-changes.html	Fri Aug 23 12:05:59 2013 -0600
@@ -19,7 +19,7 @@
 <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/>
 </head>
 <body>
-<h1>Timed Text Markup Language (TTML) 1.0 Change Summary</h1>
+<h1>Timed Text Markup Language 1 (TTML1) Change Summary</h1>
 <p>1 <a href="#change-history">Change History</a> (Non-Normative)<br/>
     1.1 <a href="#change-history-per-to-rec-23">Draft Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</a><br/>
     1.2 <a href="#change-history-rec-to-2e-per">Changes from Recommendation to Proposed Edited Recommendation (2nd Ed.)</a><br/>
@@ -36,11 +36,13 @@
 <p>Changes are ordered from most recent to least recent.</p>
 
 <div class="div2">
-<h3><a id="change-history-per-to-rec-2e"/>1.1 Draft Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</h3>
+<h3><a id="change-history-per-to-rec-2e"/>1.1 Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</h3>
 <div class="exampleInner">
 <pre>
 <span class="strong">Editorial Changes</span>
 
+* In Title, Abstract, and 1.0, use Timed Text Markup Language 1 (TTML1) to refer to the
+  first version of TTML. [The next version of TTML is expected to be called TTML2.]
 * In 1.2, add note explaining that use of &lt;p/&gt; element may be presentational or semantic
   according to intentions of author.
 * In 2.2, change the definition of "Related Media Object Region" to not imply that a
--- a/ttml1/spec/ttml1.html	Thu Aug 22 10:59:12 2013 -0600
+++ b/ttml1/spec/ttml1.html	Fri Aug 23 12:05:59 2013 -0600
@@ -88,8 +88,8 @@
 <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
 </dd><dt>Editor:</dt><dd>Glenn Adams, Cox Communications, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p>Please refer to the <a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttml-issues.html">errata</a> for this document, which may
       include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ttml1"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
-<h2><a id="abstract"></a>Abstract</h2><p>This document specifies the Timed Text Markup Language (TTML) in terms of a
-vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
+<h2><a id="abstract"></a>Abstract</h2><p>This document specifies Timed Text Markup Language (TTML), Version 1, also known as TTML1,
+in terms of a vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
 timed text media for the purpose of interchange among authoring
 systems. Timed text is textual information that is intrinsically or
 extrinsically associated with timing information.</p><p>It is intended to be used
@@ -409,19 +409,18 @@
 &nbsp;&nbsp;&nbsp;&nbsp;O.3 <a href="#paint-on-example">Paint-On Caption Example</a><br>
 P <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br>
 </p></div><hr><div class="body"><div class="div1">
-<h2><a id="intro"></a>1 Introduction</h2><p><em>Unless specified otherwise, this section and its sub-sections are non-normative.</em></p><p>The Timed Text Markup Language (TTML) 1.0
+<h2><a id="intro"></a>1 Introduction</h2><p><em>Unless specified otherwise, this section and its sub-sections are non-normative.</em></p><p>The Timed Text Markup Language (TTML) Version 1, also referred to as TTML1,
 provides a standardized representation of a particular subset of
 textual information with which stylistic, layout, and timing semantics are associated by
 an author or an authoring system for the purpose of interchange and processing.</p><p>TTML is expressly designed to meet only a limited set of requirements
 established by <a href="#ttaf1-req">[TTAF1-REQ]</a>, and summarized in <a href="#requirements"><b>I Requirements</b></a>. In particular, only those requirements which service the
 need of performing interchange with existing, legacy distribution systems are
 satisfied.</p><p>In addition to being used for interchange among legacy distribution content
-formats, TTML Content may be used directly as a distribution format (as implied by
-the acronym DFXP), providing, for
+formats, TTML Content may be used directly as a distribution format, providing, for
 example, a standard content format to reference from a <code>&lt;track&gt;</code>
 element in an HTML5 document, or a <code>&lt;text&gt;</code> or 
 <code>&lt;textstream&gt;</code> media element in a <a href="#smil21">[SMIL 2.1]</a> document. Certain properties of TTML support
-streamability of content, as described in <a href="#streaming"><b>L Streaming TTML Content</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While TTML was not expressly designed for direct (embedded) integration into an
+streamability of content, as described in <a href="#streaming"><b>L Streaming TTML Content</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While TTML is not expressly designed for direct (embedded) integration into an
 HTML or a SMIL document instance, such integration is not precluded.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In some contexts of use, it may be appropriate to employ
 animated content to depict sign language representations of the same content
 as expressed by a Timed Text <em>Document Instance</em>. This use case is not
@@ -2602,8 +2601,8 @@
 <a href="#content-vocabulary-p"><code>p</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute is <code>normal</code>, then the
 computed value of the style property must be considered to be the same
-as the largest font size that applies to any
-descendant element in the intermediate synchronic document as determined by
+as 120% of the largest font size that applies to the element and its
+descendant elements in the intermediate synchronic document as determined by
 <a href="#semantics-region-layout-step-1"><b>9.3.2 Intermediate Synchronic Document Construction</b></a>.</p><p>If specified as a <a href="#style-value-length">&lt;length&gt;</a>, then the length must
 be non-negative.</p><p>If a specified value of this attribute is not supported,
 then a presentation processor must interpret the attribute as if the
@@ -4920,9 +4919,9 @@
 <code>ttp:profile</code> parameter defined by
 Section
 <a href="#parameter-attribute-profile"><b>6.2.8 ttp:profile</b></a>
-of the published specification.</p></dd></dl></dd><dt class="label">Encoding considerations:</dt><dd><p>Same for application/xml, except constrained to either UTF-8 or UTF-16. See <a href="#xml-media">[XML Media Types]</a>, Section
-3.2.</p></dd><dt class="label">Security considerations:</dt><dd><p>As with other XML types and as noted in
-<a href="#xml-media">[XML Media Types]</a>
+of the published specification.</p></dd></dl></dd><dt class="label">Encoding considerations:</dt><dd><p>Same for application/xml, except constrained to either UTF-8 or UTF-16. See <a href="#xml-media">[XML Media Types]</a>
+(http://www.rfc-editor.org/rfc/rfc3023.txt), Section 3.2.</p></dd><dt class="label">Security considerations:</dt><dd><p>As with other XML types and as noted in
+<a href="#xml-media">[XML Media Types]</a> (http://www.rfc-editor.org/rfc/rfc3023.txt),
 Section 10, repeated expansion of maliciously constructed XML entities
 can be used to consume large amounts of memory, which may cause XML
 processors in constrained environments to fail.</p><p>In addition, because of the extensibility features for TTML and of XML
--- a/ttml1/spec/ttml1.xml	Thu Aug 22 10:59:12 2013 -0600
+++ b/ttml1/spec/ttml1.xml	Fri Aug 23 12:05:59 2013 -0600
@@ -104,8 +104,8 @@
 <errataloc href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttml-issues.html"/>
 <translationloc href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ttml1"/>
 <abstract id="abstract">
-<p>This document specifies the Timed Text Markup Language (TTML) in terms of a
-vocabulary and semantics thereof.</p>
+<p>This document specifies Timed Text Markup Language (TTML), Version 1, also known as TTML1,
+in terms of a vocabulary and semantics thereof.</p>
 <p>The Timed Text Markup Language is a content type that represents
 timed text media for the purpose of interchange among authoring
 systems. Timed text is textual information that is intrinsically or
@@ -129,7 +129,7 @@
 <div1 id="intro">
 <head>Introduction</head>
 <p><emph>Unless specified otherwise, this section and its sub-sections are non-normative.</emph></p>
-<p>The Timed Text Markup Language (TTML) 1.0
+<p>The Timed Text Markup Language (TTML) Version 1, also referred to as TTML1,
 provides a standardized representation of a particular subset of
 textual information with which stylistic, layout, and timing semantics are associated by
 an author or an authoring system for the purpose of interchange and processing.</p>
@@ -139,15 +139,14 @@
 need of performing interchange with existing, legacy distribution systems are
 satisfied.</p>
 <p>In addition to being used for interchange among legacy distribution content
-formats, TTML Content may be used directly as a distribution format (as implied by
-the acronym DFXP), providing, for
+formats, TTML Content may be used directly as a distribution format, providing, for
 example, a standard content format to reference from a <el>&lt;track&gt;</el>
 element in an HTML5 document, or a <el>&lt;text&gt;</el> or 
 <el>&lt;textstream&gt;</el> media element in a <bibref
 ref="smil21"/> document. Certain properties of TTML support
 streamability of content, as described in <specref ref="streaming"/>.</p>
 <note>
-<p>While TTML was not expressly designed for direct (embedded) integration into an
+<p>While TTML is not expressly designed for direct (embedded) integration into an
 HTML or a SMIL document instance, such integration is not precluded.</p>
 </note>
 <note>
@@ -8724,15 +8723,15 @@
 <gitem>
 <label>Encoding considerations:</label>
 <def>
-<p>Same for application/xml, except constrained to either UTF-8 or UTF-16. See <bibref ref="xml-media"/>, Section
-3.2.</p>
+<p>Same for application/xml, except constrained to either UTF-8 or UTF-16. See <bibref ref="xml-media"/>
+(http://www.rfc-editor.org/rfc/rfc3023.txt), Section 3.2.</p>
 </def>
 </gitem>
 <gitem>
 <label>Security considerations:</label>
 <def>
 <p>As with other XML types and as noted in
-<bibref ref="xml-media"/>
+<bibref ref="xml-media"/> (http://www.rfc-editor.org/rfc/rfc3023.txt),
 Section 10, repeated expansion of maliciously constructed XML entities
 can be used to consume large amounts of memory, which may cause XML
 processors in constrained environments to fail.</p>
Binary file ttml1/spec/xsd/schema.zip has changed