Talk:XML - Managing Data Exchange/VoiceXML

My chapter seems to be pretty good as far as the content goes. I think I need to go through the checklist to make its appearance consistent with the rest of the chapters.

Editorial Board Suggestions
I admit that I didn't fully understand this chapter; some of the information is a little too technical for me. I understood the chapter better when I saw the VoiceXML code examples and their corresponding dialogs. It made me think of automated phone menus or surveys that prompt callers for voice responses--scenarios that are more familiar to me. Even though the chapter explains that inputs can be in more forms than just speech, such as touch tone inputs, I think more familiar examples will help the reader understand the concepts of VoiceXML. Based on my initial reading of the chapter, here are my questions/suggestions:

Overall

''VoiceXML is created to generate audio dialogs that allows the use of synthesized speech, digitized audio, recognition of spoken and DTMF(Dual Tone Multi-Frequency Touch-tone or push-button dialing. Pushing a button on a telephone keypad generates a sound that is a combination of two tones, one high frequency and the other low frequency) key input, recording of spoken input, telephony, and mixed initiative conversations. The major goal of VoiceXML is to bring the advantages of the XML language to generate interactive voice response applications. VoiceXML sets an integration environment between voice services and data services taking advantage of the client-server paradigm.'' The parentheses need to be corrected, but aside from that, what are some examples of using synthesized speech, digitized audio, etc. in relation to VoiceXML? This didn't really ring clear to me.
 * Definitely use the checklist.
 * The chapter should have learning objectives.
 * Provide more familiar details of VoiceXML applications. In particular, correct and flesh out the following segment:
 * Just an idea--I wonder if it would make more sense to move the VoiceXML code examples before the VoiceXML elements. This may help reinforce the concepts, and when you discuss the VoiceXML elements, you could refer to the example code elements the reader has already previewed. Also, then there would be no need for the  element code example because it already exists in the form and menu code examples, and both of these examples simply can be referenced when discussing the  element and the rest of the elements.
 * Other element examples--even though the form and menu examples include the vxml, field, grammar, block, and prompt elements, the samples of code do not always include one of the listed attributes for these elements (might be nice). Furthermore, the  element in the sample code includes  and I didn't see any content in the chapter that explains the src and type attributes for the  element. Perhaps some comments in the code or more explanation in the chapter would be helpful.
 * In the Form example, there is --should the property element be explained further in its own section, as are the vxml, field, grammar, etc. elements?
 * Provide additional comments for all code examples and tables to help transition between content.
 * The exercises mention choosing options from a keyboard. Maybe I'm not familiar enough with the chapter, but I didn't understand how this is using VoiceXML.

Implementation platform requirements This section kind of lost me. The bolded terms confused me. Is "document acquisition" the hardware/software requirements? Similarly, I wasn't too sure what "audio output" and "audio input" were correlated with--it could just be the way these terms are being referenced (i.e. colon, comma, period). The bulleted list confused me as well. There doesn't seem to be a sentence that transitions to the bulleted list. Is the list a summary of implementation platform requirements? The list also contains a few ambiguous Its that should be clarified.

VoiceXML architectural model


 * The model references component titles with capital letters (e.g. Document Server). Should this style be continued throughout the chapter? There are times these components are referenced with capital and lowercase letters, and the way these are referenced should remain consistent throughout the chapter. I think the component references are more distinguished when they're used like titles with capital letters.
 * The last bullet in this section doesn't seem as though it should be a part of the list. It's an example of how the model works, so it probably should just be a paragraph after the list.
 * The graphic is a little blurry. You could replace it with the following graphic:

Christinaserrano 04:38, 24 March 2006 (UTC)

Professor
The editorial board has provided much good advice, and it should be considered carefully when making the revision.

It would be useful to have links to topics such as synthesized speech, which is probably in Wikipedia.

I agree with moving the examples before listing all the elements. Give people concrete examples before abstract notions.

Remove details of the prior authors.

For the class presentations, see if you can find a live example to use.

Rtw 14:17, 24 March 2006 (UTC)