Sample Chapter: Early Adopter VoiceXML - Generating MyRubberbandsML (contd.) (Page 7 of 9 )
Just as we iterated over the order_history/order node-set to create grammars with options for all the orders of a customer, we must now iterate over these nodes again to create individual forms containing the details for each order. If there were consistently a very large number of orders per user, we might look at generating the order details on the fly using JSP or PHP to create a separate VoiceXML document.
The block above illustrates the other way XSLT offers for including dynamic content in an attribute value, this time through the <xsl:variable> element, the value of which can be output by preceding the identifier with the dollar sign, $. This technique is used several times when creating the VoiceXML forms for each order.
<noinput> <!-- This falls through to order status top level --> <assign name="user_command" expr="'order status'"/> <goto next="#navigator"/> </noinput>
The following code generates the prompt to announce the order detail:
<prompt bargein="true" timeout="1s"> This order was placed on <sayas class="date"> <xsl:value-of select="order_date/@sayas"/></sayas>. <break msecs="500"/> The order consisted of <xsl:for-each select="product"> quantity <xsl:value-of select="./@quantity"/> of product
The <xsl:value-of> element below retrieves the name of the product with an XPath expression that selects products from the XML product_list section where the id attribute matches the id attribute of the current order. This is analogous to an SQL join between the customer_order and customer_order_product tables from relational schema. Note that XPath denotes an attribute with use of the at symbol, @.
<xsl:value-of select="/myrubberbands/product_list/product[@id=current()/@id]"/> <break msecs="500"/> </xsl:for-each> The total of the order was
Next, we see the VoiceXML <sayas> element put to use. Whether or not this causes the contents to be rendered correctly as currency depends on the TTS engine used, and its support for pronunciation markup. The rest of the block repeats the previous technique to add order options to the inline <grammar> element.
<sayas class="currency"> $<xsl:value-of select="total_charge"/></sayas>. The status of this order is <xsl:value-of select="order_status"/>. </prompt>
<grammar type="application/x-jsgf"> list | product list | more information | frequently asked questions | questions | order status | <xsl:for-each select="/myrubberbands/customer_record/order_history/order"> order number <xsl:value-of select="position()"/> | </xsl:for-each> buy me </grammar>
At this point we'll skip over the product list option, because it doesn't illustrate anything we haven't already seen. However, the product listing prompt offers the user the option to say, "Buy me", in which case their call is transferred to the MyRubberbands.com's telephone service center by the placeOrder form below. This is the quickest way for the company to add some commerce capability to the voice system, but note that the VoiceXML <transfer> element is not implemented by all platforms. When the user returns from the call, they are unconditionally sent to the main menu by the subsequent <goto> element.
<form id="placeOrder"> <block> <prompt bargein="false" timeout="1s"> Transferring your call to customer service.
We can also skip over the frequently asked questions option, since it contains only static VoiceXML code. We are now almost at the end of our stylesheet, where the navigator form is located, holding the navigation logic for many of the state transitions in our interface design.
It consists simply of an if-else construct that expresses the state transitions on the diagram of the user interface earlier. If more commands, states, or transitions were to be added to the design, the complexity of the interface might exceed the limitations of this method of implementation.
Finally, we come to the errorHandler form that is used by most of the <nomatch> handlers in the dialog. This error handler keeps a running count of the number of errors, and when four errors have occurred, it will apologize and disconnect the user. This isn't the friendliest way of handling errors, and is not suitable for a long-range solution that would more likely transfer the user to a human operator at this point. Not only that, but we'd probably want more sophisticated logic for processing errors, maybe using ECMAScript to vary the response according to the time elapsed since the last error.
<if cond="session_error_count < 4"> <prompt bargein="false" timeout="0.1s"> I'm sorry, but I'm unable to understand you. </prompt> <if cond="session_error_count > 2"> <prompt bargein="false" timeout="0.1s"> It seems I am having trouble. </prompt>
<goto next="#navigator"/> <else/> <prompt bargein="false" timeout="0.1s"> I'm sorry, but I'm having a lot of difficulty understanding you. If you are currently in a noisy environment, please call back later. </prompt> <exit/> </if> </block> </form>
All that needs to be done now is to close the document, after including an empty template matching standalone <product_list> elements, to suppress any output from them. Without this, default XSLT templates would be applied that output text children of any elements that aren't explicitly matched by a template already.