--- a/ttml2/spec/ttml2.html Sat Nov 22 10:10:45 2014 -0700
+++ b/ttml2/spec/ttml2.html Sat Nov 22 10:11:09 2014 -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/11/22 00:45:23 $<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/22 17:10:45 $<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/11/22 00:45:23 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/11/22 17:10:45 $ @@ @@@@ @@@@</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>
@@ -199,10 +199,12 @@
9.2.2 <a href="#embedded-content-attribute-type">type</a><br>
9.3 <a href="#embedded-content-value-expressions">Embedded Content Value Expressions</a><br>
9.3.1 <a href="#embedded-content-value-audio"><audio></a><br>
- 9.3.2 <a href="#embedded-content-value-font"><font></a><br>
- 9.3.3 <a href="#embedded-content-value-font-format"><font-format></a><br>
- 9.3.4 <a href="#embedded-content-value-image"><image></a><br>
- 9.3.5 <a href="#embedded-content-value-unicode-range"><unicode-range></a><br>
+ 9.3.2 <a href="#embedded-content-value-audio-format"><audio-format></a><br>
+ 9.3.3 <a href="#embedded-content-value-font"><font></a><br>
+ 9.3.4 <a href="#embedded-content-value-font-format"><font-format></a><br>
+ 9.3.5 <a href="#embedded-content-value-image"><image></a><br>
+ 9.3.6 <a href="#embedded-content-value-image-format"><image-format></a><br>
+ 9.3.7 <a href="#embedded-content-value-unicode-range"><unicode-range></a><br>
10 <a href="#styling">Styling</a><br>
10.1 <a href="#styling-element-vocabulary">Styling Element Vocabulary</a><br>
10.1.1 <a href="#styling-vocabulary-initial">initial</a><br>
@@ -478,11 +480,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="#d3e30333">Element Derivation</a><br>
- J.2 <a href="#d3e30850">Attribute Derivation</a><br>
+ J.1 <a href="#d3e30568">Element Derivation</a><br>
+ J.2 <a href="#d3e31085">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e31843">Requirements</a><br>
- K.2 <a href="#d3e32007">Guidelines</a><br>
+ K.1 <a href="#d3e32078">Requirements</a><br>
+ K.2 <a href="#d3e32242">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>
@@ -2672,7 +2674,7 @@
{<em>any attribute in TT Metadata namespace</em>}
{<em>any attribute in TT Style namespace</em>}
{<em>any attribute not in default or any TT namespace</em>}>
- <em>Content:</em> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#element-vocab-group-animation">Animation.class</a>*, <a href="#element-vocab-group-layout">Layout.class</a>?, <a href="#element-vocab-group-block">Block.class</a>|<a href="#element-vocab-group-embedded">Embedded.class</a>)*
+ <em>Content:</em> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#element-vocab-group-animation">Animation.class</a>*, <a href="#element-vocab-group-layout">Layout.class</a>?, (<a href="#element-vocab-group-block">Block.class</a>|<a href="#element-vocab-group-embedded">Embedded.class</a>)*
</div>
</pre></div>
</td></tr></tbody></table><p>An author may associate a set of style properties with a <code>div</code> element by means of either
@@ -2854,10 +2856,12 @@
<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>
<div class="exampleInner"><pre>
<audio
+ format = <a href="#embedded-content-value-audio-format"><audio-format></a>
src = <a href="#embedded-content-value-audio"><audio></a>
<a href="#data-attribute-type">type</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#content-attribute-id">xml:id</a> = ID
<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 in TT Metadata namespace</em>}
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-source">source</a>*
@@ -2872,7 +2876,11 @@
<a href="#terms-enclosing-document-instance">enclosing document instance</a>, then it should specify a
a <a href="#data-attribute-type"><code>type</code></a> attribute, in which case the value of the
<a href="#data-attribute-type"><code>type</code></a> attribute must correspond with the media (content) type
-of the referenced resource. Otherwise, a <a href="#data-attribute-type"><code>type</code></a> attribute must not be specified.</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>
+of the referenced resource. Otherwise, a <a href="#data-attribute-type"><code>type</code></a> attribute must not be specified.</p><p>If a <a href="#data-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 <code>format</code> 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 <code>format</code> 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>
<div class="exampleInner"><pre>
...
<audio src="http://example.com/audio/description.mp3" type="audio/mp3"/>
@@ -2917,9 +2925,12 @@
<div class="exampleInner"><pre>
<data
<a href="#data-attribute-encoding">encoding</a> = (base16|base32|base32hex|base64|base64url) : <em>see prose below</em>
+ format = <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
length = <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>
<span class="reqattr"><a href="#data-attribute-type">type</a></span> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#content-attribute-id">xml:id</a> = ID
+ <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 | (<a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-chunk">chunk</a>+)
</data>
@@ -2933,7 +2944,9 @@
<code>data</code> element. When decoding, if a specified length value does not match the number of decoded bytes, then a zero length byte sequence must be returned.
If no <code>length</code> attribute is specified, then the data resource is considered to have a length equal to the actual number of decoded bytes.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intention of the <code>length</code> attribute is to provide a means to perform a simple integrity check on decoded data. Note that this check does not guarantee
data integrity during transport, i.e., the data could be modified without modifying the length.</p></div><p>A <a href="#data-attribute-type"><code>type</code></a> attribute must be specified, and must correspond with the media (content) type of the data resource.
-In the absence of a defined type, the type <code>application/octet-stream</code> should be used.</p><p>The use of simple data is illustrated by the following example.</p><a id="embedded-content-vocabulary-data-example-1"></a><table class="example"><caption>Example Fragment – Simple Data</caption><tbody><tr><td>
+In the absence of a defined type, the type <code>application/octet-stream</code> should be used.</p><p>If a <a href="#data-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 data resource, then a <code>format</code> attribute should be specified as a hint to the
+content processor.</p><p>The use of simple data is illustrated by the following example.</p><a id="embedded-content-vocabulary-data-example-1"></a><table class="example"><caption>Example Fragment – Simple Data</caption><tbody><tr><td>
<div class="exampleInner"><pre>
...
<data type="text/plain; charset=us-ascii" length="269">
@@ -2959,6 +2972,8 @@
<a href="#data-attribute-type">type</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
weight = (normal|bold)
<a href="#content-attribute-id">xml:id</a> = ID
+ <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> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-source">source</a>*
</font>
@@ -2972,7 +2987,7 @@
<a href="#terms-enclosing-document-instance">enclosing document instance</a>, then it should specify a
a <a href="#data-attribute-type"><code>type</code></a> attribute, in which case the value of the
<a href="#data-attribute-type"><code>type</code></a> attribute must correspond with the media (content) type
-of the referenced resource. Otherwise, a <a href="#data-attribute-type"><code>type</code></a> attribute must not be specified.</p><p>If a <a href="#data-attribute-type"><code>type</code></a> attribute is specified as a generic type, such as <code>application/octet-stream</code>,
+of the referenced resource. Otherwise, a <a href="#data-attribute-type"><code>type</code></a> attribute must not be specified.</p><p>If a <a href="#data-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 <code>format</code> 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
the <code>format</code> attribute of the <code>source</code> child, if specified, must adhere to the <a href="#embedded-content-value-font-format"><font-format></a>
@@ -3004,9 +3019,12 @@
<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>
<image
+ format = <a href="#embedded-content-value-image-format"><image-format></a>
src = <a href="#embedded-content-value-image"><image></a>
<a href="#data-attribute-type">type</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#content-attribute-id">xml:id</a> = ID
+ <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 in TT Metadata namespace</em>}
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-source">source</a>*
@@ -3021,7 +3039,11 @@
<a href="#terms-enclosing-document-instance">enclosing document instance</a>, then it should specify a
a <a href="#data-attribute-type"><code>type</code></a> attribute, in which case the value of the
<a href="#data-attribute-type"><code>type</code></a> attribute must correspond with the media (content) type
-of the referenced resource. Otherwise, a <a href="#data-attribute-type"><code>type</code></a> attribute must not be specified.</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>
+of the referenced resource. Otherwise, a <a href="#data-attribute-type"><code>type</code></a> attribute must not be specified.</p><p>If a <a href="#data-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 <code>format</code> 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 <code>format</code> 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"/>
</pre></div>
@@ -3059,6 +3081,8 @@
<div class="exampleInner"><pre>
<resources
<a href="#content-attribute-id">xml:id</a> = ID
+ <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> <a href="#element-vocab-group-metadata">Metadata.class</a>*, (<a href="#element-vocab-group-data">Data.class</a>|<a href="#element-vocab-group-embedded">Embedded.class</a>|<a href="#element-vocab-group-font">Font.class</a>)*
</resources>
@@ -3077,10 +3101,12 @@
an <em>nested embedded source</em>.</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>
<source
- format = <a href="http://www.w3.org/TR/xmlschema-2/#ident">xsd:ident</a>
+ format = <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
src = <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
<a href="#data-attribute-type">type</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#content-attribute-id">xml:id</a> = ID
+ <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> <a href="#element-vocab-group-metadata">Metadata.class</a>*, <a href="#embedded-content-vocabulary-data">data</a>?
</source>
@@ -3142,7 +3168,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 <audio></b></a></p></li><li><p><a href="#embedded-content-value-font"><b>9.3.2 <font></b></a></p></li><li><p><a href="#embedded-content-value-font-format"><b>9.3.3 <font-format></b></a></p></li><li><p><a href="#embedded-content-value-image"><b>9.3.4 <image></b></a></p></li><li><p><a href="#embedded-content-value-unicode-range"><b>9.3.5 <unicode-range></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 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-font"><b>9.3.3 <font></b></a></p></li><li><p><a href="#embedded-content-value-font-format"><b>9.3.4 <font-format></b></a></p></li><li><p><a href="#embedded-content-value-image"><b>9.3.5 <image></b></a></p></li><li><p><a href="#embedded-content-value-image-format"><b>9.3.6 <image-format></b></a></p></li><li><p><a href="#embedded-content-value-unicode-range"><b>9.3.7 <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>
@@ -3153,7 +3179,15 @@
</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-font"></a>9.3.2 <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-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 of standardization of 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>
+</pre></div>
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification does not standardize the set of format tokens for use with audio 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.3 <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>
<div class="exampleInner"><pre>
<font>
: <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
@@ -3161,7 +3195,7 @@
</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.3 <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
+<h4><a id="embedded-content-value-font-format"></a>9.3.4 <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 to the lack of standardization of 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>
@@ -3169,9 +3203,12 @@
| otf // opentype
| ttf // truetype
| woff // web open font format
-</pre></div>
-</td></tr></tbody></table></div><div class="div3">
-<h4><a id="embedded-content-value-image"></a>9.3.4 <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>
+ | <a href="http://www.w3.org/TR/xmlschema-2/#token">xsd:token</a>
+</pre></div>
+</td></tr></tbody></table><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-image"></a>9.3.5 <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>
<div class="exampleInner"><pre>
<image>
: <a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a>
@@ -3179,7 +3216,15 @@
</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-unicode-range"></a>9.3.5 <unicode-range></h4><p>A <unicode-range> 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 – <unicode-range></caption><tbody><tr><td>
+<h4><a id="embedded-content-value-image-format"></a>9.3.6 <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 of standardization of 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>
+</pre></div>
+</td></tr></tbody></table><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.7 <unicode-range></h4><p>A <unicode-range> 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 – <unicode-range></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<unicode-range>
: range ("," range)*
@@ -8712,7 +8757,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="d3e30333"></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="d3e30568"></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
@@ -8769,7 +8814,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="d3e30850"></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="d3e31085"></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
@@ -8861,9 +8906,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="d3e31843"></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="d3e32078"></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="d3e32007"></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="d3e32242"></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">