--- a/ttml2/spec/ttml2.html Thu Nov 27 17:15:57 2014 -0700
+++ b/ttml2/spec/ttml2.html Thu Nov 27 17:16:11 2014 -0700
@@ -83,13 +83,13 @@
.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$<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/11/28 00:15:57 $<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$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/11/28 00:15:57 $ @@ @@@@ @@@@</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>
-</dd><dt>Editor:</dt><dd>Glenn Adams, Skynav, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Sean Hayes, Microsoft</dd><dd>Frans de Jong, European Broadcasting Union</dd><dd>Pierre-Anthony Lemieux, MovieLabs</dd><dd>Nigel Megitt, British Broadcasting Corporation</dd><dd>Dave Singer, Apple Computer</dd><dd>Jerry Smith, Microsoft</dd></dl><p>Please refer to the <a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttml-issues.html">errata</a> for this document, which may
+</dd><dt>Editor:</dt><dd>Glenn Adams, Skynav, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Sean Hayes, Microsoft</dd><dd>Frans de Jong, European Broadcasting Union</dd><dd>Pierre-Anthony Lemieux, MovieLabs</dd><dd>Nigel Megitt, British Broadcasting Corporation</dd><dd>Dave Singer, Apple Computer</dd><dd>Jerry Smith, Microsoft</dd><dd>Andreas Tai, Invited Expert</dd></dl><p>Please refer to the <a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttml-issues.html">errata</a> for this document, which may
include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ttml2"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
<h2><a id="abstract"></a>Abstract</h2><p>This document specifies the Timed Text Markup Language (TTML), Version 2, also known as TTML2,
in terms of a vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
@@ -500,11 +500,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>
- J.1 <a href="#d3e32735">Element Derivation</a><br>
- J.2 <a href="#d3e33252">Attribute Derivation</a><br>
+ J.1 <a href="#d3e33050">Element Derivation</a><br>
+ J.2 <a href="#d3e33567">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e34245">Requirements</a><br>
- K.2 <a href="#d3e34409">Guidelines</a><br>
+ K.1 <a href="#d3e34560">Requirements</a><br>
+ K.2 <a href="#d3e34724">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>
@@ -725,14 +725,15 @@
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-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-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-character-information-item"></a>[character information item]</dt><dd><p>Each data character appearing in an XML document corresponds with a character information
item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.6.</p></dd><dt class="label"><a id="terms-chunked-data-embedding"></a>[chunked data embedding]</dt><dd><p>A <a href="#embedded-content-vocabulary-data"><code>data</code></a> element that directly embeds a representation of the actual bytes
of an <a href="#terms-embedded-data-resource">embedded data resource</a> by making use of a
child <a href="#embedded-content-vocabulary-chunk"><code>chunk</code></a> element.</p></dd><dt class="label"><a id="terms-computed-cell-size"></a>[computed cell size]</dt><dd><p>The size (extent) of a cell computed by dividing the width of the <a href="#terms-root-container-region">root container region</a>
by the column count, i.e., the number of cells in the horizontal axis, and by dividing
the height of the <a href="#terms-root-container-region">root container region</a> by the row count, i.e., the number of cells in the vertical
-axis, where the column and row counts are determined by the <code>ttp:cellResolution</code> parameter attribute.</p></dd><dt class="label"><a id="terms-content-element"></a>[content element]</dt><dd><p>Any of the element types defined by the <a href="#element-vocab-type-content">Content Module</a>.</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
+axis, where the column and row counts are determined by the <code>ttp:cellResolution</code> parameter attribute.</p></dd><dt class="label"><a id="terms-content-element"></a>[content element]</dt><dd><p>Any of the element types defined by the <a href="#element-vocab-type-content">Content Module</a>.</p></dd><dt class="label"><a id="terms-content-image"></a>[content image]</dt><dd><p>An <a href="#terms-image-resource">image resource</a> that contains semantically significant content, e.g., a raster image
+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
@@ -797,7 +798,8 @@
that appears in media, such as in a sign.</p></dd><dt class="label"><a id="terms-font-defining-context"></a>[font defining context]</dt><dd><p>The context in which a <a href="#embedded-content-vocabulary-font"><code>font</code></a> element is specified to serve as
a sharable definition to be referenced indirectly by a <a href="#terms-font-selection-process">font selection process</a>.</p></dd><dt class="label"><a id="terms-font-selection-process"></a>[font selection process]</dt><dd><p>An internal process used by a <a href="#terms-presentation-processor">presentation processor</a> which purpose is to select
a set of author defined fonts and platform fonts for use during layout and presentation processing, where input parameters to this
-process include the computed values of font related properties, the capabilities of individual fonts, and the text content being presented.</p></dd><dt class="label"><a id="terms-fragment-identifier"></a>[fragment identifier]</dt><dd><p>A syntactic expression that adheres to the fragment identifer syntax defined by <a href="#uri">[URI]</a>,
+process include the computed values of font related properties, the capabilities of individual fonts, and the text content being presented.</p></dd><dt class="label"><a id="terms-font-resource"></a>[font resource]</dt><dd><p>A <a href="#terms-data-resource">data resource</a> that contains font information, such as character to glyph mapping data, glyph outlines or images,
+glyph metrics, and other data used in the character to glyph mapping and rendering process.</p></dd><dt class="label"><a id="terms-fragment-identifier"></a>[fragment identifier]</dt><dd><p>A syntactic expression that adheres to the fragment identifer syntax defined by <a href="#uri">[URI]</a>,
Section 4.1.</p></dd><dt class="label"><a id="terms-image-defining-context"></a>[image defining context]</dt><dd><p>The context in which an <a href="#embedded-content-vocabulary-image"><code>image</code></a> element is specified to serve as
a sharable definition to be referenced by another <a href="#embedded-content-vocabulary-image"><code>image</code></a> element
in an <a href="#terms-image-presentation-context">image presentation context</a>.</p></dd><dt class="label"><a id="terms-image-presentation-context"></a>[image presentation context]</dt><dd><p>The context in which an <a href="#embedded-content-vocabulary-image"><code>image</code></a> element is specified for the
@@ -805,7 +807,7 @@
may specify the image 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-image"><code>image</code></a> element specified in a
-<a href="#terms-image-definition-context">image definition context</a>, or it may do both.</p></dd><dt class="label"><a id="terms-implied-inline-region"></a>[implied inline region]</dt><dd><p>An anonymous (unidentified) <a href="#terms-inline-region">inline region</a> that is implied in the context of a block level
+<a href="#terms-image-definition-context">image definition context</a>, or it may do both.</p></dd><dt class="label"><a id="terms-image-resource"></a>[image resource]</dt><dd><p>A <a href="#terms-data-resource">data resource</a> that contains a raster image.</p></dd><dt class="label"><a id="terms-implied-inline-region"></a>[implied inline region]</dt><dd><p>An anonymous (unidentified) <a href="#terms-inline-region">inline region</a> that is implied in the context of a block level
<a href="#terms-content-element">content element</a>
due the presence of a <a href="#style-attribute-extent"><code>tts:extent</code></a> or <a href="#style-attribute-origin"><code>tts:origin</code></a>
style attribute on the <a href="#terms-content-element">content element</a>.</p></dd><dt class="label"><a id="terms-inline-animation"></a>[inline animation]</dt><dd><p>An <a href="#animation-vocabulary-animate"><code>animate</code></a> or <a href="#animation-vocabulary-set"><code>set</code></a> element
@@ -834,7 +836,8 @@
profile combination method determines how profile specifications from the multiple child <code>ttp:profile</code> element(s) are combined.</p></dd><dt class="label"><a id="terms-nested-embedded-source"></a>[nested embedded source]</dt><dd><p>A <a href="#embedded-content-vocabulary-source"><code>source</code></a> element that specifies a child
<a href="#embedded-content-vocabulary-data"><code>data</code></a> element which embeds the actual bytes of the
<a href="#terms-embedded-data-resource">embedded data resource</a>, whether by
-<a href="#terms-simple-data-embedding">simple data embedding</a> or <a href="#terms-chunked-data-embedding">chunked data embedding</a>.</p></dd><dt class="label"><a id="terms-non-nested-embedded-source"></a>[non-nested embedded source]</dt><dd><p>A <a href="#embedded-content-vocabulary-source"><code>source</code></a> element that specifies a child
+<a href="#terms-simple-data-embedding">simple data embedding</a> or <a href="#terms-chunked-data-embedding">chunked data embedding</a>.</p></dd><dt class="label"><a id="terms-non-content-image"></a>[non-content image]</dt><dd><p>An <a href="#terms-image-resource">image resource</a> that does not contain semantically significant content, e.g., a raster image
+representing a background design, which, if not presented, would not affect the presentation of semntically significant content.</p></dd><dt class="label"><a id="terms-non-nested-embedded-source"></a>[non-nested embedded source]</dt><dd><p>A <a href="#embedded-content-vocabulary-source"><code>source</code></a> element that specifies a child
<a href="#embedded-content-vocabulary-data"><code>data</code></a> element which does not embed a representation of the actual bytes of the
<a href="#terms-embedded-data-resource">embedded data resource</a>.</p></dd><dt class="label"><a id="terms-non-nesting-profile"></a>[non-nesting profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined without making reference to one or more child <code>ttp:profile</code> element(s); that is,
by including only child <code>ttp:features</code> and <code>ttp:extensions</code> element(s).</p></dd><dt class="label"><a id="terms-out-of-line-animation"></a>[out-of-line animation]</dt><dd><p>An <a href="#animation-vocabulary-animate"><code>animate</code></a> or <a href="#animation-vocabulary-set"><code>set</code></a> element that is defined out-of-line from
@@ -3137,19 +3140,19 @@
group definitions of embedded content for reference by subsequent elements.
The <a href="#embedded-content-vocabulary-source"><b>9.1.7 source</b></a> element may be used to
express the source of embedded content.</p><div class="div3">
-<h4><a id="embedded-content-vocabulary-audio"></a>9.1.1 audio</h4><p>The <code>audio</code> element is used to define an author supplied audio resource.</p><p>An <code>audio</code> element may appear in two contexts: (1) as a child of a <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element and
+<h4><a id="embedded-content-vocabulary-audio"></a>9.1.1 audio</h4><p>The <code>audio</code> element is used to define an author supplied <a href="#terms-audio-resource">audio resource</a>.</p><p>An <code>audio</code> element may appear in two contexts: (1) as a child of a <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element and
(2) as a child of an element in the <a href="#element-vocab-group-block">Block.class</a> element group, namely, as a child of a
<a href="#content-vocabulary-div"><code>div</code></a> or <a href="#content-vocabulary-p"><code>p</code></a> element, or
as a child of a <a href="#content-vocabulary-span"><code>span</code></a> element. The former is referred to as an
<a href="#terms-audio-defining-context">audio defining context</a>, the latter as an <a href="#terms-audio-presentation-context">audio presentation context</a>.</p><p>When an <code>audio</code> element appears in an <a href="#terms-audio-defining-context">audio defining context</a>, it
-serves as a sharable definition of an audio resource that may be referenced by other <code>audio</code> elements in the
+serves as a sharable definition of an <a href="#terms-audio-resource">audio resource</a> that may be referenced by other <code>audio</code> elements in the
<a href="#terms-enclosing-document-instance">enclosing document instance</a>. In this case, the active time interval of the <code>audio</code> element
-is the same as the active time interval of its parent <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A sharable definition of an audio resource specifies an <a href="#content-attribute-id"><code>xml:id</code></a> attribute in order to be referenced
+is the same as the active time interval of its parent <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A sharable definition of an <a href="#terms-audio-resource">audio resource</a> specifies an <a href="#content-attribute-id"><code>xml:id</code></a> attribute in order to be referenced
by <code>audio</code> elements in an <a href="#terms-audio-presentation-context">audio presentation context</a>.</p></div><p>When an <code>audio</code> element appears in an <a href="#terms-audio-presentation-context">audio presentation context</a>, it
-serves as a non-sharable definition of an audio resource that implies presentation (rendering) semantics, i.e., that it is intended to be played.
+serves as a non-sharable definition of an <a href="#terms-audio-resource">audio resource</a> that implies presentation (rendering) semantics, i.e., that it is intended to be played.
In this case, the active time interval of the <code>audio</code> element is the same as the active time interval of its parent
<a href="#terms-content-element">content element</a>.
-</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A non-sharable definition of an audio resource may or may not specify an <a href="#content-attribute-id"><code>xml:id</code></a> attribute, but this
+</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A non-sharable definition of an <a href="#terms-audio-resource">audio resource</a> may or may not specify an <a href="#content-attribute-id"><code>xml:id</code></a> attribute, but this
identifier is not referenced by other <code>audio</code> elements, or, if it is, the reference is ignored.</p></div><p>The <code>audio</code> element accepts as its children
zero or more elements in the <a href="#element-vocab-group-metadata"><code>Metadata.class</code></a> element group followed by zero or more
<a href="#embedded-content-vocabulary-source"><code>source</code></a> elements.</p><a id="elt-syntax-audio"></a><table class="syntax"><caption>XML Representation – Element Information Item: audio</caption><tbody><tr><td>
@@ -3167,7 +3170,7 @@
<em>Content:</em> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-source">source</a>*
</audio>
</pre></div>
-</td></tr></tbody></table><p>An <code>audio</code> element defines an audio resource either (1) by referring to an <a href="#terms-external-data-resource">external data resource</a>
+</td></tr></tbody></table><p>An <code>audio</code> element defines an <a href="#terms-audio-resource">audio resource</a> either (1) by referring to an <a href="#terms-external-data-resource">external data resource</a>
or (2) defining or referring to an <a href="#terms-embedded-data-resource">embedded data resource</a>, where the <a href="#terms-data-resource">data resource</a>
contains audio content.</p><p>If an <code>audio</code> element specifies a <a href="#embedded-content-attribute-src"><code>src</code></a> attribute, then it must not specify a
child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element. Conversely,
@@ -3177,7 +3180,7 @@
a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute, in which case the value of the
<a href="#embedded-content-attribute-type"><code>type</code></a> attribute must correspond with the media (content) type
of the referenced resource. Otherwise, a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute must not be specified.</p><p>If a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute is not specified or is specified as a generic type, such as <code>application/octet-stream</code>,
-and additional format information is known about a referenced audio resource, then a <a href="#embedded-content-attribute-format"><code>format</code></a> attribute should be specified as a hint to the
+and additional format information is known about a referenced <a href="#terms-audio-resource">audio resource</a>, then a <a href="#embedded-content-attribute-format"><code>format</code></a> attribute should be specified as a hint to the
content processor.</p><p>If an <code>audio</code> element includes a child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element, then
the <a href="#embedded-content-attribute-format"><code>format</code></a> attribute of the <code>source</code> child, if specified, must adhere to the <a href="#embedded-content-value-audio-format"><audio-format></a>
value expression.</p><p>The use of the <code>audio</code> element is illustrated by the following example.</p><a id="embedded-content-vocabulary-audio-example-1"></a><table class="example"><caption>Example Fragment – External Audio Resource</caption><tbody><tr><td>
@@ -3330,7 +3333,7 @@
</div>
</pre></div>
</td></tr></tbody></table><p></p></div><div class="div3">
-<h4><a id="embedded-content-vocabulary-font"></a>9.1.4 font</h4><p>The <code>font</code> element is used to define an author supplied font resource.</p><p>A <code>font</code> element may appear as a child of a <a href="#embedded-content-vocabulary-resources"><code>resources</code></a> element, referred to as a
+<h4><a id="embedded-content-vocabulary-font"></a>9.1.4 font</h4><p>The <code>font</code> element is used to define an author supplied <a href="#terms-font-resource">font resource</a>.</p><p>A <code>font</code> element may appear as a child of a <a href="#embedded-content-vocabulary-resources"><code>resources</code></a> element, referred to as a
<a href="#terms-font-defining-context">font defining context</a>.</p><p>The <code>font</code> element accepts as its children
zero or more elements in the <a href="#element-vocab-group-metadata"><code>Metadata.class</code></a> element group followed by zero or more
<a href="#embedded-content-vocabulary-source"><code>source</code></a> elements.</p><a id="elt-syntax-font"></a><table class="syntax"><caption>XML Representation – Element Information Item: font</caption><tbody><tr><td>
@@ -3351,7 +3354,7 @@
<em>Content:</em> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-source">source</a>*
</font>
</pre></div>
-</td></tr></tbody></table><p>A <code>font</code> element defines a font resource either (1) by referring to an <a href="#terms-external-data-resource">external data resource</a>
+</td></tr></tbody></table><p>A <code>font</code> element defines a <a href="#terms-font-resource">font resource</a> either (1) by referring to an <a href="#terms-external-data-resource">external data resource</a>
or (2) defining or referring to an <a href="#terms-embedded-data-resource">embedded data resource</a>, where the <a href="#terms-data-resource">data resource</a>
contains font content.</p><p>If a <code>font</code> element specifies a <a href="#embedded-content-attribute-src"><code>src</code></a> attribute, then it must not specify a
child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element. Conversely,
@@ -3361,14 +3364,14 @@
a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute, in which case the value of the
<a href="#embedded-content-attribute-type"><code>type</code></a> attribute must correspond with the media (content) type
of the referenced resource. Otherwise, a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute must not be specified.</p><p>If a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute is not specified or is specified as a generic type, such as <code>application/octet-stream</code>,
-and additional format information is known about a referenced font resource, then a <a href="#embedded-content-attribute-format"><code>format</code></a> attribute should be specified as a hint to the
-content processor.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A font format hint might be useful to a content processor to avoid accessing a font resource it knows it cannot decode.</p></div><p>If a <code>font</code> element includes a child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element, then
+and additional format information is known about a referenced <a href="#terms-font-resource">font resource</a>, then a <a href="#embedded-content-attribute-format"><code>format</code></a> attribute should be specified as a hint to the
+content processor.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A font format hint might be useful to a content processor to avoid accessing a <a href="#terms-font-resource">font resource</a> it knows it cannot decode.</p></div><p>If a <code>font</code> element includes a child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element, then
the <a href="#embedded-content-attribute-format"><code>format</code></a> attribute of the <code>source</code> child, if specified, must adhere to the <a href="#embedded-content-value-font-format"><font-format></a>
value expression.</p><p>If any of the <code>family</code>, <code>range</code>, <code>style</code>, or <code>weight</code> attributes are specified, then
-they override the family name, supported character ranges, style, and weight of the actual font resource. In particular,
-if the specified attribute value(s) differ from the value(s) of these font characteristics as encoded in the font resource, then
-the specified attribute value(s) are to be used instead of the font characteristics encoded in the font resource.</p><p>If any of the <code>family</code>, <code>range</code>, <code>style</code>, or <code>weight</code> attributes are not specified, then their values
-must be considered to be equal to the value(s) of the same named font characteristics encoded in the font resource.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Authors are advised to use subset fonts wherever possible. A subset font is a syntactically valid font resource that
+they override the family name, supported character ranges, style, and weight of the actual <a href="#terms-font-resource">font resource</a>. In particular,
+if the specified attribute value(s) differ from the value(s) of these font characteristics as encoded in the <a href="#terms-font-resource">font resource</a>, then
+the specified attribute value(s) are to be used instead of the font characteristics encoded in the <a href="#terms-font-resource">font resource</a>.</p><p>If any of the <code>family</code>, <code>range</code>, <code>style</code>, or <code>weight</code> attributes are not specified, then their values
+must be considered to be equal to the value(s) of the same named font characteristics encoded in the <a href="#terms-font-resource">font resource</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Authors are advised to use subset fonts wherever possible. A subset font is a syntactically valid <a href="#terms-font-resource">font resource</a> that
removes unreferenced glyphs and unreferenced glyph metrics. In general, a subset font is tied to a specific document, since it may have been generated
based on the actual character content of that document.</p></div><table border="1" class="ednote" summary="Editorial note: Font Loading Semantics"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Font Loading Semantics</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify font loading semantics, making as much use as possible (by reference) of material found at
<a href="http://dev.w3.org/csswg/css-fonts/#font-face-loading">CSS Font Module Level 3, Font Loading Guidelines</a>.</td></tr></table><p>The use of the <code>font</code> element is illustrated by the following example.</p><a id="embedded-content-vocabulary-font-example-1"></a><table class="example"><caption>Example Fragment – Font</caption><tbody><tr><td>
@@ -3390,22 +3393,27 @@
...
</pre></div>
</td></tr></tbody></table><p></p></div><div class="div3">
-<h4><a id="embedded-content-vocabulary-image"></a>9.1.5 image</h4><p>The <code>image</code> element is used to define an author supplied image resource.</p><p>An <code>image</code> element may appear in two contexts: (1) as a child of a <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element and
+<h4><a id="embedded-content-vocabulary-image"></a>9.1.5 image</h4><p>The <code>image</code> element is used to define an author supplied <a href="#terms-image-resource">image resource</a>.</p><p>An <code>image</code> element may appear in two contexts: (1) as a child of a <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element and
(2) as a child of an element in the <a href="#element-vocab-group-block">Block.class</a> element group, namely, as a child of a
<a href="#content-vocabulary-div"><code>div</code></a> or <a href="#content-vocabulary-p"><code>p</code></a> element, or
as a child of a <a href="#content-vocabulary-span"><code>span</code></a> element. The former is referred to as an
<a href="#terms-image-defining-context">image defining context</a>, the latter as an <a href="#terms-image-presentation-context">image presentation context</a>.</p><p>When an <code>image</code> element appears in an <a href="#terms-image-defining-context">image defining context</a>, it
-serves as a sharable definition of an image resource that may be referenced by another <code>image</code> element or by
+serves as a sharable definition of an <a href="#terms-image-resource">image resource</a> that may be referenced by another <code>image</code> element or by
a <a href="#style-attribute-backgroundImage"><code>tts:backgroundImage</code></a> style attribute
in the <a href="#terms-enclosing-document-instance">enclosing document instance</a>. In this case, the active time interval of the <code>image</code> element
-is the same as the active time interval of its parent <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A sharable definition of an image resource specifies an <a href="#content-attribute-id"><code>xml:id</code></a> attribute in order to be referenced
+is the same as the active time interval of its parent <a href="#embedded-content-vocabulary-resource"><code>resource</code></a> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A sharable definition of an <a href="#terms-image-resource">image resource</a> specifies an <a href="#content-attribute-id"><code>xml:id</code></a> attribute in order to be referenced
by an <code>image</code> element or by a <a href="#style-attribute-backgroundImage"><code>tts:backgroundImage</code></a> style attribute
in an <a href="#terms-image-presentation-context">image presentation context</a>.</p></div><p>When an <code>image</code> element appears in an <a href="#terms-image-presentation-context">image presentation context</a>, it
-serves as a non-sharable definition of an image resource that implies presentation (rendering) semantics.
+serves as a non-sharable definition of an <a href="#terms-image-resource">image resource</a> that implies presentation (rendering) semantics.
In this case, the active time interval of the <code>image</code> element is the same as the active time interval of its parent
<a href="#terms-content-element">content element</a>.
-</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A non-sharable definition of an image resource may or may not specify an <a href="#content-attribute-id"><code>xml:id</code></a> attribute, but this
-identifier is not referenced by other <code>image</code> elements, or, if it is, the reference is ignored.</p></div><p>The <code>image</code> element accepts as its children
+</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A non-sharable definition of an <a href="#terms-image-resource">image resource</a> may or may not specify an <a href="#content-attribute-id"><code>xml:id</code></a> attribute, but this
+identifier is not referenced by other <code>image</code> elements, or, if it is, the reference is ignored.</p></div><p>When an <code>image</code> element appears as a child of a <a href="#contentt-vocabulary-div"><code>div</code></a> element, then its presentation
+produces a block area in which the image is rendered; i.e., a block boundary is implied before and after the <code>image</code> element. In contrast,
+when an <code>image</code> element appears as a child of a <a href="#contentt-vocabulary-p"><code>p</code></a> or <a href="#contentt-vocabulary-span"><code>span</code></a>
+element, then its presentation produces an inline area in which the image is rendered; i.e., no block boundary is implied before and after the <code>image</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In <a href="#css2">[CSS2]</a>, these semantics would correspond to an <code>image</code> element being associated with a <code>display</code> style property with a
+value of <code>block</code> or <code>inline</code>, respectively.</p></div><p>The presentation of an <a href="#terms-image-resource">image resource</a> referenced by a
+<a href="#style-attribute-backgroundImage"><code>tts:backgroundImage</code></a> style attribute must not affect content layout.</p><p>The <code>image</code> element accepts as its children
zero or more elements in the <a href="#element-vocab-group-metadata"><code>Metadata.class</code></a> element group followed by zero or more
<a href="#embedded-content-vocabulary-source"><code>source</code></a> elements.</p><a id="elt-syntax-image"></a><table class="syntax"><caption>XML Representation – Element Information Item: image</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -3422,7 +3430,7 @@
<em>Content:</em> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-source">source</a>*
</image>
</pre></div>
-</td></tr></tbody></table><p>An <code>image</code> element defines an image resource either (1) by referring to an <a href="#terms-external-data-resource">external data resource</a>
+</td></tr></tbody></table><p>An <code>image</code> element defines an <a href="#terms-image-resource">image resource</a> either (1) by referring to an <a href="#terms-external-data-resource">external data resource</a>
or (2) defining or referring to an <a href="#terms-embedded-data-resource">embedded data resource</a>, where the <a href="#terms-data-resource">data resource</a>
contains image content.</p><p>If an <code>image</code> element specifies a <a href="#embedded-content-attribute-src"><code>src</code></a> attribute, then it must not specify a
child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element. Conversely,
@@ -3432,35 +3440,60 @@
a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute, in which case the value of the
<a href="#embedded-content-attribute-type"><code>type</code></a> attribute must correspond with the media (content) type
of the referenced resource. Otherwise, a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute must not be specified.</p><p>If a <a href="#embedded-content-attribute-type"><code>type</code></a> attribute is not specified or is specified as a generic type, such as <code>application/octet-stream</code>,
-and additional format information is known about a referenced image resource, then a <a href="#embedded-content-attribute-format"><code>format</code></a> attribute should be specified as a hint to the
+and additional format information is known about a referenced <a href="#terms-image-resource">image resource</a>, then a <a href="#embedded-content-attribute-format"><code>format</code></a> attribute should be specified as a hint to the
content processor.</p><p>If an <code>image</code> element includes a child <a href="#embedded-content-vocabulary-source"><code>source</code></a> element, then
the <a href="#embedded-content-attribute-format"><code>format</code></a> attribute of the <code>source</code> child, if specified, must adhere to the <a href="#embedded-content-value-image-format"><image-format></a>
-value expression.</p><p>The use of the <code>image</code> element is illustrated by the following examples.</p><a id="embedded-content-vocabulary-image-example-1"></a><table class="example"><caption>Example Fragment – External Image Resource</caption><tbody><tr><td>
-<div class="exampleInner"><pre>
-<image src="http://example.com/images/caption.png" type="image/png"/>
+value expression.</p><p>The use of the <code>image</code> element is illustrated by the following examples.</p><a id="embedded-content-vocabulary-image-example-1"></a><table class="example"><caption>Example Fragment – External Image Resources</caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<div>
+ <p>This division has a content image that appears as a block area after this paragraph.</p>
+ <image src="http://example.com/images/caption.png" type="image/png"/>
+<div>
+...
+<div tts:backgroundImage="http://example.com/images/background.png">
+ <p>This division has a background image that appears under this paragraph.</p>
+<div>
+...
</pre></div>
</td></tr></tbody></table><p></p><a id="embedded-content-vocabulary-image-example-2"></a><table class="example"><caption>Example Fragment – Sharable Embedded Image Resource</caption><tbody><tr><td>
<div class="exampleInner"><pre>
-<data xml:id="caption" type="image/png" length="119">
- iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8
- YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAMSURBVBhXY2BgYAAAAAQAAVzN/2kAAAAASUVORK5CYII=
-</data>
-...
-<image>
- <source src="#caption"/>
-</image>
-</pre></div>
-</td></tr></tbody></table><p></p><a id="embedded-content-vocabulary-image-example-3"></a><table class="example"><caption>Example Fragment – External Image Resource with Non-Sharable Image Fallback</caption><tbody><tr><td>
-<div class="exampleInner"><pre>
-<image>
- <source src="http://example.com/images/caption.png" type="image/png"/>
- <source>
- <data type="image/png" length="119">
+<head>
+ <resources>
+ <data xml:id="caption" type="image/png" length="119">
iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8
YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAMSURBVBhXY2BgYAAAAAQAAVzN/2kAAAAASUVORK5CYII=
</data>
- </source>
-</image>
+ </resources>
+</head>
+<body>
+ <div>
+ <p>
+ <image>
+ <source src="#caption"/>
+ </image>
+ <p>
+ ...
+ <p>
+ <image>
+ <source src="#caption"/>
+ </image>
+ <p>
+ </div>
+</body>
+</pre></div>
+</td></tr></tbody></table><p></p><a id="embedded-content-vocabulary-image-example-3"></a><table class="example"><caption>Example Fragment – External Image Resource with Non-Sharable Image Fallback</caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<div>
+ <image>
+ <source src="http://example.com/images/caption.png" type="image/png"/>
+ <source>
+ <data type="image/png" length="119">
+ iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8
+ YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAMSURBVBhXY2BgYAAAAAQAAVzN/2kAAAAASUVORK5CYII=
+ </data>
+ </source>
+ </image>
+</div>
</pre></div>
</td></tr></tbody></table><p></p></div><div class="div3">
<h4><a id="embedded-content-vocabulary-resources"></a>9.1.6 resources</h4><p>The <code>resources</code> element is a container element used to group
@@ -3578,7 +3611,7 @@
<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 <audio></b></a></p></li><li><p><a href="#embedded-content-value-audio-format"><b>9.3.2 <audio-format></b></a></p></li><li><p><a href="#embedded-content-value-data"><b>9.3.3 <data></b></a></p></li><li><p><a href="#embedded-content-value-data-format"><b>9.3.4 <data-format></b></a></p></li><li><p><a href="#embedded-content-value-font"><b>9.3.5 <font></b></a></p></li><li><p><a href="#embedded-content-value-font-format"><b>9.3.6 <font-format></b></a></p></li><li><p><a href="#embedded-content-value-format"><b>9.3.7 <format></b></a></p></li><li><p><a href="#embedded-content-value-image"><b>9.3.8 <image></b></a></p></li><li><p><a href="#embedded-content-value-image-format"><b>9.3.9 <image-format></b></a></p></li><li><p><a href="#embedded-content-value-unicode-range"><b>9.3.10 <unicode-range></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 <audio></h4><p>An <audio> value expression is used to specify an audio resource by reference.</p><a id="audio-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <audio></caption><tbody><tr><td>
+<h4><a id="embedded-content-value-audio"></a>9.3.1 <audio></h4><p>An <audio> 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 – <audio></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<audio>
: <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
@@ -3586,8 +3619,8 @@
</td></tr></tbody></table><p>If an <audio> value 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-audio"><code>audio</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-audio-format"></a>9.3.2 <audio-format></h4><p>An <audio-format> expression is used to specify the format of a audio resource. Additional format information is useful in the case
-of audio resources that lack a registered media (content) type.</p><a id="audio-format-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <audio-format></caption><tbody><tr><td>
+<h4><a id="embedded-content-value-audio-format"></a>9.3.2 <audio-format></h4><p>An <audio-format> expression is used to specify the format of a <a href="#terms-audio-resource">audio resource</a>. Additional format information is useful in the case
+of <a href="#terms-audio-resource">audio resources</a> that lack a registered media (content) type.</p><a id="audio-format-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <audio-format></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<audio-format>
: <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
@@ -3614,7 +3647,7 @@
</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 <font></h4><p>An <font> expression is used to specify an font resource by reference.</p><a id="font-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <font></caption><tbody><tr><td>
+<h4><a id="embedded-content-value-font"></a>9.3.5 <font></h4><p>An <font> 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 – <font></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<font>
: <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
@@ -3622,8 +3655,8 @@
</td></tr></tbody></table><p>If an <font> 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
<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 <font-format></h4><p>A <font-format> expression is used to specify the format of a font resource. Additional format information is useful in the case
-of font resources due that lack a registered media (content) type.</p><a id="font-format-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <font-format></caption><tbody><tr><td>
+<h4><a id="embedded-content-value-font-format"></a>9.3.6 <font-format></h4><p>A <font-format> 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 – <font-format></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<font-format>
: eot // embedded opentype
@@ -3648,7 +3681,7 @@
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 <image></h4><p>An <image> expression is used to specify an image resource by reference.</p><a id="image-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <image></caption><tbody><tr><td>
+<h4><a id="embedded-content-value-image"></a>9.3.8 <image></h4><p>An <image> 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 – <image></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<image>
: <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
@@ -3656,8 +3689,8 @@
</td></tr></tbody></table><p>If an <image> 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 <image-format></h4><p>An <image-format> expression is used to specify the format of a image resource. Additional format information is useful in the case
-of image resources that lack a registered media (content) type.</p><a id="image-format-value-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <image-format></caption><tbody><tr><td>
+<h4><a id="embedded-content-value-image-format"></a>9.3.9 <image-format></h4><p>An <image-format> 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 – <image-format></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<image-format>
: <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
@@ -3860,13 +3893,13 @@
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
-span.</p><p>An <a href="#embedded-content-value-image"><image></a> expression used with this style property may directly reference an external image resource;
+span.</p><p>An <a href="#embedded-content-value-image"><image></a> expression used with this style property may directly reference an external <a href="#terms-image-resource">image resource</a>;
however, authors should refrain from doing so, and instead, constrain their usage to only refer to <a href="#embedded-content-vocabulary-image"><code>image</code></a>
children of a <a href="#embedded-content-vocabulary-resources"><code>resources</code></a> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Referring indirectly to an image by means of an <a href="#embedded-content-vocabulary-image"><code>image</code></a> element makes it possible to
specify an image as an <a href="#terms-embedded-data-resource">embedded data resource</a>, and specify
additional information about the image, such as its content type, etc. Furthermore, by exploiting the use of multiple
<a href="#embedded-content-vocabulary-source"><code>source</code></a> children in an <a href="#embedded-content-vocabulary-image"><code>image</code></a> element,
-it becomes possible to specify resolution specific images and fallback image resources.</p></div><p>The <code>tts:backgroundImage</code> style is illustrated by the following example.</p><a id="style-attribute-backgroundImage-example-1"></a><table class="example"><caption>Example Fragment – Background Image using Embedded Image Resource</caption><tbody><tr><td>
+it becomes possible to specify resolution specific images and fallback <a href="#terms-image-resource">image resources</a>.</p></div><p>The <code>tts:backgroundImage</code> style is illustrated by the following example.</p><a id="style-attribute-backgroundImage-example-1"></a><table class="example"><caption>Example Fragment – Background Image using Embedded Image Resource</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<head>
<resources>
@@ -4267,8 +4300,8 @@
§ 7.9.2.</p></div></div><div class="div3">
<h4><a id="style-attribute-fontSelectionStrategy"></a>10.2.13 tts:fontSelectionStrategy</h4><table border="1" class="ednote" summary="Editorial note: Define tts:fontSelectionStrategy"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Define tts:fontSelectionStrategy</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define <code>tts:fontSelectionStrategy</code> style property based on
the XSL 1.1 <a href="http://www.w3.org/TR/xsl/#font-selection-strategy">font-selection-strategy</a> and
-recent <a href="http://lists.w3.org/Archives/Public/public-tt/2014Nov/0051.html">TTWG ML thread</a>.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Font Selection"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Font Selection</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify font selection semantics, including how multiple author defined font resources combine
-with (local) platform defined font resources to obtain an ordered list of font resources for performing
+recent <a href="http://lists.w3.org/Archives/Public/public-tt/2014Nov/0051.html">TTWG ML thread</a>.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Font Selection"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Font Selection</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify font selection semantics, including how multiple author defined <a href="#terms-font-resource">font resources</a> combine
+with (local) platform defined <a href="#terms-font-resource">font resources</a> to obtain an ordered list of <a href="#terms-font-resource">font resources</a> for performing
character to glyph mapping.</td></tr></table></div><div class="div3">
<h4><a id="style-attribute-fontSize"></a>10.2.14 tts:fontSize</h4><p>The <code>tts:fontSize</code> attribute is used to specify a style property
that defines the font size for glyphs that are selected for glyph areas
@@ -7305,7 +7338,9 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:desc</code> element is defined by this specification.</p></div><p>Examples of the <code>ttm:desc</code> element are shown above in
<a href="#metadata-vocabulary-metadata-example-1"><b>Example Fragment – Document Metadata</b></a> and
<a href="#metadata-vocabulary-metadata-example-2"><b>Example Fragment – Element Metadata</b></a>.</p></div><div class="div3">
-<h4><a id="metadata-vocabulary-item"></a>14.1.6 ttm:item</h4><p>The <code>ttm:item</code> element is used to express arbitrary named metadata items.</p><a id="elt-syntax-metadata-item"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:item</caption><tbody><tr><td>
+<h4><a id="metadata-vocabulary-item"></a>14.1.6 ttm:item</h4><p>The <code>ttm:item</code> element is used to express arbitrary named metadata items.</p><p>The <code>ttm:item</code> element accepts one of the following two content models:
+(1) one or more text nodes (i.e., <code>#PCDATA</code>) or
+(2) zero or more nested <a href="#metadata-vocabulary-item">ttm:item</a> elements.</p><a id="elt-syntax-metadata-item"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:item</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttm:item
<a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
@@ -7314,31 +7349,37 @@
<a href="#content-attribute-lang">xml:lang</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute not in default or any TT namespace</em>}>
- <em>Content:</em> #PCDATA
+ <em>Content:</em> #PCDATA | <a href="#metadata-vocabulary-item">ttm:item</a>*
</ttm:item>
</pre></div>
</td></tr></tbody></table><p>A <code>name</code> attribute must be specified to identify the name of the item, the value of which must adhere to
an <a href="#metadata-value-item-name"><item-name></a> value expression.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>No general constraint is placed on the appearance of multiple named metadata items that specify the same name; however,
-the definition of a specific named item may further constrain the context of use as well as the potential appearance of multiple items that share the same name.</p></div><p>The value of a named metadata item is the character content of the <code>ttm:item</code> element, which may be empty.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A particular named item may be defined so as to imply a particular value in the absence of a specified value.</p></div><p>The use of a named metadata item is illustrated by the following example, which shows the use of a named metadata item
+the definition of a specific named item may further constrain the context of use as well as the potential appearance of multiple items that share the same name.</p></div><p>The value of a named metadata item is
+(1) empty if the element has no child text or element nodes,
+(2) the character content of the <code>ttm:item</code> element when that element's children consists solely of text nodes, or
+(3) a collection of named metadata sub-items.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The definition of a particular named item will typically constrain the set of permitted values. Furthermore, it may
+specify that a particular value is implied in the absence of a specified value.</p></div><p>The use of a named metadata item is illustrated by the following example, which shows the use of a named metadata item
in order to associate a <a href="#terms-simple-data-embedding">simple data embedding</a> with an original file name.</p><a id="metadata-vocabulary-item-example-1"></a><table class="example"><caption>Example Fragment – Named Metadata Item</caption><tbody><tr><td>
<div class="exampleInner"><pre>
...
<image>
<source>
<data type="image/png">
- <metadata xmlns:ttm="http://www.w3.org/ns/ttml#metadata">
- <span class="strong"><ttm:item name="originalFileName">image.png</ttm:item></span>
- </metadata>
+ <span class="strong"><ttm:item name="originalFileName" xmlns:ttm="http://www.w3.org/ns/ttml#metadata">image.png</ttm:item></span>
<chunk length="119">
- iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8
- YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAMSURBVBhXY2BgYAAAAAQAAVzN/2kAAAAASUVORK5CYII=
+ iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8
+ YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAMSURBVBhXY2BgYAAAAAQAAVzN/2kAAAAASUVORK5CYII=
</chunk>
</data>
- <source>
-<image>
+ </source>
+</image>
...
</pre></div>
-</td></tr></tbody></table><p></p></div><div class="div3">
+</td></tr></tbody></table><p></p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above example makes use of a single <a href="#embedded-content-vocabulary-chunk">chunk</a> element in order
+to include a <code>ttm:item</code> element as a child of the <a href="#embedded-content-vocabulary-data">data</a> element;
+i.e., if the encoded image bytes had been included directly as #PCDATA in the <a href="#embedded-content-vocabulary-data">data</a> element,
+then it would not have been possible to include the <code>ttm:item</code> child element. See the supported content models on the
+<a href="#embedded-content-vocabulary-data">data</a> element for more information.</p></div></div><div class="div3">
<h4><a id="metadata-vocabulary-name"></a>14.1.7 ttm:name</h4><p>The <code>ttm:name</code> element is used to specify a name of a person, character,
group, or organization.</p><a id="elt-syntax-metadata-name"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:name</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -7452,6 +7493,9 @@
| cea708EasyReader
| cea708FCCMinimum
| cea708ServiceNumber
+ | cea708TransformMode
+ | cea708TransformOrigin
+ | cea708TransformTimingThreshold
| creationDate
| creationCountryOfOrigin
| editor
@@ -7465,6 +7509,7 @@
| readingSpeed
| revisionDate
| revisionNumber
+ | sourceFormat
| subtitleCount
| subtitleReferenceCode
| targetAspectRatio
@@ -7486,7 +7531,10 @@
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-cea708EasyReader"></a><code>cea708EasyReader</code></dt><dd><p>A boolean that expresses whether a CEA-708 caption service is characterized for use with an easy reader, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:boolean</a>.</p></dd><dt class="label"><a id="named-item-cea708FCCMinimum"></a><code>cea708FCCMinimum</code></dt><dd><p>A boolean that expresses whether a CEA-708 caption service is characterized as conforming to minimum FCC decoder requirements, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:boolean</a>.</p></dd><dt class="label"><a id="named-item-cea708ServiceNumber"></a><code>cea708ServiceNumber</code></dt><dd><p>An integer that expresses the service number of a CEA-708 caption service, where the value
-adheres to <a href="http://www.w3.org/TR/xmlschema-2/#positiveInteger">xsd:positiveInteger</a> and is less than 32.</p></dd><dt class="label"><a id="named-item-creationDate"></a><code>creationDate</code></dt><dd><p>A date that expresses the creation date of this document, where the value
+adheres to <a href="http://www.w3.org/TR/xmlschema-2/#positiveInteger">xsd:positiveInteger</a> and is less than 32.</p></dd><dt class="label"><a id="named-item-cea708TransformMode"></a><code>cea708TransformMode</code></dt><dd><p>One of the token values <code>enhanced</code> or <code>preserved</code>.</p></dd><dt class="label"><a id="named-item-cea708TransformOrigin"></a><code>cea708TransformOrigin</code></dt><dd><p>Either the token <code>none</code> or an <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>,
+where the latter expresses a CEA-708 transformation source format.</p></dd><dt class="label"><a id="named-item-cea708TransformTimingThreshold"></a><code>cea708TransformTimingThreshold</code></dt><dd><p>A real number that expresses a threshold parameter used to suppress the inclusion of temporary timed states when
+transforming amongst a CEA-708 caption service and a <a href="#terms-timed-text-content-document">timed text content document</a>,
+where the value adheres to <a href="http://www.w3.org/TR/xmlschema-2/#boolean">xsd:float</a>.</p></dd><dt class="label"><a id="named-item-creationDate"></a><code>creationDate</code></dt><dd><p>A date that expresses the creation date of this document, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#date">xsd:date</a>.</p></dd><dt class="label"><a id="named-item-creationCountryOfOrigin"></a><code>creationCountryOfOrigin</code></dt><dd><p>A string that expresses a the country or origin code associated with this document, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-editor"></a><code>editor</code></dt><dd><p>A string that expresses the name of one or more editors, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-editorContact"></a><code>editorContact</code></dt><dd><p>A string that expresses the contact details of one or more editors, where the value
@@ -7501,13 +7549,16 @@
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-readingSpeed"></a><code>readingSpeed</code></dt><dd><p>An integer that expresses the reading speed in words per minute, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#positiveInteger">xsd:positiveInteger</a>.</p></dd><dt class="label"><a id="named-item-revisionDate"></a><code>revisionDate</code></dt><dd><p>A date that expresses the last revision date of this document, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#date">xsd:date</a>.</p></dd><dt class="label"><a id="named-item-revisionNumber"></a><code>revisionNumber</code></dt><dd><p>A non-negative integer that expresses the revision number of this document, where the value
-adheres to <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>.</p></dd><dt class="label"><a id="named-item-subtitleCount"></a><code>subtitleCount</code></dt><dd><p>A non-negative integer that expresses the number of subtitles (captions) in this document, where the value
+adheres to <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>.</p></dd><dt class="label"><a id="named-item-sourceFormat"></a><code>sourceFormat</code></dt><dd><p>A string that expresses the source subtitle or caption format from which the <a href="#terms-enclosing-document-instance">enclosing document instance</a>
+was transformed, where the value adheres to either <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
+or <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>.</p></dd><dt class="label"><a id="named-item-subtitleCount"></a><code>subtitleCount</code></dt><dd><p>A non-negative integer that expresses the number of subtitles (captions) in this document, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>.</p></dd><dt class="label"><a id="named-item-subtitleReferenceCode"></a><code>subtitleReferenceCode</code></dt><dd><p>A string that expresses a subtitle reference code, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-targetAspectRatio"></a><code>targetAspectRatio</code></dt><dd><p>A string that expresses the target video's aspect ratio, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-targetActiveFormatDescriptor"></a><code>targetActiveFormatDescriptor</code></dt><dd><p>A string that expresses the target video's active format descriptor, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-targetBarData"></a><code>targetBarData</code></dt><dd><p>A string that expresses the target video's bar data, where the value
-adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-targetFormat"></a><code>targetFormat</code></dt><dd><p>A string that expresses the target subtitle or caption format, where the value
-adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-translatedEpisodeTitle"></a><code>translatedEpisodeTitle</code></dt><dd><p>A string that expresses the episode title in the translated (local) language, where the value
+adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-targetFormat"></a><code>targetFormat</code></dt><dd><p>A string that expresses the target subtitle or caption format to which the <a href="#terms-enclosing-document-instance">enclosing document instance</a>
+is intended to be transformed, where the value adheres to either <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
+or <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>.</p></dd><dt class="label"><a id="named-item-translatedEpisodeTitle"></a><code>translatedEpisodeTitle</code></dt><dd><p>A string that expresses the episode title in the translated (local) language, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-translatedProgramTitle"></a><code>translatedProgramTitle</code></dt><dd><p>A string that expresses the program title in the translated (local) language, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-translator"></a><code>translator</code></dt><dd><p>A string that expresses the name of one or more translators, where the value
adheres to <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>.</p></dd><dt class="label"><a id="named-item-translatorContact"></a><code>translatorContact</code></dt><dd><p>A string that expresses the contact details of one or more translators, where the value
@@ -9326,7 +9377,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="d3e32735"></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="d3e33050"></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
@@ -9383,7 +9434,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="d3e33252"></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="d3e33567"></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
@@ -9475,9 +9526,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> <a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e34245"></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="d3e34560"></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="d3e34409"></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="d3e34724"></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">