Re: April CCXML: 4 issues w/7_2.txml - ISSUE-705 [cc]

Chris,

We are in the process to address all ISSUES related to IR. The goal is to re-publish the CCXML-IR in a short term.
Please explicitly confirm that you accept the proposed resolution or after one week we will consider implicitly accepted the resolution. If you need clarification, please ask them very soon.

Paolo Baggia
Author of CCXML-IR Plan

ISSUE-705:

Here are the resolutions for your four issues:

1. The Spec will be fixed to define immediate attribute to be of type ECMAScript Boolean expression, like other similar attributes, so that, the default value and description values will remain the same. With this resolution the test don't need to be changed.

2. Right, it will be fixed accordingly.

3. Right, the event will be added.

4. Right, tests will be fixed accordingly.

=================================
This is tracked as ISSUE-705 

---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800 


On May 14, 2010, at 9:38 AM, Chris Davis wrote:

> Hello www-voice,
> 
> 1)  note: dialogterminate has the immediate boolean/string problem
>  7.2.3.2 says of the immediate attribute that it is "An ECMAScript expression which returns a character string,"
>  It seems simpler for the "type" to be "ECMA script expression returning boolean", but that is not the way
>  things are currently written.
> 
> 2) <var name="paramcc3='Hello world'"/> should be
> <var name="paramcc3" expr="'Hello world'"/>
> 
>  As written, it causes ECMA errors
> 
> 3) When <dialogterminate> is called, the browser generates as a side effect conference.unjoined.
>    This is consistent with 7.2.3.1, which says:
>   "The platform MUST tear down any existing bridges to the dialog and send a conference.unjoined     to the CCXML document once the media paths have been freed."
>    The problem is that the script is not expecting this, and treats the conference.unjoined as an error
> 4) <dialogstart> has maxage/maxstale passed as integers not strings. A string result of the ECMA script expression
> is implied in  7.2.2.2 where it says "The character string returned must be interpreted as a time interval."
>   It seems simpler for the "type" to be "ECMA script expression returning integer", but that is not how it is written.
> 
> Regards,
> Chris
> 
> -- 
> Chris Davis
> Interact Incorporated R&D
> 512-502-9969x117

Received on Friday, 2 July 2010 08:20:54 UTC