1copyright © pipebeach ab 2000. all rights reserved. scott mcglashan zw3c voice browser dialog...

5
Scott McGlashan PIPEBEACH 1 Copyright © PIPEBEACH AB 2000. All rights reserved. W3C Voice Browser Dialog Requirements and Specifications Transcoding WML into VoiceXML Language integration issues integration of WAP and VoiceXML languages

Upload: blanche-floyd

Post on 12-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 1Copyright © PIPEBEACH AB 2000. All rights reserved. Scott McGlashan zW3C Voice Browser Dialog Requirements and Specifications zTranscoding WML into VoiceXML

Scott McGlashan

PIPEBEACH

1 Copyright © PIPEBEACH AB 2000. All rights reserved.

W3C Voice Browser Dialog Requirements and Specifications

Transcoding WML into VoiceXML

Language integration issues

integration of WAP and VoiceXML languages

Page 2: 1Copyright © PIPEBEACH AB 2000. All rights reserved. Scott McGlashan zW3C Voice Browser Dialog Requirements and Specifications zTranscoding WML into VoiceXML

Scott McGlashan

PIPEBEACH

2 Copyright © PIPEBEACH AB 2000. All rights reserved.

‘Dialog’ qua DTMF/speech input, audio/speech output Requirements (draft published December 1999)

input/output, confirmation, navigation, events, variables, etc Specification (based on VoiceXML 1.0, submitted May 2000)

Grammar, Synthesis and NL Semantics ML integration change requests (corrections, generalizations, etc) modularization

VoiceXML into XHTML framework ‘BareBones’ Dialog ML: initiative, response, evaluation

model

W3C VB dialog requirements and specifications

Page 3: 1Copyright © PIPEBEACH AB 2000. All rights reserved. Scott McGlashan zW3C Voice Browser Dialog Requirements and Specifications zTranscoding WML into VoiceXML

Scott McGlashan

PIPEBEACH

3 Copyright © PIPEBEACH AB 2000. All rights reserved.

Service Provider

VoiceXMLInterpreter

XSL XSL

VXMLWMLService

DataTransformation 1 extract service data aligning interaction/design models text normalization limitations! free input, WMLScript, etc

Transformation 2 create media-specific presentation ‘decorate’ data in VoiceXML Add grammars, prompts and

interface logic

transcoding WML into VoiceXML

Page 4: 1Copyright © PIPEBEACH AB 2000. All rights reserved. Scott McGlashan zW3C Voice Browser Dialog Requirements and Specifications zTranscoding WML into VoiceXML

Scott McGlashan

PIPEBEACH

4 Copyright © PIPEBEACH AB 2000. All rights reserved.

WML transformation example: telstra.com

<info-service-data> <category name="national"> <item><title>Burke urges goverment …</title><content>... </content> </item><info-service-data>

…<xsl:template match="card"><xsl:element name="category"><xsl:attribute name="name"><xsl:value-of select="p[1]"/></xsl:attribute><xsl:apply-templates/></xsl:element></xsl:template>...

<wml> <card> <p>National News</p><select><option onpick="/Wap/...">Burke urges govt ..</option>...</select></card> </wml>

apply

in

source document (e.g. WML, etc)

data document(conforming to service DTD)

XSL Stylesheet

<wml> <card> <p>National News</p><select><option onpick="/Wap/...">Burke urges govt ..</option>...</select></card> </wml>

…<xsl:template match="card"><xsl:element name="category"><xsl:attribute name="name"><xsl:value-of select="p[1]"/></xsl:attribute><xsl:apply-templates/></xsl:element></xsl:template>...

out XSLTransformer

Page 5: 1Copyright © PIPEBEACH AB 2000. All rights reserved. Scott McGlashan zW3C Voice Browser Dialog Requirements and Specifications zTranscoding WML into VoiceXML

Scott McGlashan

PIPEBEACH

5 Copyright © PIPEBEACH AB 2000. All rights reserved.

XHTML Modularization Approach What modules are functionally distinctive in VoiceXML and

WML? What is redundant given XHTML-Basic? How do developers create services using this approach?

Seems very complex … (c.f. Requirements for good HTML, WML, SMIL, and VoiceXML sites). Tools?

But are we ready to create an integrated markup language in a single step, even if modularized? Stepwise approach, for example adding speech tags to WML (<grammar>, <dtmf>, <prompt>,

<audio>) + handling recognition input …

language integration issues