13:52:40 RRSAgent has joined #tvapi 13:52:40 logging to http://www.w3.org/2015/01/20-tvapi-irc 13:52:42 RRSAgent, make logs 385 13:52:42 Zakim has joined #tvapi 13:52:44 Zakim, this will be 13:52:44 I don't understand 'this will be', trackbot 13:52:45 Meeting: TV Control API Community Group Teleconference 13:52:45 Date: 20 January 2015 13:54:45 seanlin2 has joined #tvapi 13:57:17 zakim, this will be tvapi 13:57:17 ok, ted; I see WEBT_TVAPICG()9:00AM scheduled to start in 3 minutes 13:58:45 skim13 has joined #tvapi 13:59:03 cpn has joined #tvapi 13:59:26 zakim, code? 13:59:26 the conference code is 88274 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), kaz 13:59:34 zakim, who is here? 13:59:34 WEBT_TVAPICG()9:00AM has not yet started, kaz 13:59:36 On IRC I see cpn, skim13, seanlin2, Zakim, RRSAgent, ted, kaz, alexerk, trackbot 13:59:44 WEBT_TVAPICG()9:00AM has now started 13:59:52 +Andreas 14:00:18 + +1.317.475.aaaa 14:00:19 + +28786aabb 14:00:29 +Ted 14:00:30 + +44.303.040.aacc 14:00:44 zakim, call kazuyuki-617 14:00:44 ok, kaz; the call is being made 14:00:46 +Kazuyuki 14:00:59 zakim, who is here? 14:00:59 On the phone I see Andreas, +1.317.475.aaaa, +28786aabb, +44.303.040.aacc, Ted, Kazuyuki 14:01:02 On IRC I see cpn, skim13, seanlin2, Zakim, RRSAgent, ted, kaz, alexerk, trackbot 14:01:14 +Paul_Higgs 14:01:15 Bin_Hu has joined #tvapi 14:01:25 zakim, aacc is cpn 14:01:26 +cpn; got it 14:01:38 zakim, aaaa is ryan 14:01:38 +ryan; got it 14:01:58 zakim, who is here? 14:01:58 On the phone I see Andreas, ryan, +28786aabb, cpn, Ted, Kazuyuki, Paul_Higgs 14:02:00 On IRC I see Bin_Hu, cpn, skim13, seanlin2, Zakim, RRSAgent, ted, kaz, alexerk, trackbot 14:02:04 + +1.650.946.aadd 14:02:08 +[IPcaller] 14:02:09 Paul_Higgs has joined #tvapi 14:02:17 zakim, aadd is me 14:02:18 +Bin_Hu; got it 14:02:34 zakim, IPcaller is skim13 14:02:35 +skim13; got it 14:02:36 -skim13 14:02:45 zakim, who is here? 14:02:45 On the phone I see Andreas, ryan, +28786aabb, cpn, Ted, Kazuyuki, Paul_Higgs, Bin_Hu 14:02:47 On IRC I see Paul_Higgs, Bin_Hu, cpn, skim13, seanlin2, Zakim, RRSAgent, ted, kaz, alexerk, trackbot 14:02:49 ddavis has joined #tvapi 14:02:58 +[IPcaller] 14:03:00 zakim, where is 287 14:03:00 kaz, I do not see a party named 'where'. If you meant to ask a question you need to add '?' 14:03:17 zakim, IPcaller is skim13 14:03:17 +skim13; got it 14:03:29 zakim, aabb is seanlin2 14:03:29 +seanlin2; got it 14:03:34 tidoust has joined #tvapi 14:03:36 zakim, who is here? 14:03:36 On the phone I see Andreas, ryan, seanlin2, cpn, Ted, Kazuyuki, Paul_Higgs, Bin_Hu, skim13 14:03:38 On IRC I see tidoust, ddavis, Paul_Higgs, Bin_Hu, cpn, skim13, seanlin2, Zakim, RRSAgent, ted, kaz, alexerk, trackbot 14:03:54 +??P4 14:03:57 zakim, ??P4 is me 14:03:57 +tidoust; got it 14:04:00 zakim, mute me 14:04:02 tidoust should now be muted 14:04:15 +??P5 14:04:18 zakim, ??P5 is me 14:04:18 +ddavis; got it 14:04:19 zakim, who is here? 14:04:19 On the phone I see Andreas, ryan, seanlin2, cpn, Ted, Kazuyuki, Paul_Higgs, Bin_Hu, skim13, tidoust (muted), ddavis 14:04:22 On IRC I see tidoust, ddavis, Paul_Higgs, Bin_Hu, cpn, skim13, seanlin2, Zakim, RRSAgent, ted, kaz, alexerk, trackbot 14:05:19 zakim, unmute me 14:05:19 tidoust should no longer be muted 14:05:44 zakim, mute me 14:05:44 tidoust should now be muted 14:05:44 zakim, pick francois as the scribe :) 14:05:44 scribe: Francois 14:05:45 I'm glad that smiley is there, kaz 14:05:48 scribenick: tidoust 14:06:18 Bin: First meeting of our group in 2015. 14:06:28 agenda: https://lists.w3.org/Archives/Public/public-tvapi/2015Jan/0000.html 14:07:10 ... Francois is from W3C, joining us today. Ryan Davis is from iHeartMedia in Automotive BG, joining us as well: 14:07:44 Ryan: Hi. I had reviewed before the TV tuner requirements and mapping table to see commonalities. 14:07:57 q+ 14:08:14 ... There does seem to be commonalities. That's why I think it's good to be listening here, learning for you guys. 14:08:17 zakim, unmute me 14:08:17 tidoust should no longer be muted 14:08:49 q? 14:08:50 tidoust: I was at the beginning of the Web and TV IG, working for the W3C then. 14:09:08 i/I was/scribenick: ddavis/ 14:09:11 tidoust: I've been back at the W3C for the past 9 months interested in TV work. 14:09:13 zakim, mute me 14:09:13 tidoust should now be muted 14:09:19 scribenick: tidoust 14:09:22 q? 14:10:04 Daniel: A question to Ryan. The TV control API is what we're working. Why would that be appealing for Automotive people? 14:10:14 Ryan: I think of it as a media tuner API. 14:10:17 q+ 14:10:22 ack d 14:10:47 ... TV is a source of media. Could be radio or so on. The whole point is the focus on "tuner". 14:11:07 q? 14:11:44 daniel: Indeed, one of the things that got raised at last Web and TV IG F2F was that the API should not focus on broadcast streams of a particular kind, perhaps including broadband streams as well for instance. That resonates well with what you're saying. 14:11:59 Ryan: Right. I don't want to hijack the work of the TV Control API CG, here. 14:12:45 Kaz: Note I work for the Automotive BG as well and mentioned the TV Control API CG there. It should be useful for both groups to collaborate together 14:12:49 http://www.w3.org/community/tvapi/wiki/Main_Page/Agenda_Telco_Jan_20_2015 14:13:05 Bin: Let's move on with the agenda. 14:13:16 Topic: Review open action items 14:13:21 ACTION-9? 14:13:21 ACTION-9 -- Sung Hei Kim to Link to the requirement and circulate the skeleton document -- due 2014-08-12 -- CLOSED 14:13:21 http://www.w3.org/community/tvapi/track/actions/9 14:13:48 rrsagent, make log public 14:13:53 rrsagent, draft minutes 14:13:53 I have made the request to generate http://www.w3.org/2015/01/20-tvapi-minutes.html kaz 14:13:58 Bin: Action to circulate the skeleton document is now done. Sung was instrumental in that, thanks a lot! Great work and great discussions! 14:14:18 ACTION-21? 14:14:18 ACTION-21 -- Bin Hu to Contact hbbtv regarding their specification -- due 2014-12-02 -- OPEN 14:14:18 http://www.w3.org/community/tvapi/track/actions/21 14:14:19 zakim, who is here? 14:14:19 On the phone I see Andreas, ryan, seanlin2, cpn, Ted, Kazuyuki, Paul_Higgs, Bin_Hu, skim13, tidoust (muted), ddavis 14:14:22 On IRC I see tidoust, ddavis, Paul_Higgs, Bin_Hu, cpn, skim13, seanlin2, Zakim, RRSAgent, ted, kaz, alexerk, trackbot 14:14:47 Present: Andreas, Ryan, Sean, cpn, Ted, Kaz, Paul, Bin, skim, Francois, Daniel 14:14:53 Chair: Bin 14:14:55 Bin: About contacting HbbTV, Francois got in touch with IRT. Don't know if they are around today, but that's going in the right direction. 14:15:15 ... Good to have HbbTV presence in the work of the CG. 14:15:36 Topic: Status update of the draft of technical specification 14:16:00 i/First meeting/topic: Roll call, Introduction and Call for Scribe/ 14:16:05 rrsagent, draft minutes 14:16:05 I have made the request to generate http://www.w3.org/2015/01/20-tvapi-minutes.html kaz 14:16:19 Bin: Good discussions. Sung has updated the specification, available on GitHub, and shared yesterday. 14:16:45 ... Thank you for everybody who contributed to the discussion on fixing references to Promises, now part of ES6. 14:16:49 s/Sung/Sean/ 14:17:10 ... I'll leave the floor to Sean to present the draft spec. 14:18:34 Alex: Sorry to interrupt, this is Alexander Erk from IRT. First call for me. For me and my colleague Michael Probst, it's new. Just wanted to raise the fact that we've started a RadioWEB in RadioDNS and looking for participation in that group.. 14:18:49 Bin: Thanks a lot Alex for the introduction. 14:19:16 ... We are a very open group and are looking forward to your contributions to the group. 14:19:24 Present: Alex, Ryan, Sean, cpn, Ted, Kaz, Paul, Bin, skim, Francois, Daniel 14:19:40 ... You're very welcome! 14:20:14 Sean: The current draft is characterized by a few components. 14:20:50 jcverdie has joined #tvapi 14:20:52 ... We have a TVManager that gives a list of TVTuner with several TVSource that give access to the EPG. 14:21:03 ... In turn, we get access to channels and programs. 14:21:20 ... Also, some support for scanning channels. 14:21:38 -> https://github.com/w3c/tvapi TV Control API draft on Github 14:21:54 ... I think that's what we have right now. 14:22:24 Bin: The current spec is a subset of the requirements that we have come up with. 14:22:26 s/... I think/Sean: I think/ 14:22:56 rrsagent, draft minutes 14:22:56 I have made the request to generate http://www.w3.org/2015/01/20-tvapi-minutes.html kaz 14:22:58 Bin: General channel and program requirements are well covered, I think. 14:23:20 ... For EPG requirements, there's perhaps still a gap there 14:23:29 ... That's a very good starting point. 14:23:52 ... Next step for the group is to review the current specification and to identify the gaps in terms of meeting the requirements. 14:24:06 -> http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements Requirements wiki 14:24:28 Bin: I'm particularly interested from people from other companies who have not yet contributed to the discussions. 14:24:55 q? 14:24:57 ack k 14:25:00 ... Also, there might be some interest to adjust requirements. 14:25:16 zakim, who is speaking? 14:25:28 kaz, listening for 10 seconds I heard sound from the following: Paul_Higgs (34%) 14:25:53 Paul: I don't see parental lock in the current API. 14:26:06 ... Are we expecting more? 14:26:27 http://www.w3.org/community/tvapi/wiki/Main_Page/Requirements_Mapping 14:26:49 q+ to ask if we should add marks to the requirements wiki saying which is included in the spec 14:27:26 Sean: For parental controls, at the time when we did some gap analysis, the Mozilla TV API had some parental control stuff but we felt the features were not quite ready yet so we trimmed them out of scope. 14:27:45 ... I think it's just a time gap between the gap analysis and the development of the API. 14:27:57 ... Now the goal is to evolve the baseline that we have right now. 14:28:00 q? 14:28:26 ... We don't have parental control in this draft. I think that's one item we should mark as "orange" and not as "green". 14:28:42 q? 14:28:50 Paul: OK, I was looking at work items that we still had to work upon, but see it's not necessarily accurate anymore. 14:29:22 ack k 14:29:22 kaz, you wanted to ask if we should add marks to the requirements wiki saying which is included in the spec 14:29:25 Kaz: We might want to add one more column that represents our current spec 14:29:31 Bin: That's a good point, yes. 14:29:45 ... That will help measure the progress of the spec. 14:29:54 s/column/column to the mapping table/ 14:30:21 Bin: Who wants to take this action? 14:30:44 ... Maybe Paul? 14:31:06 Paul: I cannot take it right now. I don't have the bandwidth, I'm afraid. 14:31:28 Daniel: I can have a look 14:31:52 ACTION: Daniel and Kaz to add a column to the mapping table to measure the progress of our specification. 14:31:53 Created ACTION-22 - And kaz to add a column to the mapping table to measure the progress of our specification. [on Daniel Davis - due 2015-01-27]. 14:32:00 kaz: I can help 14:32:31 Bin: Any other question? 14:33:37 Alex: A very generic question. Sorry if it's out of scope. Right now, you're very focused on TV. Assuming that the API you're specifying on a DVB platform that could include radio services. To what point can we reuse the current spec? 14:33:50 ... It might be just a matter of renaming interfaces. 14:34:29 Bin: Very good question. My understanding of how the API can support radio: the scope of the group is to define an API that is agnostic of the underlying technology. 14:34:53 ... So indeed, it should support signals of different types and formats, including radio. 14:35:22 ... It should also be able to manage channels of a given type 14:36:09 ... Need some way to advertize the fact that a channel is pure audio or audio and video. 14:36:28 Alex: so an implementation for radio is in scope for this group? 14:36:59 Bin: It's not out of scope. Same type of scenario as playing TV channels. 14:37:09 q+ 14:37:13 zakim, unmute me 14:37:13 tidoust should no longer be muted 14:37:22 ack t 14:37:54 tidoust: Based on that, should we start renaming things within the spec? They're currently using "TV". 14:38:03 zakim, mute me 14:38:03 tidoust should now be muted 14:39:00 Bin: I would wait until we have a mechanism to identify the type of channel, which Alex could perhaps contribute. 14:39:27 -cpn 14:39:47 ... I would rather focus on features before worrying about names 14:39:47 q+ 14:40:53 Kaz: I think Bin's response is reasonable at this point. I would add an editor's note in the meantime to the spec to clarify that the goal is not to exclude radio. Then, at some point, we can change the name. 14:40:56 ack k 14:41:47 + +44.303.040.aaee 14:41:55 zakim, aaee is cpn 14:41:55 +cpn; got it 14:42:35 Alex: Thanks, we will have a closer look at the current draft. As said earlier, we submitted last week our first draft in the Radio WEB group. If it's ok with you, I would try to complete the mapping table from a radio perspective. 14:43:16 ... I agree with your point about leaving naming problems for the end. The architecture of the spec is more important. 14:43:57 Ryan: Indeed, we can place placeholders in the spec as suggested. 14:45:17 Ryan: The task force is from the Automotive and Web Platform Business Group. I'll share links when we have them. 14:45:40 -ddavis 14:45:50 http://www.w3.org/community/autowebplatform/ 14:45:52 Bin: Ryan, I haven't seen a lot of activity over there. Could you introduce the Media Task Force? Background, goals? 14:45:55 [ a link should be added to the BG's wiki page at: http://www.w3.org/community/autowebplatform/wiki/Main_Page ] 14:46:06 https://www.w3.org/community/autowebplatform/wiki/images/8/8e/Obigo_Navigation_FM_Tuner_API_W3C_Proposal_20140318.pdf 14:46:38 Ryan: We just kicked this off, right before the holidays. Our focus is to create an open media tuner API specification for the vehicle. 14:46:50 ... Right now, we're still in the middle of scope. 14:47:31 ... There is kind of an infinite scope in the automotive world. Part of the discussion is trying to understand what the differences are so we can write requirements around it. 14:47:53 i|We just kicked|[ cpn, the above is a use case of Obigo, one of the BG participants ]| 14:47:53 Bin: I'm looking forward for news on your side. 14:48:19 rrsagent, draft minutes 14:48:19 I have made the request to generate http://www.w3.org/2015/01/20-tvapi-minutes.html kaz 14:49:00 Bin: Any other suggestion? 14:49:50 ... If not, I encourage you to take a look at the spec, and send comment to the mailing-list. Meanwhile, Daniel and Kaz will survey gaps in the mapping table. 14:50:07 -ryan 14:50:07 ... Talk to you in about 4 weeks! 14:50:08 -Paul_Higgs 14:50:09 -Ted 14:50:09 -Andreas 14:50:11 -skim13 14:50:13 -cpn 14:50:13 -Bin_Hu 14:50:13 RRSAgent, draft minutes 14:50:13 I have made the request to generate http://www.w3.org/2015/01/20-tvapi-minutes.html tidoust 14:50:14 -seanlin2 14:50:14 -Kazuyuki 14:50:16 skim13 has left #tvapi 14:50:47 -tidoust 14:50:47 WEBT_TVAPICG()9:00AM has ended 14:50:47 Attendees were Andreas, +1.317.475.aaaa, +28786aabb, Ted, +44.303.040.aacc, Kazuyuki, Paul_Higgs, cpn, ryan, +1.650.946.aadd, Bin_Hu, skim13, seanlin2, tidoust, ddavis, 14:50:47 ... +44.303.040.aaee 14:51:53 zakim, bye 14:51:53 Zakim has left #tvapi 14:56:53 jcverdie has joined #tvapi 15:03:25 jcverdie has joined #tvapi 15:11:15 cpn has left #tvapi 15:16:15 Hello jcverdie 15:16:33 Still here? 15:27:52 RRSAgent, bye 15:27:52 I see 1 open action item saved in http://www.w3.org/2015/01/20-tvapi-actions.rdf : 15:27:52 ACTION: Daniel and Kaz to add a column to the mapping table to measure the progress of our specification. [1] 15:27:52 recorded in http://www.w3.org/2015/01/20-tvapi-irc#T14-31-52