See also: IRC log
<scribe> scribe: francois
<Clarke> Use case: http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Discussions/ViewPort-Support
<r> yes - cant track conversation in real time
<kaz> issue-37?
<trackbot> ISSUE-37 -- View-Port support for Video Window -- raised
<trackbot> http://www.w3.org/2011/webtv/track/issues/37
<Clarke> Is Kaz taking notes, or russell?
<Clarke> OK.
<kaz> r, if there is any problem, please let us know
<Clarke> Russell can take them online if you want a break.
-> http://dev.w3.org/html5/spec/the-map-element.html#the-map-element Map element in HTML5
<r> AR recorded
<kaz> unmute me
<scribe> ACTION: Duncan to review whether ISSUE-37 can already be done using existing techniques [recorded in http://www.w3.org/2011/08/04-webtv-minutes.html#action01]
<trackbot> Created ACTION-67 - Review whether ISSUE-37 can already be done using existing techniques [on Duncan Rowden - due 2011-08-11].
<kaz> issue-18?
<trackbot> ISSUE-18 -- Video tag support of MPEG2-TS -- raised
<trackbot> http://www.w3.org/2011/webtv/track/issues/18
<Clarke> use case time synch: http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Discussions/Time_Synchronization
<r> AR: Jan - Summarize ISSUE-18 as new use-case
<scribe> ACTION: Jan to summarize a new home issue for ISSUE-18 [recorded in http://www.w3.org/2011/08/04-webtv-minutes.html#action02]
<trackbot> Created ACTION-68 - Summarize a new home issue for ISSUE-18 [on Jan Lindquist - due 2011-08-11].
<kaz> bob: explains his view, esp. existing features of HTML5 related this proposal
<Zakim> kaz, you wanted to suggest we include a bit more detailed example scenario (including actual video image :) and to
<kaz> bob: 5 comments so far
<kaz> ... one of them was reject, 13333
-> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333 Bug 13333
<kaz> bob: no discussion on the other 4
-> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13357 Bug 13357
-> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13358 Bug 13358
-> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13359 Bug 13359
-> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13625 Bug 13625
<kaz> mav: we went through couple of the comments
<kaz> clarke: we did 13333 and 13357 last week
<kaz> Clarke's message on HTML5 LC comments
<kaz> bob: explains 13358
<kaz> bug 13358
<kaz> bob: had discussion with accessibility guys as well
<kaz> ... they said this requirement is valid
<kaz> giuseppe: no objection, but question about "endorsement"
<kaz> clarke: acknowledging this is a comment from the IG
<kaz> unmute me
<kaz> mute me
<kaz> kaz: explains the situation about HTML5 LC comments
<kaz> ... all the 5 comments have submitted to HTML WG before the deadline and are under review
<kaz> ... although the comment period for the first LCWD ended yesterday, we can send more comments to the HTML WG
<kaz> ... those comments will be for the 2nd LCWD
<kaz> ... we can also send a message to the chairs of the HTML WG and Hypertext Coordination Group saying we as the whole IG endorse these comments
<kaz> giuseppe: fine to send a message
<kaz> bug 13359
<kaz> bob: A way is needed to identify the type of data in a track element
<kaz> giuseppe: use case here is regarding user script
<kaz> bob: right
<kaz> bob: type attribute is populated as mime type
<kaz> fd: even though the HTML WG refuse to add type attribute, it would be useful to have mechanism to handle IDL attribute from UA
<kaz> RESOLUTION: everybody is fine to endorse 13359
<kaz> bug 13625
<kaz> bob: There is no way to pass audio and video content metadata to the user agent that is required in some cases for playback.
<kaz> ... specifically, protocol, size and content protection mechanism
<kaz> ... would propose those three are added as attributes for HTMLMediaElement
<kaz> igarashi: it would be better to have a metadata attribute which can handle all those three than adding three separate attributes
<kaz> bob: you think so mainly because some more metadata would be added later
<kaz> igarashi: RFC defines content type and content feature
<kaz> bob: might be a good comment to be added to our comment 13625 itself
<kaz> giuseppe: media element has too many parameters...
<kaz> clarke: would suggest the IG co-Chairs to draft a message acknowledging these 5 comments
<Clarke> Thanks everybody
<kaz> [ adjourned ]
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: i/use case time synch/Topic: Time Synchronization Found Scribe: francois Inferring ScribeNick: francois WARNING: Replacing list of attendees. Old list: Kazuyuki New list: francois kaz duncanr Narm Clarke_Stevens Gondo Igarashi Russell_Berkoff mav Nilo_Mitra Aizu Giuseppe Bob Default Present: francois, kaz, duncanr, Narm, Clarke_Stevens, Gondo, Igarashi, Russell_Berkoff, mav, Nilo_Mitra, Aizu, Giuseppe, Bob Present: francois duncanr kaz Narm Clarke_Stevens Gondo Igarashi Aizu Russell_Berkoff mav Nilo_Mitra Giuseppe Bob Agenda: http://www.w3.org/2011/webtv/wiki/MPTF/Agenda_Telco_4th_August_2011 Got date from IRC log name: 04 Aug 2011 Guessing minutes URL: http://www.w3.org/2011/08/04-webtv-minutes.html People with action items: duncan jan WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]