ISSUE-26: timely event delivery
timely event delivery
- State:
- CLOSED
- Product:
- MMI Architecture
- Raised by:
- James Barnett
- Opened on:
- 2006-10-30
- Description:
- add requirement on transport mechanism for timely event delivery
- Related Actions Items:
- No related actions
- Related emails:
- [f2f] minutes Monday 14 June AM 2 (from paolo.baggia@loquendo.com on 2010-06-14)
- ISSUE-95 (EMO-26): Consider making media type explicit in <link> [EmotionML] (from sysbot+tracker@w3.org on 2009-11-02)
- Re: [emo] Issues in EmotionML (from ashimura@w3.org on 2009-10-31)
- [emo] Issues in EmotionML (from schroed@dfki.de on 2009-10-30)
- ISSUE-26: timely event delivery [MMI Architecture] (from dean+cgi@w3.org on 2006-10-30)
Related notes:
I think Dan\'s suggestion to outline what is unacceptable might be the way to go.
Something like \"Event delivery should not be so untimely as to render
multimodal applications unusable. I.e., RFC 1149 is not acceptable.\".
We discussed this issue at the F2F (14 June, AM2) in Somerset and decided to close the issue as it will not be testable.
Ingmar Kliche, 14 Jun 2010, 15:29:21Display change log
