--- a/ttml2/spec/ttml2.html Sun Nov 30 12:46:39 2014 -0700
+++ b/ttml2/spec/ttml2.html Sun Nov 30 12:46:51 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/29 03:34:35 $<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/30 19:46:39 $<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/29 03:34:35 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2014/11/30 19:46:39 $ @@ @@@@ @@@@</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>
@@ -244,27 +244,29 @@
10.2.15 <a href="#style-attribute-fontStyle">tts:fontStyle</a><br>
10.2.16 <a href="#style-attribute-fontVariantPosition">tts:fontVariantPosition</a><br>
10.2.17 <a href="#style-attribute-fontWeight">tts:fontWeight</a><br>
- 10.2.18 <a href="#style-attribute-lineHeight">tts:lineHeight</a><br>
- 10.2.19 <a href="#style-attribute-opacity">tts:opacity</a><br>
- 10.2.20 <a href="#style-attribute-origin">tts:origin</a><br>
- 10.2.21 <a href="#style-attribute-overflow">tts:overflow</a><br>
- 10.2.22 <a href="#style-attribute-padding">tts:padding</a><br>
- 10.2.23 <a href="#style-attribute-position">tts:position</a><br>
- 10.2.24 <a href="#style-attribute-ruby">tts:ruby</a><br>
- 10.2.25 <a href="#style-attribute-rubyAlign">tts:rubyAlign</a><br>
- 10.2.26 <a href="#style-attribute-rubyOffset">tts:rubyOffset</a><br>
- 10.2.27 <a href="#style-attribute-rubyPosition">tts:rubyPosition</a><br>
- 10.2.28 <a href="#style-attribute-showBackground">tts:showBackground</a><br>
- 10.2.29 <a href="#style-attribute-textAlign">tts:textAlign</a><br>
- 10.2.30 <a href="#style-attribute-textDecoration">tts:textDecoration</a><br>
- 10.2.31 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
- 10.2.32 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
- 10.2.33 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
- 10.2.34 <a href="#style-attribute-visibility">tts:visibility</a><br>
- 10.2.35 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
- 10.2.36 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
- 10.2.37 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
- 10.3 <a href="#styling-style-value-expressions">Style Value Expressions</a><br>
+ 10.2.18 <a href="#style-attribute-height">tts:height</a><br>
+ 10.2.19 <a href="#style-attribute-lineHeight">tts:lineHeight</a><br>
+ 10.2.20 <a href="#style-attribute-opacity">tts:opacity</a><br>
+ 10.2.21 <a href="#style-attribute-origin">tts:origin</a><br>
+ 10.2.22 <a href="#style-attribute-overflow">tts:overflow</a><br>
+ 10.2.23 <a href="#style-attribute-padding">tts:padding</a><br>
+ 10.2.24 <a href="#style-attribute-position">tts:position</a><br>
+ 10.2.25 <a href="#style-attribute-ruby">tts:ruby</a><br>
+ 10.2.26 <a href="#style-attribute-rubyAlign">tts:rubyAlign</a><br>
+ 10.2.27 <a href="#style-attribute-rubyOffset">tts:rubyOffset</a><br>
+ 10.2.28 <a href="#style-attribute-rubyPosition">tts:rubyPosition</a><br>
+ 10.2.29 <a href="#style-attribute-showBackground">tts:showBackground</a><br>
+ 10.2.30 <a href="#style-attribute-textAlign">tts:textAlign</a><br>
+ 10.2.31 <a href="#style-attribute-textDecoration">tts:textDecoration</a><br>
+ 10.2.32 <a href="#style-attribute-textOrientation">tts:textOrientation</a><br>
+ 10.2.33 <a href="#style-attribute-textOutline">tts:textOutline</a><br>
+ 10.2.34 <a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a><br>
+ 10.2.35 <a href="#style-attribute-visibility">tts:visibility</a><br>
+ 10.2.36 <a href="#style-attribute-width">tts:width</a><br>
+ 10.2.37 <a href="#style-attribute-wrapOption">tts:wrapOption</a><br>
+ 10.2.38 <a href="#style-attribute-writingMode">tts:writingMode</a><br>
+ 10.2.39 <a href="#style-attribute-zIndex">tts:zIndex</a><br>
+ 10.3 <a href="#styling-style-value-expressions">Styling Value Expressions</a><br>
10.3.1 <a href="#style-value-alpha"><alpha></a><br>
10.3.2 <a href="#style-value-borderColor"><borderColor></a><br>
10.3.3 <a href="#style-value-borderStyle"><borderStyle></a><br>
@@ -276,9 +278,10 @@
10.3.9 <a href="#style-value-hexDigit"><hexDigit></a><br>
10.3.10 <a href="#style-value-integer"><integer></a><br>
10.3.11 <a href="#style-value-length"><length></a><br>
- 10.3.12 <a href="#style-value-namedColor"><namedColor></a><br>
- 10.3.13 <a href="#style-value-position"><position></a><br>
- 10.4 <a href="#semantics-style-resolution">Style Resolution</a><br>
+ 10.3.12 <a href="#style-value-measure"><measure></a><br>
+ 10.3.13 <a href="#style-value-namedColor"><namedColor></a><br>
+ 10.3.14 <a href="#style-value-position"><position></a><br>
+ 10.4 <a href="#semantics-styling">Styling Semantics</a><br>
10.4.1 <a href="#semantics-style-association">Style Association</a><br>
10.4.1.1 <a href="#semantics-style-association-inline">Inline Styling</a><br>
10.4.1.2 <a href="#semantics-style-association-referential">Referential Styling</a><br>
@@ -297,19 +300,21 @@
10.4.4.2 <a href="#semantics-style-resolution-processing-sss">Specified Style Set Processing</a><br>
10.4.4.3 <a href="#semantics-style-resolution-processing-css">Computed Style Set Processing</a><br>
10.4.4.4 <a href="#semantics-style-resolution-process-overall">Style Resolution Process</a><br>
+ 10.4.5 <a href="#semantics-style-automatic-measure-calculation">Automatic Measure Calculation</a><br>
11 <a href="#layout">Layout</a><br>
11.1 <a href="#layout-element-vocabulary">Layout Element Vocabulary</a><br>
11.1.1 <a href="#layout-vocabulary-layout">layout</a><br>
11.1.2 <a href="#layout-vocabulary-region">region</a><br>
11.2 <a href="#layout-attribute-vocabulary">Layout Attribute Vocabulary</a><br>
11.2.1 <a href="#layout-attribute-region">region</a><br>
- 11.3 <a href="#semantics-region-layout">Region Layout and Presentation</a><br>
- 11.3.1 <a href="#semantics-default-region">Default Region</a><br>
- 11.3.2 <a href="#semantics-inline-regions">Inline Regions</a><br>
- 11.3.3 <a href="#semantics-region-layout-step-1">Intermediate Synchronic Document Construction</a><br>
- 11.3.4 <a href="#semantics-region-layout-step-2">Synchronic Flow Processing</a><br>
- 11.3.5 <a href="#semantics-region-layout-example">Elaborated Example (Non-Normative)</a><br>
- 11.4 <a href="#semantics-line-layout">Line Layout</a><br>
+ 11.3 <a href="#semantics-layout">Layout Semantics</a><br>
+ 11.3.1 <a href="#semantics-region-layout">Region Layout and Presentation</a><br>
+ 11.3.1.1 <a href="#semantics-default-region">Default Region</a><br>
+ 11.3.1.2 <a href="#semantics-inline-regions">Inline Regions</a><br>
+ 11.3.1.3 <a href="#semantics-region-layout-step-1">Intermediate Synchronic Document Construction</a><br>
+ 11.3.1.4 <a href="#semantics-region-layout-step-2">Synchronic Flow Processing</a><br>
+ 11.3.1.5 <a href="#semantics-region-layout-example">Elaborated Example (Non-Normative)</a><br>
+ 11.3.2 <a href="#semantics-line-layout">Line Layout</a><br>
12 <a href="#timing">Timing</a><br>
12.1 <a href="#timing-element-vocabulary">Timing Element Vocabulary</a><br>
12.2 <a href="#timing-attribute-vocabulary">Timing Attribute Vocabulary</a><br>
@@ -319,7 +324,7 @@
12.2.4 <a href="#timing-attribute-timeContainer">timeContainer</a><br>
12.3 <a href="#timing-time-value-expressions">Time Value Expressions</a><br>
12.3.1 <a href="#timing-value-timeExpression"><timeExpression></a><br>
- 12.4 <a href="#timing-time-intervals">Time Intervals</a><br>
+ 12.4 <a href="#semantics-timing">Timing Semantics</a><br>
13 <a href="#animation">Animation</a><br>
13.1 <a href="#animation-element-vocabulary">Animation Element Vocabulary</a><br>
13.1.1 <a href="#animation-vocabulary-animate">animate</a><br>
@@ -499,11 +504,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="#d3e34192">Element Derivation</a><br>
- J.2 <a href="#d3e34709">Attribute Derivation</a><br>
+ J.1 <a href="#d3e34828">Element Derivation</a><br>
+ J.2 <a href="#d3e35345">Attribute Derivation</a><br>
K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
- K.1 <a href="#d3e35702">Requirements</a><br>
- K.2 <a href="#d3e35866">Guidelines</a><br>
+ K.1 <a href="#d3e36338">Requirements</a><br>
+ K.2 <a href="#d3e36502">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,7 +730,11 @@
a <a href="#embedded-content-vocabulary-source"><code>source</code></a> element child, or it may reference another
<a href="#embedded-content-vocabulary-audio"><code>audio</code></a> element specified in a
<a href="#terms-audio-definition-context">audio definition context</a>, or it may do both.</p></dd><dt class="label"><a id="terms-audio-resource"></a>[audio resource]</dt><dd><p>A <a href="#terms-data-resource">data resource</a> that contains coded or unencoded audio samples.</p></dd><dt class="label"><a id="terms-baseline-profile"></a>[baseline profile]</dt><dd><p>A <a href="#terms-profile">profile</a> referenced by the <code>use</code> attribute of a <code>ttp:profile</code> element,
-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
+which serves as a baseline (initial) set of specifications with which to populate the referencing profile.</p></dd><dt class="label"><a id="terms-block-display"></a>[block display]</dt><dd><p>Block display is a set of layout semantics that may be applied to a <a href="#terms-content-element">content element</a> in
+certain contexts, wherein child areas are composed sequentially in the block progression direction. In <a href="#css2">[CSS2]</a>,
+block display is indicated when a CSS <code>display</code> property with the value <code>block</code> is applied to a
+<a href="#terms-content-element">content element</a> during presentation processing. In <a href="#xsl11">[XSL 1.1]</a>, a block display
+occurs when composing a <code>fo:block</code> element.</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>
@@ -813,7 +822,16 @@
that is defined inline as an immediate child of
a <a href="#terms-content-element">content element</a> or <a href="#layout-vocabulary-region"><code>region</code></a> element associated with the animation.
There is a one-to-one relation between
-an inline animation element and its parent <a href="#terms-content-element">content element</a> or <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></dd><dt class="label"><a id="terms-inline-region"></a>[inline region]</dt><dd><p>A <a href="#terms-region">region</a> that is defined in an inline manner with respect to some
+an inline animation element and its parent <a href="#terms-content-element">content element</a> or <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></dd><dt class="label"><a id="terms-inline-block-display"></a>[inline block display]</dt><dd><p>Inline block display is a set of layout semantics that may be applied to a <a href="#terms-content-element">content element</a> in
+certain contexts, wherein a generated block area is treated as an an atomic area to be composed in an inline layout context, i.e., the block
+area is treated as if it were itself an inline area when considered externally, but as a block area which considered internally. In <a href="#css2">[CSS2]</a>,
+inline block display is indicated when a CSS <code>display</code> property with the value <code>inline-block</code> is applied to a
+<a href="#terms-content-element">content element</a> during presentation processing. In <a href="#xsl11">[XSL 1.1]</a>, an inline block display
+occurs when block content appears in an inline content context, e.g., when a <code>fo:block</code> appears as a child of <code>fo:inline</code>.</p></dd><dt class="label"><a id="terms-inline-display"></a>[inline display]</dt><dd><p>Inline display is a set of layout semantics that may be applied to a <a href="#terms-content-element">content element</a> in
+certain contexts, wherein child areas are composed sequentially in the inline progression direction. In <a href="#css2">[CSS2]</a>,
+inline display is indicated when a CSS <code>display</code> property with the value <code>inline</code> is applied to a
+<a href="#terms-content-element">content element</a> during presentation processing. In <a href="#xsl11">[XSL 1.1]</a>, an inline display
+occurs when composing a <code>fo:inline</code> element.</p></dd><dt class="label"><a id="terms-inline-region"></a>[inline region]</dt><dd><p>A <a href="#terms-region">region</a> that is defined in an inline manner with respect to some
<a href="#terms-content-element">content element</a> to be selected into (targeted to) the region.
An inline region is specified either explicitly by a <a href="#layout-vocabulary-region"><code>region</code></a> element child of
a <a href="#terms-content-element">content element</a> or implicitly by specifying a <a href="#style-attribute-extent">tts:extent</a>
@@ -1542,6 +1560,7 @@
<a href="#style-attribute-fontStyle">tts:fontStyle</a>,
<a href="#style-attribute-fontVariantPosition">tts:fontVariantPosition</a>,
<a href="#style-attribute-fontWeight">tts:fontWeight</a>,
+<a href="#style-attribute-height">tts:height</a>,
<a href="#style-attribute-lineHeight">tts:lineHeight</a>,
<a href="#style-attribute-opacity">tts:opacity</a>,
<a href="#style-attribute-origin">tts:origin</a>,
@@ -1559,6 +1578,7 @@
<a href="#style-attribute-textOutline">tts:textOutline</a>,
<a href="#style-attribute-unicodeBidi">tts:unicodeBidi</a>,
<a href="#style-attribute-visibility">tts:visibility</a>,
+<a href="#style-attribute-width">tts:width</a>,
<a href="#style-attribute-wrapOption">tts:wrapOption</a>,
<a href="#style-attribute-writingMode">tts:writingMode</a>,
<a href="#style-attribute-zIndex">tts:zIndex</a>
@@ -2405,7 +2425,7 @@
In this case, the <a href="#terms-content-processor">content processor</a> must create and maintain a
<a href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</a> within which these time
expressions are interpreted as further described in
-<a href="#timing-time-intervals"><b>12.4 Time Intervals</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When operating with <code>smpte</code> time base and
+<a href="#semantics-timing"><b>12.4 Timing Semantics</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When operating with <code>smpte</code> time base and
<code>continuous</code> marker mode, there is an implied time coordinate
space, the <a href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</a>,
defined by the monotonically increasing (or decreasing)
@@ -2601,7 +2621,7 @@
zero or one <code>body</code> element.</p><a id="elt-syntax-tt"></a><table class="syntax"><caption>XML Representation – Element Information Item: tt</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<tt
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#style-attribute-extent">tts:extent</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#style-attribute-position">tts:position</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#content-attribute-id">xml:id</a> = ID
@@ -2628,7 +2648,7 @@
in an external namespace, such as <code>m708:aspectRatio</code> as defined in <a href="#smpte2052">[SMPTE 2052-11]</a>, §5.4.4.
This would permit, for example, the interchange of information that reflects the
the semantics of <a href="#cea708e">[CEA-708-E]</a> , §4.5 “Caption Service Metadata”, “ASPECT RATIO”.</p></div><p>If the <a href="#style-attribute-position"><code>tts:position</code></a> attribute is specified on the <code>tt</code>
-element, then it must adhere to <a href="#style-attribute-position"><b>10.2.23 tts:position</b></a>, in which case it
+element, then it must adhere to <a href="#style-attribute-position"><b>10.2.24 tts:position</b></a>, in which case it
specifies the position of the <a href="#terms-root-container-region">root container region</a> relative to a reference positioning area.</p><p>Except for the <code>tts:extent</code> and <code>tts:position</code> attributes described above, an attribute in the TT Style Namespace should not
be specified on the <code>tt</code> element unless it denotes an inheritable style property, in which case such inheritable style property is available
for <a href="#semantics-style-inheritance-root">root style inheritance</a>. If a non-inheritable style property is specified, then
@@ -2659,7 +2679,7 @@
or <a href="#element-vocab-type-layout">Layout</a> elements.</p><a id="elt-syntax-head"></a><table class="syntax"><caption>XML Representation – Element Information Item: head</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<head
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -2684,7 +2704,7 @@
<body
<a href="#animation-attribute-animate">animate</a> = IDREFS
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#layout-attribute-region">region</a> = IDREF
@@ -2745,7 +2765,7 @@
<div
<a href="#animation-attribute-animate">animate</a> = IDREFS
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#layout-attribute-region">region</a> = IDREF
@@ -2797,7 +2817,7 @@
<p
<a href="#animation-attribute-animate">animate</a> = IDREFS
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#layout-attribute-region">region</a> = IDREF
@@ -2837,7 +2857,7 @@
implies that a <code>p</code> element constitutes a line break. In particular,
it is associated with a block-stacking constraint both before the first
generated line area and after the last generated line area. See
-<a href="#semantics-region-layout-step-2"><b>11.3.4 Synchronic Flow Processing</b></a> for further details.</p></div></div><div class="div3">
+<a href="#semantics-region-layout-step-2"><b>11.3.1.4 Synchronic Flow Processing</b></a> for further details.</p></div></div><div class="div3">
<h4><a id="content-vocabulary-span"></a>8.1.6 span</h4><p>The <code>span</code> element functions as a logical container and a temporal
structuring element for a sequence of textual content units having inline
level formatting semantics.</p><p>When presented on a visual medium, a <code>span</code> element is intended to
@@ -2853,7 +2873,7 @@
<span
<a href="#animation-attribute-animate">animate</a> = IDREFS
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#layout-attribute-region">region</a> = IDREF
@@ -2883,7 +2903,7 @@
<br
<a href="#animation-attribute-animate">animate</a> = IDREFS
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#layout-attribute-region">region</a> = IDREF
@@ -2925,7 +2945,7 @@
<a href="#xml10">[XML 1.0]</a>, §2.10, <em>White Space Handling</em>.</p><p>The <code>xml:space</code> attribute may be used with any element in
the core vocabulary catalog except parameter vocabulary.</p><p>The semantics of the value <code>default</code> are fixed to mean that
when performing presentation processing of a <a href="#terms-document-instance">document instance</a> as
-described by <a href="#semantics-region-layout-step-2"><b>11.3.4 Synchronic Flow Processing</b></a>,
+described by <a href="#semantics-region-layout-step-2"><b>11.3.1.4 Synchronic Flow Processing</b></a>,
processing must occur as
if the following properties were specified on the affected
elements of an equivalent intermediate XSL-FO document:</p><ul><li><p><code>suppress-at-line-break="auto"</code></p></li><li><p><code>linefeed-treatment="treat-as-space"</code></p></li><li><p><code>white-space-collapse="true"</code></p></li><li><p><code>white-space-treatment="ignore-if-surrounding-linefeed"</code></p></li></ul><p>Similarly, the semantics of the value <code>preserve</code> are fixed to mean that
@@ -3179,13 +3199,14 @@
<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
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#embedded-content-attribute-format">format</a> = <a href="#embedded-content-value-audio-format"><audio-format></a>
<a href="#embedded-content-attribute-src">src</a> = <a href="#embedded-content-value-audio"><audio></a>
<a href="#embedded-content-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 Style namespace</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>*
@@ -3214,7 +3235,7 @@
<h4><a id="embedded-content-vocabulary-chunk"></a>9.1.2 chunk</h4><p>The <code>chunk</code> element is used to represent a distinct chunk (fragment) of data.</p><p>A <code>chunk</code> element may appear as a child of a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element.</p><a id="elt-syntax-chunk"></a><table class="syntax"><caption>XML Representation – Element Information Item: chunk</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<chunk
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#embedded-content-attribute-encoding">encoding</a> = (base16|base32|base32hex|base64|base64url) : base64
length = <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>
<a href="#content-attribute-id">xml:id</a> = ID
@@ -3277,7 +3298,7 @@
<a href="#embedded-content-vocabulary-data"><code>data</code></a> element in a <a href="#terms-data-defining-context">data defining context</a>.</p><a id="elt-syntax-data"></a><table class="syntax"><caption>XML Representation – Element Information Item: data</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<data
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#embedded-content-attribute-encoding">encoding</a> = (base16|base32|base32hex|base64|base64url) : <em>see prose below</em>
<a href="#embedded-content-attribute-format">format</a> = <a href="#embedded-content-value-data-format"><data-format></a>
length = <a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a>
@@ -3360,7 +3381,7 @@
<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>
<div class="exampleInner"><pre>
<font
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
family = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
<a href="#embedded-content-attribute-format">format</a> = <a href="#embedded-content-value-font-format"><font-format></a>
range = <a href="#embedded-content-value-unicode-range"><unicode-range></a>
@@ -3439,13 +3460,14 @@
<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
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#embedded-content-attribute-format">format</a> = <a href="#embedded-content-value-image-format"><image-format></a>
<a href="#embedded-content-attribute-src">src</a> = <a href="#embedded-content-value-image"><image></a>
<a href="#embedded-content-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 Style namespace</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>*
@@ -3464,7 +3486,13 @@
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 Resources</caption><tbody><tr><td>
+value expression.</p><p>An <code>image</code> element may specify either (both)
+<a href="#style-attribute-width"><code>tts:width</code></a> or (and)
+<a href="#style-attribute-height"><code>tts:height</code></a> style attributes in order to specify the presentation width or height of the image when
+intrinsic width or height information is not available or is intended to be overridden. If (either or both of) these attributes are specified on both an
+<code>image</code> element in an <a href="#terms-image-presentation-context">image presentation context</a> and on the
+<code>image</code> element in an <a href="#terms-image-defining-context">image defining context</a> to which the former refers, then
+these attributes specified on the former take precedence over those specified on the latter.</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>
@@ -3526,7 +3554,7 @@
<a href="#element-vocab-group-data"><code>Font.class</code></a> element groups.</p><a id="elt-syntax-resources"></a><table class="syntax"><caption>XML Representation – Element Information Item: resources</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<resources
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -3549,7 +3577,7 @@
an <a href="#terms-nested-embedded-source">nested embedded source</a>.</p><p>A <code>source</code> element must not have an ancestor <code>source</code> element.</p><a id="elt-syntax-source"></a><table class="syntax"><caption>XML Representation – Element Information Item: source</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<source
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#embedded-content-attribute-format">format</a> = <a href="#embedded-content-value-data-format"><data-format></a>
<a href="#embedded-content-attribute-src">src</a> = <a href="#embedded-content-value-data"><data></a>
<a href="#embedded-content-attribute-type">type</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
@@ -3762,7 +3790,7 @@
the specification defined initial value(s).</p><p>The <code>initial</code> element accepts as its children zero or more <code>metadata</code> elements.</p><a id="elt-syntax-initial"></a><table class="syntax"><caption>XML Representation – Element Information Item: initial</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<initial
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -3789,7 +3817,7 @@
<a href="#semantics-style-resolution-processing-sss"><b>10.4.4.2 Specified Style Set Processing</b></a>.</p><p>The <code>style</code> element accepts as its children zero or more <code>metadata</code> elements.</p><a id="elt-syntax-style"></a><table class="syntax"><caption>XML Representation – Element Information Item: style</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<style
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#style-attribute-style">style</a> = IDREFS
<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>
@@ -3813,7 +3841,7 @@
followed by zero or more <code>style</code> elements.</p><a id="elt-syntax-styling"></a><table class="syntax"><caption>XML Representation – Element Information Item: styling</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<styling
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -3827,11 +3855,12 @@
<h3><a id="styling-attribute-vocabulary"></a>10.2 Styling Attribute Vocabulary</h3><p>This section defines the <a href="#style-attribute-style"><b>10.2.1 style</b></a> attribute used
with certain animation elements, <a href="#terms-content-element">content elements</a>, certain layout elements, and style definition elements.</p><p>In addition, this section specifies the following attributes in the TT Style Namespace
for use with style definition elements, certain layout elements, and <a href="#terms-content-element">content elements</a>
-that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>10.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-backgroundImage"><b>10.2.3 tts:backgroundImage</b></a></p></li><li><p><a href="#style-attribute-backgroundPosition"><b>10.2.4 tts:backgroundPosition</b></a></p></li><li><p><a href="#style-attribute-backgroundRepeat"><b>10.2.5 tts:backgroundRepeat</b></a></p></li><li><p><a href="#style-attribute-border"><b>10.2.6 tts:border</b></a></p></li><li><p><a href="#style-attribute-color"><b>10.2.7 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>10.2.8 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>10.2.9 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>10.2.10 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>10.2.11 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>10.2.12 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.13 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.14 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.15 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.16 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.17 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.18 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.19 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.20 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.21 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.22 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.23 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.24 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.25 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.26 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.27 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.28 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.29 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.30 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.31 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.32 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.33 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.34 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.35 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.36 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.37 tts:zIndex</b></a></p></li></ul><table border="1" class="ednote" summary="Editorial note: Additional Border Styling Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Border Styling Attributes</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:borderColor</code>, <code>tts:borderStyle</code>, and <code>tts:borderWidth</code>
+that support inline style specifications:</p><ul><li><p><a href="#style-attribute-backgroundColor"><b>10.2.2 tts:backgroundColor</b></a></p></li><li><p><a href="#style-attribute-backgroundImage"><b>10.2.3 tts:backgroundImage</b></a></p></li><li><p><a href="#style-attribute-backgroundPosition"><b>10.2.4 tts:backgroundPosition</b></a></p></li><li><p><a href="#style-attribute-backgroundRepeat"><b>10.2.5 tts:backgroundRepeat</b></a></p></li><li><p><a href="#style-attribute-border"><b>10.2.6 tts:border</b></a></p></li><li><p><a href="#style-attribute-color"><b>10.2.7 tts:color</b></a></p></li><li><p><a href="#style-attribute-direction"><b>10.2.8 tts:direction</b></a></p></li><li><p><a href="#style-attribute-display"><b>10.2.9 tts:display</b></a></p></li><li><p><a href="#style-attribute-displayAlign"><b>10.2.10 tts:displayAlign</b></a></p></li><li><p><a href="#style-attribute-extent"><b>10.2.11 tts:extent</b></a></p></li><li><p><a href="#style-attribute-fontFamily"><b>10.2.12 tts:fontFamily</b></a></p></li><li><p><a href="#style-attribute-fontSelectionStrategy"><b>10.2.13 tts:fontSelectionStrategy</b></a></p></li><li><p><a href="#style-attribute-fontSize"><b>10.2.14 tts:fontSize</b></a></p></li><li><p><a href="#style-attribute-fontStyle"><b>10.2.15 tts:fontStyle</b></a></p></li><li><p><a href="#style-attribute-fontVariantPosition"><b>10.2.16 tts:fontVariantPosition</b></a></p></li><li><p><a href="#style-attribute-fontWeight"><b>10.2.17 tts:fontWeight</b></a></p></li><li><p><a href="#style-attribute-height"><b>10.2.18 tts:height</b></a></p></li><li><p><a href="#style-attribute-lineHeight"><b>10.2.19 tts:lineHeight</b></a></p></li><li><p><a href="#style-attribute-opacity"><b>10.2.20 tts:opacity</b></a></p></li><li><p><a href="#style-attribute-origin"><b>10.2.21 tts:origin</b></a></p></li><li><p><a href="#style-attribute-overflow"><b>10.2.22 tts:overflow</b></a></p></li><li><p><a href="#style-attribute-padding"><b>10.2.23 tts:padding</b></a></p></li><li><p><a href="#style-attribute-position"><b>10.2.24 tts:position</b></a></p></li><li><p><a href="#style-attribute-ruby"><b>10.2.25 tts:ruby</b></a></p></li><li><p><a href="#style-attribute-rubyAlign"><b>10.2.26 tts:rubyAlign</b></a></p></li><li><p><a href="#style-attribute-rubyOffset"><b>10.2.27 tts:rubyOffset</b></a></p></li><li><p><a href="#style-attribute-rubyPosition"><b>10.2.28 tts:rubyPosition</b></a></p></li><li><p><a href="#style-attribute-showBackground"><b>10.2.29 tts:showBackground</b></a></p></li><li><p><a href="#style-attribute-textAlign"><b>10.2.30 tts:textAlign</b></a></p></li><li><p><a href="#style-attribute-textDecoration"><b>10.2.31 tts:textDecoration</b></a></p></li><li><p><a href="#style-attribute-textOrientation"><b>10.2.32 tts:textOrientation</b></a></p></li><li><p><a href="#style-attribute-textOutline"><b>10.2.33 tts:textOutline</b></a></p></li><li><p><a href="#style-attribute-unicodeBidi"><b>10.2.34 tts:unicodeBidi</b></a></p></li><li><p><a href="#style-attribute-visibility"><b>10.2.35 tts:visibility</b></a></p></li><li><p><a href="#style-attribute-width"><b>10.2.36 tts:width</b></a></p></li><li><p><a href="#style-attribute-wrapOption"><b>10.2.37 tts:wrapOption</b></a></p></li><li><p><a href="#style-attribute-writingMode"><b>10.2.38 tts:writingMode</b></a></p></li><li><p><a href="#style-attribute-zIndex"><b>10.2.39 tts:zIndex</b></a></p></li></ul><table border="1" class="ednote" summary="Editorial note: Additional Border Styling Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Border Styling Attributes</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:borderColor</code>, <code>tts:borderStyle</code>, and <code>tts:borderWidth</code>
in order to provide a means to independently express styling of the four different borders (top, right, bottom, left). As currently specified, i.e., with only the
<code>tts:border</code> attribute, one can only express the four borders using the same color, style, and width.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Clip, Origin, Size"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Clip, Origin, Size</b></td><td align="right" valign="top">2014-11-27</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Consider adding support for <code>tts:backgroundClip</code>,
<code>tts:backgroundOrigin</code>, and
-<code>tts:backgroundSize</code>.</td></tr></table><p>Unless explicitly permitted by an element type definition, an attribute in the TT Style Namespace should not be specified on an element
+<code>tts:backgroundSize</code>.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Additional Width/Height Related Attributes"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Additional Width/Height Related Attributes</b></td><td align="right" valign="top">2014-11-30</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Given the addition of <code>tts:width</code> and <code>tts:height</code>, consider also adding
+<code>tts:minWidth</code>, <code>tts:maxWidth</code>, <code>tts:minHeight</code>, and <code>tts:minHeight</code>.</td></tr></table><p>Unless explicitly permitted by an element type definition, an attribute in the TT Style Namespace should not be specified on an element
unless it either applies to that element or denotes an inheritable style property. If it does not apply to that element
and does not denote an inheritable style property, then it must be ignored for the purpose of non-validation processing.
In the case of validation processing, such usage should be reported as a warning, or, if strict validation is performed,
@@ -3959,7 +3988,7 @@
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>,
<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><em>see prose</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</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>A percentage value component for a horizontal position offset is relative to the width of the
positioning area minus the width of the background image.
@@ -4236,16 +4265,16 @@
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><a id="style-property-details-extent"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>auto</code> |
-<a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a>
+<a href="#style-value-measure"><measure></a> <a href="#style-value-measure"><measure></a>
</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#document-structure-vocabulary-tt"><code>tt</code></a>,
<a href="#content-vocabulary-div"><code>div</code></a>,
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-length"><length></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-measure"><measure></a>
specifications, then they must be interpreted as <em>width</em>
and <em>height</em>, where the first specification is the
-<em>width</em>, and the second specification is the <em>height</em>.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express extent must be non-negative.</p><p>If the value of this attribute is <code>auto</code>, then the computed value
+<em>width</em>, and the second specification is the <em>height</em>.</p><p>The <a href="#style-value-measure"><measure></a> value(s) used to express extent must be non-negative.</p><p>If the value of this attribute is <code>auto</code>, then the computed value
of the style property must be considered to be the same as the extent of the <a href="#terms-root-container-region">root container region</a>.</p><p>The extent of the <a href="#terms-root-container-region">root container region</a> is determined either by a
<code>tts:extent</code> specified on the <code>tt</code> element, if
present, or as described by <a href="#document-structure-vocabulary-tt"><b>8.1.1 tt</b></a> if not present.
@@ -4476,7 +4505,27 @@
</td></tr></tbody></table><p></p><a id="style-attribute-fontWeight-example-1-images"></a><table class="example-images"><caption>Example Rendition – Font Weight</caption><tbody><tr><td><img src="images/fontWeight.png" alt="TTML fontWeight style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.9.9.</p></div></div><div class="div3">
-<h4><a id="style-attribute-lineHeight"></a>10.2.18 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-height"></a>10.2.18 tts:height</h4><p>The <code>tts:height</code> attribute is used to specify the
+<em>height</em> of an area generated by content flowed into a region.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <em>height</em> is interpreted in a writing mode relative manner
+such that <em>height</em> always corresponds to a measure in the block
+progression direction. Therefore, in horizontal writing modes, <em>height</em> expresses a vertical measure,
+while, in vertical writing mode, <em>height</em> expresses a horizontal measure,
+where horizontal and vertical are always interpreted in an absolute sense.</p></div><p>If a <code>tts:height</code> attribute is specified on a <a href="#content-vocabulary-span"><code>span</code></a> element,
+then that <a href="#content-vocabulary-span"><code>span</code></a> element must be processed using
+<a href="#terms-inline-block-display">inline block display</a> semantics for the purpose of presentation processing.</p><p>This attribute may be specified by any
+element type
+that permits use of attributes in the TT Style Namespace; however, this attribute applies
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-height"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+<a href="#style-value-measure"><measure></a>
+</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<a href="#content-vocabulary-div"><code>div</code></a>,
+<a href="#content-vocabulary-p"><code>p</code></a>,
+<a href="#content-vocabulary-span"><code>span</code></a>,
+<a href="#embedded-content-vocabulary-image"><code>image</code></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If a <a href="#style-value-measure"><measure></a> is expressed as a <a href="#style-value-length"><length></a> value, then it must be non-negative.</p><p>The <code>tts:height</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Height Percentage"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Height Percentage</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify resolution of percentage value.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Height Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Height Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:height.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
+represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
+§ 7.15.14, and <a href="#css3-box">[CSS Box Model]</a>, § 9</p></div></div><div class="div3">
+<h4><a id="style-attribute-lineHeight"></a>10.2.19 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
defines the inter-baseline separation between line areas generated by content flowed into a region.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -4538,7 +4587,7 @@
allocation rectangle of a line be consistent with the <span class="strong">per-inline-height-rectangle</span>
as defined by <a href="#xsl11">[XSL 1.1]</a>, § 4.5, i.e., that a CSS-style line box stacking strategy be used.
</p></div></div><div class="div3">
-<h4><a id="style-attribute-opacity"></a>10.2.19 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-opacity"></a>10.2.20 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
defines the opacity (or conversely, the transparency)
of marks associated with a region or an area generated by content flowed into a region.</p><p>When presented onto a visual medium, the opacity of the region is applied uniformly and on a linear scale
to all marks produced by content targeted to the
@@ -4587,7 +4636,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#css3-color">[CSS3 Color]</a>,
§ 3.2.</p></div></div><div class="div3">
-<h4><a id="style-attribute-origin"></a>10.2.20 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
+<h4><a id="style-attribute-origin"></a>10.2.21 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
<em>x</em> and <em>y</em> coordinates of the origin of a
region area with respect to the origin of the <a href="#terms-root-container-region">root container region</a>.</p><p>If both <code>tts:origin</code> and <a href="#style-attribute-position"><code>tts:position</code></a> attributes are
specified on an element, then the <code>tts:origin</code> attribute must be ignored for the purpose of presentation processing.</p><p>This attribute may be specified by any
@@ -4627,7 +4676,7 @@
</p>
</pre></div>
</td></tr></tbody></table><p></p><a id="style-attribute-origin-example-1-images"></a><table class="example-images"><caption>Example Rendition – Origin</caption><tbody><tr><td><img src="images/origin.png" alt="TTML origin style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-attribute-overflow"></a>10.2.21 tts:overflow</h4><p>The <code>tts:overflow</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-overflow"></a>10.2.22 tts:overflow</h4><p>The <code>tts:overflow</code> attribute is used to specify a style property that
defines whether a region area is clipped or not if the descendant areas of the region overflow
its extent.</p><p>This attribute may be specified by any
element type
@@ -4687,7 +4736,7 @@
progression direction as opposed to the inline progression direction.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.21.2.</p></div></div><div class="div3">
-<h4><a id="style-attribute-padding"></a>10.2.22 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
+<h4><a id="style-attribute-padding"></a>10.2.23 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
space on one or more sides of a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -4739,7 +4788,7 @@
§ 7.31.15, except that individual shorthand values map to writing
mode relative padding values as defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.8.31, 7.8.32, 7.8.33, and 7.8.34.</p></div></div><div class="div3">
-<h4><a id="style-attribute-position"></a>10.2.23 tts:position</h4><p>The <code>tts:position</code> attribute is used as an alternative way to specify the position
+<h4><a id="style-attribute-position"></a>10.2.24 tts:position</h4><p>The <code>tts:position</code> attribute is used as an alternative way to specify the position
of a region area with respect the <a href="#terms-root-container-region">root container region</a>.</p><p>If both <code>tts:position</code> and <a href="#style-attribute-origin"><code>tts:origin</code></a> attributes are
specified on an element, then the <code>tts:origin</code> attribute must be ignored for the purpose of presentation processing.</p><p>This attribute may be specified by any element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -4750,7 +4799,7 @@
<a href="#content-vocabulary-div"><code>div</code></a>,
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td><em>see prose</em></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>A percentage value component for a horizontal position offset is relative to the width of the
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>A percentage value component for a horizontal position offset is relative to the width of the
positioning area minus the width of the associated region.
A percentage value component for a vertical position offset is relative to the height of the
positioning area minus the height of the associated region.</p><p>If specified on a <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element, then, if a
@@ -4786,7 +4835,7 @@
</pre></div>
</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Border Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Border Example Image</b></td><td align="right" valign="top">2011-11-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of position example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
the <code>background-position</code> property defined by <a href="#css3-bb">[CSS Backgrounds and Borders]</a>, § 3.6.</p></div></div><div class="div3">
-<h4><a id="style-attribute-ruby"></a>10.2.24 tts:ruby</h4><p>The <code>tts:ruby</code> attribute is used to specify the application of ruby
+<h4><a id="style-attribute-ruby"></a>10.2.25 tts:ruby</h4><p>The <code>tts:ruby</code> attribute is used to specify the application of ruby
styling.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-ruby"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>none</code> |
@@ -4933,7 +4982,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-ruby-example-2-images"></a><table class="example-images"><caption>Example Rendition – Complex Ruby</caption><tbody><tr><td><img src="images/ruby_2.png" alt="TTML ruby style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#ruby">[Ruby]</a> and <a href="#cssruby">[CSS Ruby]</a>. See also
<a href="#jlreq">[JLREQ]</a>, §3.3, for further information.</p></div></div><div class="div3">
-<h4><a id="style-attribute-rubyAlign"></a>10.2.25 tts:rubyAlign</h4><p>The <code>tts:rubyAlign</code> attribute is used to specify the position of ruby text within the inline area generated by the ruby text container annotation.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
+<h4><a id="style-attribute-rubyAlign"></a>10.2.26 tts:rubyAlign</h4><p>The <code>tts:rubyAlign</code> attribute is used to specify the position of ruby text within the inline area generated by the ruby text container annotation.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyAlign"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>start</code> |
<code>center</code> |
@@ -4952,7 +5001,7 @@
then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>spaceAround</code>.</p><table border="1" class="ednote" summary="Editorial note: Ruby Align Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Ruby Align Example</b></td><td align="right" valign="top">2014-09-20</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add example source and rendering of tts:rubyAlign.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#cssruby">[CSS Ruby]</a>, §4.3, and the examples and example
renderings shown there apply.</p></div></div><div class="div3">
-<h4><a id="style-attribute-rubyOffset"></a>10.2.26 tts:rubyOffset</h4><p>The <code>tts:rubyOffset</code> attribute is used to specify the offset (distance) of ruby text with respect to its associated ruby base
+<h4><a id="style-attribute-rubyOffset"></a>10.2.27 tts:rubyOffset</h4><p>The <code>tts:rubyOffset</code> attribute is used to specify the offset (distance) of ruby text with respect to its associated ruby base
in the block progression dimension.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyOffset"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-length"><length></a>
@@ -4962,7 +5011,7 @@
generated by a ruby text container (explicit or implied) and padding edge <em>E<sub>2</sub></em> of the inline area generated by a ruby base container (explicit or implied), where
<em>E<sub>1</sub></em> and <em>E<sub>2</sub></em> are perpendicular to the block progression direction and are (or would be) adjacent in the absence of
such an offset.</p><p>Negative length expressions are permitted.</p><table border="1" class="ednote" summary="Editorial note: Ruby Offset Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Ruby Offset Example</b></td><td align="right" valign="top">2014-10-02</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add example source and rendering of tts:rubyOffset.</td></tr></table></div><div class="div3">
-<h4><a id="style-attribute-rubyPosition"></a>10.2.27 tts:rubyPosition</h4><p>The <code>tts:rubyPosition</code> attribute is used to specify the position of ruby text in the block progression dimension
+<h4><a id="style-attribute-rubyPosition"></a>10.2.28 tts:rubyPosition</h4><p>The <code>tts:rubyPosition</code> attribute is used to specify the position of ruby text in the block progression dimension
with respect to its associated ruby base.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyPosition"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
<code>before</code> |
@@ -4979,7 +5028,7 @@
then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>before</code>.</p><a id="rubyPosition-semantics-mapping-table"></a><table class="common"><caption>Table 8-2 – Ruby Position Semantics Mapping by Writing Mode</caption><col width="20%" span="1"><col width="20%" span="1"><col width="20%" span="1"><col width="20%" span="1"><col width="20%" span="1"><col span="1"><tbody><tr><th>tts:rubyPosition</th><th><code>lrtb</code></th><th><code>rltb</code></th><th><code>tbrl</code></th><th><code>tblr</code></th></tr><tr><td><code>before</code></td><td><code>over</code></td><td><code>over</code></td><td><code>right</code></td><td><code>left</code></td></tr><tr><td><code>after</code></td><td><code>under</code></td><td><code>under</code></td><td><code>left</code></td><td><code>right</code></td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Ruby Position Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Ruby Position Example</b></td><td align="right" valign="top">2014-09-20</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add example source and rendering of tts:rubyPosition.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#cssruby">[CSS Ruby]</a>, §4.1, and the examples and example
renderings shown there apply modulo the mappings defined above.</p></div></div><div class="div3">
-<h4><a id="style-attribute-showBackground"></a>10.2.28 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
+<h4><a id="style-attribute-showBackground"></a>10.2.29 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
constraints on when the background color of a region is intended to be
presented.</p><p>This attribute may be specified by any
element type
@@ -5020,7 +5069,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#smil3">[SMIL 3.0]</a>,
§ 7.4.2.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textAlign"></a>10.2.29 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textAlign"></a>10.2.30 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
defines how inline areas are aligned within a containing block area in the inline progression
direction.</p><p>This attribute may be specified by any
element type
@@ -5032,8 +5081,16 @@
<code>start</code> |
<code>end</code>
</td></tr><tr><td><em>Initial:</em></td><td><code>start</code></td></tr><tr><td><em>Applies to:</em></td><td>
-<a href="#content-vocabulary-p"><code>p</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</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>If a computed value of the property associated with this attribute is not supported,
+<a href="#content-vocabulary-p"><code>p</code></a>,
+<a href="#content-vocabulary-span"><code>span</code></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>see prose</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>The <code>tts:textAlign</code> attribute is inheritable only on a <a href="#content-vocabulary-p"><code>p</code></a> element. If not
+specified on a <a href="#content-vocabulary-span"><code>span</code></a> element, then the <code>tts:textAlign</code> style property does not apply to that
+element, rather, normal inline composition and alignment apply.</p><p>If a <code>tts:textAlign</code> attribute is specified on a <a href="#content-vocabulary-span"><code>span</code></a> element,
+then that <a href="#content-vocabulary-span"><code>span</code></a> element must be processed using
+<a href="#terms-inline-block-display">inline block display</a> semantics for the purpose of presentation processing.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>tts:textAlign</code> attribute may be used on a <a href="#content-vocabulary-span"><code>span</code></a> element in order
+to force composition using <a href="#terms-inline-block-display">inline block display</a> semantics and to apply a different alignment
+to the resulting nested block area. For example, a paragraph may be composed using center text alignment, while the text content within the paragraph, if
+wrapped in a span, may be composed using left text alignment.</p></div><p>If a computed value of the property associated with this attribute is not supported,
then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>start</code>.</p><p>The <code>tts:textAlign</code> style is illustrated by the following example.</p><a id="style-attribute-textAlign-example-1"></a><table class="example"><caption>Example Fragment – Text Align</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -5060,10 +5117,10 @@
The frumious Bandersnatch!
</p>
</pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-textAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="TTML textAlign style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
+</td></tr></tbody></table><p></p><a id="style-attribute-textAlign-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Align</caption><tbody><tr><td><img src="images/textAlign.png" alt="TTML textAlign style property"></td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Text Align on Span Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Align on Span Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of use of tts:textAlign on a span element.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.16.9.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textDecoration"></a>10.2.30 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textDecoration"></a>10.2.31 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
defines a text decoration effect to apply to glyph areas or other inline
areas that are generated by content flowed into a region.</p><p>This attribute may be specified by any
element type
@@ -5112,7 +5169,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-textDecoration-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Decoration</caption><tbody><tr><td><img src="images/textDecoration.png" alt="TTML textDecoration style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.17.4.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textOrientation"></a>10.2.31 tts:textOrientation</h4><p>The <code>tts:textOrientation</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textOrientation"></a>10.2.32 tts:textOrientation</h4><p>The <code>tts:textOrientation</code> attribute is used to specify a style property that
defines a text orientation to apply to glyphs that are selected for glyph areas generated
by content flowed into a region to which a vertical writing mode applies.</p><p>This attribute may be specified by any
element type
@@ -5144,10 +5201,10 @@
a <code>tts:direction</code> of <code>ltr</code> and <code>tts:unicodeOverride</code> of
<code>override</code> were applied.</p><p>If a vertical writing mode does not apply, then this style property has no effect.</p><p>If a computed value of the property associated with this attribute is not supported,
then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>mixed</code>.</p><p>The <code>tts:textOrientation</code> style is illustrated by the following
-example.</p><table border="1" class="ednote" summary="Editorial note: Text Orientation Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Orientation Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of text orientation.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
+example.</p><table border="1" class="ednote" summary="Editorial note: Text Orientation Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Orientation Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textOrientation.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#css3-wm">[CSS Writing Modes]</a>,
§ 5.1.</p></div></div><div class="div3">
-<h4><a id="style-attribute-textOutline"></a>10.2.32 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-textOutline"></a>10.2.33 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
defines a text outline effect to apply to glyphs that are selected for glyph areas generated
by content flowed into a region.</p><p>This attribute may be specified by any
element type
@@ -5196,7 +5253,7 @@
</p>
</pre></div>
</td></tr></tbody></table><p></p><a id="style-attribute-textOutline-example-1-images"></a><table class="example-images"><caption>Example Rendition – Text Outline</caption><tbody><tr><td><img src="images/textOutline.png" alt="textOutline style property"></td></tr></tbody></table></div><div class="div3">
-<h4><a id="style-attribute-unicodeBidi"></a>10.2.33 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-unicodeBidi"></a>10.2.34 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
defines a directional embedding or override according to
the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
element type
@@ -5235,7 +5292,7 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.29.6.</p></div></div><div class="div3">
-<h4><a id="style-attribute-visibility"></a>10.2.34 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-visibility"></a>10.2.35 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
defines whether generated areas are visible or not when rendered on a visual
presentation medium.</p><p>This attribute may be specified by any
element type
@@ -5290,7 +5347,27 @@
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.30.17.</p></div></div><div class="div3">
-<h4><a id="style-attribute-wrapOption"></a>10.2.35 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-width"></a>10.2.36 tts:width</h4><p>The <code>tts:width</code> attribute is used to specify the
+<em>width</em> of an area generated by content flowed into a region.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <em>width</em> is interpreted in a writing mode relative manner
+such that <em>width</em> always corresponds to a measure in the inline
+progression direction. Therefore, in horizontal writing modes, <em>width</em> expresses a horizontal measure,
+while, in vertical writing mode, <em>width</em> expresses a vertical measure,
+where horizontal and vertical are always interpreted in an absolute sense.</p></div><p>If a <code>tts:width</code> attribute is specified on a <a href="#content-vocabulary-span"><code>span</code></a> element,
+then that <a href="#content-vocabulary-span"><code>span</code></a> element must be processed using
+<a href="#terms-inline-block-display">inline block display</a> semantics for the purpose of presentation processing.</p><p>This attribute may be specified by any
+element type
+that permits use of attributes in the TT Style Namespace; however, this attribute applies
+as a style property only to those element types indicated in the following table.</p><a id="style-property-details-width"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
+<a href="#style-value-measure"><measure></a>
+</td></tr><tr><td><em>Initial:</em></td><td><code>auto</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<a href="#content-vocabulary-div"><code>div</code></a>,
+<a href="#content-vocabulary-p"><code>p</code></a>,
+<a href="#content-vocabulary-span"><code>span</code></a>,
+<a href="#embedded-content-vocabulary-image"><code>image</code></a>
+</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>see prose</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If a <a href="#style-value-measure"><measure></a> is expressed as a <a href="#style-value-length"><length></a> value, then it must be non-negative.</p><p>The <code>tts:width</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Width Percentage"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Width Percentage</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Specify resolution of percentage value.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Width Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Width Example</b></td><td align="right" valign="top">2014-11-29</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:width.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
+represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
+§ 7.15.14, and <a href="#css3-box">[CSS Box Model]</a>, § 9</p></div></div><div class="div3">
+<h4><a id="style-attribute-wrapOption"></a>10.2.37 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
defines whether or not automatic line wrapping (breaking) applies within the context of
the affected element.</p><p>This attribute may be specified by any
element type
@@ -5324,7 +5401,7 @@
</td></tr></tbody></table><p></p><a id="style-attribute-wrapOption-example-1-images"></a><table class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="TTML wrapOption style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.16.13.</p></div></div><div class="div3">
-<h4><a id="style-attribute-writingMode"></a>10.2.36 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-writingMode"></a>10.2.38 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
defines the block and inline progression directions to be used for the purpose of
stacking block and inline areas within a region area.</p><p>This attribute may be specified by any
element type
@@ -5375,7 +5452,7 @@
the Latin script.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.29.7.</p></div></div><div class="div3">
-<h4><a id="style-attribute-zIndex"></a>10.2.37 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
+<h4><a id="style-attribute-zIndex"></a>10.2.39 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
defines the front-to-back ordering of region areas in the case that they overlap.</p><p>This attribute may be specified by any
element type
that permits use of attributes in the TT Style Namespace; however, this attribute applies
@@ -5450,7 +5527,7 @@
</td></tr></tbody></table><p></p><p></p><a id="style-attribute-zIndex-example-1-images"></a><table class="example-images"><caption>Example Rendition – Z Index</caption><tbody><tr><td><img src="images/zIndex.png" alt="TTML zIndex style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.30.18.</p></div></div></div><div class="div2">
-<h3><a id="styling-style-value-expressions"></a>10.3 Style Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>10.3.1 <alpha></b></a></p></li><li><p><a href="#style-value-borderColor"><b>10.3.2 <borderColor></b></a></p></li><li><p><a href="#style-value-borderStyle"><b>10.3.3 <borderStyle></b></a></p></li><li><p><a href="#style-value-borderWidth"><b>10.3.4 <borderWidth></b></a></p></li><li><p><a href="#style-value-color"><b>10.3.5 <color></b></a></p></li><li><p><a href="#style-value-digit"><b>10.3.6 <digit></b></a></p></li><li><p><a href="#style-value-familyName"><b>10.3.7 <familyName></b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>10.3.8 <genericFamilyName></b></a></p></li><li><p><a href="#style-value-hexDigit"><b>10.3.9 <hexDigit></b></a></p></li><li><p><a href="#style-value-integer"><b>10.3.10 <integer></b></a></p></li><li><p><a href="#style-value-length"><b>10.3.11 <length></b></a></p></li><li><p><a href="#style-value-namedColor"><b>10.3.12 <namedColor></b></a></p></li><li><p><a href="#style-value-position"><b>10.3.13 <position></b></a></p></li></ul><p>In the syntax representations defined in this section, no
+<h3><a id="styling-style-value-expressions"></a>10.3 Styling Value Expressions</h3><p>Style property values include the use of the following expressions:</p><ul><li><p><a href="#style-value-alpha"><b>10.3.1 <alpha></b></a></p></li><li><p><a href="#style-value-borderColor"><b>10.3.2 <borderColor></b></a></p></li><li><p><a href="#style-value-borderStyle"><b>10.3.3 <borderStyle></b></a></p></li><li><p><a href="#style-value-borderWidth"><b>10.3.4 <borderWidth></b></a></p></li><li><p><a href="#style-value-color"><b>10.3.5 <color></b></a></p></li><li><p><a href="#style-value-digit"><b>10.3.6 <digit></b></a></p></li><li><p><a href="#style-value-familyName"><b>10.3.7 <familyName></b></a></p></li><li><p><a href="#style-value-genericFamilyName"><b>10.3.8 <genericFamilyName></b></a></p></li><li><p><a href="#style-value-hexDigit"><b>10.3.9 <hexDigit></b></a></p></li><li><p><a href="#style-value-integer"><b>10.3.10 <integer></b></a></p></li><li><p><a href="#style-value-length"><b>10.3.11 <length></b></a></p></li><li><p><a href="#style-value-measure"><b>10.3.12 <measure></b></a></p></li><li><p><a href="#style-value-namedColor"><b>10.3.13 <namedColor></b></a></p></li><li><p><a href="#style-value-position"><b>10.3.14 <position></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="style-value-alpha"></a>10.3.1 <alpha></h4><p>An <alpha> expression is used to express an opacity value,
@@ -5706,7 +5783,31 @@
the minimum and maxium of <code>vw</code> and <code>vh</code>, respectively. For example,
the length <code>25vmin</code> is interpreted as the minimum of 25% of the width and
25% of the height of the <a href="#terms-root-container-region">root container region</a>.</p></div><div class="div3">
-<h4><a id="style-value-namedColor"></a>10.3.12 <namedColor></h4><p>A <namedColor> is used to express an RGBA color with a convenient name, and where the applicable color space is
+<h4><a id="style-value-measure"></a>10.3.12 <measure></h4><p>A <measure> value expression is used to express a distance used to measure an allocation
+dimension in either the inline progression direction or the block progression direction, where
+the direction that applies is determined by the context of use.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The terms <em>width</em> and <em>height</em> are interpreted in a writing mode relative manner
+such that <em>width</em> always corresponds to a measure in the inline
+progression direction and <em>height</em> always corresponds to a measure in the block progression direction.
+Therefore, in horizontal writing modes, <em>width</em> expresses a horizontal measure
+and <em>height</em> expresses a vertical measure, while, in vertical writing mode, <em>width</em> expresses a vertical measure
+and <em>height</em> expresses a horizontal measure, where horizontal and vertical are always interpreted in an absolute sense.</p></div><a id="measure-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <measure></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<measure>
+ : auto
+ | available
+ | fitContent
+ | maxContent
+ | minContent
+ | <a href="#style-value-length"><length></a>
+</pre></div>
+</td></tr></tbody></table><p>The semantics of measure values are defined as follows:</p><dl><dt class="label"><code>auto</code></dt><dd><p>As determined by <a href="#semantics-style-automatic-measure-calculation"><b>10.4.5 Automatic Measure Calculation</b></a>.</p></dd><dt class="label"><code>available</code></dt><dd><p>For width in a horizontal writing mode, the numeric value equal to the width of the parent containing block's height less
+the current element's combined border and padding width.</p><p>For height in a horizontal writing mode, the numeric value equal to the height of the parent containing block's height less
+the current element's combined border and padding height.</p></dd><dt class="label"><code>fitContent</code></dt><dd><p>A numeric value equal to the maximum of the values of (1) <code>minContent</code> and (2) the minimum of values of <code>maxContent</code> and <code>available</code>.</p></dd><dt class="label"><code>maxContent</code></dt><dd><p>For width in a horizontal writing mode, the maximum numeric value that encloses all of the element's content such that lines are broken only at
+hard, i.e., mandatory, break points, even if that means overflowing the parent's width.</p><p>For height in a horizontal writing mode, the maximum numeric value that encloses all of the element's content such that lines are broken at
+all possible line break positions, i.e., both hard (mandatory) and soft (optional) break points.</p><p>For vertical writing mode, the sense of width and height is reversed.</p></dd><dt class="label"><code>minContent</code></dt><dd><p>For width in a horizontal writing mode, the minimum numeric value that encloses all of the element's content such that lines are broken at
+all possible line break positions, i.e., both hard (mandatory) and soft (optional) break points.</p><p>For height in a horizontal writing mode, the minimum numeric value that encloses all of the element's content such that lines are broken only at
+hard, i.e., mandatory, break points, even if that means overflowing the parent's width.</p><p>For vertical writing mode, the sense of width and height is reversed.</p></dd><dt class="label"><code><a href="#style-value-length"><length></a></code></dt><dd><p>A non-negative numeric value expressed as a scalar or percentage.</p></dd></dl></div><div class="div3">
+<h4><a id="style-value-namedColor"></a>10.3.13 <namedColor></h4><p>A <namedColor> is used to express an RGBA color with a convenient name, and where the applicable color space is
defined by <a href="#srgb">[SRGB]</a>.</p><p>For the purpose of parsing, a distinction must not be made between lower and upper case.</p><a id="namedColor-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <namedColor></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<namedColor>
@@ -5732,7 +5833,7 @@
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>Except for <code>transparent</code>, the set of named colors specified above constitutes a proper
subset of the set of named colors specified by <a href="#svg11">[SVG 1.1]</a>, § 4.2.</p></div></div><div class="div3">
-<h4><a id="style-value-position"></a>10.3.13 <position></h4><p>A <position> expression is used to indirectly determine the origin of an area or an image with respect to a reference area.</p><a id="position-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <position></caption><tbody><tr><td>
+<h4><a id="style-value-position"></a>10.3.14 <position></h4><p>A <position> expression is used to indirectly determine the origin of an area or an image with respect to a reference area.</p><a id="position-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – <position></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<position>
: offset-position-h // single component value
@@ -5787,7 +5888,7 @@
expression. Similarly, the expression <code>(100% - <a href="#style-value-length"><length-v></a>)</code>
is to be interpreted as the difference between 100% and the percentage equivalent of the <a href="#style-value-length"><length-v></a> expression.
In both cases, the resulting difference may be a negative percentage.</p></div></div><div class="div2">
-<h3><a id="semantics-style-resolution"></a>10.4 Style Resolution</h3><p>This section defines the semantics of style resolution in terms of
+<h3><a id="semantics-styling"></a>10.4 Styling Semantics</h3><p>This section defines the semantics of style resolution in terms of
a standard processing model as follows:</p><ul><li><p><a href="#semantics-style-association"><b>10.4.1 Style Association</b></a></p></li><li><p><a href="#semantics-style-inheritance"><b>10.4.2 Style Inheritance</b></a></p></li><li><p><a href="#semantics-style-resolution-value-categories"><b>10.4.3 Style Resolution Value Categories</b></a></p></li><li><p><a href="#semantics-style-resolution-processing"><b>10.4.4 Style Resolution Processing</b></a></p></li></ul><p>Any implementation of this model is permitted provided that the
externally observable results are consistent with the results produced
by this model.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of style resolution employed here are based upon
@@ -5869,7 +5970,7 @@
using:
</p><ul><li><p><a href="#semantics-style-inheritance-content">content style inheritance</a></p></li><li><p><a href="#semantics-style-inheritance-region">region style inheritance</a></p></li><li><p><a href="#semantics-style-inheritance-root">root style inheritance</a></p></li></ul><p>For the purpose of determining inherited styles, the element hierarchy of
an intermediate synchronic document form of a <a href="#terms-document-instance">document instance</a> must be used, where
-such intermediate forms are defined by <a href="#semantics-region-layout-step-1"><b>11.3.3 Intermediate Synchronic Document Construction</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate synchronic document form is utilized rather than
+such intermediate forms are defined by <a href="#semantics-region-layout-step-1"><b>11.3.1.3 Intermediate Synchronic Document Construction</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate synchronic document form is utilized rather than
the original form in order to facilitate region inheritance
processing.</p></div><div class="div4">
<h5><a id="semantics-style-inheritance-content"></a>10.4.2.1 Content Style Inheritance</h5><p>Style properties are inherited from ancestor <a href="#terms-content-element">content elements</a>
@@ -5975,7 +6076,7 @@
<h4><a id="semantics-style-resolution-processing"></a>10.4.4 Style Resolution Processing</h4><p>The process of style resolution is defined herein as the procedure
(and results thereof) for resolving (determining) the computed values
of all style properties that apply to content and layout elements:</p><ul><li><p><a href="#semantics-style-resolution-processing-definitions"><b>10.4.4.1 Conceptual Definitions</b></a></p></li><li><p><a href="#semantics-style-resolution-processing-sss"><b>10.4.4.2 Specified Style Set Processing</b></a></p></li><li><p><a href="#semantics-style-resolution-processing-css"><b>10.4.4.3 Computed Style Set Processing</b></a></p></li><li><p><a href="#semantics-style-resolution-process-overall"><b>10.4.4.4 Style Resolution Process</b></a></p></li></ul><p>The process described here forms an integral sub-process of
-<a href="#semantics-region-layout"><b>11.3 Region Layout and Presentation</b></a>.</p><div class="div4">
+<a href="#semantics-region-layout"><b>11.3.1 Region Layout and Presentation</b></a>.</p><div class="div4">
<h5><a id="semantics-style-resolution-processing-definitions"></a>10.4.4.1 Conceptual Definitions</h5><p>For the purpose of interpreting the style resolution processing
model specified below, the following conceptual definitions apply:</p><dl><dt class="label">[style property]</dt><dd><p>a style property, <em>P</em>, is considered to consist of a
tuple <code>[name, value]</code>, where the name of the
@@ -6129,7 +6230,9 @@
do not perform the subsequent step below on <em>E</em>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><code>tt</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#content-vocabulary-br"><code>br</code></a></p></li><li><p><a href="#animation-vocabulary-animate"><code>animate</code></a></p></li><li><p><a href="#animation-vocabulary-set"><code>set</code></a></p></li><li><p><em>anonymous span</em></p></li></ul></li><li><p> <span class="strong">[resolve computed styles]</span>
determine (obtain) the computed style set <em>CSS</em> of
<em>E</em>, namely, <em>CSS(E)</em>, in accordance with
-<a href="#semantics-style-resolution-processing-css"><b>10.4.4.3 Computed Style Set Processing</b></a>.</p></li></ol></div></div></div></div><div class="div1">
+<a href="#semantics-style-resolution-processing-css"><b>10.4.4.3 Computed Style Set Processing</b></a>.</p></li></ol></div></div><div class="div3">
+<h4><a id="semantics-style-automatic-measure-calculation"></a>10.4.5 Automatic Measure Calculation</h4><table border="1" class="ednote" summary="Editorial note: Automatic Measures"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Automatic Measures</b></td><td align="right" valign="top">2014-11-30</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define semantics for resolving the <code>auto</code> value as used with a <a href="#style-value-measure"><measure></a> expression,
+the definition of which should be consistent with <a href="#css3-box">[CSS Box Model]</a>, § 15.</td></tr></table></div></div></div><div class="div1">
<h2><a id="layout"></a>11 Layout</h2><p>This section specifies the <em>layout</em> matter of the core
vocabulary catalog, where
layout is to be understood as a separable layer of information that applies to
@@ -6150,7 +6253,7 @@
zero or more <code>region</code> elements.</p><a id="elt-syntax-layout"></a><table class="syntax"><caption>XML Representation – Element Information Item: layout</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<layout
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -6187,7 +6290,7 @@
<region
<a href="#animation-attribute-animate">animate</a> = IDREFS
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#style-attribute-style">style</a> = IDREFS
@@ -6248,15 +6351,16 @@
adhere to the <code>IDREF</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
§ 3.3.9, and, furthermore, this IDREF must reference a <code>region</code> element
which has a <code>layout</code> element as an ancestor.</p><p>The <code>region</code> attribute may be specified by an instance of the following
-element types:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#content-vocabulary-br"><code>br</code></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#semantics-region-layout"><b>11.3 Region Layout and Presentation</b></a> below for further information on content
+element types:</p><ul><li><p><a href="#document-structure-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#content-vocabulary-br"><code>br</code></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>See <a href="#semantics-region-layout"><b>11.3.1 Region Layout and Presentation</b></a> below for further information on content
flow in a region.</p></div></div></div><div class="div2">
-<h3><a id="semantics-region-layout"></a>11.3 Region Layout and Presentation</h3><p>This section defines the semantics of region layout and
+<h3><a id="semantics-layout"></a>11.3 Layout Semantics</h3><div class="div3">
+<h4><a id="semantics-region-layout"></a>11.3.1 Region Layout and Presentation</h4><p>This section defines the semantics of region layout and
presentation in terms of a standard processing model as
-follows:</p><ul><li><p><a href="#semantics-default-region"><b>11.3.1 Default Region</b></a></p></li><li><p><a href="#semantics-inline-regions"><b>11.3.2 Inline Regions</b></a></p></li><li><p><a href="#semantics-region-layout-step-1"><b>11.3.3 Intermediate Synchronic Document Construction</b></a></p></li><li><p><a href="#semantics-region-layout-step-2"><b>11.3.4 Synchronic Flow Processing</b></a></p></li><li><p><a href="#semantics-region-layout-example"><b>11.3.5 Elaborated Example (Non-Normative)</b></a></p></li></ul><p>Any
+follows:</p><ul><li><p><a href="#semantics-default-region"><b>11.3.1.1 Default Region</b></a></p></li><li><p><a href="#semantics-inline-regions"><b>11.3.1.2 Inline Regions</b></a></p></li><li><p><a href="#semantics-region-layout-step-1"><b>11.3.1.3 Intermediate Synchronic Document Construction</b></a></p></li><li><p><a href="#semantics-region-layout-step-2"><b>11.3.1.4 Synchronic Flow Processing</b></a></p></li><li><p><a href="#semantics-region-layout-example"><b>11.3.1.5 Elaborated Example (Non-Normative)</b></a></p></li></ul><p>Any
implementation is permitted provided that the externally observable
results are consistent with the results produced by this model.
-</p><div class="div3">
-<h4><a id="semantics-default-region"></a>11.3.1 Default Region</h4><p>If a <a href="#terms-document-instance">document instance</a> does not specify an
+</p><div class="div4">
+<h5><a id="semantics-default-region"></a>11.3.1.1 Default Region</h5><p>If a <a href="#terms-document-instance">document instance</a> does not specify an
<a href="#terms-out-of-line-region">out-of-line region</a>,
then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the identity of the default region is considered to be an anonymous <a href="#terms-out-of-line-region">out-of-line region</a>;</p></li><li><p>the extent of the default region is the same as the extent of the <a href="#terms-root-container-region">root container region</a>;</p></li><li><p>the temporal interval of the default region is the same as the interval defined by the <a href="#terms-root-temporal-extent">root temporal extent</a>;</p></li></ul><p>Furthermore, if no
<a href="#terms-out-of-line-region">out-of-line region</a> is specified, then the
@@ -6282,8 +6386,8 @@
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, a default <code>region</code> element and <code>region</code>
attribute are implied. In addition, a <code>layout</code> container element is implied for
-the implied <code>region</code> element.</p></div></div><div class="div3">
-<h4><a id="semantics-inline-regions"></a>11.3.2 Inline Regions</h4><p>An <a href="#terms-inline-region">inline region</a> is a syntactic mechanism for specifying a
+the implied <code>region</code> element.</p></div></div><div class="div4">
+<h5><a id="semantics-inline-regions"></a>11.3.1.2 Inline Regions</h5><p>An <a href="#terms-inline-region">inline region</a> is a syntactic mechanism for specifying a
<a href="#terms-region">region</a> in a way that minimizes the syntactic distance between a region
specification and the content that references that region. Semantically, each
<a href="#terms-inline-region">inline region</a> is equivalent to specifying a unique
@@ -6407,8 +6511,8 @@
<body/>
</tt>
</pre></div>
-</td></tr></tbody></table></div><div class="div3">
-<h4><a id="semantics-region-layout-step-1"></a>11.3.3 Intermediate Synchronic Document Construction</h4><table border="1" class="ednote" summary="Editorial note: Use Formalized ISD"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Use Formalized ISD</b></td><td align="right" valign="top">2014-09-22</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Revise in order to take into account new formalization of ISD structure and semantics (Appendix C).</td></tr></table><p>For the purposes of performing presentation processing, the active time
+</td></tr></tbody></table></div><div class="div4">
+<h5><a id="semantics-region-layout-step-1"></a>11.3.1.3 Intermediate Synchronic Document Construction</h5><table border="1" class="ednote" summary="Editorial note: Use Formalized ISD"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Use Formalized ISD</b></td><td align="right" valign="top">2014-09-22</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Revise in order to take into account new formalization of ISD structure and semantics (Appendix C).</td></tr></table><p>For the purposes of performing presentation processing, the active time
duration of a <a href="#terms-document-instance">document instance</a> is divided into a sequence of time coordinates where at
each time coordinate, some element becomes temporally active or inactive,
then, at each such time coordinate, a <a href="#terms-document-instance">document instance</a> is mapped from its original, source
@@ -6452,8 +6556,8 @@
<em>DOC<sub><span>inter<sub>N−1</sub></span></sub></em>,
then it is preferred that the implementation make the transition between
presenting the two instances as smooth as possible, e.g., as described
-by <a href="#cea608e">[CEA-608-E]</a>, § C.3, and <a href="#ccreq">[CC-DECODER-REQ]</a>.</p></div></div><div class="div3">
-<h4><a id="semantics-region-layout-step-2"></a>11.3.4 Synchronic Flow Processing</h4><p>Subsequent to performing a temporal (synchronic) slice and subsequent
+by <a href="#cea608e">[CEA-608-E]</a>, § C.3, and <a href="#ccreq">[CC-DECODER-REQ]</a>.</p></div></div><div class="div4">
+<h5><a id="semantics-region-layout-step-2"></a>11.3.1.4 Synchronic Flow Processing</h5><p>Subsequent to performing a temporal (synchronic) slice and subsequent
remapping of regionally selected content hierarchy, the resulting intermediate
synchronic document is subjected to a flow transformation step that produces
a rooted flow object tree represented as an XSL FO document instance as defined by <a href="#xsl11">[XSL 1.1]</a>,
@@ -6462,7 +6566,7 @@
solely for the purpose of defining the normative presentation semantics of
TTML. An actual implementation of this algorithm is not required to create or process
XSL-FO representations. In particular, it is possible to implement these semantics
-using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>11.3.3 Intermediate Synchronic Document Construction</b></a> is mapped
+using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>11.3.1.3 Intermediate Synchronic Document Construction</b></a> is mapped
to an XSL FO document instance, <em>F</em>, as follows:</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a <a href="#terms-content-element">content element</a>,
synthesize an anonymous span to enclose the text node, substituting
the new anonymous span for the original text node child in its sibling
@@ -6549,8 +6653,8 @@
to the containing <code>region</code>, while simultaneously taking into account the needs
to satisfy alignment in the block progression dimension. For example, this assures that
the background color associated with the <code>body</code> element, if not <code>transparent</code>,
- will fill the containing region wholly.</p></div></div><div class="div3">
-<h4><a id="semantics-region-layout-example"></a>11.3.5 Elaborated Example (Non-Normative)</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><a id="region-mapping-example-1-s"></a><table class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
+ will fill the containing region wholly.</p></div></div><div class="div4">
+<h5><a id="semantics-region-layout-example"></a>11.3.1.5 Elaborated Example (Non-Normative)</h5><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><a id="region-mapping-example-1-s"></a><table class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
xmlns="http://www.w3.org/ns/ttml"
xmlns:tts="http://www.w3.org/ns/ttml#styling">
@@ -6801,13 +6905,13 @@
</head>
</tt>
</pre></div>
-</td></tr></tbody></table></div></div><div class="div2">
-<h3><a id="semantics-line-layout"></a>11.4 Line Layout</h3><p>If a profile that applies to a <a href="#terms-document-instance">document instance</a>
+</td></tr></tbody></table></div></div><div class="div3">
+<h4><a id="semantics-line-layout"></a>11.3.2 Line Layout</h4><p>If a profile that applies to a <a href="#terms-document-instance">document instance</a>
requires use of the <a href="#feature-lineBreak-uax14">#lineBreak-uax14</a> feature
(i.e., the value attribute for the feature is specified as <code>use</code>), then
the recommendations defined by <a href="http://www.unicode.org/reports/tr14/#Algorithm">Line
Breaking Algorithm</a> <a href="#uax14">[UAX14]</a> apply when performing
-line layout on the content of the <a href="#terms-document-instance">document instance</a>.</p></div></div><div class="div1">
+line layout on the content of the <a href="#terms-document-instance">document instance</a>.</p></div></div></div><div class="div1">
<h2><a id="timing"></a>12 Timing</h2><p>This section specifies the <em>timing</em> matter of the core
vocabulary catalog, where
timing is to be understood as a separable layer of information that applies to
@@ -6945,7 +7049,7 @@
when the <code>clock</code> time base applies.</p><p>If a <timeExpression> is expressed in terms of an
<em>offset-time</em> and no <em>metric</em> is specified, then it is to be treated as
if a metric of <code>s</code> (seconds) were specified.</p></div></div><div class="div2">
-<h3><a id="timing-time-intervals"></a>12.4 Time Intervals</h3><p>The semantics of time containment, durations, and intervals defined by
+<h3><a id="semantics-timing"></a>12.4 Timing Semantics</h3><p>The semantics of time containment, durations, and intervals defined by
<a href="#smil3">[SMIL 3.0]</a> apply to the interpretation of like-named timed elements and timing
vocabulary defined by this specification, given the following
constraints:</p><ul><li><p>The implicit duration of an anonymous span is defined as follows: if
@@ -6995,7 +7099,7 @@
<animate
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
calcMode = <a href="#animation-value-calcMode"><calcMode></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
fill = <a href="#animation-value-fill"><fill></a>
@@ -7068,7 +7172,7 @@
zero or more elements in the <a href="#element-vocab-group-animation"><code>Animation.class</code></a> element group.</p><a id="elt-syntax-animation"></a><table class="syntax"><caption>XML Representation – Element Information Item: animation</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<animation
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -7092,7 +7196,7 @@
<div class="exampleInner"><pre>
<set
<a href="#timing-attribute-begin">begin</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<a href="#timing-attribute-dur">dur</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
<a href="#timing-attribute-end">end</a> = <a href="#timing-value-timeExpression"><timeExpression></a>
fill = <a href="#animation-value-fill"><fill></a>
@@ -7295,7 +7399,7 @@
(4) a combination of the preceding.</p><a id="elt-syntax-metadata"></a><table class="syntax"><caption>XML Representation – Element Information Item: metadata</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<metadata
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -7365,7 +7469,7 @@
<div class="exampleInner"><pre>
<ttm:actor
<span class="reqattr">agent</span> = IDREF
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -7383,7 +7487,7 @@
agent, whether it be the name of a person, character, group, or organization.</p><a id="elt-syntax-metadata-agent"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:agent</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttm:agent
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<span class="reqattr">type</span> = (<em>person</em>|<em>character</em>|<em>group</em>|<em>organization</em>|<em>other</em>)
<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>
@@ -7440,7 +7544,7 @@
child of the <code>head</code> element.</p><a id="elt-syntax-metadata-copyright"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:copyright</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttm:copyright
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -7453,7 +7557,7 @@
a specific element instance.</p><a id="elt-syntax-metadata-desc"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:desc</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttm:desc
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -7469,7 +7573,7 @@
(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>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<span class="reqattr">name</span> = <a href="#metadata-value-item-name"><item-name></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>
@@ -7510,7 +7614,7 @@
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>
<ttm:name
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></a>
<span class="reqattr">type</span> = (<em>full</em>|<em>family</em>|<em>given</em>|<em>alias</em>|<em>other</em>)
<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>
@@ -7527,7 +7631,7 @@
a specific element instance.</p><a id="elt-syntax-metadata-title"></a><table class="syntax"><caption>XML Representation – Element Information Item: ttm:title</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttm:title
- <a href="#content-attribute-condition">condition</a> = <a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a>
+ <a href="#content-attribute-condition">condition</a> = <a href="#content-value-condition"><condition></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>)
@@ -8442,8 +8546,8 @@
(1) satisfies the generic processor criteria defined by
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>,
(2) implements support for the region and line layout
-semantics defined by <a href="#semantics-region-layout"><b>11.3 Region Layout and Presentation</b></a> and
-<a href="#semantics-line-layout"><b>11.4 Line Layout</b></a>, respectively, and
+semantics defined by <a href="#semantics-region-layout"><b>11.3.1 Region Layout and Presentation</b></a> and
+<a href="#semantics-line-layout"><b>11.3.2 Line Layout</b></a>, respectively, and
(3) implements presentation semantics for the following features:</p><ul><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#feature-core"><code>#core</code></a></p></li><li><p><a href="#feature-profile"><code>#profile</code></a></p></li><li><p><a href="#feature-structure"><code>#structure</code></a></p></li><li><p><a href="#feature-time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul><p>
In addition, a TTML processor that supports the
<code>#presentation</code> feature should satisfy the user agent
@@ -9432,6 +9536,9 @@
</dd><dt class="label"><a id="css3-bb"></a>CSS Backgrounds and Borders</dt><dd>Bert Bos, Elika Etamad and Brad Kemper,
<a href="http://dev.w3.org/csswg/css3-background/"><cite>CSS Backgrounds and Borders Module Level 3</cite></a>, W3C Editor's Draft. (See
<a href="http://dev.w3.org/csswg/css3-background/">http://dev.w3.org/csswg/css-backgrounds/</a>.)
+</dd><dt class="label"><a id="css3-box"></a>CSS Box Model</dt><dd>Bert Bos, Anton Prowse,
+<a href="http://dev.w3.org/csswg/css-box-3/"><cite>CSS Basic Box Model</cite></a>, W3C Editor's Draft. (See
+<a href="http://dev.w3.org/csswg/css-box-3/">http://dev.w3.org/csswg/css-box-3/</a>.)
</dd><dt class="label"><a id="css3-fonts"></a>CSS Fonts</dt><dd>John Daggett,
<a href="http://dev.w3.org/csswg/css-fonts/"><cite>CSS Fonts Module Level 3</cite></a>, W3C Editor's Draft. (See
<a href="http://dev.w3.org/csswg/css-fonts/">http://dev.w3.org/csswg/css-fonts/</a>.)
@@ -9506,7 +9613,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="d3e34192"></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="d3e34828"></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
@@ -9563,7 +9670,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="d3e34709"></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="d3e35345"></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
@@ -9655,9 +9762,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="d3e35702"></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="d3e36338"></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="d3e35866"></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="d3e36502"></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">