ISSUE-38: Details of Media Stream handling in life cycle events

Details of Media Stream handling in life cycle events

State:
CLOSED
Product:
MMI Architecture
Raised by:
Deborah Dahl
Opened on:
2007-04-03
Description:
The Voice Browser WG would like the architecture document to go into more
detail about media stream handling as it pertains to the life cycle events.
Related Actions Items:
Related emails:
  1. [all] MMI minutes MMI - 16 August 2010 (from ashimura@w3.org on 2010-08-17)
  2. [all] minutes MMI call - 9 Aug 2010 (from Ingmar.Kliche@telekom.de on 2010-08-09)
  3. [all] MMI agenda August 9, 2010 (from dahl@conversational-technologies.com on 2010-08-06)
  4. [arch] updated editors draft (ISSUE-38, ACTION-124) (from Ingmar.Kliche@telekom.de on 2010-08-02)
  5. [all] reminder, no call August 2, agendas for August 9-September 20 (from dahl@conversational-technologies.com on 2010-07-31)
  6. [all] MMI minutes July 26, 2010 (from dahl@conversational-technologies.com on 2010-07-26)
  7. [arch] allow <media> element in all lifecycle events (ISSUE-38) (from Ingmar.Kliche@telekom.de on 2010-07-26)
  8. [arch] clarification text for media handling (ISSUE-38) (from Ingmar.Kliche@telekom.de on 2010-07-26)
  9. [all] MMI agenda July 26, 2010 (from dahl@conversational-technologies.com on 2010-07-23)
  10. MMI call cancelled (was RE: [all] MMI agenda July 19, 2010) (from dahl@conversational-technologies.com on 2010-07-19)
  11. [all] MMI agenda July 19, 2010 (from dahl@conversational-technologies.com on 2010-07-18)
  12. [all] agenda MMI call July 12, 2010 (from dahl@conversational-technologies.com on 2010-07-09)
  13. [all] reminder, no call July 5, agendas July 12-September 20, 2010 (from dahl@conversational-technologies.com on 2010-07-02)
  14. [all] MMI agenda June 28, 2010 (from ashimura@w3.org on 2010-06-28)
  15. [all] reminder, no MMI call today and list of dates for presentations (from dahl@conversational-technologies.com on 2010-06-21)
  16. [f2f] minutes Monday 14 June AM 2 (from paolo.baggia@loquendo.com on 2010-06-14)
  17. ISSUE-137: Ensure that all reasonable kickoff orders are supported by the MMI spec [MMI Architecture] (from sysbot+tracker@w3.org on 2010-06-14)
  18. ISSUE-107 (EMO-38): Embed definition of custom vocabulary inside <emotionml> document? [EmotionML] (from sysbot+tracker@w3.org on 2009-11-02)
  19. Re: [emo] Issues in EmotionML (from ashimura@w3.org on 2009-10-31)
  20. [emo] Issues in EmotionML (from schroed@dfki.de on 2009-10-30)
  21. [all] minutes (early hour & main call) - 8 December 2008 (from ashimura@w3.org on 2008-12-09)
  22. Re: [emma] resolution of open issues in issue tracker (from ashimura@w3.org on 2007-10-31)
  23. [emma] resolution of open issues in issue tracker (from johnston@research.att.com on 2007-10-29)
  24. ISSUE-38: Details of Media Stream handling in life cycle events [MMI Architecture] (from dean+cgi@w3.org on 2007-04-03)

Related notes:

In addition, the specification should specifically mention that media streams (e.g., video input sent to a video display) does not necessarily flow through the Interaction Manager; media connections can be directly made between components.

The specification should also note that (at present) the specification does not specify how to make media connections and that our concern is with the flow of control data: all control data sent between Media Components flows through the Interaction Manager.

Moshe Yudkowsky, 26 Nov 2007, 16:56:15

From the May 19 call: There are three questions: (1) How to communicate to the various modality components what end points they should be communicating with. (2) There is a second question of negotiating media streams. (3) Once media streams are established, how do we pass that info among modality components?

James Barnett, 19 May 2008, 19:06:13

12/08/08
In case there is a need for a quicker response, wrappers should be put around the components, allowing for direct communication.

Deborah Dahl, 8 Dec 2008, 16:34:18

See Raj's document: http://lists.w3.org/Archives/Member/w3c-mmi-wg/2008Jul/0045.html

Deborah Dahl, 11 Dec 2008, 15:34:32

We discussed this issue at the F2F in Somerset (June 14, AM2) and decided to add some text for clarification to the spec (based on Moshes comment). We discussed, whether the <media> element should be added to other lifecycle events, such as the startReq (e.g. if the IM kicks of components such as VUI) or the pauseReq (e.g. if the MC controls multiple media streams and the IM wants to pause a particular stream)

Ingmar Kliche, 14 Jun 2010, 15:56:21

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: 38.html,v 1.1 2017/02/13 15:50:59 ted Exp $