- From: RJ Auburn <rj@voxeo.com>
- Date: Thu, 14 Feb 2008 08:25:25 -0500
- To: murulidharar@huawei.com
- Cc: W3C Voice Browser Working Group <w3c-voice-wg@w3.org>, www-voice@w3.org
Murali, The correct behavior in this case is to throw an error.semantic event as the implied default expression would not be valid. To help clarify this we have adding the following text to the CCXML specification: > 9.5.6: Errors in default attributes > > If the default value of an attribute is invalid in the current event > context (for example a <disconnect> in a non connection related > event) an error.semantic error MUST be thrown. The working group is now going to consider this issue closed. If you have future comments on this topic please let us know within the next 3 weeks and we would be more then happy to reopen this issue. Thank you very much for the comments on the specification, RJ --- RJ Auburn CTO, Voxeo Corporation tel:+1-407-418-1800 On Feb 8, 2007, at 10:34:27, RJ Auburn wrote: > > This is being tracked as ISSUE-109. > > RJ > > --- > RJ Auburn > CTO, Voxeo Corporation > tel:+1-407-418-1800 > > > > On Jan 30, 2007, at 2:04 AM, murulidhara wrote: > >> Hi, >> >> >> When a dialog is started is it a necessary that it must be joined >> to some connection or conference. >> >> Suppose ,I start a dialog without preparing and in dialogstart >> connectionid or conferenceid are not mentioned , and >> >> Current event being processed is non connection event then what >> should be the behavior of the CCXML interpreter. >> >> Can dialogstart use the last processed connection event to get the >> connectionid from it. if not what should be the behavior of CCXML >> interpreter. >> >> >> Regards, >> >> murali >> >> >> This e-mail and attachments contain confidential information from >> HUAWEI, which is intended only for the person or entity whose >> address is listed above. Any use of the information contained >> herein in any way (including, but not limited to, total or partial >> disclosure, reproduction, or dissemination) by persons other than >> the intended recipient's) is prohibited. If you receive this e-mail >> in error, please notify the sender by phone or email immediately >> and delete it! >> >> >> > >
Received on Thursday, 14 February 2008 13:26:13 UTC