Movatterモバイル変換

15.SMIL 2.1 Extended MobileProfile

Editors for SMIL 2.1

Dick C.A. Bulterman, CWI/Amsterdam

Daniel F. Zucker, ACCESS Co., Ltd.

Editors for SMIL 2.0 Basic and Language Profiles

Kenichi Kubota, Panasonic

Aaron Cohen, Intel

Michelle Kim, IBM.

Nabil Layaïda, INRIA

Jacco Van Ossenbruggen, CWI/Amsterdam

15.1Abstract

The SMIL 2.1 Extended Mobile Profile is a collection of SMIL 2.1 modulesthat provide extensive support for the SMIL 2.1 Language within the contextof an advanced (for 2005) mobile device. Such a device is expected to have ahigh-resolution display and sufficient memory and processor capacity torender nontrival SMIL documents. Although not as complete as the fullSMIL 2.1 Language Profile,the SMIL 2.1 Extended Mobile Profile is rich enough to meet the needs of awide range of interactive presentations.

The SMIL 2.1 Extended Mobile Profile is new to SMIL 2.1. It builds on thefunctionality defined for theSMIL 2.1 MobileProfile. The functionality of the SMIL 2.1 Extended Mobile Profile may befurther extended by using theSMIL 2.1 ScalabilityFramework.

15.2 SMIL 2.1 Extended Mobile Profile

This section isinformative.

The SMIL 2.1 Extended Mobile Profile is defined as a markup language. Thesyntax of this language is formally described with a document type definition(DTD) or an XML Schema which is based on the SMIL modules as defined in "The SMIL 2.1 Modules".

In the text in this profile specification, the termExtended MobileProfile will be considered to refer exclusively to the SMIL 2.1 ExtendedMobile Profile as defined in this document.

The Extended Mobile Profile design requirements are:

1. Ensure that the profile is backward compatible with theSMIL 2.0 Basic Profile and Scalability Framework.
2. Ensure that the profile is backward compatible with theSMIL 2.1 Mobile Profile.
3. Ensure that the profile is a proper subset of theSMIL 2.1 Language Profile.

15.2.1 Relationship with the 3GPP2 SMILLanguage Profile

This section isinformative.

The Third Generation Partnership Project 2 (3GPP2)[3GPP2] defines itsown SMIL language profile. The revision A of the 3GPP2 SMIL File Formats forMultimedia Services, which is now under discussion (as of Dec. 2005), definesthe SMIL profile including some additional modules compared to the 3GPP SMILprofile[3GPP26.234R5];AccessKeyTiming Module,MultiArcTiming Module,BasicAnimation ModuleandAudioLayout Module.A future revision of it may incorporate SMIL 2.1.

The Extended Mobile Profile includes all modules of 3GPP2 revision A SMILand the following additional ones:BasicExclTimeContainers Module,SubRegionLayout Module,BackgroundTilingLayout Module,AlignmentLayout Module,OverrideLayout Module,FullScreenTransitionsModule andBrushMedia Module.

15.3 Normative Definition of the ExtendedMobile Profile

This section isnormative.

15.3.1 Document Conformance

This version of SMIL provides a definition of strictly conforming ExtendedMobile Profile documents, which are restricted to tags and attributes fromthe SMIL 2.1 namespace. In the future, the language described in this profilemay be extended by other W3C Recommendations, or by private extensions. Forthese extensions, the following rules must be obeyed:

• All elements introduced in extensions must have askip-content attribute if it should be possible that their content is processed by Extended Mobile Profile user agents.
• Private extensions must be introduced by defining a new XML namespace.

Conformant Extended Mobile Profile user agents are expected to handledocuments containing extensions that obey these two rules.

15.3.2 Extended Mobile ProfileConformance

The Extended Mobile Profile is a conforming SMIL 2.1 specification. Therules for defining conformant documents are provided in theSMIL 2.1Language Conformance in theSMIL 2.1Language Profile document. Note that while the referenced section iswritten for the SMIL 2.1 Language Profile, all of the rules apply to theExtended Mobile Profile as well, with the exception that the Extended MobileProfile'snamespace should beused instead of the SMIL 2.1 Language Profile's namespace.

Extended Mobile ProfileNamespace

Documents written for the Extended Mobile Profile must declare a defaultnamespace for its elements with anxmlns attribute on thesmil root element with its identifier URI:

<smil xmlns="http://www.w3.org/2005/SMIL21/ExtendedMobile">   ...</smil>

The default namespace declaration must be

xmlns="http://www.w3.org/2005/SMIL21/ExtendedMobile"

Language designers and implementors wishing to extend the Extended MobileProfile must consider the implications of the use of namespace extensionsyntax. Please consult the section onScalable Profiles forrestrictions and recommendations for best practice when extending SMIL.

Extended Mobile ProfileDOCTYPEdeclaration

A SMIL 2.1 document can contain the following DOCTYPE declaration:
The SMIL 2.1 Extended Mobile Profile DOCTYPE is:

<!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 2.1 Extended Mobile//EN""http://www.w3.org/2005/SMIL21/SMIL21ExtendedMobile.dtd">

If a document contains this declaration, it must be a valid XMLdocument.
Note that this implies that extensions to the syntax defined in the DTD arenot allowed. If the document is invalid, the user agent should issue anerror.

Conforming SMIL 2.1 Extended MobileProfile User Agents

15.3.3 The SMIL 2.1 Extended Mobile Profile

• Structure functionality
  • Structure Module
• Metainformation functionality
  • Metainformation Module
• Timing functionality
  • BasicInlineTiming Module
  • EventTiming Module
  • MinMaxTiming Module
  • RepeatTiming Module
  • MultiArcTiming Module
  • AccessKeyTiming Module
  • BasicTimeContainers Module
  • BasicExclTimeContainers Module
• Animation functionality
  • BasicAnimation Module
• Content Control functionality
  • BasicContentControl Module
  • PrefetchControl Module
  • SkipContentControl Module
• Layout functionality
  • BasicLayout Module
  • AudioLayout Module
  • SubRegionLayout Module
  • BackgroundTilingLayout Module
  • AlignmentLayout Module
  • OverrideLayout Module
• Linking functionality
  • BasicLinking Module
  • LinkingAttributes Module
• Transition Effects functionality
  • BasicTransitions Module
  • FullScreenTransitions Module
• Media functionality
  • BasicMedia Module
  • MediaClipping Module
  • MediaDescription Module
  • MediaParam Module
  • BrushMedia Module
  • MediaAccessibility Module

The collection names contained in the following table define the ExtendedMobile Profile vocabulary.

In the following sections, we define the set of elements and attributesused in each of the modules included in the Extended Mobile Profile. Thecontent model for each element is described. The content model of an elementis a description of elements which can appear as its direct children. Thespecial content model "EMPTY" means that a given element may not havechildren.

Theid,classandtitleattributes in the collection Core aredefined for all the elements of the Extended Mobile Profile. Theidattribute is used in the Extended MobileProfile to assign a unique XML identifier to every element in a SMILdocument. In this document, equivalent but deprecated attributes and elementsare shown in square brackets.

15.3.4 Animation Module

TheAnimation Module provides aframework for incorporating animation into a timing framework, and amechanism for composing the effects of multiple animations. The AnimationModule uses the timing modules included in this profile for the underlyingmodel of time. The Extended Mobile Profile includes the Animationfunctionality of theBasicAnimationmodule. TheBasicAnimationModule defines the semantics for theanimate,set,animateMotion andanimateColor elements.

In the Extended Mobile Profile, Animation elements can have the followingattributes and content model :

This profile adds theanimate,set,animateMotion andanimateColor elements to the contentmodel of thepar,seq, andexcl elements of theTiming and Synchronization Modules. Italso adds these elements to the content model of thebody element of theStructure Module.

Specifying the target element of the animation

The animation target elements supported in the Extended Mobile Profile aretheregion element defined in theLayout Modules, thearea [anchor] element defined in theLinking Modules and thetext,img,audio,animation,video,ref,textstream and thebrush elements defined in theMedia Objects modules.

The SMIL Extended Mobile Profile uses thetargetElement attribute to identifythe element to be affected by animation elements. As recommended in theBasicAnimation Module when thetargetElement attribute issupported, this profile excludes the XLink attributeshref,type,actuate andshow from theanimate,set,animateMotion andanimateColor elements.

Specifying the target attribute of the animation

The target attributes of the animations are a subset of those of theregion,area [anchor], and media elements. The animatableattributes of theregion,area [anchor], and media elements are listed inthe table below.

Thearea [anchor] element has thecoords attribute which can be subject toanimation. The attributecoords isconsidered of type string in this profile. This means that only discretenon-additive animation is supported on this attribute.

Media elements have the following region attributes which can be subjectto animation:left,right,top,bottom,width,height,z-indexandbackgroundColor [background-color].

Integration definitions

The Extended Mobile Profile defines a set of integration definitions asrequired by the Animation modules. These definitions are:

• Animation values in the Extended Mobile Profile are subject to the same syntax requirements as the attribute values on the animated elements.
• Percentage values on the attributes have the same semantics as they do on the attribute. If percentage values are not supported on an attribute then percentage values are not supported for animation in the SMIL 2.1 Extended Mobile Profile.
• The Extended Mobile Profile supports CSS2[CSS2] color names. The lower clamping bound color value is the black color or rgb(0%, 0%, 0%) and the higher clamping color value is the white color or rgb(100%, 100%, 100%). Values on an animated color lower than the lower clamping bound are clamped to the black color; values greater than the higher clamping color are clamped to the white color.
• The semantics of clamping values for attributes should be performed in floating point with a precision of at least that given by a 4-byte IEEE-format real number[IEEE-Arithmetic]. Cumulative and additive presentation values should be computed without regard to the range of the target attribute. Prior to display, the presentation value should be reduced or increased to the nearest value which is within the range of the target attribute. For integer attributes the computed value should then be rounded to the nearest integer (coerced-integer-value). The mathematical definition of rounding is:

  coerced-integer-value = Math.floor( interpolated-value + 0.5 )

• The position of the region element to which theanimateMotion element applies is the top left corner, in the coordinate system within which the 'top' and 'left' attributes are defined in the Layout modules.
• The origin for theanimateMotion when applied to the sub-region on media elements is the top left of the containing region as defined in theLayout modules.

15.3.5 Content Control Modules

TheContent ControlModules provide a framework for selecting content based on a set of testattributes. TheContent ControlModules define semantics for theswitch andprefetch elements. The Extended MobileProfile includes the Content Control functionality of theBasicContentControl,PrefetchControl andSkipContentControl modules.

In the Extended Mobile Profile, Content Control elements can have thefollowing attributes and content model :

This profile adds theswitchelement to the content model of thepar,seq andexcl elements of theTiming and Synchronization Modules, ofthebody and thehead elements of theStructure Module, of the content modelof thea element of theLinking Modules.

Content Control functionality is used to define the attribute set"Test":

The Test attributes collection is added to all the elements defined in theExtended Mobile Profile. An Extended Mobile user agent must support all ofthe values for thesystemOperatingSystem andsystemCPUattributes listed in theContent Control Modules. In addition, the user agent should accept namespacedvalues as future extensions, and not declare a syntax error. The user agentshould return false for unrecognized values of thesystemOperatingSystem andsystemCPUattributes.

15.3.6 Layout Modules

TheLayout Modules provide a frameworkfor spatial layout of visual components. TheLayout Modules define semantics for theregion,root-layout,layout and theregPoint elements. The Extended MobileProfile includes the Layout functionality of theBasicLayout,AudioLayout,SubRegionLayout,BackgroundTilingLayout,AlignmentLayout,OverrideLayoutmodules.

In the Extended Mobile Profile, Layout elements can have the followingattributes and content model :

The attribute collection SubregionAttributes is defined as follows:

This profile adds thelayoutelement to the content model of thehead element of theStructure Module. It also adds thiselement to the content model of theswitch element of theContent Control Modules, whentheswitch element is a child of thehead element. The profile also adds thefollowing a

15.3.7 Linking Modules

TheLinking Modules providea framework for relating documents to content, documents and documentfragments. TheLinking Modulesdefine semantics for thea andarea [anchor] elements. They define also thesemantics of a set of attributes defined for these elements. The SMIL 2.1Extended Mobile Profile includes the Linking functionality of theBasicLinking andLinkingAttributes modules.

Both thea andarea [anchor] elements have anhref attribute, whose value must be a validURI.

Support for URIs with XPointer fragment identifier syntax is notrequired.

In the Extended Mobile Profile, Linking elements can have the followingattributes and content model :

This profile adds thea element to thecontent model of thepar,seq, andexcl elements of theTiming and Synchronization Modules. Italso adds these elements to the content model of thebody element of theStructure Module.

In the Extended Mobile Profile, a value ofonLoad set on the attributeactuate indicates that the link isautomatically traversed when the linking element becomes active. For linkingelements containing SMIL timing, this is when the active duration of thelinking element begins.

Linking behavior in the Extended Mobile Profile may be used to navigatewithin a document or to link across documents. When linking to destinationsoutside the current document, implementations may ignore the values"play" and"pause" of thesourcePlaystate attribute,and the values"new" and"pause" of theshow attribute; in these cases, the semanticsof the"stop" attribute (forsourcePlaystate) and the"replace" attribute (forshow) should be used. If an implementationignores the values of thesourcePlaystate andshow attributes, it may also ignore thesourceLevel attribute.

The attributetabindex specifiesthe position of the element in the tabbing order at a particular instant forthe current document. The tabbing order defines the order in which elementswill receive focus when navigated by the user via an input device such as akeyboard. At any particular point in time, only active elements are takeninto account for the tabbing order; inactive elements are ignored.

When a media object element has atabindex attribute and becomes active,then its ordered tab index is inserted in the SMIL tab index at the locationspecified by the media object'stabindex attribute value. This assumesthat the media object itself has tab indices, such as embedded HTML withtabindex attributes. This enablesall link starting points in a SMIL presentation to have a place on theordered list to be tab-keyed through, including those in embeddedpresentations.

The Extended Mobile Profile does not define four-way navigation in theSMIL 2.1 release. A definition for four-way navigation is expected in thefuture version of SMIL.

15.3.8 Media Object Modules

TheMedia Object Modulesprovide a framework for declaring media. TheMedia Object Modules definesemantics for theref,animation,audio,img,video,text,textstream,param,paramGroup andbrushbrush elements. The Extended MobileProfile includes the Media Object functionality of theBasicMedia,MediaClipping,MediaParam,BrushMediaandMediaAccessibilitymodules.

In the Extended Mobile Profile, media elements can have the followingattributes and content model:

Widely Supported Content Types

This section isinformative.

The members of the W3C SYMM Working Group recommend that at least thefollowing content types and file formats be supported by Mobile Profile useragents:

• For plain text: plain text with US-ASCII ([ASCII]) or UTF-8 ([UTF8]) encoding, MIME type is text/plain.
• for still image: ISO/IEC JPEG ([JPEG]) together with JFIF ([JFIF]), baseline DCT, non-differential, Huffman coding, as defined in table B.1, symbol 'SOF0' in[JPEG], MIME type is image/jpeg.
• For bitmap graphics: PNG, MIME type is image/png ([PNG-MIME],[PNG-REC]).
• For 2D vector graphics: SVG 1.1 Tiny Profile ([SVG-Mobile]), MIME type is image/svg+xml.
• For video: ITU-T Recommendation H.263[H263] profile 0 level 10, part of 3GP file format.
• For audio: MPEG-4 AAC Low Complexity object type[AAC], part of 3GP file format.
• The file format for audio and for video: the 3GP file format as defined in[3GPP26.234R5].

Media Object IntegrationRequirements

This section isnormative.

The MediaParam module defines theeraseattribute, and defers definition of the "display area" to the languageprofile. "Display area" for the purposes of the Extended Mobile Profilecorresponds to a SMIL BasicLayoutregion. The effects oferase="never"apply after the active duration of the media object and any fill period(defined by SMIL Timing and Synchronization), and only until other mediaplays to the region targeted by the media object, or until the same mediaobject restarts.

15.3.9 Metainformation Module

TheMetainformation Moduleprovides a framework for describing a document, either to inform the humanuser or to assist in automation. TheMetainformation Module defines semanticsfor themeta andmetadata elements. The Extended MobileProfile includes the Metainformation functionality of theMetainformation module.

In the Extended Mobile Profile, Metainformation elements can have thefollowing attributes and content model :

This profile adds themeta elementto the content model of theheadelement of theStructure Module.

The content model of metadata is empty. Profiles that extend the ExtendedMobile Profile may define the RDF (Resource Description Framework) schema tobe used in extending the content model of the metadata element. The ResourceDescription Framework is defined in the W3C RDF Recommendation[RDFsyntax].

15.3.10 Structure Module

The Structure Module provides a framework for structuring a SMIL document.The Structure Module defines semantics for thesmil,head, andbody elements. The Extended Mobile Profileincludes the Structure functionality of theStructure module.

In the Extended Mobile Profile, the Structure elements can have thefollowing attributes and content model :

Thebody element acts as the rootelement to span the timing tree. The body element has the behavior of aseq element. Timing on thebody element is supported. The syncbase ofthebody element is the applicationbegin time, which is implementation dependent, as is the application endtime. Note that the effect offillonthebodyelement is between the end ofthe presentation and the application end time, and therefore the effect offill is implementation dependent.

15.3.11 Timing and Synchronization Modules

TheTiming and SynchronizationModules provide a framework for describing timing structure, timingcontrol properties and temporal relationships between elements. TheTiming and Synchronization Modulesdefine semantics forpar,seq andexcl elements. In addition, these modulesdefine semantics for attributes includingbegin,dur,end,repeat (deprecated),repeatCount,repeatDur,min,max.TheExtended Mobile Profile includes the Timing and Synchronization functionalityof theBasicInlineTiming,EventTiming, MinMaxTiming, RepeatTiming, MultiArcTiming, AccessKeyTiming,BasicTimeContainers, BasicExclTimeContainers modules.

In the Extended Mobile Profile, Timing and Synchronization elements canhave the following attributes and content model :

The Attribute collection Timing is defined as follows:

This profile adds thepar,seq, andexcl elements to the content model of thebody element of theStructure Module and adds theseelements to the content model of theaelement of theLinkingModules.

Elements of theMedia ObjectModules have the attributes describing timing and properties ofcontents.

Supported Event Symbols

The Extended Mobile Profile specifies which types of events can be used aspart of thebegin andend attribute values. The supported events aredescribed as Event-symbols according to thesyntax introduced in theSMIL Timing and Synchronizationmodule.

The supported event symbols in the Extended Mobile Profile are:

As defined by theSMIL syncbasetiming semantics, any event timing attributes that reference an invalidtime-value description will be treated as if "indefinite" were specified.

Event semantics

focusInEvent:

Raised when a media element gets the keyboard focus in its rendering space, i.e., when it becomes the media element to which all subsequent keystroke-event information is passed. Once an element has the keyboard focus, it continues to have it until a user action or DOM method call either removes the focus from it or gives the focus to another media element, or until its rendering space is removed. Only one media element can have the focus at any particular time. The focusInEvent is delivered to media elements only, and does not bubble.

focusOutEvent:

Raised when a media element loses the keyboard focus from its rendering space, i.e., when it stops being the media element to which all subsequent keystroke-event information is passed. The focusOutEvent is delivered to media elements only, and does not bubble.

activateEvent:

Raised when a media element is activated by user input such as by a mouse click within its visible rendering space or by specific keystrokes when the element has the keyboard focus. The activateEvent is delivered to media elements only, and does not bubble.

beginEvent:

Raised when the element actually begins playback of its active duration. If an element does not ever begin playing, this event is never raised. If an element has a repeat count, beginEvent is only raised at the beginning of the first iteration. The beginEvent is delivered to elements that support timing, such as media elements and time containers, and does not bubble.

endEvent:

Raised when an element actually ends playback; this is when its active duration is reached or whenever a playing element is stopped. In the following example,

<ref end="30s" src="15s.mpg" /><ref end="10s" src="20s.mpg" /><ref repeatCount="4" src="5s.mpg" />

x.endEvent occurs at roughly 30s when the active duration is reached, y.endEvent occurs at roughly 10s when the playback of the continuous media is ended early by the active duration being reached, and z.endEvent occurs at roughly 20s when the fourth and final repeat has completed, thus reaching the end of its active duration. The endEvent is delivered to elements which support timing, such as media elements and time containers, and does not bubble.

repeatEvent:

Raised when the second and subsequent iterations of a repeated element begin playback. An element that has norepeatDur,repeatCount, orrepeat 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.

inBoundsEvent:

Raised when one of the following happens:

• by any input from the mouse or other input device that brings the mouse cursor from outside to within the bounds of a media element's rendering space, regardless of what part, if any, of that rendering space is visible at the time, i.e., z-order is not a factor.
• by any other action that moves the "cursor" or "pointer", as defined by the implementation, from outside to within the bounds of a media element's rendering space, regardless of what part, if any, of that rendering space is visible at the time, i.e., z-order is not a factor. An implementation may decide, for instance, to raise an inBoundsEvent on an element whenever it gets the focus, including when keystrokes give it the focus.

A media element's bounds are restrained by the bounds of the region in which it is contained., i.e., a media element's bounds do not extend beyond its region's bounds. The inBoundsEvent is delivered to media elements only, and does not bubble.

Note that, unlike with keyboard focus which can only be active on one object at a time, the state of being within an object's bounds can be true for multiple objects simultaneously. For instance, if one object is on top of another and the cursor is placed on top of both objects, both would have raised an inBoundsEvent more recently than the raising of any respective outOfBoundsEvent. If a player does not support a pointer cursor, then these players will typically not generate the inBoundsEvent and outOfBoundEvent events.

outOfBoundsEvent:

Raised when one of the following happens:

• by any input from the mouse or other input device that brings the mouse cursor from within to outside the bounds of a media element's rendering space, regardless of what part, if any, of that rendering space is visible at the time,
• by any other action that moves the "cursor" or "pointer", as defined by the implementation, from within to outside the bounds of a media element's rendering space, regardless of what part, if any, of that rendering space is visible at the time.

A media element's bounds are restrained by its region's bounds, i.e., a media element's bounds do not extend beyond its region's bounds. The outOfBoundsEvent is delivered to media elements only, and does not bubble.

Order of raising ofsimultaneous events:

There will be cases where events occur simultaneously. To ensure that eachExtended Mobile implementation handles them in the same order, the followingorder must be used to resolve ties:

1. InBoundsEvent
2. focusInEvent (should follow 1)
3. activateEvent (should follow 2)
4. OutOfBoundsEvent
5. focusOutEvent (should follow 4)
6. endEvent
7. beginEvent (must follow 6)
8. repeatEvent

Events are listed in order of precedence, e.g., if event #6 in this listoccurs at the same time as event #7, then #6 must be raised prior to #7.

The InBoundsEvent, focusInEvent, OutOfBoundsEvent, activateEvent, andfocusOutEvent events do not bubble and are delivered to the target mediaelement.

The beginEvent, endEvent and repeatEvent events do not bubble and aredelivered to the timed element on which the event occurs.

Extending the set ofsupported events

The Extended Mobile Profile supports an extensible set of events. In orderto resolve possible name conflicts with the events that are supported in thisprofile qualified event names are supported. Namespace prefixes are used toqualify the event names. As a result, the colon is reserved in begin and endattributes for qualifying event names.

For example:

<smil ... xmlns:example="http://www.example.com">   <img .../>    <audio begin="foo.example:focusInEvent".../>    ... </smil>

Integrationdefinitions

A SMIL document's begin time is defined as the moment a user agent beginsthe timeline for the overall document. A SMIL document's end time is definedas equal to the end time of thebodyelement.

15.3.12 Transition Effects Modules

TheTransition EffectsModules provide a framework for describing transitions such as fades andwipes. TheTransitionModules define semantics for thetransition element. The Extended MobileProfile includes the functionality of theBasicTransitionsandFullScreenTransitionsmodules.

In the Extended Mobile Profile, Transition Effects elements have thefollowing attributes and content model :

This profile adds thetransition element to the content modelof thehead element of theStructure Module.

TheTransition EffectsModules addtransIn andtransOut attributes toref,animation,audio,img,video,text,textstream andbrush elements of theMedia Object Modules.

TheTransition EffectsModules add thetransition value to thefill attribute for all elements on which thisvalue of thefill attribute issupported.

15.4 Appendix A: SMIL 2.1 Document TypeDefinition

This section isnormative.

TheExtended Mobile Profile Document TypeDefinition is defined as a set of SMIL 2.1 modules. All SMIL 2.1 modulesare integrated according to the guidelines in the W3C Note "SynchronizedMultimedia Modules based upon SMIL 1.0"[SMIL-MOD], and defined withintheir respective module sections.