W3C home > Mailing lists > Public > www-voice@w3.org > October to December 2003

CCXML <goto>

From: Tracy Boehrer <tboehrer@calltower.com>
Date: Sun, 23 Nov 2003 12:28:15 -0800
Message-ID: <676743E57886C340A628FB1DCCF42D3B1BB335@CTMAIL.calltower.com>
To: <www-voice@w3.org>
As raised in Appendix A "General Issues", I have suggestions for for breaking up a single documet into parts.
 
One primary problem is starting the new document in the correct state.  One solution might be to add <param> elements, much in the same flavor as <param> elements are used in the VoiceXML <subdialog> element.  That is, <goto> could specify <param> elements, which the target document would use to initialize variables with.  While the <goto> has the "namelist" attribute, which an app server could use to construct a CCXML document with the correct values, this would prohibit static CCXML documents.  Using <param> would allow for intializing the state in either dynamic or static scripts.
 
One other solution might be to allow for "global" scope, which survives for the duration of the session.  This is similar to the "application root" in CCXML.  Therefor, using <goto> to transition to a new document would leave the current global scope intact.
 
One other observation:  The ability to have an "application" document in CCXML might also be a way for the script writer to have "default" transitions (as raised in the Appendix A), as well as "global" state.
Received on Sunday, 23 November 2003 15:28:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:48:59 GMT