The SMIL 2.1 Extended Mobile Profile is a collection of SMIL 2.1 modules that provide extensive support for the SMIL 2.1 Language within the context of an advanced (for 2005) mobile device. Such a device is expected to have a high-resolution display and sufficient memory and processor capacity to render nontrival SMIL documents. Although not as complete as the full SMIL 2.1 Language Profile, the SMIL 2.1 Extended Mobile Profile is rich enough to meet the needs of a wide range of interactive presentations.
The SMIL 2.1 Extended Mobile Profile is new to SMIL 2.1. It builds on the functionality defined for the SMIL 2.1 Mobile Profile. The functionality of the SMIL 2.1 Extended Mobile Profile may be further extended by using the SMIL 2.1 Scalability Framework.
This section is informative.
The SMIL 2.1 Extended Mobile Profile is defined as a markup language. The syntax 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 term Extended Mobile Profile will be considered to refer exclusively to the SMIL 2.1 Extended Mobile Profile as defined in this document.
The Extended Mobile Profile design requirements are:
This section is informative.
The Third Generation Partnership Project 2 (3GPP2) [3GPP2] defines its own SMIL language profile. The revision A of the 3GPP2 SMIL File Formats for Multimedia Services, which is now under discussion (as of Dec. 2005), defines the SMIL profile including some additional modules compared to the 3GPP SMIL profile [3GPP26.234R5]; AccessKeyTiming Module, MultiArcTiming Module, BasicAnimation Module and AudioLayout Module. A future revision of it may incorporate SMIL 2.1.
The Extended Mobile Profile includes all modules of 3GPP2 revision A SMIL and the following additional ones: BasicExclTimeContainers Module, SubRegionLayout Module, BackgroundTilingLayout Module, AlignmentLayout Module, OverrideLayout Module, FullScreenTransitions Module and BrushMedia Module.
This section is normative.
This version of SMIL provides a definition of strictly conforming Extended Mobile Profile documents, which are restricted to tags and attributes from the SMIL 2.1 namespace. In the future, the language described in this profile may be extended by other W3C Recommendations, or by private extensions. For these extensions, the following rules must be obeyed:
Conformant Extended Mobile Profile user agents are expected to handle documents containing extensions that obey these two rules.
The Extended Mobile Profile is a conforming SMIL 2.1 specification. The rules for defining conformant documents are provided in the SMIL 2.1 Language Conformance in the SMIL 2.1 Language Profile document. Note that while the referenced section is written for the SMIL 2.1 Language Profile, all of the rules apply to the Extended Mobile Profile as well, with the exception that the Extended Mobile Profile's namespace should be used instead of the SMIL 2.1 Language Profile's namespace.
Documents written for the Extended Mobile Profile must declare a default namespace for its elements with an xmlns attribute on the smil 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 Mobile Profile must consider the implications of the use of namespace extension syntax. Please consult the section on Scalable Profiles for restrictions and recommendations for best practice when extending SMIL.
Extended Mobile Profile DOCTYPE declaration
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 XML
document.
Note that this implies that extensions to the syntax defined in the DTD are
not allowed. If the document is invalid, the user agent should issue an
error.
The collection names contained in the following table define the Extended Mobile Profile vocabulary.
| SMIL 2.1 Extended Mobile Profile | |
|---|---|
| Collection Name | Elements in Collection |
| Animation | animate, set, animateMotion, animateColor |
| ContentControl | switch, prefetch |
| Layout | region, root-layout, layout, regPoint |
| LinkAnchor | a, area [anchor] |
| MediaContent | text, img, audio, video, ref, animation, textstream, brush, param, paramGroup |
| Metainformation | , |
| Structure | smil, head, body |
| Schedule | par, seq, excl |
| Transition | transition |
In the following sections, we define the set of elements and attributes used in each of the modules included in the Extended Mobile Profile. The content model for each element is described. The content model of an element is a description of elements which can appear as its direct children. The special content model "EMPTY" means that a given element may not have children.
| Collection Name | Attributes in Collection |
|---|---|
| Core | id (ID), class (NMTOKEN), title (CDATA), alt (CDATA), longdesc (CDATA), xml:base (CDATA) |
| I18n | xml:lang (NMTOKEN) |
The id, class and title attributes in the collection Core are defined for all the elements of the Extended Mobile Profile. The id attribute is used in the Extended Mobile Profile to assign a unique XML identifier to every element in a SMIL document. In this document, equivalent but deprecated attributes and elements are shown in square brackets.
The Animation Module provides a framework for incorporating animation into a timing framework, and a mechanism for composing the effects of multiple animations. The Animation Module uses the timing modules included in this profile for the underlying model of time. The Extended Mobile Profile includes the Animation functionality of the BasicAnimation module. The BasicAnimation Module defines the semantics for the animate, set, animateMotion and animateColor elements.
In the Extended Mobile Profile, Animation elements can have the following
attributes and content model :
| Animation Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| animate | Core, I18n, Timing, Test, attributeName, attributeType, targetElement, from, to, by, values, calcMode, accumulate, additive, skip-content, fill (freeze | remove | hold | auto | default) | EMPTY |
| set | Core, I18n, Timing, Test, attributeName, attributeType, targetElement, to, skip-content, fill (freeze | remove | hold | auto | default) | EMPTY |
| animateMotion | Core, I18n, Timing, Test, targetElement, origin, from, to, by, values, calcMode, accumulate, additive, skip-content, fill (freeze | remove | hold | auto | default) | EMPTY |
| animateColor | Core, I18n, Timing, Test, attributeName, attributeType, targetElement, from, to, by, values, calcMode, accumulate, additive, skip-content, fill (freeze | remove | hold | auto | default) | EMPTY |
This profile adds the animate, set, animateMotion and animateColor 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.
Specifying the target element of the animation
The animation target elements supported in the Extended Mobile Profile are the region element defined in the Layout Modules, the area [anchor] element defined in the Linking Modules and the text, img, audio, animation, video, ref, textstream and the brush elements defined in the Media Objects modules.
The SMIL Extended Mobile Profile uses the targetElement attribute to identify the element to be affected by animation elements. As recommended in the BasicAnimation Module when the targetElement attribute is supported, this profile excludes the XLink attributes href, type, actuate and show from the animate, set, animateMotion and animateColor elements.
Specifying the target attribute of the animation
The target attributes of the animations are a subset of those of the region, area [anchor], and media elements. The animatable attributes of the region, area [anchor], and media elements are listed in the table below.
The area [anchor] element has the coords attribute which can be subject to animation. The attribute coords is considered of type string in this profile. This means that only discrete non-additive animation is supported on this attribute.
Media elements have the following region attributes which can be subject
to animation: left, right, top, bottom, width, height, z-index and backgroundColor [background-color].
Integration definitions
The Extended Mobile Profile defines a set of integration definitions as required by the Animation modules. These definitions are:
coerced-integer-value = Math.floor( interpolated-value + 0.5 )
The Content Control
Modules provide a framework for selecting content based on a set of test
attributes. The Content Control
Modules define semantics for the switch and prefetch elements. The Extended Mobile
Profile includes the Content Control functionality of the BasicContentControl, PrefetchControl and SkipContentControl modules.
In the Extended Mobile Profile, Content Control elements can have the
following attributes and content model :
| Content Control Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| switch | Core, I18n, Test | ((Schedule | MediaContent | ContentControl | LinkAnchor | Animation)* | (layout )*) |
| prefetch | Core, I18n, Test, Timing, mediaSize, mediaTime, bandwidth, src, skip-content, clipBegin, clipEnd | EMPTY |
This profile adds the switch element to the content model of the par, seq and excl elements of the Timing and Synchronization Modules, of the body and the head elements of the Structure Module, of the content model of the a element of the Linking Modules.
Content Control functionality is used to define the attribute set "Test":
The Test attributes collection is added to all the elements defined in the Extended Mobile Profile. An Extended Mobile user agent must support all of the values for the and systemCPU attributes listed in the Content Control Modules. In addition, the user agent should accept namespaced values as future extensions, and not declare a syntax error. The user agent should return false for unrecognized values of the and systemCPU attributes.
The Layout Modules provide a framework for spatial layout of visual components. The Layout Modules define semantics for the region, root-layout, layout and the regPoint elements. The Extended Mobile Profile includes the Layout functionality of the BasicLayout, AudioLayout, SubRegionLayout, BackgroundTilingLayout, AlignmentLayout, OverrideLayout modules.
In the Extended Mobile Profile, Layout elements can have the following
attributes and content model :
| Layout Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| region | Core, I18n, Test, backgroundColor [background-color], backgroundImage, backgroundRepeat, bottom, fit (fill | hidden | meet | meetBest | scroll | slice), height, left, mediaAlign, regAlign, regionName, regPoint, right, showBackground (always | whenActive), skip-content, soundAlign, soundLevel, top, width, z-index | region* |
| root-layout | Core, I18n, Test, backgroundColor [background-color], backgroundImage, backgroundRepeat, width, height, skip-content | EMPTY |
| layout | Core, I18n, Test, type | (root-layout | region | regPoint)* |
| regPoint | Core, I18n, Test, top, bottom, left, right, regAlign ( topLeft|topMid | topRight | midLeft | center | midRight | bottomLeft | bottomMid | bottomRight ), skip-content | EMPTY |
The attribute collection SubregionAttributes is defined as follows:
| Collection Name | Attributes in Collection |
|---|---|
| SubregionAttributes | top, left, bottom, right, width, height, z-index, fit, backgroundColor [background-color], mediaAlign, regPoint, regAlign, soundAlign, soundLevel |
This profile adds the layout element to the content model of the head element of the Structure Module. It also adds this element to the content model of the switch element of the Content Control Modules, when the switch element is a child of the head element. The profile also adds the following a
The Linking Modules provide a framework for relating documents to content, documents and document fragments. The Linking Modules define semantics for the a and area [anchor] elements. They define also the semantics of a set of attributes defined for these elements. The SMIL 2.1 Extended Mobile Profile includes the Linking functionality of the BasicLinking and LinkingAttributes modules.
Both the a and area [anchor] elements have an href attribute, whose value must be a valid URI.
Support for URIs with XPointer fragment identifier syntax is not required.
In the Extended Mobile Profile, Linking elements can have the following
attributes and content model :
| Linking Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| a | Core, I18n, Timing, Test, href, sourceLevel, destinationLevel, sourcePlaystate (play | pause | stop) 'pause', destinationPlaystate (play | pause) 'play', show (new | replace | pause) 'replace', accesskey, tabindex, target, external, actuate | (Schedule | MediaContent | ContentControl | Animation )* |
| area [anchor] | Core, I18n, Timing, Test, shape, coords, href, nohref, sourceLevel, destinationLevel, sourcePlaystate, destinationPlaystate, show, accesskey, tabindex, target, external, actuate, shape, fragment, skip-content | (animate | set)* |
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 these elements to the content model of the body element of the Structure Module.
In the Extended Mobile Profile, a value of onLoad set on the attribute actuate indicates that the link is automatically traversed when the linking element becomes active. For linking elements containing SMIL timing, this is when the active duration of the linking element begins.
Linking behavior in the Extended Mobile Profile may be used to navigate within a document or to link across documents. When linking to destinations outside the current document, implementations may ignore the values "play" and "pause" of the sourcePlaystate attribute, and the values "new" and "pause" of the show attribute; in these cases, the semantics of the "stop" attribute (for sourcePlaystate ) and the "replace" attribute (for show) should be used. If an implementation ignores the values of the sourcePlaystate and show attributes, it may also ignore the sourceLevel attribute.
The attribute tabindex specifies the position of the element in the tabbing order at a particular instant for the current document. The tabbing order defines the order in which elements will receive focus when navigated by the user via an input device such as a keyboard. At any particular point in time, only active elements are taken into account for the tabbing order; inactive elements are ignored.
When a media object element has a tabindex attribute and becomes active, then its ordered tab index is inserted in the SMIL tab index at the location specified by the media object's tabindex attribute value. This assumes that the media object itself has tab indices, such as embedded HTML with tabindex attributes. This enables all link starting points in a SMIL presentation to have a place on the ordered list to be tab-keyed through, including those in embedded presentations.
The Extended Mobile Profile does not define four-way navigation in the SMIL 2.1 release. A definition for four-way navigation is expected in the future version of SMIL.
The Media Object Modules provide a framework for declaring media. The Media Object Modules define semantics for the ref, animation, audio, img, video, text, textstream, param, paramGroup and brushbrush elements. The Extended Mobile Profile includes the Media Object functionality of the BasicMedia, MediaClipping, MediaParam, BrushMedia and MediaAccessibility modules.
In the Extended Mobile Profile, media elements can have the following attributes and content model:
| Media Object Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| text, img, audio, animation, video, ref, textstream | Core, I18n, Timing, Test, SubregionAttributes, region, fill (freeze | remove | hold | transition | auto | default), , copyright, abstract, src, type, erase, mediaRepeat, paramGroup, sensitivity, tabindex, transIn, transOut, clipBegin [clip-begin], clipEnd [clip-end], readIndex, endsync. | (param | area [anchor] | switch | Animation)* |
| brush | Core, I18n, Timing, Test, SubregionAttributes, abstract, region, fill (freeze | remove | hold | transition | auto | default), , copyright, color, skip-content, erase, sensitivity, tabindex, transIn, transOut, readIndex, endsync. | (param | area [anchor]| switch | Animation)* |
| param | Core, I18n, Test, name, value, valuetype (data | ref | object), type, skip-content | EMPTY |
| paramGroup | Core, I18n, Test, skip-content | (param)* |
This profile adds the ref, animation, audio, img, video, text, textstream and brush elements to the content model of the par, seq, and excl elements of the Timing and Synchronization Modules and also adds these elements to the content model of the body element of the Structure Module. It also adds these elements to the content model of the a element of the Linking Modules. Lastly, this profile adds the paramGroup element to the region element of the Layout Modules.
The following elements are allowed as children of a media object reference: anchor, area [anchor], param, animate, set, animateColor, animateMotion. The a element is not included in this list. The switch element is allowed, with the restriction that in this case the content of the switch may only be from the same set of elements as is listed above.
This section is informative.
The members of the W3C SYMM Working Group recommend that at least the following content types and file formats be supported by Mobile Profile user agents:
This section is normative.
The MediaParam module defines the erase attribute, and defers definition of the "display area" to the language profile. "Display area" for the purposes of the Extended Mobile Profile corresponds to a SMIL BasicLayout region. The effects of erase="never" apply after the active duration of the media object and any fill period (defined by SMIL Timing and Synchronization), and only until other media plays to the region targeted by the media object, or until the same media object restarts.
The Metainformation Module provides a framework for describing a document, either to inform the human user or to assist in automation. The Metainformation Module defines semantics for the and elements. The Extended Mobile Profile includes the Metainformation functionality of the Metainformation module.
In the Extended Mobile Profile, Metainformation elements can have the following attributes and content model :
| Metainformation Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| Core, I18n, skip-content, content (CDATA), name (CDATA) | EMPTY | |
| Core, I18n, skip-content | EMPTY | |
This profile adds the element to the content model of the head element of the Structure Module.
The content model of metadata is empty. Profiles that extend the Extended Mobile Profile may define the RDF (Resource Description Framework) schema to be used in extending the content model of the metadata element. The Resource Description Framework is defined in the W3C RDF Recommendation [RDFsyntax].
The Structure Module provides a framework for structuring a SMIL document. The Structure Module defines semantics for the smil, head, and body elements. The Extended Mobile Profile includes the Structure functionality of the Structure module.
In the Extended Mobile Profile, the Structure elements can have the following attributes and content model :
| Structure Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| smil | Core, I18n, Test, xmlns | (head?,body?) |
| head | Core, I18n | (*,(,*)?,((layout|switch),*)?, (transition+,*)?, (paramGroup+,*)?) |
| body | Core, I18n, Timing, fill, abstract, , copyright | (Schedule | MediaContent | ContentControl | a )* |
The body element acts as the root element to span the timing tree. The body element has the behavior of a seq element. Timing on the body element is supported. The syncbase of the body element is the application begin time, which is implementation dependent, as is the application end time. Note that the effect of fill on the body element is between the end of the presentation and the application end time, and therefore the effect of fill is implementation dependent.
The Timing and Synchronization Modules provide a framework for describing timing structure, timing control properties and temporal relationships between elements. The Timing and Synchronization Modules define semantics for par, seq and excl elements. In addition, these modules define semantics for attributes including begin, dur, end, repeat (deprecated), repeatCount, repeatDur, min, max. The Extended Mobile Profile includes the Timing and Synchronization functionality of the BasicInlineTiming, EventTiming, MinMaxTiming, RepeatTiming, MultiArcTiming, AccessKeyTiming, BasicTimeContainers, BasicExclTimeContainers modules.
In the Extended Mobile Profile, Timing and Synchronization elements can have the following attributes and content model :
| Timing and Synchronization Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| par | Core, I18n, Timing, Test, endsync, fill (freeze | remove | hold | auto | default), abstract, , copyright, region | (Schedule | MediaContent | ContentControl | a | Animation)* |
| seq | Core, I18n, Timing, Test, fill (freeze | remove | hold | auto | default), abstract, , copyright, region | (Schedule | MediaContent | ContentControl | a | Animation) * |
| excl | Core, I18n, Timing, Test, endsync, skip-content, fill (freeze | remove | hold | auto | default ), abstract, , copyright, region | ((Schedule | MediaContent | ContentControl | a | Animation)* |
The Attribute collection Timing is defined as follows:
| Collection Name | Attributes in Collection |
|---|---|
| Timing | begin, dur, end, repeat, repeatCount, repeatDur, min, max |
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 of the Linking Modules.
Elements of the Media Object Modules have the attributes describing timing and properties of contents.
The Extended Mobile Profile specifies which types of events can be used as part of the begin and end attribute values. The supported events are described as Event-symbols according to the syntax introduced in the SMIL Timing and Synchronization module.
The supported event symbols in the Extended Mobile Profile are:
| Event | example |
|---|---|
| focusInEvent (In DOM Level 2: "DOMFocusIn") | end="foo.focusInEvent + 3s" |
| focusOutEvent (In DOM Level 2: "DOMFocusOut") | begin="foo.focusOutEvent" |
| activateEvent (In DOM Level 2: "DOMActivate") | begin="foo.activateEvent" |
| beginEvent | begin="foo.beginEvent + 2s" |
| endEvent | end="foo.endEvent + 2s" |
| repeatEvent | end="foo.repeatEvent" |
| inBoundsEvent | end="foo.inBoundsEvent" |
| outOfBoundsEvent | begin="foo.outOfBoundsEvent + 5s" |
As defined by the SMIL syncbase timing semantics, any event timing attributes that reference an invalid time-value description will be treated as if "indefinite" were specified.
<ref id="x" end="30s" src="15s.mpg" /> <ref id="y" end="10s" src="20s.mpg" /> <ref 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.
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.
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.
There will be cases where events occur simultaneously. To ensure that each Extended Mobile implementation handles them in the same order, the following order must be used to resolve ties:
Events are listed in order of precedence, e.g., if event #6 in this list occurs at the same time as event #7, then #6 must be raised prior to #7.
The InBoundsEvent, focusInEvent, OutOfBoundsEvent, activateEvent, and focusOutEvent events do not bubble and are delivered to the target media element.
The beginEvent, endEvent and repeatEvent events do not bubble and are delivered to the timed element on which the event occurs.
The Extended Mobile Profile supports an extensible set of events. In order to resolve possible name conflicts with the events that are supported in this profile qualified event names are supported. Namespace prefixes are used to qualify the event names. As a result, the colon is reserved in begin and end attributes for qualifying event names.
For example:
<smil ... xmlns:example="http://www.example.com">
<img id="foo" .../>
<audio begin="foo.example:focusInEvent".../>
...
</smil>
A SMIL document's begin time is defined as the moment a user agent begins the timeline for the overall document. A SMIL document's end time is defined as equal to the end time of the body element.
The Transition Effects Modules provide a framework for describing transitions such as fades and wipes. The Transition Modules define semantics for the transition element. The Extended Mobile Profile includes the functionality of the BasicTransitions and FullScreenTransitions modules.
In the Extended Mobile Profile, Transition Effects elements have the following attributes and content model :
| Transition Effects Module | ||
|---|---|---|
| Elements | Attributes | Content model |
| transition | Core, I18n, Test, dur, type, subtype, startProgress, endProgress, direction, fadeColor, scope, skip-content | EMPTY |
This profile adds the transition element to the content model of the head element of the Structure Module.
The Transition Effects Modules add transIn and transOut attributes to ref, animation, audio, img, video, text, textstream and brush elements of the Media Object Modules.
The Transition Effects Modules add the transition value to the fill attribute for all elements on which this value of the fill attribute is supported.
This section is normative.
The Extended Mobile Profile Document Type Definition is defined as a set of SMIL 2.1 modules. All SMIL 2.1 modules are integrated according to the guidelines in the W3C Note "Synchronized Multimedia Modules based upon SMIL 1.0" [SMIL-MOD], and defined within their respective module sections.