13:58:56 RRSAgent has joined #tvapi 13:58:56 logging to http://www.w3.org/2016/01/12-tvapi-irc 13:59:01 cpn has joined #tvapi 14:01:28 hyojin has joined #tvapi 14:01:36 Bin_Hu has joined #tvapi 14:05:11 present: Kaz, amereu, Bin, Chris, Colin, Francois, Hyojin, Sean 14:06:19 present+ Igarashi 14:07:00 scribe: Chris 14:07:04 scribenick: xpn 14:07:07 scribenick: cpn 14:07:38 topic: TV Control API CG 14:07:53 Agenda: https://www.w3.org/community/tvapi/wiki/Main_Page/Agenda_Telco_Jan_12_2016 14:08:48 Bin: recapping the agenda, any other suggestions? 14:08:54 nothing 14:09:09 Topic: Working Group Charter 14:09:14 http://w3c.github.io/charter-drafts/tvcontrol-2015.html 14:09:17 present+ Adam 14:09:20 Bin: Has everybody had a chance to review the charter? 14:09:38 ... Are there any other comments or suggestions? 14:09:56 cpn: multiple deliverables? 14:10:03 ... TV Control API is the main one 14:10:30 ... but possibly to have multiple delivelables as Francois suggested 14:10:53 Francois: I have just updated the draft charter 14:11:03 ... to mention one or more deliverables 14:11:30 -> http://w3c.github.io/charter-drafts/tvcontrol-2015.html#deliverables delivelables section 14:12:36 Chris: I think this is OK as it leaves the scope and decision open for discussion 14:12:49 q+ 14:12:59 ack k 14:13:43 kaz: I also agree. Some WGs produce one report, some produce multiple notes, but the structure can be determined later 14:14:37 Bin: If there are no more comments, I'd say we've acheived consensus on the draft charter 14:14:53 q+ 14:14:59 ... The next step is for Francois to follow up with the AC 14:15:00 ack tidoust 14:15:00 s/acheived/achieved/ 14:15:20 q+ 14:15:30 Francois: Actually, the next thing is to go to W3C management, before going to AC review 14:16:16 ... It's minuted that we have consensus 14:16:46 RESOLUTION: We have consensus on the wording of the draft WG charter 14:16:54 Francois If anyone disagrees with the consensus, now would be a good time to say so 14:17:13 s/Francois If anyone disagrees with the consensus, now would be a good time to say so/Francois: If anyone disagrees with the consensus, now would be a good time to say so/ 14:17:41 s/draft WG charter/draft WG charter so that we will create a WG/ 14:17:51 rrsagent, make log public 14:17:59 rrsagent, draft minutes 14:17:59 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html kaz 14:18:14 q+ 14:18:19 igarashi has joined #tvapi 14:18:22 ack k 14:18:31 Topic: Transition plan from CG to WG 14:18:53 q- 14:19:08 Bin: Once the WG charter is approved, the WG will be officially started 14:19:21 ... And I'd encourage all CG members to join the WG 14:20:03 ... We'll have the first joint meeting of the CG and WG, but there'll be a 3 month transition period 14:20:41 ... During the joint meetings we'll discuss the WG structure, also the phase 2 work to improve the specification 14:21:00 rrsagent, draft minutes 14:21:00 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html kaz 14:21:42 ... There'll be two tracks: the recommendation track and the phase 2 track, and members can decide where to contribute their efforts 14:22:36 ... Looking at the current schedule, there's a meeting June 28th, and we'll propose to close the CG on June 30th and continue work in the WG 14:22:51 ... But we can keep the existing conference call schedule 14:23:02 ... The times could be adjusted based on the progress of work 14:24:15 Chris: At TPAC I think we discussed keeping the CG open to work on some of the phase 2 work, while the WG focuses on the specification 14:24:41 Bin: That's possible, but will be driven by the needs of the members, I'm open to that option 14:24:49 q+ 14:25:29 Kaz: I agree with both of you, but having two groups might make things complicated 14:26:07 s/but having/and having/ 14:26:13 ack k 14:26:29 ... The automotive groups are structured with a WG and a BG 14:26:57 s/The automotive/however, the automotive/ 14:27:06 Bin: I agree, if the focus of each group is clear this can be help 14:27:18 ... So, we'll keep the CG open 14:27:23 ... Thanks Chris for the suggestion 14:27:28 s/BG/BG. the WG works on specs, and the BG works on incubation kind of new work./ 14:29:06 RESOLUTION: We will keep the Community Group open while also creating the Working Group to proceed with the specification work 14:29:18 rrsagent, draft minutes 14:29:18 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html kaz 14:30:20 Bin: Regarding logistics, we should find another time slot for the CG phone call 14:30:33 Topic: Potential implementations 14:31:03 Bin: We'll need to independent implementations of the specification from the WG 14:31:19 ... We have good representation now from implementers 14:31:45 ... Will Mozilla, LG, and Sony be interested in working on implementations? 14:32:01 s/to independent/two independent/ 14:32:58 Bin: Chris, do you expect an implementation on your side? 14:33:23 Chris: That's a good question. It's unlikely you will see a complete implementation from us. We're not browser manufacturers. 14:33:29 i/do you expect/scribenick: tidoust/ 14:33:52 i/multiple delieverables?/scribenick: kaz/ 14:34:01 Chris: But we may want to do some prototyping work. I'll have to discuss with my team here. 14:34:05 i/I have just updated/scribenick: cpn/ 14:34:07 q+ 14:34:13 i/But we may/scribenick: cpn/ 14:34:18 rrsagent, draft mintues 14:34:18 I'm logging. I don't understand 'draft mintues', kaz. Try /msg RRSAgent help 14:34:30 Bin: Ok, maybe we can discuss this offline 14:35:11 Hyojin: I'll will check with the TV division in my company and let you know a contact 14:35:15 rrsagent, draft minutes 14:35:15 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html kaz 14:35:26 s/rrsagent, draft mintues// 14:35:58 i/cpn: multiple/scribenick: kaz/ 14:36:00 rrsagent, draft minutes 14:36:00 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html kaz 14:36:12 Francois: This is an important point that W3C management will review: that there are good implementation plans 14:36:20 q+ 14:36:30 ack t 14:36:34 ... This is one of the criteria for the creation of a WG 14:37:21 ... I'll need this information to go to W3C management, so will follow up privately if people don't want to say in public yet 14:37:37 ... At this stage we just need to put forward a plan 14:38:12 Igarashi: In terms of implementation, should this be in product or as a prototype? 14:38:41 Francois: A prototype is fine, but all I need to know is that there's a plan to do it 14:39:05 ... It doesn't have to be in product, just a plan to write concrete code that implements the spec 14:40:10 ... If the community group can't show that there are potential implementers, the W3C management will see it as premature to move to standardisation 14:40:26 q? 14:40:59 Bin: As Francois has mentioned, to move forward with standardisation, having 2 implementations is a must 14:41:37 ... So we have to have implementations to create the WG 14:41:52 ack k 14:42:49 Kaz: please note that the AC Review will also have a question on potential implementations. So it would be nicer to have active group participants who are interested in implementing the proposed spec./ 14:43:08 s|spec./|spec.| 14:43:19 i/please note/scribenick: kaz/ 14:43:22 scribenick: cpn 14:43:39 rrsagent, draft minutes 14:43:39 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html kaz 14:43:44 q? 14:43:46 Hyojin: What are the scope of the implementations? 14:43:59 q+ 14:44:59 Bin: The implementation will need to cover the conformance class in the specification, and also be public 14:45:51 -> http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html Model CR Exit Criteria (by the HTML WG) 14:47:11 q? 14:47:12 [I note that these exit criteria are those followed by the HTML WG. I think the Process document is less strict on the definition of what constitutes an implementation. These are good criteria though] 14:47:32 http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html 14:48:11 q? 14:48:14 Igarashi: About the public availability, I think the TV Control API can't follow such a requirement, as it can't be implemented in a generic platform such as a PC or Android 14:48:42 ... How can we demonstrate public availability? 14:49:14 Bin: I'll try to draft some language 14:49:40 ... If its not possible for a TV platform to be made public 14:49:59 s/its/it's/ 14:50:39 q? 14:50:42 ... We can clarify the stability, and define a life-cycle for the implementation, e.g., showing it publicly at some event or trade show 14:51:17 igarashi has joined #tvapi 14:51:52 Kaz: There are some basic descriptions in the process document, but the newly created WG can define criteria itself, so we can draft the text later 14:52:18 s/later/later when we go into the CR period/ 14:52:59 q? 14:53:01 ack k 14:53:02 Bin: It will be useful to help Igarashi and others to know the implementation criteria at this stage, to know what they're committing to 14:53:05 Igarashi: I agree 14:53:17 q+ tidoust 14:53:20 ack t 14:53:55 q+ 14:53:55 Francois: I'm not really asking for commitment, only that it's something you want to push for 14:54:33 Kaz: I think Hyojin was also asking about the coverage of the implementation 14:55:00 ... One implementation doesn't have to include all the features 14:55:36 ... The features could be implemented across two or three implementations 14:56:07 i/Hyoujin/[ kaz whispers that maybe we say "expectation" at the moment. ]/ 14:56:15 Bin: I'll draft something based on what we've just discussed 14:56:31 Topic: Test contributions 14:56:49 q? 14:56:51 ack k 14:56:58 Bin: I assume anyone doing implementation will also cover testing 14:57:08 q+ 14:58:02 ... But if anyone else wants to contributes, please get in touch 14:58:29 ack k 14:58:35 Kaz: We should think about using and contributing to the general W3C web platform testing effort 14:59:01 Bin: We'll need a specific test platform suitable for TVs 14:59:23 ... We can also discuss testing offline 14:59:53 igarashi has joined #tvapi 15:00:09 ... I encourage everyone to look at the proposed phase 2 work and discuss offline 15:00:52 Bin: Thank you all 15:00:57 [ adjourned ] 15:01:06 seanlin has left #tvapi 15:02:04 Thanks Bin Hu for your kind explanation :) 15:02:33 rrsagent, draft minutes 15:02:33 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html cpn 15:03:04 Chair: Bin Hu 15:03:27 Ah, I got it. 15:03:45 Meeting: TV Control API CG 15:03:49 rrsagent, draft minutes 15:03:49 I have made the request to generate http://www.w3.org/2016/01/12-tvapi-minutes.html cpn 17:18:45 Zakim has left #tvapi