--- a/spec/ttaf1-dfxp.html Mon May 04 11:32:21 2009 +0000
+++ b/spec/ttaf1-dfxp.html Mon May 04 11:45:14 2009 +0000
@@ -98,6 +98,9 @@
3 <a href="#conformance">Conformance</a><br/>
3.1 <a href="#conformance-content">Content Conformance</a><br/>
3.2 <a href="#conformance-processor">Processor Conformance</a><br/>
+ 3.2.1 <a href="#conformance-generic-processor">Generic Processor Conformance</a><br/>
+ 3.2.2 <a href="#conformance-transformation-processor">Transformation Processor Conformance</a><br/>
+ 3.2.3 <a href="#conformance-presentation-processor">Presentation Processor Conformance</a><br/>
3.3 <a href="#claims">Claims</a><br/>
4 <a href="#doctypes">Document Types</a><br/>
4.1 <a href="#dfxp-content-doctype">DFXP Content</a><br/>
@@ -108,8 +111,13 @@
5.3.1 <a href="#core-vocabulary-overview">Core Catalog</a><br/>
5.3.2 <a href="#extension-vocabulary-overview">Extension Catalog</a><br/>
6 <a href="#parameters">Parameters</a><br/>
- 6.1 <a href="#parameters-element-vocabulary">Parameters Element Vocabulary</a><br/>
- 6.2 <a href="#parameters-attribute-vocabulary">Parameters Attribute Vocabulary</a><br/>
+ 6.1 <a href="#parameter-element-vocabulary">Parameter Element Vocabulary</a><br/>
+ 6.1.1 <a href="#parameter-vocabulary-profile">ttp:profile</a><br/>
+ 6.1.2 <a href="#parameter-vocabulary-features">ttp:features</a><br/>
+ 6.1.3 <a href="#parameter-vocabulary-feature">ttp:feature</a><br/>
+ 6.1.4 <a href="#parameter-vocabulary-extensions">ttp:extensions</a><br/>
+ 6.1.5 <a href="#parameter-vocabulary-extension">ttp:extension</a><br/>
+ 6.2 <a href="#parameter-attribute-vocabulary">Parameter Attribute Vocabulary</a><br/>
6.2.1 <a href="#parameter-attribute-cellResolution">ttp:cellResolution</a><br/>
6.2.2 <a href="#parameter-attribute-clockMode">ttp:clockMode</a><br/>
6.2.3 <a href="#parameter-attribute-frameRate">ttp:frameRate</a><br/>
@@ -267,13 +275,15 @@
C.1.2.6 <a href="#rnc-dfxp-document-module">Document Module</a><br/>
C.1.2.7 <a href="#rnc-dfxp-head-module">Header Module</a><br/>
C.1.2.8 <a href="#rnc-dfxp-layout-module">Layout Module</a><br/>
- C.1.2.9 <a href="#rnc-dfxp-metdata-module">Metadata Module</a><br/>
- C.1.2.10 <a href="#rnc-dfxp-metdata-items-module">Metadata Items Module</a><br/>
+ C.1.2.9 <a href="#rnc-dfxp-metadata-module">Metadata Module</a><br/>
+ C.1.2.10 <a href="#rnc-dfxp-metadata-items-module">Metadata Items Module</a><br/>
C.1.2.11 <a href="#rnc-dfxp-metadata-attribs-module">Metadata Attributes Module</a><br/>
- C.1.2.12 <a href="#rnc-dfxp-parameter-attribs-module">Parameter Attributes Module</a><br/>
- C.1.2.13 <a href="#rnc-dfxp-styling-attribs-module">Styling Attributes Module</a><br/>
- C.1.2.14 <a href="#rnc-dfxp-styling-module">Styling Module</a><br/>
- C.1.2.15 <a href="#rnc-dfxp-timing-attribs-module">Timing Attributes Module</a><br/>
+ C.1.2.12 <a href="#rnc-dfxp-parameters-module">Parameters Module</a><br/>
+ C.1.2.13 <a href="#rnc-dfxp-parameter-items-module">Parameter Items Module</a><br/>
+ C.1.2.14 <a href="#rnc-dfxp-parameter-attribs-module">Parameter Attributes Module</a><br/>
+ C.1.2.15 <a href="#rnc-dfxp-styling-attribs-module">Styling Attributes Module</a><br/>
+ C.1.2.16 <a href="#rnc-dfxp-styling-module">Styling Module</a><br/>
+ C.1.2.17 <a href="#rnc-dfxp-timing-attribs-module">Timing Attributes Module</a><br/>
C.2 <a href="#dfxp-schema-xsd">XML Schema Definition (XSD) Schema</a><br/>
C.2.1 <a href="#xsd-dfxp-driver-schema">Driver</a><br/>
C.2.2 <a href="#xsd-dfxp-modules">Modules</a><br/>
@@ -284,14 +294,16 @@
C.2.2.5 <a href="#xsd-dfxp-document-module">Document Module</a><br/>
C.2.2.6 <a href="#xsd-dfxp-head-module">Header Module</a><br/>
C.2.2.7 <a href="#xsd-dfxp-layout-module">Layout Module</a><br/>
- C.2.2.8 <a href="#xsd-dfxp-metdata-module">Metadata Module</a><br/>
- C.2.2.9 <a href="#xsd-dfxp-metdata-items-module">Metadata Items Module</a><br/>
+ C.2.2.8 <a href="#xsd-dfxp-metadata-module">Metadata Module</a><br/>
+ C.2.2.9 <a href="#xsd-dfxp-metadata-items-module">Metadata Items Module</a><br/>
C.2.2.10 <a href="#xsd-dfxp-metadata-attribs-module">Metadata Attributes Module</a><br/>
- C.2.2.11 <a href="#xsd-dfxp-parameter-attribs-module">Parameter Attributes Module</a><br/>
- C.2.2.12 <a href="#xsd-dfxp-styling-attribs-module">Styling Attributes Module</a><br/>
- C.2.2.13 <a href="#xsd-dfxp-styling-module">Styling Module</a><br/>
- C.2.2.14 <a href="#xsd-dfxp-timing-attribs-module">Timing Attributes Module</a><br/>
- C.2.2.15 <a href="#xsd-dfxp-xml-attrs-module">XML Attributes Module</a><br/>
+ C.2.2.11 <a href="#xsd-dfxp-parameters-module">Parameters Module</a><br/>
+ C.2.2.12 <a href="#xsd-dfxp-parameter-items-module">Parameter Items Module</a><br/>
+ C.2.2.13 <a href="#xsd-dfxp-parameter-attribs-module">Parameter Attributes Module</a><br/>
+ C.2.2.14 <a href="#xsd-dfxp-styling-attribs-module">Styling Attributes Module</a><br/>
+ C.2.2.15 <a href="#xsd-dfxp-styling-module">Styling Module</a><br/>
+ C.2.2.16 <a href="#xsd-dfxp-timing-attribs-module">Timing Attributes Module</a><br/>
+ C.2.2.17 <a href="#xsd-dfxp-xml-attrs-module">XML Attributes Module</a><br/>
D <a href="#media-type-registration">Media Type Registration</a><br/>
E <a href="#features">Features</a><br/>
E.1 <a href="#feature-designations">Feature Designations</a><br/>
@@ -313,130 +325,120 @@
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-barWipe">#dynamicFlow-barWipe</a><br/>
- E.1.20 <a href="#feature-dynamicFlow-block">#dynamicFlow-block</a><br/>
- E.1.21 <a href="#feature-dynamicFlow-character">#dynamicFlow-character</a><br/>
- E.1.22 <a href="#feature-dynamicFlow-fade">#dynamicFlow-fade</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-inter">#dynamicFlow-inter</a><br/>
- E.1.27 <a href="#feature-dynamicFlow-intra">#dynamicFlow-intra</a><br/>
- E.1.28 <a href="#feature-dynamicFlow-jump">#dynamicFlow-jump</a><br/>
- E.1.29 <a href="#feature-dynamicFlow-leftToRight">#dynamicFlow-leftToRight</a><br/>
- E.1.30 <a href="#feature-dynamicFlow-line">#dynamicFlow-line</a><br/>
- E.1.31 <a href="#feature-dynamicFlow-out">#dynamicFlow-out</a><br/>
- E.1.32 <a href="#feature-dynamicFlow-pixel">#dynamicFlow-pixel</a><br/>
- E.1.33 <a href="#feature-dynamicFlow-smooth">#dynamicFlow-smooth</a><br/>
- E.1.34 <a href="#feature-dynamicFlow-teletext">#dynamicFlow-teletext</a><br/>
- E.1.35 <a href="#feature-dynamicFlow-topToBottom">#dynamicFlow-topToBottom</a><br/>
- E.1.36 <a href="#feature-dynamicFlow-within">#dynamicFlow-within</a><br/>
- E.1.37 <a href="#feature-dynamicFlow-word">#dynamicFlow-word</a><br/>
- E.1.38 <a href="#feature-extent">#extent</a><br/>
- E.1.39 <a href="#feature-fontFamily">#fontFamily</a><br/>
- E.1.40 <a href="#feature-fontFamily-generic">#fontFamily-generic</a><br/>
- E.1.41 <a href="#feature-fontFamily-non-generic">#fontFamily-non-generic</a><br/>
- E.1.42 <a href="#feature-fontSize">#fontSize</a><br/>
- E.1.43 <a href="#feature-fontSize-anisomorphic">#fontSize-anisomorphic</a><br/>
- E.1.44 <a href="#feature-fontSize-isomorphic">#fontSize-isomorphic</a><br/>
- E.1.45 <a href="#feature-fontStyle">#fontStyle</a><br/>
- E.1.46 <a href="#feature-fontStyle-italic">#fontStyle-italic</a><br/>
- E.1.47 <a href="#feature-fontWeight">#fontWeight</a><br/>
- E.1.48 <a href="#feature-fontWeight-bold">#fontWeight-bold</a><br/>
- E.1.49 <a href="#feature-frameRate">#frameRate</a><br/>
- E.1.50 <a href="#feature-frameRateMultiplier">#frameRateMultiplier</a><br/>
- E.1.51 <a href="#feature-layout">#layout</a><br/>
- E.1.52 <a href="#feature-length">#length</a><br/>
- E.1.53 <a href="#feature-length-cell">#length-cell</a><br/>
- E.1.54 <a href="#feature-length-em">#length-em</a><br/>
- E.1.55 <a href="#feature-length-integer">#length-integer</a><br/>
- E.1.56 <a href="#feature-length-negative">#length-negative</a><br/>
- E.1.57 <a href="#feature-length-percentage">#length-percentage</a><br/>
- E.1.58 <a href="#feature-length-pixel">#length-pixel</a><br/>
- E.1.59 <a href="#feature-length-positive">#length-positive</a><br/>
- E.1.60 <a href="#feature-length-real">#length-real</a><br/>
- E.1.61 <a href="#feature-lineHeight">#lineHeight</a><br/>
- E.1.62 <a href="#feature-markerMode">#markerMode</a><br/>
- E.1.63 <a href="#feature-metadata">#metadata</a><br/>
- E.1.64 <a href="#feature-nested-div">#nested-div</a><br/>
- E.1.65 <a href="#feature-nested-span">#nested-span</a><br/>
- E.1.66 <a href="#feature-opacity">#opacity</a><br/>
- E.1.67 <a href="#feature-origin">#origin</a><br/>
- E.1.68 <a href="#feature-overflow">#overflow</a><br/>
- E.1.69 <a href="#feature-overflow-dynamic">#overflow-dynamic</a><br/>
- E.1.70 <a href="#feature-padding">#padding</a><br/>
- E.1.71 <a href="#feature-padding-1">#padding-1</a><br/>
- E.1.72 <a href="#feature-padding-2">#padding-2</a><br/>
- E.1.73 <a href="#feature-padding-3">#padding-3</a><br/>
- E.1.74 <a href="#feature-padding-4">#padding-4</a><br/>
- E.1.75 <a href="#feature-pixelAspectRatio">#pixelAspectRatio</a><br/>
- E.1.76 <a href="#feature-presentation">#presentation</a><br/>
- E.1.77 <a href="#feature-profile">#profile</a><br/>
- E.1.78 <a href="#feature-requiredExtensions">#requiredExtensions</a><br/>
- E.1.79 <a href="#feature-requiredFeatures">#requiredFeatures</a><br/>
- E.1.80 <a href="#feature-showBackground">#showBackground</a><br/>
- E.1.81 <a href="#feature-smpteMode">#smpteMode</a><br/>
- E.1.82 <a href="#feature-structure">#structure</a><br/>
- E.1.83 <a href="#feature-styling">#styling</a><br/>
- E.1.84 <a href="#feature-styling-chained">#styling-chained</a><br/>
- E.1.85 <a href="#feature-styling-inheritance-content">#styling-inheritance-content</a><br/>
- E.1.86 <a href="#feature-styling-inheritance-region">#styling-inheritance-region</a><br/>
- E.1.87 <a href="#feature-styling-inline">#styling-inline</a><br/>
- E.1.88 <a href="#feature-styling-nested">#styling-nested</a><br/>
- E.1.89 <a href="#feature-styling-referential">#styling-referential</a><br/>
- E.1.90 <a href="#feature-subFrameRate">#subFrameRate</a><br/>
- E.1.91 <a href="#feature-textAlign">#textAlign</a><br/>
- E.1.92 <a href="#feature-textAlign-absolute">#textAlign-absolute</a><br/>
- E.1.93 <a href="#feature-textAlign-relative">#textAlign-relative</a><br/>
- E.1.94 <a href="#feature-textDecoration">#textDecoration</a><br/>
- E.1.95 <a href="#feature-textDecoration-over">#textDecoration-over</a><br/>
- E.1.96 <a href="#feature-textDecoration-through">#textDecoration-through</a><br/>
- E.1.97 <a href="#feature-textDecoration-under">#textDecoration-under</a><br/>
- E.1.98 <a href="#feature-textOutline">#textOutline</a><br/>
- E.1.99 <a href="#feature-textOutline-blur">#textOutline-blur</a><br/>
- E.1.100 <a href="#feature-tickRate">#tickRate</a><br/>
- E.1.101 <a href="#feature-timeBase-clock">#timeBase-clock</a><br/>
- E.1.102 <a href="#feature-timeBase-media">#timeBase-media</a><br/>
- E.1.103 <a href="#feature-timeBase-smpte">#timeBase-smpte</a><br/>
- E.1.104 <a href="#feature-timeContainer">#timeContainer</a><br/>
- E.1.105 <a href="#feature-time-clock">#time-clock</a><br/>
- E.1.106 <a href="#feature-time-clock-with-frames">#time-clock-with-frames</a><br/>
- E.1.107 <a href="#feature-time-offset">#time-offset</a><br/>
- E.1.108 <a href="#feature-time-offset-with-frames">#time-offset-with-frames</a><br/>
- E.1.109 <a href="#feature-time-offset-with-ticks">#time-offset-with-ticks</a><br/>
- E.1.110 <a href="#feature-timing">#timing</a><br/>
- E.1.111 <a href="#feature-transformation">#transformation</a><br/>
- E.1.112 <a href="#feature-unicodeBidi">#unicodeBidi</a><br/>
- E.1.113 <a href="#feature-visibility">#visibility</a><br/>
- E.1.114 <a href="#feature-visibility-block">#visibility-block</a><br/>
- E.1.115 <a href="#feature-visibility-inline">#visibility-inline</a><br/>
- E.1.116 <a href="#feature-visibility-region">#visibility-region</a><br/>
- E.1.117 <a href="#feature-wrapOption">#wrapOption</a><br/>
- E.1.118 <a href="#feature-writingMode">#writingMode</a><br/>
- E.1.119 <a href="#feature-writingMode-vertical">#writingMode-vertical</a><br/>
- E.1.120 <a href="#feature-writingMode-horizontal">#writingMode-horizontal</a><br/>
- E.1.121 <a href="#feature-writingMode-horizontal-lr">#writingMode-horizontal-lr</a><br/>
- E.1.122 <a href="#feature-writingMode-horizontal-rl">#writingMode-horizontal-rl</a><br/>
- E.1.123 <a href="#feature-zIndex">#zIndex</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-glyph">#dynamicFlow-glyph</a><br/>
+ E.1.22 <a href="#feature-dynamicFlow-in">#dynamicFlow-in</a><br/>
+ E.1.23 <a href="#feature-dynamicFlow-inline">#dynamicFlow-inline</a><br/>
+ E.1.24 <a href="#feature-dynamicFlow-inter">#dynamicFlow-inter</a><br/>
+ E.1.25 <a href="#feature-dynamicFlow-intra">#dynamicFlow-intra</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-lineHeight">#lineHeight</a><br/>
+ E.1.57 <a href="#feature-markerMode">#markerMode</a><br/>
+ E.1.58 <a href="#feature-metadata">#metadata</a><br/>
+ E.1.59 <a href="#feature-nested-div">#nested-div</a><br/>
+ E.1.60 <a href="#feature-nested-span">#nested-span</a><br/>
+ E.1.61 <a href="#feature-opacity">#opacity</a><br/>
+ E.1.62 <a href="#feature-origin">#origin</a><br/>
+ E.1.63 <a href="#feature-overflow">#overflow</a><br/>
+ E.1.64 <a href="#feature-overflow-dynamic">#overflow-dynamic</a><br/>
+ E.1.65 <a href="#feature-padding">#padding</a><br/>
+ E.1.66 <a href="#feature-padding-1">#padding-1</a><br/>
+ E.1.67 <a href="#feature-padding-2">#padding-2</a><br/>
+ E.1.68 <a href="#feature-padding-3">#padding-3</a><br/>
+ E.1.69 <a href="#feature-padding-4">#padding-4</a><br/>
+ E.1.70 <a href="#feature-pixelAspectRatio">#pixelAspectRatio</a><br/>
+ E.1.71 <a href="#feature-presentation">#presentation</a><br/>
+ E.1.72 <a href="#feature-profile">#profile</a><br/>
+ E.1.73 <a href="#feature-rollUp">#rollUp</a><br/>
+ E.1.74 <a href="#feature-showBackground">#showBackground</a><br/>
+ E.1.75 <a href="#feature-smpteMode">#smpteMode</a><br/>
+ E.1.76 <a href="#feature-structure">#structure</a><br/>
+ E.1.77 <a href="#feature-styling">#styling</a><br/>
+ E.1.78 <a href="#feature-styling-chained">#styling-chained</a><br/>
+ E.1.79 <a href="#feature-styling-inheritance-content">#styling-inheritance-content</a><br/>
+ E.1.80 <a href="#feature-styling-inheritance-region">#styling-inheritance-region</a><br/>
+ E.1.81 <a href="#feature-styling-inline">#styling-inline</a><br/>
+ E.1.82 <a href="#feature-styling-nested">#styling-nested</a><br/>
+ E.1.83 <a href="#feature-styling-referential">#styling-referential</a><br/>
+ E.1.84 <a href="#feature-subFrameRate">#subFrameRate</a><br/>
+ E.1.85 <a href="#feature-textAlign">#textAlign</a><br/>
+ E.1.86 <a href="#feature-textAlign-absolute">#textAlign-absolute</a><br/>
+ E.1.87 <a href="#feature-textAlign-relative">#textAlign-relative</a><br/>
+ E.1.88 <a href="#feature-textDecoration">#textDecoration</a><br/>
+ E.1.89 <a href="#feature-textDecoration-over">#textDecoration-over</a><br/>
+ E.1.90 <a href="#feature-textDecoration-through">#textDecoration-through</a><br/>
+ E.1.91 <a href="#feature-textDecoration-under">#textDecoration-under</a><br/>
+ E.1.92 <a href="#feature-textOutline">#textOutline</a><br/>
+ E.1.93 <a href="#feature-textOutline-blur">#textOutline-blur</a><br/>
+ E.1.94 <a href="#feature-tickRate">#tickRate</a><br/>
+ E.1.95 <a href="#feature-timeBase-clock">#timeBase-clock</a><br/>
+ E.1.96 <a href="#feature-timeBase-media">#timeBase-media</a><br/>
+ E.1.97 <a href="#feature-timeBase-smpte">#timeBase-smpte</a><br/>
+ E.1.98 <a href="#feature-timeContainer">#timeContainer</a><br/>
+ E.1.99 <a href="#feature-time-clock">#time-clock</a><br/>
+ E.1.100 <a href="#feature-time-clock-with-frames">#time-clock-with-frames</a><br/>
+ E.1.101 <a href="#feature-time-offset">#time-offset</a><br/>
+ E.1.102 <a href="#feature-time-offset-with-frames">#time-offset-with-frames</a><br/>
+ E.1.103 <a href="#feature-time-offset-with-ticks">#time-offset-with-ticks</a><br/>
+ E.1.104 <a href="#feature-timing">#timing</a><br/>
+ E.1.105 <a href="#feature-transformation">#transformation</a><br/>
+ E.1.106 <a href="#feature-unicodeBidi">#unicodeBidi</a><br/>
+ E.1.107 <a href="#feature-visibility">#visibility</a><br/>
+ E.1.108 <a href="#feature-visibility-block">#visibility-block</a><br/>
+ E.1.109 <a href="#feature-visibility-inline">#visibility-inline</a><br/>
+ E.1.110 <a href="#feature-visibility-region">#visibility-region</a><br/>
+ E.1.111 <a href="#feature-wrapOption">#wrapOption</a><br/>
+ E.1.112 <a href="#feature-writingMode">#writingMode</a><br/>
+ E.1.113 <a href="#feature-writingMode-vertical">#writingMode-vertical</a><br/>
+ E.1.114 <a href="#feature-writingMode-horizontal">#writingMode-horizontal</a><br/>
+ E.1.115 <a href="#feature-writingMode-horizontal-lr">#writingMode-horizontal-lr</a><br/>
+ E.1.116 <a href="#feature-writingMode-horizontal-rl">#writingMode-horizontal-rl</a><br/>
+ E.1.117 <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/>
-G <a href="#references">References</a><br/>
-H <a href="#other-references">Other References</a> (Non-Normative)<br/>
-I <a href="#sample-code">Sample Code</a> (Non-Normative)<br/>
- I.1 <a href="#code-rxi">Reduced XML Infoset (RXI) – RXI.SCM</a><br/>
- I.2 <a href="#code-adi">Abstract Document Instance (ADI) – ADI.SCM</a><br/>
- I.3 <a href="#code-tir">Time Interval Resolver (TIR) – TIR.SCM</a><br/>
- I.4 <a href="#code-fox">Flow Object Transformer (FOX) – FOX.SCM</a><br/>
- I.5 <a href="#code-dtf">Dynamic Text Flow Processor (DTF) – DTF.SCM</a><br/>
- I.6 <a href="#code-run">Sample Compile, Load, and Run Session</a><br/>
+G <a href="#profiles">Profiles</a><br/>
+ G.1 <a href="#profile-dfxp-presentation">DFXP Presentation Profile</a><br/>
+ G.2 <a href="#profile-dfxp-transformation">DFXP Transformation Profile</a><br/>
+H <a href="#references">References</a><br/>
+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="#d3e18480">Element Derivation</a><br/>
- K.2 <a href="#d3e18864">Attribute Derivation</a><br/>
+ K.1 <a href="#d3e19680">Element Derivation</a><br/>
+ K.2 <a href="#d3e20184">Attribute Derivation</a><br/>
L <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br/>
- L.1 <a href="#d3e19722">Requirements</a><br/>
- L.2 <a href="#d3e19886">Guidelines</a><br/>
+ L.1 <a href="#d3e21130">Requirements</a><br/>
+ L.2 <a href="#d3e21294">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/>
@@ -495,7 +497,7 @@
definitions that are referenced by layout and content information.</p><p>In <a href="#dfxp-example-styling"><b>Example Fragment – DFXP Styling</b></a>, four style sets of specifications
are defined, with one set serving as a collection of default styles.</p><table summary="HTML Table" id="dfxp-example-styling" class="example"><caption>Example Fragment – DFXP Styling</caption><tbody><tr><td>
<div class="exampleInner"><pre>
-<styling xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<styling xmlns:tts="http://www.w3.org/2006/10/ttaf1#<span class="diff-chg">styling</span>">
<!-- s1 specifies default color, font, and text alignment -->
<style xml:id="s1"
tts:color="white"
@@ -521,7 +523,7 @@
that a style is not already explicitly specified on content or inherited
via the content hierarchy.)</p><table summary="HTML Table" id="dfxp-example-layout" class="example"><caption>Example Fragment – DFXP Layout</caption><tbody><tr><td>
<div class="exampleInner"><pre>
-<layout xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<layout xmlns:tts="http://www.w3.org/2006/10/ttaf1#<span class="diff-chg">styling</span>">
<region xml:id="subtitleArea"
style="s1"
tts:extent="560px 62px"
@@ -636,9 +638,19 @@
<em>Reduced XML Infoset</em>.</p></dd><dt class="label">Abstract Document Type</dt><dd><p>A set of constraints that defines a class of <em>XML Information
Set</em>s <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label">Attribute Information Item</dt><dd><p>Each specified or defaulted attribute of an XML document corresponds with an attribute information
item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.3.</p></dd><dt class="label">Character Information Item</dt><dd><p>Each data character appearing in an XML document corresponds with a character information
-item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.6.</p></dd><dt class="label">Content Region</dt><dd><p>A logical region into which rendered content is placed when modeling or
+item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.6.</p></dd><div class="diff-add"><dt class="label">Content Processor</dt><dd><p>A processing system capable of importing (receiving) timed text authoring format
+content for the purpose of transforming, presenting, or otherwise processing the content.</p></dd></div><div class="diff-add"><dt class="label">Content Profile</dt><dd><p>A collection of features and extensions that are (or may be) employed by
+timed text authoring format content.</p></dd></div><dt class="label">Content Region</dt><dd><p>A logical region into which rendered content is placed when modeling or
performing presentation processing.</p></dd><dt class="label">Element Information Item</dt><dd><p>Each element appearing in an XML document corresponds with an element information
-item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.2.</p></dd><dt class="label">Exchange Profile</dt><dd><p>A profile (subset) of the TT AF that serves a set of needs for content exchange.</p></dd><dt class="label">Region</dt><dd><p>A logical construct that models authorial intention regarding
+item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.2.</p></dd><dt class="label">Exchange Profile</dt><dd><p>A<span class="diff-add"> content</span> profile<span class="diff-del">(subset) of the TT AF</span> that serves a set of needs
+for content <span class="diff-chg">inter</span>change.</p></dd><div class="diff-add"><dt class="label">Extension</dt><dd><p>A syntactic or semantic expression or capability that is defined and
+labeled (using a extension designation) in another (public or private)
+specification.</p></dd></div><div class="diff-add"><dt class="label">Feature</dt><dd><p>A syntactic or semantic expression or capability that is defined and
+labeled (using a feature designation) in this specification (or a
+future revision of this specification).</p></dd></div><div class="diff-add"><dt class="label">Processor</dt><dd><p>See <em>Content Processor</em>.</p></dd></div><div class="diff-add"><dt class="label">Processor Profile</dt><dd><p>A collection of features and extensions that must or may be implemented (supported) by
+by a content processor.</p></dd></div><div class="diff-add"><dt class="label">Profile Definition Document</dt><dd><p>A document that defines a specific collection of features and extensions
+for which support is required or optional in a recipient content
+processor.</p></dd></div><dt class="label">Region</dt><dd><p>A logical construct that models authorial intention regarding
desired or potential presentation processing, and which is represented as
a rectangular area of a presentation surface into which content
is composed and rendered during presentation processing.</p></dd><dt class="label">Reduced XML Infoset</dt><dd><p>An XML Information Set <a href="#infoset">[XML InfoSet]</a> that satisfieds the
@@ -698,7 +710,9 @@
instance, then the specified media type is
<code>application/ttaf+xml</code> in conformance with <a href="#rfc3023">[XML Media Types]</a> § 7, with which an optional
<code>profile</code> parameter may appear, the value of which
-conforms to the values defined by
+conforms to
+<span class="diff-del">the values</span><span class="diff-add">a profile designator as</span>
+defined by
<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p></li><li><p>The document instance is or can be represented as a Reduced XML
Infoset as defined by <a href="#reduced-infoset"><b>A Reduced XML Infoset</b></a>.</p></li><li><p>The Reduced XML
Infoset that corresponds to the document instance is or can
@@ -710,11 +724,9 @@
semantic constraints defined by this specification. In addition, this Infoset
should satisfy the web content accessibility guidelines specified by
<a href="#wcag">[WCAG]</a>.</p></li></ol></div><div class="div2">
-<h3><a name="conformance-processor" id="conformance-processor"/>3.2 Processor Conformance</h3><table border="1" class="ednote" summary="Editorial note: GA"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: GA</b></td><td align="right" valign="top">2009-01-30</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">
-The following description of processor conformance needs to be sub-divided into
-transformation and presentation processor specific descriptions, possibly retaining
-common elements in a base processor conformance clause.
-</td></tr></table><p>A TT AF processor conforms to this specification if the following criteria are
+<h3><a name="conformance-processor" id="conformance-processor"/>3.2 Processor Conformance</h3><div class="div3">
+<h4><a name="conformance-generic-processor" id="conformance-generic-processor"/>3.2.1 <span class="diff-add">Generic Processor Conformance</span></h4><p>A TT AF processor conforms to this specification if the following
+<span class="diff-add">generic processor </span>criteria are
satisfied:</p><ol class="enumar"><li><p>The processor provides at least one mechanism for notionally
instantiating a Reduced XML
Infoset representation of a conformant TT AF document
@@ -725,7 +737,10 @@
of a conformant TT AF document instance with one of the
TT AF Abstract Document Types defined by
<a href="#doctypes"><b>4 Document Types</b></a>.</p></li><li><p>The processor does not <em>a priori</em> reject or abort the
-processing of a conformant TT AF document instance.</p></li><li><p>The processor supports all mandatory processing semantics defined by this specification.</p></li><li><p>If the processor claims to support presentation processing in order
+processing of a conformant TT AF document instance
+<span class="diff-add">unless the processor does not support some required
+(mandatory) feature specified or implied by a TT AF content profile
+declared to apply to the document instance</span>.</p></li><li><p>The processor supports all mandatory processing semantics defined by this specification.</p></li><li><p class="diff-del">If the processor claims to support presentation processing in order
to produce a rendition of TT AF content on a visual medium, then it
must implement the region and line layout
semantics defined by <a href="#semantics-region-layout"><b>9.3 Region Layout and Presentation</b></a> and
@@ -733,7 +748,19 @@
processor should satisfy the user agent accessibility guidelines specified by
<a href="#uaag">[UAAG]</a>.
</p></li><li><p>If the processor supports some optional processing semantics defined by this specification,
-then it does so in a manner consistent with the defined semantics.</p></li></ol></div><div class="div2">
+then it does so in a manner consistent with the defined semantics.</p></li></ol></div><div class="diff-add">
+<h4><a name="conformance-transformation-processor" id="conformance-transformation-processor"/>3.2.2 Transformation Processor Conformance</h4><p>A TT AF processor is a conformant TT AF transformation processor if
+the following criteria are satisfied:</p><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>The processor supports the DFXP Transformation profile as specified
+by <a href="#profile-dfxp-transformation"><b>G.2 DFXP Transformation Profile</b></a>.</p></li></ol></div><div class="diff-add">
+<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>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
+by <a href="#profile-dfxp-presentation"><b>G.1 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
reference to an implementation compliance statement (ICS).</p><p>An implementation compliance statement must identify all mandatory
@@ -743,8 +770,16 @@
defined by <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>, and, if a subset or
superset profile is used or supported, then what features are excluded
or included in the subset or superset profile.</p><p>A TT AF document instance for which a compliance claim is made
-must specify a <code>ttp:profile</code> attribute on its root element
-as defined by <a href="#parameter-attribute-profile"><b>6.2.7 ttp:profile</b></a>.</p></div></div><div class="div1">
+must specify
+<span class="diff-add">either (1)</span>
+a <code>ttp:profile</code> attribute on its root
+<span class="diff-add"><code>tt</code></span>
+element
+as defined by <a href="#parameter-attribute-profile"><b>6.2.7 ttp:profile</b></a>
+<span class="diff-add">or (2)
+a <code>ttp:profile</code> element as a child of the
+<code>head</code> element as defined by
+<a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a></span>.</p></div></div><div class="div1">
<h2><a name="doctypes" id="doctypes"/>4 Document Types</h2><p>This section defines the following TT AF Abstract Document Types:</p><ul><li><p><a href="#dfxp-content-doctype"><b>4.1 DFXP Content</b></a></p></li></ul><p>Each abstract document type consists of the following constraints:</p><ul><li><p>a non-empty collection of element types, where each element type consists of a name,
a (possibly empty) collection of attributes, and a content specification</p></li><li><p>a non-empty collection of element types that may appear as the document element</p></li></ul><p>An Abstract Document Instance may be assessed in terms of validity,
and is considered to be a Valid Abstract Document Instance if it
@@ -761,16 +796,22 @@
element satisfy their respective element type's content
specifications, all required attributes are present, and the declared
value of each attribute satisfies the type declared by the
-associated abstract document type.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a conformant document
-instance, a given document instance may be constrained by the author or authoring tool
-to satisfy a more restrictive definition of validity.</p></div><div class="div2">
+associated abstract document type.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While a conformant processor may not <em>a priori</em> reject a
+conformant document instance <span class="diff-add">that adheres to a
+supported content profile</span>, a given document instance may be
+constrained by the author or authoring tool to satisfy a more
+restrictive definition of validity.</p></div><div class="div2">
<h3><a name="dfxp-content-doctype" id="dfxp-content-doctype"/>4.1 DFXP Content</h3><p>DFXP Content is an abstract document type of the Timed Text Authoring Format intended
to be used for interchange among distribution systems. This document type
is defined in terms of the
element and attribute vocabulary
specified in <a href="#vocabulary"><b>5 Vocabulary</b></a>.</p><p>This specification defines two types of normative schemas that may be used to validate a subset of
conformant DFXP document instances:</p><ul><li><p><a href="#dfxp-schema-rnc"><b>C.1 Relax NG Schema</b></a></p></li><li><p><a href="#dfxp-schema-xsd"><b>C.2 XML Schema Definition (XSD) Schema</b></a></p></li></ul><p>The (root) document element of a DFXP document instance must be a
-<code>tt</code> element, as defined by <a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a>.</p></div></div><div class="div1">
+<code>tt</code> element, as defined by <a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a>.</p><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>The schemas included in this specification do not validate all syntactic constraints
+defined by this specification. In particular, performing validation with one of the above
+referenced schemas may result in a <em>false positive</em> indication of validity.
+However, their use will not produce a <em>false negative</em> indication of validity
+when used with a compliant validating processor.</p></div></div></div></div><div class="div1">
<h2><a name="vocabulary" id="vocabulary"/>5 Vocabulary</h2><p>This section defines the
namespaces, profiles, and vocabulary (as an element an attribute
catalog) of the Timed Text Authoring Format (TT AF) as follows:</p><ul><li><p><a href="#vocabulary-namespaces"><b>5.1 Namespaces</b></a></p></li><li><p><a href="#vocabulary-profiles"><b>5.2 Profiles</b></a></p></li><li><p><a href="#vocabulary-overview"><b>5.3 Catalog</b></a></p></li></ul><div class="div2">
@@ -780,36 +821,112 @@
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><span class="diff-add">TT Feature Prefix</span></td><td><span class="diff-add"><code>ttf:</code></span></td><td><span class="diff-add"><code>http://www.w3.org/2006/10/ttaf1/feature</code></span></td></tr><tr><td><span class="diff-add">TT Extension Prefix</span></td><td><span class="diff-add"><code>ttx:</code></span></td><td><span class="diff-add"><code>http://www.w3.org/2006/10/ttaf1/extension</code></span></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#style</code></td></tr><tr><td>TT Style Extension<span class="diff-del">s</span></td><td><code>ttsx:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#style-extension</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 Metadata Extension<span class="diff-del">s</span></td><td><code>ttmx:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#metadata-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></div></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 profiles of its
+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-add">TT Parameter Extension</span></td><td><span class="diff-add"><code>ttpx:</code></span></td><td><span class="diff-add"><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#<span class="diff-chg">styling</span></code></td></tr><tr><td>TT Style Extension<span class="diff-del">s</span></td><td><code>ttsx:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#<span class="diff-chg">styling</span>-extension</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 Metadata Extension<span class="diff-del">s</span></td><td><code>ttmx:</code></td><td><code>http://www.w3.org/2006/10/ttaf1#metadata-extension</code></td></tr><tr><td><span class="diff-add">TT Profile</span></td><td><span class="diff-add"><em>none</em></span></td><td><span class="diff-add"><code>http://www.w3.org/2006/10/ttaf1/profile</code></span></td></tr><tr><td><span class="diff-add">TT Feature</span></td><td><span class="diff-add"><em>none</em></span></td><td><span class="diff-add"><code>http://www.w3.org/2006/10/ttaf1/feature</code></span></td></tr><tr><td><span class="diff-add">TT Extension</span></td><td><span class="diff-add"><em>none</em></span></td><td><span class="diff-add"><code>http://www.w3.org/2006/10/ttaf1/extension</code></span></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 class="diff-add">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></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
+<span class="diff-add">standard, predefined </span>profiles of its
vocabulary and associated semantics.
-The following table specifies this set of profiles
-and indicates a normative name for each profile.</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>Value</th></tr><tr><td>DFXP</td><td><code>http://www.w3.org/2006/10/ttaf1#profile-dfxp</code></td></tr></tbody></table><p/><p>A convention is defined for use by content authors to indicate use of a
+The following table specifies this set of
+profiles<span class="diff-chg">, indicating</span>
+a normative name
+<span class="diff-add">and designator </span>for each
+<span class="diff-add">predefined </span>profile<span class="diff-add">,
+and where each of these profiles is formally elaborated in
+<a href="#profiles"><b>G Profiles</b></a></span>.</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><span class="diff-del">Value</span><span class="diff-add">Designator</span></th></tr><tr><td>DFXP<span class="diff-add"> Transformation</span></td><td><span class="diff-chg"><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation</code></span></td></tr><tr><td><span class="diff-add">DFXP Presentation</span></td><td><span class="diff-add"><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code></span></td></tr></tbody></table><p/><p class="diff-add">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
+the base URI.</p><p class="diff-add">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><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>For example, if a profile designator were expressed as
+<code>dfxp-presentation</code>, then the absolutized profile designator
+would be
+<code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code>.</p></div></div><p class="diff-del">A convention is defined for use by content authors to indicate use of a
subtractive or additive delta to a predefined profile by using an
optional <em>sub-profile</em> suffix of a profile URI: if a sub-profile
is subtractive (results in a proper subset), then the <em>sub-profile</em>
is expressed as "-token"; if additive (results in a proper superset), then it is
expressed as "+token", where <em>token</em> expresses an author determined
sub-profile that adheres to the <code>xsd:NCName</code> data type
-defined in <a href="#xsd-2">[XML Schema Part 2]</a>, §3.3.7.</p><p>All tokens used in a sub-profile suffix that do not start with the
-prefix <code>x-</code> are reserved for future standardization.</p><p>The profile of a document instance is specified using a
-<code>ttp:profile</code> attribute as defined by <a href="#parameter-attribute-profile"><b>6.2.7 ttp:profile</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A TT AF authoring system may indicate the profile of TT AF used in
-a document instance by
-specifying a <code>ttp:profile</code> attribute.
-A TT AF content processor may make use of this profile value to
-associate a document instance with a schema or processing functions.</p></div><p>An example of an author defined "tiny" subtractive sub-profile of DFXP is shown
+defined in <a href="#xsd-2">[XML Schema Part 2]</a>, §3.3.7.</p><p class="diff-del">All tokens used in a sub-profile suffix that do not start with the
+prefix <code>x-</code> are reserved for future standardization.</p><p>The profile of a document instance is specified<span class="diff-add">
+either (1) by specifying</span> <span class="diff-del">using </span>a
+<code>ttp:profile</code> attribute<span class="diff-add"> on the root <code>tt</code> element,</span> as defined by
+<a href="#parameter-attribute-profile"><b>6.2.7 ttp:profile</b></a><span class="diff-add">, or
+(2) by including a <code>ttp:profile</code> element in the <code>head</code>
+element, in accordance with <a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a></span>.</p><p class="diff-add">If neither
+<a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
+attribute nor
+<a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a>
+element is present in a TT AF document instance, and if the document
+interchange context does not specify a profile,
+then the DFXP Transformation
+profile applies.</p><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>It is intended that the <code>ttp:profile</code> attribute be used when
+the author wishes to reference one of the standard, predefined profiles of
+TT AF content, and does not wish to modify (by supersetting or subsetting)
+that profile. This attribute may also be used by an author to indicate the use
+of a non-standard profile, in which case the specified profile designator expresses
+a URI that denotes an externally defined TT AF Profile Definition Document.
+However, it is not required that a conformant TT AF content processor be able
+to dereference such an externally specified profile definition.</p><p>In contrast, it is intended that the <code>ttp:profile</code> element be
+used when the author wishes to make use of a modified predefined profile or
+wishes to include in the document instance a non-standard profile definition
+not based upon one of the predefined profiles.</p><p>A predefined profile is supersetted by specifying some feature or extension to
+be required (mandatory) that was either not specified in the underlying, baseline
+profile or was specified as optional (voluntary) in the baseline profile.
+A predefined profile is subsetted by specifying some feature or extension to
+be optional (voluntary) that was specified as required in the underlying, baseline
+profile.</p><p>When a baseline profile is modified by subsetting, the resulting, derived profile
+is referred to as a <em>subtractive</em> profile; when modified by supersetting, the result
+is referred to as an <em>additive</em> profile.
+It is also possible to define a derived profile that is simultaneously subtractive
+and additive.</p></div></div><div class="diff-del"><div class="note"><p class="prefix"><b>Note:</b></p><p>A TT AF authoring system may indicate the profile of TT AF used in
+a document instance by specifying a <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
+attribute. A TT AF content processor may make use of this profile
+value to associate a document instance with a schema or processing
+functions.</p></div></div><p class="diff-add">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>
+specification in one of its declared 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>
+specification in one of its declared profiles.</p><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>A required 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>. A required 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>.</p></div></div><p>An example of an author defined
+<span class="diff-chg">subtractive, derived profile of the DFXP Presentation
+profile</span> is shown
below in <a href="#dfxp-example-sub-profile"><b>Example Fragment – DFXP Subtractive Profile</b></a>.</p><table summary="HTML Table" id="dfxp-example-sub-profile" class="example"><caption>Example Fragment – DFXP Subtractive Profile</caption><tbody><tr><td>
<div class="exampleInner"><pre>
-<tt
- ttp:profile="http://www.w3.org/2006/10/ttaf1#profile-dfxp-x-tiny"
- xml:lang=""
- xmlns="http://www.w3.org/2006/10/ttaf1"
- xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter">
- ...
+<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>
+ <feature value="optional">#fontStyle-italic</feature>
+ </features>
+ </profile>
+ </head>
+ <body/>
</tt>
</pre></div>
-</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>Because the above example is an author defined sub-profile (as
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p class="diff-add">In the above example, the baseline profile is declared to be
+the DFXP Presentation profile, which is then subtractively modified by making the
+<code>#fontStyle-italic</code> feature optional (rather than required as it is defined
+in <a href="#profile-dfxp-presentation"><b>G.1 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><p class="diff-del">Because the above example is an author defined sub-profile (as
opposed to a future W3C defined profile), the sub-profile token
contains the prefix <code>x-</code>.</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
@@ -860,6 +977,11 @@
<a href="#metadata-vocabulary-desc">ttm:desc</a>,
<a href="#metadata-vocabulary-name">ttm:name</a>,
<a href="#metadata-vocabulary-title">ttm:title</a>
+</td></tr><tr><td><span class="diff-add">Parameter Items</span></td><td><span class="diff-add"><a href="#parameter-vocabulary-profile">ttp:profile</a>,
+<a href="#parameter-vocabulary-features">ttp:features</a>,
+<a href="#parameter-vocabulary-feature">ttp:feature</a>,
+<a href="#parameter-vocabulary-extensions">ttp:extensions</a>,
+<a href="#parameter-vocabulary-extension">ttp:extension</a></span>
</td></tr><tr><td>
Styling
</td><td>
@@ -889,7 +1011,7 @@
<a href="#metadata-vocabulary-copyright">ttm:copyright</a> |
<a href="#metadata-vocabulary-desc">ttm:desc</a> |
<a href="#metadata-vocabulary-title">ttm:title</a>
-</td></tr></tbody></table><p/><p>The attribute vocabulary specified for use with the core vocabulary
+</td></tr><tr><td><span class="diff-add">Parameters.class</span></td><td><span class="diff-add"><a href="#parameter-vocabulary-profile">ttp:profile</a></span></td></tr></tbody></table><p/><p>The attribute vocabulary specified for use with the core vocabulary
catalog is enumerated in
<a href="#attribute-vocab-table"><b>Table 5 – Attribute Vocabulary</b></a>.</p><table summary="HTML Table" id="attribute-vocab-table" class="common"><caption>Table 5 – Attribute Vocabulary</caption><col width="25%" span="1"/><tbody><tr><th>Module</th><th>Attributes</th></tr><tr><td>
Core Attributes
@@ -968,9 +1090,9 @@
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.</p><p>In this version of this specification, no
-standardized extension vocabulary is defined. Two namespaces are
+standardized extension vocabulary is defined. The following namespaces are
specifically reserved by <a href="#namespace-vocab-table"><b>Table 1 – Namespaces</b></a>
-for metadata and style extension vocabulary:</p><ul><li><p>TT Style Extension<span class="diff-del">s</span></p></li><li><p>TT Metadata Extension<span class="diff-del">s</span></p></li></ul><p>In addition to standardized extension vocabulary, a conforming TT
+for extension vocabulary:</p><ul><li><p>TT Metadata Extension<span class="diff-del">s</span></p></li><li><p class="diff-add">TT Parameter Extension</p></li><li><p>TT Style Extension<span class="diff-del">s</span></p></li></ul><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
@@ -985,9 +1107,287 @@
interpreting the semantics of other types of information expressed by
core vocabulary items or for establishing a processing context by means
of which TT AF content can be related to an external environment.</p><div class="div2">
-<h3><a name="parameters-element-vocabulary" id="parameters-element-vocabulary"/>6.1 <span class="diff-add">Parameters </span>Element Vocabulary</h3><p>No parameters related element vocabulary is defined for use in the
-core vocabulary catalog.</p></div><div class="div2">
-<h3><a name="parameters-attribute-vocabulary" id="parameters-attribute-vocabulary"/>6.2 <span class="diff-add">Parameters </span>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
+<h3><a name="parameter-element-vocabulary" id="parameter-element-vocabulary"/>6.1 <span class="diff-add">Parameter </span>Element Vocabulary</h3><p class="diff-add">The following elements, all defined in the TT Parameter
+Namespace, specify parametric information that applies to a document
+or a content processor:</p><ul class="diff-add"><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><p class="diff-del">No parameters related element vocabulary is defined for use in the
+core vocabulary catalog.</p><div class="diff-add">
+<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
+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 is <em>feature</em> and an
+<em>extension</em> is where it is defined an how it is labeled:
+if defined in this specification (or a future revision thereof) and
+labeled with a feature designation in <a href="#features"><b>E Features</b></a>, then
+it is considered to be a feature; if defined in another specification
+and labeled there with an extension designation, then it is considered
+to be an extension.</p></div><p>This specification defines two distinct uses of the <code>ttp:profile</code> element:</p><ul><li><p>as a child of the <code>head</code> element within a TT AF document
+instance;</p></li><li><p>as the root element of a TT AF Profile Definition document
+instance;</p></li></ul><p>When a <code>tt:profile</code> element appears within a TT AF document
+instance, its purpose is to express authorial intentions about which
+featueres and extensions must or may be supported by a recipient
+content processor. In addition, the element indirectly expresses
+information about the set of features or extensions that are (or may
+expected to be) used by the document instance.</p><p>When a <code>tt:profile</code> element is used by a TT AF
+Profile Definition document instance, it serves to publish a machine
+readable specification of a specific TT AF content profile, of which
+this specification defines two such Profile Definition Documents in
+<a href="#profiles"><b>G Profiles</b></a>.</p><p>The <code>ttp:profile</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:features</code> elements, followed by
+zero or more <code>ttp:extensions</code> elements.</p><table summary="HTML Table" id="elt-syntax-parameter-profile" class="syntax"><caption>XML Representation – Element Information Item: ttp:profile</caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<ttp:profile
+ use = string
+ <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-features">ttp:features</a>*, <a href="#parameter-vocabulary-extensions">ttp:extensions</a>*
+</ttp:profile>
+</pre></div>
+</td></tr></tbody></table><p>If specified, the <code>use</code> attribute must adhere to the
+<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
+§3.2.17, and, furthermore, must denote a profile designator in
+accordance with <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>. In this case,
+the profile designator must refer to (1) a standard, predefined
+TT AF Profile Definition Document as defined by <a href="#profiles"><b>G Profiles</b></a>,
+or (2) a dereferenceable resource representing a valid TT AF Profile Definition
+document instance. In either case, the referenced profile serves as the
+baseline profile of the specifying <code>ttp:profile</code> element.</p><p>If the <code>use</code> attribute is not specified, then the baseline
+profile of the <code>ttp:profile</code> element must be considered to be
+the empty (null) profile, i.e., a profile definition containing no
+feature or extension specifications.</p><p>The collection of features and extensions of a profile are determined according
+to the following ordered rules:</p><ol class="enumar"><li><p>initialize the features and extensions of the profile to the empty
+set;</p></li><li><p>if a <code>use</code> attribute is present, then augment the profile
+with the set of features and extensions specified by the referenced
+baseline profile;</p></li><li><p>for each <code>ttp:feature</code> and <code>ttp:extension</code> element
+descendant of the <code>ttp:profile</code> element, using a post-order
+traversal, merge the specified feature or extension with the features
+and extensions of the profile, where merging a feature or extension
+entails replacing an existing feature or extension specification, if
+it already exists, or adding a new feature or extension specification,
+if it does not yet exist in the profile;</p></li></ol><p>A conformant TT AF processor is not required to be able to
+dereference a TT AF Profile Definition Document that is not one of the
+standard, predefined profiles defined by <a href="#profiles"><b>G Profiles</b></a>. A
+conformant TT AF processor may make use of a built-in, static
+form of each standard, predefined profile so as not to require
+dereferencing a network resource.</p><p>If a TT AF processor is unable to dereference a non-standard TT AF
+Profile Definition Document, then it must not further process the
+document without the presence of an explicit override from an end-user
+or some implementation specific parameter traceable to an end-user or
+to a user or system configuration setting. If a TT AF processor aborts
+processing of a TT AF document instance due to the inability to
+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>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>
+<div class="exampleInner"><pre>
+<ttp:profile use="dfxp-presentation">
+ <ttp:features>
+ <ttp:feature>#rollUp</ttp:feature>
+ </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 supersetted (thus
+creating an additive derived profile) by requiring support for
+<code>#rollUp</code> feature.</p></div></div><div class="diff-add">
+<h4><a name="parameter-vocabulary-features" id="parameter-vocabulary-features"/>6.1.2 ttp:features</h4><p>The <code>ttp:features</code> element is a container element used to group
+infomation about feature support requirements.</p><p>The <code>ttp:features</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: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
+ 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>base</code> attribute must adhere to the
+<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
+§3.2.17, and, furthermore, must express a feature namespace as
+defined by <a href="#feature-designations"><b>E.1 Feature Designations</b></a>. If not specified,
+the <code>base</code> attribute's default value applies, which is
+the TT Feature Namespace.</p><p>The <code>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="diff-add">
+<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
+infomation about support requirements for a particular feature.</p><p>The children of the <code>ttp:feature</code> element must express a non-empty
+sequence of character information items that adheres to the
+<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
+§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 = (required|optional) : 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 value of the
+<code>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>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 <code>required</code>, then the processor must implement or
+otherwise support the feature in order to process the document;
+however, if the value is <code>optional</code>, then the processor
+need not implement or otherwise support the feature in order to
+process the document.</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>, 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
+implementation specific parameter traceable to an end-user or to a
+user or system configuration setting. If a TT AF processor aborts
+processing of a TT AF document instance due to the specification of a
+required, but unsupported feature by this element, 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>If the value of the <code>value</code> attribute is
+<code>optional</code>, and if the TT AF processor implementation does
+not support the feature, then it may further process the document even
+in the case that some use of the feature is present in the document.
+In the case of actual use of a feature designated as optional, the
+default semantics associated with that feature apply; that is, the
+processor may behave as if the feature were not actually used or
+referenced by the document. Notwithstanding the above, the syntactic
+presence or reference to an optional feature by a document must not be
+considered to be a violation of document validity or a barrier to
+further processing if the syntactic expression is well-formed and
+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="strong"><ttp:feature value="required">#textDecoration-under</ttp:feature></span>
+ <span class="strong"><ttp:feature value="optional">#fontStyle-italic</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> elements, the first to superset the
+baseline profile (since <code>#textDecoration-under</code> is not required
+by the DFXP presentation profile), and the second to subset the
+baseline profile (since <code>#fontStyle-italic</code> is nominally
+required by the DFXP presentation profile). Note that the explicit
+specification of <code>required</code> on the <code>value</code>
+attribute on the first of the two <code>ttp:feature</code> elements is not
+necessary, since it is the default value of this attribute.</p><p>The effect of this example is to express authorial intentions that
+text underlining must be supported, but that the italic font style need
+not be supported (even though nominally required by the referenced baseline
+profile).</p></div></div><div class="diff-add">
+<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
+ 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>base</code> attribute must adhere to the
+<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
+§3.2.17, and, furthermore, must express an extension namespace as
+defined by <a href="#extension-designations"><b>F.1 Extension Designations</b></a>. If not specified,
+the <code>base</code> attribute's default value applies, which is
+the TT Extension Namespace.</p><p>The <code>base</code> attribute is used to permit the abbreviation
+of extension designation URIs expressed by child <code>ttp:extension</code>
+elements.</p></div><div class="diff-add">
+<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
+infomation about support requirements for a particular extension.</p><p>The children of the <code>ttp:extension</code> element must express a non-empty
+sequence of character information items that adheres to the
+<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
+§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 = (required|optional) : 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 value of the
+<code>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>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 <code>required</code>, then the processor must implement or
+otherwise support the extension in order to process the document;
+however, if the value is <code>optional</code>, then the processor
+need not implement or otherwise support the extension in order to
+process the document.</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>, 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
+implementation specific parameter traceable to an end-user or to a
+user or system configuration setting. If a TT AF processor aborts
+processing of a TT AF document instance due to the specification of a
+required, but unsupported extension by this element, 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>If the value of the <code>value</code> attribute is
+<code>optional</code>, and if the TT AF processor implementation does
+not support the extension, then it may further process the document even
+in the case that some use of the extension is present in the document.
+In the case of actual use of an extension designated as optional, the
+default semantics associated with that extension apply; that is, the
+processor may behave as if the extension were not actually used or
+referenced by the document. Notwithstanding the above, the syntactic
+presence or reference to an optional extension by a document must not be
+considered to be a violation of document validity or a barrier to
+further processing if the syntactic expression is well-formed and
+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">
+ <ttp:extensions>
+ <span class="strong"><ttp:extension value="required">#x-prefilter-by-language</ttp:extension></span>
+ </ttp:extensions>
+ <ttp:extensions base="http://foo.bar.baz/ttaf1/extension">
+ <span class="strong"><ttp:extension value="required">#private-extension-1</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 is required for 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 a
+private extension defined in a third party namespace. 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.</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 two additional extensions, one (hypothetically)
+defined by the W3C (in another specification or in a future version of
+this specification) and the other defined by a third party.</p></div></div></div><div class="div2">
+<h3><a name="parameter-attribute-vocabulary" id="parameter-attribute-vocabulary"/>6.2 <span class="diff-add">Parameter </span>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
to express the number of horizontal and vertical cells into which the root container region
@@ -1070,7 +1470,9 @@
</pre></div>
</td></tr></tbody></table><p>A frame rate multiplier is used when the desired frame rate cannot
be expressed as an integral number of frames per second.</p><p>If not specified, the frame rate multiplier must be considered to
-be equal to one (1:1). If a denominator is specified, then it must not be zero (0).</p><p>A <code>ttp:frameRateMultiplier</code> attribute is considered to be significant only
+be equal to one (1:1). If a denominator is specified, then it must not be zero (0).
+<span class="diff-add"> If no denominator is specified, then a denominator of one (1)
+applies</span>.</p><p>A <code>ttp:frameRateMultiplier</code> attribute is considered to be significant only
when specified on the <code>tt</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The frame rate multiplier used for synchronizing with NTSC <a href="#smpte170m">[SMPTE 170M]</a>
formatted video objects at 30 frames per second is nominally
1000:1001. The nominal frame rate of NTSC video is defined as the chrominance
@@ -1142,11 +1544,18 @@
to express the profile of the Timed Text Authoring Format (TT AF) used
in a document instance.</p><p>If specified, the value of this attribute must adhere to the
<code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
-§3.2.17, and, further, must specify a profile URI as defined
-by <a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p><p>If not specified, then the Distribution Format Exchange Profile
-(DFXP) must be assumed to apply.</p><p>A <code>ttp:profile</code>
+§3.2.17, and, further, must specify a
+profile <span class="diff-chg">designator in accordance with</span>
+<a href="#vocabulary-profiles"><b>5.2 Profiles</b></a>.</p><p class="diff-del">If not specified, then the Distribution Format Exchange
+Profile (DFXP) must be assumed to apply.</p><p>A <code>ttp:profile</code>
attribute is considered to be significant only when specified on the
-<code>tt</code> element.</p></div><div class="div3">
+<code>tt</code> element.</p><p class="diff-add">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">
<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
@@ -1288,19 +1697,11 @@
vocabulary catalog.</p><div class="div2">
<h3><a name="content-element-vocabulary" id="content-element-vocabulary"/>7.1 <span class="diff-add">Content </span>Element Vocabulary</h3><p>The following elements specify the structure and principal content aspects of a
document instance:</p><ul><li><p><a href="#document-structure-vocabulary-tt"><b>7.1.1 tt</b></a></p></li><li><p><a href="#document-structure-vocabulary-head"><b>7.1.2 head</b></a></p></li><li><p><a href="#document-structure-vocabulary-body"><b>7.1.3 body</b></a></p></li><li><p><a href="#content-vocabulary-div"><b>7.1.4 div</b></a></p></li><li><p><a href="#content-vocabulary-p"><b>7.1.5 p</b></a></p></li><li><p><a href="#content-vocabulary-span"><b>7.1.6 span</b></a></p></li><li><p><a href="#content-vocabulary-br"><b>7.1.7 br</b></a></p></li></ul><div class="div3">
-<h4><a name="document-structure-vocabulary-tt" id="document-structure-vocabulary-tt"/>7.1.1 tt</h4><table border="1" class="ednote" summary="Editorial note: GA"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: GA</b></td><td align="right" valign="top">2009-01-19</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">
-The inclusion of
-<code>requiredFeatures</code> and
-<code>requiredExtensions</code>
-attributes on the <code>tt</code> element type is provisional, and is provided for
-discussion purposes only.
-</td></tr></table><p>The <code>tt</code> element serves as the root, document element of a document
+<h4><a name="document-structure-vocabulary-tt" id="document-structure-vocabulary-tt"/>7.1.1 tt</h4><p>The <code>tt</code> element serves as the root, document element of a document
instance.</p><p>The <code>tt</code> element accepts as its children zero or one <code>head</code> element followed by
zero or one <code>body</code> element.</p><table summary="HTML Table" id="elt-syntax-tt" class="syntax"><caption>XML Representation – Element Information Item: tt</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<tt
- <span class="diff-add">requiredFeatures = string</span>
- <span class="diff-add">requiredExtensions = string</span>
<span class="diff-add"><a href="#style-attribute-extent">tts:extent</a> = string</span>
<a href="#content-attribute-id">xml:id</a> = ID
<a href="#content-attribute-lang"><span class="reqattr">xml:lang</span></a> = string
@@ -1316,48 +1717,9 @@
these points is referred to subsequently as the <em>external time interval</em>.
</p><p>A document instance has an implicit duration that is equal to the
implicit duration of the <code>body</code> element of the document, if present, or zero,
-if not present.</p><p class="diff-add">If a TT AF document instance makes use of an optional
-language or semantic feature, and if the intended use of the document
-requires recognition and processing of that feature, then the document
-instance must specify the use of that feature using a
-<code>requiredFeatures</code> attribute. If this attribute is specified
-on the <code>tt</code> element, then it must specify a non-empty, whitespace separated list of
-feature designators as defined by <a href="#feature-designations"><b>E.1 Feature Designations</b></a>.</p><p class="diff-add">If the use of an optional feature is designated by the
-<code>requiredFeatures</code> attribute, then a conforming TT AF
-processor must implement or otherwise support the designated feature
-in order to process the document; otherwise, it must not further
-process the document without the presence of an explicit override from
-an end-user or some implementation specific parameter traceable to an
-end-user or to a user or system configuration setting. If a TT AF
-processor aborts processing of a TT AF document instance due to the
-specification of an unsupported feature by this attribute, 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><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>The means by which an end-user is notified that the processing of a
-document has aborted due to lack of support of a feature is
-considered to be implementation dependent, and is not further defined
-by this specification.</p></div></div><p class="diff-add">If a TT AF document instance makes use of a language or
-semantic extension, and if the intended use of the document requires
-recognition and processing of that extension, then the document
-instance must specify the use of that extension using a
-<code>requiredExtensions</code> attribute. If this attribute is
-specified on the <code>tt</code> element, then it must specify a non-empty, whitespace separated
-list of extension designators as defined by <a href="#extension-designations"><b>F.1 Extension Designations</b></a>.</p><p class="diff-add">If the use of an extension is designated by the
-<code>requiredExtensions</code> attribute, then a conforming TT AF
-processor must implement or otherwise support the designated extension
-in order to process the document; otherwise, it must not further
-process the document without the presence of an explicit override from
-an end-user or some implementation specific parameter traceable to an
-end-user or to a user or system configuration setting. If a TT AF
-processor aborts processing of a TT AF document instance due to the
-specification of an unsupported extension by this attribute, 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><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>The means by which an end-user is notified that the processing of a
-document has aborted due to lack of support of an extension is
-considered to be implementation dependent, and is not further defined
-by this specification.</p></div></div><p class="diff-add">If the <code>tts:extent</code> attribute is specified on the <code>tt</code>
-element, then it specifies the spatial extent of the root container region in
+if not present.</p><p class="diff-add">If the <code>tts:extent</code> attribute is specified on the <code>tt</code>
+element, then it must adhere to <a href="#style-attribute-extent"><b>8.2.8 tts:extent</b></a>, in which case it
+specifies the spatial extent of the root container region in
which content regions are located and presented. If no <code>tts:extent</code>
attribute is specified, then the spatial extent of the root container region is
considered to be determined by the external authoring or presentation
@@ -1366,11 +1728,15 @@
to the text contained within the document instance.</p><p>If no <code>xml:space</code> attribute is specified upon the <code>tt</code> element, then it must
be considered as if the attribute had been specified with a value of <code>default</code>.</p></div><div class="div3">
<h4><a name="document-structure-vocabulary-head" id="document-structure-vocabulary-head"/>7.1.2 head</h4><p>The <code>head</code> element is a container element used to group
-header matter, including metadata, styling, and layout information.</p><p>The <code>head</code> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group,
-followed by
-zero or one <code>styling</code> element, followed by zero or one
-<code>layout</code> element.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
+header matter, including metadata<span class="diff-add">,
+profile</span>, styling, and layout information.</p><p>The <code>head</code> element accepts as its children zero or more
+elements in the <code>Metadata.class</code> element group<span class="diff-add">,
+followed by zero or more elements in the
+<code>Parameters.class</code> element group</span>,
+followed by zero or one <code>styling</code> element,
+followed by zero or one <code>layout</code> element.</p><p>Any metadata specified by children in the <code>Metadata.class</code>
+element group applies semantically to the document instance as a
+whole, and not just the <code>head</code> element.</p><p>Any parameters specified by children in the <code>Parameters.class</code>
element group applies semantically to the document instance as a
whole, and not just the <code>head</code> element.</p><p>A <code>styling</code> child element is used to specify style constructs
that are referenced from other style constructs, by layout constructs, and by
@@ -1381,7 +1747,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>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#styling-vocabulary-styling">styling</a>?, <a href="#layout-vocabulary-layout">layout</a>?
+ <em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*<span class="diff-add">, <a href="#element-vocab-group-table">Parameters.class</a>*</span>, <a href="#styling-vocabulary-styling">styling</a>?, <a href="#layout-vocabulary-layout">layout</a>?
</head>
</pre></div>
</td></tr></tbody></table><p>To the extent that time semantics apply to the content of the
@@ -1724,7 +2090,8 @@
<code>style</code> attribute<span class="diff-add">, as well as <a href="#semantics-style-association-referential"><b>8.4.1.2 Referential Styling</b></a> and <a href="#semantics-style-association-chained-referential"><b>8.4.1.3 Chained Referential Styling</b></a>,</span> for
further information on its semantics.</p></div></div><div class="div3">
<h4><a name="style-attribute-backgroundColor" id="style-attribute-backgroundColor"/>8.2.2 tts:backgroundColor</h4><p>The <code>tts:backgroundColor</code> attribute is used to specify a style property that
-defines the background color of a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any style specification element or content element
+defines the background color of a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-backgroundColor" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-color"><color></a><span class="diff-del"> |
@@ -1756,19 +2123,22 @@
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.7.2.</p></div></div><div class="div3">
<h4><a name="style-attribute-color" id="style-attribute-color"/>8.2.3 tts:color</h4><p>The <code>tts:color</code> attribute is used to specify a style property that
-defines the foreground color of marks associated with an area generated by content flowed into a region.</p><p>This attribute may be specified by any style specification element or content element
+defines the foreground color of marks associated with an area generated by content flowed into a region.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-color" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-color"><color></a><span class="diff-del"> |
<code>inherit</code></span>
-</td></tr><tr><td><em>Initial:</em></td><td>
-<code>transparent</code>
-</td></tr><tr><td><em>Applies to:</em></td><td>
+</td></tr><tr><td><em>Initial:</em></td><td><span class="diff-chg">see prose</span></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p class="diff-chg">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span<span class="diff-del">, where the value of this style property on the anonymous span is considered to be
-<code>inherit</code></span>.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-color-example-1" class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
+<code>inherit</code></span>.</p><p class="diff-add">The initial value of the <code>tts:color</code> property
+is considered to be implementation dependent. In the absence of
+end-user preference information, a conformant presentation processor
+should use an initial value that is highly contrastive to the
+background color of the root container region.</p><p>The <code>tts:color</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-color-example-1" class="example"><caption>Example Fragment – Color</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:backgroundColor="black"/>
@@ -1787,7 +2157,8 @@
§ 7.17.1.</p></div></div><div class="div3">
<h4><a name="style-attribute-direction" id="style-attribute-direction"/>8.2.4 tts:direction</h4><p>The <code>tts:direction</code> attribute is used to specify a style property that
defines the directionality of an embedding or override according to
-the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any style specification element or content element
+the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-direction" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>ltr</code> |
@@ -1800,7 +2171,8 @@
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p class="diff-add">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
-span.</p><p>The <code>tts:direction</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-direction-example-1" class="example"><caption>Example Fragment – Direction</caption><tbody><tr><td>
+span.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must ignore the attribute.</p><p>The <code>tts:direction</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-direction-example-1" class="example"><caption>Example Fragment – Direction</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="265px 84px"/>
@@ -1824,7 +2196,8 @@
§ 7.27.1.</p></div></div><div class="div3">
<h4><a name="style-attribute-display" id="style-attribute-display"/>8.2.5 tts:display</h4><p>The <code>tts:display</code> attribute is used to specify a style property that
defines whether an element is a candidate for layout and composition
-in a region.</p><p>This attribute may be specified by any style specification element or content element
+in a region.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-display" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>auto</code> |
@@ -1887,7 +2260,8 @@
represented by this attribute are based upon that defined by <a href="#css2">[CSS2]</a>,
§ 9.2.5.</p></div></div><div class="div3">
<h4><a name="style-attribute-displayAlign" id="style-attribute-displayAlign"/>8.2.6 tts:displayAlign</h4><p>The <code>tts:displayAlign</code> attribute is used to specify a style property that
-defines the alignment of block areas in the block progression direction.</p><p>This attribute may be specified by any style specification element or content element
+defines the alignment of block areas in the block progression direction.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-displayAlign" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>before</code> |
@@ -1898,7 +2272,9 @@
<code>before</code>
</td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p/><p>The <code>tts:displayAlign</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-displayAlign-example-1" class="example"><caption>Example Fragment – Display Align</caption><tbody><tr><td>
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>before</code> were specified.</p><p>The <code>tts:displayAlign</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-displayAlign-example-1" class="example"><caption>Example Fragment – Display Align</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="128px 66px"/>
@@ -1946,7 +2322,8 @@
<h4><a name="style-attribute-dynamicFlow" id="style-attribute-dynamicFlow"/>8.2.7 tts:dynamicFlow</h4><p>The <code>tts:dynamicFlow</code> attribute is used to specify a style property that
defines how to dynamically flow content into and out of a region over some time
interval.</p><p>This style property applies only to a region when the <code>tts:overflow</code>
-property for that region has the value <span class="diff-chg"><code>dynamic</code></span>.</p><p>This attribute may be specified by any style specification element or content element
+property for that region has the value <span class="diff-chg"><code>dynamic</code></span>.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-dynamicFlow" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>none</code><span class="diff-add"> | <code>rollUp</code></span> |
@@ -1954,19 +2331,20 @@
</td></tr><tr><td><em>Initial:</em></td><td><code>none</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p>If the value of this attribute is <code>none</code>, then no
-dynamic flow semantics apply.</p><p class="diff-add">If the value of this attribute is <code>rollUp</code>, then interpret
-this value as a shorthand value equivalent to
-<code>out(line,smooth) inter(0.433s)</code>.</p><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>, <em>reflow within</em>, and <em>clear
-from</em> dynamic flow operations.</p><p>If a reflow <code>within()</code> flow function is specified, but
-no clear <code>out()</code> flow function is specified, or vice-versa,
-then the function applies equally to both <em>reflow within</em>
-and <em>clear from</em> dynamic flow operations.</p><p>If either <code>intra()</code> or <code>inter()</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>
+dynamic flow semantics apply.</p><p class="diff-add">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) inter(0.433s)</code>.</p><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><span class="diff-del">, <em>reflow within</em>,</span> and <em>clear
+from</em> dynamic flow operations.</p><p class="diff-del">If a reflow <code>within()</code> flow function is
+specified, but no clear <code>out()</code> flow function is specified,
+or vice-versa, then the function applies equally to both <em>reflow
+within</em> and <em>clear from</em> dynamic flow operations.</p><p>If either <code>intra()</code> or <code>inter()</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.</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>The <code>tts:dynamicFlow</code> style is illustrated by the
+specified in <a href="#dynamicFlowModel"><b>B Dynamic Flow Processing Model</b></a>.</p><p class="diff-add">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
following example, and depicted in an <a href="images/dynamicFlow_RU_animated.svg">SVG Animation</a>.</p><table summary="HTML Table" id="style-attribute-dynamicFlow-example-1" class="example"><caption>Example Fragment – Dynamic Flow</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -1994,7 +2372,8 @@
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-dynamicFlow-example-2-images" class="example-images-bordered"><caption>Example Rendition – Dynamic Flow – Discrete Frames</caption><col width="136px" span="1"/><col width="136px" span="1"/><col width="136px" span="1"/><col width="136px" span="1"/><tbody><tr><td><img src="images/dynamicFlow_snake_0.png" alt="DFXP dynamic flow style property - frame 0"/></td><td><img src="images/dynamicFlow_snake_1.png" alt="DFXP dynamic flow style property - frame 1"/></td><td><img src="images/dynamicFlow_snake_2.png" alt="DFXP dynamic flow style property - frame 2"/></td><td><img src="images/dynamicFlow_snake_3.png" alt="DFXP dynamic flow style property - frame 3"/></td></tr><tr><td><img src="images/dynamicFlow_snake_4.png" alt="DFXP dynamic flow style property - frame 4"/></td><td><img src="images/dynamicFlow_snake_5.png" alt="DFXP dynamic flow style property - frame 5"/></td><td><img src="images/dynamicFlow_snake_6.png" alt="DFXP dynamic flow style property - frame 6"/></td><td><img src="images/dynamicFlow_snake_7.png" alt="DFXP dynamic flow style property - frame 7"/></td></tr><tr><td><img src="images/dynamicFlow_snake_8.png" alt="DFXP dynamic flow style property - frame 8"/></td><td><img src="images/dynamicFlow_snake_9.png" alt="DFXP dynamic flow style property - frame 9"/></td><td><img src="images/dynamicFlow_snake_10.png" alt="DFXP dynamic flow style property - frame 10"/></td><td><img src="images/dynamicFlow_snake_11.png" alt="DFXP dynamic flow style property - frame 11"/></td></tr><tr><td><img src="images/dynamicFlow_snake_12.png" alt="DFXP dynamic flow style property - frame 12"/></td><td><img src="images/dynamicFlow_snake_13.png" alt="DFXP dynamic flow style property - frame 13"/></td><td><img src="images/dynamicFlow_snake_14.png" alt="DFXP dynamic flow style property - frame 14"/></td><td><img src="images/dynamicFlow_snake_15.png" alt="DFXP dynamic flow style property - frame 15"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-extent" id="style-attribute-extent"/>8.2.8 tts:extent</h4><p>The <code>tts:extent</code> attribute is used to specify the
<em>width</em> and <em>height</em> of a region area
-(which may be the root container region).</p><p>This attribute may be specified by any style specification element or content element
+(which may be the root container region).</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-extent" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>auto</code> |
@@ -2009,13 +2388,22 @@
<em>width</em>, and the second specification is the
<em>height</em>.</p><p>If the value of this attribute is <code>auto</code>, then the initial value
of the style property must be considered to be the same as the root container extent.
+</p><p>
The root container extent is determined either by a
<code>tts:extent</code> specified on the <span class="diff-chg">tt</span> element, if
-present, or by the external authoring context, if not present. In the
-former case, if the width and height is expressed in terms of two
+present, or by the external authoring context, if not present.
+<span class="diff-del">In the former case,</span><span class="diff-add">If
+<code>tts:extent</code> is specified on the <code>tt</code> element,</span>
+<span class="diff-del">if</span><span class="diff-add">then</span>
+the width and height
+<span class="diff-del">is</span><span class="diff-add">must be</span>
+expressed in terms of two
<a href="#style-value-length"><length></a> specifications,
-then these specifications must be expressed as non-percentage,
-definite lengths using pixel units.</p><p>The <code>tts:extent</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-extent-example-1" class="example"><caption>Example Fragment – Extent</caption><tbody><tr><td>
+<span class="diff-del">then</span><span class="diff-add">and</span>
+these specifications must be expressed as non-percentage,
+definite lengths using pixel units.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>auto</code> were specified.</p><p>The <code>tts:extent</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-extent-example-1" class="example"><caption>Example Fragment – Extent</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style <span class="strong">tts:extent="330px 122px"</span>/>
@@ -2035,7 +2423,8 @@
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-extent-example-1-images" class="example-images"><caption>Example Rendition – Extent</caption><tbody><tr><td><img src="images/extent.png" alt="DFXP extent style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-fontFamily" id="style-attribute-fontFamily"/>8.2.9 tts:fontFamily</h4><p>The <code>tts:fontFamily</code> attribute is used to specify a style property that
defines the font family from which glyphs are selected for glyph areas generated
-by content flowed into a region.</p><p>This attribute may be specified by any style specification element or content element
+by content flowed into a region.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-fontFamily" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
(<a href="#style-value-familyName"><familyName></a> | <a href="#style-value-genericFamilyName"><genericFamilyName></a>)
@@ -2048,7 +2437,12 @@
further described in <a href="#style-value-genericFamilyName"><b>8.3.8 <genericFamilyName></b></a> below.</p></div><p class="diff-chg">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span<span class="diff-del">, where the value of this style property on the anonymous span is considered to be
-<code>inherit</code></span>.</p><p>The <code>tts:fontFamily</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontFamily-example-1" class="example"><caption>Example Fragment – Font Family</caption><tbody><tr><td>
+<code>inherit</code></span>.</p><p class="diff-add">If a specified font family is not available, then a
+presentation processor must attempt to map the specified font family
+to an available font family that has similar typographic
+characteristics, or, in the absence of such a mapping, it must
+interpret the font family as if the value <code>default</code> were
+specified.</p><p>The <code>tts:fontFamily</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontFamily-example-1" class="example"><caption>Example Fragment – Font Family</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="474px 146px"/>
@@ -2080,7 +2474,8 @@
<h4><a name="style-attribute-fontSize" id="style-attribute-fontSize"/>8.2.10 tts:fontSize</h4><p>The <code>tts:fontSize</code> attribute is used to specify a style property
that defines the font size for glyphs that are selected for glyph areas
generated by content flowed into a region, where font size is interpreted as a
-scaling transform to the font's design EM square.</p><p>This attribute may be specified by any style specification element or content element
+scaling transform to the font's design EM square.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-fontSize" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a>?<span class="diff-del"> |
@@ -2096,7 +2491,9 @@
metrics of the <a href="#style-value-length"><length></a> values must be the same.</p><p>The <a href="#style-value-length"><length></a> value(s) used to express font size must be non-negative.</p><p class="diff-chg">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span<span class="diff-del">, where the value of this style property on the anonymous span is considered to be
-<code>inherit</code></span>.</p><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontSize-example-1" class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
+<code>inherit</code></span>.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>1c</code> were specified.</p><p>The <code>tts:fontSize</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontSize-example-1" class="example"><caption>Example Fragment – Font Size</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="299px 97px"/>
@@ -2122,7 +2519,8 @@
defines the font style to apply to glyphs that are selected for glyph areas generated
by content flowed into a region, where the mapping from font
style value to specific font face or style parameterization is not determined
-by this specification.</p><p>This attribute may be specified by any style specification element or content element
+by this specification.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-fontStyle" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>normal</code> |
@@ -2137,13 +2535,18 @@
span<span class="diff-del">, where the value of this style property on the anonymous span is considered to be
<code>inherit</code></span>.</p><p>Use of values <code>oblique</code> and <code>reverseOblique</code>
denote a shear and reverse shear transformation (at an unspecified
-angle) in the inline progression dimension. A conformant processor may
-perform such a transform on a font in order to satisfy this authorial
-intent for the purpose of presentation processing. If a specified font
-style is not available or a shear or reverse shear transformation is
-not supported, then the processor must interpret the font style as if
-the value <code>normal</code> were specified for the purpose of
-presentation processing.</p><p>The <code>tts:fontStyle</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontStyle-example-1" class="example"><caption>Example Fragment – Font Style</caption><tbody><tr><td>
+angle) in the inline progression dimension.<span class="diff-del"> A
+conformant processor may perform such a transform on a font in order
+to satisfy this authorial intent for the purpose of presentation
+processing. If a specified font style is not available or a shear or
+reverse shear transformation is not supported, then the processor must
+interpret the font style as if the value <code>normal</code> were
+specified for the purpose of presentation processing.</span></p><p class="diff-add">If a specified font style is not available, then a
+presentation processor must attempt to map the specified font style
+to an available font style that has similar typographic
+characteristics, or, in the absence of such a mapping, it must
+interpret the font style as if the value <code>normal</code> were
+specified.</p><p>The <code>tts:fontStyle</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontStyle-example-1" class="example"><caption>Example Fragment – Font Style</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="331px 84px"/>
@@ -2166,7 +2569,8 @@
that defines the font weight to apply to glyphs that are selected for glyph
areas generated by content flowed into a region, where the mapping from font
weight value to specific font face or weight parameterization is not determined
-by this specification.</p><p>This attribute may be specified by any style specification element or content element
+by this specification.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-fontWeight" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>normal</code> |
@@ -2177,9 +2581,12 @@
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p class="diff-chg">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span<span class="diff-del">, where the value of this style property on the anonymous span is considered to be
-<code>inherit</code></span>.</p><p>If a specified font weight is not available, then a conformant
-processor must interpret the font weight as if the value <code>normal</code> were
-specified for the purpose of presentation processing.</p><p>The <code>tts:fontWeight</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontWeight-example-1" class="example"><caption>Example Fragment – Font Weight</caption><tbody><tr><td>
+<code>inherit</code></span>.</p><p class="diff-chg">If a specified font weight is not available, then a
+presentation processor must attempt to map the specified font weight
+to an available font weight that has similar typographic
+characteristics, or, in the absence of such a mapping, it must
+interpret the font weight as if the value <code>normal</code> were
+specified.</p><p>The <code>tts:fontWeight</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-fontWeight-example-1" class="example"><caption>Example Fragment – Font Weight</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="376px 95px"/>
@@ -2201,7 +2608,8 @@
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.8.9.</p></div></div><div class="div3">
<h4><a name="style-attribute-lineHeight" id="style-attribute-lineHeight"/>8.2.13 tts:lineHeight</h4><p>The <code>tts:lineHeight</code> attribute is used to specify a style property that
-defines the inter-baseline separation between line areas generated by content flowed into a region.</p><p>This attribute may be specified by any style specification element or content element
+defines the inter-baseline separation between line areas generated by content flowed into a region.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-lineHeight" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>normal</code> |
@@ -2213,7 +2621,9 @@
initial value of the style property must be considered to be the same
as the largest font size that applies to any <span class="diff-del">child</span><span class="diff-add">descendant</span>
element.</p><p>If specified as a <a href="#style-value-length"><length></a>, then the length must
-be non-negative.</p><p>The <code>tts:lineHeight</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-lineHeight-example-1" class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
+be non-negative.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>normal</code> were specified.</p><p>The <code>tts:lineHeight</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-lineHeight-example-1" class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="255px 190px"/>
@@ -2239,11 +2649,13 @@
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.15.4.</p></div></div><div class="div3">
<h4><a name="style-attribute-opacity" id="style-attribute-opacity"/>8.2.14 tts:opacity</h4><p>The <code>tts:opacity</code> attribute is used to specify a style property that
-defines the opacity (or transparency) of marks associated with a region (such as
+defines the opacity (or transparency) of marks associated with a
+region<span class="diff-del"> (such as
a region's background color) or marks associated with areas generated by a given
-content element to which opacity applies.</p><p>When presented onto a visual medium, the opacity of the affacted
-element is applied uniformly and on a linear scale to all marks produced by the affected
-element (and its descendants).</p><p>This attribute may be specified by any style specification element or content element
+content element to which opacity applies</span>.</p><p>When presented onto a visual medium, the opacity of the <span class="diff-chg">region</span> is applied uniformly and on a linear scale
+to all marks produced by <span class="diff-chg">content targeted to the
+region</span>.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-opacity" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-alpha"><alpha></a><span class="diff-del"> |
@@ -2252,8 +2664,8 @@
<code>1.0</code>
</td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>An <a href="#style-value-alpha"><alpha></a> value greater than 1.0 must be considered equivalent
-to an <a href="#style-value-alpha"><alpha></a> value of 1.0.</p><p>The <code>tts:opacity</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-opacity-example-1" class="example"><caption>Example Fragment – Opacity</caption><tbody><tr><td>
+</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>An <a href="#style-value-alpha"><alpha></a> value greater
+than 1.0 must be considered equivalent to an <a href="#style-value-alpha"><alpha></a> value of 1.0.</p><p>The <code>tts:opacity</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-opacity-example-1" class="example"><caption>Example Fragment – Opacity</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1" dur="5s">
<set begin="0s" dur="1s" <span class="strong">tts:opacity="1.00"</span>/>
@@ -2288,7 +2700,8 @@
<h4><a name="style-attribute-origin" id="style-attribute-origin"/>8.2.15 tts:origin</h4><p>The <code>tts:origin</code> attribute is used to specify the
<em>x</em> and <em>y</em> coordinates of the origin of a
region area with respect to the origin of the root container extent,
-if specified, or the external authoring context, if not specified.</p><p>This attribute may be specified by any style specification element or content element
+if specified, or the external authoring context, if not specified.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-origin" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>auto</code> |
@@ -2300,7 +2713,9 @@
then they must be interpreted as <em>x</em> and <em>y</em> coordinates, where the first specification
is the <em>x</em> coordinate, and the second specification is the <em>y</em> coordinate.</p><p>If the value of this attribute is <code>auto</code>, then the initial value
of the style property must be considered to be the same as the root container origin.
-The root container origin is determined by the external authoring context.</p><p>The <code>tts:origin</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-origin-example-1" class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
+The root container origin is determined by the external authoring context.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>auto</code> were specified.</p><p>The <code>tts:origin</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-origin-example-1" class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style <span class="strong">tts:origin="40px 40px"</span>/>
@@ -2320,7 +2735,8 @@
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-origin-example-1-images" class="example-images"><caption>Example Rendition – Origin</caption><tbody><tr><td><img src="images/origin.png" alt="DFXP origin style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-overflow" id="style-attribute-overflow"/>8.2.16 tts:overflow</h4><p>The <code>tts:overflow</code> attribute is used to specify a style property that
defines whether a region area is clipped or not if the descendant areas of the region overflow
-its extent.</p><p>This attribute may be specified by any style specification element or content element
+its extent.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-overflow" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>visible</code> |
@@ -2331,7 +2747,9 @@
<a href="#layout-vocabulary-region"><code>region</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p>If the value of this attribute is <code>visible</code>, then content should
not be clipped outside of the affected region, and region composition and layout
-must be performed as if the region's width and height were infinite, but with
+must be performed as if the region's width and height were
+<span class="diff-del">infinite</span><span class="diff-add">unconstrained</span>,
+but with
a well-defined origin. If the value is <code>hidden</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
@@ -2341,7 +2759,9 @@
dynamically flowed into and out of the affected region according to the values
of the <code>tts:dynamicFlow</code> style property; in this case, the
semantics of the <code>tts:dynamicFlow</code> apply whether or not the
-affected region has overflowed.</p><p>The <code>tts:overflow</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-overflow-example-1" class="example"><caption>Example Fragment – Overflow</caption><tbody><tr><td>
+affected region has overflowed.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>hidden</code> were specified.</p><p>The <code>tts:overflow</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-overflow-example-1" class="example"><caption>Example Fragment – Overflow</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="232px 40px"/>
@@ -2385,7 +2805,8 @@
§ 7.20.2.</p></div></div><div class="div3">
<h4><a name="style-attribute-padding" id="style-attribute-padding"/>8.2.17 tts:padding</h4><p>The <code>tts:padding</code> attribute is used to specify padding (or inset)
space on all sides of a region area<span class="diff-del"> or a content area produced by a content
-element</span>.</p><p>This attribute may be specified by any style specification element or content element
+element</span>.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-padding" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<a href="#style-value-length"><length></a> |
@@ -2393,7 +2814,7 @@
<a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a> |
<a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a> <a href="#style-value-length"><length></a><span class="diff-del"> |
<code>inherit</code></span>
-</td></tr><tr><td><em>Initial:</em></td><td><code>0</code></td></tr><tr><td><em>Applies to:</em></td><td>
+</td></tr><tr><td><em>Initial:</em></td><td><code>0<span class="diff-add">px</span></code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of region</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>If the value of this attribute consists of one <a href="#style-value-length"><length></a> specification,
then that length applies to all edges of the affected areas. If the value
@@ -2403,7 +2824,9 @@
before edge, the second applies to the start and end edges, and the third applies
to the after edge.
If four <a href="#style-value-length"><length></a> specifications are provided, then they apply to before, end,
-after, and start edges, respectively.</p><p>The <code>tts:padding</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-padding-example-1" class="example"><caption>Example Fragment – Padding</caption><tbody><tr><td>
+after, and start edges, respectively.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>0px</code> were specified.</p><p>The <code>tts:padding</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-padding-example-1" class="example"><caption>Example Fragment – Padding</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="446px 104px"/>
@@ -2431,7 +2854,8 @@
§ 7.7.31, 7.7.32, 7.7.33, and 7.7.34.</p></div></div><div class="div3">
<h4><a name="style-attribute-showBackground" id="style-attribute-showBackground"/>8.2.18 tts:showBackground</h4><p>The <code>tts:showBackground</code> attribute is used to specify
constraints on when the background color of a region is intended to be
-presented.</p><p>This attribute may be specified by any style specification element or content element
+presented.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-showBackground" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>always</code> |
@@ -2443,7 +2867,9 @@
background color of a region is always rendered when performing presentation
processing on a visual medium; if the value is <code>whenActive</code>,
then the background color of a region is rendered only when some
-content is selected into the region.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-showBackground-example-1" class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
+content is selected into the region.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>always</code> were specified.</p><p>The <code>tts:showBackground</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-showBackground-example-1" class="example"><caption>Example Fragment – Show Background</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:origin="0px 0px"/>
@@ -2469,7 +2895,8 @@
§ 5.3.1.</p></div></div><div class="div3">
<h4><a name="style-attribute-textAlign" id="style-attribute-textAlign"/>8.2.19 tts:textAlign</h4><p>The <code>tts:textAlign</code> attribute is used to specify a style property that
defines how inline areas are aligned within a containing block area in the inline progression
-direction.</p><p>This attribute may be specified by any style specification element or content element
+direction.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-textAlign" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>left</code> |
@@ -2480,7 +2907,9 @@
<code>inherit</code></span>
</td></tr><tr><td><em>Initial:</em></td><td><code>start</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#content-vocabulary-p"><code>p</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>The <code>tts:textAlign</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-textAlign-example-1" class="example"><caption>Example Fragment – Text Align</caption><tbody><tr><td>
+</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>start</code> were specified.</p><p>The <code>tts:textAlign</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-textAlign-example-1" class="example"><caption>Example Fragment – Text Align</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="355px 43px"/>
@@ -2511,7 +2940,8 @@
§ 7.15.9.</p></div></div><div class="div3">
<h4><a name="style-attribute-textDecoration" id="style-attribute-textDecoration"/>8.2.20 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
defines a text decoration effect to apply to glyph areas or other inline
-areas that are generated by content flowed into a region.</p><p>This attribute may be specified by any style specification element or content element
+areas that are generated by content flowed into a region.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-textDecoration" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>none</code> |
@@ -2529,7 +2959,9 @@
</td></tr><tr><td><em>Initial:</em></td><td><code>none</code></td></tr><tr><td><em>Applies to:</em></td><td><span class="diff-del"><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="#layout-vocabulary-region"><code>region</code></a>,</span><a href="#content-vocabulary-span"><code>span</code></a></td></tr><tr><td><em>Inherited:</em></td><td><span class="diff-del">no, but see prose of <a href="#xsl11">[XSL 1.1]</a>,
§ 7.16.4</span><span class="diff-add">yes</span></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 class="diff-add">For the purpose of determining applicability of this
style property, each character child of a <code>p</code> element is
-considered to be enclosed in an anonymous span.</p><p>The <code>tts:textDecoration</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-textDecoration-example-1" class="example"><caption>Example Fragment – Text Decoration</caption><tbody><tr><td>
+considered to be enclosed in an anonymous span.</p><p class="diff-add">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:textDecoration</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-textDecoration-example-1" class="example"><caption>Example Fragment – Text Decoration</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="385px 82px"/>
@@ -2541,15 +2973,14 @@
</region>
...
<p region="r1">
- The sea was wet<span <span class="strong">tts:textDecoration="noUnderline"</span>> as </span>wet<span
- <span class="strong">tts:textDecoration="noUnderline"</span>>
- could be,<br/>
- The sand was dry as dry.<br/>
- <span <span class="strong">tts:textDecoration="lineThrough"</span>>There weren't any</span>
- You
- <span <span class="strong">tts:textDecoration="lineThrough"</span>>couldn't</span>
- could not see a cloud<br/>
- Because no cloud was in the sky.
+ The sea was wet<span <span class="strong">tts:textDecoration="noUnderline"</span>> as </span>wet
+ <span <span class="strong">tts:textDecoration="noUnderline"</span>>
+ could be,<br/>
+ The sand was dry as dry.<br/>
+ <span <span class="strong">tts:textDecoration="lineThrough"</span>>There weren't any</span>
+ You <span <span class="strong">tts:textDecoration="lineThrough"</span>>couldn't</span>
+ could not see a cloud<br/>
+ Because no cloud was in the sky.
</span>
</p>
</pre></div>
@@ -2558,7 +2989,8 @@
§ 7.16.4.</p></div></div><div class="div3">
<h4><a name="style-attribute-textOutline" id="style-attribute-textOutline"/>8.2.21 tts:textOutline</h4><p>The <code>tts:textOutline</code> attribute is used to specify a style property that
defines a text outline effect to apply to glyphs that are selected for glyph areas generated
-by content flowed into a region.</p><p>This attribute may be specified by any style specification element or content element
+by content flowed into a region.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-textOutline" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>none</code> |
@@ -2576,7 +3008,9 @@
present, then it denotes the outline color; if no <em>color</em> term is
present, the computed value of the <code>tts:color</code> applies. The first
<em>length</em> term denotes the outline thickness and the second length
-term, if present, indicates the blur radius.</p><p>The <code>tts:textOutline</code> style is illustrated by the following
+term, if present, indicates the blur radius.</p><p class="diff-add">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:textOutline</code> style is illustrated by the following
example.</p><table summary="HTML Table" id="style-attribute-textOutline-example-1" class="example"><caption>Example Fragment – Text Outline</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -2601,7 +3035,8 @@
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-textOutline-example-1-images" class="example-images"><caption>Example Rendition – Text Outline</caption><tbody><tr><td><img src="images/textOutline.png" alt="backgroundColor style property"/></td></tr></tbody></table></div><div class="div3">
<h4><a name="style-attribute-unicodeBidi" id="style-attribute-unicodeBidi"/>8.2.22 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
defines a directional embedding or override according to
-the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any style specification element or content element
+the Unicode bidirectional algorithm.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-unicodeBidi" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>normal</code> |
@@ -2615,7 +3050,9 @@
<a href="#content-vocabulary-span"><code>span</code></a>
</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p class="diff-add">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
-span.</p><p>The <code>tts:unicodeBidi</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-unicodeBidi-example-1" class="example"><caption>Example Fragment – Unicode Bidirectionality</caption><tbody><tr><td>
+span.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>normal</code> were specified.</p><p>The <code>tts:unicodeBidi</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-unicodeBidi-example-1" class="example"><caption>Example Fragment – Unicode Bidirectionality</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="265px 84px"/>
@@ -2639,7 +3076,8 @@
§ 7.27.6.</p></div></div><div class="div3">
<h4><a name="style-attribute-visibility" id="style-attribute-visibility"/>8.2.23 tts:visibility</h4><p>The <code>tts:visibility</code> attribute is used to specify a style property that
defines whether generated areas are visible or not when rendered on a visual
-presentation medium.</p><p>This attribute may be specified by any style specification element or content element
+presentation medium.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-visibility" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>visible</code> |
@@ -2656,7 +3094,9 @@
</td></tr><tr><td><span class="diff-add"><em>Inherited:</em></span></td><td><span class="diff-add">yes</span></td></tr><tr><td><span class="diff-add"><em>Percentages:</em></span></td><td><span class="diff-add">N/A</span></td></tr><tr><td><span class="diff-del"><em>Animatable:</em></span></td><td><span class="diff-del">discrete</span></td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p class="diff-add">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span.</p><p>The <code>tts:visibility</code> style has no affect on content layout or
-composition, but merely determines whether composed content is visible or not.</p><p>The <code>tts:visibility</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-visibility-example-1" class="example"><caption>Example Fragment – Visibility</caption><tbody><tr><td>
+composition, but merely determines whether composed content is visible or not.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>visible</code> were specified.</p><p>The <code>tts:visibility</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-visibility-example-1" class="example"><caption>Example Fragment – Visibility</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="398px 121px"/>
@@ -2693,7 +3133,8 @@
§ 7.28.8.</p></div></div><div class="div3">
<h4><a name="style-attribute-wrapOption" id="style-attribute-wrapOption"/>8.2.24 tts:wrapOption</h4><p>The <code>tts:wrapOption</code> attribute is used to specify a style property that
defines whether or not automatic line wrapping (breaking) applies within the context of
-the affected element.</p><p>This attribute may be specified by any style specification element or content element
+the affected element.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-wrapOption" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>wrap</code> |
@@ -2704,7 +3145,9 @@
</td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p class="diff-chg">For the purpose of determining applicability of this style property,
each character child of a <code>p</code> element is considered to be enclosed in an anonymous
span<span class="diff-del">, where the value of this style property on the anonymous span is considered to be
-<code>inherit</code></span>.</p><p>The <code>tts:wrapOption</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-wrapOption-example-1" class="example"><caption>Example Fragment – Wrap Option</caption><tbody><tr><td>
+<code>inherit</code></span>.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>wrap</code> were specified.</p><p>The <code>tts:wrapOption</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-wrapOption-example-1" class="example"><caption>Example Fragment – Wrap Option</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="192px 117px"/>
@@ -2727,7 +3170,8 @@
§ 7.15.13.</p></div></div><div class="div3">
<h4><a name="style-attribute-writingMode" id="style-attribute-writingMode"/>8.2.25 tts:writingMode</h4><p>The <code>tts:writingMode</code> attribute is used to specify a style property that
defines the block and inline progression directions to be used for the purpose of
-stacking block and inline areas within a region area.</p><p>This attribute may be specified by any style specification element or content element
+stacking block and inline areas within a region area.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-writingMode" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>lrtb</code> |
@@ -2740,7 +3184,9 @@
<code>inherit</code></span>
</td></tr><tr><td><em>Initial:</em></td><td><code>lrtb</code></td></tr><tr><td><em>Applies to:</em></td><td>
<a href="#layout-vocabulary-region"><code>region</code></a>
-</td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p>The <code>tts:writingMode</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-writingMode-example-1" class="example"><caption>Example Fragment – Writing Mode</caption><tbody><tr><td>
+</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><span class="diff-del">none</span><span class="diff-add">discrete</span></td></tr></tbody></table><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>lrtb</code> were specified.</p><p>The <code>tts:writingMode</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-writingMode-example-1" class="example"><caption>Example Fragment – Writing Mode</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:extent="50px 570px"/>
@@ -2776,7 +3222,8 @@
represented by this attribute are based upon that defined by <a href="#xsl11">[XSL 1.1]</a>,
§ 7.27.7.</p></div></div><div class="div3">
<h4><a name="style-attribute-zIndex" id="style-attribute-zIndex"/>8.2.26 tts:zIndex</h4><p>The <code>tts:zIndex</code> attribute is used to specify a style property that
-defines the front-to-back ordering of region areas in the case that they overlap.</p><p>This attribute may be specified by any style specification element or content element
+defines the front-to-back ordering of region areas in the case that they overlap.</p><p>This attribute may be specified by any
+<span class="diff-chg">element type</span>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p><table summary="HTML Table" id="style-property-details-zIndex" class="common"><col width="25%" span="1"/><tbody><tr><td><em>Values:</em></td><td>
<code>auto</code> |
@@ -2790,7 +3237,9 @@
order is defined as the postorder traversal of a document
instance.</p><p>The semantics of the value <code>auto</code> are those defined by
<a href="#xsl11">[XSL 1.1]</a>, § 7.28.9, where the <code>tt</code> element
-is considered to establish the root stacking context.</p><p>The <code>tts:zIndex</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-zIndex-example-1" class="example"><caption>Example Fragment – Z Index</caption><tbody><tr><td>
+is considered to establish the root stacking context.</p><p class="diff-add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>auto</code> were specified.</p><p>The <code>tts:zIndex</code> style is illustrated by the following example.</p><table summary="HTML Table" id="style-attribute-zIndex-example-1" class="example"><caption>Example Fragment – Z Index</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<region xml:id="r1">
<style tts:origin="0px 0px"/>
@@ -2861,7 +3310,9 @@
3.2.4.1.<span class="diff-add"> If the value represented is less than 0.0,
then it must be interpreted as equal to 0.0; similarly, if the value
represented is greater than 1.0, then it must be interpreted as
-1.0.</span></p></div><div class="div3">
+1.0.</span></p><p class="diff-add">If a presentation processor does not support a specific,
+valid opacity value, then it must interpret it as being equal to the
+closest supported value.</p></div><div class="div3">
<h4><a name="style-value-color" id="style-value-color"/>8.3.2 <color></h4><p>A <color> expression is used to specify a named color, exact RGB color triple,
or exact RGBA color tuple, where the alpha component, if expressed,
is maximum (255) at 100% opacity
@@ -2896,10 +3347,12 @@
semantics of compositing functions are defined with respect to the use of
the <a href="#srgb">[SRGB]</a> color space for both inputs and outputs of
the composition function.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of <a href="#srgb">[SRGB]</a> for the stated semantics of
-composition is not mean to prevent an actual processor from using some
+composition is not mean<span class="diff-add">t</span> to prevent an actual processor from using some
other color space either for internal or external purposes. For
example, a presentation processor may ultimately convert the SRGB values
-used here to the YUV color space for rendition on a television device.</p></div></div><div class="div3">
+used here to the YUV color space for rendition on a television device.</p></div><p class="diff-add">If a presentation processor does not support a specific,
+valid color or alpha value, then it must interpret it as being equal
+to the closest supported value.</p></div><div class="div3">
<h4><a name="style-value-digit" id="style-value-digit"/>8.3.3 <digit></h4><p>A <digit> is used to express integers and other types of numbers or tokens.</p><table summary="HTML Table" id="digit-style-expression-syntax" class="syntax"><caption>Syntax Representation – <digit></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<digit>
@@ -2934,14 +3387,14 @@
| <a href="#style-value-quotedString"><quotedString></a>
</pre></div>
</td></tr></tbody></table></div><div class="div3">
-<h4><a name="style-value-flowFunction" id="style-value-flowFunction"/>8.3.6 <flowFunction></h4><p>A <flowFunction> expression specifies a unit of content to be dynamic
-flowed into, within, and from a region according to an optional
-dynamic flow style, flow transition effect, and flow transition effect
-style.</p><table summary="HTML Table" id="flowFunction-style-expression-syntax" class="syntax"><caption>Syntax Representation – <flowFunction></caption><tbody><tr><td>
+<h4><a name="style-value-flowFunction" id="style-value-flowFunction"/>8.3.6 <flowFunction></h4><p>A <flowFunction> expression specifies a unit of content to be
+dynamic flowed into<span class="diff-del">, within,</span> and <span class="diff-chg">out of</span> a region according to an optional dynamic
+flow style<span class="diff-del">, flow transition effect, and flow
+transition effect style</span>.</p><table summary="HTML Table" id="flowFunction-style-expression-syntax" class="syntax"><caption>Syntax Representation – <flowFunction></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<flowFunction>
- : "in(" flowArguments ")"
- | "within(" flowArguments ")"
+ : "in(" flowArguments ")"<span class="diff-del">
+ | "within(" flowArguments ")"</span>
| "out(" flowArguments ")"
flowArguments
@@ -2959,8 +3412,8 @@
flowStyle
: "jump"
- | "smooth"
- | "fade"
+ | "smooth"<span class="diff-del">
+ | "fade"</span>
| extensionToken<span class="diff-del">
flowTransition
@@ -2976,10 +3429,10 @@
: "x-" <token>
</pre></div>
</td></tr></tbody></table><p>Dynamic flow can be specified independently for flowing content
-into its region, flowing it within its region, and flowing it out of
-its region. These three phases of dynamic flow are specified using the
-<code>in()</code>, <code>within()</code>, and <code>out()</code> flow
-functions respectively.</p><p>Dynamic flow occurs on the basis of specific visual or semantic
+into its region<span class="diff-del">, flowing it within its
+region,</span> and flowing it out of its region. These <span class="diff-chg">two</span> phases of dynamic flow are specified using the
+<code>in()</code><span class="diff-del">, <code>within()</code>,</span>
+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-del"><code>pixel</code>, </span><code>glyph</code>,
<code>inline</code>, <code>line</code>, and <code>block</code>, the
unit of dynamic flow is based upon a visually rendered construct
@@ -2996,20 +3449,21 @@
Ideographic characters, then <code>word</code> is to be interpreted
as if <code>character</code> were specified.</p></li><li><p>Otherwise, <code>word</code> is to be interpreted as denoting
a sequence of one or more characters that are not interpreted as an
-XML whitespace character.</p></li></ol><p>When a flow unit is flowed into, within, or out of its region, the
-manner by which the unit is flowed is controlled by the optional
-<code>flowStyle</code> argument of the relevant flow function. If the
-flow style is specified as <code>jump</code>, or if no flow style is
-specified, then the flow unit is instantaneously transitioned into,
-within, or out of the region. If the flow style is
-<code>smooth</code>, then the flow unit is smoothly transitioned by
-means of pixel based exposure, movement, or hiding, respectively. If
-the flow style is <code>fade</code>, then the flow unit is faded into
-or out of the region by continuously incrementing or decrementing the
-alpha component of the affected content.</p><p class="diff-add">If a presentation processor that supports dynamic flow
-does not support either or both the <code>smooth</code> or
-<code>fade</code> flow styles, then these flow styles must be
-interpreted as if <code>jump</code> flow style were specified.</p><p class="diff-del">In addition to the primary flow style, an optional flow transition
+XML whitespace character.</p></li></ol><p>When a flow unit is flowed into<span class="diff-del">,
+within,</span> or out of its region, the manner by which the unit is
+flowed is controlled by the optional <code>flowStyle</code> argument
+of the relevant flow function. If the flow style is specified as
+<code>jump</code>, or if no flow style is specified, then the flow
+unit is instantaneously transitioned into, within, or out of the
+region. If the flow style is <code>smooth</code>, then the flow unit
+is smoothly transitioned by means of pixel based exposure, movement,
+or hiding, respectively.<span class="diff-del"> If the flow style is
+<code>fade</code>, then the flow unit is faded into or out of the
+region by continuously incrementing or decrementing the alpha
+component of the affected content.</span></p><p class="diff-add">If a presentation processor that supports dynamic flow
+does not the <code>smooth</code> flow style, then this flow style must
+be interpreted as if the <code>jump</code> flow style were
+specified.</p><p class="diff-del">In addition to the primary flow style, an optional flow transition
effect and flow transition effect style may be specified, in which
case the transition effect is additively (and simultaneously) applied
to the primary flow style transition.</p><p class="diff-del">For the permitted values of <code>flowTransition</code> and
@@ -3071,7 +3525,10 @@
then it may be interpreted as equivalent to either <code>monospaceSansSerif</code>
or <code>monospaceSerif</code>. The generic family names <code>sansSerif</code>
and <code>serif</code> are to be interpreted as equivalent to <code>proportionalSansSerif</code>
-and <code>proportionalSerif</code>, respectively.</p></div><div class="div3">
+and <code>proportionalSerif</code>, respectively.</p><p class="diff-add">If the generic family name <code>default</code> is specified (or implied by
+an initial value), then its typographic characteristics is considered to be implementation
+dependent; however, it is recommended that this default font family be mapped to
+an monospaced, sans-serif font.</p></div><div class="div3">
<h4><a name="style-value-hexDigit" id="style-value-hexDigit"/>8.3.9 <hexDigit></h4><p>A <hexDigit> is used to express integers and other types of numbers or tokens
that employ base 16 arithmetic.</p><p>For the purpose of parsing, no distinction must be made between lower and upper case.</p><table summary="HTML Table" id="hexDigit-style-expression-syntax" class="syntax"><caption>Syntax Representation – <hexDigit></caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -3378,7 +3835,7 @@
tuple <code>[category, type, value expression]</code></p><table summary="HTML Table" id="conceptual-definition-example-style-property" class="example"><caption>Example – conceptual style property</caption><tbody><tr><td>
<div class="exampleInner"><pre>
[
- ["http://www.w3.org/2006/10/ttaf1#style", "color"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
["specified", <em>color</em>, "red"]
]
</pre></div>
@@ -3391,19 +3848,19 @@
<div class="exampleInner"><pre>
{
[
- ["http://www.w3.org/2006/10/ttaf1#style", "backgroundColor"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "backgroundColor"],
["specified", <em>color</em>, 0x00FF00 ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "color"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
["specified", <em>color</em>, "red" ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "fontSize"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "fontSize"],
["specified", <em>length</em>, "1c" ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "lineHeight"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "lineHeight"],
["specified", <em>length</em>, "117%" ]
]
}
@@ -3414,19 +3871,19 @@
<div class="exampleInner"><pre>
{
[
- ["http://www.w3.org/2006/10/ttaf1#style", "backgroundColor"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "backgroundColor"],
["specified", <em>color</em>, 0x00FF00 ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "color"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
["computed", <em>color</em>, 0xFF0000 ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "fontSize"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "fontSize"],
["computed", <em>length</em>, "24px" ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "lineHeight"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "lineHeight"],
["computed", <em>length</em>, "28px" ]
]
}
@@ -3465,7 +3922,6 @@
<em>E</em>, <em>SSS(E)</em>;</p></li><li><p><span class="strong">[inline styling]</span> for each
style property <em>P</em> expressed as a specified styling
attribute of <em>E</em>,
-
merge <em>P</em> into the specified style
set of <em>E</em>, <em>SSS(E)</em>;</p></li><li><p><span class="strong">[implicit inheritance]</span> if the
element type of <em>E</em> is not the styling element type
@@ -3584,7 +4040,7 @@
<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>
</pre></div>
-</td></tr></tbody></table><p>The declared value of an inline style attribute on a <code>region</code>
+</td></tr></tbody></table><p class="diff-del">The declared value of an inline style attribute on a <code>region</code>
element must not be <code>inherit</code>.</p><p class="diff-del">A <code>region</code> element is considered to define a computed style
specification set, where the set is determined using the
following ordered rules:</p><div class="diff-del"><li><p>If a <code>style</code> attribute is specified on the <code>region</code> element,
@@ -3642,9 +4098,9 @@
a <code>region</code> element, then it must be interpreted as having
<em>parallel</em> time containment semantics.</p><p class="diff-add">If a <a href="#metadata-attribute-role"><code>ttm:role</code></a> attribute is
specified on a <code>region</code> element, then it must adhere to the
-value syntax defined by <a href="#metadata-attribute-role-syntax"><b>Syntax Representation – ttm:role</b></a>, and where the role identified
-by this attribute expresses the semantic role of the region
-independently from the semantic role of any content targeted to
+value syntax defined by <a href="#metadata-attribute-role-syntax"><b>Syntax Representation – ttm:role</b></a>, and where the role(s) identified
+by this attribute expresses the semantic role(s) of the region
+independently from the semantic role(s) of any content targeted to
(associated with) the region.</p></div></div><div class="div2">
<h3><a name="layout-attribute-vocabulary" id="layout-attribute-vocabulary"/>9.2 <span class="diff-add">Layout </span>Attribute Vocabulary</h3><p>This section defines the <a href="#layout-attribute-region"><b>9.2.1 region</b></a> attribute used with content elements.</p><div class="div3">
<h4><a name="layout-attribute-region" id="layout-attribute-region"/>9.2.1 region</h4><p>The <code>region</code> attribute is used to reference a <code>region</code>
@@ -3657,7 +4113,7 @@
implementation is permitted provided that the externally observable
results are consistent with the results produced by this model.
</p><div class="diff-add">
-<h4><a name="semantics-default-region" id="semantics-default-region"/>9.3.1 Default Region</h4><p>If a TT AF document instance does not specify a
+<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 identify of the default region is consider 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
@@ -3778,7 +4234,16 @@
<code>none</code>, map the element to a distinct <code>fo:block</code> element,
populating the style properties of <code>fo:block</code> by using the computed
style<span class="diff-del"> specification</span>
-set associated with each original TT AF content element;</p></li><li><p>for each <code>span</code> element that is not
+set associated with each original TT AF content element;</p></li><li><p class="diff-add">for the resulting <code>fo:block</code> formatting object
+produced in the previous step that corresponds to the <code>body</code>
+element, synthesize and append to the end of its children an empty
+<code>fo:block</code> with the following attributes:
+<code>space-after.optimum</code>, <code>space-after.maximum</code>, and
+<code>space-after.conditionality</code>, where the value of the former
+two attributes is the height or width of the containing
+<code>fo:block-container</code> element, whichever of these is designated
+as the block progression dimension, and where the value of the last is
+<code>retain</code>;</p></li><li><p>for each <code>span</code> element that is not
associated with a <code>tts:display</code> style property with the value
<code>none</code> and for each anonymous
span<span class="diff-add"> that is a child of a <code>p</code> or <code>span</code> element</span>,
@@ -3803,14 +4268,20 @@
if processing
requires presentation on a visual medium, then apply the formatting semantics
prescribed by <a href="#xsl11">[XSL 1.1]</a> in order to produce an XSL FO area tree that
-may then be subsequently rendered onto the visual medium.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Due to the possible presence of TT AF style properties
+may then be subsequently rendered onto the visual medium.</p><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>In the XSL FO area tree produced by formatting
+<em>DOC<sub>FO</sub></em>, the <code>page-viewport-area</code>,
+which is generated by <code>fo:page-sequence</code> element by
+reference to the sole generated <code>fo:simple-page-master</code>
+element, corresponds to the <em>root container region</em> defined
+above in <a href="#definitions"><b>2 Definitions</b></a>.</p></div></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Due to the possible presence of TT AF style properties
or style property values in a given DFXP document instance for which
there is no <a href="#xsl11">[XSL 1.1]</a> counterpart, the use of a compliant <a href="#xsl11">[XSL 1.1]</a> formatting processor
is not necessarily sufficient to satisfy the presentation
semantics defined by this specification.</p></div></div><div class="div3">
<h4><a name="semantics-region-layout-example" id="semantics-region-layout-example"/>9.3.4 Elaborated Example</h4><p>An example of the processing steps described above is elaborated below, starting with <a href="#region-mapping-example-1-s"><b>Example – Sample Source Document</b></a>.</p><table summary="HTML Table" id="region-mapping-example-1-s" class="example"><caption>Example – Sample Source Document</caption><tbody><tr><td>
-<div class="exampleInner"><pre><tt xml:lang="en" xmlns="http://www.w3.org/2006/10/ttaf1"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
+ xmlns="http://www.w3.org/2006/10/ttaf1"
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<head>
<layout>
<region xml:id="r1">
@@ -3835,7 +4306,7 @@
</region>
</layout>
</head>
- <body tts:extent="640px 480px" xml:id="b1">
+ <body xml:id="b1">
<div xml:id="d1" begin="0s" dur="2s">
<p xml:id="p1" region="r1">Text 1</p>
<p xml:id="p2" region="r2">Text 2</p>
@@ -3857,8 +4328,9 @@
are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The intermediate documents shown below are not valid DFXP document instances,
but rather, are representations of possible internal processing states used for
didactic purposes.</p></div><table summary="HTML Table" id="region-mapping-example-1-i0" class="example"><caption>Example – Intermediate Document – [0s,1s)</caption><tbody><tr><td>
-<div class="exampleInner"><pre><tt xml:lang="en" xmlns="http://www.w3.org/2006/10/ttaf1"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
+ xmlns="http://www.w3.org/2006/10/ttaf1"
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<head>
<layout>
<region xml:id="r1">
@@ -3870,7 +4342,7 @@
<style tts:color="red"/>
<style tts:textAlign="center"/>
<style tts:displayAlign="center"/>
- <body tts:extent="640px 480px" xml:id="b1-1">
+ <body xml:id="b1-1">
<div xml:id="d1-1">
<p xml:id="p1">Text 1</p>
</div>
@@ -3885,7 +4357,7 @@
<style tts:color="yellow"/>
<style tts:textAlign="center"/>
<style tts:displayAlign="center"/>
- <body tts:extent="640px 480px" xml:id="b1-2">
+ <body xml:id="b1-2">
<div xml:id="d1-2">
<p xml:id="p2">Text 2</p>
</div>
@@ -3900,7 +4372,7 @@
<div class="exampleInner"><pre><fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
<fo:layout-master-set>
<fo:simple-page-master master-name="m1"
- page-width="640px" page-height="480px">
+ page-width="640px" page-height="480px">
<fo:region-body/>
</fo:simple-page-master>
</fo:layout-master-set>
@@ -3908,8 +4380,8 @@
<fo:flow flow-name="xsl-region-body">
<!-- region (r1) -->
<fo:block-container id="r1" absolute-position="absolute"
- left="10px" top="100px" width="620px" height="96px"
- background-color="black" display-align="center">
+ left="10px" top="100px" width="620px" height="96px"
+ background-color="black" display-align="center">
<!-- body (b1) -->
<fo:block id="b1-1">
<!-- div (d1) -->
@@ -3920,12 +4392,17 @@
color="red">Text 1</fo:inline>
</fo:block>
</fo:block>
+ <!-- body's space filler ->
+ <fo:block
+ space-after.optimum="96px"
+ space-after.maximum="96px"
+ space-after.conditionality="retain"/>
</fo:block>
</fo:block-container>
<!-- region (r2) -->
<fo:block-container id="r2" absolute-position="absolute"
- left="10px" top="300px" width="620px" height="96px"
- background-color="black" display-align="center">
+ left="10px" top="300px" width="620px" height="96px"
+ background-color="black" display-align="center">
<!-- body (b1) -->
<fo:block id="b1-2">
<!-- div (d1) -->
@@ -3936,6 +4413,11 @@
color="yellow">Text 2</fo:inline>
</fo:block>
</fo:block>
+ <!-- body's space filler ->
+ <fo:block
+ space-after.optimum="96px"
+ space-after.maximum="96px"
+ space-after.conditionality="retain"/>
</fo:block>
</fo:block-container>
</fo:flow>
@@ -3948,8 +4430,9 @@
<code>p4</code> (and their ancestors) are selected into region <code>r1</code>
and paragraphs <code>p2</code> and <code>p3</code> (and their ancestors) are
selected into region <code>r2</code>.</p><table summary="HTML Table" id="region-mapping-example-1-i1" class="example"><caption>Example – Intermediate Document – [1s,2s)</caption><tbody><tr><td>
-<div class="exampleInner"><pre><tt xml:lang="en" xmlns="http://www.w3.org/2006/10/ttaf1"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
+ xmlns="http://www.w3.org/2006/10/ttaf1"
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<head>
<layout>
<region xml:id="r1">
@@ -3961,7 +4444,7 @@
<style tts:color="red"/>
<style tts:textAlign="center"/>
<style tts:displayAlign="center"/>
- <body tts:extent="640px 480px" xml:id="b1-1">
+ <body xml:id="b1-1">
<div xml:id="d1-1">
<p xml:id="p1">Text 1</p>
</div>
@@ -3979,7 +4462,7 @@
<style tts:color="yellow"/>
<style tts:textAlign="center"/>
<style tts:displayAlign="center"/>
- <body tts:extent="640px 480px" xml:id="b1-2">
+ <body xml:id="b1-2">
<div xml:id="d1-2">
<p xml:id="p2">Text 2</p>
</div>
@@ -3996,8 +4479,9 @@
interval [2,3), at which time only division <code>d2</code> is temporally active,
and where paragraphs <code>p4</code> and <code>p3</code> (and their ancestors)
are selected into regions <code>r1</code> and <code>r2</code>, respectively.</p><table summary="HTML Table" id="region-mapping-example-1-i2" class="example"><caption>Example – Intermediate Document – [2s,3s)</caption><tbody><tr><td>
-<div class="exampleInner"><pre><tt xml:lang="en" xmlns="http://www.w3.org/2006/10/ttaf1"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<div class="exampleInner"><pre><tt tts:extent="640px 480px" xml:lang="en"
+ xmlns="http://www.w3.org/2006/10/ttaf1"
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<head>
<layout>
<region xml:id="r1">
@@ -4009,7 +4493,7 @@
<style tts:color="red"/>
<style tts:textAlign="center"/>
<style tts:displayAlign="center"/>
- <body tts:extent="640px 480px" xml:id="b1-1">
+ <body xml:id="b1-1">
<div xml:id="d2-1">
<p xml:id="p4">Text 4</p>
</div>
@@ -4024,7 +4508,7 @@
<style tts:color="yellow"/>
<style tts:textAlign="center"/>
<style tts:displayAlign="center"/>
- <body tts:extent="640px 480px" xml:id="b1-2">
+ <body xml:id="b1-2">
<div xml:id="d2-2">
<p xml:id="p3">Text 3</p>
</div>
@@ -4204,7 +4688,8 @@
<h3><a name="animation-element-vocabulary" id="animation-element-vocabulary"/>11.1 <span class="diff-add">Animation </span>Element Vocabulary</h3><p>The following elements specify the structure and principal animation aspects of a
document instance:</p><ul><li><p><a href="#animation-vocabulary-set"><b>11.1.1 set</b></a></p></li></ul><div class="div3">
<h4><a name="animation-vocabulary-set" id="animation-vocabulary-set"/>11.1.1 set</h4><p>The <code>set</code> element is used as a child element of a content
-element in order to express a discrete change of some style parameter value
+element<span class="diff-add"> or a <code>region</code> element</span>
+in order to express a discrete change of some style parameter value
that applies over some time interval.</p><p>The <code>set</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group.</p><table summary="HTML Table" id="elt-syntax-set" class="syntax"><caption>XML Representation – Element Information Item: set</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -4221,7 +4706,48 @@
</set>
</pre></div>
</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The use of multiple <code>set</code> element children may be used to effect fade and
-position transitions.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>set</code> element
+position transitions.</p></div><p class="diff-add">An example of using the <code>set</code> element to animate content
+styling is illustrated below:</p><table summary="HTML Table" id="animation-vocabulary-set-example-1" class="example"><caption><span class="diff-add">Example Fragment – Content Style Animation</span></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<span class="diff-add">...
+<p dur="5s" tts:color="yellow">
+<span class="strong"><set begin="1s" dur="1s" tts:color="red"/></span>
+<span class="strong"><set begin="2s" dur="1s" tts:color="green"/></span>
+<span class="strong"><set begin="3s" dur="1s" tts:color="red"/></span>
+Text with Flashing Colors!
+</p>
+...</span>
+</pre></div>
+</td></tr></tbody></table><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the foreground color of the content "Text
+with Flashing Colors" is animated from yellow, to red, to green, to
+red, then back to yellow over a 5 second period.</p></div></div><p class="diff-add">An example of using the <code>set</code> element to animate region
+styling is illustrated below:</p><table summary="HTML Table" id="animation-vocabulary-set-example-2" class="example"><caption><span class="diff-add">Example Fragment – Region Style Animation</span></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<span class="diff-add"><tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"
+ xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter"
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling"
+ ttp:cellResolution="40 16">
+ <head>
+ <layout>
+ <region xml:id="r1" timeContainer="seq">
+ <span class="strong"><set dur="10s" tts:origin=" 8c 14c"/></span>
+ <span class="strong"><set dur="2s" tts:origin=" 2c 2c"/></span>
+ <span class="strong"><set dur="3s" tts:origin=" 8c 14c"/></span>
+ <span class="strong"><set dur="2s" tts:origin="14c 4c"/></span>
+ <span class="strong"><set dur="10s" tts:origin=" 8c 14c"/></span>
+ <style tts:extent="24c 2c"/>
+ </region>
+ </layout>
+ </head>
+ <body region="r1">...</body>
+</tt></span>
+</pre></div>
+</td></tr></tbody></table><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, the root container region is divided into a
+cell grid of 40 columns and 16 rows. A region, <code>r1</code>, with
+dimensions of 24 columns and 2 rows is then positioned within the
+root container region, with its position varying over time in order to
+create an effect of moving the region, which may be desirable so as
+to avoid obscuring characters in an underlying video with captions.</p></div></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>set</code> element
are based upon that defined by <a href="#smil21">[SMIL 2.1]</a>,
§ 3.5.2.</p></div></div></div><div class="div2">
<h3><a name="animation-attribute-vocabulary" id="animation-attribute-vocabulary"/>11.2 <span class="diff-add">Animation </span>Attribute Vocabulary</h3><p>No animation related attribute vocabulary is defined for use in the
@@ -4229,7 +4755,8 @@
<h2><a name="metadata" id="metadata"/>12 Metadata</h2><p>This section specifies the <em>metadata</em> matter of the core
vocabulary catalog, where
metadata is to be understood as a separable layer of information that applies to
-content, style, layout, timing, and even metadata itself, where the information
+<span class="diff-add">parameters, </span>content,
+style, layout, timing, and even metadata itself, where the information
represented by metadata takes one of two forms: (1) metadata defined by this
specification for standardized use in a document instance, and (2) arbitrary
metadata defined outside of the scope of this specification, whose use and
@@ -4242,8 +4769,12 @@
<h4><a name="metadata-vocabulary-metadata" id="metadata-vocabulary-metadata"/>12.1.1 metadata</h4><p>The <code>metadata</code> element functions as a generic container for metadata
information.</p><p>Metadata information may be expressed by a <code>metadata</code> element
in one of two (non-mutually exclusive) manners: (1) by specifying one
-or more metadata attributes on the element, and (2) by specifying one
-or more <code>metadata</code> child elements that express metadata. Both types of metadata
+or more metadata attributes on the<span class="diff-add"> <code>metadata</code></span>
+element, and (2) by specifying one
+or more
+<span class="diff-del"><code>metadata</code> </span>child elements
+<span class="diff-add">in the <code>metadata</code> element</span>
+that express metadata. Both types of metadata
are referred to in this document as <em>metadata items</em>.</p><table summary="HTML Table" id="elt-syntax-metadata" class="syntax"><caption>XML Representation – Element Information Item: metadata</caption><tbody><tr><td>
<div class="exampleInner"><pre>
<metadata
@@ -4260,7 +4791,43 @@
context of where it appears. The core vocabulary catalog permits an arbitrary number of
<code>metadata</code> element children of any non-empty element type except
for the <code>body</code> element. See specific element vocabulary
-definitions for any constraints that apply to such usage.</p></div></div><div class="div3">
+definitions for any constraints that apply to such usage.</p></div><p class="diff-add">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><span class="diff-add">Example Fragment – Document Metadata</span></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<span class="diff-add">...
+<head>
+ <metadata xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
+ <ttm:title>Document Metadata Example</ttm:title>
+ <ttm:desc>This document employs document metadata.</ttm:desc>
+ </metadata>
+</head>
+...</span>
+</pre></div>
+</td></tr></tbody></table><p/><p class="diff-add">The use of element metadata is illustrated by the following example.</p><table summary="HTML Table" id="metadata-vocabulary-metadata-example-2" class="example"><caption><span class="diff-add">Example Fragment – Element Metadata</span></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<span class="diff-add">...
+<div>
+ <metadata xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
+ <ttm:title>Chapter 6 – Sherlock Holmes Gives a Demonstration</ttm:title>
+ <ttm:desc>Holmes shows Watson how the murderer entered the window.</ttm:desc>
+ </metadata>
+</div>
+...</span>
+</pre></div>
+</td></tr></tbody></table><p/><p class="diff-add">The use of metadata attribute items is illustrated by the following example.</p><table summary="HTML Table" id="metadata-vocabulary-metadata-example-3" class="example"><caption><span class="diff-add">Example Fragment – Metadata Attribute Items</span></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<span class="diff-add">...
+<div xmlns:ext="http://foo.bar.baz/ttaf1#metadata">
+ <metadata ext:ednote="remove this division prior to publishing"/>
+</div>
+...</span>
+</pre></div>
+</td></tr></tbody></table><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, a global attribute from a foreign (external)
+namespace is used to express a metadata attribute that applies
+semantically to the containing <code>div</code> element. Note that the
+attribute may also be expressed directly on the <code>div</code> element;
+however, in this case the author wishes to segregate certain metadata
+attributes by expressing them indirectly on <code>metadata</code>
+elements.</p></div></div><p/></div><div class="div3">
<h4><a name="metadata-vocabulary-title" id="metadata-vocabulary-title"/>12.1.2 ttm:title</h4><p>The <code>ttm:title</code> element is used to express a human-readable title of
a specific element instance.</p><table summary="HTML Table" id="elt-syntax-metadata-title" class="syntax"><caption>XML Representation – Element Information Item: ttm:title</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -4272,7 +4839,9 @@
<em>Content:</em> #PCDATA
</ttm:title>
</pre></div>
-</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:title</code> element is defined by this specification.</p></div></div><div class="div3">
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:title</code> element is defined by this specification.</p></div><p class="diff-add">Examples of the <code>ttm:name</code> element are shown above in
+<a href="#metadata-vocabulary-metadata-example-1"><b>Example Fragment – Document Metadata</b></a> and
+<a href="#metadata-vocabulary-metadata-example-2"><b>Example Fragment – Element Metadata</b></a>.</p></div><div class="div3">
<h4><a name="metadata-vocabulary-desc" id="metadata-vocabulary-desc"/>12.1.3 ttm:desc</h4><p>The <code>ttm:desc</code> element is used to express a human-readable description of
a specific element instance.</p><table summary="HTML Table" id="elt-syntax-metadata-desc" class="syntax"><caption>XML Representation – Element Information Item: ttm:desc</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -4284,7 +4853,9 @@
<em>Content:</em> #PCDATA
</ttm:desc>
</pre></div>
-</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:desc</code> element is defined by this specification.</p></div></div><div class="div3">
+</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>No specific use of the <code>ttm:desc</code> element is defined by this specification.</p></div><p class="diff-add">Examples of the <code>ttm:desc</code> element are shown above in
+<a href="#metadata-vocabulary-metadata-example-1"><b>Example Fragment – Document Metadata</b></a> and
+<a href="#metadata-vocabulary-metadata-example-2"><b>Example Fragment – Element Metadata</b></a>.</p></div><div class="div3">
<h4><a name="metadata-vocabulary-copyright" id="metadata-vocabulary-copyright"/>12.1.4 ttm:copyright</h4><p>The <code>ttm:copyright</code> element is used to express a human-readable copyright that
applies to some scoping level.</p><p>A copyright statement that applies to a document as a whole should appear as a
child of the <code>head</code> element.</p><table summary="HTML Table" id="elt-syntax-metadata-copyright" class="syntax"><caption>XML Representation – Element Information Item: ttm:copyright</caption><tbody><tr><td>
@@ -4320,7 +4891,43 @@
<code>metadata</code> element child of the <code>head</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>A <code>ttm:agent</code> element instance is typically referenced using a <code>ttm:agent</code>
attribute on a content element.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If a character agent is played by multiple actors, then multiple character
agents may be specified (and referenced) wherein different definitions of the
-character specify different actors.</p></div></div><div class="div3">
+character specify different actors.</p></div><p class="diff-add">The use of agent metadata is illustrated by the following example.</p><table summary="HTML Table" id="metadata-vocabulary-agent-example-1" class="example"><caption><span class="diff-add">Example Fragment – Agent Metadata</span></caption><tbody><tr><td>
+<div class="exampleInner"><pre>
+<span class="diff-add">
+<tt xml:lang="en" xmlns="http://www.w3.org/2006/10/ttaf1" xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
+ <head>
+ <span class="strong"><ttm:agent xml:id="connery" type="person"></span>
+ <ttm:name type="family">Connery</ttm:name>
+ <ttm:name type="given">Thomas Sean</ttm:name>
+ <ttm:name type="alias">Sean</ttm:name>
+ <ttm:name type="full">Sir Thomas Sean Connery</ttm:name>
+ <span class="strong"></ttm:agent></span>
+ <span class="strong"><ttm:agent xml:id="bond" type="character"></span>
+ <ttm:name type="family">Bond</ttm:name>
+ <ttm:name type="given">James</ttm:name>
+ <ttm:name type="alias">007</ttm:name>
+ <ttm:actor agent="connery"/>
+ <span class="strong"></ttm:agent></span>
+ </head>
+ <body>
+ <div>
+ ...
+ <p <span class="strong">ttm:agent="bond"</span>>I travel, a sort of licensed troubleshooter.</p>
+ ...
+ </div>
+ </body>
+</tt>
+</span>
+</pre></div>
+</td></tr></tbody></table><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>In the above example, two agents, a real (person) agent, Sean
+Connery, and a fictitious (character) agent, James Bond, are defined,
+where the latter is linked to the former by means of the a
+<code>ttm:actor</code> element. A reference is then made from content (the
+<code>p</code> element) to the character agent associated with
+(responsible for producing) that content. Note that in this example
+the <code>ttm:agent</code> metadata items are specified as immediate
+children of the document's <code>head</code> element rather than being
+placed in a container <code>metadata</code> element.</p></div></div></div><div class="div3">
<h4><a name="metadata-vocabulary-name" id="metadata-vocabulary-name"/>12.1.6 ttm:name</h4><p>The <code>ttm:name</code> element is used to specify a name of a person, character,
group, or organization.</p><table summary="HTML Table" id="elt-syntax-metadata-name" class="syntax"><caption>XML Representation – Element Information Item: ttm:name</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -4335,7 +4942,8 @@
</pre></div>
</td></tr></tbody></table><p>A <code>type</code> attribute must be specified on each <code>ttm:name</code> element, and,
if specified, must have one of the following values:</p><ul><li><p><code>full</code></p></li><li><p><code>family</code></p></li><li><p><code>given</code></p></li><li><p><code>alias</code></p></li><li><p><code>other</code></p></li></ul><p>The relationship between the type of a name and the syntactic expression of the name
-is not defined by this specification.</p></div><div class="div3">
+is not defined by this specification.</p><p class="diff-add">Two examples of the <code>ttm:name</code> element are shown above in
+<a href="#metadata-vocabulary-agent-example-1"><b>Example Fragment – Agent Metadata</b></a>.</p></div><div class="div3">
<h4><a name="metadata-vocabulary-actor" id="metadata-vocabulary-actor"/>12.1.7 ttm:actor</h4><p>The <code>ttm:actor</code> element is used to link the definition of a (role-based) character
agent with another agent that portrays the character.</p><table summary="HTML Table" id="elt-syntax-metadata-actor" class="syntax"><caption>XML Representation – Element Information Item: ttm:actor</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -4350,19 +4958,32 @@
</pre></div>
</td></tr></tbody></table><p>The <code>agent</code> attribute of a <code>ttm:actor</code> element must
reference a <code>ttm:agent</code> element that denotes the person,
-group, or organization acting the part of a character.</p></div></div><div class="div2">
+group, or organization acting the part of a character.</p><p class="diff-add">An example of the <code>ttm:actor</code> element is shown above in
+<a href="#metadata-vocabulary-agent-example-1"><b>Example Fragment – Agent Metadata</b></a>.</p></div></div><div class="div2">
<h3><a name="metadata-attribute-vocabulary" id="metadata-attribute-vocabulary"/>12.2 <span class="diff-add">Metadata </span>Attribute Vocabulary</h3><p>This section specifies the following attributes in the TT Metadata Namespace
for use with the <code>metadata</code> element and with certain content elements:</p><ul><li><p><a href="#metadata-attribute-agent"><b>12.2.1 ttm:agent</b></a></p></li><li><p><a href="#metadata-attribute-role"><b>12.2.2 ttm:role</b></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Only certain metadata item attributes may be used with content elements. See
the definitions of content elements to determine permissible usage.</p></div><div class="div3">
<h4><a name="metadata-attribute-agent" id="metadata-attribute-agent"/>12.2.1 ttm:agent</h4><p>The <code>ttm:agent</code> attribute takes an <code>IDREFS</code>
-value, and is used with certain content elements to designate the agent that performs
-or is involved in the performance of the content.</p><p>If specified, a <code>ttm:agent</code> attribute must reference a <code>ttm:agent</code> element
-instance that appears as a descendent of the same document instance as
-that of the referring element.</p></div><div class="div3">
+value, and is used with certain content elements to designate the
+<span class="diff-chg">agents that perform or are</span>
+involved in the performance of the content.</p><p>If specified, a <code>ttm:agent</code> attribute must reference
+<span class="diff-chg"><code>ttm:agent</code> element instances that appear</span>
+as a descendent of the same document instance as
+that of the referring element.</p><p class="diff-add">An example of the <code>ttm:agent</code> attribute is shown above in
+<a href="#metadata-vocabulary-agent-example-1"><b>Example Fragment – Agent Metadata</b></a>.</p></div><div class="div3">
<h4><a name="metadata-attribute-role" id="metadata-attribute-role"/>12.2.2 ttm:role</h4><p>The <code>ttm:role</code> attribute may be used by a content author
-to express a role, function, or characteristic of some content element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following syntax:</p><table summary="HTML Table" id="metadata-attribute-role-syntax" class="syntax"><caption>Syntax Representation – ttm:role</caption><tbody><tr><td>
+to express
+<span class="diff-chg">the roles, functions, or characteristics</span>
+of some content element that is so labeled.</p><p>If specified, the value of this attribute must adhere to the following
+syntax<span class="diff-add">, where
+the syntactic element <em>S</em> must adhere to production
+[3] <code>S</code> as defined by <a href="#xml11">[XML 1.1]</a> §
+2.3</span>:</p><table summary="HTML Table" id="metadata-attribute-role-syntax" class="syntax"><caption>Syntax Representation – ttm:role</caption><tbody><tr><td>
<div class="exampleInner"><pre>
-ttm:role
+ttm:role<span class="diff-add">
+ role ( <em>S</em> role )*
+
+role</span>
: "action"
| "caption"
<span class="diff-add"> | "description"</span>
@@ -4414,8 +5035,8 @@
content may not be known at authoring time. In certain real-time
streaming contexts, even the content is not known at authoring time,
but is only known at time of streaming.</p><p>In describing dynamic flow, the flow process is logically divided
-into three types of flow operations:</p><ul><li><p><em>fill into</em> – causes new content
-to consume extent in the designated presentation region;</p></li><li><p><em>reflow within</em> – causes content
+into <span class="diff-chg">two</span> types of flow operations:</p><ul><li><p><em>fill into</em> – causes new content
+to consume extent in the designated presentation region;</p></li><li><p class="diff-del"><em>reflow within</em> – causes content
presently consuming extent to be moved, possibly entailing new line break
positions, within its designated
presentation region;</p></li><li><p><em>clear out</em> – causes content
@@ -4431,9 +5052,13 @@
of the <code>in()</code> flow function;</p></li><li><p class="diff-del"><em>fill transition</em>, as specified by the <code>flowTransition</code> argument
of the <code>in()</code> flow function;</p></li><li><p class="diff-del"><em>fill transition style</em>, as specified by the
<code>flowTransitionStyle</code> argument
-of the <code>in()</code> flow function;</p></li><li><p><em>reflow unit</em>, as specified by the <code>flowUnit</code> argument
-of the <code>within()</code> flow function;</p></li><li><p><em>reflow style</em>, as specified by the <code>flowStyle</code> argument
-of the <code>within()</code> flow function;</p></li><li><p class="diff-del"><em>reflow transition</em>, as specified by the <code>flowTransition</code> argument
+of the <code>in()</code> flow function;</p></li><li><p><em>reflow unit</em>, <span class="diff-del">as specified by the
+<code>flowUnit</code> argument of the <code>within()</code> flow
+function</span> <span class="diff-add">which is set to the same value as
+the <em>clear unit</em> parameter</span>;</p></li><li><p><em>reflow style</em>, <span class="diff-del">as specified by the
+<code>flowStyle</code> argument of the <code>within()</code> flow
+function</span> <span class="diff-add">which is set to the same value as
+the <em>clear style</em> parameter</span>;</p></li><li><p class="diff-del"><em>reflow transition</em>, as specified by the <code>flowTransition</code> argument
of the <code>within()</code> flow function;</p></li><li><p class="diff-del"><em>reflow transition style</em>, as specified by the
<code>flowTransitionStyle</code> argument
of the <code>within()</code> flow function;</p></li><li><p><em>clear unit</em>, as specified by the <code>flowUnit</code> argument
@@ -4524,7 +5149,7 @@
color, foreground color, glyph decoration(s), actual presentation
order of glyphs (independently from their assigned position).</p></div></div><p class="diff-add">If the value of a style property assigned to content
awaiting in a flow buffer or already dynamically flowed into a
-presentation region is changed, due to animation or other temporal
+presentation region is changed due to animation or other temporal
effects, and that style property change is not otherwise construed as
a significant difference between temporal flow buffer states as
described above, then the semantic, presentation effects of that
@@ -4605,7 +5230,7 @@
present in the presentation region divided by the number of clear units
currently available in the presentation region.</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<span class="diff-del">g</span>, and from
+formatted content into, within, and from
a presentation <span class="diff-add">region </span>undergoing dynamic
flow processing.</p><p class="diff-add">When performing flow operations, the fill unit state parameters that
apply to these operations determine which logical content and
@@ -4619,8 +5244,10 @@
presentation region, fill, reflow, and clear operations operate on
formatted content units (glyph, inline, line, and block areas);
however, in the context of the flow buffer, fill, reflow, and clear
-operations operate on logical content units (characters and
-words). Because logical content units and formatted content units are
+operations operate on logical content units (character information items and
+element information items –
+<code>fo:inline</code> and <code>fo:block</code>).
+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
units, and vice-versa.</p><div class="diff-add"><div class="note"><p class="prefix"><b>Note:</b></p><p>In general, there is not a one-to-one correspondence between
@@ -4755,10 +5382,7 @@
DFXP document instances:</p><ul><li><p>Relax NG, Compact Syntax (RNC) Schema</p></li><li><p>XML Schema Definition (XSD) Schema</p></li></ul><p>In any case where a schema specified by this appendix differs from the
normative definitions of document type, element type, or attribute type
as defined by the body of this specification, then the body of this
-specification takes precedence.</p><table border="1" class="ednote" summary="Editorial note: GA"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: GA</b></td><td align="right" valign="top">2009-01-30</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">
-The following schemas need to be updated to reflect changes since the previously
-published candidate recommendation.
-</td></tr></table><div class="div2">
+specification takes precedence.</p><div class="diff-chg">
<h3><a name="dfxp-schema-rnc" id="dfxp-schema-rnc"/>C.1 Relax NG Schema</h3><p>This section specifies a Relax NG Compact Syntax (RNC) <a href="#rng">[RELAX NG]</a> based schema
for DFXP, also available in a <a href="rnc/schema.zip">ZIP
Archive</a>.</p><div class="div3">
@@ -4777,8 +5401,10 @@
include "ttaf1-dfxp-metadata-attribs.rnc"
include "ttaf1-dfxp-styling-attribs.rnc"
include "ttaf1-dfxp-timing-attribs.rnc"
+include "ttaf1-dfxp-parameter-items.rnc"
+include "ttaf1-dfxp-parameters.rnc"
+include "ttaf1-dfxp-metadata-items.rnc"
include "ttaf1-dfxp-metadata.rnc"
-include "ttaf1-dfxp-metadata-items.rnc"
include "ttaf1-dfxp-styling.rnc"
include "ttaf1-dfxp-animation.rnc"
include "ttaf1-dfxp-layout.rnc"
@@ -4786,7 +5412,7 @@
include "ttaf1-dfxp-head.rnc"
include "ttaf1-dfxp-document.rnc"
-start = TTAF.tt
+start = TTAF.tt | TTAF.parameters.profile
# .......................................................................
# .......................................................................
@@ -5034,26 +5660,43 @@
TTAF.Direction.datatype =
"ltr" |
- "rtl" |
- "inherit"
+ "rtl"
TTAF.Display.datatype =
"auto" |
- "none" |
- "inherit"
+ "none"
TTAF.DisplayAlign.datatype =
"before" |
"center" |
- "after" |
- "inherit"
+ "after"
TTAF.DynamicFlow.datatype =
string
+TTAF.ExtensionBase.datatype =
+ TTAF.URI.datatype
+
+TTAF.ExtensionDesignator.datatype =
+ TTAF.URI.datatype
+
+TTAF.ExtensionValue.datatype =
+ "required" |
+ "optional"
+
TTAF.Extent.datatype =
string
+TTAF.FeatureBase.datatype =
+ TTAF.URI.datatype
+
+TTAF.FeatureDesignator.datatype =
+ TTAF.URI.datatype
+
+TTAF.FeatureValue.datatype =
+ "required" |
+ "optional"
+
TTAF.FontFamily.datatype =
string
@@ -5064,13 +5707,11 @@
"normal" |
"italic" |
"oblique" |
- "reverseOblique" |
- "inherit"
+ "reverseOblique"
TTAF.FontWeight.datatype =
"normal" |
- "bold" |
- "inherit"
+ "bold"
TTAF.FrameRate.datatype =
xsd:nonNegativeInteger
@@ -5105,6 +5746,7 @@
TTAF.MetadataRoleBaseType.datatype =
"action" |
"caption" |
+ "description" |
"dialog" |
"expletive" |
"kinesic" |
@@ -5129,8 +5771,7 @@
TTAF.Overflow.datatype =
"visible" |
"hidden" |
- "scroll" |
- "inherit"
+ "dynamic"
TTAF.Padding.datatype =
string
@@ -5142,12 +5783,11 @@
TTAF.URI.datatype
TTAF.Role.datatype =
- xsd:NMTOKEN
+ xsd:NMTOKENS
TTAF.ShowBackground.datatype =
"always" |
- "whenActive" |
- "inherit"
+ "whenActive"
TTAF.SMPTEMode.datatype =
"dropNTSC" |
@@ -5162,8 +5802,7 @@
"center" |
"right" |
"start" |
- "end" |
- "inherit"
+ "end"
TTAF.TextDecoration.datatype =
"none" |
@@ -5172,8 +5811,7 @@
"overline" |
"noOverline" |
"lineThrough" |
- "noLineThrough" |
- "inherit"
+ "noLineThrough"
TTAF.TextOutline.datatype =
string
@@ -5202,18 +5840,15 @@
TTAF.UnicodeBidi.datatype =
"normal" |
"embed" |
- "bidiOverride" |
- "inherit"
+ "bidiOverride"
TTAF.Visibility.datatype =
"hidden" |
- "visible" |
- "inherit"
+ "visible"
TTAF.WrapOption.datatype =
"wrap" |
- "noWrap" |
- "inherit"
+ "noWrap"
TTAF.WritingMode.datatype =
"lrtb" |
@@ -5222,8 +5857,7 @@
"tblr" |
"lr" |
"rl" |
- "tb" |
- "inherit"
+ "tb"
TTAF.XMLSpace.datatype =
"default" |
@@ -5275,6 +5909,7 @@
TTAF.head.content.extra = empty
TTAF.head.content =
(TTAF.Metadata.class*,
+ TTAF.Parameters.class*,
TTAF.styling?,
TTAF.layout?,
TTAF.head.content.extra*)
@@ -5336,7 +5971,7 @@
# .......................................................................
# .......................................................................
</pre></div></div><div class="div4">
-<h5><a name="rnc-dfxp-metdata-module" id="rnc-dfxp-metdata-module"/>C.1.2.9 Metadata Module</h5><div class="exampleInner"><pre># .......................................................................
+<h5><a name="rnc-dfxp-metadata-module" id="rnc-dfxp-metadata-module"/>C.1.2.9 Metadata Module</h5><div class="exampleInner"><pre># .......................................................................
# TT-AF 1.0 DFXP Metadata Module ........................................
# .......................................................................
@@ -5379,7 +6014,7 @@
# .......................................................................
# .......................................................................
</pre></div></div><div class="div4">
-<h5><a name="rnc-dfxp-metdata-items-module" id="rnc-dfxp-metdata-items-module"/>C.1.2.10 Metadata Items Module</h5><div class="exampleInner"><pre># .......................................................................
+<h5><a name="rnc-dfxp-metadata-items-module" id="rnc-dfxp-metadata-items-module"/>C.1.2.10 Metadata Items Module</h5><div class="exampleInner"><pre># .......................................................................
# TT-AF 1.0 DFXP Metadata Items Module ......................................
# .......................................................................
@@ -5513,7 +6148,114 @@
# .......................................................................
# .......................................................................
</pre></div></div><div class="div4">
-<h5><a name="rnc-dfxp-parameter-attribs-module" id="rnc-dfxp-parameter-attribs-module"/>C.1.2.12 Parameter Attributes Module</h5><div class="exampleInner"><pre># .......................................................................
+<h5><a name="rnc-dfxp-parameters-module" id="rnc-dfxp-parameters-module"/>C.1.2.12 Parameters Module</h5><div class="exampleInner"><pre># .......................................................................
+# TT-AF 1.0 DFXP Parameters Module ......................................
+# .......................................................................
+
+TTAF.Parameters.class |=
+ TTAF.ParameterItems.class
+
+# .......................................................................
+# .......................................................................
+# .......................................................................
+</pre></div></div><div class="div4">
+<h5><a name="rnc-dfxp-parameter-items-module" id="rnc-dfxp-parameter-items-module"/>C.1.2.13 Parameter Items Module</h5><div class="exampleInner"><pre># .......................................................................
+# TT-AF 1.0 DFXP Parameter Items Module .................................
+# .......................................................................
+
+namespace ttp = "http://www.w3.org/2006/10/ttaf1#parameter"
+
+# profile - profile definition or use declaration
+TTAF.parameters.profile =
+ element ttp:profile {
+ TTAF.parameters.profile.attlist,
+ TTAF.parameters.profile.content
+ }
+
+TTAF.parameters.profile.attlist &=
+ TTAF.id.attrib,
+ attribute use { TTAF.Profile.datatype }?
+
+TTAF.parameters.profile.content.extra = empty
+TTAF.parameters.profile.content =
+ (TTAF.Metadata.class*,
+ TTAF.parameters.features*,
+ TTAF.parameters.extensions*,
+ TTAF.parameters.profile.content.extra*)
+
+# features - container for feature elements
+TTAF.parameters.features =
+ element ttp:features {
+ TTAF.parameters.features.attlist,
+ TTAF.parameters.features.content
+ }
+
+TTAF.parameters.features.attlist &=
+ TTAF.id.attrib,
+ attribute base { TTAF.FeatureBase.datatype }?
+
+TTAF.parameters.features.content.extra = empty
+TTAF.parameters.features.content =
+ (TTAF.Metadata.class*,
+ TTAF.parameters.feature*,
+ TTAF.parameters.features.content.extra*)
+
+# feature - feature requirements declaration
+TTAF.parameters.feature =
+ element ttp:feature {
+ TTAF.parameters.feature.attlist,
+ TTAF.parameters.feature.content
+ }
+
+TTAF.parameters.feature.attlist =
+ TTAF.id.attrib,
+ attribute value { TTAF.FeatureValue.datatype }?
+
+TTAF.parameters.feature.content =
+ TTAF.FeatureDesignator.datatype
+
+# extensions - container for extension elements
+TTAF.parameters.extensions =
+ element ttp:extensions {
+ TTAF.parameters.extensions.attlist,
+ TTAF.parameters.extensions.content
+ }
+
+TTAF.parameters.extensions.attlist &=
+ TTAF.id.attrib,
+ attribute base { TTAF.ExtensionBase.datatype }?
+
+TTAF.parameters.extensions.content.extra = empty
+TTAF.parameters.extensions.content =
+ (TTAF.Metadata.class*,
+ TTAF.parameters.extension*,
+ TTAF.parameters.extensions.content.extra*)
+
+# extension - extension requirements declaration
+TTAF.parameters.extension =
+ element ttp:extension {
+ TTAF.parameters.extension.attlist,
+ TTAF.parameters.extension.content
+ }
+
+TTAF.parameters.extension.attlist =
+ TTAF.id.attrib,
+ attribute value { TTAF.ExtensionValue.datatype }?
+
+TTAF.parameters.extension.content =
+ TTAF.ExtensionDesignator.datatype
+
+## ParameterItems.class
+TTAF.ParameterItems.extra = empty
+TTAF.ParameterItems.class |=
+ TTAF.parameters.profile |
+ TTAF.ParameterItems.extra
+
+# .......................................................................
+# .......................................................................
+# .......................................................................
+</pre></div></div><div class="div4">
+<h5><a name="rnc-dfxp-parameter-attribs-module" id="rnc-dfxp-parameter-attribs-module"/>C.1.2.14 Parameter Attributes Module</h5><div class="exampleInner"><pre># .......................................................................
# TT-AF 1.0 DFXP Parameter Attributes Module ............................
# .......................................................................
@@ -5563,7 +6305,7 @@
# .......................................................................
# .......................................................................
</pre></div></div><div class="div4">
-<h5><a name="rnc-dfxp-styling-attribs-module" id="rnc-dfxp-styling-attribs-module"/>C.1.2.13 Styling Attributes Module</h5><div class="exampleInner"><pre># .......................................................................
+<h5><a name="rnc-dfxp-styling-attribs-module" id="rnc-dfxp-styling-attribs-module"/>C.1.2.15 Styling Attributes Module</h5><div class="exampleInner"><pre># .......................................................................
# TT-AF 1.0 DFXP Styling Attributes Module ..............................
# .......................................................................
@@ -5676,7 +6418,7 @@
# .......................................................................
# .......................................................................
</pre></div></div><div class="div4">
-<h5><a name="rnc-dfxp-styling-module" id="rnc-dfxp-styling-module"/>C.1.2.14 Styling Module</h5><div class="exampleInner"><pre># .......................................................................
+<h5><a name="rnc-dfxp-styling-module" id="rnc-dfxp-styling-module"/>C.1.2.16 Styling Module</h5><div class="exampleInner"><pre># .......................................................................
# TT-AF 1.0 DFXP Styling Module .........................................
# .......................................................................
@@ -5728,7 +6470,7 @@
# .......................................................................
# .......................................................................
</pre></div></div><div class="div4">
-<h5><a name="rnc-dfxp-timing-attribs-module" id="rnc-dfxp-timing-attribs-module"/>C.1.2.15 Timing Attributes Module</h5><div class="exampleInner"><pre># .......................................................................
+<h5><a name="rnc-dfxp-timing-attribs-module" id="rnc-dfxp-timing-attribs-module"/>C.1.2.17 Timing Attributes Module</h5><div class="exampleInner"><pre># .......................................................................
# TT-AF 1.0 DFXP Timing Attributes Module ...............................
# .......................................................................
@@ -5777,7 +6519,7 @@
# .......................................................................
# .......................................................................
# .......................................................................
-</pre></div></div></div></div><div class="div2">
+</pre></div></div></div></div><div class="diff-chg">
<h3><a name="dfxp-schema-xsd" id="dfxp-schema-xsd"/>C.2 XML Schema Definition (XSD) Schema</h3><p>This section specifies a W3C XML Schema Definition (XSD) <a href="#xsd-1">[XML Schema Part 1]</a> based schema
for DFXP, also available in a <a href="xsd/schema.zip">ZIP
Archive</a>.</p><div class="div3">
@@ -5792,11 +6534,11 @@
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-timing-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-metadata.xsd"/>
- <xs:import namespace="http://www.w3.org/2006/10/ttaf1#style"
+ <xs:import namespace="http://www.w3.org/2006/10/ttaf1#styling"
schemaLocation="ttaf1-dfxp-styling-attribs.xsd"/>
<xs:attributeGroup name="set.attlist">
<xs:attributeGroup ref="tt:Core.attrib.class" />
@@ -5821,7 +6563,7 @@
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-timing-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-metadata.xsd"/>
@@ -5937,13 +6679,16 @@
xmlns:xml="http://www.w3.org/XML/1998/namespace">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="xml.xsd"/>
+ <xs:attributeGroup name="Core.ID.attrib.class">
+ <xs:attribute ref="xml:id"/>
+ </xs:attributeGroup>
<xs:attributeGroup name="Core.attrib.class">
- <xs:attribute ref="xml:id"/>
+ <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
<xs:attribute ref="xml:lang"/>
<xs:attribute ref="xml:space"/>
</xs:attributeGroup>
<xs:attributeGroup name="Core.required.attrib.class">
- <xs:attribute ref="xml:id"/>
+ <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
<xs:attribute ref="xml:lang" use="required"/>
<xs:attribute ref="xml:space"/>
</xs:attributeGroup>
@@ -5981,14 +6726,12 @@
<xs:restriction base="xs:token">
<xs:enumeration value="ltr"/>
<xs:enumeration value="rtl"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="display">
<xs:restriction base="xs:token">
<xs:enumeration value="auto"/>
<xs:enumeration value="none"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="displayAlign">
@@ -5996,24 +6739,47 @@
<xs:enumeration value="before"/>
<xs:enumeration value="center"/>
<xs:enumeration value="after"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="dynamicFlow">
<xs:restriction base="xs:string"/>
</xs:simpleType>
+ <xs:simpleType name="extensionBase">
+ <xs:restriction base="xs:anyURI"/>
+ </xs:simpleType>
+ <xs:simpleType name="extensionDesignator">
+ <xs:restriction base="xs:anyURI"/>
+ </xs:simpleType>
+ <xs:simpleType name="extensionValue">
+ <xs:restriction base="xs:token">
+ <xs:enumeration value="required"/>
+ <xs:enumeration value="optional"/>
+ </xs:restriction>
+ </xs:simpleType>
<xs:simpleType name="extent">
<xs:annotation>
- <xs:documentation>auto | inherit | length length</xs:documentation>
+ <xs:documentation>auto | length length</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
+ <xs:simpleType name="featureBase">
+ <xs:restriction base="xs:anyURI"/>
+ </xs:simpleType>
+ <xs:simpleType name="featureDesignator">
+ <xs:restriction base="xs:anyURI"/>
+ </xs:simpleType>
+ <xs:simpleType name="featureValue">
+ <xs:restriction base="xs:token">
+ <xs:enumeration value="required"/>
+ <xs:enumeration value="optional"/>
+ </xs:restriction>
+ </xs:simpleType>
<xs:simpleType name="fontFamily">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="fontSize">
<xs:annotation>
- <xs:documentation>inherit | length | length length</xs:documentation>
+ <xs:documentation>length | length length</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
@@ -6023,14 +6789,12 @@
<xs:enumeration value="italic"/>
<xs:enumeration value="oblique"/>
<xs:enumeration value="reverseOblique"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="fontWeight">
<xs:restriction base="xs:token">
<xs:enumeration value="normal"/>
<xs:enumeration value="bold"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="frameRate">
@@ -6046,7 +6810,7 @@
</xs:simpleType>
<xs:simpleType name="lineHeight">
<xs:annotation>
- <xs:documentation>normal | inherit | length</xs:documentation>
+ <xs:documentation>normal | length</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
@@ -6081,6 +6845,7 @@
<xs:restriction base="xs:token">
<xs:enumeration value="action"/>
<xs:enumeration value="caption"/>
+ <xs:enumeration value="description"/>
<xs:enumeration value="dialog"/>
<xs:enumeration value="expletive"/>
<xs:enumeration value="kinesic"/>
@@ -6099,13 +6864,13 @@
</xs:simpleType>
<xs:simpleType name="opacity">
<xs:annotation>
- <xs:documentation>inherit | alpha</xs:documentation>
+ <xs:documentation>alpha</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="origin">
<xs:annotation>
- <xs:documentation>auto | inherit | length length</xs:documentation>
+ <xs:documentation>auto | length length</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
@@ -6113,13 +6878,12 @@
<xs:restriction base="xs:token">
<xs:enumeration value="visible"/>
<xs:enumeration value="hidden"/>
- <xs:enumeration value="scroll"/>
- <xs:enumeration value="inherit"/>
+ <xs:enumeration value="dynamic"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="padding">
<xs:annotation>
- <xs:documentation>inherit | length length | length length length | length length length length</xs:documentation>
+ <xs:documentation>length length | length length length | length length length length</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
@@ -6138,13 +6902,12 @@
<xs:annotation>
<xs:documentation>metadataRoleBaseType | "x-"string</xs:documentation>
</xs:annotation>
- <xs:restriction base="xs:NMTOKEN"/>
+ <xs:restriction base="xs:NMTOKENS"/>
</xs:simpleType>
<xs:simpleType name="showBackground">
<xs:restriction base="xs:token">
<xs:enumeration value="always"/>
<xs:enumeration value="whenActive"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="smpteMode">
@@ -6164,7 +6927,6 @@
<xs:enumeration value="right"/>
<xs:enumeration value="start"/>
<xs:enumeration value="end"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="textDecoration">
@@ -6176,12 +6938,11 @@
<xs:enumeration value="noOverline"/>
<xs:enumeration value="lineThrough"/>
<xs:enumeration value="noLineThrough"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="textOutline">
<xs:annotation>
- <xs:documentation>none | inherit | length | length length | color length | color length length</xs:documentation>
+ <xs:documentation>none | length | length length | color length | color length length</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
@@ -6218,21 +6979,18 @@
<xs:enumeration value="normal"/>
<xs:enumeration value="embed"/>
<xs:enumeration value="bidiOverride"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="visibility">
<xs:restriction base="xs:token">
<xs:enumeration value="hidden"/>
<xs:enumeration value="visible"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="wrapOption">
<xs:restriction base="xs:token">
<xs:enumeration value="wrap"/>
<xs:enumeration value="noWrap"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="writingMode">
@@ -6244,12 +7002,11 @@
<xs:enumeration value="lr"/>
<xs:enumeration value="rl"/>
<xs:enumeration value="tb"/>
- <xs:enumeration value="inherit"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="zIndex">
<xs:annotation>
- <xs:documentation>auto | inherit | integer</xs:documentation>
+ <xs:documentation>auto | integer</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
@@ -6260,12 +7017,12 @@
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata"
xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<xs:import namespace="http://www.w3.org/2006/10/ttaf1#metadata"
schemaLocation="ttaf1-dfxp-metadata-items.xsd"/>
<xs:import namespace="http://www.w3.org/2006/10/ttaf1#parameter"
- schemaLocation="ttaf1-dfxp-parameter-attribs.xsd"/>
- <xs:import namespace="http://www.w3.org/2006/10/ttaf1#style"
+ schemaLocation="ttaf1-dfxp-parameter-items.xsd"/>
+ <xs:import namespace="http://www.w3.org/2006/10/ttaf1#styling"
schemaLocation="ttaf1-dfxp-styling-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-timing-attribs.xsd"/>
@@ -6289,9 +7046,11 @@
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+ xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter"
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-metadata.xsd"/>
+ <xs:include schemaLocation="ttaf1-dfxp-parameters.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-styling.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-layout.xsd"/>
<xs:attributeGroup name="head.attlist">
@@ -6300,6 +7059,7 @@
<xs:complexType name="head.eltype">
<xs:sequence>
<xs:group ref="tt:Metadata.class" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:group ref="tt:Parameters.class" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="tt:styling" minOccurs="0" maxOccurs="1"/>
<xs:element ref="tt:layout" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
@@ -6312,13 +7072,13 @@
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-timing-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-metadata.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-animation.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-styling.xsd"/>
- <xs:import namespace="http://www.w3.org/2006/10/ttaf1#style"
+ <xs:import namespace="http://www.w3.org/2006/10/ttaf1#styling"
schemaLocation="ttaf1-dfxp-styling-attribs.xsd"/>
<xs:attributeGroup name="RegionBinding.attrib.class">
<xs:attribute name="region" type="xs:IDREF"/>
@@ -6350,7 +7110,7 @@
<xs:element name="region" type="tt:region.eltype"/>
</xs:schema>
</pre></div></div><div class="div4">
-<h5><a name="xsd-dfxp-metdata-module" id="xsd-dfxp-metdata-module"/>C.2.2.8 Metadata Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1" xml:lang="en"
+<h5><a name="xsd-dfxp-metadata-module" id="xsd-dfxp-metadata-module"/>C.2.2.8 Metadata Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1" xml:lang="en"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
@@ -6382,7 +7142,7 @@
</xs:group>
</xs:schema>
</pre></div></div><div class="div4">
-<h5><a name="xsd-dfxp-metdata-items-module" id="xsd-dfxp-metdata-items-module"/>C.2.2.9 Metadata Items Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1#metadata"
+<h5><a name="xsd-dfxp-metadata-items-module" id="xsd-dfxp-metadata-items-module"/>C.2.2.9 Metadata Items Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1#metadata"
xml:lang="en" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttd="http://www.w3.org/2006/10/ttaf1#datatype"
@@ -6465,7 +7225,96 @@
</xs:attributeGroup>
</xs:schema>
</pre></div></div><div class="div4">
-<h5><a name="xsd-dfxp-parameter-attribs-module" id="xsd-dfxp-parameter-attribs-module"/>C.2.2.11 Parameter Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1#parameter"
+<h5><a name="xsd-dfxp-parameters-module" id="xsd-dfxp-parameters-module"/>C.2.2.11 Parameters Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1" xml:lang="en"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:tt="http://www.w3.org/2006/10/ttaf1"
+ xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter">
+ <xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
+ <xs:import namespace="http://www.w3.org/2006/10/ttaf1#parameter"
+ schemaLocation="ttaf1-dfxp-parameter-items.xsd"/>
+ <xs:group name="Parameters.class">
+ <xs:choice>
+ <xs:group ref="ttp:ParameterItems.class"/>
+ </xs:choice>
+ </xs:group>
+</xs:schema>
+</pre></div></div><div class="div4">
+<h5><a name="xsd-dfxp-parameter-items-module" id="xsd-dfxp-parameter-items-module"/>C.2.2.12 Parameter Items Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1#parameter"
+ xml:lang="en" xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:tt="http://www.w3.org/2006/10/ttaf1"
+ xmlns:ttd="http://www.w3.org/2006/10/ttaf1#datatype"
+ xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter">
+ <xs:import namespace="http://www.w3.org/2006/10/ttaf1#datatype"
+ schemaLocation="ttaf1-dfxp-datatypes.xsd"/>
+ <xs:import namespace="http://www.w3.org/2006/10/ttaf1"
+ schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
+ <xs:include schemaLocation="ttaf1-dfxp-parameter-attribs.xsd"/>
+ <xs:attributeGroup name="profile.attlist">
+ <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
+ <xs:attribute name="use" type="ttd:profile"/>
+ </xs:attributeGroup>
+ <xs:attributeGroup name="features.attlist">
+ <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
+ <xs:attribute name="base" type="ttd:featureBase"/>
+ </xs:attributeGroup>
+ <xs:attributeGroup name="feature.attlist">
+ <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
+ <xs:attribute name="value" type="ttd:featureValue"/>
+ </xs:attributeGroup>
+ <xs:attributeGroup name="extensions.attlist">
+ <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
+ <xs:attribute name="base" type="ttd:extensionBase"/>
+ </xs:attributeGroup>
+ <xs:attributeGroup name="extension.attlist">
+ <xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
+ <xs:attribute name="value" type="ttd:extensionValue"/>
+ </xs:attributeGroup>
+ <xs:complexType name="profile.eltype">
+ <xs:sequence>
+ <xs:element ref="ttp:features" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="ttp:extensions" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attributeGroup ref="ttp:profile.attlist"/>
+ </xs:complexType>
+ <xs:complexType name="features.eltype">
+ <xs:sequence>
+ <xs:element ref="ttp:feature" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attributeGroup ref="ttp:features.attlist"/>
+ </xs:complexType>
+ <xs:complexType name="feature.eltype">
+ <xs:simpleContent>
+ <xs:extension base="ttd:featureDesignator">
+ <xs:attributeGroup ref="ttp:feature.attlist"/>
+ </xs:extension>
+ </xs:simpleContent>
+ </xs:complexType>
+ <xs:complexType name="extensions.eltype">
+ <xs:sequence>
+ <xs:element ref="ttp:extension" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attributeGroup ref="ttp:extensions.attlist"/>
+ </xs:complexType>
+ <xs:complexType name="extension.eltype">
+ <xs:simpleContent>
+ <xs:extension base="ttd:extensionDesignator">
+ <xs:attributeGroup ref="ttp:extension.attlist"/>
+ </xs:extension>
+ </xs:simpleContent>
+ </xs:complexType>
+ <xs:element name="profile" type="ttp:profile.eltype"/>
+ <xs:element name="features" type="ttp:features.eltype"/>
+ <xs:element name="feature" type="ttp:feature.eltype"/>
+ <xs:element name="extensions" type="ttp:extensions.eltype"/>
+ <xs:element name="extension" type="ttp:extension.eltype"/>
+ <xs:group name="ParameterItems.class">
+ <xs:choice>
+ <xs:element ref="ttp:profile"/>
+ </xs:choice>
+ </xs:group>
+</xs:schema>
+</pre></div></div><div class="div4">
+<h5><a name="xsd-dfxp-parameter-attribs-module" id="xsd-dfxp-parameter-attribs-module"/>C.2.2.13 Parameter Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1#parameter"
xml:lang="en" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ttd="http://www.w3.org/2006/10/ttaf1#datatype"
xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter">
@@ -6497,10 +7346,10 @@
</xs:attributeGroup>
</xs:schema>
</pre></div></div><div class="div4">
-<h5><a name="xsd-dfxp-styling-attribs-module" id="xsd-dfxp-styling-attribs-module"/>C.2.2.12 Styling Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1#style" xml:lang="en"
+<h5><a name="xsd-dfxp-styling-attribs-module" id="xsd-dfxp-styling-attribs-module"/>C.2.2.14 Styling Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1#styling" xml:lang="en"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ttd="http://www.w3.org/2006/10/ttaf1#datatype"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<xs:import namespace="http://www.w3.org/2006/10/ttaf1#datatype"
schemaLocation="ttaf1-dfxp-datatypes.xsd"/>
<xs:attribute name="backgroundColor" type="ttd:color"/>
@@ -6557,14 +7406,14 @@
</xs:attributeGroup>
</xs:schema>
</pre></div></div><div class="div4">
-<h5><a name="xsd-dfxp-styling-module" id="xsd-dfxp-styling-module"/>C.2.2.13 Styling Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1" xml:lang="en"
+<h5><a name="xsd-dfxp-styling-module" id="xsd-dfxp-styling-module"/>C.2.2.15 Styling Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1" xml:lang="en"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tt="http://www.w3.org/2006/10/ttaf1"
xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata"
- xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling">
<xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/>
<xs:include schemaLocation="ttaf1-dfxp-metadata.xsd"/>
- <xs:import namespace="http://www.w3.org/2006/10/ttaf1#style"
+ <xs:import namespace="http://www.w3.org/2006/10/ttaf1#styling"
schemaLocation="ttaf1-dfxp-styling-attribs.xsd"/>
<xs:attributeGroup name="StyleBinding.attrib.class">
<xs:attribute name="style" type="xs:IDREFS"/>
@@ -6597,7 +7446,7 @@
<xs:element name="style" type="tt:style.eltype"/>
</xs:schema>
</pre></div></div><div class="div4">
-<h5><a name="xsd-dfxp-timing-attribs-module" id="xsd-dfxp-timing-attribs-module"/>C.2.2.14 Timing Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1" xml:lang="en"
+<h5><a name="xsd-dfxp-timing-attribs-module" id="xsd-dfxp-timing-attribs-module"/>C.2.2.16 Timing Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/2006/10/ttaf1" xml:lang="en"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ttd="http://www.w3.org/2006/10/ttaf1#datatype"
xmlns:tt="http://www.w3.org/2006/10/ttaf1">
@@ -6620,7 +7469,7 @@
</xs:attributeGroup>
</xs:schema>
</pre></div></div><div class="div4">
-<h5><a name="xsd-dfxp-xml-attrs-module" id="xsd-dfxp-xml-attrs-module"/>C.2.2.15 XML Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace" xml:lang="en"
+<h5><a name="xsd-dfxp-xml-attrs-module" id="xsd-dfxp-xml-attrs-module"/>C.2.2.17 XML Attributes Module</h5><div class="exampleInner"><pre><xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace" xml:lang="en"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:attribute name="id" type="xs:ID"/>
<xs:attribute name="lang" type="xs:language"/>
@@ -6686,7 +7535,7 @@
: feature-namespace designation
feature-namespace
- : <em>TT Feature Prefix Namespace</em> // <span><code>http://www.w3.org/2006/10/ttaf1/feature</code></span>
+ : <em>TT Feature Namespace</em> // http://www.w3.org/2006/10/ttaf1/feature
designation
: "#" token-char+
@@ -6694,23 +7543,9 @@
token-char
: { XML NameChar } // XML 1.1 Production [4a]
</pre></div><p>All values of <code>feature-designation</code> not defined by this specification are reserved
-for future standardization.</p><p>An example is shown below of using feature designations to indicate the author's intent that a
-receiving processor must be a transformation processor and must support transformation of
-content vocabulary elements.</p><table summary="HTML Table" id="dfxp-example-requiredFeatures" class="example"><caption>Example Fragment – Required Features</caption><tbody><tr><td>
-<div class="exampleInner"><pre>
-<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"
- <span class="strong">requiredFeatures="http://www.w3.org/2006/10/ttaf1/feature#transformation
- http://www.w3.org/2006/10/ttaf1/feature#content"</span>>
- <head/>
- <body>
- <div>
- <p/>
- </div>
- </body>
-</tt>
-</pre></div>
-</td></tr></tbody></table><p>The following sub-sections define all feature designations (expressed
-without the TT Feature Prefix Namespace).</p><div class="div3">
+for future standardization.</p><p>The following sub-sections define all feature designations, expressed
+as relative URIs (fragment identifiers) with respect to the
+TT Feature Namespace base URI.</p><div class="div3">
<h4><a name="feature-animation" id="feature-animation"/>E.1.1 #animation</h4><p>A TT AF transformation processor supports the <code>#animation</code>
feature if it recognizes and is capable of transforming the following
vocabulary defined by <a href="#animation"><b>11 Animation</b></a>:</p><ul><li><p><a href="#animation-vocabulary-set"><code>set</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#animation</code>
@@ -6720,34 +7555,47 @@
<code>#backgroundColor</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute.</p><p>A TT AF presentation processor supports the
-<code>#backgroundColor</code> feature if it implements presentation semantic support
+<code>#backgroundColor</code> feature if it (1) implements presentation semantic support
for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
-attribute.</p></div><div class="div3">
+attribute
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
<h4><a name="feature-backgroundColor-block" id="feature-backgroundColor-block"/>E.1.3 #backgroundColor-block</h4><p>A TT AF transformation processor supports the
<code>#backgroundColor-block</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that would generate a
block area during presentation processing.</p><p>A TT AF presentation processor supports the
-<code>#backgroundColor-block</code> feature if it implements presentation semantic
-support for all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
+<code>#backgroundColor-block</code> feature if it (1) implements presentation semantic
+support for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that generates a
-block area.</p></div><div class="div3">
+block area
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
<h4><a name="feature-backgroundColor-inline" id="feature-backgroundColor-inline"/>E.1.4 #backgroundColor-inline</h4><p>A TT AF transformation processor supports the
<code>#backgroundColor-inline</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that would generate an
inline area during presentation processing.</p><p>A TT AF presentation processor supports the
-<code>#backgroundColor-inline</code> feature if it implements presentation semantic
-support for all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
+<code>#backgroundColor-inline</code> feature if it (1) implements presentation semantic
+support for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
attribute when applied to a content element that generates an
-inline area.</p></div><div class="div3">
+inline area
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
<h4><a name="feature-backgroundColor-region" id="feature-backgroundColor-region"/>E.1.5 #backgroundColor-region</h4><p>A TT AF transformation processor supports the
<code>#backgroundColor-region</code> feature if it recognizes and is
capable of transforming all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</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>#backgroundColor-region</code> feature if it implements presentation semantic
-support for all defined values of the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
-attribute when applied to a <a href="layout-vocabulary-region"><code>region</code></a> element.</p></div><div class="div3">
+<code>#backgroundColor-region</code> feature if it (1) implements presentation semantic
+support for the <a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a>
+attribute when applied to a <a href="layout-vocabulary-region"><code>region</code></a> element
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space
+.</p></div><div class="div3">
<h4><a name="feature-bidi" id="feature-bidi"/>E.1.6 #bidi</h4><p>A TT AF processor supports the <code>#bidi</code> feature if it
supports the following features:</p><ul><li><p><a href="#feature-direction"><code>#direction</code></a></p></li><li><p><a href="#feature-unicodeBidi"><code>#unicodeBidi</code></a></p></li><li><p><a href="#feature-writingMode-horizontal"><code>#writingMode-horizontal</code></a></p></li></ul></div><div class="div3">
<h4><a name="feature-cellResolution" id="feature-cellResolution"/>E.1.7 #cellResolution</h4><p>A TT AF transformation processor supports the
@@ -6768,9 +7616,12 @@
<code>#color</code> feature if it recognizes and is capable of
transforming the <a href="#style-attribute-color"><code>tts:color</code></a>
attribute.</p><p>A TT AF presentation processor supports the
-<code>#color</code> feature if it implements presentation semantic support
+<code>#color</code> feature if it (1) implements presentation semantic support
for the <a href="#style-attribute-color"><code>tts:color</code></a>
-attribute.</p></div><div class="div3">
+attribute
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p></div><div class="div3">
<h4><a name="feature-content" id="feature-content"/>E.1.10 #content</h4><p>A TT AF transformation processor supports the <code>#content</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="#content-vocabulary-body"><code>body</code></a></p></li><li><p><a href="#content-vocabulary-div"><code>div</code></a></p></li><li><p><a href="#content-vocabulary-p"><code>p</code></a></p></li><li><p><a href="#content-vocabulary-span"><code>span</code></a></p></li><li><p><a href="#content-vocabulary-br"><code>br</code></a></p></li></ul><p>A TT AF presentation processor supports the <code>#content</code>
@@ -6834,18 +7685,7 @@
<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="div3">
-<h4><a name="feature-dynamicFlow-barWipe" id="feature-dynamicFlow-barWipe"/>E.1.19 #dynamicFlow-barWipe</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-barWipe</code> feature if it recognizes and
-is capable of transforming the flow transition <code>barWipe</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-barWipe</code> feature if it implements
-presentation semantic support for the flow transition <code>barWipe</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-block" id="feature-dynamicFlow-block"/>E.1.20 #dynamicFlow-block</h4><p>A TT AF transformation processor supports the
+<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
@@ -6856,7 +7696,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-character" id="feature-dynamicFlow-character"/>E.1.21 #dynamicFlow-character</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-character" id="feature-dynamicFlow-character"/>E.1.20 #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
@@ -6867,18 +7707,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-fade" id="feature-dynamicFlow-fade"/>E.1.22 #dynamicFlow-fade</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-fade</code> feature if it recognizes and
-is capable of transforming the flow style <code>fade</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-fade</code> feature if it implements
-presentation semantic support for the flow style <code>fade</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.21 #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
@@ -6889,7 +7718,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.22 #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
@@ -6900,7 +7729,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-inline" id="feature-dynamicFlow-inline"/>E.1.25 #dynamicFlow-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-inline" id="feature-dynamicFlow-inline"/>E.1.23 #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
@@ -6911,7 +7740,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-inter" id="feature-dynamicFlow-inter"/>E.1.26 #dynamicFlow-inter</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-inter" id="feature-dynamicFlow-inter"/>E.1.24 #dynamicFlow-inter</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-inter</code> feature if it recognizes and
is capable of transforming the flow interval function <code>inter(..)</code> as
defined by <a href="#style-value-flowIntervalFunction"><b>8.3.7 <flowIntervalFunction></b></a> when used with the
@@ -6922,7 +7751,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-intra" id="feature-dynamicFlow-intra"/>E.1.27 #dynamicFlow-intra</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-intra" id="feature-dynamicFlow-intra"/>E.1.25 #dynamicFlow-intra</h4><p>A TT AF transformation processor supports the
<code>#dynamicFlow-intra</code> feature if it recognizes and
is capable of transforming the flow interval function <code>intra(..)</code> as
defined by <a href="#style-value-flowIntervalFunction"><b>8.3.7 <flowIntervalFunction></b></a> when used with the
@@ -6933,7 +7762,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-jump" id="feature-dynamicFlow-jump"/>E.1.28 #dynamicFlow-jump</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-jump" id="feature-dynamicFlow-jump"/>E.1.26 #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
@@ -6944,18 +7773,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-leftToRight" id="feature-dynamicFlow-leftToRight"/>E.1.29 #dynamicFlow-leftToRight</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-leftToRight</code> feature if it recognizes and
-is capable of transforming the flow transition style <code>leftToRight</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-leftToRight</code> feature if it implements
-presentation semantic support for the flow transition style <code>leftToRight</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-line" id="feature-dynamicFlow-line"/>E.1.30 #dynamicFlow-line</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-line" id="feature-dynamicFlow-line"/>E.1.27 #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
@@ -6966,7 +7784,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.31 #dynamicFlow-out</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-out" id="feature-dynamicFlow-out"/>E.1.28 #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
@@ -6977,18 +7795,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-pixel" id="feature-dynamicFlow-pixel"/>E.1.32 #dynamicFlow-pixel</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-pixel</code> feature if it recognizes and
-is capable of transforming the flow unit <code>pixel</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>
+<h4><a name="feature-dynamicFlow-rollUp" id="feature-dynamicFlow-rollUp"/>E.1.29 #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-pixel</code> feature if it implements
-presentation semantic support for the flow unit <code>pixel</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>
+<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.33 #dynamicFlow-smooth</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-smooth" id="feature-dynamicFlow-smooth"/>E.1.30 #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
@@ -6999,40 +7813,18 @@
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.34 #dynamicFlow-teletext</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-dynamicFlow-teletext" id="feature-dynamicFlow-teletext"/>E.1.31 #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>
attribute that is equivalent to
-"in(glyph,jump) out(line,jump)".</p><p>A TT AF presentation processor supports the
+<code>in(glyph,jump) out(line,jump)</code>.</p><p>A TT AF presentation processor supports the
<code>#dynamicFlow-teletext</code> feature if it implements presentation semantic
-support forany well-defined value of the
-<a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a>
-attribute that is equivalent to "in(glyph,jump)
-out(line,jump)".</p></div><div class="div3">
-<h4><a name="feature-dynamicFlow-topToBottom" id="feature-dynamicFlow-topToBottom"/>E.1.35 #dynamicFlow-topToBottom</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-topToBottom</code> feature if it recognizes and
-is capable of transforming the flow transition style <code>topToBottom</code> as
-defined by <a href="#style-value-flowFunction"><b>8.3.6 <flowFunction></b></a> when used with the
+support for any well-defined 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-topToBottom</code> feature if it implements
-presentation semantic support for the flow transition style <code>topToBottom</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-within" id="feature-dynamicFlow-within"/>E.1.36 #dynamicFlow-within</h4><p>A TT AF transformation processor supports the
-<code>#dynamicFlow-within</code> feature if it recognizes and
-is capable of transforming the flow function <code>within(..)</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-within</code> feature if it implements
-presentation semantic support for the flow function <code>within(..)</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-word" id="feature-dynamicFlow-word"/>E.1.37 #dynamicFlow-word</h4><p>A TT AF transformation processor supports the
+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
<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
@@ -7043,21 +7835,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.38 #extent</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-extent" id="feature-extent"/>E.1.33 #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.39 #fontFamily</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily" id="feature-fontFamily"/>E.1.34 #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.40 #fontFamily-generic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontFamily-generic" id="feature-fontFamily-generic"/>E.1.35 #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>
@@ -7066,7 +7858,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.41 #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.36 #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>
@@ -7075,97 +7867,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.42 #fontSize</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize" id="feature-fontSize"/>E.1.37 #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.43 #fontSize-anisomorphic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize-anisomorphic" id="feature-fontSize-anisomorphic"/>E.1.38 #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.44 #fontSize-isomorphic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontSize-isomorphic" id="feature-fontSize-isomorphic"/>E.1.39 #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.45 #fontStyle</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle" id="feature-fontStyle"/>E.1.40 #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.46 #fontStyle-italic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontStyle-italic" id="feature-fontStyle-italic"/>E.1.41 #fontStyle-italic</h4><p>A TT AF transformation processor supports the
<code>#fontStyle-italic</code> feature if it recognizes and is
-capable of transforming <code>italic</code> value of the <a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a>
+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.47 #fontWeight</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontWeight" id="feature-fontWeight"/>E.1.42 #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.48 #fontWeight-bold</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-fontWeight-bold" id="feature-fontWeight-bold"/>E.1.43 #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.49 #frameRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-frameRate" id="feature-frameRate"/>E.1.44 #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.50 #frameRateMultiplier</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-frameRateMultiplier" id="feature-frameRateMultiplier"/>E.1.45 #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.51 #layout</h4><p>A TT AF transformation processor supports the <code>#layout</code>
+<h4><a name="feature-layout" id="feature-layout"/>E.1.46 #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.52 #length</h4><p>A TT AF transformation processor supports the <code>#length</code>
+<h4><a name="feature-length" id="feature-length"/>E.1.47 #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.53 #length-cell</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-cell" id="feature-length-cell"/>E.1.48 #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.54 #length-em</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-em" id="feature-length-em"/>E.1.49 #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.55 #length-integer</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-integer" id="feature-length-integer"/>E.1.50 #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
@@ -7173,7 +7965,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.56 #length-negative</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-negative" id="feature-length-negative"/>E.1.51 #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
@@ -7181,7 +7973,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.57 #length-percentage</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-percentage" id="feature-length-percentage"/>E.1.52 #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
@@ -7189,14 +7981,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.58 #length-pixel</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-pixel" id="feature-length-pixel"/>E.1.53 #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.59 #length-positive</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-positive" id="feature-length-positive"/>E.1.54 #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
@@ -7204,7 +7996,7 @@
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.60 #length-real</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-length-real" id="feature-length-real"/>E.1.55 #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
@@ -7212,21 +8004,21 @@
support for real values of the <a href="#style-value-length"><length></a> style value
expression.
</p></div><div class="div3">
-<h4><a name="feature-lineHeight" id="feature-lineHeight"/>E.1.61 #lineHeight</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-lineHeight" id="feature-lineHeight"/>E.1.56 #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.62 #markerMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-markerMode" id="feature-markerMode"/>E.1.57 #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.63 #metadata</h4><p>A TT AF transformation processor supports the <code>#metadata</code>
+<h4><a name="feature-metadata" id="feature-metadata"/>E.1.58 #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
@@ -7234,173 +8026,167 @@
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.64 #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.59 #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.65 #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.60 #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.66 #opacity</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-opacity" id="feature-opacity"/>E.1.61 #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
-<code>#opacity</code> feature if it implements presentation semantic support for
+<code>#opacity</code> feature if it (1) implements presentation semantic support for
the <a href="#style-attribute-opacity"><code>tts:opacity</code></a>
-attribute.</p></div><div class="div3">
-<h4><a name="feature-origin" id="feature-origin"/>E.1.67 #origin</h4><p>A TT AF transformation processor supports the
+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.62 #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.68 #overflow</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-overflow" id="feature-overflow"/>E.1.63 #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.69 #overflow-dynamic</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-overflow-dynamic" id="feature-overflow-dynamic"/>E.1.64 #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.70 #padding</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding" id="feature-padding"/>E.1.65 #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.71 #padding-1</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-1" id="feature-padding-1"/>E.1.66 #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.72 #padding-2</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-2" id="feature-padding-2"/>E.1.67 #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.73 #padding-3</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-3" id="feature-padding-3"/>E.1.68 #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.74 #padding-4</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-padding-4" id="feature-padding-4"/>E.1.69 #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.75 #pixelAspectRatio</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-pixelAspectRatio" id="feature-pixelAspectRatio"/>E.1.70 #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.76 #presentation</h4><p>A TT AF processor supports the
+<h4><a name="feature-presentation" id="feature-presentation"/>E.1.71 #presentation</h4><p>A TT AF processor supports the
<code>#presentation</code> feature if it is a compliant TT AF Presentation
Processor as defined by <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-profile" id="feature-profile"/>E.1.77 #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.</p><p>A TT AF presentation processor supports the
+<h4><a name="feature-profile" id="feature-profile"/>E.1.72 #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
+transforming the following vocabulary defined by
+<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 <a href="#parameter-attribute-profile"><code>ttp:profile</code></a>
-attribute.</p></div><div class="div3">
-<h4><a name="feature-requiredExtensions" id="feature-requiredExtensions"/>E.1.78 #requiredExtensions</h4><p>A TT AF processor supports the
-<code>#requiredExtensions</code> feature if it implements semantic support
-for the <a href="#parameter-attribute-requiredExtensions"><code>ttp:requiredExtensions</code></a>
-attribute on the
-<a href="#content-vocabulary-tt"><code>tt</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-requiredFeatures" id="feature-requiredFeatures"/>E.1.79 #requiredFeatures</h4><p>A TT AF processor supports the
-<code>#requiredFeatures</code> feature if it implements semantic support
-for the <a href="#parameter-attribute-requiredFeatures"><code>ttp:requiredFeatures</code></a>
-attribute on the
-<a href="#content-vocabulary-tt"><code>tt</code></a> element.</p></div><div class="div3">
-<h4><a name="feature-showBackground" id="feature-showBackground"/>E.1.80 #showBackground</h4><p>A TT AF transformation processor supports the
+for the same vocabulary specified above.</p></div><div class="div3">
+<h4><a name="feature-rollUp" id="feature-rollUp"/>E.1.73 #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="#overflow-dynamic"><code>#overflow-dynamic</code></a></p></li><li><p><a href="#dynamicFlow-rollUp"><code>#dynamicFlow-rollUp</code></a></p></li></ul></div><div class="div3">
+<h4><a name="feature-showBackground" id="feature-showBackground"/>E.1.74 #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.81 #smpteMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-smpteMode" id="feature-smpteMode"/>E.1.75 #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.82 #structure</h4><p>A TT AF transformation processor supports the <code>#structure</code>
+<h4><a name="feature-structure" id="feature-structure"/>E.1.76 #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="#content-vocabulary-tt"><code>tt</code></a></p></li><li><p><a href="#styling-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.83 #styling</h4><p>A TT AF transformation processor supports the <code>#styling</code>
+<h4><a name="feature-styling" id="feature-styling"/>E.1.77 #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.84 #styling-chained</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-chained" id="feature-styling-chained"/>E.1.78 #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.85 #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.79 #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.86 #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.80 #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.87 #styling-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-inline" id="feature-styling-inline"/>E.1.81 #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.88 #styling-nested</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-nested" id="feature-styling-nested"/>E.1.82 #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.89 #styling-referential</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-styling-referential" id="feature-styling-referential"/>E.1.83 #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.90 #subFrameRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-subFrameRate" id="feature-subFrameRate"/>E.1.84 #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.91 #textAlign</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign" id="feature-textAlign"/>E.1.85 #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.92 #textAlign-absolute</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign-absolute" id="feature-textAlign-absolute"/>E.1.86 #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>
@@ -7409,7 +8195,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.93 #textAlign-relative</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textAlign-relative" id="feature-textAlign-relative"/>E.1.87 #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>
@@ -7418,14 +8204,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.94 #textDecoration</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration" id="feature-textDecoration"/>E.1.88 #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.95 #textDecoration-over</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-over" id="feature-textDecoration-over"/>E.1.89 #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>
@@ -7434,7 +8220,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.96 #textDecoration-through</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-through" id="feature-textDecoration-through"/>E.1.90 #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>
@@ -7443,7 +8229,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.97 #textDecoration-under</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textDecoration-under" id="feature-textDecoration-under"/>E.1.91 #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>
@@ -7452,56 +8238,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.98 #textOutline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textOutline" id="feature-textOutline"/>E.1.92 #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.99 #textOutline-blur</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-textOutline-blur" id="feature-textOutline-blur"/>E.1.93 #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.100 #tickRate</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-tickRate" id="feature-tickRate"/>E.1.94 #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.101 #timeBase-clock</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-clock" id="feature-timeBase-clock"/>E.1.95 #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.102 #timeBase-media</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-media" id="feature-timeBase-media"/>E.1.96 #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.103 #timeBase-smpte</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeBase-smpte" id="feature-timeBase-smpte"/>E.1.97 #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.104 #timeContainer</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-timeContainer" id="feature-timeContainer"/>E.1.98 #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.105 #time-clock</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-clock" id="feature-time-clock"/>E.1.99 #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>
@@ -7510,7 +8296,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.106 #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.100 #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
@@ -7524,7 +8310,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.107 #time-offset</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-time-offset" id="feature-time-offset"/>E.1.101 #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>
@@ -7533,7 +8319,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.108 #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.102 #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
@@ -7547,7 +8333,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.109 #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.103 #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
@@ -7558,29 +8344,29 @@
</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.110 #timing</h4><p>A TT AF transformation processor supports the <code>#timing</code>
+<h4><a name="feature-timing" id="feature-timing"/>E.1.104 #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.111 #transformation</h4><p>A TT AF processor supports the
+<h4><a name="feature-transformation" id="feature-transformation"/>E.1.105 #transformation</h4><p>A TT AF processor supports the
<code>#transformation</code> feature if it is a compliant TT AF Transformation
Processor as defined by <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a>.</p></div><div class="div3">
-<h4><a name="feature-unicodeBidi" id="feature-unicodeBidi"/>E.1.112 #unicodeBidi</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-unicodeBidi" id="feature-unicodeBidi"/>E.1.106 #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.113 #visibility</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility" id="feature-visibility"/>E.1.107 #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.114 #visibility-block</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-block" id="feature-visibility-block"/>E.1.108 #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
@@ -7589,7 +8375,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.115 #visibility-inline</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-inline" id="feature-visibility-inline"/>E.1.109 #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
@@ -7598,28 +8384,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.116 #visibility-region</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-visibility-region" id="feature-visibility-region"/>E.1.110 #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.117 #wrapOption</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-wrapOption" id="feature-wrapOption"/>E.1.111 #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.118 #writingMode</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode" id="feature-writingMode"/>E.1.112 #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.119 #writingMode-vertical</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-vertical" id="feature-writingMode-vertical"/>E.1.113 #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>
@@ -7628,7 +8414,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.120 #writingMode-horizontal</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-writingMode-horizontal" id="feature-writingMode-horizontal"/>E.1.114 #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>
@@ -7637,7 +8423,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.121 #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.115 #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>
@@ -7646,7 +8432,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.122 #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.116 #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>
@@ -7655,7 +8441,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.123 #zIndex</h4><p>A TT AF transformation processor supports the
+<h4><a name="feature-zIndex" id="feature-zIndex"/>E.1.117 #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
@@ -7664,24 +8450,30 @@
attribute.</p></div></div><div class="div2">
<h3><a name="feature-support" id="feature-support"/>E.2 Feature Support</h3><p>The following table, <a href="#feature-support-table"><b>Table E-1 – Feature Support</b></a>,
enumerates every defined feature designation (expressed without the TT
-Feature Prefix Namespace), and, for each designated feature, specifies
+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>M</td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>O</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>M</td></tr><tr><td><a href="#feature-display-inline"><code>#display-inline</code></a></td><td>O</td><td>M</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-barWipe"><code>#dynamicFlow-barWipe</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-block"><code>#dynamicFlow-block</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-fade"><code>#dynamicFlow-fade</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-inline"><code>#dynamicFlow-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-inter"><code>#dynamicFlow-inter</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-intra"><code>#dynamicFlow-intra</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-leftToRight"><code>#dynamicFlow-leftToRight</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-pixel"><code>#dynamicFlow-pixel</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-topToBottom"><code>#dynamicFlow-topToBottom</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-within"><code>#dynamicFlow-within</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>M</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>M</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>M</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>M</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>M</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>M</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>M</td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>O</td><td>M</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-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>O</td><td>O</td></tr><tr><td><a href="#feature-requiredExtensions"><code>#requiredExtensions</code></a></td><td>M</td><td>M</td></tr><tr><td><a href="#feature-requiredFeatures"><code>#requiredFeatures</code></a></td><td>M</td><td>M</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>M</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>M</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>M</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>O</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>O</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>M</td></tr><tr><td><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></td><td>O</td><td>M</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>M</td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>O</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>M</td></tr><tr><td><a href="#feature-display-inline"><code>#display-inline</code></a></td><td>O</td><td>M</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-block"><code>#dynamicFlow-block</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-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-inline"><code>#dynamicFlow-inline</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-inter"><code>#dynamicFlow-inter</code></a></td><td>O</td><td>O</td></tr><tr><td><a href="#feature-dynamicFlow-intra"><code>#dynamicFlow-intra</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>M</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>M</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>M</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>M</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>M</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>M</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>M</td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>O</td><td>M</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-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>M</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>M</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>M</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>O</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>O</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>M</td></tr><tr><td><a href="#feature-visibility-inline"><code>#visibility-inline</code></a></td><td>O</td><td>M</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.</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-core"><code>#core</code></a></td><td>
+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.2 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><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-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="#content-vocabulary-tt"><code>tt</code></a>,
<a href="#styling-vocabulary-head"><code>head</code></a>
-</td></tr><tr><td><a href="#feature-requiredExtensions"><code>#requiredExtensions</code></a></td><td><a href="#content-vocabulary-tt">@<code>requiredExtensions</code></a>
-applied to <a href="content-vocabulary-tt"><code>tt</code></a></td></tr><tr><td><a href="#feature-requiredFeatures"><code>#requiredFeatures</code></a></td><td><a href="#content-vocabulary-tt">@<code>requiredFeatures</code></a>
-applied to <a href="content-vocabulary-tt"><code>tt</code></a></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,
+</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.</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-color"><code>#color</code></a></td><td><a href="#style-attribute-color">@<code>tts:color</code></a></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
+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.1 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-color"><code>#color</code></a></td><td><a href="#style-attribute-color">@<code>tts:color</code></a></td></tr><tr><td><a href="#feature-content"><code>#content</code></a></td><td>
<a href="#content-vocabulary-body"><code>body</code></a>,
<a href="#content-vocabulary-div"><code>div</code></a>,
<a href="#content-vocabulary-p"><code>p</code></a>,
@@ -7718,9 +8510,7 @@
<code><a href="#style-value-integer"><integer></a>px</code>
</td></tr><tr><td><a href="#feature-length-positive"><code>#length-positive</code></a></td><td>
<code><a href="#style-value-length"><length></a></code>≥0
-</td></tr><tr><td><a href="#feature-presentation"><code>#presentation</code></a></td><td/></tr><tr><td><a href="#feature-requiredExtensions"><code>#requiredExtensions</code></a></td><td><a href="#content-vocabulary-tt">@<code>requiredExtensions</code></a>
-applied to <a href="content-vocabulary-tt"><code>tt</code></a></td></tr><tr><td><a href="#feature-requiredFeatures"><code>#requiredFeatures</code></a></td><td><a href="#content-vocabulary-tt">@<code>requiredFeatures</code></a>
-applied to <a href="content-vocabulary-tt"><code>tt</code></a></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-presentation"><code>#presentation</code></a></td><td/></tr><tr><td><a href="#feature-structure"><code>#structure</code></a></td><td>
<a href="#content-vocabulary-tt"><code>tt</code></a>,
<a href="#styling-vocabulary-head"><code>head</code></a>
</td></tr><tr><td><a href="#feature-styling-inheritance-content"><code>#styling-inheritance-content</code></a></td><td/></tr><tr><td><a href="#feature-styling-inline"><code>#styling-inline</code></a></td><td/></tr><tr><td><a href="#feature-textAlign-absolute"><code>#textAlign-absolute</code></a></td><td>
@@ -7741,7 +8531,7 @@
<a href="#content-vocabulary-br"><code>br</code></a>
</td></tr></tbody></table></div></div><div class="diff-add">
<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 presence of extension
+used to express authorial intent regarding the support for extension
mechanisms in a TT AF processor.</p><div class="div2">
<h3><a name="extension-designations" id="extension-designations"/>F.1 Extension Designations</h3><p>An extension designation is expressed as a string that adheres to the following
form:</p><div class="exampleInner"><pre>
@@ -7749,46 +8539,285 @@
: extension-namespace designation
extension-namespace
- : <em>TT Extension Prefix Namespace</em> // <span><code>http://www.w3.org/2006/10/ttaf1/extension</code></span>
+ : <em>TT Extension Namespace</em> // http://www.w3.org/2006/10/ttaf1/extension
+ | <em>Other Extension Namespace</em> // expressed as an absolute URI
designation
- : "#" designation-token
-
-designation-token
- : standard-designation-token
- | extension-designation-token
-
-standard-designation-token
- : token-char+
-
-extension-designation-token
- : "x-" token-char+
+ : "#" token-char+
token-char
: { XML NameChar } // XML 1.1 Production [4a]
-</pre></div><p>All values of <code>designation-token</code> that do not start with the prefix
-<code>x-</code> are reserved for future standardization.</p><p>An example is shown below of using feature and extension
-designations to indicate the author's intent that a receiving
-processor must implement both transformation and presentation
-processors and must perform a non-standardized (extension)
-transformation in order to pre-filter by language.</p><table summary="HTML Table" id="dfxp-example-requiredExtensions" class="example"><caption>Example Fragment – Required Extensions</caption><tbody><tr><td>
-<div class="exampleInner"><pre>
-<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"
- requiredFeatures="http://www.w3.org/2006/10/ttaf1/feature#transformation
- http://www.w3.org/2006/10/ttaf1/feature#presentation"
- <span class="strong">requiredExtensions="http://www.w3.org/2006/10/ttaf1/extension#x-prefilter-by-language"</span>>
- <head/>
- <body>
- <div xml:lang="en"/>
- <div xml:lang="fr"/>
- <div xml:lang="es"/>
- <div xml:lang="it"/>
- <div xml:lang="de"/>
- </body>
-</tt>
-</pre></div>
-</td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="references" id="references"/>G References</h2><p><em>This appendix is normative.</em></p><dl><dt class="label"><a name="css2" id="css2"/>CSS2</dt><dd>Bert Bos et al.,
+</pre></div><p>If the extension namespace of an extension designation is the TT
+Extension Namespace, then all values of the following
+<code>designation</code> token are reserved for future
+standardization.</p><p>If the extension namespace of an extension designation is not the
+TT Extension Namespace, i.e., is an <em>Other Extension Namespace</em>,
+then the extension namespace must be expressed as an absolute URI
+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="diff-add">
+<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-presentation"><b>G.1 DFXP Presentation Profile</b></a></p></li><li><p><a href="#profile-dfxp-transformation"><b>G.2 DFXP Transformation 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-presentation" id="profile-dfxp-presentation"/>G.1 DFXP Presentation Profile</h3><div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8"?>
+<!-- this file defines the "presentation" profile of ttaf1-dfxp -->
+<profile xmlns="http://www.w3.org/2006/10/ttaf1#parameter">
+<features base="http://www.w3.org/2006/10/ttaf1/feature"/>
+<!-- required (mandatory) feature support -->
+<feature value="required">#color</feature>
+<feature value="required">#content</feature>
+<feature value="required">#core</feature>
+<feature value="required">#display-block</feature>
+<feature value="required">#display-inline</feature>
+<feature value="required">#extent</feature>
+<feature value="required">#fontSize-isomorphic</feature>
+<feature value="required">#fontStyle-italic</feature>
+<feature value="required">#fontWeight-bold</feature>
+<feature value="required">#length-cell</feature>
+<feature value="required">#length-pixel</feature>
+<feature value="required">#length-positive</feature>
+<feature value="required">#presentation</feature>
+<feature value="required">#profile</feature>
+<feature value="required">#structure</feature>
+<feature value="required">#styling-inheritance-content</feature>
+<feature value="required">#styling-inline</feature>
+<feature value="required">#textAlign-absolute</feature>
+<feature value="required">#time-offset</feature>
+<feature value="required">#timing</feature>
+<feature value="required">#visibility-block</feature>
+<feature value="required">#visibility-inline</feature>
+<!-- optional (voluntary) feature support -->
+<feature value="optional">#animation</feature>
+<feature value="optional">#backgroundColor</feature>
+<feature value="optional">#backgroundColor-block</feature>
+<feature value="optional">#backgroundColor-inline</feature>
+<feature value="optional">#backgroundColor-region</feature>
+<feature value="optional">#bidi</feature>
+<feature value="optional">#cellResolution</feature>
+<feature value="optional">#clockMode</feature>
+<feature value="optional">#direction</feature>
+<feature value="optional">#display</feature>
+<feature value="optional">#display-region</feature>
+<feature value="optional">#displayAlign</feature>
+<feature value="optional">#dynamicFlow</feature>
+<feature value="optional">#dynamicFlow-block</feature>
+<feature value="optional">#dynamicFlow-character</feature>
+<feature value="optional">#dynamicFlow-glyph</feature>
+<feature value="optional">#dynamicFlow-in</feature>
+<feature value="optional">#dynamicFlow-inline</feature>
+<feature value="optional">#dynamicFlow-inter</feature>
+<feature value="optional">#dynamicFlow-intra</feature>
+<feature value="optional">#dynamicFlow-jump</feature>
+<feature value="optional">#dynamicFlow-line</feature>
+<feature value="optional">#dynamicFlow-out</feature>
+<feature value="optional">#dynamicFlow-rollUp</feature>
+<feature value="optional">#dynamicFlow-smooth</feature>
+<feature value="optional">#dynamicFlow-teletext</feature>
+<feature value="optional">#dynamicFlow-word</feature>
+<feature value="optional">#fontFamily</feature>
+<feature value="optional">#fontFamily-generic</feature>
+<feature value="optional">#fontFamily-non-generic</feature>
+<feature value="optional">#fontSize</feature>
+<feature value="optional">#fontSize-anisomorphic</feature>
+<feature value="optional">#fontStyle</feature>
+<feature value="optional">#fontWeight</feature>
+<feature value="optional">#frameRate</feature>
+<feature value="optional">#frameRateMultiplier</feature>
+<feature value="optional">#layout</feature>
+<feature value="optional">#length</feature>
+<feature value="optional">#length-em</feature>
+<feature value="optional">#length-negative</feature>
+<feature value="optional">#length-percentage</feature>
+<feature value="optional">#length-real</feature>
+<feature value="optional">#lineHeight</feature>
+<feature value="optional">#markerMode</feature>
+<feature value="optional">#metadata</feature>
+<feature value="optional">#nested-div</feature>
+<feature value="optional">#nested-span</feature>
+<feature value="optional">#opacity</feature>
+<feature value="optional">#origin</feature>
+<feature value="optional">#overflow</feature>
+<feature value="optional">#overflow-scroll</feature>
+<feature value="optional">#padding</feature>
+<feature value="optional">#padding-1</feature>
+<feature value="optional">#padding-2</feature>
+<feature value="optional">#padding-3</feature>
+<feature value="optional">#padding-4</feature>
+<feature value="optional">#pixelAspectRatio</feature>
+<feature value="optional">#rollUp</feature>
+<feature value="optional">#showBackground</feature>
+<feature value="optional">#smpteMode</feature>
+<feature value="optional">#styling</feature>
+<feature value="optional">#styling-chained</feature>
+<feature value="optional">#styling-inheritance-region</feature>
+<feature value="optional">#styling-nested</feature>
+<feature value="optional">#styling-referential</feature>
+<feature value="optional">#subFrameRate</feature>
+<feature value="optional">#textAlign</feature>
+<feature value="optional">#textAlign-relative</feature>
+<feature value="optional">#textDecoration</feature>
+<feature value="optional">#textDecoration-over</feature>
+<feature value="optional">#textDecoration-through</feature>
+<feature value="optional">#textDecoration-under</feature>
+<feature value="optional">#textOutline</feature>
+<feature value="optional">#textOutline-blur</feature>
+<feature value="optional">#tickRate</feature>
+<feature value="optional">#timeBase-clock</feature>
+<feature value="optional">#timeBase-media</feature>
+<feature value="optional">#timeBase-smpte</feature>
+<feature value="optional">#timeContainer</feature>
+<feature value="optional">#time-clock</feature>
+<feature value="optional">#time-clock-with-frames</feature>
+<feature value="optional">#time-offset-with-frames</feature>
+<feature value="optional">#time-offset-with-ticks</feature>
+<feature value="optional">#transformation</feature>
+<feature value="optional">#unicodeBidi</feature>
+<feature value="optional">#visibility</feature>
+<feature value="optional">#visibility-region</feature>
+<feature value="optional">#wrapOption</feature>
+<feature value="optional">#writingMode</feature>
+<feature value="optional">#writingMode-vertical</feature>
+<feature value="optional">#writingMode-horizontal</feature>
+<feature value="optional">#writingMode-horizontal-lr</feature>
+<feature value="optional">#writingMode-horizontal-rl</feature>
+<feature value="optional">#zIndex</feature>
+</features>
+<extensions base="http://www.w3.org/2006/10/ttaf1/extension">
+<!-- required (mandatory) extension support -->
+<!-- optional (voluntary) extension support -->
+</extensions>
+</profile>
+</pre></div></div><div class="div2">
+<h3><a name="profile-dfxp-transformation" id="profile-dfxp-transformation"/>G.2 DFXP Transformation Profile</h3><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 base="http://www.w3.org/2006/10/ttaf1/feature"/>
+<!-- required (mandatory) feature support -->
+<feature value="required">#core</feature>
+<feature value="required">#profile</feature>
+<feature value="required">#structure</feature>
+<feature value="required">#transformation</feature>
+<!-- optional (voluntary) feature support -->
+<feature value="optional">#animation</feature>
+<feature value="optional">#backgroundColor-block</feature>
+<feature value="optional">#backgroundColor-inline</feature>
+<feature value="optional">#backgroundColor-region</feature>
+<feature value="optional">#backgroundColor</feature>
+<feature value="optional">#bidi</feature>
+<feature value="optional">#cellResolution</feature>
+<feature value="optional">#clockMode</feature>
+<feature value="optional">#color</feature>
+<feature value="optional">#content</feature>
+<feature value="optional">#direction</feature>
+<feature value="optional">#display-block</feature>
+<feature value="optional">#display-inline</feature>
+<feature value="optional">#display-region</feature>
+<feature value="optional">#display</feature>
+<feature value="optional">#displayAlign</feature>
+<feature value="optional">#dynamicFlow-block</feature>
+<feature value="optional">#dynamicFlow-character</feature>
+<feature value="optional">#dynamicFlow-glyph</feature>
+<feature value="optional">#dynamicFlow-in</feature>
+<feature value="optional">#dynamicFlow-inline</feature>
+<feature value="optional">#dynamicFlow-inter</feature>
+<feature value="optional">#dynamicFlow-intra</feature>
+<feature value="optional">#dynamicFlow-jump</feature>
+<feature value="optional">#dynamicFlow-line</feature>
+<feature value="optional">#dynamicFlow-out</feature>
+<feature value="optional">#dynamicFlow-rollUp</feature>
+<feature value="optional">#dynamicFlow-smooth</feature>
+<feature value="optional">#dynamicFlow-teletext</feature>
+<feature value="optional">#dynamicFlow-word</feature>
+<feature value="optional">#dynamicFlow</feature>
+<feature value="optional">#extent</feature>
+<feature value="optional">#fontFamily-generic</feature>
+<feature value="optional">#fontFamily-non-generic</feature>
+<feature value="optional">#fontFamily</feature>
+<feature value="optional">#fontSize-anisomorphic</feature>
+<feature value="optional">#fontSize-isomorphic</feature>
+<feature value="optional">#fontSize</feature>
+<feature value="optional">#fontStyle-italic</feature>
+<feature value="optional">#fontStyle</feature>
+<feature value="optional">#fontWeight-bold</feature>
+<feature value="optional">#fontWeight</feature>
+<feature value="optional">#frameRate</feature>
+<feature value="optional">#frameRateMultiplier</feature>
+<feature value="optional">#layout</feature>
+<feature value="optional">#length-cell</feature>
+<feature value="optional">#length-em</feature>
+<feature value="optional">#length-negative</feature>
+<feature value="optional">#length-percentage</feature>
+<feature value="optional">#length-pixel</feature>
+<feature value="optional">#length-positive</feature>
+<feature value="optional">#length-real</feature>
+<feature value="optional">#length</feature>
+<feature value="optional">#lineHeight</feature>
+<feature value="optional">#markerMode</feature>
+<feature value="optional">#metadata</feature>
+<feature value="optional">#nested-div</feature>
+<feature value="optional">#nested-span</feature>
+<feature value="optional">#opacity</feature>
+<feature value="optional">#origin</feature>
+<feature value="optional">#overflow-scroll</feature>
+<feature value="optional">#overflow</feature>
+<feature value="optional">#padding-1</feature>
+<feature value="optional">#padding-2</feature>
+<feature value="optional">#padding-3</feature>
+<feature value="optional">#padding-4</feature>
+<feature value="optional">#padding</feature>
+<feature value="optional">#pixelAspectRatio</feature>
+<feature value="optional">#rollUp</feature>
+<feature value="optional">#showBackground</feature>
+<feature value="optional">#smpteMode</feature>
+<feature value="optional">#styling-chained</feature>
+<feature value="optional">#styling-inheritance-content</feature>
+<feature value="optional">#styling-inheritance-region</feature>
+<feature value="optional">#styling-inline</feature>
+<feature value="optional">#styling-nested</feature>
+<feature value="optional">#styling-referential</feature>
+<feature value="optional">#styling</feature>
+<feature value="optional">#subFrameRate</feature>
+<feature value="optional">#textAlign-absolute</feature>
+<feature value="optional">#textAlign-relative</feature>
+<feature value="optional">#textAlign</feature>
+<feature value="optional">#textDecoration-over</feature>
+<feature value="optional">#textDecoration-through</feature>
+<feature value="optional">#textDecoration-under</feature>
+<feature value="optional">#textDecoration</feature>
+<feature value="optional">#textOutline-blur</feature>
+<feature value="optional">#textOutline</feature>
+<feature value="optional">#tickRate</feature>
+<feature value="optional">#time-clock-with-frames</feature>
+<feature value="optional">#time-clock</feature>
+<feature value="optional">#time-offset-with-frames</feature>
+<feature value="optional">#time-offset-with-ticks</feature>
+<feature value="optional">#time-offset</feature>
+<feature value="optional">#timeBase-clock</feature>
+<feature value="optional">#timeBase-media</feature>
+<feature value="optional">#timeBase-smpte</feature>
+<feature value="optional">#timeContainer</feature>
+<feature value="optional">#timing</feature>
+<feature value="optional">#transformation</feature>
+<feature value="optional">#unicodeBidi</feature>
+<feature value="optional">#visibility-block</feature>
+<feature value="optional">#visibility-inline</feature>
+<feature value="optional">#visibility-region</feature>
+<feature value="optional">#visibility</feature>
+<feature value="optional">#wrapOption</feature>
+<feature value="optional">#writingMode-horizontal-lr</feature>
+<feature value="optional">#writingMode-horizontal-rl</feature>
+<feature value="optional">#writingMode-horizontal</feature>
+<feature value="optional">#writingMode-vertical</feature>
+<feature value="optional">#writingMode</feature>
+<feature value="optional">#zIndex</feature>
+</features>
+<extensions base="http://www.w3.org/2006/10/ttaf1/extension">
+<!-- required (mandatory) extension support -->
+<!-- optional (voluntary) extension support -->
+</extensions>
+</profile>
+</pre></div></div></div><div class="div1">
+<h2><a name="references" id="references"/>H References</h2><p><em>This appendix is normative.</em></p><dl><dt class="label"><a name="css2" id="css2"/>CSS2</dt><dd>Bert Bos et al.,
<a href="http://www.w3.org/TR/1998/REC-CSS2-19980512/"><cite>Cascading
Style Sheets, Level 2</cite></a>, W3C Recommendation, 12
May 1998. (See
@@ -7886,7 +8915,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"/>H Other References (Non-Normative)</h2><dl><dt class="label"><a name="cea608c" id="cea608c"/>CEA-608-C</dt><dd>
+<h2><a name="other-references" id="other-references"/>I Other References (Non-Normative)</h2><dl><dt class="label"><a name="cea608c" id="cea608c"/>CEA-608-C</dt><dd>
EIA/CEA-608-C,
<a href="http://members.ce.org/standards/StandardDetails.aspx?Id=1506"><cite>Line 21 Data
Services</cite></a>, EIA/CEA Standard,
@@ -7933,1066 +8962,6 @@
August 2002. (See
<a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>.)
</dd></dl></div><div class="div1">
-<h2><a name="sample-code" id="sample-code"/>I Sample Code (Non-Normative)</h2><p>This appendix contains sample code, also available in
-a <a href="scm/code.zip">ZIP Archive</a> along with related files, that implements
-certain algorithms described by this specification. This code makes
-use of the MIT Scheme <a href="#scheme">[SCHEME]</a> dialect of the Lisp Programming Language.</p><p>The following algorithms are implemented by this code:</p><ul><li><p>Reduced XML Infoset (RXI)</p></li><li><p>Abstract Document Instance (ADI)</p></li><li><p>Time Interval Resolver (TIR)</p></li><li><p>Flow Object Transformer (FOX)</p></li><li><p>Dynamic Text Flow Processor (DTF)</p></li></ul><p>Subsequent to the sample code listings, a transcript of a sample
-compile, load, and run session is provided.</p><div class="div2">
-<h3><a name="code-rxi" id="code-rxi"/>I.1 Reduced XML Infoset (RXI) – <code>RXI.SCM</code></h3><div class="exampleInner"><pre>;;; -*-Scheme-*-
-;;; Package: (dfxp rxi)
-
-;
-; DFXP Reduced XML Infoset Load, Save, Transformer
-;
-
-(declare (usual-integrations))
-
-;
-; The default reverse binding for the XML namespace is represented
-; by *XML-DEFAULT-REVERSE-BINDING*.
-;
-(define *xml-default-reverse-binding*
- '("http://www.w3.org/XML/1998/namespace" . "xml"))
-
-;
-; An RXI-BINDINGS structure consists of a BINDINGS slot that contains a
-; stack represented as a list of association lists whose keys are XMLNS name
-; prefixes and whose values are XMLNS namespace URIs. A binding for the
-; "empty" or "null" namespace is designated by a prefix whose value is "".
-;
-(define-structure
- (rxi-bindings
- (conc-name rxi-bindings/)
- (constructor make-rxi-bindings (#!optional bindings)))
- (bindings '() read-only #f))
-
-;
-; Push a list of NEW bindings onto BINDINGS.
-;
-(define (rxi-bindings/push! bindings new)
- (set-rxi-bindings/bindings!
- bindings
- (cons new (rxi-bindings/bindings bindings))))
-
-;
-; Pop the list of bindings at the top of BINDINGS.
-;
-(define (rxi-bindings/pop! bindings)
- (set-rxi-bindings/bindings!
- bindings
- (let ((old (rxi-bindings/bindings bindings)))
- (if (pair? old)
- (cdr old)
- '()))))
-
-;
-; Look up a binding for the designated XMLNS name PREFIX in BINDINGS,
-; returning either an associated XMLNS namespace URI string or '() if
-; not found.
-;
-
-(define (rxi-bindings/lookup bindings prefix)
- (let find
- ((bindings (rxi-bindings/bindings bindings)))
- (cond ((null? bindings)
- '())
- (else
- (let
- ((b (find-matching-item
- (car bindings)
- (lambda (b) (string=? (car b) prefix)))))
- (if (not (false? b))
- (cdr b)
- (find (cdr bindings))))))))
-
-;
-; Resolve qualified name QNAME to (VALUES LOCAL NSURI) where LOCAL is
-; the local (unqualified) component of QNAME and NSURI is the
-; associated namespace URI or '() if there is no associated namepsace
-; URI, where IS-ATTRIBUTE? indicates whether the QNAME is the name of
-; an attribute or an element.
-;
-; N.B. the lack of a namespace URI is permitted only for unqualified
-; attribute names; all element names must have an associated namespace URI
-; or an error is signaled. This implies that there must exist a binding for
-; the empty (null) namespace prefix when resolving unqualified element
-; names.
-;
-(define (rxi-bindings/resolve bindings qname is-attribute?)
- (let* ((i (string-find-next-char qname #\:))
- (pfx (substring qname 0 (if (false? i) 0 i)))
- (local (string-tail qname (if (false? i) 0 (+ i 1)))))
- (values
- local
- (if (or (> (string-length pfx) 0) (not is-attribute?))
- (let ((uri (rxi-bindings/lookup bindings pfx)))
- (or uri
- (error "unbound XMLNS prefix on prefix" pfx)))
- '()))))
-
-;
-; An RXI-NAME structure represents the name and namespace properties of a
-; reduced XML infoset element or attribute information item and consists of
-; a local name LOCAL and an associated namespace NAMESPACE, a non-empty
-; string or '(), denoting that the name is not namespace qualified. An
-; RXI-NAME is essentially a representation of an XMLNS "expanded name".
-;
-(define-structure
- (rxi-name (conc-name rxi-name/))
- (local "" read-only #t)
- (namespace '() read-only #t))
-
-;
-; Convert an RXI-NAME instance NAME to a list consisting of its constituent
-; slots.
-;
-(define (rxi-name->list name)
- (list (rxi-name/local name)
- (rxi-name/namespace name)))
-
-;
-; Transform an XML name IQNAME as defined by the XML package as an uninterned
-; symbol to an RXI-NAME, resolving qualified names into their XMLNS
-; "expanded name" form, where IS-ATTRIBUTE? indicates whether the QNAME is
-; the name of an attribute or an element.
-;
-(define (rxi-name/transform-from-xml iqname is-attribute? bindings)
- (call-with-values
- (lambda ()
- (rxi-bindings/resolve bindings (symbol-name iqname) is-attribute?))
- make-rxi-name))
-
-;
-; An RXI-ATTRIBUTE structure represents a reduced XML infoset attribute
-; information item and consists of a NAME represented as an RXI-NAME
-; instance and a VALUE represented as a string.
-;
-(define-structure
- (rxi-attribute (conc-name rxi-attribute/))
- (name '() read-only #t)
- (value "" read-only #t))
-
-;
-; Convert an RXI-ATTRIBUTE instance ATTRIBUTE to a list consisting of its
-; constituent slots.
-;
-(define (rxi-attribute->list attribute)
- (list (rxi-name->list (rxi-attribute/name attribute))
- (rxi-attribute/value attribute)))
-
-;
-; Transform XML-ATTRIBUTE instance ATTRIBUTE to RXI-ATTRIBUTE instance,
-; where BINDINGS is the current bindings stack.
-;
-(define (rxi-attribute/transform-from-xml attribute bindings)
- (let ((n (car attribute)) (v (cdr attribute)))
- (make-rxi-attribute (rxi-name/transform-from-xml n #t bindings) v)))
-
-;
-; An RXI-ELEMENT structure represents a reduced XML infoset element
-; information item and consists of a NAME represented as an RXI-NAME
-; instance, a possibly empty set of ATTRIBUTES represented as a list of
-; RXI-ATTRIBUTE instances, and a possibly empty set of CHILDREN represented
-; as a list of string or RXI-ELEMENT instances.
-;
-(define-structure
- (rxi-element (conc-name rxi-element/))
- (name "" read-only #t)
- (attributes '() read-only #f)
- (children '() read-only #f))
-
-;
-; Convert an RXI-ELEMENT instance ELEMENT to a list consisting of its
-; constituent slots.
-;
-(define (rxi-element->list element)
- (list (rxi-name->list (rxi-element/name element))
- (map
- rxi-attribute->list
- (rxi-element/attributes element))
- (map
- (lambda (c)
- (if (string? c)
- c
- (rxi-element->list c)))
- (rxi-element/children element))))
-
-;
-; Determine if XML-ATTRIBUTE instance ATTRIBUTE, represented as a pair
-; (NAME . VALUE), is an XMLNS attribute or not, i.e., has a qualified name
-; whose prefix is "xmlns" or is the unqualified name "xmlns".
-;
-(define (namespace-attribute? attribute)
- (let ((qname (symbol-name (car attribute))))
- (and (string-prefix? "xmlns" qname)
- (or (= (string-length qname) 5)
- (let ((i (string-find-next-char qname #\:)))
- (and (not (false? i)) (= i 5)))))))
-
-;
-; Given a list ATTRIBUTES of XML-ATTRIBUTE instances consisting only of
-; XMLNS attributes as determined by NAMESPACE-ATTRIBUTE? above, return a set
-; of bindings as an association list whose keys are namespace prefixes and
-; whose values are the associated namespace URIs.
-;
-(define (extract-namespace-bindings attributes)
- (map
- (lambda (a)
- (let ((qname (symbol-name (car a))))
- (if (= (string-match-forward qname "xmlns") 5)
- (cons
- (if (>= (string-length qname) 6)
- (string-tail qname 6)
- "")
- (cdr a))
- (error "Invalid namespace attribute" qname))))
- attributes))
-
-;
-; Transform XML-ELEMENT instance ELEMENT to RXI-ELEMENT instance,
-; where BINDINGS is the current bindings stack.
-;
-(define (rxi-element/transform-from-xml element bindings)
- (let* ((attributes
- (xml-element-attributes element))
- (ns-attributes
- (keep-matching-items attributes namespace-attribute?))
- (other-attributes
- (keep-matching-items
- attributes
- (lambda (a) (not (namespace-attribute? a))))))
- (rxi-bindings/push! bindings (extract-namespace-bindings ns-attributes))
- (let ((rxi-element
- (make-rxi-element
- (rxi-name/transform-from-xml
- (xml-element-name element) #f bindings)
- (map
- (lambda (a) (rxi-attribute/transform-from-xml a bindings))
- other-attributes)
- (map
- (lambda (c)
- (if (string? c)
- c
- (rxi-element/transform-from-xml c bindings)))
- (xml-element-contents element)))))
- (rxi-bindings/pop! bindings)
- rxi-element)))
-
-;
-; An RXI-DOCUMENT structure represents a reduced XML infoset document
-; information item and consists of an ANNOTATIONS association list, used for
-; internal book-keeping purposes, and an RXI-ELEMENT instance representing
-; the document's root element or '() if there is no root element.
-;
-(define-structure
- (rxi-document (conc-name rxi-document/))
- (annotations '() read-only #f)
- (root '() read-only #f))
-
-;
-; Look up value of annotation named KEY on RXI-DOCUMENT instance DOCUMENT.
-;
-(define (rxi-document/annotation document key)
- (assq key (rxi-document/annotations document)))
-
-;
-; Add annotation (KEY . VALUE) to RXI-DOCUMENT instance DOCUMENT.
-;
-(define (set-rxi-document/annotation! document key value)
- (set-rxi-document/annotations! document (cons (cons key value) (rxi-document/annotations document))))
-
-;
-; Remove all annotations named KEY from RXI-DOCUMENT instance DOCUMENT.
-;
-(define (rxi-document/remove-annotation! document key)
- (del-assq! key (rxi-document/annotations document)))
-
-;
-; Convert an RXI-DOCUMENT instance DOCUMENT to a list consisting of its
-; constituent slots.
-;
-(define (rxi-document->list document)
- (list (rxi-document/annotations document)
- (rxi-element->list (rxi-document/root document))))
-
-;
-; Transform XML-DOCUMENT instance DOCUMENT to RXI-DOCUMENT instance.
-;
-(define (rxi-document/transform-from-xml document)
- (let
- ((bindings
- (make-rxi-bindings
- (list (list (cons (cdr *xml-default-reverse-binding*)
- (car *xml-default-reverse-binding*)))))))
- (make-rxi-document
- '()
- (rxi-element/transform-from-xml (xml-document-root document) bindings))))
-
-;
-; Load XML document instance from PATHNAME using XML package's XML parser,
-; then transform resulting XML-DOCUMENT instance to an RXI-DOCUMENT
-; instance.
-;
-(define (rxi-document/load pathname)
- (rxi-document/transform-from-xml
- (call-with-input-file pathname
- (lambda (port)
- (parse-xml-document (input-port->parser-buffer port))))))
-
-;
-; An RXI-REVERSE-BINDINGS structure consists of a REVERSE-BINDINGS slot
-; that contains an association list whose keys are XMLNS namespace URIs and
-; whose values are XMLNS name prefixes. The URI component of a reverse
-; binding entry MUST be a non-empty string.
-;
-(define-structure
- (rxi-reverse-bindings
- (conc-name rxi-reverse-bindings/)
- (constructor make-rxi-reverse-bindings (#!optional reverse-bindings)))
- (reverse-bindings '() read-only #f))
-
-(define (rxi-reverse-bindings/lookup reverse-bindings uri)
- (if (and (string? uri)
- (not (string-null? uri)))
- (let find
- ((rb (rxi-reverse-bindings/reverse-bindings reverse-bindings)))
- (cond ((null? rb)
- '())
- (else
- (let
- ((b (car rb)))
- (if (string=? (car b) uri)
- (cdr b)
- (find (cdr rb)))))))
- (error "non-string or empty XMLNS namespace URI" uri)))
-
-(define (rxi-reverse-bindings/generate-prefix reverse-bindings)
- (let ((g (lambda () (string-downcase (symbol-name (generate-uninterned-symbol)))))
- (rb (rxi-reverse-bindings/reverse-bindings reverse-bindings)))
- (let loop
- ((pfx '()))
- (cond ((null? pfx)
- (loop (g)))
- (else
- (if (not (find-matching-item
- rb
- (lambda (b)
- (and (string? (cdr b)) (string=? (cdr b) pfx)))))
- pfx
- (loop (g))))))))
-
-(define (rxi-reverse-bindings/add! reverse-bindings uri pfx)
- (set-rxi-reverse-bindings/reverse-bindings!
- reverse-bindings
- (cons (cons uri pfx) (rxi-reverse-bindings/reverse-bindings reverse-bindings))))
-
-(define (rxi-reverse-bindings/sort! reverse-bindings)
- (let
- ((rb (rxi-reverse-bindings/reverse-bindings reverse-bindings)))
- (set-rxi-reverse-bindings/reverse-bindings!
- reverse-bindings
- (sort rb
- (lambda (x y)
- (string<? (cdr x) (cdr y)))))))
-
-(define (rxi-reverse-bindings/normalize-preferred preferred-reverse-bindings)
- (let ((rbt (make-string-hash-table (length preferred-reverse-bindings)))
- (xrb *xml-default-reverse-binding*))
- (let loop
- ((prb preferred-reverse-bindings))
- (cond ((null? prb)
- (if (not (hash-table/get rbt (car xrb) #f))
- (hash-table/put! rbt (car xrb) (cdr xrb)))
- (hash-table->alist rbt))
- (else
- (let ((b (car prb)))
- (if (not (pair? b))
- (error "preferred reverse binding not a pair" b)
- (let ((u (car b))
- (p (cdr b)))
- (if (not (hash-table/get rbt u #f))
- (hash-table/put! rbt u p))
- (loop (cdr prb))))))))))
-
-;
-; Transform an RXI-NAME instance NAME to an XML name IQNAME as defined by the
-; XML package as an uninterned symbol, where IS-ATTRIBUTE? indicates whether
-; the IQNAME is the name of an attribute or an element, and where REVERSE-BINDINGS
-; is the current reverse bindings.
-;
-(define (rxi-name/transform-to-xml name is-attribute? reverse-bindings)
- (let ((uri (rxi-name/namespace name))
- (loc (rxi-name/local name)))
- (xml-intern
- (if (null? uri)
- loc
- (let ((pfx (rxi-reverse-bindings/lookup reverse-bindings uri)))
- (if (string-null? pfx)
- loc
- (string-append
- pfx
- (string-append ":" loc))))))))
-
-;
-; Transform RXI-ATTRIBUTE instance ATTRIBUTE to XML-ATTRIBUTE instance.
-;
-(define (rxi-attribute/transform-to-xml attribute reverse-bindings)
- (cons
- (rxi-name/transform-to-xml (rxi-attribute/name attribute) #t reverse-bindings)
- (rxi-attribute/value attribute)))
-
-(define (maybe-add-reverse-binding! reverse-bindings name)
- (let ((uri (rxi-name/namespace name)))
- (if (not (null? uri))
- (if (not (rxi-reverse-bindings/lookup reverse-bindings uri))
- (rxi-reverse-bindings/add! reverse-bindings uri (rxi-reverse-bindings/generate-prefix reverse-bindings))))))
-
-(define (rxi-element/collect-reverse-bindings element reverse-bindings)
- ;; collect element's binding
- (maybe-add-reverse-binding! reverse-bindings (rxi-element/name element))
- ;; collect attribute reverse-bindings
- (let ((attributes (rxi-element/attributes element)))
- (for-each
- (lambda (a)
- (maybe-add-reverse-binding! reverse-bindings (rxi-attribute/name a)))
- attributes))
- ;; collect childrens' reverse bindings
- (let ((children (rxi-element/children element)))
- (for-each
- (lambda (c)
- (if (not (string? c))
- (rxi-element/collect-reverse-bindings c reverse-bindings)))
- children)))
-
-;
-; Transform RXI-ELEMENT instance ELEMENT to XML-ELEMENT instance.
-;
-(define (rxi-element/transform-to-xml element reverse-bindings)
- (make-xml-element
- (rxi-name/transform-to-xml (rxi-element/name element) #f reverse-bindings)
- (map
- (lambda (a)
- (rxi-attribute/transform-to-xml a reverse-bindings))
- (rxi-element/attributes element))
- (map
- (lambda (c)
- (if (string? c)
- c
- (rxi-element/transform-to-xml c reverse-bindings)))
- (rxi-element/children element))))
-
-;
-; Add XMLNS attributes that correspond with REVERSE-BINDINGS to the root
-; element of XML-DOCUMENT instance DOCUMENT. If DOCUMENT has no root
-; element, then do nothing.
-;
-(define (xml-document-add-bindings! document reverse-bindings)
- (let ((root (xml-document-root document)))
- (if (not (null? root))
- (set-xml-element-attributes!
- root
- (append
- (xml-element-attributes root)
- (map
- (lambda (b)
- (let*
- ((prefix (cdr b))
- (ns-attr-name
- (if (string-null? prefix)
- "xmlns"
- (string-append "xmlns:" prefix))))
- (cons (xml-intern ns-attr-name) (car b))))
- (rxi-reverse-bindings/reverse-bindings reverse-bindings)))))))
-
-;
-; Collect
-;
-(define (rxi-document/collect-reverse-bindings document reverse-bindings)
- (let ((root (rxi-document/root document)))
- (if (not (null? root))
- (rxi-element/collect-reverse-bindings root reverse-bindings))
- (rxi-reverse-bindings/sort! reverse-bindings)
- reverse-bindings))
-
-;
-; Transform RXI-DOCUMENT instance DOCUMENT to XML-DOCUMENT instance.
-;
-(define (rxi-document/transform-to-xml document preferred-reverse-bindings)
- (let
- ((reverse-bindings
- (make-rxi-reverse-bindings
- (rxi-reverse-bindings/normalize-preferred preferred-reverse-bindings))))
- (rxi-document/collect-reverse-bindings document reverse-bindings)
- (let
- ((xml-document
- (make-xml-document
- '() ; declaration
- '() ; misc-1
- '() ; dtd
- '() ; misc-2
- (rxi-element/transform-to-xml
- (rxi-document/root document) reverse-bindings)
- '()))) ; misc-3
- (xml-document-add-bindings! xml-document reverse-bindings)
- xml-document)))
-
-;
-; Save RXI-DOCUMENT instance DOCUMENT by transforming to an XML-DOCUMENT
-; instance and serializing to PATHNAME using XML package's document serializer,
-; where optional argument PREFERRED-REVERSE-BINDINGS, if specified, consists
-; of an association list whose keys are namespace URIs and values are the
-; preferred namespace prefixes to use to designate those namespaces.
-;
-; If a namepsace URI appears in DOCUMENT and it has no preferred binding
-; specified, then a prefix is generated unless the namespace URI is
-; "http://www.w3.org/XML/1998/namespace", in which case the prefix "xml" is
-; used.
-;
-(define (rxi-document/save document pathname #!optional preferred-reverse-bindings)
- (let
- ((xml-document
- (rxi-document/transform-to-xml
- document
- (if (default-object? preferred-reverse-bindings)
- '()
- preferred-reverse-bindings))))
- (call-with-output-file pathname
- (lambda (port)
- (write-xml xml-document port)))))
-</pre></div></div><div class="div2">
-<h3><a name="code-adi" id="code-adi"/>I.2 Abstract Document Instance (ADI) – <code>ADI.SCM</code></h3><div class="exampleInner"><pre>;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi)
-
-;
-; DFXP Abstrarct Document Instance Load, Save, Transformer
-;
-
-(declare (usual-integrations))
-
-(define *dfxp-preferred-reverse-bindings*
- '(("http://www.w3.org/2006/10/ttaf1" . "")
- ("http://www.w3.org/2006/10/ttaf1#parameter" . "ttp")
- ("http://www.w3.org/2006/10/ttaf1#style" . "tts")
- ("http://www.w3.org/2006/10/ttaf1#style-extension" . "ttsx")
- ("http://www.w3.org/2006/10/ttaf1#metadata" . "ttm")
- ("http://www.w3.org/2006/10/ttaf1#metadata-extension" . "ttmx")))
-
-(define *dfxp-namespaces-table*
- (let ((t (make-string-hash-table)))
- (for-each
- (lambda (b)
- (hash-table/put! t (car b) #t))
- *dfxp-preferred-reverse-bindings*)
- t))
-
-(define *dfxp-empty-element-types*
- '(("br" . "http://www.w3.org/2006/10/ttaf1")
- ("metadata" . "http://www.w3.org/2006/10/ttaf1")))
-
-(define (in-per-element-namespace? attr)
- (let* ((name (rxi-attribute/name attr))
- (namespace (rxi-name/namespace name)))
- (null? namespace)))
-
-(define (in-dfxp-namespace? name)
- (hash-table/get *dfxp-namespaces-table* (rxi-name/namespace name) #f))
-
-(define (in-xml-namespace? name)
- (string=? (rxi-name/namespace name) (car *xml-default-reverse-binding*)))
-
-(define (in-dfxp-or-xml-namespace? name)
- (or (in-dfxp-namespace? name)
- (in-xml-namespace? name)))
-
-(define (empty-dfxp-element-type? elt)
- (let* ((name (rxi-element/name elt))
- (local (rxi-name/local name))
- (namespace (rxi-name/namespace name)))
- (find-matching-item
- *dfxp-empty-element-types*
- (lambda (n)
- (and (string=? local (car n))
- (string=? namespace (cdr n)))))))
-
-(define (only-whitespace-children? elt)
- (let ((children (rxi-element/children elt)))
- (not
- (find-matching-item
- children
- (lambda (c)
- (or (not (string? c))
- (string-find-next-char-in-set c char-set:not-whitespace)))))))
-
-(define (rxi-document/adi-transform-element elt)
- ;; prune and transform children
- (set-rxi-element/children!
- elt
- (delete-matching-items
- (map
- (lambda (c)
- (if (string? c)
- c
- (if (not (in-dfxp-namespace? (rxi-element/name c)))
- '()
- (rxi-document/adi-transform-element c))))
- (rxi-element/children elt))
- null?))
- ;; prune remaining children if empty element type and only whitespace remains
- (if (and (empty-dfxp-element-type? elt)
- (only-whitespace-children? elt))
- (set-rxi-element/children! elt '()))
- ;; prune foreign namespace attributes
- (set-rxi-element/attributes!
- elt
- (delete-matching-items
- (rxi-element/attributes elt)
- (lambda (a)
- (not (or (in-per-element-namespace? a)
- (in-dfxp-or-xml-namespace? (rxi-attribute/name a)))))))
- elt)
-
-(define (rxi-document/adi-transform document)
- (if (not (null? (rxi-document/annotation document 'adi-transform)))
- (warn "Document already transformed, ignoring re-transform.")
- (let ((root (rxi-document/root document)))
- (set-rxi-document/root! document (rxi-document/adi-transform-element root))
- (set-rxi-document/annotation! document 'adi-transform #t)))
- document)
-
-;
-; Load TT AF document instance from PATHNAME using RXI loader,
-; then transform resulting RXI-DOCUMENT instance to an ADI-DOCUMENT
-; instance.
-;
-(define (adi-document/load pathname)
- (rxi-document/adi-transform
- (rxi-document/load pathname)))
-
-;
-; Save ADI-DOCUMENT instance DOCUMENT, which was created by ADI-DOCUMENT/LOAD,
-; to PATHNAME using underlying RXI-DOCUMENT's document serializer,
-; where optional argument OTHER-REVERSE-BINDINGS, if specified, consists
-; of an association list whose keys are namespace URIs and values are the
-; namespace prefixes to use to designate those namespaces.
-;
-; By default the set of refeverse bindings defined by *DFXP-PREFERRED-REVERSE-BINDING*
-; are used when serializaing. However, reverse bindings specified by using
-; OTHER-REVERSE-BINDINGS take precedence, overriding default reverse bindings.
-;
-(define (adi-document/save document pathname #!optional other-reverse-bindings)
- (rxi-document/save document pathname
- (if (default-object? other-reverse-bindings)
- *dfxp-preferred-reverse-bindings*
- (append other-reverse-bindings *dfxp-preferred-reverse-bindings*))))
-</pre></div></div><div class="div2">
-<h3><a name="code-tir" id="code-tir"/>I.3 Time Interval Resolver (TIR) – <code>TIR.SCM</code></h3><div class="exampleInner"><pre>;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi tir)
-
-;;;; DFXP Timing Interval Resolver
-
-(declare (usual-integrations))
-
-;
-; NOT YET IMPLEMENTED - TO BE PROVIDED PRIOR TO PROPOSED RECOMMENDATION PHASE
-;
-
-(define (adi-document/tir-transform document) document)
-</pre></div></div><div class="div2">
-<h3><a name="code-fox" id="code-fox"/>I.4 Flow Object Transformer (FOX) – <code>FOX.SCM</code></h3><div class="exampleInner"><pre>;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi tir)
-
-;;;; DFXP Timing Interval Resolver
-
-(declare (usual-integrations))
-
-;
-; NOT YET IMPLEMENTED - TO BE PROVIDED PRIOR TO PROPOSED RECOMMENDATION PHASE
-;
-
-(define (adi-document/tir-transform document) document)
-</pre></div></div><div class="div2">
-<h3><a name="code-dtf" id="code-dtf"/>I.5 Dynamic Text Flow Processor (DTF) – <code>DTF.SCM</code></h3><div class="exampleInner"><pre>;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi tir dtf)
-
-;;;; Dynamic Text Flow Processor
-
-(declare (usual-integrations))
-
-;
-; NOT YET IMPLEMENTED - TO BE PROVIDED PRIOR TO PROPOSED RECOMMENDATION PHASE
-;
-
-(define (adi-document/dtf-process document) document)
-</pre></div></div><div class="div2">
-<h3><a name="code-run" id="code-run"/>I.6 Sample Compile, Load, and Run Session</h3><p>The following transcript shows a sample compile, load, and run
-session of the sample code, where the following steps are
-performed:</p><ol class="enumar"><li><p>Start scheme using Edwin editor (included with MIT Scheme).</p></li><li><p>Change working directory to sample code directory.</p></li><li><p>Compile DFXP optional package by loading <code>compile.scm</code>.</p></li><li><p>Load DFXP optional package by loading <code>load.scm</code>.</p></li><li><p>Dump world identity to show that the just compiled, DFXP optional
-package has been loaded (MIT Scheme SOS, CREF, and XML optional packages are also
-loaded a side effect.)</p></li><li><p>Load DFXP document instance using <code>ADI-DOCUMENT/LOAD</code>
-function and save resulting <code>ADI-DOCUMENT</code> instance into variable
-<code>D</code>.</p></li><li><p>Convert loaded <code>ADI-DOCUMENT</code> into a list structure and pretty print
-this structure using <code>PP</code> environment function.</p></li><li><p>Serialize loaded <code>ADI-DOCUMENT</code> to file
-<code>out.xml</code>.</p></li><li><p>Exit scheme interpreter.</p></li></ol><p>The forms to be entered to accomplish the above tasks are depicted in boldface.</p><div class="exampleInner"><pre>
-Scheme saved on Tuesday June 18, 2002 at 12:25:05 AM
- Release 7.7.1
- Microcode 14.9
- Runtime 15.1
- Win32 1.6
- SF 4.40
- Liar (Intel i386) 4.115
- Edwin 3.112
-
-;You are in an interaction window of the Edwin editor.
-;Type C-h for help. C-h m will describe some commands.
-;Package: (user)
-
-<span class="strong">(cd "/work/dfxp/scm")</span>
-;Value 12: #[pathname 12 "c:\\work\\dfxp\\scm\\"]
-
-<span class="strong">(load "compile")</span>
-;Loading "compile.scm"
-;Loading "load.scm"
-;Loading "load.scm"
-;Loading "sos-w32.pkd" -- done
-;Loading "slot.com" -- done
-;Loading "class.com" -- done
-;Loading "instance.com" -- done
-;Loading "method.com" -- done
-;Loading "printer.com" -- done
-;Loading "macros.com" -- done
- -- done
-;Loading "xml-w32.pkd" -- done
-;Loading "xml-struct.com" -- done
-;Loading "xml-chars.com" -- done
-;Loading "xml-parser.com" -- done
-;Loading "xml-output.com" -- done
- -- done
-;Loading "make.com" -- done
-;Loading "cref-w32.pkd" -- done
-;Loading "mset.com" -- done
-;Loading "object.com" -- done
-;Loading "toplev.com" -- done
-;Loading "anfile.com" -- done
-;Loading "conpkg.com" -- done
-;Loading "forpkg.com" -- done
-;Loading "redpkg.com" -- done
-;Generating "rxi.bin" because of: "rxi.scm"
-Syntax file: "rxi.scm" "rxi.bin"
- Read...
- Time taken: .031 (process time); .031 (real time)
- Syntax...
- Time taken: .032 (process time); .031 (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
-;Warning: Unreferenced bound variable: is-attribute? (rxi-name/transform-to-xml)
- Time taken: .015 (process time); .016 (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "rxi.ext" -- done
-;Dumping "rxi.bin" -- done
-;Generating "rxi.com" because of: "rxi.bin"
-Compile File: "rxi.bin" => "rxi.com"
-;Loading "rxi.bin" -- done
- Compiling procedure: rxi-bindings/bindings...
- Compiling procedure: set-rxi-bindings/bindings!...
- Compiling procedure: rxi-bindings/push!...
- Compiling procedure: rxi-bindings/pop!...
- Compiling procedure: rxi-bindings/lookup...
- Compiling procedure: rxi-bindings/resolve...
- Compiling procedure: rxi-name/local...
- Compiling procedure: rxi-name/namespace...
- Compiling procedure: rxi-name->list...
- Compiling procedure: rxi-name/transform-from-xml...
- Compiling procedure: rxi-attribute/name...
- Compiling procedure: rxi-attribute/value...
- Compiling procedure: rxi-attribute->list...
- Compiling procedure: rxi-attribute/transform-from-xml...
- Compiling procedure: rxi-element/name...
- Compiling procedure: rxi-element/attributes...
- Compiling procedure: rxi-element/children...
- Compiling procedure: set-rxi-element/attributes!...
- Compiling procedure: set-rxi-element/children!...
- Compiling procedure: rxi-element->list...
- Compiling procedure: namespace-attribute?...
- Compiling procedure: extract-namespace-bindings...
- Compiling procedure: rxi-element/transform-from-xml...
- Compiling procedure: rxi-document/annotations...
- Compiling procedure: rxi-document/root...
- Compiling procedure: set-rxi-document/annotations!...
- Compiling procedure: set-rxi-document/root!...
- Compiling procedure: rxi-document/annotation...
- Compiling procedure: set-rxi-document/annotation!...
- Compiling procedure: rxi-document/remove-annotation!...
- Compiling procedure: rxi-document->list...
- Compiling procedure: rxi-document/transform-from-xml...
- Compiling procedure: rxi-document/load...
- Compiling procedure: rxi-reverse-bindings/reverse-bindings...
- Compiling procedure: set-rxi-reverse-bindings/reverse-bindings!...
- Compiling procedure: rxi-reverse-bindings/lookup...
- Compiling procedure: rxi-reverse-bindings/generate-prefix...
- Compiling procedure: rxi-reverse-bindings/add!...
- Compiling procedure: rxi-reverse-bindings/sort!...
- Compiling procedure: rxi-reverse-bindings/normalize-preferred...
- Compiling procedure: rxi-name/transform-to-xml...
- Compiling procedure: rxi-attribute/transform-to-xml...
- Compiling procedure: maybe-add-reverse-binding!...
- Compiling procedure: rxi-element/collect-reverse-bindings...
- Compiling procedure: rxi-element/transform-to-xml...
- Compiling procedure: xml-document-add-bindings!...
- Compiling procedure: rxi-document/collect-reverse-bindings...
- Compiling procedure: rxi-document/transform-to-xml...
- Compiling procedure: rxi-document/save...
-;"rxi.bci" dumped
-;Dumping "rxi.com" -- done
-;Generating "adi.bin" because of: "adi.scm"
-Syntax file: "adi.scm" "adi.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: .016 (process time); .015 (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "adi.bin" -- done
-;Generating "adi.com" because of: "adi.bin"
-Compile File: "adi.bin" => "adi.com"
-;Loading "adi.bin" -- done
- Compiling procedure: in-per-element-namespace?...
- Compiling procedure: in-dfxp-namespace?...
- Compiling procedure: in-xml-namespace?...
- Compiling procedure: in-dfxp-or-xml-namespace?...
- Compiling procedure: empty-dfxp-element-type?...
- Compiling procedure: only-whitespace-children?...
- Compiling procedure: rxi-document/adi-transform-element...
- Compiling procedure: rxi-document/adi-transform...
- Compiling procedure: adi-document/load...
- Compiling procedure: adi-document/save...
-;"adi.bci" dumped
-;Dumping "adi.com" -- done
-;Generating "tir.bin" because of: "tir.scm"
-Syntax file: "tir.scm" "tir.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "tir.bin" -- done
-;Generating "tir.com" because of: "tir.bin"
-Compile File: "tir.bin" => "tir.com"
-;Loading "tir.bin" -- done
- Compiling procedure: adi-document/tir-transform...
-;"tir.bci" dumped
-;Dumping "tir.com" -- done
-;Generating "fox.bin" because of: "fox.scm"
-Syntax file: "fox.scm" "fox.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "fox.bin" -- done
-;Generating "fox.com" because of: "fox.bin"
-Compile File: "fox.bin" => "fox.com"
-;Loading "fox.bin" -- done
- Compiling procedure: adi-document/fox-transform...
-;"fox.bci" dumped
-;Dumping "fox.com" -- done
-;Generating "dtf.bin" because of: "dtf.scm"
-Syntax file: "dtf.scm" "dtf.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "dtf.bin" -- done
-;Generating "dtf.com" because of: "dtf.bin"
-Compile File: "dtf.bin" => "dtf.com"
-;Loading "dtf.bin" -- done
- Compiling procedure: adi-document/dtf-process...
-;"dtf.bci" dumped
-;Dumping "dtf.com" -- done
-;Loading "dtf.bin" -- done
-;Loading "fox.bin" -- done
-;Loading "tir.bin" -- done
-;Loading "adi.bin" -- done
-;Loading "rxi.bin" -- done
-;Dumping "dfxp-w32.fre" -- done
-;Dumping "dfxp-w32.pkd" -- done
- -- done
-;Unspecified return value
-
-<span class="strong">(load "load")</span>
-;Loading "load.scm"
-;Loading "dfxp-w32.pkd" -- done
-;Loading "rxi.com" -- done
-;Loading "adi.com" -- done
-;Loading "tir.com" -- done
-;Loading "fox.com" -- done
-;Loading "dtf.com" -- done
- -- done
-;Unspecified return value
-
-<span class="strong">(identify-world)</span>
-Scheme saved on Tuesday June 18, 2002 at 12:25:05 AM
- Release 7.7.1
- Microcode 14.9
- Runtime 15.1
- Win32 1.6
- SF 4.40
- Liar (Intel i386) 4.115
- Edwin 3.112
- SOS 1.7
- XML 0.2
- CREF 2.3
- DFXP 0.8
-;Unspecified return value
-
-<span class="strong">(define d (adi-document/load "test.xml"))</span>
-;Value: d
-
-<span class="strong">(pp (rxi-document->list d))</span>
-(((adi-transform . #t))
- (("tt" "http://www.w3.org/2006/10/ttaf1")
- ((("profile" "http://www.w3.org/2006/10/ttaf1#parameter")
- "http://www.w3.org/2006/10/ttaf1#profile-dfxp")
- (("lang" "http://www.w3.org/XML/1998/namespace") "en"))
- ("\n "
- (("head" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("metadata" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("title" "http://www.w3.org/2006/10/ttaf1#metadata") () ("Timed Text DFXP Example"))
- "\n "
- (("copyright" "http://www.w3.org/2006/10/ttaf1#metadata") () ("The Authors (c) 2006"))
- "\n "))
- "\n "
- (("styling" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s1")
- (("color" "http://www.w3.org/2006/10/ttaf1#style") "white")
- (("fontFamily" "http://www.w3.org/2006/10/ttaf1#style") "proportionalSansSerif")
- (("fontSize" "http://www.w3.org/2006/10/ttaf1#style") "22px")
- (("textAlign" "http://www.w3.org/2006/10/ttaf1#style") "center"))
- ())
- "\n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s2") (("style" ()) "s1")
- (("color" "http://www.w3.org/2006/10/ttaf1#style") "yellow"))
- ())
- "\n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s1Right") (("style" ()) "s1")
- (("textAlign" "http://www.w3.org/2006/10/ttaf1#style") "end"))
- ())
- " \n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s2Left") (("style" ()) "s2")
- (("textAlign" "http://www.w3.org/2006/10/ttaf1#style") "start"))
- ())
- "\n "))
- "\n "
- (("layout" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("region" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitleArea")
- (("style" ()) "s1")
- (("extent" "http://www.w3.org/2006/10/ttaf1#style") "560px 62px")
- (("padding" "http://www.w3.org/2006/10/ttaf1#style") "5px 3px")
- (("backgroundColor" "http://www.w3.org/2006/10/ttaf1#style") "black")
- (("displayAlign" "http://www.w3.org/2006/10/ttaf1#style") "after"))
- ())
- "\n "))
- " \n "))
- "\n "
- (("body" "http://www.w3.org/2006/10/ttaf1")
- ((("region" ()) "subtitleArea"))
- ("\n "
- (("div" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle1") (("begin" ()) "0.76s") (("end" ()) "3.45s"))
- ("\n It seems a paradox, does it not,\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle2") (("begin" ()) "5.0s") (("end" ()) "10.0s"))
- ("\n that the image formed on" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n the Retina should be inverted?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle3") (("begin" ()) "10.0s") (("end" ()) "16.0s") (("style" ()) "s2"))
- ("\n It is puzzling, why is it" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n we do not see things upside-down?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle4") (("begin" ()) "17.2s") (("end" ()) "23.0s"))
- ("\n You have never heard the Theory,"
- (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n then, that the Brain also is inverted?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle5") (("begin" ()) "23.0s") (("end" ()) "27.0s") (("style" ()) "s2"))
- ("\n No indeed! What a beautiful fact!\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle6a") (("begin" ()) "28.0s") (("end" ()) "34.6s") (("style" ()) "s2Left"))
- ("\n But how is it proved?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle6b") (("begin" ()) "28.0s") (("end" ()) "34.6s") (("style" ()) "s1Right"))
- ("\n Thus: what we call\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle7") (("begin" ()) "34.6s") (("end" ()) "45.0s") (("style" ()) "s1Right"))
- ("\n the vertex of the Brain" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n is really its base\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle8") (("begin" ()) "45.0s") (("end" ()) "52.0s") (("style" ()) "s1Right"))
- ("\n and what we call its base" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n is really its vertex,\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle9a") (("begin" ()) "53.5s") (("end" ()) "58.7s"))
- ("\n it is simply a question of nomenclature.\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle9b") (("begin" ()) "53.5s") (("end" ()) "58.7s") (("style" ()) "s2"))
- ("\n How truly delightful!\n "))
- "\n "))
- " \n "))
- "\n")))
-;Unspecified return value
-
-<span class="strong">(adi-document/save d "out.xml")</span>
-;Unspecified return value
-
-<span class="strong">(exit)</span>
-</pre></div></div></div><div class="div1">
<h2><a name="requirements" id="requirements"/>J Requirements (Non-Normative)</h2><p>The Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring
Format (TT AF) satisfies a subset of the requirements established by
<a href="#ttaf1-req">[TTAF1-REQ]</a>. The following table enumerates these requirements and
@@ -9006,7 +8975,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="d3e18480" id="d3e18480"/>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="d3e19680" id="d3e19680"/>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
@@ -9044,7 +9013,7 @@
name and value, with optional inclusion of other styles by reference
to other style elements</td><td>7</td></tr><tr><td><a href="#styling-vocabulary-styling"><code>tt:styling</code></a></td><td><code>xhtml:style</code></td><td><a href="#xhtml10">[XHTML 1.0]</a></td><td>XML representation of a set of style specifications sets, each
represented by a style child element</td><td>1,7</td></tr><tr><td><a href="#document-structure-vocabulary-tt"><code>tt:tt</code></a></td><td><code>xhtml:html</code></td><td><a href="#xhtml10">[XHTML 1.0]</a></td><td>-@dir, -@lang; +@id, +@ttp:*, +@xml:space; content model subsetted by
-permitting body and/or head to be optional</td><td>1,8</td></tr><tr><td><a href="#metadata-vocabulary-actor"><code>ttm:actor</code></a></td><td><code>mpeg7:Creator</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-agent"><code>ttm:agent</code></a></td><td><code>mpeg7:Agent</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-copyright"><code>ttm:copyright</code></a></td><td><code>mpeg7:CopyrightString</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-desc"><code>ttm:desc</code></a></td><td><code>svg:desc</code></td><td><a href="#svg11">[SVG 1.1]</a></td><td>-@class, -@style, -@xml:base</td><td>2,5,9</td></tr><tr><td><a href="#metadata-vocabulary-name"><code>ttm:name</code></a></td><td><code>mpeg7:Name</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-title"><code>ttm:title</code></a></td><td><code>svg:title</code></td><td><a href="#svg11">[SVG 1.1]</a></td><td>-@class, -@style, -@xml:base</td><td>2,5,9</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Derivation is indicated with respect to the strict DTD defined
+permitting body and/or head to be optional</td><td>1,8</td></tr><tr><td><a href="#metadata-vocabulary-actor"><code>ttm:actor</code></a></td><td><code>mpeg7:Creator</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-agent"><code>ttm:agent</code></a></td><td><code>mpeg7:Agent</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-copyright"><code>ttm:copyright</code></a></td><td><code>mpeg7:CopyrightString</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-desc"><code>ttm:desc</code></a></td><td><code>svg:desc</code></td><td><a href="#svg11">[SVG 1.1]</a></td><td>-@class, -@style, -@xml:base</td><td>2,5,9</td></tr><tr><td><a href="#metadata-vocabulary-name"><code>ttm:name</code></a></td><td><code>mpeg7:Name</code></td><td><a href="#mpeg7-5">[MPEG7-5]</a></td><td>conceptual derivation</td><td>4</td></tr><tr><td><a href="#metadata-vocabulary-title"><code>ttm:title</code></a></td><td><code>svg:title</code></td><td><a href="#svg11">[SVG 1.1]</a></td><td>-@class, -@style, -@xml:base</td><td>2,5,9</td></tr><tr><td><span class="diff-add"><a href="#parameter-vocabulary-extension"><code>ttp:extension</code></a></span></td><td><span class="diff-add"><code>@requiredExtensions</code></span></td><td><span class="diff-add"><a href="#svg11">[SVG 1.1]</a></span></td><td><span class="diff-add">conceptual derivation</span></td><td><span class="diff-add">10</span></td></tr><tr><td><span class="diff-add"><a href="#parameter-vocabulary-extensions"><code>ttp:extensions</code></a></span></td><td><span class="diff-add"><code>@requiredExtensions</code></span></td><td><span class="diff-add"><a href="#svg11">[SVG 1.1]</a></span></td><td><span class="diff-add">conceptual derivation</span></td><td><span class="diff-add">10</span></td></tr><tr><td><span class="diff-add"><a href="#parameter-vocabulary-feature"><code>ttp:feature</code></a></span></td><td><span class="diff-add"><code>@requiredFeatures</code></span></td><td><span class="diff-add"><a href="#svg11">[SVG 1.1]</a></span></td><td><span class="diff-add">conceptual derivation</span></td><td><span class="diff-add">10</span></td></tr><tr><td><span class="diff-add"><a href="#parameter-vocabulary-features"><code>ttp:features</code></a></span></td><td><span class="diff-add"><code>@requiredFeatures</code></span></td><td><span class="diff-add"><a href="#svg11">[SVG 1.1]</a></span></td><td><span class="diff-add">conceptual derivation</span></td><td><span class="diff-add">10</span></td></tr><tr><td><span class="diff-add"><a href="#parameter-vocabulary-profile"><code>ttp:profile</code></a></span></td><td><span class="diff-add"><code>@baseProfile</code></span></td><td><span class="diff-add"><a href="#svg11">[SVG 1.1]</a></span></td><td><span class="diff-add">conceptual derivation</span></td><td><span class="diff-add">11</span></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Derivation is indicated with respect to the strict DTD defined
by <a href="#xhtml10">[XHTML 1.0]</a>, §A.1.</p></li><li><p>The <code>class</code> attribute is effectively replaced by the
<code>style</code>
attribute, which, instead of specifying an inline style,
@@ -9057,8 +9026,11 @@
direct expression of the target attribute name and value by use of a
<code>tts:*</code> attribute.</p></li><li><p>CSS style specification syntax is mapped to XML by use of
attributes defined in the TT Style Namespace.</p></li><li><p>The <code>xml:id</code> attribute is defined for use on all element types.</p></li><li><p>The <code>style</code> attribute is supported only on content
-elements.</p></li></ol></div></div><div class="div2">
-<h3><a name="d3e18864" id="d3e18864"/>K.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table K-2 – Attributes</b></a>
+elements.</p></li><li><p class="diff-add">Derived from the use of <code>@requiredExtensions</code>
+and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
+but extended to support distinct specification of optionality.</p></li><li><p class="diff-add">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="d3e20184" id="d3e20184"/>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
@@ -9079,7 +9051,7 @@
that are uniquely defined for a specific TT AF element type are not
listed below, but are considered to be part of the specific element
type's derivation described in <a href="#element-vocab-derivation-table"><b>Table K-1 – Elements</b></a>
-above.</p><table summary="HTML Table" id="attribute-vocab-derivation-table" class="common"><caption>Table K-2 – Attributes</caption><col width="20%" span="1"/><col width="17%" span="1"/><col width="13%" align="center" span="1"/><col width="40%" span="1"/><col width="10%" align="center" span="1"/><tbody><tr><td><span class="strong">Attribute</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#timing-attribute-begin"><code>begin</code></a></td><td><code>begin</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-dur"><code>dur</code></a></td><td><code>dur</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-end"><code>end</code></a></td><td><code>end</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#layout-attribute-region"><code>region</code></a></td><td><code>master-reference</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>conceptual derivation</td><td/></tr><tr><td><a href="#style-attribute-style"><code>style</code></a></td><td><code>class</code></td><td><a href="#css2">[CSS2]</a></td><td>dereferences style specification(s) directly</td><td/></tr><tr><td><a href="#timing-attribute-timeContainer"><code>timeContainer</code></a></td><td><code>timeContainer</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>-excl, -none; no default attribute value</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td/><td>used to attribute agent of content</td><td/></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td/><td>used to attribute role of content</td><td/></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td/><td>expresses uniform grid resolution for cell based coordinates</td><td/></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td/><td>determines how to interpret time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td/><td>expresses integral frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td/><td>used to express non-integral, rational frame rates</td><td/></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td/><td>expresses marker continuity semantics</td><td/></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td/><td>expresses pixel aspect ratio of related media</td><td/></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td/><td>expresses profile of TT AF used by document instance</td><td/></tr><tr><td><a href="#parameter-attribute-smpteMode"><code>ttp:smpteMode</code></a></td><td><em>none</em></td><td/><td>expresses frame counting (drop) modes</td><td/></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td/><td>expresses sub-frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td/><td>used to interpret tick based time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td/><td>used to interpret semantics of time expressions</td><td/></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>see notes</td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>initial value specified as <code>transparent</code></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>complies with model</td><td/></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only auto, none, inherit</td><td/></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>except for name normalization, complies with model</td><td>1</td></tr><tr><td><a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a></td><td><em>none</em></td><td/><td>defines <span class="diff-chg">dynamic</span> overflow behavior</td><td/></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td/></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>see notes</td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a></td><td><code>font-style</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>uses alias <code>reverseOblique</code> for <code>backslant</code></td><td>1</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-bolder, -lighter, -<number></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-<number>, -<space></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td>complies with model</td><td/></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td/></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-auto, -error-if-overflow; <span class="diff-chg">dynamic added</span></td><td>8</td></tr><tr><td><a href="#style-attribute-padding"><code>tts:padding</code></a></td><td><code>padding</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>see notes</td><td>9</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>complies with model</td></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>except for name normalization, complies with model</td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>except for name normalization, complies with model</td><td>1,10</td></tr><tr><td><a href="#style-attribute-textOutline"><code>tts:textOutline</code></a></td><td><code>text-shadow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>see notes</td><td>11</td></tr><tr><td><a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a></td><td><code>unicode-bidi</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>except for name normalization, complies with model</td><td>1</td></tr><tr><td><a href="#style-attribute-visibility"><code>tts:visibility</code></a></td><td><code>visibility</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>-collapse</td><td/></tr><tr><td><a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a></td><td><code>wrap-option</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>except for name normalization, complies with model</td><td>1</td></tr><tr><td><a href="#style-attribute-writingMode"><code>tts:writingMode</code></a></td><td><code>writing-mode</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>+tblr</td><td>1</td></tr><tr><td><a href="#style-attribute-zIndex"><code>tts:zIndex</code></a></td><td><code>z-index</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>except for name normalization, complies with model</td><td>1</td></tr><tr><td><a href="#content-attribute-id"><code>xml:id</code></a></td><td><code>xml:id</code></td><td><a href="#xmlid">[XML ID]</a></td><td>complies with model</td><td/></tr><tr><td><a href="#content-attribute-lang"><code>xml:lang</code></a></td><td><code>xml:lang</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>complies with model</td><td/></tr><tr><td><a href="#content-attribute-space"><code>xml:space</code></a></td><td><code>xml:space</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>see notes</td><td>12</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Attribute name and/or value(s) are normalized to use
+above.</p><table summary="HTML Table" id="attribute-vocab-derivation-table" class="common"><caption>Table K-2 – Attributes</caption><col width="20%" span="1"/><col width="17%" span="1"/><col width="13%" align="center" span="1"/><col width="40%" span="1"/><col width="10%" align="center" span="1"/><tbody><tr><td><span class="strong">Attribute</span></td><td><span class="strong">Model</span></td><td><span class="strong">Reference</span></td><td><span class="strong">Details</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="#timing-attribute-begin"><code>begin</code></a></td><td><code>begin</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-dur"><code>dur</code></a></td><td><code>dur</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#timing-attribute-end"><code>end</code></a></td><td><code>end</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>see notes</td><td>2,3,4</td></tr><tr><td><a href="#layout-attribute-region"><code>region</code></a></td><td><code>master-reference</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>conceptual derivation</td><td/></tr><tr><td><a href="#style-attribute-style"><code>style</code></a></td><td><code>class</code></td><td><a href="#css2">[CSS2]</a></td><td>dereferences style specification(s) directly</td><td/></tr><tr><td><a href="#timing-attribute-timeContainer"><code>timeContainer</code></a></td><td><code>timeContainer</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td>-excl, -none; no default attribute value</td><td>5</td></tr><tr><td><a href="#metadata-attribute-agent"><code>ttm:agent</code></a></td><td><em>none</em></td><td/><td>used to attribute agent of content</td><td/></tr><tr><td><a href="#metadata-attribute-role"><code>ttm:role</code></a></td><td><em>none</em></td><td/><td>used to attribute role of content</td><td/></tr><tr><td><a href="#parameter-attribute-cellResolution"><code>ttp:cellResolution</code></a></td><td><em>none</em></td><td/><td>expresses uniform grid resolution for cell based coordinates</td><td/></tr><tr><td><a href="#parameter-attribute-clockMode"><code>ttp:clockMode</code></a></td><td><em>none</em></td><td/><td>determines how to interpret time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-frameRate"><code>ttp:frameRate</code></a></td><td><em>none</em></td><td/><td>expresses integral frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-frameRateMultiplier"><code>ttp:frameRateMultiplier</code></a></td><td><em>none</em></td><td/><td>used to express non-integral, rational frame rates</td><td/></tr><tr><td><a href="#parameter-attribute-markerMode"><code>ttp:markerMode</code></a></td><td><em>none</em></td><td/><td>expresses marker continuity semantics</td><td/></tr><tr><td><a href="#parameter-attribute-pixelAspectRatio"><code>ttp:pixelAspectRatio</code></a></td><td><em>none</em></td><td/><td>expresses pixel aspect ratio of related media</td><td/></tr><tr><td><a href="#parameter-attribute-profile"><code>ttp:profile</code></a></td><td><em>none</em></td><td/><td>expresses profile of TT AF used by document instance</td><td/></tr><tr><td><a href="#parameter-attribute-smpteMode"><code>ttp:smpteMode</code></a></td><td><em>none</em></td><td/><td>expresses frame counting (drop) modes</td><td/></tr><tr><td><a href="#parameter-attribute-subFrameRate"><code>ttp:subFrameRate</code></a></td><td><em>none</em></td><td/><td>expresses sub-frame rate</td><td/></tr><tr><td><a href="#parameter-attribute-tickRate"><code>ttp:tickRate</code></a></td><td><em>none</em></td><td/><td>used to interpret tick based time expressions</td><td/></tr><tr><td><a href="#parameter-attribute-timeBase"><code>ttp:timeBase</code></a></td><td><em>none</em></td><td/><td>used to interpret semantics of time expressions</td><td/></tr><tr><td><a href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></a></td><td><code>background-color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1,6</td></tr><tr><td><a href="#style-attribute-color"><code>tts:color</code></a></td><td><code>color</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>6</td></tr><tr><td><a href="#style-attribute-direction"><code>tts:direction</code></a></td><td><code>direction</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td/></tr><tr><td><a href="#style-attribute-display"><code>tts:display</code></a></td><td><code>display</code></td><td><a href="#css2">[CSS2]</a></td><td>only <code>auto</code>, <code>none</code><span class="diff-del">, inherit</span></td><td/></tr><tr><td><a href="#style-attribute-displayAlign"><code>tts:displayAlign</code></a></td><td><code>display-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1</td></tr><tr><td><a href="#style-attribute-dynamicFlow"><code>tts:dynamicFlow</code></a></td><td><em>none</em></td><td/><td>defines <span class="diff-chg">dynamic</span> overflow behavior</td><td/></tr><tr><td><a href="#style-attribute-extent"><code>tts:extent</code></a></td><td><code>width</code>, <code>height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td/></tr><tr><td><a href="#style-attribute-fontFamily"><code>tts:fontFamily</code></a></td><td><code>font-family</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-add"><code>-inherit</code>, </span>extends generic family names</td><td>1</td></tr><tr><td><a href="#style-attribute-fontSize"><code>tts:fontSize</code></a></td><td><code>font-size</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1,7</td></tr><tr><td><a href="#style-attribute-fontStyle"><code>tts:fontStyle</code></a></td><td><code>font-style</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-add"><code>-inherit</code>, </span>uses alias <code>reverseOblique</code> for <code>backslant</code></td><td>1</td></tr><tr><td><a href="#style-attribute-fontWeight"><code>tts:fontWeight</code></a></td><td><code>font-weight</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-add"><code>-inherit</code>, </span><code>-bolder</code>, <code>-lighter</code>, <code>-<number></code></td><td>1</td></tr><tr><td><a href="#style-attribute-lineHeight"><code>tts:lineHeight</code></a></td><td><code>line-height</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-add"><code>-inherit</code>, </span><code>-<number></code>, <code>-<space></code></td><td>1</td></tr><tr><td><a href="#style-attribute-opacity"><code>tts:opacity</code></a></td><td><code>opacity</code></td><td><a href="#css3-color">[CSS3 Color]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td/></tr><tr><td><a href="#style-attribute-origin"><code>tts:origin</code></a></td><td><code>top</code>, <code>left</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td>shorthand property</td><td/></tr><tr><td><a href="#style-attribute-overflow"><code>tts:overflow</code></a></td><td><code>overflow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-add"><code>-inherit</code>, </span><code>-auto</code>, <code>-error-if-overflow</code>; <span class="diff-chg"><code>+dynamic</code></span></td><td>8</td></tr><tr><td><a href="#style-attribute-padding"><code>tts:padding</code></a></td><td><code>padding</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>9</td></tr><tr><td><a href="#style-attribute-showBackground"><code>tts:showBackground</code></a></td><td><code>showBackground</code></td><td><a href="#smil21">[SMIL 2.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td/></tr><tr><td><a href="#style-attribute-textAlign"><code>tts:textAlign</code></a></td><td><code>text-align</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1</td></tr><tr><td><a href="#style-attribute-textDecoration"><code>tts:textDecoration</code></a></td><td><code>text-decoration</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1,10<span class="diff-add">,13</span></td></tr><tr><td><a href="#style-attribute-textOutline"><code>tts:textOutline</code></a></td><td><code>text-shadow</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>11<span class="diff-add">,13</span></td></tr><tr><td><a href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></a></td><td><code>unicode-bidi</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1</td></tr><tr><td><a href="#style-attribute-visibility"><code>tts:visibility</code></a></td><td><code>visibility</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-add"><code>-inherit</code>, </span><code>-collapse</code></td><td/></tr><tr><td><a href="#style-attribute-wrapOption"><code>tts:wrapOption</code></a></td><td><code>wrap-option</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1</td></tr><tr><td><a href="#style-attribute-writingMode"><code>tts:writingMode</code></a></td><td><code>writing-mode</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-add"><code>-inherit</code>, </span><code>+tblr</code></td><td>1</td></tr><tr><td><a href="#style-attribute-zIndex"><code>tts:zIndex</code></a></td><td><code>z-index</code></td><td><a href="#xsl11">[XSL 1.1]</a></td><td><span class="diff-chg"><code>-inherit</code></span></td><td>1</td></tr><tr><td><a href="#content-attribute-id"><code>xml:id</code></a></td><td><code>xml:id</code></td><td><a href="#xmlid">[XML ID]</a></td><td>complies with model</td><td/></tr><tr><td><a href="#content-attribute-lang"><code>xml:lang</code></a></td><td><code>xml:lang</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>complies with model</td><td/></tr><tr><td><a href="#content-attribute-space"><code>xml:space</code></a></td><td><code>xml:space</code></td><td><a href="#xml10">[XML 1.0]</a></td><td>see notes</td><td>12</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>Attribute name and/or value(s) are normalized to use
<em>lowerCamelCase</em> naming convention.</p></li><li><p>Restricted to expressing a clock value that denotes one of the
following in accordance to whether the parameter expressed by the
<code>ttp:timeBase</code> attribute is <code>media</code>, <code>smpte</code>,
@@ -9127,13 +9099,13 @@
contours and inside of inner closed contours.</p></li><li><p>On root element, default attribute value specified as
<code>default</code>, which is defined in terms of whitespace
normalization. Semantics of preservation and default normalization are
-defined in terms of presentation semantics by <a href="#content-attribute-space"><b>7.2.3 xml:space</b></a>.</p></li></ol></div></div></div><div class="div1">
+defined in terms of presentation semantics by <a href="#content-attribute-space"><b>7.2.3 xml:space</b></a>.</p></li><li><p class="diff-add">Defined to be inheritable.</p></li></ol></div></div></div><div class="div1">
<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="d3e19722" id="d3e19722"/>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="d3e21130" id="d3e21130"/>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="d3e19886" id="d3e19886"/>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><a href="#sample-code">YES</a></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="d3e21294" id="d3e21294"/>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><a href="#sample-code">YES</a></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">
--- a/spec/ttaf1-dfxp.xml Mon May 04 11:32:21 2009 +0000
+++ b/spec/ttaf1-dfxp.xml Mon May 04 11:45:14 2009 +0000
@@ -44,6 +44,8 @@
<!ENTITY rnc-dfxp-metadata-module SYSTEM "./rnc/ttaf1-dfxp-metadata.rnc.esc">
<!ENTITY rnc-dfxp-metadata-items-module SYSTEM "./rnc/ttaf1-dfxp-metadata-items.rnc.esc">
<!ENTITY rnc-dfxp-metadata-attribs-module SYSTEM "./rnc/ttaf1-dfxp-metadata-attribs.rnc.esc">
+<!ENTITY rnc-dfxp-parameters-module SYSTEM "./rnc/ttaf1-dfxp-parameters.rnc.esc">
+<!ENTITY rnc-dfxp-parameter-items-module SYSTEM "./rnc/ttaf1-dfxp-parameter-items.rnc.esc">
<!ENTITY rnc-dfxp-parameter-attribs-module SYSTEM "./rnc/ttaf1-dfxp-parameter-attribs.rnc.esc">
<!ENTITY rnc-dfxp-styling-attribs-module SYSTEM "./rnc/ttaf1-dfxp-styling-attribs.rnc.esc">
<!ENTITY rnc-dfxp-styling-module SYSTEM "./rnc/ttaf1-dfxp-styling.rnc.esc">
@@ -59,17 +61,16 @@
<!ENTITY xsd-dfxp-metadata-module SYSTEM "./xsd/ttaf1-dfxp-metadata.xsd.esc">
<!ENTITY xsd-dfxp-metadata-items-module SYSTEM "./xsd/ttaf1-dfxp-metadata-items.xsd.esc">
<!ENTITY xsd-dfxp-metadata-attribs-module SYSTEM "./xsd/ttaf1-dfxp-metadata-attribs.xsd.esc">
+<!ENTITY xsd-dfxp-parameters-module SYSTEM "./xsd/ttaf1-dfxp-parameters.xsd.esc">
+<!ENTITY xsd-dfxp-parameter-items-module SYSTEM "./xsd/ttaf1-dfxp-parameter-items.xsd.esc">
<!ENTITY xsd-dfxp-parameter-attribs-module SYSTEM "./xsd/ttaf1-dfxp-parameter-attribs.xsd.esc">
<!ENTITY xsd-dfxp-styling-attribs-module SYSTEM "./xsd/ttaf1-dfxp-styling-attribs.xsd.esc">
<!ENTITY xsd-dfxp-styling-module SYSTEM "./xsd/ttaf1-dfxp-styling.xsd.esc">
<!ENTITY xsd-dfxp-layout-module SYSTEM "./xsd/ttaf1-dfxp-layout.xsd.esc">
<!ENTITY xsd-dfxp-timing-attribs-module SYSTEM "./xsd/ttaf1-dfxp-timing-attribs.xsd.esc">
<!ENTITY xsd-dfxp-xml-attrs-module SYSTEM "./xsd/xml.xsd.esc">
-<!ENTITY code-rxi SYSTEM "./scm/rxi.scm.esc">
-<!ENTITY code-adi SYSTEM "./scm/adi.scm.esc">
-<!ENTITY code-tir SYSTEM "./scm/tir.scm.esc">
-<!ENTITY code-fox SYSTEM "./scm/fox.scm.esc">
-<!ENTITY code-dtf SYSTEM "./scm/dtf.scm.esc">
+<!ENTITY profile-dfxp-presentation SYSTEM "./profiles/dfxp-presentation.xml.esc">
+<!ENTITY profile-dfxp-transformation SYSTEM "./profiles/dfxp-transformation.xml.esc">
]>
<?xml-stylesheet type='text/xsl' href='xmlspec-ttaf1-dfxp.xsl'?>
<spec w3c-doctype="&doctype;" role="&document.role;">
@@ -250,7 +251,7 @@
<tr>
<td>
<eg xml:space="preserve">
-<styling xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<styling xmlns:tts="http://www.w3.org/2006/10/ttaf1#<phrase diff="chg">styling</phrase>">
<!-- s1 specifies default color, font, and text alignment -->
<style xml:id="s1"
tts:color="white"
@@ -285,7 +286,7 @@
<tr>
<td>
<eg xml:space="preserve">
-<layout xmlns:tts="http://www.w3.org/2006/10/ttaf1#style">
+<layout xmlns:tts="http://www.w3.org/2006/10/ttaf1#<phrase diff="chg">styling</phrase>">
<region xml:id="subtitleArea"
style="s1"
tts:extent="560px 62px"
@@ -561,6 +562,20 @@
item as defined by <bibref ref="infoset"/>, §2.6.</p>
</def>
</gitem>
+<gitem diff="add">
+<label>Content Processor</label>
+<def>
+<p>A processing system capable of importing (receiving) timed text authoring format
+content for the purpose of transforming, presenting, or otherwise processing the content.</p>
+</def>
+</gitem>
+<gitem diff="add">
+<label>Content Profile</label>
+<def>
+<p>A collection of features and extensions that are (or may be) employed by
+timed text authoring format content.</p>
+</def>
+</gitem>
<gitem>
<label>Content Region</label>
<def>
@@ -578,7 +593,46 @@
<gitem>
<label>Exchange Profile</label>
<def>
-<p>A profile (subset) of the TT AF that serves a set of needs for content exchange.</p>
+<p>A<phrase diff="add"> content</phrase> profile<phrase
+diff="del">(subset) of the TT AF</phrase> that serves a set of needs
+for content <phrase diff="chg">inter</phrase>change.</p>
+</def>
+</gitem>
+<gitem diff="add">
+<label>Extension</label>
+<def>
+<p>A syntactic or semantic expression or capability that is defined and
+labeled (using a extension designation) in another (public or private)
+specification.</p>
+</def>
+</gitem>
+<gitem diff="add">
+<label>Feature</label>
+<def>
+<p>A syntactic or semantic expression or capability that is defined and
+labeled (using a feature designation) in this specification (or a
+future revision of this specification).</p>
+</def>
+</gitem>
+<gitem diff="add">
+<label>Processor</label>
+<def>
+<p>See <emph>Content Processor</emph>.</p>
+</def>
+</gitem>
+<gitem diff="add">
+<label>Processor Profile</label>
+<def>
+<p>A collection of features and extensions that must or may be implemented (supported) by
+by a content processor.</p>
+</def>
+</gitem>
+<gitem diff="add">
+<label>Profile Definition Document</label>
+<def>
+<p>A document that defines a specific collection of features and extensions
+for which support is required or optional in a recipient content
+processor.</p>
</def>
</gitem>
<gitem>
@@ -733,7 +787,9 @@
<code>application/ttaf+xml</code> in conformance with <bibref
ref="rfc3023"/> § 7, with which an optional
<code>profile</code> parameter may appear, the value of which
-conforms to the values defined by
+conforms to
+<phrase diff="del">the values</phrase><phrase diff="add">a profile designator as</phrase>
+defined by
<specref ref="vocabulary-profiles"/>.</p>
</item>
<item>
@@ -762,16 +818,10 @@
</div2>
<div2 id="conformance-processor">
<head>Processor Conformance</head>
-<ednote>
-<name>GA</name>
-<date>2009-01-30</date>
-<edtext>
-The following description of processor conformance needs to be sub-divided into
-transformation and presentation processor specific descriptions, possibly retaining
-common elements in a base processor conformance clause.
-</edtext>
-</ednote>
-<p>A TT AF processor conforms to this specification if the following criteria are
+<div3 id="conformance-generic-processor">
+<head><phrase diff="add">Generic Processor Conformance</phrase></head>
+<p>A TT AF processor conforms to this specification if the following
+<phrase diff="add">generic processor </phrase>criteria are
satisfied:</p>
<olist>
<item>
@@ -791,13 +841,16 @@
</item>
<item>
<p>The processor does not <emph>a priori</emph> reject or abort the
-processing of a conformant TT AF document instance.</p>
+processing of a conformant TT AF document instance
+<phrase diff="add">unless the processor does not support some required
+(mandatory) feature specified or implied by a TT AF content profile
+declared to apply to the document instance</phrase>.</p>
</item>
<item>
<p>The processor supports all mandatory processing semantics defined by this specification.</p>
</item>
<item>
-<p>If the processor claims to support presentation processing in order
+<p diff="del">If the processor claims to support presentation processing in order
to produce a rendition of TT AF content on a visual medium, then it
must implement the region and line layout
semantics defined by <specref ref="semantics-region-layout"/> and
@@ -811,6 +864,43 @@
then it does so in a manner consistent with the defined semantics.</p>
</item>
</olist>
+</div3>
+<div3 id="conformance-transformation-processor" diff="add">
+<head>Transformation Processor Conformance</head>
+<p>A TT AF processor is a conformant TT AF transformation processor if
+the following criteria are satisfied:</p>
+<olist>
+<item>
+<p>The processor satisfies all requirements specified by
+<specref ref="conformance-generic-processor"/>.</p>
+</item>
+<item>
+<p>The processor supports the DFXP Transformation profile as specified
+by <specref ref="profile-dfxp-transformation"/>.</p>
+</item>
+</olist>
+</div3>
+<div3 id="conformance-presentation-processor" diff="add">
+<head>Presentation Processor Conformance</head>
+<olist>
+<item>
+<p>The processor satisfies all requirements specified by
+<specref ref="conformance-generic-processor"/>.</p>
+</item>
+<item>
+<p>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>
+</olist>
+</div3>
</div2>
<div2 id="claims">
<head>Claims</head>
@@ -825,8 +915,16 @@
superset profile is used or supported, then what features are excluded
or included in the subset or superset profile.</p>
<p>A TT AF document instance for which a compliance claim is made
-must specify a <att>ttp:profile</att> attribute on its root element
-as defined by <specref ref="parameter-attribute-profile"/>.</p>
+must specify
+<phrase diff="add">either (1)</phrase>
+a <att>ttp:profile</att> attribute on its root
+<phrase diff="add"><el>tt</el></phrase>
+element
+as defined by <specref ref="parameter-attribute-profile"/>
+<phrase diff="add">or (2)
+a <el>ttp:profile</el> element as a child of the
+<el>head</el> element as defined by
+<specref ref="parameter-vocabulary-profile"/></phrase>.</p>
</div2>
</div1>
<div1 id="doctypes">
@@ -871,9 +969,11 @@
value of each attribute satisfies the type declared by the
associated abstract document type.</p>
<note>
-<p>While a conformant processor may not <emph>a priori</emph> reject a conformant document
-instance, a given document instance may be constrained by the author or authoring tool
-to satisfy a more restrictive definition of validity.</p>
+<p>While a conformant processor may not <emph>a priori</emph> reject a
+conformant document instance <phrase diff="add">that adheres to a
+supported content profile</phrase>, a given document instance may be
+constrained by the author or authoring tool to satisfy a more
+restrictive definition of validity.</p>
</note>
<div2 id="dfxp-content-doctype">
<head>DFXP Content</head>
@@ -891,6 +991,13 @@
<p>The (root) document element of a DFXP document instance must be a
<el>tt</el> element, as defined by <specref
ref="document-structure-vocabulary-tt"/>.</p>
+<note role="clarification" diff="add">
+<p>The schemas included in this specification do not validate all syntactic constraints
+defined by this specification. In particular, performing validation with one of the above
+referenced schemas may result in a <emph>false positive</emph> indication of validity.
+However, their use will not produce a <emph>false negative</emph> indication of validity
+when used with a compliant validating processor.</p>
+</note>
</div2>
</div1>
<div1 id="vocabulary">
@@ -930,29 +1037,24 @@
<td><code>http://www.w3.org/2006/10/ttaf1</code></td>
</tr>
<tr>
-<td><phrase diff="add">TT Feature Prefix</phrase></td>
-<td><phrase diff="add"><code>ttf:</code></phrase></td>
-<td><phrase diff="add"><code>http://www.w3.org/2006/10/ttaf1/feature</code></phrase></td>
-</tr>
-<tr>
-<td><phrase diff="add">TT Extension Prefix</phrase></td>
-<td><phrase diff="add"><code>ttx:</code></phrase></td>
-<td><phrase diff="add"><code>http://www.w3.org/2006/10/ttaf1/extension</code></phrase></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><phrase diff="add">TT Parameter Extension</phrase></td>
+<td><phrase diff="add"><code>ttpx:</code></phrase></td>
+<td><phrase diff="add"><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#style</code></td>
+<td><code>http://www.w3.org/2006/10/ttaf1#<phrase diff="chg">styling</phrase></code></td>
</tr>
<tr>
<td>TT Style Extension<phrase diff="del">s</phrase></td>
<td><code>ttsx:</code></td>
-<td><code>http://www.w3.org/2006/10/ttaf1#style-extension</code></td>
+<td><code>http://www.w3.org/2006/10/ttaf1#<phrase diff="chg">styling</phrase>-extension</code></td>
</tr>
<tr>
<td>TT Metadata</td>
@@ -964,35 +1066,81 @@
<td><code>ttmx:</code></td>
<td><code>http://www.w3.org/2006/10/ttaf1#metadata-extension</code></td>
</tr>
+<tr>
+<td><phrase diff="add">TT Profile</phrase></td>
+<td><phrase diff="add"><emph>none</emph></phrase></td>
+<td><phrase diff="add"><code>http://www.w3.org/2006/10/ttaf1/profile</code></phrase></td>
+</tr>
+<tr>
+<td><phrase diff="add">TT Feature</phrase></td>
+<td><phrase diff="add"><emph>none</emph></phrase></td>
+<td><phrase diff="add"><code>http://www.w3.org/2006/10/ttaf1/feature</code></phrase></td>
+</tr>
+<tr>
+<td><phrase diff="add">TT Extension</phrase></td>
+<td><phrase diff="add"><emph>none</emph></phrase></td>
+<td><phrase diff="add"><code>http://www.w3.org/2006/10/ttaf1/extension</code></phrase></td>
+</tr>
</tbody>
</table>
<note role="clarification">
<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 diff="add">For certain namespaces defined above, the default prefix
+is specified as <emph>none</emph> 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>
</note>
</div2>
<div2 id="vocabulary-profiles">
<head>Profiles</head>
-<p>The Timed Text Authoring Format (TT AF) employs a number of profiles of its
+<p>The Timed Text Authoring Format (TT AF) employs a number of
+<phrase diff="add">standard, predefined </phrase>profiles of its
vocabulary and associated semantics.
-The following table specifies this set of profiles
-and indicates a normative name for each profile.</p>
+The following table specifies this set of
+profiles<phrase diff="chg">, indicating</phrase>
+a normative name
+<phrase diff="add">and designator </phrase>for each
+<phrase diff="add">predefined </phrase>profile<phrase diff="add">,
+and where each of these profiles is formally elaborated in
+<specref ref="profiles"/></phrase>.</p>
<table id="profile-vocab-table" role="common">
<caption>Table 2 – Profiles</caption>
<col width="25%"/>
<tbody>
<tr>
<th>Name</th>
-<th>Value</th>
-</tr>
-<tr>
-<td>DFXP</td>
-<td><code>http://www.w3.org/2006/10/ttaf1#profile-dfxp</code></td>
+<th><phrase diff="del">Value</phrase><phrase diff="add">Designator</phrase></th>
+</tr>
+<tr>
+<td>DFXP<phrase diff="add"> Transformation</phrase></td>
+<td><phrase diff="chg"><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation</code></phrase></td>
+</tr>
+<tr>
+<td><phrase diff="add">DFXP Presentation</phrase></td>
+<td><phrase diff="add"><code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code></phrase></td>
</tr>
</tbody>
</table>
<p/>
-<p>A convention is defined for use by content authors to indicate use of a
+<p diff="add">A profile designator must adhere to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+§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
+the base URI.</p>
+<p diff="add">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>
+<note role="example" diff="add">
+<p>For example, if a profile designator were expressed as
+<code>dfxp-presentation</code>, then the absolutized profile designator
+would be
+<code>http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation</code>.</p>
+</note>
+<p diff="del">A convention is defined for use by content authors to indicate use of a
subtractive or additive delta to a predefined profile by using an
optional <emph>sub-profile</emph> suffix of a profile URI: if a sub-profile
is subtractive (results in a proper subset), then the <emph>sub-profile</emph>
@@ -1000,19 +1148,82 @@
expressed as "+token", where <emph>token</emph> expresses an author determined
sub-profile that adheres to the <code>xsd:NCName</code> data type
defined in <bibref ref="xsd-2"/>, §3.3.7.</p>
-<p>All tokens used in a sub-profile suffix that do not start with the
+<p diff="del">All tokens used in a sub-profile suffix that do not start with the
prefix <code>x-</code> are reserved for future standardization.</p>
-<p>The profile of a document instance is specified using a
-<att>ttp:profile</att> attribute as defined by <specref
-ref="parameter-attribute-profile"/>.</p>
-<note role="explanation">
+<p>The profile of a document instance is specified<phrase diff="add">
+either (1) by specifying</phrase> <phrase diff="del">using </phrase>a
+<att>ttp:profile</att> attribute<phrase
+diff="add"> on the root <el>tt</el> element,</phrase> as defined by
+<specref ref="parameter-attribute-profile"/><phrase diff="add">, or
+(2) by including a <el>ttp:profile</el> element in the <el>head</el>
+element, in accordance with <specref
+ref="parameter-vocabulary-profile"/></phrase>.</p>
+<p diff="add">If neither
+<loc href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
+attribute nor
+<loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
+element is present in a TT AF document instance, and if the document
+interchange context does not specify a profile,
+then the DFXP Transformation
+profile applies.</p>
+<note role="elaboration" diff="add">
+<p>It is intended that the <att>ttp:profile</att> attribute be used when
+the author wishes to reference one of the standard, predefined profiles of
+TT AF content, and does not wish to modify (by supersetting or subsetting)
+that profile. This attribute may also be used by an author to indicate the use
+of a non-standard profile, in which case the specified profile designator expresses
+a URI that denotes an externally defined TT AF Profile Definition Document.
+However, it is not required that a conformant TT AF content processor be able
+to dereference such an externally specified profile definition.</p>
+<p>In contrast, it is intended that the <el>ttp:profile</el> element be
+used when the author wishes to make use of a modified predefined profile or
+wishes to include in the document instance a non-standard profile definition
+not based upon one of the predefined profiles.</p>
+<p>A predefined profile is supersetted by specifying some feature or extension to
+be required (mandatory) that was either not specified in the underlying, baseline
+profile or was specified as optional (voluntary) in the baseline profile.
+A predefined profile is subsetted by specifying some feature or extension to
+be optional (voluntary) that was specified as required in the underlying, baseline
+profile.</p>
+<p>When a baseline profile is modified by subsetting, the resulting, derived profile
+is referred to as a <emph>subtractive</emph> profile; when modified by supersetting, the result
+is referred to as an <emph>additive</emph> profile.
+It is also possible to define a derived profile that is simultaneously subtractive
+and additive.</p>
+</note>
+<note role="explanation" diff="del">
<p>A TT AF authoring system may indicate the profile of TT AF used in
-a document instance by
-specifying a <att>ttp:profile</att> attribute.
-A TT AF content processor may make use of this profile value to
-associate a document instance with a schema or processing functions.</p>
-</note>
-<p>An example of an author defined "tiny" subtractive sub-profile of DFXP is shown
+a document instance by specifying a <loc
+href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
+attribute. A TT AF content processor may make use of this profile
+value to associate a document instance with a schema or processing
+functions.</p>
+</note>
+<p diff="add">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>
+specification in one of its declared 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>
+specification in one of its declared profiles.</p>
+<note role="elaboration" diff="add">
+<p>A required 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>. A required 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>.</p>
+</note>
+<p>An example of an author defined
+<phrase diff="chg">subtractive, derived profile of the DFXP Presentation
+profile</phrase> is shown
below in <specref ref="dfxp-example-sub-profile"/>.</p>
<table id="dfxp-example-sub-profile" role="example">
<caption>Example Fragment – DFXP Subtractive Profile</caption>
@@ -1020,19 +1231,27 @@
<tr>
<td>
<eg xml:space="preserve">
-<tt
- ttp:profile="http://www.w3.org/2006/10/ttaf1#profile-dfxp-x-tiny"
- xml:lang=""
- xmlns="http://www.w3.org/2006/10/ttaf1"
- xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter">
- ...
+<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>
+ <feature value="optional">#fontStyle-italic</feature>
+ </features>
+ </profile>
+ </head>
+ <body/>
</tt>
</eg>
</td></tr>
</tbody>
</table>
<note role="explanation">
-<p>Because the above example is an author defined sub-profile (as
+<p diff="add">In the above example, the baseline profile is declared to be
+the DFXP Presentation profile, which is then subtractively modified by making the
+<code>#fontStyle-italic</code> feature optional (rather than required 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>
+<p diff="del">Because the above example is an author defined sub-profile (as
opposed to a future W3C defined profile), the sub-profile token
contains the prefix <code>x-</code>.</p>
</note>
@@ -1142,6 +1361,15 @@
</td>
</tr>
<tr>
+<td><phrase diff="add">Parameter Items</phrase></td>
+<td><phrase diff="add"><loc href="#parameter-vocabulary-profile">ttp:profile</loc>,
+<loc href="#parameter-vocabulary-features">ttp:features</loc>,
+<loc href="#parameter-vocabulary-feature">ttp:feature</loc>,
+<loc href="#parameter-vocabulary-extensions">ttp:extensions</loc>,
+<loc href="#parameter-vocabulary-extension">ttp:extension</loc></phrase>
+</td>
+</tr>
+<tr>
<td>
Styling
</td>
@@ -1202,6 +1430,11 @@
<loc href="#metadata-vocabulary-title">ttm:title</loc>
</td>
</tr>
+<tr>
+<td><phrase diff="add">Parameters.class</phrase></td>
+<td><phrase diff="add"><loc
+href="#parameter-vocabulary-profile">ttp:profile</loc></phrase></td>
+</tr>
</tbody>
</table>
<p/>
@@ -1332,16 +1565,19 @@
<p>The extension vocabulary catalog is intended for use by future
profiles of the TT AF.</p>
<p>In this version of this specification, no
-standardized extension vocabulary is defined. Two namespaces are
+standardized extension vocabulary is defined. The following namespaces are
specifically reserved by <specref ref="namespace-vocab-table"/>
-for metadata and style extension vocabulary:</p>
+for extension vocabulary:</p>
<ulist>
<item>
+<p>TT Metadata Extension<phrase diff="del">s</phrase></p>
+</item>
+<item>
+<p diff="add">TT Parameter Extension</p>
+</item>
+<item>
<p>TT Style Extension<phrase diff="del">s</phrase></p>
</item>
-<item>
-<p>TT Metadata Extension<phrase diff="del">s</phrase></p>
-</item>
</ulist>
<p>In addition to standardized extension vocabulary, a conforming TT
AF document instance may contain arbitrary namespace qualified
@@ -1363,13 +1599,451 @@
interpreting the semantics of other types of information expressed by
core vocabulary items or for establishing a processing context by means
of which TT AF content can be related to an external environment.</p>
-<div2 id="parameters-element-vocabulary">
-<head><phrase diff="add">Parameters </phrase>Element Vocabulary</head>
-<p>No parameters related element vocabulary is defined for use in the
+<div2 id="parameter-element-vocabulary">
+<head><phrase diff="add">Parameter </phrase>Element Vocabulary</head>
+<p diff="add">The following elements, all defined in the TT Parameter
+Namespace, specify parametric information that applies to a document
+or a content processor:</p>
+<ulist diff="add">
+<item><p><specref ref="parameter-vocabulary-profile"/></p></item>
+<item><p><specref ref="parameter-vocabulary-features"/></p></item>
+<item><p><specref ref="parameter-vocabulary-feature"/></p></item>
+<item><p><specref ref="parameter-vocabulary-extensions"/></p></item>
+<item><p><specref ref="parameter-vocabulary-extension"/></p></item>
+</ulist>
+<p diff="del">No parameters related element vocabulary is defined for use in the
core vocabulary catalog.</p>
+
+<div3 id="parameter-vocabulary-profile" diff="add">
+<head>ttp:profile</head>
+<p>The <el>ttp:profile</el> element is used to specify a collection of
+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>
+<note role="clarification">
+<p>The difference between is <emph>feature</emph> and an
+<emph>extension</emph> is where it is defined an how it is labeled:
+if defined in this specification (or a future revision thereof) and
+labeled with a feature designation in <specref ref="features"/>, then
+it is considered to be a feature; if defined in another specification
+and labeled there with an extension designation, then it is considered
+to be an extension.</p>
+</note>
+<p>This specification defines two distinct uses of the <el>ttp:profile</el> element:</p>
+<ulist>
+<item>
+<p>as a child of the <el>head</el> element within a TT AF document
+instance;</p>
+</item>
+<item>
+<p>as the root element of a TT AF Profile Definition document
+instance;</p>
+</item>
+</ulist>
+<p>When a <el>tt:profile</el> element appears within a TT AF document
+instance, its purpose is to express authorial intentions about which
+featueres and extensions must or may be supported by a recipient
+content processor. In addition, the element indirectly expresses
+information about the set of features or extensions that are (or may
+expected to be) used by the document instance.</p>
+<p>When a <el>tt:profile</el> element is used by a TT AF
+Profile Definition document instance, it serves to publish a machine
+readable specification of a specific TT AF content profile, of which
+this specification defines two such Profile Definition Documents in
+<specref ref="profiles"/>.</p>
+<p>The <el>ttp:profile</el> element accepts as its children zero or more
+elements in the <code>Metadata.class</code> element group, followed by
+zero or more <el>ttp:features</el> elements, followed by
+zero or more <el>ttp:extensions</el> elements.</p>
+<table id="elt-syntax-parameter-profile" role="syntax">
+<caption>XML Representation – Element Information Item: ttp:profile</caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:profile
+ use = string
+ <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-features">ttp:features</loc>*, <loc href="#parameter-vocabulary-extensions">ttp:extensions</loc>*
+</ttp:profile>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<p>If specified, the <att>use</att> attribute must adhere to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+§3.2.17, and, furthermore, must denote a profile designator in
+accordance with <specref ref="vocabulary-profiles"/>. In this case,
+the profile designator must refer to (1) a standard, predefined
+TT AF Profile Definition Document as defined by <specref ref="profiles"/>,
+or (2) a dereferenceable resource representing a valid TT AF Profile Definition
+document instance. In either case, the referenced profile serves as the
+baseline profile of the specifying <el>ttp:profile</el> element.</p>
+<p>If the <att>use</att> attribute is not specified, then the baseline
+profile of the <el>ttp:profile</el> element must be considered to be
+the empty (null) profile, i.e., a profile definition containing no
+feature or extension specifications.</p>
+<p>The collection of features and extensions of a profile are determined according
+to the following ordered rules:</p>
+<olist>
+<item>
+<p>initialize the features and extensions of the profile to the empty
+set;</p>
+</item>
+<item>
+<p>if a <att>use</att> attribute is present, then augment the profile
+with the set of features and extensions specified by the referenced
+baseline profile;</p>
+</item>
+<item>
+<p>for each <el>ttp:feature</el> and <el>ttp:extension</el> element
+descendant of the <el>ttp:profile</el> element, using a post-order
+traversal, merge the specified feature or extension with the features
+and extensions of the profile, where merging a feature or extension
+entails replacing an existing feature or extension specification, if
+it already exists, or adding a new feature or extension specification,
+if it does not yet exist in the profile;</p>
+</item>
+</olist>
+<p>A conformant TT AF processor is not required to be able to
+dereference a TT AF Profile Definition Document that is not one of the
+standard, predefined profiles defined by <specref ref="profiles"/>. A
+conformant TT AF processor may make use of a built-in, static
+form of each standard, predefined profile so as not to require
+dereferencing a network resource.</p>
+<p>If a TT AF processor is unable to dereference a non-standard TT AF
+Profile Definition Document, then it must not further process the
+document without the presence of an explicit override from an end-user
+or some implementation specific parameter traceable to an end-user or
+to a user or system configuration setting. If a TT AF processor aborts
+processing of a TT AF document instance due to the inability to
+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>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>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:profile use="dfxp-presentation">
+ <ttp:features>
+ <ttp:feature>#rollUp</ttp:feature>
+ </ttp:features>
+</ttp:profile>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<note role="explanation">
+<p>In the above example, the DFXP presentation profile is used as the
+baseline profile. This baseline profile is then supersetted (thus
+creating an additive derived profile) by requiring support for
+<code>#rollUp</code> feature.</p>
+</note>
+
+</div3>
+<div3 id="parameter-vocabulary-features" diff="add">
+<head>ttp:features</head>
+<p>The <el>ttp:features</el> element is a container element used to group
+infomation about feature support requirements.</p>
+<p>The <el>ttp:features</el> element accepts as its children zero or more
+elements in the <code>Metadata.class</code> element group, followed by
+zero or more <el>ttp:feature</el> elements.</p>
+<table id="elt-syntax-parameter-features" role="syntax">
+<caption>XML Representation – Element Information Item: ttp:features</caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:features
+ 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>*
+</ttp:features>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<p>If specified, the <att>base</att> attribute must adhere to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+§3.2.17, and, furthermore, must express a feature namespace as
+defined by <specref ref="feature-designations"/>. If not specified,
+the <att>base</att> attribute's default value applies, which is
+the TT Feature Namespace.</p>
+<p>The <att>base</att> attribute is used to permit the abbreviation
+of feature designation URIs expressed by child <el>ttp:feature</el>
+elements.</p>
+</div3>
+<div3 id="parameter-vocabulary-feature" diff="add">
+<head>ttp:feature</head>
+<p>The <el>ttp:feature</el> element is used to specify
+infomation about support requirements for a particular feature.</p>
+<p>The children of the <el>ttp:feature</el> element must express a non-empty
+sequence of character information items that adheres to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+§3.2.17.</p>
+<table id="elt-syntax-parameter-feature" role="syntax">
+<caption>XML Representation – Element Information Item: ttp:feature</caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:feature
+ value = (required|optional) : 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
+</ttp:feature>
+</eg>
+</td>
+</tr>
+</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 value of the
+<att>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>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 <code>required</code>, then the processor must implement or
+otherwise support the feature in order to process the document;
+however, if the value is <code>optional</code>, then the processor
+need not implement or otherwise support the feature in order to
+process the document.</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
+item definition. Therefore, if a <att>value</att> attribute is not
+specified on a <el>ttp:feature</el> element, it is equivalent to
+specifying that support for the feature is required.</p>
+</note>
+<p>If the value of the <att>value</att> attribute is
+<code>required</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
+implementation specific parameter traceable to an end-user or to a
+user or system configuration setting. If a TT AF processor aborts
+processing of a TT AF document instance due to the specification of a
+required, but unsupported feature by this element, 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>If the value of the <att>value</att> attribute is
+<code>optional</code>, and if the TT AF processor implementation does
+not support the feature, then it may further process the document even
+in the case that some use of the feature is present in the document.
+In the case of actual use of a feature designated as optional, the
+default semantics associated with that feature apply; that is, the
+processor may behave as if the feature were not actually used or
+referenced by the document. Notwithstanding the above, the syntactic
+presence or reference to an optional feature by a document must not be
+considered to be a violation of document validity or a barrier to
+further processing if the syntactic expression is well-formed and
+valid.</p>
+<p>The <el>ttp:feature</el> element is illustrated by the following example.</p>
+<table id="parameter-vocabulary-feature-example-1" role="example">
+<caption>Example Fragment – ttp:feature</caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-presentation">
+ <ttp:features>
+ <phrase role="strong"><ttp:feature value="required">#textDecoration-under</ttp:feature></phrase>
+ <phrase role="strong"><ttp:feature value="optional">#fontStyle-italic</ttp:feature></phrase>
+ </ttp:features>
+</ttp:profile>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<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> elements, the first to superset the
+baseline profile (since <code>#textDecoration-under</code> is not required
+by the DFXP presentation profile), and the second to subset the
+baseline profile (since <code>#fontStyle-italic</code> is nominally
+required by the DFXP presentation profile). Note that the explicit
+specification of <code>required</code> on the <att>value</att>
+attribute on the first of the two <el>ttp:feature</el> elements is not
+necessary, since it is the default value of this attribute.</p>
+<p>The effect of this example is to express authorial intentions that
+text underlining must be supported, but that the italic font style need
+not be supported (even though nominally required by the referenced baseline
+profile).</p>
+</note>
+</div3>
+<div3 id="parameter-vocabulary-extensions" diff="add">
+<head>ttp:extensions</head>
+<p>The <el>ttp:extensions</el> element is a container element used to group
+infomation about extension support requirements.</p>
+<p>The <el>ttp:extensions</el> element accepts as its children zero or more
+elements in the <code>Metadata.class</code> element group, followed by
+zero or more <el>ttp:extension</el> elements.</p>
+<table id="elt-syntax-parameter-extensions" role="syntax">
+<caption>XML Representation – Element Information Item: ttp:extensions</caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:extensions
+ 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>*
+</ttp:extensions>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<p>If specified, the <att>base</att> attribute must adhere to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+§3.2.17, and, furthermore, must express an extension namespace as
+defined by <specref ref="extension-designations"/>. If not specified,
+the <att>base</att> attribute's default value applies, which is
+the TT Extension Namespace.</p>
+<p>The <att>base</att> attribute is used to permit the abbreviation
+of extension designation URIs expressed by child <el>ttp:extension</el>
+elements.</p>
+</div3>
+<div3 id="parameter-vocabulary-extension" diff="add">
+<head>ttp:extension</head>
+<p>The <el>ttp:extension</el> element is used to specify
+infomation about support requirements for a particular extension.</p>
+<p>The children of the <el>ttp:extension</el> element must express a non-empty
+sequence of character information items that adheres to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+§3.2.17.</p>
+<table id="elt-syntax-parameter-extension" role="syntax">
+<caption>XML Representation – Element Information Item: ttp:extension</caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:extension
+ value = (required|optional) : 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
+</ttp:extension>
+</eg>
+</td>
+</tr>
+</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 value of the
+<att>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>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 <code>required</code>, then the processor must implement or
+otherwise support the extension in order to process the document;
+however, if the value is <code>optional</code>, then the processor
+need not implement or otherwise support the extension in order to
+process the document.</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
+item definition. Therefore, if a <att>value</att> attribute is not
+specified on a <el>ttp:extension</el> element, it is equivalent to
+specifying that support for the extension is required.</p>
+</note>
+<p>If the value of the <att>value</att> attribute is
+<code>required</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
+implementation specific parameter traceable to an end-user or to a
+user or system configuration setting. If a TT AF processor aborts
+processing of a TT AF document instance due to the specification of a
+required, but unsupported extension by this element, 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>If the value of the <att>value</att> attribute is
+<code>optional</code>, and if the TT AF processor implementation does
+not support the extension, then it may further process the document even
+in the case that some use of the extension is present in the document.
+In the case of actual use of an extension designated as optional, the
+default semantics associated with that extension apply; that is, the
+processor may behave as if the extension were not actually used or
+referenced by the document. Notwithstanding the above, the syntactic
+presence or reference to an optional extension by a document must not be
+considered to be a violation of document validity or a barrier to
+further processing if the syntactic expression is well-formed and
+valid.</p>
+<p>The <el>ttp:extension</el> element is illustrated by the following example.</p>
+<table id="parameter-vocabulary-extension-example-1" role="example">
+<caption>Example Fragment – ttp:extension</caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<ttp:profile use="http://www.w3.org/2006/10/ttaf1/profile/dfxp-transformation">
+ <ttp:extensions>
+ <phrase role="strong"><ttp:extension value="required">#x-prefilter-by-language</ttp:extension></phrase>
+ </ttp:extensions>
+ <ttp:extensions base="http://foo.bar.baz/ttaf1/extension">
+ <phrase role="strong"><ttp:extension value="required">#private-extension-1</ttp:extension></phrase>
+ </ttp:extensions>
+</ttp:profile>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<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 is required for 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 a
+private extension defined in a third party namespace. 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.</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 two additional extensions, one (hypothetically)
+defined by the W3C (in another specification or in a future version of
+this specification) and the other defined by a third party.</p>
+</note>
+</div3>
</div2>
-<div2 id="parameters-attribute-vocabulary">
-<head><phrase diff="add">Parameters </phrase>Attribute Vocabulary</head>
+<div2 id="parameter-attribute-vocabulary">
+<head><phrase diff="add">Parameter </phrase>Attribute Vocabulary</head>
<p>The following attributes are defined in the TT Parameter Namespace.</p>
<ulist>
<item><p><specref ref="parameter-attribute-cellResolution"/></p></item>
@@ -1540,7 +2214,9 @@
<p>A frame rate multiplier is used when the desired frame rate cannot
be expressed as an integral number of frames per second.</p>
<p>If not specified, the frame rate multiplier must be considered to
-be equal to one (1:1). If a denominator is specified, then it must not be zero (0).</p>
+be equal to one (1:1). If a denominator is specified, then it must not be zero (0).
+<phrase diff="add"> If no denominator is specified, then a denominator of one (1)
+applies</phrase>.</p>
<p>A <att>ttp:frameRateMultiplier</att> attribute is considered to be significant only
when specified on the <el>tt</el> element.</p>
<note role="example">
@@ -1665,12 +2341,22 @@
in a document instance.</p>
<p>If specified, the value of this attribute must adhere to the
<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-§3.2.17, and, further, must specify a profile URI as defined
-by <specref ref="vocabulary-profiles"/>.</p>
-<p>If not specified, then the Distribution Format Exchange Profile
-(DFXP) must be assumed to apply.</p> <p>A <att>ttp:profile</att>
+§3.2.17, and, further, must specify a
+profile <phrase diff="chg">designator in accordance with</phrase>
+<specref ref="vocabulary-profiles"/>.</p>
+<p diff="del">If not specified, then the Distribution Format Exchange
+Profile (DFXP) must be assumed to apply.</p>
+<p>A <att>ttp:profile</att>
attribute is considered to be significant only when specified on the
<el>tt</el> element.</p>
+<p diff="add">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>
@@ -1919,17 +2605,6 @@
</ulist>
<div3 id="document-structure-vocabulary-tt">
<head>tt</head>
-<ednote>
-<name>GA</name>
-<date>2009-01-19</date>
-<edtext>
-The inclusion of
-<att>requiredFeatures</att> and
-<att>requiredExtensions</att>
-attributes on the <el>tt</el> element type is provisional, and is provided for
-discussion purposes only.
-</edtext>
-</ednote>
<p>The <el>tt</el> element serves as the root, document element of a document
instance.</p>
<p>The <el>tt</el> element accepts as its children zero or one <el>head</el> element followed by
@@ -1941,8 +2616,6 @@
<td>
<eg xml:space="preserve">
<tt
- <phrase diff="add">requiredFeatures = string</phrase>
- <phrase diff="add">requiredExtensions = string</phrase>
<phrase diff="add"><loc href="#style-attribute-extent">tts:extent</loc> = string</phrase>
<loc href="#content-attribute-id">xml:id</loc> = ID
<loc href="#content-attribute-lang"><phrase role="reqattr">xml:lang</phrase></loc> = string
@@ -1964,58 +2637,9 @@
<p>A document instance has an implicit duration that is equal to the
implicit duration of the <el>body</el> element of the document, if present, or zero,
if not present.</p>
-<p diff="add">If a TT AF document instance makes use of an optional
-language or semantic feature, and if the intended use of the document
-requires recognition and processing of that feature, then the document
-instance must specify the use of that feature using a
-<att>requiredFeatures</att> attribute. If this attribute is specified
-on the <el>tt</el> element, then it must specify a non-empty, whitespace separated list of
-feature designators as defined by <specref
-ref="feature-designations"/>.</p>
-<p diff="add">If the use of an optional feature is designated by the
-<att>requiredFeatures</att> attribute, then a conforming TT AF
-processor must implement or otherwise support the designated feature
-in order to process the document; otherwise, it must not further
-process the document without the presence of an explicit override from
-an end-user or some implementation specific parameter traceable to an
-end-user or to a user or system configuration setting. If a TT AF
-processor aborts processing of a TT AF document instance due to the
-specification of an unsupported feature by this attribute, 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>
-<note role="clarification" diff="add">
-<p>The means by which an end-user is notified that the processing of a
-document has aborted due to lack of support of a feature is
-considered to be implementation dependent, and is not further defined
-by this specification.</p></note>
-<p diff="add">If a TT AF document instance makes use of a language or
-semantic extension, and if the intended use of the document requires
-recognition and processing of that extension, then the document
-instance must specify the use of that extension using a
-<att>requiredExtensions</att> attribute. If this attribute is
-specified on the <el>tt</el> element, then it must specify a non-empty, whitespace separated
-list of extension designators as defined by <specref
-ref="extension-designations"/>.</p>
-<p diff="add">If the use of an extension is designated by the
-<att>requiredExtensions</att> attribute, then a conforming TT AF
-processor must implement or otherwise support the designated extension
-in order to process the document; otherwise, it must not further
-process the document without the presence of an explicit override from
-an end-user or some implementation specific parameter traceable to an
-end-user or to a user or system configuration setting. If a TT AF
-processor aborts processing of a TT AF document instance due to the
-specification of an unsupported extension by this attribute, 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>
-<note role="clarification" diff="add">
-<p>The means by which an end-user is notified that the processing of a
-document has aborted due to lack of support of an extension is
-considered to be implementation dependent, and is not further defined
-by this specification.</p></note>
<p diff="add">If the <att>tts:extent</att> attribute is specified on the <el>tt</el>
-element, then it specifies the spatial extent of the root container region in
+element, then it must adhere to <specref ref="style-attribute-extent"/>, in which case it
+specifies the spatial extent of the root container region in
which content regions are located and presented. If no <att>tts:extent</att>
attribute is specified, then the spatial extent of the root container region is
considered to be determined by the external authoring or presentation
@@ -2029,15 +2653,20 @@
<div3 id="document-structure-vocabulary-head">
<head>head</head>
<p>The <el>head</el> element is a container element used to group
-header matter, including metadata, styling, and layout information.</p>
+header matter, including metadata<phrase diff="add">,
+profile</phrase>, styling, and layout information.</p>
<p>The <el>head</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group,
-followed by
-zero or one <el>styling</el> element, followed by zero or one
-<el>layout</el> element.</p>
+elements in the <code>Metadata.class</code> element group<phrase diff="add">,
+followed by zero or more elements in the
+<code>Parameters.class</code> element group</phrase>,
+followed by zero or one <el>styling</el> element,
+followed by zero or one <el>layout</el> element.</p>
<p>Any metadata specified by children in the <code>Metadata.class</code>
element group applies semantically to the document instance as a
whole, and not just the <el>head</el> element.</p>
+<p>Any parameters specified by children in the <code>Parameters.class</code>
+element group applies semantically to the document instance as a
+whole, and not just the <el>head</el> element.</p>
<p>A <el>styling</el> child element is used to specify style constructs
that are referenced from other style constructs, by layout constructs, and by
content elements.</p>
@@ -2053,7 +2682,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>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#styling-vocabulary-styling">styling</loc>?, <loc href="#layout-vocabulary-layout">layout</loc>?
+ <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*<phrase diff="add">, <loc href="#element-vocab-group-table">Parameters.class</loc>*</phrase>, <loc href="#styling-vocabulary-styling">styling</loc>?, <loc href="#layout-vocabulary-layout">layout</loc>?
</head>
</eg>
</td>
@@ -2699,7 +3328,8 @@
<head>tts:backgroundColor</head>
<p>The <att>tts:backgroundColor</att> attribute is used to specify a style property that
defines the background color of a region or an area generated by content flowed into a region.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-backgroundColor" role="common">
@@ -2786,7 +3416,8 @@
<head>tts:color</head>
<p>The <att>tts:color</att> attribute is used to specify a style property that
defines the foreground color of marks associated with an area generated by content flowed into a region.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-color" role="common">
@@ -2801,9 +3432,7 @@
</tr>
<tr>
<td><emph>Initial:</emph></td>
-<td>
-<code>transparent</code>
-</td>
+<td><phrase diff="chg">see prose</phrase></td>
</tr>
<tr>
<td><emph>Applies to:</emph></td>
@@ -2829,6 +3458,11 @@
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
span<phrase diff="del">, where the value of this style property on the anonymous span is considered to be
<code>inherit</code></phrase>.</p>
+<p diff="add">The initial value of the <att>tts:color</att> property
+is considered to be implementation dependent. In the absence of
+end-user preference information, a conformant presentation processor
+should use an initial value that is highly contrastive to the
+background color of the root container region.</p>
<p>The <att>tts:color</att> style is illustrated by the following example.</p>
<table id="style-attribute-color-example-1" role="example">
<caption>Example Fragment – Color</caption>
@@ -2872,7 +3506,8 @@
<p>The <att>tts:direction</att> attribute is used to specify a style property that
defines the directionality of an embedding or override according to
the Unicode bidirectional algorithm.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-direction" role="common">
@@ -2916,6 +3551,8 @@
<p diff="add">For the purpose of determining applicability of this style property,
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
span.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must ignore the attribute.</p>
<p>The <att>tts:direction</att> style is illustrated by the following example.</p>
<table id="style-attribute-direction-example-1" role="example">
<caption>Example Fragment – Direction</caption>
@@ -2964,7 +3601,8 @@
<p>The <att>tts:display</att> attribute is used to specify a style property that
defines whether an element is a candidate for layout and composition
in a region.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-display" role="common">
@@ -3096,7 +3734,8 @@
<head>tts:displayAlign</head>
<p>The <att>tts:displayAlign</att> attribute is used to specify a style property that
defines the alignment of block areas in the block progression direction.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-displayAlign" role="common">
@@ -3137,7 +3776,9 @@
</tr>
</tbody>
</table>
-<p/>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>before</code> were specified.</p>
<p>The <att>tts:displayAlign</att> style is illustrated by the following example.</p>
<table id="style-attribute-displayAlign-example-1" role="example">
<caption>Example Fragment – Display Align</caption>
@@ -3211,7 +3852,8 @@
interval.</p>
<p>This style property applies only to a region when the <att>tts:overflow</att>
property for that region has the value <phrase diff="chg"><code>dynamic</code></phrase>.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-dynamicFlow" role="common">
@@ -3250,25 +3892,32 @@
</table>
<p>If the value of this attribute is <code>none</code>, then no
dynamic flow semantics apply.</p>
-<p diff="add">If the value of this attribute is <code>rollUp</code>, then interpret
-this value as a shorthand value equivalent to
+<p diff="add">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) inter(0.433s)</code>.</p>
-<p>If the value of this attribute contains a single
-<loc href="#style-value-flowFunction"><flowFunction></loc>, then that flow function applies equally to
-<emph>fill into</emph>, <emph>reflow within</emph>, and <emph>clear
+<p>If the value of this attribute contains a single <loc
+href="#style-value-flowFunction"><flowFunction></loc>, then that
+flow function applies equally to <emph>fill into</emph><phrase
+diff="del">, <emph>reflow within</emph>,</phrase> and <emph>clear
from</emph> dynamic flow operations.</p>
-<p>If a reflow <code>within()</code> flow function is specified, but
-no clear <code>out()</code> flow function is specified, or vice-versa,
-then the function applies equally to both <emph>reflow within</emph>
-and <emph>clear from</emph> dynamic flow operations.</p>
-<p>If either <code>intra()</code> or <code>inter()</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>
+<p diff="del">If a reflow <code>within()</code> flow function is
+specified, but no clear <code>out()</code> flow function is specified,
+or vice-versa, then the function applies equally to both <emph>reflow
+within</emph> and <emph>clear from</emph> dynamic flow operations.</p>
+<p>If either <code>intra()</code> or <code>inter()</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.</p>
<p>The normative processing model for dynamic flow behavior is
specified in <specref ref="dynamicFlowModel"/>.</p>
+<p diff="add">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 <att>tts:dynamicFlow</att> style is illustrated by the
-following example, and depicted in an <loc href="images/dynamicFlow_RU_animated.svg">SVG Animation</loc>.</p>
+following example, and depicted in an <loc
+href="images/dynamicFlow_RU_animated.svg">SVG Animation</loc>.</p>
<table id="style-attribute-dynamicFlow-example-1" role="example">
<caption>Example Fragment – Dynamic Flow</caption>
<tbody>
@@ -3341,7 +3990,8 @@
<p>The <att>tts:extent</att> attribute is used to specify the
<emph>width</emph> and <emph>height</emph> of a region area
(which may be the root container region).</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-extent" role="common">
@@ -3387,13 +4037,24 @@
<emph>height</emph>.</p>
<p>If the value of this attribute is <code>auto</code>, then the initial value
of the style property must be considered to be the same as the root container extent.
+</p>
+<p>
The root container extent is determined either by a
<att>tts:extent</att> specified on the <el diff="chg">tt</el> element, if
-present, or by the external authoring context, if not present. In the
-former case, if the width and height is expressed in terms of two
+present, or by the external authoring context, if not present.
+<phrase diff="del">In the former case,</phrase><phrase diff="add">If
+<att>tts:extent</att> is specified on the <el>tt</el> element,</phrase>
+<phrase diff="del">if</phrase><phrase diff="add">then</phrase>
+the width and height
+<phrase diff="del">is</phrase><phrase diff="add">must be</phrase>
+expressed in terms of two
<loc href="#style-value-length"><length></loc> specifications,
-then these specifications must be expressed as non-percentage,
+<phrase diff="del">then</phrase><phrase diff="add">and</phrase>
+these specifications must be expressed as non-percentage,
definite lengths using pixel units.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>auto</code> were specified.</p>
<p>The <att>tts:extent</att> style is illustrated by the following example.</p>
<table id="style-attribute-extent-example-1" role="example">
<caption>Example Fragment – Extent</caption>
@@ -3435,7 +4096,8 @@
<p>The <att>tts:fontFamily</att> attribute is used to specify a style property that
defines the font family from which glyphs are selected for glyph areas generated
by content flowed into a region.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-fontFamily" role="common">
@@ -3482,6 +4144,12 @@
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
span<phrase diff="del">, where the value of this style property on the anonymous span is considered to be
<code>inherit</code></phrase>.</p>
+<p diff="add">If a specified font family is not available, then a
+presentation processor must attempt to map the specified font family
+to an available font family that has similar typographic
+characteristics, or, in the absence of such a mapping, it must
+interpret the font family as if the value <code>default</code> were
+specified.</p>
<p>The <att>tts:fontFamily</att> style is illustrated by the following example.</p>
<table id="style-attribute-fontFamily-example-1" role="example">
<caption>Example Fragment – Font Family</caption>
@@ -3538,7 +4206,8 @@
that defines the font size for glyphs that are selected for glyph areas
generated by content flowed into a region, where font size is interpreted as a
scaling transform to the font's design EM square.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-fontSize" role="common">
@@ -3591,6 +4260,9 @@
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
span<phrase diff="del">, where the value of this style property on the anonymous span is considered to be
<code>inherit</code></phrase>.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>1c</code> were specified.</p>
<p>The <att>tts:fontSize</att> style is illustrated by the following example.</p>
<table id="style-attribute-fontSize-example-1" role="example">
<caption>Example Fragment – Font Size</caption>
@@ -3641,7 +4313,8 @@
by content flowed into a region, where the mapping from font
style value to specific font face or style parameterization is not determined
by this specification.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-fontStyle" role="common">
@@ -3687,13 +4360,19 @@
<code>inherit</code></phrase>.</p>
<p>Use of values <code>oblique</code> and <code>reverseOblique</code>
denote a shear and reverse shear transformation (at an unspecified
-angle) in the inline progression dimension. A conformant processor may
-perform such a transform on a font in order to satisfy this authorial
-intent for the purpose of presentation processing. If a specified font
-style is not available or a shear or reverse shear transformation is
-not supported, then the processor must interpret the font style as if
-the value <code>normal</code> were specified for the purpose of
-presentation processing.</p>
+angle) in the inline progression dimension.<phrase diff="del"> A
+conformant processor may perform such a transform on a font in order
+to satisfy this authorial intent for the purpose of presentation
+processing. If a specified font style is not available or a shear or
+reverse shear transformation is not supported, then the processor must
+interpret the font style as if the value <code>normal</code> were
+specified for the purpose of presentation processing.</phrase></p>
+<p diff="add">If a specified font style is not available, then a
+presentation processor must attempt to map the specified font style
+to an available font style that has similar typographic
+characteristics, or, in the absence of such a mapping, it must
+interpret the font style as if the value <code>normal</code> were
+specified.</p>
<p>The <att>tts:fontStyle</att> style is illustrated by the following example.</p>
<table id="style-attribute-fontStyle-example-1" role="example">
<caption>Example Fragment – Font Style</caption>
@@ -3742,7 +4421,8 @@
areas generated by content flowed into a region, where the mapping from font
weight value to specific font face or weight parameterization is not determined
by this specification.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-fontWeight" role="common">
@@ -3784,9 +4464,12 @@
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
span<phrase diff="del">, where the value of this style property on the anonymous span is considered to be
<code>inherit</code></phrase>.</p>
-<p>If a specified font weight is not available, then a conformant
-processor must interpret the font weight as if the value <code>normal</code> were
-specified for the purpose of presentation processing.</p>
+<p diff="chg">If a specified font weight is not available, then a
+presentation processor must attempt to map the specified font weight
+to an available font weight that has similar typographic
+characteristics, or, in the absence of such a mapping, it must
+interpret the font weight as if the value <code>normal</code> were
+specified.</p>
<p>The <att>tts:fontWeight</att> style is illustrated by the following example.</p>
<table id="style-attribute-fontWeight-example-1" role="example">
<caption>Example Fragment – Font Weight</caption>
@@ -3833,7 +4516,8 @@
<head>tts:lineHeight</head>
<p>The <att>tts:lineHeight</att> attribute is used to specify a style property that
defines the inter-baseline separation between line areas generated by content flowed into a region.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-lineHeight" role="common">
@@ -3879,6 +4563,9 @@
<p>If specified as a <loc
href="#style-value-length"><length></loc>, then the length must
be non-negative.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>normal</code> were specified.</p>
<p>The <att>tts:lineHeight</att> style is illustrated by the following example.</p>
<table id="style-attribute-lineHeight-example-1" role="example">
<caption>Example Fragment – Line Height</caption>
@@ -3929,13 +4616,16 @@
<div3 id="style-attribute-opacity">
<head>tts:opacity</head>
<p>The <att>tts:opacity</att> attribute is used to specify a style property that
-defines the opacity (or transparency) of marks associated with a region (such as
+defines the opacity (or transparency) of marks associated with a
+region<phrase diff="del"> (such as
a region's background color) or marks associated with areas generated by a given
-content element to which opacity applies.</p>
-<p>When presented onto a visual medium, the opacity of the affacted
-element is applied uniformly and on a linear scale to all marks produced by the affected
-element (and its descendants).</p>
-<p>This attribute may be specified by any style specification element or content element
+content element to which opacity applies</phrase>.</p>
+<p>When presented onto a visual medium, the opacity of the <phrase
+diff="chg">region</phrase> is applied uniformly and on a linear scale
+to all marks produced by <phrase diff="chg">content targeted to the
+region</phrase>.</p>
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-opacity" role="common">
@@ -3974,8 +4664,9 @@
</tr>
</tbody>
</table>
-<p>An <loc href="#style-value-alpha"><alpha></loc> value greater than 1.0 must be considered equivalent
-to an <loc href="#style-value-alpha"><alpha></loc> value of 1.0.</p>
+<p>An <loc href="#style-value-alpha"><alpha></loc> value greater
+than 1.0 must be considered equivalent to an <loc
+href="#style-value-alpha"><alpha></loc> value of 1.0.</p>
<p>The <att>tts:opacity</att> style is illustrated by the following example.</p>
<table id="style-attribute-opacity-example-1" role="example">
<caption>Example Fragment – Opacity</caption>
@@ -4047,7 +4738,8 @@
<emph>x</emph> and <emph>y</emph> coordinates of the origin of a
region area with respect to the origin of the root container extent,
if specified, or the external authoring context, if not specified.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-origin" role="common">
@@ -4091,6 +4783,9 @@
<p>If the value of this attribute is <code>auto</code>, then the initial value
of the style property must be considered to be the same as the root container origin.
The root container origin is determined by the external authoring context.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>auto</code> were specified.</p>
<p>The <att>tts:origin</att> style is illustrated by the following example.</p>
<table id="style-attribute-origin-example-1" role="example">
<caption>Example Fragment – Origin</caption>
@@ -4132,7 +4827,8 @@
<p>The <att>tts:overflow</att> attribute is used to specify a style property that
defines whether a region area is clipped or not if the descendant areas of the region overflow
its extent.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-overflow" role="common">
@@ -4173,7 +4869,9 @@
</table>
<p>If the value of this attribute is <code>visible</code>, then content should
not be clipped outside of the affected region, and region composition and layout
-must be performed as if the region's width and height were infinite, but with
+must be performed as if the region's width and height were
+<phrase diff="del">infinite</phrase><phrase diff="add">unconstrained</phrase>,
+but with
a well-defined origin. If the value is <code>hidden</code>, then content should
be clipped outside of the affected region.</p>
<note role="explanation">
@@ -4188,6 +4886,9 @@
of the <att>tts:dynamicFlow</att> style property; in this case, the
semantics of the <att>tts:dynamicFlow</att> apply whether or not the
affected region has overflowed.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>hidden</code> were specified.</p>
<p>The <att>tts:overflow</att> style is illustrated by the following example.</p>
<table id="style-attribute-overflow-example-1" role="example">
<caption>Example Fragment – Overflow</caption>
@@ -4259,7 +4960,8 @@
<p>The <att>tts:padding</att> attribute is used to specify padding (or inset)
space on all sides of a region area<phrase diff="del"> or a content area produced by a content
element</phrase>.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-padding" role="common">
@@ -4277,7 +4979,7 @@
</tr>
<tr>
<td><emph>Initial:</emph></td>
-<td><code>0</code></td>
+<td><code>0<phrase diff="add">px</phrase></code></td>
</tr>
<tr>
<td><emph>Applies to:</emph></td>
@@ -4308,6 +5010,9 @@
to the after edge.
If four <loc href="#style-value-length"><length></loc> specifications are provided, then they apply to before, end,
after, and start edges, respectively.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>0px</code> were specified.</p>
<p>The <att>tts:padding</att> style is illustrated by the following example.</p>
<table id="style-attribute-padding-example-1" role="example">
<caption>Example Fragment – Padding</caption>
@@ -4360,7 +5065,8 @@
<p>The <att>tts:showBackground</att> attribute is used to specify
constraints on when the background color of a region is intended to be
presented.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-showBackground" role="common">
@@ -4403,6 +5109,9 @@
processing on a visual medium; if the value is <code>whenActive</code>,
then the background color of a region is rendered only when some
content is selected into the region.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>always</code> were specified.</p>
<p>The <att>tts:showBackground</att> style is illustrated by the following example.</p>
<table id="style-attribute-showBackground-example-1" role="example">
<caption>Example Fragment – Show Background</caption>
@@ -4456,7 +5165,8 @@
<p>The <att>tts:textAlign</att> attribute is used to specify a style property that
defines how inline areas are aligned within a containing block area in the inline progression
direction.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-textAlign" role="common">
@@ -4497,6 +5207,9 @@
</tr>
</tbody>
</table>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>start</code> were specified.</p>
<p>The <att>tts:textAlign</att> style is illustrated by the following example.</p>
<table id="style-attribute-textAlign-example-1" role="example">
<caption>Example Fragment – Text Align</caption>
@@ -4552,7 +5265,8 @@
<p>The <att>tts:textDecoration</att> attribute is used to specify a style property that
defines a text decoration effect to apply to glyph areas or other inline
areas that are generated by content flowed into a region.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-textDecoration" role="common">
@@ -4606,6 +5320,9 @@
<p diff="add">For the purpose of determining applicability of this
style property, each character child of a <el>p</el> element is
considered to be enclosed in an anonymous span.</p>
+<p diff="add">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 <att>tts:textDecoration</att> style is illustrated by the following example.</p>
<table id="style-attribute-textDecoration-example-1" role="example">
<caption>Example Fragment – Text Decoration</caption>
@@ -4623,15 +5340,14 @@
</region>
...
<p region="r1">
- The sea was wet<span <phrase role="strong">tts:textDecoration="noUnderline"</phrase>> as </span>wet<span
- <phrase role="strong">tts:textDecoration="noUnderline"</phrase>>
- could be,<br/>
- The sand was dry as dry.<br/>
- <span <phrase role="strong">tts:textDecoration="lineThrough"</phrase>>There weren't any</span>
- You
- <span <phrase role="strong">tts:textDecoration="lineThrough"</phrase>>couldn't</span>
- could not see a cloud<br/>
- Because no cloud was in the sky.
+ The sea was wet<span <phrase role="strong">tts:textDecoration="noUnderline"</phrase>> as </span>wet
+ <span <phrase role="strong">tts:textDecoration="noUnderline"</phrase>>
+ could be,<br/>
+ The sand was dry as dry.<br/>
+ <span <phrase role="strong">tts:textDecoration="lineThrough"</phrase>>There weren't any</span>
+ You <span <phrase role="strong">tts:textDecoration="lineThrough"</phrase>>couldn't</span>
+ could not see a cloud<br/>
+ Because no cloud was in the sky.
</span>
</p>
</eg>
@@ -4659,7 +5375,8 @@
<p>The <att>tts:textOutline</att> attribute is used to specify a style property that
defines a text outline effect to apply to glyphs that are selected for glyph areas generated
by content flowed into a region.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-textOutline" role="common">
@@ -4709,6 +5426,9 @@
present, the computed value of the <att>tts:color</att> applies. The first
<emph>length</emph> term denotes the outline thickness and the second length
term, if present, indicates the blur radius.</p>
+<p diff="add">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 <att>tts:textOutline</att> style is illustrated by the following
example.</p>
<table id="style-attribute-textOutline-example-1" role="example">
@@ -4755,7 +5475,8 @@
<p>The <att>tts:unicodeBidi</att> attribute is used to specify a style property that
defines a directional embedding or override according to
the Unicode bidirectional algorithm.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-unicodeBidi" role="common">
@@ -4800,6 +5521,9 @@
<p diff="add">For the purpose of determining applicability of this style property,
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
span.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>normal</code> were specified.</p>
<p>The <att>tts:unicodeBidi</att> style is illustrated by the following example.</p>
<table id="style-attribute-unicodeBidi-example-1" role="example">
<caption>Example Fragment – Unicode Bidirectionality</caption>
@@ -4848,7 +5572,8 @@
<p>The <att>tts:visibility</att> attribute is used to specify a style property that
defines whether generated areas are visible or not when rendered on a visual
presentation medium.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-visibility" role="common">
@@ -4901,6 +5626,9 @@
span.</p>
<p>The <att>tts:visibility</att> style has no affect on content layout or
composition, but merely determines whether composed content is visible or not.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>visible</code> were specified.</p>
<p>The <att>tts:visibility</att> style is illustrated by the following example.</p>
<table id="style-attribute-visibility-example-1" role="example">
<caption>Example Fragment – Visibility</caption>
@@ -4971,7 +5699,8 @@
<p>The <att>tts:wrapOption</att> attribute is used to specify a style property that
defines whether or not automatic line wrapping (breaking) applies within the context of
the affected element.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-wrapOption" role="common">
@@ -5013,6 +5742,9 @@
each character child of a <el>p</el> element is considered to be enclosed in an anonymous
span<phrase diff="del">, where the value of this style property on the anonymous span is considered to be
<code>inherit</code></phrase>.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>wrap</code> were specified.</p>
<p>The <att>tts:wrapOption</att> style is illustrated by the following example.</p>
<table id="style-attribute-wrapOption-example-1" role="example">
<caption>Example Fragment – Wrap Option</caption>
@@ -5060,7 +5792,8 @@
<p>The <att>tts:writingMode</att> attribute is used to specify a style property that
defines the block and inline progression directions to be used for the purpose of
stacking block and inline areas within a region area.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-writingMode" role="common">
@@ -5103,6 +5836,9 @@
</tr>
</tbody>
</table>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>lrtb</code> were specified.</p>
<p>The <att>tts:writingMode</att> style is illustrated by the following example.</p>
<table id="style-attribute-writingMode-example-1" role="example">
<caption>Example Fragment – Writing Mode</caption>
@@ -5166,7 +5902,8 @@
<head>tts:zIndex</head>
<p>The <att>tts:zIndex</att> attribute is used to specify a style property that
defines the front-to-back ordering of region areas in the case that they overlap.</p>
-<p>This attribute may be specified by any style specification element or content element
+<p>This attribute may be specified by any
+<phrase diff="chg">element type</phrase>
that permits use of attributes in the TT Style Namespace; however, this attribute applies
as a style property only to those element types indicated in the following table.</p>
<table id="style-property-details-zIndex" role="common">
@@ -5212,6 +5949,9 @@
<p>The semantics of the value <code>auto</code> are those defined by
<bibref ref="xsl11"/>, § 7.28.9, where the <el>tt</el> element
is considered to establish the root stacking context.</p>
+<p diff="add">If a specified value of this attribute is not supported,
+then a presentation processor must interpret the attribute as if the
+value <code>auto</code> were specified.</p>
<p>The <att>tts:zIndex</att> style is illustrated by the following example.</p>
<table id="style-attribute-zIndex-example-1" role="example">
<caption>Example Fragment – Z Index</caption>
@@ -5336,6 +6076,9 @@
then it must be interpreted as equal to 0.0; similarly, if the value
represented is greater than 1.0, then it must be interpreted as
1.0.</phrase></p>
+<p diff="add">If a presentation processor does not support a specific,
+valid opacity value, then it must interpret it as being equal to the
+closest supported value.</p>
</div3>
<div3 id="style-value-color">
<head><color></head>
@@ -5385,11 +6128,14 @@
the composition function.</p>
<note role="clarification">
<p>The use of <bibref ref="srgb"/> for the stated semantics of
-composition is not mean to prevent an actual processor from using some
+composition is not mean<phrase diff="add">t</phrase> to prevent an actual processor from using some
other color space either for internal or external purposes. For
example, a presentation processor may ultimately convert the SRGB values
used here to the YUV color space for rendition on a television device.</p>
</note>
+<p diff="add">If a presentation processor does not support a specific,
+valid color or alpha value, then it must interpret it as being equal
+to the closest supported value.</p>
</div3>
<div3 id="style-value-digit">
<head><digit></head>
@@ -5464,10 +6210,11 @@
</div3>
<div3 id="style-value-flowFunction">
<head><flowFunction></head>
-<p>A <flowFunction> expression specifies a unit of content to be dynamic
-flowed into, within, and from a region according to an optional
-dynamic flow style, flow transition effect, and flow transition effect
-style.</p>
+<p>A <flowFunction> expression specifies a unit of content to be
+dynamic flowed into<phrase diff="del">, within,</phrase> and <phrase
+diff="chg">out of</phrase> a region according to an optional dynamic
+flow style<phrase diff="del">, flow transition effect, and flow
+transition effect style</phrase>.</p>
<table id="flowFunction-style-expression-syntax" role="syntax">
<caption>Syntax Representation – <flowFunction></caption>
<tbody>
@@ -5475,8 +6222,8 @@
<td>
<eg xml:space="preserve">
<flowFunction>
- : "in(" flowArguments ")"
- | "within(" flowArguments ")"
+ : "in(" flowArguments ")"<phrase diff="del">
+ | "within(" flowArguments ")"</phrase>
| "out(" flowArguments ")"
flowArguments
@@ -5494,8 +6241,8 @@
flowStyle
: "jump"
- | "smooth"
- | "fade"
+ | "smooth"<phrase diff="del">
+ | "fade"</phrase>
| extensionToken<phrase diff="del">
flowTransition
@@ -5514,11 +6261,14 @@
</tr>
</tbody>
</table>
+
<p>Dynamic flow can be specified independently for flowing content
-into its region, flowing it within its region, and flowing it out of
-its region. These three phases of dynamic flow are specified using the
-<code>in()</code>, <code>within()</code>, and <code>out()</code> flow
-functions respectively.</p>
+into its region<phrase diff="del">, flowing it within its
+region,</phrase> and flowing it out of its region. These <phrase
+diff="chg">two</phrase> phases of dynamic flow are specified using the
+<code>in()</code><phrase diff="del">, <code>within()</code>,</phrase>
+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="del"><code>pixel</code>, </phrase><code>glyph</code>,
<code>inline</code>, <code>line</code>, and <code>block</code>, the
@@ -5542,21 +6292,25 @@
a sequence of one or more characters that are not interpreted as an
XML whitespace character.</p></item>
</olist>
-<p>When a flow unit is flowed into, within, or out of its region, the
-manner by which the unit is flowed is controlled by the optional
-<code>flowStyle</code> argument of the relevant flow function. If the
-flow style is specified as <code>jump</code>, or if no flow style is
-specified, then the flow unit is instantaneously transitioned into,
-within, or out of the region. If the flow style is
-<code>smooth</code>, then the flow unit is smoothly transitioned by
-means of pixel based exposure, movement, or hiding, respectively. If
-the flow style is <code>fade</code>, then the flow unit is faded into
-or out of the region by continuously incrementing or decrementing the
-alpha component of the affected content.</p>
+
+<p>When a flow unit is flowed into<phrase diff="del">,
+within,</phrase> or out of its region, the manner by which the unit is
+flowed is controlled by the optional <code>flowStyle</code> argument
+of the relevant flow function. If the flow style is specified as
+<code>jump</code>, or if no flow style is specified, then the flow
+unit is instantaneously transitioned into, within, or out of the
+region. If the flow style is <code>smooth</code>, then the flow unit
+is smoothly transitioned by means of pixel based exposure, movement,
+or hiding, respectively.<phrase diff="del"> If the flow style is
+<code>fade</code>, then the flow unit is faded into or out of the
+region by continuously incrementing or decrementing the alpha
+component of the affected content.</phrase></p>
+
<p diff="add">If a presentation processor that supports dynamic flow
-does not support either or both the <code>smooth</code> or
-<code>fade</code> flow styles, then these flow styles must be
-interpreted as if <code>jump</code> flow style were specified.</p>
+does not the <code>smooth</code> flow style, then this flow style must
+be interpreted as if the <code>jump</code> flow style were
+specified.</p>
+
<p diff="del">In addition to the primary flow style, an optional flow transition
effect and flow transition effect style may be specified, in which
case the transition effect is additively (and simultaneously) applied
@@ -5650,6 +6404,10 @@
or <code>monospaceSerif</code>. The generic family names <code>sansSerif</code>
and <code>serif</code> are to be interpreted as equivalent to <code>proportionalSansSerif</code>
and <code>proportionalSerif</code>, respectively.</p>
+<p diff="add">If the generic family name <code>default</code> is specified (or implied by
+an initial value), then its typographic characteristics is considered to be implementation
+dependent; however, it is recommended that this default font family be mapped to
+an monospaced, sans-serif font.</p>
</div3>
<div3 id="style-value-hexDigit">
<head><hexDigit></head>
@@ -6039,7 +6797,6 @@
using:
</p>
<ulist>
-<!-- [OMIT <item><p>explicit style inheritance</p></item> OMIT] -->
<item><p><loc href="#semantics-style-inheritance-content">content style inheritance</loc></p></item>
<item><p><loc href="#semantics-style-inheritance-content">region style inheritance</loc></p></item>
</ulist>
@@ -6051,60 +6808,6 @@
the original form in order to facilitate region inheritance
processing.</p>
</note>
-<!-- [OMIT
-<div4 id="semantics-style-inheritance-explicit" diff="add">
-<head>Explicit Style Inheritance</head>
-<p>If a style property is associated with a content element by means
-of <specref ref="semantics-style-association-inline"/>, the element is
-not a <el>body</el> element, and the specified value of the property
-is <code>inherit</code>, then the value of the style property is
-considered to be the value of the same named style property in the
-computed style set of the element's immediate ancestor element within
-the applicable intermediate synchronic document.</p>
-<p>When determining the value of an explicitly inherited style from the
-computed style set of an element's immediate ancestor, if the style
-property is not present in the computed style set (i.e., because it is
-not an inheritable style property and it is not otherwise specified or
-associated with the immediate ancestor), then the initial value of
-the style property must be used.</p>
-<p>It is considered an error to specify <code>inherit</code> as the
-value of a style property attribute in any context other than an inline
-style on the following element types: <el>div</el>, <el>p</el>, <el>span</el>.</p>
-<table id="style-inheritance-example-1" role="example">
-<caption>Example – Explicit Style Inheritance</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-<p tts:textOutline="2px">
- <span tts:textOutline=<phrase role="strong">"inherit"</phrase>>Outlined Text</span>
- <span>Unoutlined Text</span>
- <span tts:textOutline=<phrase role="strong">"inherit"</phrase>>Outlined Text</span>
-</p>
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<note role="explanation">
-<p>In the above example, <att>tts:textOutline</att> is explicitly
-inherited from the ancestor <el>p</el> element. Since
-<att>tts:textOutline</att> is not an inheritable style property, the
-usage shown here permits the <el>span</el> children to explicitly
-inherit from their common ancestor.</p>
-</note>
-<p/>
-<ednote>
-<name>GA</name>
-<date>2009-04-12</date>
-<edtext>The example shown above appears to be the only case (of all
-properties) where significant semantic use may be made of explicit
-inheritance. Given the very limited utility of this usage, it is
-probably worthwhile removing the <code>inherit</code> value and
-explicit inheritance altogether.</edtext>
-</ednote>
-</div4>
-OMIT] -->
<div4 id="semantics-style-inheritance-content">
<head>Content Style Inheritance</head>
<p>Style properties are inherited from ancestor content elements
@@ -6212,18 +6915,6 @@
by an element or anonymous span are referred to as <emph>specified values</emph>. The
set of all specified style properties of a given element is referred to
as the <emph>specified style set</emph> of that element.</p>
-<!-- [OMIT
-<p>Specified values are further distinguished as explicit or
-implicit. Specified values assigned to an element by means of <specref
-ref="semantics-style-association"/> or
-<specref ref="semantics-style-inheritance-explicit"/>
-are considered to be
-<emph>explicitly</emph> specified values. In contrast, specified values
-assigned to an element by means of
-<specref ref="semantics-style-inheritance-content"/> or
-<specref ref="semantics-style-inheritance-region"/>
-are considered to be
-<emph>implicitly</emph> specified values.</p> OMIT] -->
</div4>
<div4 id="semantics-style-resolved-value-category-computed">
<head>Computed Values</head>
@@ -6307,7 +6998,7 @@
<td>
<eg xml:space="preserve">
[
- ["http://www.w3.org/2006/10/ttaf1#style", "color"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
["specified", <emph>color</emph>, "red"]
]
</eg>
@@ -6336,19 +7027,19 @@
<eg xml:space="preserve">
{
[
- ["http://www.w3.org/2006/10/ttaf1#style", "backgroundColor"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "backgroundColor"],
["specified", <emph>color</emph>, 0x00FF00 ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "color"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
["specified", <emph>color</emph>, "red" ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "fontSize"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "fontSize"],
["specified", <emph>length</emph>, "1c" ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "lineHeight"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "lineHeight"],
["specified", <emph>length</emph>, "117%" ]
]
}
@@ -6368,19 +7059,19 @@
<eg xml:space="preserve">
{
[
- ["http://www.w3.org/2006/10/ttaf1#style", "backgroundColor"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "backgroundColor"],
["specified", <emph>color</emph>, 0x00FF00 ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "color"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "color"],
["computed", <emph>color</emph>, 0xFF0000 ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "fontSize"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "fontSize"],
["computed", <emph>length</emph>, "24px" ]
],
[
- ["http://www.w3.org/2006/10/ttaf1#style", "lineHeight"],
+ ["http://www.w3.org/2006/10/ttaf1#styling", "lineHeight"],
["computed", <emph>length</emph>, "28px" ]
]
}
@@ -6446,32 +7137,8 @@
<item><p><phrase role="strong">[inline styling]</phrase> for each
style property <emph>P</emph> expressed as a specified styling
attribute of <emph>E</emph>,
-<!-- [OMIT where the value of <emph>P</emph> is not
-<code>inherit</code>, OMIT] -->
merge <emph>P</emph> into the specified style
set of <emph>E</emph>, <emph>SSS(E)</emph>;</p></item>
-<!-- [OMIT
-<item><p><phrase role="strong">[explicit inheritance]</phrase> if the
-element type of <emph>E</emph> is a content element type, then for
-each style property <emph>P</emph> expressed as a specified styling
-attribute of <emph>E</emph>, where the value of <emph>P</emph> is
-<code>inherit</code>, perform the following ordered sub-steps:</p>
-<olist>
-<item><p>initialize <emph>P′</emph> to the result of looking up the
-value of <emph>P</emph> in the computed style set of the immediate
-ancestor element of <emph>E</emph>, i.e.,
-<emph>CSS(PARENT(E))</emph>;</p></item>
-<item><p>if <emph>P′</emph> is not defined, i.e., because the above
-lookup failed to return a value, then set <emph>P′</emph> to the
-initial value of property <emph>P</emph>, where the initial value of a
-property is determined according to the specific property definition
-found above in <specref
-ref="styling-attribute-vocabulary"/>;</p></item>
-<item><p>if the value of <emph>P′</emph> is not undefined, then
-merge <emph>P′</emph> into the specified style set of
-<emph>E</emph>, <emph>SSS(E)</emph>;</p></item>
-</olist>
-</item> OMIT] -->
<item>
<p><phrase role="strong">[implicit inheritance]</phrase> if the
element type of <emph>E</emph> is not the styling element type
@@ -6669,7 +7336,7 @@
</tr>
</tbody>
</table>
-<p>The declared value of an inline style attribute on a <el>region</el>
+<p diff="del">The declared value of an inline style attribute on a <el>region</el>
element must not be <code>inherit</code>.</p>
<p diff="del">A <el>region</el> element is considered to define a computed style
specification set, where the set is determined using the
@@ -6752,9 +7419,9 @@
href="#metadata-attribute-role"><att>ttm:role</att></loc> attribute is
specified on a <el>region</el> element, then it must adhere to the
value syntax defined by <specref
-ref="metadata-attribute-role-syntax"/>, and where the role identified
-by this attribute expresses the semantic role of the region
-independently from the semantic role of any content targeted to
+ref="metadata-attribute-role-syntax"/>, and where the role(s) identified
+by this attribute expresses the semantic role(s) of the region
+independently from the semantic role(s) of any content targeted to
(associated with) the region.</p>
</div3>
</div2>
@@ -6796,7 +7463,7 @@
</p>
<div3 id="semantics-default-region" diff="add">
<head>Default Region</head>
-<p>If a TT AF document instance does not specify a
+<p>If a DFXP document instance does not specify a
<loc href="#layout-vocabulary-region"><el>region</el></loc> element,
then a <emph>default region</emph> is implied with the following characteristics:</p>
<ulist>
@@ -7018,6 +7685,18 @@
set associated with each original TT AF content element;</p>
</item>
<item>
+<p diff="add">for the resulting <el>fo:block</el> formatting object
+produced in the previous step that corresponds to the <el>body</el>
+element, synthesize and append to the end of its children an empty
+<el>fo:block</el> with the following attributes:
+<att>space-after.optimum</att>, <att>space-after.maximum</att>, and
+<att>space-after.conditionality</att>, where the value of the former
+two attributes is the height or width of the containing
+<el>fo:block-container</el> element, whichever of these is designated
+as the block progression dimension, and where the value of the last is
+<code>retain</code>;</p>
+</item>
+<item>
<p>for each <el>span</el> element that is not
associated with a <att>tts:display</att> style property with the value
<code>none</code> and for each anonymous
@@ -7064,6 +7743,14 @@
requires presentation on a visual medium, then apply the formatting semantics
prescribed by <bibref ref="xsl11"/> in order to produce an XSL FO area tree that
may then be subsequently rendered onto the visual medium.</p>
+<note role="elaboration" diff="add">
+<p>In the XSL FO area tree produced by formatting
+<emph>DOC<sub>FO</sub></emph>, the <code>page-viewport-area</code>,
+which is generated by <code>fo:page-sequence</code> element by
+reference to the sole generated <code>fo:simple-page-master</code>
+element, corresponds to the <emph>root container region</emph> defined
+above in <specref ref="definitions"/>.</p>
+</note>
<note>
<p>Due to the possible presence of TT AF style properties
or style property values in a given DFXP document instance for which
@@ -7451,7 +8138,8 @@
<div3 id="animation-vocabulary-set">
<head>set</head>
<p>The <el>set</el> element is used as a child element of a content
-element in order to express a discrete change of some style parameter value
+element<phrase diff="add"> or a <el>region</el> element</phrase>
+in order to express a discrete change of some style parameter value
that applies over some time interval.</p>
<p>The <el>set</el> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group.</p>
@@ -7481,6 +8169,72 @@
<p>The use of multiple <el>set</el> element children may be used to effect fade and
position transitions.</p>
</note>
+<p diff="add">An example of using the <el>set</el> element to animate content
+styling is illustrated below:</p>
+<table id="animation-vocabulary-set-example-1" role="example">
+<caption><phrase diff="add">Example Fragment – Content Style Animation</phrase></caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<phrase diff="add">...
+<p dur="5s" tts:color="yellow">
+<phrase role="strong"><set begin="1s" dur="1s" tts:color="red"/></phrase>
+<phrase role="strong"><set begin="2s" dur="1s" tts:color="green"/></phrase>
+<phrase role="strong"><set begin="3s" dur="1s" tts:color="red"/></phrase>
+Text with Flashing Colors!
+</p>
+...</phrase>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<note role="explanation" diff="add">
+<p>In the above example, the foreground color of the content "Text
+with Flashing Colors" is animated from yellow, to red, to green, to
+red, then back to yellow over a 5 second period.</p>
+</note>
+
+<p diff="add">An example of using the <el>set</el> element to animate region
+styling is illustrated below:</p>
+<table id="animation-vocabulary-set-example-2" role="example">
+<caption><phrase diff="add">Example Fragment – Region Style Animation</phrase></caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<phrase diff="add"><tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"
+ xmlns:ttp="http://www.w3.org/2006/10/ttaf1#parameter"
+ xmlns:tts="http://www.w3.org/2006/10/ttaf1#styling"
+ ttp:cellResolution="40 16">
+ <head>
+ <layout>
+ <region xml:id="r1" timeContainer="seq">
+ <phrase role="strong"><set dur="10s" tts:origin=" 8c 14c"/></phrase>
+ <phrase role="strong"><set dur="2s" tts:origin=" 2c 2c"/></phrase>
+ <phrase role="strong"><set dur="3s" tts:origin=" 8c 14c"/></phrase>
+ <phrase role="strong"><set dur="2s" tts:origin="14c 4c"/></phrase>
+ <phrase role="strong"><set dur="10s" tts:origin=" 8c 14c"/></phrase>
+ <style tts:extent="24c 2c"/>
+ </region>
+ </layout>
+ </head>
+ <body region="r1">...</body>
+</tt></phrase>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<note role="explanation" diff="add">
+<p>In the above example, the root container region is divided into a
+cell grid of 40 columns and 16 rows. A region, <code>r1</code>, with
+dimensions of 24 columns and 2 rows is then positioned within the
+root container region, with its position varying over time in order to
+create an effect of moving the region, which may be desirable so as
+to avoid obscuring characters in an underlying video with captions.</p>
+</note>
<note role="derivation">
<p>The semantics of the <el>set</el> element
are based upon that defined by <bibref ref="smil21"/>,
@@ -7499,7 +8253,8 @@
<p>This section specifies the <emph>metadata</emph> matter of the core
vocabulary catalog, where
metadata is to be understood as a separable layer of information that applies to
-content, style, layout, timing, and even metadata itself, where the information
+<phrase diff="add">parameters, </phrase>content,
+style, layout, timing, and even metadata itself, where the information
represented by metadata takes one of two forms: (1) metadata defined by this
specification for standardized use in a document instance, and (2) arbitrary
metadata defined outside of the scope of this specification, whose use and
@@ -7526,8 +8281,12 @@
information.</p>
<p>Metadata information may be expressed by a <el>metadata</el> element
in one of two (non-mutually exclusive) manners: (1) by specifying one
-or more metadata attributes on the element, and (2) by specifying one
-or more <el>metadata</el> child elements that express metadata. Both types of metadata
+or more metadata attributes on the<phrase diff="add"> <el>metadata</el></phrase>
+element, and (2) by specifying one
+or more
+<phrase diff="del"><el>metadata</el> </phrase>child elements
+<phrase diff="add">in the <el>metadata</el> element</phrase>
+that express metadata. Both types of metadata
are referred to in this document as <emph>metadata items</emph>.</p>
<table id="elt-syntax-metadata" role="syntax">
<caption>XML Representation – Element Information Item: metadata</caption>
@@ -7556,6 +8315,75 @@
for the <el>body</el> element. See specific element vocabulary
definitions for any constraints that apply to such usage.</p>
</note>
+<p diff="add">The use of document metadata is illustrated by the following example.</p>
+<table id="metadata-vocabulary-metadata-example-1" role="example">
+<caption><phrase diff="add">Example Fragment – Document Metadata</phrase></caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<phrase diff="add">...
+<head>
+ <metadata xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
+ <ttm:title>Document Metadata Example</ttm:title>
+ <ttm:desc>This document employs document metadata.</ttm:desc>
+ </metadata>
+</head>
+...</phrase>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<p/>
+<p diff="add">The use of element metadata is illustrated by the following example.</p>
+<table id="metadata-vocabulary-metadata-example-2" role="example">
+<caption><phrase diff="add">Example Fragment – Element Metadata</phrase></caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<phrase diff="add">...
+<div>
+ <metadata xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
+ <ttm:title>Chapter 6 – Sherlock Holmes Gives a Demonstration</ttm:title>
+ <ttm:desc>Holmes shows Watson how the murderer entered the window.</ttm:desc>
+ </metadata>
+</div>
+...</phrase>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<p/>
+<p diff="add">The use of metadata attribute items is illustrated by the following example.</p>
+<table id="metadata-vocabulary-metadata-example-3" role="example">
+<caption><phrase diff="add">Example Fragment – Metadata Attribute Items</phrase></caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<phrase diff="add">...
+<div xmlns:ext="http://foo.bar.baz/ttaf1#metadata">
+ <metadata ext:ednote="remove this division prior to publishing"/>
+</div>
+...</phrase>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<note role="explanation" diff="add">
+<p>In the above example, a global attribute from a foreign (external)
+namespace is used to express a metadata attribute that applies
+semantically to the containing <el>div</el> element. Note that the
+attribute may also be expressed directly on the <el>div</el> element;
+however, in this case the author wishes to segregate certain metadata
+attributes by expressing them indirectly on <el>metadata</el>
+elements.</p>
+</note>
+<p/>
</div3>
<div3 id="metadata-vocabulary-title">
<head>ttm:title</head>
@@ -7582,6 +8410,9 @@
<note role="elaboration">
<p>No specific use of the <el>ttm:title</el> element is defined by this specification.</p>
</note>
+<p diff="add">Examples of the <att>ttm:name</att> element are shown above in
+<specref ref="metadata-vocabulary-metadata-example-1"/> and
+<specref ref="metadata-vocabulary-metadata-example-2"/>.</p>
</div3>
<div3 id="metadata-vocabulary-desc">
<head>ttm:desc</head>
@@ -7608,6 +8439,9 @@
<note role="elaboration">
<p>No specific use of the <el>ttm:desc</el> element is defined by this specification.</p>
</note>
+<p diff="add">Examples of the <att>ttm:desc</att> element are shown above in
+<specref ref="metadata-vocabulary-metadata-example-1"/> and
+<specref ref="metadata-vocabulary-metadata-example-2"/>.</p>
</div3>
<div3 id="metadata-vocabulary-copyright">
<head>ttm:copyright</head>
@@ -7688,6 +8522,54 @@
agents may be specified (and referenced) wherein different definitions of the
character specify different actors.</p>
</note>
+<p diff="add">The use of agent metadata is illustrated by the following example.</p>
+<table id="metadata-vocabulary-agent-example-1" role="example">
+<caption><phrase diff="add">Example Fragment – Agent Metadata</phrase></caption>
+<tbody>
+<tr>
+<td>
+<eg xml:space="preserve">
+<phrase diff="add">
+<tt xml:lang="en" xmlns="http://www.w3.org/2006/10/ttaf1" xmlns:ttm="http://www.w3.org/2006/10/ttaf1#metadata">
+ <head>
+ <phrase role="strong"><ttm:agent xml:id="connery" type="person"></phrase>
+ <ttm:name type="family">Connery</ttm:name>
+ <ttm:name type="given">Thomas Sean</ttm:name>
+ <ttm:name type="alias">Sean</ttm:name>
+ <ttm:name type="full">Sir Thomas Sean Connery</ttm:name>
+ <phrase role="strong"></ttm:agent></phrase>
+ <phrase role="strong"><ttm:agent xml:id="bond" type="character"></phrase>
+ <ttm:name type="family">Bond</ttm:name>
+ <ttm:name type="given">James</ttm:name>
+ <ttm:name type="alias">007</ttm:name>
+ <ttm:actor agent="connery"/>
+ <phrase role="strong"></ttm:agent></phrase>
+ </head>
+ <body>
+ <div>
+ ...
+ <p <phrase role="strong">ttm:agent="bond"</phrase>>I travel, a sort of licensed troubleshooter.</p>
+ ...
+ </div>
+ </body>
+</tt>
+</phrase>
+</eg>
+</td>
+</tr>
+</tbody>
+</table>
+<note role="explanation" diff="add">
+<p>In the above example, two agents, a real (person) agent, Sean
+Connery, and a fictitious (character) agent, James Bond, are defined,
+where the latter is linked to the former by means of the a
+<el>ttm:actor</el> element. A reference is then made from content (the
+<el>p</el> element) to the character agent associated with
+(responsible for producing) that content. Note that in this example
+the <el>ttm:agent</el> metadata items are specified as immediate
+children of the document's <el>head</el> element rather than being
+placed in a container <el>metadata</el> element.</p>
+</note>
</div3>
<div3 id="metadata-vocabulary-name">
<head>ttm:name</head>
@@ -7723,6 +8605,8 @@
</ulist>
<p>The relationship between the type of a name and the syntactic expression of the name
is not defined by this specification.</p>
+<p diff="add">Two examples of the <el>ttm:name</el> element are shown above in
+<specref ref="metadata-vocabulary-agent-example-1"/>.</p>
</div3>
<div3 id="metadata-vocabulary-actor">
<head>ttm:actor</head>
@@ -7750,6 +8634,8 @@
<p>The <att>agent</att> attribute of a <el>ttm:actor</el> element must
reference a <el>ttm:agent</el> element that denotes the person,
group, or organization acting the part of a character.</p>
+<p diff="add">An example of the <el>ttm:actor</el> element is shown above in
+<specref ref="metadata-vocabulary-agent-example-1"/>.</p>
</div3>
</div2>
<div2 id="metadata-attribute-vocabulary">
@@ -7767,24 +8653,37 @@
<div3 id="metadata-attribute-agent">
<head>ttm:agent</head>
<p>The <att>ttm:agent</att> attribute takes an <code>IDREFS</code>
-value, and is used with certain content elements to designate the agent that performs
-or is involved in the performance of the content.</p>
-<p>If specified, a <att>ttm:agent</att> attribute must reference a <el>ttm:agent</el> element
-instance that appears as a descendent of the same document instance as
+value, and is used with certain content elements to designate the
+<phrase diff="chg">agents that perform or are</phrase>
+involved in the performance of the content.</p>
+<p>If specified, a <att>ttm:agent</att> attribute must reference
+<phrase diff="chg"><el>ttm:agent</el> element instances that appear</phrase>
+as a descendent of the same document instance as
that of the referring element.</p>
+<p diff="add">An example of the <att>ttm:agent</att> attribute is shown above in
+<specref ref="metadata-vocabulary-agent-example-1"/>.</p>
</div3>
<div3 id="metadata-attribute-role">
<head>ttm:role</head>
<p>The <att>ttm:role</att> attribute may be used by a content author
-to express a role, function, or characteristic of some content element that is so labeled.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
+to express
+<phrase diff="chg">the roles, functions, or characteristics</phrase>
+of some content element that is so labeled.</p>
+<p>If specified, the value of this attribute must adhere to the following
+syntax<phrase diff="add">, where
+the syntactic element <emph>S</emph> must adhere to production
+[3] <code>S</code> as defined by <bibref ref="xml11"/> §
+2.3</phrase>:</p>
<table id="metadata-attribute-role-syntax" role="syntax">
<caption>Syntax Representation – ttm:role</caption>
<tbody>
<tr>
<td>
<eg xml:space="preserve">
-ttm:role
+ttm:role<phrase diff="add">
+ role ( <emph>S</emph> role )*
+
+role</phrase>
: "action"
| "caption"
<phrase diff="add"> | "description"</phrase>
@@ -7886,11 +8785,11 @@
streaming contexts, even the content is not known at authoring time,
but is only known at time of streaming.</p>
<p>In describing dynamic flow, the flow process is logically divided
-into three types of flow operations:</p>
+into <phrase diff="chg">two</phrase> types of flow operations:</p>
<ulist>
<item><p><emph>fill into</emph> – causes new content
to consume extent in the designated presentation region;</p></item>
-<item><p><emph>reflow within</emph> – causes content
+<item><p diff="del"><emph>reflow within</emph> – causes content
presently consuming extent to be moved, possibly entailing new line break
positions, within its designated
presentation region;</p></item>
@@ -7915,17 +8814,23 @@
of the <code>in()</code> flow function;</p></item>
<item><p><emph>fill style</emph>, as specified by the <code>flowStyle</code> argument
of the <code>in()</code> flow function;</p></item>
-
<item><p diff="del"><emph>fill transition</emph>, as specified by the <code>flowTransition</code> argument
of the <code>in()</code> flow function;</p></item>
<item><p diff="del"><emph>fill transition style</emph>, as specified by the
<code>flowTransitionStyle</code> argument
of the <code>in()</code> flow function;</p></item>
-
-<item><p><emph>reflow unit</emph>, as specified by the <code>flowUnit</code> argument
-of the <code>within()</code> flow function;</p></item>
-<item><p><emph>reflow style</emph>, as specified by the <code>flowStyle</code> argument
-of the <code>within()</code> flow function;</p></item>
+<item>
+<p><emph>reflow unit</emph>, <phrase diff="del">as specified by the
+<code>flowUnit</code> argument of the <code>within()</code> flow
+function</phrase> <phrase diff="add">which is set to the same value as
+the <emph>clear unit</emph> parameter</phrase>;</p>
+</item>
+<item>
+<p><emph>reflow style</emph>, <phrase diff="del">as specified by the
+<code>flowStyle</code> argument of the <code>within()</code> flow
+function</phrase> <phrase diff="add">which is set to the same value as
+the <emph>clear style</emph> parameter</phrase>;</p>
+</item>
<item><p diff="del"><emph>reflow transition</emph>, as specified by the <code>flowTransition</code> argument
of the <code>within()</code> flow function;</p></item>
<item><p diff="del"><emph>reflow transition style</emph>, as specified by the
@@ -8071,7 +8976,7 @@
</note>
<p diff="add">If the value of a style property assigned to content
awaiting in a flow buffer or already dynamically flowed into a
-presentation region is changed, due to animation or other temporal
+presentation region is changed due to animation or other temporal
effects, and that style property change is not otherwise construed as
a significant difference between temporal flow buffer states as
described above, then the semantic, presentation effects of that
@@ -8176,7 +9081,7 @@
<div2 id="dynamicFlowOperations">
<head>Flow Operations</head>
<p>Flow operations perform the filling, reflowing, and clearing of
-formatted content into, within<phrase diff="del">g</phrase>, and from
+formatted content into, within, and from
a presentation <phrase diff="add">region </phrase>undergoing dynamic
flow processing.</p>
<p diff="add">When performing flow operations, the fill unit state parameters that
@@ -8192,8 +9097,10 @@
presentation region, fill, reflow, and clear operations operate on
formatted content units (glyph, inline, line, and block areas);
however, in the context of the flow buffer, fill, reflow, and clear
-operations operate on logical content units (characters and
-words). Because logical content units and formatted content units are
+operations operate on logical content units (character information items and
+element information items –
+<code>fo:inline</code> and <code>fo:block</code>).
+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
units, and vice-versa.</p>
@@ -8406,15 +9313,7 @@
normative definitions of document type, element type, or attribute type
as defined by the body of this specification, then the body of this
specification takes precedence.</p>
-<ednote>
-<name>GA</name>
-<date>2009-01-30</date>
-<edtext>
-The following schemas need to be updated to reflect changes since the previously
-published candidate recommendation.
-</edtext>
-</ednote>
-<div2 id="dfxp-schema-rnc">
+<div2 id="dfxp-schema-rnc" diff="chg">
<head>Relax NG Schema</head>
<p>This section specifies a Relax NG Compact Syntax (RNC) <bibref ref="rng"/> based schema
for DFXP, also available in a <loc href="rnc/schema.zip">ZIP
@@ -8457,11 +9356,11 @@
<head>Layout Module</head>
<eg xml:space="preserve">&rnc-dfxp-layout-module;</eg>
</div4>
-<div4 id="rnc-dfxp-metdata-module">
+<div4 id="rnc-dfxp-metadata-module">
<head>Metadata Module</head>
<eg xml:space="preserve">&rnc-dfxp-metadata-module;</eg>
</div4>
-<div4 id="rnc-dfxp-metdata-items-module">
+<div4 id="rnc-dfxp-metadata-items-module">
<head>Metadata Items Module</head>
<eg xml:space="preserve">&rnc-dfxp-metadata-items-module;</eg>
</div4>
@@ -8469,6 +9368,14 @@
<head>Metadata Attributes Module</head>
<eg xml:space="preserve">&rnc-dfxp-metadata-attribs-module;</eg>
</div4>
+<div4 id="rnc-dfxp-parameters-module">
+<head>Parameters Module</head>
+<eg xml:space="preserve">&rnc-dfxp-parameters-module;</eg>
+</div4>
+<div4 id="rnc-dfxp-parameter-items-module">
+<head>Parameter Items Module</head>
+<eg xml:space="preserve">&rnc-dfxp-parameter-items-module;</eg>
+</div4>
<div4 id="rnc-dfxp-parameter-attribs-module">
<head>Parameter Attributes Module</head>
<eg xml:space="preserve">&rnc-dfxp-parameter-attribs-module;</eg>
@@ -8487,7 +9394,7 @@
</div4>
</div3>
</div2>
-<div2 id="dfxp-schema-xsd">
+<div2 id="dfxp-schema-xsd" diff="chg">
<head>XML Schema Definition (XSD) Schema</head>
<p>This section specifies a W3C XML Schema Definition (XSD) <bibref ref="xsd-1"/> based schema
for DFXP, also available in a <loc href="xsd/schema.zip">ZIP
@@ -8526,11 +9433,11 @@
<head>Layout Module</head>
<eg xml:space="preserve">&xsd-dfxp-layout-module;</eg>
</div4>
-<div4 id="xsd-dfxp-metdata-module">
+<div4 id="xsd-dfxp-metadata-module">
<head>Metadata Module</head>
<eg xml:space="preserve">&xsd-dfxp-metadata-module;</eg>
</div4>
-<div4 id="xsd-dfxp-metdata-items-module">
+<div4 id="xsd-dfxp-metadata-items-module">
<head>Metadata Items Module</head>
<eg xml:space="preserve">&xsd-dfxp-metadata-items-module;</eg>
</div4>
@@ -8538,6 +9445,14 @@
<head>Metadata Attributes Module</head>
<eg xml:space="preserve">&xsd-dfxp-metadata-attribs-module;</eg>
</div4>
+<div4 id="xsd-dfxp-parameters-module">
+<head>Parameters Module</head>
+<eg xml:space="preserve">&xsd-dfxp-parameters-module;</eg>
+</div4>
+<div4 id="xsd-dfxp-parameter-items-module">
+<head>Parameter Items Module</head>
+<eg xml:space="preserve">&xsd-dfxp-parameter-items-module;</eg>
+</div4>
<div4 id="xsd-dfxp-parameter-attribs-module">
<head>Parameter Attributes Module</head>
<eg xml:space="preserve">&xsd-dfxp-parameter-attribs-module;</eg>
@@ -8709,7 +9624,7 @@
: feature-namespace designation
feature-namespace
- : <emph>TT Feature Prefix Namespace</emph> // <phrase><code>http://www.w3.org/2006/10/ttaf1/feature</code></phrase>
+ : <emph>TT Feature Namespace</emph> // http://www.w3.org/2006/10/ttaf1/feature
designation
: "#" token-char+
@@ -8719,32 +9634,9 @@
</eg>
<p>All values of <code>feature-designation</code> not defined by this specification are reserved
for future standardization.</p>
-<p>An example is shown below of using feature designations to indicate the author's intent that a
-receiving processor must be a transformation processor and must support transformation of
-content vocabulary elements.</p>
-<table id="dfxp-example-requiredFeatures" role="example">
-<caption>Example Fragment – Required Features</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"
- <phrase role="strong">requiredFeatures="http://www.w3.org/2006/10/ttaf1/feature#transformation
- http://www.w3.org/2006/10/ttaf1/feature#content"</phrase>>
- <head/>
- <body>
- <div>
- <p/>
- </div>
- </body>
-</tt>
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The following sub-sections define all feature designations (expressed
-without the TT Feature Prefix Namespace).</p>
+<p>The following sub-sections define all feature designations, expressed
+as relative URIs (fragment identifiers) with respect to the
+TT Feature Namespace base URI.</p>
<div3 id="feature-animation">
<head>#animation</head>
<p>A TT AF transformation processor supports the <code>#animation</code>
@@ -8765,10 +9657,13 @@
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute.</p>
<p>A TT AF presentation processor supports the
-<code>#backgroundColor</code> feature if it implements presentation semantic support
+<code>#backgroundColor</code> feature if it (1) implements presentation semantic support
for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
-attribute.</p>
+attribute
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p>
</div3>
<div3 id="feature-backgroundColor-block">
<head>#backgroundColor-block</head>
@@ -8779,11 +9674,14 @@
attribute when applied to a content element that would generate a
block area during presentation processing.</p>
<p>A TT AF presentation processor supports the
-<code>#backgroundColor-block</code> feature if it implements presentation semantic
-support for all defined values of the <loc
+<code>#backgroundColor-block</code> feature if it (1) implements presentation semantic
+support for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute when applied to a content element that generates a
-block area.</p>
+block area
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p>
</div3>
<div3 id="feature-backgroundColor-inline">
<head>#backgroundColor-inline</head>
@@ -8794,11 +9692,14 @@
attribute when applied to a content element that would generate an
inline area during presentation processing.</p>
<p>A TT AF presentation processor supports the
-<code>#backgroundColor-inline</code> feature if it implements presentation semantic
-support for all defined values of the <loc
+<code>#backgroundColor-inline</code> feature if it (1) implements presentation semantic
+support for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute when applied to a content element that generates an
-inline area.</p>
+inline area
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p>
</div3>
<div3 id="feature-backgroundColor-region">
<head>#backgroundColor-region</head>
@@ -8809,11 +9710,15 @@
attribute when applied to a <loc
href="layout-vocabulary-region"><el>region</el></loc> element.</p>
<p>A TT AF presentation processor supports the
-<code>#backgroundColor-region</code> feature if it implements presentation semantic
-support for all defined values of the <loc
+<code>#backgroundColor-region</code> feature if it (1) implements presentation semantic
+support for the <loc
href="#style-attribute-backgroundColor"><att>tts:backgroundColor</att></loc>
attribute when applied to a <loc
-href="layout-vocabulary-region"><el>region</el></loc> element.</p>
+href="layout-vocabulary-region"><el>region</el></loc> element
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space
+.</p>
</div3>
<div3 id="feature-bidi">
<head>#bidi</head>
@@ -8862,10 +9767,13 @@
href="#style-attribute-color"><att>tts:color</att></loc>
attribute.</p>
<p>A TT AF presentation processor supports the
-<code>#color</code> feature if it implements presentation semantic support
+<code>#color</code> feature if it (1) implements presentation semantic support
for the <loc
href="#style-attribute-color"><att>tts:color</att></loc>
-attribute.</p>
+attribute
+and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least sixteen (16) values of color,
+including all primary and secondary colors of the SRGB color space.</p>
</div3>
<div3 id="feature-content">
<head>#content</head>
@@ -8994,21 +9902,6 @@
href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
-<div3 id="feature-dynamicFlow-barWipe">
-<head>#dynamicFlow-barWipe</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-barWipe</code> feature if it recognizes and
-is capable of transforming the flow transition <code>barWipe</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-barWipe</code> feature if it implements
-presentation semantic support for the flow transition <code>barWipe</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-block">
<head>#dynamicFlow-block</head>
<p>A TT AF transformation processor supports the
@@ -9039,21 +9932,6 @@
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
-<div3 id="feature-dynamicFlow-fade">
-<head>#dynamicFlow-fade</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-fade</code> feature if it recognizes and
-is capable of transforming the flow style <code>fade</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-fade</code> feature if it implements
-presentation semantic support for the flow style <code>fade</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-glyph">
<head>#dynamicFlow-glyph</head>
<p>A TT AF transformation processor supports the
@@ -9144,21 +10022,6 @@
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
-<div3 id="feature-dynamicFlow-leftToRight">
-<head>#dynamicFlow-leftToRight</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-leftToRight</code> feature if it recognizes and
-is capable of transforming the flow transition style <code>leftToRight</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-leftToRight</code> feature if it implements
-presentation semantic support for the flow transition style <code>leftToRight</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-line">
<head>#dynamicFlow-line</head>
<p>A TT AF transformation processor supports the
@@ -9189,19 +10052,17 @@
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
-<div3 id="feature-dynamicFlow-pixel">
-<head>#dynamicFlow-pixel</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-pixel</code> feature if it recognizes and
-is capable of transforming the flow unit <code>pixel</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-pixel</code> feature if it implements
-presentation semantic support for the flow unit <code>pixel</code> as
-defined by <specref ref="style-value-flowFunction"/> when used with the
-<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
+<div3 id="feature-dynamicFlow-rollUp">
+<head>#dynamicFlow-rollUp</head>
+<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 <loc
+href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
+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 <loc
+href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute.</p>
</div3>
<div3 id="feature-dynamicFlow-smooth">
@@ -9226,43 +10087,13 @@
is capable of transforming any well-defined value of the
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
attribute that is equivalent to
-<attval>in(glyph,jump) out(line,jump)</attval>.</p>
+<code>in(glyph,jump) out(line,jump)</code>.</p>
<p>A TT AF presentation processor supports the
<code>#dynamicFlow-teletext</code> feature if it implements presentation semantic
-support forany well-defined value of the
-<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
-attribute that is equivalent to <attval>in(glyph,jump)
-out(line,jump)</attval>.</p> </div3>
-<div3 id="feature-dynamicFlow-topToBottom">
-<head>#dynamicFlow-topToBottom</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-topToBottom</code> feature if it recognizes and
-is capable of transforming the flow transition style <code>topToBottom</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-topToBottom</code> feature if it implements
-presentation semantic support for the flow transition style <code>topToBottom</code> as
-defined by <specref ref="style-value-flowFunction"/> when used with the
+support for any well-defined value of the
<loc href="#style-attribute-dynamicFlow"><att>tts:dynamicFlow</att></loc>
-attribute.</p>
-</div3>
-<div3 id="feature-dynamicFlow-within">
-<head>#dynamicFlow-within</head>
-<p>A TT AF transformation processor supports the
-<code>#dynamicFlow-within</code> feature if it recognizes and
-is capable of transforming the flow function <code>within(..)</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-within</code> feature if it implements
-presentation semantic support for the flow function <code>within(..)</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>
+attribute that is equivalent to <code>in(glyph,jump)
+out(line,jump)</code>.</p> </div3>
<div3 id="feature-dynamicFlow-word">
<head>#dynamicFlow-word</head>
<p>A TT AF transformation processor supports the
@@ -9398,7 +10229,7 @@
<head>#fontStyle-italic</head>
<p>A TT AF transformation processor supports the
<code>#fontStyle-italic</code> feature if it recognizes and is
-capable of transforming <code>italic</code> value of the <loc
+capable of transforming the <code>italic</code> value of the <loc
href="#style-attribute-fontStyle"><att>tts:fontStyle</att></loc>
attribute.</p>
<p>A TT AF presentation processor supports the
@@ -9679,10 +10510,11 @@
href="#style-attribute-opacity"><att>tts:opacity</att></loc>
attribute.</p>
<p>A TT AF presentation processor supports the
-<code>#opacity</code> feature if it implements presentation semantic support for
+<code>#opacity</code> feature if it (1) implements presentation semantic support for
the <loc
href="#style-attribute-opacity"><att>tts:opacity</att></loc>
-attribute.</p>
+attribute and (2) is capable of displaying or generating an output display
+signal that distinguishes between at least eight (8) values of opacity.</p>
</div3>
<div3 id="feature-origin">
<head>#origin</head>
@@ -9813,34 +10645,41 @@
</div3>
<div3 id="feature-profile">
<head>#profile</head>
-<p>A TT AF transformation processor supports the
-<code>#profile</code> feature if it recognizes and is capable of
-transforming the <loc
-href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
-attribute.</p>
+<p>A TT AF transformation processor supports the <code>#profile</code>
+feature if it recognizes and is capable of transforming the
+<loc href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
+attribute on the <loc
+href="#document-structure-vocabulary-tt"><el>tt</el></loc> element and
+transforming the following vocabulary defined by
+<specref ref="parameter-element-vocabulary"/>:</p>
+<ulist>
+<item><p><loc
+href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc></p></item>
+<item><p><loc
+href="#parameter-vocabulary-features"><el>ttp:features</el></loc></p></item>
+<item><p><loc
+href="#parameter-vocabulary-feature"><el>ttp:feature</el></loc></p></item>
+<item><p><loc
+href="#parameter-vocabulary-extensions"><el>ttp:extensions</el></loc></p></item>
+<item><p><loc
+href="#parameter-vocabulary-extension"><el>ttp:extension</el></loc></p></item>
+</ulist>
<p>A TT AF presentation processor supports the
<code>#profile</code> feature if it implements presentation semantic support
-for the <loc
-href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
-attribute.</p>
-</div3>
-<div3 id="feature-requiredExtensions">
-<head>#requiredExtensions</head>
-<p>A TT AF processor supports the
-<code>#requiredExtensions</code> feature if it implements semantic support
-for the <loc
-href="#parameter-attribute-requiredExtensions"><att>ttp:requiredExtensions</att></loc>
-attribute on the
-<loc href="#content-vocabulary-tt"><el>tt</el></loc> element.</p>
-</div3>
-<div3 id="feature-requiredFeatures">
-<head>#requiredFeatures</head>
-<p>A TT AF processor supports the
-<code>#requiredFeatures</code> feature if it implements semantic support
-for the <loc
-href="#parameter-attribute-requiredFeatures"><att>ttp:requiredFeatures</att></loc>
-attribute on the
-<loc href="#content-vocabulary-tt"><el>tt</el></loc> element.</p>
+for the same vocabulary specified above.</p>
+</div3>
+<div3 id="feature-rollUp">
+<head>#rollUp</head>
+<p>A TT AF processor supports the <code>#rollUp</code> feature if it
+supports the following features:</p>
+<ulist>
+<item><p><loc
+href="#layout"><code>#layout</code></loc></p></item>
+<item><p><loc
+href="#overflow-dynamic"><code>#overflow-dynamic</code></loc></p></item>
+<item><p><loc
+href="#dynamicFlow-rollUp"><code>#dynamicFlow-rollUp</code></loc></p></item>
+</ulist>
</div3>
<div3 id="feature-showBackground">
<head>#showBackground</head>
@@ -10452,7 +11291,7 @@
<head>Feature Support</head>
<p>The following table, <specref ref="feature-support-table"/>,
enumerates every defined feature designation (expressed without the TT
-Feature Prefix Namespace), and, for each designated feature, specifies
+Feature Namespace), and, for each designated feature, specifies
whether the feature is mandatory (M) or optional (O) for
transformation and presentation processors.</p>
<table id="feature-support-table" role="common">
@@ -10557,11 +11396,6 @@
<td>O</td>
</tr>
<tr>
-<td><loc href="#feature-dynamicFlow-barWipe"><code>#dynamicFlow-barWipe</code></loc></td>
-<td>O</td>
-<td>O</td>
-</tr>
-<tr>
<td><loc href="#feature-dynamicFlow-block"><code>#dynamicFlow-block</code></loc></td>
<td>O</td>
<td>O</td>
@@ -10572,11 +11406,6 @@
<td>O</td>
</tr>
<tr>
-<td><loc href="#feature-dynamicFlow-fade"><code>#dynamicFlow-fade</code></loc></td>
-<td>O</td>
-<td>O</td>
-</tr>
-<tr>
<td><loc href="#feature-dynamicFlow-glyph"><code>#dynamicFlow-glyph</code></loc></td>
<td>O</td>
<td>O</td>
@@ -10607,11 +11436,6 @@
<td>O</td>
</tr>
<tr>
-<td><loc href="#feature-dynamicFlow-leftToRight"><code>#dynamicFlow-leftToRight</code></loc></td>
-<td>O</td>
-<td>O</td>
-</tr>
-<tr>
<td><loc href="#feature-dynamicFlow-line"><code>#dynamicFlow-line</code></loc></td>
<td>O</td>
<td>O</td>
@@ -10622,7 +11446,7 @@
<td>O</td>
</tr>
<tr>
-<td><loc href="#feature-dynamicFlow-pixel"><code>#dynamicFlow-pixel</code></loc></td>
+<td><loc href="#feature-dynamicFlow-rollUp"><code>#dynamicFlow-rollUp</code></loc></td>
<td>O</td>
<td>O</td>
</tr>
@@ -10637,16 +11461,6 @@
<td>O</td>
</tr>
<tr>
-<td><loc href="#feature-dynamicFlow-topToBottom"><code>#dynamicFlow-topToBottom</code></loc></td>
-<td>O</td>
-<td>O</td>
-</tr>
-<tr>
-<td><loc href="#feature-dynamicFlow-within"><code>#dynamicFlow-within</code></loc></td>
-<td>O</td>
-<td>O</td>
-</tr>
-<tr>
<td><loc href="#feature-dynamicFlow-word"><code>#dynamicFlow-word</code></loc></td>
<td>O</td>
<td>O</td>
@@ -10848,18 +11662,13 @@
</tr>
<tr>
<td><loc href="#feature-profile"><code>#profile</code></loc></td>
-<td>O</td>
-<td>O</td>
-</tr>
-<tr>
-<td><loc href="#feature-requiredExtensions"><code>#requiredExtensions</code></loc></td>
<td>M</td>
<td>M</td>
</tr>
<tr>
-<td><loc href="#feature-requiredFeatures"><code>#requiredFeatures</code></loc></td>
-<td>M</td>
-<td>M</td>
+<td><loc href="#feature-rollUp"><code>#rollUp</code></loc></td>
+<td>O</td>
+<td>O</td>
</tr>
<tr>
<td><loc href="#feature-showBackground"><code>#showBackground</code></loc></td>
@@ -11086,7 +11895,11 @@
<p>For the sake of convenience, the following table,
<specref ref="feature-transformation-mandatory-table"/>, 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.</p>
+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
+<specref ref="profile-dfxp-transformation"/>.
+</p>
<table id="feature-transformation-mandatory-table" role="common">
<caption>Table E-2 – Mandatory Features - Transformation</caption>
<col width="60%"/>
@@ -11105,6 +11918,10 @@
</td>
</tr>
<tr>
+<td><loc href="#feature-profile"><code>#profile</code></loc></td>
+<td></td>
+</tr>
+<tr>
<td><loc href="#feature-structure"><code>#structure</code></loc></td>
<td>
<loc href="#content-vocabulary-tt"><el>tt</el></loc>,
@@ -11112,16 +11929,6 @@
</td>
</tr>
<tr>
-<td><loc href="#feature-requiredExtensions"><code>#requiredExtensions</code></loc></td>
-<td><loc href="#content-vocabulary-tt">@<att>requiredExtensions</att></loc>
-applied to <loc href="content-vocabulary-tt"><el>tt</el></loc></td>
-</tr>
-<tr>
-<td><loc href="#feature-requiredFeatures"><code>#requiredFeatures</code></loc></td>
-<td><loc href="#content-vocabulary-tt">@<att>requiredFeatures</att></loc>
-applied to <loc href="content-vocabulary-tt"><el>tt</el></loc></td>
-</tr>
-<tr>
<td><loc href="#feature-transformation"><code>#transformation</code></loc></td>
<td></td>
</tr>
@@ -11130,7 +11937,11 @@
<p>For the sake of convenience, the following table,
<specref ref="feature-presentation-mandatory-table"/>, 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.</p>
+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
+<specref ref="profile-dfxp-presentation"/>.
+</p>
<table id="feature-presentation-mandatory-table" role="common">
<caption>Table E-3 – Mandatory Features - Presentation</caption>
<col width="60%"/>
@@ -11226,20 +12037,14 @@
</td>
</tr>
<tr>
+<td><loc href="#feature-profile"><code>#profile</code></loc></td>
+<td></td>
+</tr>
+<tr>
<td><loc href="#feature-presentation"><code>#presentation</code></loc></td>
<td></td>
</tr>
<tr>
-<td><loc href="#feature-requiredExtensions"><code>#requiredExtensions</code></loc></td>
-<td><loc href="#content-vocabulary-tt">@<att>requiredExtensions</att></loc>
-applied to <loc href="content-vocabulary-tt"><el>tt</el></loc></td>
-</tr>
-<tr>
-<td><loc href="#feature-requiredFeatures"><code>#requiredFeatures</code></loc></td>
-<td><loc href="#content-vocabulary-tt">@<att>requiredFeatures</att></loc>
-applied to <loc href="content-vocabulary-tt"><el>tt</el></loc></td>
-</tr>
-<tr>
<td><loc href="#feature-structure"><code>#structure</code></loc></td>
<td>
<loc href="#content-vocabulary-tt"><el>tt</el></loc>,
@@ -11298,7 +12103,7 @@
<head>Extensions</head>
<p><emph>This appendix is normative.</emph></p>
<p>This appendix specifies the syntactic form of extension designations, which are
-used to express authorial intent regarding the presence of extension
+used to express authorial intent regarding the support for extension
mechanisms in a TT AF processor.</p>
<div2 id="extension-designations">
<head>Extension Designations</head>
@@ -11309,55 +12114,45 @@
: extension-namespace designation
extension-namespace
- : <emph>TT Extension Prefix Namespace</emph> // <phrase><code>http://www.w3.org/2006/10/ttaf1/extension</code></phrase>
+ : <emph>TT Extension Namespace</emph> // http://www.w3.org/2006/10/ttaf1/extension
+ | <emph>Other Extension Namespace</emph> // expressed as an absolute URI
designation
- : "#" designation-token
-
-designation-token
- : standard-designation-token
- | extension-designation-token
-
-standard-designation-token
- : token-char+
-
-extension-designation-token
- : "x-" token-char+
+ : "#" token-char+
token-char
: { XML NameChar } // XML 1.1 Production [4a]
</eg>
-<p>All values of <code>designation-token</code> that do not start with the prefix
-<code>x-</code> are reserved for future standardization.</p>
-<p>An example is shown below of using feature and extension
-designations to indicate the author's intent that a receiving
-processor must implement both transformation and presentation
-processors and must perform a non-standardized (extension)
-transformation in order to pre-filter by language.</p>
-<table id="dfxp-example-requiredExtensions" role="example">
-<caption>Example Fragment – Required Extensions</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-<tt xml:lang="" xmlns="http://www.w3.org/2006/10/ttaf1"
- requiredFeatures="http://www.w3.org/2006/10/ttaf1/feature#transformation
- http://www.w3.org/2006/10/ttaf1/feature#presentation"
- <phrase role="strong">requiredExtensions="http://www.w3.org/2006/10/ttaf1/extension#x-prefilter-by-language"</phrase>>
- <head/>
- <body>
- <div xml:lang="en"/>
- <div xml:lang="fr"/>
- <div xml:lang="es"/>
- <div xml:lang="it"/>
- <div xml:lang="de"/>
- </body>
-</tt>
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
+<p>If the extension namespace of an extension designation is the TT
+Extension Namespace, then all values of the following
+<code>designation</code> token are reserved for future
+standardization.</p>
+<p>If the extension namespace of an extension designation is not the
+TT Extension Namespace, i.e., is an <emph>Other Extension Namespace</emph>,
+then the extension namespace must be expressed as an absolute URI
+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>
+</div2>
+</div1>
+<div1 id="profiles" diff="add">
+<head>Profiles</head>
+<p><emph>This appendix is normative.</emph></p>
+<p>This appendix specifies the following standard TT AF profiles:</p>
+<ulist>
+<item><p><specref ref="profile-dfxp-presentation"/></p></item>
+<item><p><specref ref="profile-dfxp-transformation"/></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-presentation">
+<head>DFXP Presentation Profile</head>
+<eg xml:space="preserve">&profile-dfxp-presentation;</eg>
+</div2>
+<div2 id="profile-dfxp-transformation">
+<head>DFXP Transformation Profile</head>
+<eg xml:space="preserve">&profile-dfxp-transformation;</eg>
</div2>
</div1>
<div1 id="references">
@@ -11562,446 +12357,6 @@
</bibl>
</blist>
</inform-div1>
-<inform-div1 id="sample-code">
-<head>Sample Code</head>
-<p>This appendix contains sample code, also available in
-a <loc href="scm/code.zip">ZIP Archive</loc> along with related files, that implements
-certain algorithms described by this specification. This code makes
-use of the MIT Scheme <bibref ref="scheme"/> dialect of the Lisp Programming Language.</p>
-<p>The following algorithms are implemented by this code:</p>
-<ulist>
-<item><p>Reduced XML Infoset (RXI)</p></item>
-<item><p>Abstract Document Instance (ADI)</p></item>
-<item><p>Time Interval Resolver (TIR)</p></item>
-<item><p>Flow Object Transformer (FOX)</p></item>
-<item><p>Dynamic Text Flow Processor (DTF)</p></item>
-</ulist>
-<p>Subsequent to the sample code listings, a transcript of a sample
-compile, load, and run session is provided.</p>
-<div2 id="code-rxi">
-<head>Reduced XML Infoset (RXI) – <code>RXI.SCM</code></head>
-<eg xml:space="preserve">&code-rxi;</eg>
-</div2>
-<div2 id="code-adi">
-<head>Abstract Document Instance (ADI) – <code>ADI.SCM</code></head>
-<eg xml:space="preserve">&code-adi;</eg>
-</div2>
-<div2 id="code-tir">
-<head>Time Interval Resolver (TIR) – <code>TIR.SCM</code></head>
-<eg xml:space="preserve">&code-tir;</eg>
-</div2>
-<div2 id="code-fox">
-<head>Flow Object Transformer (FOX) – <code>FOX.SCM</code></head>
-<eg xml:space="preserve">&code-tir;</eg>
-</div2>
-<div2 id="code-dtf">
-<head>Dynamic Text Flow Processor (DTF) – <code>DTF.SCM</code></head>
-<eg xml:space="preserve">&code-dtf;</eg>
-</div2>
-<div2 id="code-run">
-<head>Sample Compile, Load, and Run Session</head>
-<p>The following transcript shows a sample compile, load, and run
-session of the sample code, where the following steps are
-performed:</p>
-<olist>
-<item>
-<p>Start scheme using Edwin editor (included with MIT Scheme).</p>
-</item>
-<item>
-<p>Change working directory to sample code directory.</p>
-</item>
-<item>
-<p>Compile DFXP optional package by loading <code>compile.scm</code>.</p>
-</item>
-<item>
-<p>Load DFXP optional package by loading <code>load.scm</code>.</p>
-</item>
-<item>
-<p>Dump world identity to show that the just compiled, DFXP optional
-package has been loaded (MIT Scheme SOS, CREF, and XML optional packages are also
-loaded a side effect.)</p>
-</item>
-<item>
-<p>Load DFXP document instance using <code>ADI-DOCUMENT/LOAD</code>
-function and save resulting <code>ADI-DOCUMENT</code> instance into variable
-<code>D</code>.</p>
-</item>
-<item>
-<p>Convert loaded <code>ADI-DOCUMENT</code> into a list structure and pretty print
-this structure using <code>PP</code> environment function.</p>
-</item>
-<item>
-<p>Serialize loaded <code>ADI-DOCUMENT</code> to file
-<code>out.xml</code>.</p>
-</item>
-<item>
-<p>Exit scheme interpreter.</p>
-</item>
-</olist>
-<p>The forms to be entered to accomplish the above tasks are depicted in boldface.</p>
-<eg xml:space="preserve">
-Scheme saved on Tuesday June 18, 2002 at 12:25:05 AM
- Release 7.7.1
- Microcode 14.9
- Runtime 15.1
- Win32 1.6
- SF 4.40
- Liar (Intel i386) 4.115
- Edwin 3.112
-
-;You are in an interaction window of the Edwin editor.
-;Type C-h for help. C-h m will describe some commands.
-;Package: (user)
-
-<phrase role="strong">(cd "/work/dfxp/scm")</phrase>
-;Value 12: #[pathname 12 "c:\\work\\dfxp\\scm\\"]
-
-<phrase role="strong">(load "compile")</phrase>
-;Loading "compile.scm"
-;Loading "load.scm"
-;Loading "load.scm"
-;Loading "sos-w32.pkd" -- done
-;Loading "slot.com" -- done
-;Loading "class.com" -- done
-;Loading "instance.com" -- done
-;Loading "method.com" -- done
-;Loading "printer.com" -- done
-;Loading "macros.com" -- done
- -- done
-;Loading "xml-w32.pkd" -- done
-;Loading "xml-struct.com" -- done
-;Loading "xml-chars.com" -- done
-;Loading "xml-parser.com" -- done
-;Loading "xml-output.com" -- done
- -- done
-;Loading "make.com" -- done
-;Loading "cref-w32.pkd" -- done
-;Loading "mset.com" -- done
-;Loading "object.com" -- done
-;Loading "toplev.com" -- done
-;Loading "anfile.com" -- done
-;Loading "conpkg.com" -- done
-;Loading "forpkg.com" -- done
-;Loading "redpkg.com" -- done
-;Generating "rxi.bin" because of: "rxi.scm"
-Syntax file: "rxi.scm" "rxi.bin"
- Read...
- Time taken: .031 (process time); .031 (real time)
- Syntax...
- Time taken: .032 (process time); .031 (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
-;Warning: Unreferenced bound variable: is-attribute? (rxi-name/transform-to-xml)
- Time taken: .015 (process time); .016 (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "rxi.ext" -- done
-;Dumping "rxi.bin" -- done
-;Generating "rxi.com" because of: "rxi.bin"
-Compile File: "rxi.bin" => "rxi.com"
-;Loading "rxi.bin" -- done
- Compiling procedure: rxi-bindings/bindings...
- Compiling procedure: set-rxi-bindings/bindings!...
- Compiling procedure: rxi-bindings/push!...
- Compiling procedure: rxi-bindings/pop!...
- Compiling procedure: rxi-bindings/lookup...
- Compiling procedure: rxi-bindings/resolve...
- Compiling procedure: rxi-name/local...
- Compiling procedure: rxi-name/namespace...
- Compiling procedure: rxi-name->list...
- Compiling procedure: rxi-name/transform-from-xml...
- Compiling procedure: rxi-attribute/name...
- Compiling procedure: rxi-attribute/value...
- Compiling procedure: rxi-attribute->list...
- Compiling procedure: rxi-attribute/transform-from-xml...
- Compiling procedure: rxi-element/name...
- Compiling procedure: rxi-element/attributes...
- Compiling procedure: rxi-element/children...
- Compiling procedure: set-rxi-element/attributes!...
- Compiling procedure: set-rxi-element/children!...
- Compiling procedure: rxi-element->list...
- Compiling procedure: namespace-attribute?...
- Compiling procedure: extract-namespace-bindings...
- Compiling procedure: rxi-element/transform-from-xml...
- Compiling procedure: rxi-document/annotations...
- Compiling procedure: rxi-document/root...
- Compiling procedure: set-rxi-document/annotations!...
- Compiling procedure: set-rxi-document/root!...
- Compiling procedure: rxi-document/annotation...
- Compiling procedure: set-rxi-document/annotation!...
- Compiling procedure: rxi-document/remove-annotation!...
- Compiling procedure: rxi-document->list...
- Compiling procedure: rxi-document/transform-from-xml...
- Compiling procedure: rxi-document/load...
- Compiling procedure: rxi-reverse-bindings/reverse-bindings...
- Compiling procedure: set-rxi-reverse-bindings/reverse-bindings!...
- Compiling procedure: rxi-reverse-bindings/lookup...
- Compiling procedure: rxi-reverse-bindings/generate-prefix...
- Compiling procedure: rxi-reverse-bindings/add!...
- Compiling procedure: rxi-reverse-bindings/sort!...
- Compiling procedure: rxi-reverse-bindings/normalize-preferred...
- Compiling procedure: rxi-name/transform-to-xml...
- Compiling procedure: rxi-attribute/transform-to-xml...
- Compiling procedure: maybe-add-reverse-binding!...
- Compiling procedure: rxi-element/collect-reverse-bindings...
- Compiling procedure: rxi-element/transform-to-xml...
- Compiling procedure: xml-document-add-bindings!...
- Compiling procedure: rxi-document/collect-reverse-bindings...
- Compiling procedure: rxi-document/transform-to-xml...
- Compiling procedure: rxi-document/save...
-;"rxi.bci" dumped
-;Dumping "rxi.com" -- done
-;Generating "adi.bin" because of: "adi.scm"
-Syntax file: "adi.scm" "adi.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: .016 (process time); .015 (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "adi.bin" -- done
-;Generating "adi.com" because of: "adi.bin"
-Compile File: "adi.bin" => "adi.com"
-;Loading "adi.bin" -- done
- Compiling procedure: in-per-element-namespace?...
- Compiling procedure: in-dfxp-namespace?...
- Compiling procedure: in-xml-namespace?...
- Compiling procedure: in-dfxp-or-xml-namespace?...
- Compiling procedure: empty-dfxp-element-type?...
- Compiling procedure: only-whitespace-children?...
- Compiling procedure: rxi-document/adi-transform-element...
- Compiling procedure: rxi-document/adi-transform...
- Compiling procedure: adi-document/load...
- Compiling procedure: adi-document/save...
-;"adi.bci" dumped
-;Dumping "adi.com" -- done
-;Generating "tir.bin" because of: "tir.scm"
-Syntax file: "tir.scm" "tir.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "tir.bin" -- done
-;Generating "tir.com" because of: "tir.bin"
-Compile File: "tir.bin" => "tir.com"
-;Loading "tir.bin" -- done
- Compiling procedure: adi-document/tir-transform...
-;"tir.bci" dumped
-;Dumping "tir.com" -- done
-;Generating "fox.bin" because of: "fox.scm"
-Syntax file: "fox.scm" "fox.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "fox.bin" -- done
-;Generating "fox.com" because of: "fox.bin"
-Compile File: "fox.bin" => "fox.com"
-;Loading "fox.bin" -- done
- Compiling procedure: adi-document/fox-transform...
-;"fox.bci" dumped
-;Dumping "fox.com" -- done
-;Generating "dtf.bin" because of: "dtf.scm"
-Syntax file: "dtf.scm" "dtf.bin"
- Read...
- Time taken: 0. (process time); 0. (real time)
- Syntax...
- Time taken: 0. (process time); 0. (real time)
- Transform...
- Time taken: 0. (process time); 0. (real time)
- Optimize...
- Time taken: 0. (process time); 0. (real time)
- Generate SCode...
- Time taken: 0. (process time); 0. (real time)
-;Dumping "dtf.bin" -- done
-;Generating "dtf.com" because of: "dtf.bin"
-Compile File: "dtf.bin" => "dtf.com"
-;Loading "dtf.bin" -- done
- Compiling procedure: adi-document/dtf-process...
-;"dtf.bci" dumped
-;Dumping "dtf.com" -- done
-;Loading "dtf.bin" -- done
-;Loading "fox.bin" -- done
-;Loading "tir.bin" -- done
-;Loading "adi.bin" -- done
-;Loading "rxi.bin" -- done
-;Dumping "dfxp-w32.fre" -- done
-;Dumping "dfxp-w32.pkd" -- done
- -- done
-;Unspecified return value
-
-<phrase role="strong">(load "load")</phrase>
-;Loading "load.scm"
-;Loading "dfxp-w32.pkd" -- done
-;Loading "rxi.com" -- done
-;Loading "adi.com" -- done
-;Loading "tir.com" -- done
-;Loading "fox.com" -- done
-;Loading "dtf.com" -- done
- -- done
-;Unspecified return value
-
-<phrase role="strong">(identify-world)</phrase>
-Scheme saved on Tuesday June 18, 2002 at 12:25:05 AM
- Release 7.7.1
- Microcode 14.9
- Runtime 15.1
- Win32 1.6
- SF 4.40
- Liar (Intel i386) 4.115
- Edwin 3.112
- SOS 1.7
- XML 0.2
- CREF 2.3
- DFXP 0.8
-;Unspecified return value
-
-<phrase role="strong">(define d (adi-document/load "test.xml"))</phrase>
-;Value: d
-
-<phrase role="strong">(pp (rxi-document->list d))</phrase>
-(((adi-transform . #t))
- (("tt" "http://www.w3.org/2006/10/ttaf1")
- ((("profile" "http://www.w3.org/2006/10/ttaf1#parameter")
- "http://www.w3.org/2006/10/ttaf1#profile-dfxp")
- (("lang" "http://www.w3.org/XML/1998/namespace") "en"))
- ("\n "
- (("head" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("metadata" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("title" "http://www.w3.org/2006/10/ttaf1#metadata") () ("Timed Text DFXP Example"))
- "\n "
- (("copyright" "http://www.w3.org/2006/10/ttaf1#metadata") () ("The Authors (c) 2006"))
- "\n "))
- "\n "
- (("styling" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s1")
- (("color" "http://www.w3.org/2006/10/ttaf1#style") "white")
- (("fontFamily" "http://www.w3.org/2006/10/ttaf1#style") "proportionalSansSerif")
- (("fontSize" "http://www.w3.org/2006/10/ttaf1#style") "22px")
- (("textAlign" "http://www.w3.org/2006/10/ttaf1#style") "center"))
- ())
- "\n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s2") (("style" ()) "s1")
- (("color" "http://www.w3.org/2006/10/ttaf1#style") "yellow"))
- ())
- "\n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s1Right") (("style" ()) "s1")
- (("textAlign" "http://www.w3.org/2006/10/ttaf1#style") "end"))
- ())
- " \n \n "
- (("style" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "s2Left") (("style" ()) "s2")
- (("textAlign" "http://www.w3.org/2006/10/ttaf1#style") "start"))
- ())
- "\n "))
- "\n "
- (("layout" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("region" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitleArea")
- (("style" ()) "s1")
- (("extent" "http://www.w3.org/2006/10/ttaf1#style") "560px 62px")
- (("padding" "http://www.w3.org/2006/10/ttaf1#style") "5px 3px")
- (("backgroundColor" "http://www.w3.org/2006/10/ttaf1#style") "black")
- (("displayAlign" "http://www.w3.org/2006/10/ttaf1#style") "after"))
- ())
- "\n "))
- " \n "))
- "\n "
- (("body" "http://www.w3.org/2006/10/ttaf1")
- ((("region" ()) "subtitleArea"))
- ("\n "
- (("div" "http://www.w3.org/2006/10/ttaf1")
- ()
- ("\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle1") (("begin" ()) "0.76s") (("end" ()) "3.45s"))
- ("\n It seems a paradox, does it not,\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle2") (("begin" ()) "5.0s") (("end" ()) "10.0s"))
- ("\n that the image formed on" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n the Retina should be inverted?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle3") (("begin" ()) "10.0s") (("end" ()) "16.0s") (("style" ()) "s2"))
- ("\n It is puzzling, why is it" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n we do not see things upside-down?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle4") (("begin" ()) "17.2s") (("end" ()) "23.0s"))
- ("\n You have never heard the Theory,"
- (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n then, that the Brain also is inverted?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle5") (("begin" ()) "23.0s") (("end" ()) "27.0s") (("style" ()) "s2"))
- ("\n No indeed! What a beautiful fact!\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle6a") (("begin" ()) "28.0s") (("end" ()) "34.6s") (("style" ()) "s2Left"))
- ("\n But how is it proved?\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle6b") (("begin" ()) "28.0s") (("end" ()) "34.6s") (("style" ()) "s1Right"))
- ("\n Thus: what we call\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle7") (("begin" ()) "34.6s") (("end" ()) "45.0s") (("style" ()) "s1Right"))
- ("\n the vertex of the Brain" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n is really its base\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle8") (("begin" ()) "45.0s") (("end" ()) "52.0s") (("style" ()) "s1Right"))
- ("\n and what we call its base" (("br" "http://www.w3.org/2006/10/ttaf1") () ())
- "\n is really its vertex,\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle9a") (("begin" ()) "53.5s") (("end" ()) "58.7s"))
- ("\n it is simply a question of nomenclature.\n "))
- "\n "
- (("p" "http://www.w3.org/2006/10/ttaf1")
- ((("xml:id" ()) "subtitle9b") (("begin" ()) "53.5s") (("end" ()) "58.7s") (("style" ()) "s2"))
- ("\n How truly delightful!\n "))
- "\n "))
- " \n "))
- "\n")))
-;Unspecified return value
-
-<phrase role="strong">(adi-document/save d "out.xml")</phrase>
-;Unspecified return value
-
-<phrase role="strong">(exit)</phrase>
-</eg>
-</div2>
-</inform-div1>
<inform-div1 id="requirements">
<head>Requirements</head>
<p>The Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring
@@ -12644,6 +12999,42 @@
<td>-@class, -@style, -@xml:base</td>
<td>2,5,9</td>
</tr>
+
+<tr>
+<td><phrase diff="add"><loc href="#parameter-vocabulary-extension"><code>ttp:extension</code></loc></phrase></td>
+<td><phrase diff="add"><code>@requiredExtensions</code></phrase></td>
+<td><phrase diff="add"><bibref ref="svg11"/></phrase></td>
+<td><phrase diff="add">conceptual derivation</phrase></td>
+<td><phrase diff="add">10</phrase></td>
+</tr>
+<tr>
+<td><phrase diff="add"><loc href="#parameter-vocabulary-extensions"><code>ttp:extensions</code></loc></phrase></td>
+<td><phrase diff="add"><code>@requiredExtensions</code></phrase></td>
+<td><phrase diff="add"><bibref ref="svg11"/></phrase></td>
+<td><phrase diff="add">conceptual derivation</phrase></td>
+<td><phrase diff="add">10</phrase></td>
+</tr>
+<tr>
+<td><phrase diff="add"><loc href="#parameter-vocabulary-feature"><code>ttp:feature</code></loc></phrase></td>
+<td><phrase diff="add"><code>@requiredFeatures</code></phrase></td>
+<td><phrase diff="add"><bibref ref="svg11"/></phrase></td>
+<td><phrase diff="add">conceptual derivation</phrase></td>
+<td><phrase diff="add">10</phrase></td>
+</tr>
+<tr>
+<td><phrase diff="add"><loc href="#parameter-vocabulary-features"><code>ttp:features</code></loc></phrase></td>
+<td><phrase diff="add"><code>@requiredFeatures</code></phrase></td>
+<td><phrase diff="add"><bibref ref="svg11"/></phrase></td>
+<td><phrase diff="add">conceptual derivation</phrase></td>
+<td><phrase diff="add">10</phrase></td>
+</tr>
+<tr>
+<td><phrase diff="add"><loc href="#parameter-vocabulary-profile"><code>ttp:profile</code></loc></phrase></td>
+<td><phrase diff="add"><code>@baseProfile</code></phrase></td>
+<td><phrase diff="add"><bibref ref="svg11"/></phrase></td>
+<td><phrase diff="add">conceptual derivation</phrase></td>
+<td><phrase diff="add">11</phrase></td>
+</tr>
</tbody>
</table>
<note>
@@ -12689,6 +13080,15 @@
<p>The <att>style</att> attribute is supported only on content
elements.</p>
</item>
+<item>
+<p diff="add">Derived from the use of <code>@requiredExtensions</code>
+and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
+but extended to support distinct specification of optionality.</p>
+</item>
+<item>
+<p diff="add">Derived from the use of <code>@baseProfile</code>
+and <code>@version</code> on the <code>svg:svg</code> element.</p>
+</item>
</olist>
</note>
</div2>
@@ -12871,35 +13271,35 @@
<td><loc href="#style-attribute-backgroundColor"><code>tts:backgroundColor</code></loc></td>
<td><code>background-color</code></td>
<td><bibref ref="xsl11"/></td>
-<td>see notes</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>1,6</td>
</tr>
<tr>
<td><loc href="#style-attribute-color"><code>tts:color</code></loc></td>
<td><code>color</code></td>
<td><bibref ref="xsl11"/></td>
-<td>initial value specified as <code>transparent</code></td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>6</td>
</tr>
<tr>
<td><loc href="#style-attribute-direction"><code>tts:direction</code></loc></td>
<td><code>direction</code></td>
<td><bibref ref="xsl11"/></td>
-<td>complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td></td>
</tr>
<tr>
<td><loc href="#style-attribute-display"><code>tts:display</code></loc></td>
<td><code>display</code></td>
<td><bibref ref="css2"/></td>
-<td>only auto, none, inherit</td>
+<td>only <code>auto</code>, <code>none</code><phrase diff="del">, inherit</phrase></td>
<td></td>
</tr>
<tr>
<td><loc href="#style-attribute-displayAlign"><code>tts:displayAlign</code></loc></td>
<td><code>display-align</code></td>
<td><bibref ref="xsl11"/></td>
-<td>except for name normalization, complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>1</td>
</tr>
<tr>
@@ -12920,42 +13320,42 @@
<td><loc href="#style-attribute-fontFamily"><code>tts:fontFamily</code></loc></td>
<td><code>font-family</code></td>
<td><bibref ref="xsl11"/></td>
-<td>extends generic family names</td>
+<td><phrase diff="add"><code>-inherit</code>, </phrase>extends generic family names</td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-fontSize"><code>tts:fontSize</code></loc></td>
<td><code>font-size</code></td>
<td><bibref ref="xsl11"/></td>
-<td>see notes</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>1,7</td>
</tr>
<tr>
<td><loc href="#style-attribute-fontStyle"><code>tts:fontStyle</code></loc></td>
<td><code>font-style</code></td>
<td><bibref ref="xsl11"/></td>
-<td>uses alias <code>reverseOblique</code> for <code>backslant</code></td>
+<td><phrase diff="add"><code>-inherit</code>, </phrase>uses alias <code>reverseOblique</code> for <code>backslant</code></td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-fontWeight"><code>tts:fontWeight</code></loc></td>
<td><code>font-weight</code></td>
<td><bibref ref="xsl11"/></td>
-<td>-bolder, -lighter, -<number></td>
+<td><phrase diff="add"><code>-inherit</code>, </phrase><code>-bolder</code>, <code>-lighter</code>, <code>-<number></code></td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-lineHeight"><code>tts:lineHeight</code></loc></td>
<td><code>line-height</code></td>
<td><bibref ref="xsl11"/></td>
-<td>-<number>, -<space></td>
+<td><phrase diff="add"><code>-inherit</code>, </phrase><code>-<number></code>, <code>-<space></code></td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-opacity"><code>tts:opacity</code></loc></td>
<td><code>opacity</code></td>
<td><bibref ref="css3-color"/></td>
-<td>complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td></td>
</tr>
<tr>
@@ -12969,76 +13369,77 @@
<td><loc href="#style-attribute-overflow"><code>tts:overflow</code></loc></td>
<td><code>overflow</code></td>
<td><bibref ref="xsl11"/></td>
-<td>-auto, -error-if-overflow; <phrase diff="chg">dynamic added</phrase></td>
+<td><phrase diff="add"><code>-inherit</code>, </phrase><code>-auto</code>, <code>-error-if-overflow</code>; <phrase diff="chg"><code>+dynamic</code></phrase></td>
<td>8</td>
</tr>
<tr>
<td><loc href="#style-attribute-padding"><code>tts:padding</code></loc></td>
<td><code>padding</code></td>
<td><bibref ref="xsl11"/></td>
-<td>see notes</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>9</td>
</tr>
<tr>
<td><loc href="#style-attribute-showBackground"><code>tts:showBackground</code></loc></td>
<td><code>showBackground</code></td>
<td><bibref ref="smil21"/></td>
-<td>complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
+<td></td>
</tr>
<tr>
<td><loc href="#style-attribute-textAlign"><code>tts:textAlign</code></loc></td>
<td><code>text-align</code></td>
<td><bibref ref="xsl11"/></td>
-<td>except for name normalization, complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-textDecoration"><code>tts:textDecoration</code></loc></td>
<td><code>text-decoration</code></td>
<td><bibref ref="xsl11"/></td>
-<td>except for name normalization, complies with model</td>
-<td>1,10</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
+<td>1,10<phrase diff="add">,13</phrase></td>
</tr>
<tr>
<td><loc href="#style-attribute-textOutline"><code>tts:textOutline</code></loc></td>
<td><code>text-shadow</code></td>
<td><bibref ref="xsl11"/></td>
-<td>see notes</td>
-<td>11</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
+<td>11<phrase diff="add">,13</phrase></td>
</tr>
<tr>
<td><loc href="#style-attribute-unicodeBidi"><code>tts:unicodeBidi</code></loc></td>
<td><code>unicode-bidi</code></td>
<td><bibref ref="xsl11"/></td>
-<td>except for name normalization, complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-visibility"><code>tts:visibility</code></loc></td>
<td><code>visibility</code></td>
<td><bibref ref="xsl11"/></td>
-<td>-collapse</td>
+<td><phrase diff="add"><code>-inherit</code>, </phrase><code>-collapse</code></td>
<td></td>
</tr>
<tr>
<td><loc href="#style-attribute-wrapOption"><code>tts:wrapOption</code></loc></td>
<td><code>wrap-option</code></td>
<td><bibref ref="xsl11"/></td>
-<td>except for name normalization, complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-writingMode"><code>tts:writingMode</code></loc></td>
<td><code>writing-mode</code></td>
<td><bibref ref="xsl11"/></td>
-<td>+tblr</td>
+<td><phrase diff="add"><code>-inherit</code>, </phrase><code>+tblr</code></td>
<td>1</td>
</tr>
<tr>
<td><loc href="#style-attribute-zIndex"><code>tts:zIndex</code></loc></td>
<td><code>z-index</code></td>
<td><bibref ref="xsl11"/></td>
-<td>except for name normalization, complies with model</td>
+<td><phrase diff="chg"><code>-inherit</code></phrase></td>
<td>1</td>
</tr>
<tr>
@@ -13153,6 +13554,9 @@
defined in terms of presentation semantics by <specref
ref="content-attribute-space"/>.</p>
</item>
+<item>
+<p diff="add">Defined to be inheritable.</p>
+</item>
</olist>
</note>
</div2>
@@ -13876,7 +14280,26 @@
for use with DFXP, or the defined value space of an attribute or
property:
-* Add requiredExtensions, requiredFeatures, and requiredFonts attributes.
+* SCHEMA TECHNICAL CHANGES *
+
+* Change TT Style Namespace to use #styling instead of #style as
+ fragment identifier.
+* Add ttp:{profile,features,feature,extensions,extension> elements.
+* Add tts:extent to tt element.
+* Add Parameters.class group to head content model.
+* Add attributes from metadata extension namespace to body, div, p,
+ span, br, metadata.
+* Add attributes from style extension namespace to body, div, p, span,
+ br, region.
+* Remove 'inherit' value from all tts:* style attributes.
+* Change 'scroll' value to 'dynamic' on tts:overflow attribute.
+* Add 'description' value to ttm:role attribute.
+* Change data type of ttm:role attribute to NMTOKENS.
+
+* NON-SCHEMA TECHNICAL CHANGES *
+
+* Add 'rollUp' value to tts:dynamicFlow attribute.
+
<phrase role="strong">Editorial Changes</phrase>