13:03:11 RRSAgent has joined #webtv 13:03:11 logging to http://www.w3.org/2016/07/06-webtv-irc 13:03:21 present: Kaz, Alexandra, Nilo, Steve 13:04:14 colin has joined #webtv 13:05:01 Nilo has joined #webtv 13:05:41 present+ Colin 13:06:58 zakim, pick a scribe 13:06:58 Not knowing who is chairing or who scribed recently, I propose Nilo 13:07:04 zakim, pick a scribe 13:07:04 Not knowing who is chairing or who scribed recently, I propose Steve 13:07:23 zakim, pick a scribe 13:07:23 Not knowing who is chairing or who scribed recently, I propose Colin 13:07:47 zakim, pick myself :) 13:07:47 I'm glad that smiley is there, kaz 13:07:56 scribenick: kaz 13:08:43 alex: great that ActiveVideo has joined W3C :) 13:09:42 Agenda: https://lists.w3.org/Archives/Member/member-web-and-tv/2016Jun/0001.html 13:10:02 alex: Colin made great job for the draft document 13:10:14 ... will share the screen 13:11:25 colin: created a separate page 13:11:57 ... will go to the page and introduce it 13:12:43 -> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Introduction_cloud_browser Colin's write-up 13:14:17 colin: short introduction about what "Cloud Browser" is like 13:14:52 ... the first diagram shows a "Local browser" 13:15:05 ... and the second one shows a "Cloud browser" 13:15:34 s/second/second one and the following ones/ 13:17:14 ... "orchestration" responsible for communication between the client and cloud browser, etc. 13:17:23 nilo: need to define "orchestration" 13:17:49 colin: ok, we should update the main architecture document with the definition 13:18:55 ... "rte" (Runtime Environment) 13:19:02 ... Each client need to implement a small part which should be standardized to be vendor interchangeable 13:19:24 ... identifying the gaps with the existing standards 13:20:03 ... important to identify who uses resources 13:20:41 ... For example, in the case of EME, this could be a problem because the media is send in the clear from the orchestration to the rte. 13:20:49 q? 13:20:52 q+ 13:21:08 nilo: very nice 13:21:43 ... maybe you might want to expand the sentence saying "This is not the only task" 13:21:48 colin: right 13:21:55 ... still generating the text 13:22:03 ... and would like to improve it 13:22:16 ... also want to edit the last block 13:22:27 alex: tx, Colin! 13:22:30 ... 2 comments 13:22:45 ... wanted to ask about the display example 13:22:58 ... do you also address display as a client? 13:23:09 colin: have to add communication use case 13:23:41 alex: another one is 13:23:46 ... a bit confused 13:24:05 ... we wanted to establish standard APIs 13:24:36 ... address browser vendors are expected to implement the API 13:25:09 ... who has implementation? 13:25:22 ... implemented by the browser itself 13:25:27 ... or by the environment 13:25:43 ... we should clarify that 13:25:47 colin: good question 13:26:17 ... cloud browser without any change can use the API 13:26:50 ... compatible API or vendor specific one 13:27:17 ... sometimes communication between orchestration and environment 13:27:46 alex: three logical groups 13:28:26 ... rte, gaps towards JS api, and implementation by Google/Microsof, etc. 13:28:45 ... we have risk people won't implement our APis 13:29:11 ... possibly implemented by Google/Mozilla 13:29:36 colin: cloud browser api? 13:29:57 alex: maybe there are something executed by the browser itself 13:30:08 colin: rte is something simple here 13:30:38 ... cloud browser could be different from Android OS 13:31:39 alex: is the JS logic part of browser? 13:31:45 ... or rte? 13:32:11 colin: API should be part of the cloud browser 13:32:23 ... but should not be a specific cloud browser api 13:32:58 alex: MSE, EME or TV Control API, etc. 13:33:42 nilo: most compelling part is that application shouldn't change 13:34:38 ... don't have to care about whether local or not 13:35:42 colin: we're able to do that 13:36:17 alex: requirements for cloud browser 13:36:36 s/requirements/maybe could put as requirements/ 13:37:10 colin: maybe we could have use cases which don't depend on the mechanism (local or not) 13:37:16 alex: ok 13:37:30 ... and you could expand the text as well 13:38:08 ... we'll work with existing groups to see gaps 13:38:29 nilo: clarification question 13:39:14 colin: hoped to explain much more in the architecture section 13:39:25 ... but started this separate article 13:39:37 q? 13:39:44 q? 13:41:35 kaz: @@@ 13:41:46 ... what is done on which side 13:42:00 ... and data transfer, etc., should be clarified 13:42:04 colin: good question 13:42:22 ... orchestration deals with abstraction 13:42:37 ... tuner api also is abstracted by orchestration 13:43:01 ... we could implement tuner api 13:43:10 ... and cloud browser could use that 13:43:28 ... but how orchestration would do is fairly complicated 13:44:56 kaz: "orchestration" sounds similar to UI integration, i.e., multimodal interaction 13:45:05 colin: would see that spec as well 13:45:38 -> https://www.w3.org/2013/10/mmi-charter.html multimodal interaction charter 13:46:20 kaz: maybe state transition capability would be useful for cloud browser too 13:46:24 colin: should look at that 13:46:48 q? 13:46:56 ack k 13:47:06 alex: tx a lot, Colin 13:47:22 ... would be great if you could add a link from the main architecture page to this introduction wiki 13:47:24 colin: ok 13:47:47 alex: shaping the scope is great 13:48:23 ... if we're ok with this, have another question on the architecture doc 13:50:00 topic: Main Architecture wiki 13:50:22 -> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture main architecture wiki 13:50:26 alex: we have 4 models 13:51:02 ... we have "primary approaches" and "secondary approaches" 13:51:21 ... and have "Cloud Browser Lifecycle" 13:51:57 ... and "Terminology" 13:52:09 ... and then "Evolution of the TV UI" 13:52:24 ... and "Architecture" section after that 13:53:12 ... sometimes to use cloud browsers 13:53:27 ... in that case we use local browser 13:54:28 ... diagrams of main/primary approaches and secondary approaches 13:54:37 ... "Functions" section 13:54:48 ... comments welcome 13:54:59 ... good description we would address 13:55:07 colin: much more clear now 13:55:12 ... good improvement 13:55:31 alex: tx! 13:56:47 ... the TF Charter wiki says the deadline is 23 Sep. 13:58:00 kaz: we can extend the TF period :) 13:58:14 ... we can send an announcement/proposal to the IG list 13:58:20 alex: ok 13:58:55 kaz: we can publish this architecture wiki after converting to HTML 13:59:09 alex: review for a few weeks 14:00:33 ... we need to handle the session use cases as well 14:00:47 -> https://lists.w3.org/Archives/Public/public-web-and-tv/2016Jul/0001.html session use case discussion 14:01:20 alex: what is your view on session handling 14:01:24 s/handling/handling?/ 14:01:41 ... who would handle/establish sessions? 14:01:54 colin: could be both 14:02:09 ... orchestration also called as session manager 14:02:48 alex: is it valid to use session id? 14:02:57 colin: yes 14:03:36 alex: in some case, the application has complete capability to handle sesson 14:04:05 colin: has just read this message 14:04:16 ... client sets up the connection 14:04:50 alex: if we destroy the session, every entity in the framework could destroy it? 14:05:05 ... or only the guy who created can destroy? 14:05:12 colin: both should be possible 14:06:12 kaz: in that case the guy (who didn't create the session but would destroy the session) need to get the session id and permission to destroy the session 14:07:07 alex: before writing the concrete use cases, would be good to have description on every entity within the architecture 14:07:22 ... who could destroy whom 14:07:38 ... if you have any opinions, please respond to the email 14:07:45 q? 14:07:58 colin: question regarding TPAC 14:08:05 ... never joined TPAC sessions 14:08:14 ... most of us are going to TPAC? 14:08:17 alex: yes 14:08:48 ... as a part of the main Web&TV IG, we'll get a session during the f2f 14:09:04 ... TF update, etc. 14:09:13 ... have already contacted the Chairs 14:09:33 what are the dates of the TPAC? 14:09:42 ... would have a specific session for cloud browser discussion 14:10:22 kaz: TPAC will be held Sep. 19-23 14:11:37 alex: can extend the meeting schedule? 14:11:42 kaz: need to pay more 14:11:54 ... but we can use Wednesday for additional discussion 14:12:06 ... using the breakout meeting 14:12:33 kaz: will remind the IG co-Chairs of the TPAC schedule 14:12:39 alex: ok 14:12:48 ... please review the architecture wiki 14:13:00 ... also look at the use case document as well 14:13:10 ... the next meeting will be held in 2 weeks 14:13:17 ok, bye 14:13:40 [ adjourned ] 14:15:16 rrsagent, make log public 14:15:22 rrsagent, draft minutes 14:15:22 I have made the request to generate http://www.w3.org/2016/07/06-webtv-minutes.html kaz 14:18:03 Meeting: Web and TV IG - Cloud Browser TF 14:18:10 Chair: Alexandra 14:18:33 i/great that/topic: Architecture introduction/ 14:18:36 rrsagent, draft minutes 14:18:36 I have made the request to generate http://www.w3.org/2016/07/06-webtv-minutes.html kaz 14:19:46 s/@@@/TV Control API could be used on the Cloud Browser side/ 14:20:07 s/what is done on which side/need to clarify what is done on which side/ 14:20:25 rrsagent, draft minutes 14:20:25 I have made the request to generate http://www.w3.org/2016/07/06-webtv-minutes.html kaz