--- a/spec/ttaf1-dfxp.html Sun May 31 14:57:44 2009 +0000
+++ b/spec/ttaf1-dfxp.html Sun May 31 14:59:30 2009 +0000
@@ -76,7 +76,7 @@
<a href="ttaf1-dfxp.html">ttaf1-dfxp.html</a>
</dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2008/tt/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2008/tt/spec/ttaf1-dfxp.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116/">http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116/</a>
-</dd><dt>Editor:</dt><dd>Glenn Adams, <span class="diff-chg">Samsung Electronics Co., Ltd.</span></dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+</dd><dt>Editor:</dt><dd>Glenn Adams, Samsung Electronics Co., Ltd.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>This document specifies the distribution format exchange profile
(DFXP) of the timed text authoring format (TT AF) in terms of a
vocabulary and semantics thereof.</p><p>The timed text authoring format is a content type that represents
@@ -327,106 +327,104 @@
E.1.16 <a href="#feature-display-region">#display-region</a><br/>
E.1.17 <a href="#feature-displayAlign">#displayAlign</a><br/>
E.1.18 <a href="#feature-dynamicFlow">#dynamicFlow</a><br/>
- E.1.19 <a href="#feature-dynamicFlow-block">#dynamicFlow-block</a><br/>
- E.1.20 <a href="#feature-dynamicFlow-character">#dynamicFlow-character</a><br/>
- E.1.21 <a href="#feature-dynamicFlow-clear">#dynamicFlow-clear</a><br/>
- E.1.22 <a href="#feature-dynamicFlow-fill">#dynamicFlow-fill</a><br/>
- E.1.23 <a href="#feature-dynamicFlow-glyph">#dynamicFlow-glyph</a><br/>
- E.1.24 <a href="#feature-dynamicFlow-in">#dynamicFlow-in</a><br/>
- E.1.25 <a href="#feature-dynamicFlow-inline">#dynamicFlow-inline</a><br/>
- E.1.26 <a href="#feature-dynamicFlow-jump">#dynamicFlow-jump</a><br/>
- E.1.27 <a href="#feature-dynamicFlow-line">#dynamicFlow-line</a><br/>
- E.1.28 <a href="#feature-dynamicFlow-out">#dynamicFlow-out</a><br/>
- E.1.29 <a href="#feature-dynamicFlow-rollUp">#dynamicFlow-rollUp</a><br/>
- E.1.30 <a href="#feature-dynamicFlow-smooth">#dynamicFlow-smooth</a><br/>
- E.1.31 <a href="#feature-dynamicFlow-teletext">#dynamicFlow-teletext</a><br/>
- E.1.32 <a href="#feature-dynamicFlow-word">#dynamicFlow-word</a><br/>
- E.1.33 <a href="#feature-extent">#extent</a><br/>
- E.1.34 <a href="#feature-fontFamily">#fontFamily</a><br/>
- E.1.35 <a href="#feature-fontFamily-generic">#fontFamily-generic</a><br/>
- E.1.36 <a href="#feature-fontFamily-non-generic">#fontFamily-non-generic</a><br/>
- E.1.37 <a href="#feature-fontSize">#fontSize</a><br/>
- E.1.38 <a href="#feature-fontSize-anisomorphic">#fontSize-anisomorphic</a><br/>
- E.1.39 <a href="#feature-fontSize-isomorphic">#fontSize-isomorphic</a><br/>
- E.1.40 <a href="#feature-fontStyle">#fontStyle</a><br/>
- E.1.41 <a href="#feature-fontStyle-italic">#fontStyle-italic</a><br/>
- E.1.42 <a href="#feature-fontWeight">#fontWeight</a><br/>
- E.1.43 <a href="#feature-fontWeight-bold">#fontWeight-bold</a><br/>
- E.1.44 <a href="#feature-frameRate">#frameRate</a><br/>
- E.1.45 <a href="#feature-frameRateMultiplier">#frameRateMultiplier</a><br/>
- E.1.46 <a href="#feature-layout">#layout</a><br/>
- E.1.47 <a href="#feature-length">#length</a><br/>
- E.1.48 <a href="#feature-length-cell">#length-cell</a><br/>
- E.1.49 <a href="#feature-length-em">#length-em</a><br/>
- E.1.50 <a href="#feature-length-integer">#length-integer</a><br/>
- E.1.51 <a href="#feature-length-negative">#length-negative</a><br/>
- E.1.52 <a href="#feature-length-percentage">#length-percentage</a><br/>
- E.1.53 <a href="#feature-length-pixel">#length-pixel</a><br/>
- E.1.54 <a href="#feature-length-positive">#length-positive</a><br/>
- E.1.55 <a href="#feature-length-real">#length-real</a><br/>
- E.1.56 <a href="#feature-lineBreak-uax14">#lineBreak-uax14</a><br/>
- E.1.57 <a href="#feature-lineHeight">#lineHeight</a><br/>
- E.1.58 <a href="#feature-markerMode">#markerMode</a><br/>
- E.1.59 <a href="#feature-metadata">#metadata</a><br/>
- E.1.60 <a href="#feature-nested-div">#nested-div</a><br/>
- E.1.61 <a href="#feature-nested-span">#nested-span</a><br/>
- E.1.62 <a href="#feature-opacity">#opacity</a><br/>
- E.1.63 <a href="#feature-origin">#origin</a><br/>
- E.1.64 <a href="#feature-overflow">#overflow</a><br/>
- E.1.65 <a href="#feature-overflow-dynamic">#overflow-dynamic</a><br/>
- E.1.66 <a href="#feature-padding">#padding</a><br/>
- E.1.67 <a href="#feature-padding-1">#padding-1</a><br/>
- E.1.68 <a href="#feature-padding-2">#padding-2</a><br/>
- E.1.69 <a href="#feature-padding-3">#padding-3</a><br/>
- E.1.70 <a href="#feature-padding-4">#padding-4</a><br/>
- E.1.71 <a href="#feature-pixelAspectRatio">#pixelAspectRatio</a><br/>
- E.1.72 <a href="#feature-presentation">#presentation</a><br/>
- E.1.73 <a href="#feature-profile">#profile</a><br/>
- E.1.74 <a href="#feature-rollUp">#rollUp</a><br/>
- E.1.75 <a href="#feature-showBackground">#showBackground</a><br/>
- E.1.76 <a href="#feature-smpteMode">#smpteMode</a><br/>
- E.1.77 <a href="#feature-structure">#structure</a><br/>
- E.1.78 <a href="#feature-styling">#styling</a><br/>
- E.1.79 <a href="#feature-styling-chained">#styling-chained</a><br/>
- E.1.80 <a href="#feature-styling-inheritance-content">#styling-inheritance-content</a><br/>
- E.1.81 <a href="#feature-styling-inheritance-region">#styling-inheritance-region</a><br/>
- E.1.82 <a href="#feature-styling-inline">#styling-inline</a><br/>
- E.1.83 <a href="#feature-styling-nested">#styling-nested</a><br/>
- E.1.84 <a href="#feature-styling-referential">#styling-referential</a><br/>
- E.1.85 <a href="#feature-subFrameRate">#subFrameRate</a><br/>
- E.1.86 <a href="#feature-textAlign">#textAlign</a><br/>
- E.1.87 <a href="#feature-textAlign-absolute">#textAlign-absolute</a><br/>
- E.1.88 <a href="#feature-textAlign-relative">#textAlign-relative</a><br/>
- E.1.89 <a href="#feature-textDecoration">#textDecoration</a><br/>
- E.1.90 <a href="#feature-textDecoration-over">#textDecoration-over</a><br/>
- E.1.91 <a href="#feature-textDecoration-through">#textDecoration-through</a><br/>
- E.1.92 <a href="#feature-textDecoration-under">#textDecoration-under</a><br/>
- E.1.93 <a href="#feature-textOutline">#textOutline</a><br/>
- E.1.94 <a href="#feature-textOutline-blur">#textOutline-blur</a><br/>
- E.1.95 <a href="#feature-tickRate">#tickRate</a><br/>
- E.1.96 <a href="#feature-timeBase-clock">#timeBase-clock</a><br/>
- E.1.97 <a href="#feature-timeBase-media">#timeBase-media</a><br/>
- E.1.98 <a href="#feature-timeBase-smpte">#timeBase-smpte</a><br/>
- E.1.99 <a href="#feature-timeContainer">#timeContainer</a><br/>
- E.1.100 <a href="#feature-time-clock">#time-clock</a><br/>
- E.1.101 <a href="#feature-time-clock-with-frames">#time-clock-with-frames</a><br/>
- E.1.102 <a href="#feature-time-offset">#time-offset</a><br/>
- E.1.103 <a href="#feature-time-offset-with-frames">#time-offset-with-frames</a><br/>
- E.1.104 <a href="#feature-time-offset-with-ticks">#time-offset-with-ticks</a><br/>
- E.1.105 <a href="#feature-timing">#timing</a><br/>
- E.1.106 <a href="#feature-transformation">#transformation</a><br/>
- E.1.107 <a href="#feature-unicodeBidi">#unicodeBidi</a><br/>
- E.1.108 <a href="#feature-visibility">#visibility</a><br/>
- E.1.109 <a href="#feature-visibility-block">#visibility-block</a><br/>
- E.1.110 <a href="#feature-visibility-inline">#visibility-inline</a><br/>
- E.1.111 <a href="#feature-visibility-region">#visibility-region</a><br/>
- E.1.112 <a href="#feature-wrapOption">#wrapOption</a><br/>
- E.1.113 <a href="#feature-writingMode">#writingMode</a><br/>
- E.1.114 <a href="#feature-writingMode-vertical">#writingMode-vertical</a><br/>
- E.1.115 <a href="#feature-writingMode-horizontal">#writingMode-horizontal</a><br/>
- E.1.116 <a href="#feature-writingMode-horizontal-lr">#writingMode-horizontal-lr</a><br/>
- E.1.117 <a href="#feature-writingMode-horizontal-rl">#writingMode-horizontal-rl</a><br/>
- E.1.118 <a href="#feature-zIndex">#zIndex</a><br/>
+ E.1.19 <a href="#feature-dynamicFlow-character">#dynamicFlow-character</a><br/>
+ E.1.20 <a href="#feature-dynamicFlow-clear">#dynamicFlow-clear</a><br/>
+ E.1.21 <a href="#feature-dynamicFlow-fill">#dynamicFlow-fill</a><br/>
+ E.1.22 <a href="#feature-dynamicFlow-glyph">#dynamicFlow-glyph</a><br/>
+ E.1.23 <a href="#feature-dynamicFlow-in">#dynamicFlow-in</a><br/>
+ E.1.24 <a href="#feature-dynamicFlow-jump">#dynamicFlow-jump</a><br/>
+ E.1.25 <a href="#feature-dynamicFlow-line">#dynamicFlow-line</a><br/>
+ E.1.26 <a href="#feature-dynamicFlow-out">#dynamicFlow-out</a><br/>
+ E.1.27 <a href="#feature-dynamicFlow-rollUp">#dynamicFlow-rollUp</a><br/>
+ E.1.28 <a href="#feature-dynamicFlow-smooth">#dynamicFlow-smooth</a><br/>
+ E.1.29 <a href="#feature-dynamicFlow-teletext">#dynamicFlow-teletext</a><br/>
+ E.1.30 <a href="#feature-dynamicFlow-word">#dynamicFlow-word</a><br/>
+ E.1.31 <a href="#feature-extent">#extent</a><br/>
+ E.1.32 <a href="#feature-fontFamily">#fontFamily</a><br/>
+ E.1.33 <a href="#feature-fontFamily-generic">#fontFamily-generic</a><br/>
+ E.1.34 <a href="#feature-fontFamily-non-generic">#fontFamily-non-generic</a><br/>
+ E.1.35 <a href="#feature-fontSize">#fontSize</a><br/>
+ E.1.36 <a href="#feature-fontSize-anisomorphic">#fontSize-anisomorphic</a><br/>
+ E.1.37 <a href="#feature-fontSize-isomorphic">#fontSize-isomorphic</a><br/>
+ E.1.38 <a href="#feature-fontStyle">#fontStyle</a><br/>
+ E.1.39 <a href="#feature-fontStyle-italic">#fontStyle-italic</a><br/>
+ E.1.40 <a href="#feature-fontWeight">#fontWeight</a><br/>
+ E.1.41 <a href="#feature-fontWeight-bold">#fontWeight-bold</a><br/>
+ E.1.42 <a href="#feature-frameRate">#frameRate</a><br/>
+ E.1.43 <a href="#feature-frameRateMultiplier">#frameRateMultiplier</a><br/>
+ E.1.44 <a href="#feature-layout">#layout</a><br/>
+ E.1.45 <a href="#feature-length">#length</a><br/>
+ E.1.46 <a href="#feature-length-cell">#length-cell</a><br/>
+ E.1.47 <a href="#feature-length-em">#length-em</a><br/>
+ E.1.48 <a href="#feature-length-integer">#length-integer</a><br/>
+ E.1.49 <a href="#feature-length-negative">#length-negative</a><br/>
+ E.1.50 <a href="#feature-length-percentage">#length-percentage</a><br/>
+ E.1.51 <a href="#feature-length-pixel">#length-pixel</a><br/>
+ E.1.52 <a href="#feature-length-positive">#length-positive</a><br/>
+ E.1.53 <a href="#feature-length-real">#length-real</a><br/>
+ E.1.54 <a href="#feature-lineBreak-uax14">#lineBreak-uax14</a><br/>
+ E.1.55 <a href="#feature-lineHeight">#lineHeight</a><br/>
+ E.1.56 <a href="#feature-markerMode">#markerMode</a><br/>
+ E.1.57 <a href="#feature-metadata">#metadata</a><br/>
+ E.1.58 <a href="#feature-nested-div">#nested-div</a><br/>
+ E.1.59 <a href="#feature-nested-span">#nested-span</a><br/>
+ E.1.60 <a href="#feature-opacity">#opacity</a><br/>
+ E.1.61 <a href="#feature-origin">#origin</a><br/>
+ E.1.62 <a href="#feature-overflow">#overflow</a><br/>
+ E.1.63 <a href="#feature-overflow-dynamic">#overflow-dynamic</a><br/>
+ E.1.64 <a href="#feature-padding">#padding</a><br/>
+ E.1.65 <a href="#feature-padding-1">#padding-1</a><br/>
+ E.1.66 <a href="#feature-padding-2">#padding-2</a><br/>
+ E.1.67 <a href="#feature-padding-3">#padding-3</a><br/>
+ E.1.68 <a href="#feature-padding-4">#padding-4</a><br/>
+ E.1.69 <a href="#feature-pixelAspectRatio">#pixelAspectRatio</a><br/>
+ E.1.70 <a href="#feature-presentation">#presentation</a><br/>
+ E.1.71 <a href="#feature-profile">#profile</a><br/>
+ E.1.72 <a href="#feature-rollUp">#rollUp</a><br/>
+ E.1.73 <a href="#feature-showBackground">#showBackground</a><br/>
+ E.1.74 <a href="#feature-smpteMode">#smpteMode</a><br/>
+ E.1.75 <a href="#feature-structure">#structure</a><br/>
+ E.1.76 <a href="#feature-styling">#styling</a><br/>
+ E.1.77 <a href="#feature-styling-chained">#styling-chained</a><br/>
+ E.1.78 <a href="#feature-styling-inheritance-content">#styling-inheritance-content</a><br/>
+ E.1.79 <a href="#feature-styling-inheritance-region">#styling-inheritance-region</a><br/>
+ E.1.80 <a href="#feature-styling-inline">#styling-inline</a><br/>
+ E.1.81 <a href="#feature-styling-nested">#styling-nested</a><br/>
+ E.1.82 <a href="#feature-styling-referential">#styling-referential</a><br/>
+ E.1.83 <a href="#feature-subFrameRate">#subFrameRate</a><br/>
+ E.1.84 <a href="#feature-textAlign">#textAlign</a><br/>
+ E.1.85 <a href="#feature-textAlign-absolute">#textAlign-absolute</a><br/>
+ E.1.86 <a href="#feature-textAlign-relative">#textAlign-relative</a><br/>
+ E.1.87 <a href="#feature-textDecoration">#textDecoration</a><br/>
+ E.1.88 <a href="#feature-textDecoration-over">#textDecoration-over</a><br/>
+ E.1.89 <a href="#feature-textDecoration-through">#textDecoration-through</a><br/>
+ E.1.90 <a href="#feature-textDecoration-under">#textDecoration-under</a><br/>
+ E.1.91 <a href="#feature-textOutline">#textOutline</a><br/>
+ E.1.92 <a href="#feature-textOutline-blur">#textOutline-blur</a><br/>
+ E.1.93 <a href="#feature-tickRate">#tickRate</a><br/>
+ E.1.94 <a href="#feature-timeBase-clock">#timeBase-clock</a><br/>
+ E.1.95 <a href="#feature-timeBase-media">#timeBase-media</a><br/>
+ E.1.96 <a href="#feature-timeBase-smpte">#timeBase-smpte</a><br/>
+ E.1.97 <a href="#feature-timeContainer">#timeContainer</a><br/>
+ E.1.98 <a href="#feature-time-clock">#time-clock</a><br/>
+ E.1.99 <a href="#feature-time-clock-with-frames">#time-clock-with-frames</a><br/>
+ E.1.100 <a href="#feature-time-offset">#time-offset</a><br/>
+ E.1.101 <a href="#feature-time-offset-with-frames">#time-offset-with-frames</a><br/>
+ E.1.102 <a href="#feature-time-offset-with-ticks">#time-offset-with-ticks</a><br/>
+ E.1.103 <a href="#feature-timing">#timing</a><br/>
+ E.1.104 <a href="#feature-transformation">#transformation</a><br/>
+ E.1.105 <a href="#feature-unicodeBidi">#unicodeBidi</a><br/>
+ E.1.106 <a href="#feature-visibility">#visibility</a><br/>
+ E.1.107 <a href="#feature-visibility-block">#visibility-block</a><br/>
+ E.1.108 <a href="#feature-visibility-inline">#visibility-inline</a><br/>
+ E.1.109 <a href="#feature-visibility-region">#visibility-region</a><br/>
+ E.1.110 <a href="#feature-wrapOption">#wrapOption</a><br/>
+ E.1.111 <a href="#feature-writingMode">#writingMode</a><br/>
+ E.1.112 <a href="#feature-writingMode-vertical">#writingMode-vertical</a><br/>
+ E.1.113 <a href="#feature-writingMode-horizontal">#writingMode-horizontal</a><br/>
+ E.1.114 <a href="#feature-writingMode-horizontal-lr">#writingMode-horizontal-lr</a><br/>
+ E.1.115 <a href="#feature-writingMode-horizontal-rl">#writingMode-horizontal-rl</a><br/>
+ E.1.116 <a href="#feature-zIndex">#zIndex</a><br/>
E.2 <a href="#feature-support">Feature Support</a><br/>
F <a href="#extensions">Extensions</a><br/>
F.1 <a href="#extension-designations">Extension Designations</a><br/>
@@ -438,11 +436,11 @@
I <a href="#other-references">Other References</a> (Non-Normative)<br/>
J <a href="#requirements">Requirements</a> (Non-Normative)<br/>
K <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br/>
- K.1 <a href="#d3e19267">Element Derivation</a><br/>
- K.2 <a href="#d3e19746">Attribute Derivation</a><br/>
+ K.1 <a href="#d3e18335">Element Derivation</a><br/>
+ K.2 <a href="#d3e18814">Attribute Derivation</a><br/>
L <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br/>
- L.1 <a href="#d3e20658">Requirements</a><br/>
- L.2 <a href="#d3e20822">Guidelines</a><br/>
+ L.1 <a href="#d3e19726">Requirements</a><br/>
+ L.2 <a href="#d3e19890">Guidelines</a><br/>
M <a href="#streaming">Streaming DFXP Content</a> (Non-Normative)<br/>
N <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br/>
O <a href="#change-history">Change History</a> (Non-Normative)<br/>
@@ -751,12 +749,7 @@
<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the DFXP Transformation profile as specified
by <a href="#profile-dfxp-transformation"><b>G.1 DFXP Transformation Profile</b></a>.</p></li></ol></div><div class="div3">
<h4><a name="conformance-presentation-processor" id="conformance-presentation-processor"/>3.2.3 Presentation Processor Conformance</h4><ol class="enumar"><li><p>The processor satisfies all requirements specified by
-<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p class="diff-del">The processor implements support for the region and line layout
-semantics defined by <a href="#semantics-region-layout"><b>9.3 Region Layout and Presentation</b></a> and
-<a href="#semantics-line-layout"><b>9.4 Line Layout</b></a>, respectively. In addition, the
-processor should satisfy the user agent accessibility guidelines specified by
-<a href="#uaag">[UAAG]</a>.
-</p></li><li><p>The processor supports the DFXP Presentation profile as specified
+<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>.</p></li><li><p>The processor supports the DFXP Presentation profile as specified
by <a href="#profile-dfxp-presentation"><b>G.2 DFXP Presentation Profile</b></a>.</p></li></ol></div></div><div class="div2">
<h3><a name="claims" id="claims"/>3.3 Claims</h3><p>Any claim of compliance with respect to TT AF content or processor
conformance must make
@@ -818,14 +811,14 @@
and indicates the default prefix used within this specification and the
normative URI that denotes each namespace.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In a specific document instance, it is not required that the default
prefixes shown below are used. Any prefix or namespace binding that satisfies the constraints
-of XML Namespaces may be used that is associated with the specified namespace URI.</p></div><table summary="HTML Table" id="namespace-vocab-table" class="common"><caption>Table 1 – Namespaces</caption><col width="30%" span="1"/><tbody><tr><th>Name</th><th>Prefix</th><th>Value</th></tr><tr><td>TT</td><td><code>tt:</code></td><td><code>http://www.w3.org/2006/10/ttaf1</code></td></tr><tr><td>TT Parameter</td><td><code>ttp:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#parameter</code></td></tr><tr><td><span class="diff-del">TT Parameter Extension</span></td><td><span class="diff-del"><code>ttpx:</code></span></td><td><span class="diff-del"><code>http://www.w3.org/2006/10/ttaf1#parameter-extension</code></span></td></tr><tr><td>TT Style</td><td><code>tts:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#styling</code></td></tr><tr><td><span class="diff-del">TT Style Extension</span></td><td><span class="diff-del"><code>ttsx:</code></span></td><td><span class="diff-del"><code>http://www.w3.org/2006/10/ttaf1#styling-extension</code></span></td></tr><tr><td>TT Metadata</td><td><code>ttm:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#metadata</code></td></tr><tr><td><span class="diff-del">TT Metadata Extension</span></td><td><span class="diff-del"><code>ttmx:</code></span></td><td><span class="diff-del"><code>http://www.w3.org/2006/10/ttaf1#metadata-extension</code></span></td></tr><tr><td>TT Profile</td><td><em>none</em></td><td><code>http://www.w3.org/2006/10/ttaf1/profile</code></td></tr><tr><td>TT Feature</td><td><em>none</em></td><td><code>http://www.w3.org/2006/10/ttaf1/feature</code></td></tr><tr><td>TT Extension</td><td><em>none</em></td><td><code>http://www.w3.org/2006/10/ttaf1/extension</code></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If a reference to an element type is used in this specification and the name
+of XML Namespaces may be used that is associated with the specified namespace URI.</p></div><table summary="HTML Table" id="namespace-vocab-table" class="common"><caption>Table 1 – Namespaces</caption><col width="30%" span="1"/><tbody><tr><th>Name</th><th>Prefix</th><th>Value</th></tr><tr><td>TT</td><td><code>tt:</code></td><td><code>http://www.w3.org/2006/10/ttaf1</code></td></tr><tr><td>TT Parameter</td><td><code>ttp:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#parameter</code></td></tr><tr><td>TT Style</td><td><code>tts:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#styling</code></td></tr><tr><td>TT Metadata</td><td><code>ttm:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#metadata</code></td></tr><tr><td>TT Profile</td><td><em>none</em></td><td><code>http://www.w3.org/2006/10/ttaf1/profile</code></td></tr><tr><td>TT Feature</td><td><em>none</em></td><td><code>http://www.w3.org/2006/10/ttaf1/feature</code></td></tr><tr><td>TT Extension</td><td><em>none</em></td><td><code>http://www.w3.org/2006/10/ttaf1/extension</code></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>If a reference to an element type is used in this specification and the name
of the element type is not namespace qualified, then the TT Namespace applies.</p><p>For certain namespaces defined above, the default prefix
is specified as <em>none</em> if no XML vocabulary is defined in
the namespace by this specification (nor expected to be defined in a
future version of this specification). In such cases, the use of the
namespace URI is for purposes other than defining XML vocabulary,
e.g., for designating profiles, features, extensions and for
-dereferencing standard profile definitions.</p></div><p class="diff-add">All TT AF Namespaces are <a href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><em>mutable</em></a>
+dereferencing standard profile definitions.</p></div><p>All TT AF Namespaces are <a href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><em>mutable</em></a>
<a href="#nsstate">[NSState]</a>; all undefined names in these namespaces are reserved for future
standardization by the W3C.</p></div><div class="div2">
<h3><a name="vocabulary-profiles" id="vocabulary-profiles"/>5.2 Profiles</h3><p>The Timed Text Authoring Format (TT AF) employs a number of
@@ -837,7 +830,7 @@
and designator for each
predefined profile,
and where each of these profiles is formally elaborated in
-<a href="#profiles"><b>G Profiles</b></a>.</p><table summary="HTML Table" id="profile-vocab-table" class="common"><caption>Table 2 – Profiles</caption><col width="25%" span="1"/><tbody><tr><th>Name</th><th>Designator</th></tr><tr><td>DFXP Transformation</td><td><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation</code></td></tr><tr><td>DFXP Presentation</td><td><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code></td></tr><tr><td><span class="diff-add">DFXP Full</span></td><td><span class="diff-add"><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-full</code></span></td></tr></tbody></table><p/><p>A profile designator must adhere to the
+<a href="#profiles"><b>G Profiles</b></a>.</p><table summary="HTML Table" id="profile-vocab-table" class="common"><caption>Table 2 – Profiles</caption><col width="25%" span="1"/><tbody><tr><th>Name</th><th>Designator</th></tr><tr><td>DFXP Transformation</td><td><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation</code></td></tr><tr><td>DFXP Presentation</td><td><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code></td></tr><tr><td>DFXP Full</td><td><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-full</code></td></tr></tbody></table><p/><p>A profile designator must adhere to the
<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
§3.2.17. If the profile designator is expressed as a relative URI,
then it must be absolutized by using the TT Profile Namespace value as
@@ -846,20 +839,20 @@
would be
<code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code>.</p></div><p>A profile designator is not restricted to the set of designators enumerated
in <a href="#profile-vocab-table"><b>Table 2 – Profiles</b></a>, but may be any URI that
-feasibly dereferences a TT AF Profile Definition Document.</p><p>The profile of <span class="diff-add">TT AF that must be supported by a
-TT AF content processor in order to process</span> a document
+feasibly dereferences a TT AF Profile Definition Document.</p><p>The profile of TT AF that must be supported by a
+TT AF content processor in order to process a document
instance is specified either (1) by specifying a
<code>ttp:profile</code> attribute on the root <code>tt</code> element, as
defined by <a href="#parameter-attribute-profile"><b>6.2.7 ttp:profile</b></a>, or (2) by
-including <span class="diff-chg">one or more</span> <code>ttp:profile</code>
-element<span class="diff-add">s</span> in the <code>head</code> element, in
-accordance with <a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p><p class="diff-add">If a <code>ttp:profile</code> element appears as a
+including one or more <code>ttp:profile</code>
+elements in the <code>head</code> element, in
+accordance with <a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p><p>If a <code>ttp:profile</code> element appears as a
descendant of the <code>tt</code> element, then the <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
attribute should not be specified on the <code>tt</code> element. If both
a <code>ttp:profile</code> element and a <code>ttp:profile</code>
attribute are present (in a given document instance), then the
<code>ttp:profile</code> attribute must be ignored for the purpose of
-determining the declared profile requirements.</p><p class="diff-add">If more than one <code>ttp:profile</code> element appears in
+determining the declared profile requirements.</p><p>If more than one <code>ttp:profile</code> element appears in
a TT AF document instance, then all specified profiles apply
simultaneously. In such a case, if some feature or some extension is
specified by one profile to be used (mandatory and enabled) and by
@@ -897,35 +890,35 @@
and additive.</p></div><p>If a TT AF document instance makes use of a feature defined by
<a href="#feature-designations"><b>E.1 Feature Designations</b></a> and if the intended use of the
document requires the recognition and processing of that feature, then
-the document must include a <em>required feature</em><span class="diff-add"> or
-a <em>used feature</em></span>
-specification in one of its declared<span class="diff-add"> or
-referenced</span> profiles. If a TT AF document instance makes use
+the document must include a <em>required feature</em> or
+a <em>used feature</em>
+specification in one of its declared or
+referenced profiles. If a TT AF document instance makes use
of an extension designatable by <a href="#extension-designations"><b>F.1 Extension Designations</b></a> and if the intended use of the document
requires the recognition and processing of that extension, then the
-document must include a <em>required extension</em><span class="diff-add"> or
-a <em>used extension</em></span> specification
-in one of its declared<span class="diff-add"> or referenced</span>
-profiles.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A required<span class="diff-add"> or used</span> feature
+document must include a <em>required extension</em> or
+a <em>used extension</em> specification
+in one of its declared or referenced
+profiles.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A required or used feature
specification is expressed directly (or indirectly by referring to a
profile) by means of a <a href="#parameter-vocabulary-feature"><code>ttp:feature</code></a>
element where the value of its <code>value</code> attribute is
-<code>required</code><span class="diff-add"> or <code>use</code>,
-respectively</span>. A required<span class="diff-add"> or used</span>
+<code>required</code> or <code>use</code>,
+respectively. A required or used
extension specification is expressed directly (or indirectly by
referring to a profile) by means of a <a href="#parameter-vocabulary-extension"><code>ttp:extension</code></a>
element where the value of its <code>value</code> attribute is
-<code>required</code><span class="diff-add"> or <code>use</code>,
-respectively</span>.</p></div><p>An example of an author defined
-<span class="diff-chg">additive</span>, derived profile of the DFXP Presentation
+<code>required</code> or <code>use</code>,
+respectively.</p></div><p>An example of an author defined
+additive, derived profile of the DFXP Presentation
profile is shown
-below in <a href="#dfxp-example-sub-profile"><b>Example Fragment – DFXP Additive Profile</b></a>.</p><table summary="HTML Table" id="dfxp-example-sub-profile" class="example"><caption>Example Fragment – DFXP <span class="diff-chg">Additive</span> Profile</caption><tbody><tr><td>
+below in <a href="#dfxp-example-sub-profile"><b>Example Fragment – DFXP Additive Profile</b></a>.</p><table summary="HTML Table" id="dfxp-example-sub-profile" class="example"><caption>Example Fragment – DFXP Additive Profile</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1">
<head>
<profile use="dfxp-presentation" xmlns="http://www.w3.org/2006/10/ttaf1#parameter">
- <features <span class="diff-add">xml:base="http://www.w3.org/2006/10/ttaf1/feature"</span>>
- <feature value="<span class="diff-chg">required</span>">#fontStyle-italic</feature>
+ <features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
+ <feature value="required">#fontStyle-italic</feature>
</features>
</profile>
</head>
@@ -933,9 +926,9 @@
</tt>
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the baseline profile is declared to be
-the DFXP Presentation profile, which is then <span class="diff-chg">additively</span> modified by making the
-<code>#fontStyle-italic</code> feature <span class="diff-chg">required</span> (rather than
-<span class="diff-chg">optional</span> as it is defined
+the DFXP Presentation profile, which is then additively modified by making the
+<code>#fontStyle-italic</code> feature required (rather than
+optional as it is defined
in <a href="#profile-dfxp-presentation"><b>G.2 DFXP Presentation Profile</b></a>). Note also the resetting of the
default XMLNS binding on the <code>profile</code> element to the TT Parameter Namespace.</p></div></div><div class="div2">
<h3><a name="vocabulary-overview" id="vocabulary-overview"/>5.3 Catalog</h3><p>The vocabulary of the Timed Text Authoring Format (TT AF) is
@@ -1098,11 +1091,8 @@
change of a name when the name was based upon another specification
that used a different naming convention.</p></div></div><div class="div3">
<h4><a name="extension-vocabulary-overview" id="extension-vocabulary-overview"/>5.3.2 Extension Catalog</h4><p>The extension vocabulary catalog is intended for use by future
-profiles of the TT AF<span class="diff-add">, and is not further defined
-by this version of this specification</span>.</p><p class="diff-del">In this version of this specification, no
-standardized extension vocabulary is defined. The following namespaces are
-specifically reserved by <a href="#namespace-vocab-table"><b>Table 1 – Namespaces</b></a>
-for extension vocabulary:</p><ul class="diff-del"><li><p>TT Metadata Extension</p></li><li><p>TT Parameter Extension</p></li><li><p>TT Style Extension</p></li></ul><p>In addition to standardized extension vocabulary, a conforming TT
+profiles of the TT AF, and is not further defined
+by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming TT
AF document instance may contain arbitrary namespace qualified
elements that reside in any namespace other than those namespaces
defined for use with this specification. Furthermore, a conforming TT
@@ -1121,8 +1111,8 @@
Namespace, specify parametric information that applies to a document
or a content processor:</p><ul><li><p><a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a></p></li><li><p><a href="#parameter-vocabulary-features"><b>6.1.2 ttp:features</b></a></p></li><li><p><a href="#parameter-vocabulary-feature"><b>6.1.3 ttp:feature</b></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><b>6.1.4 ttp:extensions</b></a></p></li><li><p><a href="#parameter-vocabulary-extension"><b>6.1.5 ttp:extension</b></a></p></li></ul><div class="div3">
<h4><a name="parameter-vocabulary-profile" id="parameter-vocabulary-profile"/>6.1.1 ttp:profile</h4><p>The <code>ttp:profile</code> element is used to specify a collection of
-<span class="diff-chg">used (mandatory and enabled), required (mandatory),
-and optional (voluntary)</span> features and extensions that must or
+used (mandatory and enabled), required (mandatory),
+and optional (voluntary) features and extensions that must or
may be supported by a TT AF content processor in order to process a TT
AF document that makes use (or may make use) of such features and
extensions.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The difference between a <em>feature</em> and an
@@ -1191,15 +1181,10 @@
reference a non-standard TT AF Profile Definition Document, then some
end-user notification should be given unless the end-user or system
has disabled such a notification, or if the processor does not permit
-or entail the intervention of an end-user.</p><p class="diff-del">If more than one <code>ttp:profile</code> element appears in a TT AF
-document instance, then all specified profiles apply simultaneously.
-In such a case, if some feature or some extension is specified by one profile
-to be required (mandatory) and by another profile to be optional
-(voluntary), then that feature or extension must be considered to be
-required (mandatory).</p><p>The <code>ttp:profile</code> element is illustrated by the following example.</p><table summary="HTML Table" id="parameter-vocabulary-profile-example-1" class="example"><caption>Example Fragment – ttp:profile</caption><tbody><tr><td>
+or entail the intervention of an end-user.</p><p>The <code>ttp:profile</code> element is illustrated by the following example.</p><table summary="HTML Table" id="parameter-vocabulary-profile-example-1" class="example"><caption>Example Fragment – ttp:profile</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:profile use="dfxp-presentation">
- <ttp:features <span class="diff-add">xml:base="http://www.w3.org/2006/10/ttaf1/feature"</span>>
+ <ttp:features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
<ttp:feature>#rollUp</ttp:feature>
</ttp:features>
</ttp:profile>
@@ -1214,20 +1199,21 @@
zero or more <code>ttp:feature</code> elements.</p><table summary="HTML Table" id="elt-syntax-parameter-features" class="syntax"><caption>XML Representation – Element Information Item: ttp:features</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:features
- <span class="diff-add">xml:</span>base = string : <em>TT Feature Namespace</em>
+ xml:base = string : <em>TT Feature Namespace</em>
<a href="#content-attribute-id">xml:id</a> = ID
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#parameter-vocabulary-feature">ttp:feature</a>*
</ttp:features>
</pre></div>
-</td></tr></tbody></table><p>If specified, the <code><span class="diff-add">xml:</span>base</code>
-attribute must <span class="diff-add">(1) </span>adhere to the
+</td></tr></tbody></table><p>If specified, the <code>xml:base</code>
+attribute must (1) adhere to the
<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
-§3.2.17, <span class="diff-add">(2) express an absolute URI that
-adheres to <a href="#xmlbase">[XML Base]</a></span> and, <span class="diff-chg">(3) </span> express a feature namespace as defined by
+§3.2.17, (2) express an absolute URI that
+adheres to <a href="#xmlbase">[XML Base]</a> and,
+(3) express a feature namespace as defined by
<a href="#feature-designations"><b>E.1 Feature Designations</b></a>. If not specified, the
-<code><span class="diff-add">xml:</span>base</code> attribute's default
-value applies, which is the TT Feature Namespace.</p><p>The <code><span class="diff-add">xml:</span>base</code> attribute is
+<code>xml:base</code> attribute's default
+value applies, which is the TT Feature Namespace.</p><p>The <code>xml:base</code> attribute is
used to permit the abbreviation of feature designation URIs expressed
by child <code>ttp:feature</code> elements.</p></div><div class="div3">
<h4><a name="parameter-vocabulary-feature" id="parameter-vocabulary-feature"/>6.1.3 ttp:feature</h4><p>The <code>ttp:feature</code> element is used to specify
@@ -1237,38 +1223,39 @@
§3.2.17.</p><table summary="HTML Table" id="elt-syntax-parameter-feature" class="syntax"><caption>XML Representation – Element Information Item: ttp:feature</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:feature
- value = (<span class="diff-chg">optional|required|use</span>) : required
+ value = (optional|required|use) : required
<a href="#content-attribute-id">xml:id</a> = ID
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> #PCDATA
</ttp:feature>
</pre></div>
</td></tr></tbody></table><p>If the URI expressed by the content of the <code>ttp:feature</code>
-element is a relative URI, then, when combined with the <span class="diff-chg">feature namespace value expressed by</span> the
-<code><span class="diff-add">xml:</span>base</code> attribute of the
+element is a relative URI, then, when combined with the
+feature namespace value expressed by the
+<code>xml:base</code> attribute of the
nearest ancestor <code>ttp:features</code> element, it must express an
absolute URI. In either case (original absolute URI or resulting
absolutized URI), the URI expressed by the <code>ttp:feature</code>
element must further adhere to the syntax of a feature designation as
-defined by <a href="#feature-designations"><b>E.1 Feature Designations</b></a>.</p><p class="diff-add">If
+defined by <a href="#feature-designations"><b>E.1 Feature Designations</b></a>.</p><p>If
the URI expressed by the content of the <code>ttp:feature</code> element
is a relative URI, then an <code>xml:base</code> attribute should be
specified on the nearest ancestor <code>ttp:features</code> element.</p><p>The <code>value</code> attribute specifies whether a conforming TT AF
processor must or may implement the designated feature in order to
process the document. If the value of the <code>value</code> attribute
-is <span class="diff-chg"> <code>optional</code>, then the processor need
+is <code>optional</code>, then the processor need
not implement or otherwise support the feature in order to process the
document; if the value is <code>required</code>, then the processor
must implement or otherwise support the feature in order to process
-the document;</span><span class="diff-add"> if the value is
+the document; if the value is
<code>use</code>, then the processor must both (1) implement or
otherwise support the feature and (2) enable (activate) use of the
-feature</span>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The default value of the <code>value</code> attribute is
+feature.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The default value of the <code>value</code> attribute is
<code>required</code>, as indicated in the above element information
item definition. Therefore, if a <code>value</code> attribute is not
specified on a <code>ttp:feature</code> element, it is equivalent to
specifying that support for the feature is required.</p></div><p>If the value of the <code>value</code> attribute is
-<code>required</code><span class="diff-add"> or <code>use</code></span>,
+<code>required</code> or <code>use</code>,
and if the TT AF processor implementation does
not support the feature, then it must not further process the document
without the presence of an explicit override from an end-user or some
@@ -1292,45 +1279,46 @@
valid.</p><p>The <code>ttp:feature</code> element is illustrated by the following example.</p><table summary="HTML Table" id="parameter-vocabulary-feature-example-1" class="example"><caption>Example Fragment – ttp:feature</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation">
- <ttp:features <span class="diff-add">xml:base="http://www.w3.org/2006/10/ttaf1/feature"</span>>
- <span class="strong"><ttp:feature value="<span class="diff-add">required</span>">#fontStyle-italic</ttp:feature></span>
+ <ttp:features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
+ <span class="strong"><ttp:feature value="required">#fontStyle-italic</ttp:feature></span>
<span class="strong"><ttp:feature value="required">#textDecoration-under</ttp:feature></span>
</ttp:features>
</ttp:profile>
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the DFXP presentation profile is used as the
baseline profile. This baseline profile is then modified by two
-<code>ttp:feature</code> <span class="diff-chg">elements in order</span> to
-superset the baseline profile <span class="diff-chg">(since neither
+<code>ttp:feature</code> elements in order to
+superset the baseline profile (since neither
<code>#fontStyle-italic</code> nor <code>#textDecoration-under</code>
-are required by the DFXP presentation profile)</span>. Note that
+are required by the DFXP presentation profile). Note that
the explicit specification of <code>required</code> on the
-<code>value</code> attribute on <span class="diff-chg">these two</span>
-<code>ttp:feature</code> elements is not <span class="diff-add">strictly
-</span>necessary, since it is the default value of this
+<code>value</code> attribute on these two
+<code>ttp:feature</code> elements is not strictly
+necessary, since it is the default value of this
attribute.</p><p>The effect of this example is to express authorial intentions that
-<span class="diff-chg">italic font style and text underlining must be
-supported</span>.</p></div></div><div class="div3">
+italic font style and text underlining must be
+supported.</p></div></div><div class="div3">
<h4><a name="parameter-vocabulary-extensions" id="parameter-vocabulary-extensions"/>6.1.4 ttp:extensions</h4><p>The <code>ttp:extensions</code> element is a container element used to group
infomation about extension support requirements.</p><p>The <code>ttp:extensions</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group, followed by
zero or more <code>ttp:extension</code> elements.</p><table summary="HTML Table" id="elt-syntax-parameter-extensions" class="syntax"><caption>XML Representation – Element Information Item: ttp:extensions</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:extensions
- <span class="diff-add">xml:</span>base = string : <em>TT Extension Namespace</em>
+ xml:base = string : <em>TT Extension Namespace</em>
<a href="#content-attribute-id">xml:id</a> = ID
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#parameter-vocabulary-extension">ttp:extension</a>*
</ttp:extensions>
</pre></div>
-</td></tr></tbody></table><p>If specified, the <code><span class="diff-add">xml:</span>base</code>
-attribute must <span class="diff-add">(1) </span>adhere to the
+</td></tr></tbody></table><p>If specified, the <code>xml:base</code>
+attribute must (1) adhere to the
<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
-§3.2.17, <span class="diff-add">(2) express an absolute URI that
-adheres to <a href="#xmlbase">[XML Base]</a></span> and, <span class="diff-chg">(3) </span> express an extension namespace as defined by
+§3.2.17, (2) express an absolute URI that
+adheres to <a href="#xmlbase">[XML Base]</a> and,
+(3) express an extension namespace as defined by
<a href="#extension-designations"><b>F.1 Extension Designations</b></a>. If not specified, the
-<code><span class="diff-add">xml:</span>base</code> attribute's default
-value applies, which is the TT Extension Namespace.</p><p>The <code><span class="diff-add">xml:</span>base</code> attribute is
+<code>xml:base</code> attribute's default
+value applies, which is the TT Extension Namespace.</p><p>The <code>xml:base</code> attribute is
used to permit the abbreviation of feature designation URIs expressed
by child <code>ttp:extension</code> elements.</p></div><div class="div3">
<h4><a name="parameter-vocabulary-extension" id="parameter-vocabulary-extension"/>6.1.5 ttp:extension</h4><p>The <code>ttp:extension</code> element is used to specify
@@ -1340,38 +1328,39 @@
§3.2.17.</p><table summary="HTML Table" id="elt-syntax-parameter-extension" class="syntax"><caption>XML Representation – Element Information Item: ttp:extension</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:extension
- value = (<span class="diff-chg">optional|required|use</span>) : required
+ value = (optional|required|use) : required
<a href="#content-attribute-id">xml:id</a> = ID
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> #PCDATA
</ttp:extension>
</pre></div>
</td></tr></tbody></table><p>If the URI expressed by the content of the <code>ttp:extension</code>
-element is a relative URI, then, when combined with the <span class="diff-chg">extension namespace value expressed by</span> the
-<code><span class="diff-add">xml:</span>base</code> attribute of the
+element is a relative URI, then, when combined with the
+extension namespace value expressed by the
+<code>xml:base</code> attribute of the
nearest ancestor <code>ttp:extensions</code> element, it must express an
absolute URI. In either case (original absolute URI or resulting
absolutized URI), the URI expressed by the <code>ttp:extension</code>
element must further adhere to the syntax of an extension designation
-as defined by <a href="#extension-designations"><b>F.1 Extension Designations</b></a>.</p><p class="diff-add">If the URI expressed by the content of the
+as defined by <a href="#extension-designations"><b>F.1 Extension Designations</b></a>.</p><p>If the URI expressed by the content of the
<code>ttp:feature</code> element is a relative URI, then an
<code>xml:base</code> attribute should be specified on the nearest
ancestor <code>ttp:extensions</code> element.</p><p>The <code>value</code> attribute specifies whether a conforming TT AF
processor must or may implement the designated extension in order to
process the document. If the value of the <code>value</code> attribute
-is <span class="diff-chg"> <code>optional</code>, then the processor need
+is <code>optional</code>, then the processor need
not implement or otherwise support the extension in order to process the
document; if the value is <code>required</code>, then the processor
must implement or otherwise support the extension in order to process
-the document;</span><span class="diff-add"> if the value is
+the document; if the value is
<code>use</code>, then the processor must both (1) implement or
otherwise support the extension and (2) enable (activate) use of the
-extension</span>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The default value of the <code>value</code> attribute is
+extension.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The default value of the <code>value</code> attribute is
<code>required</code>, as indicated in the above element information
item definition. Therefore, if a <code>value</code> attribute is not
specified on a <code>ttp:extension</code> element, it is equivalent to
specifying that support for the extension is required.</p></div><p>If the value of the <code>value</code> attribute is
-<code>required</code><span class="diff-add"> or <code>use</code></span>,
+<code>required</code> or <code>use</code>,
and if the TT AF processor implementation does not support the
extension, then it must not further process the document without the
presence of an explicit override from an end-user or some
@@ -1395,34 +1384,17 @@
valid.</p><p>The <code>ttp:extension</code> element is illustrated by the following example.</p><table summary="HTML Table" id="parameter-vocabulary-extension-example-1" class="example"><caption>Example Fragment – ttp:extension</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation">
-<span class="diff-del"> <ttp:extensions>
- <span class="strong"><ttp:extension value="required">#x-prefilter-by-language</ttp:extension></span>
- </ttp:extensions></span>
- <ttp:extensions <span class="diff-add">xml:</span>base="http://foo.bar.example.org/ttaf1/extension">
- <span class="strong"><ttp:extension value="<span class="diff-chg">use</span>">#<span class="diff-chg">prefilter-by-language</span></ttp:extension></span>
+ <ttp:extensions xml:base="http://foo.bar.example.org/ttaf1/extension">
+ <span class="strong"><ttp:extension value="use">#prefilter-by-language</ttp:extension></span>
</ttp:extensions>
</ttp:profile>
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the DFXP transformation profile is used as
the baseline profile. This baseline profile is then supersetted by
-specifying that support<span class="diff-add"> and use</span> is
-required for<span class="diff-del"> two extensions, where the first
-extension is a experimental extension
-<code>#x-prefilter-by-language</code> defined (hypothetically) by the
-W3C in the TT Extension Namespace, and where the second extension
-is</span> a private extension defined in a third party
-namespace.<span class="diff-del">The <code>base</code> attribute is elided
-from the first specified <code>ttp:extensions</code> element since it
-makes use of the TT Extension Namespace. Note that the explicit
-specification of <code>required</code> on the <code>value</code>
-attributes on the two <code>ttp:extension</code> elements is not
-necessary, since it is the default value of this
-attribute.</span></p><p>The effect of this example is to express authorial intentions that
+specifying that support and use is required for a private extension
+defined in a third party namespace.</p><p>The effect of this example is to express authorial intentions that
a recipient processor must support the DFXP transformation profile and
-must also support<span class="diff-add"> and use</span> <span class="diff-del"> two additional extensions, one (hypothetically) defined by
-the W3C (in another specification or in a future version of this
-specification) and the other</span><span class="diff-add">an extension
-</span>defined by a third party.</p></div></div></div><div class="div2">
+must also support and use an extension defined by a third party.</p></div></div></div><div class="div2">
<h3><a name="parameter-attribute-vocabulary" id="parameter-attribute-vocabulary"/>6.2 Parameter Attribute Vocabulary</h3><p>The following attributes are defined in the TT Parameter Namespace.</p><ul><li><p><a href="#parameter-attribute-cellResolution"><b>6.2.1 ttp:cellResolution</b></a></p></li><li><p><a href="#parameter-attribute-clockMode"><b>6.2.2 ttp:clockMode</b></a></p></li><li><p><a href="#parameter-attribute-frameRate"><b>6.2.3 ttp:frameRate</b></a></p></li><li><p><a href="#parameter-attribute-frameRateMultiplier"><b>6.2.4 ttp:frameRateMultiplier</b></a></p></li><li><p><a href="#parameter-attribute-markerMode"><b>6.2.5 ttp:markerMode</b></a></p></li><li><p><a href="#parameter-attribute-pixelAspectRatio"><b>6.2.6 ttp:pixelAspectRatio</b></a></p></li><li><p><a href="#parameter-attribute-profile"><b>6.2.7 ttp:profile</b></a></p></li><li><p><a href="#parameter-attribute-smpteMode"><b>6.2.8 ttp:smpteMode</b></a></p></li><li><p><a href="#parameter-attribute-subFrameRate"><b>6.2.9 ttp:subFrameRate</b></a></p></li><li><p><a href="#parameter-attribute-tickRate"><b>6.2.10 ttp:tickRate</b></a></p></li><li><p><a href="#parameter-attribute-timeBase"><b>6.2.11 ttp:timeBase</b></a></p></li></ul><p>Unless explicitly stated otherwise, linear white-space (LWSP) may
appear between tokens of a value of a TT Parameter.</p><div class="div3">
<h4><a name="parameter-attribute-cellResolution" id="parameter-attribute-cellResolution"/>6.2.1 ttp:cellResolution</h4><p>The <code>ttp:cellResolution</code> attribute may be used by an author
@@ -1584,13 +1556,7 @@
profile designator in accordance with
<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p><p>A <code>ttp:profile</code>
attribute is considered to be significant only when specified on the
-<code>tt</code> element.</p><p class="diff-del">If a <code>ttp:profile</code> element appears as a
-descendant of the <code>tt</code> element, then the <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
-attribute should not be specified on the <code>tt</code> element. If both
-a <code>ttp:profile</code> element and a <code>ttp:profile</code>
-attribute are present (in a given document instance), then the
-<code>ttp:profile</code> attribute must be ignored for the purpose of
-determining the declared profile requirements.</p></div><div class="div3">
+<code>tt</code> element.</p></div><div class="div3">
<h4><a name="parameter-attribute-smpteMode" id="parameter-attribute-smpteMode"/>6.2.8 ttp:smpteMode</h4><p>The <code>ttp:smpteMode</code> attribute is used to specify
constraints on the interpretation and use of frame counts
that correspond with <a href="#smpte12m">[SMPTE 12M]</a> time coordinates when operating
@@ -1782,7 +1748,7 @@
<a href="#content-attribute-id">xml:id</a> = ID
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
- <span class="diff-add">{<em>any attribute not in default or any TT namespace</em>}</span>>
+ {<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Parameters.class</a>*, <a href="#styling-vocabulary-styling">styling</a>?, <a href="#layout-vocabulary-layout">layout</a>?
</head>
</pre></div>
@@ -1811,9 +1777,7 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Metadata namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Metadata Extension namespace</em>}</span>
{<em>any attribute in TT Style namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Style Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Animation.class</a>*, <a href="#content-vocabulary-div">div</a>*
</body>
@@ -1872,9 +1836,7 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Metadata namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Metadata Extension namespace</em>}</span>
{<em>any attribute in TT Style namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Style Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Animation.class</a>*, <a href="#element-vocab-group-table">Block.class</a>*
</div>
@@ -1914,9 +1876,7 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Metadata namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Metadata Extension namespace</em>}</span>
{<em>any attribute in TT Style namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Style Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Animation.class</a>*, <a href="#element-vocab-group-table">Inline.class</a>*
</p>
@@ -1958,9 +1918,7 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Metadata namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Metadata Extension namespace</em>}</span>
{<em>any attribute in TT Style namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Style Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Animation.class</a>*, <a href="#element-vocab-group-table">Inline.class</a>*
</span>
@@ -1981,9 +1939,7 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Metadata namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Metadata Extension namespace</em>}</span>
{<em>any attribute in TT Style namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Style Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Animation.class</a>*
</br>
@@ -2057,7 +2013,6 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Style namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Style Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*
</style>
@@ -2331,17 +2286,17 @@
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute is <code>none</code>, then no
dynamic flow semantics apply.</p><p>If the value of this attribute is <code>rollUp</code>, then
this value is interpreted as a shorthand value equivalent to
-<code>out(line,smooth) <span class="diff-chg">clear</span>(0.433s)</code>.</p><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>The choice of a definite duration of 0.433 seconds for the clear
+<code>out(line,smooth) clear(0.433s)</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The choice of a definite duration of 0.433 seconds for the clear
interval for roll up dynamic flow timing is based upon recommendations
specified in <a href="#ccreq">[CC-DECODER-REQ]</a>, p. 792.
-</p></div></div><p>If the value of this attribute contains a single <a href="#style-value-flowFunction"><flowFunction></a>, then that
+</p></div><p>If the value of this attribute contains a single <a href="#style-value-flowFunction"><flowFunction></a>, then that
flow function applies equally to <em>fill into</em> and <em>clear
-from</em> dynamic flow operations.</p><p>If either <code><span class="diff-chg">fill</span>()</code> or
-<code><span class="diff-chg">clear</span>()</code> <a href="#style-value-flowIntervalFunction"><flowIntervalFunction></a>
+from</em> dynamic flow operations.</p><p>If either <code>fill()</code> or
+<code>clear()</code> <a href="#style-value-flowIntervalFunction"><flowIntervalFunction></a>
is not specified, then the <code>auto</code> value for the missing
<a href="#style-value-flowIntervalFunction"><flowIntervalFunction></a>
-applies. <span class="diff-add">Multiple instances of the same <a href="#style-value-flowIntervalFunction"><flowIntervalFunction></a>
-must not appear in the value of this attribute.</span></p><p>The normative processing model for dynamic flow behavior is
+applies. Multiple instances of the same <a href="#style-value-flowIntervalFunction"><flowIntervalFunction></a>
+must not appear in the value of this attribute.</p><p>The normative processing model for dynamic flow behavior is
specified in <a href="#dynamicFlowModel"><b>B Dynamic Flow Processing Model</b></a>.</p><p>If a specified value of this attribute is not supported,
then a presentation processor must interpret the attribute as if the
value <code>none</code> were specified.</p><p>The <code>tts:dynamicFlow</code> style is illustrated by the
@@ -2354,7 +2309,7 @@
<style tts:fontFamily="proportionalSansSerif"/>
<style tts:fontSize="18px"/>
<style <span class="strong">tts:overflow="dynamic"</span>/>
- <style <span class="strong">tts:dynamicFlow="in(word,jump) <span class="diff-add">fill(1.0s) </span>out(line,smooth) <span class="diff-chg">clear</span>(0.3s)"</span>/>
+ <style <span class="strong">tts:dynamicFlow="in(word,jump) fill(1.0s) out(line,smooth) clear(0.3s)"</span>/>
</region>
...
<p region="r1">
@@ -2729,8 +2684,8 @@
must be performed as if the region's width and height were
unconstrained,
but with
-a well-defined origin. If the value is <code>hidden</code><span class="diff-add"> or
-<code>dynamic</code></span>, then content should
+a well-defined origin. If the value is <code>hidden</code> or
+<code>dynamic</code>, then content should
be clipped outside of the affected region.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Unless a manual line break element <code>br</code> is used by the content author,
a paragraph of a given region will generate no more than one line area in that
region if the value of the <code>tts:overflow</code> style that applies to the
@@ -3366,9 +3321,7 @@
flowUnit
: "glyph"
- <span class="diff-del">| "inline"</span>
| "line"
- <span class="diff-del">| "block"</span>
| "character"
| "word"
| extensionToken
@@ -3385,7 +3338,7 @@
into its region and flowing it out of its region. These two phases of dynamic flow are specified using the
<code>in()</code> and <code>out()</code> flow functions respectively.</p><p>Dynamic flow occurs on the basis of specific visual or semantic
content units. In the case of
-<span class="diff-chg"><code>glyph</code> and <code>line</code></span>,
+<code>glyph</code> and <code>line</code>,
the unit of dynamic flow is based upon a visually rendered construct
(<code>glyph</code>) or upon an area of the area
tree produced by formatting the affected content. In the case of
@@ -3416,8 +3369,8 @@
duration that affects dynamic flow timing behavior.</p><table summary="HTML Table" id="flowIntervalFunction-style-expression-syntax" class="syntax"><caption>Syntax Representation – <flowIntervalFunction></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<flowIntervalFunction>
- : "<span class="diff-chg">fill</span>(" flowIntervalArguments ")"
- | "<span class="diff-chg">clear</span>(" flowIntervalArguments ")"
+ : "fill(" flowIntervalArguments ")"
+ | "clear(" flowIntervalArguments ")"
flowIntervalArguments
: "auto"
@@ -3427,12 +3380,12 @@
flowIntervalRate
: <a href="#style-value-digit"><digit></a>+ ( "." <a href="#style-value-digit"><digit></a>+ )?
</pre></div>
-</td></tr></tbody></table><p>The <code><span class="diff-chg">fill</span>()</code> flow interval function is used to
+</td></tr></tbody></table><p>The <code>fill()</code> flow interval function is used to
determine the <em>computed fill interval</em> state parameter for performing
dynamic flow processing, which expresses the
duration of time between fill
timer events, as specified by <a href="#flowTimerFill"><b>B.5.1 Fill Timer</b></a>, which
-in turn, limits the dynamic flowed content fill rate.</p><p>The <code><span class="diff-chg">clear</span>()</code> flow interval function is used to
+in turn, limits the dynamic flowed content fill rate.</p><p>The <code>clear()</code> flow interval function is used to
determine the <em>computed clear interval</em> state parameter for performing
dynamic flow processing, which expresses the
duration of time between clear
@@ -3444,8 +3397,8 @@
specified as an argument to a flow interval function, then it is
considered to represent a <em>definite rate</em> in units per
second, where the applicable unit is determined in the context of
-whether the rate is used with an <code><span class="diff-chg">fill</span>()</code> or
-<code><span class="diff-chg">clear</span>()</code> flow interval function.</p><p>The computed fill and clear interval values are defined by
+whether the rate is used with an <code>fill()</code> or
+<code>clear()</code> flow interval function.</p><p>The computed fill and clear interval values are defined by
<a href="#dynamicFlowIntervalTimingCalculation"><b>B.3 Flow Interval Timing Calculation</b></a>.</p></div><div class="div3">
<h4><a name="style-value-genericFamilyName" id="style-value-genericFamilyName"/>8.3.8 <genericFamilyName></h4><p>A <genericFamilyName> expression specifies a font family using a general
token that indicates a class of font families.</p><p>The resolution of a generic family name to a concrete font instance is considered to
@@ -3589,10 +3542,10 @@
specified style set of each content and
layout element.</p><p>Style matter may be associated with content
and layout matter in a number of ways:</p><ul><li><p><a href="#semantics-style-association-inline">inline styling</a></p></li><li><p><a href="#semantics-style-association-referential">referential styling</a></p></li><li><p><a href="#semantics-style-association-chained-referential">chained referential styling</a></p></li></ul><p>In addition to the above, style matter may be associated with layout matter using:</p><ul><li><p><a href="#semantics-style-association-nested">nested styling</a></p></li></ul><div class="div4">
-<h5><a name="semantics-style-association-inline" id="semantics-style-association-inline"/>8.4.1.1 Inline Styling</h5><p>Style properties may be expressed in an inline manner by direct specification of an
-attribute from the TT Style Namespace<span class="diff-del"> or TT Style Extension Namespace</span>
-on the affected element. When expressed in this manner, the association of style information
-is referred to as <em>inline styling</em>.</p><p>Style properties associated by inline styling are afforded a higher priority than all other
+<h5><a name="semantics-style-association-inline" id="semantics-style-association-inline"/>8.4.1.1 Inline Styling</h5><p>Style properties may be expressed in an inline manner by direct
+specification of an attribute from the TT Style Namespace on the
+affected element. When expressed in this manner, the association of
+style information is referred to as <em>inline styling</em>.</p><p>Style properties associated by inline styling are afforded a higher priority than all other
forms of style association.</p><table summary="HTML Table" id="style-association-example-1" class="example"><caption>Example – Inline Styling</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<p <span class="strong">tts:color="white"</span>>White 1 <span <span class="strong">tts:color="yellow"</span>>Yellow</span> White 2</p>
@@ -3970,7 +3923,6 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Style namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Style Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#element-vocab-group-table">Animation.class</a>*, <a href="#styling-vocabulary-style">style</a>*
</region>
@@ -4016,7 +3968,7 @@
</p><div class="div3">
<h4><a name="semantics-default-region" id="semantics-default-region"/>9.3.1 Default Region</h4><p>If a DFXP document instance does not specify a
<a href="#layout-vocabulary-region"><code>region</code></a> element,
-then a <em>default region</em> is implied with the following characteristics:</p><ul><li><p>the <span class="diff-chg">identity</span> of the default region is consider<span class="diff-add">ed</span> to be anonymous;</p></li><li><p>the extent of the default region is the same as the root container
+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 anonymous;</p></li><li><p>the extent of the default region is the same as the root container
region;</p></li><li><p>the temporal interval of the default region is the same as temporal
interval of the document instance;</p></li></ul><p>Furthermore, if no <a href="#layout-vocabulary-region"><code>region</code></a> element was
specified, then the <a href="#layout-attribute-region"><code>region</code></a> attribute must
@@ -4066,12 +4018,12 @@
then the element is associated with the region referenced by that
attribute;</p></li><li><p>if some ancestor of that element specifies a <a href="#layout-attribute-region"><code>region</code></a> attribute,
then the element is associated with the region referenced by the most
-immediate ancestor that specifies this attribute;</p></li><li><p class="diff-add"> if the element contains a descendant element that
+immediate ancestor that specifies this attribute;</p></li><li><p> if the element contains a descendant element that
specifies a <a href="#layout-attribute-region"><code>region</code></a> attribute,
then the element is associated with the region referenced by that
attribute;</p></li><li><p>if a default region was implied (due to the absence of any
<a href="#layout-vocabulary-region"><code>region</code></a> element),
-then the element is associated with the default region<span class="diff-add">;</span></p></li><li><p>the element is not associated with any region<span class="diff-add">.</span></p></li></ol><p>The pseudo-code shown in <a href="#content-hierarchy-region-mapping"><b>Example – Content Hierarchy Region Mapping</b></a>
+then the element is associated with the default region;</p></li><li><p>the element is not associated with any region.</p></li></ol><p>The pseudo-code shown in <a href="#content-hierarchy-region-mapping"><b>Example – Content Hierarchy Region Mapping</b></a>
provides one possible algorithm that implements these processing steps.</p><table summary="HTML Table" id="content-hierarchy-region-mapping" class="example"><caption>Example – Content Hierarchy Region Mapping</caption><tbody><tr><td>
<div class="exampleInner"><pre>
PREPARE-CONTENT ( D ) :=
@@ -4416,7 +4368,7 @@
</td></tr></tbody></table></div></div><div class="div2">
<h3><a name="semantics-line-layout" id="semantics-line-layout"/>9.4 Line Layout</h3><p>The semantics of line layout, including line breaking, defined by
<a href="#xsl11">[XSL 1.1]</a> apply to the performance of the composition and layout of
-lines for presentation processing of a document instance on a visual medium.</p><p class="diff-add">If a profile that applies to a document instance
+lines for presentation processing of a document instance on a visual medium.</p><p>If a profile that applies to a document instance
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/unicode/reports/tr14/#Algorithm">Line
@@ -4591,7 +4543,7 @@
<a href="#content-attribute-id">xml:id</a> = ID
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
- {<em>a single attribute in TT Style<span class="diff-del"> or TT Style Extension</span> namespace</em>}
+ {<em>a single attribute in TT Style namespace</em>}
{<em>any attribute not in default or any TT namespace</em>}>
<em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*
</set>
@@ -4672,14 +4624,15 @@
<a href="#content-attribute-lang">xml:lang</a> = string
<a href="#content-attribute-space">xml:space</a> = (<em>default</em>|<em>preserve</em>)
{<em>any attribute in TT Metadata namespace</em>}
- <span class="diff-del">{<em>any attribute in TT Metadata Extension namespace</em>}</span>
{<em>any attribute not in default or any TT namespace</em>}>
- <em>Content:</em> <span class="diff-chg">({<em>any element in TT Metadata namespace</em>}|{<em>any element not in any TT namespace</em>})*</span>
+ <em>Content:</em> ({<em>any element in TT Metadata namespace</em>}|{<em>any element not in any TT namespace</em>})*
</metadata>
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The meaning of a specific metadata item must be evaluated in the
context of where it appears. The core vocabulary catalog permits an
-arbitrary number of <code>metadata</code> element children of any <span class="diff-chg">content</span> element type except for the <span class="diff-chg"><code>tt</code></span> element. See specific element
+arbitrary number of <code>metadata</code> element children of any
+content element type except for the
+<code>tt</code> element. See specific element
vocabulary definitions for any constraints that apply to such
usage.</p></div><p>The use of document metadata is illustrated by the following example.</p><table summary="HTML Table" id="metadata-vocabulary-metadata-example-1" class="example"><caption>Example Fragment – Document Metadata</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -4939,13 +4892,13 @@
the <em>clear unit</em> parameter;</p></li><li><p><em>reflow style</em>, which is set to the same value as
the <em>clear style</em> parameter;</p></li><li><p><em>clear unit</em>, as specified by the <code>flowUnit</code> argument
of the <code>out()</code> flow function;</p></li><li><p><em>clear style</em>, as specified by the <code>flowStyle</code> argument
-of the <code>out()</code> flow function;</p></li><li><p><em>fill interval</em>, as specified by the <code><span class="diff-chg">fill</span>()</code>
-flow interval function;</p></li><li><p><em>clear interval</em>, as specified by the <code><span class="diff-chg">clear</span>()</code>
+of the <code>out()</code> flow function;</p></li><li><p><em>fill interval</em>, as specified by the <code>fill()</code>
+flow interval function;</p></li><li><p><em>clear interval</em>, as specified by the <code>clear()</code>
flow interval function;</p></li><li><p><em>computed fill interval</em>, as determined by the flow
interval timing calculation below;</p></li><li><p><em>computed clear interval</em>, as determined by the flow
-interval timing calculation below;</p></li><li><p class="diff-add"><em>last fill time</em>, the time at which the last fill operation
-occurred;</p></li><li><p class="diff-add"><em>last clear time</em>, the time at which the last clear operation
-occurred;</p></li><li><p class="diff-add"><em>dynamic flow lock</em>, a synchronization primitive;</p></li></ol></li></ol><p>Except for the computed fill and clear
+interval timing calculation below;</p></li><li><p><em>last fill time</em>, the time at which the last fill operation
+occurred;</p></li><li><p><em>last clear time</em>, the time at which the last clear operation
+occurred;</p></li><li><p><em>dynamic flow lock</em>, a synchronization primitive;</p></li></ol></li></ol><p>Except for the computed fill and clear
interval parameters,
and unless the
<code>tts:dynamicFlow</code> property is animated,
@@ -4986,9 +4939,8 @@
the logical content positions
that correspond with the most logically prior
and subsequent content presently visible in the region;</p></li></ol></li><li><p>If any one of the conditions 2a, 2b, and 2c applies, then do not
-change the flow buffer.</p></li><li><p>If condition 2d applies, then<span class="diff-del">
-instantaneously</span> replace
-<span class="diff-add">at time <code>T<sub>k+1</sub></code> </span>the affected
+change the flow buffer.</p></li><li><p>If condition 2d applies, then replace
+at time <code>T<sub>k+1</sub></code> the affected
content of the flow buffer with the new content (in part or in whole) that corresponds with
time <code>T<sub>k+1</sub></code> such that the
logical content position
@@ -5009,18 +4961,19 @@
flow state parameters for the region have changed since last performing
this procedure, then re-perform the process described in <a href="#dynamicFlowIntervalTimingCalculation"><b>B.3 Flow Interval Timing Calculation</b></a>, then reset both fill and
clear timers to their inactive state.</p></li><li><p>If using automatic flow interval timing, then re-perform the process
-described in <a href="#dynamicFlowIntervalTimingCalculation"><b>B.3 Flow Interval Timing Calculation</b></a>.</p></li><li><p>If the fill timer is not active, then <span class="diff-chg">reset the fill timer to the current value of the computed
-fill interval</span>.</p></li></ol></li></ol><p>In the procedure described above, the content of a flow
+described in <a href="#dynamicFlowIntervalTimingCalculation"><b>B.3 Flow Interval Timing Calculation</b></a>.</p></li><li><p>If the fill timer is not active, then
+reset the fill timer to the current value of the computed
+fill interval.</p></li></ol></li></ol><p>In the procedure described above, the content of a flow
buffer at time <code>T<sub>k</sub></code> is considered to be
significantly different from the content of the same flow buffer at
time <code>T<sub>k+1</sub></code> if the set of glyph areas that would
be produced by
-<span class="diff-del">formatting the content</span><span class="diff-add">performing synchronic flow processing on the intermediate
-synchronic document</span> at time
+performing synchronic flow processing on the intermediate
+synchronic document at time
<code>T<sub>k</sub></code> differs from the set of glyph areas that
would be produced by
-<span class="diff-del">formatting the content</span><span class="diff-add">performing synchronic flow processing on the intermediate
-synchronic document</span> at time
+performing synchronic flow processing on the intermediate
+synchronic document at time
<code>T<sub>k+1</sub></code> in any of the following ways:</p><ul><li><p>the number of glyph areas are different;</p></li><li><p>the (positionally) ordered sets of glyphs associated with the
two sets of glyph areas are different;</p></li><li><p>the positions assigned to the glyph images associated with the two
sets of glyph areas are different;</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Other potential, but insignificant differences (as far as flow
@@ -5079,11 +5032,12 @@
dynamically upon changes to style property, the
content of the flow buffer, or the presentation
region.</p><div class="div3">
-<h4><a name="flowIntervalFillTiming" id="flowIntervalFillTiming"/>B.3.1 Computed Fill Timing Interval</h4><p>The computed fill timing interval<span class="diff-add"> from time <code>T<sub>k</sub></code> up to but not
-including <code>T<sub>k+1</sub></code></span> is determined as
-follows<span class="diff-add">, where the meaning of
+<h4><a name="flowIntervalFillTiming" id="flowIntervalFillTiming"/>B.3.1 Computed Fill Timing Interval</h4><p>The computed fill timing interval
+from time <code>T<sub>k</sub></code> up to but not
+including <code>T<sub>k+1</sub></code> is determined as
+follows, where the meaning of
<code>T<sub>k</sub></code> and <code>T<sub>k+1</sub></code> is as
-described above</span>:</p><ol class="enumar"><li><p>If the value of the <em>fill interval</em> parameter is a
+described above:</p><ol class="enumar"><li><p>If the value of the <em>fill interval</em> parameter is a
definite duration, then use this duration as the computed fill
interval;</p></li><li><p>otherwise, if the value of the <em>fill interval</em> parameter is a
definite rate, then the computed fill interval is equal to the
@@ -5092,17 +5046,18 @@
<code>auto</code>, then the computed fill interval is equal to the
difference between the time coordinate associated with the most
temporally prior beginning point of an active duration of some content
-unit present in the flow buffer<span class="diff-add"> at time
-<code>T<sub>k</sub></code></span> and the most temporally subsequent
+unit present in the flow buffer at time
+<code>T<sub>k</sub></code> and the most temporally subsequent
ending point of an active duration of some content unit present in the
-flow buffer<span class="diff-add"> at time
-<code>T<sub>k</sub></code></span> divided by the number of fill
-units currently available in the flow buffer<span class="diff-add"> at
-time <code>T<sub>k</sub></code></span>.</p></li></ol></div><div class="div3">
-<h4><a name="flowIntervalClearTiming" id="flowIntervalClearTiming"/>B.3.2 Computed Clear Timing Interval</h4><p>The computed clear timing interval<span class="diff-add"> from time
+flow buffer at time
+<code>T<sub>k</sub></code> divided by the number of fill
+units currently available in the flow buffer at
+time <code>T<sub>k</sub></code>.</p></li></ol></div><div class="div3">
+<h4><a name="flowIntervalClearTiming" id="flowIntervalClearTiming"/>B.3.2 Computed Clear Timing Interval</h4><p>The computed clear timing interval from time
<code>T<sub>k</sub></code> up to but not including
-<code>T<sub>k+1</sub></code></span> is determined as follows<span class="diff-add">, where the meaning of <code>T<sub>k</sub></code> and
-<code>T<sub>k+1</sub></code> is as described above</span>:</p><ol class="enumar"><li><p>If the value of the <em>clear interval</em> parameter is a
+<code>T<sub>k+1</sub></code> is determined as follows,
+where the meaning of <code>T<sub>k</sub></code> and
+<code>T<sub>k+1</sub></code> is as described above:</p><ol class="enumar"><li><p>If the value of the <em>clear interval</em> parameter is a
definite duration, then use this duration as the computed clear
interval;</p></li><li><p>otherwise, if the value of the <em>clear interval</em>
parameter is a definite rate, then the computed clear interval is
@@ -5110,12 +5065,13 @@
<code>auto</code>, then the computed clear interval is equal to the
difference between the time coordinate associated with the most
temporally prior beginning point of an active duration of some content
-unit present in the presentation region<span class="diff-add"> at time
-<code>T<sub>k</sub></code></span> and the most temporally subsequent
+unit present in the presentation region at time
+<code>T<sub>k</sub></code> and the most temporally subsequent
ending point of an active duration of some content unit present in the
-presentation region<span class="diff-add"> at time
-<code>T<sub>k</sub></code></span> divided by the number of clear
-units currently available in the presentation region<span class="diff-add"> at time <code>T<sub>k</sub></code></span>.</p></li></ol></div></div><div class="div2">
+presentation region at time
+<code>T<sub>k</sub></code> divided by the number of clear
+units currently available in the presentation region
+at time <code>T<sub>k</sub></code>.</p></li></ol></div></div><div class="div2">
<h3><a name="dynamicFlowOperations" id="dynamicFlowOperations"/>B.4 Flow Operations</h3><p>Flow operations perform the filling, reflowing, and clearing of
formatted content into, within, and from
a presentation region undergoing dynamic
@@ -5130,11 +5086,10 @@
and to its corresponding formatted content. In the context of the
presentation region, fill, reflow, and clear operations operate on
formatted content units
-(<span class="diff-chg">glyph and line areas</span>);
+(glyph and line areas);
however, in the context of the flow buffer, fill, reflow, and clear
operations operate on logical content units
-(character information items<span class="diff-del"> and element information
-items – <code>fo:inline</code> and <code>fo:block</code></span>).
+(character information items).
Because logical content units and formatted content units are
deterministically related to one another, an operation upon logical
units can always be described in terms of operations on formatted
@@ -5145,19 +5100,19 @@
with multiple logical content units. For example, a single character
information item may correspond to multiple glyph areas; likewise, a
single glyph area may correspond to multiple character information
-items.</p></div><p class="diff-add">For the purpose of performing line breaking in the
+items.</p></div><p>For the purpose of performing line breaking in the
context of dynamic flow processing, fill, reflow, and clear flow unit
boundaries must be interpreted as potential legal line break opportunity
regardless of other constraints.</p><p>When effecting the result of a flow operation on a
presentation region, the direction of (apparent)
translation of formatted content is determined by the nature of the
affected formatted content element. If the affected formatted content
-unit is a glyph<span class="diff-del"> or inline</span> area,
+unit is a glyph area,
then it is translated in the inline
progression direction that applies to the nearest immediate ancestor
inline or block area, and it is translated in a direction towards the
start edge of this ancestor area. If the affected formatted content
-unit is a line<span class="diff-del"> or block area</span>,
+unit is a line,
then it is translated in the block
progression direction that applies to the nearest immediate ancestor
block, and it is translated in a direction towards the before edge of
@@ -5166,19 +5121,19 @@
belong to the affected formatted content follows the direction of
translation of the formatted content units as determined above.</p><div class="div3">
<h4><a name="flowOperationFill" id="flowOperationFill"/>B.4.1 Fill Operation</h4><p>A <em>fill operation</em> causes the following ordered steps
-to be performed:</p><ol class="enumar"><li><p class="diff-add">reset the <em>last fill time</em> to the
+to be performed:</p><ol class="enumar"><li><p>reset the <em>last fill time</em> to the
current value of the flow timers timeline;</p></li><li><p>remove sufficient logical content from the beginning of the
<em>flow buffer</em> to constitute (or compose) a <em>fill
unit</em>;</p></li><li><p>format the content removed from the <em>flow buffer</em>
in the previous step in order to create a sequence of glyph areas or a
-sequence of <span class="diff-del">(full or partial measure) </span>line
+sequence of line
areas each containing a sequence of glyph areas;</p></li><li><p>append the sequence of areas produced in the previous step to
the sequence of areas currently associated with the presentation
region, where new glyph areas are appended to the current line area
and new line areas are appended to the sequence of line
areas;</p></li><li><p>cause the newly appended areas to be made visible according
-to the <em>fill style</em> state parameter in force<span class="diff-chg">;</span></p></li><li><p class="diff-add">if the clear timer is not active, then reset the
-clear timer to the current value of the <em>computed clear interval</em>;</p></li><li><p class="diff-add">reset the fill timer to the
+to the <em>fill style</em> state parameter in force;</p></li><li><p>if the clear timer is not active, then reset the
+clear timer to the current value of the <em>computed clear interval</em>;</p></li><li><p>reset the fill timer to the
current value of the <em>computed fill interval</em>.</p></li></ol><div class="note"><p class="prefix"><b>Note:</b></p><p>In certain cases, it may be necessary to retain logical content
removed from the flow buffer in an intermediate, holding buffer. This
will be the case when the smallest logical content unit of a flow
@@ -5188,8 +5143,8 @@
<code>glyph</code>, then such a character needs to be retained (in
such a holding buffer) until all generated glyphs are consumed.</p></div></div><div class="div3">
<h4><a name="flowOperationReflow" id="flowOperationReflow"/>B.4.2 Reflow Operation</h4><p>A <em>reflow operation</em> causes the following ordered steps
-to be performed:</p><ol class="enumar"><li><p>translate <span class="diff-chg">glyph areas or
-line areas</span> that correspond with a <em>reflow
+to be performed:</p><ol class="enumar"><li><p>translate glyph areas or
+line areas that correspond with a <em>reflow
unit</em> of formatted content that follows (in inline or block
progression dimension order) the space cleared by the immediately
preceding <em>clear operation</em> to a new position such that the
@@ -5198,25 +5153,26 @@
and where the translation adheres to the <em>reflow style</em>
state parameter in force.</p></li></ol><div class="note"><p class="prefix"><b>Note:</b></p><p>If a reflow unit is based on logical content units, then "reflow
unit of formatted content" refers to the logical content that
-generates the <span class="diff-chg">glyph and line areas</span> of
+generates the glyph and line areas of
formatted content that are being translated within the presentation
region. In contrast, if a reflow unit is based on formatted content
units, then "reflow unit of formatted content" refers directly to the
-generated <span class="diff-chg">glyph and line areas</span> of
+generated glyph and line areas of
formatted content.</p></div></div><div class="div3">
<h4><a name="flowOperationClear" id="flowOperationClear"/>B.4.3 Clear Operation</h4><p>A <em>clear operation</em> causes the following ordered steps
-to be performed:</p><ol class="enumar"><li><p class="diff-add">reset the <em>last clear time</em> to the
-current value of the flow timers timeline;</p></li><li><p>remove <span class="diff-chg">glyph areas or
-line areas</span> that correspond with a <em>clear unit</em> of
+to be performed:</p><ol class="enumar"><li><p>reset the <em>last clear time</em> to the
+current value of the flow timers timeline;</p></li><li><p>remove glyph areas or
+line areas that correspond with a <em>clear unit</em> of
formatted content from the starting edge or the before edge of the
presentation region in inline or block progression direction,
respectively, applying the <em>clear style</em> state parameter in
force.</p></li></ol><div class="note"><p class="prefix"><b>Note:</b></p><p>If a clear unit is based on logical content units, then "clear unit
of formatted content" refers to the logical content that generates the
-<span class="diff-chg">glyph and line areas</span> of formatted content
+glyph and line areas of formatted content
that are being cleared from the presentation region. In contrast, if a
clear unit is based on formatted content units, then "clear unit of
-formatted content" refers directly to the generated <span class="diff-chg">glyph and line areas</span> of formatted content.</p></div></div><div class="diff-add">
+formatted content" refers directly to the generated
+glyph and line areas of formatted content.</p></div></div><div class="div3">
<h4><a name="flowOperationCombined" id="flowOperationCombined"/>B.4.4 Combined Flow Operation</h4><p>A combined flow operation causes the following ordered steps to be performed:</p><ol class="enumar"><li><p>if the presentation region contains sufficient formatted
content to compose a <em>clear unit</em>, then perform the
processing described in <a href="#flowOperationClear"><b>B.4.3 Clear Operation</b></a>;</p></li><li><p>if (1) the space created by the above clear operation is
@@ -5245,9 +5201,9 @@
operations or clear, reflow, and flow operations are performed
simultaneously if the (logically, but not necesesarily temporally)
prior operation would create sufficient space in the presentation
-region to accept the subsequent unit of formatted content.</p></div><p class="diff-add">When resetting a flow timer, the <em>dynamic flow
+region to accept the subsequent unit of formatted content.</p></div><p>When resetting a flow timer, the <em>dynamic flow
lock</em> must first be acquired prior to changing the flow timer's
-value, and must be released immediately after making the change.</p><div class="diff-chg">
+value, and must be released immediately after making the change.</p><div class="div3">
<h4><a name="flowTimerFill" id="flowTimerFill"/>B.5.1 Fill Timer</h4><p>The fill timer is used to pace the addition of formatted content to the
presentation region undergoing dynamic flow processing.</p><p>Each time the fill timer expires, the following ordered steps are
performed:</p><ol class="enumar"><li><p>acquire <em>dynamic flow lock</em>;</p></li><li><p>if the difference between the current value of the flow
@@ -5264,7 +5220,7 @@
timers timeline and the <em>last fill time</em> is less than
the current value of the computed fill interval), reset the fill timer
to the difference between the current value of the computed fill interval
-and the current value of the flow timers timeline;</p></li><li><p>release <em>dynamic flow lock</em>.</p></li></ol></div><div class="diff-chg">
+and the current value of the flow timers timeline;</p></li><li><p>release <em>dynamic flow lock</em>.</p></li></ol></div><div class="div3">
<h4><a name="flowTimerClear" id="flowTimerClear"/>B.5.2 Clear Timer</h4><p>The clear timer is used to pace the removal of formatted content from the
presentation region undergoing dynamic flow processing.</p><p>Each time the clear timer expires, the following ordered steps are
performed:</p><ol class="enumar"><li><p>acquire <em>dynamic flow lock</em>;</p></li><li><p>if the difference between the current value of the flow
@@ -7581,19 +7537,8 @@
attribute.</p><p>A TT AF presentation processor supports the
<code>#dynamicFlow</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
-attribute.</p></div><div class="diff-del">
-<h4><a name="feature-dynamicFlow-block" id="feature-dynamicFlow-block"/>E.1.19 #dynamicFlow-block</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-block</code> feature if it recognizes and
-is capable of transforming the flow unit <code>block</code> as
-defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
-<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
-<code>#dynamicFlow-block</code> feature if it implements
-presentation semantic support for the flow unit <code>block</code> as
-defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
-<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-character" id="feature-dynamicFlow-character"/>E.1.20 #dynamicFlow-character</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-character" id="feature-dynamicFlow-character"/>E.1.19 #dynamicFlow-character</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-character</code> feature if it recognizes and
is capable of transforming the flow unit <code>character</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7604,29 +7549,29 @@
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-clear" id="feature-dynamicFlow-clear"/>E.1.21 #dynamicFlow-<span class="diff-chg">clear</span></h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-<span class="diff-chg">clear</span></code> feature if it recognizes and
-is capable of transforming the flow interval function <code><span class="diff-chg">clear</span>(..)</code> as
+<h4><a name="feature-dynamicFlow-clear" id="feature-dynamicFlow-clear"/>E.1.20 #dynamicFlow-clear</h4><p>A TT AF transformation processor supports the
+<code>#dynamicFlow-clear</code> feature if it recognizes and
+is capable of transforming the flow interval function <code>clear(..)</code> as
defined by <a href="#style-value-flowIntervalFunction"><b>8.3.7 <flowIntervalFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p><p>A TT AF presentation processor supports the
-<code>#dynamicFlow-<span class="diff-chg">clear</span></code> feature if it implements
-presentation semantic support for the flow interval function <code><span class="diff-chg">clear</span>(..)</code> as
+<code>#dynamicFlow-clear</code> feature if it implements
+presentation semantic support for the flow interval function <code>clear(..)</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-fill" id="feature-dynamicFlow-fill"/>E.1.22 #dynamicFlow-<span class="diff-chg">fill</span></h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-<span class="diff-chg">fill</span></code> feature if it recognizes and
-is capable of transforming the flow interval function <code><span class="diff-chg">fill</span>(..)</code> as
+<h4><a name="feature-dynamicFlow-fill" id="feature-dynamicFlow-fill"/>E.1.21 #dynamicFlow-fill</h4><p>A TT AF transformation processor supports the
+<code>#dynamicFlow-fill</code> feature if it recognizes and
+is capable of transforming the flow interval function <code>fill(..)</code> as
defined by <a href="#style-value-flowIntervalFunction"><b>8.3.7 <flowIntervalFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p><p>A TT AF presentation processor supports the
-<code>#dynamicFlow-<span class="diff-chg">fill</span></code> feature if it implements
-presentation semantic support for the flow interval function <code><span class="diff-chg">fill</span>(..)</code> as
+<code>#dynamicFlow-fill</code> feature if it implements
+presentation semantic support for the flow interval function <code>fill(..)</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-glyph" id="feature-dynamicFlow-glyph"/>E.1.23 #dynamicFlow-glyph</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-glyph" id="feature-dynamicFlow-glyph"/>E.1.22 #dynamicFlow-glyph</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-glyph</code> feature if it recognizes and
is capable of transforming the flow unit <code>glyph</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7637,7 +7582,7 @@
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-in" id="feature-dynamicFlow-in"/>E.1.24 #dynamicFlow-in</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-in" id="feature-dynamicFlow-in"/>E.1.23 #dynamicFlow-in</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-in</code> feature if it recognizes and
is capable of transforming the flow function <code>in(..)</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7647,19 +7592,8 @@
presentation semantic support for the flow function <code>in(..)</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
-attribute.</p></div><div class="diff-del">
-<h4><a name="feature-dynamicFlow-inline" id="feature-dynamicFlow-inline"/>E.1.25 #dynamicFlow-inline</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-inline</code> feature if it recognizes and
-is capable of transforming the flow unit <code>inline</code> as
-defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
-<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
-attribute.</p><p>A TT AF presentation processor supports the
-<code>#dynamicFlow-inline</code> feature if it implements
-presentation semantic support for the flow unit <code>inline</code> as
-defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
-<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-jump" id="feature-dynamicFlow-jump"/>E.1.26 #dynamicFlow-jump</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-jump" id="feature-dynamicFlow-jump"/>E.1.24 #dynamicFlow-jump</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-jump</code> feature if it recognizes and
is capable of transforming the flow style <code>jump</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7670,7 +7604,7 @@
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-line" id="feature-dynamicFlow-line"/>E.1.27 #dynamicFlow-line</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-line" id="feature-dynamicFlow-line"/>E.1.25 #dynamicFlow-line</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-line</code> feature if it recognizes and
is capable of transforming the flow unit <code>line</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7681,7 +7615,7 @@
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-out" id="feature-dynamicFlow-out"/>E.1.28 #dynamicFlow-out</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-out" id="feature-dynamicFlow-out"/>E.1.26 #dynamicFlow-out</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-out</code> feature if it recognizes and
is capable of transforming the flow function <code>out(..)</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7692,14 +7626,14 @@
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-rollUp" id="feature-dynamicFlow-rollUp"/>E.1.29 #dynamicFlow-rollUp</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-rollUp" id="feature-dynamicFlow-rollUp"/>E.1.27 #dynamicFlow-rollUp</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-rollUp</code> feature if it recognizes and is
capable of transforming the <code>rollUp</code> value of the <a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#dynamicFlow-rollUp</code> feature if it implements presentation semantic
support for the <code>rollUp</code> of the <a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-smooth" id="feature-dynamicFlow-smooth"/>E.1.30 #dynamicFlow-smooth</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-smooth" id="feature-dynamicFlow-smooth"/>E.1.28 #dynamicFlow-smooth</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-smooth</code> feature if it recognizes and
is capable of transforming the flow style <code>smooth</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7710,7 +7644,7 @@
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-teletext" id="feature-dynamicFlow-teletext"/>E.1.31 #dynamicFlow-teletext</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-teletext" id="feature-dynamicFlow-teletext"/>E.1.29 #dynamicFlow-teletext</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-teletext</code> feature if it recognizes and
is capable of transforming any well-defined value of the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
@@ -7721,7 +7655,7 @@
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute that is equivalent to <code>in(glyph,jump)
out(line,jump)</code>.</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-word" id="feature-dynamicFlow-word"/>E.1.32 #dynamicFlow-word</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-word" id="feature-dynamicFlow-word"/>E.1.30 #dynamicFlow-word</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-word</code> feature if it recognizes and
is capable of transforming the flow unit <code>word</code> as
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
@@ -7732,21 +7666,21 @@
defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-extent" id="feature-extent"/>E.1.33 #extent</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-extent" id="feature-extent"/>E.1.31 #extent</h4><p>A TT AF transformation processor supports the
<code>#extent</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-extent"><code>tts:extent</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#extent</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-extent"><code>tts:extent</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontFamily" id="feature-fontFamily"/>E.1.34 #fontFamily</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily" id="feature-fontFamily"/>E.1.32 #fontFamily</h4><p>A TT AF transformation processor supports the
<code>#fontFamily</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#fontFamily</code> feature if it implements presentation semantic support
for the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontFamily-generic" id="feature-fontFamily-generic"/>E.1.35 #fontFamily-generic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily-generic" id="feature-fontFamily-generic"/>E.1.33 #fontFamily-generic</h4><p>A TT AF transformation processor supports the
<code>#fontFamily-generic</code> feature if it recognizes and is
capable of transforming <a href="#style-value-genericFamilyName"><genericFamilyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
@@ -7755,7 +7689,7 @@
support for <a href="#style-value-genericFamilyName"><genericFamilyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontFamily-non-generic" id="feature-fontFamily-non-generic"/>E.1.36 #fontFamily-non-generic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily-non-generic" id="feature-fontFamily-non-generic"/>E.1.34 #fontFamily-non-generic</h4><p>A TT AF transformation processor supports the
<code>#fontFamily-non-generic</code> feature if it recognizes and is
capable of transforming <a href="#style-value-familyName"><familyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
@@ -7764,97 +7698,97 @@
support for <a href="#style-value-familyName"><familyName></a>
values when used with the <a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontSize" id="feature-fontSize"/>E.1.37 #fontSize</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize" id="feature-fontSize"/>E.1.35 #fontSize</h4><p>A TT AF transformation processor supports the
<code>#fontSize</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#fontSize</code> feature if it implements presentation semantic support
for the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontSize-anisomorphic" id="feature-fontSize-anisomorphic"/>E.1.38 #fontSize-anisomorphic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize-anisomorphic" id="feature-fontSize-anisomorphic"/>E.1.36 #fontSize-anisomorphic</h4><p>A TT AF transformation processor supports the
<code>#fontSize-anisomorphic</code> feature if it recognizes and is
capable of transforming values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute that consist of two <a href="#style-value-length"><length></a> specifications.</p><p>A TT AF presentation processor supports the
<code>#fontSize-anisomorphic</code> feature if it implements presentation semantic
support for defined values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute that consist of two <a href="#style-value-length"><length></a> specifications.</p></div><div class="div3">
-<h4><a name="feature-fontSize-isomorphic" id="feature-fontSize-isomorphic"/>E.1.39 #fontSize-isomorphic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize-isomorphic" id="feature-fontSize-isomorphic"/>E.1.37 #fontSize-isomorphic</h4><p>A TT AF transformation processor supports the
<code>#fontSize-isomorphic</code> feature if it recognizes and is
capable of transforming values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute that consist of a single <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the
<code>#fontSize-isomorphic</code> feature if it implements presentation semantic
support for defined values of the <a href="#style-attribute-fontSize"><code>tts:fontSize</code></a>
attribute that consist of a single <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-fontStyle" id="feature-fontStyle"/>E.1.40 #fontStyle</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle" id="feature-fontStyle"/>E.1.38 #fontStyle</h4><p>A TT AF transformation processor supports the
<code>#fontStyle</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#fontStyle</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontStyle-italic" id="feature-fontStyle-italic"/>E.1.41 #fontStyle-italic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle-italic" id="feature-fontStyle-italic"/>E.1.39 #fontStyle-italic</h4><p>A TT AF transformation processor supports the
<code>#fontStyle-italic</code> feature if it recognizes and is
capable of transforming the <code>italic</code> value of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#fontStyle-italic</code> feature if it implements presentation semantic
support for the <code>italic</code> of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontWeight" id="feature-fontWeight"/>E.1.42 #fontWeight</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontWeight" id="feature-fontWeight"/>E.1.40 #fontWeight</h4><p>A TT AF transformation processor supports the
<code>#fontWeight</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#fontWeight</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-fontWeight-bold" id="feature-fontWeight-bold"/>E.1.43 #fontWeight-bold</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontWeight-bold" id="feature-fontWeight-bold"/>E.1.41 #fontWeight-bold</h4><p>A TT AF transformation processor supports the
<code>#fontWeight-bold</code> feature if it recognizes and is
capable of transforming <code>bold</code> value of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#fontWeight-bold</code> feature if it implements presentation semantic
support for the <code>bold</code> of the <a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-frameRate" id="feature-frameRate"/>E.1.44 #frameRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-frameRate" id="feature-frameRate"/>E.1.42 #frameRate</h4><p>A TT AF transformation processor supports the
<code>#frameRate</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#frameRate</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-frameRateMultiplier" id="feature-frameRateMultiplier"/>E.1.45 #frameRateMultiplier</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-frameRateMultiplier" id="feature-frameRateMultiplier"/>E.1.43 #frameRateMultiplier</h4><p>A TT AF transformation processor supports the
<code>#frameRateMultiplier</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#frameRateMultiplier</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-layout" id="feature-layout"/>E.1.46 #layout</h4><p>A TT AF transformation processor supports the <code>#layout</code>
+<h4><a name="feature-layout" id="feature-layout"/>E.1.44 #layout</h4><p>A TT AF transformation processor supports the <code>#layout</code>
feature if it (1) recognizes and is capable of transforming the following
vocabulary defined by <a href="#layout"><b>9 Layout</b></a>:</p><ul><li><p><a href="#layout-vocabulary-layout"><code>layout</code></a></p></li><li><p><a href="#layout-vocabulary-region"><code>region</code></a></p></li><li><p><a href="#layout-attribute-region">@<code>region</code></a></p></li></ul><p>and (2) supports the following attributes when applied to the
<a href="#layout-vocabulary-region"><code>region</code></a> element:</p><ul><li><p><a href="#style-attribute-extent"><code>tts:extent</code></a></p></li><li><p><a href="#style-attribute-origin"><code>tts:origin</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#layout</code>
feature if it implements presentation semantic support for the
same vocabulary and features enumerated above.</p></div><div class="div3">
-<h4><a name="feature-length" id="feature-length"/>E.1.47 #length</h4><p>A TT AF transformation processor supports the <code>#length</code>
+<h4><a name="feature-length" id="feature-length"/>E.1.45 #length</h4><p>A TT AF transformation processor supports the <code>#length</code>
feature if it recognizes and is capable of transforming all defined
values of the <a href="#style-value-length"><length></a>
style value expression.</p><p>A TT AF presentation processor supports the <code>#length</code>
feature if it implements presentation semantic support for all defined values of
the <a href="#style-value-length"><length></a> style value
expression.</p></div><div class="div3">
-<h4><a name="feature-length-cell" id="feature-length-cell"/>E.1.48 #length-cell</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-cell" id="feature-length-cell"/>E.1.46 #length-cell</h4><p>A TT AF transformation processor supports the
<code>#length-cell</code> feature if it recognizes and is capable of
transforming scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>c</code> (cell) units.</p><p>A TT AF presentation processor supports the
<code>#length-cell</code> feature if it implements presentation semantic support
for scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>c</code> (cell) units.</p></div><div class="div3">
-<h4><a name="feature-length-em" id="feature-length-em"/>E.1.49 #length-em</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-em" id="feature-length-em"/>E.1.47 #length-em</h4><p>A TT AF transformation processor supports the
<code>#length-em</code> feature if it recognizes and is capable of
transforming scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>em</code> (EM) units.</p><p>A TT AF presentation processor supports the
<code>#length-em</code> feature if it implements presentation semantic support
for scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>em</code> (EM) units.</p></div><div class="div3">
-<h4><a name="feature-length-integer" id="feature-length-integer"/>E.1.50 #length-integer</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-integer" id="feature-length-integer"/>E.1.48 #length-integer</h4><p>A TT AF transformation processor supports the
<code>#length-integer</code> feature if it recognizes and is
capable of transforming integer values of the <a href="#style-value-length"><length></a> style value
expression.</p><p>A TT AF presentation processor supports the
@@ -7862,7 +7796,7 @@
support for integer values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-negative" id="feature-length-negative"/>E.1.51 #length-negative</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-negative" id="feature-length-negative"/>E.1.49 #length-negative</h4><p>A TT AF transformation processor supports the
<code>#length-negative</code> feature if it recognizes and is
capable of transforming negative values of the <a href="#style-value-length"><length></a> style value
expression.</p><p>A TT AF presentation processor supports the
@@ -7870,7 +7804,7 @@
support for negative values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-percentage" id="feature-length-percentage"/>E.1.52 #length-percentage</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-percentage" id="feature-length-percentage"/>E.1.50 #length-percentage</h4><p>A TT AF transformation processor supports the
<code>#length-percentage</code> feature if it recognizes and is
capable of transforming percentage values of the <a href="#style-value-length"><length></a> style value
expression.</p><p>A TT AF presentation processor supports the
@@ -7878,14 +7812,14 @@
support for percentage values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-pixel" id="feature-length-pixel"/>E.1.53 #length-pixel</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-pixel" id="feature-length-pixel"/>E.1.51 #length-pixel</h4><p>A TT AF transformation processor supports the
<code>#length-pixel</code> feature if it recognizes and is capable of
transforming scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>px</code> (pixel) units.</p><p>A TT AF presentation processor supports the
<code>#length-pixel</code> feature if it implements presentation semantic support
for scalar values of the <a href="#style-value-length"><length></a> style value expression
that use <code>px</code> (pixel) units.</p></div><div class="div3">
-<h4><a name="feature-length-positive" id="feature-length-positive"/>E.1.54 #length-positive</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-positive" id="feature-length-positive"/>E.1.52 #length-positive</h4><p>A TT AF transformation processor supports the
<code>#length-positive</code> feature if it recognizes and is
capable of transforming positive values of the <a href="#style-value-length"><length></a> style value
expression.</p><p>A TT AF presentation processor supports the
@@ -7893,35 +7827,35 @@
support for positive values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-length-real" id="feature-length-real"/>E.1.55 #length-real</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-real" id="feature-length-real"/>E.1.53 #length-real</h4><p>A TT AF transformation processor supports the
<code>#length-real</code> feature if it recognizes and is
capable of transforming real values of the <a href="#style-value-length"><length></a> style value
expression.</p><p>A TT AF presentation processor supports the
<code>#length-real</code> feature if it implements presentation semantic
support for real values of the <a href="#style-value-length"><length></a> style value
expression.
-</p></div><div class="diff-add">
-<h4><a name="feature-lineBreak-uax14" id="feature-lineBreak-uax14"/>E.1.56 #lineBreak-uax14</h4><p>A TT AF transformation processor supports the
+</p></div><div class="div3">
+<h4><a name="feature-lineBreak-uax14" id="feature-lineBreak-uax14"/>E.1.54 #lineBreak-uax14</h4><p>A TT AF transformation processor supports the
<code>#lineBreak-uax14</code> feature if it recognizes and is capable of
transforming requirements expressed by <a href="#uax14">[UAX14]</a> into its
target document space.</p><p>A TT AF presentation processor supports the
<code>#lineBreak-uax14</code> feature if it implements presentation semantic support
for <a href="#uax14">[UAX14]</a> as applies to line breaking.</p></div><div class="div3">
-<h4><a name="feature-lineHeight" id="feature-lineHeight"/>E.1.57 #lineHeight</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-lineHeight" id="feature-lineHeight"/>E.1.55 #lineHeight</h4><p>A TT AF transformation processor supports the
<code>#lineHeight</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#lineHeight</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-markerMode" id="feature-markerMode"/>E.1.58 #markerMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-markerMode" id="feature-markerMode"/>E.1.56 #markerMode</h4><p>A TT AF transformation processor supports the
<code>#markerMode</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#markerMode</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-metadata" id="feature-metadata"/>E.1.59 #metadata</h4><p>A TT AF transformation processor supports the <code>#metadata</code>
+<h4><a name="feature-metadata" id="feature-metadata"/>E.1.57 #metadata</h4><p>A TT AF transformation processor supports the <code>#metadata</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <a href="#metadata"><b>12 Metadata</b></a>:</p><ul><li><p><a href="#metadata-vocabulary-metadata"><code>metadata</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:title</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:desc</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:copyright</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:agent</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:name</code></a></p></li><li><p><a href="#metadata-vocabulary-title"><code>ttm:actor</code></a></p></li><li><p><a href="#metadata-attribute-agent">@<code>ttm:agent</code></a></p></li><li><p><a href="#metadata-attribute-role">@<code>ttm:role</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#metadata</code>
feature if it recognizes and is capable of presenting the information
@@ -7929,17 +7863,17 @@
presentation of metadata information. The presentation or ability to
present metadata information is considered to be implementation
dependent.</p></div></div><div class="div3">
-<h4><a name="feature-nested-div" id="feature-nested-div"/>E.1.60 #nested-div</h4><p>A TT AF transformation processor supports the <code>#nested-div</code>
+<h4><a name="feature-nested-div" id="feature-nested-div"/>E.1.58 #nested-div</h4><p>A TT AF transformation processor supports the <code>#nested-div</code>
feature if it recognizes and is capable of transforming nested
<a href="#content-vocabulary-div"><code>div</code></a> elements.</p><p>A TT AF presentation processor supports the <code>#nested-div</code>
feature if it implements presentation semantic support for nested
<a href="#content-vocabulary-div"><code>div</code></a> elements.</p></div><div class="div3">
-<h4><a name="feature-nested-span" id="feature-nested-span"/>E.1.61 #nested-span</h4><p>A TT AF transformation processor supports the <code>#nested-span</code>
+<h4><a name="feature-nested-span" id="feature-nested-span"/>E.1.59 #nested-span</h4><p>A TT AF transformation processor supports the <code>#nested-span</code>
feature if it recognizes and is capable of transforming nested
<a href="#content-vocabulary-span"><code>span</code></a> elements.</p><p>A TT AF presentation processor supports the <code>#nested-span</code>
feature if it implements presentation semantic support for nested
<a href="#content-vocabulary-span"><code>span</code></a> elements.</p></div><div class="div3">
-<h4><a name="feature-opacity" id="feature-opacity"/>E.1.62 #opacity</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-opacity" id="feature-opacity"/>E.1.60 #opacity</h4><p>A TT AF transformation processor supports the
<code>#opacity</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-opacity"><code>tts:opacity</code></a>
attribute.</p><p>A TT AF presentation processor supports the
@@ -7947,77 +7881,77 @@
the <a href="#style-attribute-opacity"><code>tts:opacity</code></a>
attribute and (2) is capable of displaying or generating an output display
signal that distinguishes between at least eight (8) values of opacity.</p></div><div class="div3">
-<h4><a name="feature-origin" id="feature-origin"/>E.1.63 #origin</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-origin" id="feature-origin"/>E.1.61 #origin</h4><p>A TT AF transformation processor supports the
<code>#origin</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-origin"><code>tts:origin</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#origin</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-origin"><code>tts:origin</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-overflow" id="feature-overflow"/>E.1.64 #overflow</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-overflow" id="feature-overflow"/>E.1.62 #overflow</h4><p>A TT AF transformation processor supports the
<code>#overflow</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#overflow</code> feature if it implements presentation semantic support for
all defined values of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-overflow-dynamic" id="feature-overflow-dynamic"/>E.1.65 #overflow-dynamic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-overflow-dynamic" id="feature-overflow-dynamic"/>E.1.63 #overflow-dynamic</h4><p>A TT AF transformation processor supports the
<code>#overflow-dynamic</code> feature if it recognizes and is capable of
transforming the <code>dynamic</code> value of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#overflow-dynamic</code> feature if it implements presentation semantic support for
the <code>dynamic</code> value of the <a href="#style-attribute-overflow"><code>tts:overflow</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-padding" id="feature-padding"/>E.1.66 #padding</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding" id="feature-padding"/>E.1.64 #padding</h4><p>A TT AF transformation processor supports the
<code>#padding</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-padding"><code>tts:padding</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#padding</code> feature if it implements presentation semantic support for
the <a href="#style-attribute-padding"><code>tts:padding</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-padding-1" id="feature-padding-1"/>E.1.67 #padding-1</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-1" id="feature-padding-1"/>E.1.65 #padding-1</h4><p>A TT AF transformation processor supports the
<code>#padding-1</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of one <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-1</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of one <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-2" id="feature-padding-2"/>E.1.68 #padding-2</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-2" id="feature-padding-2"/>E.1.66 #padding-2</h4><p>A TT AF transformation processor supports the
<code>#padding-2</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of two <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-2</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of two <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-3" id="feature-padding-3"/>E.1.69 #padding-3</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-3" id="feature-padding-3"/>E.1.67 #padding-3</h4><p>A TT AF transformation processor supports the
<code>#padding-3</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of three <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-3</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of three <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-padding-4" id="feature-padding-4"/>E.1.70 #padding-4</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-4" id="feature-padding-4"/>E.1.68 #padding-4</h4><p>A TT AF transformation processor supports the
<code>#padding-4</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of four <a href="#style-value-length"><length></a> specification.</p><p>A TT AF presentation processor supports the <code>#padding-4</code>
feature if it implements presentation semantic support for values of the <a href="#style-attribute-padding"><code>tts:padding</code></a> attribute
that consist of four <a href="#style-value-length"><length></a> specification.</p></div><div class="div3">
-<h4><a name="feature-pixelAspectRatio" id="feature-pixelAspectRatio"/>E.1.71 #pixelAspectRatio</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-pixelAspectRatio" id="feature-pixelAspectRatio"/>E.1.69 #pixelAspectRatio</h4><p>A TT AF transformation processor supports the
<code>#pixelAspectRatio</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#pixelAspectRatio</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-presentation" id="feature-presentation"/>E.1.72 #presentation</h4><p class="diff-chg">A TT AF processor supports the
+<h4><a name="feature-presentation" id="feature-presentation"/>E.1.70 #presentation</h4><p>A TT AF processor supports the
<code>#presentation</code> feature if it
(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>9.3 Region Layout and Presentation</b></a> and
<a href="#semantics-line-layout"><b>9.4 Line Layout</b></a>, respectively, and
-(3) implements presentation semantics for the following features:</p><ul class="diff-add"><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#core"><code>#core</code></a></p></li><li><p><a href="#profile"><code>#profile</code></a></p></li><li><p><a href="#structure"><code>#structure</code></a></p></li><li><p><a href="#time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul><p class="diff-add">
+(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="#core"><code>#core</code></a></p></li><li><p><a href="#profile"><code>#profile</code></a></p></li><li><p><a href="#structure"><code>#structure</code></a></p></li><li><p><a href="#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 TT AF processor that supports the
<code>#presentation</code> feature should satisfy the user agent
accessibility guidelines specified by <a href="#uaag">[UAAG]</a>.</p></div><div class="div3">
-<h4><a name="feature-profile" id="feature-profile"/>E.1.73 #profile</h4><p>A TT AF transformation processor supports the <code>#profile</code>
+<h4><a name="feature-profile" id="feature-profile"/>E.1.71 #profile</h4><p>A TT AF transformation processor supports the <code>#profile</code>
feature if it recognizes and is capable of transforming the
<a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
attribute on the <a href="#document-structure-vocabulary-tt"><code>tt</code></a> element and
@@ -8025,79 +7959,79 @@
<a href="#parameter-element-vocabulary"><b>6.1 Parameter Element Vocabulary</b></a>:</p><ul><li><p><a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a></p></li><li><p><a href="#parameter-vocabulary-features"><code>ttp:features</code></a></p></li><li><p><a href="#parameter-vocabulary-feature"><code>ttp:feature</code></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><code>ttp:extensions</code></a></p></li><li><p><a href="#parameter-vocabulary-extension"><code>ttp:extension</code></a></p></li></ul><p>A TT AF presentation processor supports the
<code>#profile</code> feature if it implements presentation semantic support
for the same vocabulary specified above.</p></div><div class="div3">
-<h4><a name="feature-rollUp" id="feature-rollUp"/>E.1.74 #rollUp</h4><p>A TT AF processor supports the <code>#rollUp</code> feature if it
+<h4><a name="feature-rollUp" id="feature-rollUp"/>E.1.72 #rollUp</h4><p>A TT AF processor supports the <code>#rollUp</code> feature if it
supports the following features:</p><ul><li><p><a href="#layout"><code>#layout</code></a></p></li><li><p><a href="#feature-overflow-dynamic"><code>#overflow-dynamic</code></a></p></li><li><p><a href="#feature-dynamicFlow-rollUp"><code>#dynamicFlow-rollUp</code></a></p></li></ul></div><div class="div3">
-<h4><a name="feature-showBackground" id="feature-showBackground"/>E.1.75 #showBackground</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-showBackground" id="feature-showBackground"/>E.1.73 #showBackground</h4><p>A TT AF transformation processor supports the
<code>#showBackground</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-showBackground"><code>tts:showBackground</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#showBackground</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-showBackground"><code>tts:showBackground</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-smpteMode" id="feature-smpteMode"/>E.1.76 #smpteMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-smpteMode" id="feature-smpteMode"/>E.1.74 #smpteMode</h4><p>A TT AF transformation processor supports the
<code>#smpteMode</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-smpteMode"><code>ttp:smpteMode</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#smpteMode</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-smpteMode"><code>ttp:smpteMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-structure" id="feature-structure"/>E.1.77 #structure</h4><p>A TT AF transformation processor supports the <code>#structure</code>
+<h4><a name="feature-structure" id="feature-structure"/>E.1.75 #structure</h4><p>A TT AF transformation processor supports the <code>#structure</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <a href="#content"><b>7 Content</b></a>:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><code>tt</code></a></p></li><li><p><a href="#document-structure-vocabulary-head"><code>head</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#structure</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-styling" id="feature-styling"/>E.1.78 #styling</h4><p>A TT AF transformation processor supports the <code>#styling</code>
+<h4><a name="feature-styling" id="feature-styling"/>E.1.76 #styling</h4><p>A TT AF transformation processor supports the <code>#styling</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <a href="#styling"><b>8 Styling</b></a>:</p><ul><li><p><a href="#styling-vocabulary-styling"><code>styling</code></a></p></li><li><p><a href="#styling-vocabulary-style"><code>style</code></a></p></li><li><p><a href="#style-attribute-style">@<code>style</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#styling</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-styling-chained" id="feature-styling-chained"/>E.1.79 #styling-chained</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-chained" id="feature-styling-chained"/>E.1.77 #styling-chained</h4><p>A TT AF transformation processor supports the
<code>#styling-chained</code> feature if it recognizes and is capable
of transforming chained style association as defined by <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p><p>A TT AF presentation processor supports the
<code>#styling-chained</code> feature if it implements presentation semantic
support for chained style association as defined by <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inheritance-content" id="feature-styling-inheritance-content"/>E.1.80 #styling-inheritance-content</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-inheritance-content" id="feature-styling-inheritance-content"/>E.1.78 #styling-inheritance-content</h4><p>A TT AF transformation processor supports the
<code>#styling-inheritance</code> feature if it recognizes and is
capable of transforming content style inheritance as defined by
<a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p><p>A TT AF presentation processor supports the
<code>#styling-inheritance-content</code> feature if it implements
presentation semantic support for content style inheritance as defined by <a href="#semantics-style-inheritance-content"><b>8.4.2.1 Content Style Inheritance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inheritance-region" id="feature-styling-inheritance-region"/>E.1.81 #styling-inheritance-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-inheritance-region" id="feature-styling-inheritance-region"/>E.1.79 #styling-inheritance-region</h4><p>A TT AF transformation processor supports the
<code>#styling-inheritance</code> feature if it recognizes and is
capable of transforming region style inheritance as defined by
<a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p><p>A TT AF presentation processor supports the
<code>#styling-inheritance-region</code> feature if it implements
presentation semantic support for region style inheritance as defined by <a href="#semantics-style-inheritance-region"><b>8.4.2.2 Region Style Inheritance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-inline" id="feature-styling-inline"/>E.1.82 #styling-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-inline" id="feature-styling-inline"/>E.1.80 #styling-inline</h4><p>A TT AF transformation processor supports the
<code>#styling-inline</code> feature if it recognizes and is capable
of transforming inline style association as defined by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p><p>A TT AF presentation processor supports the
<code>#styling-inline</code> feature if it implements presentation semantic support
for inline style association as defined by <a href="#semantics-style-association-inline"><b>8.4.1.1 Inline Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-nested" id="feature-styling-nested"/>E.1.83 #styling-nested</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-nested" id="feature-styling-nested"/>E.1.81 #styling-nested</h4><p>A TT AF transformation processor supports the
<code>#styling-nested</code> feature if it recognizes and is capable
of transforming nested style association as defined by <a href="#semantics-style-association-nested"><b>8.4.1.4 Nested Styling</b></a>.</p><p>A TT AF presentation processor supports the
<code>#styling-nested</code> feature if it implements presentation semantic support
for nested style association as defined by <a href="#semantics-style-association-nested"><b>8.4.1.4 Nested Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-styling-referential" id="feature-styling-referential"/>E.1.84 #styling-referential</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-referential" id="feature-styling-referential"/>E.1.82 #styling-referential</h4><p>A TT AF transformation processor supports the
<code>#styling-referential</code> feature if it recognizes and is capable
of transforming referential style association as defined by <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a>.</p><p>A TT AF presentation processor supports the
<code>#styling-referential</code> feature if it implements presentation semantic
support for referential style association as defined by <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a>.</p></div><div class="div3">
-<h4><a name="feature-subFrameRate" id="feature-subFrameRate"/>E.1.85 #subFrameRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-subFrameRate" id="feature-subFrameRate"/>E.1.83 #subFrameRate</h4><p>A TT AF transformation processor supports the
<code>#subFrameRate</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#subFrameRate</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign" id="feature-textAlign"/>E.1.86 #textAlign</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign" id="feature-textAlign"/>E.1.84 #textAlign</h4><p>A TT AF transformation processor supports the
<code>#textAlign</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#textAlign</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign-absolute" id="feature-textAlign-absolute"/>E.1.87 #textAlign-absolute</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign-absolute" id="feature-textAlign-absolute"/>E.1.85 #textAlign-absolute</h4><p>A TT AF transformation processor supports the
<code>#textAlign-absolute</code> feature if it recognizes and is
capable of transforming the <code>left</code>, <code>center</code>,
and <code>right</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
@@ -8106,7 +8040,7 @@
support for the <code>left</code>, <code>center</code>, and
<code>right</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textAlign-relative" id="feature-textAlign-relative"/>E.1.88 #textAlign-relative</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign-relative" id="feature-textAlign-relative"/>E.1.86 #textAlign-relative</h4><p>A TT AF transformation processor supports the
<code>#textAlign-relative</code> feature if it recognizes and is
capable of transforming the <code>start</code>, <code>center</code>,
and <code>end</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
@@ -8115,14 +8049,14 @@
support for the <code>start</code>, <code>center</code>, and
<code>end</code> values of the <a href="#style-attribute-textAlign"><code>tts:textAlign</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration" id="feature-textDecoration"/>E.1.89 #textDecoration</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration" id="feature-textDecoration"/>E.1.87 #textDecoration</h4><p>A TT AF transformation processor supports the
<code>#textDecoration</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#textDecoration</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-over" id="feature-textDecoration-over"/>E.1.90 #textDecoration-over</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-over" id="feature-textDecoration-over"/>E.1.88 #textDecoration-over</h4><p>A TT AF transformation processor supports the
<code>#textDecoration-over</code> feature if it recognizes and is
capable of transforming the <code>overline</code> and
<code>noOverline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
@@ -8131,7 +8065,7 @@
presentation semantic support for the <code>overline</code> and
<code>noOverline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-through" id="feature-textDecoration-through"/>E.1.91 #textDecoration-through</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-through" id="feature-textDecoration-through"/>E.1.89 #textDecoration-through</h4><p>A TT AF transformation processor supports the
<code>#textDecoration-through</code> feature if it recognizes and is
capable of transforming the <code>lineThrough</code> and
<code>noLineThrough</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
@@ -8140,7 +8074,7 @@
presentation semantic support for the <code>lineThrough</code> and
<code>noLineThrough</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textDecoration-under" id="feature-textDecoration-under"/>E.1.92 #textDecoration-under</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-under" id="feature-textDecoration-under"/>E.1.90 #textDecoration-under</h4><p>A TT AF transformation processor supports the
<code>#textDecoration-under</code> feature if it recognizes and is
capable of transforming the <code>underline</code> and
<code>noUnderline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
@@ -8149,56 +8083,56 @@
presentation semantic support for the <code>underline</code> and
<code>noUnderline</code> values of the <a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textOutline" id="feature-textOutline"/>E.1.93 #textOutline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textOutline" id="feature-textOutline"/>E.1.91 #textOutline</h4><p>A TT AF transformation processor supports the
<code>#textOutline</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#textOutline</code> feature if it implements presentation semantic support
for the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-textOutline-blur" id="feature-textOutline-blur"/>E.1.94 #textOutline-blur</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textOutline-blur" id="feature-textOutline-blur"/>E.1.92 #textOutline-blur</h4><p>A TT AF transformation processor supports the
<code>#textOutline-blur</code> feature if it recognizes and is capable of
transforming values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
attribute that include a blur radius specification.</p><p>A TT AF presentation processor supports the
<code>#textOutline-blur</code> feature if it implements presentation semantic support
for values of the <a href="#style-attribute-textOutline"><code>tts:textOutline</code></a>
attribute that include a blur radius specification.</p></div><div class="div3">
-<h4><a name="feature-tickRate" id="feature-tickRate"/>E.1.95 #tickRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-tickRate" id="feature-tickRate"/>E.1.93 #tickRate</h4><p>A TT AF transformation processor supports the
<code>#tickRate</code> feature if it recognizes and is capable of
transforming the <a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#tickRate</code> feature if it implements presentation semantic support
for the <a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-timeBase-clock" id="feature-timeBase-clock"/>E.1.96 #timeBase-clock</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-clock" id="feature-timeBase-clock"/>E.1.94 #timeBase-clock</h4><p>A TT AF transformation processor supports the
<code>#timeBase-clock</code> feature if it recognizes and is capable
of transforming the <code>clock</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p><p>A TT AF presentation processor supports the
<code>#timeBase-clock</code> feature if it implements presentation
semantic support for the <code>clock</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute and if it supports the <a href="#feature-clockMode"><code>#clockMode</code></a> feature.</p></div><div class="div3">
-<h4><a name="feature-timeBase-media" id="feature-timeBase-media"/>E.1.97 #timeBase-media</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-media" id="feature-timeBase-media"/>E.1.95 #timeBase-media</h4><p>A TT AF transformation processor supports the
<code>#timeBase-media</code> feature if it recognizes and is capable
of transforming the <code>media</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#timeBase-media</code> feature if it implements presentation
semantic support for the <code>media</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-timeBase-smpte" id="feature-timeBase-smpte"/>E.1.98 #timeBase-smpte</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-smpte" id="feature-timeBase-smpte"/>E.1.96 #timeBase-smpte</h4><p>A TT AF transformation processor supports the
<code>#timeBase-smpte</code> feature if it recognizes and is capable
of transforming the <code>smpte</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute and if it supports the <a href="#feature-smpteMode"><code>#smpteMode</code></a> feature.</p><p>A TT AF presentation processor supports the
<code>#timeBase-smpte</code> feature if it implements presentation
semantic support for the <code>smpte</code> value of the <a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a>
attribute and if it supports the <a href="#feature-smpteMode"><code>#smpteMode</code></a> feature.</p></div><div class="div3">
-<h4><a name="feature-timeContainer" id="feature-timeContainer"/>E.1.99 #timeContainer</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeContainer" id="feature-timeContainer"/>E.1.97 #timeContainer</h4><p>A TT AF transformation processor supports the
<code>#timeContainer</code> feature if it recognizes and is capable of
transforming the <a href="#timing-attribute-timeContainer"><code>timeContainer</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#timeContainer</code> feature if it implements presentation semantic support
for the <a href="#timing-attribute-timeContainer"><code>timeContainer</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-time-clock" id="feature-time-clock"/>E.1.100 #time-clock</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-clock" id="feature-time-clock"/>E.1.98 #time-clock</h4><p>A TT AF transformation processor supports the
<code>#time-clock</code> feature if it recognizes and is capable of
transforming all values of the <a href="#timing-value-timeExpression"><timeExpression></a> that
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
@@ -8207,7 +8141,7 @@
</pre></div><p>A TT AF presentation processor supports the
<code>#time-clock</code> feature if it implements presentation
semantic support for the same syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-time-clock-with-frames" id="feature-time-clock-with-frames"/>E.1.101 #time-clock-with-frames</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-clock-with-frames" id="feature-time-clock-with-frames"/>E.1.99 #time-clock-with-frames</h4><p>A TT AF transformation processor supports the
<code>#time-clock-with-frames</code> feature if it supports the
<a href="#feature-frameRate"><code>#frameRate</code></a>,
<a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a>, and
@@ -8221,7 +8155,7 @@
<code>#time-clock-with-frames</code> feature if it implements
presentation semantic support for the same features and syntax
specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset" id="feature-time-offset"/>E.1.102 #time-offset</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-offset" id="feature-time-offset"/>E.1.100 #time-offset</h4><p>A TT AF transformation processor supports the
<code>#time-offset</code> feature if it recognizes and is capable of
transforming all values of the <a href="#timing-value-timeExpression"><timeExpression></a> that
satisfy the following subset of time expression syntax:</p><div class="exampleInner"><pre>
@@ -8230,7 +8164,7 @@
</pre></div><p>A TT AF presentation processor supports the
<code>#time-offset</code> feature if it implements presentation
semantic support for the same syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset-with-frames" id="feature-time-offset-with-frames"/>E.1.103 #time-offset-with-frames</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-offset-with-frames" id="feature-time-offset-with-frames"/>E.1.101 #time-offset-with-frames</h4><p>A TT AF transformation processor supports the
<code>#time-offset-with-frames</code> feature if it supports the
<a href="#feature-frameRate"><code>#frameRate</code></a>,
<a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a>, and
@@ -8244,7 +8178,7 @@
<code>#time-offset-with-frames</code> feature if it implements
presentation semantic support for the same features and syntax
specified above.</p></div><div class="div3">
-<h4><a name="feature-time-offset-with-ticks" id="feature-time-offset-with-ticks"/>E.1.104 #time-offset-with-ticks</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-offset-with-ticks" id="feature-time-offset-with-ticks"/>E.1.102 #time-offset-with-ticks</h4><p>A TT AF transformation processor supports the
<code>#time-offset-with-ticks</code> feature if it supports the
<a href="#feature-tickRate"><code>#tickRate</code></a> feature
and if it recognizes and is capable of
@@ -8255,31 +8189,31 @@
</pre></div><p>A TT AF presentation processor supports the
<code>#time-offset-with-ticks</code> feature if it implements presentation
semantic support for the same features and syntax specified above.</p></div><div class="div3">
-<h4><a name="feature-timing" id="feature-timing"/>E.1.105 #timing</h4><p>A TT AF transformation processor supports the <code>#timing</code>
+<h4><a name="feature-timing" id="feature-timing"/>E.1.103 #timing</h4><p>A TT AF transformation processor supports the <code>#timing</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <a href="#timing"><b>10 Timing</b></a>:</p><ul><li><p><a href="#timing-attribute-begin">@<code>begin</code></a></p></li><li><p><a href="#timing-attribute-dur">@<code>dur</code></a></p></li><li><p><a href="#timing-attribute-end">@<code>end</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#timing</code>
feature if it implements presentation semantic support for the
same vocabulary enumerated above.</p></div><div class="div3">
-<h4><a name="feature-transformation" id="feature-transformation"/>E.1.106 #transformation</h4><p class="diff-chg">A TT AF processor supports the
+<h4><a name="feature-transformation" id="feature-transformation"/>E.1.104 #transformation</h4><p>A TT AF processor supports the
<code>#transformation</code> feature if it
(1) satisfies the generic processor criteria defined by
-<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>,
-(2) implements transformation semantics for the following features:</p><ul class="diff-add"><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#core"><code>#core</code></a></p></li><li><p><a href="#profile"><code>#profile</code></a></p></li><li><p><a href="#structure"><code>#structure</code></a></p></li><li><p><a href="#time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul></div><div class="div3">
-<h4><a name="feature-unicodeBidi" id="feature-unicodeBidi"/>E.1.107 #unicodeBidi</h4><p>A TT AF transformation processor supports the
+<a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a> and
+(2) implements transformation semantics for the following features:</p><ul><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#core"><code>#core</code></a></p></li><li><p><a href="#profile"><code>#profile</code></a></p></li><li><p><a href="#structure"><code>#structure</code></a></p></li><li><p><a href="#time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul></div><div class="div3">
+<h4><a name="feature-unicodeBidi" id="feature-unicodeBidi"/>E.1.105 #unicodeBidi</h4><p>A TT AF transformation processor supports the
<code>#unicodeBidi</code> feature if it recognizes and is capable of
transforming all defined values of the <a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#unicodeBidi</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-visibility" id="feature-visibility"/>E.1.108 #visibility</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility" id="feature-visibility"/>E.1.106 #visibility</h4><p>A TT AF transformation processor supports the
<code>#visibility</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#visibility</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-visibility-block" id="feature-visibility-block"/>E.1.109 #visibility-block</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-block" id="feature-visibility-block"/>E.1.107 #visibility-block</h4><p>A TT AF transformation processor supports the
<code>#visibility-block</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that would generate a
@@ -8288,7 +8222,7 @@
support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that generates a
block area.</p></div><div class="div3">
-<h4><a name="feature-visibility-inline" id="feature-visibility-inline"/>E.1.110 #visibility-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-inline" id="feature-visibility-inline"/>E.1.108 #visibility-inline</h4><p>A TT AF transformation processor supports the
<code>#visibility-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that would generate an
@@ -8297,28 +8231,28 @@
support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a content element that generates an
inline area.</p></div><div class="div3">
-<h4><a name="feature-visibility-region" id="feature-visibility-region"/>E.1.111 #visibility-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-region" id="feature-visibility-region"/>E.1.109 #visibility-region</h4><p>A TT AF transformation processor supports the
<code>#visibility-region</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p><p>A TT AF presentation processor supports the
<code>#visibility-region</code> feature if it implements presentation semantic
support for all defined values of the <a href="#style-attribute-visibility"><code>tts:visibility</code></a>
attribute when applied to a <a href="#layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-wrapOption" id="feature-wrapOption"/>E.1.112 #wrapOption</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-wrapOption" id="feature-wrapOption"/>E.1.110 #wrapOption</h4><p>A TT AF transformation processor supports the
<code>#wrapOption</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#wrapOption</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode" id="feature-writingMode"/>E.1.113 #writingMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode" id="feature-writingMode"/>E.1.111 #writingMode</h4><p>A TT AF transformation processor supports the
<code>#writingMode</code> feature if it recognizes and is capable
of transforming all defined values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p><p>A TT AF presentation processor supports the
<code>#writingMode</code> feature if it implements presentation semantic support
for all defined values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-vertical" id="feature-writingMode-vertical"/>E.1.114 #writingMode-vertical</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-vertical" id="feature-writingMode-vertical"/>E.1.112 #writingMode-vertical</h4><p>A TT AF transformation processor supports the
<code>#writingMode-vertical</code> feature if it recognizes and is
capable of transforming the <code>tbrl</code>, <code>tblr</code>, and
<code>tb</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -8327,7 +8261,7 @@
support for the <code>tbrl</code>, <code>tblr</code>, and
<code>tb</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal" id="feature-writingMode-horizontal"/>E.1.115 #writingMode-horizontal</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-horizontal" id="feature-writingMode-horizontal"/>E.1.113 #writingMode-horizontal</h4><p>A TT AF transformation processor supports the
<code>#writingMode-horizontal</code> feature if it recognizes and is
capable of transforming the <code>lrtb</code>, <code>rltb</code>,
<code>lr</code> and <code>rl</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -8336,7 +8270,7 @@
support for the <code>lrtb</code>, <code>rltb</code>, <code>lr</code>
and <code>rl</code> values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal-lr" id="feature-writingMode-horizontal-lr"/>E.1.116 #writingMode-horizontal-lr</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-horizontal-lr" id="feature-writingMode-horizontal-lr"/>E.1.114 #writingMode-horizontal-lr</h4><p>A TT AF transformation processor supports the
<code>#writingMode-horizontal</code> feature if it recognizes and is
capable of transforming the <code>lrtb</code> and <code>lr</code>
values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -8345,7 +8279,7 @@
support for the <code>lrtb</code> and <code>lr</code> values of the
<a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-writingMode-horizontal-rl" id="feature-writingMode-horizontal-rl"/>E.1.117 #writingMode-horizontal-rl</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-horizontal-rl" id="feature-writingMode-horizontal-rl"/>E.1.115 #writingMode-horizontal-rl</h4><p>A TT AF transformation processor supports the
<code>#writingMode-horizontal</code> feature if it recognizes and is
capable of transforming the <code>rltb</code> and <code>rl</code>
values of the <a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
@@ -8354,7 +8288,7 @@
support for the <code>rltb</code> and <code>rl</code> values of the
<a href="#style-attribute-writingMode"><code>tts:writingMode</code></a>
attribute.</p></div><div class="div3">
-<h4><a name="feature-zIndex" id="feature-zIndex"/>E.1.118 #zIndex</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-zIndex" id="feature-zIndex"/>E.1.116 #zIndex</h4><p>A TT AF transformation processor supports the
<code>#zIndex</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-zIndex"><code>tts:zIndex</code></a>
attribute.</p><p>A TT AF presentation processor supports the
@@ -8365,38 +8299,14 @@
enumerates every defined feature designation (expressed without the TT
Feature Namespace), and, for each designated feature, specifies
whether the feature is mandatory (M) or optional (O) for
-transformation and presentation processors.</p><table summary="HTML Table" id="feature-support-table" class="common"><caption>Table E-1 – Feature Support</caption><col width="60%" span="1"/><col width="20%" span="1"/><col width="20%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Transformation</span></td><td><span class="strong">Presentation</span></td></tr><tr><td><a href="#feature-animation"><code>#animation</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor"><code>#backgroundColor</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-block"><code>#backgroundColor-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-inline"><code>#backgroundColor-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-region"><code>#backgroundColor-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-bidi"><code>#bidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-cellResolution"><code>#cellResolution</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode"><code>#clockMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-color"><code>#color</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td><span class="diff-chg">M</span></td><td>M</td></tr><tr><td><a href="#feature-core"><code>#core</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-direction"><code>#direction</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display"><code>#display</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-block"><code>#display-block</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-display-inline"><code>#display-inline</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-display-region"><code>#display-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-displayAlign"><code>#displayAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow"><code>#dynamicFlow</code></a></td><td>O</td><td>O</td></tr><tr><td><span class="diff-del"><a href="#feature-dynamicFlow-block"><code>#dynamicFlow-block</code></a></span></td><td><span class="diff-del">O</span></td><td><span class="diff-del">O</span></td></tr><tr><td><a href="#feature-dynamicFlow-character"><code>#dynamicFlow-character</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-clear"><code>#dynamicFlow-<span class="diff-chg">clear</span></code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-fill"><code>#dynamicFlow-<span class="diff-chg">fill</span></code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-glyph"><code>#dynamicFlow-glyph</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-in"><code>#dynamicFlow-in</code></a></td><td>O</td><td>O</td></tr><tr><td><span class="diff-del"><a href="#feature-dynamicFlow-inline"><code>#dynamicFlow-inline</code></a></span></td><td><span class="diff-del">O</span></td><td><span class="diff-del">O</span></td></tr><tr><td><a href="#feature-dynamicFlow-jump"><code>#dynamicFlow-jump</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-line"><code>#dynamicFlow-line</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-out"><code>#dynamicFlow-out</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-rollUp"><code>#dynamicFlow-rollUp</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-smooth"><code>#dynamicFlow-smooth</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-teletext"><code>#dynamicFlow-teletext</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-word"><code>#dynamicFlow-word</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent"><code>#extent</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-fontFamily"><code>#fontFamily</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-generic"><code>#fontFamily-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-non-generic"><code>#fontFamily-non-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize"><code>#fontSize</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-anisomorphic"><code>#fontSize-anisomorphic</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle"><code>#fontStyle</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-fontWeight"><code>#fontWeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-frameRate"><code>#frameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-layout"><code>#layout</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length"><code>#length</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-cell"><code>#length-cell</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-length-em"><code>#length-em</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-integer"><code>#length-integer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-negative"><code>#length-negative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-percentage"><code>#length-percentage</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-pixel"><code>#length-pixel</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-length-real"><code>#length-real</code></a></td><td>O</td><td>O</td></tr><tr><td><span class="diff-add"><a href="#feature-lineBreak-uax14"><code>#lineBreak-uax14</code></a></span></td><td><span class="diff-add">O</span></td><td><span class="diff-add">O</span></td></tr><tr><td><a href="#feature-lineHeight"><code>#lineHeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode"><code>#markerMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-metadata"><code>#metadata</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-div"><code>#nested-div</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-span"><code>#nested-span</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-opacity"><code>#opacity</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-origin"><code>#origin</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow"><code>#overflow</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow-dynamic"><code>#overflow-dynamic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding"><code>#padding</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-1"><code>#padding-1</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-2"><code>#padding-2</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-3"><code>#padding-3</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-4"><code>#padding-4</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-pixelAspectRatio"><code>#pixelAspectRatio</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td>O</td><td>M</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-rollUp"><code>#rollUp</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-showBackground"><code>#showBackground</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-smpteMode"><code>#smpteMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-styling"><code>#styling</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-chained"><code>#styling-chained</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-styling-inheritance-region"><code>#styling-inheritance-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inline"><code>#styling-inline</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-styling-nested"><code>#styling-nested</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-referential"><code>#styling-referential</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-subFrameRate"><code>#subFrameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign"><code>#textAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></a></td><td>O</td><td><span class="diff-chg">O</span></td></tr><tr><td><a href="#feature-textAlign-relative"><code>#textAlign-relative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration"><code>#textDecoration</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-over"><code>#textDecoration-over</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-through"><code>#textDecoration-through</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-under"><code>#textDecoration-under</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline"><code>#textOutline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-blur"><code>#textOutline-blur</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-tickRate"><code>#tickRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-clock"><code>#timeBase-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-media"><code>#timeBase-media</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-smpte"><code>#timeBase-smpte</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeContainer"><code>#timeContainer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock"><code>#time-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock-with-frames"><code>#time-clock-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset"><code>#time-offset</code></a></td><td><span class="diff-chg">M</span></td><td>M</td></tr><tr><td><a href="#feature-time-offset-with-frames"><code>#time-offset-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset-with-ticks"><code>#time-offset-with-ticks</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timing"><code>#timing</code></a></td><td><span class="diff-chg">M</span></td><td>M</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td>M</td><td>O</td></tr><tr><td><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility"><code>#visibility</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-block"><code>#visibility-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-region"><code>#visibility-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-wrapOption"><code>#wrapOption</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode"><code>#writingMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-vertical"><code>#writingMode-vertical</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-lr"><code>#writingMode-horizontal-lr</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-rl"><code>#writingMode-horizontal-rl</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-zIndex"><code>#zIndex</code></a></td><td>O</td><td>O</td></tr></tbody></table><p>For the sake of convenience, the following table,
+transformation and presentation processors.</p><table summary="HTML Table" id="feature-support-table" class="common"><caption>Table E-1 – Feature Support</caption><col width="60%" span="1"/><col width="20%" span="1"/><col width="20%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Transformation</span></td><td><span class="strong">Presentation</span></td></tr><tr><td><a href="#feature-animation"><code>#animation</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor"><code>#backgroundColor</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-block"><code>#backgroundColor-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-inline"><code>#backgroundColor-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-backgroundColor-region"><code>#backgroundColor-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-bidi"><code>#bidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-cellResolution"><code>#cellResolution</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-clockMode"><code>#clockMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-color"><code>#color</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-core"><code>#core</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-direction"><code>#direction</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display"><code>#display</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-block"><code>#display-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-inline"><code>#display-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-display-region"><code>#display-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-displayAlign"><code>#displayAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow"><code>#dynamicFlow</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-character"><code>#dynamicFlow-character</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-clear"><code>#dynamicFlow-clear</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-fill"><code>#dynamicFlow-fill</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-glyph"><code>#dynamicFlow-glyph</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-in"><code>#dynamicFlow-in</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-jump"><code>#dynamicFlow-jump</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-line"><code>#dynamicFlow-line</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-out"><code>#dynamicFlow-out</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-rollUp"><code>#dynamicFlow-rollUp</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-smooth"><code>#dynamicFlow-smooth</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-teletext"><code>#dynamicFlow-teletext</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-word"><code>#dynamicFlow-word</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-extent"><code>#extent</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily"><code>#fontFamily</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-generic"><code>#fontFamily-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontFamily-non-generic"><code>#fontFamily-non-generic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize"><code>#fontSize</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-anisomorphic"><code>#fontSize-anisomorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle"><code>#fontStyle</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight"><code>#fontWeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRate"><code>#frameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-frameRateMultiplier"><code>#frameRateMultiplier</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-layout"><code>#layout</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length"><code>#length</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-cell"><code>#length-cell</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-em"><code>#length-em</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-integer"><code>#length-integer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-negative"><code>#length-negative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-percentage"><code>#length-percentage</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-pixel"><code>#length-pixel</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-length-real"><code>#length-real</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineBreak-uax14"><code>#lineBreak-uax14</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-lineHeight"><code>#lineHeight</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-markerMode"><code>#markerMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-metadata"><code>#metadata</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-div"><code>#nested-div</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-nested-span"><code>#nested-span</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-opacity"><code>#opacity</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-origin"><code>#origin</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow"><code>#overflow</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-overflow-dynamic"><code>#overflow-dynamic</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding"><code>#padding</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-1"><code>#padding-1</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-2"><code>#padding-2</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-3"><code>#padding-3</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-padding-4"><code>#padding-4</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-pixelAspectRatio"><code>#pixelAspectRatio</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td>O</td><td>M</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-rollUp"><code>#rollUp</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-showBackground"><code>#showBackground</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-smpteMode"><code>#smpteMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-styling"><code>#styling</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-chained"><code>#styling-chained</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inheritance-region"><code>#styling-inheritance-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-inline"><code>#styling-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-nested"><code>#styling-nested</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-styling-referential"><code>#styling-referential</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-subFrameRate"><code>#subFrameRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign"><code>#textAlign</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textAlign-relative"><code>#textAlign-relative</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration"><code>#textDecoration</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-over"><code>#textDecoration-over</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-through"><code>#textDecoration-through</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textDecoration-under"><code>#textDecoration-under</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline"><code>#textOutline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-textOutline-blur"><code>#textOutline-blur</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-tickRate"><code>#tickRate</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-clock"><code>#timeBase-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-media"><code>#timeBase-media</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeBase-smpte"><code>#timeBase-smpte</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timeContainer"><code>#timeContainer</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock"><code>#time-clock</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-clock-with-frames"><code>#time-clock-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset"><code>#time-offset</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-time-offset-with-frames"><code>#time-offset-with-frames</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-time-offset-with-ticks"><code>#time-offset-with-ticks</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-timing"><code>#timing</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td>M</td><td>O</td></tr><tr><td><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility"><code>#visibility</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-block"><code>#visibility-block</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-visibility-region"><code>#visibility-region</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-wrapOption"><code>#wrapOption</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode"><code>#writingMode</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-vertical"><code>#writingMode-vertical</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-lr"><code>#writingMode-horizontal-lr</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-writingMode-horizontal-rl"><code>#writingMode-horizontal-rl</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-zIndex"><code>#zIndex</code></a></td><td>O</td><td>O</td></tr></tbody></table><p>For the sake of convenience, the following table,
<a href="#feature-transformation-mandatory-table"><b>Table E-2 – Mandatory Features - Transformation</b></a>, enumerates all
mandatory features for a TT AF Transformation Processor, providing additional
comments to summarize the context of usage or the nature of the feature.
The TT AF Profile Definition Document that defines the corresponding
DFXP Transformation Profile is specified in
<a href="#profile-dfxp-transformation"><b>G.1 DFXP Transformation Profile</b></a>.
-</p><table summary="HTML Table" id="feature-transformation-mandatory-table" class="common"><caption>Table E-2 – Mandatory Features - Transformation</caption><col width="60%" span="1"/><col width="40%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><span class="diff-add"><a href="#feature-content"><code>#content</code></a></span></td><td><span class="diff-add">
-<a href="#document-structure-vocabulary-body"><code>body</code></a>,
-<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="#content-vocabulary-br"><code>br</code></a></span>
-</td></tr><tr><td><a href="#feature-core"><code>#core</code></a></td><td>
-<a href="#content-attribute-id">@<code>xml:id</code></a>,
-<a href="#content-attribute-id">@<code>xml:lang</code></a>,
-<a href="#content-attribute-id">@<code>xml:space</code></a>
-</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td/></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>
-<a href="#document-structure-vocabulary-tt"><code>tt</code></a>,
-<a href="#document-structure-vocabulary-head"><code>head</code></a>
-</td></tr><tr><td><span class="diff-add"><a href="#feature-time-offset"><code>#time-offset</code></a></span></td><td/></tr><tr><td><span class="diff-add"><a href="#feature-timing"><code>#timing</code></a></span></td><td><span class="diff-add">
-<a href="#timing-attribute-begin">@<code>begin</code></a>,
-<a href="#timing-attribute-dur">@<code>dur</code></a>,
-<a href="#timing-attribute-end">@<code>end</code></a></span>
-</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td/></tr></tbody></table><p>For the sake of convenience, the following table,
-<a href="#feature-presentation-mandatory-table"><b>Table E-3 – Mandatory Features - Presentation</b></a>, enumerates all
-mandatory features for a TT AF Presentation Processor, providing additional
-comments to summarize the context of usage or the nature of the feature.
-The TT AF Profile Definition Document that defines the corresponding
-DFXP Presentation Profile is specified in
-<a href="#profile-dfxp-presentation"><b>G.2 DFXP Presentation Profile</b></a>.
-</p><table summary="HTML Table" id="feature-presentation-mandatory-table" class="common"><caption>Table E-3 – Mandatory Features - Presentation</caption><col width="60%" span="1"/><col width="40%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><span class="diff-del"><a href="#feature-color"><code>#color</code></a></span></td><td><span class="diff-del"><a href="#style-attribute-color">@<code>tts:color</code></a></span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
+</p><table summary="HTML Table" id="feature-transformation-mandatory-table" class="common"><caption>Table E-2 – Mandatory Features - Transformation</caption><col width="60%" span="1"/><col width="40%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
<a href="#document-structure-vocabulary-body"><code>body</code></a>,
<a href="#content-vocabulary-div"><code>div</code></a>,
<a href="#content-vocabulary-p"><code>p</code></a>,
@@ -8406,52 +8316,37 @@
<a href="#content-attribute-id">@<code>xml:id</code></a>,
<a href="#content-attribute-id">@<code>xml:lang</code></a>,
<a href="#content-attribute-id">@<code>xml:space</code></a>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-display-block"><code>#display-block</code></a></span></td><td><span class="diff-del"><a href="#style-attribute-display">@<code>tts:display</code></a>
-applied to
-<a href="#document-structure-vocabulary-body"><code>body</code></a>,
-<a href="#content-vocabulary-div"><code>div</code></a>,
-<a href="#content-vocabulary-p"><code>p</code></a></span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-display-inline"><code>#display-inline</code></a></span></td><td><span class="diff-del"><a href="#style-attribute-display">@<code>tts:display</code></a>
-applied to
-<a href="#content-vocabulary-span"><code>span</code></a>,
-<a href="#content-vocabulary-br"><code>br</code></a></span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-extent"><code>#extent</code></a></span></td><td><span class="diff-del"><a href="#style-attribute-extent">@<code>tts:extent</code></a>
-applied to <a href="#document-structure-vocabulary-tt"><code>tt</code></a></span></td></tr><tr><td><span class="diff-del"><a href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></a></span></td><td><span class="diff-del">
-<a href="#style-attribute-fontSize">@<code>tts:fontSize</code></a>=
-"<code><a href="#style-value-length"><length></a></code>"</span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></a></span></td><td><span class="diff-del">
-<a href="#style-attribute-fontStyle">@<code>tts:fontStyle</code></a>=
-"<code>italic</code>"</span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></a></span></td><td><span class="diff-del">
-<a href="#style-attribute-fontWeight">@<code>tts:fontWeight</code></a>=
-"<code>bold</code>"</span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-length-cell"><code>#length-cell</code></a></span></td><td><span class="diff-del">
-<code><a href="#style-value-length"><length></a></code> :
-<code><a href="#style-value-integer"><integer></a>c</code></span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-length-pixel"><code>#length-pixel</code></a></span></td><td><span class="diff-del">
-<code><a href="#style-value-length"><length></a></code> :
-<code><a href="#style-value-integer"><integer></a>px</code></span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-length-positive"><code>#length-positive</code></a></span></td><td><span class="diff-del">
-<code><a href="#style-value-length"><length></a></code>≥0</span>
-</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td/></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td/></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>
+</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td/></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>
<a href="#document-structure-vocabulary-tt"><code>tt</code></a>,
<a href="#document-structure-vocabulary-head"><code>head</code></a>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></a></span></td><td/></tr><tr><td><span class="diff-del"><a href="#feature-styling-inline"><code>#styling-inline</code></a></span></td><td/></tr><tr><td><span class="diff-del"><a href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></a></span></td><td><span class="diff-del">
-<a href="#style-attribute-textAlign">@<code>tts:textAlign</code></a>=
-"<code>left</code>|<code>center</code>|<code>right</code>"</span>
</td></tr><tr><td><a href="#feature-time-offset"><code>#time-offset</code></a></td><td/></tr><tr><td><a href="#feature-timing"><code>#timing</code></a></td><td>
<a href="#timing-attribute-begin">@<code>begin</code></a>,
<a href="#timing-attribute-dur">@<code>dur</code></a>,
<a href="#timing-attribute-end">@<code>end</code></a>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-visibility-block"><code>#visibility-block</code></a></span></td><td><span class="diff-del"><a href="#style-attribute-visibility">@<code>tts:visibility</code></a>
-applied to
+</td></tr><tr><td><a href="#feature-transformation"><code>#transformation</code></a></td><td/></tr></tbody></table><p>For the sake of convenience, the following table,
+<a href="#feature-presentation-mandatory-table"><b>Table E-3 – Mandatory Features - Presentation</b></a>, enumerates all
+mandatory features for a TT AF Presentation Processor, providing additional
+comments to summarize the context of usage or the nature of the feature.
+The TT AF Profile Definition Document that defines the corresponding
+DFXP Presentation Profile is specified in
+<a href="#profile-dfxp-presentation"><b>G.2 DFXP Presentation Profile</b></a>.
+</p><table summary="HTML Table" id="feature-presentation-mandatory-table" class="common"><caption>Table E-3 – Mandatory Features - Presentation</caption><col width="60%" span="1"/><col width="40%" span="1"/><tbody><tr><td><span class="strong">Feature</span></td><td><span class="strong">Comments</span></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
<a href="#document-structure-vocabulary-body"><code>body</code></a>,
<a href="#content-vocabulary-div"><code>div</code></a>,
-<a href="#content-vocabulary-p"><code>p</code></a></span>
-</td></tr><tr><td><span class="diff-del"><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></span></td><td><span class="diff-del"><a href="#style-attribute-visibility">@<code>tts:visibility</code></a>
-applied to
+<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#content-vocabulary-span"><code>span</code></a>,
-<a href="#content-vocabulary-br"><code>br</code></a></span>
+<a href="#content-vocabulary-br"><code>br</code></a>
+</td></tr><tr><td><a href="#feature-core"><code>#core</code></a></td><td>
+<a href="#content-attribute-id">@<code>xml:id</code></a>,
+<a href="#content-attribute-id">@<code>xml:lang</code></a>,
+<a href="#content-attribute-id">@<code>xml:space</code></a>
+</td></tr><tr><td><a href="#feature-profile"><code>#profile</code></a></td><td/></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td/></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>
+<a href="#document-structure-vocabulary-tt"><code>tt</code></a>,
+<a href="#document-structure-vocabulary-head"><code>head</code></a>
+</td></tr><tr><td><a href="#feature-time-offset"><code>#time-offset</code></a></td><td/></tr><tr><td><a href="#feature-timing"><code>#timing</code></a></td><td>
+<a href="#timing-attribute-begin">@<code>begin</code></a>,
+<a href="#timing-attribute-dur">@<code>dur</code></a>,
+<a href="#timing-attribute-end">@<code>end</code></a>
</td></tr></tbody></table></div></div><div class="div1">
<h2><a name="extensions" id="extensions"/>F Extensions</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the syntactic form of extension designations, which are
used to express authorial intent regarding the support for extension
@@ -8479,11 +8374,11 @@
capable of serving as a base URI used in combination with a
<code>designation</code> token that takes the form of a fragment
identifier.</p></div></div><div class="div1">
-<h2><a name="profiles" id="profiles"/>G Profiles</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following standard TT AF profiles:</p><ul><li><p><a href="#profile-dfxp-transformation"><b>G.1 DFXP Transformation Profile</b></a></p></li><li><p><a href="#profile-dfxp-presentation"><b>G.2 DFXP Presentation Profile</b></a></p></li><li><p class="diff-add"><a href="#profile-dfxp-full"><b>G.3 DFXP Full Profile</b></a></p></li></ul><p>Each TT AF profile is defined in terms of a TT AF Profile Definition Document,
+<h2><a name="profiles" id="profiles"/>G Profiles</h2><p><em>This appendix is normative.</em></p><p>This appendix specifies the following standard TT AF profiles:</p><ul><li><p><a href="#profile-dfxp-transformation"><b>G.1 DFXP Transformation Profile</b></a></p></li><li><p><a href="#profile-dfxp-presentation"><b>G.2 DFXP Presentation Profile</b></a></p></li><li><p><a href="#profile-dfxp-full"><b>G.3 DFXP Full Profile</b></a></p></li></ul><p>Each TT AF profile is defined in terms of a TT AF Profile Definition Document,
which is expressed as an XML document wherein the root element adheres to
<a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a>.</p><div class="div2">
-<h3><a name="profile-dfxp-transformation" id="profile-dfxp-transformation"/>G.1 DFXP Transformation Profile</h3><p class="diff-add">The DFXP Transformation Profile is intended to be used to
-express minimum compliance for transformation processing.</p><div class="exampleInner"><pre><span class="diff-chg"><?xml version="1.0" encoding="utf-8"?>
+<h3><a name="profile-dfxp-transformation" id="profile-dfxp-transformation"/>G.1 DFXP Transformation Profile</h3><p>The DFXP Transformation Profile is intended to be used to
+express minimum compliance for transformation processing.</p><div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8"?>
<!-- this file defines the "dfxp-transformation" profile of ttaf1 -->
<profile xmlns="http://www.w3.org/2006/10/ttaf1#parameter">
<features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
@@ -8610,10 +8505,10 @@
<!-- optional (voluntary) extension support -->
</extensions>
</profile>
-</span></pre></div></div><div class="div2">
-<h3><a name="profile-dfxp-presentation" id="profile-dfxp-presentation"/>G.2 DFXP Presentation Profile</h3><p class="diff-add">The DFXP Presentation Profile is intended to be used to
-express minimum compliance for presentation processing.</p><div class="exampleInner"><pre><span class="diff-chg"><?xml version="1.0" encoding="utf-8"?>
-<!-- this file defines the "presentation" profile of ttaf1-dfxp -->
+</pre></div></div><div class="div2">
+<h3><a name="profile-dfxp-presentation" id="profile-dfxp-presentation"/>G.2 DFXP Presentation Profile</h3><p>The DFXP Presentation Profile is intended to be used to
+express minimum compliance for presentation processing.</p><div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8"?>
+<!-- this file defines the "dfxp-presentation" profile of ttaf1-dfxp -->
<profile xmlns="http://www.w3.org/2006/10/ttaf1#parameter">
<features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
<!-- required (mandatory) feature support -->
@@ -8739,10 +8634,10 @@
<!-- optional (voluntary) extension support -->
</extensions>
</profile>
-</span></pre></div></div><div class="diff-add">
-<h3><a name="profile-dfxp-full" id="profile-dfxp-full"/>G.3 DFXP Full Profile</h3><p class="diff-add add">The DFXP Full Profile is intended to be used to
+</pre></div></div><div class="div2">
+<h3><a name="profile-dfxp-full" id="profile-dfxp-full"/>G.3 DFXP Full Profile</h3><p>The DFXP Full Profile is intended to be used to
express maximum compliance for both transformation and presentation processing.</p><div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8"?>
-<!-- this file defines the "full" profile of ttaf1-dfxp -->
+<!-- this file defines the "dfxp-full" profile of ttaf1-dfxp -->
<profile xmlns="http://www.w3.org/2006/10/ttaf1#parameter">
<features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
<!-- required (mandatory) feature support -->
@@ -8924,7 +8819,7 @@
<a href="http://www.w3.org/TR/2008/REC-xml-20081126/"><cite>Extensible Markup Language (XML)
1.0 (Fifth Edition)</cite></a>, W3C Recommendation, 26 November 2008. (See
<a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>.)
-</dd><dt class="labeldiff-add"><a name="xmlbase" id="xmlbase"/>XML Base</dt><dd class="diff-add">Jonathan Marsh and Richard Tobin, Eds.,
+</dd><dt class="label"><a name="xmlbase" id="xmlbase"/>XML Base</dt><dd>Jonathan Marsh and Richard Tobin, Eds.,
<a href="http://www.w3.org/TR/2009/REC-xmlbase-20090128/"><cite>XML Base (Second Edition)</cite></a>,
W3C Recommendation, 28 January 2009. (See
<a href="http://www.w3.org/TR/2009/REC-xmlbase-20090128/">http://www.w3.org/TR/2009/REC-xmlbase-20090128/</a>.)
@@ -8933,10 +8828,10 @@
W3C Recommendation, 09 September 2005. (See
<a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/">http://www.w3.org/TR/2005/REC-xml-id-20050909/</a>.)
</dd><dt class="label"><a name="xml-media" id="xml-media"/>XML Media</dt><dd>Makato Murata, Simon St. Laurent,
-Kan Khon<span class="diff-add">, Eds.</span>, <a href="http://www.rfc-editor.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>,
+Kan Khon, Eds., <a href="http://www.rfc-editor.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>,
RFC 3023, January 2001, IETF.(See
<a href="http://www.rfc-editor.org/rfc/rfc3023.txt">http://www.rfc-editor.org/rfc/rfc3023.txt</a>.)
-</dd><dt class="label"><a name="infoset" id="infoset"/>XML InfoSet</dt><dd>John Cowan and Richard Tobin<span class="diff-add">, Eds.</span>,
+</dd><dt class="label"><a name="infoset" id="infoset"/>XML InfoSet</dt><dd>John Cowan and Richard Tobin, Eds.,
<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>XML Information Set (Second Edition)</cite></a>,
W3C Recommendation, 04 February 2004. (See
<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</a>.)
@@ -8962,7 +8857,7 @@
W3C Recommendation, 05 December 2006. (See
<a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/">http://www.w3.org/TR/2006/REC-xsl11-20061205/</a>.)
</dd></dl></div><div class="div1">
-<h2><a name="other-references" id="other-references"/>I Other References (Non-Normative)</h2><dl><dt class="labeldiff-add"><a name="ccreq" id="ccreq"/>CC-DECODER-REQ</dt><dd class="diff-add">Norman Walsh, Ed.,
+<h2><a name="other-references" id="other-references"/>I Other References (Non-Normative)</h2><dl><dt class="label"><a name="ccreq" id="ccreq"/>CC-DECODER-REQ</dt><dd>Norman Walsh, Ed.,
<a href="http://edocket.access.gpo.gov/cfr_2005/octqtr/47cfr15.119.htm"><cite>Closed Caption Decoder
Requirements for Analog Television</cite></a>,
United States Code of Federal Regulations, Title 47, Volume 1, Part 15, § 15.119. (See
@@ -8984,7 +8879,7 @@
<a href="http://www.iso.org/"><cite>Information technology – Multimedia content description
interface – Part 5: Multimedia description schemes</cite></a>,
International Organization for Standardization (ISO).
-</dd><dt class="labeldiff-add"><a name="nsstate" id="nsstate"/>NSState</dt><dd class="diff-add">Norman Walsh, Ed.,
+</dd><dt class="label"><a name="nsstate" id="nsstate"/>NSState</dt><dd>Norman Walsh, Ed.,
<a href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html"><cite>The Disposition
of Names in an XML Namespace</cite></a>, TAG Finding, 9 January 2006. (See
<a href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html">http://www.w3.org/tag/doc/namespaceState-2006-01-09</a>.)
@@ -8993,11 +8888,6 @@
Framework: Specifications Guidelines</cite></a>, W3C Recommendation, 17
August 2005. (See
<a href="http://www.w3.org/TR/qaframe-spec/">http://www.w3.org/TR/qaframe-spec/</a>.)
-</dd><dt class="labeldiff-del"><a name="scheme" id="scheme"/>SCHEME</dt><dd class="diff-del">Guy Steele and Gerald Sussman,
-<a href="http://swiss.csail.mit.edu/projects/scheme/"><cite>Scheme Programming
-Environment</cite></a>,
-Massachusetts Institute of Technology. (See
-<a href="http://swiss.csail.mit.edu/projects/scheme/">http://swiss.csail.mit.edu/projects/scheme/</a>.)
</dd><dt class="label"><a name="smpte170m" id="smpte170m"/>SMPTE 170M</dt><dd>ANSI/SMPTE 170M,
<a href="http://www.smpte.org/"><cite>Television – Composite Analog Video
Signal – NTSC for Studio Applications</cite></a>, SMPTE Standard.
@@ -9031,7 +8921,7 @@
<h2><a name="derivation" id="derivation"/>K Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TT AF
vocabulary, separately describing derivation of elements and
attributes.</p><div class="div2">
-<h3><a name="d3e19267" id="d3e19267"/>K.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
+<h3><a name="d3e18335" id="d3e18335"/>K.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
specifies a TT AF 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
@@ -9086,7 +8976,7 @@
and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e19746" id="d3e19746"/>K.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
+<h3><a name="d3e18814" id="d3e18814"/>K.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
specifies a TT AF 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
@@ -9159,9 +9049,9 @@
<h2><a name="qa" id="qa"/>L 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 name="d3e20658" id="d3e20658"/>L.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-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 name="d3e19726" id="d3e19726"/>L.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table L-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/></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/></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/></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/></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/></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/></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/></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/></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/></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/></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/></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>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>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 name="d3e20822" id="d3e20822"/>L.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-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/></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/></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/></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>NO</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/></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/></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/></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>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/></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>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/></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>NO</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/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td/><td/><td/></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/></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/></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/></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/></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/></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>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>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>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/></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 name="d3e19890" id="d3e19890"/>L.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table L-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/></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/></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/></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>NO</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/></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/></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/></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>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/></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>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/></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>NO</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/></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiles">YES</a></td><td/><td/><td/></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/></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/></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/></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/></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/></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>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>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>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/></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>K 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
<a href="#doctypes">TT AF 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">
@@ -9513,7 +9403,7 @@
</pre></div></div><div class="div2">
<h3><a name="change-history-cr1-to-lc3" id="change-history-cr1-to-lc3"/>O.3 Changes from First Candidate Recommendation to Third Last Call
Working Draft</h3><div class="exampleInner"><pre>
-<span class="diff-chg"><span class="strong">Technical Changes</span>
+<span class="strong">Technical Changes</span>
The following changes result in a technical change of the conformance
criteria, the normative abstract document type that is defined
@@ -9597,4 +9487,4 @@
* Remove style and metadata extension namespaces [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/112">I-112</a>].
* Clarify region association algorithm [<a href="http://www.w3.org/AudioVideo/TT/tracker/issues/118">I-118</a>].
-</span></pre></div></div></div></div></body></html>
\ No newline at end of file
+</pre></div></div></div></div></body></html>
\ No newline at end of file
--- a/spec/ttaf1-dfxp.xml Sun May 31 14:57:44 2009 +0000
+++ b/spec/ttaf1-dfxp.xml Sun May 31 14:59:30 2009 +0000
@@ -96,7 +96,7 @@
<authlist id="editors" role="editor">
<author>
<name>Glenn Adams</name>
-<affiliation><phrase diff="chg">Samsung Electronics Co., Ltd.</phrase></affiliation>
+<affiliation>Samsung Electronics Co., Ltd.</affiliation>
</author>
</authlist>
<authlist id="contributors" role="contributor">
@@ -876,14 +876,6 @@
<specref ref="conformance-generic-processor"/>.</p>
</item>
<item>
-<p diff="del">The processor implements support for the region and line layout
-semantics defined by <specref ref="semantics-region-layout"/> and
-<specref ref="semantics-line-layout"/>, respectively. In addition, the
-processor should satisfy the user agent accessibility guidelines specified by
-<bibref ref="uaag"/>.
-</p>
-</item>
-<item>
<p>The processor supports the DFXP Presentation profile as specified
by <specref ref="profile-dfxp-presentation"/>.</p>
</item>
@@ -1030,31 +1022,16 @@
<td><code>http://www.w3.org/2006/10/ttaf1#parameter</code></td>
</tr>
<tr>
-<td><phrase diff="del">TT Parameter Extension</phrase></td>
-<td><phrase diff="del"><code>ttpx:</code></phrase></td>
-<td><phrase diff="del"><code>http://www.w3.org/2006/10/ttaf1#parameter-extension</code></phrase></td>
-</tr>
-<tr>
<td>TT Style</td>
<td><code>tts:</code></td>
<td><code>http://www.w3.org/2006/10/ttaf1#styling</code></td>
</tr>
<tr>
-<td><phrase diff="del">TT Style Extension</phrase></td>
-<td><phrase diff="del"><code>ttsx:</code></phrase></td>
-<td><phrase diff="del"><code>http://www.w3.org/2006/10/ttaf1#styling-extension</code></phrase></td>
-</tr>
-<tr>
<td>TT Metadata</td>
<td><code>ttm:</code></td>
<td><code>http://www.w3.org/2006/10/ttaf1#metadata</code></td>
</tr>
<tr>
-<td><phrase diff="del">TT Metadata Extension</phrase></td>
-<td><phrase diff="del"><code>ttmx:</code></phrase></td>
-<td><phrase diff="del"><code>http://www.w3.org/2006/10/ttaf1#metadata-extension</code></phrase></td>
-</tr>
-<tr>
<td>TT Profile</td>
<td><emph>none</emph></td>
<td><code>http://www.w3.org/2006/10/ttaf1/profile</code></td>
@@ -1082,7 +1059,7 @@
e.g., for designating profiles, features, extensions and for
dereferencing standard profile definitions.</p>
</note>
-<p diff="add">All TT AF Namespaces are <loc
+<p>All TT AF Namespaces are <loc
href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><emph>mutable</emph></loc>
<bibref ref="nsstate"/>; all undefined names in these namespaces are reserved for future
standardization by the W3C.</p>
@@ -1116,8 +1093,8 @@
<td><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code></td>
</tr>
<tr>
-<td><phrase diff="add">DFXP Full</phrase></td>
-<td><phrase diff="add"><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-full</code></phrase></td>
+<td>DFXP Full</td>
+<td><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-full</code></td>
</tr>
</tbody>
</table>
@@ -1136,15 +1113,15 @@
<p>A profile designator is not restricted to the set of designators enumerated
in <specref ref="profile-vocab-table"/>, but may be any URI that
feasibly dereferences a TT AF Profile Definition Document.</p>
-<p>The profile of <phrase diff="add">TT AF that must be supported by a
-TT AF content processor in order to process</phrase> a document
+<p>The profile of TT AF that must be supported by a
+TT AF content processor in order to process a document
instance is specified either (1) by specifying a
<att>ttp:profile</att> attribute on the root <el>tt</el> element, as
defined by <specref ref="parameter-attribute-profile"/>, or (2) by
-including <phrase diff="chg">one or more</phrase> <el>ttp:profile</el>
-element<phrase diff="add">s</phrase> in the <el>head</el> element, in
+including one or more <el>ttp:profile</el>
+elements in the <el>head</el> element, in
accordance with <specref ref="parameter-vocabulary-profile"/>.</p>
-<p diff="add">If a <el>ttp:profile</el> element appears as a
+<p>If a <el>ttp:profile</el> element appears as a
descendant of the <el>tt</el> element, then the <loc
href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
attribute should not be specified on the <el>tt</el> element. If both
@@ -1152,7 +1129,7 @@
attribute are present (in a given document instance), then the
<att>ttp:profile</att> attribute must be ignored for the purpose of
determining the declared profile requirements.</p>
-<p diff="add">If more than one <el>ttp:profile</el> element appears in
+<p>If more than one <el>ttp:profile</el> element appears in
a TT AF document instance, then all specified profiles apply
simultaneously. In such a case, if some feature or some extension is
specified by one profile to be used (mandatory and enabled) and by
@@ -1198,38 +1175,38 @@
<p>If a TT AF document instance makes use of a feature defined by
<specref ref="feature-designations"/> and if the intended use of the
document requires the recognition and processing of that feature, then
-the document must include a <emph>required feature</emph><phrase diff="add"> or
-a <emph>used feature</emph></phrase>
-specification in one of its declared<phrase diff="add"> or
-referenced</phrase> profiles. If a TT AF document instance makes use
+the document must include a <emph>required feature</emph> or
+a <emph>used feature</emph>
+specification in one of its declared or
+referenced profiles. If a TT AF document instance makes use
of an extension designatable by <specref
ref="extension-designations"/> and if the intended use of the document
requires the recognition and processing of that extension, then the
-document must include a <emph>required extension</emph><phrase diff="add"> or
-a <emph>used extension</emph></phrase> specification
-in one of its declared<phrase diff="add"> or referenced</phrase>
+document must include a <emph>required extension</emph> or
+a <emph>used extension</emph> specification
+in one of its declared or referenced
profiles.</p>
<note role="elaboration">
-<p>A required<phrase diff="add"> or used</phrase> feature
+<p>A required or used feature
specification is expressed directly (or indirectly by referring to a
profile) by means of a <loc
href="#parameter-vocabulary-feature"><el>ttp:feature</el></loc>
element where the value of its <att>value</att> attribute is
-<code>required</code><phrase diff="add"> or <code>use</code>,
-respectively</phrase>. A required<phrase diff="add"> or used</phrase>
+<code>required</code> or <code>use</code>,
+respectively. A required or used
extension specification is expressed directly (or indirectly by
referring to a profile) by means of a <loc
href="#parameter-vocabulary-extension"><el>ttp:extension</el></loc>
element where the value of its <att>value</att> attribute is
-<code>required</code><phrase diff="add"> or <code>use</code>,
-respectively</phrase>.</p>
+<code>required</code> or <code>use</code>,
+respectively.</p>
</note>
<p>An example of an author defined
-<phrase diff="chg">additive</phrase>, derived profile of the DFXP Presentation
+additive, derived profile of the DFXP Presentation
profile is shown
below in <specref ref="dfxp-example-sub-profile"/>.</p>
<table id="dfxp-example-sub-profile" role="example">
-<caption>Example Fragment – DFXP <phrase diff="chg">Additive</phrase> Profile</caption>
+<caption>Example Fragment – DFXP Additive Profile</caption>
<tbody>
<tr>
<td>
@@ -1237,8 +1214,8 @@
<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1">
<head>
<profile use="dfxp-presentation" xmlns="http://www.w3.org/2006/10/ttaf1#parameter">
- <features <phrase diff="add">xml:base="http://www.w3.org/2006/10/ttaf1/feature"</phrase>>
- <feature value="<phrase diff="chg">required</phrase>">#fontStyle-italic</feature>
+ <features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
+ <feature value="required">#fontStyle-italic</feature>
</features>
</profile>
</head>
@@ -1250,9 +1227,9 @@
</table>
<note role="explanation">
<p>In the above example, the baseline profile is declared to be
-the DFXP Presentation profile, which is then <phrase diff="chg">additively</phrase> modified by making the
-<code>#fontStyle-italic</code> feature <phrase diff="chg">required</phrase> (rather than
-<phrase diff="chg">optional</phrase> as it is defined
+the DFXP Presentation profile, which is then additively modified by making the
+<code>#fontStyle-italic</code> feature required (rather than
+optional as it is defined
in <specref ref="profile-dfxp-presentation"/>). Note also the resetting of the
default XMLNS binding on the <el>profile</el> element to the TT Parameter Namespace.</p>
</note>
@@ -1564,23 +1541,8 @@
<div3 id="extension-vocabulary-overview">
<head>Extension Catalog</head>
<p>The extension vocabulary catalog is intended for use by future
-profiles of the TT AF<phrase diff="add">, and is not further defined
-by this version of this specification</phrase>.</p>
-<p diff="del">In this version of this specification, no
-standardized extension vocabulary is defined. The following namespaces are
-specifically reserved by <specref ref="namespace-vocab-table"/>
-for extension vocabulary:</p>
-<ulist diff="del">
-<item>
-<p>TT Metadata Extension</p>
-</item>
-<item>
-<p>TT Parameter Extension</p>
-</item>
-<item>
-<p>TT Style Extension</p>
-</item>
-</ulist>
+profiles of the TT AF, and is not further defined
+by this version of this specification.</p>
<p>In addition to standardized extension vocabulary, a conforming TT
AF document instance may contain arbitrary namespace qualified
elements that reside in any namespace other than those namespaces
@@ -1616,8 +1578,8 @@
<div3 id="parameter-vocabulary-profile">
<head>ttp:profile</head>
<p>The <el>ttp:profile</el> element is used to specify a collection of
-<phrase diff="chg">used (mandatory and enabled), required (mandatory),
-and optional (voluntary)</phrase> features and extensions that must or
+used (mandatory and enabled), required (mandatory),
+and optional (voluntary) features and extensions that must or
may be supported by a TT AF content processor in order to process a TT
AF document that makes use (or may make use) of such features and
extensions.</p>
@@ -1726,12 +1688,6 @@
end-user notification should be given unless the end-user or system
has disabled such a notification, or if the processor does not permit
or entail the intervention of an end-user.</p>
-<p diff="del">If more than one <el>ttp:profile</el> element appears in a TT AF
-document instance, then all specified profiles apply simultaneously.
-In such a case, if some feature or some extension is specified by one profile
-to be required (mandatory) and by another profile to be optional
-(voluntary), then that feature or extension must be considered to be
-required (mandatory).</p>
<p>The <el>ttp:profile</el> element is illustrated by the following example.</p>
<table id="parameter-vocabulary-profile-example-1" role="example">
<caption>Example Fragment – ttp:profile</caption>
@@ -1740,7 +1696,7 @@
<td>
<eg xml:space="preserve">
<ttp:profile use="dfxp-presentation">
- <ttp:features <phrase diff="add">xml:base="http://www.w3.org/2006/10/ttaf1/feature"</phrase>>
+ <ttp:features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
<ttp:feature>#rollUp</ttp:feature>
</ttp:features>
</ttp:profile>
@@ -1770,7 +1726,7 @@
<td>
<eg xml:space="preserve">
<ttp:features
- <phrase diff="add">xml:</phrase>base = string : <emph>TT Feature Namespace</emph>
+ xml:base = string : <emph>TT Feature Namespace</emph>
<loc href="#content-attribute-id">xml:id</loc> = ID
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#parameter-vocabulary-feature">ttp:feature</loc>*
@@ -1780,16 +1736,16 @@
</tr>
</tbody>
</table>
-<p>If specified, the <att><phrase diff="add">xml:</phrase>base</att>
-attribute must <phrase diff="add">(1) </phrase>adhere to the
+<p>If specified, the <att>xml:base</att>
+attribute must (1) adhere to the
<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-§3.2.17, <phrase diff="add">(2) express an absolute URI that
-adheres to <bibref ref="xmlbase"/></phrase> and, <phrase
-diff="chg">(3) </phrase> express a feature namespace as defined by
+§3.2.17, (2) express an absolute URI that
+adheres to <bibref ref="xmlbase"/> and,
+(3) express a feature namespace as defined by
<specref ref="feature-designations"/>. If not specified, the
-<att><phrase diff="add">xml:</phrase>base</att> attribute's default
+<att>xml:base</att> attribute's default
value applies, which is the TT Feature Namespace.</p>
-<p>The <att><phrase diff="add">xml:</phrase>base</att> attribute is
+<p>The <att>xml:base</att> attribute is
used to permit the abbreviation of feature designation URIs expressed
by child <el>ttp:feature</el> elements.</p>
</div3>
@@ -1808,7 +1764,7 @@
<td>
<eg xml:space="preserve">
<ttp:feature
- value = (<phrase diff="chg">optional|required|use</phrase>) : required
+ value = (optional|required|use) : required
<loc href="#content-attribute-id">xml:id</loc> = ID
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> #PCDATA
@@ -1819,28 +1775,28 @@
</tbody>
</table>
<p>If the URI expressed by the content of the <el>ttp:feature</el>
-element is a relative URI, then, when combined with the <phrase
-diff="chg">feature namespace value expressed by</phrase> the
-<att><phrase diff="add">xml:</phrase>base</att> attribute of the
+element is a relative URI, then, when combined with the
+feature namespace value expressed by the
+<att>xml:base</att> attribute of the
nearest ancestor <el>ttp:features</el> element, it must express an
absolute URI. In either case (original absolute URI or resulting
absolutized URI), the URI expressed by the <el>ttp:feature</el>
element must further adhere to the syntax of a feature designation as
-defined by <specref ref="feature-designations"/>.</p> <p diff="add">If
+defined by <specref ref="feature-designations"/>.</p> <p>If
the URI expressed by the content of the <el>ttp:feature</el> element
is a relative URI, then an <att>xml:base</att> attribute should be
specified on the nearest ancestor <el>ttp:features</el> element.</p>
<p>The <att>value</att> attribute specifies whether a conforming TT AF
processor must or may implement the designated feature in order to
process the document. If the value of the <att>value</att> attribute
-is <phrase diff="chg"> <code>optional</code>, then the processor need
+is <code>optional</code>, then the processor need
not implement or otherwise support the feature in order to process the
document; if the value is <code>required</code>, then the processor
must implement or otherwise support the feature in order to process
-the document;</phrase><phrase diff="add"> if the value is
+the document; if the value is
<code>use</code>, then the processor must both (1) implement or
otherwise support the feature and (2) enable (activate) use of the
-feature</phrase>.</p>
+feature.</p>
<note role="clarification">
<p>The default value of the <att>value</att> attribute is
@@ -1850,7 +1806,7 @@
specifying that support for the feature is required.</p>
</note>
<p>If the value of the <att>value</att> attribute is
-<code>required</code><phrase diff="add"> or <code>use</code></phrase>,
+<code>required</code> or <code>use</code>,
and if the TT AF processor implementation does
not support the feature, then it must not further process the document
without the presence of an explicit override from an end-user or some
@@ -1881,8 +1837,8 @@
<td>
<eg xml:space="preserve">
<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation">
- <ttp:features <phrase diff="add">xml:base="http://www.w3.org/2006/10/ttaf1/feature"</phrase>>
- <phrase role="strong"><ttp:feature value="<phrase diff="add">required</phrase>">#fontStyle-italic</ttp:feature></phrase>
+ <ttp:features xml:base="http://www.w3.org/2006/10/ttaf1/feature">
+ <phrase role="strong"><ttp:feature value="required">#fontStyle-italic</ttp:feature></phrase>
<phrase role="strong"><ttp:feature value="required">#textDecoration-under</ttp:feature></phrase>
</ttp:features>
</ttp:profile>
@@ -1894,18 +1850,18 @@
<note role="explanation">
<p>In the above example, the DFXP presentation profile is used as the
baseline profile. This baseline profile is then modified by two
-<el>ttp:feature</el> <phrase diff="chg">elements in order</phrase> to
-superset the baseline profile <phrase diff="chg">(since neither
+<el>ttp:feature</el> elements in order to
+superset the baseline profile (since neither
<code>#fontStyle-italic</code> nor <code>#textDecoration-under</code>
-are required by the DFXP presentation profile)</phrase>. Note that
+are required by the DFXP presentation profile). Note that
the explicit specification of <code>required</code> on the
-<att>value</att> attribute on <phrase diff="chg">these two</phrase>
-<el>ttp:feature</el> elements is not <phrase diff="add">strictly
-</phrase>necessary, since it is the default value of this
+<att>value</att> attribute on these two
+<el>ttp:feature</el> elements is not strictly
+necessary, since it is the default value of this
attribute.</p>
<p>The effect of this example is to express authorial intentions that
-<phrase diff="chg">italic font style and text underlining must be
-supported</phrase>.</p>
+italic font style and text underlining must be
+supported.</p>
</note>
</div3>
<div3 id="parameter-vocabulary-extensions">
@@ -1922,7 +1878,7 @@
<td>
<eg xml:space="preserve">
<ttp:extensions
- <phrase diff="add">xml:</phrase>base = string : <emph>TT Extension Namespace</emph>
+ xml:base = string : <emph>TT Extension Namespace</emph>
<loc href="#content-attribute-id">xml:id</loc> = ID
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#parameter-vocabulary-extension">ttp:extension</loc>*
@@ -1932,16 +1888,16 @@
</tr>
</tbody>
</table>
-<p>If specified, the <att><phrase diff="add">xml:</phrase>base</att>
-attribute must <phrase diff="add">(1) </phrase>adhere to the
+<p>If specified, the <att>xml:base</att>
+attribute must (1) adhere to the
<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-§3.2.17, <phrase diff="add">(2) express an absolute URI that
-adheres to <bibref ref="xmlbase"/></phrase> and, <phrase
-diff="chg">(3) </phrase> express an extension namespace as defined by
+§3.2.17, (2) express an absolute URI that
+adheres to <bibref ref="xmlbase"/> and,
+(3) express an extension namespace as defined by
<specref ref="extension-designations"/>. If not specified, the
-<att><phrase diff="add">xml:</phrase>base</att> attribute's default
+<att>xml:base</att> attribute's default
value applies, which is the TT Extension Namespace.</p>
-<p>The <att><phrase diff="add">xml:</phrase>base</att> attribute is
+<p>The <att>xml:base</att> attribute is
used to permit the abbreviation of feature designation URIs expressed
by child <el>ttp:extension</el> elements.</p>
</div3>
@@ -1960,7 +1916,7 @@
<td>
<eg xml:space="preserve">
<ttp:extension
- value = (<phrase diff="chg">optional|required|use</phrase>) : required
+ value = (optional|required|use) : required
<loc href="#content-attribute-id">xml:id</loc> = ID
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> #PCDATA
@@ -1971,29 +1927,29 @@
</tbody>
</table>
<p>If the URI expressed by the content of the <el>ttp:extension</el>
-element is a relative URI, then, when combined with the <phrase
-diff="chg">extension namespace value expressed by</phrase> the
-<att><phrase diff="add">xml:</phrase>base</att> attribute of the
+element is a relative URI, then, when combined with the
+extension namespace value expressed by the
+<att>xml:base</att> attribute of the
nearest ancestor <el>ttp:extensions</el> element, it must express an
absolute URI. In either case (original absolute URI or resulting
absolutized URI), the URI expressed by the <el>ttp:extension</el>
element must further adhere to the syntax of an extension designation
as defined by <specref ref="extension-designations"/>.</p>
-<p diff="add">If the URI expressed by the content of the
+<p>If the URI expressed by the content of the
<el>ttp:feature</el> element is a relative URI, then an
<att>xml:base</att> attribute should be specified on the nearest
ancestor <el>ttp:extensions</el> element.</p>
<p>The <att>value</att> attribute specifies whether a conforming TT AF
processor must or may implement the designated extension in order to
process the document. If the value of the <att>value</att> attribute
-is <phrase diff="chg"> <code>optional</code>, then the processor need
+is <code>optional</code>, then the processor need
not implement or otherwise support the extension in order to process the
document; if the value is <code>required</code>, then the processor
must implement or otherwise support the extension in order to process
-the document;</phrase><phrase diff="add"> if the value is
+the document; if the value is
<code>use</code>, then the processor must both (1) implement or
otherwise support the extension and (2) enable (activate) use of the
-extension</phrase>.</p>
+extension.</p>
<note role="clarification">
<p>The default value of the <att>value</att> attribute is
<code>required</code>, as indicated in the above element information
@@ -2002,7 +1958,7 @@
specifying that support for the extension is required.</p>
</note>
<p>If the value of the <att>value</att> attribute is
-<code>required</code><phrase diff="add"> or <code>use</code></phrase>,
+<code>required</code> or <code>use</code>,
and if the TT AF processor implementation does not support the
extension, then it must not further process the document without the
presence of an explicit override from an end-user or some
@@ -2033,11 +1989,8 @@
<td>
<eg xml:space="preserve">
<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation">
-<phrase diff="del"> <ttp:extensions>
- <phrase role="strong"><ttp:extension value="required">#x-prefilter-by-language</ttp:extension></phrase>
- </ttp:extensions></phrase>
- <ttp:extensions <phrase diff="add">xml:</phrase>base="http://foo.bar.example.org/ttaf1/extension">
- <phrase role="strong"><ttp:extension value="<phrase diff="chg">use</phrase>">#<phrase diff="chg">prefilter-by-language</phrase></ttp:extension></phrase>
+ <ttp:extensions xml:base="http://foo.bar.example.org/ttaf1/extension">
+ <phrase role="strong"><ttp:extension value="use">#prefilter-by-language</ttp:extension></phrase>
</ttp:extensions>
</ttp:profile>
</eg>
@@ -2048,26 +2001,11 @@
<note role="explanation">
<p>In the above example, the DFXP transformation profile is used as
the baseline profile. This baseline profile is then supersetted by
-specifying that support<phrase diff="add"> and use</phrase> is
-required for<phrase diff="del"> two extensions, where the first
-extension is a experimental extension
-<code>#x-prefilter-by-language</code> defined (hypothetically) by the
-W3C in the TT Extension Namespace, and where the second extension
-is</phrase> a private extension defined in a third party
-namespace.<phrase diff="del">The <att>base</att> attribute is elided
-from the first specified <el>ttp:extensions</el> element since it
-makes use of the TT Extension Namespace. Note that the explicit
-specification of <code>required</code> on the <att>value</att>
-attributes on the two <el>ttp:extension</el> elements is not
-necessary, since it is the default value of this
-attribute.</phrase></p>
+specifying that support and use is required for a private extension
+defined in a third party namespace.</p>
<p>The effect of this example is to express authorial intentions that
a recipient processor must support the DFXP transformation profile and
-must also support<phrase diff="add"> and use</phrase> <phrase
-diff="del"> two additional extensions, one (hypothetically) defined by
-the W3C (in another specification or in a future version of this
-specification) and the other</phrase><phrase diff="add">an extension
-</phrase>defined by a third party.</p>
+must also support and use an extension defined by a third party.</p>
</note>
</div3>
</div2>
@@ -2376,14 +2314,6 @@
<p>A <att>ttp:profile</att>
attribute is considered to be significant only when specified on the
<el>tt</el> element.</p>
-<p diff="del">If a <el>ttp:profile</el> element appears as a
-descendant of the <el>tt</el> element, then the <loc
-href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
-attribute should not be specified on the <el>tt</el> element. If both
-a <el>ttp:profile</el> element and a <att>ttp:profile</att>
-attribute are present (in a given document instance), then the
-<att>ttp:profile</att> attribute must be ignored for the purpose of
-determining the declared profile requirements.</p>
</div3>
<div3 id="parameter-attribute-smpteMode">
<head>ttp:smpteMode</head>
@@ -2709,7 +2639,7 @@
<loc href="#content-attribute-id">xml:id</loc> = ID
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
- <phrase diff="add">{<emph>any attribute not in default or any TT namespace</emph>}</phrase>>
+ {<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#element-vocab-group-table">Parameters.class</loc>*, <loc href="#styling-vocabulary-styling">styling</loc>?, <loc href="#layout-vocabulary-layout">layout</loc>?
</head>
</eg>
@@ -2753,9 +2683,7 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Metadata namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Metadata Extension namespace</emph>}</phrase>
{<emph>any attribute in TT Style namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Style Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#element-vocab-group-table">Animation.class</loc>*, <loc href="#content-vocabulary-div">div</loc>*
</body>
@@ -2843,9 +2771,7 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Metadata namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Metadata Extension namespace</emph>}</phrase>
{<emph>any attribute in TT Style namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Style Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc
href="#element-vocab-group-table">Metadata.class</loc>*, <loc
@@ -2907,9 +2833,7 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Metadata namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Metadata Extension namespace</emph>}</phrase>
{<emph>any attribute in TT Style namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Style Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc
href="#element-vocab-group-table">Metadata.class</loc>*, <loc
@@ -2975,9 +2899,7 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Metadata namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Metadata Extension namespace</emph>}</phrase>
{<emph>any attribute in TT Style namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Style Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc
href="#element-vocab-group-table">Metadata.class</loc>*, <loc
@@ -3017,9 +2939,7 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Metadata namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Metadata Extension namespace</emph>}</phrase>
{<emph>any attribute in TT Style namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Style Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#element-vocab-group-table">Animation.class</loc>*
</br>
@@ -3201,7 +3121,6 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Style namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Style Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*
</style>
@@ -3865,8 +3784,8 @@
dynamic flow semantics apply.</p>
<p>If the value of this attribute is <code>rollUp</code>, then
this value is interpreted as a shorthand value equivalent to
-<code>out(line,smooth) <phrase diff="chg">clear</phrase>(0.433s)</code>.</p>
-<note role="explanation" diff="add">
+<code>out(line,smooth) clear(0.433s)</code>.</p>
+<note role="explanation">
<p>The choice of a definite duration of 0.433 seconds for the clear
interval for roll up dynamic flow timing is based upon recommendations
specified in <bibref ref="ccreq"/>, p. 792.
@@ -3876,15 +3795,15 @@
href="#style-value-flowFunction"><flowFunction></loc>, then that
flow function applies equally to <emph>fill into</emph> and <emph>clear
from</emph> dynamic flow operations.</p>
-<p>If either <code><phrase diff="chg">fill</phrase>()</code> or
-<code><phrase diff="chg">clear</phrase>()</code> <loc
+<p>If either <code>fill()</code> or
+<code>clear()</code> <loc
href="#style-value-flowIntervalFunction"><flowIntervalFunction></loc>
is not specified, then the <code>auto</code> value for the missing
<loc
href="#style-value-flowIntervalFunction"><flowIntervalFunction></loc>
-applies. <phrase diff="add">Multiple instances of the same <loc
+applies. Multiple instances of the same <loc
href="#style-value-flowIntervalFunction"><flowIntervalFunction></loc>
-must not appear in the value of this attribute.</phrase></p>
+must not appear in the value of this attribute.</p>
<p>The normative processing model for dynamic flow behavior is
specified in <specref ref="dynamicFlowModel"/>.</p>
<p>If a specified value of this attribute is not supported,
@@ -3906,7 +3825,7 @@
<style tts:fontFamily="proportionalSansSerif"/>
<style tts:fontSize="18px"/>
<style <phrase role="strong">tts:overflow="dynamic"</phrase>/>
- <style <phrase role="strong">tts:dynamicFlow="in(word,jump) <phrase diff="add">fill(1.0s) </phrase>out(line,smooth) <phrase diff="chg">clear</phrase>(0.3s)"</phrase>/>
+ <style <phrase role="strong">tts:dynamicFlow="in(word,jump) fill(1.0s) out(line,smooth) clear(0.3s)"</phrase>/>
</region>
...
<p region="r1">
@@ -4824,8 +4743,8 @@
must be performed as if the region's width and height were
unconstrained,
but with
-a well-defined origin. If the value is <code>hidden</code><phrase diff="add"> or
-<code>dynamic</code></phrase>, then content should
+a well-defined origin. If the value is <code>hidden</code> or
+<code>dynamic</code>, then content should
be clipped outside of the affected region.</p>
<note role="explanation">
<p>Unless a manual line break element <el>br</el> is used by the content author,
@@ -6159,9 +6078,7 @@
flowUnit
: "glyph"
- <phrase diff="del">| "inline"</phrase>
| "line"
- <phrase diff="del">| "block"</phrase>
| "character"
| "word"
| extensionToken
@@ -6183,7 +6100,7 @@
<code>in()</code> and <code>out()</code> flow functions respectively.</p>
<p>Dynamic flow occurs on the basis of specific visual or semantic
content units. In the case of
-<phrase diff="chg"><code>glyph</code> and <code>line</code></phrase>,
+<code>glyph</code> and <code>line</code>,
the unit of dynamic flow is based upon a visually rendered construct
(<code>glyph</code>) or upon an area of the area
tree produced by formatting the affected content. In the case of
@@ -6230,8 +6147,8 @@
<td>
<eg xml:space="preserve">
<flowIntervalFunction>
- : "<phrase diff="chg">fill</phrase>(" flowIntervalArguments ")"
- | "<phrase diff="chg">clear</phrase>(" flowIntervalArguments ")"
+ : "fill(" flowIntervalArguments ")"
+ | "clear(" flowIntervalArguments ")"
flowIntervalArguments
: "auto"
@@ -6245,13 +6162,13 @@
</tr>
</tbody>
</table>
-<p>The <code><phrase diff="chg">fill</phrase>()</code> flow interval function is used to
+<p>The <code>fill()</code> flow interval function is used to
determine the <emph>computed fill interval</emph> state parameter for performing
dynamic flow processing, which expresses the
duration of time between fill
timer events, as specified by <specref ref="flowTimerFill"/>, which
in turn, limits the dynamic flowed content fill rate.</p>
-<p>The <code><phrase diff="chg">clear</phrase>()</code> flow interval function is used to
+<p>The <code>clear()</code> flow interval function is used to
determine the <emph>computed clear interval</emph> state parameter for performing
dynamic flow processing, which expresses the
duration of time between clear
@@ -6264,8 +6181,8 @@
specified as an argument to a flow interval function, then it is
considered to represent a <emph>definite rate</emph> in units per
second, where the applicable unit is determined in the context of
-whether the rate is used with an <code><phrase diff="chg">fill</phrase>()</code> or
-<code><phrase diff="chg">clear</phrase>()</code> flow interval function.</p>
+whether the rate is used with an <code>fill()</code> or
+<code>clear()</code> flow interval function.</p>
<p>The computed fill and clear interval values are defined by
<specref ref="dynamicFlowIntervalTimingCalculation"/>.</p>
</div3>
@@ -6532,10 +6449,10 @@
</ulist>
<div4 id="semantics-style-association-inline">
<head>Inline Styling</head>
-<p>Style properties may be expressed in an inline manner by direct specification of an
-attribute from the TT Style Namespace<phrase diff="del"> or TT Style Extension Namespace</phrase>
-on the affected element. When expressed in this manner, the association of style information
-is referred to as <emph>inline styling</emph>.</p>
+<p>Style properties may be expressed in an inline manner by direct
+specification of an attribute from the TT Style Namespace on the
+affected element. When expressed in this manner, the association of
+style information is referred to as <emph>inline styling</emph>.</p>
<p>Style properties associated by inline styling are afforded a higher priority than all other
forms of style association.</p>
<table id="style-association-example-1" role="example">
@@ -7206,7 +7123,6 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Style namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Style Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#element-vocab-group-table">Animation.class</loc>*, <loc href="#styling-vocabulary-style">style</loc>*
</region>
@@ -7299,8 +7215,7 @@
then a <emph>default region</emph> is implied with the following characteristics:</p>
<ulist>
<item>
-<p>the <phrase diff="chg">identity</phrase> of the default region is consider<phrase
-diff="add">ed</phrase> to be anonymous;</p>
+<p>the identity of the default region is considered to be anonymous;</p>
</item>
<item>
<p>the extent of the default region is the same as the root container
@@ -7402,15 +7317,15 @@
href="#layout-attribute-region"><att>region</att></loc> attribute,
then the element is associated with the region referenced by the most
immediate ancestor that specifies this attribute;</p></item>
-<item><p diff="add"> if the element contains a descendant element that
+<item><p> if the element contains a descendant element that
specifies a <loc
href="#layout-attribute-region"><att>region</att></loc> attribute,
then the element is associated with the region referenced by that
attribute;</p></item>
<item><p>if a default region was implied (due to the absence of any
<loc href="#layout-vocabulary-region"><el>region</el></loc> element),
-then the element is associated with the default region<phrase diff="add">;</phrase></p></item>
-<item><p>the element is not associated with any region<phrase diff="add">.</phrase></p></item>
+then the element is associated with the default region;</p></item>
+<item><p>the element is not associated with any region.</p></item>
</olist>
<p>The pseudo-code shown in <specref ref="content-hierarchy-region-mapping"/>
provides one possible algorithm that implements these processing steps.</p>
@@ -7672,7 +7587,7 @@
<p>The semantics of line layout, including line breaking, defined by
<bibref ref="xsl11"/> apply to the performance of the composition and layout of
lines for presentation processing of a document instance on a visual medium.</p>
-<p diff="add">If a profile that applies to a document instance
+<p>If a profile that applies to a document instance
requires use of the <loc
href="#feature-lineBreak-uax14">#lineBreak-uax14</loc> feature
(i.e., the value attribute for the feature is specified as <code>use</code>), then
@@ -7981,7 +7896,7 @@
<loc href="#content-attribute-id">xml:id</loc> = ID
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
- {<emph>a single attribute in TT Style<phrase diff="del"> or TT Style Extension</phrase> namespace</emph>}
+ {<emph>a single attribute in TT Style namespace</emph>}
{<emph>any attribute not in default or any TT namespace</emph>}>
<emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*
</set>
@@ -8123,9 +8038,8 @@
<loc href="#content-attribute-lang">xml:lang</loc> = string
<loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
{<emph>any attribute in TT Metadata namespace</emph>}
- <phrase diff="del">{<emph>any attribute in TT Metadata Extension namespace</emph>}</phrase>
{<emph>any attribute not in default or any TT namespace</emph>}>
- <emph>Content:</emph> <phrase diff="chg">({<emph>any element in TT Metadata namespace</emph>}|{<emph>any element not in any TT namespace</emph>})*</phrase>
+ <emph>Content:</emph> ({<emph>any element in TT Metadata namespace</emph>}|{<emph>any element not in any TT namespace</emph>})*
</metadata>
</eg>
</td>
@@ -8135,9 +8049,9 @@
<note role="explanation">
<p>The meaning of a specific metadata item must be evaluated in the
context of where it appears. The core vocabulary catalog permits an
-arbitrary number of <el>metadata</el> element children of any <phrase
-diff="chg">content</phrase> element type except for the <phrase
-diff="chg"><el>tt</el></phrase> element. See specific element
+arbitrary number of <el>metadata</el> element children of any
+content element type except for the
+<el>tt</el> element. See specific element
vocabulary definitions for any constraints that apply to such
usage.</p>
</note>
@@ -8647,19 +8561,19 @@
of the <code>out()</code> flow function;</p></item>
<item><p><emph>clear style</emph>, as specified by the <code>flowStyle</code> argument
of the <code>out()</code> flow function;</p></item>
-<item><p><emph>fill interval</emph>, as specified by the <code><phrase diff="chg">fill</phrase>()</code>
+<item><p><emph>fill interval</emph>, as specified by the <code>fill()</code>
flow interval function;</p></item>
-<item><p><emph>clear interval</emph>, as specified by the <code><phrase diff="chg">clear</phrase>()</code>
+<item><p><emph>clear interval</emph>, as specified by the <code>clear()</code>
flow interval function;</p></item>
<item><p><emph>computed fill interval</emph>, as determined by the flow
interval timing calculation below;</p></item>
<item><p><emph>computed clear interval</emph>, as determined by the flow
interval timing calculation below;</p></item>
-<item><p diff="add"><emph>last fill time</emph>, the time at which the last fill operation
+<item><p><emph>last fill time</emph>, the time at which the last fill operation
occurred;</p></item>
-<item><p diff="add"><emph>last clear time</emph>, the time at which the last clear operation
+<item><p><emph>last clear time</emph>, the time at which the last clear operation
occurred;</p></item>
-<item><p diff="add"><emph>dynamic flow lock</emph>, a synchronization primitive;</p></item>
+<item><p><emph>dynamic flow lock</emph>, a synchronization primitive;</p></item>
</olist>
</item>
</olist>
@@ -8725,9 +8639,8 @@
</item>
<item><p>If any one of the conditions 2a, 2b, and 2c applies, then do not
change the flow buffer.</p></item>
-<item><p>If condition 2d applies, then<phrase diff="del">
-instantaneously</phrase> replace
-<phrase diff="add">at time <code>T<sub>k+1</sub></code> </phrase>the affected
+<item><p>If condition 2d applies, then replace
+at time <code>T<sub>k+1</sub></code> the affected
content of the flow buffer with the new content (in part or in whole) that corresponds with
time <code>T<sub>k+1</sub></code> such that the
logical content position
@@ -8755,9 +8668,9 @@
clear timers to their inactive state.</p></item>
<item><p>If using automatic flow interval timing, then re-perform the process
described in <specref ref="dynamicFlowIntervalTimingCalculation"/>.</p></item>
-<item><p>If the fill timer is not active, then <phrase
-diff="chg">reset the fill timer to the current value of the computed
-fill interval</phrase>.</p></item>
+<item><p>If the fill timer is not active, then
+reset the fill timer to the current value of the computed
+fill interval.</p></item>
</olist>
</item>
</olist>
@@ -8766,14 +8679,12 @@
significantly different from the content of the same flow buffer at
time <code>T<sub>k+1</sub></code> if the set of glyph areas that would
be produced by
-<phrase diff="del">formatting the content</phrase><phrase
-diff="add">performing synchronic flow processing on the intermediate
-synchronic document</phrase> at time
+performing synchronic flow processing on the intermediate
+synchronic document at time
<code>T<sub>k</sub></code> differs from the set of glyph areas that
would be produced by
-<phrase diff="del">formatting the content</phrase><phrase
-diff="add">performing synchronic flow processing on the intermediate
-synchronic document</phrase> at time
+performing synchronic flow processing on the intermediate
+synchronic document at time
<code>T<sub>k+1</sub></code> in any of the following ways:</p>
<ulist>
<item><p>the number of glyph areas are different;</p></item>
@@ -8848,12 +8759,12 @@
region.</p>
<div3 id="flowIntervalFillTiming">
<head>Computed Fill Timing Interval</head>
-<p>The computed fill timing interval<phrase
-diff="add"> from time <code>T<sub>k</sub></code> up to but not
-including <code>T<sub>k+1</sub></code></phrase> is determined as
-follows<phrase diff="add">, where the meaning of
+<p>The computed fill timing interval
+from time <code>T<sub>k</sub></code> up to but not
+including <code>T<sub>k+1</sub></code> is determined as
+follows, where the meaning of
<code>T<sub>k</sub></code> and <code>T<sub>k+1</sub></code> is as
-described above</phrase>:</p>
+described above:</p>
<olist>
<item><p>If the value of the <emph>fill interval</emph> parameter is a
definite duration, then use this duration as the computed fill
@@ -8866,22 +8777,22 @@
<code>auto</code>, then the computed fill interval is equal to the
difference between the time coordinate associated with the most
temporally prior beginning point of an active duration of some content
-unit present in the flow buffer<phrase diff="add"> at time
-<code>T<sub>k</sub></code></phrase> and the most temporally subsequent
+unit present in the flow buffer at time
+<code>T<sub>k</sub></code> and the most temporally subsequent
ending point of an active duration of some content unit present in the
-flow buffer<phrase diff="add"> at time
-<code>T<sub>k</sub></code></phrase> divided by the number of fill
-units currently available in the flow buffer<phrase diff="add"> at
-time <code>T<sub>k</sub></code></phrase>.</p></item>
+flow buffer at time
+<code>T<sub>k</sub></code> divided by the number of fill
+units currently available in the flow buffer at
+time <code>T<sub>k</sub></code>.</p></item>
</olist>
</div3>
<div3 id="flowIntervalClearTiming">
<head>Computed Clear Timing Interval</head>
-<p>The computed clear timing interval<phrase diff="add"> from time
+<p>The computed clear timing interval from time
<code>T<sub>k</sub></code> up to but not including
-<code>T<sub>k+1</sub></code></phrase> is determined as follows<phrase
-diff="add">, where the meaning of <code>T<sub>k</sub></code> and
-<code>T<sub>k+1</sub></code> is as described above</phrase>:</p>
+<code>T<sub>k+1</sub></code> is determined as follows,
+where the meaning of <code>T<sub>k</sub></code> and
+<code>T<sub>k+1</sub></code> is as described above:</p>
<olist>
<item><p>If the value of the <emph>clear interval</emph> parameter is a
definite duration, then use this duration as the computed clear
@@ -8893,13 +8804,13 @@
<code>auto</code>, then the computed clear interval is equal to the
difference between the time coordinate associated with the most
temporally prior beginning point of an active duration of some content
-unit present in the presentation region<phrase diff="add"> at time
-<code>T<sub>k</sub></code></phrase> and the most temporally subsequent
+unit present in the presentation region at time
+<code>T<sub>k</sub></code> and the most temporally subsequent
ending point of an active duration of some content unit present in the
-presentation region<phrase diff="add"> at time
-<code>T<sub>k</sub></code></phrase> divided by the number of clear
-units currently available in the presentation region<phrase
-diff="add"> at time <code>T<sub>k</sub></code></phrase>.</p></item>
+presentation region at time
+<code>T<sub>k</sub></code> divided by the number of clear
+units currently available in the presentation region
+at time <code>T<sub>k</sub></code>.</p></item>
</olist>
</div3>
</div2>
@@ -8921,11 +8832,10 @@
and to its corresponding formatted content. In the context of the
presentation region, fill, reflow, and clear operations operate on
formatted content units
-(<phrase diff="chg">glyph and line areas</phrase>);
+(glyph and line areas);
however, in the context of the flow buffer, fill, reflow, and clear
operations operate on logical content units
-(character information items<phrase diff="del"> and element information
-items – <code>fo:inline</code> and <code>fo:block</code></phrase>).
+(character information items).
Because logical content units and formatted content units are
deterministically related to one another, an operation upon logical
units can always be described in terms of operations on formatted
@@ -8940,7 +8850,7 @@
single glyph area may correspond to multiple character information
items.</p>
</note>
-<p diff="add">For the purpose of performing line breaking in the
+<p>For the purpose of performing line breaking in the
context of dynamic flow processing, fill, reflow, and clear flow unit
boundaries must be interpreted as potential legal line break opportunity
regardless of other constraints.</p>
@@ -8948,12 +8858,12 @@
presentation region, the direction of (apparent)
translation of formatted content is determined by the nature of the
affected formatted content element. If the affected formatted content
-unit is a glyph<phrase diff="del"> or inline</phrase> area,
+unit is a glyph area,
then it is translated in the inline
progression direction that applies to the nearest immediate ancestor
inline or block area, and it is translated in a direction towards the
start edge of this ancestor area. If the affected formatted content
-unit is a line<phrase diff="del"> or block area</phrase>,
+unit is a line,
then it is translated in the block
progression direction that applies to the nearest immediate ancestor
block, and it is translated in a direction towards the before edge of
@@ -8967,14 +8877,14 @@
<p>A <emph>fill operation</emph> causes the following ordered steps
to be performed:</p>
<olist>
-<item><p diff="add">reset the <emph>last fill time</emph> to the
+<item><p>reset the <emph>last fill time</emph> to the
current value of the flow timers timeline;</p></item>
<item><p>remove sufficient logical content from the beginning of the
<emph>flow buffer</emph> to constitute (or compose) a <emph>fill
unit</emph>;</p> </item>
<item><p>format the content removed from the <emph>flow buffer</emph>
in the previous step in order to create a sequence of glyph areas or a
-sequence of <phrase diff="del">(full or partial measure) </phrase>line
+sequence of line
areas each containing a sequence of glyph areas;</p></item>
<item><p>append the sequence of areas produced in the previous step to
the sequence of areas currently associated with the presentation
@@ -8982,11 +8892,10 @@
and new line areas are appended to the sequence of line
areas;</p></item>
<item><p>cause the newly appended areas to be made visible according
-to the <emph>fill style</emph> state parameter in force<phrase
-diff="chg">;</phrase></p></item>
-<item><p diff="add">if the clear timer is not active, then reset the
+to the <emph>fill style</emph> state parameter in force;</p></item>
+<item><p>if the clear timer is not active, then reset the
clear timer to the current value of the <emph>computed clear interval</emph>;</p></item>
-<item><p diff="add">reset the fill timer to the
+<item><p>reset the fill timer to the
current value of the <emph>computed fill interval</emph>.</p></item>
</olist>
<note role="elaboration">
@@ -9006,8 +8915,8 @@
to be performed:</p>
<olist>
<item>
-<p>translate <phrase diff="chg">glyph areas or
-line areas</phrase> that correspond with a <emph>reflow
+<p>translate glyph areas or
+line areas that correspond with a <emph>reflow
unit</emph> of formatted content that follows (in inline or block
progression dimension order) the space cleared by the immediately
preceding <emph>clear operation</emph> to a new position such that the
@@ -9020,11 +8929,11 @@
<note role="elaboration">
<p>If a reflow unit is based on logical content units, then "reflow
unit of formatted content" refers to the logical content that
-generates the <phrase diff="chg">glyph and line areas</phrase> of
+generates the glyph and line areas of
formatted content that are being translated within the presentation
region. In contrast, if a reflow unit is based on formatted content
units, then "reflow unit of formatted content" refers directly to the
-generated <phrase diff="chg">glyph and line areas</phrase> of
+generated glyph and line areas of
formatted content.</p>
</note>
</div3>
@@ -9033,11 +8942,11 @@
<p>A <emph>clear operation</emph> causes the following ordered steps
to be performed:</p>
<olist>
-<item><p diff="add">reset the <emph>last clear time</emph> to the
+<item><p>reset the <emph>last clear time</emph> to the
current value of the flow timers timeline;</p></item>
<item>
-<p>remove <phrase diff="chg">glyph areas or
-line areas</phrase> that correspond with a <emph>clear unit</emph> of
+<p>remove glyph areas or
+line areas that correspond with a <emph>clear unit</emph> of
formatted content from the starting edge or the before edge of the
presentation region in inline or block progression direction,
respectively, applying the <emph>clear style</emph> state parameter in
@@ -9047,14 +8956,14 @@
<note role="elaboration">
<p>If a clear unit is based on logical content units, then "clear unit
of formatted content" refers to the logical content that generates the
-<phrase diff="chg">glyph and line areas</phrase> of formatted content
+glyph and line areas of formatted content
that are being cleared from the presentation region. In contrast, if a
clear unit is based on formatted content units, then "clear unit of
-formatted content" refers directly to the generated <phrase
-diff="chg">glyph and line areas</phrase> of formatted content.</p>
-</note>
-</div3>
-<div3 id="flowOperationCombined" diff="add">
+formatted content" refers directly to the generated
+glyph and line areas of formatted content.</p>
+</note>
+</div3>
+<div3 id="flowOperationCombined">
<head>Combined Flow Operation</head>
<p>A combined flow operation causes the following ordered steps to be performed:</p>
<olist>
@@ -9102,10 +9011,10 @@
simultaneously if the (logically, but not necesesarily temporally)
prior operation would create sufficient space in the presentation
region to accept the subsequent unit of formatted content.</p></note>
-<p diff="add">When resetting a flow timer, the <emph>dynamic flow
+<p>When resetting a flow timer, the <emph>dynamic flow
lock</emph> must first be acquired prior to changing the flow timer's
value, and must be released immediately after making the change.</p>
-<div3 id="flowTimerFill" diff="chg">
+<div3 id="flowTimerFill">
<head>Fill Timer</head>
<p>The fill timer is used to pace the addition of formatted content to the
presentation region undergoing dynamic flow processing.</p>
@@ -9143,7 +9052,7 @@
<item><p>release <emph>dynamic flow lock</emph>.</p></item>
</olist>
</div3>
-<div3 id="flowTimerClear" diff="chg">
+<div3 id="flowTimerClear">
<head>Clear Timer</head>
<p>The clear timer is used to pace the removal of formatted content from the
presentation region undergoing dynamic flow processing.</p>
@@ -9776,21 +9685,6 @@
href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
-<div3 id="feature-dynamicFlow-block" diff="del">
-<head>#dynamicFlow-block</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-block</code> feature if it recognizes and
-is capable of transforming the flow unit <code>block</code> as
-defined by <specref ref="style-value-flowFunction"/> when used with the
-<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
-attribute.</p>
-<p>A TT AF presentation processor supports the
-<code>#dynamicFlow-block</code> feature if it implements
-presentation semantic support for the flow unit <code>block</code> as
-defined by <specref ref="style-value-flowFunction"/> when used with the
-<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
-attribute.</p>
-</div3>
<div3 id="feature-dynamicFlow-character">
<head>#dynamicFlow-character</head>
<p>A TT AF transformation processor supports the
@@ -9807,31 +9701,31 @@
attribute.</p>
</div3>
<div3 id="feature-dynamicFlow-clear">
-<head>#dynamicFlow-<phrase diff="chg">clear</phrase></head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-<phrase diff="chg">clear</phrase></code> feature if it recognizes and
-is capable of transforming the flow interval function <code><phrase diff="chg">clear</phrase>(..)</code> as
+<head>#dynamicFlow-clear</head>
+<p>A TT AF transformation processor supports the
+<code>#dynamicFlow-clear</code> feature if it recognizes and
+is capable of transforming the flow interval function <code>clear(..)</code> as
defined by <specref ref="style-value-flowIntervalFunction"/> when used with the
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
<p>A TT AF presentation processor supports the
-<code>#dynamicFlow-<phrase diff="chg">clear</phrase></code> feature if it implements
-presentation semantic support for the flow interval function <code><phrase diff="chg">clear</phrase>(..)</code> as
+<code>#dynamicFlow-clear</code> feature if it implements
+presentation semantic support for the flow interval function <code>clear(..)</code> as
defined by <specref ref="style-value-flowFunction"/> when used with the
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
<div3 id="feature-dynamicFlow-fill">
-<head>#dynamicFlow-<phrase diff="chg">fill</phrase></head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-<phrase diff="chg">fill</phrase></code> feature if it recognizes and
-is capable of transforming the flow interval function <code><phrase diff="chg">fill</phrase>(..)</code> as
+<head>#dynamicFlow-fill</head>
+<p>A TT AF transformation processor supports the
+<code>#dynamicFlow-fill</code> feature if it recognizes and
+is capable of transforming the flow interval function <code>fill(..)</code> as
defined by <specref ref="style-value-flowIntervalFunction"/> when used with the
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
<p>A TT AF presentation processor supports the
-<code>#dynamicFlow-<phrase diff="chg">fill</phrase></code> feature if it implements
-presentation semantic support for the flow interval function <code><phrase diff="chg">fill</phrase>(..)</code> as
+<code>#dynamicFlow-fill</code> feature if it implements
+presentation semantic support for the flow interval function <code>fill(..)</code> as
defined by <specref ref="style-value-flowFunction"/> when used with the
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
@@ -9866,21 +9760,6 @@
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
-<div3 id="feature-dynamicFlow-inline" diff="del">
-<head>#dynamicFlow-inline</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-inline</code> feature if it recognizes and
-is capable of transforming the flow unit <code>inline</code> as
-defined by <specref ref="style-value-flowFunction"/> when used with the
-<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
-attribute.</p>
-<p>A TT AF presentation processor supports the
-<code>#dynamicFlow-inline</code> feature if it implements
-presentation semantic support for the flow unit <code>inline</code> as
-defined by <specref ref="style-value-flowFunction"/> when used with the
-<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
-attribute.</p>
-</div3>
<div3 id="feature-dynamicFlow-jump">
<head>#dynamicFlow-jump</head>
<p>A TT AF transformation processor supports the
@@ -10306,7 +10185,7 @@
expression.
</p>
</div3>
-<div3 id="feature-lineBreak-uax14" diff="add">
+<div3 id="feature-lineBreak-uax14">
<head>#lineBreak-uax14</head>
<p>A TT AF transformation processor supports the
<code>#lineBreak-uax14</code> feature if it recognizes and is capable of
@@ -10523,7 +10402,7 @@
</div3>
<div3 id="feature-presentation">
<head>#presentation</head>
-<p diff="chg">A TT AF processor supports the
+<p>A TT AF processor supports the
<code>#presentation</code> feature if it
(1) satisfies the generic processor criteria defined by
<specref ref="conformance-generic-processor"/>,
@@ -10531,7 +10410,7 @@
semantics defined by <specref ref="semantics-region-layout"/> and
<specref ref="semantics-line-layout"/>, respectively, and
(3) implements presentation semantics for the following features:</p>
-<ulist diff="add">
+<ulist>
<item><p><loc href="#content"><code>#content</code></loc></p></item>
<item><p><loc href="#core"><code>#core</code></loc></p></item>
<item><p><loc href="#profile"><code>#profile</code></loc></p></item>
@@ -10539,7 +10418,7 @@
<item><p><loc href="#time-offset"><code>#time-offset</code></loc></p></item>
<item><p><loc href="#timing"><code>#timing</code></loc></p></item>
</ulist>
-<p diff="add">
+<p>
In addition, a TT AF processor that supports the
<code>#presentation</code> feature should satisfy the user agent
accessibility guidelines specified by <bibref ref="uaag"/>.</p>
@@ -11013,12 +10892,12 @@
</div3>
<div3 id="feature-transformation">
<head>#transformation</head>
-<p diff="chg">A TT AF processor supports the
+<p>A TT AF processor supports the
<code>#transformation</code> feature if it
(1) satisfies the generic processor criteria defined by
-<specref ref="conformance-generic-processor"/>,
+<specref ref="conformance-generic-processor"/> and
(2) implements transformation semantics for the following features:</p>
-<ulist diff="add">
+<ulist>
<item><p><loc href="#content"><code>#content</code></loc></p></item>
<item><p><loc href="#core"><code>#core</code></loc></p></item>
<item><p><loc href="#profile"><code>#profile</code></loc></p></item>
@@ -11259,11 +11138,11 @@
<tr>
<td><loc href="#feature-color"><code>#color</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-content"><code>#content</code></loc></td>
-<td><phrase diff="chg">M</phrase></td>
+<td>M</td>
<td>M</td>
</tr>
<tr>
@@ -11284,12 +11163,12 @@
<tr>
<td><loc href="#feature-display-block"><code>#display-block</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-display-inline"><code>#display-inline</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-display-region"><code>#display-region</code></loc></td>
@@ -11307,22 +11186,17 @@
<td>O</td>
</tr>
<tr>
-<td><phrase diff="del"><loc href="#feature-dynamicFlow-block"><code>#dynamicFlow-block</code></loc></phrase></td>
-<td><phrase diff="del">O</phrase></td>
-<td><phrase diff="del">O</phrase></td>
-</tr>
-<tr>
<td><loc href="#feature-dynamicFlow-character"><code>#dynamicFlow-character</code></loc></td>
<td>O</td>
<td>O</td>
</tr>
<tr>
-<td><loc href="#feature-dynamicFlow-clear"><code>#dynamicFlow-<phrase diff="chg">clear</phrase></code></loc></td>
-<td>O</td>
-<td>O</td>
-</tr>
-<tr>
-<td><loc href="#feature-dynamicFlow-fill"><code>#dynamicFlow-<phrase diff="chg">fill</phrase></code></loc></td>
+<td><loc href="#feature-dynamicFlow-clear"><code>#dynamicFlow-clear</code></loc></td>
+<td>O</td>
+<td>O</td>
+</tr>
+<tr>
+<td><loc href="#feature-dynamicFlow-fill"><code>#dynamicFlow-fill</code></loc></td>
<td>O</td>
<td>O</td>
</tr>
@@ -11337,11 +11211,6 @@
<td>O</td>
</tr>
<tr>
-<td><phrase diff="del"><loc href="#feature-dynamicFlow-inline"><code>#dynamicFlow-inline</code></loc></phrase></td>
-<td><phrase diff="del">O</phrase></td>
-<td><phrase diff="del">O</phrase></td>
-</tr>
-<tr>
<td><loc href="#feature-dynamicFlow-jump"><code>#dynamicFlow-jump</code></loc></td>
<td>O</td>
<td>O</td>
@@ -11379,7 +11248,7 @@
<tr>
<td><loc href="#feature-extent"><code>#extent</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-fontFamily"><code>#fontFamily</code></loc></td>
@@ -11404,7 +11273,7 @@
<tr>
<td><loc href="#feature-fontSize-anisomorphic"><code>#fontSize-anisomorphic</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></loc></td>
@@ -11419,7 +11288,7 @@
<tr>
<td><loc href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-fontWeight"><code>#fontWeight</code></loc></td>
@@ -11429,7 +11298,7 @@
<tr>
<td><loc href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-frameRate"><code>#frameRate</code></loc></td>
@@ -11454,7 +11323,7 @@
<tr>
<td><loc href="#feature-length-cell"><code>#length-cell</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-length-em"><code>#length-em</code></loc></td>
@@ -11479,12 +11348,12 @@
<tr>
<td><loc href="#feature-length-pixel"><code>#length-pixel</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-length-positive"><code>#length-positive</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-length-real"><code>#length-real</code></loc></td>
@@ -11492,9 +11361,9 @@
<td>O</td>
</tr>
<tr>
-<td><phrase diff="add"><loc href="#feature-lineBreak-uax14"><code>#lineBreak-uax14</code></loc></phrase></td>
-<td><phrase diff="add">O</phrase></td>
-<td><phrase diff="add">O</phrase></td>
+<td><loc href="#feature-lineBreak-uax14"><code>#lineBreak-uax14</code></loc></td>
+<td>O</td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-lineHeight"><code>#lineHeight</code></loc></td>
@@ -11614,7 +11483,7 @@
<tr>
<td><loc href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-styling-inheritance-region"><code>#styling-inheritance-region</code></loc></td>
@@ -11624,7 +11493,7 @@
<tr>
<td><loc href="#feature-styling-inline"><code>#styling-inline</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-styling-nested"><code>#styling-nested</code></loc></td>
@@ -11649,7 +11518,7 @@
<tr>
<td><loc href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></loc></td>
<td>O</td>
-<td><phrase diff="chg">O</phrase></td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-textAlign-relative"><code>#textAlign-relative</code></loc></td>
@@ -11723,7 +11592,7 @@
</tr>
<tr>
<td><loc href="#feature-time-offset"><code>#time-offset</code></loc></td>
-<td><phrase diff="chg">M</phrase></td>
+<td>M</td>
<td>M</td>
</tr>
<tr>
@@ -11738,7 +11607,7 @@
</tr>
<tr>
<td><loc href="#feature-timing"><code>#timing</code></loc></td>
-<td><phrase diff="chg">M</phrase></td>
+<td>M</td>
<td>M</td>
</tr>
<tr>
@@ -11826,13 +11695,13 @@
<td><phrase role="strong">Comments</phrase></td>
</tr>
<tr>
-<td><phrase diff="add"><loc href="#feature-content"><code>#content</code></loc></phrase></td>
-<td><phrase diff="add">
+<td><loc href="#feature-content"><code>#content</code></loc></td>
+<td>
<loc href="#document-structure-vocabulary-body"><el>body</el></loc>,
<loc href="#content-vocabulary-div"><el>div</el></loc>,
<loc href="#content-vocabulary-p"><el>p</el></loc>,
<loc href="#content-vocabulary-span"><el>span</el></loc>,
-<loc href="#content-vocabulary-br"><el>br</el></loc></phrase>
+<loc href="#content-vocabulary-br"><el>br</el></loc>
</td>
</tr>
<tr>
@@ -11856,15 +11725,15 @@
</tr>
<tr>
-<td><phrase diff="add"><loc href="#feature-time-offset"><code>#time-offset</code></loc></phrase></td>
+<td><loc href="#feature-time-offset"><code>#time-offset</code></loc></td>
<td></td>
</tr>
<tr>
-<td><phrase diff="add"><loc href="#feature-timing"><code>#timing</code></loc></phrase></td>
-<td><phrase diff="add">
+<td><loc href="#feature-timing"><code>#timing</code></loc></td>
+<td>
<loc href="#timing-attribute-begin">@<att>begin</att></loc>,
<loc href="#timing-attribute-dur">@<att>dur</att></loc>,
-<loc href="#timing-attribute-end">@<att>end</att></loc></phrase>
+<loc href="#timing-attribute-end">@<att>end</att></loc>
</td>
</tr>
<tr>
@@ -11891,10 +11760,6 @@
<td><phrase role="strong">Comments</phrase></td>
</tr>
<tr>
-<td><phrase diff="del"><loc href="#feature-color"><code>#color</code></loc></phrase></td>
-<td><phrase diff="del"><loc href="#style-attribute-color">@<att>tts:color</att></loc></phrase></td>
-</tr>
-<tr>
<td><loc href="#feature-content"><code>#content</code></loc></td>
<td>
<loc href="#document-structure-vocabulary-body"><el>body</el></loc>,
@@ -11913,69 +11778,6 @@
</td>
</tr>
<tr>
-<td><phrase diff="del"><loc href="#feature-display-block"><code>#display-block</code></loc></phrase></td>
-<td><phrase diff="del"><loc href="#style-attribute-display">@<att>tts:display</att></loc>
-applied to
-<loc href="#document-structure-vocabulary-body"><el>body</el></loc>,
-<loc href="#content-vocabulary-div"><el>div</el></loc>,
-<loc href="#content-vocabulary-p"><el>p</el></loc></phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-display-inline"><code>#display-inline</code></loc></phrase></td>
-<td><phrase diff="del"><loc href="#style-attribute-display">@<att>tts:display</att></loc>
-applied to
-<loc href="#content-vocabulary-span"><el>span</el></loc>,
-<loc href="#content-vocabulary-br"><el>br</el></loc></phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-extent"><code>#extent</code></loc></phrase></td>
-<td><phrase diff="del"><loc href="#style-attribute-extent">@<att>tts:extent</att></loc>
-applied to <loc href="#document-structure-vocabulary-tt"><el>tt</el></loc></phrase></td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-fontSize-isomorphic"><code>#fontSize-isomorphic</code></loc></phrase></td>
-<td><phrase diff="del">
-<loc href="#style-attribute-fontSize">@<att>tts:fontSize</att></loc>=
-"<code><loc href="#style-value-length"><length></loc></code>"</phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-fontStyle-italic"><code>#fontStyle-italic</code></loc></phrase></td>
-<td><phrase diff="del">
-<loc href="#style-attribute-fontStyle">@<att>tts:fontStyle</att></loc>=
-"<code>italic</code>"</phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-fontWeight-bold"><code>#fontWeight-bold</code></loc></phrase></td>
-<td><phrase diff="del">
-<loc href="#style-attribute-fontWeight">@<att>tts:fontWeight</att></loc>=
-"<code>bold</code>"</phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-length-cell"><code>#length-cell</code></loc></phrase></td>
-<td><phrase diff="del">
-<code><loc href="#style-value-length"><length></loc></code> :
-<code><loc href="#style-value-integer"><integer></loc>c</code></phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-length-pixel"><code>#length-pixel</code></loc></phrase></td>
-<td><phrase diff="del">
-<code><loc href="#style-value-length"><length></loc></code> :
-<code><loc href="#style-value-integer"><integer></loc>px</code></phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-length-positive"><code>#length-positive</code></loc></phrase></td>
-<td><phrase diff="del">
-<code><loc href="#style-value-length"><length></loc></code>≥0</phrase>
-</td>
-</tr>
-<tr>
<td><loc href="#feature-profile"><code>#profile</code></loc></td>
<td></td>
</tr>
@@ -11991,21 +11793,6 @@
</td>
</tr>
<tr>
-<td><phrase diff="del"><loc href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></loc></phrase></td>
-<td></td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-styling-inline"><code>#styling-inline</code></loc></phrase></td>
-<td></td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></loc></phrase></td>
-<td><phrase diff="del">
-<loc href="#style-attribute-textAlign">@<att>tts:textAlign</att></loc>=
-"<code>left</code>|<code>center</code>|<code>right</code>"</phrase>
-</td>
-</tr>
-<tr>
<td><loc href="#feature-time-offset"><code>#time-offset</code></loc></td>
<td></td>
</tr>
@@ -12017,23 +11804,6 @@
<loc href="#timing-attribute-end">@<att>end</att></loc>
</td>
</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-visibility-block"><code>#visibility-block</code></loc></phrase></td>
-<td><phrase diff="del"><loc href="#style-attribute-visibility">@<att>tts:visibility</att></loc>
-applied to
-<loc href="#document-structure-vocabulary-body"><el>body</el></loc>,
-<loc href="#content-vocabulary-div"><el>div</el></loc>,
-<loc href="#content-vocabulary-p"><el>p</el></loc></phrase>
-</td>
-</tr>
-<tr>
-<td><phrase diff="del"><loc href="#feature-visibility-inline"><code>#visibility-inline</code></loc></phrase></td>
-<td><phrase diff="del"><loc href="#style-attribute-visibility">@<att>tts:visibility</att></loc>
-applied to
-<loc href="#content-vocabulary-span"><el>span</el></loc>,
-<loc href="#content-vocabulary-br"><el>br</el></loc></phrase>
-</td>
-</tr>
</tbody>
</table>
</div2>
@@ -12081,26 +11851,26 @@
<ulist>
<item><p><specref ref="profile-dfxp-transformation"/></p></item>
<item><p><specref ref="profile-dfxp-presentation"/></p></item>
-<item><p diff="add"><specref ref="profile-dfxp-full"/></p></item>
+<item><p><specref ref="profile-dfxp-full"/></p></item>
</ulist>
<p>Each TT AF profile is defined in terms of a TT AF Profile Definition Document,
which is expressed as an XML document wherein the root element adheres to
<specref ref="parameter-vocabulary-profile"/>.</p>
<div2 id="profile-dfxp-transformation">
<head>DFXP Transformation Profile</head>
-<p diff="add">The DFXP Transformation Profile is intended to be used to
+<p>The DFXP Transformation Profile is intended to be used to
express minimum compliance for transformation processing.</p>
-<eg xml:space="preserve"><phrase diff="chg">&profile-dfxp-transformation;</phrase></eg>
+<eg xml:space="preserve">&profile-dfxp-transformation;</eg>
</div2>
<div2 id="profile-dfxp-presentation">
<head>DFXP Presentation Profile</head>
-<p diff="add">The DFXP Presentation Profile is intended to be used to
+<p>The DFXP Presentation Profile is intended to be used to
express minimum compliance for presentation processing.</p>
-<eg xml:space="preserve"><phrase diff="chg">&profile-dfxp-presentation;</phrase></eg>
+<eg xml:space="preserve">&profile-dfxp-presentation;</eg>
</div2>
-<div2 id="profile-dfxp-full" diff="add">
+<div2 id="profile-dfxp-full">
<head>DFXP Full Profile</head>
-<p diff="add">The DFXP Full Profile is intended to be used to
+<p>The DFXP Full Profile is intended to be used to
express maximum compliance for both transformation and presentation processing.</p>
<eg xml:space="preserve">&profile-dfxp-full;</eg>
</div2>
@@ -12182,7 +11952,7 @@
1.0 (Fifth Edition)</titleref>, W3C Recommendation, 26 November 2008. (See
<xspecref href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</xspecref>.)
</bibl>
-<bibl id="xmlbase" key="XML Base" diff="add">Jonathan Marsh and Richard Tobin, Eds.,
+<bibl id="xmlbase" key="XML Base">Jonathan Marsh and Richard Tobin, Eds.,
<titleref href="http://www.w3.org/TR/2009/REC-xmlbase-20090128/">XML Base (Second Edition)</titleref>,
W3C Recommendation, 28 January 2009. (See
<xspecref href="http://www.w3.org/TR/2009/REC-xmlbase-20090128/">http://www.w3.org/TR/2009/REC-xmlbase-20090128/</xspecref>.)
@@ -12193,13 +11963,13 @@
<xspecref href="http://www.w3.org/TR/2005/REC-xml-id-20050909/">http://www.w3.org/TR/2005/REC-xml-id-20050909/</xspecref>.)
</bibl>
<bibl id="xml-media" key="XML Media">Makato Murata, Simon St. Laurent,
-Kan Khon<phrase diff="add">, Eds.</phrase>, <titleref
+Kan Khon, Eds., <titleref
href="http://www.rfc-editor.org/rfc/rfc3023.txt">XML Media Types</titleref>,
RFC 3023, January 2001, IETF.(See
<xspecref
href="http://www.rfc-editor.org/rfc/rfc3023.txt">http://www.rfc-editor.org/rfc/rfc3023.txt</xspecref>.)
</bibl>
-<bibl id="infoset" key="XML InfoSet">John Cowan and Richard Tobin<phrase diff="add">, Eds.</phrase>,
+<bibl id="infoset" key="XML InfoSet">John Cowan and Richard Tobin, Eds.,
<titleref href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">XML Information Set (Second Edition)</titleref>,
W3C Recommendation, 04 February 2004. (See
<xspecref href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</xspecref>.)
@@ -12237,7 +12007,7 @@
<inform-div1 id="other-references">
<head>Other References</head>
<blist>
-<bibl id="ccreq" key="CC-DECODER-REQ" diff="add">Norman Walsh, Ed.,
+<bibl id="ccreq" key="CC-DECODER-REQ">Norman Walsh, Ed.,
<titleref
href="http://edocket.access.gpo.gov/cfr_2005/octqtr/47cfr15.119.htm">Closed Caption Decoder
Requirements for Analog Television</titleref>,
@@ -12266,7 +12036,7 @@
interface – Part 5: Multimedia description schemes</titleref>,
International Organization for Standardization (ISO).
</bibl>
-<bibl id="nsstate" key="NSState" diff="add">Norman Walsh, Ed.,
+<bibl id="nsstate" key="NSState">Norman Walsh, Ed.,
<titleref
href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09.html">The Disposition
of Names in an XML Namespace</titleref>, TAG Finding, 9 January 2006. (See
@@ -12279,14 +12049,6 @@
August 2005. (See
<xspecref href="http://www.w3.org/TR/qaframe-spec/">http://www.w3.org/TR/qaframe-spec/</xspecref>.)
</bibl>
-<bibl id="scheme" key="SCHEME" diff="del">Guy Steele and Gerald Sussman,
-<titleref
-href="http://swiss.csail.mit.edu/projects/scheme/">Scheme Programming
-Environment</titleref>,
-Massachusetts Institute of Technology. (See
-<xspecref
-href="http://swiss.csail.mit.edu/projects/scheme/">http://swiss.csail.mit.edu/projects/scheme/</xspecref>.)
-</bibl>
<bibl id="smpte170m" key="SMPTE 170M">ANSI/SMPTE 170M,
<titleref
href="http://www.smpte.org/">Television – Composite Analog Video
@@ -14233,7 +13995,7 @@
<head>Changes from First Candidate Recommendation to Third Last Call
Working Draft</head>
<eg xml:space="preserve">
-<phrase diff="chg"><phrase role="strong">Technical Changes</phrase>
+<phrase role="strong">Technical Changes</phrase>
The following changes result in a technical change of the conformance
criteria, the normative abstract document type that is defined
@@ -14317,7 +14079,7 @@
* Remove style and metadata extension namespaces [<loc href="http://www.w3.org/AudioVideo/TT/tracker/issues/112">I-112</loc>].
* Clarify region association algorithm [<loc href="http://www.w3.org/AudioVideo/TT/tracker/issues/118">I-118</loc>].
-</phrase></eg>
+</eg>
</div2>
</inform-div1>
</back>