- From: RJ Auburn <rj@voxeo.com>
- Date: Thu, 18 Jun 2009 10:38:58 -0400
- To: Jayalakshmi Swaminathan <jayalakshmi@huawei.com>
- Cc: www-voice@w3.org, ranjit@huawei.com, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>
- Message-Id: <A6427E0A-B936-4550-81B5-7115BF8716D4@voxeo.com>
Jaya, We have addressed your comment with the following spec changes: OLD: A <move> attempt MUST fail under any of the following conditions: · The referenced event source does not exist, or does not belong to the session executing the <move>; · The referenced event source is immovable - the CCXML session itself and various external event I/O processors are examples of this; · The referenced event source is currently bridged in a way that prevents it from being moved (as described below) ; · The session to which the event source is being moved does not exist, or cannot accept the event source that is being moved; A <move> attempt MAY fail for causes other than the above, which may or may not be platform specific A <move> is not allowed once an event source is associated with another object through an implicit or explicit <join>. NEW: A <move> attempt MUST fail under any of the following conditions: · The referenced event source does not exist, or does not belong to the session executing the <move>; · The referenced event source is immovable - the CCXML session itself and various external event I/O processors are examples of this; · The referenced event source is currently bridged to another object through an implicit or explicit join; · The session to which the event source is being moved does not exist, or cannot accept the event source that is being moved; · The event attribute is used to identify the event source, but refers to multiple event sources (such as connection.merge.failed); A <move> attempt MAY fail for causes other than the above, which may or may not be platform specific A <move> is not allowed once an event source is associated with another object through an implicit or explicit <join>. Please let us know if this addresses your concerns. If we do not hear back from by 7/9 we will consider this issue closed. Thank you again for this feedback, Best regards, RJ --- RJ Auburn CTO, Voxeo Corporation Chair, Editor and Chair, CCXML, VBWG, W3C On May 7, 2009, at 9:35 AM, RJ Auburn wrote: > 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, 18 June 2009 14:39:37 UTC