ISSUE-32: Create Request/Response events

Create Request/Response events

State:
CLOSED
Product:
MMI Architecture
Raised by:
James Barnett
Opened on:
2007-01-15
Description:
In the current life cycle events, \'Data\' is provided as the catch-all vehicle
for application-specific events. But given its name and the fact that it
doesn\'t expect a response, it seems primarily an Update or Notification event.
Another class of application-specific events is Request/Response pairs. Perhaps
we should introduce new life-cycle events to cover them.
Related Actions Items:
No related actions
Related emails:
  1. ISSUE-101 (EMO-32): List of valid discrete scale values [EmotionML] (from sysbot+tracker@w3.org on 2009-11-02)
  2. Re: [emo] Issues in EmotionML (from ashimura@w3.org on 2009-10-31)
  3. [emo] Issues in EmotionML (from schroed@dfki.de on 2009-10-30)
  4. ISSUE-32: Create Request/Response events [MMI Architecture] (from dean+cgi@w3.org on 2007-01-15)

Related notes:

This was discussed during the April 30, 2007 call.
(minutes -- http://lists.w3.org/Archives/Member/w3c-mmi-wg/2007Apr/0056.html)
We agreed that we need the following focus “synchronization� events:
We agreed that there should be:
* a \"notify\" event from modality to IM to notify of a change in focus
* a \"request\" event from IM to modality component to request a change
in focus
* a \"response\" event from modality component to IM

These should be standard events because they will be needed by
many applications (perhaps not all applications will need
synchronization, so they don’t need to use these events; but there are
enough applications that will use these events that they should be made
standard events.)
We may decide to call these synchronization events.
These should a subclass of life cycle events that inherit the
attributes of life cycle events (e.g. \"Error\", \"ContextID\", \"Data\"...)

30 Apr 2007, 00:00:00

The LC extension event is designed to allow async communication/starting of MC component processes. There is no need for responses. This decision was made at the face-to-face session.

Joseph Paparella, 4 Mar 2008, 16:59:15

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 32.html,v 1.1 2017/02/13 15:50:59 ted Exp $