Media Fragments Working Group: Agenda 09 June, Telecon 0900 UTC

Dear Media Fragmenters,

Please, find below the agenda for this week telecon
Actions opened:

I have to send regrets for this week again since I will be in a 
conference. This is the last telecon before the F2F meeting so 
discussion should happen regarding the agenda. Jakub who has implemented 
the Media Fragments URI plugin for firefox will be here on Tuesday 
morning, so I suggest we start with a demo and technical explanation of 
this implementation ...
Best regards.

   Erik & RaphaŽl


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

09 June 2010, 0900 UTC
               0200 (West US)
               1000 (Galway)
               1100 (Amsterdam, Sophia-Antipolis, Pretoria)
               1800 (Tokyo)		
               1900 (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   : and
Zakim information    :
Zakim bridge monitor :
Zakim IRC bot        :

Chair: Erik
Scribe: Silvia (On Deck: Conrad, Michael)
Regrets: Raphael, Yves

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 02 June 2010 telecon:
* ACTION-119: Yves to request admins to set up a cvs notifications 
mailing list and notifications

2. F2F Meeting Agenda

* ACTION-169: Yves to reserve the bridge for 15&16 June mediafrag f2f


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


4.1 Media Fragment URI syntax: (Yves)
* 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

3.2 Protocol for URI fragment Resolution in HTTP:
* ACTION-160: Yves to send an email reporting the issue for track names
* ACTION-137: Jack to check that section 5.2 is implementable using the 
* ACTION-166: Yves  to review the ABNF syntax of the HTTP headers 
introduced by the Media Fragment URI spec
* ACTION-170: Yves to send an email about metadata headers and 206 responses

3.3 Rendering of Media Fragments URI in UA:
* ISSUE-5 [Jack]: Handling spatial cropping requires information at
* Image sprite in HTML5:

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
** See also:
* 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
* ACTION-167: Erik to find license free movies for the automatic test 
suite ... starting with Elephant Dreams and the creative commons
* ACTION-168: Davy to investigate how the automatic test suite could 
also be done for evaluating the UA behavior
* 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 Monday, 7 June 2010 22:16:21 UTC