Media Fragments Working Group: Agenda 31 March, Telecon 0900 UTC

Dear Media Fragmenters,

[Apologies for this late notice]
Please, find below the agenda for this week telecon
Actions opened:
We are back to the same hour than before for the Europeans ... but not 
yet for Silvia and Conrad :-( Do you have daylight saving times?

The agenda is actually the same than 2 weeks ago when we canceled the 
telecon. We must decide what we publish by the end of the week.
Best regards.

Erik & RaphaŽl


AGENDA Teleconference
W3C Media Fragments Working Group telephone conference 2010-03-31
Wednesday, 31 March *09:00-10:00 UTC*
Local time:

31 March 2010, 0900 UTC
               0200 (West US)
               1000 (Galway)
               1100 (Amsterdam, Sophia-Antipolis, Pretoria)
               1800 (Tokyo)		
               2000 (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: Conrad (On Deck: Silvia, Michael)
Regrets: Erik, Davy

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 03 March 2010 telecon:
* PROPOSED to accept the minutes of the 5th F2F meeting:

* ACTION-119: Yves to request admins to set up a cvs notifications 
mailing list and notifications
* ACTION-92: Erik and Raphael to coordinate the writing of papers
** Postpone (new deadline is May 1st 2010)

* Next WG F2F:
  - 25-30 April in Raleigh, collocated with WWW (HTML5 Track?)
  - 01-03 June in Heraklion, collocated with ESWC
  - 14-16 June in Sophia Antipolis/Amsterdam
  - 25-26 or 28-29 June in New York, collocated with FOMS+OVC


* ACTION-156: Conrad to add a "bandwidth conservation use case"


3.1 Media Fragment URI syntax: (Yves)

* ACTION-151: Yves to modify the production rule for the track dimension 
in order to allow multiple semi-colon separated values
* ACTION-152: Yves to change the formal syntax to reflect that we don't 
need a subdelim for selecting multiple tracks but we allow multiple 
track= in the URI
* ACTION-153: Raphael to review the complete document and check whether 
there are more references to uniqueness

3.2 Protocol for URI fragment Resolution in HTTP:
* ACTION-123: Yves to come up with ABNF for header syntax
* ACTION-154: Yves to add a section 5.2.4 describing his new optimization
* ACTION-137: Jack to check that 5.1 is implementable using the protocol
* ACTION-155: Davy to draw diagrams to include in the spec, similar to 
Yves's email, that shows which bytes from the headers and body of the 
media file are sent

3.3 Rendering of Media Fragments URI in UA:
* ACTION-135: Davy, Erik to extend section 7 regarding spatial and track 
* ISSUE-5 [Jack]: Handling spatial cropping requires information at

3.4 Discovery of 'Track' and 'Named' fragments:
* ISSUE-4 [Silvia]: Should we pre-define some track names?
* Davy's strawman implementation using ROE:
* Silvia's blog post: 

* Jack's proposal to write up that we should distinguish the mechanism 
(ROE, MPEG-21) vs the semantics

4. TEST CASES: (Michael)
* Corrib test tool:
* ACTION-146: Jack to identify and add in corrib any missing test cases 
for temporal fragments 	
* ACTION-158: Raphael to enter the big table of all test cases for the 
temporal dimension in the wiki
* ACTION-147: Michael to add all MF WG members to corrib
* ACTION-148: Michael to add a copy TC functionality in corrib
* ACTION-149: Michael to come up with a fix for overview vs. edit single 
TC in corrib
* Suggestion of nasty test cases by Philip:


5.1 Active:

5.2 Non-Active:
* ISSUE-6 [Jack]: Temporal clips that require transcoding
* ISSUE-7 [Michael]: User Agent Media Fragment Resolution and Processing
* ISSUE-9 [Michael]: Should we have the media type inside the Test Cases?
* 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
* ISSUE-14 [Davy]: How to deal with embedded time stamps
* ISSUE-16 [Jack]: Combining axis is probably not going to be done by 
LC, but we should write somewhere that this is doable

* 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
* Someone to investigate whether he could have an implementation in 
Javascript that does the client-side media fragments parsing?

7. AOB

RaphaŽl Troncy
EURECOM, Multimedia Communications Department
2229, route des CrÍtes, 06560 Sophia Antipolis, France.
e-mail: &
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200

Received on Wednesday, 31 March 2010 06:42:45 UTC