[ttml11] remove appendix C contents; change appendices O and N to normative
authorGlenn Adams <glenn@skynav.com>
Wed, 10 Jul 2013 14:51:20 -0600
changeset 434 c89e51970e16
parent 433 a4fadd196850
child 435 23c764ca4f42
[ttml11] remove appendix C contents; change appendices O and N to normative
ttml11/spec/ttml-changes.html
ttml11/spec/ttml11.xml
ttml11/spec/xmlspec-ttml11.dtd
--- a/ttml11/spec/ttml-changes.html	Wed Jul 10 12:24:29 2013 -0600
+++ b/ttml11/spec/ttml-changes.html	Wed Jul 10 14:51:20 2013 -0600
@@ -39,6 +39,12 @@
   including normative processing semantics.
 * In 6.1.5, add 'prohibited' value to 'value' attribute of ttp:extension element,
   including normative processing semantics.
+* In Appendix C, remove contents for mediate type registration, since registration
+  has (will have) already occurred (by the time TTML11 goes to FPWD).
+* In Appendix O, change appendix designation to normative, effectively changing
+  the informative concrete encoding recommendation to a normative recommendation.
+* In Appendix N, change appendix designation to normative, effectively making
+  the time expression semantics normatively applicable.
 
 </pre>
 </div>
--- a/ttml11/spec/ttml11.xml	Wed Jul 10 12:24:29 2013 -0600
+++ b/ttml11/spec/ttml11.xml	Wed Jul 10 14:51:20 2013 -0600
@@ -6198,7 +6198,8 @@
 </table>
 </div3>
 <div3 id="style-value-duration">
-<head>Deleted</head>
+<head>&lt;duration&gt;</head>
+<p><emph>This section is non-normative.</emph></p>
 <note>
 <p>The information from this section has been removed due to lack of any normative
 use within this specification. This section is retained in its empty form
@@ -6482,7 +6483,8 @@
 </note>
 </div3>
 <div3 id="style-value-quotedString">
-<head>Deleted</head>
+<head>&lt;quotedString&gt;</head>
+<p><emph>This section is non-normative.</emph></p>
 <note>
 <p>The information from this section has been incorporated into
 <specref ref="style-value-familyName"/>. This section is retained in its empty form
@@ -6490,7 +6492,8 @@
 </note>
 </div3>
 <div3 id="style-value-string">
-<head>Deleted</head>
+<head>&lt;string&gt;</head>
+<p><emph>This section is non-normative.</emph></p>
 <note>
 <p>The information from this section has been incorporated into
 <specref ref="style-value-familyName"/>. This section is retained in its empty form
@@ -8698,180 +8701,14 @@
 is defined by <specref ref="conformance-content"/>.</p>
 </div2>
 </div1>
-<div1 id="media-types-registration">
+<inform-div1 id="media-types-registration">
 <head>Media Type Registration</head>
-<p><emph>This appendix is normative.</emph></p>
-<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
-href="http://www.w3.org/2002/06/registering-mediatype.html">W3CRegMedia</loc>.
-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>
-<glist>
-<gitem>
-<label>Type name:</label>
-<def>
-<p>application</p>
-</def>
-</gitem>
-<gitem>
-<label>Subtype name:</label>
-<def>
-<p>ttml+xml</p>
-</def>
-</gitem>
-<gitem>
-<label>Required parameters:</label>
-<def>
-<p>None.</p>
-</def>
-</gitem>
-<gitem>
-<label>Optional parameters:</label>
-<def>
-<glist>
-<gitem>
-<label>charset</label>
-<def>
-<p>If specified, the <code>charset</code> parameter must match the XML encoding declaration, or if absent, the actual encoding.</p>
-</def>
-</gitem>
-<gitem>
-<label>profile</label>
-<def>
-<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
-<att>ttp:profile</att> parameter defined by
-Section
-<specref ref="parameter-attribute-profile"/>
-of the published specification.</p>
-</def>
-</gitem>
-</glist>
-</def>
-</gitem>
-<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>
-</def>
-</gitem>
-<gitem>
-<label>Security considerations:</label>
-<def>
-<p>As with other XML types and as noted in
-<bibref ref="xml-media"/>
-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>
-</def>
-</gitem>
-<gitem>
-<label>Interoperability considerations:</label>
-<def>
-<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>
-<p></p>
-</def>
-</gitem>
-<gitem>
-<label>Published specification:</label>
-<def>
-<p>This media type registration is extracted from Appendix C Media Type
-Registration of the Timed Text Markup Language (TTML) 1.0 specification:
-<loc
-href="http://www.w3.org/TR/ttaf1-dfxp/">Timed Text Markup Language (TTML) 1.0</loc>.</p>
-</def>
-</gitem>
-<gitem>
-<label>Applications that use this media type:</label>
-<def>
-<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>
-</def>
-</gitem>
-<gitem>
-<label>Additional information:</label>
-<def>
-<glist>
-<gitem>
-    <label>Magic number(s):</label>
-    <def></def>
-</gitem>
-<gitem>
-    <label>File extension(s):</label>
-    <def><p>.ttml</p></def>
-</gitem>
-<gitem>
-    <label>Macintosh file type code(s):</label>
-    <def><p>"TTML"</p></def>
-</gitem>
-<gitem>
-<label>Fragment identifiers:</label>
-<def><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 <loc
-href="http://www.w3.org/TR/ttaf1-dfxp/">Timed Text Markup Language (TTML) 1.0</loc> specification.</p></def>
-</gitem>
-</glist>
-</def>
-</gitem>
-<gitem>
-<label>Person &amp; email address to contact for further information:</label>
-<def>
-<p>Timed Text Working Group ([email protected])</p>
-</def>
-</gitem>
-<gitem>
-<label>Intended usage:</label>
-<def>
-<p>COMMON</p>
-</def>
-</gitem>
-<gitem>
-<label>Restrictions on usage:</label>
-<def>
-<p>None</p>
-</def>
-</gitem>
-<gitem>
-<label>Author:</label>
-<def>
-<p>The published specification is a work product of the World Wide Web
-Consortium's Timed Text (TT) Working Group.</p>
-</def>
-</gitem>
-<gitem>
-<label>Change controller:</label>
-<def>
-<p>The W3C has change control over this specification.</p>
-</def>
-</gitem>
-</glist>
-</div1>
+<note>
+<p>The information from this appendix has been removed since media type
+registration has already occurred. This section is retained in its empty form
+in order to prevent appendix renumbering.</p>
+</note>
+</inform-div1>
 <div1 id="features">
 <head>Features</head>
 <p><emph>This appendix is normative.</emph></p>
@@ -13166,17 +13003,16 @@
 capabilities model.</p>
 </note>
 </inform-div1>
-<inform-div1 id="concrete-encoding">
+<div1 id="concrete-encoding">
 <head>Concrete Encoding</head>
-<p>In the absence of other requirements, it is recommended that a <emph>Document Instance</emph> be concretely encoded as a
+<p><emph>This appendix is normative.</emph></p>
+<p>In the absence of other requirements, a <emph>Document Instance</emph> should be concretely encoded as a
 well-formed XML 1.0 <bibref ref="xml10"/> document using the UTF-8 character encoding.</p>
-</inform-div1>
-<inform-div1 id="time-expression-semantics">
+</div1>
+<div1 id="time-expression-semantics">
 <head>Time Expression Semantics</head>
-<p>This appendix describes the intended semantics for interpreting time expressions in <emph>Document Instances</emph>.</p>
-<note role="elaboration">
-<p>It is expected that the information in this appendix will be elevated to normative status in a future revision of this specification.</p>
-</note>
+<p><emph>This appendix is normative.</emph></p>
+<p>This appendix specifies the semantics for interpreting time expressions in <emph>Document Instances</emph>.</p>
 <note role="clarification">
 <p>The phrase <emph>local real time</emph> as used below is intended to model a virtual real time clock in the document processing context, where
 <emph>local</emph> means in the immediate proximity of the implementation of this processing context. The intent
@@ -13190,7 +13026,7 @@
 </note>
 <div2 id="time-expression-semantics-clock">
 <head>Clock Time Base</head>
-<p>When operating with the <code>clock</code> time base, the following semantics should be applied for interpreting time expressions,
+<p>When operating with the <code>clock</code> time base, the following semantics apply for interpreting time expressions,
 as defined by <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>, and their relationship to media time and local real time.</p>
 <p>The clock time base <phrase role="strong"><code>C</code></phrase> is related to local real time <phrase role="strong"><code>R</code></phrase>
 expressed in an arbitrary (implementation defined) epoch <phrase role="strong"><code>E</code></phrase>
@@ -13315,7 +13151,7 @@
 </div2>
 <div2 id="time-expression-semantics-media">
 <head>Media Time Base</head>
-<p>When operating with the <code>media</code> time base, the following semantics should be applied for interpreting time expressions,
+<p>When operating with the <code>media</code> time base, the following semantics apply for interpreting time expressions,
 as defined by <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>, and their relationship to media time and local real time.</p>
 <p>The media time base <phrase role="strong"><code>M</code></phrase> is related to local real time <phrase role="strong"><code>R</code></phrase>
 expressed in an arbitrary (implementation defined) epoch <phrase role="strong"><code>E</code></phrase> as follows:</p>
@@ -13431,7 +13267,7 @@
 </div2>
 <div2 id="time-expression-semantics-smpte">
 <head>SMPTE Time Base</head>
-<p>When operating with the <code>smpte</code> time base, the following semantics should be applied for interpreting time expressions,
+<p>When operating with the <code>smpte</code> time base, the following semantics apply for interpreting time expressions,
 as defined by <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>, and their relationship to media time and local real time.</p>
 <p>If the computed value of the <att>ttp:markerMode</att> parameter is <code>discontinuous</code>, then there is no direct relationship between
 time expressions and media time <phrase role="strong"><code>M</code></phrase> or local real time <phrase role="strong"><code>R</code></phrase>. In
@@ -13502,7 +13338,7 @@
 <sitem>
 Notwithstanding the above, if a time expression contains a frame code that is designated as
 dropped according to <specref ref="parameter-attribute-dropMode"/>, then that time expression
-should be considered to be invalid for purposes of validation assessment.
+must be considered to be invalid for purposes of validation assessment.
 </sitem>
 <sitem/>
 </slist>
@@ -13541,7 +13377,7 @@
 media time base <phrase role="strong"><code>M</code></phrase> is related to the local real time <phrase role="strong"><code>R</code></phrase>
 as described in <specref ref="time-expression-semantics-media"/> above.</p>
 </div2>
-</inform-div1>
+</div1>
 <inform-div1 id="common-styling">
 <head>Common Caption Style Examples</head>
 <p>This section provides examples of the following common caption styles using TTML Content
--- a/ttml11/spec/xmlspec-ttml11.dtd	Wed Jul 10 12:24:29 2013 -0600
+++ b/ttml11/spec/xmlspec-ttml11.dtd	Wed Jul 10 14:51:20 2013 -0600
@@ -23,6 +23,7 @@
 	"#PCDATA|loc|ednote|phrase|rfc2119|sub|sup">
 
 <!-- element definition ignores -->
+<!ENTITY % back.element "IGNORE">
 <!ENTITY % loc.element "IGNORE">
 
 <!-- xmlspec inclusion -->
@@ -30,4 +31,5 @@
 %xmlspec;
 
 <!-- element definition overrides -->
+<!ELEMENT back (div1|inform-div1)+>
 <!ELEMENT loc (#PCDATA|phrase|el|att|code|emph)*>