- From: Vickers, Mark <Mark_Vickers@cable.comcast.com>
- Date: Fri, 23 Aug 2013 19:29:45 +0000
- To: Giuseppe Pascale <giuseppep@opera.com>
- CC: public-web-and-tv <public-web-and-tv@w3.org>
Looks good to me. Thanks! mav On Aug 21, 2013, at 2:38 AM, Giuseppe Pascale <giuseppep@opera.com> wrote: > ** with this mail I'm carrying out ACTION-130 ** > > Hi all, > during last Media APIs TF call, we agreed to work in iterations, in order to be able to progress those use cases that are more mature while leaving more time to those items that need further discussion. > > Here is a proposal on how to work and also a possible timeline for the current iteration and the following ones. This is for discussion during todays call. > > Each iteration could look like this: > > Phase 1: collect use cases > Phase 2: generate requirements > Phase 3: gap analysis: are there existing spec covering this requirements already? If not, which specs/WGs would need to be addressed to fill these gaps? > Phase 4: consolidate UCs, reqs and gap analysis in one document and discuss next steps (reach out to WGs, etc) > > For the first iteration of this process, I propose the following deadlines: > > Aug 28th: last chance to submit UCs for inclusion in the first iteration > Sept 4th (conf call): discuss and agree on the final list of use cases included in the first iteration > Oct 2nd (conf call): finalize and agree a list of requirements derived from the use cases > Oct 30th (conf call): finalize gap analysis > 12th of November (TPAC): review and approve the WG note including UCs, Req. and Gap analysis and discuss next steps. > > > /g > > > >
Received on Friday, 23 August 2013 19:30:34 UTC