[vtp-dev] REMINDER: 15 September Eclipse Voice Tools Development Call

[Brent D Metz <bdmetz@xxxxxxxxxx>]

Hello,

This is a reminder that the next Eclipse
Voice Tools Development Call will take place on:

Thursday, September 15, 2005
11:00am ET  (http://www.timeanddate.com/worldclock/)
Duration: 1 hour
Dial-in numbers:  
   866-650-8398  (toll
free within US)
   210-516-7928 (toll call
within US)
Passcode: 4075904

Proposed Agenda:

1) Roll call
2) Review of project status
3) Presentation of draft Execution API
4) Discussion of Speech Engine API

--
Brent D. Metz
Enterprise Voice Tools
bdmetz@xxxxxxxxxx
"Simple things should be simple, and complex things should be possible."
- Alan Kay
Eclipse Voice Tools Development Call Minutes

September 8, 2005, 11am EST

Attendees:

Frederic Gloppe, HP
Brent D. Metz, IBM
Jeff Pedigo, SandCherry
Michael Greenawalt, TellMe
Andrew Wahbe, VoiceGenie

The call began with a summary of the "Milestone 0.7" build that was released. Instructions on
how to insert new code were made.

A discussion was held on a speech engine API design. Feature sets were discussed including
text simulation and text to speech. The point was raised that functionality should be minimal
to reflect what would be exercised by potential users of the the tool.

It was proposed that a media resource layer be part of the API in order to facilitate
cross-engine property settings such as automatically stopping a text to speech engine when
a recognizer detects speech input. It was agreed that a logical grouping of speech engines
should be a part of the API.

The topic of value adds in the platform such as a speech engine pool manager was brought up.
Since there is no immediate issue for which this would be a problem, it was left as a feature
for a future revision of the tooling and declared out of scope for an initial release.

The subject of standardized VoiceXML Browser events came up and it was noted that most eventing
could take advantage of pre-existing mechanisms in the Debug Event model such as declaring an
event model-specific with an object containing the pertinent voicexml-specific event data. The
question was raised as to whether or not VoiceXML browsers should be required to go through
a standardized API in order to throw these events or if they should be able to insert events
into the debug manager's event queue directly. It was decided that for the correct amount of
flexiblity and ease of implementation a utility class should be written to throw the events to
the debug event manager for clients.