This section is informative.
Since the publication of SMIL 1.0
Modularization is an approach in which markup functionality isspecified as a set of modules that contain semantically-related XML elements,attributes, and attribute values.Profiling is the creation of anXML-based language through combining these modules, in order to provide thefunctionality required by a particular application.
Profiling introduces the ability to tailor an XML-based language tospecific needs, e.g. to optimize presentation and interaction for theclient's capabilities. Profiling also adds the ability for integratingfunctionality from other markup languages, releasing the language designerfrom specifying that functionality. Moreover, it provides for consistency inmarkup through the use of the same model to incorporate a function. Identicalconstructs ease authoring, while at the user agent side there is a potentialfor re-use of code. For example, a scheduler supporting SMIL timing andsynchronization functionality could be used for SMIL documents, XHTML+SMILdocuments, and SVG documents.
Modularization enables language designers to specify dedicated markupintended for integration with other, existing, language profiles. Examples ofspecifications intended for such integration are MathML and XForms
Modularization and profiling use the extensibility properties of XML, andrelated technology like XML namespaces and XML Schema
This part of the SMIL 2.1 specification describes the framework on whichSMIL modularization and profiling is based, and specifies the SMIL 2.1Modules, their identifiers, and the requirements for conformance within thisframework.
This section is informative.
The modularization approach used in this specification derives from thatset forth in XHTML Modularization
AModule is a collection ofsemantically-related XML elements, attributes, and attribute values thatrepresents a unit of functionality. Modules are defined in coherent sets.This coherency is expressed in that the elements of these modules areassociated with the same namespace.
ALanguage Profile is acombination of modules. Modules areatomic, i.e. they cannot besubset when included in a language profile. Furthermore, a modulespecification may include a set of integration requirements, to whichlanguage profiles that include the module must comply.
Commonly, there is a main language profile that incorporates nearly allthe modules associated with a single namespace. For example, the SMIL 2.1language profile uses most of the SMIL 2.1 modules. Usually, the same nameis used to loosely reference both - "SMIL 2.1" in the example. Also, thename "profile" is used to mean "language profile".
Other language profiles can be specified that are subsets of the largerone, or that incorporate a mixture of modules associated with differentnamespaces. SMIL 2.1 Basic is an example of the first, XHTML+SMIL of thelatter.
A special module in a language profile is the so-calledStructure Module, in that itcontains the root element of the language profile, e.g. <smil> or<html>. Any language profile that incorporates modules associated witha single namespace will include the Structure module associated with thatnamespace.
Other modules that require special mention are those that characterize thecore of the functionality provided by the namespace. This is expressed by thenotions ofhost language andintegration set.Both of them relate to a set of conformance requirements for languageprofiles, which includes the requirement to incorporate at least the core setof modules. The set may be different for a host language and an integrationset. A host language must incorporate the Structure module; an integrationset need not. There may be other differences as well.
The main purpose of language profile conformance is to enhanceinteroperability. Preferably, the mandatory modules for host languageconformance are defined in such a way that any document interchanged in aconforming language profile will yield a reasonable presentation when thedocument renderer, while supporting the associated mandatory module set,would ignore all other (unknown) elements and attributes. Here, "reasonablepresentation" is to be understood as something intelligible, which is notnecessarily a close reflection of the author's original intentions. Toachieve the latter, a negotiation would have to be conducted to agree on thespecific language profile to be used for the document interchange.
This section is informative.
SMIL 2.1 specification provides three classes of changes to the SMILRecommendation, among the ten functional areas;
The following functional areas are affected by SMIL2.1.
Timing
Layout
Media Object
Transitions
This section is normative.
SMIL functionality is partitioned into ten functional areas. Within eachfunctional area a further partitioning is applied intomodules. All of these modules, and onlythese modules, are associated with the SMIL namespace.
The functional areas and their corresponding modules are:
Note: Modules marked with (**) are new Modules added in SMIL2.1. Modulesmarked with (*) are revised modules from SMIL
Each of these modules introduces a set of semantically-related elements,properties, and attributes. Each functional area has a corresponding sectionin this specification document. Further details on each of the modules isspecified within those sections.
The modules may be independent or complementary. For example, theSyncMaster module requires and builds upon the SyncBehavior module, but thePrefetchControl and SkipContentControl modules are independent from eachother. In addition, some modules require modules from other functionalareas.
Modules specify their integration requirements. When one module requiresanother module for basic features and as a prerequisite for integration, alanguage profile must include the second module in order to include thefirst. The first module is said to be adependent of the secondmodule. Dependency may be nested, in that a module may be dependent on amodule that is a dependent itself.
Table 1 presents the SMIL 2.1 modules and the modules they depend on.
| Module | Dependencies |
| AccessKeyTiming | NONE |
| AlignmentLayout | BasicLayout |
| AudioLayout | BasicLayout |
| BackgroundTilingLayout | BasicLayout |
| BasicAnimation | BasicInlineTiming |
| BasicContentControl | NONE |
| BasicInlineTiming | NONE |
| BasicExclTimeContainers | NONE |
| BasicLayout | NONE |
| BasicLinking | NONE |
| BasicMedia | NONE |
| BasicPriorityClassContainers | BasicExclTimeContiners |
| BasicTimeContainers | NONE |
| BasicTransitions | NONE |
| BrushMedia | NONE |
| CustomTestAttributes | BasicContentControl |
| EventTiming | NONE |
| ExclTimeContainers | former SMIL module REMOVED in SMIL2.1 |
| FillDefault | BasicTimeContainers, and/or BasicExclTimeContainers, BasicPriorityClassContainers, and/or TimeContainerAttributes |
| FullScreenTransitionEffects | BasicTransitions |
| HierarchicalLayout | former SMIL module REMOVED in SMIL2.1 |
| InlineTransitions | NONE |
| LinkingAttributes | NONE |
| MediaAccessibility | MediaDescription |
| MediaClipMarkers | MediaClipping |
| MediaClipping | BasicMedia |
| MediaDescription | NONE |
| MediaMarkerTiming | NONE |
| MediaParam | BasicMedia |
| MetaInformation | NONE |
| MinMaxTiming | NONE |
| MultiArcTiming | AccessKeyTiming, and/or BasicInlineTiming, and/or EventTiming, and/or MediaMarkerTiming, and/or RepeatValueTiming, and/or SyncbaseTiming, and/or WallclockTiming |
| MultiWindowLayout | BasicLayout |
| ObjectLinking | BasicLinking |
| OverrideLayout | BasicLayout |
| PrefetchControl | NONE |
| RepeatTiming | NONE |
| RepeatValueTiming | NONE |
| RestartDefault | RestartTiming |
| RestartTiming | NONE |
| SkipContentControl | NONE |
| SplineAnimation | BasicAnimation |
| Structure | BasicContentControl, and BasicInlineTiming, and BasicLayout, and BasicLinking, and BasicMedia, and BasicTimeContainers, and SkipContentControl, and SyncbaseTiming |
| SubRegionLayout | BasicLayout |
| SyncbaseTiming | NONE |
| SyncBehavior | BasicTimeContainers, and/or BasicExclTimeContainers, BasicPriorityClassContainers, and/or TimeContainerAttributes |
| SyncBehaviorDefault | SyncBehavior |
| SyncMaster | SyncBehavior |
| TimeContainerAttributes | NONE |
| TimeManipulations | NONE |
| TransitionModifiers | BasicTransitions, and/or InlineTransitions |
| WallclockTiming | NONE |
This section is informative.
SMIL is an XML-based language and conforms to the (XML) DOM Core
This section is normative.
This section specifies the identifiers for the SMIL 2.1 namespace and theSMIL 2.1 modules. Each SMIL host language conformant language profile shouldexplicitly state the namespace URI that is to be used to identify it. Thatnamespace URI must comply with the "Requirements on Identifiers forSMIL Host Language Conformant Language Profiles", defined below.
Documents authored in language profiles that include the SMIL Structuremodule can be associated with the "application/smil+xml" mimetype. Documents using the "application/smil+xml" mime type arerequired to be host language conformant. This Recommendation obsoletes theformer "application/smil" mime type as specified in SMIL 2.0[SMIL20].
The XML namespace identifier for the complete set of SMIL 2.1 modules,elements and attributes, are contained within the following namespace:
http://www.w3.org/2005/SMIL21/
Each module in this specification has a unique identifier associated withit. They are intended to uniquely and consistently identify each of them.They should be used as values in a test for whether an implementationincludes a specific module, as well as in other circumstances where a need torefer to a specific SMIL 2.1 module is necessary.
Table 2 summarizes the identifiers for SMIL 2.1 modules.
| Module name | Identifier |
| AccessKeyTiming | http://www.w3.org/2005/SMIL21/AccessKeyTiming |
| AudioLayout | http://www.w3.org/2005/SMIL21/AudioLayout |
| BackgroundTilingLayout | http://www.w3.org/2005/SMIL21/BackgroundTilingLayout |
| AlignmentLayout | http://www.w3.org/2005/SMIL21/AlignmentLayout |
| BasicAnimation | http://www.w3.org/2005/SMIL21/BasicAnimation |
| BasicContentControl | http://www.w3.org/2005/SMIL21/BasicContentControl |
| BasicInlineTiming | http://www.w3.org/2005/SMIL21/BasicInlineTiming |
| BasicExclTimeContainers | http://www.w3.org/2005/SMIL21/BasicExclTimeContainers |
| BasicLayout | http://www.w3.org/2005/SMIL21/BasicLayout |
| BasicLinking | http://www.w3.org/2005/SMIL21/BasicLinking |
| BasicMedia | http://www.w3.org/2005/SMIL21/BasicMedia |
| BasicPriorityClassContainers | http://www.w3.org/2005/SMIL21/BasicPriorityClassContainers |
| BasicTimeContainers | http://www.w3.org/2005/SMIL21/BasicTimeContainers |
| BasicTransitions | http://www.w3.org/2005/SMIL21/BasicTransitions |
| BrushMedia | http://www.w3.org/2005/SMIL21/BrushMedia |
| CustomTestAttributes | http://www.w3.org/2005/SMIL21/CustomTestAttributes |
| EventTiming | http://www.w3.org/2005/SMIL21/EventTiming |
former SMIL module removed in SMIL21 | |
| FillDefault | http://www.w3.org/2005/SMIL21/FillDefault |
| FullScreenTransitionEffects | http://www.w3.org/2005/SMIL21/FullScreenTransitionEffects |
former SMIL module removed in SMIL21 | |
| InlineTransitions | http://www.w3.org/2005/SMIL21/InlineTransitions |
| LinkingAttributes | http://www.w3.org/2005/SMIL21/LinkingAttributes |
| MediaAccessibility | http://www.w3.org/2005/SMIL21/MediaAccessibility |
| MediaClipMarkers | http://www.w3.org/2005/SMIL21/MediaClipMarkers |
| MediaClipping | http://www.w3.org/2005/SMIL21/MediaClipping |
| MediaDescription | http://www.w3.org/2005/SMIL21/MediaDescription |
| MediaMarkerTiming | http://www.w3.org/2005/SMIL21/MediaMarkerTiming |
| MediaParam | http://www.w3.org/2005/SMIL21/MediaParam |
| Metainformation | http://www.w3.org/2005/SMIL21/Metainformation |
| MinMaxTiming | http://www.w3.org/2005/SMIL21/MinMaxTiming |
| MultiArcTiming | http://www.w3.org/2005/SMIL21/MultiArcTiming |
| MultiWindowLayout | http://www.w3.org/2005/SMIL21/MultiWindowLayout |
| ObjectLinking | http://www.w3.org/2005/SMIL21/ObjectLinking |
| OverrideLayout | http://www.w3.org/2005/SMIL21/OverrideLayout |
| PrefetchControl | http://www.w3.org/2005/SMIL21/PrefetchControl |
| RepeatTiming | http://www.w3.org/2005/SMIL21/RepeatTiming |
| RepeatValueTiming | http://www.w3.org/2005/SMIL21/RepeatValueTiming |
| RestartDefault | http://www.w3.org/2005/SMIL21/RestartDefault |
| RestartTiming | http://www.w3.org/2005/SMIL21/RestartTiming |
| SkipContentControl | http://www.w3.org/2005/SMIL21/SkipContentControl |
| SplineAnimation | http://www.w3.org/2005/SMIL21/SplineAnimation |
| Structure | http://www.w3.org/2005/SMIL21/Structure |
| SubRegionLayout | http://www.w3.org/2005/SMIL21/SubRegionLayout |
| SyncbaseTiming | http://www.w3.org/2005/SMIL21/SyncbaseTiming |
| SyncBehavior | http://www.w3.org/2005/SMIL21/SyncBehavior |
| SyncBehaviorDefault | http://www.w3.org/2005/SMIL21/SyncBehaviorDefault |
| SyncMaster | http://www.w3.org/2005/SMIL21/SyncMaster |
| TimeContainerAttributes | http://www.w3.org/2005/SMIL21/TimeContainerAttributes |
| TimeManipulations | http://www.w3.org/2005/SMIL21/TimeManipulations |
| TransitionModifiers | http://www.w3.org/2005/SMIL21/TransitionModifiers |
| WallclockTiming | http://www.w3.org/2005/SMIL21/WallclockTiming |
In addition to the module identifiers above, there may be differentfeatures and variances from one language profile to another that may not beexpressed as the support or non-support of a particular module. Thesefeatures may be expressed using the following identifiers:
http://www.w3.org/2005/SMIL21/NestedTimeContainershttp://www.w3.org/2005/SMIL21/SMIL20DeprecatedFeatureshttp://www.w3.org/2005/SMIL21/SMIL10DeprecatedFeaturesImplementations that support the SMIL BasicContentControl module mustallow these as identifiers for use with the XML namespace mechanism, and mustallow the associated namespace identifier to be used with the systemRequiredtest attribute. Profiles must identify those attributes for which animplementation must return "true" (this is an integration requirement).Implementations must return "false" for modules or features which are notfully supported.
This section is informative.
Modules can also be identified collectively. The following modulecollections are defined:
http://www.w3.org/2005/SMIL21/http://www.w3.org/2005/SMIL21/Languagehttp://www.w3.org/2005/SMIL21/Mobilehttp://www.w3.org/2005/SMIL21/ExtendedMobilehttp://www.w3.org/2005/SMIL21/HostLanguagehttp://www.w3.org/2005/SMIL21/IntegrationSetThis section is informative.
In this section we specify the rules for SMIL host language and SMILintegration set conformance. First, the conformance requirements forhost languageconformance andintegration setconformance are given. The requirements are similar to those set forthfor XHTML host language document type conformance and XHTML integration setdocument type conformance[XMOD]. In a final section the requirements onidentifiers for host languageconformant language profiles are given.
Currently, there exist four language profiles using SMIL 2.1 Modules.They are theSMIL 2.1 Language Profile,theSMIL 2.1Extended Mobile Profile, theSMIL 2.1 MobileProfile and theSMIL 2.1Basic Language Profile. All four profiles are SMIL host languageconformant.
This section is normative.
The following two tables list names used to collectively reference certainsets of SMIL 2.1 elements and attributes. These are used in the definitionsof the minimum support in the two sections below on SMIL host languageconformance and SMIL integration set conformance. The term "minimum support"is used to refer to the minimum set of elements that an element can contain,and the minimum set of attributes that can be used on an element.
| Element Set Name | Elements |
| TIMING-ELMS | par,seq |
| MEDIA-ELMS | ref,animation,audio,img,video,text,textstream |
| EMPTY | no elements are required as a minimum |
| Attribute Set Name | Attributes |
| TIMING-ATTRS | begin,end,dur,repeatDur,repeatCount,max,min,fill,endsync |
| CONTCTRL-ATTRS | systemBitrate,systemCaptions,systemLanguage,systemRequired,systemSize,systemDepth,systemOverdubOrSubtitle,systemAudioDesc,systemOperatingSystem,systemCPU,systemComponent |
| MEDIA-ATTRS | src,type |
| LINKING-ATTRS | href,sourceLevel,destinationLevel,sourcePlaystate,destinationPlaystate,show,accesskey,tabindex,target,external,actuate,alt |
| COMMON-ATTRS | id,class,xml:lang,title |
A language profile is said to be SMIL 2.1 host language conformant if itincludes the following modules:
In addition, the following requirements must be satisfied:
Support of deprecated elements and attributes is no longer required forSMIL 2.1 host language conformance but it is highly recommended for allmodules the given language supports. Support of deprecated elements andattributes can only be left out in cases where interoperability with SMIL 1.0implementations is not an issue. For example, if a SMIL 2.1 host languagesupports theMultiArcTiming module,it is highly recommended that it support the deprecated syntax defined in theMultiArcTiming module.
Since the SMIL 2.1Structure modulemay only be used in a profile that is SMIL host language conformant, thisimplies that the SMIL 2.1Structuremodule must at least be accompanied with the nine other modules required forhost language conformance that were named above. Those modules themselves canstill be used in other, non SMIL host language conformant, languageprofiles.
A language profile is said to be SMIL 2.1 integration set conformant if itincludes the following modules:
In addition, the following requirements must be satisfied:
| Element | Minimum Support | |
| Elements | Attributes | |
| ref,animation,audio,img,video,text,textstream | CONTCTRL-ATTRS,TIMING-ATTRS,MEDIA-ATTRS | |
| par,seq | TIMING-ELMS,MEDIA-ELMS,switch | CONTCTRL-ATTRS,TIMING-ATTRS |
| switch | TIMING-ELMS,MEDIA-ELMS | CONTCTRL-ATTRS |
Support of deprecated elements and attributes is not required forSMIL 2.1 integration set conformance. However, when included, the aboverequirements also apply to these elements and attributes. Also, whensupported, it is required that all the deprecated elements and attributesfrom all the included modules are supported as a whole.
This section is informative.
A language profile is specified through its DTD or XML Schema. Theidentifier of these can be used to identify the language profile. SMIL 1.0has specified the default namespace declaration on its root element,
http://www.w3.org/TR/REC-smil
as the namespace identifier for SMIL 1.0
This section is normative.
For the purpose of identifying the version and the language profile used,SMIL host language conformant documents must satisfy the followingrequirements:
Syntax errors in a SMIL Host Language conformant document are handledaccording to the XML rules for well-formed or valid XML
Semantic errors can arise at various levels. One is where the declaredattribute values are of unknown value. Another is where the assembledpresentation is (possibly) conflicting, as in a case where media objects arecompeting for display space or where they are synchronized ambiguously. Theselatter types, although maybe an error according to the author's intentions,are not considered an error and the user agent will present according to theresolution rules defined in this specification.
Errors in attribute values might remain undetectable to the parser,because the value type is declared as CDATA, or because the value range isopen ended, as in the case of events, for example. However, errors inattribute values can be detected within a given language profile, where thatlanguage profile specifies the supported value set. Specifications oflanguage profiles are required to specify the error handling that is requiredwhen such an attribute value error occurs.
This section is informative.
This section describes how language profiles could be defined using theSMIL 2.1 modular DTDs. The reader is assumed to be familiar with themechanisms defined in "Modularization of XHTML"
Below, we give a short description of the files that are used to definethe SMIL 2.1 modular DTDs. See the table and the end of the section for acomplete list of the filenames involved.
Following the same mechanisms as the XHTML modular DTDs, the SMIL 2.1specification places the XML element declarations (e.g. <!ELEMENT...>)and attribute list declarations (e.g. <!ATTLIST...>) of all SMIL 2.1elements in separate files, the SMIL module files. A SMIL module file isprovided for each functional area in the SMIL 2.1 specification (that is,there is a SMIL module file for animation, layout, timing, etc).
The SMIL module files are used in the normative definitions of thespecification of the SMIL 2.1 Language Profile. Usage of the same modulefiles for defining other SMIL profiles is recommended, but not required. Therequirements that SMIL language profiles must follow are stated in theSMIL 2.1 specification, not in the DTD code.
To make the SMIL module files independent of each other, and independentof the language profiles, the element and attribute declarations make heavyuse of XML entities. This provides profiles with the necessary hooks todefine the actual content models and attributes of the SMIL elements.
The SMIL 2.1 Language Profile provides examples of how the SMIL modulefiles can be used. Most of the DTD files are reused across the differentprofiles. Reused are the SMIL module files, the files that define the datatypes and the common attributes, the "qname" file that takes care of addingnamespace prefixes if necessary, and the framework file, which takes care ofincluding files in the appropriate order.
The files that are different for each profile are the driver file anddocument model file. This would, in general, also apply to new profiles: todefine a new language profile, one has to write the extension module(s), thedriver file that defines which modules are used, and a document model filethat defines the extended document model. The driver file and document modelfile are described in more detail below.
The driver file.
This is the file that would be referenced by a document's DOCTYPEdeclaration. Its main job is to define which document model file and which ofthe SMIL module files the profile is using. It may also define an optionalnamespace to be used in all namespace prefixes. For example, to prefix allSMIL element names with "foobar", the following can be added to the start ofthe profile:
<!ENTITY % SMIL.prefixed "INCLUDE" >
<!ENTITY % SMIL.prefix "foobar" >
Elements defined in their modules as, for example, <video> willbecome parsed as <foobar:video>. This also applies for SMIL attributesthat appear on other elements, so, for example, "begin" becomes"foobar:begin". The default is that the qname prefix is empty -- that is, itis effectively turned off by default.
After these definitions, the driver file includes the framework file(which will subsequently include the data type, common attributes, qname anddocument model file), after which the SMIL module files are included that areused by this profile.
The document model file.
The document model file contains the XML entities that are used by theSMIL module files to define the content models and attribute lists of theelements in that profile.
Content models generally differ from profile to profile, or containelements from other modules. To avoid these dependencies in the SMIL modulefiles, content models need to be defined in the document model file. The(dummy) default content model as defined in the SMIL module files is "EMPTY"for all SMIL 2.1 elements.
For the same reasons, the SMIL module files only define a defaultattribute list for their elements. This default list only contains theSMIL 2.1 core attributes and the attributes that are defined in the sameSMIL module file. All other attributes need to be added to this default listby defining the appropriate XML entities. For example, the Media ObjectsModule file only adds the core and media related attributes on the mediaobjects; other attributes, such as the timing attributes, are added to thislist by the document model file.
| Driver files for the predefined profiles | |
| -//W3C//DTD SMIL 2.1 Language //EN | http://www.w3.org/2005/SMIL21/SMIL21.dtd |
| -//W3C//DTD SMIL 2.1 Extended Mobile//EN | http://www.w3.org/2005/SMIL21/SMIL21ExtendedMobile.dtd |
| -//W3C//DTD SMIL 2.1 Mobile //EN | http://www.w3.org/2005/SMIL21/SMIL21Mobile.dtd |
| Document model files for the predefined profiles | |
| -//W3C//ENTITIES SMIL 2.1 Language Profile Document Model 1.0//EN | http://www.w3.org/2005/SMIL21/smil-language-profile-model-1.mod |
| -//W3C//ENTITIES SMIL 2.1 Extended Mobile Profile Document Model 1.0//EN | http://www.w3.org/2005/SMIL21/smil-extended-mobile-profile-model-1.mod |
| -//W3C//ENTITIES SMIL 2.1 Mobile Profile Document Model 1.0//EN | http://www.w3.org/2005/SMIL21/smil-mobile-profile-model-1.mod |
| SMIL 2.1 module files | |
| -//W3C//ELEMENTS SMIL 2.1 Animation//EN | http://www.w3.org/2005/SMIL21/SMIL-anim.mod |
| -//W3C//ELEMENTS SMIL 2.1 Content Control//EN | http://www.w3.org/2005/SMIL21/SMIL-control.mod |
| -//W3C//ELEMENTS SMIL 2.1 Layout//EN | http://www.w3.org/2005/SMIL21/SMIL-layout.mod |
| -//W3C//ELEMENTS SMIL 2.1 Linking//EN | http://www.w3.org/2005/SMIL21/SMIL-link.mod |
| -//W3C//ELEMENTS SMIL 2.1 Media Objects//EN | http://www.w3.org/2005/SMIL21/SMIL-media.mod |
| -//W3C//ELEMENTS SMIL 2.1 Document Metainformation//EN | http://www.w3.org/2005/SMIL21/SMIL-metainformation.mod |
| -//W3C//ELEMENTS SMIL 2.1 Document Structure//EN | http://www.w3.org/2005/SMIL21/SMIL-struct.mod |
| -//W3C//ELEMENTS SMIL 2.1 Timing//EN | http://www.w3.org/2005/SMIL21/SMIL-timing.mod |
| -//W3C//ELEMENTS SMIL 2.1 Transition//EN | http://www.w3.org/2005/SMIL21/SMIL-transition.mod |
| Other utilities: data types, common attributes, qname and frame work files | |
| -//W3C//ENTITIES SMIL 2.1 Datatypes 1.0//EN | http://www.w3.org/2005/SMIL21/smil-datatypes-1.mod |
| -//W3C//ENTITIES SMIL 2.1 Common Attributes 1.0//EN | http://www.w3.org/2005/SMIL21/smil-attribs-1.mod |
| -//W3C//ENTITIES SMIL 2.1 Qualified Names 1.0//EN | http://www.w3.org/2005/SMIL21/smil-qname-1.mod |
| -//W3C//ENTITIES SMIL 2.1 Modular Framework 1.0//EN | http://www.w3.org/2005/SMIL21/smil-framework-1.mod |