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

Re: July CCXML Implementation Report: 8_2_3: how to handle error in loading static <script> - ISSUE-732

From: Petr Kuba <kuba@optimsys.cz>
Date: Fri, 17 Sep 2010 08:51:25 +0200
Message-ID: <4C930FED.6030708@optimsys.cz>
To: Baggia Paolo <paolo.baggia@loquendo.com>
CC: "'www-voice@w3.org'" <www-voice@w3.org>, 'RJ Auburn' <rj@voxeo.com>

We accept this resolution.


On 16.9.2010 16:01, 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-732:
> We accepted your request and the test will be fixed to allow pre-load the
> script as well as to load during interpretation.
> Section timeout property will be updated to say:
> "The character string must be interpreted as a time interval. This interval must begin when the script is requested; If the script has not been fetched at the end of this interval, an error.fetch [[or error.createccxml]] event must be thrown."
> =================================
> From: RJ Auburn<rj@voxeo.com>
> Date: Thu, 29 Jul 2010 10:49:43 -0400
> Cc: www-voice<www-voice@w3.org>, W3C Voice Browser Working Group<w3c-voice-wg@w3.org>
> Message-Id:<13FBD6EF-70D5-491B-8962-04F245FCA86E@voxeo.com>
> To: Petr Kuba<kuba@optimsys.cz>
> Tracked as ISSUE-732
> On Jul 26, 2010, at 4:14 AM, Petr Kuba wrote:
>> Hello www-voice,
>> In 8_2_3, the following code is used to load a script:
>> 		<script src="sleeper.ircgi" timeout="1s"/>
>> Since the sleeper.ircgi script contains 20s delay loading of the script must fail.
>> Our question is how to handle this loading error. The Specification, Section contains the following note:
>> "INFORMATIVE NOTE: The<script>  element's resource loading model is a bit different than the rest of CCXML for a number of reasons. Because CCXML and ECMAScript applications can be CPU intensive to compile we define<script>'s src attribute (defining the URI of the document to load) to be a static string instead of a dynamically valued ECMAScript result. This allows implementations to load ECMAScript content at CCXML document load time and perform compiling and/or caching of the resulting ECMAScript code. We do however recognize that there are cases where a CCXML application needs to load a dynamic ECMAScript resource, for this reason applications can use the the<fetch>  element to asynchronously load a resource and then execute it by referencing it's fetchid in the the<script>  element."
>> We load the script content at the CCXML document load time as recommended. The loading error results in throwing error.createccxml because we were not able to load the CCXML document or one of its parts. The CCXML document interpretation is not started at all.
>> We believe that the test script 8_2_3_A.txml is incorrect when it expects the error.fetch event to be thrown.
>> Please clarify on this.
>> 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, 17 September 2010 06:52:03 UTC

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