[ttml1] add errata for missing character entities (issue 282)
authorGlenn Adams <glenn@skynav.com>
Thu, 20 Feb 2014 09:18:34 -0700
changeset 597 a6e693d1cfa1
parent 596 f32bd11bc601
child 598 83d32f4837ee
[ttml1] add errata for missing character entities (issue 282)
ttml1/spec/ttml1-errata.html
--- a/ttml1/spec/ttml1-errata.html	Wed Feb 12 22:56:48 2014 -0800
+++ b/ttml1/spec/ttml1-errata.html	Thu Feb 20 09:18:34 2014 -0700
@@ -1,150 +1,251 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<title>TTML1 - Errata</title>
-<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/>
-</head>
-<body>
-<h1>Errata for Timed Text Markup Language 1 (TTML1); W3C REC, 24 September 2013</h1>
-<h2>Section 5.2 - Profiles</h2>
-<p id="errata-5.2-1">In the third paragraph under Table 2, change "... and must not be appear ..." to read "... and must not appear ...".</p>
-<h2>Appendix C - Media Type Registration</h2>
-<p id="errata-C-1">Replace the body of Appendix C with the following:</p>
-<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>. The
-information in this appendix is being submitted to the Internet Engineering
-Steering Group (IESG) for review, approval, and registration with the Internet
-Assigned Numbers Authority (IANA).</p>
-<dl>
-  <dt class="label">Type name:</dt>
-  <dd>
-    <p>application</p>
-  </dd>
-  <dt class="label">Subtype name:</dt>
-  <dd>
-    <p>ttml+xml</p>
-  </dd>
-  <dt class="label">Required parameters:</dt>
-  <dd>
-    <p>None.</p>
-  </dd>
-  <dt class="label">Optional parameters:</dt>
-  <dd>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html
+  xmlns="http://www.w3.org/1999/xhtml">
+  <head>
+    <style type="text/css">
+    .diff-chg { background-color: lime }
+    .diff-add { background-color: yellow }
+    .diff-del { background-color: #FFBBBB; text-decoration: line-through; }
+    .remove { background: #ccccff; }
+    .title-description { color:red; font-style:italic }
+    .title-correction { color:red; font-style:italic }
+    .error{ background:  #dddddd;border-width: 1;margin-top:1cm;}
+  </style>
+    <title>TTML1 - Errata</title>
+    <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css" />
+  </head>
+  <body>
+    <h1>Errata for Timed Text Markup Language 1 (TTML1)</h1>
+    <h2>W3C Recommendation 24 September 2013</h2>
     <dl>
-      <dt class="label">charset</dt>
+      <dt><span style="font-weight: normal;">This version:</span></dt>
+      <dd><a href="http://www.w3.org/2013/09/ttml1-errata.html">http://www.w3.org/2013/09/ttml1-errata.html</a></dd>
+      <dt><span style="font-weight: normal;">This document records known errors
+          in the document:</span></dt>
+      <dd><a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/">http://www.w3.org/TR/2013/REC-ttml1-20130924/</a></dd>
+      <dt><span style="font-weight: normal;">Latest TTML1 version:</span></dt>
+      <dd><a href="http://www.w3.org/TR/ttml1/">http://www.w3.org/TR/ttml1/</a></dd>
+    </dl>
+    <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
+      © 2014 <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>
+    <hr title="Separator from Header" />
+    <h2>About the TTML1 Recommendation</h2>
+    <p>The <a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/">TTML1
+        Recommendation</a> has been produced by the W3C <a href="http://www.w3.org/AudioVideo/TT/">Timed
+        Text (TT) Working Group</a> as part of the W3C <a href="http://www.w3.org/2008/WebVideo/">Video
+        in the Web Activity</a>.</p>
+    <p>This document lists the known errata to the <a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/">TTML1
+        Recommendation</a><br />
+      Each entry has the following information:</p>
+    <ul>
+      <li>A unique entry number</li>
+      <li>The date it was added to the errata page.</li>
+      <li>Whether the entry is considered an important error, a minor
+        typographical error, a clarification, or a known problem with the
+        document itself.</li>
+      <li>The section referred to.</li>
+      <li>A description of the problem and correction if applicable.</li>
+    </ul>
+    <p>Please send general comments about this document to the public mailing
+      list <a href="mailto:[email protected]">[email protected]</a> (<a href="mailto:[email protected]">subscribe</a>,
+      <a href="http://lists.w3.org/Archives/Public/public-tt/">archive</a>). </p>
+    <h2>Conventions</h2>
+    <p>Added text marked <span class="diff-add">thus</span>. Removed text
+      marked <span class="diff-del">thus</span>. Changed text marked <span class="diff-chg">thus</span>.</p>
+    <h2 id="errors">Known errors as of 30 January 2014</h2>
+    <ul>
+      <li><a href="#errata-5.2-1">E01: Correction in in TTML1 Section 5.2 Profiles</a>
+          (published 30 01 2014)</li>
+      <li><a href="#errata-C-1">E02: Correction in TTML1 Appendix C - Media Type
+          Registration</a> (published 30 01 2014)</li>
+      <li><a href="#errata-M-1">E03: Correction in TTML1 Appendix M - Concrete
+          Encoding</a> (published 20 02 2014)</li>
+    </ul>
+    <h2>Erratas:</h2>
+    <p id="errata-5.2-1"><strong> E01: </strong><a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/#vocabulary-profiles">Correction
+        in TTML1 Section 5.2 Profiles</a> (published 30 01 2014) </p>
+    <p class="description"><span class="title-description">Description</span>:</p>
+    Minor typographical error, in the third paragraph under Table 2.
+    <p class="description"><em><strong><span class="title-correction">Resolution</span></strong></em>:</p>
+    <p>change "... and must not <span class="diff-del">be </span>appear ..."</p>
+    <p>to read "... and must not appear ...".</p>
+    <hr />
+    <p id="errata-C-1"><strong>E02: </strong><a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/#media-types-registration">Correction
+        in TTML1 Appendix C - Media Type Registration</a> (published 30 01 2014)</p>
+    <p class="description"><span class="title-description">Description</span>:</p>
+    <p class="description">Correction in the Media Type Registration wording:<br />
+    </p>
+    <ul>
+      <li> in <span style="font-weight: bold;">Encoding Considerations</span>
+        paragraph: changed entire wording to "<span class="diff-add">binary</span>"
+      </li>
+      <li>in <span style="font-weight: bold;">profile</span> parameter
+        definition: removed former comment "<span class="diff-del">See Encoding
+          Considerations below.</span>".</li>
+    </ul>
+    <p class="description"><em><strong><span class="title-correction">Resolution</span></strong></em>:</p>
+    Replace the body of Appendix C with the following:
+    <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>.
+      The information in this appendix is being submitted to the Internet
+      Engineering Steering Group (IESG) for review, approval, and registration
+      with the Internet Assigned Numbers Authority (IANA).</p>
+    <dl>
+      <dt class="label">Type name:</dt>
       <dd>
-        <p>If specified, the <code>charset</code> parameter must match the XML
-        encoding declaration, or if absent, the actual encoding.</p>
+        <p>application</p>
       </dd>
-      <dt class="label">profile</dt>
+      <dt class="label">Subtype name:</dt>
       <dd>
-        <p>The document profile of a TTMLDocument Instance may be specified using
-        an optional <code>profile</code> parameter, which, if specified, the value
-        of which must adhere to the syntax and semantics of
-        <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>
+        <p>ttml+xml</p>
+      </dd>
+      <dt class="label">Required parameters:</dt>
+      <dd>
+        <p>None.</p>
+      </dd>
+      <dt class="label">Optional parameters:</dt>
+      <dd>
+        <dl>
+          <dt class="label">charset</dt>
+          <dd>
+            <p>If specified, the <code>charset</code> parameter must match the
+              XML encoding declaration, or if absent, the actual encoding.</p>
+          </dd>
+          <dt class="label">profile</dt>
+          <dd>
+            <p>The document profile of a TTMLDocument Instance may be specified
+              using an optional <code>profile</code> parameter, which, if
+              specified, the value of which must adhere to the syntax and
+              semantics of <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>binary</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 in general, it is possible that "application/ttml+xml" may
+          describe content that has security implications beyond those described
+          here. However, TTML does not provide for any sort of active or
+          executable content, and if the processor follows only the normative
+          semantics of the published specification, this content will be outside
+          TTML namespaces and may be ignored. Only in the case where the
+          processor recognizes and processes the additional content, or where
+          further processing of that content is dispatched to other processors,
+          would security issues potentially arise. And in that case, they would
+          fall outside the domain of this registration document.</p>
+        <p>Although not prohibited, there are no expectations that XML
+          signatures or encryption would normally be employed.</p>
+      </dd>
+      <dt class="label">Interoperability considerations:</dt>
+      <dd>
+        <p>The published specification describes processing semantics that
+          dictate behavior that must be followed when dealing with, among other
+          things, unrecognized elements and attributes, both in TTML namespaces
+          and in other namespaces.</p>
+        <p>Because TTML is extensible, conformant "application/ttml+xml"
+          processors may expect (and enforce) that content received is
+          well-formed XML, but it cannot be guaranteed that the content is valid
+          to a particular DTD or Schema or that the processor will recognize all
+          of the elements and attributes in the document.</p>
+      </dd>
+      <dt class="label">Published specification:</dt>
+      <dd>
+        <p>This media type registration is extracted from Appendix C Media Type
+          Registration of the Timed Text Markup Language (TTML) 1.0
+          specification: <a href="http://www.w3.org/TR/ttml1/">Timed Text
+            Markup Language 1 (TTML1)</a>.</p>
+      </dd>
+      <dt class="label">Applications that use this media type:</dt>
+      <dd>
+        <p>TTML is used in the television industry for the purpose of authoring,
+          transcoding and exchanging timed text information and for delivering
+          captions, subtitles, and other metadata for television material
+          repurposed for the Web or, more generally, the Internet.</p>
+        <p>There is partial and full support of TTML in components used by
+          several Web browsers plugins, and in a number of caption authoring
+          tools.</p>
+      </dd>
+      <dt class="label">Additional information:</dt>
+      <dd>
+        <dl>
+          <dt class="label">Magic number(s):</dt>
+          <dt class="label">File extension(s):</dt>
+          <dd>
+            <p>.ttml</p>
+          </dd>
+          <dt class="label">Macintosh file type code(s):</dt>
+          <dd>
+            <p>"TTML"</p>
+          </dd>
+          <dt class="label">Fragment identifiers:</dt>
+          <dd>
+            <p>For documents labeled as application/ttml+xml, the fragment
+              identifier notation is intended to be used with xml:id attributes,
+              as described in section 7.2.1 of the <a href="http://www.w3.org/TR/ttml1/">Timed
+                Text Markup Language 1 (TTML1)</a> specification.</p>
+          </dd>
+        </dl>
+      </dd>
+      <dt class="label">Person &amp; email address to contact for further
+        information:</dt>
+      <dd>
+        <p>Timed Text Working Group ([email protected])</p>
+      </dd>
+      <dt class="label">Intended usage:</dt>
+      <dd>
+        <p>COMMON</p>
+      </dd>
+      <dt class="label">Restrictions on usage:</dt>
+      <dd>
+        <p>None</p>
+      </dd>
+      <dt class="label">Author:</dt>
+      <dd>
+        <p>The published specification is a work product of the World Wide Web
+          Consortium's Timed Text (TT) Working Group.</p>
+      </dd>
+      <dt class="label">Change controller:</dt>
+      <dd>
+        <p>The W3C has change control over this specification.</p>
       </dd>
     </dl>
-  </dd>
-  <dt class="label">Encoding considerations:</dt>
-  <dd>
-    <p>binary</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 in
-    general, it is possible that "application/ttml+xml" may describe content that
-    has security implications beyond those described here. However, TTML does not
-    provide for any sort of active or executable content, and if the processor
-    follows only the normative semantics of the published specification, this
-    content will be outside TTML namespaces and may be ignored. Only in the case
-    where the processor recognizes and processes the additional content, or where
-    further processing of that content is dispatched to other processors, would
-    security issues potentially arise. And in that case, they would fall outside
-    the domain of this registration document.</p>
-    <p>Although not prohibited, there are no expectations that XML signatures or
-    encryption would normally be employed.</p>
-  </dd>
-  <dt class="label">Interoperability considerations:</dt>
-  <dd>
-    <p>The published specification describes processing semantics that dictate
-    behavior that must be followed when dealing with, among other things,
-    unrecognized elements and attributes, both in TTML namespaces and in other
-    namespaces.</p>
-    <p>Because TTML is extensible, conformant "application/ttml+xml" processors may
-    expect (and enforce) that content received is well-formed XML, but it cannot be
-    guaranteed that the content is valid to a particular DTD or Schema or that the
-    processor will recognize all of the elements and attributes in the
-    document.</p>
-  </dd>
-  <dt class="label">Published specification:</dt>
-  <dd>
-    <p>This media type registration is extracted from Appendix C Media Type
-    Registration of the Timed Text Markup Language (TTML) 1.0 specification:
-    <a href="http://www.w3.org/TR/ttml1/">Timed Text Markup Language 1
-    (TTML1)</a>.</p>
-  </dd>
-  <dt class="label">Applications that use this media type:</dt>
-  <dd>
-    <p>TTML is used in the television industry for the purpose of authoring,
-    transcoding and exchanging timed text information and for delivering captions,
-    subtitles, and other metadata for television material repurposed for the Web
-    or, more generally, the Internet.</p>
-    <p>There is partial and full support of TTML in components used by several Web
-    browsers plugins, and in a number of caption authoring tools.</p>
-  </dd>
-  <dt class="label">Additional information:</dt>
-  <dd>
-    <dl>
-      <dt class="label">Magic number(s):</dt>
-      <dt class="label">File extension(s):</dt>
-      <dd>
-        <p>.ttml</p>
-      </dd>
-      <dt class="label">Macintosh file type code(s):</dt>
-      <dd>
-        <p>"TTML"</p>
-      </dd>
-      <dt class="label">Fragment identifiers:</dt>
-      <dd>
-        <p>For documents labeled as application/ttml+xml, the fragment identifier
-        notation is intended to be used with xml:id attributes, as described in
-        section 7.2.1 of the <a href="http://www.w3.org/TR/ttml1/">Timed Text
-        Markup Language 1 (TTML1)</a> specification.</p>
-      </dd>
-    </dl>
-  </dd>
-  <dt class="label">Person &amp; email address to contact for further
-  information:</dt>
-  <dd>
-    <p>Timed Text Working Group ([email protected])</p>
-  </dd>
-  <dt class="label">Intended usage:</dt>
-  <dd>
-    <p>COMMON</p>
-  </dd>
-  <dt class="label">Restrictions on usage:</dt>
-  <dd>
-    <p>None</p>
-  </dd>
-  <dt class="label">Author:</dt>
-  <dd>
-    <p>The published specification is a work product of the World Wide Web
-    Consortium's Timed Text (TT) Working Group.</p>
-  </dd>
-  <dt class="label">Change controller:</dt>
-  <dd>
-    <p>The W3C has change control over this specification.</p>
-  </dd>
-</dl>
-</body>
+    <hr />
+    <p id="errata-M-1"><strong> E03: </strong><a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/#concrete-encoding">Correction
+        in TTML1 Appendix M - Concrete Encoding</a> (published 20 02 2014) </p>
+    <p class="description"><span class="title-description">Description</span>:</p>
+    Add standard XML named character entities unintentionally omitted from note.
+    <p class="description"><em><strong><span class="title-correction">Resolution</span></strong></em>:</p>
+    <p>change &quot;... only the following named character entities are defined:
+    <code>&amp;amp;</code>,
+    <code>&amp;lt;</code>,
+    and <code>&amp;gt;</code>.&quot;
+    </p>
+    <p>to read  &quot;... only the following named character entities are defined:
+    <code>&amp;amp;</code>,
+    <span class="diff-add"><code>&amp;apos;</code>, </span><code>&amp;lt;</code>,
+    <span class="diff-chg"><code>&amp;gt;</code>, and
+    <span class="diff-add"><code>&amp;quot;</code></span></span>.&quot;.
+    </p>
+    <hr />
+  </body>
 </html>