14:02:32 RRSAgent has joined #tvapi 14:02:32 logging to http://www.w3.org/2015/11/10-tvapi-irc 14:02:48 Kaz, do you know how to solve WebEx issue? 14:02:55 oh 14:03:12 please click: https://mit.webex.com/mit/j.php?MTID=m1f2b8ef22eb495cf5f3c41be56c425de 14:03:33 I could join the call using the link 14:03:52 though I couldn't join the call using the meeting no. and password 14:06:03 present: Kaz_Ashimura, Tatsuya_Igarashi, Bin_Hu, Chris_Needham, Paul_Higgs, Sean_Lin, SungHei_Kim 14:06:29 https://www.w3.org/community/tvapi/wiki/Main_Page/Agenda_Telco_Nov_10_2015 14:06:49 Agenda: https://www.w3.org/community/tvapi/wiki/Main_Page/Agenda_Telco_Nov_10_2015 14:07:17 scribe: Kaz 14:07:29 scribenick: kaz 14:08:08 Paul_Higgs has joined #tvapi 14:08:09 topic: action items 14:08:19 -> http://www.w3.org/community/tvapi/track/actions/open actions 14:08:20 nigel_ has joined #tvapi 14:08:24 action-41? 14:08:24 action-41 -- Sean Lin to Verify the cas-related changes proposed. -- due 2015-10-06 -- OPEN 14:08:24 http://www.w3.org/community/tvapi/track/actions/41 14:08:34 bin: already done 14:08:41 close action-41 14:08:41 Closed action-41. 14:08:45 nigel_ has joined #tvapi 14:08:52 action-42? 14:08:52 action-42 -- Sean Lin to Review the emails around program.data.detail and implement/remove requirement. -- due 2015-10-06 -- OPEN 14:08:52 http://www.w3.org/community/tvapi/track/actions/42 14:08:56 close action-42 14:08:56 Closed action-42. 14:09:18 topic: publish TV Control API v1.0 14:09:32 bin: sent out the review request 14:09:45 ... Sean has revised the spec based on the comments 14:09:58 ... also we got a liaison statement from ATSC 14:10:12 ... they're evaluating the spec 14:10:33 ... one of the questions was the plan for the spec 14:11:13 ... would proposed we go ahead and publish the spec by the end of November 14:11:52 ... the quality of the spec is not perfect but could be implementable 14:12:23 ... next step would be bringing it to the WG status to make it a W3C Rec 14:12:48 paul: we started the CG to create the draft 14:13:03 ... would this CG continue the work after the publication? 14:13:12 ... what would be the procedure? 14:13:15 bin: good question 14:13:33 ... there is the Web&TV IG which work on use cases and requirements 14:13:51 ... 2 years ago we collected use cases within the IG 14:14:04 ... and then we created this CG to generate a spec 14:14:19 ... that's the background 14:15:12 ... the IG and the CG are separate from the process viewpoint 14:15:20 ... there are two possibilities 14:15:32 ... 1. we continue to work as a CG 14:15:48 ... we had a collection of technical use cases and requirements 14:16:02 ... we can continue this model within the CG 14:16:16 ... basically no big changes 14:16:55 ... another possibility given the broader interest from, e.g., ATSC 14:17:21 ... is creating a WG to generate a formal W3C Rec 14:17:26 s/another/2. another/ 14:17:48 ... Working Group is a formal group of W3C which generates W3C Recommendations 14:18:14 ... starting with WD followed by LC/CR, PR and Rec 14:18:27 ... need to develop test cases as well 14:18:46 ... define test success criteria 14:19:04 ... check successfully passed all the tests 14:19:22 ... we have done a great job and generated a spec draft 14:19:42 ... the possible WG would help us improve the spec draft 14:20:16 ... W3C specs require stricter procedures 14:20:38 ... W3C Team Staff (Yosuke, Francois and Kaz) are involved 14:20:46 ... Francois has generated a draft charter document 14:20:57 http://w3c.github.io/charter-drafts/tvcontrol-2015.html 14:21:12 bin: email discussion with Francois yesterday 14:21:31 ... would suggest we review the draft charter 14:22:15 ... scope, further work, etc. 14:22:42 ... after that the charter will be reviewed by all the AC Reps 14:23:19 ... considering the timing as well 14:23:44 ... WG need, e.g., 2 years, to make the spec a W3C Rec. 14:23:51 ... HTML5 needed 7 years 14:24:18 ... the official AC Review may end up with a formal objection 14:24:40 ... a very early draft of the proposed WG Charter is generated by Francois 14:25:00 ... would review until the next call on Dec. 8 14:25:16 ... and at the Dec. 8 call, would make a consensus 14:26:18 ... and in January we'd ask the AC for review 14:26:50 ... the AC might be going to support our proposal, but maybe not 14:27:38 igarashi: some comment 14:27:52 ... Sony has joined this CG recently because of the ATSC standardization 14:28:06 ... during the f2f meeting in Sapporo, we discussed ATSC liaison as well 14:28:32 ... can't say beyond the liaison, but Sony would like to create a WG and work with you 14:28:37 bin: tx! 14:28:51 ... glad to hear you would support the WG and contribute to it 14:29:00 ... helpful to everybody here 14:29:15 ... great news 14:29:23 ... what do you think, Chris? 14:29:37 cpn: their contribution is very welcome 14:29:48 bin: what do you think about the plan? 14:29:52 cpn: the plan sounds good 14:29:59 ... with the support from Sony 14:30:18 ... a question about the spec in the current shape 14:30:29 ... which should be the final spec of the CG 14:30:43 ... and what should be taken over by the WG? 14:31:14 bin: security/privacy, hardware issues may take another 6 months 14:31:15 q+ 14:31:33 ... need coordination with the other groups 14:31:58 ... we should discuss that 14:32:25 cpn: agree 14:32:35 ... possibly new spec for the CG 14:32:46 ... existing spec for WG 14:32:50 bin: right 14:33:01 ... need to have something closed 14:33:42 ... having the current spec closed and let people give us feedback 14:34:06 ... would help us 14:34:14 ... and minimize the issues 14:34:30 nigel has joined #tvapi 14:34:42 igarashi: security and privacy is a new issue 14:34:53 ... CG could continue to address that 14:35:15 ... but we should keep the momentum 14:35:49 ... the core spec should be brought to the REC stage asap 14:35:59 ... we need implementations 14:36:05 q? 14:36:26 ... and we could handle security&privacy in parallel 14:38:32 kaz: explains the situation of the Automotive BG/WG 14:38:39 bin: tx! 14:38:57 ... core group focus on the REC trac work 14:39:26 ... and the sec&priv TF focus on the security&privacy portion 14:39:35 ... similar to the Automotive groups and HTML5/5.1 14:39:48 cpn: will we continue email discussions? 14:40:06 bin: first review the Charter till Dec. 8 14:40:36 ... clarify why we need to work in this WG setting 14:41:12 ... would create an entry to the wiki 14:41:38 ... so that people can raise issues and use case/requirements 14:41:57 ... we can start the work immediately 14:42:12 cpn: yeah 14:42:18 ... so your suggestion is creating a wiki 14:42:26 ... and I can add descriptions 14:42:38 bin: yes, I'll create a wiki 14:42:49 ... also would work with Francois, Kaz, etc. 14:43:02 ... and all the participants, please give your feedback 14:43:37 ... and we'd have more stable and improved Charter document by Dec. 8 14:43:49 paul: we need implementations 14:44:03 ... not sure what that really means 14:44:16 ... in Chrome, IE, Safari, etc.? 14:44:33 ... if somebody implemented the feature within Blink 14:44:40 ... would that suffice? 14:44:50 bin: implementation means user agents 14:45:16 ... and generally available 14:45:44 ... another possibility is non-shipping products 14:46:12 ... to check conformance we need test specs 14:46:36 igarashi has joined #tvapi 14:46:45 ... implementations must be stable but not have to be a formal product 14:46:52 q+ 14:48:51 kaz: explains the implementation mechanism 14:49:06 paul: ok 14:50:05 igarashi: tv control api itself is independent 14:50:22 kaz: right 14:50:40 igarashi: another question is if a prototype implementation ok? 14:51:12 bin: could be a preview release or non-shipping product 14:52:33 igarashi: tv control api strongly depends on hardware 14:52:46 ... so we need prototype implementations 14:52:52 bin: yes 14:53:04 ... that should be considered 14:53:20 ... but the detail of the criteria is not defined by the W3C Process 14:53:32 ... so we need to check with the W3C Team 14:54:02 kaz: yes, that is the case with the Automotive group as well 14:54:12 ack k 14:54:34 bin: for CR, we need to define the exit criteria 14:54:51 kaz: right 14:55:51 ... and would confirm that everybody here is interested in creating a WG :) 14:55:58 bin: yes, that's my understanding 14:56:14 ... we'll discuss the draft charter on Dec. 8 14:56:27 ... after this call, I'll create a wiki page to gather opinions 14:57:03 cpn: just one comment 14:57:12 ... raised during the IG 14:57:14 ... the ML is very quiet 14:57:44 ... somebody should respond to the comments 14:57:53 bin: good suggestions 14:58:01 s/suggestions/suggestion/ 14:58:12 ... e.g., the one from Sangwhan 14:58:22 ... let me respond to him 14:59:12 ... think all the comments should be handled by the next version 14:59:20 ... tx for reminding me of that 15:00:01 nigel has joined #tvapi 15:00:03 skim13 has left #tvapi 15:00:09 seanlin has left #tvapi 15:03:23 [ adjourned ] 15:03:31 rrsagent, draft minutes 15:03:31 I have made the request to generate http://www.w3.org/2015/11/10-tvapi-minutes.html kaz 15:04:03 rrsagent, make log public 15:04:04 rrsagent, draft minutes 15:04:04 I have made the request to generate http://www.w3.org/2015/11/10-tvapi-minutes.html kaz 15:05:35 nigel_ has joined #tvapi 16:04:02 nigel has joined #tvapi 16:10:22 nigel has joined #tvapi 17:15:14 nigel_ has joined #tvapi 17:22:58 Zakim has left #tvapi