W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2007

[cc] Re: Comments on CCXML Working Draft 19 January 2007 (2)

From: RJ Auburn <rj@voxeo.com>
Date: Wed, 7 Feb 2007 07:51:39 -0500
Message-Id: <32F6AB09-2D2E-4AA6-AE90-EF922ADAD06F@voxeo.com>
Cc: <www-voice@w3.org>
To: Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>

Hrvoje:

Thanks for your comments on the CCXML LCWD specification. The working  
group will reply to your comments very shortly.

Thanks,

	RJ
---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800



On Feb 7, 2007, at 6:19 AM, Hrvoje Nezic wrote:

>
> 9: Event handling
>
> Current text:
> "If a semantic error occurs that prevents an element in the  
> transition from being executed (such as the 'cond' attribute of  
> <if> being an invalid ECMAScript expression), then successive  
> elements within that transition will NOT be executed; an  
> error.semantic will be raised for the element that could not be  
> executed. Note that elements that can be executed but that generate  
> errors (such as a <disconnect> on an invalid connection ID) do not  
> terminate execution of the transition."
>
> I think that this explanation is not clear enough. The phrase  
> "elements that can be executed but that generate errors" could be  
> applied to most CCXML elements. I think that intention was probably  
> to distinguish between synchronous and asynchronous elements.  
> Synchronous elements are <var>, <assign>, <script>, <if>, <elseif>,  
> <else>, <goto>, <exit>, <log>, while other elements are  
> asynchronous and generate events to signal success or failure.
>
> The new text could be something like this:
> "If a semantic error occurs that prevents a synchronous element in  
> the transition from being executed (such as the 'cond' attribute of  
> <if> being an invalid ECMAScript expression), then successive  
> elements within that transition will NOT be executed; an  
> error.semantic will be raised for the element that could not be  
> executed. If a semantic error occurs that prevents an asynchrounous  
> element from being executed (such as a <disconnect> on an invalid  
> connection ID), execution of the transition will not be terminated."
>
Received on Wednesday, 7 February 2007 12:53:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 February 2007 12:53:41 GMT