Nuance position Paper for W3C/WAP Workshop

Peter Monaco, Chief Software Architect

Steve Ehrlich, VP of Marketing

September 5-6, 2000

Short Term Requirements

Short term usage scenario

• A voice application pushes information (E.g. a list of flights) to the caller’s device one or more times during a conversation

• Achievable using WAP “push”, but requires phones that allow concurrent voice/data

• Needs to be easy for the content developer to synchronize the two applications

• Nuance has a working demo of this using the web, not WAP (www.v-commerce.com)

Longer Term Usage Scenarios

Voice handoff to WAP

• The voice application “links” or “transfers” to a WML page, putting the user in WAP mode

WAP handoff to Voice

Essentially, placing a call to a SIP URL

WAP makes use of networked speech

• Use networked ASR to enter some information; WAP interaction continues

Fully synchronized WAP and Voice

• User says “the second one” or taps

Summary of our requirements

Shorter term

• Allow voice applications to push visual content to clients (once 3G networks arrive)

• Enable a unified authoring experience for the content developer writing WML and VoiceXML

Longer term

• Agree on means for WML content to link to a SIP URL

• Agree on means for a SIP session to “transfer” the caller to a WML URL

User interface standards

• How to signal voice<->WAP transitions

• When to confirm using voice vs. WAP

How to let the user choose and switch modalities

Peter Monaco, Steve Ehrlich

monaco@nuance.com stevee@nuance.com

www.nuance.com

www.v-commerce.com