Mercurial > hg > ttml / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset
[ttml2] regenerate ED
authorGlenn Adams <glenn@skynav.com>
Sun, 21 Sep 2014 06:37:31 -0600
changeset 709 de8b1226492a
parent 708 3cbc109b90bd
child 710 86641164a28a
[ttml2] regenerate ED
ttml2/spec/ttml2.html 
--- a/ttml2/spec/ttml2.html	Sun Sep 21 06:37:21 2014 -0600
+++ b/ttml2/spec/ttml2.html	Sun Sep 21 06:37:31 2014 -0600
@@ -82,9 +82,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: 2014/09/21 10:40:49 $<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: 2014/09/21 12:37:21 $<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: 2014/09/21 10:40:49 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/09/21 12:37:21 $ @@ @@@@ @@@@</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>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>
@@ -152,18 +152,20 @@
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.8 <a href="#parameter-attribute-inferProcessorProfileMethod">ttp:inferProcessorProfileMethod</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.9 <a href="#parameter-attribute-inferProcessorProfileSource">ttp:inferProcessorProfileSource</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.10 <a href="#parameter-attribute-markerMode">ttp:markerMode</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.11 <a href="#parameter-attribute-permitFeatureNarrowing">ttp:permitFeatureNarrowing</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.12 <a href="#parameter-attribute-permitFeatureWidening">ttp:permitFeatureWidening</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.13 <a href="#parameter-attribute-pixelAspectRatio">ttp:pixelAspectRatio</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.14 <a href="#parameter-attribute-profile">ttp:profile</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.15 <a href="#parameter-attribute-processorProfiles">ttp:processorProfiles</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.16 <a href="#parameter-attribute-processorProfileCombination">ttp:processorProfileCombination</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.17 <a href="#parameter-attribute-subFrameRate">ttp:subFrameRate</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.18 <a href="#parameter-attribute-tickRate">ttp:tickRate</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.19 <a href="#parameter-attribute-timeBase">ttp:timeBase</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.20 <a href="#parameter-attribute-validation">ttp:validation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.21 <a href="#parameter-attribute-validationAction">ttp:validationAction</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.22 <a href="#parameter-attribute-version">ttp:version</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.11 <a href="#parameter-attribute-mediaDuration">ttp:mediaDuration</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.12 <a href="#parameter-attribute-mediaOffset">ttp:mediaOffset</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.13 <a href="#parameter-attribute-permitFeatureNarrowing">ttp:permitFeatureNarrowing</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.14 <a href="#parameter-attribute-permitFeatureWidening">ttp:permitFeatureWidening</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.15 <a href="#parameter-attribute-pixelAspectRatio">ttp:pixelAspectRatio</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.16 <a href="#parameter-attribute-profile">ttp:profile</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.17 <a href="#parameter-attribute-processorProfiles">ttp:processorProfiles</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.18 <a href="#parameter-attribute-processorProfileCombination">ttp:processorProfileCombination</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.19 <a href="#parameter-attribute-subFrameRate">ttp:subFrameRate</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.20 <a href="#parameter-attribute-tickRate">ttp:tickRate</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.21 <a href="#parameter-attribute-timeBase">ttp:timeBase</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.22 <a href="#parameter-attribute-validation">ttp:validation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.23 <a href="#parameter-attribute-validationAction">ttp:validationAction</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.2.24 <a href="#parameter-attribute-version">ttp:version</a><br>
 7 <a href="#content">Content</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#content-element-vocabulary">Content Element Vocabulary</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.1.1 <a href="#document-structure-vocabulary-tt">tt</a><br>
@@ -438,11 +440,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>
-&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e26194">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e26711">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e26375">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e26892">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e27704">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e27868">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e27885">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e28049">Guidelines</a><br>
 L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
 M <a href="#concrete-encoding">Concrete Encoding</a><br>
 N <a href="#time-expression-semantics">Time Expression Semantics</a><br>
@@ -904,7 +906,7 @@
 a <code>ttp:profile</code> attribute on its root
 <code>tt</code>
 element
-as defined by <a href="#parameter-attribute-profile"><b>6.2.14 ttp:profile</b></a>
+as defined by <a href="#parameter-attribute-profile"><b>6.2.16 ttp:profile</b></a>
 or (2)
 a <code>ttp:profile</code> element as a child of the
 <code>head</code> element as defined by
@@ -1305,6 +1307,8 @@
 <a href="#parameter-attribute-inferProcessorProfileMethod">ttp:inferProcessorProfileMethod</a>,
 <a href="#parameter-attribute-inferProcessorProfileSource">ttp:inferProcessorProfileSource</a>,
 <a href="#parameter-attribute-markerMode">ttp:markerMode</a>,
+<a href="#parameter-attribute-mediaDuration">ttp:mediaDuration</a>,
+<a href="#parameter-attribute-mediaOffset">ttp:mediaOffset</a>,
 <a href="#parameter-attribute-permitFeatureNarrowing">ttp:permitFeatureNarrowing</a>,
 <a href="#parameter-attribute-permitFeatureWidening">ttp:permitFeatureWidening</a>,
 <a href="#parameter-attribute-pixelAspectRatio">ttp:pixelAspectRatio</a>,
@@ -1778,7 +1782,7 @@
 defined in a third party namespace.</p><p>The effect of this example is to express authorial intentions that
 a recipient processor must support the TTML transformation profile and
 must also support and enable an extension defined by a third party.</p></div></div></div><div class="div2">
-<h3><a id="parameter-attribute-vocabulary"></a>6.2 Parameter Attribute Vocabulary</h3><p>The following attributes are defined in the TT Parameter Namespace.</p><ul><li><p><a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a></p></li><li><p><a href="#parameter-attribute-clockMode"><b>6.2.2 ttp:clockMode</b></a></p></li><li><p><a href="#parameter-attribute-contentProfiles"><b>6.2.3 ttp:contentProfiles</b></a></p></li><li><p><a href="#parameter-attribute-contentProfileCombination"><b>6.2.4 ttp:contentProfileCombination</b></a></p></li><li><p><a href="#parameter-attribute-dropMode"><b>6.2.5 ttp:dropMode</b></a></p></li><li><p><a href="#parameter-attribute-frameRate"><b>6.2.6 ttp:frameRate</b></a></p></li><li><p><a href="#parameter-attribute-frameRateMultiplier"><b>6.2.7 ttp:frameRateMultiplier</b></a></p></li><li><p><a href="#parameter-attribute-inferProcessorProfileMethod"><b>6.2.8 ttp:inferProcessorProfileMethod</b></a></p></li><li><p><a href="#parameter-attribute-inferProcessorProfileSource"><b>6.2.9 ttp:inferProcessorProfileSource</b></a></p></li><li><p><a href="#parameter-attribute-markerMode"><b>6.2.10 ttp:markerMode</b></a></p></li><li><p><a href="#parameter-attribute-permitFeatureNarrowing"><b>6.2.11 ttp:permitFeatureNarrowing</b></a></p></li><li><p><a href="#parameter-attribute-permitFeatureWidening"><b>6.2.12 ttp:permitFeatureWidening</b></a></p></li><li><p><a href="#parameter-attribute-pixelAspectRatio"><b>6.2.13 ttp:pixelAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-profile"><b>6.2.14 ttp:profile</b></a></p></li><li><p><a href="#parameter-attribute-processorProfiles"><b>6.2.15 ttp:processorProfiles</b></a></p></li><li><p><a href="#parameter-attribute-processorProfileCombination"><b>6.2.16 ttp:processorProfileCombination</b></a></p></li><li><p><a href="#parameter-attribute-subFrameRate"><b>6.2.17 ttp:subFrameRate</b></a></p></li><li><p><a href="#parameter-attribute-tickRate"><b>6.2.18 ttp:tickRate</b></a></p></li><li><p><a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a></p></li><li><p><a href="#parameter-attribute-validation"><b>6.2.20 ttp:validation</b></a></p></li><li><p><a href="#parameter-attribute-validationAction"><b>6.2.21 ttp:validationAction</b></a></p></li><li><p><a href="#parameter-attribute-version"><b>6.2.22 ttp:version</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) must
+<h3><a id="parameter-attribute-vocabulary"></a>6.2 Parameter Attribute Vocabulary</h3><p>The following attributes are defined in the TT Parameter Namespace.</p><ul><li><p><a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a></p></li><li><p><a href="#parameter-attribute-clockMode"><b>6.2.2 ttp:clockMode</b></a></p></li><li><p><a href="#parameter-attribute-contentProfiles"><b>6.2.3 ttp:contentProfiles</b></a></p></li><li><p><a href="#parameter-attribute-contentProfileCombination"><b>6.2.4 ttp:contentProfileCombination</b></a></p></li><li><p><a href="#parameter-attribute-dropMode"><b>6.2.5 ttp:dropMode</b></a></p></li><li><p><a href="#parameter-attribute-frameRate"><b>6.2.6 ttp:frameRate</b></a></p></li><li><p><a href="#parameter-attribute-frameRateMultiplier"><b>6.2.7 ttp:frameRateMultiplier</b></a></p></li><li><p><a href="#parameter-attribute-inferProcessorProfileMethod"><b>6.2.8 ttp:inferProcessorProfileMethod</b></a></p></li><li><p><a href="#parameter-attribute-inferProcessorProfileSource"><b>6.2.9 ttp:inferProcessorProfileSource</b></a></p></li><li><p><a href="#parameter-attribute-markerMode"><b>6.2.10 ttp:markerMode</b></a></p></li><li><p><a href="#parameter-attribute-mediaDuration"><b>6.2.11 ttp:mediaDuration</b></a></p></li><li><p><a href="#parameter-attribute-mediaOffset"><b>6.2.12 ttp:mediaOffset</b></a></p></li><li><p><a href="#parameter-attribute-permitFeatureNarrowing"><b>6.2.13 ttp:permitFeatureNarrowing</b></a></p></li><li><p><a href="#parameter-attribute-permitFeatureWidening"><b>6.2.14 ttp:permitFeatureWidening</b></a></p></li><li><p><a href="#parameter-attribute-pixelAspectRatio"><b>6.2.15 ttp:pixelAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-profile"><b>6.2.16 ttp:profile</b></a></p></li><li><p><a href="#parameter-attribute-processorProfiles"><b>6.2.17 ttp:processorProfiles</b></a></p></li><li><p><a href="#parameter-attribute-processorProfileCombination"><b>6.2.18 ttp:processorProfileCombination</b></a></p></li><li><p><a href="#parameter-attribute-subFrameRate"><b>6.2.19 ttp:subFrameRate</b></a></p></li><li><p><a href="#parameter-attribute-tickRate"><b>6.2.20 ttp:tickRate</b></a></p></li><li><p><a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a></p></li><li><p><a href="#parameter-attribute-validation"><b>6.2.22 ttp:validation</b></a></p></li><li><p><a href="#parameter-attribute-validationAction"><b>6.2.23 ttp:validationAction</b></a></p></li><li><p><a href="#parameter-attribute-version"><b>6.2.24 ttp:version</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) must
 appear between adjacent non-terminal components of a TT Parameter value
 unless some other delimiter is permitted and used.</p><div class="div3">
 <h4><a id="parameter-attribute-cellResolution"></a>6.2.1 ttp:cellResolution</h4><p>The <code>ttp:cellResolution</code> attribute may be used by an author
@@ -1809,7 +1813,7 @@
 before and after padding will be (480 / 10) * 0.1 pixels.</p></div></div><div class="div3">
 <h4><a id="parameter-attribute-clockMode"></a>6.2.2 ttp:clockMode</h4><p>The <code>ttp:clockMode</code> attribute is used to specify the
 interpretation of time expressions as real-time time coordinates when
-operating with time base of <code>clock</code> as defined by <a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#timing-time-value-expressions"><b>10.3 Time Value Expressions</b></a> for the
+operating with time base of <code>clock</code> as defined by <a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#timing-time-value-expressions"><b>10.3 Time Value Expressions</b></a> for the
 specification of time expression syntax and semantics.</p></div><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-clockMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:clockMode</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:clockMode
@@ -1817,7 +1821,7 @@
   | "gps"
   | "utc"
 </pre></div>
-</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a>, is designated as
+</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a>, is designated as
 <code>clock</code>, then this parameter applies as follows: if the
 parameter's value is <code>local</code>, then time expressions are
 interpreted as local wall-clock time coordinates;
@@ -1882,14 +1886,14 @@
 constraints on the interpretation and use of frame counts
 that correspond with <a href="#smpte12m">[SMPTE 12M]</a> time coordinates when operating
 with time base of <code>smpte</code> as defined by
-<a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-dropMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:dropMode</caption><tbody><tr><td>
+<a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-dropMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:dropMode</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:dropMode
   : "dropNTSC"
   | "dropPAL"
   | "nonDrop"
 </pre></div>
-</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a>, is designated as
+</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a>, is designated as
 <code>smpte</code>, then this parameter applies as follows: if the
 parameter's value is <code>nonDrop</code>, then, within any given
 second of a time expression, frames count from 0 to
@@ -2010,7 +2014,7 @@
 constraints on the interpretation and use of time expressions
 that correspond with <a href="#smpte12m">[SMPTE 12M]</a> time coordinates when operating
 with time base of <code>smpte</code> as defined by
-<a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a>.</p><p>If specified and support for neither <code>#markerMode</code> nor <code>#markerMode-continuous</code> feature
+<a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a>.</p><p>If specified and support for neither <code>#markerMode</code> nor <code>#markerMode-continuous</code> feature
 is required by a document's <a href="#terms-effective-processor-profile">effective processor profile</a>,
 then the specified value must be ignored and the value <code>discontinuous</code> applied.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-markerMode-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:markerMode</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2018,7 +2022,7 @@
   : "continuous"
   | "discontinuous"
 </pre></div>
-</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a>, is designated as
+</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a>, is designated as
 <code>smpte</code>, then this parameter applies as follows: if the
 parameter's value is <code>continuous</code>, then <a href="#smpte12m">[SMPTE 12M]</a> time coordinates
 may be assumed to be linear and either monotonically increasing or
@@ -2077,7 +2081,48 @@
 example, two consecutive frames labeled as <code>10:00:00:00</code>
 and <code>10:00:01:00</code>.
 </p></div></div><div class="div3">
-<h4><a id="parameter-attribute-permitFeatureNarrowing"></a>6.2.11 ttp:permitFeatureNarrowing</h4><p>The <code>ttp:permitFeatureNarrowing</code> attribute is used to specify whether
+<h4><a id="parameter-attribute-mediaDuration"></a>6.2.11 ttp:mediaDuration</h4><p>The <code>ttp:mediaDuration</code> attribute is used to specify the
+temporal extent (simple duration) of a <a href="#terms-related-media-object">related media object</a>.</p><p>If the temporal extent (simple duration) of the <a href="#terms-related-media-object">related media object</a> is known at authoring time, then this
+attribute should be specified; otherwise, if no <a href="#terms-related-media-object">related media object</a> applies or its
+temporal extent is unknown, then this attribute should not be specified.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-mediaDuration-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:mediaDuration</caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+ttp:mediaDuration
+  : <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>                        // restricted to <em>offset-time</em> form
+  | "indefinite"
+</pre></div>
+</td></tr></tbody></table><p>If specified, the value of this parameter must either (1) adhere to the <em>offset-time</em> form of
+a <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a> or (2) take the value <code>indefinite</code>.</p><p>If the value <code>indefinite</code> is specified, then there is no <a href="#terms-related-media-object">related media object</a>,
+the temporal extent (simple duration) of the
+<a href="#terms-related-media-object">related media object</a> is not known at the time this attribute is
+encoded, or the <a href="#terms-related-media-object">related media object</a> has no temporal end point.</p><p>If not specified, the value of this parameter must be considered
+to be <code>indefinite</code>.</p><p>A <code>ttp:mediaDuration</code> attribute is considered to be significant only
+when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#timing-time-value-expressions"><b>10.3 Time Value Expressions</b></a> for the
+specification of time expression syntax and semantics.</p></div></div><div class="div3">
+<h4><a id="parameter-attribute-mediaOffset"></a>6.2.12 ttp:mediaOffset</h4><p>The <code>ttp:mediaOffset</code> attribute is used to specify the
+temporal offset between the begin time of the <a href="#terms-root-temporal-extent">root temporal extent</a>
+and the begin time of a <a href="#terms-related-media-object">related media object</a> when operating in a
+<a href="#time-expression-semantics-media">Media Time Base</a>
+or a <a href="#time-expression-semantics-smpte">SMPTE Time Base</a>. It does not apply and
+must not be specified when operating in a <a href="#time-expression-semantics-clock">Clock Time Base</a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-mediaOffset-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:mediaOffset</caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+ttp:mediaOffset
+  : sign? <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>                  // restricted to <em>offset-time</em> form
+
+sign
+  : "+" | "-"
+</pre></div>
+</td></tr></tbody></table><p>If specified, the value of this parameter must adhere to the <em>offset-time</em> form of
+a <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a> optionally expressed with a sign.
+If not specified, the value of this parameter must be considered
+to be <code>0s</code>.</p><p>If no sign is specified or it is specified as <code>+</code>, then the begin time of the
+<a href="#terms-root-temporal-extent">root temporal extent</a> follows the begin time of the
+<a href="#terms-related-media-object">related media object</a>; otherwise (sign is present and
+specified as <code>-</code>), the begin time of the
+<a href="#terms-root-temporal-extent">root temporal extent</a> precedes the begin time of the
+<a href="#terms-related-media-object">related media object</a>.</p><p>A <code>ttp:mediaOffset</code> attribute is considered to be significant only
+when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#timing-time-value-expressions"><b>10.3 Time Value Expressions</b></a> for the
+specification of time expression syntax and semantics.</p></div></div><div class="div3">
+<h4><a id="parameter-attribute-permitFeatureNarrowing"></a>6.2.13 ttp:permitFeatureNarrowing</h4><p>The <code>ttp:permitFeatureNarrowing</code> attribute is used to specify whether
 requirements related to a feature or extension may be satisfied by a (syntactically or semantically) narrower interpretation
 of the feature or extension.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-permitFeatureNarrowing-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:permitFeatureNarrowing</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2090,7 +2135,7 @@
 by a more narrowly defined feature or extension specified by an <code>extends</code> attribute.</p><p>If not specified, the value of this parameter must be considered
 to be <code>false</code>.</p><p>A <code>ttp:permitFeatureNarrowing</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-permitFeatureWidening"></a>6.2.12 ttp:permitFeatureWidening</h4><p>The <code>ttp:permitFeatureWidening</code> attribute is used to specify whether
+<h4><a id="parameter-attribute-permitFeatureWidening"></a>6.2.14 ttp:permitFeatureWidening</h4><p>The <code>ttp:permitFeatureWidening</code> attribute is used to specify whether
 requirements related to a feature or extension may be satisfied by a (syntactically or semantically) wider interpretation
 of the feature or extension.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-permitFeatureWidening-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:permitFeatureWidening</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2103,7 +2148,7 @@
 by a more widely defined feature or extension specified by an <code>restricts</code> attribute.</p><p>If not specified, the value of this parameter must be considered
 to be <code>false</code>.</p><p>A <code>ttp:permitFeatureWidening</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-pixelAspectRatio"></a>6.2.13 ttp:pixelAspectRatio</h4><p>The <code>ttp:pixelAspectRatio</code> attribute may be used by a content author
+<h4><a id="parameter-attribute-pixelAspectRatio"></a>6.2.15 ttp:pixelAspectRatio</h4><p>The <code>ttp:pixelAspectRatio</code> attribute may be used by a content author
 to express the aspect ratio of non-square pixels in the production of content that
 makes use of pixel coordinates.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-pixelAspectRatio-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:pixelAspectRatio</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2118,9 +2163,9 @@
 when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This parameter may be used by a content transcoder or translator in
 order to convert pixel measurements between different pixel aspect
 ratios while still maintaining authorial layout intentions.</p></div></div><div class="div3">
-<h4><a id="parameter-attribute-profile"></a>6.2.14 ttp:profile</h4><p>The <code>ttp:profile</code> attribute is <span class="deprecated">deprecated</span>. If creating a TTML document instance for TTML2 (or later versions),
+<h4><a id="parameter-attribute-profile"></a>6.2.16 ttp:profile</h4><p>The <code>ttp:profile</code> attribute is <span class="deprecated">deprecated</span>. If creating a TTML document instance for TTML2 (or later versions),
 then the <code>ttp:profile</code> attribute should not be used; instead, the content author should use the <code>ttp:processorProfiles</code>
-attribute, specified at <a href="#parameter-attribute-processorProfiles"><b>6.2.15 ttp:processorProfiles</b></a>.</p><p>If used in a document, the <code>ttp:profile</code> attribute
+attribute, specified at <a href="#parameter-attribute-processorProfiles"><b>6.2.17 ttp:processorProfiles</b></a>.</p><p>If used in a document, the <code>ttp:profile</code> attribute
 denotes a <a href="#terms-processor-profile">processor profile</a>
 of the Timed Text Markup Language (TTML) that applies when processing
 a <a href="#terms-document-instance">document instance</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>For information on signaling content profile(s), see <a href="#parameter-attribute-contentProfiles"><b>6.2.3 ttp:contentProfiles</b></a>.</p></div><p>If specified, the value of this attribute must adhere to the following syntax
@@ -2142,7 +2187,7 @@
 is defined in a <a href="#terms-document-instance">document instance</a>, then the
 <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
 attribute should not be specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-processorProfiles"></a>6.2.15 ttp:processorProfiles</h4><p>The <code>ttp:processorProfiles</code> attribute may be used by a content author
+<h4><a id="parameter-attribute-processorProfiles"></a>6.2.17 ttp:processorProfiles</h4><p>The <code>ttp:processorProfiles</code> attribute may be used by a content author
 to express one or more <a href="#terms-processor-profile">processor profiles</a> of
 the Timed Text Markup Language (TTML) where the
 <a href="#terms-enclosing-document-instance">enclosing document instance</a> requires support for each and all
@@ -2171,7 +2216,7 @@
 of the designated <a href="#terms-processor-profile">processor profiles</a>.</p><p>A <code>ttp:processorProfiles</code>
 attribute is considered to be significant only when specified on the
 <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-processorProfileCombination"></a>6.2.16 ttp:processorProfileCombination</h4><p>The <code>ttp:processorProfileCombination</code> attribute is used to specify the
+<h4><a id="parameter-attribute-processorProfileCombination"></a>6.2.18 ttp:processorProfileCombination</h4><p>The <code>ttp:processorProfileCombination</code> attribute is used to specify the
 method for combining multiple <a href="#terms-processor-profile">processor profiles</a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-processorProfileCombination-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:processorProfileCombination</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 ttp:processorProfileCombination
@@ -2184,7 +2229,7 @@
 of arguments is determined in accordance with the lexical order of
 <a href="#terms-processor-profile">processor profiles</a> in a <a href="#terms-document-instance">document instance</a>.</p><a id="processor-profile-combination-table"></a><table class="common"><caption>Table 6-3 – Processor Profile Combination</caption><col width="16.67%" span="1"><col width="16.67%" span="1"><col width="22%" span="1"><col width="22%" span="1"><col width="22%" span="1"><tbody><tr><th><em>arg1</em></th><th><em>arg2</em></th><th><code>leastRestrictive</code></th><th><code>mostRestrictive</code></th><th><code>replace</code></th></tr><tr><td>optional</td><td>optional</td><td>optional</td><td>optional</td><td>optional</td></tr><tr><td>optional</td><td>required</td><td>optional</td><td>required</td><td>required</td></tr><tr><td>required</td><td>optional</td><td>optional</td><td>required</td><td>optional</td></tr><tr><td>required</td><td>required</td><td>required</td><td>required</td><td>required</td></tr></tbody></table><p>A <code>ttp:processorProfileCombination</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-subFrameRate"></a>6.2.17 ttp:subFrameRate</h4><p>The <code>ttp:subFrameRate</code> attribute is used to specify the sub-frame rate of a related
+<h4><a id="parameter-attribute-subFrameRate"></a>6.2.19 ttp:subFrameRate</h4><p>The <code>ttp:subFrameRate</code> attribute is used to specify the sub-frame rate of a related
 media object or the intrinsic sub-frame rate of a <a href="#terms-document-instance">document instance</a> in case it is intended
 to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-subFrameRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:subFrameRate</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2203,7 +2248,7 @@
 equal to one (1). If specified, then the sub-frame rate must be greater than zero (0).</p><p>A <code>ttp:subFrameRate</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The sub-frame is sometimes referred to as a <em>field</em> in
 the context of synchronization with an interlaced video media object.</p></div></div><div class="div3">
-<h4><a id="parameter-attribute-tickRate"></a>6.2.18 ttp:tickRate</h4><p>The <code>ttp:tickRate</code> attribute is used to specify the tick rate of a related
+<h4><a id="parameter-attribute-tickRate"></a>6.2.20 ttp:tickRate</h4><p>The <code>ttp:tickRate</code> attribute is used to specify the tick rate of a related
 media object or the intrinsic tick rate of content of a <a href="#terms-document-instance">document instance</a> in case it is intended
 to function as an independent media object.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-tickRate-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:tickRate</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2228,7 +2273,7 @@
 use of fixed point arithmetic rather than fractional (and potentially
 inexact) expressions of seconds.</p></div><p>A <code>ttp:tickRate</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-timeBase"></a>6.2.19 ttp:timeBase</h4><p>The <code>ttp:timeBase</code> attribute is used to specify the
+<h4><a id="parameter-attribute-timeBase"></a>6.2.21 ttp:timeBase</h4><p>The <code>ttp:timeBase</code> attribute is used to specify the
 temporal coordinate system by means of which time expressions are
 interpreted in a <a href="#terms-document-instance">document instance</a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-timeBase-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:timeBase</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2274,7 +2319,7 @@
 given <a href="#terms-document-instance">document instance</a>, the interpretation of time expressions
 is uniform throughout the <a href="#terms-document-instance">document instance</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#time-expression-semantics"><b>N Time Expression Semantics</b></a> for further details
 on the interpretation of time expressions according to the designated time base.</p></div></div><div class="div3">
-<h4><a id="parameter-attribute-validation"></a>6.2.20 ttp:validation</h4><p>The <code>ttp:validation</code> attribute is used to specify whether validation processing
+<h4><a id="parameter-attribute-validation"></a>6.2.22 ttp:validation</h4><p>The <code>ttp:validation</code> attribute is used to specify whether validation processing
 may or must be performed on a <a href="#terms-document-instance">document instance</a> by a
 <a href="#terms-validating-content-processor">validating content processor</a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-validation-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:validation</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2293,7 +2338,7 @@
 the <code>ttp:validationAction</code> parameter property is used to determine what action to take before performing further processing.</p><p>If not specified, the value of this parameter must be considered
 to be <code>optional</code>.</p><p>A <code>ttp:validation</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-validationAction"></a>6.2.21 ttp:validationAction</h4><p>The <code>ttp:validationAction</code> attribute is used to specify what action is to be taken
+<h4><a id="parameter-attribute-validationAction"></a>6.2.23 ttp:validationAction</h4><p>The <code>ttp:validationAction</code> attribute is used to specify what action is to be taken
 by a <a href="#terms-validating-content-processor">validating content processor</a> when
 validation of a <a href="#terms-document-instance">document instance</a> fails.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-validationAction-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:validationAction</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -2313,7 +2358,7 @@
 otherwise, if it is <code>prohibited</code>,
 then the value must be considered to be <code>ignore</code>.</p><p>A <code>ttp:validationAction</code> attribute is considered to be significant only
 when specified on the <code>tt</code> element.</p></div><div class="div3">
-<h4><a id="parameter-attribute-version"></a>6.2.22 ttp:version</h4><p>The <code>ttp:version</code> attribute is used to specify which version of the
+<h4><a id="parameter-attribute-version"></a>6.2.24 ttp:version</h4><p>The <code>ttp:version</code> attribute is used to specify which version of the
 <a href="#terms-timed-text-markup-language">Timed Text Markup Language</a>
 specification was used in authoring a TTML <a href="#terms-document-instance">document instance</a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-version-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:version</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -5475,9 +5520,9 @@
 <code>ttp:timeBase</code> parameter, and where the semantics defined
 by <a href="#time-expression-semantics"><b>N Time Expression Semantics</b></a> apply.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See
 <a href="#parameter-attribute-frameRate"><b>6.2.6 ttp:frameRate</b></a>,
-<a href="#parameter-attribute-subFrameRate"><b>6.2.17 ttp:subFrameRate</b></a>,
-<a href="#parameter-attribute-tickRate"><b>6.2.18 ttp:tickRate</b></a>, and
-<a href="#parameter-attribute-timeBase"><b>6.2.19 ttp:timeBase</b></a> for further information on
+<a href="#parameter-attribute-subFrameRate"><b>6.2.19 ttp:subFrameRate</b></a>,
+<a href="#parameter-attribute-tickRate"><b>6.2.20 ttp:tickRate</b></a>, and
+<a href="#parameter-attribute-timeBase"><b>6.2.21 ttp:timeBase</b></a> for further information on
 explicit specification of frame rate, sub-frame rate, tick rate, and time base.</p></div><a id="timeExpression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;timeExpression&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;timeExpression&gt;
@@ -5533,7 +5578,7 @@
 <em>clock-time</em> and a <em>sub-frames</em> term is
 specified, then the value of this term must be constrained to the
 interval [0…<em>S-1</em>], where <em>S</em> is the
-sub-frame rate determined by the <code>ttp:subFrameRate</code> parameter as defined by <a href="#parameter-attribute-subFrameRate"><b>6.2.17 ttp:subFrameRate</b></a>.
+sub-frame rate determined by the <code>ttp:subFrameRate</code> parameter as defined by <a href="#parameter-attribute-subFrameRate"><b>6.2.19 ttp:subFrameRate</b></a>.
 It is considered an error if a <em>sub-frames</em> term is specified
 when the <code>clock</code> time base applies.</p></div></div><div class="div2">
 <h3><a id="timing-time-intervals"></a>10.4 Time Intervals</h3><p>The semantics of time containment, durations, and intervals defined by
@@ -7772,7 +7817,7 @@
 <h2><a id="derivation"></a>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 id="d3e26194"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
+<h3><a id="d3e26375"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-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
@@ -7829,7 +7874,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="d3e26711"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
+<h3><a id="d3e26892"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-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
@@ -7921,9 +7966,9 @@
 <h2><a id="qa"></a>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>&nbsp;<a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e27704"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-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="d3e27885"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-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="d3e27868"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-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-profiles">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="d3e28049"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-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-profiles">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>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
 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">
@@ -8068,8 +8113,9 @@
 <br><br>
 and <code>tickRate</code> is the computed value of the <code>ttp:tickRate</code> parameter;
 <br></p></blockquote>
-</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If the computed <code>frameRateMultipler</code> ratio is not integral, then <code>effectiveFrameRate</code> will be a non-integral rational.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The above formalisms assumes that the <a href="#terms-root-temporal-extent">root temporal extent</a> corresponds with the beginning of a related media object. If
-this assumption doesn't hold, then an additional offset that accounts for the difference may be introduced when computing media time <code>M</code>.</p></div></div><div class="div2">
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If the computed <code>frameRateMultipler</code> ratio is not integral, then <code>effectiveFrameRate</code> will be a non-integral rational.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The begin time of the <a href="#terms-root-temporal-extent">root temporal extent</a> is related to the begin time of a
+<a href="#terms-related-media-object">related media object</a> in accordance with the computed value of the
+<a href="#parameter-attribute-mediaOffset"><code>ttp:mediaOffset</code></a> parameter property.</p></div></div><div class="div2">
 <h3><a id="time-expression-semantics-smpte"></a>N.3 SMPTE Time Base</h3><p>When operating with the <code>smpte</code> time base, the following semantics apply for interpreting time expressions,
 as defined by <a href="#timing-value-timeExpression">&lt;timeExpression&gt;</a>, and their relationship to media time and local real time.</p><p>If the computed value of the <code>ttp:markerMode</code> parameter is <code>discontinuous</code>, then there is no direct relationship between
 time expressions and media time <span class="strong"><code>M</code></span> or local real time <span class="strong"><code>R</code></span>. In
@@ -8125,7 +8171,9 @@
 <br></p></blockquote>
 </td></tr></tbody></table><p>Given the derived media time base as described above, then 
 media time base <span class="strong"><code>M</code></span> is related to the local real time <span class="strong"><code>R</code></span>
-as described in <a href="#time-expression-semantics-media"><b>N.2 Media Time Base</b></a> above.</p></div></div><div class="div1">
+as described in <a href="#time-expression-semantics-media"><b>N.2 Media Time Base</b></a> above.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The begin time of the <a href="#terms-root-temporal-extent">root temporal extent</a> is related to the begin time of a
+<a href="#terms-related-media-object">related media object</a> in accordance with the computed value of the
+<a href="#parameter-attribute-mediaOffset"><code>ttp:mediaOffset</code></a> parameter property.</p></div></div></div><div class="div1">
 <h2><a id="common-styling"></a>O Common Caption Style Examples (Non-Normative)</h2><p>This section provides examples of the following common caption styles using TTML Content
 to obtain the desired behavior:</p><ul><li><p>Pop-On Captions</p></li><li><p>Roll-Up Captions</p></li><li><p>Paint-On Captions</p></li></ul><div class="div2">
 <h3><a id="pop-on-example"></a>O.1 Pop-On Caption Example</h3><p>An example of paint-on captions. In this example, two regions are targeted with alternating, paint-on content, where content is timed
ttml

Hosted by W3C Systems Team, please report bugs to sysreq@w3.org