12:00:32 RRSAgent has joined #wot-uc 12:00:32 logging to https://www.w3.org/2021/08/31-wot-uc-irc 12:06:43 meeting: WoT Use Cases 12:07:03 present+ Kaz_Ashimura, Michael_McCool Tetsushi_Matsuda, Tomoaki_Mizushima 12:07:43 matsuda has joined #wot-uc 12:07:49 McCool has joined #wot-uc 12:10:20 scribenick: kaz 12:10:43 agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#Agenda_31.8. 12:10:55 topic: ECHONET review/updates/translations 12:11:15 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template.md ECHONET use case MD 12:11:44 ->https://github.com/w3c/wot-usecases/blob/main/USE-CASES/wot-usecase-echonet.md echonet use case 12:11:54 s|-> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template.md ECHONET use case MD|| 12:12:47 tm: a use case consists of ECHONET devices 12:13:09 mm: for people at home and outside home? 12:13:24 tm: yes, people going out of the home 12:13:56 mm: fyi, OGC is working on Geofencing to identify the location 12:14:12 tm: ok 12:14:31 ... but please note this use case itself doesn't use Geofencing 12:14:37 mm: ok 12:14:43 ... the smartphone is the UI 12:14:58 ... going to talk with the cloud service 12:15:07 ... so not directly talk with the devices 12:15:10 tm: right 12:15:25 mm: would assume the connections is HTTP-based 12:15:32 tm: yes, that's my assumption 12:18:17 mm: ECHONET consolidated Things and other parties' devices included here 12:18:33 ... what is a bit confusing is 12:18:38 ... having two hubs 12:18:48 ... 1. ECHONET Lite Controller at the home 12:19:09 ... and 2. Device manufacturer's server on the cloud 12:19:45 tm: some devices can be directly connected to the device manufacturer's server 12:20:19 ... but wanted to avoid confusion 12:21:23 mm: it's common to have multiple paths to the cloud, e.g., SmartThings in addition to ECHONET 12:22:56 tm: ECHONET itself doesn't specify the protocol between the ECHONET controller and the device manufacturer's server 12:23:31 mm: ok 12:23:59 ... btw, the latest template has an additional section of "Variants" 12:24:42 ... to describe possible variants of the proposed use case 12:25:08 ... if applicable 12:25:13 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template.md latest template 12:26:03 tm: need to check with the ECHONET HQ if need to add it 12:26:09 mm: that's not mandate 12:26:41 ... our main target is the Web interface 12:27:15 ... i.e., Smartphone-Service provider's serer A-Device manufacturer's server 12:27:38 q+ 12:28:43 ack k 12:29:14 kaz: so the Service provider's server A and B would handle the possible binding between the ECHONET Lite Web API and the WoT 12:29:16 tm: yes 12:29:54 mm: possibly a 1:1 mapping 12:31:51 tm: it depends on the level of coverage of the ECHONET Lit Web API capability by WoT 12:32:19 mm: maybe we might want to have an ECHONET Profile for WoT at some point to clarify the coverage 12:33:00 s/mm:/kaz:/ 12:33:16 mm: the smartphone might talk with all the devices one by one 12:33:48 ... or the Service provider's server A may provide a virtual device including those devices 12:34:32 kaz: yeah 12:34:52 ... as Matsuda-san described in March, ECHONET Lite Web API has device grouping capability 12:35:23 ... but probably for this use case and the upcoming Plugfest, they would like to start with one-by-one connection 12:35:29 mm: ok 12:35:35 ... I got the use case itself 12:36:04 ... and would like to think about some more possible settings as useful subsets (if possible) 12:39:31 ... (goes through the ECHONET Lite Web API Dev Specs v. 1.3.0) 12:39:47 -> https://echonet.jp/wp/wp-content/uploads/pdf/General/Download/web_API/ECHONET_Lite_Web_API_Dev_Specs_v1.3.0.pdf ECHONET Lite Web API Dev Specs v.1.3.0 12:39:51 s/v. /v./ 12:40:59 (Their "Device Description" is described P32 and the following pages.) 12:42:42 mm: the next step is whether we merge this proposed use cases into the main Use Cases document or not 12:43:21 ... would have a prototype implementation as well 12:43:35 kaz: yes, that's why I'm asking them to join the Plugfest during TPAC 12:45:09 mm: would see which device can be mapped to TD how 12:46:08 ... I think this interface, e.g., for battery, is quite similar to TD 12:46:53 kaz: can we ask Matsuda-san to start generating the HTML? 12:47:17 mm: would see Geofencing mentioned as a possible variant 12:48:04 ... but if Matsuda-san can wait, would be better to talk with Lagally next Tuesday 12:49:08 ... and then make decision 12:49:49 tm: the next official meeting on the ECHONET side will be held Wednesday next week 12:50:10 ... so can't guarantee we can add additional variants 12:51:35 kaz: I think Geofencing itself is rather a horizontal feature which could be applied various vertical use cases 12:51:53 ... so don't have to describe it within this use case description 12:52:20 ... we can think about combination of Geofencing and other vertical use cases later 12:52:29 mm: that's true 12:52:33 [adjourned] 12:52:41 rrsagent, make log public 12:52:46 rrsagent, draft minutes 12:52:46 I have made the request to generate https://www.w3.org/2021/08/31-wot-uc-minutes.html kaz 14:35:05 Zakim has left #wot-uc