14:54:59 <RRSAgent> RRSAgent has joined #webtv
14:54:59 <RRSAgent> logging to http://www.w3.org/2011/10/06-webtv-irc
14:55:01 <trackbot> RRSAgent, make logs world
14:55:01 <Zakim> Zakim has joined #webtv
14:55:03 <trackbot> Zakim, this will be 
14:55:03 <Zakim> I don't understand 'this will be', trackbot
14:55:04 <trackbot> Meeting: Web and TV Interest Group Teleconference
14:55:04 <trackbot> Date: 06 October 2011
14:55:09 <francois> zakim, what conferences?
14:55:09 <Zakim> I see SW_RDFa()10:00AM, T&S_GLDWG()10:00AM, WAI_ERTWG(Eval TF)10:00AM, WF_(WFCH)8:00AM, SW_HCLS()11:00AM active
14:55:12 <Zakim> also scheduled at this time are INC_LLDXG()10:00AM, WF_TF()9:00AM, Team_(pointy)13:39Z, XML_PMWG()10:00AM, Team_Comm()10:30AM, Styl_XSL-FO-()11:00AM, MM_MMI(EMMA)10:00AM,
14:55:16 <Zakim> ... WAI_PFWG(AAPI)10:00AM, WAI_PFWG(HTML TF)11:00AM, Math_IG()10:00AM, VB_VBWG(CCXML)11:00AM, SW_(PROV)11:00AM, Team_Global(review)8:00AM, SW_HCLS(TMO)11:00AM, I18N_WG(MLW)11:00AM,
14:55:22 <Zakim> ... XML_QueryWG(XSLT)11:00AM, UW_POI(POIWG)10:00AM, WAI_RDWG()11:00AM, UW_WebTVIG()11:00AM
14:55:28 <francois> zakim, this will be WebTVIG
14:55:31 <Zakim> ok, francois; I see UW_WebTVIG()11:00AM scheduled to start in 5 minutes
14:58:16 <JanL> JanL has joined #webtv
14:58:34 <Clarke> Clarke has joined #webtv
14:58:55 <kaz> zakim, code?
14:58:55 <Zakim> the conference code is 93288 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), kaz
14:59:03 <kaz> zakim, call kazuyuki-617
14:59:03 <Zakim> ok, kaz; the call is being made
14:59:04 <Zakim> UW_WebTVIG()11:00AM has now started
14:59:08 <Zakim> +??P64
14:59:12 <aizu> aizu has joined #webtv
14:59:18 <Zakim> -??P64
14:59:20 <Zakim> UW_WebTVIG()11:00AM has ended
14:59:20 <Zakim> Attendees were 
14:59:27 <kaz> zakim, call kazuyuki-617
14:59:27 <Zakim> UW_WebTVIG()11:00AM has now started
14:59:28 <Zakim> ok, kaz; the call is being made
14:59:36 <Zakim> +Jan_Lindquist
14:59:44 <kaz> zakim, call kazuyuki-617
14:59:52 <Zakim> + +329987aaaa
14:59:58 <Zakim> ok, kaz; the call is being made
15:00:05 <Zakim> +??P53
15:00:08 <Clarke> +Clarke_Stevens
15:00:10 <kaz> zakim, call kazuyuki-617
15:00:23 <eric> eric has joined #webtv
15:00:24 <Zakim> + +44.303.040.aabb
15:00:34 <Zakim> ok, kaz; the call is being made
15:00:34 <Clarke> I'm here
15:00:54 <Zakim> +??P68
15:01:11 <Zakim> +[Microsoft]
15:01:37 <franck> franck has joined #webtv
15:01:39 <Johnsim> Johnsim has joined #webtv
15:02:11 <kaz> zakim, who is here?
15:02:24 <Zakim> +??P15
15:02:34 <Zakim> + +1.760.705.aacc
15:02:44 <Zakim> On the phone I see Jan_Lindquist, +329987aaaa, ??P53, +44.303.040.aabb, ??P68, [Microsoft], ??P15, +1.760.705.aacc
15:03:09 <Zakim> On IRC I see Johnsim, franck, eric, aizu, Clarke, JanL, Zakim, RRSAgent, duncanr, kaz, francois, masao_, trackbot
15:03:20 <Zakim> +??P17
15:03:32 <kaz> zakim, ??P17 is Aizu
15:03:34 <Zakim> +Francois_Daoust
15:03:40 <francois> zakim, mute me
15:04:13 <kaz> Present: Johnsim, franck, eric, aizu, Clarke, JanL, duncanr, kaz, francois, MarkW
15:04:17 <Zakim> +Aizu; got it
15:04:33 <Zakim> + +1.415.867.aadd
15:04:37 <francois> ack me
15:04:44 <kaz> zakim, aadd is MarkW
15:04:44 <Zakim> Francois_Daoust should now be muted
15:04:46 <Russell_Berkoff> Russell_Berkoff has joined #webtv
15:05:02 <francois> zakim, mute me
15:05:10 <francois> scribenick: francois
15:05:25 <francois> Chair: Clarke
15:05:38 <kaz> zakim, mute me
15:05:40 <francois> Clarke: got to requirement 2 last week. Let's move on from there.
15:05:50 <Zakim> +MarkW; got it
15:05:58 <francois> ... We can get through the rest of the less controversial ones today.
15:06:00 <Zakim> Francois_Daoust should now be muted
15:06:10 <Zakim> sorry, kaz, I do not know which phone connection belongs to you
15:06:19 <francois> ... Next week, we can get to adaptive streaming, then the week after that to the digital rights requirements.
15:06:28 <francois> ... Then that's TPAC.
15:07:03 <francois> ... Less concerned that we're not ready by TPAC. We want to show that we have requirements at TPAC. From the F2F, we do have general agreement about use cases and requirements even it not perfect.
15:07:16 <Zakim> + +1.678.795.aaee
15:07:27 <francois> ... Main goal of TPAC is to bring these to WG.
15:07:28 <Zakim> +??P25
15:07:47 <francois> John: is the intent to take all of them to TPAC or some of them?
15:07:50 <Zakim> +Mark.a
15:08:05 <francois> Clarke: We only want to have standardized those things that can't be done today.
15:08:09 <mav> mav has joined #webtv
15:09:15 <Clarke> R3:http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements
15:09:20 <francois> Topic: Midstream Modification of Track Elements
15:09:24 <kaz> zakim, who is here?
15:09:25 <Zakim> On the phone I see Jan_Lindquist, +329987aaaa, ??P53, +44.303.040.aabb, ??P68, [Microsoft], ??P15, +1.760.705.aacc, Aizu, Francois_Daoust (muted), MarkW, +1.678.795.aaee, ??P25,
15:09:26 <francois> -> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements#R3._Midstream_Modification_of_Track_Elements R3
15:09:32 <Zakim> ... Mark.a
15:09:38 <Zakim> On IRC I see mav, Russell_Berkoff, Johnsim, franck, eric, aizu, Clarke, JanL, Zakim, RRSAgent, duncanr, kaz, francois, masao_, trackbot
15:09:46 <francois> Clarke: ability to change, add, remove track element in the middle of a stream.
15:09:58 <francois> ... From some discussion, maybe removing them is not necessary.
15:09:59 <JanL> +q
15:10:12 <francois> Bob: Changes are going into HTML5 spec as we speak to add this capability.
15:10:25 <kaz> present+ mav, bob
15:10:41 <francois> ... Ian Hickson is leaving the door open to track removal if a use case comes for that.
15:11:07 <francois> ... We agree that it's difficult to a) know when a track is gone, and b) do something useful with it.
15:11:21 <francois> ??1: Potential problem if a track comes back?
15:11:28 <francois> Bob: It wouldn't get added as a new one.
15:11:41 <francois> ??1: How would you know it's come back?
15:11:56 <francois> Bob: you'd look at cues.
15:12:02 <francois> ??1: What about audio?
15:12:32 <kaz> s/??1:/markW:/g
15:12:36 <francois> ... [example with English track]
15:12:49 <francois> ... Was planning to comment to HTML WG about that.
15:12:57 <Clarke> q?
15:13:16 <Clarke> ack JanL
15:13:28 <francois> Russell: Similar comment, if you don't know when a track's gone, hard to see when a track comes back.
15:14:16 <francois> ... The argument goes that in order for you to rewind, you need to have them available. Broadcast does not support rewind, so they should reflect what is available.
15:15:05 <francois> Bob: Didn't see anything in the bug's response that it was specifically about seeking.
15:15:14 <francois> Russell: maybe I read through the lines here.
15:15:23 <RRSAgent> I have made the request to generate http://www.w3.org/2011/10/06-webtv-minutes.html kaz
15:16:06 <kaz> present+ russell
15:16:12 <francois> ... How do I have my default language, and over time want to switch to another default. If I don't know when a track is removed, I can't implement a selection mechanism based on preferences.
15:16:14 <RRSAgent> I have made the request to generate http://www.w3.org/2011/10/06-webtv-minutes.html kaz
15:16:45 <francois> MarkW: valid points. Not quite sure what Ian proposes works in the end.
15:17:10 <francois> ... What about track numbers when you remove a track?
15:17:31 <Zakim> -MarkW
15:17:33 <francois> ... It has to be treated in a different way. A track that gets removed has to remain in the list.
15:17:46 <francois> Bob: I think that's right, otherwise you can't reorder track.
15:18:06 <Zakim> +MarkW
15:18:30 <francois> Russell: dealt with in OIPF, whether array of tracks is dynamic. Ended up with a static array parsed again and again.
15:18:47 <francois> Clarke: in the user agent, you then have to "track" which track maps to which index.
15:18:51 <francois> Russell: Yes.
15:20:14 <francois> Clarke: We don't need to change the requirement here necessarily. Checking that Jan and Mark's comments are recorded in that bug seems the appropriate way to go.
15:20:50 <francois> Topic: R4. Content Authorization Parameters
15:20:55 <francois> -> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements#R4._Content_Authorization_Parameters R4
15:21:04 <francois> Clarke: does this one have a bug?
15:21:22 <francois> Bob: No. It is my opinion that this can already be done.
15:21:54 <francois> ... There are a bunch of other issues about parental issues that are not covered by the use case.
15:22:26 <francois> Clarke: could be covered by the requirement 2 on being able to distinguish types of metadata
15:22:37 <francois> -> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements#R2._Key_Metadata_Types R2
15:23:27 <francois> John: I took an action item to identify ways to document metadata conventions. Two options inside W3C for this kind of documentation: community and business groups.
15:23:28 <Zakim> + +1.908.848.aaff
15:23:42 <francois> -> http://www.w3.org/community/ Community and Business Groups
15:24:21 <francois> John: this could be the way to get together and work on this kind of specification.
15:24:54 <kaz> zakim, aaff is Steven_Wright
15:24:54 <Zakim> +Steven_Wright; got it
15:25:02 <kaz> Present+ Steven
15:25:07 <francois> Clarke: Do people agree that a community/business group would be the place to work on metadata mapping?
15:25:24 <kaz> present+ Paul
15:25:59 <francois> Bob: I'll be able to share a few things with this group.
15:26:18 <francois> Topic: R5. Content Authorization Failure
15:26:22 <francois> -> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements#R5._Content_Authorization_Failure R5
15:26:46 <francois> Clarke: There are a number of reasons that could explain why you cannot play a content.
15:27:23 <francois> MarkW: This seems to be a narrow example of a more generic problem for an error reporting mechanism.
15:28:00 <francois> ... It's a real requirement, but I wonder if we could report on the generic error reporting mechanism and enumerate the examples we have here as part of it.
15:28:52 <francois> Clarke: It may just be the addition of an error, or if the error reporting mechanism is not efficient enough.
15:29:25 <francois> Topic: R6. Adaptive Bit Rate Format Support
15:29:27 <francois> -> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements#R6._Adaptive_Bit_Rate_Format_Support R6
15:30:28 <francois> MarkW: question here is what do we want to normatively specify here? That different solutions be supported?
15:31:32 <francois> Bob: We had a couple of specific requests (going through)
15:32:10 <francois> Clarke: we have to be able to tell when it is an adaptive streaming format.
15:32:14 <mav> I don't think R6 is a gap
15:32:32 <mav> Suggest delete R6 & leave R7  & R8
15:32:48 <francois> MarkW: We need to be clear what we're requesting. If it is something that can already be satisified with no changes, it doesn't make sense to list that as a requirement.
15:34:01 <francois> JanL: I'm having the same comment as Mark. Could we flag the requirement as needed but nothing needs to be done?
15:35:09 <francois> MarkW: If there had been a RF codec, then they would have made a requirement. The same applies for adaptive streaming format. If we can have DASH be that format, then good. Unclear we can, though.
15:35:40 <francois> ??2: I think it's going to evolve in the next couple of years. Even if we have a RF format, I don't think we should put it forward yet.
15:36:28 <francois> John: HTML WG is being format agnostic to let the market decide which format to use.
15:36:44 <francois> Clarke: I'm not seeing any strong push to keep that requirement in there.
15:37:08 <francois> ... I propose to leave it for a few days. If somebody has some strong argument, please make them. Otherwise, I propose to drop it.
15:37:27 <francois> s/??2:/MarkV:/
15:37:35 <Zakim> -Mark.a
15:37:43 <francois> Topic: R7. Adaptive Bit Rate Parameters
15:37:51 <francois> -> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements#R7._Adaptive_Bit_Rate_Parameters R7
15:38:03 <francois> Clarke: Requirement we captured at the F2F.
15:38:22 <francois> JanL: I don't believe there's any mechanism today, e.g. to specify the max.
15:38:44 <francois> Clarke: Could we say we have a preference of a way to do this?
15:38:47 <mark> mark has joined #webtv
15:38:47 <Zakim> +Mark.a
15:39:12 <francois> JanL: My preference would be to have a dialog with WG who will pick up this requirement.
15:39:38 <francois> ... I don't have a solution. Many times, you come to W3C with a proposal. Here I don't have that, so that's why I suggest a dialog.
15:41:06 <francois> Mark: R7 and R8 are the counterparts of R4 and R5. Parameters in the media pipeline, one way for R4 and R7, or the other way for R5 and R8
15:41:39 <kaz> s/Mark:/MarkV:/
15:42:30 <francois> JanL: I note we could change "failure" into "feedback", as we need a generic feedback mechanism, not only for failures. I agree with MarkV that it's a good parallel.
15:42:51 <francois> Clarke: suggest to merge them?
15:42:54 <francois> JanL: no.
15:43:09 <francois> MarkV: I agree on keeping them separate, just adjust the wording to use same words.
15:43:48 <francois> Clarke: ok, so we covered R8 as well. Going on to security.
15:43:57 <francois> Topic: R9. Security and Digital Rights Management Identification
15:43:58 <kaz> s/Web and TV Interest Group Teleconference/Media Pipeline Task Force Teleconference/
15:44:07 <francois> -> http://www.w3.org/2011/webtv/wiki/MPTF/MPTF_Requirements#R9._Security_and_Digital_Rights_Management_Identification R9
15:44:41 <francois> Clarke: Parallel with R6. Is the conclusion the same?
15:44:57 <francois> ... For instance, if I am to use UltraViolet, can I do it already?
15:45:33 <francois> Bob: I don't know for UltraViolet. I think that, in general, anything can be encoded as mime type parameters.
15:45:53 <francois> Clarke: Do we have anyone from DECE who knows what we might need?
15:46:42 <francois> John: DECE does define a very specific encoding format, not just down to the container, also pixel details.
15:47:04 <francois> ... Encoding works find with downloading and adaptive streaming.
15:47:37 <francois> ... Both DASH on-demand and live demand can be encrypted for instance. Not DRM specific.
15:47:39 <franck> s/works find/works fine/
15:48:00 <francois> ... It's a part 12 compliant encoding (ISO base file format).
15:49:00 <francois> ... I don't see additional requirement for HTML
15:49:35 <francois> ... You may want to know whether the device supports a given encryption mechanism.
15:50:14 <francois> JanL: I was a bit confused as to how it worked in a streaming world where you keep sending authentication information.
15:50:44 <francois> John: you can have information in the MPD telling if it's DASH, where to get the key.
15:51:05 <francois> ... It's just not a file.
15:51:36 <francois> ... In terms of key rotation and things of that nature, that's also supported in adaptive streaming as well.
15:52:50 <francois> ... [example of things to do on the production side]
15:53:34 <francois> ... From a browser's point of view, there are lots of reasons why you will fail to play content, in particular while dealing with one of the DRM subsystems.
15:54:02 <francois> ... Even if you may be able to require a key, you may still end up not being able to play the content.
15:54:32 <francois> Clarke: Two basic questions. R9, I haven't heard anything here that says we cannot do it today.
15:55:06 <francois> ... Second, I hear more stuff to expose parameters in R10.
15:55:27 <francois> Bob: Second point, similar issue as adaptive bitrate, but different information that needs to be conveyed.
15:56:06 <francois> Clarke: Are there some additional security functionalities that need to be added beyond being able to expose parameters and provide feedback?
15:56:15 <francois> MarkW: [scribe missed that]
15:57:26 <francois> John: [missed beginning] It's a piece of piece process. You can pick up one, such as device identification we're talking right now.
15:57:44 <francois> JanL: I just sent a bug proposal based on Hollywood meeting.
15:58:17 <francois> ... If people can comment. ISSUE-18. I'll pick it up next week in any case.
15:59:03 <francois> John: We have to be very concise in the requirements for 9 and 10. For example, DECE Utlraviolet is too vague, because you might have different systems that support different functionalities.
15:59:50 <francois> JanL: Points I raised previously, retrieval of ? and device identification, are these precise enough?
15:59:59 <francois> John: I think so.
16:00:12 <Zakim> -??P25
16:00:31 <francois> ... For some, it's more a matter of user experience issue, where you don't want to discover you cannot play after having tried.
16:00:59 <francois> JanL: As I presented in Hollywood, this is something Open IPTV Forum touched upon.
16:01:12 <francois> Clarke: Any work that we can reference is useful, yes.
16:01:58 <francois> ... I'm going to suggest that R6 and R9 are already covered, and then I'll try to parallelize R10/R11 with R7/R8 and R4/R5.
16:02:17 <Zakim> -Steven_Wright
16:02:18 <francois> ... Thanks everyone, be active online and talk to you next week!
16:02:20 <Zakim> -[Microsoft]
16:02:20 <Clarke> Thanks Francois
16:02:22 <Zakim> -Jan_Lindquist
16:02:22 <duncanr> duncanr has left #webtv
16:02:24 <Zakim> -MarkW
16:02:28 <Zakim> - +44.303.040.aabb
16:02:30 <Zakim> -Mark.a
16:02:32 <Zakim> -??P68
16:02:33 <francois> [Call adjourned]
16:02:34 <Zakim> -??P53
16:02:36 <Zakim> - +1.760.705.aacc
16:02:50 <Zakim> -Aizu
16:02:56 <Zakim> -Francois_Daoust
16:03:04 <Zakim> - +1.678.795.aaee
16:03:22 <Zakim> - +329987aaaa
16:03:28 <francois> RRSAgent, list attendees
16:03:28 <RRSAgent> I'm logging. I don't understand 'list attendees', francois.  Try /msg RRSAgent help
16:03:32 <francois> Zakim, list attendees
16:03:52 <Zakim> As of this point the attendees have been Jan_Lindquist, +329987aaaa, +44.303.040.aabb, [Microsoft], +1.760.705.aacc, Francois_Daoust, Aizu, +1.415.867.aadd, MarkW, +1.678.795.aaee,
16:03:58 <franck> franck has left #webtv
16:03:59 <francois> RRSAgent, draft minutes
16:03:59 <RRSAgent> I have made the request to generate http://www.w3.org/2011/10/06-webtv-minutes.html francois
16:04:00 <Zakim> ... Mark, +1.908.848.aaff, Steven_Wright
16:04:42 <Zakim> -??P15
16:04:44 <Zakim> UW_WebTVIG()11:00AM has ended
16:04:47 <Zakim> Attendees were Jan_Lindquist, +329987aaaa, +44.303.040.aabb, [Microsoft], +1.760.705.aacc, Francois_Daoust, Aizu, +1.415.867.aadd, MarkW, +1.678.795.aaee, Mark, +1.908.848.aaff,
16:04:49 <Zakim> ... Steven_Wright