SMIL 2.0 Recommendation Errata

This version:

http://www.w3.org/2001/07/REC-SMIL20-20010731-errata

Last modified:

$Date: 2004/12/23 22:05:59 $

This document records known errors in the document:

http://www.w3.org/TR/2001/REC-smil20-20010807/ 

The latest version of the SMIL 2.0 specification is at:

http://www.w3.org/TR/smil20/

Copyright © 2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.

---

About the SMIL 2.0 Recommendation

The SMIL 2.0 Recommendation has been produced by the W3C SYMM Working Group as part of the activity of the W3C Interaction Domain.

This document lists the known errata to the SMIL 2.0 Recommendation. Each entry has the following information:

• A unique entry number
• The date it was added to the errata page.
• Whether the entry is considered an important error, a minor typographical error, a clarification, or a known problem with the document itself.
• The section referred to.
• A description of the problem and correction if applicable.

Please send general comments about this document to the public mailing list www-smil@w3.org. An archive is available at http://lists.w3.org/Archives/Public/www-smil/.

The following erratas have been discussed and resolved by the former W3C SYMM Interest Group and current SYMM Working Group.

Note: To allow proper validation of SMIL 2.0 Documents, the DTD errata and Schemas errata are also updated in the DTD module identified by the PUBLIC and SYSTEM identifiers:

(for exemple the errata E10, the DTD is updated for the Linking module
PUBLIC "-//W3C//ELEMENTS SMIL 2.0 Linking//EN" SYSTEM "http://www.w3.org/2001/SMIL20/SMIL-link.mod"

(for exemple the errata E26, the Schema is updated for the Linking at public URI http://www.w3.org/2001/SMIL20/smil20-linking.xsd)

The downloadable Zip file are also updated accordinglly.

• http://www.w3.org/2001/SMIL20/schemas.zip
• http://www.w3.org/2001/SMIL20/DTD.zip

Conventions

Added text marked thus. Removed text marked thus. Changed text marked thus.

Known errors as of June 02 2004

1. E01: Typographical error  in section SMIL 2.0 Introduction (revised 28 08 2001)
2. E02: Clarification  in section Index of attributes (revised 13 09 2001)
3. E03: Typographical error  in section 5.9.1. (hierarchical region Layout) (revised 13 09 2001)
4. E04: Typographical error  in section 4.2.2 for definition of "systemCaptions" (revised 13 09 2001)
5. E05: Clarification in section 7.10.1 Appendix A: Changes to SMIL 1.0 Media Object Attributes (revised 13 09 2001)
6. E06: Substantive error in section 3.5.3 The "animateMotion" element (revised 13 09 2001)
7. E07: Substantive error in section 7 : Media Object module (revised 13 09 2001)
8. E08: Substantive error in section 10.3.2: definition of "priorityClass" (revised 01 10 2001)
9. E09: Substantive error in appendix A.1.6: The SMIL Metainformation Module  (revised 01 10 2001)
10. E10: Substantive DTD error in appendix A.1.4: The SMIL Linking Module  (revised 01 10 2001)
11. E11: Clarification in section 4.2.2: definition of "systemComponent" (revised 01 10 2001)
12. E12: Clarification In section 3.7.1 SMIL 2.0 SplineAnimation Module Attributes, under Calculation mode attributes (revised 01 11 2001)
13. E13: Clarification in event-based timing section (revised 12 11 2001)
14. E14: Correction in the pseudo-code for the computation of getFirstInterval() in section 10.3.3 (revised 13 11 2001)
15. E15: Correction in the pseudo-code for the computation of getNextInterval() in section 10.3.3 (revised 13 11 2001)
16. E16: Correction in the description of repeatEvent in section 13.3.11 (revised 22 11 2001)
17. E17: Correction in SMIL20 Language Profile the reference to the area element should be removed from section 13.3.7 (revised 01 12 2001).
18. E18: Correction in SMIL20 Language Profile the reference to the area element should be removed from section 13.3.11 (revised 01 12 2001)
19. E19: Correction in SMIL20 Language Profile, the reference MediaDescription module was inadvertently omitted from the list of modules in section 13.3.3 (revised 13 12 2001).
20. E20: Typographical error in the list of SMIL 2.0 modules in in section 2.2 (revised 13 12 2001).
21. E21: Typographical error in the SMIL 2.0 Metainformation Module example in section 8.4 (revised 07 01 2002).
22. E22: Correction in SMIL 2.0 Animation Module, Specifying the simple animation function f(t) in section 3.4.2 (revised 08 01 2002).
23. E23: Typographical error in the SMIL 2.0 Linking Module examples in section 6.5.2 (revised 21 02 2002).
24. E24: Typographical error in SMIL 2.0 Transition Module, examples in section 12.4.1 and section 12.4.2 (revised 21 02 2002)
25. E25: Correction in SMIL20 Transition Module for the transitionFilter element in section 12.5.1 (revised 21 02 2002)
26. E26: Substantive error in SMIL 2.0 The SMIL Linking Module schema, Appendix B.1.5 (revised 21 02 2002)
27. E27: Clarification in the SMIL 2.0 Linking Module, in section 6.2.2 , Relationship with XLink (revised 26 02 2002)
28. E28: Correction in the SMIL 2.0 Linking Module, section 6.2.2 (revised 26 02 2002)
29. E29: Correction in SMIL20 Transition Module, section 12.4.1, definition of the 'fadeColor' attribute (revised 18 03 2002)
30. E30: Correction in the SMIL 2.0 utility Schema (revised 29 03 2002)
31. E31: Correction in the SMIL 2.0 Animation Module (revised 08 04 2002)
32. E32: Correction for <excl> example in SMIL 2.0 Timing and Synchronization Module (revised 15 04 2002)
33. E33: Correction in the SMIL 2.0 Timing and Synchronization Module, Hyperlinks and timing section (revised 16 09 2002)
34. E34: Clarification in the SMIL 2.0 Linking section 6.4 (revised 17 09 2002)
35. E35: Correction in the SMIL 2.0 Language Profile, section 13.3.8 Media Object Modules (revised 17 09 2002)
36. E36: Correction in the SMIL 2.0 Linking Module for the destinationPlaystate attribute, section 6.4 (revised 17 04 2002))
37. E37: Substantive DTD error in appendix A.1.4: The SMIL Linking Module (revised 17 04 2002)
38. E38: Clarification in The SMIL 2.0 Transition Effects Module, section 12.8.1  (revised 09 10 2002)
39. E39: Correction in The SMIL 2.0 Transition Effects Module,section 12.6  (revised 09 10 2002)
40. E40: Typographical error in the SMIL 2.0 Transition Effects Modulein sections 12.4.2 and 12.5.2 The param element  (revised 20 02 2003)
41. E41: Correction in the SMIL 2.0 Timing and Synchronization Module in section 12.4.2 Semantics of the Timing Model  (revised 20 02 2003)
42. E42: Clarification in the SMIL 2.0 Animation Module in section 3.5.3 The animateMotion element  (revised 20 02 2003)
43. E43: Correction in the SMIL 2.0 Timing Module (Section 10.3.1, under Timing attribute value grammars)  (revised 20 02 2003)
44. E44: Clarification in the SMIL 2.0 Animation Modules, Section 3.4.1.  (revised 24 02 2003)
45. E45: Substantive DTD error in Appendix A.3.2 SMIL 2.0 common attributes for customTest attribute of the Content Control Modules (revised 2 06 2004)
46. E46: Substantive DTD error in Appendix A.1.9 for hozRepeat and vertRepeat attributes of the TransitionModifiers Module (revised 2 06 2004)
47. E47: Correction in the SMIL 2.0 MediaClipping Module, section 7.5.1 (revised 2 06 2004)
48. E48: Clarification in SMIL 2.0 Timing and Synchronization Module, in section 10.3.3 for min attribute and time container constraints (revised 2 06 2004)
49. E49: Clarification in SMIL 2.0 Linking Module, in section 6.5.2 for nohref attribute definition (revised 2 06 2004)
50. E50: Typographical error  in the SMIL 2.0 Language Profile, in section 13.3.7 (revised 2 06 2004)
51. E51: Clarification in SMIL 2.0 Timing and Synchronization Module section 10.3.3 (revised 2 08 2004)
52. E52: Substantive DTD error in Appendix A.3.1 SMIL 2.0 common datatypes (revised 2 08 2004)
53. E53: Clarification added in SMIL20 Second Edition to clarify the normative SMIL 2.0 DTD (revised 5 11 2004)
54. E54: Clarification added in SMIL20 Second Edition for Namespace policy (revised 5 11 2004)

Rejected proposed erratas:

1. R01: Clarification in the the SMIL 2.0 Language Profile <animateMotion> on <brush> (revised 16 09 2002)
2. R02: Architectural error in the definition of the type attribute (section 7.3.1) (revised 2 06 2004)

Erratas:

- E01: Typographical error  in section SMIL 2.0 Introduction (revised 28 08 2001)

Description: The XHTML+SMIL WD date (06 August 2001) is wrong.
Correction: All XHTML+SMIL examples in this Recommendation conform to the Profile as of the Working Draft of 07 August 2001.

- E02: Clarification  in section Index of attributes (revised 13 09 2001)

Description: Missing "sensitivity" attribute in the attribute index.
Correction: sensitivity.

- E03: Typographical error  in section 5.9.1. (hierarchical region Layout) (revised 13 09 2001)

Description: The first example: the start tag of topLayout should have a ">" i.s.o. " />".
Correction:

<topLayout width="640px" height="480px"/>

- E04: Typographical error  in section 4.2.2 for definition of "systemCaptions" (revised 13 09 2001)

Description: double occurrence of "to" in "allows authors to to specify"
Correction: This attribute allows authors to to specify a redundant text equivalent ...

- E05: Clarification in section 7.10.1 Appendix A: Changes to SMIL 1.0 Media Object Attributes (revised 13 09 2001)

Description: Incorrect explanation for "clipBegin"/"clip-begin" precedence rules

Correction: SMIL 1.0 players implementing the recommended extensibility rules of SMIL 1.0 [SMIL10] will ignore the clip attributes using the new functionality, since they are not part of SMIL 1.0. SMIL 2.0 players, in contrast, will ignore the clip attributes using SMIL 1.0 syntax, since they occur later in the text because the SMIL 2.0 syntax takes precedence over the SMIL 1.0 syntax.

- E06: Substantive error in section 3.5.3 The "animateMotion" element (revised 13 09 2001)

Description: The BNF of the coordinate-pair should wrap the brackets in between quotes such as to make them literals

Correction:

coordinate-pair ::="(" coordinate comma-wsp coordinate")"

For example:

<img ... region="window" left="10" bottom="10" width="10" height="10">
<animateMotion from="(10,10)" to="(20,20)" fill="freeze" />
</img>

Note that the coordinates in the animateMotion are top-left pairs (not left-bottom).

- E07: Substantive error in section 7 : Media Object module (revised 13 09 2001)

Description: Difference between normative and informative text not marked in Media Object module

Correction: To clarify, numbered sections in the Media Object module are normative, and the examples and appendices are informative.

- E08: Substantive error in section 10.3.2: definition of "priorityClass" (revised 01 10 2001)

Description: In the section describing the "priorityClass" element has a bulleted list. The first two items in the bullets list currently read:

• priorityClass elements can only be children of an excl.
• priorityClass elements can only have media elements as (timed) children.

Correction: That is, priorityClass elements cannot be nested, The first two bullets should read:

• priorityClass elements may only appear as immediate children of excl elements and cannot be nested.
• Only elements allowed as immediate children of excl may appear as immediate children of priorityClass elements.

- E09: Substantive error in appendix A.1.6: The SMIL Metainformation Module  (revised 01 10 2001)

Description: DTD should make "content" attribute required for "meta" elements.

Correction: The text of section 8.3.1 correctly specifies the "content" attribute as being required for "meta" elements. The corresponding default declaration in section A.1.6 should thus be #REQUIRED instead of #IMPLIED:

<!ATTLIST %SMIL.meta.qname; %SMIL.meta.attrib;
%Core.attrib;
%I18n.attrib;
content CDATA #IMPLIED #REQUIRED
name CDATA #REQUIRED
>

- E10: Substantive DTD error in appendix A.1.4: The SMIL Linking Module  (revised 01 10 2001)

Description: DTD should make "href" attribute required for "a" elements.

Correction: The text of section 6.5.1 correctly specifies the "href" attribute as being required for "a" elements. The corresponding default declaration in section A.1.4 should thus be #REQUIRED instead of #IMPLIED:

<!ATTLIST %SMIL.a.qname; %SMIL.a.attrib;
%SMIL.linking-attrs;
href %URI.datatype; #IMPLIED #REQUIRED
%Core.attrib;
%I18n.attrib;
>

- E11: Clarification in section 4.2.2: definition of "systemComponent" (revised 01 10 2001)

Description: Incorrect explanation for "systemComponent" values rules, in following sentence:

• Evaluates to true if the resulting value is true. Evaluates to false otherwise.

Correction: Should read:

• Evaluates to true if all URI's match one of the URI's that the user agent recognizes. Evaluates to false otherwise.

- E12: Clarification In section 3.7.1 SMIL 2.0 SplineAnimation Module Attributes, under Calculation mode attributes, calcMode (revised 01 11 2001)

Description: Incorrect name of Animation module in following sentence:

• "In addition to the values discrete, linear and paced of the BasicAnimation module, the AdvanceAnimation module supports the value spline"

Correction: Should read:

• "In addition to the values discrete, linear and paced of the BasicAnimation module, the SplineAnimation module supports the value spline".

- E13: Clarification in event-based timing section (revised 12 11 2001)

Description:

• The SMIL 2.0 test suite contains many examples of event-based timing, and states the preferred behavior for these tests. However, it is acknowledged that the timing of event propagation is implementation dependent, and so there are occasions in which delivery of an event may not occur because an intervening state change in the timegraph precludes event delivery (as per the event sensitivity rules). That is, after the event generation but before the event dispatch and handling something else in the timegraph is evaluated which precludes event delivery. This includes the internally generated timing events beginEvent, endEvent, and repeatEvent, as well as externally generated events such as the focusInEvent and focusOutEvent.
  In these cases, it is desirable for model implementations to behave as if they responded to the internal timing events instantaneously, but an implementation is considered conformant if event propagation delay precludes this behavior.
• For example, in timing test case 1.15, the delivery of the image1.beginEvent to the image2 element may not occur until after the par has ended at 3s (due to image1 having 0 duration and no other children of the par with resolved begin times), and so it is also compliant behavior for the image1 element to show for 0 seconds and then for the par to end..

- E14: Correction in the pseudo-code for the computation of getFirstInterval() in section 10.3.3 (revised 13 11 2001)

Description:

• // We have an end - is it after the parent simple begin?
if( tempEnd > 0 )
return( Interval( tempBegin, tempEnd ) );
else
// Change beginAfter to find next interval, and loop
beginAfter = tempEnd;

Correction: Should read:

• // We have an end - is it after the parent simple begin?
// Handle the zero duration intervals at the parent begin time as a special case
if( tempEnd > 0 || (tempBegin==0 && tempEnd==0))
return( Interval( tempBegin, tempEnd ) );
else
// Change beginAfter to find next interval, and loop
beginAfter = tempEnd;
  

- E15: Correction in the pseudo-code for the computation of getNextInterval() in section 10.3.3 (revised 13 11 2001)

Description:

• Set tempBegin = the first value in the begin list that is >= beginAfter.

Correction: Should read:

• If (currentInterval.end > currentInterval.begin)
Set tempBegin = the first value in the begin list that is >= beginAfter.
Else
Set tempBegin = the first value in the begin list that is > beginAfter..

- E16: Correction in the description of repeatEvent in section 13.3.11 (revised 22 11 2001)

Description:

• repeatEvent:
  Fired when the second and subsequent iterations of a repeated element begin playback. An element that has no repeatDur, repeatCount, or repeat attribute but that plays two or more times due to multiple begin times will not raise a repeatEvent when it restarts. Also, children of a time container that repeats will not raise their own repeatEvents when their parent repeats and they begin playing again. The beginEvent is delivered to elements which support timing, such as media elements and time containers, and does not bubble.

Correction: Should read:

• repeatEvent:
  Raised when the second and subsequent iterations of a repeated element begin playback. An element that has no repeatDur, repeatCount, or repeat attribute but that plays two or more times due to multiple begin times will not raise a repeatEvent when it restarts. Also, children of a time container that repeats will not raise their own repeatEvents when their parent repeats and they begin playing again. The repeatEvent is delivered to elements which support timing, such as media elements and time containers, and does not bubble.

- E17: Correction in SMIL20 Language Profile the reference to the area element should be removed from section 13.3.7 (revised 01 12 2001). The content model of the par, seq, and excl elements is correctly defined in the section tables, schema and DTD. The reference to the area element was inadvertently added to the prose in this section.

Description:

• This profile adds the area and a elements to the content model of the par, seq, and excl elements of the Timing and Synchronization Modules. It also adds these elements to the content model of the body element of the Structure Module.

Correction: Should read:

• This profile adds the a element to the content model of the par, seq, and excl elements of the Timing and Synchronization Modules. It also adds this element to the content model of the body element of the Structure Module.

- E18: Correction in SMIL20 Language Profile the reference to the area element should be removed from section 13.3.11 (revised 01 12 2001). The content model of the a and area elements is correctly defined in the section tables, schema and DTD. The reference to the area element was inadvertently added to the prose in this section.

Description:

• This profile adds the par, seq, and excl elements to the content model of the body element of the Structure Module and adds these elements to the content model of the a and area elements of the Linking Modules.

Correction: Should read:

• This profile adds the par, seq, and excl elements to the content model of the body element of the Structure Module and adds these elements to the content model of the a element from the Linking Modules.

- E19: Correction in SMIL20 Language Profile, the reference MediaDescription module was inadvertently omitted from the list of modules in section 13.3.3 (revised 13 12 2001).

Description:

• The reference MediaDescription module was inadvertently omitted from the list of modules.

Correction: Should read:

• The MediaDescription module should be explicitly included in the list of modules making up the SMIL20 Language Profile. The module is implicitly required since the included MediaAccessibility module depends on MediaDescription. The content model of the media elements is correctly defined in the section tables, schema and DTD and clearly shows the inclusion of the MediaDescription module.

- E20: Typographical error in the list of SMIL 2.0 modules in in section 2.2 (revised 13 12 2001).

Description:

• In the list of SMIL 2.0 modules there is a typo: "BasicTransistions"

Correction: Should read:

"BasicTransitions"

- E21: Typographical error in the SMIL 2.0 Metainformation Module example in section 8.4 (revised 07 01 2002).

Description:

• In the example there is a typo in the attribute: <rdf:li Resource=

Correction: Should read:

<rdf:li resource=

- E22: Correction in SMIL 2.0 Animation Module, Specifying the simple animation function f(t) in section 3.4.2 (revised 08 01 2002).

Description: In the normative section, the specification of the simple animation function f(t) is revised.

Normative

With i = floor((t*n)/d), d the simple duration of the animation element, n the number of entries in the values attribute and value[i] the ith entry (counting from 0):

• For discrete animation, the duration is divided inton equal time periods, one per value. The animation function takes on the values in order, one value for each time period:

  f(t) = value[i]

• For linear animation, the duration is divided inton-1 equal periods, and the animation function is a linear interpolation between the values at the associated times:

        f(t) = value[i] + (value[i+1]-value[i]) * (t-ti)/d.

• For paced animations, the duration is divided into periods of lengths such that the rate of change of the attribute remains constant. If the distance between two values is dist(v1,v2), the total distance traversed D(i) up to and including value[i] is

  D(0) = 0, and

  D(i) = dist(value[0],value[1]) + dist(value[1],value[2]) +...+ dist(value[i-1],value[i]), for integers i with 0<i<=n.

  The animation function takes on the values in the values attribute at times determined by these distances:

    T(i) = (D(i)/D(n)) * d, for integers i with 0<=i<=n.

    f(t) = value[i] + (value[i+1]-value[i]) * (t-T(i))/d,

  where i is the largest non-negative integer such that T(i)<=t.

Note that a linear or paced animation will be a smoothly closed loop if the first value is repeated as the last.

Correction: Should read:

Normative

Let i = floor((t*n)/d), d be the simple duration of the animation element, n be the number of entries in the values attribute, value[i] be the ith entry (counting from 0), di be the duration of the ith time period, and ti be the time at which the ith time period begins.

• For discrete animation with nokeyTimesattribute, the duration is divided into n equal time periods, one per value. With a keyTimes attribute, the time periods are specified by the keyTimesvalues. The animation function takes on the values in order, one value for each time period:

      f(t) = value[i]

• For linear animation with nokeyTimes attribute, the duration is divided inton-1 equal periods, anddi = d/(n-1) for any value ofi. The animation function is a linear interpolation between the values at the associated times: 

       f(t) = value[i] + (value[i+1] - value[i]) * (t - ti)/di

With a keyTimes attribute, the time periods are specified by the keyTimes values and so di is the duration of the ith period as defined by the keyTimes values:

       di = (keyTimes[i+1] - keyTimes[i]) * d

• For paced animations, the duration is divided into periods of lengths such that the rate of change of the attribute remains constant. If the distance between two values is dist(v1,v2), the total distance traversed D(i) up to and including value[i] is

    D(0) = 0, and

    D(i) = dist(value[0],value[1]) + dist(value[1],value[2]) +...+ dist(value[i-1],value[i]), for integers i with 0<i<= n.

The animation function takes on the values in the values attribute at times determined by these distances:

    ti = (D(i)/D(n)) * d, for integers i with 0<=i<=n.

    di = ti+1 - ti = ((D(i+1) - D(i)) / D(n)) * d = (dist(value[i],value[i+1]) / D(n)) * d

    f(t) = value[i] + (value[i+1] - value[i]) * (t-ti)/di,

where i is the largest non-negative integer such that ti<=t.

Note that a linear or paced animation will be a smoothly closed loop if the first value is repeated as the last. The keyTimes attribute is described in the SplineAnimation section.

- E23: Typographical error in the SMIL 2.0 Linking Module examples in section 6.5.2 (revised 20 02 2002).

Description:

The key of the examples 2 and 3 is that different link targets can be active during an object's duration. Unfortunately, the example uses the same link target twice, and both link targets are not well-formed (no closing '"')

Correction: Should read:

2) Associating links with spatial segments:

...
<area shape="rect" coords="5,5,50,50" title="Journalist" href="http://www.example.org/journalist"/>
<area shape="rect" coords="60,5,100,50" title="Subject" href="http://www.example.org/subject"/>
...

3) Associating links with temporal segments

...
<area begin="0s" dur="20s" title="first question" href="http://www.example.org/question"/>
<area begin="20s" dur="50s" title="first answer" href="http://www.example.org/answer"/>

...

8) The coords attribute and re-sized images

...
<layout>
<region id="region" right="50" bottom="50"/>
...

- E24: Typographical error in SMIL 2.0 Transition Module, examples in section 12.4.1 and section 12.4.2 (revised 21 02 2002)

Description:

The transition element allows the "fadeColor" attribute, but examples at the section 12.4.1 and 12.4.3 use attribute 'color' instead of 'fadeColor'.

Correction: Should read:

12.4.1 :

<transition id="ftb2" type="fade" subtype="fadeToColor" dur="2s" fadeColor="#000000"/>

12.4.3 :

<transition id="toblack1s" type="fade" subtype="fadeToColor"
fadeColor="#000000" dur="1s"/>

- E25: Correction in SMIL20 Transition Module for the transitionFilter element in section 12.5.1 (revised 22 02 2002)

Description:

The "must" in the following text is in error.

This element must be the child of a media element or other element with renderable content, as defined by the host language. This is in contrast to BasicTransitions that are declared in the "transition" element and then specified in the transIn or transOut attributes that are applied to media elements.

Correction: Should read:

A transitionFilter element can define the target element of the transition either explicitly or implicitly. An explicit definition uses an attribute to specify the target element. The syntax for this is described below.

If no explicit target is specified, the implicit target element is the parent element of the transitionFilter element in the document tree. It is expected that the common case will be that a transitionFilter element is declared as a child of the element to be animated. In this case, no explicit target need be specified.

This element must target a media element or other element with renderable content, as defined by the host language. This is in contrast to BasicTransitions that are declared in the "transition" element and then specified in the transIn or transOut attributes that are applied to media elements. When an implicit targetElement reference is used, the transitionFilter element must be a child of an element that supports transition effects (or it has no effect).

- E26: Substantive error in SMIL 2.0 The SMIL Linking Module schema, Appendix B.1.5 (revised 25 02 2002)

Description:

In the Normative SMIL DTD, the "nohref" attribute allows the "nohref"value.

The Informative SMIL schema declare an incorrect boolean default value "false" for the "nohref" attribute.

<attribute name="nohref" type="boolean" use="optional" default="false"/>

Correction: Should read:

<attribute name="nohref" use="optional">    
  <simpleType>
    <restriction base="string"> 
      <enumeration value="nohref"/>
    </restriction>
  </simpleType>  
</attribute>

- E27: Clarification in the SMIL 2.0 Linking Module, in section 6.2.2 , Relationship with XLink (revised 26 02 2002)

Description:

The is a reference in the Linking Modules to XLink as if a Recommendation were to be expected in the future, but in reality the XLink REC was finalised in June 2001. Therefore the following sentence should be changed:

"It also makes it easier for SMIL code to be processed into and recognized as XLink code once XLink is released as a recommendation and when the appropriate transform mechanisms become available."

Correction: Should read:

"It also makes it easier for SMIL code to be processed into and recognized as XLink code when the appropriate transform mechanisms become available."

- E28: Correction in the SMIL 2.0 Linking Module, in section 6.2.2 (revised 26 02 2002)

Description:

We here refer to an earlier draft of XLink where the XLink draft had XLink elements, unlike the final XLink Recommendation. Therefore the following sentence should be changed:
"Where possible, SMIL linking constructs have the same element, attribute and value names as constructs from XLink [XLINK]."

Correction: Should read:

"Where possible, SMIL linking constructs have the same names as constructs from XLink [XLINK]."

- E29: Correction in the SMIL 2.0 Transition Modules, section 12.4.1, definition of the 'fadeColor' attribute (revised 18 03 2002)

Description:

The definition of the 'fadeColor' attribute says:
"Legal color values are CSS2 system color values."

Correction: Should read:

"Legal color values are CSS2 color values."

Note that the link now points to http://www.w3.org/TR/REC-CSS2/syndata.html#color-units (instead of the system color section of the CSS spec).

- E30: Correction in the SMIL 2.0 utility Schema, section B.3.48 (revised 29 03 2002)

Description:

Typographic error in the SMIL 2.0 utility Schema, section B.3.48 and in the Public URI: http://www.w3.org/2001/SMIL20/smil20-utility.xsd

The simpleType name="greatThanZeroDecimalType" is wrong. It should be changed to "greaterThanZeroDecimalType"

Correction: Should read:

- <!--  utility types for non-zero values   --> 
- <simpleType name="greaterThanZeroDecimalType"> 

- E31: Correction in the SMIL 2.0 Animation Modules, section 3.2 (revised 08 04 2002)

Description: The SMIL 2.0 Animation chapter must be modified with the seven following changes:

Change 1:

In Section 3.2.2: Add clarification to definition of f(t).

Correction: Change following text

f(t)

The simple animation function of times within the simple duration. Note that while F(t,u) defines the mapping for the entire animation, f(t) has a simplified model that just handles the simple duration.

f(t)

The simple animation function of times within the simple duration. This is defined for t: 0<=t<d.
Note that while F(t,u) defines the mapping for the entire animation, f(t) has a simplified model that just handles the simple duration.

Change 2:

In Section 3.2.2: Add definition of f(d). This is added immediately after the item for f(t), described in Change 1.

Correction: Insert following text

f(d)

While f(t) is not defined for the value t=d, the expression f(d) is used as a shorthand to refer to the last value defined for the animation function.

Change 3:

In Section 3.2.2: Change the time range for F(t,u) to be endpoint exclusive. The only change is to change '<=' to '<' in "...(t: 0<=t<=AD)..."

Correction: Change following text

F(t,u)
The effect of an animation for any point in the active duration of the animation. This maps times within the active duration (t: 0<=t<=AD) and an underlying value to a value for the target attribute. A time value of 0 corresponds to the time at which the animation begins. F(t,u) combines the simple animation function f(t) with all the other aspects of animation and timing controls.

F(t,u)
The effect of an animation for any point in the active duration of the animation. This maps times within the active duration (t: 0<=t<AD) and an underlying value to a value for the target attribute. A time value of 0 corresponds to the time at which the animation begins. F(t,u) combines the simple animation function f(t) with all the other aspects of animation and timing controls.

Change 4:

End of section 3.2.1, make similar change as for Change 3:

Correction: Change following text

The animation effect function, F(t,u), of an animation element with active duration AD is a function mapping times t: 0<=t<=AD and values u of the type of the target attribute a into values of the type of a.

The animation effect function, F(t,u), of an animation element with active duration AD is a function mapping times t: 0<=t<AD and values u of the type of the target attribute a into values of the type of a.

Change 5:

Early in section 3.2.6, remove replicated definition of F(t,u). This uses 'x' and 'y' in place of 'd' and 'AD', adds nothing and is potentially confusing or even contradictory for some readers.

Correction: Remove following text

The animation effect function, F(t,u), for an animation element with simple duration x and active duration y is a function mapping t, 0<=t<=AD and u, a value of the type of the target attribute of the animation into that same type.

Change 6:

Fix conflicting verbiage in intro to section 3.2.5.

Correction: Change following text

Since these functions describe the animation outside of the simple duration, they are defined for any non-negative time t.

Since these functions describe the animation outside of the simple duration, they are defined for any time t:0<=t<AD. The frozen animation function ff(t) is additionally defined for t=AD, to account for the case when the element is frozen.

Change 7:

End of Section 3.2.5: Fix formalisms for ff(t):

Correction: Change following text

The frozen animation function, ff(t), for an element with active duration AD, 0<=t<=AD is given by
ff(t) = fc(t) for all times t: 0<=t<AD

If AD is not an even multiple of the simple duration d,
ff(AD) = fc(AD).

If AD is an even multiple of d, i.e. AD = d*i for some positive integer i, and the animation is non-cumulative,
ff(AD) = f(d).

If AD is an even multiple of d, i.e. AD = d*i for some positive integer i, and the animation is cumulative,
ff(AD) = f(d) * i.

The frozen animation function, ff(t), for an element with active duration AD, is given by
ff(t) = fc(t) for all times t: 0<=t<AD (i.e. before it is frozen)

When the element is frozen, t is effectively equal to AD.
The following equations assume that t is set to AD when the element is frozen.

If AD is not an even multiple of the simple duration d,
ff(t) = fi(t), where i = floor(t/d).

This is equivalent to fc(t), except that fc(t) is not formally defined for t=AD. In this case, the equations remain consistent, and so the equivalent of fc(t) is used for the frozen value ff(t).

If AD is an even multiple of d, i.e. AD = d*i for some positive integer i, and the animation is non-cumulative,
ff(t) = f(d).

If AD is an even multiple of d, i.e. AD = d*i for some positive integer i, and the animation is cumulative,
ff(t) = f(d) * i.

Note that f(d) is a shorthand for the "last value defined for the animation function" (e.g., the "to" value or the last value in the "values" list).

- E32: Correction in the SMIL 2.0 Timing and Synchronization Module, section 10.3.2 (revised 15 04 2002)

Description:

The first example of the <excl> element needs a duration attribute in order to follow the "Implicit duration of excl containers" rule.

Adding an "endsync" attribute on the <par> element allows the presentation to end when the video ends, and so the <excl> would end then as well.

<smil>
...
<par>
   <video id="vid1" .../>
   <excl>
      <par begin="englishBtn.activateEvent">
         <audio begin="vid1.begin" src="english.au" />
      </par>
      <par begin="frenchBtn.activateEvent">
         <audio begin="vid1.begin" src="french.au" />
      </par>
      <par begin="swahiliBtn.activateEvent">
         <audio begin="vid1.begin"src="swahili.au" />
      </par>
   </excl>
</par>
...
</smil>

Correction: Should read:

<smil>
...
<par endsync="vid1">
   <video id="vid1" .../>
   <excl dur ="indefinite">
      <par begin="englishBtn.activateEvent">
         <audio begin="vid1.begin" src="english.au" />
      </par>
      <par begin="frenchBtn.activateEvent">
         <audio begin="vid1.begin" src="french.au" />
      </par>
      <par begin="swahiliBtn.activateEvent">
         <audio begin="vid1.begin"src="swahili.au" />
      </par>
   </excl>
</par>
...
</smil>

- E33: Correction in the SMIL 2.0 Timing and Synchronization Module, Hyperlinks and timing section (revised 16 09 2002)

Description: The SMIL 2.0 Timing and Synchronization Module chapter must be modified with the three following changes:

Change 1:

In the Hyperlinks and timing section, add clarification to the wording of the informative example.

Correction: Change following text

The begin of elements C and D are unresolved when the document starts. Therefore activating the hyperlink will have no effect upon the presentation time or upon elements C and D.

Should read:

The begin of elements C and D are unresolved when the document starts. Therefore activating the hyperlink will resolve the begin of D but have no effect upon the presentation time for element C.

Change 2:

In the Hyperlinks and timing section, add clarification to the second normative section.

Correction: Change following text

If an element is active at the time of hyperlinking and the element's current interval begins during the seek interval, the element is turned off and an endEvent is raised. The associated time for the event is the document time before the seek.

Should read:

If an element is active at the time of hyperlinking and the element's current interval begins during the seek interval, the element is turned off and an endEvent is raised. The associated time for the event is the document time before the seek. This action does not resolve any times in the instance times list for end times.

Change 3:

In the Hyperlinks and timing section, add clarification to the second normative section.

Correction: Add to following text

Resolved begin times (e.g. a begin associated with an event) are not cleared or lost by seeking to an earlier time.

Resolved end times associated with events, repeat-values, accesskey-values or added via DOM method calls are cleared when seeking to time earlier than the resolved end time. This follows the semantics for resetting element state.

- E34: Clarification in the SMIL 2.0 Linking section 6.4 (revised 17 09 2002)

Description: The definition of the external attribute in section 6.4 needs clarification.

Correction: Add final Note in following text:

This attribute defines whether the link destination should be opened by the current application or some external application. A value of true will open the link in an external application defined on the system to handle this media type. A value of false will open the destination in the current application, however, if the current application does not support the media type of the referenced media, then it should attempt to render the media using an external application. Note that the means of associating media types with external applications is system dependent and not defined here. The default value of external is false.

Note that the above behavior for the external attribute applies to mailto links as well as media.

- E35: Correction in the SMIL 2.0 Language Profile, section 13.3.8 Media Object Modules (revised 17 09 2002)

Change 1:

Description: Missing endsync attribute for the brush element in the Media Object Modules, section 13.3.8 and in Schema.

Correction: Add following attribute

Change 2:

Description: Missing endsync attribute for the brush element in the Schema for the Media Functionality of the SMIL 2.0 Profile.

Correction: Add following attribute:

<!-- brush element and content model -->

<element name="brush" type="smil20lang:brushType"/>
<complexType name="brushType">
<complexContent>
<extension base="smil20:brushPrototype">
<choice minOccurs="0" maxOccurs="unbounded">
<group ref="smil20lang:paramGroup"/>
<group ref="smil20lang:areaGroup"/>
<group ref="smil20lang:switchGroup"/>
<group ref="smil20lang:animationGroup"/>
</choice>
<attributeGroup ref="smil20lang:CoreAttrs"/>
<attributeGroup ref="smil20lang:TimingAttrs"/>
<attributeGroup ref="smil20:systemTestAttrs"/>
<attributeGroup ref="smil20:deprecatedSystemTestAttrs"/>
<attributeGroup ref="smil20:customTestAttrs"/>
<attributeGroup ref="smil20:regionAttrs"/>
<attributeGroup ref="smil20:eraseMediaAttrs"/>
<attributeGroup ref="smil20:sensitivityMediaAttrs"/>
<attributeGroup ref="smil20:tabindexAttrs"/>
<attributeGroup ref="smil20:transInOutAttrs"/>
<attributeGroup ref="smil20:mediaAccessAttrs"/>
<attributeGroup ref="smil20:mediaObjectOverrideAttrs"/>
<attributeGroup ref="smil20:subregionPositioningAttrs"/>
<attributeGroup ref="smil20:regPointAttrs"/>
<attributeGroup ref="smil20:mediaAnnotateAttrs"/>
<attributeGroup ref="smil20:endsyncTimingAttrs"/>
<anyAttribute namespace="##any" processContents="strict"/>
</extension>
</complexContent>

</complexType>

- E36: Substantive error in the SMIL 2.0 Profile and Linking Module for the destinationPlaystate attribute, section13.3.7 and Appendix A.1.4 (revised 17 04 2002)

Change 1:

Description: Error for the SMIL 2.0 Profile listing in the Linking Module "stop" as an allowed value for the the destinationPlaystate attribute, section13.3.7

Correction: Remove the "stop" value for the the destinationPlaystate attribute.

Change 2:

Description: Error in the DTD for SMIL 2.0 Linking Module for the destinationPlaystate attribute, Appendix A.1.4 .

Correction: Remove "stop" value in the destinationPlaystate in the DTD as follows :

<!-- ======================== LinkingAttributes Entities =================== -->
<!ENTITY % SMIL.linking-attrs "
sourceLevel CDATA '100&#37;'
destinationLevel CDATA '100&#37;'
sourcePlaystate (play|pause|stop) #IMPLIED
destinationPlaystate (play|pause|stop) 'play'
show (new|pause|replace) 'replace'
accesskey %Character.datatype;#IMPLIED
target CDATA #IMPLIED
external (true|false) 'false'
actuate (onRequest|onLoad) 'onRequest'
%SMIL.tabindex.attrib; ">

- E37: Substantive DTD error in appendix A.1.5: The SMIL Media Object Module   (revised 26 09 2002)

Description: The "sensitivity" attribute is missing on media items in the DTD.

Correction: Add the sensitivity attribute definition as follows;

<!ENTITY % SMIL.mo-attributes-MediaParam "
erase (whenDone|never) 'whenDone'
mediaRepeat (preserve|strip) 'preserve'
sensitivity CDATA 'opaque'
">

- E38: Clarification in The SMIL 2.0 Transition Effects Module,section 12.8.1  (revised 09 10 2002)

Description: In the descriptions of non-SMPTE Transitions, "fade" transitions need clarification.

Correction: Add to the following text:

The "fade" transitions are pixel-by-pixel blends between the destination media and either the background media or a specified color.

Should read:

The "fade" transitions are pixel-by-pixel blends between the destination media and either the background media or a specified color. The "fadeToColor" and "fadeFromColor" subtypes are equivalent. The fade direction is determined by whether it is used as transIn or transOut.

- E39: Correction in The SMIL 2.0 Transition Effects Module, section 12.6  (revised 09 10 2002)

Description: The definition of the 'borderColor' attribute needs correction.

Correction: remove the word "system" in the current definition of the 'borderColor' attribute as follows:

If the value of the type attribute is not "fade", then this attribute specifies the content of the generated border along a wipe edge. Legal color values are CSS2 system color values or the string "blend". If the value of this attribute is a color, then the generated border along the wipe or warp edge is filled with this color. If the value of this attribute is "blend", then the generated border along the wipe blend is an additive blend (or blur) of the media sources. The default value is "black".

Should read:

If the value of the type attribute is not "fade", then this attribute specifies the content of the generated border along a wipe edge. Legal color values are CSS2 color values or the string "blend". If the value of this attribute is a color, then the generated border along the wipe or warp edge is filled with this color. If the value of this attribute is "blend", then the generated border along the wipe blend is an additive blend (or blur) of the media sources. The default value is "black".

Note that the link now points to http://www.w3.org/TR/REC-CSS2/syndata.html#color-units (instead of the system color section of the CSS spec).

- E40: Typographical error in the SMIL 2.0 Transition Effects Module in sections 12.4.2 and 12.5.2 The param element (revised 20 02 2003)

Description: In the following examples, the param element is an empty element and should have "/>" instead of ">".

Correction1: (sections 12.4.2)

<param name="flameLength" value="20" />

Correction2: (sections 12.5.2)

<param name="radius" value="3in" />

- E41: Correction in the SMIL 2.0 Timing and Synchronization Module in section 12.4.2 Semantics of the Timing Model (revised 20 02 2003)

Description: The wording in the fourth example says: "In this example, however, each time the parent time container repeats, the video elements will begin one second earlier than they did in the previous parent." iteration.

Resolution: Should read

In this example, however, each time the parent time container repeats, the video elements will begin two seconds earlier than they did in the previous parent iteration.

- E42: Clarification in the SMIL 2.0 Animation Module in section 3.5.3 The animateMotion element (revised 20 02 2003)

Description: In description of the two ways describing path of the animateMotion element:

The path can be described in either of two ways:

• Specifying x,y pairs for the from/to/by attributes. These will define a straight line motion path.
• Specifying x,y pairs for the values attribute. This will define a motion path of straight line segments, or points (if calcMode is set to discrete). This will override any from/to/by attribute values.
  

Resolution: Should read:

• Specifying an x,y pair for each of the from/to/by attributes. These will define a straight line motion path.
• Specifying a semicolon separated list of x,y pairs for the values attribute. This will define a motion path of straight line segments, or points (if calcMode is set to discrete). This will override any from/to/by attribute values.

- E43: Correction in the SMIL 2.0 Timing Module (Section 10.3.1, under Timing attribute value grammars) (revised 20 02 2003)

Description: The syntax of the offset-value token is ambiguous. At present, it is specified as

An offset value has the following syntax:

offset-value ::= (( S? "+" | "-" S? )? ( Clock-value )

Resolution: Should read

An offset value has the following syntax:

offset-value ::= ( S? ("+" | "-") S? )? ( Clock-value )

- E44: Clarification in the SMIL 2.0 Animation Modules, Section 3.4.1. (revised 24 02 2003)

Description:

There is an issue with the use of the term “default namespace”,

• In particular, in the third paragraph under the heading ”The target attribute”,
  “if no CSS match is made (or CSS does not apply) the default namespace for the target element will be matched”

• Also, in the fourth paragraph there appears:
  “If a target attribute is defined in an XML Namespace other than the default namespace for the target element, ...”

According to the Namespaces in XML Recommendation, If the qname value of the attributeName attribute does not contain a prefix (i.e., is a local name), then the named attribute is considered to be a member of the per-element-type partition namespace of the targetElement, and, as such, is associated with the XML namespace of the target element [which is not necessarily associated with the namespace value of the currently in-scope xmlns attribute, i.e., the default [XML] namespace].

Resolution: Should read:

• “if no CSS match is made (or CSS does not apply) the per-element-type partition namespace for the target element will be matched”
• “If a target attribute is defined in an XML Namespace other than the per-element-type partition namespace for the target element, ...”

- E45: Substantive DTD error in Appendix A.3.2 SMIL 2.0 common attributes for customTest attribute of the Content Control Modules (revised 2 06 2004)

Description: In section 4.3.2, the syntax of the customTest attribute is defined as list of customTest element identifier references, separated by the '+' character therefore the current DTD is wrong and must be modified as follows:

<!--=================== Content Control =======================-->
<!-- customTest Attribute, do not confuse with customTest element! -->
<!ENTITY % SMIL.customTestAttr.attrib "
%SMIL.pfx;customTest IDREF #IMPLIED ">

Resolution: Should read:

%SMIL.pfx;customTest CDATA #IMPLIED ">

- E46: Substantive DTD error in Appendix A.1.9 for hozRepeat and vertRepeat attributes of the TransitionModifiers Module (revised 2 06 2004)

Description: According to the definition of the hozRepeat and vertRepeat attributes, both have a default value of "1".
Therefore the DTD is wrong and must be modified as follows:

<!ENTITY % SMIL.transition-modifiers-attrs '
horzRepeat CDATA "0"
vertRepeat CDATA "0"
borderWidth CDATA "0"
borderColor CDATA "black" '>

Resolution: Should read:

<!ENTITY % SMIL.transition-modifiers-attrs '
horzRepeat CDATA "1"
vertRepeat CDATA "1"
borderWidth CDATA "0"
borderColor CDATA "black" '>

- E47: Correction in the SMIL 2.0 MediaClipping Module, section 7.5.1 for Subframe value in timecode (revised 2 06 2004)

Description: The following Note in section 7.5.1 about the clipBegin attribute is wrong and must be modified as follows:

Note: additional BNF for level 1 extensions defined later

Resolution: Should read:

Note: The following informative note is added in the revised 2004 version for clarification:
The definition of Subframe value in timecode introduces an inconsistency between SMIL 1.0 and SMIL 2.0.
At this time of revision, as some documents may have already been written using this Subframe value we have decided not to delete it from the Recommendation.
User agent should ignore subframe. Subframe should not be used as it is depreciated.

- E48: Clarification in SMIL 2.0 Timing and Synchronization Module, in section 10.3.3 for min attribute and time container constraints (revised 2 06 2004)

Change 1:

Description: To clarify the min attribute and time container constraints on child durations, the following text in section 10.3.3 must be modified as follows:

The min attribute has no effect on the time container constraint on child duration. This constraint still applies even if a child's active duration does not satisfy a min value constraint. In the following example, the image is displayed between 0 and 5 seconds.

Resolution: Should read:

The fill attribute is also used to extend the active duration if it is less than the duration specified in the min attribute.

Change 2:

Description: To clarify the min attribute and time container constraints on child durations, the following example in section 10.3.3 must be modified as follows:

<par dur="5s">
<img id="img" min="7s" dur="4s" .../>
</par>

Resolution: Should read:

<par dur="5s">
<img id="img" min="7s" dur="4s" fill="freeze" .../>
</par>

- E49: Clarification in SMIL 2.0 Linking Module, in section 6.5.2 for nohref attribute definition (revised 2 06 2004)

Description: The nohref attribute is defined very unclearly in the Linking Module. It should point to the relevant section of HTML and the word "Boolean" should be removed. Therefore the definition of nohref attribute must be modified as follows:

When set, this Boolean attribute specifies that the region has no associated link, even if other area elements for the media object define links for it.

Resolution: Should read:

When set, this attribute specifies that the region has no associated link, even if other area elements for the media object define links for it. It uses the same syntax as for the nohref attribute in HTML 4.01.

- E50: Typographical error  in the SMIL 2.0 Language Profile, in section 13.3.7 (revised 2 06 2004)

Description: The caption of the Linking Module Table is misspelled

Resolution: Should read:

Linking Module

- E51: Clarification in SMIL 2.0 Timing and Synchronization Module for time container constraints in section 10.3.3 (revised 2 08 2004)

Description: The time container constraints on child durations is ambiguous. At present, it is specified in the normative section as:

This section is normative

All time containers share the basic overriding constraint:

• A child element may not be active before the beginning, nor after the end of the parent simple duration.

Resolution: Should read:

This section is normative

All time containers share the basic overriding constraint:

• A child element may not be active before the beginning, nor after the end of either the parent simple duration or parent active duration.

- E52: Substantive DTD error in Appendix A.3.1 SMIL 2.0 common datatypes for LanguageCode.datatype (revised 2 06 2004)

Description: The defined %LanguageCode.datatype; is as follows :

<!ENTITY % LanguageCode.datatype "NMTOKEN">
<!-- a language code, as per [RFC1766] -->

[RFC1766] is out of date, and it should mention [RFC3066], but also, XML 1.0 Second Edition allowed an empty xml:lang value through an erratum and it is now incorporated into the Third Edition. NMTOKEN cannot allow an empty string.

Resolution:

In order to be consistent with the XML spec, the SMIL DTD needs to be modified to use "CDATA" rather than "NMTOKEN" for %LanguageCode.datatype.
Should read:

<!ENTITY % LanguageCode.datatype "CDATA">
<!-- a language code, as per [RFC3066] -->

- E53: Clarification added in http://www.w3.org/TR/2004/PER-smil20-20040706/smil20-profile.html (revised 05 11 2004)

Description: The following wording was included into the section 13.3.2 SMIL 2.0 second edition , to clarify the normative SMIL 2.0 DTD

.A document is a conforming SMIL 2.0 document if it satisfies the requirements of this specification (Synchronized Multimedia Integration Language (SMIL) 2.0 Profile Specification) and is valid per the normative DTD identified by http://www.w3.org/TR/2005/REC-smil20-20050107/smil-DTD.dtd.

Per section 7.6 of the W3C Process Document, W3C will make every effort to make this normative DTD available, in its original form, at this URI.

The SYMM WG also publishes a non-normative SMIL 2.0 DTD, identified by http://www.w3.org/2001/SMIL20/SMIL20.dtd. The SYMM WG plans to make changes to this DTD over time to correct errata. If you choose to refer to this DTD, please note that it is subject to change without notice at any time. The SYMM WG MAY publish a normative "snapshot" of the corrected DTD at a new URI by following the W3C Process for modifying a Recommendation.

Individuals are free to use either of the two URIs above as the system identifier in the SMIL 2.0 language DOCTYPE, according to the desired level of stability.

Resolution:

The SYMM WG publishes a non-normative SMIL 2.0 DTD, identified by http://www.w3.org/2001/SMIL20/SMIL20.dtd. The SYMM WG plans to make changes to this DTD over time to correct errata. If you choose to refer to this DTD, please note that it is subject to change without notice at any time.

- E54: Clarification added in http://www.w3.org/TR/2004/PER-smil20-20040706/smil20-profile.html (revised 05 11 2004)

Description: In section 13.3.2 SMIL 2.0 Language Conformance,we have included the following namespace change policy

This namespace URI will only be used to refer to this version of this specification: different URIs will be used for any and all new versions of the specification.

This namespace name may be reused in any update of the specification which is made for the purpose of clarification or bug fixes. These changes will be minor in that they do not
(a) change the meaning of existing documents written using the namespace, or (b) affect the operation of existing software written to process such documents. The SYMM WG may reuse this namespace URI in a future specification that revises the SMIL 2.0 DTD, thus affecting the validity of published documents.

Rejected proposed erratas:

- R01: Clarification in the the SMIL 2.0 Language Profile <animateMotion> on <brush> (revised 16 09 2002)

Description: in the SMIL 2.0 Language Profile, we allow animation of the color, and the location of the brush can be animated with the basic <animate> element. But we do not allow animateMotion on the brush

Resolution: The <animateMotion> on <brush> issue does not qualify as errata. It is not a bug, it is an "obvious" missing feature. Therefore this "obvious oversights" to be fixed, is a good candidate for a future SMIL 2.1 maintenance release.

- R02: Architectural error in the definition of the type attribute (section 7.3.1) (revised 2 06 2004)

Description: The Technical Architecture Group (TAG) has brought to our attention that "The W3C Recommendation SMIL 2.0 includes an architectural error in the definition of the type attribute (section 7.3.1); it specifies circumstances in which type is supposed to take precedence over server headers."

Resolution: Web server should send the proper Mimetype or send nothing.
This is not really an error. This is an inconsistency with TAG. TAG was not available when SMIL 2.0 was written.
This should be addressed in a future version, since it is not an error in SMIL 2.0.
If TAG wants to propose a solution to be used by next version of SMIL. We will look at it again for SMIL 2.1.