HTML Media Task Force Teleconference -- 09 Oct 2012

<trackbot> Date: 09 October 2012

<scribe> ScribeNick: adrianba

<scribe> Scribe: Adrian Bateman

<paulc> waves

Role call and introductions

paulc: done

Preview meeting minutes

http://www.w3.org/2012/09/25-html-media-minutes.html

paulc: didn't see any comments on the minutes

Review of action items

paulc: none assigned to MSE work

TPAC meeting plans

paulc: wg meeting thur/fri nov 1/2 in lyon, france
... same place as November 2010
... confirmed we have the same two meeting rooms we had 2 years ago
... i want to confirm that the people on the call are okay with the general plan
... that MSE and EME experts meet for 90mins to 2 hours at TPAC
... having talked to some of the editors about this i want to suggest that we meet on thursday
... so that the editors can meet afterwards to discuss how to take actions as a result of the meeting
... and the goal would be to have enough discussion at TPAC to make sure we can do a CfC for a FPWD immediately after TPAC
... we want to make sure we have the general discussion for both specs in the right direction
... so that the group will be happy to go to FPWD
... this doesn't mean every bug closed
... but it means the scope and direction is well understood
... comments?
... chairs will build a wiki site for unconference meeting requests so my proposal is to request 90-120 mins for each of the media specs
... in the past the HTML WG meeting session discusses the ideas at 9am on the first day
... and the group discusses which to talk about

pal: will there be a conference bridge?

paulc: the rooms will have a bridge so we'll see if that is feasible
... i want to warn you that there are 44 members and 40+ observers registered and the room is pretty large and even with the phone in the middle of the room it's not clear how audible to the meeting would be

<pal> thanks

matt: when will we know what the agenda will be for that thursday?

paulc: at 9.30am on thursday

matt: so we should come in at 9am to show our support of the topics

paulc: yes
... this is the model that we've done before and it worked well
... we have one coordination request already so sometimes the chairs anchor the coordination requests when they involve another WG
... but the rest of the sessions are determined by unconference

matt: i suspect that some people will be in other meetings too

paulc: the agenda will be set at 9am on thursday

Baseline documents

paulc: aaron had produced a draft on oct 1 that resolved 5 bugs and then on oct 8 that resolved 5 more
... not planning to go through the list of bugs specifically
... acknowledge that you made progress by cutting the bugs by 1/3
... do you have anything specific to highlight?

acolwell: most are clarifications

<paulc> Latest update news is in http://lists.w3.org/Archives/Public/public-html-media/2012Oct/0024.html

acolwell: seeking doesn't set things back into open so that you seeking doesn't require you to call endstream
... you weren't allowed to call append in the ended state - now it will transition to open and allow the append to happen
... for example if the app determined it had some higher quality data it could append that

paulc: there are currently 19 bugs outstanding
... most listed under agenda 6 and 7
... i'd like to propose that we handle the next agenda item as follows
... looking at the bugs, some of them i'd characterise as "hard" that we've been carrying for a few weeks
... i haven't seen any significant progress on the bugs in agenda 6
... high level question is how to get ready for TPAC sessions
... especially for work items assigned to editors or others in the group

acolwell: a bunch of things in section 6 are new features and have lower priority for me because trying to focus on clarifying existing behaviour before adding new stuff
... that's why these haven't made as much progress
... have started on remove because i think others can be specified using the remove method
... the TS one is one that I need to continue to read the specs

paulc: remove is bug 18709
... TS is bug 17094

adrianba: i'd like to propose that
... the editors meet to triage the current bugs
... and figure out the status and next action of each
... so that in two weeks we can work on the TPAC agenda
... and let people know to come to TPAC prepared to discuss concrete issues
... and make actual progress on the things that have been blocked

acolwell: that sounds good to me

paulc: i had mail from mark about bug 18962 - allow appending with xhr

markw: i wanted to point out that there is some work in webapps
... that is about adding a stream response to XHR
... which allows the app to lazily access data received
... so we should discuss if that might be a solution for this bug
... and if so coordinate with webapps on this to make sure it addresses the requirements we have

paulc: webapps meet on mon/tue - will you be there?

markw: i might need to go to Web & TV but will shuttle between them

<matt> adrianba: The discussion in Web Apps is partly about the proposal that MS made for stream support for XHR.

<matt> adrianba: The broader discussion is about whether that's a good solution for this or if there's a need for something else. This was mostly in the context of understanding what support there would be for chunked HTTP.

<matt> adrianba: I think the current proposal is to add at least the receive part of the MS proposal. That's the last I saw, not sure if anything specific changed in the last few days.

paulc: mark does that help?

markw: yes

paulc: other bug on action 6 and 7 is bug 17002
... this is SourceID to .id mapping
... i asked about the status in the other media group
... aaron followed up with some questions
... and that thread is continuing

<paulc> http://lists.w3.org/Archives/Public/public-html-media/2012Oct/0026.html

paulc: i think i'm going to skip to agenda 9 - any other business

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18666

adrianba: this is HTMLMediaElement.seekable

acolwell: all seekable does is to be from 0 to the duration
... so in the case of live, the duration would be positive infinity
... wait, let me look at the text
... in a live stream what will happen is if the duration is set to something other that +inf then seekable will be zero to the duration
... otherwise it will be zero to the highest time in the source buffer
... then the seekable will be set to the highest of what is in the buffer
... so you can only seek to what is in the buffer

adrianba: does that mean that the seekable range will grow as the data is being buffered, say from a URL

acolwell: yes

adrianba: that answers my question

paulc: are thinking of reopening this?

adrianba: i don't expect to reopen this - solution sounds good

pal: question on process - if i have some minor questions on the spec - how should i ask them?

paulc: depending on how many you have, you might consider sending mail to the list with the list of questions
... sometimes if the questions are complicated it might make sense to put one per email
... then you can put the question in the subject
... or you could open a bug
... my preference is option 2

pal: thank you

paulc: i think option 2 is the best approach - you might get an answer to the first before you asked the second
... any other business?

Chair and scribe for next meeting

paulc: i will chair, any volunteers for scribe?
... not hearing any one
... major item of discussion for next meeting will be the triage from the editors and preparing for the TPAC meeting

Adjournment

paulc: bye everyone

<strobe> thanks

- DRAFT -

HTML Media Task Force Teleconference

09 Oct 2012

Attendees

Contents