ttml: changeset 801:7bf1cf77ce3b

--- a/ttml2/spec/ttml2.html	Mon Jan 05 02:36:30 2015 -0700
+++ b/ttml2/spec/ttml2.html	Mon Jan 05 02:36:51 2015 -0700
@@ -83,9 +83,9 @@
 .obsoleted { background-color: #f26d7d }
 .reqattr { font-weight: bold }
 .optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2014/12/01 03:10:45 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2015/01/05 09:36:30 $<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/12/01 03:10:45 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/01/05 09:36:30 $ @@ @@@@ @@@@</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>
@@ -169,9 +169,10 @@
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.7 <a href="#parameter-attribute-mediaDuration">ttp:mediaDuration</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.8 <a href="#parameter-attribute-mediaOffset">ttp:mediaOffset</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.9 <a href="#parameter-attribute-pixelAspectRatio">ttp:pixelAspectRatio</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.10 <a href="#parameter-attribute-subFrameRate">ttp:subFrameRate</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.11 <a href="#parameter-attribute-tickRate">ttp:tickRate</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.12 <a href="#parameter-attribute-timeBase">ttp:timeBase</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.10 <a href="#parameter-attribute-storageAspectRatio">ttp:storageAspectRatio</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.11 <a href="#parameter-attribute-subFrameRate">ttp:subFrameRate</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.12 <a href="#parameter-attribute-tickRate">ttp:tickRate</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.2.13 <a href="#parameter-attribute-timeBase">ttp:timeBase</a><br>
 8 <a href="#content">Content</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#content-element-vocabulary">Content Element Vocabulary</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;8.1.1 <a href="#document-structure-vocabulary-tt">tt</a><br>
@@ -217,10 +218,9 @@
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.4 <a href="#embedded-content-value-data-format">&lt;data-format&gt;</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.5 <a href="#embedded-content-value-font">&lt;font&gt;</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.6 <a href="#embedded-content-value-font-format">&lt;font-format&gt;</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.7 <a href="#embedded-content-value-format">&lt;format&gt;</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.8 <a href="#embedded-content-value-image">&lt;image&gt;</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.9 <a href="#embedded-content-value-image-format">&lt;image-format&gt;</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.10 <a href="#embedded-content-value-unicode-range">&lt;unicode-range&gt;</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.7 <a href="#embedded-content-value-image">&lt;image&gt;</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.8 <a href="#embedded-content-value-image-format">&lt;image-format&gt;</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.3.9 <a href="#embedded-content-value-unicode-range">&lt;unicode-range&gt;</a><br>
 10 <a href="#styling">Styling</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;10.1 <a href="#styling-element-vocabulary">Styling Element Vocabulary</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;10.1.1 <a href="#styling-vocabulary-initial">initial</a><br>
@@ -505,11 +505,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="#d3e35000">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e35517">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e35235">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e35752">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e36510">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e36674">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e36745">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e36909">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>
@@ -730,7 +730,7 @@
 may specify the audio data inline by using a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element within
 a <a href="#embedded-content-vocabulary-source"><code>source</code></a> element child, or it may reference another
 <a href="#embedded-content-vocabulary-audio"><code>audio</code></a> element specified in a 
-<a href="#terms-audio-definition-context">audio definition context</a>, or it may do both.</p></dd><dt class="label"><a id="terms-audio-resource"></a>[audio resource]</dt><dd><p>A <a href="#terms-data-resource">data resource</a> that contains coded or unencoded audio samples.</p></dd><dt class="label"><a id="terms-baseline-profile"></a>[baseline profile]</dt><dd><p>A <a href="#terms-profile">profile</a> referenced by the <code>use</code> attribute of a <code>ttp:profile</code> element,
+<a href="#terms-audio-definition-context">audio definition context</a>, or it may do both.</p></dd><dt class="label"><a id="terms-audio-resource"></a>[audio resource]</dt><dd><p>A <a href="#terms-data-resource">data resource</a> that contains coded or unencoded audio samples.</p></dd><dt class="label"><a id="terms-authoring-viewport"></a>[authoring viewport]</dt><dd><p>A <a href="#terms-viewport">viewport</a> employed at authoring (content encoding) time.</p></dd><dt class="label"><a id="terms-baseline-profile"></a>[baseline profile]</dt><dd><p>A <a href="#terms-profile">profile</a> referenced by the <code>use</code> attribute of a <code>ttp:profile</code> element,
 which serves as a baseline (initial) set of specifications with which to populate the referencing profile.</p></dd><dt class="label"><a id="terms-block-display"></a>[block display]</dt><dd><p>Block display is a set of layout semantics that may be applied to a <a href="#terms-content-element">content element</a> in
 certain contexts, wherein child areas are composed sequentially in the block progression direction. In <a href="#css2">[CSS2]</a>,
 block display is indicated when a CSS <code>display</code> property with the value <code>block</code> is applied to a
@@ -745,7 +745,7 @@
 representing the rendering of a caption.</p></dd><dt class="label"><a id="terms-content-processor"></a>[content processor]</dt><dd><p>A processing system capable of importing (receiving) Timed Text Markup Language
 content for the purpose of transforming, presenting, or otherwise processing the content.</p></dd><dt class="label"><a id="terms-content-profile"></a>[content profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must not, must, or may be employed by
 Timed Text Markup Language content.</p><p></p></dd><dt class="label"><a id="terms-content-region"></a>[content region]</dt><dd><p>A logical region into which rendered content is placed when modeling or
-performing presentation processing.</p></dd><dt class="label"><a id="terms-data-binding-context"></a>[data binding context]</dt><dd><p>The context in which an <a href="#embedded-content-vocabulary-data"><code>data</code></a> element is specified for the
+performing presentation processing.</p><table border="1" class="ednote" summary="Editorial note: Content Region vs Region"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Content Region vs Region</b></td><td align="right" valign="top">2014-12-10</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Clean up terminology regarding content region vs region, which difference is vague at best.</td></tr></table><p></p></dd><dt class="label"><a id="terms-data-binding-context"></a>[data binding context]</dt><dd><p>The context in which an <a href="#embedded-content-vocabulary-data"><code>data</code></a> element is specified for the
 purpose of semantic binding (association). Such a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element
 may specify the data inline by using a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element within
 a <a href="#embedded-content-vocabulary-source"><code>source</code></a> element child, or it may reference another
@@ -767,12 +767,15 @@
 an explicitly specified out-of-line <a href="#layout-vocabulary-region"><code>region</code></a> element, i.e.,
 when no <a href="#layout-vocabulary-region"><code>region</code></a> element is specified as a child of
 a <a href="#layout-vocabulary-layout"><code>layout</code></a> element.</p></dd><dt class="label"><a id="terms-designated-profile"></a>[designated profile]</dt><dd><p>A <a href="#terms-profile">profile</a> that is associated with a <a href="#terms-profile-designator">profile designator</a> by
-means of a <code>designator</code> attribute or prose text in a specification of profile.</p></dd><dt class="label"><a id="terms-document-instance"></a>[document instance]</dt><dd><p>A <a href="#terms-timed-text-document-instance">timed text document instance</a>.</p></dd><dt class="label"><a id="terms-document-interchange-context"></a>[document interchange context]</dt><dd><p>The implied context or environment external to a <a href="#terms-content-processor">content processor</a> in
+means of a <code>designator</code> attribute or prose text in a specification of profile.</p></dd><dt class="label"><a id="terms-display-aspect-ratio"></a>[display aspect ratio]</dt><dd><p>The ratio between the horizontal dimension and vertical dimension of a displayed image, video frame,
+viewport or region, display device, etc. Equal to the product of <a href="#terms-storage-aspect-ratio">storage aspect ratio</a>
+and <a href="#terms-pixel-aspect-ratio">pixel aspect ratio</a>.</p></dd><dt class="label"><a id="terms-display-region-target"></a>[display region target]</dt><dd><p>A <a href="#terms-viewport">viewport</a> targeted to a rectangular region of a display device, i.e., not in full-screen mode.</p></dd><dt class="label"><a id="terms-display-target"></a>[display target]</dt><dd><p>A <a href="#terms-viewport">viewport</a> targeted to a display device as a whole, i.e., in full-screen mode.</p></dd><dt class="label"><a id="terms-document-coordinate-space"></a>[document coordinate space]</dt><dd><p></p><table border="1" class="ednote" summary="Editorial note: Document Coordinate Space Definition"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Document Coordinate Space Definition</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Either define or express in terms of (some) viewport.</td></tr></table><p></p></dd><dt class="label"><a id="terms-document-instance"></a>[document instance]</dt><dd><p>A <a href="#terms-timed-text-document-instance">timed text document instance</a>.</p></dd><dt class="label"><a id="terms-document-interchange-context"></a>[document interchange context]</dt><dd><p>The implied context or environment external to a <a href="#terms-content-processor">content processor</a> in
 which document interchange occurs, and in which out-of-band protocols or specifications
 may define certain behavioral defaults, such as an implied profile.</p></dd><dt class="label"><a id="terms-document-processing-context"></a>[document processing context]</dt><dd><p>The implied context or environment internal to a <a href="#terms-content-processor">content processor</a> in
 which document processing occurs, and in which out-of-band protocols or specifications
 may define certain behavioral defaults, such as the establishment or creation of a
-<a href="#terms-synthetic-document-syncbase">synthetic document syncbase</a>.</p></dd><dt class="label"><a id="terms-effective-content-profile"></a>[effective content profile]</dt><dd><p>The <a href="#terms-content-profile">content profile</a> computed from the set of all <a href="#terms-content-profile">content profiles</a>
+<a href="#terms-synthetic-document-syncbase">synthetic document syncbase</a>.</p></dd><dt class="label"><a id="terms-dot-pitch"></a>[dot pitch]</dt><dd><p>Depending upon display device technology, the distance between holes in the shadow mask, the distance between wires in the aperture grill,
+the distance between sub-pixels of the same color, etc.</p></dd><dt class="label"><a id="terms-effective-content-profile"></a>[effective content profile]</dt><dd><p>The <a href="#terms-content-profile">content profile</a> computed from the set of all <a href="#terms-content-profile">content profiles</a>
 explicitly or implicitly referenced by or assigned to a TTML <a href="#terms-document-instance">document instance</a> after applying any
 explicit or implicit profile and profile specification combination methods. When performing validation on a given <a href="#terms-document-instance">document instance</a>,
 then this validation is performed by making use of a document's <a href="#terms-effective-content-profile">effective content profile</a>.</p></dd><dt class="label"><a id="terms-effective-processor-profile"></a>[effective processor profile]</dt><dd><p>The <a href="#terms-processor-profile">processor profile</a> computed from the set of all <a href="#terms-processor-profile">processor profiles</a>
@@ -875,9 +878,13 @@
 on the associated element to be selected into the region. There is a one-to-many relation between
 a referenced out-of-line region element and referencing <a href="#terms-content-element">content elements</a>.
 A <a href="#terms-default-region">default out-of-line region</a> is implied if no
-<a href="#terms-out-of-line-region">out-of-line region</a> is specified explicitly.</p></dd><dt class="label"><a id="terms-presentation-processor"></a>[presentation processor]</dt><dd><p>A <a href="#terms-content-processor">content processor</a> which purpose is to layout, format, and render,
+<a href="#terms-out-of-line-region">out-of-line region</a> is specified explicitly.</p></dd><dt class="label"><a id="terms-pixel-aspect-ratio"></a>[pixel aspect ratio]</dt><dd><p>The ratio between the horizontal dimension and vertical dimension of a displayed pixel. Note that the dimensions of a display pixel may or may not
+correspond to the <a href="#terms-dot-pitch">dot pitch</a> of the display device on which it is rendered.</p></dd><dt class="label"><a id="terms-presentation-context-coordinate-space"></a>[presentation context coordinate space]</dt><dd><p></p><table border="1" class="ednote" summary="Editorial note: Presentation Context Coordinate Space Definition"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Presentation Context Coordinate Space Definition</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Either define or express in terms of (some) viewport.</td></tr></table><p></p></dd><dt class="label"><a id="terms-presentation-processor"></a>[presentation processor]</dt><dd><p>A <a href="#terms-content-processor">content processor</a> which purpose is to layout, format, and render,
 i.e., to present, <a href="#terms-timed-text-markup-language">Timed Text Markup Language</a> content by applying the presentation semantics
-defined in this specification.</p></dd><dt class="label"><a id="terms-processor"></a>[processor]</dt><dd><p>See <a href="#terms-content-processor">content processor</a>.</p></dd><dt class="label"><a id="terms-processor-profile"></a>[processor profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must or may be implemented (supported) by
+defined in this specification.</p></dd><dt class="label"><a id="terms-presentation-viewport"></a>[presentation viewport]</dt><dd><p>A <a href="#terms-viewport">viewport</a> employed at presentation (content decoding) time.</p><p>Note well that the characteristics of a <a href="#presentation-viewport">presentation viewport</a> may or may not
+match the characteristics of the <a href="#authoring-viewport">authoring viewport</a> used when content was authored (encoded).
+In particular, the <a href="#terms-storage-aspect-ratio">storage aspect ratio</a> and (or) the <a href="#terms-pixel-aspect-ratio">pixel aspect ratio</a>
+of the former may differ from that of the latter.</p></dd><dt class="label"><a id="terms-processor"></a>[processor]</dt><dd><p>See <a href="#terms-content-processor">content processor</a>.</p></dd><dt class="label"><a id="terms-processor-profile"></a>[processor profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must or may be implemented (supported) by
 a content processor.</p></dd><dt class="label"><a id="terms-profile"></a>[profile]</dt><dd><p>A <a href="#terms-content-profile">content profile</a> or <a href="#terms-processor-profile">processor profile</a>.</p></dd><dt class="label"><a id="terms-profile-definition-document"></a>[profile definition document]</dt><dd><p>A <a href="#terms-timed-text-profile-document">timed text profile document</a> or a
 <a href="#terms-timed-text-profile-document-instance">timed text profile document instance</a>, according to the context of use.</p></dd><dt class="label"><a id="terms-profile-designator"></a>[profile designator]</dt><dd><p>An absolute URI used to label or reference an externally defined <a href="#terms-profile">profile</a>, where
 external refers to being external to a <a href="#terms-document-instance">document instance</a>.</p></dd><dt class="label"><a id="terms-profile-fragment-identifier"></a>[profile fragment identifier]</dt><dd><p>A <a href="#terms-fragment-identifier">fragment identifier</a> used to label or reference an internally defined <a href="#terms-profile">profile</a>, where
@@ -891,15 +898,16 @@
 object for which a <a href="#terms-document-instance">document instance</a> provides caption or subtitle
 information, and with which that <a href="#terms-document-instance">document instance</a> is associated.</p></dd><dt class="label"><a id="terms-related-media-object-region"></a>[related media object region]</dt><dd><p>When a non-null <a href="#terms-related-media-object">related media object</a> exists, the region of this media object,
 expressed in the coordinate system that applies to the <a href="#terms-document-instance">document instance</a> that is associated with the
-related media object.</p></dd><dt class="label"><a id="terms-root-container-region"></a>[root container region]</dt><dd><p>A logical region that establishes a coordinate system into which
+related media object.</p><table border="1" class="ednote" summary="Editorial note: Update Definition of Related Media Object Region"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Update Definition of Related Media Object Region</b></td><td align="right" valign="top">2014-12-02</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Untangle definition from use of document coordinate space.</td></tr></table><p></p></dd><dt class="label"><a id="terms-related-media-object-region-target"></a>[related media object region target]</dt><dd><p>A <a href="#terms-viewport">viewport</a> targeted to a <a href="#terms-related-media-object-region">related media object region</a>.</p></dd><dt class="label"><a id="terms-root-container-region"></a>[root container region]</dt><dd><p>A logical region that establishes a coordinate system into which
 <a href="#terms-content-region">content regions</a> are placed and optionally clipped.</p></dd><dt class="label"><a id="terms-root-temporal-extent"></a>[root temporal extent]</dt><dd><p>The temporal extent (interval) defined by the temporal beginning and ending of a <a href="#terms-document-instance">document instance</a>
 in relationship with some external application or presentation context.</p></dd><dt class="label"><a id="terms-simple-data-embedding"></a>[simple data embedding]</dt><dd><p>A <a href="#embedded-content-vocabulary-data"><code>data</code></a> element the directly embeds a representation of the actual bytes
 of an <a href="#terms-embedded-data-resource">embedded data resource</a> without making use of a
 child <a href="#embedded-content-vocabulary-chunk"><code>chunk</code></a> element.</p></dd><dt class="label"><a id="terms-smpte-time-code"></a>[smpte time code]</dt><dd><p>A time code whose format and semantics are established by <a href="#smpte12m">[SMPTE 12M]</a>,
 which may be embedded into or otherwise associated with media content, such
-as a broadcast audio/video stream.</p></dd><dt class="label"><a id="terms-sourced-data-embedding"></a>[chunked data embedding]</dt><dd><p>A <a href="#embedded-content-vocabulary-data"><code>data</code></a> element the indirectly references the content
+as a broadcast audio/video stream.</p></dd><dt class="label"><a id="terms-sourced-data-embedding"></a>[sourced data embedding]</dt><dd><p>A <a href="#embedded-content-vocabulary-data"><code>data</code></a> element that indirectly references the content
 of an <a href="#terms-embedded-data-resource">embedded data resource</a> by making use of a
-child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element.</p></dd><dt class="label"><a id="terms-synthetic-document-syncbase"></a>[synthetic document syncbase]</dt><dd><p>A document level <a href="http://www.w3.org/TR/2008/REC-SMIL3-20081201/smil30.html#smil-timing-q158">syncbase</a>
+child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element.</p></dd><dt class="label"><a id="terms-storage-aspect-ratio"></a>[storage aspect ratio]</dt><dd><p>The ratio between the number of horizontal samples and the number of vertical samples of a two-dimensional
+representation of an image, a video frame, a viewport or region, etc.</p></dd><dt class="label"><a id="terms-synthetic-document-syncbase"></a>[synthetic document syncbase]</dt><dd><p>A document level <a href="http://www.w3.org/TR/2008/REC-SMIL3-20081201/smil30.html#smil-timing-q158">syncbase</a>
 <a href="#smil3">[SMIL 3.0]</a>, § 5.7.1, synthesized or otherwise established by
 the <a href="#terms-document-processing-context">document processing context</a> in accordance with the
 <a href="#terms-related-media-object">related media object</a> or other processing criteria.</p></dd><dt class="label"><a id="terms-synthetic-smpte-document-syncbase"></a>[synthetic smpte document syncbase]</dt><dd><p>A <a href="#terms-synthetic-document-syncbase">synthetic document syncbase</a> constructed from <a href="#terms-smpte-time-code">smpte time code</a>
@@ -931,7 +939,14 @@
 specification does not otherwise define a target profile or format for transformation processing,
 no further transformation semantics are defined by this specification.</p></dd><dt class="label"><a id="terms-undesignated-profile"></a>[undesignated profile]</dt><dd><p>A <a href="#terms-profile">profile</a> that is not associated with a <a href="#terms-profile-designator">profile designator</a>, and which is
 referred to implicitly in the context of the profile's definition. Also referred to as an <em>anonymous profile</em>.</p></dd><dt class="label"><a id="terms-valid-abstract-document-instance"></a>[valid abstract document instance]</dt><dd><p>An <a href="#terms-abstract-document-instance">abstract document instance</a> which has been assessed for validity
-and found to be valid as defined by <a href="#doctypes"><b>4 Document Types</b></a>.</p></dd></dl></div><div class="div2">
+and found to be valid as defined by <a href="#doctypes"><b>4 Document Types</b></a>.</p></dd><dt class="label"><a id="terms-viewport"></a>[viewport]</dt><dd><p>A logical, rectangular area with respect to which content is encoded or decoded for the purpose of presentation, where such area
+may be employed by or for the authoring or presentation of a <a href="#terms-related-media-object">related media object</a> or
+the <a href="#terms-root-container-region">root container region</a> and its constituent <a href="#terms-region">regions</a>.</p></dd><dt class="label"><a id="terms-viewport-target"></a>[viewport target]</dt><dd><p>An implied or explicit target or mapping of a <a href="#viewport">viewport</a> to some logical or physical entity, of which this
+specification identifies three such targets:
+<a href="#terms-display-target">display target</a>,
+<a href="#terms-display-region-target">display region target</a>, and
+<a href="#terms-related-media-object-region-target">related media object region target</a>.
+</p></dd></dl></div><div class="div2">
 <h3><a id="conventions"></a>2.3 Documentation Conventions</h3><p>Within normative prose in this specification, the words
 <em>may</em>, <em>should</em>, and <em>must</em> are
 defined as follows:</p><dl class="conformance-keywords"><dt class="label">may</dt><dd><p>Conforming documents and/or TTML processors are permitted to,
@@ -1520,6 +1535,7 @@
 <a href="#parameter-attribute-mediaDuration">ttp:mediaDuration</a>,
 <a href="#parameter-attribute-mediaOffset">ttp:mediaOffset</a>,
 <a href="#parameter-attribute-pixelAspectRatio">ttp:pixelAspectRatio</a>,
+<a href="#parameter-attribute-storageAspectRatio">ttp:storageAspectRatio</a>,
 <a href="#parameter-attribute-subFrameRate">ttp:subFrameRate</a>,
 <a href="#parameter-attribute-tickRate">ttp:tickRate</a>,
 <a href="#parameter-attribute-timeBase">ttp:timeBase</a>,
@@ -2242,7 +2258,7 @@
 core vocabulary items or for establishing a <a href="#terms-document-processing-context">document processing context</a> by means
 of which TTML Content can be related to an external environment.</p><div class="div2">
 <h3><a id="parameter-element-vocabulary"></a>7.1 Parameter Element Vocabulary</h3><p>No parameter element vocabulary is defined in this specification.</p></div><div class="div2">
-<h3><a id="parameter-attribute-vocabulary"></a>7.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>7.2.1 ttp:cellResolution</b></a></p></li><li><p><a href="#parameter-attribute-clockMode"><b>7.2.2 ttp:clockMode</b></a></p></li><li><p><a href="#parameter-attribute-dropMode"><b>7.2.3 ttp:dropMode</b></a></p></li><li><p><a href="#parameter-attribute-frameRate"><b>7.2.4 ttp:frameRate</b></a></p></li><li><p><a href="#parameter-attribute-frameRateMultiplier"><b>7.2.5 ttp:frameRateMultiplier</b></a></p></li><li><p><a href="#parameter-attribute-markerMode"><b>7.2.6 ttp:markerMode</b></a></p></li><li><p><a href="#parameter-attribute-mediaDuration"><b>7.2.7 ttp:mediaDuration</b></a></p></li><li><p><a href="#parameter-attribute-mediaOffset"><b>7.2.8 ttp:mediaOffset</b></a></p></li><li><p><a href="#parameter-attribute-pixelAspectRatio"><b>7.2.9 ttp:pixelAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-subFrameRate"><b>7.2.10 ttp:subFrameRate</b></a></p></li><li><p><a href="#parameter-attribute-tickRate"><b>7.2.11 ttp:tickRate</b></a></p></li><li><p><a href="#parameter-attribute-timeBase"><b>7.2.12 ttp:timeBase</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) must
+<h3><a id="parameter-attribute-vocabulary"></a>7.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>7.2.1 ttp:cellResolution</b></a></p></li><li><p><a href="#parameter-attribute-clockMode"><b>7.2.2 ttp:clockMode</b></a></p></li><li><p><a href="#parameter-attribute-dropMode"><b>7.2.3 ttp:dropMode</b></a></p></li><li><p><a href="#parameter-attribute-frameRate"><b>7.2.4 ttp:frameRate</b></a></p></li><li><p><a href="#parameter-attribute-frameRateMultiplier"><b>7.2.5 ttp:frameRateMultiplier</b></a></p></li><li><p><a href="#parameter-attribute-markerMode"><b>7.2.6 ttp:markerMode</b></a></p></li><li><p><a href="#parameter-attribute-mediaDuration"><b>7.2.7 ttp:mediaDuration</b></a></p></li><li><p><a href="#parameter-attribute-mediaOffset"><b>7.2.8 ttp:mediaOffset</b></a></p></li><li><p><a href="#parameter-attribute-pixelAspectRatio"><b>7.2.9 ttp:pixelAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-storageAspectRatio"><b>7.2.10 ttp:storageAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-subFrameRate"><b>7.2.11 ttp:subFrameRate</b></a></p></li><li><p><a href="#parameter-attribute-tickRate"><b>7.2.12 ttp:tickRate</b></a></p></li><li><p><a href="#parameter-attribute-timeBase"><b>7.2.13 ttp:timeBase</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>7.2.1 ttp:cellResolution</h4><p>The <code>ttp:cellResolution</code> attribute may be used by an author
@@ -2273,7 +2289,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>7.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>7.2.12 ttp:timeBase</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#timing-time-value-expressions"><b>12.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>7.2.13 ttp:timeBase</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#timing-time-value-expressions"><b>12.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
@@ -2281,7 +2297,7 @@
   | "gps"
   | "utc"
 </pre></div>
-</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>7.2.12 ttp:timeBase</b></a>, is designated as
+</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>7.2.13 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;
@@ -2304,14 +2320,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>7.2.12 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>7.2.13 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>7.2.12 ttp:timeBase</b></a>, is designated as
+</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>7.2.13 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
@@ -2404,13 +2420,13 @@
 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>7.2.12 ttp:timeBase</b></a>.</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>
+<a href="#parameter-attribute-timeBase"><b>7.2.13 ttp:timeBase</b></a>.</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>
 ttp:markerMode
   : "continuous"
   | "discontinuous"
 </pre></div>
-</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>7.2.12 ttp:timeBase</b></a>, is designated as
+</td></tr></tbody></table><p>If the time base, defined by <a href="#parameter-attribute-timeBase"><b>7.2.13 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
@@ -2510,22 +2526,31 @@
 <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>12.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-pixelAspectRatio"></a>7.2.9 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>
+<h4><a id="parameter-attribute-pixelAspectRatio"></a>7.2.9 ttp:pixelAspectRatio</h4><p>The <code>ttp:pixelAspectRatio</code> attribute may be used to express the <a href="#terms-pixel-aspect-ratio">pixel aspect ratio</a> associated with the
+<a href="#terms-authoring-viewport">authoring viewport</a>.</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>
 ttp:pixelAspectRatio
-  : width height                            // <em>width</em> != 0; <em>height</em> != 0
-
-width | height
+  : numerator demoninator                   // <em>numerator</em> != 0; <em>demoninator</em> != 0
+
+numerator | demoninator
   : <a href="#style-value-digit">&lt;digit&gt;</a>+
 </pre></div>
 </td></tr></tbody></table><p>If not specified, then square pixels (i.e., aspect ratio 1:1) must be assumed to apply.
-If specified, then both width and height must be non-zero.</p><p>A <code>ttp:pixelAspectRatio</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>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-subFrameRate"></a>7.2.10 ttp:subFrameRate</h4><p>The <code>ttp:subFrameRate</code> attribute is used to specify the sub-frame rate of a related
+If specified, then both numerator and demoninator must be non-zero.</p><p>A <code>ttp:pixelAspectRatio</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-storageAspectRatio"></a>7.2.10 ttp:storageAspectRatio</h4><p>The <code>ttp:storageAspectRatio</code> attribute may be used to express the <a href="#terms-storage-aspect-ratio">storage aspect ratio</a> associated with the
+<a href="#terms-authoring-viewport">authoring viewport</a>.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><a id="parameter-attribute-storageAspectRatio-syntax"></a><table class="syntax"><caption>Syntax Representation – ttp:storageAspectRatio</caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+ttp:storageAspectRatio
+  : numerator demoninator                   // <em>numerator</em> != 0; <em>demoninator</em> != 0
+
+numerator | demoninator
+  : <a href="#style-value-digit">&lt;digit&gt;</a>+
+</pre></div>
+</td></tr></tbody></table><p>If specified, then both numerator and demoninator must be non-zero.
+If not specified, then the storage aspect ratio of the <a href="#terms-authoring-viewport">authoring viewport</a> is undefined.</p><p>A <code>ttp:storageAspectRatio</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>7.2.11 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>
@@ -2544,7 +2569,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>7.2.11 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>7.2.12 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>
@@ -2569,7 +2594,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>7.2.12 ttp:timeBase</h4><p>The <code>ttp:timeBase</code> attribute is used to specify the
+<h4><a id="parameter-attribute-timeBase"></a>7.2.13 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>
@@ -3576,7 +3601,7 @@
 if the <a href="#embedded-content-attribute-src"><code>src</code></a> attribute refers to an embedded resource
 in the <a href="#terms-enclosing-document-instance">enclosing document instance</a>.</p><p>If a <code>source</code> element does not specify a <a href="#embedded-content-attribute-src"><code>src</code></a> attribute, then it must specify a
 child <a href="#embedded-content-vocabulary-data"><code>data</code></a> element, in which case it is referred to as
-an <a href="#terms-nested-embedded-source">nested embedded source</a>.</p><p>A <code>source</code> element must not have an ancestor <code>source</code> element.</p><a id="elt-syntax-source"></a><table class="syntax"><caption>XML Representation – Element Information Item: source</caption><tbody><tr><td>
+a <a href="#terms-nested-embedded-source">nested embedded source</a>.</p><p>A <code>source</code> element must not have an ancestor <code>source</code> element.</p><a id="elt-syntax-source"></a><table class="syntax"><caption>XML Representation – Element Information Item: source</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;source
   <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition">&lt;condition&gt;</a>
@@ -3647,9 +3672,8 @@
 e.g., when no media (content) type is available or a generic type is used, such as
 <code>application/octet-stream</code>.</p></div><p>The <code>format</code> attribute may be specified by an instance of the following
 element types:</p><ul><li><p><a href="#embedded-content-vocabulary-audio"><code>audio</code></a></p></li><li><p><a href="#embedded-content-vocabulary-data"><code>data</code></a></p></li><li><p><a href="#embedded-content-vocabulary-font"><code>font</code></a></p></li><li><p><a href="#embedded-content-vocabulary-image"><code>image</code></a></p></li><li><p><a href="#embedded-content-vocabulary-source"><code>source</code></a></p></li></ul><p>The value of a <code>format</code> attribute must adhere to a
-<a href="#embedded-content-value-format">&lt;format&gt;</a> expression.</p><p>Depending on the context of use, additional constraints may apply.</p></div><div class="div3">
-<h4><a id="embedded-content-attribute-src"></a>9.2.3 src</h4><p>The <code>src</code> attribute is used to specify the media (content) type of data resource, and may express additional
-parameters that characterize the data.</p><p>The <code>src</code> attribute may be specified by an instance of the following
+<a href="#embedded-content-value-data-format">&lt;data-format&gt;</a> expression.</p><p>Depending on the context of use, additional constraints may apply.</p></div><div class="div3">
+<h4><a id="embedded-content-attribute-src"></a>9.2.3 src</h4><p>The <code>src</code> attribute is used to specify the location or an identifier that maps to the location of data resource.</p><p>The <code>src</code> attribute may be specified by an instance of the following
 element types:</p><ul><li><p><a href="#embedded-content-vocabulary-audio"><code>audio</code></a></p></li><li><p><a href="#embedded-content-vocabulary-data"><code>data</code></a></p></li><li><p><a href="#embedded-content-vocabulary-font"><code>font</code></a></p></li><li><p><a href="#embedded-content-vocabulary-image"><code>image</code></a></p></li><li><p><a href="#embedded-content-vocabulary-source"><code>source</code></a></p></li></ul><p>If specified, the value of a <code>src</code> attribute must adhere to the value syntax of the
 <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>, §3.2.17.</p><p>Depending on the context of use, additional constraints may apply.</p></div><div class="div3">
 <h4><a id="embedded-content-attribute-type"></a>9.2.4 type</h4><p>The <code>type</code> attribute is used to specify the media (content) type of data resource, and may express additional
@@ -3659,7 +3683,7 @@
 must respect the specified type whether it is correct or not. That is, if a <code>type</code> attribute mis-specifies the
 type of a data resource, then content processing must not attempt to override that type by performing content
 sniffing.</p></div></div><div class="div2">
-<h3><a id="embedded-content-value-expressions"></a>9.3 Embedded Content Value Expressions</h3><p>Embedded content elements as well as certain style property values include the use of the following expressions:</p><ul><li><p><a href="#embedded-content-value-audio"><b>9.3.1 &lt;audio&gt;</b></a></p></li><li><p><a href="#embedded-content-value-audio-format"><b>9.3.2 &lt;audio-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-data"><b>9.3.3 &lt;data&gt;</b></a></p></li><li><p><a href="#embedded-content-value-data-format"><b>9.3.4 &lt;data-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-font"><b>9.3.5 &lt;font&gt;</b></a></p></li><li><p><a href="#embedded-content-value-font-format"><b>9.3.6 &lt;font-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-format"><b>9.3.7 &lt;format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-image"><b>9.3.8 &lt;image&gt;</b></a></p></li><li><p><a href="#embedded-content-value-image-format"><b>9.3.9 &lt;image-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-unicode-range"><b>9.3.10 &lt;unicode-range&gt;</b></a></p></li></ul><p>In the syntax representations defined in this section, no
+<h3><a id="embedded-content-value-expressions"></a>9.3 Embedded Content Value Expressions</h3><p>Embedded content elements as well as certain style property values make use of the following expressions:</p><ul><li><p><a href="#embedded-content-value-audio"><b>9.3.1 &lt;audio&gt;</b></a></p></li><li><p><a href="#embedded-content-value-audio-format"><b>9.3.2 &lt;audio-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-data"><b>9.3.3 &lt;data&gt;</b></a></p></li><li><p><a href="#embedded-content-value-data-format"><b>9.3.4 &lt;data-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-font"><b>9.3.5 &lt;font&gt;</b></a></p></li><li><p><a href="#embedded-content-value-font-format"><b>9.3.6 &lt;font-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-image"><b>9.3.7 &lt;image&gt;</b></a></p></li><li><p><a href="#embedded-content-value-image-format"><b>9.3.8 &lt;image-format&gt;</b></a></p></li><li><p><a href="#embedded-content-value-unicode-range"><b>9.3.9 &lt;unicode-range&gt;</b></a></p></li></ul><p>In the syntax representations defined in this section, no
 linear whitespace (LWSP) is implied or permitted between tokens
 unless explicitly specified.</p><div class="div3">
 <h4><a id="embedded-content-value-audio"></a>9.3.1 &lt;audio&gt;</h4><p>An &lt;audio&gt; value expression is used to specify an <a href="#terms-audio-resource">audio resource</a> by reference.</p><a id="audio-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;audio&gt;</caption><tbody><tr><td>
@@ -3698,13 +3722,13 @@
 </td></tr></tbody></table><p>If a format expression takes the form of an <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>,
 then it must express an absolute URI.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not standardize the set of format tokens for use with data content. Authors are encouraged to
 use tokens in common use, or absent that, to add a prefix <code>"x-"</code> to form a private use token.</p></div></div><div class="div3">
-<h4><a id="embedded-content-value-font"></a>9.3.5 &lt;font&gt;</h4><p>An &lt;font&gt; expression is used to specify an <a href="#terms-font-resource">font resource</a> by reference.</p><a id="font-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;font&gt;</caption><tbody><tr><td>
+<h4><a id="embedded-content-value-font"></a>9.3.5 &lt;font&gt;</h4><p>An &lt;font&gt; expression is used to specify a <a href="#terms-font-resource">font resource</a> by reference.</p><a id="font-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;font&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;font&gt;
   : <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
 </pre></div>
-</td></tr></tbody></table><p>If an &lt;font&gt; expression takes the form of a <a href="#terms-fragment-identifier">fragment identifier</a>,
-then that fragment identifier must reference an <a href="#embedded-content-vocabulary-font"><code>font</code></a> element that is a child of a
+</td></tr></tbody></table><p>If a &lt;font&gt; expression takes the form of a <a href="#terms-fragment-identifier">fragment identifier</a>,
+then that fragment identifier must reference a <a href="#embedded-content-vocabulary-font"><code>font</code></a> element that is a child of a
 <a href="#embedded-content-vocabulary-resources"><code>resources</code></a> element in the <a href="#terms-enclosing-document-instance">enclosing document instance</a>.</p></div><div class="div3">
 <h4><a id="embedded-content-value-font-format"></a>9.3.6 &lt;font-format&gt;</h4><p>A &lt;font-format&gt; expression is used to specify the format of a <a href="#terms-font-resource">font resource</a>. Additional format information is useful in the case
 of <a href="#terms-font-resource">font resources</a> due that lack a registered media (content) type.</p><a id="font-format-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;font-format&gt;</caption><tbody><tr><td>
@@ -3721,18 +3745,7 @@
 then it must express an absolute URI.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification standardizes a limited set of format tokens for use with font content. In case none of
 these tokens are appropriate, authors are encouraged to use tokens in common use, or absent that, to add a
 prefix <code>"x-"</code> to form a private use token.</p></div></div><div class="div3">
-<h4><a id="embedded-content-value-format"></a>9.3.7 &lt;format&gt;</h4><p>A &lt;format&gt; expression is used to specify the format of a data resource. Additional format information is useful in the case
-of data resources that lack a registered media (content) type.</p><a id="format-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;format&gt;</caption><tbody><tr><td>
-<div class="exampleInner"><pre>
-&lt;format&gt;
-  : <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
-  | <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
-</pre></div>
-</td></tr></tbody></table><p>If a format expression takes the form of an <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>,
-then it must express an absolute URI.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not standardize the set of format tokens. Authors are encouraged to
-use tokens in common use, or absent that, to add a prefix <code>"x-"</code> to form a private use token.
-Alternatively, an author may use an arbitrary absolute URI as a format specification.</p></div></div><div class="div3">
-<h4><a id="embedded-content-value-image"></a>9.3.8 &lt;image&gt;</h4><p>An &lt;image&gt; expression is used to specify an <a href="#terms-image-resource">image resource</a> by reference.</p><a id="image-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;image&gt;</caption><tbody><tr><td>
+<h4><a id="embedded-content-value-image"></a>9.3.7 &lt;image&gt;</h4><p>An &lt;image&gt; expression is used to specify an <a href="#terms-image-resource">image resource</a> by reference.</p><a id="image-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;image&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;image&gt;
   : <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
@@ -3740,7 +3753,7 @@
 </td></tr></tbody></table><p>If an &lt;image&gt; expression takes the form of a <a href="#terms-fragment-identifier">fragment identifier</a>,
 then that fragment identifier must reference an <a href="#embedded-content-vocabulary-image"><code>image</code></a> element that is a child of a
 <a href="#embedded-content-vocabulary-resources"><code>resources</code></a> element in the <a href="#terms-enclosing-document-instance">enclosing document instance</a>.</p></div><div class="div3">
-<h4><a id="embedded-content-value-image-format"></a>9.3.9 &lt;image-format&gt;</h4><p>An &lt;image-format&gt; expression is used to specify the format of a <a href="#terms-image-resource">image resource</a>. Additional format information is useful in the case
+<h4><a id="embedded-content-value-image-format"></a>9.3.8 &lt;image-format&gt;</h4><p>An &lt;image-format&gt; expression is used to specify the format of a <a href="#terms-image-resource">image resource</a>. Additional format information is useful in the case
 of <a href="#terms-image-resource">image resources</a> that lack a registered media (content) type.</p><a id="image-format-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;image-format&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;image-format&gt;
@@ -3750,7 +3763,7 @@
 </td></tr></tbody></table><p>If a format expression takes the form of a <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>,
 then it must express an absolute URI.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not standardize the set of format tokens for use with image content. Authors are encouraged to
 use tokens in common use, or absent that, to add a prefix <code>"x-"</code> to form a private use token.</p></div></div><div class="div3">
-<h4><a id="embedded-content-value-unicode-range"></a>9.3.10 &lt;unicode-range&gt;</h4><p>A &lt;unicode-range&gt; expression is used to specify a collection of Unicode codepoints by enumerating singleton codepoints or ranges of codepoints.</p><a id="unicode-range-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;unicode-range&gt;</caption><tbody><tr><td>
+<h4><a id="embedded-content-value-unicode-range"></a>9.3.9 &lt;unicode-range&gt;</h4><p>A &lt;unicode-range&gt; expression is used to specify a collection of Unicode codepoints by enumerating singleton codepoints or ranges of codepoints.</p><a id="unicode-range-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;unicode-range&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;unicode-range&gt;
   : range ("," range)*
@@ -4261,12 +4274,15 @@
 represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
 § 7.14.4.</p></div></div><div class="div3">
 <h4><a id="style-attribute-extent"></a>10.2.11 tts:extent</h4><p>The <code>tts:extent</code> attribute is used to specify the
-<em>width</em> and <em>height</em> of a region area
-(which may be the <a href="#terms-root-container-region">root container region</a>).</p><p>This attribute may be specified by any
+<em>width</em> and <em>height</em> of a region area. It may also be used to specify the extent of
+the <a href="#terms-root-container-region">root container region</a>, which has the effect of defining
+the <a href="#terms-document-coordinate-space">document coordinate space</a>.</p><p>This attribute may be specified by any
 element type
 that permits use of attributes in the TT Style Namespace; however, this attribute applies
 as a style property only to those element types indicated in the following table.</p><a id="style-property-details-extent"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>auto</code> |
+<code>contain</code> |
+<code>cover</code> |
 <a href="#style-value-measure">&lt;measure&gt;</a> <a href="#style-value-measure">&lt;measure&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
 <a href="#document-structure-vocabulary-tt"><code>tt</code></a>,
@@ -4277,7 +4293,7 @@
 specifications, then they must be interpreted as <em>width</em>
 and <em>height</em>, where the first specification is the
 <em>width</em>, and the second specification is the <em>height</em>.</p><p>The <a href="#style-value-measure">&lt;measure&gt;</a> value(s) used to express extent must be non-negative.</p><p>If the value of this attribute is <code>auto</code>, then the computed value
-of the style property must be considered to be the same as the extent of the <a href="#terms-root-container-region">root container region</a>.</p><p>The extent of the <a href="#terms-root-container-region">root container region</a> is determined either by a
+of the style property must be considered to be the same as the extent of the <a href="#terms-root-container-region">root container region</a>.</p><table border="1" class="ednote" summary="Editorial note: Semantics of contain and cover"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Semantics of contain and cover</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define semantics of new <code>contain</code> and <code>cover</code> values.</td></tr></table><p>The extent of the <a href="#terms-root-container-region">root container region</a> is determined either by a
 <code>tts:extent</code> specified on the <code>tt</code> element, if
 present, or as described by <a href="#document-structure-vocabulary-tt"><b>8.1.1 tt</b></a> if not present.
 If <code>tts:extent</code> is specified on the <code>tt</code> element, then
@@ -4847,7 +4863,11 @@
 an unspecified presentation region determined by the <a href="#terms-document-processing-context">document processing context</a>.
 For other applicable element types, the positioning area corresponds with the content rectangle (content box)
 of the <a href="#terms-root-container-region">root container region</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The <a href="#terms-root-container-region">root container region</a> has no border or padding; consequently, its border, padding, and
-content rectangles (boxes) are coterminous.</p></div><p>If a <code>tts:position</code> attribute is specified on a <code>div</code> or <code>p</code> element, then that specification must be considered to be
+content rectangles (boxes) are coterminous.</p></div><p>If a horizontal or vertical position offset is specified by a <code>tts:position</code> attribute in the form of a scalar value
+on a <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element, then that value must be expressed using pixel (<code>px</code>) units,
+in which case a pixel must be interpreted as a pixel in the <a href="#terms-presentation-context-coordinate-space">presentation context coordinate space</a>
+(and not a pixel in the <a href="#terms-document-coordinate-space">document coordinate space</a>).</p><p>If a <code>tts:position</code> attribute is specified on a <a href="#content-vocabulary-div"><code>div</code></a> or
+<a href="#content-vocabulary-p"><code>p</code></a> element, then that specification must be considered to be
 equivalent to specifying an anonymous <a href="#terms-inline-region">inline region</a> child of the <code>div</code> or <code>p</code> element, where the
 position of the corresponding region, also referred to as an <a href="#terms-implied-inline-region">implied inline region</a>, is equal to the
 value of this attribute.</p><p>If a computed value of the property associated with this attribute is not supported,
@@ -7024,9 +7044,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>7.2.4 ttp:frameRate</b></a>,
-<a href="#parameter-attribute-subFrameRate"><b>7.2.10 ttp:subFrameRate</b></a>,
-<a href="#parameter-attribute-tickRate"><b>7.2.11 ttp:tickRate</b></a>, and
-<a href="#parameter-attribute-timeBase"><b>7.2.12 ttp:timeBase</b></a> for further information on
+<a href="#parameter-attribute-subFrameRate"><b>7.2.11 ttp:subFrameRate</b></a>,
+<a href="#parameter-attribute-tickRate"><b>7.2.12 ttp:tickRate</b></a>, and
+<a href="#parameter-attribute-timeBase"><b>7.2.13 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;
@@ -7082,7 +7102,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>7.2.10 ttp:subFrameRate</b></a>.
+sub-frame rate determined by the <code>ttp:subFrameRate</code> parameter as defined by <a href="#parameter-attribute-subFrameRate"><b>7.2.11 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><p>If a &lt;timeExpression&gt; is expressed in terms of an
 <em>offset-time</em> and no <em>metric</em> is specified, then it is to be treated as
@@ -9657,7 +9677,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="d3e35000"></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="d3e35235"></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
@@ -9714,7 +9734,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="d3e35517"></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="d3e35752"></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
@@ -9806,9 +9826,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="d3e36510"></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="d3e36745"></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="d3e36674"></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-profiling">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e36909"></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-profiling">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
 specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>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">
@@ -10156,6 +10176,7 @@
 Frank Olivier,
 Soohong Daniel Park,
 Silvia Pfeiffer,
+Rohit Puri,
 Brian Raymor,
 David Ronca,
 Patrick Schmitz,
author	Glenn Adams <glenn@skynav.com>
	Mon, 05 Jan 2015 02:36:51 -0700
changeset 801	7bf1cf77ce3b
parent 800	bd172bc178ae
child 802	36262001dea5