11:58:28 RRSAgent has joined #wot-uc 11:58:28 logging to https://www.w3.org/2021/09/28-wot-uc-irc 11:58:55 meeting: WoT Use Cases 11:58:59 present+ Kaz_Ashimura 12:00:10 present+ Jack_Dickinson 12:01:46 Mizushima has joined #wot-uc 12:01:47 present+ Michael_Lagally 12:03:17 dezell has joined #wot-uc 12:03:34 present+ David_Ezell 12:04:47 present+ Tomoaki_Mizushima 12:10:07 mlagally has joined #wot-uc 12:10:19 q? 12:10:28 present? 12:10:38 zakim, who is here? 12:10:38 Present: Kaz_Ashimura, Jack_Dickinson, Michael_Lagally, David_Ezell, Tomoaki_Mizushima 12:10:41 On IRC I see mlagally, dezell, Mizushima, RRSAgent, Zakim, kaz, Joshue108, benfrancis 12:12:32 s/present?// 12:13:12 scribenick: kaz 12:13:25 topic: TPAC 12:13:40 -> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2021 WoT TPAC wiki 12:13:46 https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2021 12:13:49 ml: (goes through the TPAC wiki above) 12:14:14 ... what should be presented about use cases there? 12:15:12 -> https://w3c.github.io/wot-usecases/ wot-usecases doc 12:15:38 ml: we have domain-specific use cases (and horizontal ones) within the use cases document above 12:15:50 ... there is a section about "retail" as well 12:16:16 ... let's pick up some of the domains during TPAC vF2F 12:16:22 de: when to have the discussion? 12:16:28 ml: not scheduled yet 12:16:34 ... any preference? 12:16:54 de: Jack and myself will be out for another event next week 12:17:02 ml: (goes through the schedule) 12:17:44 ... next week (Oct. 5, 7) and the week of Oct 25 (26, 27, 28) 12:18:55 kaz: any preferred date? 12:19:41 .. 26? 12:19:49 1Prefered UC slot during TPAC: 2:00 UTC on Tuesday, Oct 26th 12:20:34 kaz: NHK also wanted to talk about their media use case 12:20:49 ... so maybe we can use the whole 2 hours on that day :) 12:20:52 ml: ok 12:21:08 ... also some update on Takenaka and WoT-JP CG 12:21:09 kaz: ok 12:21:13 topic: Minutes 12:21:40 -> https://www.w3.org/2021/09/21-wot-uc-minutes.html Sep-21 12:21:50 ml: (goes through the minutes) 12:22:38 ... any objections? 12:22:42 (none; approved) 12:22:55 topic: Editorial updates 12:23:24 -> https://github.com/w3c/wot-usecases/pulls PRs 12:23:33 ml: (goes through the PRs) 12:23:52 subtopic: PR 131 12:24:00 -> https://github.com/w3c/wot-usecases/pull/131 PR 131 - Cultural Spaces (Museums) use case 12:24:12 ml: the proposer wrongly deleted the template itself 12:24:17 ... but fixed the problem 12:24:55 de: missing "f" for "affiliation", btw 12:25:02 ml: will fix it 12:25:37 ... other than that, would merge this PR 12:25:44 ... any objections? 12:26:08 (none; merged) 12:26:30 subtopic: PR 147 12:26:52 -> https://github.com/w3c/wot-usecases/pull/147 PR 147 - Reinstate / Update use-case-template.html 12:27:11 ml: some conflicts to be fixed 12:27:17 ... will work on that later 12:27:36 subtopic: PR 117 12:27:58 -> https://github.com/w3c/wot-usecases/pull/117 PR 117 - WIP: Add liaisons 12:28:21 ml: close it 12:28:23 (closed) 12:28:33 subtoic: PR 148 12:29:03 -> https://github.com/w3c/wot-usecases/pull/148 PR 148 - updated liaison chapter 12:29:19 ml: sections for liaison orgs 12:29:48 kaz: asking ECHONET about brief text on their work 12:30:07 ml: yeah, not big text but brief summary 12:30:40 topic: Issues 12:30:46 subtopic: Issue 135 12:31:17 -> https://github.com/w3c/wot-usecases/issues/135 Issue 135 - Improve references: Use Specref Database references where avaliable for release 2.0 12:31:25 s/avaliable/available/ 12:31:33 ml: some trouble with ReSpec 12:31:56 s/ReSpec/Specref/ 12:32:58 ... (goes through the Specref entries) 12:33:41 ... would like to continue to work on "publication-2.0" issues 12:33:52 kaz: that means "next publication". right? 12:33:54 ml: yes 12:33:54 https://github.com/w3c/wot-usecases/issues?q=is%3Aissue+is%3Aopen+label%3Apublication-2.0 12:34:19 ml: those issues marked as "publication-2.0" above 12:34:28 topic: Retail use cases 12:34:41 ml: any high-level introduction? 12:35:04 de: as we develop based on user story 12:35:35 ... one of our outcome should be to figure out what would be useful for people 12:35:41 ... one of the biggest problems 12:35:55 ... a lot of aspects might be important 12:36:00 ... one of the things is 12:36:17 ... controlling a device in a concrete use case 12:36:26 ... e.g., your freezers 12:36:37 ... how to hook up things 12:36:50 ... interfering things 12:37:15 ... we've done our best to justify why given device might need to be standardized 12:37:31 ... ecosystem to accomplish some task 12:38:00 ... controlling single freezer is not nearly that important 12:38:35 ... the store operation, etc., related to the merchants' need 12:38:50 jd: things related to spoil edge 12:39:09 de: how to do categorization is another question 12:39:51 kaz: based on geolocation information? 12:40:15 ml: would it make sense to have discussion by a smaller group? 12:40:42 ... including Michael McCool 12:41:05 ... thought there was some ZIP file 12:41:14 de: you can share the resource here 12:41:48 ... (shares the information on Conexxus Use Cases - first draft) 12:42:17 ... let me see the original document 12:42:41 rrsagent, make log public 12:42:45 rrsagent, draft minutes 12:42:45 I have made the request to generate https://www.w3.org/2021/09/28-wot-uc-minutes.html kaz 12:43:18 ... (shows the original document) 12:43:24 ... sales-related devices 12:43:39 ... facilities, data and power equipment 12:43:48 ... food preparation and food service devices 12:44:04 ... classification field to categorize the devices 12:45:14 ml: wondering about "indoor and outdoor freezers" and "kitchen refrigerator" 12:45:30 jd: a little bit of overlap and some more differences 12:45:50 chair: Lagally 12:46:05 ml: maybe we can pick up some key use cases 12:46:17 q+ 12:46:43 ... or do we want to categorize them with some fine-grained categories? 12:47:01 de: (shows a use case description) 12:47:23 jd: yeah, this is an actual use case 12:48:02 de: no outdoor refrigerator here 12:48:11 ... let me provide one 12:48:48 ... btw, this list of devices is more useful 12:49:10 ml: looks a good categorization 12:49:23 ... about a gas station? 12:49:27 de: typically :) 12:50:11 ml: why don't you create Pullrequests based on the use cases? 12:50:36 de: wondering about category and class 12:50:40 ... how to use the "Class"? 12:50:47 ml: we've not used it yet 12:51:36 de: can we use the "Class" field to clarify the details? 12:51:41 ml: sounds good 12:52:35 de: would provide a use case for the Oct 26 meeting 12:53:18 ml: 5 stories under one use case are mentioned here (within the device list) 12:53:29 de: maybe one-page presentation on our situation 12:54:08 ... in 10 minutes 12:54:21 ml: during the Oct-26 meeting? 12:54:24 de: yes 12:54:29 ml: ok 12:54:38 ... my question is what/how to review the proposals 12:55:07 q? 12:55:23 de: may remove the classification of indoor/outdoor 12:55:31 jd: makes sense 12:56:52 kaz: think you can use the "Category" field for "Retail" 12:57:10 ... and use the "Class" field to show actual categorization of your use cases 12:57:12 de: ok 12:57:16 ... can do within a few days 12:57:36 ml: and some more discussion/review including McCool? 12:57:38 de: ok 12:57:51 ml: you can create Pullrequests as well 12:58:16 ack k 12:58:40 de: how about aiming 19th? 12:58:42 ml: ok 12:59:15 kaz: nice 12:59:25 ... we can start with one specific use case 12:59:39 ... and use the "Variants" field to show possible variants 13:00:16 ml: let's continue the discussion by emai 13:00:22 s/emai/email/ 13:00:38 kaz: so on 19th possible initial use case description 13:01:02 ... and then on 26th actual use case discussion during TPAC vF2F with one pager slide 13:01:05 all: yes 13:01:09 ml: aob? 13:01:10 (none) 13:01:14 [adjourned] 13:01:18 rrsagent, draft minutes 13:01:18 I have made the request to generate https://www.w3.org/2021/09/28-wot-uc-minutes.html kaz 14:58:57 Zakim has left #wot-uc