User Interface Service Software Developerís Guide - Hitech Projects

January 2008
Public
actionDesc
increase
increase
argumentDesc
Continuous_Scale
That’s for the initialization part. The actual scenario contains these kinds of elements:
• gesture, gestureSignal, gestureCancel
• sentence, sentenceSignal, sentenceCancel
• selection, selectionSignal, selectionCancel
Each “*Signal” and “*Cancel” elements are parameterized by a “time” argument stating when
to send the corresponding signal to the MFM, based on the start time of the scenario. Other
elements have “start” and “end” parameters, for corresponding parameters of the MFM
interface’s methods. These methods are invoked at the time specified by the “end” parameter.
Those elements contain a MMIL message, which is sent as content in the method calls. As
seen in the example scenario, the MMIL component is simply embedded between
and tags (sentence can be replaced by selection or gesture).
When the MFM receives several messages from different modalities (and, actually even if it
receives only one message) in a given time window, it tries to unify commands’ references and
objects’ references into one unique functional application (with the command as the function
and the objects as arguments). Then, it completes the original messages with information from
this unique functional application, and publishes all of them at once as an OSGi event. In order
to receive this information, services must subscribe to the MFM subscription service for the
“fusionEvent” event.
3.4.4 Dialogue Manager
A full usage and developers guide for the backend of the Dialogue Manager (PEGASUS) is
available at gforge, in the document called “Pegasus-Manual.pdf”.
Amigo IST-2004-004182 94/114