12:48:52 RRSAgent has joined #webtv 12:48:52 logging to http://www.w3.org/2013/10/16-webtv-irc 12:48:54 RRSAgent, make logs world 12:48:54 Zakim has joined #webtv 12:48:56 Zakim, this will be 12:48:56 I don't understand 'this will be', trackbot 12:48:57 Meeting: Web and TV Interest Group Teleconference 12:48:57 Date: 16 October 2013 12:49:19 Meeting: Web and TV IG - Media APIs TF Teleconference 12:49:38 Agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0038.html 12:50:37 Agenda+ Review of action items: https://www.w3.org/2011/webtv/track/agenda 12:50:43 Agenda+ Review of gap analysis 12:50:49 Agenda+ Assign further gap analysis 12:50:49 Agenda+ AOB 12:50:49 Agenda+ Next meeting 12:54:56 kaz has joined #webtv 12:55:45 zakim, code? 12:55:45 sorry, kaz, I don't know what conference this is 12:55:56 zakim, this will be webtv 12:55:56 ok, kaz, I see UW_WebTVIG()9:00AM already started 12:56:13 zakim, call kazuyuki-617 12:56:13 ok, kaz; the call is being made 12:56:15 +Kazuyuki 12:56:31 zakim, who is here? 12:56:31 On the phone I see ??P17, Kazuyuki 12:56:32 On IRC I see kaz, Zakim, RRSAgent, olivier, trackbot, timeless 12:59:01 skim13 has joined #webtv 12:59:46 ddavis has joined #webtv 12:59:50 Bin_Hu has joined #webtv 13:00:39 +Bin_Hu 13:01:11 +??P21 13:01:13 zakim, ??P17 is olivier 13:01:13 +olivier; got it 13:01:14 Zakim, ??P21 is me 13:01:14 +ddavis; got it 13:01:22 zakim, who is here? 13:01:22 On the phone I see olivier, Kazuyuki, Bin_Hu, ddavis 13:01:23 On IRC I see Bin_Hu, ddavis, skim13, kaz, Zakim, RRSAgent, olivier, trackbot, timeless 13:01:26 Sheau has joined #webtv 13:01:54 +sheau 13:03:05 +??P26 13:03:12 zakim, ??P26 is me 13:03:12 +olivier; got it 13:03:21 zakim, who is here? 13:03:21 On the phone I see olivier, Kazuyuki, Bin_Hu, ddavis, sheau, olivier.a 13:03:23 On IRC I see Sheau, Bin_Hu, ddavis, skim13, kaz, Zakim, RRSAgent, olivier, trackbot, timeless 13:03:25 zakim, who is here? 13:03:25 On the phone I see olivier, Kazuyuki, Bin_Hu, ddavis, sheau, olivier.a 13:03:26 On IRC I see Sheau, Bin_Hu, ddavis, skim13, kaz, Zakim, RRSAgent, olivier, trackbot, timeless 13:03:36 gmandyam has joined #webtv 13:03:46 +gmandyam 13:04:13 zakim, olivier is ??P17 13:04:13 +??P17; got it 13:04:16 zakim, who is here? 13:04:16 On the phone I see ??P17, Kazuyuki, Bin_Hu, ddavis, sheau, olivier.a, gmandyam 13:04:18 On IRC I see gmandyam, Sheau, Bin_Hu, ddavis, skim13, kaz, Zakim, RRSAgent, olivier, trackbot, timeless 13:04:22 zakim, olivier.a is olivier 13:04:22 +olivier; got it 13:04:29 zakim, drop ??P17 13:04:29 ??P17 is being disconnected 13:04:31 -??P17 13:05:09 +??P17 13:05:44 zakim, ??P17 is skim13 13:05:44 +skim13; got it 13:06:02 Agenda? 13:06:22 -> Proposed agenda http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0038.html 13:07:05 scribenick: ddavis 13:07:08 scribe: Daniel 13:07:11 zakim, take up agendum 1 13:07:11 agendum 1. "Review of action items: https://www.w3.org/2011/webtv/track/agenda" taken up [from olivier] 13:07:24 zakim, mute me 13:07:24 ddavis should now be muted 13:07:49 olivier: Action 146, update use cases 6 & 7 has been done, no objections. 13:07:52 close action-146 13:07:52 Closed action-146. 13:08:24 http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements 13:08:24 olivier: Action 147, edit requirements doc & link to spreadsheet - done. 13:08:32 close action-147 13:08:32 Closed action-147. 13:09:11 olivier: Action 140, Sheau to split service & device discovery in requirements doc. 13:09:16 close action-140 13:09:16 Closed action-140. 13:09:18 Sheau: Done 13:09:25 whyun has joined #webtv 13:09:35 http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Network_Selection 13:09:40 olivier: Action 141, requirement on network selection - done. 13:09:42 Present: Kaz, Bin, Daniel, Sheau, Olivier, Giri 13:09:54 rrsagent, make log public 13:09:58 rrsagent, draft minutes 13:09:58 I have made the request to generate http://www.w3.org/2013/10/16-webtv-minutes.html kaz 13:10:04 s/ - done// 13:10:18 gmandyam: I just need to add hyperlinks on the Google spreadsheet 13:10:52 close action-141 13:10:52 Closed action-141. 13:10:57 olivier: If we're happy, let's close 141 13:11:12 olivier: That's all the action items for this Task Force 13:11:14 zakim, close agendum 1 13:11:14 agendum 1, Review of action items: https://www.w3.org/2011/webtv/track/agenda, closed 13:11:16 I see 4 items remaining on the agenda; the next one is 13:11:16 2. Review of gap analysis [from olivier] 13:11:20 zakim, take up agendum 2 13:11:20 agendum 2. "Review of gap analysis" taken up [from olivier] 13:11:58 * Gap Analysis on Requirement 9 "Context-based and targeted Service Aggregation" http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0028.html 13:12:01 * Gap Analysis on Requirement 17 "Tuner Control" http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0029.html 13:12:04 * Gap Analysis on Requirement 18 "Channel Identification" http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0031.html 13:12:07 * Gap Analysis on Requirement 19 "Content Streaming" http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0032.html 13:12:09 olivier: There were a number of mails on the list about the gap analysis 13:13:20 olivier: Requirements 9, 17, 18, 19 had good suggestions of gaps 13:13:26 present+ wyhun 13:13:54 olivier: All specs mentioned in those requirement analysis are not W3C specs. 13:14:29 olivier: We could look at those specs to see if they do what we need and whether we need to add features to the web platform. 13:14:45 http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0028.html 13:14:51 olivier: Let's look at GA for Req 9. 13:15:07 olivier: Related spec is Hybrid broadcast for broadband TV 13:15:43 olivier: There are a number of gaps. ETSI people, please could you talk more about it? 13:16:04 skim13: The existing spec has similar features to the application we've defined. 13:16:37 s/ETSI people/ETRI people/ 13:16:45 http://www.etsi.org/deliver/etsi_ts/102700_102799/102796/01.02.01_60/ts_102796v010201p.pdf 13:16:48 s/ for broadband/broadband/ 13:16:57 skim13: Maybe we can re-use some of what's in the spec 13:17:33 olivier: So the recommendation is to re-use some of the concepts, but we'll need to see how that relates to W3C-based web platform architecture. 13:17:48 olivier: Is there any volunteer to look into these features? 13:18:45 Zakim, unmute e 13:18:45 sorry, ddavis, I do not know which phone connection belongs to e 13:18:47 Zakim, unmute me 13:18:47 ddavis should no longer be muted 13:19:43 ACTION: ddavis to look into what features of existing non-W3C specs can be re-used in web platform for Gap Analysis of Req 9 13:19:44 Created ACTION-152 - Look into what features of existing non-w3c specs can be re-used in web platform for gap analysis of req 9 [on Daniel Davis - due 2013-10-23]. 13:20:03 zakim, mute me 13:20:03 ddavis should now be muted 13:20:03 http://lists.w3.org/Archives/Public/public-web-and-tv/2013Oct/0029.html 13:20:12 olivier: Moving on to req 17 13:20:13 q+ 13:20:34 ack kaz 13:20:43 olivier: There is a related spec that seems to have this feature already 13:21:10 kaz: Does the action item for Daniel include other specs as well, e.g. NHK's Hybridcast, not just HbbTV? 13:21:23 olivier: Possibly. Probably a good idea to start with just one and see how we go. 13:21:46 olivier: Either we don't do anything, we need to integrate something or @@@ 13:22:10 q+ 13:22:14 olivier: E.g. GA for Req 17, the feature in the existing spec should probably be replicated at the JavaScript level. 13:22:19 ack gmandyam 13:22:42 i/Either/kaz: ok. So Daniel can start with HbbTV 13:22:49 gmandyam: Is there are requirement for a specific format for ESG? Is it left up to the service implementation? 13:23:19 olivier: Good question. I think what we were talking about is that ESG is more of an implementation that uses several of the requirements we have 13:23:29 olivier: E.g. exposing channels and controlling them. 13:24:02 gmandyam: I agree with that. We support ATSC 3.0 which has different requirements. 13:24:26 +q 13:24:28 gmandyam: I'm not seeing any direct dependencies on any particular ESG so I think we're OK. 13:24:48 olivier: maybe we should clarify this when we publish our findings. 13:25:02 olivier: We might want to make it clear in our use cases. 13:25:13 olivier: The Tablet EPG is somewhat similar. 13:25:18 http://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases 13:25:26 http://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases#3._.22Use_Case_Three_.E2.80.93_Tablet_EPG.22 13:25:39 https://docs.google.com/spreadsheet/ccc?key=0AvACjV6qSvmxdEctdjYwa2JOalZLOG10elE1LVRZNlE#gid=0 13:26:09 olivier: The EPG use case is covered by a number of requirements. 13:26:25 olivier: That has been our approach so far - EPG/ESG are served by our requirements. 13:26:30 Zakim, unmute me 13:26:30 ddavis should no longer be muted 13:26:42 ack Sheau 13:26:44 zakim, mute me 13:26:44 ddavis should now be muted 13:27:12 Sheau: Some of these topics are probably going to be worked on by ATSC 3.0 as well. 13:27:32 Sheau: So this gap analysis is looking back rather than looking sideways. Other organisations are surely working on these issues. 13:27:42 q+ 13:27:45 Sheau: I believe we have a liaison with some of these groups already. 13:27:50 ack gmandyam 13:27:55 Sheau: What should we do? 13:28:18 gmandyam: With the ATSC, I'm putting together a draft with a listing of the relevant requirements for v. 3.0. 13:28:33 gmandyam: ATSC has already prepared a liaison, not sent yet. 13:29:03 gmandyam: Starting with the gap analysis on the HbbTV doc will satisfy a lot of the ATSC requirements, this group should receive a liaison to take care of this. 13:29:16 Sheau: We're already very active on ATSC 3.0 13:29:30 Sheau: Maybe we can expedite things or explore further 13:29:55 gmandyam: These liaisons are being created by the ATSC S34 group which deals with the presentation layer. 13:30:37 olivier: Would we, as a group consider HbbTV or ATSC standards good enough or would we need another specification elsewhere to tackle these requirements. 13:31:06 olivier: I would say as long as there's a way for us to refer to those works in progress, we should say in our analysis when we know of similar work elsewhere. 13:31:19 olivier: It doesn't seem honest and useful to just ignore similar external work. 13:31:39 Sheau: I wonder whether we would, through the liaison, put forward our desire. 13:32:17 q+ to count IPTVF-J as well, because they already have an official liaison with W3C 13:32:28 Sheau: Insofar as ATSC falls within an HTML/browser environment, that falls inside HTTP protocol and we should ensure there is minimal divergence between the two groups. 13:32:55 Sheau: If ATSC starts using HTTP or some W3C protocol, we need to be aligned. 13:32:58 ack kaz 13:33:06 kaz, you wanted to count IPTVF-J as well, because they already have an official liaison with W3C 13:33:30 kaz: We should include IP TV Forum Japan as well. 13:33:45 olivier: Does OIPF count as well? 13:33:47 s/IP TV Forum/IPTV Forum/ 13:33:55 olivier: Should we have a liaison with OIPF as well? 13:34:18 kaz: We do have a liaison with OIPF as well 13:34:36 -> http://www.w3.org/2001/11/StdLiaison Liaison table 13:34:55 olivier: Let's move on - looking at the spreadsheet 13:34:57 https://docs.google.com/spreadsheet/ccc?key=0AvACjV6qSvmxdEctdjYwa2JOalZLOG10elE1LVRZNlE#gid=1 13:35:53 olivier: There are a number of existing W3C specs, at different stages of progress, and the spreadsheet tries to match them with our requirements. 13:36:02 olivier: We should review and edit them a bit. 13:36:46 olivier: In column G, Giuseppe asked the point of including this - it's not a specification. 13:37:02 olivier: I'd suggest dropping this because we have Media Source Extensions to cover this. 13:37:04 +1 13:37:13 +2 13:37:25 +1 13:37:43 olivier: OK, done 13:37:55 olivier: NSD API is the most worked-on column so far 13:37:58 q+ 13:38:10 zakim, unmute me 13:38:10 ddavis should no longer be muted 13:38:36 ack ddavis 13:39:41 ddavis: I had a hard time understanding the difference between "aggregation of services" and "service discovery" 13:40:20 olivier: One way we can say that is that NSD allows you to aggregate with some work by content creators on top. 13:41:07 olivier: I think there are two meanings we should show in the table. 13:41:37 olivier: One is that the spec doesn't cover it but it should (e.g. red cross), the other is that we're not sure (e.g. a yellow question mark) 13:42:52 olivier: So a red cross would mean the requirement is not possible with the current version of that spec. 13:43:15 olivier: At the end of this process, we should have a number of requirements for different groups - the red crosses would indicate this. 13:43:40 olivier: No objections - let's go with that symbol/colour choice. 13:44:15 olivier: Giuseppe says, in row 8, column B, he doesn't think NSD is in scope to handle authentication. 13:46:10 ddavis: Security is being discussed re. NSD API with the DAP WG, so some kind of authentication could be being looked at. 13:46:16 olivier: Let's put it as a question mark. 13:46:38 olivier: Tuner control, could this be covered by a different spec and not NSD API? 13:46:48 q+ 13:46:54 ack gmandyam 13:47:12 gmandyam: The NSD API is meant to cover UPnP, Bonjour, etc. 13:47:37 gmandyam: I thought tuner control was something more general than that, so I don't know why you'd want to shoehorn that into NSD. 13:47:42 ddavis: I agree 13:47:56 olivier: Let's say there's some doubt as to whether this is the right place for it. 13:48:41 olivier: Given the difference in opinion, this is a question mark. 13:48:57 olivier: Given the time, let's move on to column G which I've worked on. 13:49:09 olivier: Maybe we can then assign different columns to different people. 13:49:22 olivier: Column G is EME. 13:49:42 olivier: At the bottom of the list of requirements, row 25 & 26, EME is all about content protection. 13:50:07 olivier: Looking at the spec, it seems that offline protection could be taken care of by EME. 13:50:29 olivier: EME only provides an interface to the content decryption module (CDM). 13:50:43 olivier: The CDM could be online or offline, so I think EME covers this requirement. 13:51:09 Sheau: I'd like to confirm that with Mark Vickers. 13:51:40 olivier: I sent an email about this earlier which maybe Mark can answer. I think it should be a "yes" but let's put it as a question mark for now. 13:52:15 olivier: I believe EME can also be used for device authentication (row 8) 13:52:35 olivier: Regarding row 11, Local Access Control, I don't know if this is what EME should be able to do. 13:52:42 q? 13:52:45 olivier: So I'm putting that as a question mark 13:53:39 olivier: Would anyone like to commit to looking into a particular spec, for example WebRTC? 13:54:00 gmandyam: I can look into it, but in what context? 13:54:39 gmandyam: WebRTC is a peer-to-peer tech - how does it relate to TV? 13:55:21 ddavis: Something like the "Device-to-device content transfer" could be relevant. 13:55:37 gmandyam: There could be issues with content protection there. 13:56:00 ACTION: gmandyam to look through WebRTC column in gap analysis document - due in 2 weeks 13:56:01 Created ACTION-153 - Look through webrtc column in gap analysis document [on Giridhar Mandyam - due 2013-10-30]. 13:56:38 olivier: There's already been an entry for Web Storage. Do we have a volunteer to look at Web Storage and File API together please? 13:57:18 Sheau: Generally we would want a qualification who knows something about the particular spec, right? 13:57:32 olivier: Yes, even for a first pass, an educated guess would be good. 13:57:57 Sheau: I would volunteer for either web Storage or Media Source Extensions, but not within the next 2 weeks 13:58:50 ACTION: Sheau to look through Web Storage column in the gap analysis doc - due in 4 weeks 13:58:50 Created ACTION-154 - Look through web storage column in the gap analysis doc [on Sheau Ng - due 2013-11-13]. 13:58:51 olivier: The goal is to have most of it done by the time we meet at TPAC 13:58:52 q+ 13:58:56 ack ddavis 13:59:31 ddavis: We should note in the spreadsheet who's looking at each spec and whether the analysis has been done. 13:59:41 olivier: I'll do that at the top of each column. 14:00:28 olivier: Any other specs that someone could take a look at? Would be good to get about a half done. 14:01:02 olivier: You don't have to be an expert - just read through the spec a bit to understand it roughly. 14:01:24 ACTION: olivier to look through MSE column in gap analysis 14:01:24 Created ACTION-155 - Look through mse column in gap analysis [on Olivier Thereaux - due 2013-10-23]. 14:01:39 ACTION: bin to look through server-sent events columns in gap analysis doc 14:01:40 Created ACTION-156 - Look through server-sent events columns in gap analysis doc [on Bin Hu - due 2013-10-23]. 14:01:50 ACTION: bin to look through push api column in gap analysis doc 14:01:50 Created ACTION-157 - Look through push api column in gap analysis doc [on Bin Hu - due 2013-10-23]. 14:02:15 olivier: Any other volunteers for another column? 14:04:28 ddavis: Manifest for Web Applications is probably not going to be worked on further. 14:04:28 ACTION: sheau to look through manifest/appcache column, to be used as input for service worker - due in 4 weeks 14:04:29 Created ACTION-158 - Look through manifest/appcache column, to be used as input for service worker [on Sheau Ng - due 2013-11-13]. 14:04:46 ACTIOM: sheau to look through messaging api column - due in 4 weeks 14:04:58 ACTION: sheau to look through messaging api column - due in 4 weeks 14:04:58 Created ACTION-159 - Look through messaging api column [on Sheau Ng - due 2013-11-13]. 14:05:00 ddavis: We can see what Manifest for Web Apps covers already, but we probably can't get new features added to it. Instead, they may be added to ServiceWorker. 14:05:29 zakim, close agendum 2 14:05:29 agendum 2, Review of gap analysis, closed 14:05:30 I see 3 items remaining on the agenda; the next one is 14:05:30 3. Assign further gap analysis [from olivier] 14:05:30 olivier: Thanks everyone. We have some good coverage there and can use the mailing list for me. 14:05:37 zakim, close agendum 3 14:05:37 agendum 3, Assign further gap analysis, closed 14:05:38 I see 2 items remaining on the agenda; the next one is 14:05:38 4. AOB [from olivier] 14:05:49 q+ 14:05:57 ack ddavis 14:06:25 ddavis: bizdev - we are interested in work of the IG. put a summary into a slide deck 14:06:34 ... and pointed to UC&R documents 14:06:39 q+ 14:06:43 ack me 14:07:36 q+ 14:07:38 q- 14:07:52 ack kaz 14:08:04 action: ddavis to forward slide deck of use cases to TV IG 14:08:04 Created ACTION-160 - Forward slide deck of use cases to tv ig [on Daniel Davis - due 2013-10-23]. 14:09:23 zakim, take up agendum 5 14:09:23 agendum 5. "Next meeting" taken up [from olivier] 14:09:50 s/bizdev/the W3C Business Development Team/ 14:09:55 olivier: Next meeting is on 30th October. Is that OK with everyone? 14:10:16 olivier: No objections so that's confirmed. 14:10:38 olivier: That's all for today - let's continue on the mailing list. 14:10:54 -sheau 14:10:54 olivier: Thanks everyone, have a good morning/day/evening/night. 14:10:55 -gmandyam 14:10:57 -Bin_Hu 14:10:57 -olivier 14:11:00 skim13 has left #webtv 14:11:00 whyun has left #webtv 14:11:00 -Kazuyuki 14:11:02 -ddavis 14:11:13 [ adjourned ] 14:11:23 rrsagent, generate minutes 14:11:23 I have made the request to generate http://www.w3.org/2013/10/16-webtv-minutes.html ddavis 14:11:36 regrets: Giuseppe, JC, Mark 14:11:44 Chair: Olivier 14:11:49 rrsagent, draft minutes 14:11:49 I have made the request to generate http://www.w3.org/2013/10/16-webtv-minutes.html kaz 14:13:22 -skim13 14:13:23 UW_WebTVIG()9:00AM has ended 14:13:23 Attendees were Kazuyuki, Bin_Hu, ddavis, sheau, gmandyam, olivier, skim13 14:19:15 I can add the link on the wiki when you send the minutes link to the ML 14:19:21 zakim, bye 14:19:21 Zakim has left #webtv 14:19:27 rrsagent, bye 14:19:27 I see 9 open action items saved in http://www.w3.org/2013/10/16-webtv-actions.rdf : 14:19:27 ACTION: ddavis to look into what features of existing non-W3C specs can be re-used in web platform for Gap Analysis of Req 9 [1] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T13-19-43 14:19:27 ACTION: gmandyam to look through WebRTC column in gap analysis document - due in 2 weeks [2] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T13-56-00 14:19:27 ACTION: Sheau to look through Web Storage column in the gap analysis doc - due in 4 weeks [3] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T13-58-50 14:19:27 ACTION: olivier to look through MSE column in gap analysis [4] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T14-01-24 14:19:27 ACTION: bin to look through server-sent events columns in gap analysis doc [5] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T14-01-39 14:19:27 ACTION: bin to look through push api column in gap analysis doc [6] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T14-01-50 14:19:27 ACTION: sheau to look through manifest/appcache column, to be used as input for service worker - due in 4 weeks [7] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T14-04-28-1 14:19:27 ACTION: sheau to look through messaging api column - due in 4 weeks [8] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T14-04-58 14:19:27 ACTION: ddavis to forward slide deck of use cases to TV IG [9] 14:19:27 recorded in http://www.w3.org/2013/10/16-webtv-irc#T14-08-04 14:19:35 Thanks olivier