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

Re: CCXML :<move event=event$> in transition for "connection.merge.failed" - ISSUE-603

From: RJ Auburn <rj@voxeo.com>
Date: Thu, 7 May 2009 09:35:59 -0400
Cc: www-voice@w3.org, ranjit@huawei.com, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>
Message-Id: <A3A89723-0397-4047-8DA0-285221D1A3C8@voxeo.com>
To: Jayalakshmi Swaminathan <jayalakshmi@huawei.com>
Jaya,

Thanks for sending this in. We are tracking this as issue id ISSUE-603.

Best regards,

	RJ

---
RJ Auburn
CTO, Voxeo Corporation
Chair, Editor and Chair, CCXML, VBWG, W3C

On May 4, 2009, at 1:27 AM, Jayalakshmi Swaminathan wrote:

> Hi,
>
> From the CCXML specification, for event attribute of <move>:
>
> "The event source, from which the event object originated, if any,  
> must be moved to the target session.
> The event must also be sent to the target session to provide a  
> notification."
>
> The attribute list for connection.merge.failed:
> 10.6.19: connection.merge.failed
> This event MUST be emitted when a <merge> attempt fails. This event  
> MUST NOTchange the state of either of the Connection Objects  
> involved in the merge operation The fields of this event are:
> Attribute Name
> Required
> Type
> Details
> name
> true
> string
> error.merge
> connectionid1
> true
> string
> The ID of the first Connection identified when the merge was invoked.
> connectionid2
> true
> string
> The ID of the second Connection identified when the merge was invoked.
> reason
> true
> string
> A description of the reason the merge failed. Content of this field  
> is platform-specific.
> eventid
> true
> string
> The unique identifier for the event. This must match the  
> sendidattribute of send, if the event was generated by a CCXML  
> document.
> eventsource
> true
> string
> The unique identifier of the event source. This identifies the  
> Platform Event I/O Processor that sent this event.
> eventsourcetype
> true
> string
> The name of the Event I/O Processor that sent this event. The value  
> is platform dependent as this is an event generated by the Platform  
> Event I/O processor.
>
> Consider the following transition:
>
> <transition event="connection.merge.failed">
>     <move session_id="target_session_id" event="event$" />
>      ...
> </transition>
>
> In the above case, where we have <move> with event attribute within  
> the transition for “connection.merge.failed”, should both event  
> sources(connectionid1 and connectionid2) be moved to the target  
> session??
>
> The specification does not talk about moving multiple event sources.  
> All other connection events are only associated with one connection  
> object, but this event – connection.merge.failed is associated with  
> two connection objects. So, should both eventsources be moved to the  
> target session? If not, what should be the handling?
>
> Pls clarify.
>
> Thanks
> Jaya
>
>
>
>
Received on Thursday, 7 May 2009 13:36:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 May 2009 13:36:47 GMT