- From: Petr Kuba <kuba@optimsys.cz>
- Date: Fri, 20 Aug 2010 10:48:16 +0200
- To: Baggia Paolo <paolo.baggia@loquendo.com>
- CC: "'www-voice@w3.org'" <www-voice@w3.org>, 'RJ Auburn' <rj@voxeo.com>
Paolo, We confirm that we accept the proposed resolution. Sorry for the confusion with the assert numbers. Thanks, Petr On 19.8.2010 12:00, Baggia Paolo wrote: > Petr, > > 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 > > ISSUE-740: > > You write "In 7_3, assert 412", but it seems to be assert 425, > In any case you are right, it will be fixed. > > ================================= > From: RJ Auburn<rj@voxeo.com> > Date: Thu, 29 Jul 2010 10:57:47 -0400 > Cc: www-voice<www-voice@w3.org>, W3C Voice Browser Working Group<w3c-voice-wg@w3.org> > Message-Id:<C373DCBD-C405-4E28-8B6B-00C858D5F70B@voxeo.com> > To: Petr Kuba<kuba@optimsys.cz> > > Tracked as ISSUE-740 > > On Jul 27, 2010, at 7:19 PM, Petr Kuba wrote: > >> Hello www-voice, >> >> In 7_3, assert 412, the following code is used: >> >> >> >> <transition event="connection.disconnected" state="ASSERTION_NMBR_425"> >> <conf:comment expr=" 'Current state : ' + current_state + ' , Event: ' + event$.name"/> >> <dialogterminate dialogid="DialogID"/> >> </transition> >> >> <transition event="conference.unjoined" state="ASSERTION_NMBR_425"> >> <conf:comment expr=" 'Current state : ' + current_state + ' , Event: ' + event$.name"/> >> </transition> >> >> >> <transition event="dialog.exit" state="ASSERTION_NMBR_425"> >> <conf:comment expr=" 'Current state : ' + current_state + ' , Event: ' + event$.name"/> >> <send targettype="'ccxml'" target="session.id" name="name_prepare_new"/> >> </transition> >> >> >> >> <dialogterminate> results in two events: >> >> 1) conference.unjoined >> 2) dialog.exit >> >> The problem is that the order of these two events is not specified and if conference.unjoined is receiver after dialog.exit then it is processed by the consequent assertion. This results in unexpected event being reported. >> >> >> >> Thanks, >> Petr >> >> -- >> 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 Friday, 20 August 2010 08:48:50 UTC