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

Re: CCXML Implementation Report: asserts 714 and 715 - ISSUE-670

From: Petr Kuba <kuba@optimsys.cz>
Date: Thu, 03 Jun 2010 14:04:52 +0200
Message-ID: <4C079A64.2010603@optimsys.cz>
To: Baggia Paolo <paolo.baggia@loquendo.com>
CC: www-voice <www-voice@w3.org>, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>

Could you please clarify the "sessionid in ccxml.kill" issue in more 
detail? Perhaps I'm missing something...

We are OK with all the remaining resolutions you've posted so far.

Description of the "sessionid in ccxml.kill" issue:

We understand that the sessionid attribute in ccxml.kill contains the 
session id. The question is who is responsible for inserting the 
sessionid attribute into the ccxml.kill event if the event is sent using 

I understand that the platform must insert the attributes listed in 
"9.4.2: Standard Event Attributes" into an event when interpreting 
<send>. The sessionid attribute is not listed here. However, I don't 
think that the platform should insert any other attributes of standard 
events automatically.

Since 6_1.txml doesn't include sessionid in the namelist of the <send> 
it looks like the platform should be responsible for inserting the 
sessionid attribute. Is it correct? It sounds strange to me...

Thanks for clasrification,

On 1.6.2010 15:52, Baggia Paolo wrote:
> Petr,
> We are in the process to address all ISSUES related to IR. The goal is to re-publish the CCXML-IR in a short term.
> Please explicitly confirm that you accept the proposed resolution or after one week we will consider implicitly accepted the resolution. If you need clarification, please ask them very soon.
> Paolo Baggia
> Author of CCXML-IR Plan
> ISSUE-670:
> Proposed Resolution: Partially Accept
> The 'ccxml.kill' event was generated by send element:
> - sessionid is the target of send (no need to change)
> - reason is missing (accepted)
> =================================
> Petr:
> Thanks. We have tracked this as ISSUE-670. We are discussing this in the next few days internally and should have an answer shortly (within a week at the most).
> 	RJ
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> tel:+1-407-418-1800 begin_of_the_skype_highlighting              +1-407-418-1800      end_of_the_skype_highlighting
> On Apr 8, 2010, at 11:04 AM, Petr Kuba wrote:
>> Hello,
>> We believe that the script 6_1.txml for testing Assers 714 and 715
>> (required properties sessionid and reason of the ccxml.kill event) is
>> not correct because it breaks the following part of the specification:
>> CCXML specification, Section 9.1:
>> "...however, it is legal for external sources and for events created
>> using<send>   to generate standard events. For instance, it is useful to be able to generate a ccxml.kill event to attempt graceful termination of a session from an external context, or from another CCXML session. Platforms SHOULD reject any standard events that do not contain all of the mandatory properties defined in this specification, and SHOULD notify the sender of the rejection (for instance with an error.send event)."
>> We believe that the following statement at line 573, 6_1.txml breaks the specification because it does not contain required properties sessionid and reason:
>> <send target="childSessionId" targettype="'ccxml'" name="'ccxml.kill'"
>> sendid="mySendId"/>
>> Therefore the event SHOULD be rejected and the asserts 714 and 715
>> cannot pass.
>> Could you please look into this?
>> Best Regards,
>> Petr Kuba
>> --
>>    Petr Kuba, Project Manager
>>    OptimSys, s.r.o
>>    kuba@optimsys.cz
>>    Tel: +420 541 143 065 begin_of_the_skype_highlighting              +420 541 143 065      end_of_the_skype_highlighting
>>    Fax: +420 541 143 066
>>    http://www.optimsys.cz
Received on Thursday, 3 June 2010 12:05:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:03:56 UTC