W3C home > Mailing lists > Public > www-voice@w3.org > July to September 2010

Re: April CCXML, 7_2: combination of attributes in <dialogstart> - ISSUE-724

From: Baggia Paolo <paolo.baggia@loquendo.com>
Date: Thu, 23 Sep 2010 16:42:09 +0200
To: 'Petr Kuba' <kuba@optimsys.cz>
CC: Baggia Paolo <paolo.baggia@loquendo.com>, "'www-voice@w3.org'" <www-voice@w3.org>, 'RJ Auburn' <rj@voxeo.com>, "'W3C Voice Browser Working Group'" <w3c-voice-wg@w3.org>
Message-ID: <20E062AE0851CC41B7FBECC23638796F394A438099@GRFMBX704BA020.griffon.local>

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


We accepted your request: mutually exclusive elements should be checked at load time. We are in the process to update the test-suite.

Note that this resolution will impact also the behaviour of constraints
in other elements. We will review also all the related tests.

From: RJ Auburn <rj@voxeo.com> 
Date: Thu, 29 Jul 2010 10:14:08 -0400
Cc: www-voice <www-voice@w3.org>, W3C Voice Browser Working Group <w3c-voice-wg@w3.org> 
Message-Id: <3A385059-FAD5-4C2C-8149-4B32558519EC@voxeo.com> 
To: Petr Kuba <kuba@optimsys.cz> 


This did indeed get missed the first time around. Thanks for resending. 

Tracker ID is ISSUE-724. 


On Jul 19, 2010, at 9:59 AM, Petr Kuba wrote:

> Hello www-voice,
> We haven't received any response to this issue. Could you please look into this because it's blocking us in the new Implementation Report.
> Thanks,
> Petr
> On 27.5.2010 17:29, Petr Kuba wrote:
>> Hello www-voice,
>> In 7_2.txml, assertions 340, 342, 347, 349, 366, 368, 370, 373, and 1186
>> test the following features in <dialogstart>:
>> (1) The src, type, namelist, maxage, maxstale, enctype, method, and
>> parameters attributes MUST NOT be specified in conjunction with the
>> prepareddialogid attribute.
>> (2) If the prepareddialogid attribute is specified and any attribute
>> values conflict with the values specified in the <dialogprepare> element
>> this MUST result in the throwing of an error.dialog.notstarted event.
>> ------
>> We believe that the incorrect combination of mutually exclusive
>> attributes in (1) should be handled according to 9.5.1 Fetching &
>> compilation errors:
>> "Errors that occur in trying to load and compile a CCXML document, such
>> as ... validation errors (Including checks for mutually exclusive
>> attributes...)"
>> Therefore these errors should result in error.createccxml or error.fetch
>> instead of error.dialog.notstarted.
>> ------
>> Thus (2) could apply only on the connectionid and conferenceid
>> attributes. However, the Specification states in description of these
>> attributes:
>> "If the dialog was previously prepared using a <dialogprepare> element
>> with a connectionid or conferenceid specified, and this attribute is
>> also specified, execution of the <dialogstart> MUST fail with an
>> error.dialog.notstarted event."
>> Therefore the conflict in (2) cannot occur because it is not allowed to
>> use connectionid / conferenceid in both <dialogprepare> and <dialogstart>.
>> We recommend to remove the statement (2) from the specification (Section
>>, paragraph 4).
>> Thanks,
>> Petr
Received on Thursday, 23 September 2010 14:42:56 UTC

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