--- a/spec/editlist.txt Sun Dec 14 06:10:23 2008 +0000
+++ b/spec/editlist.txt Sun Dec 14 09:05:00 2008 +0000
@@ -4,9 +4,21 @@
NOT YET IMPLEMENTED
-1. B.4 change typo "withing" to "within"
-2. 8.2.24 remove extra '"' at end of last line of wrap option example
+[GA-A-026-20081205] * define default region
+[GA-I-028-20081208] 8.2.13 elaborate prose to accommodate nested spans
+[GA-I-034-20081209] 9.3.2 (1) elaborate processing of anonymous spans
+[GA-I-036-20081209] 8.2.21 inheritance by anonymous spans
+[GA-I-042-20081211] * processing in absence of region attribute
ALREADY IMPLEMENTED
-
+[GA-A-024-20081214] 7.1.4 correct prose to accommodate nested divs
+[GA-A-024-20081214] 7.1.6 correct prose to accommodate nested spans
+[GA-A-027-20081214] 9.3.2 (7) map anonymous spans to fo:inline only when parent is p or span
+[GA-I-016-20081214] 10.2.* fix incorrect reference to smil2 section (should be 10.4.1)
+[GA-I-017-20081214] 8.3.4 correct definition of <duration> syntax to <digit>+
+[GA-I-027-20081214] 8.2.20 correct names of textDecoration values (lineThrough)
+[GA-I-037-20081214] 9.3.2 (7) map anonymous spans to fo:inline only when parent is p or span
+[GA-I-044-20081214] B.4 change typo "withing" to "within"
+[GA-I-045-20081214] 8.2.24 remove extra '"' at end of last line of wrap option example
+[GA-I-046-20081214] 8.2.23 missing inheritance and percentage constraints
--- a/spec/ttaf1-dfxp.html Sun Dec 14 06:10:23 2008 +0000
+++ b/spec/ttaf1-dfxp.html Sun Dec 14 09:05:00 2008 +0000
@@ -65,8 +65,8 @@
.strong { font-weight: bold }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-.diff-add { color: red; }
-.diff-del { color: red; text-decoration: line-through; }
+.diff-add { color: red; background-color: #99FF99; }
+.diff-del { color: red; text-decoration: line-through; background-color: #99FF99; }
.diff-chg { background-color: #99FF99; }
.diff-off {}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body>Last Modified: $Date$<div id="revisions"/><div class="head">
@@ -292,11 +292,11 @@
G.6 <a href="#code-run">Sample Compile, Load, and Run Session</a><br/>
H <a href="#requirements">Requirements</a> (Non-Normative)<br/>
I <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br/>
- I.1 <a href="#d3e11525">Element Derivation</a><br/>
- I.2 <a href="#d3e11909">Attribute Derivation</a><br/>
+ I.1 <a href="#d3e11612">Element Derivation</a><br/>
+ I.2 <a href="#d3e11996">Attribute Derivation</a><br/>
J <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br/>
- J.1 <a href="#d3e12761">Requirements</a><br/>
- J.2 <a href="#d3e12925">Guidelines</a><br/>
+ J.1 <a href="#d3e12848">Requirements</a><br/>
+ J.2 <a href="#d3e13012">Guidelines</a><br/>
K <a href="#streaming">Streaming DFXP Content</a> (Non-Normative)<br/>
L <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br/>
M <a href="#change-history">Change History</a> (Non-Normative)<br/>
@@ -1237,19 +1237,26 @@
element must not be <code>inherit</code>.</p></div><div class="div3">
<h4><a name="content-vocabulary-div" id="content-vocabulary-div"/>7.1.4 div</h4><p>The <code>div</code> element functions as a logical container and a temporal
structuring element for a sequence of textual content units represented as
-logical paragraphs.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When rendered on a continuous (non-paged) visual presentation medium,
-a <code>div</code> element is expected to generate a single block area that
-contains zero or more child block areas generated by the <code>div</code>
-element's child <code>p</code> elements.
-</p><p>If the single block area generated by a <code>div</code> element does
+logical <span class="diff-add">sub-divisions or </span>paragraphs.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When rendered on a continuous (non-paged) visual presentation medium,
+a <code>div</code> element is expected to generate
+<span class="diff-del">a single</span><span class="diff-add">one or more</span> block
+area<span class="diff-add">s</span>
+that contain<span class="diff-del">s</span> zero or more child block areas
+generated by the <code>div</code> element's
+<span class="diff-del">child</span><span class="diff-add">descendant</span>
+<code>p</code> elements.
+</p><p>If <span class="diff-del">the single</span><span class="diff-add">some</span>
+block area generated by a <code>div</code> element does
not contain any child areas, then it is not expected to be presented.</p></div><p>The <code>div</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group,
followed by zero or more
elements in the <code>Animation.class</code> element group,
followed by
-zero or more <code>p</code> elements.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The core vocabulary intentionally does not support nested divisions in order to reduce
+zero or more
+<span class="diff-add"><code>div</code> or </span>
+<code>p</code> elements.</p><div class="diff-del"><div class="note"><p class="prefix"><b>Note:</b></p><p>The core vocabulary intentionally does not support nested divisions in order to reduce
the complexity of the profile to match that of the legacy distribution formats with which
-the core vocabulary was designed to interoperate.</p></div><p>Any metadata specified by children in the <code>Metadata.class</code>
+the core vocabulary was designed to interoperate.</p></div></div><p>Any metadata specified by children in the <code>Metadata.class</code>
element group applies semantically to the <code>div</code> element and its descendants as a whole.</p><p>Any animation elements specified by children in the <code>Animation.class</code>
element group apply semantically to the <code>div</code> element.</p><table summary="HTML Table" id="elt-syntax-div" class="syntax"><caption>XML Representation – Element Information Item: div</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -1271,9 +1278,13 @@
</pre></div>
</td></tr></tbody></table><p>If no <code>timeContainer</code> attribute is specified, then a <code>div</code> element must be
interpreted as having <em>parallel</em> time containment semantics.</p><p>An author may associate a set of style properties with a <code>div</code> element by means of either
-the <code>style</code> attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated to a <code>div</code> element in a document instance
+the <code>style</code> attribute or inline style attributes or a combination thereof.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Style properties that are associated
+<span class="diff-del">to</span><span class="diff-add">with</span>
+a <code>div</code> element in a document instance
are available for style inheritance by descendant content elements such as
-<code>p</code> and <code>span</code>.</p></div></div><div class="div3">
+<span class="diff-add"><code>div</code>, </span>
+<code>p</code><span class="diff-add">,</span>
+and <code>span</code>.</p></div></div><div class="div3">
<h4><a name="content-vocabulary-p" id="content-vocabulary-p"/>7.1.5 p</h4><p>A <code>p</code> element represents a logical paragraph, serving as
a transition between block level and inline level formatting semantics.</p><p>The <code>p</code> element accepts as its children zero or more
elements in the <code>Metadata.class</code> element group,
@@ -1316,10 +1327,11 @@
elements in the <code>Animation.class</code> element group,
followed by
zero or more
-<code>br</code> element
-or text nodes interpreted as anonymous spans.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The core vocabulary intentionally does not support nested spans in order to reduce
+<span class="diff-add"><code>span</code> elements ,</span>
+<code>br</code> element<span class="diff-add">s,</span>
+or text nodes interpreted as anonymous spans.</p><div class="diff-del"><div class="note"><p class="prefix"><b>Note:</b></p><p>The core vocabulary intentionally does not support nested spans in order to reduce
the complexity of the profile to match that of the legacy distribution formats with which
-the core vocabulary was designed to interoperate.</p></div><p>Any metadata specified by children in the <code>Metadata.class</code>
+the core vocabulary was designed to interoperate.</p></div></div><p>Any metadata specified by children in the <code>Metadata.class</code>
element group applies semantically to the <code>span</code> element and its descendants as a whole.</p><p>Any animation elements specified by children in the <code>Animation.class</code>
element group apply semantically to the <code>span</code> element.</p><table summary="HTML Table" id="elt-syntax-span" class="syntax"><caption>XML Representation – Element Information Item: span</caption><tbody><tr><td>
<div class="exampleInner"><pre>
@@ -2246,8 +2258,8 @@
<code>underline</code> |
<code>noUnderline</code>
] || [
-<code>throughline</code> |
-<code>noThroughline</code>
+<span class="diff-chg"><code>lineThrough</code></span> |
+<span class="diff-chg"><code>noLineThrough</code></span>
] || [
<code>overline</code> |
<code>noOverline</code>
@@ -2380,7 +2392,7 @@
<a href="#content-vocabulary-p"><code>p</code></a>,
<a href="#layout-vocabulary-region"><code>region</code></a>,
<a href="#content-vocabulary-span"><code>span</code></a>
-</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>The <code>tts:visibility</code> style has no affect on content layout or
+</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: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>
<div class="exampleInner"><pre>
<region xml:id="r1">
@@ -2443,7 +2455,7 @@
I'll tell thee everything I can:<br/>
There's little to relate.<br/>
I saw an aged aged man,<br/>
- A-sitting on a gate."
+ A-sitting on a gate.<span class="diff-del">"</span>
</p>
</pre></div>
</td></tr></tbody></table><p/><table summary="HTML Table" id="style-attribute-wrapOption-example-1-images" class="example-images"><caption>Example Rendition – Wrap Option</caption><tbody><tr><td><img src="images/wrapOption.png" alt="DFXP wrapOption style property"/></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property
@@ -2630,7 +2642,7 @@
<h4><a name="style-value-duration" id="style-value-duration"/>8.3.4 <duration></h4><p>A <duration> expression is used to express a temporal duration value.</p><table summary="HTML Table" id="duration-style-expression-syntax" class="syntax"><caption>Syntax Representation – <duration></caption><tbody><tr><td>
<div class="exampleInner"><pre>
<duration>
- : <a href="#style-value-digit"><digit></a> ( "." <a href="#style-value-digit"><digit></a>+ )? metric
+ : <a href="#style-value-digit"><digit></a><span class="diff-add">+</span> ( "." <a href="#style-value-digit"><digit></a>+ )? metric
metric
: "s" // seconds
@@ -3159,7 +3171,9 @@
populating the style properties of <code>fo:block</code> by using the computed style
specification set associated with each original TT AF content element;</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, map the element or
+<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>,
+map the element or
sequence of character items to a distinct <code>fo:inline</code> element,
populating the style properties of <code>fo:inline</code> by using the computed style
specification set associated with each original TT AF content element
@@ -3424,7 +3438,7 @@
specified, the value of a <code>begin</code> attribute must adhere to
a <timeExpression> specification as defined by <a href="#timing-value-timeExpression"><b>10.3.1 <timeExpression></b></a>.</p><p>The begin point of a temporal interval is included in the
interval; i.e., the interval is left-wise closed.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>begin</code> attribute are based upon that defined
-by <a href="#smil21">[SMIL 2.1]</a>, § 10.3.1.</p></div></div><div class="div3">
+by <a href="#smil21">[SMIL 2.1]</a>, § <span class="diff-chg">10.4.1</span>.</p></div></div><div class="div3">
<h4><a name="timing-attribute-end" id="timing-attribute-end"/>10.2.2 end</h4><p>The <code>end</code> attribute is used to specify the ending point
of a temporal interval associated with a timed element. If
specified, the value of an <code>end</code> attribute must adhere to a
@@ -3437,12 +3451,12 @@
are limited to frames 300 through 309 only (assuming that 0s corresponds
with frame 0). The same holds if the active interval is specified
as [300f,310f).</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>end</code> attribute are based upon that defined
-by <a href="#smil21">[SMIL 2.1]</a>, § 10.3.1.</p></div></div><div class="div3">
+by <a href="#smil21">[SMIL 2.1]</a>, § <span class="diff-chg">10.4.1</span>.</p></div></div><div class="div3">
<h4><a name="timing-attribute-dur" id="timing-attribute-dur"/>10.2.3 dur</h4><p>The <code>dur</code> attribute is used to specify the duration of a
temporal interval associated with a timed element. If specified,
the value of a <code>dur</code> attribute must adhere to a
<timeExpression> specification as defined by <a href="#timing-value-timeExpression"><b>10.3.1 <timeExpression></b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the <code>dur</code> attribute are based upon that defined
-by <a href="#smil21">[SMIL 2.1]</a>, § 10.3.1.</p></div></div><div class="div3">
+by <a href="#smil21">[SMIL 2.1]</a>, § <span class="diff-chg">10.4.1</span>.</p></div></div><div class="div3">
<h4><a name="timing-attribute-timeContainer" id="timing-attribute-timeContainer"/>10.2.4 timeContainer</h4><p>The <code>timeContainer</code> attribute is used to specify a local temporal
context by means of which timed child elements are temporally situated.</p><p>If specified, the value of a <code>timeContainer</code> attribute must be one
of the following:</p><ul><li><p><code>par</code></p></li><li><p><code>seq</code></p></li></ul><p>If the time container semantics of an element instance is <code>par</code>,
@@ -3863,7 +3877,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, withing, and from a presentation undergoing dynamic flow processing.</p><div class="div3">
+formatted content into, within<span class="diff-del">g</span>, and from a presentation undergoing dynamic flow processing.</p><div class="div3">
<h4><a name="flowOperationFill" id="flowOperationFill"/>B.4.1 Fill Operation</h4><p>A <em>fill operation</em> causes the following ordered steps
to be performed:</p><ol class="enumar"><li><p>remove sufficient content from the beginning of the
<em>flow buffer</em> to constitute a <em>fill
@@ -7065,7 +7079,7 @@
<h2><a name="derivation" id="derivation"/>I 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="d3e11525" id="d3e11525"/>I.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table I-1 – Elements</b></a>
+<h3><a name="d3e11612" id="d3e11612"/>I.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table I-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
@@ -7117,7 +7131,7 @@
<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="d3e11909" id="d3e11909"/>I.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table I-2 – Attributes</b></a>
+<h3><a name="d3e11996" id="d3e11996"/>I.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table I-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
@@ -7190,9 +7204,9 @@
<h2><a name="qa" id="qa"/>J 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="d3e12761" id="d3e12761"/>J.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table J-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="d3e12848" id="d3e12848"/>J.1 Requirements</h3><table summary="HTML Table" id="qa-framework-requirements-table" class="common"><caption>Table J-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="d3e12925" id="d3e12925"/>J.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table J-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="d3e13012" id="d3e13012"/>J.2 Guidelines</h3><table summary="HTML Table" id="qa-framework-guidelines-table" class="common"><caption>Table J-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>I 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 Sun Dec 14 06:10:23 2008 +0000
+++ b/spec/ttaf1-dfxp.xml Sun Dec 14 09:05:00 2008 +0000
@@ -2056,14 +2056,19 @@
<head>div</head>
<p>The <el>div</el> element functions as a logical container and a temporal
structuring element for a sequence of textual content units represented as
-logical paragraphs.</p>
+logical <phrase diff="add">sub-divisions or </phrase>paragraphs.</p>
<note role="explanation">
<p>When rendered on a continuous (non-paged) visual presentation medium,
-a <el>div</el> element is expected to generate a single block area that
-contains zero or more child block areas generated by the <el>div</el>
-element's child <el>p</el> elements.
+a <el>div</el> element is expected to generate
+<phrase diff="del">a single</phrase><phrase diff="add">one or more</phrase> block
+area<phrase diff="add">s</phrase>
+that contain<phrase diff="del">s</phrase> zero or more child block areas
+generated by the <el>div</el> element's
+<phrase diff="del">child</phrase><phrase diff="add">descendant</phrase>
+<el>p</el> elements.
</p>
-<p>If the single block area generated by a <el>div</el> element does
+<p>If <phrase diff="del">the single</phrase><phrase diff="add">some</phrase>
+block area generated by a <el>div</el> element does
not contain any child areas, then it is not expected to be presented.</p>
</note>
<p>The <el>div</el> element accepts as its children zero or more
@@ -2071,8 +2076,10 @@
followed by zero or more
elements in the <code>Animation.class</code> element group,
followed by
-zero or more <el>p</el> elements.</p>
-<note role="motivation">
+zero or more
+<phrase diff="add"><el>div</el> or </phrase>
+<el>p</el> elements.</p>
+<note role="motivation" diff="del">
<p>The core vocabulary intentionally does not support nested divisions in order to reduce
the complexity of the profile to match that of the legacy distribution formats with which
the core vocabulary was designed to interoperate.</p>
@@ -2115,9 +2122,13 @@
<p>An author may associate a set of style properties with a <el>div</el> element by means of either
the <att>style</att> attribute or inline style attributes or a combination thereof.</p>
<note role="explanation">
-<p>Style properties that are associated to a <el>div</el> element in a document instance
+<p>Style properties that are associated
+<phrase diff="del">to</phrase><phrase diff="add">with</phrase>
+a <el>div</el> element in a document instance
are available for style inheritance by descendant content elements such as
-<el>p</el> and <el>span</el>.</p>
+<phrase diff="add"><el>div</el>, </phrase>
+<el>p</el><phrase diff="add">,</phrase>
+and <el>span</el>.</p>
</note>
</div3>
<div3 id="content-vocabulary-p">
@@ -2184,9 +2195,10 @@
elements in the <code>Animation.class</code> element group,
followed by
zero or more
-<code>br</code> element
+<phrase diff="add"><el>span</el> elements ,</phrase>
+<el>br</el> element<phrase diff="add">s,</phrase>
or text nodes interpreted as anonymous spans.</p>
-<note role="motivation">
+<note role="motivation" diff="del">
<p>The core vocabulary intentionally does not support nested spans in order to reduce
the complexity of the profile to match that of the legacy distribution formats with which
the core vocabulary was designed to interoperate.</p>
@@ -4421,8 +4433,8 @@
<code>underline</code> |
<code>noUnderline</code>
] || [
-<code>throughline</code> |
-<code>noThroughline</code>
+<phrase diff="chg"><code>lineThrough</code></phrase> |
+<phrase diff="chg"><code>noLineThrough</code></phrase>
] || [
<code>overline</code> |
<code>noOverline</code>
@@ -4730,8 +4742,12 @@
</td>
</tr>
<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
+<td><emph>Inherited:</emph></td>
+<td>yes</td>
+</tr>
+<tr>
+<td><emph>Percentages:</emph></td>
+<td>N/A</td>
</tr>
<tr>
<td><emph>Animatable:</emph></td>
@@ -4872,7 +4888,7 @@
I'll tell thee everything I can:<br/>
There's little to relate.<br/>
I saw an aged aged man,<br/>
- A-sitting on a gate."
+ A-sitting on a gate.<phrase diff="del">"</phrase>
</p>
</eg>
</td>
@@ -5253,7 +5269,7 @@
<td>
<eg xml:space="preserve">
<duration>
- : <loc href="#style-value-digit"><digit></loc> ( "." <loc href="#style-value-digit"><digit></loc>+ )? metric
+ : <loc href="#style-value-digit"><digit></loc><phrase diff="add">+</phrase> ( "." <loc href="#style-value-digit"><digit></loc>+ )? metric
metric
: "s" // seconds
@@ -6168,7 +6184,9 @@
<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 span, map the element or
+<code>none</code> and for each anonymous
+span<phrase diff="add"> that is a child of a <el>p</el> or <el>span</el> element</phrase>,
+map the element or
sequence of character items to a distinct <el>fo:inline</el> element,
populating the style properties of <el>fo:inline</el> by using the computed style
specification set associated with each original TT AF content element
@@ -6336,7 +6354,7 @@
interval; i.e., the interval is left-wise closed.</p>
<note role="derivation">
<p>The semantics of the <att>begin</att> attribute are based upon that defined
-by <bibref ref="smil21"/>, § 10.3.1.</p>
+by <bibref ref="smil21"/>, § <phrase diff="chg">10.4.1</phrase>.</p>
</note>
</div3>
<div3 id="timing-attribute-end">
@@ -6361,7 +6379,7 @@
</note>
<note role="derivation">
<p>The semantics of the <att>end</att> attribute are based upon that defined
-by <bibref ref="smil21"/>, § 10.3.1.</p>
+by <bibref ref="smil21"/>, § <phrase diff="chg">10.4.1</phrase>.</p>
</note>
</div3>
<div3 id="timing-attribute-dur">
@@ -6373,7 +6391,7 @@
ref="timing-value-timeExpression"/>.</p>
<note role="derivation">
<p>The semantics of the <att>dur</att> attribute are based upon that defined
-by <bibref ref="smil21"/>, § 10.3.1.</p>
+by <bibref ref="smil21"/>, § <phrase diff="chg">10.4.1</phrase>.</p>
</note>
</div3>
<div3 id="timing-attribute-timeContainer">
@@ -7187,7 +7205,7 @@
<div2 id="dynamicFlowOperations">
<head>Flow Operations</head>
<p>Flow operations perform the filling, reflowing, and clearing of
-formatted content into, withing, and from a presentation undergoing dynamic flow processing.</p>
+formatted content into, within<phrase diff="del">g</phrase>, and from a presentation undergoing dynamic flow processing.</p>
<div3 id="flowOperationFill">
<head>Fill Operation</head>
<p>A <emph>fill operation</emph> causes the following ordered steps
--- a/spec/xmlspec-ttaf1-dfxp.xsl Sun Dec 14 06:10:23 2008 +0000
+++ b/spec/xmlspec-ttaf1-dfxp.xsl Sun Dec 14 09:05:00 2008 +0000
@@ -41,8 +41,8 @@
.strong { font-weight: bold }
.reqattr { font-weight: bold }
.optattr { font-style: italic }
-.diff-add { color: red; }
-.diff-del { color: red; text-decoration: line-through; }
+.diff-add { color: red; background-color: #99FF99; }
+.diff-del { color: red; text-decoration: line-through; background-color: #99FF99; }
.diff-chg { background-color: #99FF99; }
.diff-off {}
</xsl:text>
@@ -97,6 +97,16 @@
<xsl:apply-templates/>
</span>
</xsl:when>
+ <xsl:when test="ancestor-or-self::note">
+ <div xmlns="http://www.w3.org/1999/xhtml" class="diff-{$diff}">
+ <div class="note">
+ <p class="prefix">
+ <b>Note:</b>
+ </p>
+ <xsl:apply-templates/>
+ </div>
+ </div>
+ </xsl:when>
<xsl:otherwise>
<div xmlns="http://www.w3.org/1999/xhtml" class="diff-{$diff}">
<xsl:apply-templates/>