Media Fragments Working Group: Agenda 2 September, Telecon 1200 UTC

Dear Media Fragmenters,

We have an exciting telecon coming. Please, find below the agenda for
this week telecon: 

Jack will scribe (Yves is on deck).
We expect all the group participants, so if someone cannot make it,
please write Erik and I an email stating whether your unavailability is
due to a permanent bad scheduling (in case we have to change the telecon
time) or is just temporary.

Highlights will be: discussion on the role of # and ? and discussion on 
protocol (communication server - UA).

We have *some* actions opened:
ALL, please, give status update during the call so we can identify the
remaining bottlenecks.
Best regards.

   Erik & RaphaŽl


AGENDA Teleconference
W3C Media Fragments Working Group telephone conference 2009-09-02
Wednesday, 02 September *12:00-13:00 UTC*
Local time: 

02 September 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 26 August 2009 telecon:
* Next WG gathering:
   - 17-18 September: Virtual Meeting, see the poll results: (@Conrad, @Davy, @Dave, @Jack, 
@Philip, please, answer the questionnaire asap)
   - 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)

* ACTION-95: Michael to review ALL UC with a mobile hat on and check
whether these sufficiently cover the mobile usage
* ACTION-101: Yves to write a UC describing the use of aspect ratio
feature, and thus motivating its usage
* Use Cases and Requirements WD review:
   - Media Annotations WG:
   - TimedText, SVG, HTML5+WHATWG: (member only)
   - TAG: Yves ... re-raise around 01/09/09


3.1 Terminology: (Silvia)
* Change "URI" to "URI Reference" through the whole document since only
a URI ref can be relative?

3.2 Syntax: (Yves)
* Discussion 1: [proposal for resolution] we will *NOT* allow editUnits
for specifying the temporal dimension?
* Discussion 2: should we extend the syntax to have absolute time
specification that contains day and year (see RTSP RFC, section 3.7)
** Should we adopt HTML5/SMIL EBNF syntax?
* 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 01/09/09)

3.3 UA Server HTTP Communication (Conrad/Raphael)
* On the role of the '&' and the '#' in the Media Fragment
* ACTION-69: Conrad to draw a representation of the general structure of
a media resource, for streamable formats

4. TEST CASES: (Michael)
* Michael: we need to carefully define the three different error cases:
undefined/wrongly defined/not present; Might renumber the TC; See
whether the TC could be put into a table (with support from a
programmatic tool).
* ACTION-93: Michael to revisit the TC and see which are affected by the
* ACTION-99: Michael to add TC0010, TC0011 and TC0012 to the Test Cases
page per WG decision


5.1 Active:
* 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-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?

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
* ISSUE-12 [Raphael]: What's the relationship between Images (CSS)
Sprites and the spatial dimension of the Media Fragments URI scheme?
* ISSUE-13 [Raphael]: Write a IETF draft for proposing how to register
the fragment scheme for all media types

* 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, 1 September 2009 07:23:44 UTC