14:00:39 RRSAgent has joined #webtv 14:00:39 logging to http://www.w3.org/2017/08/09-webtv-irc 14:00:53 Meeting: Media&Entertainment IG - Cloud Browser TF 14:01:52 alexandra has joined #webtv 14:02:00 hi 14:02:09 colin has joined #webtv 14:02:10 present+ Kaz, Alex, Chris, Colin 14:05:20 alex: several issues 14:05:24 ... and also TPAC planning 14:05:43 ... use case discussion by TPAC 14:05:55 all: ok 14:06:02 alex: we had some discussion on EME 14:06:03 cob has joined #webtv 14:06:25 ... action for Colin 14:06:41 colin: did some work 14:06:48 s/EME/MSE/ 14:07:15 ... similar mechanism with what we've been discussing 14:07:48 -> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/MSE MSE use cases 14:08:19 alex: would be good to have joint discussion with MSE guys 14:08:25 ... who would be the best person? 14:08:30 ... maybe Mark Watson? 14:09:14 kaz: before TPAC? 14:09:16 alex: yes 14:09:40 ... would finalize our points before TPAC 14:09:56 ... and we could have joint discussion during TPAC as well 14:10:34 colin: please not that we should not too much concentrate on MSE 14:10:55 s/MSE/MSE spec itself/ 14:11:20 alex: right. it's not our main document 14:12:34 colin: we should skip some of the use cases 14:13:02 alex: MSE use cases and communication use cases? 14:13:09 colin: yeah 14:13:52 alex: we put the use cases together 14:13:55 ... since 2015 14:14:19 colin: most use cases lack solutions 14:14:50 ... what we should focus is what kind of consequence we would have 14:15:14 ... manageable things 14:15:43 kaz: you mean requirements based on the use cases? 14:15:55 ... we should clarify requirements for specs 14:16:08 colin: what would be our next steps? 14:17:22 alex: impact of our work? 14:17:31 ... MSE/EME is one track 14:19:02 ... would put all our slots together 14:19:44 kaz: what do you mean by "next group"? 14:21:34 ... maybe "related groups"? 14:21:45 alex: possible "Cloud Browser WG" for example 14:22:03 colin: there are several possible options 14:23:53 kaz: explains the possible options@@@ 14:25:26 colin: my personal preference is not working on "Control", etc. 14:25:39 alex: would clarify core/impact use cases 14:26:47 kaz: impact use cases are important ones? 14:27:46 alex: basic interactions between cloud browser and its clent: blue lines are cloud browser use cases 14:28:13 ... green line : shift of the browser into the cloud (no local execution available) is impact useces 14:30:14 kaz: would suggest change the name 14:31:17 ... green one should be "cloud-only use cases" 14:31:35 ... and blue one should be "hybrid (cloud/client interaction) use cases" 14:33:27 ... in any case, we should clarify uc, req, gaps 14:33:39 ... also better to rename the use case categories 14:34:20 colin: not sure 14:34:48 kaz: we should add some more descriptions to those two categories: impact use cases and cloud browser use cases 14:34:59 ... and after that we could give them nicer names 14:35:25 colin: will you attend TPAC? 14:35:36 alex: planning to come 14:35:43 colin: arranging it 14:35:49 ... Mon/Tue 14:36:02 s|Mon/Tue|Mon-Thu| 14:36:09 chris: will be there 14:36:18 ... leaving Friday night 14:36:34 ... Sat-Fri 14:36:51 s/will you/btw, will you/ 14:37:11 alex: publication by TPAC? 14:37:46 ... would make control/state/session/communication more generic 14:37:59 ... less dependent on the cloud browser architecture 14:38:12 ... any updates? 14:38:16 colin: just the structure 14:38:23 ... no concrete changes with the content 14:38:54 alex: can you work on requirements for the use cases? 14:39:09 ... I myself also can work on MSE use cases 14:39:33 colin: can come up with some requirements 14:39:54 alex: ok 14:41:38 kaz: btw, do we want to continue to work with wiki? 14:41:44 ... or would start with using GitHub? 14:42:48 colin: wondering about that 14:42:57 kaz: we already have a repo for the Web&TV IG 14:43:13 ... but we can create a new repo for the Media&Entertainment IG 14:43:27 ... should be discussed during the whole IG call next week or the after 14:43:56 ... please respond to the doodle poll for the call 14:44:08 colin: how to transition to GH? 14:44:30 kaz: we can convert the content from wiki to HTML on GitHub anytime 14:44:38 colin: ok 14:44:46 alex: tx for working on this 14:45:41 kaz: btw, do we want to ask Chris to start reviews for accessibility? 14:45:55 ... accessibility use cases and also other use cases from accessibility viewpoint 14:46:02 ... and clarify the requirements 14:46:13 chris: what would be the starting point? 14:46:29 alex: there is a separate accessibility use case page @@@ 14:46:53 ... also there are other use cases to be reviewed by accessibility viewpoint 14:46:55 chris: ok 14:47:31 alex: you could update the accessibility use cases as well 14:48:31 ... we can do both Colin's work and Chris's work in parallel 14:49:32 kaz: for example, we can use the 1st part for Colin 14:49:39 ... and the 2nd part for Chris 14:49:41 all: ok 14:50:10 chris: sometimes difficult to understand specific features 14:50:21 ... so maybe would add some notes 14:50:29 ... and mention general requirements 14:50:33 s/mention/describe/ 14:50:42 alex: that's fine 14:50:58 ... good to start with general requirements 14:51:45 ... let's work on them by the next call in 2 weeks (=August 23rd) 14:52:04 [ adjourned ] 14:52:08 rrsagent, make log public 14:52:12 rrsagent, draft minutes 14:52:12 I have made the request to generate http://www.w3.org/2017/08/09-webtv-minutes.html kaz 16:07:27 Zakim has left #webtv 16:31:49 Karen has joined #webtv