Comments on CCXML WD 19 January 2007

Hello,
I believe that the following issues were not addressed in any previous 
contribution:

Issue 1: Wrong description of IN/OUT media streams
Location: 10.4

Rationale:

The following text in Section 10.4 (first item in the second block of 
items) contains wrong description of input and output media stream - and 
is in contradiction with description in Section 10.2, paragraph 4:

"Each Connection has one input, and 0 or more outputs. If a network call
is active on a Connection, the media stream received from the network is
the Connection input, and the Connection output media stream is
transmitted to the network."

Proposed change:

"Each Connection has 0 or one input, and 0 or more outputs. If a network 
call is active on a Connection, the media stream received from the 
network is the Connection output, and the Connection input media stream 
is transmitted to the network."

---

Issue 2: Session IDs in Basic HTTP Event I/O Processor
Location: Appendix K

Rationale:

Section K.3 says:
"To inject an event into an existing CCXML session, the HTTP request 
must specify the id of the session and the name of the event. The 
session id MUST be specified as an HTTP parameter named "sessionid"."

Section K.4 says:
"The id of the CCXML session id MUST be sent as a HTTP parameter named 
"session"."

Suppose that we are sending an event from one CCXML session to another 
via Basic HTTP. Then it should contain the following parameters:

session = id of the source CCXML session
sessionid = id of the target CCXML session

Is this correct? It seems to be a bit confusing. Please clarify on this.

---
Issue 3: Bugs in examples.

We've met a bunch of bugs in examples:

In section 9.2.3.3 fourth example:

1) <var> and <assign> tags are not finished with slash
2) New objects are not declared with: expr="new Object()" [line 5 and 
line 9] or are not declared at all (e.g obj1.prop2 is not explicitly 
created)
3) There is an apostrophe missing on line 12 after "'my.complex.event

In section 11.3 outbound_greetings.vxml:

1) [line 15 and 19] value is assigned to variables using wrong syntax
    Instead of <assign ... value=...> there should be <assign ... expr=...>
    Also the value of expr attribute should be in apostrophes.

In section 11.3 holdmusic.vxml:

1) [line 5] Instead of <prompt bargin="false"> there should be <prompt 
bargein="false">

In Appendix D, section 11 VoiceXML 2.0 Example

1) [line 64] there is transition with nonexistent event: 
connection.disconnect
    There should be connection.disconnected
2) [line 180] unjoined is called with attribute duplex="full"
    unjoin does not have duplex attribute
3) [line 189] join is called with attribute duplex="full"
    duplex value is expression and therefore duplex="'full'" should be used


Thanks for your response.
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, 31 May 2007 08:38:08 UTC