14:02:53 RRSAgent has joined #webtv 14:02:53 logging to http://www.w3.org/2017/09/07-webtv-irc 14:03:35 Agenda: https://lists.w3.org/Archives/Member/member-web-and-tv/2017Aug/0003.html 14:03:45 Meeting: Media&Entertainment IG 14:04:30 MarkVickers has joined #webtv 14:06:02 hyojin has joined #webtv 14:07:30 kazho has joined #webtv 14:08:20 present+ Kaz_Ashimura, Mark_Vickers, Bob_Lund, Chris_Needham, Chris_O'Breien, Colin_Meerveld, Francois_Daourst, Giri_Mandiam, Glenn_Goldstein, Hyojin_Song, Tatsuya_Igarashi, John_Luther, Kazuhiro_Hoya 14:08:38 present+ Peter_Pogrzeba 14:09:07 BobLund has joined #webtv 14:09:08 MarkVickers has joined #webtv 14:09:16 igarashi_ has joined #webtv 14:09:21 Chris_AMI has joined #webtv 14:10:02 mv: welcome 14:10:04 igarashi__ has joined #webtv 14:10:06 ... showing the charter 14:10:16 ... we hold monthly calls 14:10:22 ... and possible some more TF calls 14:10:50 ... basic idea is summary of various W3C groups 14:10:54 ... and invited guests 14:11:03 ... introducing the whole things 14:11:08 ... also deep dive as well 14:11:16 ... shows agenda: 14:11:17 https://lists.w3.org/Archives/Member/member-web-and-tv/2017Aug/0003.html 14:11:45 mv: quick introduction, TPAC agenda, summary of work 14:12:13 -> https://www.w3.org/2017/03/webtv-charter.html Media and Entertainment IG Charter 14:12:28 mv: 3 Charters and 2 W3C contacts 14:12:42 ... Tatsuya Igarashi (Sony), Chris Needham (BBC), Mark Vickers (Comcast) 14:12:56 ... started as one of the original Chairs in 2011 14:13:05 ... let me introduce the other co-Chairs 14:13:09 ... Chris and Igarashi 14:13:23 cn: r&d devision of BBC 14:13:40 ... research and development related to web technology 14:13:55 ... various people in the organization for different wg/activities 14:14:28 ... standardization work and application development 14:14:38 ... my focus is web technology and web standards 14:14:42 mv: tx 14:14:45 ... Igarashi-san? 14:14:55 ti: work for Sony 14:15:04 ... TV equipment 14:15:08 ... also have services 14:15:16 ... OTT services 14:15:26 ... Sony music, etc. 14:15:32 ... main role is standardization 14:15:45 ... also work on smart home 14:15:54 ... IPTV and broadcast 14:16:03 ... media and entertainment aspect within W3C 14:16:24 present+ Alex_Deacon 14:16:37 mv: the Chairs represent, US, UK and Asia 14:16:45 ... media is regional 14:16:51 ... and regional standards 14:17:01 ... but becoming more and more global 14:17:16 ... so need for contact persons for regional industry 14:17:25 ... also would introduce team contacts 14:17:39 alex_deacon has joined #webtv 14:17:59 ... Kaz Ashimura 14:18:07 kaz: working on TV since 2011 14:18:10 ... WoT as well 14:18:26 mv: also would introduce Francois Daourst 14:18:40 fd: M&E champion 14:18:53 ... media-related groups 14:18:58 ... including the M&E IG 14:19:09 ... extract priorities from W3C Membership 14:19:25 ... not really the Staff Contact but will be around and contribute to the discussion 14:19:34 mv: one of the issue is 14:19:48 ... formerly we were "Web&TV IG" 14:19:57 ... now we're "Media&Entertainment IG" 14:20:04 https://www.w3.org/2017/03/webtv-charter.html Charter 14:20:16 mv: the focus is media on the Web 14:20:22 ... not necessarily TV 14:20:27 ... so broaden the scope 14:20:35 ... as you see here in the Charter 14:20:56 ... (shows the section "1. Scope") 14:21:07 ... video, audio, radio, streaming media 14:21:15 ... any questions about the new name/charter? 14:21:26 ... still same mission and somewhat broaden 14:21:40 cn: regarding the scope 14:22:00 ... the scope includes entire production chain 14:22:08 ... not just distribution, etc. 14:22:20 ... there is a need we should discuss the entire production system 14:22:26 ... we used to have the GGIE TF 14:22:36 ... bringing use cases slightly broader 14:22:44 ... would reflect that as well 14:22:54 mv: that's good/key point of the name change 14:23:17 ... capture with camera, distribution and consumption on screen 14:23:25 ... that's also key part of the new name 14:23:42 ... any otherb 14:23:52 s/otherb/other business to be added to the agenda?/ 14:24:05 (none) 14:24:10 topic: TPAC agenda 14:24:17 mv: anybody can attend 14:24:27 https://www.w3.org/2017/11/TPAC/ TPAC page 14:24:39 mv: if you've not got registered... 14:24:54 ... it's Burlingame closed to San Fransisco 14:24:58 ... 6-10 Nov. 14:25:11 ... we'll meet on Monday 14:25:20 ... TPAC goes through Mon to Fri 14:25:36 https://www.w3.org/2017/11/TPAC/schedule.html TPAC schedule 14:25:54 mv: last year, what we had was... 14:26:03 ... (shows the agenda for the TPAC in Lisbon) 14:26:12 kazho has joined #webtv 14:26:15 ... HTML Media Extensions WG - EME/MSE 14:26:25 igarashi has joined #webtv 14:26:40 present+ Tatsuya.Igarashi 14:26:40 ... joint meetings with Timed Text WG, TV Control WG 14:26:54 ... and Cloud Browser TF meeting 14:27:02 ... so 14:27:09 ... joint meetings with certain groups 14:27:14 ... TF report 14:27:22 ... Cloud Browser TF 14:27:46 present+ Guen-Hyung_Kim 14:27:54 mv: anybody from the TF? 14:28:00 cm: I'm here 14:28:29 present+ Kasar_Masood 14:29:24 mv: joint meetings with Timed Text and Second Screen 14:29:35 ... and work around the world 14:30:10 ... HbbTV from Europe, ATSC from US, Next@@@ from Korea and Hybridcast from Japan 14:30:20 ... also Web Media API CG 14:30:54 ... coordinating technical standardization groups 14:31:02 s/technical/with technical/ 14:31:11 ... other WGs/CGs should be included 14:31:23 gg: HTML streaming group? 14:31:38 ... streaming graphics much like Timed Text 14:31:45 ... potential for the future TV 14:31:48 mv: interesting 14:32:02 ... we may pick up that kind of related work 14:32:13 ... recent report? 14:32:22 gg: SVG group is kind dormant 14:32:39 [I'm not aware of on-going work on streaming graphics right now. The SVG streaming CG is indeed dormant, as far as I know] 14:32:43 mv: strong relationship with CGs/BGs 14:33:10 ... any possible joint meetings? 14:33:19 cn: TV Control discussion hosted by IG? 14:33:31 mv: ok 14:33:51 ... Web Media API CG is another possibility 14:34:02 ... joint meeting with the IG or sometime different 14:34:22 ... any feedback from working group, etc? 14:34:23 q+ 14:35:25 ack k 14:35:35 kaz: joint meeting with WoT would make sense @@@ 14:35:52 mv: smart device in home, TV, STB, etc. 14:36:09 ... many of them have streaming media, video/audio, capability 14:36:16 ... Amazon Alexa, etc. 14:36:22 ... 2-way audio streaming media 14:36:28 ... smart device as the huv 14:36:31 s/huv/hub/ 14:36:38 ... so huge overwrap 14:36:43 ... let's have a joint meeting 14:37:03 km: talked about participating W3C groups 14:37:11 ... liaison from W3C? 14:37:27 ... advertising standards 14:37:32 mv: a lot of work we done 14:37:43 ... EME/MSE work started withing the Web&TV IG 14:37:55 ... not sure any work on advertisement 14:38:05 fd: IAB is a W3C Member 14:38:23 ... active on tracking protection 14:38:35 km: there is IAB Lab as well 14:38:43 fd: nothing official or concrete so far 14:38:53 ... IG input is more than welcome 14:39:11 ... not sure if we can set up a meeting with them at TPAC 14:39:21 mv: let's talk about this offline 14:39:36 ... should we go through the related groups? 14:39:42 ... summary of current work 14:39:46 ... or TV Control? 14:40:00 cn: you can see the list in the agenda 14:40:07 https://lists.w3.org/Archives/Member/member-web-and-tv/2017Aug/0003.html 14:40:18 cn: this call as getting update 14:40:48 ... if you look at the Web Incubator CG 14:40:54 ... there are a number of specs 14:41:10 ... would talk about the TV Control topic today 14:41:19 ... we can revisit other groups for the next call 14:41:35 mv: good idea 14:41:58 ... will you share your screen on webex? 14:42:02 https://www.w3.org/2016/03/tvcontrol.html 14:42:03 cn: will put resources here on IRC 14:42:20 mv: can open the links via IRC 14:42:37 cn: TV Control WG charter 14:42:49 ... need for APIs 14:42:53 ... gaps are identified 14:43:18 ... to handle video/audio stream 14:43:28 ... originally the CG had discussion 14:43:41 ... Mozilla's work became the basis 14:44:14 ... in 2016, started work for standards 14:44:23 ... (shows the scope) 14:44:33 https://www.w3.org/2016/03/tvcontrol.html#scope 14:44:49 cn: conditional access as well 14:45:03 ... broad enough to cover various environment 14:45:34 ... closer integration of broadcasting and HTML5 environment 14:45:44 ... how we could provide audio/video stream 14:45:53 ... in the browser in order to display the media 14:46:01 ... and select different channels 14:46:16 ... resource constraint 14:46:23 ... limited number of pipelines 14:46:32 ... how can we allow applications to present media 14:47:05 ... and allow some element to allow automatic decoding on devices with limited capability 14:47:35 ... initial conversation about possible integration in ATSC 3 14:48:57 ... the feedback we gate later is the APIs require extra efforts 14:49:24 ... at the end of the h 14:49:36 s/the h/the charter period/ 14:49:45 ... the conclusion was not continuing the work in the WG 14:49:56 ... but having some more discussion in this IG 14:50:27 ... there are number of APIs that exist for the purposes 14:50:44 ... do we still want W3C to standardize the API? 14:51:20 ... TAG's suggested approach more TV as a device controlled on network 14:51:30 ... applications on TVs 14:51:57 ... selecting content vs streams bound to broadcast 14:52:40 ... should those applications be allowed? 14:52:57 ... is this something we still feel useful to do at W3C? 14:53:17 ... different APIs for different devices by different vendors? 14:53:25 s/different APIs/OK with different APIs/ 14:54:09 ... should be tightly coupled with use cases? 14:54:33 ... would like to hear your views/questions 14:54:43 mv: a couple of comments 14:55:00 ... 1. TAG talking about device for home network? 14:55:17 ... involved in discussion at ATSC 14:55:21 ... tuners on network 14:55:33 ... they would use web-based device 14:55:46 gm: that's correct 14:56:07 mv: we could have discussion during TPAC 14:56:31 ... on the other hand, their is a naming problem 14:56:57 ... how broadcast channels/TV channels would fit with the Web media 14:58:04 ... different channel systems depending on regions 14:58:34 ... maybe URL, etc., as universal resource 14:58:39 q? 14:59:06 gm: ATSC's response on TV Control API 14:59:17 ... some attempt for TV-triggered application 14:59:44 ... API work may be rigid 15:00:25 ... consistency with the existing DRM systems 15:01:04 ti: had been working on the TV Control WG 15:01:15 ... one of the challenges was timeline 15:01:42 ... misalignment between the broadcasters' expectation and the WG process 15:01:49 ... so failed 15:02:28 ... dedicated TV, radio, car audio, etc. 15:02:45 ... those kind of devices that have embedded tuner capability 15:03:17 ... should generate W3C standard to be used by broadcasters 15:03:59 kaz: do you mean we need to involve more stakeholders from those industries? 15:04:02 ti: yes 15:04:38 gm: agree regarding car environment 15:05:10 ti: the main purpose of the TV Control API is handling embedded tuners 15:06:05 cn: we have interest in multicast delivery, etc., as well 15:06:10 ... live media streaming 15:06:33 ... for the possible future direction 15:06:55 ... TV Control API provides high-level abstraction 15:07:02 ti: ok 15:07:47 ... "tuner" here could be any kind of "device with tuning capability" 15:08:24 cn: btw, alignment of timeline is an interesting point 15:08:46 ... how early should we attempt to bring the discussion to W3C? 15:09:20 ... work within ATSC and HbbTV, for example 15:09:30 mv: we have 2 missions 15:09:36 ... within this IG 15:09:42 ... facing out and facing in 15:10:00 ... active liaison with related groups which increase the activity 15:10:41 ... understand their standards are and communicate with them 15:11:16 ... and looking-in is looking at related W3C standards 15:11:54 ... have been working with ATSC, etc. 15:12:37 gm: TV Control API was targeted to wrong direction from the market's requirements 15:13:24 ... more or less solved by the market place 15:14:04 mv: would have ATSC more inline with the HTML5 standard 15:14:21 ti: ok to continue the discussion on TV Control API in this IG 15:14:30 ... we need to narrow down the scope 15:14:35 ... what the target area is 15:14:57 ... remember there was discussion on TV Control API during TPAC 2016 15:15:56 ... by whome applications are provided? 15:16:11 ... we should think about those provided by Web developers 15:16:46 ... btw, what kind of use cases we have discussed, e.g., during TPAC 2016? 15:16:55 ... categorization of the use cases 15:18:19 ti: the APIs should be used by Web applications 15:18:38 cn: which Web apps are allowed to contact the device? 15:18:59 ... relationship between the Web domain and the broadcast signal 15:20:01 s/signal/channels/ 15:20:05 ... possible next step 15:20:16 ... current state of TV industry standards 15:21:45 ... any more points for today? 15:21:48 (none) 15:21:58 topic: EME vote 15:22:20 mv: vote available until next week (Sep. 14) 15:22:42 ... we'll meet in month for the next call? 15:22:55 cn: got comments from some of the Timed Text WG participants 15:23:03 ... overlap with their call 15:23:37 kaz: should we try another doodle? 15:24:03 mv: maybe two (or small number of) choices, this slot vs Monday 15:24:22 [ adjourned ] 15:24:28 rrsagent, make log public 15:25:23 rrsagent, draft minutes 15:25:23 I have made the request to generate http://www.w3.org/2017/09/07-webtv-minutes.html kaz 15:27:45 Chair: Mark, Chris, Igarashi 15:27:47 rrsagent, draft minutes 15:27:47 I have made the request to generate http://www.w3.org/2017/09/07-webtv-minutes.html kaz 16:49:59 cpn has joined #webtv 17:22:58 Karen_ has joined #webtv 17:29:58 Zakim has left #webtv 17:44:03 Karen has joined #webtv 17:49:05 Karen__ has joined #webtv 17:53:28 Karen_ has joined #webtv