Media Fragments Working Group: Agenda 15 July, Telecon 1200 UTC

Dear Media Fragmenters,



Please, find below the agenda for today's telecon, and apologies for this
late advert.



Best regards.



RaphaŽl (regrets) & Erik




AGENDA Teleconference

W3C Media Fragments Working Group telephone conference 2009-07-15


Wednesday, 15 July *12:00-13:00 UTC*

Local time:



15 July 2009, 1200 UTC

              0500 (West US)

              1300 (Galway)

              1400 (Amsterdam, Paris, 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: Erik


Scribe: ?

Regrets: RaphaŽl, Jack


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 10 June 2009 telecon:




* ACTION-68: Raphael to ask the Media Annotations WG to review our document

* ACTION-74: Erik and Raphael to request feedback of other groups such

as SYMM, SVG, HTML + WHATWG, WAI, MAWG, TAG, MobileWeb, TimedText

* ACTION-65: Raphael to split current document into i) UC and Req and

ii) Syntax and Processing and setup the diff in xmlspec 





3.1 Syntax: (Yves)

* ACTION-49: Yves to Draft the HTTP-Range syntax for different units

(completing all the syntax for the two way handshake)

* ACTION-84: Erik to
<> summarize the
info from Jean Pierre, and mail it to the group [Sync with Jean Pierre to
get the edit units spec reference]

* ACTION-86: Raphael to bring the 'comma optional' discussion during next
week telecon, in order to measure the price when releasing the syntax


3.2 UA Server HTTP Communication (Conrad/Raphael)

* ACTION-63: Conrad to update the Wiki with his more general approach

with precisely the same examples

* ACTION-69: Conrad to draw a representation of the general structure of

a media resource, for streamable formats

* ACTION-80: Conrad to provide some rational and use cases for his proposal


3.3 UA MF Resolution and Processing: (Michael)

* ACTION-64: Michael to write into the WD section 6.4, what the client

should do with #everything after the hash : "Client Side Media Fragment

Resolution" (See also ISSUE-7)

* ACTION-85: Michael to update resolution page, TC pages with that
resolution [consensus that 416 is the correct response when the TC returns



4. TEST CASES: (Michael)

* See:

* ACTION-87: Michael to
<> add the HTTP
status code for all TC




* ISSUE-3 [Michael]: Does our MF URI syntax imply that we need to update

MIME Type registrations?

** ACTION-76: Erik to contact the editors of MPEG-21 Part 17 regarding

the registry of their scheme


* ISSUE-5 [Jack]: Handling spatial cropping requires information at



* 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


* ISSUE-9 [Michael]: Should we have the media type inside the Test Cases?

** ACTION-82: Michael to flesh out TC vocabulary re ISSUE-9


Can be closed?

* ISSUE-4 ( <>
Should we pre-define some track names?)

* ISSUE-10 ( <>
Media Fragments Test Case Maintenance ) [Michael]




* 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




7. AOB


Received on Wednesday, 15 July 2009 09:24:53 UTC