Copyright © 2005 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
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
[Second edition].
Each entry has the following information:
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/.
Added text marked thus. Removed text marked thus. Changed text marked thus.
- E01: Correction in the SMIL 2.0 Timing and Synchronization Module, section 10.3.1 and SMIL 2.0 Animation section 3.9.1, for Event values (revised 7 04 2005)
Description:
In SMIL Animation Recommendation, we said specifically that the default event base for animation elements was the animation target. This in turn defaulted to the parent element, but may also be specified (of course).
In SMIL 2.0 Timing, we expressly say that the eventbase defaults to the element on which timing is specified (self). Later, there is an informative section (within smil-timing.html#Timing-BeginValueListSyntax) that says:
"... A host language designer may override the definition of the default eventbase element. As an example of this, the SMIL Animation elements (animate, animateMotion, etc.) specify that the default eventbase element is the target element of the animation. See also [[SMIL ANIMATION]]. ..."
There are several problems with this.
1) [[SMIL ANIMATION]] is not a link
2) Should presumably reference the SMIL 2.0
Animation chapter, and not SMIL Animation
Recommendation
3) There should be a normative section in SMIL 2.0
Timing that specifies that it is okay to override the event-base
default.
Resolution:
1- Add a sentence after the normative section in SMIL Timing section 10.3.1 that currently reads:
"... If the Eventbase-element term is missing, the event-base element defaults to the element on which the eventbase timing is specified (the current element)...."
The added text is:
"A host language designer may override the definition of the default eventbase element. As an example of this, the SMIL 2.0 Animation modules describe Timing integration requirements for the animation elements (animate, animateMotion, etc.). These requirements specify that the default eventbase element is the target element of the animation. See SMIL 2 Animation section 3.9.1 (Integration requirements) .
2- Remove the informative paragraph in SMIL Timing section 10.3.1
If the eventbase element has no associated layout (e.g. a time container in a SMIL document), then some UI events may not be defined (e.g. mouse events). A host language designer may override the definition of the default eventbase element. As an example of this, the SMIL Animation elements (animate, animateMotion, etc.) specify that the default eventbase element is the target element of the animation. See also [[SMIL ANIMATION]].
3- Add in the SMIL 2 Animation section 3.9.1 (Integration requirements) a new paragraph after
"In particular, the fill attribute is supported on animation elements only if the host language integrates the SMIL 2.0 BasicTimeContainers module in addition to the BasicInlineTiming module."
The added text is:
normative section
"If the Eventbase-element term is missing, the event-base element is defined to be the target element of the animation."
- E02: Correction in the SMIL 2.0 Time manipulation Module , section 11.1.3 (revised 08 08 2005)
Description:
1- formula:(2.0*0.75= = 1.5) is wrong.
Resolution:
should be
(2.0*0.75 = 1.5)
- E03: Clarification in the SMIL 2.0 Time manipulation Module , section 11.1.4 (revised 08 08 2005)
Description:
2- AD is the associated Active Duration, but this is not mentioned in the text.
Resolution:
Added in the following paragraph:
Let t_ps be a time in parent simple time, and
B be the
begin time, and O be the
accumulated synchronization offset for
an element, measured in parent
simple time. Let AD be the Active
Duration.
- E04: Revision of the SMIL Mime Type, section 2.3.1 (revised 13 12 2005)
Description:
The SMIL Mime Type application/smil
is deprecated in favor of
application/smil+xml
.
The SMIL 2.0 Recommendation says in the normative section, section 2.3.1
Documents authored in language profiles that include the SMIL Structure
module can be associated with the "application/smil
" mime type.
Documents using the "application/smil
" mime type are required to
be host language conformant.
Resolution:
1- The previous paragraph should be replaced by
Documents authored in language profiles that include the SMIL Structure
module can be associated with the "application/smil+xml
" mime
type. Documents using the "application/smil+xml
" mime type are
required to be host language conformant. This errata obsoletes the former
"application/smil
" mime type as specified in SMIL 2.0.
2- Also in section 1.1.1 "Relation to SMIL 1.0" and in section 10.4.1 "Required host language definitions",
in each paragraph, "application/smil
" is replaced by
"application/smil+xml
"
- E05: Correction in Date wallclock values example, section 10.3.1 (revised 13 12 2005)
Description:
Date wallclock values are treated as a DateTime value of the given date at time 00:00:00.00, that is, midnight on the given date, in the time zone given, or the local time zone if none is specified.
According to the Date wallclock values grammar, it is impossible to give a time zone with the 'Date' production.
Resolution:
Remove the first example which is wrong
begin="wallclock(2000-01-01Z)"
- E06: Revision of the semantics for the "type" selection in an HTTP exchange, section 7.3.1 (revised 13 12 2005)
Description:
Revision of the semantics for the "type" selection in an HTTP exchange. The semantics defined by this errata now conforms to the TAG Finding Authoritative Metadata.
Resolution:
The definition of type attribute is replaced by:
Content type of the media object referenced by the src attribute. The usage of this attribute depends on the protocol of the src attribute.
When the content represented by a URL is available in many data formats, implementations MAY use the type value to influence which of the multiple formats is used. For instance, on a server implementing HTTP content negotiation, the client may use the type attribute to order the preferences in the negotiation. The type attribute is not intended for use in media sub-stream selection.
For protocols not enumerated in this specification, implementations should use the following rules: When the media is encapsulated in a media file and delivered intact to the SMIL user agent via a protocol designed for delivery as a complete file, the media type as provided by this protocol should take precedence over the type attribute value. For protocols which deliver the media in a media-aware fashion, such as those delivering media in a manner using or dependent upon the specific type of media, the application of the type attribute is not defined by this specification.
- E07: Clarification of repeat 'event' , section 10.5.2 (revised 13 12 2005)
Description:
Clarification of "repeat" event and "repeatEvent".
Resolution:
Replace the following paragraph:
repeat
This event is raised when the element local timeline repeats. It will be
raised each time the element repeats, after the first iteration. Associated
with the repeat event is an integer that indicates which repeat iteration is
beginning. The value is a 0-based integer, but the repeat event is not raised
for the first iteration and so the observed values will be >= 1.
by the two following paragraphs.
repeatEvent and repeat
Depending on
the profile, one or the other of these events is raised when the element
local timeline repeats. It will be raised each time the element repeats,
after the first iteration.
repeat (n)
This event is raised when the element local timeline repeats. It
will be raised each time the element repeats, after the first iteration.
Associated with the repeat event is an integer that indicates which repeat
iteration is beginning. The value is a 0-based integer, but the repeat event
is not raised for the first iteration and so the observed values will be
>= 1.
- R01: None
Description: TBD
Resolution: TBD.