Media Fragments Working Group Teleconference -- 29 Sep 2010

<scribe> ACTION: troncy to remind Jack and Michael to register asap for TPAC [recorded in http://www.w3.org/2010/09/29-mediafrag-minutes.html#action01]

<trackbot> Created ACTION-188 - Remind Jack and Michael to register asap for TPAC [on Raphaël Troncy - due 2010-10-06].

MEDIA FRAGMENT EXTENSION:

action-186?

<trackbot> ACTION-186 -- Philip Jägenstedt to send his list of test cases to the mailing list for understanding how browsers handle %-encodded and html-encoded URL -- due 2010-09-29 -- OPEN

<trackbot> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/186

<raphael> http://lists.w3.org/Archives/Public/public-media-fragment/2010Sep/0057.html

Yves: wonder if the same thing can be obtained with firebug

close action-186

<trackbot> ACTION-186 Send his list of test cases to the mailing list for understanding how browsers handle %-encodded and html-encoded URL closed

action-187?

<trackbot> ACTION-187 -- Philip Jägenstedt to start a new thread about extensibility of the Media Fragments in order to get consensus by next week -- due 2010-09-29 -- OPEN

<trackbot> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/187

raphael: people agreed with proposal (2) of Philip

yves: would like to know the opinion of Jack

raphael: first decide which proposal, afterwards decide how it is written in the spec

yves: just against the fact that saying that all key-value pairs are media fragments

raphael: on condition is that you need to have keys that we understand
... if this is not the case, it's not a media fragment

yves: not in favour, but also not against this

close action-187

<trackbot> ACTION-187 Start a new thread about extensibility of the Media Fragments in order to get consensus by next week closed

raphael: philip would like to distinguish between validity and parsing

yves: if we have grammar explaining what should be there, and a parsing algorithm, that's fine

<raphael> Is this grammar could be http://lists.w3.org/Archives/Public/public-media-fragment/2010Aug/0005.html

yves: this is not a grammar
... it's a general approach to parse key-value pairs

raphael: the grammar we currently have, will be kept of course

<Yves> I propose, keep the current grammar and add the extension point, _and_ define a parsing algorithm for those who need it

<Yves> mediasegment = namesegment / axissegment

<Yves> axissegment = ( timesegment / spacesegment / tracksegment )

<Yves> *( "&" ( timesegment / spacesegment / tracksegment )

<Yves> ;

<Yves> => add extensionsegment there

yves: a mediasegment can't be only an extensionsegment

<raphael> Yves propose that: mediasegment = namesegment / axissegment / extensionsegment + prose to state that a media segment cannot be only an extension segment

yves: we have to state that extensions should remain compatible with the current spec
... e.g., bounding box (through xywh) as fallback for an arbitrary shape (through ref)

<Yves> extensionsegment = extensionname '=' extensionvalue

<raphael> extensionsegment = extensionprefix '=' extensionparam

<Yves> issue is with extensions that conflict with already defined axis, like 'ref' being impacting the spatial dimension defined by 'xywh'

raphael: top-level production rules of the grammar should be in de document as well, not only in the appendix
... in section 4.3.5 or 4.1

<scribe> ACTION: troncy to put the top-level production rules back into the document (in section 4.3.5 or 4.1) [recorded in http://www.w3.org/2010/09/29-mediafrag-minutes.html#action02]

<trackbot> Created ACTION-189 - Put the top-level production rules back into the document (in section 4.3.5 or 4.1) [on Raphaël Troncy - due 2010-10-06].

raphael: still missing is a paragraph how things should be parsed
... I will ask Philip regarding this issue

close action-187

<trackbot> ACTION-187 Start a new thread about extensibility of the Media Fragments in order to get consensus by next week closed

action-173?

<trackbot> ACTION-173 -- Yves Lafon to produce the code that will check the grammar of both the URI syntax and the Headers syntax -- due 2010-06-22 -- OPEN

<trackbot> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/173

yves: not done yet for the header syntax

PUBLIC COMMENTS

<raphael> ACTION-184?

<trackbot> ACTION-184 -- Yves Lafon to email Chris the reply on when to send the range header -- due 2010-09-15 -- OPEN

<trackbot> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/184

close action-184

<trackbot> ACTION-184 Email Chris the reply on when to send the range header closed

raphael: should we use the bug tracker for LC comments?

yves: a manual approach should be feasible (e.g., manually building an HTML table)

raphael: suggest to start with manual approach, when a lot of comments are coming, we might consider using the bug tracker

<raphael> ACTION-167?

<trackbot> ACTION-167 -- Erik Mannens to find licence free movies for the automatic test suite ... starting with Elephant Dreams and the creative commons -- due 2010-06-02 -- OPEN

<trackbot> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/167

AOB

[adjourned]

Media Fragments Working Group Teleconference

29 Sep 2010

Attendees

Contents

ADMIN

MEDIA FRAGMENT EXTENSION:

PUBLIC COMMENTS

AOB

Summary of Action Items