7 Authoring Mobile Browser and Voice Applications

7.5.3.1 Hello World Example

The first example (Example 7-4) shows how to display the traditional "Hello World" content on a mobile device. Figure 7-1 shows the result on mobile devices.

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleText>
   <SimpleTextItem>Hello World</SimpleTextItem>
  </SimpleText>
 </SimpleContainer>
</SimpleResult>

Figure 7-1 Hello World Content on Mobile Devices

Description of "Figure 7-1 Hello World Content on Mobile Devices"

In this example, XML is transformed into the device-specific markup language to render on the displays of a pocket PC and a telephone. This example demonstrates the power of XML; application proGrammar need not have any knowledge of the target device. Oracle Application Server Wireless renders XML into the various device screens. The following section explains the XML elements, tags and attributes used in the above example. Additionally, other tags will be discussed which can be used to display and format content on device screens or voice browsers.

7.5.3.2 DOCTYPE Declaration

XML documents authored for Oracle Application Server Wireless should have DOCTYPE declaration specifying the schema version. For backward compatibility (in the absence of DOCTYPE declaration), the style sheet for Oracle Application Server Wireless Edition 1.0 will be applied. However, if 1.0 style sheets are not available to the Oracle Application Server Wireless runtime, then Oracle Application Server Wireless 1.x style sheets will be used regardless of DOCTYPE declaration. If no 1.x style sheets are found, an error will result.

7.5.3.3 SimpleResult

SimpleResult is the root element of the Oracle Application Server Wireless XML schema. Every valid Oracle Application Server Wireless XML document must have SimpleResult as its root element. SimpleResult can contain multiple SimpleContainer blocks to allow for multi-card decks.

7.5.3.3.1 SimpleContainer

SimpleContainer is the root of all major block constructs such as Form, Menu and Text. Elements such as menu, text and form items can act as cards in the deck. DeckExample.xml (Example 7-5) demonstrates the usage of SimpleText as a placeholder for cards. Figure 7-2 shows the result on a mobile telephone. Considering the limitations of target devices and deck size restrictions on devices, judgment should be exercised in the number of cards per deck and the total content size in a single request.

Example 7-5 DeckExample.xml

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN"
"http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleText id="card1">
   <SimpleTextItem>This is Card 1
    <SimpleBreak/>
    <SimpleHref target="#card2">Go to Card2</SimpleHref>
   </SimpleTextItem>
  </SimpleText>
  <SimpleText id="card2">
   <SimpleTextItem>Welcome to Card2</SimpleTextItem>
  </SimpleText>
 </SimpleContainer>
</SimpleResult>

Figure 7-2 Cards Displayed on Mobile Telephones

Description of "Figure 7-2 Cards Displayed on Mobile Telephones"

<SimpleText>
 <SimpleTextItem>
  <SimpleAudio src="http://www.domain.com/filename.wav" deviceclass="voice">Alt text for TTS if the wave file is not found.
 </SimpleAudio>
 </SimpleTextItem>
 <SimpleTextItem deviceclass="microbrowser"> Text for small screen devices
 </SimpleTextItem>
</SimpleText>

7.5.3.4 Formatting the Display

This section describes how to customize the display using various elements.

7.5.3.4.1 SimpleBreak, SimpleStrong and SimpleEm

These elements are used for fine-tuning the display of text content on a screen. SimpleStrong displays enclosed text in a stronger representation, usually bold. SimpleEm displays the enclosed text with emphasis, usually displayed as italicized text. For voice-enabled applications, level attribute can be used to specify the level of emphasis. Permissible values for level attribute are: strong, moderate, none and reduced.

SimpleBreak creates a new line on the page on which the tag is placed. The rule attribute can be used to display a line <hr>, for HTML output. Deviceclass can be used for directive processing of small screen or voice enabled devices, or both. For voice-enabled applications, SimpleBreak inserts a pause; the msecs or size attribute enables you to control the length of the pause. Example 7-7 shows the details of the file; Figure 7-3 shows the results.

Example 7-7 FormattingExample.xml

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult bgcolor="99ff99">
 <SimpleContainer>
  <SimpleText>
   <SimpleTitle>Seach Result</SimpleTitle>
   <SimpleTextItem>
    <SimpleEm level="strong">1 Entry found</SimpleEm>
    <SimpleBreak msecs="500"/>
    <SimpleStrong>Chandra Patni</SimpleStrong>
    <SimpleBreak/>400 Oracle Pkwy
    <SimpleBreak/>Redwood Shores
    <SimpleBreak/>CA, 94065
   </SimpleTextItem>
  </SimpleText>
 </SimpleContainer>
</SimpleResult>

Figure 7-3 Results of Formatting Example

Description of "Figure 7-3 Results of Formatting Example"

7.5.3.5 Tables and Basic Formatting Example

This section shows a basic formatting example using tables.

7.5.3.5.1 SimpleTable, SimpleTableHeader, SimpleTableBody, SimpleRow and SimpleCol

SimpleTable displays a table. A table consists of a header and body which are abstracted by SimpleTableHeader and SimpleTableBody, respectively. The body of a table consists of SimpleRow and SimpleCol elements. Images can be used in tables cells. TableExample.xml (Example 7-8) provides an example of the table elements. The results are shown in Figure 7-4.

Example 7-8 TableExample.xml

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleTable >
   <SimpleTitle> My Portfolio </SimpleTitle>
   <SimpleTableHeader>
    <SimpleCol>Symbol</SimpleCol>
    <SimpleCol>Price</SimpleCol>
    <SimpleCol>Delta</SimpleCol>
   </SimpleTableHeader>
   <SimpleTableBody>
    <SimpleRow>
     <SimpleCol>ORCL</SimpleCol>
     <SimpleCol>18.32</SimpleCol>
     <SimpleCol>+0.24</SimpleCol>
    </SimpleRow>
    <SimpleRow>
     <SimpleCol>SUNW</SimpleCol>
     <SimpleCol>17.35</SimpleCol>
     <SimpleCol>+1.06</SimpleCol>
    </SimpleRow>
    <SimpleRow>
     <SimpleCol>CSCO</SimpleCol>
     <SimpleCol>20.30</SimpleCol>
     <SimpleCol>+0.24</SimpleCol>
    </SimpleRow>
    <SimpleRow>
     <SimpleCol>MSFT</SimpleCol>
     <SimpleCol>6647</SimpleCol>
     <SimpleCol>+0.28</SimpleCol>
    </SimpleRow>
   </SimpleTableBody>
  </SimpleTable>
 </SimpleContainer>
</SimpleResult>

Figure 7-4 Results of Tables and Basic Formatting Example

Description of "Figure 7-4 Results of Tables and Basic Formatting Example"

7.5.3.6 Image Adaptation Support in OracleAS Wireless XML

Application developers embed images in their OracleAS Wireless XML applications using the SimpleImage tag. Image adaptation support is provided through the addImageExtension attribute of the SimpleImage tag. The semantics of the values taken by addImageExtension and available attributes are listed in Table 7-3.

Example 1: The simplest case is one in which a single image is provided by the application and is adapted for all devices that support images based on the device profile.

<SimpleImage src="http://www.oracle.com/admin/images/oralogo.gif" alt="Oracle logo" addImageExtension="auto" />

Example 2: Multiple images are provided and the most suitable image is selected. If the size or content format needs to be adapted, the most suitable image is adapted. In this case, if the device supports GIF images, the GIF image is used for any adaptation to the size or content format if required. If the device supports WBMP, the WBMP image is used in the nested object for any adaptation to the size. If the device does not support either, the first listed image format is used.

<SimpleImage src="http://../images/oralogo" alt="Oracle logo" available="gif wbmp" addImageExtension="auto"/>

Example 3: Multiple images are provided with image adaptation turned off. The two lines below have the same meaning:

<SimpleImage src="http://../images/oralogo" alt="Oracle logo" available="gif wbmp" addImageExtension="true"/>

<SimpleImage src="http://../images/oralogo" alt="Oracle logo" available="gif wbmp" />

Example 4: Turn image adaptation off and only use the provided image, ignoring devices that do not support this format.

<SimpleImage src="http://www.oracle.com/admin/images/oralogo.gif" alt="Oracle logo" addImageExtension="false" />

7.5.4.1 SimpleAudio and SimpleSpeech

The SimpleAudio element can be used for playing audio. The file specified by the src attribute must be in 8-bit mulaw format. The SimpleSpeech element may be used to control prosody, pitch and other VoiceXML text-to-speech engine parameters. For example, the class attribute can be used to specify that the contents of SimpleSpeech should be interpreted as the say-as type phone, date, digits, literal, currency, number or time. See Example 7-9 for usage. Figure 7-5 shows the results.

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleText>
   <SimpleTextItem>
    <SimpleAudio src="welcome1.wav">Welcome to Oracle Mobile, India Development Center</SimpleAudio>
    <SimpleBreak/>
    <SimpleAudio src="welcome2.wav">You can contact us at phone number </SimpleAudio>
    <SimpleBreak/>
    <SimpleAudio src="phone.wav">
     <SimpleSpeech class="phone">91 080 552 8335</SimpleSpeech>
    </SimpleAudio>
   </SimpleTextItem>
  </SimpleText>
 </SimpleContainer>
</SimpleResult>

Figure 7-5 Results of SimpleAudio and SimpleSpeech Example

Description of "Figure 7-5 Results of SimpleAudio and SimpleSpeech Example"

7.5.4.2 Recommendation for Voice Navigation

While writing applications for Oracle Application Server Wireless, developers should consider voice navigation at design time. Well-designed voice applications tend to have different semantics than small screen devices and desktop applications. Although Oracle Application Server Wireless automatically provides an audio interface for service, the system is not intended to be a speech-controlled small-screen device browser, where speech is added as an afterthought. Application developers should develop services that have appropriate small-screen and speech interfaces in their own right, and the respective strengths of these different devices can be used to advantage.

The development path for beginners should follow this model:

1. Write a basic version of the service using exactly the same flow and markup for small-screen devices and audio interfaces.

2. Test on small-screen devices and voice telephones. If it is acceptable, you are done.

For a large class of services, particularly menu-driven services that provide information, the method works surprisingly well. If one or another interface seems clumsy, there are several things that can be done to improve it.

1. There are a number of attribute values that can be adjusted to enhance the interface for one of the device classes.

2. If that is insufficient, one can selectively include or exclude certain elements from the user interface depending on the deviceclass.

3. You can alter the user interface flow by selectively following different paths through a service, again, depending on the deviceclass.

7.5.5.1 Introduction

This section contains the details of creating Oracle Application Server Wireless XML pages containing navigation elements such as menus, hyperlinks, e-mail, help, and cover forms. The elements necessary to build a form are different from a menu as these will be the core elements needed for a wireless developer to build an effective application that simplifies user input without compromising a rich feature set across different devices.

Because voice navigation is inherently more complicated than in small screen devices, this section focuses on the fundamentals of Oracle Application Server Wireless XML for small devices, and highlights the required voice additions.

Menus allow consumers of services to simply navigate to a predefined choice and enable different URLs to be invoked for a given choice. Forms, on the other hand, typically differ from Menus in that there is one target which dictates the user's next page based on user input.

7.5.5.2 Basic Navigation

This section describes basic navigation.

7.5.5.3 SimpleMenu, SimpleMenuItem

The SimpleMenu element represents a single menu with selectable menu items defined by SimpleMenuItem elements. It is possible to add images to the top of each Menu, but avoid using large titles and images. See SimpleMenuExample.xml (Example 7-10) for an example. Figure 7-6 shows the result.

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC " = //ORACLE//DTD SimpleResult 1.1//EN"
"http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleMenu>
   <SimpleTitle>OracleMobile Services
    <SimpleImage src="
http://portal.oraclemobile.com/other/oow/oramobile"alt="Oracle Software
Powers the Internet"/>
   </SimpleTitle>
   <SimpleMenuItem target="mission.xml">OracleMobile
MissionStatement</SimpleMenuItem>
   <SimpleMenuItem target="timer.xml">Oracle Server</SimpleMenuItem>
   <SimpleMenuItem target="e-mail.xml">E-mail the authors</SimpleMenuItem>
   </SimpleMenu>
  </SimpleContainer>
 </SimpleResult>

Figure 7-6 Results of Simple Navigation Example

Description of "Figure 7-6 Results of Simple Navigation Example"

7.5.5.4 Navigating by Voice

The system reads the items of menu elements and concurrently listens for the values of the SimpleMenuItem element. If one of these values is recognized, then the target URL is fetched. If the user says nothing, the system will prompt the user with a system default noinput message. If the user says something that the system is unable to recognize, the system default nomatch message is played. However, application programmer may control such messages. Such fail-over logic is critical for making robust voice applications. Application developers should make extensive use of such features. For menus with a large number of items, voice interfaces should not read the entire list of menu items to the user. The default can be disabled by setting the autoprompt attribute of SimpleMenu to false. Instead, applications should wait for user input and should only present an options list as help if requested by user. See EnhancedSimpleMenuExample.xml (Example 7-11) for an example. Some of the tags and elements used in the application are covered later in this chapter.

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC " = //ORACLE//DTD SimpleResult 1.1//EN"
"http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
 <SimpleResult>
  <SimpleContainer>
   <SimpleMenu deviceclass="microbrowser pdabrowser pcbrowser micromessager
messenger">
   <SimpleTitle>Oracle Mobile Services
   <SimpleImage src="http://portal.oraclemobile.com/other/oow/oramobile"
alt="Oracle Software Powers the Internet"/></SimpleTitle>
   <SimpleTitle>Oracle Mobile Services</SimpleTitle>
   <SimpleMenuItem target="mission.xml">Oracle Mobile Mission Statement</SimpleMenuItem>
   <SimpleMenuItem target="timer.xml">Oracle Server</SimpleMenuItem>
   <SimpleMenuItem target="e-mail.xml">E-mail the authors</SimpleMenuItem>
  </SimpleMenu>
  <SimpleMenu deviceclass="voice" autoprompt="false">
   <SimpleTitle>
    <SimpleAudio src="title.wav">oracle mobile services
    </SimpleAudio>
   </SimpleTitle>
   <SimpleMenuItem target="mission.xml">Oracle Mobile Mission Statement
    <SimpleGrammar><grammar root="ms">
    <rule id="ms">
    <item repeat="0-1">Oracle</item> mission statement
    </rule>
    </grammar>
    </SimpleGrammar>
   </SimpleMenuItem>
   <SimpleMenuItem target="timer.xml">Oracle Server
    <SimpleGrammar><grammar root="server">
    <rule id="server">
    <item repeat="0-1">Oracle</item> server
    </rule>
    </grammar>
    </SimpleGrammar>
   </SimpleMenuItem>
   <SimpleMenuItem target="e-mail.xml">E-mail the authors
    <SimpleGrammar><grammar root="e-mail">
    <ruleid="e-mail">
    <one-of>
    <item>e-mail the authors</item>
    <item>e-mail</item>
    <item>e-mail authors</item>
    </one-of>
    </rule>
    </grammar>
    </SimpleGrammar>
   </SimpleMenuItem>
   <SimpleCatch type="noinput">
    <SimpleAudio src="menuOptions.wav">Please speak up. You may also say help.
    </SimpleAudio>
   </SimpleCatch>
   <SimpleCatch type="nomatch">
    <SimpleAudio src="nomatch.wav">I'm sorry, I did not understand you. Please say that again or say help.</SimpleAudio>
   </SimpleCatch type="help">
    <SimpleAudio src="menuHelp.wav"> Help. Oracle Mobile. You may say mission statement, oracle server or e-mail the authors.
    </SimpleAudio>
  </SimpleMenu>
 </SimpleContainer>
</SimpleResult>

The output of this application on small screen devices is the same as shown above, while a typical voice session may be as follows:

System: "Oracle Mobile Services."

User: "Help."

System: "Help. Oracle Mobile. You may say mission statement, oracle server or e-mail the authors."

User: "I am going to trick you."

System: "I'm sorry, I did not understand you. Please say that again or say help."

User: "E-mail authors."

Voice gateways provide a text-to-speech (TTS) engine that reads out SimpleTitles, SimpleTextItems, and others. For the TTS to sound intelligible, proper spacing and punctuation are required.

SimpleFormOptions and SimpleMenuItems should not have text punctuation unless the deviceclass has been set to a value other than voice. This is because the text in these tags is used to produce speech recognition grammars, and many voice gateways cannot process such characters in speech grammars. If a developer wishes to avoid using the synthesized message, he may specify a prerecorded audio file to be played. The location of the audio file can be specified through the <SimpleAudio> tag. End user experience of TTS is often considered unpleasant, so as much as possible, prerecorded human sounds should be used instead of TTS.

7.5.6.1 SimpleAction

SimpleActionprovides the ability to define a submit action that navigates users to a new context. Mobile devices can associate a submit action to a number of input methods of the device, such as pressing a key on a WAP device or speaking a command on a voice-enabled device. SimpleAction can also be used for navigation to different pages and different cards within a deck, and overriding default behavior on voice browsers. For mobile phones, the main usage would be to override the buttons (left and right) on a wireless phone and PDAs to provide a similar navigation functionality as SimpleHref.

Like many programming languages, SimpleAction, for a given type, conforms to scoping rules. For example, if SimpleAction is defined as a child of SimpleMenu and also as a child of the enclosing SimpleContainer for a given type, the SimpleAction tag within the SimpleMenu overrides the SimpleAction of the SimpleContainer. If the value for type attribute is different, then the two SimpleActions will be active within the context. The behavior of SimpleAction is unspecified if two elements are defined with the same type and same deviceclass values in the same context. See the following example for usage.

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer id="message">
 <SimpleTimer target="#employeePortal" timer="30"/>
  <SimpleText>
   <SimpleTextItem> There will be ice cream bars in every lobby at Headquarters to promote the use of the new employee wireless portal.
   </SimpleTextItem>
  </SimpleText>
 </SimpleContainer>
 <SimpleContainer>
  <SimpleText id="employeePortal">
  <SimpleTitle>
   <SimpleImage valign="top" src= http://portal.oraclemobile.com/other/oow/oraclemobile alt="oraclemobile icon"/>
  </SimpleTitle>
   <SimpleTextItem>Welcome to <SimpleEm>OracleMobile</SimpleEm> Employee Portal <SimpleBreak/>
   </SimpleTextItem>
   <SimpleAction type="secondary" label="Support" target="phone.xml"/>
   <SimpleHref label="PORTAL" id="portal" target="form.xml"> enterPortal
   </SimpleHref>
  </SimpleText>
 </SimpleContainer>
</SimpleResult>

7.5.6.2 Enhancing with Voice

This section describes customizing your applications using voice.

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleCache ttl="0"/>
 <SimpleContainer>
  <SimpleMenu wrapmode="nowrap" autoprompt="false">
   <SimpleTitle>Voice demo</SimpleTitle>
   <SimpleMenuItem target="deposit.jsp">Deposit
    <SimpleDTMF> <grammar root="one">
    <rule id="one">1</rule>
    </grammar>
    </SimpleDTMF>
   </SimpleMenuItem>
   <SimpleMenuItem target="HelloWorld.jsp">Withdraw
    <SimpleDTMF> <grammar root="two">
    <rule id="two">2</rule>
    </grammar>
    </SimpleDTMF>
   </SimpleMenuItem>
   <SimpleCatch type="cancel">
   <SimpleGo target="cancel.jsp/>
   </SimpleCatch>
   <SimpleCatch type="help">
    <SimpleAudio src="help2.wav">Help. For deposit, you may say deposit or press 1. For withdraw, you 
    may say withdraw or press 2.</SimpleAudio>
   </SimpleCatch>
   <SimpleCatch type="help" count="2">
    <SimpleAudio src="help.wav">Help. For deposit, you may say deposit or press 1. For withdraw, you 
    may say withdraw or press 2. You may also say cancel to return to account menu.</SimpleAudio>
   </SimpleCatch>
  </SimpleMenu>
 </SimpleContainer>
</SimpleResult>

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleMenu deviceclass="voice">
   <SimpleTitle src="title.wav">Please select a freeway</SimpleTitle>
   <SimpleMenuItem target="./traffic.jsp?index=5">I 5
    <SimpleGrammar> <grammar route="i5">
    <rule id="i5">
    <one-of>
    <item>i five</item>
    <item>interstate five</item>
    <item>five</item>
    <item>route five</item>
    <item>san diego</item>
    </one-of>
    </rule>
    </grammar>
    </SimpleGrammar>
   </SimpleMenuItem>
   <SimpleMenuItem target="./traffic.jsp?index=8 ">I 8 
    <SimpleGrammar><grammar root="i8">
    <rule id="i8">
    <one-of>
    <item>i eight</item>
    <item>interstate eight</item>
    <item>eight</item>
    <item>route eight</item>
    <item>alvarado freeway</item>
    <item>mission valley freeway</item>
    <item>ocean beach freeway</item>
    </one-of>
    </rule>
    </grammar>
    </SimpleGrammar>
   </SimpleMenuItem>
   <SimpleMenuItem target="./traffic.jsp?index=15 ">I 15
    <SimpleGrammar> <grammar root="i15">
    <rule id="i15">
    <one-of>
    <item>i fifteen</item>
    <item>fifteen</item>
    <item>nterstate fifteen</item>
    <item>escondido freeway</item>
    <item>escondido</item>
    </one-of>
    </rule>
    </grammar>
    </SimpleGrammar>
   </SimpleMenuItem>
   <SimpleMenuItem target="./traffic.jsp?index=805 ">I 805
    <SimpleGrammar> <grammar root="i805">
   <rule id="i805">
   <one-of>
   <item>i eight zero five</item>
   <item>i eight hundred five</item>
   <item>eight zero five</item>
   <item>eight hundred five</item>
   <item>interstate eight zero five</item>
   <item>interstate eight hundred five</item>
   <item>route eight zero five</item>
   <item>route eight hundred five</item>
   </one-of>
   </rule>
   </grammar>
    </SimpleGrammar>
   </SimpleMenuItem>
  </SimpleMenu>
 </SimpleContainer>
</SimpleResult>

<SimpleResult>
  <SimpleContainer>
    <SimpleForm method="post"
  enctype="application/x-www-form-urlencoded" target="recordaudio.jsp">
      <SimpleFormItem type="audio" enctype="audio/wav"
> name="recorded_audio_msg" beep="true" dtmfterm="true">
        Say something to record after the beep.
      </SimpleFormItem>
    </SimpleForm>
  </SimpleContainer>
</SimpleResult>

// WRITE THE AUDIO CONTENT TO A FILE
// AND PLAY BACK THE CONTENTS
String myrecording = request.getParameter("record_audio_msg");
String wavdirectory = "path/testharness/audio/"; // ABSOLUTE PATH OF WHERE TO STORE THE AUDIO
String myWaveFile  = wavdirectory + "test.wav";
File myWFile = new File(myWaveFile);
String result = "";
try {
  byte[] myWaveBytes = myrecording.getBytes();
  FileOutputStream myFileOutput = new FileOutputStream(myWaveFile);
  myFileOutput.write(myWaveBytes);
  myFileOutput.close();
  result = "<SimpleAudio
src=\"http://iaswvoice.oracle.com/testharness/audio/" + fileName +
"test.wav\"/>"; // THIS IS TO CHECK TO MAKE SURE THE FILE WAS RECORDED
} catch (IOException e) {
  result = "Error No Audio File Created";
}
  %>
Value: <%=result%> <!-- PLAY THE AUDIO FILE FOR THE USER, SEE ABOVE RESULT STRING -->

7.5.7.1 Introduction

Forms provide the basic building blocks for user interactions. Forms for phones and PDAs are fairly similar, except in form factor. Like HTML forms, forms in mobile devices are used for passing name-value parameters to the server. Multiple form items can be laid out on the device screen, if supported. Therefore, a user may populate a form item in an arbitrary order. Certain format restrictions can be specified on a form item to ensure the type, safety and validity of form fields. For example, it is possible to specify a restriction of five digits for US postal codes. However, most of the validation should occur on the server side. This constraint is due to the limited resources on the devices. On a voice browser, every thing must be processed by the voice gateway, which enables rich validation and exception handling at the markup language level.

7.5.7.2 Basic User Interaction

This section describes SimpleForm and SimpleFormItem.

7.5.7.2.2 SimpleFormItem

SimpleFormItem is the equivalent of a text field, text area, password field and hidden field for desktop browsers. The type of item may be specified using the display mode attribute. It may take text field, text area, noecho or hidden. SimpleFormItem can be used to obtain input from a user. This element presents a prompt and waits for input from the user. The content of this element, which is in a character format that can be parsed, specifies default values for the form item. For example, a login screen and guest book screen may appear as in Example 7-17. Figure 7-9 shows the results.

Example 7-17 FormExample.xml

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleForm target="login.jsp" method="post">
   <SimpleFormItem name="userName">User Name:</SimpleFormItem>
   <SimpleFormItem name="password" displaymode="noecho">Password:</SimpleFormItem>
  </SimpleForm>
 </SimpleContainer>
</SimpleResult>

Figure 7-9 Results of FormExample.xml Example

Description of "Figure 7-9 Results of FormExample.xml Example"

Example 7-18 shows GuestBook.xml. Figure 7-10 shows the results of GuestBook.xml.

Example 7-18 GuestBook.xml

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleForm target="sendMail.jsp" method="post">
   <SimpleTitle>Thanks for signing my guestbook.</SimpleTitle>
   <SimpleFormItem name="Name">Name:</SimpleFormItem>
   <SimpleFormItem name="message" displaymode="textarea">Message:</SimpleFormItem>
  </SimpleForm>
 </SimpleContainer>
</SimpleResult>

Figure 7-10 Results of GuestBook.xml Example

Description of "Figure 7-10 Results of GuestBook.xml Example"

7.5.7.3 Complete User Forms

This section describes user forms.

7.5.7.3.1 SimpleFormSelect, SimpleFormOption, and SimpleOptGroup

These elements display a selected option list. It can display drop down list, check box and radio button, using the display mode attribute. Check boxes or option lists may allow single selection or multiple selections using the multiple attribute. The items to be displayed are abstracted by the SimpleFormOption element. SimpleOptGroup groups SimpleFormOption elements into a hierarchy. It is useful for small screen devices, where long list of options cannot be esthetically presented. The content of SimpleFormOption element is character data that can be parsed, which specifies default values for the form item. See Example 7-19 for usage. Figure 7-11 shows the result.

Example 7-19 Profile.xml

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleForm name="employeeinfo" target="process.jsp">
   <SimpleTitle>Your Profile</SimpleTitle>
   <SimpleFormItem name="homepage" default="http://">Homepage</SimpleFormItem>
   <SimpleFormSelect name="skills" displaymode="checkbox" multiple="true">
    <SimpleTitle>Skills</SimpleTitle>
    <SimpleFormOption value="Java">Java</SimpleFormOption>
    <SimpleFormOption value="xml">XML</SimpleFormOption>
    <SimpleFormOption value="sql">SQL</SimpleFormOption>
   </SimpleFormSelect>
   <SimpleFormSelect name="nerd" displaymode="checkbox">
    <SimpleTitle>Addicted to Java?</SimpleTitle>
    <SimpleFormOption value="yes">Yes</SimpleFormOption>
    <SimpleFormOption value="no">No</SimpleFormOption>
   </SimpleFormSelect>
   <SimpleFormSelect name="location" displaymode="list">
    <SimpleTitle>Location</SimpleTitle>
    <SimpleFormOption value="Redwood Shores_CA">HQ Redwood Shores,CA</SimpleFormOption>
    <SimpleFormOption value="Nashua_NH">NEDC Nashua, NH</SimpleFormOption>
    <SimpleFormOption value="SanFrancisco_CA">SanFrancisco, CA</SimpleFormOption>
    <SimpleFormOption value="NewYork,NY">NewYork, NY</SimpleFormOption>
   </SimpleFormSelect>
   </SimpleForm>
  </SimpleContainer>
</SimpleResult>

Figure 7-11 Results of Profile.xml Example

Description of "Figure 7-11 Results of Profile.xml Example"

7.5.7.4 Enhancing Voice

This section describes customizing voice.

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleForm id="Starting" target="test2a.jsp">
   <SimpleFormItem name="addrInput" slot="value">
    simple grammar test, please say oracle or san mateo
   <SimpleGrammar> <grammar root="addr">
   <rule id="addr">
   <one-of>
   <item>Oracle <tag>value = "bridge"</tag></item>
   <item>San Mateo <tag>value = "foster city"</tag></item>
   </one-of>
   </rule>
   </grammar>
   </SimpleGrammar>
   </SimpleFormItem>
   <SimpleFormItem name="zipInput" slot="zip">
    <SimpleDTMF> <grammar root="n5">
    <rule id="n5"> 95 <tag>zip = "232"</tag> </rule>
    </grammar>
    </SimpleDTMF>
     Simple DTMF test, please press 95
   </SimpleFormItem>
  </SimpleForm>
 </SimpleContainer>
</SimpleResult>

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleForm target="guess.jsp">
   <SimpleFormItem name="guess">
    <SimpleTitle>
    I am thinking of a number between 1 and 100.
    What is your first guess?
    </SimpleTitle>
   </SimpleFormItem>
  </SimpleForm>
 </SimpleContainer>
</SimpleResult>

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleForm target="guess.jsp">
   <SimpleFormItem name="guess" type="number">
    <SimpleTitle>
    I am thinking of a number between 1 and 100.
    What is your first guess?
    </SimpleTitle>
   </SimpleFormItem>
  </SimpleForm>
 </SimpleContainer>
</SimpleResult>

<?xml version = "1.0" encoding = "UTF-8" standalone="yes" ?>
<!DOCTYPE SimpleResult PUBLIC "-//ORACLE//DTD SimpleResult 1.1//EN" "http://xmlns.oracle.com/ias/dtds/SimpleResult_1_1_0.dtd">
<SimpleResult>
 <SimpleContainer>
  <SimpleForm target="tipcalc.jsp">
   <SimpleFormItem name="howmuch" type="currency">How much is the bill?
   </SimpleFormItem>
   <SimpleFormItem name="howmany" format="N*" type="number">
   How many are in your party?
    <SimpleCatch type="cancel">Canceling.
<SimpleClear>
	    <SimpleName name="howmuch"/>
	</SimpleClear>    
</SimpleCatch>
   </SimpleFormItem>
   <SimpleFormSelect name="howbig" deviceclass="microbrowser pdabrowser pcbrowser micromessenger messenger">
    <SimpleTitle>How big do you want your tip to be?</SimpleTitle>
    <SimpleFormOption value="10">small (10%)</SimpleFormOption>
    <SimpleFormOption value="15">medium (15%)</SimpleFormOption>
    <SimpleFormOption value="20">large (20%)</SimpleFormOption>
   </SimpleFormSelect>
   <SimpleFormSelect name="howbig" deviceclass="voice" autoprompt="false">
    <SimpleTitle>
     How big do you want your tip to be?
     For 'ten percent' say 'small',
     for 'fifteen percent' say 'medium', 
     for 'twenty percent' say 'large'.
    </SimpleTitle>
    <SimpleFormOption value="10">small</SimpleFormOption>
    <SimpleFormOption value="15">medium</SimpleFormOption> 
    <SimpleFormOption value="20">large</SimpleFormOption>
    <SimpleCatch type="nomatch">Please say that again</SimpleCatch>
    <SimpleCatch type="cancel">Canceling.
<SimpleClear>
	    <SimpleName name="howmuch"/>
	    <SimpleName name="howmany"/>
	</SimpleClear>
    </SimpleCatch>
   </SimpleFormSelect> 
  </SimpleForm>
 </SimpleContainer>
</SimpleResult>

7.5.7.5 Working with Signature Capture Form Control

Some browsers (such as the Spectrum24® WebClient for Palm Computing Platform) support the ability to capture signatures. Applications developed using OracleAS Wireless XML can generate the target markup required to support signature capture. In this release, the following browsers are supported for signature capture:

• Symbol Spectrum24® WebClient for Palm Computing Platform Version 2.8-10 for Palm OS 4.1

• Microsoft Pocket Internet Explorer 4.1 on Microsoft Pocket PC

• Microsoft Pocket Internet Explorer on Microsoft CE3 or later

On supported Microsoft Pocket PC and Windows Mobile platforms, the Oracle Signature Capture Plug-in for Pocket Internet Explorer must be installed. The Oracle Signature Capture Plug-in is available for download from Oracle MetaLink at http://metalink.oracle.com. Go to the Downloads area to download the software and instructions. Be sure to read the readme file included int he download; it includes important information about the Plug-in, and detailed instructions on how to properly install it. If you need any further assistance, contact Oracle Support.

7.5.7.5.1 SimpleFormItem type=signature

The OracleAS Wireless XML tag <SimpleFormItem> has an additional type (signature) to support signature capture on target browsers that have this capability. Example 7-24 code segment illustrates how to use signature capture form control in an application developed using OracleAS Wireless XML. Figure 7-12 shows the result.

Example 7-24 Signature capture form control

<SimpleResult>
<SimpleContainer>
 
    <SimpleForm method="post" target="processForm.jsp" layout="linear">
      <SimpleTitle>Signature</SimpleTitle>
 
      <SimpleFormItem name="Text" size="6" type="text">
          <SimpleTitle>Description:<SimpleBreak/></SimpleTitle>
      </SimpleFormItem>    
 
      <SimpleFormItem name="capture" type="signature">
        <SimpleTitle>Signature: :<SimpleBreak/></SimpleTitle>
      </SimpleFormItem>    
      <SimpleAction name="submit" type="submit" value="submit"/>
    </SimpleForm>
 
  </SimpleContainer>
</SimpleResult>

Figure 7-12 Signature Capture Code Rendered on a Pocket PC 2000 Emulator

Description of "Figure 7-12 Signature Capture Code Rendered on a Pocket PC 2000 Emulator"

7.5.8.1 Introduction

In this section, we will discuss some of the advanced user interaction techniques provided by Oracle Application Server Wireless. So far, we have seen how Oracle Application Server Wireless allows users to specify a task when a user performs an action (for example, pressing a soft key on the phone or uttering a command on a voice-enabled device). Advanced User Interactions provide the ability to perform many tasks in response to an action triggered by a user (when supported by the device). And, the ability to perform tasks based on the value input by users is highly desirable.

Oracle Application Server Wireless provides an elaborate scheme to facilitate very sophisticated binding of tasks and actions. This is performed by the SimpleBind element which may appear in the context of SimpleText, SimpleForm, SimpleFormItem, SimpleFormSelect, SimpleMenu, SimpleResult or SimpleContainer.

7.5.8.2 Events and Tasks Using SimpleBind

SimpleBind lets you specify a task which is performed in response to conditions specified by the children of the SimpleMatch element. SimpleMatch may specify primary, secondary, or continue keys, noinput or other events, a speech or DTMF grammar, the condition of filling in a form or form item (SimpleFinish), or menu item, and others. Only one task may be specified in SimpleTask, and when any of the conditions specified in the SimpleMatch occur, the task in the SimpleTask is executed. SimpleTask may also perform tasks selectively by using SimpleSwitch and SimpleCase elements which are analogous to the switch and case constructs of many programming languages.

In SimpleSwitch, a value of a particular user input is compared to the values enumerated by SimpleCase elements. SimpleTask may specify to:

• go to a remote location using SimpleGo

• display (or speak) a text item using SimpleTextItem

• refresh the device screen (if supported) using SimpleRefresh

• clear the specified device form fields using SimpleClear and SimpleName

• allow voice users to reprompt input using SimpleReprompt

• exit the application using SimpleExit

• disconnect the device from connected state (for example, hang up the phone if the service is being accessed through a voice gateway) using SimpleDisconnect

• go back using SimplePrev

• submit form items using SimpleSubmit and SimpleName

The rendering characteristics of the SimpleBind element are specified by the SimpleDisplay element. SimpleDisplay supports SimpleTextItem as child elements that contain the actual render-and-display content. This allows you to play an audio or render the text for a MenuItem (Example 7-25). Figure 7-13 shows the results.

<SimpleBind deviceclass="voice microbrowser">
          <SimpleMatch>
            <SimpleFinish/>
            <SimpleGrammar>
              <grammar root="affirmative">
              <rule id="affirmative">
              <one-of>
              <item>yes</item>
              <item>correct</item>
              <item>true</item>
              <item>one</item>
              </one-of>
              </rule>
              </grammar>
 
            </SimpleGrammar>
            <SimpleDTMF> <grammar root="one">
            <rule id="one">1</rule>
            </grammar>
            </SimpleDTMF>
          <SimpleKey type="primary"/>
          </SimpleMatch>
 
          <SimpleTask>
            <SimpleSubmit
              target="changepin.jsp"
              name="Submit"
              method="post">
              <SimpleName name="p_old_pin" />
              <SimpleName name="p_new_pin" />
            </SimpleSubmit>
          </SimpleTask>
 
          <SimpleDisplay>
            <SimpleTextItem deviceclass="voice">
              <SimpleAudio src="sayYesOrPressOne.wav">
                say yes, or press one, to submit
              </SimpleAudio>
            </SimpleTextItem>
 
            <SimpleTextItem deviceclass="microbrowser">
              Submit
            </SimpleTextItem>
          </SimpleDisplay>
        </SimpleBind>

Figure 7-13 Results of SimpleBind, SimpleMatch and SimpleDisplay

Description of "Figure 7-13 Results of SimpleBind, SimpleMatch and SimpleDisplay"