CCXML feedback from Ecma TC32-TG11 CSTA

Liaison officer: Mr. Gerald McCobb, IBM
The Ecma TC32-TG11 (
http://www.ecma-international.org/memento/TC32-TG11.htm) has the following 
comments regarding CCXML (http://www.w3.org/TR/ccxml) and CSTA: 
Comment 1
Section 9.2.3 <send> 
9.2.3.1  The following sentence: 
<send> is used to send messages containing events or other information 
directly to another CCXML Interpreter other external systems using an 
Event I/O Processor. 
should be: 
<send> is used to send messages containing events or other information 
directly to another CCXML Interpreter or other external systems using an 
Event I/O Processor. 
Comment 2
>From Section 9.2.3, "Platforms may support other types of Event I/O 
Processors, for example: Web-services, SIP or basic HTTP GET. However, 
platforms SHOULD name the Event I/O Processor beginning with "x-" to 
signify that they are platform dependent." 
Ecma TC32-TG11 would prefer the standard name "csta" used for the CSTA 
event I/O processor.  Use of "csta" would formally specify compliance to 
the CSTA Phase III specifications, ECMA-269 6th edition and ECMA-323  3rd 
edition , XML Protocol for Computer Supported Telecommunications 
Applications (CSTA).  Use of "x-csta" would allow  a platform-dependent, 
noncompliant, version of CSTA to be specified.  Furthermore, use of the 
prefix "x-" when specifying a MIME type means it has not been registered 
with IESG.  Ecma TC32-TG11 has registered the "application/csta+xml" MIME 
type for ECMA standard compliant CSTA applications. 
Comment 3
The value of the CSTA namespace to use with the "csta" targettype in the 
included <send> example should be:  "
http://www.ecma-international.org/standards/ecma-323/csta/ed3" . 
Comment 4
Appendix A - Related Work 
The ECMA-CSTA section heading should be Ecma CSTA. 
Regarding the following paragraph: 
The architecture of CCXML would allow a platform to be based on CSTA for 
the underlying telephony protocol (similar to how a platform could be 
based on SIP or ISDN Q.931) while still providing the CCXML execution 
environment for ease of integration with voice browsers. 
Ecma TC32-TG11 finds the words between the parentheses to be confusing 
because there is an implied comparison between CSTA and SIP or ISDN Q.931 
communication protocols, which have a very different role and are targeted 
at different layers.  We would like the words between the parentheses 
removed. 

Regards,
Gerald McCobb
IBM
8051 Congress Avenue
Boca Raton, FL 33487
Tel. # 561-862-2109 T/L 975-2109