13:00:20 RRSAgent has joined #wot-uc 13:00:24 logging to https://www.w3.org/2023/02/07-wot-uc-irc 13:00:24 McCool_ has joined #wot-uc 13:00:36 meeting: WoT Use Cases 13:00:57 present+ Kaz_Ashimura, Ege_Korkan, Michael_Lagally, Michael_McCool 13:03:57 q+ 13:04:15 ack k 13:06:33 Mizushima has joined #wot-uc 13:07:03 luca_barbato has joined #wot-uc 13:07:19 present+ Tomoaki_Mizushima 13:08:33 topic: Agenda 13:08:40 present+ Luca_Barbato 13:08:43 q+ 13:08:48 scribenick: Ege 13:09:33 mm: let's reverse the order 13:09:41 q+ 13:09:43 ... because we could not talk about the policy last time 13:10:41 ack m 13:10:43 ack k 13:11:05 present+ Geun-Hyung_Kim 13:11:14 topic: Minutes Review 13:11:28 -> https://www.w3.org/2023/01/31-wot-uc-minutes.html Jan-31 13:11:52 i|Minutes|-> https://www.w3.org/WoT/IG/wiki/index.php?title=IG_UseCase_WebConf&action=edit§ion=13 Agenda for today| 13:11:59 ml: we merged the ETRI use case about pest control 13:13:19 mjk has joined #wot-uc 13:15:03 topic: Pull Requests 13:15:14 i/Pull/Minutes approved/ 13:15:15 subtopic: Updating Requirments Template 13:15:50 -> https://github.com/w3c/wot-usecases/pull/209 PR 209 - Update requirements-template.md 13:16:26 q+ 13:17:13 ml: should we go with this template? 13:17:28 mm: how do we refer to UCs? 13:17:31 ... do we have id? 13:17:37 ml: we have internal ids 13:18:36 (the webex coordinate on the WoT calendar is expired) 13:19:32 ek: I think we should use html ids otherwise the numbers will change 13:19:42 ack e 13:21:45 s/(the webex coordinate on the WoT calendar is expired)// 13:22:04 q+ 13:22:29 mm: we can do an example and then do the other ones 13:22:58 ml: we can take a strawman proposal 13:23:12 q+ 13:23:17 ack e 13:23:38 present+ Michael_Koster 13:23:44 q+ 13:24:40 mm: geolocation would be nice but it is a big UC 13:24:54 ek: how can one know other person's business case? 13:24:55 Geun_Hyung has joined #wot-uc 13:25:10 ... I think this should be in the UC input 13:25:58 mlagally has joined #wot-uc 13:26:06 present+ 13:26:21 ml: it can be also in the use case, like in the pest control it is about saving money 13:26:27 ack k 13:26:28 ack m 13:26:37 ek: I thought this means more the business importance 13:27:00 kaz: business importance is a bit delicate 13:27:21 mm: we should focus on the policy, justification can come later 13:28:01 q+ 13:28:26 s/Business importance is a bit delicate/saying "business justification" within this requirements description would be a bit too strong, also kind of delicate. So would suggest we simply say "Need and Motivation" instead./ 13:28:51 q? 13:28:56 ack m 13:29:16 ml: we should make sure that we give less priority to hobby projects and look for business cases 13:29:25 s/we should/Agree. Also we should/ 13:30:20 q+ 13:30:24 mm: we can list multiple justifications and assign them. then we can rank them 13:30:59 lb: how about having an impact gauge, whether it is business or societal 13:31:08 q+ 13:31:25 ack m 13:32:35 q+ 13:32:36 ml: Let's merge and iterate on it 13:32:45 ek: ok I will create a PR to remove 13:32:46 ack e 13:32:52 ack k 13:33:00 ek: should we update the HTML too? 13:33:04 ml: good question 13:33:11 mm: the final document would be html 13:33:26 q+ 13:34:15 ack m 13:34:32 lb: I think we should to stick to md but say what dialect we use 13:34:37 q+ Luca 13:34:50 q+ 13:34:54 ack l 13:34:56 ... we can use to github flavor 13:36:07 ml: is this the one? 13:36:18 lb: yes, we can also remove some complex cases 13:36:19 https://github.github.com/gfm/ 13:36:35 mm: I would say let's use github and not make it complicated 13:39:19 luca_barbato_ has joined #wot-uc 13:39:32 ml: we can remove the html version 13:39:40 q+ 13:40:41 ack m 13:42:00 mm: I think we can start with the geolocation 13:42:26 q+ 13:42:36 mm: it has variants but we can handle them internally 13:45:15 ml: can someone takeover the screen 13:45:45 s/takeover/take over/ 13:48:05 q? 13:49:14 q? 13:49:27 ack k 13:49:51 q+ 13:52:12 kaz: note that "geolocation" is a kind of data which could be used by various use cases including smart home, smart building and smart city. So this description is also a kind of generic description for various use cases derived from this./ 13:52:26 s|this./|this.| 13:52:39 mm: right. so would start with generic description for this 13:52:50 i/not that/scribenick: kaz/ 13:52:57 mm: also we need to capture variants. 13:53:06 i/also/scribenick: Ege/ 13:53:16 rrsagent, make log public 13:53:21 rrsagent, draft minutes 13:53:22 I have made the request to generate https://www.w3.org/2023/02/07-wot-uc-minutes.html kaz 13:55:22 lb: it might good to use HTML comments 13:55:28 mm: but they should be visible 14:00:16 [adjourned] 14:00:17 rrsagent, draft minutes 14:00:19 I have made the request to generate https://www.w3.org/2023/02/07-wot-uc-minutes.html kaz 16:03:02 Zakim has left #wot-uc