W3C home > Mailing lists > Public > www-voice@w3.org > October to December 2008

Re: Incorrect example in the CCXML spec (ISSUE-553)

From: RJ Auburn <rj@voxeo.com>
Date: Thu, 4 Dec 2008 09:59:47 -0500
Cc: www-voice@w3.org, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>
Message-Id: <0DAAA8F9-CC27-4494-9C23-5EFEF98BB1A1@voxeo.com>
To: Petr Kuba <kuba@optimsys.cz>

Petr,

We have accepted your change and applied it to the internal version of  
the CCXML spec. At this point we consider this issued to be resolved.

Best regards,

	RJ

---
RJ Auburn
CTO, Voxeo Corporation
Chair, Editor and Chair, CCXML, VBWG, W3C

On Nov 13, 2008, at 8:00 AM, RJ Auburn wrote:

>
> Peter,
>
> Thanks for raising this issue. We are tracking it as ISSUE-553. We  
> will take a look at this during the next call or two and let you  
> know what we find.
>
> Best regards,
>
> 	RJ
>
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> Chair, Editor and Chair, CCXML, VBWG, W3C
>
>
> On Nov 13, 2008, at 7:19 AM, Petr Kuba wrote:
>
>>
>> Dear WBWG,
>>
>> It seems that there is an incorrect example in the CCXML  
>> specification.
>> The problem is on the very last line in Section 10.5.4.3 in the hints
>> attribute of the <createcall> tag:
>> hints="{callingDevice: 'notSpecified', callCharacteristics:  
>> 'voiceUnitCall'}"
>>
>> When we tried to interpret a similar <createcall> using our  
>> OptimTalk CCXML interpreter, we received the following ECMAScript  
>> error:
>> "SyntaxError: invalid label"
>>
>> We looked at the ECMAScript formal grammar in the ECMAScript  
>> specification and found out that reporting an error when evaluating  
>> the
>> "{callingDevice: 'notSpecified', callCharacteristics:  
>> 'voiceUnitCall'}"
>> script is a correct behavior.
>>
>> Following the ECMAScript formal grammar, the script is an expression
>> statement and the ECMAScript spec says:
>>
>> <CITATION>
>> 12.4 Expression Statement
>>
>> ExpressionStatement :
>> [lookahead ? {{, function}] Expression ;
>>
>> Note that an ExpressionStatement cannot start with an opening curly  
>> brace
>> because that might make it ambiguous with a Block. [...]
>> </CITATION>
>>
>> A solution is to use the hints attribute as follows:
>> hints="var tmp = {callingDevice: 'notSpecified',  
>> callCharacteristics: 'voiceUnitCall'}; tmp"
>>
>> Can you please correct the specification?
>>
>> Regards,
>> Petr Kuba
>>
>> -- 
>>  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 Thursday, 4 December 2008 14:59:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 4 December 2008 14:59:56 GMT