W3C home > Mailing lists > Public > public-media-fragment@w3.org > March 2010

Re: [ERRATA] Media Fragments Working Group: Agenda 17 March, Telecon *0900 UTC*

From: Yves Lafon <ylafon@w3.org>
Date: Tue, 16 Mar 2010 12:23:58 -0400 (EDT)
To: raphael.troncy@eurecom.fr
cc: Media Fragment <public-media-fragment@w3.org>, Erik Mannens <erik.mannens@ugent.be>
Message-ID: <alpine.DEB.1.10.1003161223430.12875@wnl.j3.bet>
On Tue, 16 Mar 2010, RaphaŽl Troncy wrote:

> Dear all,
>
> [ERRATA]: tomorrow's telecon is at 09:00 UTC due to the change of the US 
> clock last week-end. Which means, *one hour earlier* for most of us:
>  0200 (West US)
>  0900 (Galway)
>  1000 (Amsterdam, Sophia-Antipolis, Pretoria)
>  1800 (Tokyo)
>  2000 (Sydney)

Potential regrets.

> Best regards.
>
>  RaphaŽl
>
> Le 16/03/2010 14:15, RaphaŽl Troncy a ťcrit :
>> Dear Media Fragmenters,
>> 
>> Please, find below the agenda for this week telecon
>> http://www.timeanddate.com/worldclock/fixedtime.html?day=10&month=03&year=2010&hour=10&min=00&sec=0&p1=0
>> 
>> Actions opened:
>> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/open
>> 
>> We have 24 hours to complete more actions, so please *do*! I suggest
>> that this week, we mainly talk about the clarifying ABNF syntax of the
>> media fragments URI (Yves) + accompanying processing text from Philip in
>> order to agree on this piece. Silvia, thanks a lot for your valuable
>> input regarding the combination of multiple dimensions in the URI. I
>> suggest we made a topic for next week telecon ... where we should also
>> decide to publish another round of documents.
>> Best regards.
>> 
>> Erik & RaphaŽl
>> 
>> ------------
>> 
>> AGENDA Teleconference
>> W3C Media Fragments Working Group telephone conference 2010-03-10
>> -----------------------------------------------------------------
>> Wednesday, 10 March *10:00-11:00 UTC*
>> Local time:
>> http://www.timeanddate.com/worldclock/fixedtime.html?day=10&month=03&year=2010&hour=10&min=00&sec=0&p1=0
>> 
>> 
>> 10 March 2010, 1000 UTC
>> 0200 (West US)
>> 1000 (Galway)
>> 1100 (Amsterdam, Sophia-Antipolis, Pretoria)
>> 1900 (Tokyo)
>> 2100 (Sydney)
>> Bridge US: +1-617-761-6200 (Zakim)
>> Bridge FR: +33.4.89.06.34.99
>> Bridge UK: +44.117.370.6152
>> Conference code : 3724# (spells "FRAG")
>> Duration : 60 minutes
>> -------------------------------------------------------------------
>> IRC channel : #mediafrag on irc.w3.org:6665
>> W3C IRC Web Client : http://www.w3.org/2001/01/cgi-irc
>> Other clients are listed at http://www.w3.org/Project/IRC/#Client
>> Zakim information : http://www.w3.org/2002/01/UsingZakim
>> Zakim bridge monitor : http://www.w3.org/1998/12/bridge/Zakim.html
>> Zakim IRC bot : http://www.w3.org/2001/12/zakim-irc-bot.html
>> -------------------------------------------------------------------
>> 
>> Chair: Raphael, Erik
>> ScribeList: http://www.w3.org/2008/WebVideo/Fragments/wiki/ScribeList
>> Scribe: Conrad (On Deck: Silvia, Michael)
>> Regrets:
>> 
>> Please note that Media Fragments WG telecons are for attendance by
>> members and invited experts only.
>> 
>> 1. ADMIN:
>> * Roll call
>> * PROPOSED to accept the minutes of the 03 March 2010 telecon:
>> http://www.w3.org/2010/03/03-mediafrag-minutes.html
>> * PROPOSED to accept the minutes of the 5th F2F meeting:
>> http://www.w3.org/2010/03/08-mediafrag-minutes.html
>> http://www.w3.org/2010/03/09-mediafrag-minutes.html
>> 
>> * 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
>> 
>> 2. USE CASES & REQUIREMENTS
>> 
>> * ACTION-156: Conrad to add a "bandwidth conservation use case"
>> 
>> 3. SPECIFICATION:
>> 
>> 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
>> dimension
>> * ISSUE-5 [Jack]: Handling spatial cropping requires information at
>> client-side
>> 
>> 3.4 Discovery of 'Track' and 'Named' fragments:
>> * ISSUE-4 [Silvia]: Should we pre-define some track names?
>> * Davy's strawman implementation using ROE:
>> http://lists.w3.org/Archives/Public/public-media-fragment/2009Nov/0014.html
>> * Silvia's blog post:
>> http://blog.gingertech.net/2009/11/25/manifests-exposing-structure-of-a-composite-media-resource/
>> 
>> * 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: http://ld2sd.deri.org/corrib/
>> * 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:
>> http://lists.w3.org/Archives/Public/public-media-fragment/2009Dec/0015.html
>> 
>> 5. ISSUES
>> 
>> 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
>> 
>> 6. IMPLEMENTATION:
>> * 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
>> 
>
>

-- 
Baroula que barouleras, au tiťu toujou t'entourneras.

         ~~Yves
Received on Tuesday, 16 March 2010 16:24:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:38 GMT