W3C

Edit comment LC-1918 for Ubiquitous Web Applications Working Group

Quick access to

Next: LC-1917

Comment LC-1918
:
Commenter: Debbie Dahl <dahl@conversational-technologies.com> on behalf of MMI WG

or
Resolution status:

Registration for events:
MMI Architecture allows Interaction Manager (IM) and Modality
Components( MC) to be distributed. And except in the case of
nested-modality components, modality components communicate with each
other only through the Interaction Manager. Given this principle of
MMI architecture, MMI authors would be required under the proposed
DCCI spec, to implement another DCCI-interface component to register
and obtain the local DCI events to pass on to IM for every device on
which any modality component is running..

For example, a device-client could be getting the text-to-speech
streamed from a TTS server. Now, if the user mutes the speaker on the
device, an event gets generated on the local device through DCI, but
the IM running on the server (a different device) will not get this
event to signal the TTS-component to stop streaming audio, as it will
not have a way to remotely register and get this event from the
device. So, under the proposed specification, an MMI author would be
forced to implement another MMI component just for passing on DCI
events to the IM. Please, note that the local Modality Component
cannot directly do this job, as the local Modality Components are to
be implemented as black-boxes and as such cannot snoop on these events
and determine which ones should be passed-on to the Interaction
Manager.

We would like to hear from DCI-WG on how this remote-registration for
events could be done, under the the current DCI framework.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 1918.html,v 1.1 2017/08/11 06:45:10 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org