13:07:06 RRSAgent has joined #webtv 13:07:06 logging to http://www.w3.org/2016/07/20-webtv-irc 13:11:33 open question for Alexandra is where our API actually resides 13:13:24 Should we follow the EME approach so that the application has a control over application 13:15:25 TF: we have to identify the missing specs on w3c to make an application run as on a normal browser 13:16:33 RTE could be also the Cloud Browser 13:19:02 colin... RTE could be a browser which impliments the CB API to talk to the Cloud Orchestration environemnt 13:20:40 https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases 13:20:53 We will go through State and Control UCs 13:30:15 Meeting: Web&TV IG - Cloud Browser TF 13:30:20 Chair: Alexandra 13:30:34 present: Alexandra, Colin, Julian, Kaz 13:31:19 rrsagent, make log publi 13:31:24 rrsagent, make log public 13:31:30 rrsagent, draft mintues 13:31:30 I'm logging. I don't understand 'draft mintues', kaz. Try /msg RRSAgent help 13:31:35 rrsagent, draft minutes 13:31:35 I have made the request to generate http://www.w3.org/2016/07/20-webtv-minutes.html kaz 13:31:55 scribenick: kaz 13:32:44 https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/state 13:32:59 am: looking at the "state" use case 13:33:24 -> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/state state use case 13:34:08 am: this is direct continuation of the control use case 13:34:37 ... two use cases 13:35:02 colin: brining events 13:35:12 am: in the first use case 13:35:19 ... application runs on the cloud side 13:35:32 ... and a lot of information on the client side as well 13:36:11 ... we'll support different information 13:36:18 ... resolution, color, etc. 13:36:28 s/color/color space/ 13:36:41 ... requested by orchestration 13:36:52 ... there must be a control channel 13:37:03 ... requested state must be available 13:37:15 ... must be made available by the orchestration 13:37:22 colin: important part of the use case 13:37:39 ... more details of the use case 13:37:54 s/colin:/cm:/g 13:38:18 am: we should clarify which is the basic functionality and which is additional one 13:38:44 ... US-State-2 13:39:06 ... Description: An event made it necessary to signal the Cloud Browser that the current state has changed 13:39:20 cm: if the client has sensory data 13:39:28 ... every 20ms, etc. 13:40:04 ... better approach would be cloud browser telling some particular event and the client send back another event 13:40:13 am: ok 13:40:22 ... there are lot of events 13:40:37 ... like key presses, remote control stops the video... 13:40:43 ... device plugged/unplugged 13:40:48 cm: yes 13:41:19 am: session of use cases 13:41:28 cm: good approach 13:42:02 am: one cloud browser and one RTE 13:42:54 cm: state and control 13:43:04 ... we could use reference to explain the use cases 13:43:20 am: control, state, session 13:43:30 ... synchronization of building apis 13:43:52 ... we're closing the session use cases 13:44:14 ... would talk with other groups 13:44:23 ... Web Crypto, TV Control, etc. 13:44:38 ... you've partially addressed your tuner use cases 13:45:01 ... high-level description on the gaps 13:45:15 cm: TV Control API especially tuner API 13:45:22 ... don't see any issues with that 13:45:40 am: the idea is that TV Control API also have listener? 13:45:50 ... very general work 13:45:56 ... which part could be reused? 13:46:09 ... better approach to copy the use cases 13:46:24 ... interesting for the Cloud Browser TF 13:46:59 cm: if the idea is general browser, e.g., in smart tv, it should work 13:47:28 am: good to mention the tuner API if it works within the cloud browser context 13:47:47 cm: we already have one use case necessary in that area 13:47:51 am: that's true 13:47:54 q? 13:48:03 ... it's more of a summary 13:48:28 ... what we're doing is how different from the other group's work 13:48:39 s/group's/groups'/ 13:48:42 cm: ok 13:49:04 q+ 13:49:22 am: next three weeks, you'll be not available? 13:49:29 cm: no, I'll be on holiday 13:49:48 am: planning for the TPAC meeting? 13:50:00 ka: will talk with the Web&TV IG Chairs again 13:50:49 ... there will be the Web&TV IG f2f meeting on Monday 13:51:04 ... the TV Control WG will be Tuesday 13:52:41 ... FYI, we might want to look at DOM Events 13:52:49 -> https://www.w3.org/TR/DOM-Level-3-Events/ DOM Events L3 13:53:10 cm: I'm quite familiar with this :) 13:54:39 s/quite/not/ 13:55:00 ka: TV remote key codes can be handled this event model 13:56:10 cm: also checked the MMI Architecture 13:56:23 ka: that is an abstract level event handling model 13:57:01 -> https://www.w3.org/TR/mmi-arch/ MMI Architecture 13:57:12 cm: how to handle back key, etc., is interesting 13:59:21 ka: MMI Architecture was invented to integrate various UI modalities originally 13:59:32 ... but could be used to integrate any kind of services 13:59:53 am: let's go through it (later) 14:00:20 ... have some trouble with email system 14:00:38 ... we'll have our next call in 2 weeks 14:00:43 [ adjourend ] 14:01:05 rrsagent, draft minutes 14:01:05 I have made the request to generate http://www.w3.org/2016/07/20-webtv-minutes.html kaz 16:30:22 Karen_ has joined #webtv