| wrong direction [message #3541] |
Tue, 26 October 2004 16:38  |
Eclipse User |
|
|
|
Originally posted by: ross.siberiancellars.com
It seems to me that the direction of the Voice tools is at too low of a
level. That is, it is just VXML/CCXML and etc syntax editors. I believe
that you really want something higher level and that the speech application
developer should not care that vxml is the underlying technology. VXML is
really an platform independent protocol that allow an application to run on
multiple platforms (in theory) with out change. Like in web services one
does not write in SOAP xml though you could.
Ross
|
|
|
| Re: wrong direction [message #3575 is a reply to message #3541] |
Tue, 26 October 2004 17:30  |
| Eclipse User |
|
|
|
Although many organizations choose to use abstraction runtimes or tooling
there are many organizations that write all of their speech applications
natively in VoiceXML. To that end many people work hard in standard bodies
to ensure that VoiceXML does not become simply a normalization layer. The
goal of the project proposal is initially focused on providing editors for
those that work with standard markups. In the future, the scope of the
project could grow to provide some of the functionality you describe,
especially if commitments of development resources can be made. By focusing
on the standard markups we provide the seed around which other tooling can
emerge in a future project plan such as simulation, debugging, analysis,
deployment, tuning, pronounciation support, and yes, higher level tooling.
"Ross Yakulis" <ross@siberiancellars.com> wrote in message
news:cllu7q$qms$1@eclipse.org...
> It seems to me that the direction of the Voice tools is at too low of a
> level. That is, it is just VXML/CCXML and etc syntax editors. I believe
> that you really want something higher level and that the speech
> application developer should not care that vxml is the underlying
> technology. VXML is really an platform independent protocol that allow an
> application to run on multiple platforms (in theory) with out change.
> Like in web services one does not write in SOAP xml though you could.
|
|
|
| Re: wrong direction [message #571225 is a reply to message #3541] |
Tue, 26 October 2004 17:30 |
| Eclipse User |
|
|
|
Although many organizations choose to use abstraction runtimes or tooling
there are many organizations that write all of their speech applications
natively in VoiceXML. To that end many people work hard in standard bodies
to ensure that VoiceXML does not become simply a normalization layer. The
goal of the project proposal is initially focused on providing editors for
those that work with standard markups. In the future, the scope of the
project could grow to provide some of the functionality you describe,
especially if commitments of development resources can be made. By focusing
on the standard markups we provide the seed around which other tooling can
emerge in a future project plan such as simulation, debugging, analysis,
deployment, tuning, pronounciation support, and yes, higher level tooling.
"Ross Yakulis" <ross@siberiancellars.com> wrote in message
news:cllu7q$qms$1@eclipse.org...
> It seems to me that the direction of the Voice tools is at too low of a
> level. That is, it is just VXML/CCXML and etc syntax editors. I believe
> that you really want something higher level and that the speech
> application developer should not care that vxml is the underlying
> technology. VXML is really an platform independent protocol that allow an
> application to run on multiple platforms (in theory) with out change.
> Like in web services one does not write in SOAP xml though you could.
|
|
|
Powered by
FUDForum. Page generated in 0.02638 seconds
] 
Search
Help
Register
Login
Home
