Table of contents

• 17.1 Overview and Summary of Changes for SMIL 3.0
• 17.2 Abstract
• 17.3 Introduction to the SMIL 3.0 Language Profile
• 17.4 Normative Definition of the SMIL 3.0 Language Profile
  • 17.4.1 SMIL 3.0 Language Profile Conformance
  • 17.4.2 SMIL 3.0 Language Profile User Agent Conformance
  • 17.4.3 The SMIL 3.0 Language Profile
  • 17.4.4 Structure Modules
  • 17.4.5 Media Object Modules
    • Media Object Integration Requirements
  • 17.4.6 Timing and Synchronization Modules
    • Supported Event Symbols
    • Event semantics
    • Order of raising of simultaneous events:
    • Extending the set of supported events
    • Integration definitions
  • 17.4.7 Content Control Modules
  • 17.4.8 Layout Modules
  • 17.4.9 smilText Modules
  • 17.4.10 Linking Modules
  • 17.4.11 Metainformation Module
  • 17.4.12 Transition Effects Modules
  • 17.4.13 Animation Module
  • 17.4.14 State Modules
    • Expression Language and Data Model
• 17.5 Appendix A: SMIL 3.0 Document Type Definition
• 17.6 Appendix B: Recommended MIME Types
  • 17.6.1 JPEG Support

This section is informative.

The SMIL 3.0 Language profile extends the SMIL 2.1 Language profile withnew functionalities introduced in SMIL 3.0 Modules. Specifically, thefollowing modules have been added to the list of modules:

• Identity Module
• RequiredContentControl Module
• StructureLayout Module
• MediaOpacity Module
• MediaPanZoom Module
• MediaRenderAttributes Module
• StateTest Module
• UserState Module
• StateSubmission Module
• StateInterpolation Module
• BasicText Module
• TextStyling Module
• TextMotion Module

The following modules were changed for SMIL 3.0:

• BasicContentControl
• BasicLayout Module
• MediaParam Module
• Metainformation Module

In addition to new and changed modules, this version of SMIL also has anew requirement about the media formats that are to be supported by useragents, and thereadIndexattribute was added to theCore collection,meaning it may occur on many more elements.

This section is normative.

The SMIL 3.0 Language profile describes the SMIL 3.0 modules that areincluded in the SMIL 3.0 Language and details how these modules areintegrated. It contains support for all of the major SMIL 3.0 featuresincluding animation, content control, layout, linking, media object,meta-information, structure, timing and transition effects. It is designedfor Web clients that support direct playback from SMIL 3.0 markup.

This section isinformative.

The SMIL 3.0 Language profile is defined as a markup language. The syntaxof 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 3.0 Modules".

The SMIL 3.0 Language profile design requirements are:

1. Ensure that the profile is completely backward compatible with SMIL 1.0.
2. Ensure that the profile is completely backward compatible with SMIL 2.1.
3. Ensure that all the modules' semantics maintain compatibility with SMIL semantics (this includes content and timing).
4. Adopt new W3C Recommendations when appropriate without conflicting with other requirements.

This section is normative.

In the text in this profile specification, the termLanguageProfile will be considered to refer exclusively to the SMIL 3.0 Language profile as defined in this document.

17.4.1SMIL 3.0 Language ProfileConformance

The definition of conformance for a SMIL 3.0 profile is given in theDefinitions section of theSMIL 3.0 Scalability Framework. Based on these definitions, the Language profile isaStrict Host-Language Conformant SMIL 3.0 Profile.

Within the referenced sections of the Scalability Framework, the following definitions should be used:

1. The profile identification string for the Language profile is:http://www.w3.org/2008/SMIL30/Language.
2. Documents written for the Language profile must declare the defaultSMIL namespace with thexmlnsattribute on thesmil root element.For SMIL 3.0, this is:

   xmlns="http://www.w3.org/ns/SMIL"

3. The SMIL 3.0 Language profile DOCTYPE is:

   <!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 3.0 Language//EN""http://www.w3.org/2008/SMIL30/SMIL30Language.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 (orin the corresponding XML or RelaxNG schemas) are not allowed. If the documentis invalid, the user agent should issue an error.
4. The identification string for the non-normative DTD used for integration of errata is:

   http://www.w3.org/2008/SMIL30/informative-DTD/SMIL30Language.dtd

5. Documents written for the Language Profile must declare (explicitly or implicitly via the DTD) thefollowing valuesfor theversion andbaseProfile attributes:

   version="3.0" baseProfile="Language"

   As a consequence of the two requirements above, the effective root element declaration fora Language profile document must be:

   <smil xmlns="http://www.w3.org/ns/SMIL" version="3.0" baseProfile="Language">     ...</smil>

   The root element may be extended as required with additional atttributes.

This version of SMIL provides a definition of strict host-language conformant SMIL 3.0documents, which are restricted to tags and attributes from the SMIL 3.0namespace. The Section "Extending/Restricting a SMIL3.0 Profile" provides information on using the SMIL 3.0 Languageprofile with other namespaces, for instance, on including new tags withinSMIL 3.0 documents.

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

17.4.2SMIL 3.0 Language Profile User AgentConformance

The definition of user agent conformance for SMIL 3.0 Languageprofile documents is given in theConforming SMIL 3.0 UserAgents section of theSMIL 3.0 Scalability Framework. Conforming Language profile user agents must adhere completely to this section.

17.4.3TheSMIL 3.0 Language Profile

The SMIL 3.0 Language profile supports the structured-timeline-centricmultimedia features found in the SMIL 3.0 modules. It uses only modules fromthe SMIL 3.0 recommendation. This Language profile includes thefollowing SMIL 3.0 modules:

1. Structure functionality
   1. Structure Module
   2. Identity Module
2. Media functionality
   1. BasicMedia Module
   2. BrushMedia Module
   3. MediaAccessibility Module
   4. MediaClipMarkers Module
   5. MediaClipping Module
   6. MediaDescription Module
   7. MediaOpacity Module
   8. MediaPanZoom Module
   9. MediaParam Module
   10. MediaRenderAttributes Module
3. Timing functionality
   1. AccessKeyTiming Module
   2. BasicExclTimeContainers Module
   3. BasicInlineTiming Module
   4. BasicPriorityClassContainers Module
   5. BasicTimeContainers Module
   6. EventTiming Module
   7. FillDefault Module
   8. MediaMarkerTiming Module
   9. MinMaxTiming Module
   10. MultiArcTiming Module
   11. RepeatTiming Module
   12. RepeatValueTiming Module
   13. RestartDefault Module
   14. RestartTiming Module
   15. SyncbaseTiming Module
   16. SyncBehaviorDefault Module
   17. SyncBehavior Module
   18. WallclockTiming Module
4. Content Control functionality
   1. BasicContentControl Module
   2. CustomTestAttributes Module
   3. PrefetchControl Module
   4. RequiredContentControl Module
   5. SkipContentControl Module
5. Layout functionality
   1. AlignmentLayout Module
   2. AudioLayout Module
   3. BackgroundTilingLayout Module
   4. BasicLayout Module
   5. MultiWindowLayout Module
   6. OverrideLayout Module
   7. StructureLayout Module
   8. SubRegionLayout Module
6. smilText functionality
   1. BasicText Module
   2. TextMotion Module
   3. TextStyling Module
7. Linking functionality
   1. BasicLinking Module
   2. LinkingAttributes Module
   3. ObjectLinking Module
8. Metainformation functionality
   1. Metainformation Module
9. Transition Effects functionality
   1. BasicTransitions Module
   2. FullScreenTransitions Module
   3. TransitionModifiers Module
10. Animation functionality
    1. BasicAnimation Module
11. State functionality
    1. StateInterpolation Module
    2. StateSubmission Module
    3. StateTest Module
    4. UserState Module

The collection names contained in the following table define the SMIL 3.0Language profile vocabulary.

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

Thexml:id andid attributes are used to assign a unique XMLidentifier to every element in a SMIL document. Thexml:id andid attributes are equivalent and must not bothbe used on an element. Thexml:idshould be used in preference to theidattribute. When the document uses the SMIL 3.0 Language Profile DOCTYPE, onlyxml:id must be used.

The attributes in the collection Core are defined for all the elements ofthe SMIL 3.0 Language profile.

In this document, equivalent but deprecated attributes and elements are inparentheses.

17.4.4Structure Modules

The Structure Module provides a framework for structuring a SMIL document.The Structure Module defines semantics for thesmil,head andbody elements. The SMIL 3.0 Language profileincludes the Structure functionality of theStructuremodule.

The Identity Module provides attributes to identify the SMIL version andprofile used in a SMIL document. The Identity Module defines semantics fortheversion andbaseProfile attributes. The SMIL 3.0Language profile includes the functionality of theIdentityModule. The SMIL 3.0 Language Profile DTD provides default values forversion andbaseProfile.

In the SMIL 3.0 Language profile, the Structure elements may have thefollowing attributes and content model :

The attributexmlns must be presenton the elementsmil and it must havethe value'http://www.w3.org/ns/SMIL'.

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 offill onthebody element is between the end ofthe presentation and the application end time, and therefore the effect offill is implementation dependent.

17.4.5Media Object Modules

TheMedia Object Modules providea framework for declaring media. TheMedia Object Modules define semanticsfor theref,animation,audio,img,text,textstream,video andbrush elements. The SMIL 3.0 Languageprofile includes the Media functionality of theBasicMedia,BrushMedia,MediaAccessibility,MediaClipping,MediaClipMarkers,MediaDescription,MediaOpacity,MediaPanZoom,MediaParamandMediaRenderAttributesmodules.

In the SMIL 3.0 Language profile, media elements may have the followingattributes and content model:

The attribute collections MediaDescriptionAttributes andMediaOpacityAttributes are defined as follows:

This profile adds theref,animation,audio,img,text,textstream,video andbrush elements to the content model of thepar,seq,excl andpriorityClass elements of theTiming and Synchronization Modules. It also addsthese elements to the content model of thebody element of theStructure Module, to the content model of thea element of theLinking Modules and to the contentmodel of theswitch element of theContent Control Modules.

SMIL 1.0 only allowedanchor as achild element of a media element. In addition toanchor, the following elements are allowedin SMIL 3.0 as children of a SMIL media object:area,param,animate,set,animateColor,animateMotion,meta,metadata (note that thea element is not included). Theswitch element is allowed, with therestriction that in this case the content of the switch may only be from thesame set of elements.

Media Object IntegrationRequirements

TheMediaRenderAttributesModule defines theeraseattribute, and defers definition of the "display area" to the languageprofile. "Display area" for the purposes of the SMIL 3.0 Language correspondsto a SMIL BasicLayoutregion. Theeffects oferase="never" apply after the active duration of the mediaobject and any fill period (defined by SMIL Timing and Synchronization), andonly until other media plays to the region targeted by the media object, oruntil the same media object restarts.

17.4.6Timing and Synchronization Modules

TheTiming and Synchronization Modulesprovide a framework for describing timing structure, timing controlproperties and temporal relationships between elements. TheTiming and Synchronization Modules definesemantics forpar,seq,excl andpriorityClass elements. In addition,these modules define semantics for attributes includingbegin,dur,end,fill,fillDefault,repeat (deprecated),repeatCount,repeatDur,restart,restartDefault,syncBehavior,syncBehaviorDefault,syncTolerance,syncToleranceDefault. TheSMIL 3.0 Language profile includes the Timing functionality of theAccessKeyTimingModule,BasicInlineTimingModule,BasicTimeContainersModule,BasicExclTimeContaineModule,BasicPriorityClassContainersModule,EventTimingModule,FillDefaultModule,MediaMarkerTimingModule,MinMaxTimingModule,MultiArcTimingModule,RepeatTiming Module,RepeatValueTimingModule,RestartDefaultModule,RestartTiming Module,SyncbaseTimingModule,SyncBehavior Module,SyncBehaviorDefaultModule,WallclockTimingModule modules.

In the SMIL 3.0 Language profile, Timing and Synchronization elements mayhave the following attributes and content model :

The Attribute collections Timing and BasicTiming are defined asfollows:

This profile adds thepar,seq andexcl elements to the content model of thebody element of theStructure Module, to the content model of thea element of theLinking Modules and to the contentmodel of theswitch element of theContent Control Modules.

Elements of theMedia ObjectModules, elements of theAnimationModule, elements of theState Modules andthesmilText element of thesmilText Modules have the attributes describingtiming and properties of contents.

Supported Event Symbols

The SMIL 3.0 Language profile specifies which types of events may be usedas part of thebegin andend attribute values. The supported events aredescribed as Event-symbols according to thesyntax introduced in theSMIL Timing and Synchronization module.

The supported event symbols in the SMIL 3.0 Language profile are:

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 may 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 only is raised at the beginning of the first iteration. The beginEvent is delivered to elements which 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.

This example is informative.

In the following example,

<ref xml:id="x" end="30s" src="15s.mpg" /><ref xml:id="y" end="10s" src="20s.mpg" /><ref xml:id="z" 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 may only be active on one object at a time, the state of being within an object's bounds may 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.

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.

topLayoutCloseEvent:

Raised when a topLayout closes for any reason. This event is delivered to that topLayout. If a topLayout reopens when additional media becomes active in its region(s), this event will be raised again if and when the topLayout closes again, and will be raised every subsequent time it closes. This event is delivered totopLayout elements only and does not bubble.

topLayoutOpenEvent:

Raised when a topLayout window opens. This event is delivered to that topLayout. If a topLayout closes and then reopens when additional media becomes active in its region(s), this event will be raised again, and will be raised every subsequent time it reopens. This event is delivered totopLayout elements only and does not bubble.

stateChange(ref):

Raised by thestate element. The parameter is a reference to an item in the data model. Whenever any of the referenced data model item is changed, this event is raised.

contentControlChange(attrname):

Raised by the root of the SMIL document when the named Content Control test values has changed. It does not bubble. The list of allowed values forattrname is taken from theContent Control Module attribute names. The parameterless contentControlChange event is raised as well.

contentControlChange:

Raised by the root of the SMIL document when any Content Control test value has changed. It does not bubble.

Order of raising of simultaneous events:

There will be cases where events occur simultaneously. To ensure that eachSMIL 3.0 Language implementation handles them in the same order, thefollowing order must be used to resolve ties:

1. InBoundsEvent
2. focusInEvent (should follow 1)
3. OutOfBoundsEvent
4. activateEvent (should follow 2)
5. focusOutEvent (should follow 3)
6. endEvent
7. beginEvent (must follow 6)
8. repeatEvent
9. topLayoutCloseEvent
10. topLayoutOpenEvent (must follow 9)
11. stateChange
12. contentControlChange(param)
13. contentControlChange

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.

The topLayoutOpenEvent and topLayoutCloseEvent events do not bubble andare delivered to thetopLayoutelement on which the event occurs.

Extending the set of supported events

The SMIL 3.0 Language profile supports an extensible set of events. Inorder to resolve possible name conflicts with the events that are supportedin this profile qualified event names are supported. Namespace prefixes areused to qualify the event names. As a result, the colon is reserved in beginand end attributes for qualifying event names.

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

Integration definitions

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.

17.4.7Content Control Modules

TheContent Control Modules provide aframework for selecting content based on a set of test attributes. TheContent Control Modules define semantics for theswitch,prefetch,customAttributes andcustomTest elements. The SMIL 3.0Language profile includes the Content Control functionality of theBasicContentControl,CustomTestAttributes,PrefetchControl,RequiredContentControlandSkipContentControlmodules.

In the SMIL 3.0 Language profile, Content Control elements may have thefollowing attributes and content model :

This profile adds theswitchelement to the content model of thepar,seq andexcl elements of theTiming and Synchronization Modules, the contentmodel of thebody and thehead elements of theStructure Module, the content model of thea element of theLinking Modules, and the content modelof theref,animation,audio,img,text,textstream,video andbrush elements of theMedia Object Modules. The profile addsthecustomAttributeselement to the content model of thehead element and thecustomTest element to the content modelof thecustomAttributeselement.

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

The collection of Attributes Test is added to all the elements defined inthe SMIL 3.0 Language profile, exceptbody,br,clear,customAttributes,customTest,div,head,meta,metadata,p,span,state,submission,tev andtextStyling. A SMIL 3.0 user agentmust support all of the values for thesystemOperatingSystem andsystemCPU attributes 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 andsystemCPU attributes.

17.4.8Layout Modules

TheLayout Modules provide a framework forspatial layout of visual components. TheLayoutModules define semantics for theregion,root-layout,topLayout,layout and theregPoint elements. The SMIL 3.0 Languageprofile includes the Layout functionality of theAlignmentLayoutModule,AudioLayoutModule,BackgroundTilingLayoutModule,BasicLayoutModule,MultiWindowLayoutModule,OverrideLayoutModule,StructureLayoutModule,SubRegionLayoutModule modules.

In the SMIL 3.0 Language profile, Layout elements may have the followingattributes and content model :

The "background-color"attribute of SMIL1.0 is deprecated in favor of "backgroundColor", but both aresupported.

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 this element tothe content model of theswitchelement of theContent Control Modules, whentheswitch element is a child of thehead element.

17.4.9smilText Modules

ThesmilText Modules provide a light-weightmethod of adding in-line text to a SMIL presentation. ThesmilText Modules define semantics for thesmilText,tev,clear,br,span,p,div,textStyle,textStyling elements and theirattributes. The SMIL 3.0 Language profile includes the smilText functionalityof theBasicText,TextStyling andTextMotion modules.

In the SMIL 3.0 Language profile, SMILtext elements may have the followingattributes and content model:

This profile adds thesmilTextelement to the content model of thepar,seq,excl andpriorityClass elements of theTiming and Synchronization Modules. It also addsthe elements to the content model of thebody element of theStructure Module, to the content model of thea element of theLinking Modules and to the contentmodel of theswitch element of theContent Control Modules.

The SMILtext functionality is used to define the Attribute set"TextAttributes":

17.4.10Linking Modules

TheLinking Modules provide aframework 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 3.0Language profile includes the Linking functionality of theBasicLinking,LinkingAttributesandObjectLinking modules.

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

Support for URIs with XPointer fragment identifier syntax is notrequired.

In the SMIL 3.0 Language profile, Linking elements may have the followingattributes and content model :

This profile adds thea element to thecontent model of thepar,seq andexcl elements of theTiming and Synchronization Modules. It also addsthe elements to the content model of thebody element of theStructure Module and to the content model oftheswitch element of theContent Control Modules.

In the SMIL 3.0 language 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.

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.

For SMIL 1.0 backward compatibility, theanchor element is available but deprecatedin favor ofarea. Theanchor element supports the same attributesasarea, both the new SMIL 3.0attributes and the SMIL 1.0 attributes as defined in[SMIL10].

SMIL 1.0 backward compatibility: The show attribute valuepause is deprecated in favor of setting theshow attribute tonew and thesourcePlaystate attribute topause.

17.4.11Metainformation Module

TheMetainformation Module provides aframework for describing a document, either to inform the human user or toassist in automation. TheMetainformationModule defines semantics for themeta andmetadata elements. The SMIL 3.0 Languageprofile includes the Metainformation functionality of theMetainformation module.

In the SMIL 3.0 Language profile, Metainformation elements may have thefollowing attributes and content model :

This profile adds themeta andmetadata elements to the content model ofall elements exceptmeta,metadata andstate.

The content model of metadata is empty. Profiles that extend the SMIL 3.0Language profile may define the RDF (Resource Description Framework) schemato be used in extending the content model of the metadata element. TheResource Description Framework is defined in the W3C RDF Recommendation[RDFsyntax]. Other XML-based metadata formats may also be included in asmiliar manner. Note that if any content is added to themetadata element, a DOCTYPE must not bedeclared in the document.

17.4.12Transition Effects Modules

TheTransition Modules provide aframework for describing transitions such as fades and wipes. TheTransition Modules define semantics for thetransition element and thetransIn andtransOut attributes. The SMIL 3.0Language profile includes the functionality of theBasicTransitions,TransitionModifiersand theFullScreenTransitionsModule modules.

In the SMIL 3.0 Language 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 Effects Modules addtransIn andtransOut attributes toref,animation,audio,img,text,textstream,video andbrush elements of theMedia Object Modules.

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

17.4.13Animation 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 SMIL 3.0 Language profile includes the animationfunctionality of theBasicAnimation module.TheBasicAnimation Module defines thesemantics for theanimate,set,animateMotion andanimateColor elements.

In the SMIL 3.0 Language profile, Animation elements may have thefollowing attributes and content model :

This profile adds theanimate,set,animateMotion andanimateColor elements to the contentmodel of thepar,seq,excl andpriorityClass elements of theTiming and Synchronization Modules. It also addsthese elements to the content model of thebody element of theStructure Module, to the content model of thea element of theLinking Modules and to the contentmodel of theswitch element of theContent Control Modules.

Specifying the target element of the animation

The animation target elements supported in the SMIL 3.0 Language profileare theregion element defined in theLayout Modules, thearea (anchor) element defined in theLinking Modules and theref,animation,audio,img,text,textstream,video and thebrush elements defined in theMedia Objects modules.

The SMIL 3.0 Language 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 may be subject toanimation. The attributecoords isconsidered of type string in this profile. This means that only discretenon-additive animation is supported on this attribute.

The media elements have the following sub-region attributes which may besubject to animation:left,right,top,bottom,width,height,z-index andbackgroundColor.

Integration definitions

The SMIL 3.0 Language profile defines a set of integration definitions asrequired by the Animation modules. These definitions are:

• Animation values in the SMIL 3.0 Language 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 3.0 Language profile.
• The SMIL 3.0 Language profile supports CSS2[CSS2] color names as described in theLayout modules. 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.

17.4.14State Modules

TheState Modules provide a framework fordeclaratively manipulating various bits of state in a SMIL presentation. TheState Modules define semantics for thedelvalue,newvalue,send,setvalue,state andsubmission elements and theaction,expr,language,method,name,ref,replace,submission andvalue attributes. The SMIL 3.0 Languageprofile includes the State functionality of theStateTest,UserState,StateSubmission,StateInterpolationmodules.

In the SMIL 3.0 Language profile, the State elements may have thefollowing attributes and content model:

This profile adds thestate andsubmission elements to thecontent model of thehead element oftheStructure Module, and thesetvalue,newvalue,delvalue andsend elements to the content model of thebody,switch,a,par,seq,excl,priorityClass elements. It also addstheexpr attribute to all timedelements within the content model of thebody element.

The content model of thestateelement is declared as empty. Thestate element defines the data model of theSMIL State engine using the language defined by thelanguage attribute. If that language isXPath 1.0 the contents of thestateelement is an XML document that is not imported into SMIL 3.0 but needs to bedeclared using a namespace prefix. For other languages the contents of thestate element are probably CDATA. Notethat if any content is added to thestate element, a DOCTYPE must not bedeclared in the document.

Thesubmission attribute valueis an IDREF that refers to asubmission element.

Themethod attribute must at leastsupport the valuesget,put andpost. Serializationand submission must follow the description of these methods in[XFORMS10],section 11.2. Support for other methods described in that document isoptional.

Interpolation of values using the mechanism from theStateInterpolationmodule is supported on the attributes for whichanimation is supported.Interpolation is also supported on thesrc,href,clipBegin andclipEnd attributes. Interpolation isdisallowed on the Timing and Synchronization attributes. Use of interpolationon other attributes is implementation-dependent.

Expression Language and DataModel

Support for using XPath 1.0 as the expression language is required.Support for other languages is implementation-defined. The default value forthelanguage attribute ishttp://www.w3.org/TR/1999/REC-xpath-19991116, whichdenotes the use of XPath 1.0 as the expression language.

When using XPath as the expression language, the content of thestate element must be a single XML document.If this document is empty at initialization time a single empty<data/> root element is added.

When using XPath as the expression language the following constraints arein force:

• Theexpr attribute value is an XPath 1.0 expression that must evaluate to aboolean.
• Theref attribute value is an XPath 1.0 expression that must evaluate to anodeset containing exactly one node.
• Thetarget attribute value is an XPath 1.0 expression that must evaluate to anodeset containing exactly one node.
• Thevalue attribute value is an XPath 1.0 expression that must evaluate to astring.
• Thename attribute value must be a valid XML element name.
• Thenewvalue element must have aname attribute. Theref attribute is optional and defaults to/*.

Interpretation of XPath expressions depends on anexpressioncontext. That context is defined thus:

• Thecontext node is the root of the document defined in thestate element.
• Thecontext position andcontext size refer to that same root node.
• Thevariable bindings are empty.
• Thefunction library consists of the functions defined in the StateTest module and theXPath Core Function Library.
• Theset of namespace declarations is defined by thexmlns attribute on the context node.

This section is normative.

TheSMIL 3.0 Language profile Document TypeDefinition is defined as a set of SMIL 3.0 modules. All SMIL 3.0 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.

This section is normative.

The following royalty-free media formats should be supported:

• audio/basic[MIME-2]
• Ogg Vorbis audio (application/ogg)[VORBIS]
• image/png[PNG-MIME],[PNG-REC]
• image/jpeg[MIME-2],[JFIF] (Seebelow)
• Ogg Theora video (application/ogg)[THEORA]

While many SMIL user agents support speciality media types for streamingaudio and video content, SMIL user agent developers are also encouraged tosupport the following non-royalty-free media formats to furtherinteroperability of SMIL content:

• audio/AAC (reference to follow)
• video/H264 (reference to follow)

Since both of these technologies are not freely available to user agentdevelopers, the actual availability will remain player dependent.

<switch>  <audio src="non-baseline-format-object" ... />  <audio src="baseline-format-object" ... /></switch>

17.6.1JPEG Support

This section specifies the JPEG support recommended by a SMIL 3.0implementations. The recommended support is targeted at specifying a level offunctionality known to be compatibly supported within the industryandwithout licensing issues.

In general when people refer to JPEG[JPEG], they actually mean JPEGcompressed images within the JFIF[JFIF] file format. JFIF was created bythe Independent JPEG Group (IJG) for storing a single JPEG-compressed imagein a file.

SMIL 3.0 User Agents should support JPEG images stored in a JFIF file[JFIF]. Other transport or storage mechanisms may be supported.

The following coding processes defined by the JPEG specification[JPEG],in Table 1, section 4.11, should be supported:

• Baseline process
• Extended DCT-based processes (with the exception of arithmetic coding).

The following statements also apply:

• 8-bit samples should be supported. 12-bit samples may be supported, (Section 4.7[JPEG]).
• Support for the DNL Marker (Section 3.2[JPEG]) is not required.
• Support for non-integer sampling ratios is not required. (A.1.1[JPEG]).

The following encoding processes may be supported

• Complete Extended DCT-based processes.
• Lossless Processes
• Hierarchical Processes

SMIL 3.0 UA's should convert Y,Cb,Cr values compressed in the JPEG imageto RGB as defined in the JFIF specification[JFIF] and may assume that theRGB values are sRGB.