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

Media Fragments Working Group: Agenda 20 January, Telecon 1000 UTC

From: RaphaŽl Troncy <raphael.troncy@cwi.nl>
Date: Wed, 20 Jan 2010 10:08:57 +0100
Message-ID: <4B56C829.2010201@cwi.nl>
To: Media Fragment <public-media-fragment@w3.org>
CC: Erik Mannens <erik.mannens@ugent.be>
Dear Media Fragmenters,

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

Best regards.

Erik & RaphaŽl


AGENDA Teleconference
W3C Media Fragments Working Group telephone conference 2010-01-20
Wednesday, 20 January *10:00-11:00 UTC*
Local time:

20 January 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: +
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: RaphaŽl
ScribeList: http://www.w3.org/2008/WebVideo/Fragments/wiki/ScribeList
Scribe: Guillaume (On Deck: 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 13 January 2009 telecon:
* Charter Extension:
** ACTION-127: Yves to look for the charter extension
* Next F2F Meeting:
** ACTION-128: Erik to poll Silvia, Conrad, Guillaume, and Michael 
regarding the new proposed date for the next F2F
** See also: 
** Results (missing Conrad, Silvia, Michael, Guillaume):
   . Seoul (feb 23-25): 1 present (Erik) + 3 remotes (Davy, Raphael, 
Phiilip) + 1 absent (Jack)
   . Amsterdam (mar 8-9): 4 present (Erik, Davy, Jack, Raphael) + 1 
remote (Philip)
* ACTION-92: Erik and Raphael to coordinate the writing of papers
** Target is MTAP SI on Semantic Multimedia, 
http://www.samt2009.org/sites/default/files/mtap_cfp_flyer_v1.pdf, Erik 
will circulate a draft version soon.


2.1 Media Fragment URI syntax: (Yves)
* Bug in the npt specification found by Philip:
"I'd also like to point out that the ABNF for NPT does not match
RFC2326. It allows there to be 0 or more digits following the decimal
point, while the MF ABNF allows 1 or more digits."
* ACTION-126: Yves to follow up on error in ABFN for npt

2.2 UA Server HTTP Communication: (Conrad/Raphael)
* ACTION-123: Yves to come up with ABNF for header syntax
* ACTION-125: Michael to revisit his ednote in section 5

2.3 Media Fragment Processing:
* Question of MF URI validity by Philip:
* Suggestion of nasty test cases by Philip:

2.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

2.5 Handling of 'Track' and 'ID':
Conrad's proposal (Fragment header):

3. TEST CASES: (Michael)
* Corrib test tool: http://ld2sd.deri.org/corrib/ * ACTION-108: Michael 
to add the missing test cases in corrib
* ACTION-115: Michael to come up with categorization of test cases wrt
empty, undefined, etc
* ACTION-118: Michael to come up with individual 'normal' test cases (+/-20)
* ACTION-119: Yves to request admins to set up a cvs notifications 
mailing list and notifications

* 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 


5.1 Active:

5.2 Non-Active:
* ISSUE-5 [Jack]: Handling spatial cropping requires information at
* 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

6. AOB

RaphaŽl Troncy
EURECOM, Multimedia Communications Department
2229, route des CrÍtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~troncy/
Received on Wednesday, 20 January 2010 09:09:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:44 UTC