Re: April CCXML 9_2_3_B: handling of invalid event name in <send> [cc] ISSUE-719


We are in the process to address all ISSUES related to IR. The goal is to finalize the test-suite during the PR transition.
Please explicitly confirm that you accept the proposed resolution or after one week we will consider it implicitly accepted.
If you need clarifications, please ask them very soon.

Paolo Baggia
Author of CCXML-IR Plan


We reviewed this ISSU-719 and also ISSUE 734 (see separate email).

The behaviour is correct and coherent with CCXML specification, to clarify
it CCXML will be clarified as follows:

9.3.5: error.send.failed

This error event MUST be thrown when a <send> could not be completed for a reason not covered by another error.send.* event [[[(for example, due to an invalid event name specified on <send>)]]].

From: RJ Auburn <> 
Date: Thu, 3 Jun 2010 08:47:22 -0400
Cc: www-voice <>, W3C Voice Browser Working Group <> 
Message-Id: <> 
To: Petr Kuba <> 

tracked as ISSUE-719
RJ Auburn
CTO, Voxeo Corporation

On May 31, 2010, at 10:51 AM, Petr Kuba wrote:

> Hello www-voice,
> In 9_2_3_B.txml, assertion 1247 expects that invalid name attribute value ('.name_prepare_new') results in throwing an error.send.* event (error.send.failed).
> In this case we would expect an error.semantic event to be thrown because it better fits the situation where an attribute has an incorrect value:
> "9.3.2: error.semantic
> This error event MUST be thrown when there is a semantic error in a CCXML element ( e.g. passing an incorrect value for an attribute, etc.)."
> error.send.* event seem to be used in situation where delivery of events fails for some "dynamic" reason, e.g. target unavailable.
> Thanks,
> Petr
> -- 
>  Petr Kuba, Project Manager
>  OptimSys, s.r.o
>  Tel: +420 541 143 
>  Fax: +420 541 143 066

Received on Friday, 27 August 2010 08:24:21 UTC