This section is informative.

The DAISY profile is new for SMIL 3.0.

This section is normative.

DAISY[DAISY] digital talking books arefully accessible for persons with print disabilities, such as those withblindness, low vision, hearing impairments, deaf-blindness, motordisabilities, dyslexia, and a wide range of cognitive/intellectualdisabilities. DAISY is the recognized international standard for digitaltalking books and has been adopted worldwide by organizations serving thesegroups.

With the release of SMIL 3.0, the pre-existing DAISY standard has gottenthe opportunity to move into the mainstream of multimedia development.Several accessibility features have been added to the SMIL language, and afully-conforming language profile has been defined for DAISY books.

This section is informative.

Although SMIL has always been an integral part of the DAISY standard, noneof the existing profiles fit the needs of DAISY. The fulllanguage profile is too large to be consideredpractical, while theTiny profile lackscertain timing, state, and media object modules required by DAISY. TheUnifiedMobile profile also lacksome of what is necessary for representing DAISY books in SMIL (e.g. thestate modules), and include modules which are not required by DAISY (e.g.animation, tiling, and transitions modules).

This section is normative.

In the text in this profile specification, the termDAISY profilewill be considered to refer exclusively to the SMIL 3.0 DAISY profile asdefined in this document.

19.4.1 SMIL 3.0 DAISY ProfileConformance

The definition of conformance for a SMIL 3.0 profile is given in theDefinitionssection of theSMIL 3.0 ScalabilityFramework. Based on these definitions, the DAISY profile is aStrictHost-Language Conformant SMIL 3.0 Profile.

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

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

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

3. The SMIL 3.0 DAISY profile DOCTYPE is:

   <!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 3.0 Daisy//EN""http://www.w3.org/2008/SMIL30/SMIL30Daisy.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 (or in the corresponding XML or RelaxNG schemas) are not allowed. If the document is 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/SMIL30Daisy.dtd

5. Documents written for the DAISY profile must declare (explicitly or implicitly via the DTD) the following values for theversion andbaseProfile attributes:

   version="3.0" baseProfile="Daisy"

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

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

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

This version of SMIL provides a definition of strict host-languageconformant SMIL 3.0 documents, which are restricted to tags and attributesfrom the SMIL 3.0 namespace. The Section "Extending/Restrictinga SMIL 3.0 Profile" provides information on using the SMIL 3.0 DAISYprofile with other namespaces, for instance, on including new tags withinSMIL 3.0 documents.

Language designers and implementors wishing to extend the DAISY profilemust consider the implications of the use of namespace extension syntax.Please consult the section onScalable Profiles for restrictionsand recommendations for best practice when extending SMIL.

19.4.2SMIL 3.0 DAISY Profile User AgentConformance

The definition of user agent conformance for SMIL 3.0 DAISY profiledocuments is given in theConformingSMIL 3.0 User Agents section of theSMIL 3.0 Scalability Framework.Conforming DAISY profile user agents must adhere completely to thissection.

19.4.3 The DAISY Profile

The DAISY profile includes the following SMIL modules:

• Structure functionality
  • Structure Module
  • Identity Module
• Metainformation functionality
  • Metainformation Module
• Timing functionality
  • BasicInlineTiming Module
  • EventTiming Module
  • MultiArcTiming Module
  • BasicTimeContainers Module
  • BasicExclTimeContainers Module
• Content Control functionality
  • BasicContentControl Module
  • RequiredContentControl Module
  • SkipContentControl Module
• State functionality
  • StateTest Module
  • UserState Module
  • StateSubmission Module
  • StateInterpolation Module
• Layout functionality
  • BasicLayout Module
  • StructureLayout Module
  • SubRegionLayout Module
• Linking functionality
  • BasicLinking Module
• Media functionality
  • BasicMedia Module
  • MediaClipping Module
  • MediaParam Module
  • MediaAccessibility Module
  • MediaDescription Module

The collection names contained in the following table define the DAISYprofile vocabulary.

In the following sections, we define the set of elements and attributesused in each of the modules included in the DAISY profile. The content modelfor each element is described. The content model of an element is adescription of elements which may appear as its direct children. The specialcontent model "EMPTY" means that a given element may not have children.

All attributes in the collectionCore aredefined for all the elements of the DAISY profile. Thexml:idattribute is used in the DAISY profileto assign a unique XML identifier to every element in a SMIL document.

XHTML Role Attribute Module

The DAISY profile includes the separate XHTML Role Attribute Module[XHTMLrole]. This provides a mechanism for allowinga semantic classification of elements via thexhtml:role attribute. The DAISY profile adds thexhtml:role attribute to theswitch,region,a,area,text,img,audio,video,ref,textstream,par,seq,andexcl elements.

<smil xmlns="http://www.w3.org/ns/SMIL" version="3.0" baseProfile="Daisy" xmlns:xhtml="http://www.w3.org/1999/xhtml" >    ...    <par xhtml:role="...">        ...    </par>    ...</smil>

19.4.4 Content Control Modules

In the DAISY profile, Content Control elements may have the followingattributes and content model :

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

Theswitch element has therestriction that the content of the switch may only be from the same set ofelements.

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

19.4.5 Layout Modules

In the DAISY profile, Layout elements may have the following attributesand content model :

The attribute collection SubregionAttributes is defined as follows:

This profile adds thelayoutelement to the content model of thehead element of theStructure Module. It also adds this element tothe content model of theswitchelement of theContent Control Modules, whentheswitch element is a child of thehead element.

19.4.6 Linking Modules

This profile includes both timing and linking modules; however, theprofile authors have decided to explicitly exclude timing attributes onlinking elements because it introduces too much complexity.

Both thea andarea elements have anhref attribute, whose value must be a validURI or XPointer[XPTR] fragmentidentifier.

In the DAISY profile, linking elements may have the following attributesand content model :

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

19.4.7 Media Object Modules

In the DAISY profile, media elements may have the following attributes andcontent model:

The attribute collection MediaDescriptionAttributes is defined asfollows:

This profile adds theref,animation,audio,img,video,text, andtextstream elements to the contentmodel of thepar,seq, andexcl elements of theTiming and Synchronization Modules. It also addsthese elements to the content model of thebody element of theStructure Module. It also adds these elementsto the content model of thea element oftheLinking Modules.

Examples

<par>    <text src="text.xml#id"/>    <audio src="audio.mp3"/></par>

<par>    <text src="text.xml#xpointer(/body/p[2])"/>    <audio src="audio.mp3"/></par>

Using param

Theparam element conveys renderinginstructions about a media type.

The DAISY profile defines the followingname values as rendering instructions fortext media:

It is expected that media objects using<paramname="daisy:use-renderer" value="..." /> exist alongside a defaultrendering of the media.

In the case where the whole document is being shown at once(<param name="daisy:display-in-context" value="true"/>),an intelligent renderer will ensure that the portion of the parent documentcontaining the specified fragment will be put in view so the fragment may beseen. It is left to the renderer to decide how much of the surroundingdocument context to include (lines above and below the target fragment).

Examples:

<smil xmlns="http://www.w3.org/ns/SMIL" version="3.0" baseProfile="Daisy" >    ...  <body>      ...      <par>          <text src="example.html#p2" region="centerTextRegion" >              <param name="daisy:display-in-context" value="true" />              <param name="daisy:css-highlight-style" value="background-color: yellow; color: black; border: solid thin green"/>          </text>      </par>      ...  </body></smil>

<smil xmlns="http://www.w3.org/ns/SMIL" version="3.0" baseProfile="Daisy" >    <head>        <paramGroup xml:id="textParams">              <param name="daisy:display-in-context" value="true" />            <param name="daisy:css-highlight-style" value="background-color: yellow; color: black; border: solid thin green"/>        </paramGroup>        <region xml:id="textWindow" width="100%" height="100%" paramGroup="textParams"/>        ...    </head>    <body>        ...        <par>            <text src="my_text.txt" region="textWindow"/>            <audio src="audio.mp3" clipBegin="0.00s" clipEnd="3.00s"/>        </par>        ...    </body></smil>

MIME Types

This profile does not require support of any particular formats. However,it is strongly recommended to support the formats listed in the SMIL 3.0Language profile'sRequired MIME Typessection.

19.4.8 Metainformation Modules

In the DAISY profile, Metainformation elements may have the followingattributes and content model :

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

The content model ofmetadata isEMPTY. Profiles that extend the DAISY profile may define the RDF (ResourceDescription Framework) schema to be used in extending the content model ofthemetadata element. The ResourceDescription Framework is defined in the W3C RDF Recommendation[RDFsyntax].

Note that because themetadataelement may appear on its own, it may be used to wrap ameta element and placed anywhere in thedocument.

The following name attribute values may be used to specify therelationship between documents:

An example using this to define the static default playback order in amulti-document SMIL presentation:

<-- chapter2.smil --><smil xmlns="http://www.w3.org/ns/SMIL" version="3.0" baseProfile="Daisy" >    <head>        <meta name="next" content="chapter3.smil"/>        <meta name="prev" content="chapter1.smil"/>        ...    </head>    <body>        ...    </body></smil>

19.4.9StateModules

TheState Modules provide a framework fordeclaratively manipulating various bits of state in a SMIL presentation. TheState Modules define semantics for thesubmission,send,state,setvalue,newvalue, anddelvalue elements and theexpr,submission,action,method,replace,target,language,ref,where,name,value attributes. The DAISY profile includesthe State functionality of theStateTest,UserState,StateSubmission, andStateInterpolationmodules.

In the DAISY profile, the State elements may have the following attributesand 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 elements. It also adds theexpr attribute to all elements within thecontent model of thebody element (i.e.excluding the body element itself).

The content model of thestateelement is declared as EMPTY. Thestate element defines the data model of theSMIL State engine using the XForms 1.0 syntax. The elements are not importedinto SMIL 3.0 and must be fully qualified.

Thesubmission attribute valueis an IDREF that refers to a submission 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 thehref,src,clipBegin,clipEnd andvalue attributes.

Expression Languageand Data Model

Support for using XPath 1.0[XPATH10] asthe expression language is required. The default value for thelanguage attribute ishttp://www.w3.org/TR/1999/REC-xpath-19991116, whichdenotes the use of XPath 1.0 as the expression language.

The content of thestate elementmust be a single XML document. If this document is empty at initializationtime a single empty<data/> root element isadded.

The following constraints are in 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.

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 the XPath Core Function Library[XPATH-CoreFunctionLibrary].
• Theset of namespace declarations is defined by thexmlns attribute on the context node.

<smil xmlns="http://www.w3.org/ns/SMIL" version="3.0" baseProfile="Daisy" >  <head>  <--This state data model could live in a separate file and be accessed by other user agent components -->  <state xmlns:f="http://www.w3.org/2002/xforms">    <f:model>      <data xmlns="">        <brailleAvailable>true</brailleAvailable>      </data>    </f:model>    <f:bind nodeset="brailleAvailable" type="xsd:boolean"/></state>    ...  </head>  <body>      <seq>          <par>            <-- This is the Braille rendering equivalent of the text contents.  A Braille display is required to show it. -->            <text src="special-notation-for-braille.xml#p4" dur="indefinite" expr="brailleAvailable">                <param name="daisy:use-renderer" value="braille"/>            </text>            <-- This is the default visual rendering of the text contents.-->            <text src="my_text.xml#p4"/>            <audio src="audio.mp3" clipBegin="0.00s" clipEnd="3.00s"/>          </par>          ...      </seq>  </body></smil>

19.4.10 Structure Modules

In the DAISY profile, Structure elements may have the following attributesand content model:

19.4.11 Timing Modules

In the DAISY profile, Timing elements may have the following attributesand content model:

The Attribute collection Timing is defined as follows:

Special values for the endattribute

This profile defines the following values for theend attribute, in addition to what is given bySMIL.

This section is normative.

The DAISY profileDocument Type Definition isdefined as a set of SMIL 3.0 modules, with the addition of the XHTML RoleAttribute Module[XHTMLrole]. All SMIL 3.0modules are integrated according to the guidelines in the W3C Note"Synchronized Multimedia Modules based upon SMIL 1.0"[SMIL-MOD], and defined within their respectivemodule sections. The XHTML Role Attribute Module's DTD Implementation[XHTMLrole-DTDImpl] is used for integratingrole into the DAISY profile DTD.

This section is informative.

This document shows a SMIL file representing part of a DAISY book whichhas been produced according to the SMIL 3.0 DAISY profile. It renderssynchronized text and audio with user-controlled playback options. It addsthe following new features, which have not been present in previous versionsof DAISY specifications:

• Semantic roles
• Control flow via SMIL State
• Use of layout
• Next and previous document references
• External text document support via param
• Text highlighting via param

Important note: the namespace "daisyskip" has not yet been officiallydefined and is included here in concept only. The concept is that thereshould be a separate section for variables whose values may be set by theuser agent.

<?xml version="1.0" encoding="iso-8859-1"?><!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 3.0 Daisy//EN" "http://www.w3.org/2008/SMIL30/SMIL30Daisy.dtd"><smil xmlns="http://www.w3.org/ns/SMIL" version="3.0" baseProfile="Daisy" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:daisyskip="http://daisy.org/smil/features/skippability" ><head>    <meta name="title" content="Smil 3 Demo"/>    <meta name="next" content="bagw0002.smil"/>    <meta name="previous" content="bagw0000.smil"/>    <paramGroup xml:id="textParams">        <param name="daisy:display–in–context" value="true" />        <param name="daisy:css–highlight–style" value="background–color: yellow; color: black; border: solid thin green"/>    </paramGroup>    <layout>        <root-layout xml:id="root-layout" width="100%" height="100%"/>        <region xml:id="text" width="100%" height="100%" paramGroup="textParams"/>    </layout>    <!--Note that, instead of the following state element, that data could go in a separate file-->    <!--such as: <state src="stateData.xml"/>-->    <state xmlns:f="http://www.w3.org/2002/xforms">        <f:model>            <!--Everything in the daisyskip namespace should be exposed by the user agent-->            <!--Variables that are for internal use only (there are none here) would be declared in the same way, but without the daisyskip: prefix-->            <f:instance>                <!--The label references a text/audio representation of "play page number announcements"-->                <daisyskip:playPageAnnouncements label="labels.smil#play_page">true</daisyskip:playPageAnnouncements>                <daisyskip:playProducerNotes label="labels.smil#play_prodnote">true</daisyskip:playProducerNotes>                              </f:instance>            <f:bind nodeset="/daisyskip:playPageAnnouncements" type="xsd:boolean"/>            <f:bind nodeset="/daisyskip:playProducerNotes" type="xsd:boolean"/>        </f:model>    </state></head><body>    <seq dur="30.076s">        <par endsync="last" xhtml:role="sectionStart" label="labels.smil#section">            <text src="ncconlydemo.html#bagw_0001" xml:id="bagw_0001" region="text"/>            <seq>                <audio src="bagw0019.mp3" clip-begin="npt=0.000s" clip-end="npt=2.035s" xml:id="qwrt_0001"/>            </seq>        </par>        <par endsync="last" xhtml:role="paragraph">            <text src="ncconlydemo.html#bagw_0001" xml:id="xbag_0001" region="text"/>            <seq>                <audio src="bagw0019.mp3" clip-begin="npt=2.035s" clip-end="npt=8.901s" xml:id="qwrt_0002"/>            </seq>        </par>        <par endsync="last" xhtml:role="ProducerNote" expr="/daisyskip:playProducerNotes">            <text src="ncconlydemo.html#bagw_0002" xml:id="bagw_0002" region="text"/>            <seq>                <audio src="bagw0019.mp3" clip-begin="npt=8.901s" clip-end="npt=19.554s" xml:id="qwrt_0003"/>                <audio src="bagw0019.mp3" clip-begin="npt=19.554s" clip-end="npt=28.774s" xml:id="qwrt_0004"/>            </seq>        </par>        <par endsync="last" xhtml:role="PageAnnouncement" expr="/daisyskip:playPageAnnouncements">            <text src="ncconlydemo.html#bagw_0003" xml:id="bagw_0003" region="text"/>            <seq>                <audio src="bagw0019.mp3" clip-begin="npt=28.774s" clip-end="npt=30.076s" xml:id="qwrt_0005"/>            </seq>        </par>        <par endsync="last" xhtml:role="Page">            <text src="ncconlydemo.html#bagw_0003" xml:id="bagw_0003" region="text"/>            <seq>                <audio src="bagw0019.mp3" clip-begin="npt=28.774s" clip-end="npt=30.076s" xml:id="qwrt_0005"/>            </seq>        </par>        <par endsync="last" xhtml:role="Page">            <text src="ncconlydemo.html#bagw_0003" xml:id="bagw_0003" region="text"/>            <seq>                <audio src="bagw0019.mp3" clip-begin="npt=28.774s" clip-end="npt=30.076s" xml:id="qwrt_0005"/>            </seq>        </par>    </seq></body></smil>