Media Fragments Working Group Teleconference

<trackbot> Date: 06 July 2011

1. Admin

PROPOSED to accept the minutes of the last week telecon, http://www.w3.org/2011/06/29-mediafrag-minutes.html

<davy> +1

+1

<doublec> +1

minutes accepted

ACTION-203?

<trackbot> ACTION-203 -- Thomas Steiner to build a media fragment URI parser in javascript -- due 2011-01-31 -- CLOSED

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

ACTION-230?

<trackbot> ACTION-230 -- Raphaël Troncy to open a questionnaire for splitting out or not (the section 5.2 of) the spec -- due 2011-06-29 -- OPEN

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

close ACTION-230

<trackbot> ACTION-230 Open a questionnaire for splitting out or not (the section 5.2 of) the spec closed

Raphael: results of the poll have shown by a short majority to not split the spec at this stage

2. Spec Maintenance

ACTIOn-229?

<trackbot> ACTION-229 -- Raphaël Troncy to bring the CSS/SVG/Media Fragments possible issues to the CG group -- due 2011-06-29 -- OPEN

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

<doublec> Sounds good

<tomayac> +1

<davy> +1

Raphael: we should perhaps say explicitely in the spec that the behaviour of multi resolution images is undefined for media fragments

<erik> +1

Raphael: this will address the comments from fantasai
... should we edit http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#media-fragment-display ?

Yves: rather after http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-space in a note

<Yves> Note that in the case of pixel-based clipping areas, application of those areas to multi-resolution visual media is undefined.

<Yves> (multi-resolutions)

Chris: send comments regarding the ABNF syntax of npt

Yves: indeed, the grammar is just here for validating the syntax ... you need to do your own parsing rules to implement the grammar
... I will look at my own parser since I don't remember to have any issues
... I will check if my grammar is in syn with the spec

<scribe> ACTION: Yves to check if his grammar is in synch with the latest version of the spec [recorded in http://www.w3.org/2011/07/06-mediafrag-minutes.html#action01]

<trackbot> Created ACTION-231 - Check if his grammar is in synch with the latest version of the spec [on Yves Lafon - due 2011-07-13].

3. Test Cases

ACTION-223?

<trackbot> ACTION-223 -- Raphaël Troncy to start up a thread for discussion and approval of all test cases for the UA for the temporal dimension -- due 2011-06-15 -- OPEN

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

close ACTION-223

<trackbot> ACTION-223 Start up a thread for discussion and approval of all test cases for the UA for the temporal dimension closed

Raphael: no discussion on this thread?
... does it mean you *all* agree?

Davy: if I remember, Opera has some facility to run a test suite and test the browser

Chris: we have also a framework to run a test suite

<doublec> http://www.w3.org/2008/WebVideo/Fragments/TC/ua-test-cases

Chris: I will look at how the TC are written in a machine readable way

<davy> http://www.w3.org/2008/WebVideo/Fragments/TC/ua-test-cases.n3

<davy> http://www.w3.org/2008/WebVideo/Fragments/TC/ua-test-cases.rdf

<scribe> ACTION: Chris to use the machine readable descriptions of the test cases (n3, rdf) for adapting to the Mozilla test suite framework [recorded in http://www.w3.org/2011/07/06-mediafrag-minutes.html#action02]

<trackbot> Created ACTION-232 - Use the machine readable descriptions of the test cases (n3, rdf) for adapting to the Mozilla test suite framework [on Chris Double - due 2011-07-13].

<doublec> Ok, thanks

Thread to consider http://lists.w3.org/Archives/Public/public-media-fragment/2011Jun/0050.html

<silvia> I haven't reviewed the recent list either - I did lots earlier - Chris's suggestion sounds good

Raphael: 34 remaining TC that should be valid

Chris: I can take the range 66 to 94 and write to the list by tomorrow

<tomayac> can you simply assign them? raphael?

Silvia: I do 27 to 65

Thomas: I do 6 to 26

Raphael: we review those batches next week depending on the problems encountered

4. HTML5 liaison

Raphael: what is the overall HTML5 timeline?

Silvia: I haven't look at our bugs since a while

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10723

<doublec> I'll comment in 10723 what I plan to implement

thanks Chris

Raphael: loop attribute, will it be deprecated?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12426

Chris: we can revisit the loop attribute by changing to the in media element
... int fragment
... I will edit the bug with this

<silvia> http://lists.w3.org/Archives/Public/public-html/2011May/0162.html

<doublec> Yep, I'll comment on the bugs after the call

Raphael: should we organize a group review of the HTML5 spec?
... or will the bugs entered be enough?

<doublec> I think the entered bugs are enough

<tomayac> i guess we're fine w/ the entered bugs

Silvia: I'm not keen to do a full review of the spec, this is a lot of reading

5. AOB

Silvia: when we transition to CR?

Raphael: just after CSS review of the spec
... exiting CR will require to have 2 implementations for all features, some features might get out of the spec if they are not implemented
... all implementations count (from the group and from outsiders)