Media Fragments Working Group: Agenda 19 August, Telecon 1200 UTC

Dear Media Fragmenters,

Please, find below the agenda for this week telecon 

I suggest to have either Jack or Yves for scribbing.

I have also cleaned  the tracker, postponing some of the actions as 
discussed during the last telecon. The current summary is at It would be great to 
clean the overdue actions.

As Silvia recently reminded us, our charter expires in Jan 2010, and we 
need to move on quickly to LC and progress at the same time on 
implementations. Targeting short term demo (for the temporal dimension, 
using HTML5) seems to be a very good idea. I suggest we aim at sorting 
out the UA / HTTP communication (ACTION-69) during the next 2 telecon so 
be prepared for discussion.
Best regards.

   Erik & RaphaŽl


AGENDA Teleconference
W3C Media Fragments Working Group telephone conference 2009-08-19
Wednesday, 19 August *12:00-13:00 UTC*
Local time: 

19 August 2009, 1200 UTC
              0500 (West US)
              1300 (Galway)
              1400 (Amsterdam, Sophia-Antipolis, Pretoria)
              2100 (Tokyo)
              2200 (Sydney)
Bridge US: +1-617-761-6200 (Zakim)
Bridge FR: +
Bridge UK: +44.117.370.6152
Conference code : 3724# (spells "FRAG")
Duration : 60 minutes
IRC channel          : #mediafrag on
W3C IRC Web Client   :
Other clients are listed at
Zakim information    :
Zakim bridge monitor :
Zakim IRC bot        :

Chair: Raphael
Scribe: Jack (On Deck: Yves)
Regrets: Erik

Please note that Media Fragments WG telecons are for attendance by
members and invited experts only.

* Roll call
* PROPOSED to accept the minutes of the 12 August 2009 telecon:
* Next WG gathering:
   - 17-18 September: F2F in Amsterdam or Virtual Meeting?
   - 2-6 November: TPAC week in Santa Clara (CA, USA)
* ACTION-92: Erik and Raphael to coordinate the writing of papers 
(ongoing ... re-raise around 15/09/09)

* Use Cases and Requirements WD review:
   - Media Annotations WG:
   - TimedText, SVG, HTML5+WHATWG: (member only)
   - TAG: Yves?
* ACTION-94: Silvia to write specification for streaming use case
* ACTION-95: Michael to review the new UC written by Silvia and check 
whether it will cover a mobile usage


3.1 Syntax: (Yves)
* ACTION-49: Yves to Draft the HTTP-Range syntax for different units
(completing all the syntax for the two way handshake) (ongoing ... 
re-raise around 30/08/09, after IANA ratification?)
* ACTION-96: Yves to make change to temporal-optional-comma specification
** Done:
* Discussion: should we allow editUnits for specifying the temporal 
dimension? (see:

3.2 UA Server HTTP Communication (Conrad/Raphael)
* ACTION-69: Conrad to draw a representation of the general structure of
a media resource, for streamable formats

4. TEST CASES: (Michael)
* See:
* Discussion: Jack objects about the lack of coherency between returing 
the full asset for 2 dimensions (track, id), and an error for the 2 
others (time, space)
* ACTION-93: Michael to revisit the TC and see which are affected by the 
* Michael to add TC0010, TC0011 and TC0012 to the Test Cases page per WG 


5.1 Active:
* ISSUE-3 [Michael]: Does our MF URI syntax imply that we need to update
MIME Type registrations?
** ACTION-89: Yves to find out more about fragment identifier 
registration (ongoing ... re-raise around 15/08/09, after IETF Meeting)
* ISSUE-6 [Jack]: Temporal clips that require transcoding
** ACTION-62: Yves to ask the TAG whether transcoding should be
forbidden or not when we send a fragment of a resource
** Done: 
(+ thread). How to restart the discussion? Ask Noah to have an item 
during the next call?
* ISSUE-9 [Michael]: Should we have the media type inside the Test Cases?
** ACTION-82: Michael to flesh out TC vocabulary re ISSUE-9
* ISSUE-11 [Silvia]: How the UA knows the full media duration when only 
a fragment is served?

5.2 Non-Active:
* ISSUE-4 [Silvia]: Should we pre-define some track names?
* ISSUE-5 [Jack]: Handling spatial cropping requires information at
* ISSUE-7 [Michael]: User Agent Media Fragment Resolution and Processing

* ACTION-34: Jack to look at python-url library to see whether he could
implement the logic on client side
* ACTION-35: Raphael to look at curl and/or wget to see whether the
logic could be implemented on client side
* ACTION-70: Jack to commit in CVS (code directory) his python code
doing the parsing on client side of the media fragment
* ACTION-71: Michael to investigate whether he could have an
implementation in Javascript that does the client-side media fragments
* ACTION-90: Davy to provide a pointer to Yves to a lib he can use to 
slice media files

7. AOB

RaphaŽl Troncy
CWI (Centre for Mathematics and Computer Science),
Kruislaan 413, 1098 SJ Amsterdam, The Netherlands
e-mail: &
Tel: +31 (0)20 - 592 4093
Fax: +31 (0)20 - 592 4312

Received on Tuesday, 18 August 2009 13:56:35 UTC