12:04:39 RRSAgent has joined #wot-uc 12:04:39 logging to https://www.w3.org/2021/09/07-wot-uc-irc 12:04:50 meeting: WoT Use Cases 12:04:53 chair: Lagally 12:05:13 present+ Kaz_Ashimura, Michael_Lagally, Michael_McCool, Tetsushi_Matsuda 12:05:31 matsuda has joined #wot-uc 12:06:34 Agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#Agenda_7.9. 12:07:42 scribenick: kaz 12:07:48 present+ Tomoaki_Mizushima 12:07:58 topic: Minutes 12:08:03 -> https://www.w3.org/2021/08/03-wot-uc-minutes.html Aug-3 12:08:12 ml: (goes through the minutes) 12:10:41 ... will follow up Conexxus 12:11:50 mm: btw, there was some information on industry cases of WoT during the Marketing call 12:13:53 ml: minutes approved 12:14:05 -> https://www.w3.org/2021/08/31-wot-uc-minutes.html Aug-31 12:14:11 mm: (gives summary) 12:14:51 ml: this use case itself is quite simple on smart homes 12:15:21 q+ 12:15:40 sebastian has joined #wot-uc 12:16:38 kaz: right 12:16:52 ... we should handle geofencing, etc., separately from this use case 12:17:08 ... and can generate another separate use case about that as a horizontal use case 12:17:23 ml: ok 12:17:37 ... btw, what's the status on the liaison with OGC? 12:17:46 mm: talking with Christine 12:18:04 ... it seems there is an IEEE WG on geospatial data as well 12:18:16 ack k 12:18:18 q+ 12:18:40 kaz: we should have a joint session with them during TPAC 12:18:53 mm: yeah 12:19:06 ... another question is how to manage the geolocation data 12:19:19 ... along with time-series data 12:20:06 kaz: we can start with some basic discussion based on use cases 12:20:09 mm: yeah 12:20:57 ml: for concrete extensions, we should be careful about our Charter 12:21:05 ... current Charter or the next one 12:21:29 ... e.g., clustering things 12:21:42 mm: thinking about orchestration 12:22:17 ... are we just concern about grouping the status? 12:22:25 ... or what do we want to achieve? 12:22:33 q? 12:22:35 ack k 12:22:37 q+ 12:23:19 ml: seems various topics there 12:23:59 ... including permission management 12:24:10 mm: we have things like OAuth now 12:24:24 ... but no standard to manage orchestration 12:24:54 ... e.g., a visitor visiting my home would like to get connected with the network at my home 12:25:01 q? 12:25:16 present+ Sebastian_Kaebisch 12:26:15 kaz: let's approve the minutes first :) 12:26:29 mm: yes, the minutes are fine :) 12:27:04 ... regarding the next steps, we have several advanced use cases in the pipe 12:27:26 ml: so we added "gaps" to the use case template to clarify the gaps 12:28:25 ... what was the conclusion about ECHONET use case description itself? 12:28:39 sorry I have to go 12:28:40 kaz: was quickly skimming it again today with Michael Lagally ;) 12:29:30 q+ 12:29:34 ml: ok. the minutes themselves are approved 12:29:36 ack k 12:29:51 topic: ECHONET use cases 12:29:54 s/cases/case/ 12:30:28 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/wot-usecase-echonet.md ECHONET use case 12:30:58 (discussion on the "Gaps" section specifically) 12:31:17 [[ 12:31:18 controlling multiple devices in an orchestrated manner is dependent on the implementation of a client application in the current WoT specification 12:31:18 ]] 12:32:08 mm: so there is a gap for multi-vendor orchestration 12:32:22 ml: what level of orchestration is expected? 12:32:46 ... how the ECHONET spec handles orchestration? 12:33:22 mt: ECHONET Lite Web API spec itself doesn't have orchestration capability 12:33:42 q+ 12:33:46 ack mc 12:34:44 q+ 12:36:40 kaz: ECHONET doesn't have multi-vendor/multi-standard orchestration capability, and so they would like to use WoT for that purpose 12:37:46 mt: right, we just wanted to show you that there is a use case which can't be implemented with existing standards 12:37:58 s/right,/right./ 12:39:00 ml: what kind of "orchestration" is expected here? 12:39:42 mt: multiple devices which use multiple data models 12:39:58 q? 12:40:01 ack k 12:40:07 ack m 12:40:24 mm: "orchestration" here is not just operation 12:40:32 ... but also include data 12:40:43 ... so need to maintain the data somewhere 12:40:58 q+ 12:42:05 ... btw, ECHONET Lite Web API spec has the device spec and the device description 12:42:48 ... more than one access point may be involved 12:43:13 q+ 12:44:34 kaz: I'm OK with accepting this use case description itself, but we should clarify our expectation for "orchestration" 12:45:14 ... based on some concrete scenario, e.g., the conductor work with the pianist, violinist, drummer, etc. :) 12:45:42 mm: right. and "orchestration" should include "configuration management" 12:46:06 mt: for the moment, we can avoid using the term of "orchestration" within our use case 12:46:39 q? 12:46:41 ack k 12:46:44 ack m 12:46:47 q+ 12:47:37 ack k 12:47:53 kaz: ECHONET is planning to join the Plugfest during TPAC 12:48:09 q+ 12:49:07 ... so we can think about actual "orchestration" during the Plugfest and its planning 12:49:26 ... note that their spec document is written in Japanese 12:49:54 ... but the most important definition is done by tables which include English as well as Japanese 12:50:13 ... so we can refer to part of their spec document 12:50:15 mm: right 12:50:17 q? 12:50:21 ack m 12:50:29 ml: ok 12:50:41 q+ 12:51:06 ... Matsuda-san, what kind of features for "orchestration" or "grouping" do you want in addition to your own grouping capability? 12:51:33 mt: @@@ missed 12:51:56 mm: things like where to store data, how to handle different data from various vendors, etc. 12:52:17 ack m 12:52:19 q+ 12:52:31 mm: we could put them on the document 12:53:50 ml: can we have some more detailed description about the gaps? 12:54:06 q+ 12:55:03 ... grouping and sequence of actions? 12:57:00 mm: note that it would take a few more weeks for them to add requirements description 12:57:13 ... since they need to discuss the changes internally 12:57:19 ml: ok 12:57:31 ack m 12:57:48 mm: wondering about the schedule 12:57:55 ml: let's go for weekly meeting 12:58:13 mm: will send an updated invite 12:59:01 kaz: can we move ahead with the ECHONET use case itself? 12:59:28 ... can we ask Matsuda-san to generate the HTML description for the use case document? 13:00:04 Proposal: Include ECHONET use case into use cases document 13:00:36 Resolution: Include ECHONET use case into use cases document 13:01:15 q? 13:01:17 ack k 13:01:47 ml: wondering about outreach 13:01:57 mm: could have joint meetings during TPAC 13:02:01 https://built.itmedia.co.jp/bt/articles/2108/31/news030.html 13:03:32 kaz: fyi, as I mentioned during the Marketing call today, big companies like Takenaka from Japan have started to use WoT as the basis for their IoT systems :) 13:03:36 ml: great! 13:03:42 [adjoured] 13:03:47 rrsagent, make log public 13:03:51 rrsagent, draft minutes 13:03:51 I have made the request to generate https://www.w3.org/2021/09/07-wot-uc-minutes.html kaz 13:04:33 i/wondering/topic: AOB/ 13:04:36 rrsagent, draft minutes 13:04:36 I have made the request to generate https://www.w3.org/2021/09/07-wot-uc-minutes.html kaz 15:04:47 Zakim has left #wot-uc