0% found this document useful (0 votes)

42 views142 pages

XHTML Voice Programmers Guide

This edition applies to release 1, modification 0 of the multimodal Programmer's Guide. IBM may publish one or more new editions of this publication in a downloadable format. To obtain the most recent edition of this publication, go to the IBM Web site.

Uploaded by

enaam1977

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

42 views142 pages

XHTML Voice Programmers Guide

Uploaded by

enaam1977

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 142

XHTML+Voice Programmers Guide

Version 1.0

Printed in the USA

Note: Before using this information and the product it supports, read the general information in Notices on page 133.

First Edition (February 2004) This edition applies to release 1, modification 0 of the Multimodal Programmers Guide and to all subsequent releases and modifications until otherwise indicated in new editions. IBM may publish one or more new editions of this publication in a downloadable format after the program is generally available. To obtain the most recent edition of this publication, go to the Web site at http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

Copyright International Business Machines Corporation 2004. All Rights Reserved. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
About this Book 1
Who should read this book? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Related programs and publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Multimodal user-interface design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Specifications and standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 How this book is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 1

Overview of XHTML+Voice

XHTML+Voice as a markup language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 What can a multimodal interaction offer? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 How XHTML+Voice works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Starting with a visual interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Adding voice markup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Combining voice and visual markup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Correlating voice and visual input/output . . . . . . . . . . . . . . . . . . . . . . . . . . 9 The architecture of X+V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Advantages of separating visual and voice . . . . . . . . . . . . . . . . . . . . . . . . 11 Coding a multimodal interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Individual elements of XHTML+Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is VoiceXML? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is XHTML? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is an event handler? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is a conformance document? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 17 17 18 18

Chapter 2

Elements and attributes of the XHTML+Voice Language

VoiceXML elements supported in X+V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Form and Form Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

XHMTL+Voice Programmers Guide

Contents

<form> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <initial> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <field> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <block> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <record> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Catching/Throwing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <catch>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <throw> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <error> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <help> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <noinput> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <nomatch> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speech Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <grammar>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <option> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <lexicon> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Executable Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <assign> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <clear> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <else> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <elseif> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <filled>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <if>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <log> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <var> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speech and Audio Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <audio> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <enumerate> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <prompt> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <reprompt> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <lexicon> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subdialog Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <param> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <return> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <subdialog> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <property> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22 24 25 28 29 30 30 31 32 33 34 35 36 36 37 38 40 40 41 41 42 43 44 44 45 46 46 49 50 53 54 56 57 57 59 61 65 65

XHTML+Voice tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 <sync> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

XHMTL+Voice Programmers Guide

Contents

<cancel> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 XML Events supported in X+V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 <listener> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Compatibility with the XHTML+Voice Specification . . . . . . . . . . . . . . . . . . XHTML+Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XHTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VoiceXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JSGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SISR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 77 77 77 79 80

Setting MIME types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 3

Adding Grammars
What is a grammar? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grammar considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using fast match grammar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grammar features available in the Multimodal Toolkit . . . . . . . . . . . . . . Creating JSGF grammars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an external JSGF grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an inline JSGF grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exceptions to the JSGF specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a JSGF grammar into another JSGF grammar . . . . . . . . . . . . .

81
81 82 83 84 84 85 86 86 87

Adding semantic interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Exceptions to the SISR specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Creating a pronunciation pool file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a pool file for an external grammar . . . . . . . . . . . . . . . . . . . . . . . Adding a pool file for an inline grammar . . . . . . . . . . . . . . . . . . . . . . . . . Pronunciation features available in the Multimodal Toolkit . . . . . . . . . . . 88 89 89 89

Importing Reusable Dialog Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Adding mixed initiative applications and form level grammars . . . . . . . . . . 90

Chapter 4

Example Applications

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Three basic examples to get started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Example 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Yes/no JSGF grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

XHMTL+Voice Programmers Guide

Contents

Beverage JSGF grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Yes/no JSGF grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 5

Multimodal Browser

123

What is a Multimodal Browser? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Browser features available in the Multimodal Toolkit . . . . . . . . . . . . . . 123 Running the Multimodal Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Opera browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Voice preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the NetFront browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Voice preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 125 125 127 127

Troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Chapter 6 Appendix A

References Notices

131 133

Copyright License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

XHMTL+Voice Programmers Guide

About This Book

This book provides information about the XHTML + Voice 1.2 language to create multimodal applications written in XHTML and VoiceXML 2.0. The resulting applications can then be deployed in a browser that has been modified to accept speech input, referred to as a multimodal browser. This chapter contains the following sections: Who should read this book? on page 1. Related programs and publications on page 1. How this book is organized on page 2. Document conventions on page 3.

Who should read this book?

The following users can benefit from this book: An application developer interested in creating XHTML + Voice applications. A content creator responsible for the creative aspects of multimodal applications. A multimodal user-interface designer interested in promoting and maintaining uniformity in the visual and voice interfaces.

Related programs and publications

Reference, design, and programming information for creating multimodal applications is available from a variety of sources, as represented by the documents listed in this section. Note: Guidelines and publications cited in this book are for your information only and do not in any manner serve as an endorsement of those materials. You alone are responsible for determining the suitability and applicability of this information to your needs.

XHMTL+Voice Programmers Guide

About This Book

Multimodal user-interface design

The user-interface guidelines presented in this book are an evolving set of recommendations based on industry research and lessons learned in the process of developing our own speech and multimodal applications. For more information, refer to speech industry literature and publications such as the following sources: Audio System for Technical Readings (ASTeR) by T. V. Raman, a Ph.D. Thesis published by Cornell University, May 1994. Auditory User InterfacesTowards The Speaking Computer by T. V. Raman, published by Kluwer Academic Publishers, August 1997. Directing the Dialog: The Art of IVR by Myra Hambleton, published in Speech Technology, Feb/Mar 2000. Handbook of Human-Computer Interaction by Thomas K Landauer, Martin Helander, and Prasad V. Prabhu, published by Elsevier Science, Amsterdam, North-Holland, June 1997. How to Build a Speech Recognition Application: A Style Guide for Telephony Dialogues (Second Edition) by Bruce Balentine, David P. Morgan, and William S. Meisel, published by Enterprise Integration Group, San Ramon, CA, 2001.

Specifications and standards

If asked, most developers will cite speed and efficiency as the main reasons for developing multimodal interfaces. Parallel input, such as the ability to both key in commands and voice them, allows users to more quickly access and respond to information delivered by their devices. In fact, multimodal systems don't just enable faster interactions, they also add value to the overall experience of interaction. Multimodal interfaces allow more room for user preference (giving users a choice of how they interact with the system) and reduce the overexertion that can result from single-modality interaction. Being able to switch between modes of interaction (using a combination of keyboard, touch screen, stylus, telephone keys, and voice) can lead to a lower incidence of error (because users can choose the mode most suited to different activities), as well as easier error recovery. And, finally, multimodal interfaces have the capacity to accommodate a wider range of tasks and environments than single-modality interfaces. While speech adds value to small mobile devices, mobility and wireless connectivity are also moving computing itself into new physical environments. In the past, checking your e-mail meant sitting down at a desktop or laptop with a modem and dialing up an e-mail service. Now, you can do it from a bench in the park or walking from your desk to your car. Bringing devices into new environments and circumstances requires new ways to access them. The ability to switch between interaction modes -eyes-free, hands-free, audio-only -- is essential to facilitating true device mobility. And, thinking it through, the need for multimodal interaction doesn't end with the device interface. Wireless networks now provide connectivity anywhere and anytime. Connecting mobile devices to the network links mobile computing to back-end data anywhere and anytime.

XHMTL + Voice Programmers Guide

How XHTML+Voice works

If the need for multimodal interaction extends to the network, then the Internet needs new technologies and standards to enable that functionality. Increasingly, Web developers are seeking ways to turn existing visually oriented Web pages into multimodal ones. And that's where X+V comes in.

How XHTML+Voice works

XHTML+Voice (X+V) is a proposed markup language for developing multimodal Web pages. X+V combines XHTML and a subset of VoiceXML. XHTML is essentially HTML 4.0 adjusted to comply with the rules of XML. It is the current standard for building Web pages. VoiceXML was one of the first XML-based languages developed in the W3C(R). It provides an easy, standardized format for building speech-based applications. Together, XHTML and VoiceXML enable Web developers to add voice input and output to traditional, graphically-based Web pages. X+V is still in the proposal phase, but it promises to deliver the feature set, flexibility, and ease of use that developers need to write one application that supports visual-only, voice-only, and multimodal interaction. The versatility of the Web and XML is reflected in the fact that X+V nicely integrates VoiceXML into the Web by marrying it with XHTML. For more information, locate the XHTML+Voice specification in Chapter 6, References on page 131.

Starting with a visual interface

Today, most Web application developers use some type of markup language to code an application's user interface. The markup language for the user interface is called the presentation layer of the application. The presentation layer defines how the user can interact with the application. It is in the presentation layer that an application is enabled for voice. HTML was once the ruling standard for coding the presentation layer, but in recent years it has been supplanted by XHTML. Building an XHTML user interface typically involves laying out graphics, input fields, text prompts, check boxes, and so on. More sophisticated user interfaces might also include some type of scripting, such as JavaScript, to enable input checking and other minor

XHMTL + Voice Programmers Guide

Overview of XHTML+Voice

computation or user-interface tasks. Figure 1 shows a portion of a flight information application UI, where you can see a variety of input fields, check boxes, and so on, combined.
Figure 1. Multimodal Flight Query example

Adding voice markup

X+V incorporates a subset of VoiceXML, a fully standardized and complete markup language for creating voice applications. VoiceXML has been developed and revised over several years by industry experts in voice programming and tested in complex real-world programming scenarios such as call centers. VoiceXML is a rich language for developing a wide range of applications, and with X+V, it is not limited to just voice applications. X+V uses the most essential elements of VoiceXML, applying them to the specific task of speech-enabling application interfaces. One advantage of basing X+V on VoiceXML is the existing, highly trained developer community, as well as the educational materials, infrastructure, tooling, and test facilities that come with a standardized language. The other advantage is the powerful framework that VoiceXML provides to developers working with X+V. Taking the simple interface in Figure 1 as an example, you see several input fields: a few check boxes, a bank of radio buttons, and some push buttons. A basic X+V implementation of this application

XHMTL + Voice Programmers Guide

How XHTML+Voice works

would speech-enable each input field so that, as you move between the fields (check boxes, and so on), you get a voice prompt as well as a visual one. This fairly simple type of speech interaction is called a directed dialog interaction. A richer implementation would allow more conversational voice input from the user, such as "I'm going from Miami to Atlanta on May 21 and returning on June 1." This type of interaction, called a mixed initiative interaction, is enabled by VoiceXML and is available in X+V.

Combining voice and visual markup

Visual markup tells a Web browser what you want the user interface to look like and how you want it to behave when the user types, points, or clicks. Similarly, voice markup tells the Web browser what you want it to do when the user speaks to it. For visual markup, the browser uses a graphics engine; for voice markup, the browser uses a speech engine. Just as visual markup specifies the visual interface items, voice markup specifies the voice interface items. Speech-enabling an application interface is a matter of first breaking the visual interface into its basic components (for example, an input field for a time of day and a check box for "a.m." or "p.m."), creating snippets of voice markup for each component, and then associating the snippets to the existing visual markup for each component. Consider the following examples: What words should the speech engine speak or synthesize? What words and phrases should the speech engine listen for? What should the browser do if the speech engine doesn't recognize a word or phrase? What will be the result of the speech engine recognizing a word or phrase that has been spoken?

Correlating voice and visual input/output

Given an application's visual markup plus a collection of voice markup snippets, you have almost everything you need to create the presentation layer of a multimodal Web application. In fact, the only thing you still need is a way to tell the browser which snippets of voice markup go with which visual elements, and (because a speech engine can only have one snippet active at a time) when to activate each snippet of voice markup.

XHMTL + Voice Programmers Guide

Overview of XHTML+Voice

Given that the Web application environment is event-driven, X+V incorporates the Document Object Model (DOM) eventing framework used in the XML Events standard. Using this framework, X+V defines the familiar event types from HTML such as "on mouse-over" or "on input focus" to create the correlation between visual and voice markup. Using XML Events provides X+V with a uniform and standards-based eventing model that enables event integration between XML languages.

The architecture of X+V

So far, you know that a multimodal Web application written in X+V consists of visual markup, a collection of snippets of voice markup for each element in the user interface, and event markup that tells the application which snippets to activate when. For visual markup, X+V uses the familiar XHTML standard. For voice markup, it uses a subset of VoiceXML defined by the VoiceXML Form construct. For associating VoiceXML with visual interface elements, X+V uses the XML Events standard. All of these are official standards for the Web as defined by the Internet Engineering Task Force (IETF) that governs Web standards. Thinking of this visually (or architecturally), you can imagine the XHTML document as a container of markup for visual elements (forms, fields, check boxes, text); a container of markup that speechenables those elements (VoiceXML fields, forms); and a container for XML Event markup that correlates voice and visual elements so that they behave as you want them to. Figure 2 is a visual representation of the X+V language structure.
Figure 2. X+Vs language architecture

XHMTL + Voice Programmers Guide

How XHTML+Voice works

Advantages of separating visual and voice

Because all the parts of X+V are XML-compliant, the voice markup can be packaged in two ways: in the same file as the XHTML or in separate files. Separating voice markup from visual markup gives you more flexibility in developing your applications. For example, you can develop the voice markup separately from the visual markup and combine the two later. Another advantage of keeping the files separate is reuse, such as the ability to reuse snippets of VoiceXML in numerous XHTML pages. In the example of our flight-reservation application, when a user makes a reservation he will be asked if he wants a one-way, round-trip, or multi-leg reservation. For each answer, the system will call up a different form. While the three forms differ with regard to the type of trip desired, each one has the same departure city. If you have separated the voice snippet for the departure city you can reuse it in each of the three different XHTML forms, or containers. The final advantage of keeping the VoiceXML separate from the XHTML is that it allows the snippets of VoiceXML to be reused in containers other than XHTML. For example, we might use a VoiceXML document as a container, as shown in Figure 3.
Figure 3. X+V language structure with multiple containers

In this case, X+V is utilizing the VoiceXML notion of documents and forms, wherein a VoiceXML document contains one or more forms. You already know that VoiceXML forms can be linked to XHTML to create multimodal applications. But such forms can also be stitched together in a

XHMTL + Voice Programmers Guide

Overview of XHTML+Voice

VoiceXML document (or container) to create voice-only applications. The end result is that you can (by reuse) create a single application that simultaneously supports multimodal browsers, GUI-only browsers, and voice-only systems such as IVRs.

Coding a multimodal interaction

You know that X+V uses XHTML for visual interaction, a subset of VoiceXML (basically the <form> tag and everything it contains) for voice interaction, and XML Events to correlate the two. The next step is to see how the different code elements come together to create a multimodal interaction. We'll

XHMTL + Voice Programmers Guide

How XHTML+Voice works

take the original example shown in Figure 1 and advance it to implement the scenario diagrammed in Figure 4. Figure 4. Multimodal scenario

In this scenario, the user is prompted both visually and by a synthesized voice. The user responds to the first directive, "Enter the departure city," with voice input: "Boston, Massachusetts." The speech engine recognizes the phrase and returns a text string. The text is displayed and the application moves the input focus to the next field, where the next interaction takes place.

XHMTL + Voice Programmers Guide

Overview of XHTML+Voice

The XHTML markup for the Departure City field is essentially a one-line Field tag:
<input type="text" id="from" name="to" size="20">

The VoiceXML markup for the Departure City field is a bit more complex, having the following elements: A voice prompt for Departure City A grammar that lists all the Airport Cities A directive telling the speech engine where to put the results Directives for what to do in case of failure (for example, if the user says "Help," the speech engine can't match the user's word or phrase to a grammar element, or the user says nothing).

Grammars are the way that application developers tell the recognition engine what words and phrases are allowable in the application. In this example, the application developer provides a grammar for all the phrases that might be spoken to fill out all the fields in the page. Other grammars are provided for the individual fields. The VoiceXML snippet that speech enables a field will use the grammar for that field but the grammar with the phrases for all the fields would be used to speech enable the whole page. This is where XML Events ties the voice and visual together. XML Events is how the application developer indicates what conditions the system activates the grammar for the page (e.g. when the page is loaded) or the grammar for the field (e.g. when the user clicks on a specific field). The sample code below shows the snippet of VoiceXML for the Departure City field.
<vxml:form id="voice_city"> <vxml:field name="field_city"> <vxml:grammar src="city.grxml" type="application/srgs+xml"/> <vxml:prompt>Please enter your departure city.</vxml:prompt> <vxml:catch event="help nomatch noinput"> For example, say either Chicago or O'Hare. </vxml:catch> <vxml:filled> <vxml:assign name="document.getElementById('from')" expr="field_city"/> </vxml:filled> </vxml:form>

The final step is to add the XML Events markup to the XHTML tag. The event markup does two things: It identifies the snippet of VoiceXML that speech-enables the XHTML tag and it identifies the

XHMTL + Voice Programmers Guide

How XHTML+Voice works

conditions or event that will activate the VoiceXML snippet. The resulting <field> tag activates the VoiceXML form named voice_city when an input focus event occurs, as shown below.
<input type="text" id="from" name="to" size="20" ev:event="inputfocus" ev:handler="#voice_city"/>

In Figure 5 we see how all of this comes together. The visual markup for the departure city field is denoted in green, the voice markup is in red, and the event that ties them together is in purple.

XHMTL + Voice Programmers Guide

Overview of XHTML+Voice

Figure 5. Implementing a multimodal scenario in X+V

Conclusion
X+V is the latest addition to the XML family of technologies for user interface development. Whereas XHTML is for developing visual interfaces, and VoiceXML focuses entirely on voice-based development, X+V is a hybrid, dedicated to developing multimodal application interfaces. X+V is particularly well suited to wireless development, where developers are faced with small visual interfaces and increasing user demand for voice input and output. As you can see from this section, X+V's foundation in existing XML standards lends it tremendous strength and versatility. Interfaces developed using X+V are portable to a wide range of applications and development environments, can be easily developed in teams, and are highly scalable over time.

XHMTL + Voice Programmers Guide

Individual elements of XHTML+Voice

Developers working with X+V can access the numerous resources that come with a well-developed standard such as XML. X+V also takes developers out of the loop of learning a new development language such as SALT, or adapting to the constraints of a more visually oriented development environment. Perhaps best of all, X+V does not require a degree in linguistics to operate; a basic knowledge of XML and related standards is sufficient to get started.

Individual elements of XHTML+Voice

The following topics provide background information of the individual elements of the X+V markup language.

What is VoiceXML?
The Voice eXtensible Markup Language (VoiceXML) is an XML-based markup language for creating distributed voice applications, just as HTML is a language for distributed visual applications. VoiceXML was defined and promoted by an industry forum, the VoiceXML Forum(TM), founded by AT&T(R), Lucent(R), Motorola(R), and IBM, and supported by approximately 500 member companies. Updates to VoiceXML are a product of the W3C voice working group. The language is designed to create audio dialogs that feature text-to-speech, pre-recorded audio, recognition of both spoken and DTMF key input, recording of spoken input, telephony, and mixed-initiative conversations. Its goal is to provide voice access and interactive voice response (such as by telephone, PDA, or desktop) to Web-based content and applications. Users interact with these Web-based voice applications by speaking or by pressing telephone keys rather than through a graphical user interface. For more information, locate the VoiceXML specification in Chapter 6, References on page 131.

What is XHTML?
The eXtensible HyperText Markup Language (XHTML) is an XML-based markup language for creating visual applications that users can access from their desktops or wireless devices. XHTML is

XHMTL + Voice Programmers Guide

Overview of XHTML+Voice

the next generation of HTML 4.01 in XML, meaning the XHTML markup language can create pages that can be read by all XML-enabled devices. If you have an existing application with HTML pages, you will have to make some simple structural changes to comply with XHTML conventions. When creating an XHTML+Voice application, your XHTML pages will remain the visual portion of the application, and at points in the interaction where voice input would help your users, you can add VoiceXML. XHTML has replaced HTML as the supported language by the World Wide Web Consortium(R) (W3C), so future-proofing your Web pages by using XHTML will not only help you with multimodal applications, but will ensure that users with all types of devices will be able to access your pages correctly. For more information, locate the XHTML specification in Chapter 6, References on page 131.

What is an event handler?

An event handler specifies an action to be performed when a particular event (such as a mouse click) takes place. In XHTML+Voice, event handlers enable interaction between XHTML and VoiceXML markup. The XML Events specification specifies the XML language with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces. For more information, locate the XML Events and Document Object Model (DOM) specification in Chapter 6, References on page 131.

What is a conformance document?

A conforming XHTML+Voice document must meet all of the following criteria: It must validate against the XML Schema found in schema listed in this document. The root element of the document must be html. The name of the default namespace on the root element must be the XHTML namespace name: http://www.w3.org/1999/xhtml

XHMTL + Voice Programmers Guide

Individual elements of XHTML+Voice

If a DOCTYPE declaration is present and includes a public identifier, the DOCTYPE declaration must reference the DTD provided in this document using its Formal Public Identifier. The system identifier may be modified appropriately. For more information, locate the XHTML+Voice specification in Chapter 6, References on page 131.

XHMTL + Voice Programmers Guide

Overview of XHTML+Voice

XHMTL + Voice Programmers Guide

Chapter 2

Elements and attributes of the XHTML+Voice Language

This chapter provides a brief introduction to basic XHTML+Voice (X+V) concepts and constructs, and describes IBMs implementation of X+V. For a complete description of the functionality of the language, refer to the XHTML+Voice 1.2 specification, which is based on the VoiceXML 2.0 specification. The elements and attributes included in this chapter are supported in the XHTML+Voice markup language, except when noted not supported. Note: The supported XHTML elements are not included in this guide. Please refer to the specification (as well as other specifications), listed in Chapter 6, References on page 131. The information in this chapter is NOT a substitute for thoroughly reading the XHTML+Voice 1.2 specification. This chapter includes the following sections: VoiceXML elements supported in X+V on page 21. XHTML+Voice tags on page 68. XML Events supported in X+V on page 74. Compatibility with the XHTML+Voice Specification on page 77. Setting MIME types on page 80.

VoiceXML elements supported in X+V

The following elements and attributes of VoiceXML are supported and in certain cases extended by the X+V language. Refer to the VoiceXML specification for further information on these and other VoiceXML elements and attributes. VoiceXML elements supported in X+V: Form and Form Items on page 22

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

Catching/Throwing Events on page 30. Speech Input on page 36. Executable Content on page 40. Speech and Audio Output on page 46. Subdialog Support on page 57. Property on page 65.

Form and Form Items

The <form> element and its children defines a speech dialog. The form items are immediate children of the <form> element that can be visited in the main loop of the VoiceXML form interpretation algorithm (FIA). The subset of form items supported in XHTML+Voice include <field>, <record>, <subdialog>, <block>, and <initial>. The latter two elements are for procedural statements and mixedinitiative processing, respectively. The other elements are for collecting user input. The <subdialog> element has its own section, below.

<form>
Description
The <form> element is the top level element of an XHTML+Voice speech dialog. It collects user input and presents information to the user using speech. A <form> element also represents a voice handler that is activated in response to either an HTML or VoiceXML event.

Syntax
<form id = "string" xmlns = "URI"> child elements </form>

XHMTL+Voice Programmers Guide

VoiceXML elements supported in X+V

type

The type of field, i.e., the name of a built-in grammar type. If the specified built-in type is not supported by the platform, an error.unsupported.builtin event is thrown. The name of the grammar slot used to populate the variable (if it is absent, it defaults to the variable name). This attribute is useful in the case where the grammar format being used has a mechanism for returning sets of slot/ value pairs and the slot names differ from the form item variable names. If this is false (the default) all active grammars are turned on while collecting this field. If this is true, then only the fields grammars are enabled: all others are temporarily disabled. Unique document identifier for <field>.

slot

VoiceXML elements supported in X+V

Speech Input
<grammar>
Description
Defines a speech recognition grammar.
<grammar root="string" src="URI" type="media type" fetchhint="safe|prefetch" fetchtimeout="time interval" maxage="time interval" maxstale="time interval"> />

Attributes
Attribute version xml:lang mode root tag-format xml:base src scope type weight Description Not supported. Not supported. Not supported. Defines the rule which acts as the root rule of the grammar. Not supported. Not supported. The URI specifying the location of the external or built-in grammar. Not supported. The media type of the grammar. application/x-jsgf for the Java Speech Grammar Format (JSGF). Not supported.

XHMTL+Voice Programmers Guide

VoiceXML elements supported in X+V

fetchhint

Defines when the browser should retrieve content from the server. prefetch indicates a file may be downloaded when the page is loaded, whereas safe indicates a file that should only be downloaded when actually needed. If not specified, a value derived from the innermost relevant fetchhint property is used. The time in seconds (s) or milliseconds (ms) for the browser to wait for content to be returned by the HTTP server before throwing an error.badfetch event. If not specified, a value derived from the innermost fetchtimeout property is used. Indicates that the document is willing to use content whose age is no greater than the specified time in seconds. The document is not willing to use stale content, unless maxstale is also provided. If not specified, a value derived from the innermost relevant maxage property, if present, is used. Indicates that the document is willing to use content that has exceeded its expiration time. If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. If not specified, a value derived from the innermost relevant maxstale property, if present, is used.

Example
The following example includes both recorded audio and TTS. The location of the audio is relative to the location of the VoiceXML document that contains the audio element. If the recorded audio cannot be fetched, the VoiceXML interpreter plays back the TTS string instead.
<?xml version="1.0"?> <vxml version="2.0"> <form> <block> <audio src="welcome.wav">Welcome to Online University</audio> </block> </form> </vxml>

The following example uses a variable and a constant string to reference an audio file. When referencing a variable, use the expr attribute instead of the src attribute.
<?xml version="1.0"?> <vxml version="2.0"> <form> <var name="path_earcons" expr="'http://audio.en-US.onine.com/ common-audio/'"/> <block> <audio expr="path_earcons + 'intellipause.wav'"/> </block> </form> </vxml>

The following example plays back TTS stored in a variable. To reference a variable containing TTS, use the value element.
<?xml version="1.0"?> <vxml version="2.0"> <form> <var name="motd" expr="'I am sorry, Dave, but I cannot do that.'"/> <block> <audio src="sorry_dave.wav"><value expr="motd"/></audio> </block> </form> </vxml>

XHMTL+Voice Programmers Guide

VoiceXML elements supported in X+V

The following example attempts to retrieve a recorded audio file from audio01.acme.net. If the fetch fails, the interpreter attempts to retrieve an alternate recording from audio02.acme.net. If that fetch fails, the interpreter renders the TTS "123".
<vxml version="2.0"> <form> <block> <audio src="http://audio01.acme.net/numbers/123.wav"> <audio src="http://audio02.acme.net/numbers/123.wav">123</audio> </audio> </block> </form> </vxml>

<enumerate>
Description
The <enumerate> element specifies a template that is applied to each choice in the order they appear in the field options. The <enumerate> element may be used within the prompt and catch elements associated with <field> elements that contain <option> elements.

Syntax
<enumerate/>

VoiceXML elements supported in X+V

Attributes
Attribute expr Description Required. An ECMAScript expression evaluated and returned as text to the containing element.

Parents
<audio>, <block>, <catch>, <enumerate>, <error>, <field>, <filled>, <help>, <if>, <initial>, <log>, <noinput>, <nomatch>, <prompt>, <record>, <subdialog>

Children
The <value> element can be used evaluate a JavaScript expression contained in an XHTML <script> element.

Example
The following example shows how the variable assignment in a CDATA section is referenced in a prompt element.
<?xml version="1.0"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:vxml="http://www.w3.org/2001/vxml" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xv="http://www.voicexml.org/2002/xhtml+voice"> <head> <title>Value Example</title> <script type="text/javascript"> var saythis = "Hello, world!"; </script>  <vxml:form id="sayHello"> <vxml:block> <vxml:value expr="saythis"/> </vxml:block> </vxml:form> </head>

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

<body> <h1>Value Example</h1> </body> </vxml>

<lexicon>
Description
The <lexicon> element is used to reference an external pronunciation lexicon document.

Syntax
<lexicon uri="URI" type="media-type"/>

Attributes
Attribute uri type Description URI location of the pronunciation lexicon document. The media type of the pronunciation lexicon document.

VoiceXML elements supported in X+V

<body ev:event="load" ev:handler="#topform"> <h1>Param example</h1> </body> </html>

The "getdriverslicense" subdialog:

<?xml version="1.0"?> <vxml version="2.0"> <form id="getdriverslicense"> <var name="birthday"/> <var name="age"/> <block> Hello, your birthday is <value expr="birthday"/> and you are <value expr="age"/> years old. <return/> </block> </form> </vxml>

<return>
Description
The <return> element completes execution of <subdialog> and returns control and data to the dialog that calling dialog.

Syntax
<return event="string"|namelist="variable1 variable2 "/>

Attributes
Attribute event Description The event to be returned to the calling dialog and thrown. Exactly one of event, eventexpr, and namelist may be specified

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

namelist

A space-separated list of variables to be returned to the calling dialog. Exactly one of event, eventexpr, and namelist may be specified (Defaults to no variables) Not supported.

eventexpr

Parents
<block>, <catch>, <error>, <filled>, <help>, <if>, <noinput>, <nomatch>

Children
None.

Remarks
XHTML+Voice allows the <return> element to run within executable content of a top level voice handler (i.e., one that is not called as a subdialog). The <return> element within executable content of a top level voice handler is used to end the execution of the voice handler. When the <return> element is specified within a top-level voice form, its namelist attribute has no meaning and is ignored. However, either the event or eventexpr attribute can be used to return a VoiceXML event to the XHTML container.

Example
Voice handler topform calls the account subdialog:
<?xml version="1.0"?> <?xml version="1.0"?> <html xmlns=http://www.w3.org/1999/xhtml xmlns:vxml=http://www.w3.org/2001/vxml xmlns:ev=http://www.w3.org/2001/xml-events xmlns:xv=http://www.w3.org/2002/xhtml+voice > <head> <vxml:form id="topform"> <vxml:subdialog name="result" src="subdialog.vxml#account"> <vxml:filled> Your account number is <vxml:value expr="result.acctnum"/>. Your phone

XHMTL+Voice Programmers Guide

VoiceXML elements supported in X+V

is <vxml:value expr="result.acctphone"/>. </vxml:filled> </vxml:subdialog> </vxml:form> </head> <body ev:event="load" ev:handler="#topform"> <h1>Return example</h1> </body> </html>

The account subdialog:

<?xml version="1.0"?> <vxml version="2.0"> <form id="account"> <field name="acctnum" type="digits"> <prompt> What is your account number? </prompt> </field> <field name="acctphone" type="phone"> <prompt> What is your home telephone number? </prompt> <filled> <return namelist="acctnum acctphone"/> </filled> </field> </form> </vxml>

<subdialog>
Description
The <subdialog> element invokes another VoiceXML form as a subdialog of the current one. The subdialog form is a reusable dialog that allows values to be returned. The subdialog runs in a new application scope with all variables initialized. Values can be passed into the subdialog using <param> child elements, and the subdialog must contain <var> variable declaration for each parameter defined by <param>. The original dialog continues execution only when the subdialog executes the <return> element. The values returned by <return> are available as properties of the <subdialog> form item variable.

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

XHTML+Voice requires the <subdialog> elements src or srcexpr attribute to reference the subdialog form explicitly with the value of the forms id attribute appended to the URI as a fragment identifier. If the subdialog form is in the same document as the form that calls the subdialog, then the src or evaluated srcexpr attribute will contain only the fragment identifier referencing the value of the subdialog forms id attribute. The namelist attribute is relevant only if the source of the <subdialog> element is a server-side script (e.g. CGI). Only one of either the src or srcexpr attribute can be used to reference a subdialog form.

Syntax
<subdialog name="string" expr="ECMAScript_Expression" cond="ECMAScript_Expression" namelist="variable1 variable2 ..." src="URI"|srcexpr="ECMAScript_Expression" fetchhint="safe" fetchtimeout="time_interval" maxage="integer" maxstale="integer"> child elements </subdialog>

XHMTL+Voice Programmers Guide

VoiceXML elements supported in X+V

Attributes
Attribute name Description The name of this subdialog, representing a variable that can be referenced anywhere within the subdialog's form. The results returned from the subdialog can be retrieved as properties of the subdialog variable: name.returnVariable. An ECMAScript expression that supplies the initial value for the form item associated with this element. If the expression evaluates to something other than null or ECMAScript undefined, the element will not be run until the form item variable is explicitly cleared. An ECMAScript expression that evaluates to true or false. If false, the element is not run. If true, the element is run. A space-separated list of variables to be submitted to the referenced subdialog (VoiceXML form). The URI of the containing document appended with the fragment identifier of the subdialog (VoiceXML form). An ECMAScript expression that evaluates to the URI of the containing document appended with the fragment identifier of the subdialog. Not supported. Not supported. Not supported. The time in seconds (s) or milliseconds (ms) for the voice browser to wait for content to be returned by the HTTP server before throwing an error.badfetch event. If not specified, a value derived from the innermost fetchtimeout property is used. Defines when the voice browser should retrieve content from the server. prefetch indicates a file may be downloaded when the page is loaded, whereas safe indicates a file that should only be downloaded when actually needed. If not specified, a value derived from the innermost relevant fetchhint property is used.

expr

cond namelist src srcexpr method enctype fetchaudio fetchtimeout

fetchhint

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

maxage

Indicates that the document is willing to use content whose age is no greater than the specified time in seconds. The document is not willing to use stale content, unless maxstale is also provided. If not specified, a value derived from the innermost relevant maxage property, if present, is used. Indicates that the document is willing to use content that has exceeded its expiration time. If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. If not specified, a value derived from the innermost relevant maxstale property, if present, is used.

maxstale

Parents
<form>

Children
<audio>, <catch>, <enumerate>, <error>, <filled>, <help>, <noinput>, <nomatch>, <param>, <prompt>, <property>, <value>

Example
Voice handler topform calls the account subdialog:
<?xml version="1.0"?> <?xml version="1.0"?> <html xmlns=http://www.w3.org/1999/xhtml xmlns:vxml=http://www.w3.org/2001/vxml xmlns:ev=http://www.w3.org/2001/xml-events xmlns:xv=http://www.w3.org/2002/xhtml+voice> <head> <vxml:form id="topform"> <vxml:subdialog name="result" src="subdialog.vxml#account"> <vxml:filled> Your account number is <vxml:value expr="result.acctnum"/>. Your phone is <vxml:value expr="result.acctphone"/>. </vxml:filled> </vxml:subdialog> </vxml:form> </head> <body ev:event="load" ev:handler="#topform">

XHMTL+Voice Programmers Guide

VoiceXML elements supported in X+V

<h1>Subdialog example</h1> </body> </html>

The account subdialog:

Property
<property>
Description
The <property> element is used to set a speech parameter for the VoiceXML form or form input item. The parameter is a value that affects platform behavior, such as the recognition process, timeouts, caching policy, etc. Please refer to the list properties supported by XHTML+Voice below.

Syntax
<property name="string" value="string"/>

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

Attribute
Attribute name value Description The property name. Required. The property value. Required.

Parents
<field> <form> <initial> <record> <subdialog>

Children
None.

Example
<?xml version="1.0"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:vxml="http://www.w3.org/2001/vxml" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xv="http://www.w3.org/2002/xhtml+voice"> <head> <vxml:form id="topform"> <vxml:property name="fetchtimeout" value="60s"/> <vxml:subdialog name="result" src="subdialog.vxml#getdriverslicense"> <vxml:param name="birthday" expr="'2000-02-10'"/> <vxml:param name="age" value="100"/> </vxml:subdialog> </vxml:form> </head> <body ev:event="load" ev:handler="#topform"> <h1>Param example</h1> </body> </html>

Tables of properties and default values

Table 1 lists the VoiceXML properties that apply to XHTML+Voice. Properties with a strike-through are not supported in Multimodal Tools.

XHMTL+Voice Programmers Guide

VoiceXML elements supported in X+V

Table 1. List of properties

audiofetchhint audiomaxage audiomaxstale bargein bargeintype completetimeout confidencelevel documentfetchhint documentmaxage documentmaxstale fetchaudio fetchaudiodelay fetchaudiominimum fetchtimeout

grammarfetchhint grammarmaxage grammarmaxstale incompletetimeout inputmodes interdigittimeout maxnbest maxspeechtimeout sensitivity speedvsaccuracy termchar termtimeout timeout universals

Table 2 lists the default property values for all platforms.

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

Table 2. Table of default property values for all platforms:

bargein timeout audiofetchhint audiomaxage audiomaxstale documentfetchhint documentmaxage documentmaxstale grammarfetchhint grammarmaxage grammarmaxstale fetchtimeout com.ibm.speech.asr.vocabtype maxnbest confidencelevel confidence shadow variable of the <field> element

true infinite prefetch infinite 0s safe infinite 0s prefetch infinite 0s 30s detailedmatch 0.2 0.2 0.5

XHTML+Voice tags
The X+V markup language offers the following elements and attributes. Refer to the XHTML+Voice specification for further information on these and other X+V elements and attributes.

XHMTL+Voice Programmers Guide

XHTML+Voice tags

<sync>
Description
The <sync> element adds support for synchronization of data entered via either speech or visual input. It binds the value property of an XHTML form input to the VoiceXML field with the given id attribute value. This means several things: 1) Speech dialog results are returned to both the VoiceXML field and the XHTML <input> element. 2) Keyboard data entered into the <input> element updates both the VoiceXML field and the XHTML <input> element. 3) Keyboard data entered into the <input> element satisfies the guard condition on the VoiceXML field. 4) For an active VoiceXML form with multiple fields, if the user gives focus to the input field, the FIA is instructed to visit the referenced VoiceXML field as the next item.

Syntax
<xv:sync xv:input="string" xv:field="URI+#+ID" xv:html-form-id="#+ID"/>

Attributes
Attribute input field html-form-id Description The name of an XHTML form input field. A URI reference to a field ID within a VoiceXML form. A reference to the ID of the XHTML form enclosing the input field.

Parents
<head>

Children
None.

Remarks
The <sync> element does not activate a voice handler and the referenced XHTML input field is not cleared if data is already there.

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

Only changes made while a VoiceXML form is active are synchronized. An existing XHTML input value does not update the synchronized VoiceXML <field> when the VoiceXML form is activated.

Standard Grammars for XHTML Controls

The <sync> element synchronizes the results between a VoiceXML <field> and an XHTML input control, or group of controls. A VoiceXML field is filled when the user's utterance matches a word or phrase in the field's grammar. The grammar, along with [Semantic Interpretation], determines how the VoiceXML field is filled and can be used to determine how a field's contents updates an arbitrary XHTML control, or group of controls. Standardizing the grammars enables a straight-forward algorithm for updating an HTML input control based on the contents of a VoiceXML <field>. The following standard grammars are used with the <sync> element for synchronizing HTML controls with the following property types: radio button and radio group, check box and check-box group, hidden, password, file, text, text area, select-one, select-multiple, submit, reset, and button. Here is an example of a grammar for a single selection list (i.e., <select>) and a radio group (i.e., multiple HTML inputs of type "radio" with the same name).
<![CDATA[ #JSGF V1.0; grammar crust; public <crust> = thin | medium | thick | chicago [style] | cheese; ]]>

Here is an example of a grammar for a multiple selection list (i.e., <select multiple="multiple">) and a checkbox group (i.e., multiple HTML inputs of type "checkbox" with the same name). Each selected item is pushed onto an array. The filled VoiceXML field is an array containing the selected items.
<![CDATA[ #JSGF V1.0; grammar meat_toppings; <meats> = bacon | chicken | ham | meatball | sausage | pepperoni; public <toppings> = <NULL> { $= new Array; } ( <meats> [and] { $.push($meats) } )+; ]]>

Here is an example of a grammar for a single radio button, check box, or button (button includes the submit and reset buttons). For the radio button or check box, the "checked" attribute is toggled according to the semantic interpretation tag contained in the filled VoiceXML field. For the button input type, a semantic interpretation value of "true" causes the button to be clicked.

XHMTL+Voice Programmers Guide

XHTML+Voice tags

<![CDATA[ #JSGF V1.0; grammar pizza_extra; public <yesno> = no {$=false} | nope {$=false} | next {$=false} | yes {$=true} | {$=true}; ]]>

The grammar for the text, text area, password, hidden, and file input types does not require any semantic interpretation. The contents of the filled VoiceXML field is set to the value attribute of these input types. Here is an example:
<![CDATA[ #JSGF V1.0; grammar one_twenty; public <onetotwenty> = 1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20; ]]>

The user should always have the option of saying "none" or "next" to decline updating the HTML control. This is supported by adding a grammar to the VoiceXML field which is outside of the standard grammar used for that field. The sample code below shows an example of a grammar, added to the grammar for a multiple selection list, that allows the user to say "none" or "skip":
<grammar> <![CDATA[ #JSGF V1.0; grammar meat_toppings; <meats> = bacon | chicken | ham public <toppings> = <NULL> { $= ( <meats> [and] { ]]> </grammar> <grammar> <![CDATA[ #JSGF V1.0; grammar no_sel; public <no_sel> = none | next | ]]> </grammar>

| meatball | sausage | pepperoni; new Array; } $.push($meats) } )+;

skip;

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

Note that the above example grammars are JSGF, but the grammars can be in any standard format supported by VoiceXML 2.0.

Example
<?xml version="1.0"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:vxml="http://www.w3.org/2001/vxml" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xv="http://www.w3.org/2002/xhtml+voice"> <head><title>Sync Example</title> <xv:sync xv:input="in1" xv:field="#result"/> <vxml:form id="topform"> <vxml:field name="result xv:id="result"> <vxml:prompt>Say a name</vxml:prompt> <vxml:grammar src="result.gram"/> </vxml:field> </vxml:form> </head> <body ev:event="load" ev:handler="#topform"> <h1>Sync example</h1> <form action="cgi/result.cgi"> Result: <input type="text name="in1"/> </form> </body> </html>

<cancel>
Description
The <cancel> element allows a document author to cancel a running speech dialog. It is a stand-alone element with no content that can be referenced as an XML Events event handler.

Syntax
<xv:cancel id="string" xv:voice-handler="URI+#+ID"/>

XHMTL+Voice Programmers Guide

XHTML+Voice tags

Attributes
Attribute id voice-handler Description Unique document identifier. A URI reference to a VoiceXML form ID.

Parents
<head>

Children
None.

Remarks
The id attribute is required. The optional voice-handler attribute references the id attribute of a voice handler form. If the voice-handler attribute is omitted, then the currently running speech dialog is canceled. If voice-handler is specified, then only the specified voice handler is canceled.

Example
<?xml version="1.0"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:vxml="http://www.w3.org/2001/vxml" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xv="http://www.w3.org/2002/xhtml+voice"> <head><title>Sync Example</title> <xv:sync xv:input="in1" xv:field="#result"/> <xv:cancel id="can1" voice-handler="#topform"/> <vxml:form id="topform"> <vxml:field name="result xv:id="result"> <vxml:prompt>Say a name</vxml:prompt> <vxml:grammar src="result.gram"/> </vxml:field> </vxml:form> </head> <body ev:event="load" ev:handler="#topform"> <h1>Sync example</h1>

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

<form action="cgi/result.cgi"> Result: <input type="text name="in1"/><br/> <input type="reset" ev:event="click" ev:handler="#can1"/> </form> </body> </html>

XML Events supported in X+V

The following elements and attributes of XML Events are supported and expanded by the X+V language. Refer to the XML Events specification for further information on these and other XML Events elements and attributes.

<listener>
Description
Element listener supports a subset of the DOM's EventListener interface. It is used to declare event listeners and register them with specific nodes in the DOM.

Syntax

XHMTL+Voice Programmers Guide

XML Events supported in X+V

Attributes
Attribute event Description (NMTOKEN) The required event attribute specifies the event type for which the listener is being registered. As specified by DOM2EVENTS, the value of the attribute should be an XML Name XML. (IDREF) The optional observer attribute specifies the id of the element with which the event listener is to be registered. If this attribute is not present, the observer is the element that the event attribute is on, or the parent of that element. (IDREF) The optional target attribute specifies the id of the target element of the event (i.e., the node that caused the event). If this attribute is present, only events that match both the event and target attributes will be processed by the associated event handler. Clearly because of the way events propagate, the target element should be a descendent node of the observer element, or the observer element itself. Use of this attribute requires care; for instance, if you specify <listener event="click" observer="para1" target="link1" handler="#clicker"/> where 'para1' is some ancestor of the following node <a id="link1" href="doc.html">The <em>draft</em> document</a> and the user happens to click on the word "draft", the <em> element, and not the <a>, will be the target, and so the handler will not be activated; to catch all mouse clicks on the <a> element and its children, use observer="link1", and no target attribute. (URI) The optional handler attribute specifies the URI reference of a resource that defines the action that should be performed if the event reaches the observer. If this attribute is not present, the handler is the element that the event attribute is on.

observer

target

handler

XHMTL+Voice Programmers Guide

Elements and attributes of the XHTML+Voice Language

phase

The optional phase attribute specifies when (during which DOM 2 event propagation phase) the listener will be activated by the desired event. capture Listener is activated during capturing phase. default Listener is activated during bubbling or target phase. The default behavior is phase="default". Note that not all events bubble, in which case with phase="default" you can only handle the event by making the event's target the observer.

propagate

The optional propagate attribute specifies whether after processing all listeners at the current node, the event is allowed to continue on its path (either in the capture or the bubble phase). stop Event propagation stops continue Event propagation continues (unless stopped by other means, such as scripting, or by another listener). The default behavior is propagate="continue".

defaultAction

The optional defaultAction attribute specifies whether after processing of all listeners for the event, the default action for the event (if any) should be performed or not. For instance, in XHTML the default action for a mouse click on an <a> element or one of its descendents is to traverse the link. cancel If the event type is cancelable, the default action is cancelled. perform The default action is performed (unless cancelled by other means, such as scripting, or by another listener). The default value is defaultAction="perform". Note that not all events are cancelable, in which case this attribute is ignored.

(ID) The optional id attribute is a document-unique identifier. The value of this identifier is often used to manipulate the element through a DOM interface.

XHMTL+Voice Programmers Guide

Compatibility with the XHTML+Voice Specification

The Multimodal Toolkit and Multimodal Browser in this release are based on the specifications listed in Chapter 6, References on page 131. However, this section describes how the X+V in this release differs from specifications.

XHTML+Voice
For details about XHTML+Voice, see the location of the XHTML+Voice 1.2 specification. In addition, this version of the Multimodal Toolkit and Multimodal Browser supports only JSGF grammars. See the exceptions for JSGF grammars below.

The "import" command must specify a URI, plus a rulename or asterisk. For example: "import <http://www.yourcompany.com/grammar.jsgf.rulename>" or "import <http://www.yourcompany.com/grammar.jsgf.*>"

SISR
The Multimodal Browser supports the SISR specification, with the exception of semantic interpretation literals (Section 3.2.2) and global variable declarations and initialization (Section 4.3).

Setting MIME types

Some servers will send only the files that they recognize. Files must be defined using MIME types. Table 4 includes valid file extensions and the corresponding MIME Content types.
Table 4. MIME types

Extension
.mxml, .jsm jsgf, .jsg, .gram, .gra

Content type
application/x-xhtml+voice+xml application/x-jsgf

The first line is the "official" X+V (XHTML + VoiceXML) document MIME type. However, in the traditional spirit of trying to render whatever the author writes, the browsers are enabling X+V for the standard html MIME type in the first line. The second line is for Java Speech Grammar Format. Grammar files are only of interest when they are pulled in to X+V as external resources. Generally, in the JSP programming model, the grammars will be inlined in the XHTML+Voice language. See the VoiceXML spec for the grammar tag.

XHMTL+Voice Programmers Guide

Chapter 3

Adding Grammars

At each point in the multimodal application where users can respond with words, the application will rely on the IBM speech recognition engine to hear, or recognize, the spoken input. The engine can detect and interpret words and phrases, as long as the programmer tells the engine what words and phrases to expect. The programmer does this by including the expected words in grammars. Every word that you want the system to recognize, even Yes and No, must be included in a grammar. Your ability to design the application with simple, tightly controlled grammars will contribute significantly to its usability and customer satisfaction. This chapter includes the following sections: What is a grammar? on page 81. Creating JSGF grammars on page 84. Adding semantic interpretation on page 87. Creating a pronunciation pool file on page 88. Importing Reusable Dialog Components on page 90. Adding mixed initiative applications and form level grammars on page 90.

Note: In addition to the grammar specifications referenced in this chapter, for more information on grammars used in VoiceXML applications, see the VoiceXML Programmers Guide (pgmguide.pdf).

What is a grammar?
A grammar is an enumeration, in compact form, of the set of utteranceswords and phrasesthat constitute the acceptable user response to a given prompt. All the words that you want the speech recognition engine to recognize when users respond to your application must be included in a grammar.

XHMTL+Voice Programmers Guide

Adding Grammars

A grammar can be as simple as a list of words, or it can be designed with more flexibility and variability so that it has the capability to recognize natural language, such as phrases and sentences. In the application, as an end-user says words or phrases, the speech recognition engines compare each word or phrase spoken by an end-user with the words and phrases in the active grammar, which can define several ways to say the same thing. The design of grammars is important to achieving accuracy. Each type of grammar in a voice application uses a particular syntax, or set of rules, to define the words and phrases that can be recognized by the engine. Multimodal browsers support the following grammar formats: Java(TM) Speech Grammar Format (JSGF) grammars Reusable Dialog Components (subdialogs included with the Multimodal Toolkit) Additional or customized pronunciations using pronunciation pool files Grammars also allow for the specification of semantic return values using the W3C Semantic Interpretation for Speech Recognition (SISR) 1.0 specification. Locate the SISR specification in Chapter 6, References on page 131.

Grammar considerations
Grammar considerations include the following: Inline vs. external grammars. You can create grammars inline or in external files (additional information is included in this chapter). An inline grammar is written within the application. For example, create an inline grammar if you want the words to be language-specific or available only at that response point. However, inline grammars are not recommended because you cannot reuse an inline grammar and, if you use the Multimodal Toolkit, the functions provided by the grammar editor are not available, such as validation, content assist, formatting, and execution in the grammar test tool. An external grammar consists of a separate file, such as a JSGF file, that is referenced from the application. For example, create an external grammar if you want the words to be language neutral or if you want to reuse the grammar in other parts of the application. Both external and inline grammars use the <vxml:grammar> tag in the VoiceXML part of the application.

XHMTL+Voice Programmers Guide

What is a grammar?

Default vs. customized pronunciations. The IBM speech recognition engine contains default pronunciations for thousands of words, so your grammar will not have to specify expected pronunciations of all words. However, default pronunciations are sometimes based on the spelling and not the common pronunciation. In this case, if testing warrants it, you can customize pronunciations and add them in pool files to your application. For more information, see Creating a pronunciation pool file on page 88. Generic vs. customized grammars. When you write your application, you can use the flexible, but generic, built-in grammars and create one or more of your own. Whether you use a built-in grammar or your own customized grammar, you must decide when each grammar should be active. The speech recognition engine uses only the active grammars to define what it listens for in the incoming speech. Minimizing complexity and size. Remember that the size and complexity of the grammar will affect performance. During testing, when you click in a field and press the Push-to-Talk button, and it takes a long time to hear the tone, it might mean that your grammar is too complex. Try simplifying the grammar and reducing the number of words.

Using fast match grammar

To improve the recognition response time on a large list grammar (greater than 500 words), you can direct the browser to compile the grammar in fast match mode by setting the property of "com.ibm.speech.asr.vocabtype" to "fastmatch" (default setting is "detailedmatch"). To do this, add the value in the <vxml:property> tag within a <vxml:field> or <vxml:form> element, as shown in the following example:
<vxml:property name="com.ibm.speech.asr.vocabtype" value="fastmatch"/>

The fast match grammar should not contain any branch or contain fewer than 500 words. (Doing so would degrade performance.) If the grammar contains a branch or contains fewer than 500 words, you should always use "detailedmatch." Only one fast match grammar should be enabled at any given point. Enabling more than one fast match grammar simultaneously will degrade performance.

XHMTL+Voice Programmers Guide

Adding Grammars

Grammar features available in the Multimodal Toolkit

The Multimodal Toolkit includes easy-to-use grammar editors that help create, edit, and validate grammars, as well as convert grammars from one format to another. In addition, the toolkit provides a Generate Sync wizard that automatically connects the grammar to the XHTML input element using the XHTML+Voice <sync> tag. For more information on these and other features, after you install the toolkit, open the online help (from the Help menu, select Help contents > Multimodal developer information > Grammar information).

Creating JSGF grammars

Java Speech Grammar Format (JSGF) is a platform-independent, vendor-independent textual representation of grammars for use in speech recognition. The JSGF format, developed by Sun Microsystems(TM), Inc., adopts the style and conventions of the Java programming language, in addition to use of traditional grammar notations. For more information, see the Java Speech Grammar Format specification. Locate the JSGF specification in Chapter 6, References on page 131.

XHMTL+Voice Programmers Guide

Creating JSGF grammars

Adding an external JSGF grammar

The default extension for a JSGF grammar file is .jsgf. Other valid extensions include .jsg, .gram, and .gra. The following sample code shows a basic JSGF grammar:
#JSGF V1.0 iso-8859-1; grammar lastnames; public <lastnames> = Nichols | Smith | Olson ;

Type the grammar source code in a text editor. Between the equal sign and the semicolon, type a complete list of all the single words that you expect users say, pressing Enter between each word. For phrases, add each word in the phrase individually, but without duplication. Do NOT use quotation marks or apostrophes. Make sure that the last entry is followed immediately by the semicolon. The following sample code shows a call to an external JSGF grammar file in the VoiceXML part of the multimodal application:
<vxml:grammar src="lastnames.jsgf">/>

XHMTL+Voice Programmers Guide

Adding Grammars

Adding an inline JSGF grammar

To add an inline JSGF grammar, make sure that the grammar is correct and valid. To do this, use the CDATA tag within the <vxml:grammar> tag, as shown in the JSGF example below:
<vxml:grammar> <![CDATA[ #JSGF V1.0; grammar lastnames; public <lastnames> = Nichols | Smith | Olson ; ]]> </vxml:grammar>

Exceptions to the JSGF specification

The XHTML+Voice language supports the JSGF specification, with the following exceptions: Do not use qualified or fully-qualified rulenames in a grammar. Rulenames cannot contain the following punctuation symbols: +-:;,=|/\()[]@#%!^&~ The "import" command must specify a URI, plus a rulename or asterisk. For example,
import <http://www.yourcompany.com/grammar.jsgf.rulename>

or
import <http://www.yourcompany.com/grammar.jsgf.*>

XHMTL+Voice Programmers Guide

Adding semantic interpretation

Importing a JSGF grammar into another JSGF grammar

To import a JSGF grammar into another JSGF grammar, add the import statement, as shown in the following example, which imports the namelist.jsgf grammar into the names.jsgf grammar.
names.jsgf #JSGF V1.0; grammar names; import <namelist.jsgf.*>; public <names> = <first> <last> | <last> <first> ;

namelist.jsgf #JSGF V1.0; grammar namelist; public <first> = Tom | Chris | Ann ; public <last> = Nichols | Smith | Olson ;

In the examples above, the import statement: import <namelist.jsfg.*>; makes the <first> and <last> public rules in namelist.jsgf visible to the names.jsgf grammar.

Adding semantic interpretation

You might want to add semantic interpretation tags to your grammar. Semantic interpretation tags can be used to translate recognition results into a format that is more useful to your application. For example, you may want to translate a recognition result into a language-independent format, or reformat dates and numbers into a standard notation.

XHMTL+Voice Programmers Guide

Adding Grammars

The Semantic Interpretation for Speech Recognition (SISR) specification describes the format of semantic interpretation tags and specifies how these tags will be used to compute a semantic interpretation result. Section 3.1.6 of the VoiceXML 2.0 spec further describes how that semantic interpretation result will be used to fill in one or more VoiceXML fields. For more information, see the Semantic Interpretation for Speech Recognition (SISR) specification. Locate the SISR specification in Chapter 6, References on page 131.

Exceptions to the SISR specification

The Multimodal Browser supports the SISR specification, with the exception of semantic interpretation literals (Section 3.2.2) and global variable declarations and initialization (Section 4.3).

Creating a pronunciation pool file

If you add words to your grammars that are not vocabulary of the speech engine, the IBM Speech Recognition engine automatically creates a default pronunciation based on the spelling of the word. If you want to customize pronunciations, such as alternative pronunciations or editing a pronunciation, you can add the modified pronunciations in a pool file (file extension .pbs), and add the pool file to the project using the <vxml:lexicon> tag within the body of the <vxml:grammar> tag. For best results, a pool file should be associated with only one JSGF grammar and should contain all the customized pronunciations for that grammar. You can create a pool file for each JSGF grammar, if needed. The following sample code shows an example of a pool file created using the IPA phonology. The example includes alternative pronunciations for a last name.:
smith smith jones davis S M IH TH S M AY TH JH OW N Z D EY V IX S

XHMTL+Voice Programmers Guide

Creating a pronunciation pool file

Adding a pool file for an external grammar

The example below shows how the lastnames.grxml grammar file calls the customized pronunciations specified in the lastnames.pbs pool file.
<vxml:grammar src="lastnames.grxml"> <vxml:lexicon uri="lastnames.pbs"/> <vxml:lexicon uri="lastnames.pbs"/> </vxml:grammar>

Adding a pool file for an inline grammar

The example below shows how to create an inline grammar and call the customized pronunciations specified in the lastnames.pbs specified in the lexicon tag.
<vxml:grammar> <![CDATA[ #JSGF V1.0; grammar lastnames; public <lastnames> = Smith | Jones | Davis ; ]]> <vxml:lexicon uri="lastnames.pbs"/> </vxml:grammar>

Pronunciation features available in the Multimodal Toolkit

In the sample code above, note the following, which will be used in all the examples to follow: The DOCTYPE describes the type of document this is, with the valid DTD for XHTML+Voice. It isn't necessary for voice processing, but is necessary for the document to be valid. The <html> tag includes the XHTML and XML Events declarations. The <head> tag includes the spoken and visual application. In this application, no recognition is included.

XHMTL+Voice Programmers Guide

Three basic examples to get started

The <vxml:form> tag is the basic element of a VoiceXML document, to which we should assign an element ID. The <vxml:block> tag includes the spoken output. In later examples, we can use this tag to perform more complex tasks with VoiceXML. The second basic example is an application that prompts for a response, recognizes a spoken response, and repeats it back to you. Note that the application will not actually run because it has no HTML. It is an example of VoiceXML, not XHTML+Voice.
<?xml version="1.0" encoding="UTF-8"?> <vxml xmlns="http://www.w3.org/2001/vxml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2001/vxml http://www.w3.org/TR/voicexml20/vxml.xsd" version="2.0">  <form> <field name="drink"> <prompt>Would you like coffee, tea, milk, or nothing?</prompt> <grammar src="drink.jsgf" type="application/x-jsgf"/> </field> <block> Thank you! Your <value expr="drink"/> order will be processed shortly! </block> </form> </vxml>

The following JSGF grammar is called with the application above.

drink.jsgf #JSGF V1.0; grammar ctm; public <ctm> = coffee | tea | milk ;

The third basic example shows the most basic XHTML+Voice document, "Hello world," and how we use XHTML+Voice to combine VoiceXML content with an HTML document, at the most basic level.

XHMTL+Voice Programmers Guide

Example Applications

Example 2

</vxml:filled> </vxml:field>

We can mix and match as many vxml:field or vxml:block elements as we want to, and they'll be visited in order. We can actually control how they get visited, but that's a more advanced topic that we'll talk about later!

<vxml:block> Hello <vxml:value expr="planet_var"/>, you sure are a wonderful planet! </vxml:block> </vxml:form> </head> <body id="page.body" ev:event="load" ev:handler="#vxml_form_prompt"> <input type="text" id="page.output_box" value="Hello?" size="18"/> <br/> </body> </html>

The purpose of this guide is not to teach VoiceXML, so we refer interested readers instead to the VoiceXML spec or to the VoiceXML Programmer's Guide. However, that said, while we used a grammar to describe our list of options in this example, we could have instead used the tag <vxml:option>. That way, instead of having a <vxml:grammar> tag, we would have had something like this:
<vxml:option value="mercury"> mercury </vxml:option> <vxml:option value="venus"> venus </vxml:option> <vxml:option value="earth"> earth </vxml:option>

XHMTL+Voice Programmers Guide

101

Example Applications

106

XHMTL+Voice Programmers Guide

Example 3

FormDone(); </script>  <ev:listener ev:observer="page.body" ev:event="vxmldone" ev:handler="#vxml_drink_form_handler" ev:propagate="stop" />  <ev:listener ev:observer="vxml.coffee" ev:event="vxmldone" ev:handler="#vxml_coffee_form_handler" ev:propagate="stop" />

XHMTL+Voice Programmers Guide

107

Example Applications

</head> <body id="page.body" ev:event="load" ev:handler="#vxml_drink_form"> <input type="hidden" id="vxml.coffee" value="" ev:event="click" ev:handler="#vxml_coffee_prompt"/> <b>Multimodal Drink Order</b><br/> <br/> Size options:<br/> <input type="radio" name="size" Small <br/> <input type="radio" name="size" Medium <br/> <input type="radio" name="size" Large <br/> <br/><br/> Drink options:<br/> <input type="radio" name="type" Soda <br/> <input type="radio" name="type" Lemonade <br/> <input type="radio" name="type" Coffee <br/> <input type="radio" name="type" Milk <br/> <br/><br/>

id="page.size.small"/> id="page.size.medium"/> id="page.size.large"/>

id="page.drink.soda"/> id="page.drink.lemonade"/> id="page.drink.coffee"/> id="page.drink.milk"/>

108

XHMTL+Voice Programmers Guide

Example 3

Yes/no JSGF grammar

This grammar includes typical responses for specifying yes or no.
#JSGF V1.0 iso-8859-1; grammar yes_no; // // This is a good example of trying to give users as // many options as possible for conveying their // meaning, while keeping the program constructs // as constrained as possible for the programmer (in // this case, we only consider a boolean result). // // It saves the programmer from having to parse the // the utterance string. // public <yes_no> = <yes> { $ = true; } | <no> { $ = false; }; <yes> = yes [please] | sure | okay | fine | yep | yup | affirmative; <no> = no | nope | no thanks | negative;

XHMTL+Voice Programmers Guide

109

Example Applications

Beverage JSGF grammar

This grammar provides valid utterances, such as "Give me a regular coffee." Note that we make use of "optional" phrases in this grammar, in order to make the grammar more natural for the average person. However, as an aside, keep in mind that when you start to make your grammars more lenient, people may start to develop higher expectations of what is valid, and get frustrated when your carefully planned grammar does not recognize what they try to respond. This example also uses "semantic interpretation." This means that we explicitly assign a value to the field/rule, rather than always assigning the utterance (which is the default behavior). This lets us have multiple words signifying the same result. Also, it is usually not a desirable thing to include the optional phrases like "I would like" in the final result, as far as the programmer is concerned. The code "$.size = $size" might seem confusing. In this context, "$" refers to the field itself, whereas $rule refers to the last rule that was recognized with that name. So what we are doing here is creating a variable called "size" that is a member of the field variable (as we would do with a C structure, for example), and assigning it to the value assigned by the most recent rule (i.e. <size>). In essence, it is saying "$.variable = $lastrule", which is confusing only because in this case the rule name is the same as the variable name.
#JSGF V1.0; grammar beverage; public <beverage> = [I would like | I want | [please] give me] [a | an] <size> { $.size = $size; } <type> { $.type = $type; } ; // // Semantic interpretation lets us assign "medium" to // the utterance "regular", giving us more flexibility. // <size> = small { $ = "small"; } | (medium | regular) { $ = "medium"; } | large { $ = "large"; } ; // // The default assignment is fine for most of these!

110

XHMTL+Voice Programmers Guide

Example 3

// <type> = coffee | milk | (soda|pop|coke) { $ = "soda"; } | lemonade ;

XHMTL+Voice Programmers Guide

111

Example Applications

Example 4
This final example illustrates how we can use mixed-initiative techniques to control the flow through a VXML form. It also shows a few different types of HTML input types that we can control with X+V, and how we do it. First of all, we need a short explanation of what we mean by "mixed-initiative". In all XHTML+Voice application, we use the Form Interpretation Algorithm (FIA) to make sure that we visit all the fields and blocks in the form in a certain order. Visually, this order is start to finish. Basically, when the VoiceXML interpreter goes through a form, it visits only those fields that have the value "undefined." Once those fields are filled with some input, then they are no longer undefined, and so they will not be visited again. What we can do is manually set the value of the fields before they would normally be visited, if we already have enough information about that particular input that we do not need to use that field anymore. In this case, we use a form-level grammar (a grammar that is embedded into the whole form, independent of field/block) to specify a grammar that includes all the grammar entries for each of the following fields. By carefully constructing this "exhaustive" grammar, we can let users say all in one utterance the various input details for our order form, and for each type of input (such as the type of bread), then we set the field for that input to some appropriate value besides undefined, so that it won't get visited again. Users do not have to specify all the options; they can say only a partial list of options, and the form will still go through and visit all the remaining fields (those that are still undefined), in effect prompting them for all the information they still might wish to include.
<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//VoiceXML Forum//DTD XHTML+Voice 1.2//EN" "http://www.voicexml.org/specs/multimodal/x+v/12/dtd/xhtml+voice12.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:vxml="http://www.w3.org/2001/vxml" xml:lang="en_US"> <head> <title>Multimodal Sandwich Order Form</title> <script type="text/javascript"> /**** ***** The functions in this script block are just some text-

112

XHMTL+Voice Programmers Guide

Example 4

***** formatting helper functions, so that we can provide ***** nice-looking visual feedback to the user. ****/ function countToppings() { var count = 0; if (document.getElementById('page.toppings.tomato') .checked) count++; if (document.getElementById('page.toppings.lettuce') .checked) count++; if (document.getElementById('page.toppings.onion') .checked) count++; return count; } function displayOrder() { alert(getOrderString()); } function getOrderString() { var order = "Your order is: A sandwich "; var total = countToppings(); var count = 0; if (total > 0) { order += "with "; if (document.getElementById('page.toppings.tomato') .checked) { count++; order += "tomatoes"; order += getComma(count, total); } if (document.getElementById('page.toppings.lettuce')

XHMTL+Voice Programmers Guide

113

Example Applications

118

XHMTL+Voice Programmers Guide

Example 4

<vxml:catch event="help nomatch noinput"> If you would like your bread toasted, say "yes". Otherwise say "no." </vxml:catch> <vxml:filled> <vxml:if cond="voice_field_toasted === true"> <vxml:assign name="document.getElementById ('page.toasted').checked" expr="true"/> </vxml:if> </vxml:filled> </vxml:field>  <vxml:field name="voice_field_bread" modal="true"> <vxml:grammar> <![CDATA[ #JSGF V1.0; grammar bread_options; public <bread_options> = [I would like | I'd like] <bread> { $ = $bread } [bread] ; <bread> = white | wheat | spicey ; ]]> </vxml:grammar> <vxml:prompt> What kind of bread would you like? You may choose white, wheat, or spicey bread. </vxml:prompt> <vxml:catch event="help nomatch noinput"> You may order white, wheat, or spicey bread. </vxml:catch> <vxml:filled> <vxml:if cond="voice_field_bread.search(/white/i) != -1"> <vxml:assign name="document.getElementById ('page.bread.white').checked" expr="true"/>

XHMTL+Voice Programmers Guide

119

Example Applications

<vxml:elseif cond="voice_field_bread.search(/wheat/i) != -1"/> <vxml:assign name="document.getElementById ('page.bread.wheat').checked" expr="true"/> <vxml:elseif cond="voice_field_bread.search(/spicey/i) != -1"/> <vxml:assign name="document.getElementById ('page.bread.spicey').checked" expr="true"/> </vxml:if> </vxml:filled> </vxml:field> <vxml:block> <vxml:value expr="getOrderString()"/>. Thank you for your order. </vxml:block> </vxml:form> </head> <body ev:event="load" ev:handler="#sandwich_order_form">  <form onsubmit="displayOrder(); return false;" action=""> <b>Multimodal Sandwich Order Form</b><br/> <br/> <b>Toppings:</b><br/>  <input type="checkbox" id="page.toppings.tomato"/> Tomato<br/>  <input type="checkbox" id="page.toppings.lettuce"/> Lettuce<br/>  <input type="checkbox" id="page.toppings.onion"/> Onion<br/> <br/> <b>Toasted?</b>

What is a Multimodal Browser?

The Multimodal Browser provides a Web browser in which you can test voice-enabled Web applications. The Multimodal Browser is based on familiar browser technology that is enhanced with extensions that include the IBM automatic speech recognition and text-to-speech technology. This allows you to view and interact with multimodal applications that you have built using XHTML+Voice. In addition to running and testing your multimodal applications with voice, the browser includes a command and control vocabulary so that you can navigate your browser using voice commands.

Browser features available in the Multimodal Toolkit

When you develop an application in the toolkit, you can open the application in the browser using the right-click option. If you make changes in the .mxml file in the X+V editor, save the changes, and then Reload the application in the browser and test your changes immediately. In the toolkit, you can set a Run configuration that will launch the application in the specified multimodal browser using the Run menu:

XHMTL+Voice Programmers Guide

123

Multimodal Browser

Using the Run menu or the Run toolbar icon, select Run... to open the Launch Configurations dialog. By default, the Multimodal Browser window opens on the Main page. By default, the open X+V file name appears, or you can use the Browse button to locate the .mxml file. Select the preferred browser from the drop-down list, and click Apply. When you click the Run button on the dialog, the file opens in the specified browser. You can launch the application anytime by selecting Run > Run History, selecting the configuration name.

Running the Multimodal Browser

To test your multimodal application, you will need a Microsoft Windows 2000 compatible, 16-bit, fullduplex sound card (with a microphone input jack) with good recording quality and a high-quality microphone. Use one of the following methods to open the Multimodal Browser: Double click the desktop icon for the Multimodal Browser, such as the Opera browser. Using the Start menu, select Programs and select the installed browser, such as Opera. Then use the File > Open menu to locate the <filename>.mxml or .html file (change the "Files of type" field to show All files). When you give focus to a voice-enabled field (click in the field with the cursor), you will hear the voice prompt for the field. 1. Open a voice-enabled file in the browser. In some applications, a voice prompt begins immediately. In other applications, you should click in each field to hear the voice prompt. 2. Press the Scroll Lock key as the Push-to-Talk (or microphone) button. Listen for the tone, and then pause a second before speaking to let the speech recognition engine engage. 3. Speak into the microphone to respond (continue to press the key for a second so that the recognition engine captures all of your response). 4. Release the key, and your response should appear as text in the field.

124

XHMTL+Voice Programmers Guide

Running the Multimodal Browser

5. If you make changes to any of the application files, such as the grammar or pool files, you should

close and re-open the browser to make sure that the new files are loaded.

Using the Opera browser

At installation, if you selected to install the Opera browser, the desktop icon was added to your desktop. You can use this icon to open and run the Multimodal Browser based on Opera technology. For full documentation on using the Opera browser, refer to the online help included with the browser. Only the Voice preferences added to the browser are described in this document.

Setting Voice preferences

The Opera browser includes a Voice preferences page in which you can change the listening mode, keyboard Push-to-Talk button, and log level. To do this, in the browser, select Tools > Preferences > Voice, and use the following settings: The Enable voice check box is selected by default. Deselect it to disable the voice features with the browser. The Voice setup area and buttons are reserved for future use. The Stop computer speech if I click mouse button check box is selected by default. When checked, you can stop voice prompts by clicking the mouse on the screen (anywhere except in a voice-enabled field). Deselect the check box to disable the canceling feature. The Key to talk drop-down list includes the following options for the keyboard key that will activate the system microphone for input: Scroll Lock (default selection) Insert The Talk Key mode drop-down box includes the following options for activating the "listening" function on the browser: In Hold key while talking mode, press and hold the button on the device while speaking, and then release the button (default selection). In Press key, then talk mode, press and release the button, and then talk. When you finish speaking, it detects silence and automatically stops listening (if there is background noise, it might take a moment for the system to detect the end of speech).

XHMTL+Voice Programmers Guide

125

Multimodal Browser

Note: When using the VoiceXML <record> tag, the Push-to-activate mode has a slightly different behavior. You press and release the button, say the response and then push and release the button to signal the end of the response. In Key not required to talk mode, the browser automatically sounds a tone when it is ready to record your response. When you finish speaking, the device detects silence and automatically stops listening (if there is background noise, it might take a moment for the device to detect the end of speech). Note: In this mode, the system will not throw a VoiceXML <noinput> event.

The Voice log level drop-down box includes the following preferences for logging: Log disabled (default selection) Verbose Info Warning Severe Check Control Opera user interface using voice to enable the command, control, and content vocabulary (deselected by default). If you enable it, you can use voice commands to activate controls in the browser, instead of the grammars in the X+V applications. The voice commands must be preceded by the Browser Name ("Browser," by default). For example, to see a list of voice commands, with the browser running and this option enabled, you can press the Scroll Lock key and say "Browser, show voice commands." Voice commands include: Back, forward, home, refresh, page up, page down, zoom in, zoom out, normal size, show bookmarks, show help, and show voice commands (or show commands). In the Browser Name field, type the command name (browser, by default) that will activate the global command and control vocabulary, instead of the grammars in the X+V applications. Refer to the Control Opera user interface using voice option, above. Other tips: If you find that the Opera browser has become your default browser, you can reset your preferred browser as the default and continue to use the Opera browser to test your multimodal projects. For example, to reset Microsoft Internet Explorer, from the IE toolbar, select Tools > Internet Options > Programs, and click the Reset Web Settings button. You can control the Memory and Disk caching. To enable or disable caching in the browser, select Tools > Preferences, and select History and cache. For example, next to Disk cache, select the

126

XHMTL+Voice Programmers Guide

Running the Multimodal Browser

XHMTL+Voice Programmers Guide

Intrusion Detection Honeypots
From Everand
Intrusion Detection Honeypots
Chris Sanders
3/5 (2)
Progress Programming Handbook
No ratings yet
Progress Programming Handbook
1,024 pages
Xtext Documentation
No ratings yet
Xtext Documentation
300 pages
Install Shield 2012 Install Script Reference Guide
No ratings yet
Install Shield 2012 Install Script Reference Guide
1,634 pages
Website Project Specification Template
100% (2)
Website Project Specification Template
6 pages
XHTML Voice Programmers Guide PDF
No ratings yet
XHTML Voice Programmers Guide PDF
142 pages
VXML Tutorial
No ratings yet
VXML Tutorial
68 pages
VXML
100% (1)
VXML
396 pages
VXMLRef 007-02542-0025 R4.21 v01
No ratings yet
VXMLRef 007-02542-0025 R4.21 v01
232 pages
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
Interactive Voice Response (IVR) Book
No ratings yet
Interactive Voice Response (IVR) Book
383 pages
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
From Everand
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
Michael Basler
No ratings yet
How to Create Pragmatic, Lightweight Languages
No ratings yet
How to Create Pragmatic, Lightweight Languages
370 pages
Java™ Speech Grammar Format Specification: Version 1.0 - October 26, 1998
No ratings yet
Java™ Speech Grammar Format Specification: Version 1.0 - October 26, 1998
37 pages
BC Prog
No ratings yet
BC Prog
339 pages
Grammar
No ratings yet
Grammar
102 pages
Create Languages
100% (1)
Create Languages
235 pages
C - Elements of Style
No ratings yet
C - Elements of Style
132 pages
Tips For Mainframe Programmers
No ratings yet
Tips For Mainframe Programmers
101 pages
Voicexml Programmer'S Guide: Websphere Voice Server For Multiplatforms
No ratings yet
Voicexml Programmer'S Guide: Websphere Voice Server For Multiplatforms
224 pages
UserGuideToConceptsOfSAPConversationalAI
No ratings yet
UserGuideToConceptsOfSAPConversationalAI
336 pages
User Guide To Concepts of Sap Conversational A I
No ratings yet
User Guide To Concepts of Sap Conversational A I
290 pages
ChatGPT for Business: Strategies for Success
From Everand
ChatGPT for Business: Strategies for Success
Matthew C. Smith
1/5 (1)
XText Documentation
No ratings yet
XText Documentation
210 pages
Pandoc Manual 20231201 1
No ratings yet
Pandoc Manual 20231201 1
164 pages
Mit Scheme Ref
No ratings yet
Mit Scheme Ref
360 pages
CDI user guide
No ratings yet
CDI user guide
105 pages
PHP Pandas
100% (1)
PHP Pandas
194 pages
Cheetah Users Guide
No ratings yet
Cheetah Users Guide
95 pages
Webassembly Specification: Release 1.0
No ratings yet
Webassembly Specification: Release 1.0
155 pages
Pandoc MANUAL
No ratings yet
Pandoc MANUAL
162 pages
Pandoc Manual
No ratings yet
Pandoc Manual
154 pages
Pandoc User'S Guide: John Macfarlane June 11, 2019
No ratings yet
Pandoc User'S Guide: John Macfarlane June 11, 2019
122 pages
Modern Perl Letter PDF
No ratings yet
Modern Perl Letter PDF
204 pages
Modern Perl A4
No ratings yet
Modern Perl A4
204 pages
COBOL Programming Course 1 Getting Started
No ratings yet
COBOL Programming Course 1 Getting Started
122 pages
COBOL New Standard PDF
No ratings yet
COBOL New Standard PDF
986 pages
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet
PHP Pandas PDF
No ratings yet
PHP Pandas PDF
194 pages
0511 Proghand PDF
No ratings yet
0511 Proghand PDF
1,024 pages
Progress
No ratings yet
Progress
1,024 pages
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
No ratings yet
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
85 pages
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
No ratings yet
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
84 pages
MEL Expressions
No ratings yet
MEL Expressions
312 pages
Starting with Windows PowerShell Cheatsheet
No ratings yet
Starting with Windows PowerShell Cheatsheet
19 pages
Net Suite Open Air So A Papi Guide
No ratings yet
Net Suite Open Air So A Papi Guide
212 pages
XMPProgrammers Guide
No ratings yet
XMPProgrammers Guide
83 pages
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
No ratings yet
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
85 pages
Mako Documentation: Release 1.0.8
No ratings yet
Mako Documentation: Release 1.0.8
106 pages
Web Assembly
No ratings yet
Web Assembly
155 pages
Manual
No ratings yet
Manual
150 pages
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
No ratings yet
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
84 pages
The Julius Book: Akinobu LEE May 17, 2010
No ratings yet
The Julius Book: Akinobu LEE May 17, 2010
67 pages
Environment and Tools
No ratings yet
Environment and Tools
1,012 pages
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
No ratings yet
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
83 pages
jsp(3)-1-10
No ratings yet
jsp(3)-1-10
10 pages
Programming Languages' Lecture Notes by Hüsnü Yenigün (CS305) (Sabancı University)
No ratings yet
Programming Languages' Lecture Notes by Hüsnü Yenigün (CS305) (Sabancı University)
259 pages
ISO TR 10303-12-1997 Scan
No ratings yet
ISO TR 10303-12-1997 Scan
128 pages
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
No ratings yet
The C Preprocessor: Richard M. Stallman, Zachary Weinberg
78 pages
Voice XML
No ratings yet
Voice XML
42 pages
Application of Definite Integrals
No ratings yet
Application of Definite Integrals
37 pages
6.2: Determining Volumes by Slicing: Volume and The Slicing Method
No ratings yet
6.2: Determining Volumes by Slicing: Volume and The Slicing Method
18 pages
A. B. C. D. E. A. B. C. D. E. F. G.: Main Menu
No ratings yet
A. B. C. D. E. A. B. C. D. E. F. G.: Main Menu
39 pages
6.2 Volumes: Applications of Integration
No ratings yet
6.2 Volumes: Applications of Integration
70 pages
Pocketsphinx: A Free, Real-Time Continuous Speech Recognition System For Hand-Held Devices
No ratings yet
Pocketsphinx: A Free, Real-Time Continuous Speech Recognition System For Hand-Held Devices
4 pages
Opnet Exercise 1
No ratings yet
Opnet Exercise 1
33 pages
The Integral: Sections 6.1, 6.2, and 6.3
No ratings yet
The Integral: Sections 6.1, 6.2, and 6.3
43 pages
OPNET 14.5 Installation
No ratings yet
OPNET 14.5 Installation
4 pages
Sensor Perf
No ratings yet
Sensor Perf
12 pages
Introduction To Speech Recognition
No ratings yet
Introduction To Speech Recognition
7 pages
Monitoring, Controlling and Configuring A Wireless Household-Electric Network Through Labview Remote Virtual Interface
No ratings yet
Monitoring, Controlling and Configuring A Wireless Household-Electric Network Through Labview Remote Virtual Interface
2 pages
TPSC Online Application Process
No ratings yet
TPSC Online Application Process
41 pages
Brocade vEPC: The First Full-Function, Cloud-Based Virtual Evolved Packet Core
No ratings yet
Brocade vEPC: The First Full-Function, Cloud-Based Virtual Evolved Packet Core
8 pages
Digital Photography Handbook
100% (1)
Digital Photography Handbook
26 pages
P - Microsoft Nintendo of America Sony Interactive Entertainment - List 4
No ratings yet
P - Microsoft Nintendo of America Sony Interactive Entertainment - List 4
7 pages
Final Galey 5. Tegar Putra Socrates Smart Detector Spectrum
No ratings yet
Final Galey 5. Tegar Putra Socrates Smart Detector Spectrum
7 pages
M.5 - STD Move If Noexcept Learn C++
No ratings yet
M.5 - STD Move If Noexcept Learn C++
7 pages
BERT Model
No ratings yet
BERT Model
69 pages
Unit 1 Introduction To Operating System
No ratings yet
Unit 1 Introduction To Operating System
29 pages
Human Machine Interaction
No ratings yet
Human Machine Interaction
27 pages
Populating A Tree View Inside AutoCAD With Sheet Set Data Using
No ratings yet
Populating A Tree View Inside AutoCAD With Sheet Set Data Using
3 pages
Art Implied and Actual Texture Dada Inspired Lesson Presentation in Pink and Grey Collage Mixed Media Style
No ratings yet
Art Implied and Actual Texture Dada Inspired Lesson Presentation in Pink and Grey Collage Mixed Media Style
14 pages
Hci 101
No ratings yet
Hci 101
11 pages
2016 A1 Assignment
No ratings yet
2016 A1 Assignment
3 pages
Biamp Case Study Peoria Riverfront Museum
No ratings yet
Biamp Case Study Peoria Riverfront Museum
3 pages
SLM Mindmap v4
No ratings yet
SLM Mindmap v4
1 page
Shoeb CV PDF
No ratings yet
Shoeb CV PDF
3 pages
Chat GPT
No ratings yet
Chat GPT
7 pages
Bscol 7
No ratings yet
Bscol 7
29 pages
Build Master Guide
No ratings yet
Build Master Guide
10 pages
Aisha R. Corobong 11 - Iris Identifying Basic Parts of The Excel Window
No ratings yet
Aisha R. Corobong 11 - Iris Identifying Basic Parts of The Excel Window
2 pages
Hyundai Logix Report
No ratings yet
Hyundai Logix Report
80 pages
FY23 EMEA TAC Security Workshop - Secure Firewall - Cheat Sheet
No ratings yet
FY23 EMEA TAC Security Workshop - Secure Firewall - Cheat Sheet
14 pages
Docker Private Registry
No ratings yet
Docker Private Registry
4 pages
Data Analyst Roadmap by Shakra Shamim
0% (1)
Data Analyst Roadmap by Shakra Shamim
13 pages
Fairbanks HR5000 QUICK SILVER
No ratings yet
Fairbanks HR5000 QUICK SILVER
56 pages
User Manual of DS-7208 and 7216 HVI-SDVR (V3.1.0)
No ratings yet
User Manual of DS-7208 and 7216 HVI-SDVR (V3.1.0)
97 pages
Assignment Build A Quiz App Using HTML, CSS, and JavaScript
No ratings yet
Assignment Build A Quiz App Using HTML, CSS, and JavaScript
6 pages
2.4.3.4 Lab - Configuring HSRP and GLBP
No ratings yet
2.4.3.4 Lab - Configuring HSRP and GLBP
9 pages