W3C home > Mailing lists > Public > www-voice@w3.org > April to June 2010

Re: April CCXML: attribute 'id' of the error.notallowed event - ISSUE-707 [cc]

From: RJ Auburn <rj@voxeo.com>
Date: Thu, 3 Jun 2010 08:18:56 -0400
Cc: www-voice <www-voice@w3.org>, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>
Message-Id: <37199072-E323-44D4-BE8C-C44994B10568@voxeo.com>
To: Petr Kuba <kuba@optimsys.cz>
Petr:

This is tracked as ISSUE-707. 

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

Come join us at our Voxeo Customer Summit
June 21st  June 23rd at the Hard Rock Hotel
Register today for your All Access Pass:  
http://www.voxeo.com/summits/customer




On May 5, 2010, at 11:03 AM, Petr Kuba wrote:

> Hello,
> 
> Usage of the error.notallowed event in the <cancel> element should be probably clarified.
> 
> Overview of the <cancel> element in 9.2.5.1 states:
> 
>    ...the <cancel> request MUST fail and an error.notallowed event
>    MUST be delivered to the event queue...
> 
> Description of the 'id' attribute of the error.notallowed event states:
> 
>    The ID, if specified in the element being executed, of the affected
>    connection, dialog, session, or conference.
> 
> The question is: shall the 'id' attribute of the error.notallowed event contain id of the event for which <cancel> failed? If yes, it should be explicitly stated in 9.2.5.1 and description of the 'id' attribute of the error.notallowed event should list also event (besides connection, session and others).
> 
> 
> Thanks,
> Petr Kuba
> 
> -- 
>   Petr Kuba, Project Manager
>   OptimSys, s.r.o
>   kuba@optimsys.cz
>   Tel: +420 541 143 065
>   Fax: +420 541 143 066
>   http://www.optimsys.cz
> 
Received on Thursday, 3 June 2010 12:19:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 June 2010 12:19:44 GMT