14:00:13 RRSAgent has joined #tvapi 14:00:13 logging to http://www.w3.org/2016/03/08-tvapi-irc 14:00:42 tidoust has joined #tvapi 14:02:04 present+ Kaz 14:02:06 Bin_Hu has joined #tvapi 14:03:32 Present+ Francois 14:03:36 RRSAgent, draft minutes 14:03:36 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html tidoust 14:04:00 RRSagent, make logs public 14:04:29 Meeting: TV Control API CG call 14:04:32 skim13 has joined #tvapi 14:04:35 Chair: Bin 14:04:45 Present+ Chris 14:04:57 Present+ Igarashi_san 14:05:04 Present+ Ryan_Davis 14:05:05 rrsagent, make log public 14:05:14 Present+ Sung_Hei_Kim 14:05:25 rrsagent, draft minutes 14:05:25 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 14:05:31 Scribe: Chris 14:05:35 Scribenick: cpn 14:05:37 Meeting: TV Control API CG 14:05:43 rrsagent, draft minutes 14:05:43 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 14:05:43 Topic: Review of action items 14:05:59 Bin: The draft WG charter is still out for AC review 14:06:05 present+ Bin, Chris, Igarashi, Paul, Ryan, SungHei 14:06:10 Chair: Bin 14:06:16 Bin: so we'll wait for the outcome of the review 14:06:18 rrsagent, draft minutes 14:06:18 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 14:06:47 Bin: We had a good discussion last time, thanks Chris and Ryan 14:07:07 ... There are 3 actions from last time 14:07:46 ... reviewed automotive work and security work 14:08:14 ... don't think we need changes to the draft 14:08:41 ... maybe we can ask Ryan about the latest status of the automotive group 14:09:02 ryan: my update on the media tuner or the automotive in general? 14:09:21 cpn: security work specifically 14:09:41 Kaz: The automotive security TF has been working on use cases and requirements in a google doc 14:09:57 ... Also work on some basic architecture since the TPAC meeting 14:10:09 ... There was some detailed discussion at the Paris meeting, with Genivi 14:11:05 -> https://www.w3.org/2016/03/03-auto-minutes.html auto minutes - Mar. 3 14:11:40 ... We recently have another security expert, from New Sky Security, which should accelerate the security discussion 14:12:35 -> https://www.w3.org/auto/security/wiki/ASP_TF security wiki 14:12:53 Bin: We should continue to contact with this expert and see how their security model could apply to our use case 14:13:31 ... So, we could leave this action open, as we haven't identified the impact on our spec yet 14:13:52 ... And maybe Kaz can help get in contact with the automotive TF 14:14:07 ... You could also join the security TF call 14:15:07 Chris: I think there are other good W3C resources. There's a fingerprinting guidance document, security questionnaire, and priviledged Context document 14:15:12 ... All very useful input. 14:15:34 ... It seems useful to go through each of our API features and evaluate them against these documents. 14:15:47 ... E.g. the ability to scan/list channels, to schedule recordings, etc. 14:16:01 ... Each of these areas may have different level of impacts. 14:16:26 ... I noticed in the NFC CG that they produced a report on security and privacy considerations. 14:16:32 http://w3c.github.io/web-nfc/security-privacy.html -- NFC report 14:17:10 ... The Permissions API is interesting for us. It allows the user to allow or deny a particular API. 14:17:35 ... I don't know if that's the right model for us, or if we need something different for that. 14:18:15 -> https://www.w3.org/2015/10/26-27-auto-minutes.html auto tpac minutes 14:18:21 ... Something I heard from the Automotive meeting at TPAC: two possible runtimes, regular Web runtime and Web-view runtime with the possibility to deliver a signed package. 14:19:17 ... In some other specification that I've looked at, the Generic Sensors API just says that some reading should be only available to secure contexts. 14:19:39 -> https://www.w3.org/TR/2015/WD-generic-sensor-20151015/ generic sensor api 14:20:09 The draft on github: https://w3c.github.io/sensors/ 14:20:23 https://w3c.github.io/fingerprinting-guidance/ 14:20:34 https://www.w3.org/TR/permissions/ -- permissions API 14:20:46 i/Chris: I think there are other/scribe: tidoust/ 14:20:51 https://www.w3.org/TR/powerful-features/ -- privileged contexts 14:20:53 rdavis has joined #tvapi 14:21:05 rrsagent, draft minutes 14:21:05 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 14:21:18 s|-> https://www.w3.org/TR/2015/WD-generic-sensor-20151015/ generic sensor api|| 14:21:22 rrsagent, draft minutes 14:21:22 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 14:21:44 Chris: This all relates to some of the requirements we may have around the visibility of EPG metadata 14:22:19 ... Do we allow arbitrary Web pages to have access to EPG data? Or is it something that we may want to constrain to certain restricted contexts. 14:22:30 ... There may be business incentive to restrict access. 14:23:04 ... It's not just the end-user privacy, also need to consider the content provider's side as well. 14:23:18 q+ 14:23:21 Bin: Right, it's still a debatting point in most of these markets. 14:23:42 ack k 14:23:57 scribe: Chris 14:24:26 Kaz: On the previous aotomotive call there was some discussion, what should the destination device should this be? 14:24:28 Kaz: In the Automotive API, the discussion is also about the destination server for the EPG data. Is it localhost? 14:24:39 ... Some server-based URL? 14:24:52 ... The security depends on the destination as well 14:25:02 Bin: I guess there are no answers yet. 14:25:54 ... So one of the areas to investigate is full/restricted access to EPG data. 14:26:18 Kaz: The NFC started similar kinds of discussions, the result is great. 14:26:29 s/NFC/NFC CG/ 14:26:41 Bin: I propose to leave these action items open and create two additional action items 14:27:15 ACTION: Kaz to get in touch with security experts in the Automotive group 14:27:17 Error creating an ACTION: data field(s) missing from result. Please mail with details about what happened. 14:27:58 ACTION: Bin to draft a Wiki page listing high-level requirements related to restricted access to EPG metadata for the sake of security. 14:27:58 Error creating an ACTION: data field(s) missing from result. Please mail with details about what happened. 14:28:18 Chris: Should we do that on the Wiki, or create a report using ReSpec? 14:28:31 ... I'm just looking at the NFC group and they published this as a CG report. 14:28:49 Bin: Right, that's a final report, but I'm more interested to collect requirements here. 14:29:23 ... Once we have done that, we may decide whether to publish a report. 14:31:07 scribenick: cpn 14:32:06 Ryan: [shows the automotive tuner use cases] 14:32:49 ... All of these pertain to the media tuner API. The functional owner shows who has the information that's needed in each case 14:33:52 ... Some of these have multiple owners, e.g., for the parental lock there's both Web Application and Infotainment Systsm 14:34:03 ... That was the premise behind the functional owner 14:34:17 ... All the system functions listed here should all be present in the media tuner API 14:34:27 ... Based on what's needed in current applications today 14:35:00 ... I'm currently reformatting the media tuner web page into the correct format, also to make it more self explanatory 14:35:15 ... I want to create a draft, to put the pieces together 14:35:52 Bin: I have a question about the functional owner. If the owner is the Infotainment System, is it that the functionality needs to be addressed by the API? 14:36:21 Ryan: Not really, all of these need addressing by the API, the owner shows more in which direction the information flows 14:37:02 ... For example, the Login function is really for the Web Application's use 14:37:39 Bin: I agree, so all of these need API support, so the question is whether they are defined by us, or somewhere else 14:37:52 Ryan: Yes 14:38:32 Kaz: Is the google spreadsheet public? If so we should put it in the minutes 14:39:17 https://docs.google.com/a/pandora.com/spreadsheets/d/1yEZVIqgtxp-HgW3dZx9qnUzwOLgGmzmkGO-pF7m8noc/edit?usp=sharing 14:39:53 Bin: There's another column for the mapping between the media API and the TV control API 14:40:31 Ryan: Yes, I'll be doing that 14:40:40 Bin: Thanks Ryan for the great work 14:42:01 Action: Ryan to continue use case mapping between the automotive media API and the TV Control API, and start to put together a draft 14:42:02 Error creating an ACTION: data field(s) missing from result. Please mail with details about what happened. 14:43:32 Bin: That completes the review of active items. Is there anything new in terms of Phase 2 contributions? 14:44:17 ... Once Ryan has completed the mapping, there may be some gaps, so we can consider those in our requirements 14:44:47 Bin: Is there any other business? 14:45:03 Kaz: Please ask your AC reps to respond to the WG charter review 14:45:12 (positively :) 14:45:22 Bin: Anything else? 14:45:40 ... Thank you all for your contributions, and we'll speak on the next call in 4 weeks 14:45:43 [adjourned] 14:45:48 skim13 has left #tvapi 14:46:31 rrsagent, draft minutes 14:46:31 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 14:47:23 i/reviewed automotive work/scribenick: kaz/ 14:47:45 i/The automotive security TF has/scribenick: cpn/ 14:47:47 rrsagent, draft minutes 14:47:47 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 14:48:45 present: Kaz, Francois, Chris, Igarashi_san, Ryan, Sung_Hei, Bin, Paul 14:48:47 rrsagent, draft minutes 14:48:47 I have made the request to generate http://www.w3.org/2016/03/08-tvapi-minutes.html kaz 16:59:25 Zakim has left #tvapi 17:03:41 cpn has joined #tvapi 17:11:15 cpn has left #tvapi