- From: Scott McGlashan <scott.mcglashan@pipebeach.com>
- Date: Tue, 28 May 2002 15:33:17 +0200
- To: <Teemu.Tingander@tecnomen.fi>
- Cc: "w3c voice (E-mail)" <www-voice@w3.org>
Teemu, Your request (R418) for clarification of prompt counting (reproduced below) was discussed by the Dialog team on 2002-05-07. We believe that this issue has been addressed in the latest draft. If you think we still need to address your issue, please let us know as soon as possible. If we do not hear from you with 14 days, we will take this as tacit acceptance. thank you for input on the specification. Scott Dialog Team Leader, VBWG [request discussed ...] While reading spec 2.0 I found following "problem". --> Taken form W3C VoiceXML 2.0 draft in chapter 4.1.6 "Each form item and each menu has an internal prompt counter that is reset to one each time the form or menu is entered. Whenever the system uses a prompt, its associated prompt counter is incremented. This is the mechanism supporting tapered prompts." So the question is : Are prompt counts maintained for <form/> and <menu/> elements only or are they maintainded for each <*form item*> - specified in chapter 2.1.2 ? If we are working like in events; Counters are reseted when entering <form/> or <menu/> and we have individual counter for each <*form item*> , but initial uses <form/>s counters. This is right? So does this mean that when <goto item="this" /> occurs in field "that" while field "this" has prompt counter 3 the prompt that has count 3 is selected. So entering <field name="this">..</field> does not reset counter. So returning to <*form item*> that has prompted something before maintains <*form item*>s prompt count and allows us to do "tapared prompting", yeah ?
Received on Tuesday, 28 May 2002 09:30:41 UTC