12:06:43 RRSAgent has joined #wot-uc 12:06:47 logging to https://www.w3.org/2023/03/28-wot-uc-irc 12:06:49 Zakim has joined #wot-uc 12:06:53 meeting: WoT Use Cases 12:06:57 chair: McCool 12:07:35 present+ Kaz_Ashimura, Michael_McCool, Changkyu_Lee, Luca_Barbato, Sunghyun_Yoon, Tomoaki_Mizushima 12:07:41 agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#March_28th.2C_2023 12:07:43 topic: Minutes 12:07:53 -> https://www.w3.org/2023/03/21-wot-uc-minutes.html Mar-21 12:08:13 regrets+ Lagally 12:09:41 approved 12:09:56 q+ 12:10:40 ack k 12:11:03 present+ Ege_Korkan 12:11:45 Ege has joined #wot-uc 12:11:52 q+ 12:12:18 q- 12:12:37 topic: Contributions 12:13:10 kaz: note that we need to think about the policy and procedure about how to handle the use case proposals before adding actual use cases 12:13:22 q+ 12:13:28 mm: don't disagree, but we don't have Lagally today, so... 12:14:24 kaz: right. specifically for today, we can't have the discussion on the policy and procedure without Lagally... 12:15:15 q+ 12:16:03 mm: we should not reject use case proposals because we're working on the discussion... 12:16:39 kaz: yeah 12:16:58 ... I personally think we could have one-hour call to make sure the initial direction 12:17:13 ... then think about the detail based on the new proposals 12:17:25 mm: yeah 12:17:47 q+ 12:17:51 ... given the queue of the proposed use cases is relatively empty, it's good timing to discuss the policy and procedure 12:17:54 ack e 12:17:55 q+ 12:18:48 mm: we can think about MD proposals at least 12:18:53 q? 12:18:59 ack l 12:19:17 lb: regarding the features 12:19:32 ... there is a default procedure of getting contributions 12:19:43 ... so we could use it for a while 12:19:46 mm: yeah 12:19:58 ... and we're discussing how to improve the procedure 12:21:40 ... we should shut down new contributions when we discuss the policy 12:23:27 topic: PRs 12:23:49 subtopic: PR 218 12:24:02 -> https://github.com/w3c/wot-usecases/pull/218 PR 218 - Proposed new usecase of smart agriculture 12:24:32 i/PRs/kaz: right. we should declare the agenda would be the discussion around the policy and procedure at some point./ 12:24:48 cl: (goes through the proposal) 12:25:02 q? 12:25:04 q+ 12:25:13 -> https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/218/5fdbe0c...mhchoi76:f01a778.html#Agricultural%20Machinery%20Management diff 12:26:39 ack e 12:26:43 q- 12:26:44 ack m 12:27:26 mm: suggest w describe the acronyms, e.g., GNSS 12:27:40 s/w d/we d/ 12:27:52 ... also talk about the means of standardization 12:28:21 ... should add motivation text 12:28:33 cl: agree 12:28:59 mm: also around I18N 12:29:13 ... we have need for scheduling 12:29:26 ... e.g., Daylight-Saving time depending on the areas 12:29:45 ... holidays, locations, translation into some specific languages... 12:30:19 ... also why don't we think about workers in addition to the machinery 12:30:34 ... people driving the machinery 12:31:23 ... also weather forecast is very important 12:31:55 s/motivation text/motivation text around various kinds of machinery/ 12:32:18 q+ 12:33:33 ack k 12:33:41 kaz: basically agree with McCool 12:34:47 ... also think having variations of machinery, species of fruits/vegetables, lands, locations, etc., would be good motivation for this use case to be covered by WoT 12:34:58 ack k 12:34:59 q+ 12:36:23 kaz: in addition, smart agriculture can't exist by itself 12:37:26 ... would be nicer to work with smart supply-chain services to deliver the food as product to the consumers 12:37:48 ... might be better to describe that as a separate use case, though 12:37:52 cl: yeah 12:38:01 ... would be better to describe that separately 12:38:05 q? 12:38:08 ack k 12:39:20 mm: (adds comments based on the discussion) 12:40:05 ... like smart factory but more influenced by environment 12:40:20 ... how to handle the potential use case on supply chain? 12:40:45 kaz: we can simply create a GitHub Issue for that 12:41:04 ... pointing to this use case and some others like the ones from Conexxus 12:41:14 mm: yes 12:41:26 ... (creates a new Issue for that purpose) 12:41:28 q? 12:41:32 rrsagent, make log public 12:42:33 ... and mention the Issue from PR 218 12:42:37 ... can we merge this PR 218? 12:44:19 ... (adds some more comments) 12:44:54 ... need to resolve the conflicts later offline... 12:45:11 subtopic: PR 211 12:45:26 -> https://github.com/w3c/wot-usecases/pull/211 PR 211 - Hazard Annotation 12:45:38 lb: asked to extend the use cases 12:45:50 s/asked/was asked/ 12:46:26 ... to cover the possibility of things being dangerous 12:46:44 ... added a few more scenarios 12:48:13 ... chemical hazards, biological hazards, physical hazards, ... 12:48:53 mm: can see the diff between this updated version and the previous version? 12:49:01 lb: can simply review the updated one 12:51:10 ... tried to expand the hazard cases because got a comment not to dive into the solution 12:51:34 mm: different type of hazards are handled by different standards. Right? 12:51:49 ... electric hazards, chemical hazards, etc. 12:52:00 ... so we need to refer to various IoT standards 12:53:03 q+ 12:55:33 ack k 12:56:11 kaz: for the use case description itself, we don't/can't prescribe which ontology would be used for which kind of hazard 12:56:52 ... we should rather describe our expectation from the user's viewpoint about what to be handled how 12:57:08 ... including various types of hazards in various areas and situations 12:57:28 mm: I myself need to review this a bit more 12:58:10 lb: waiting for comments 12:58:34 ... so if we don't get any further comments, would like to merge this PR 12:58:37 mm: yeah 12:58:47 q+ 12:59:21 kaz: can understand your feeling 12:59:48 ... and so think we should clarify the policy, procedure and what to be described how before getting actual proposals... 13:00:17 mm: once Lagally is back, we should think about that 13:00:40 [adjourned] 13:00:45 rrsagent, make log public 13:00:48 rrsagent, draft minutes 13:00:50 I have made the request to generate https://www.w3.org/2023/03/28-wot-uc-minutes.html kaz 13:00:59 zakim, who is on the call? 13:00:59 Present: Kaz_Ashimura, Michael_McCool, Changkyu_Lee, Luca_Barbato, Sunghyun_Yoon, Tomoaki_Mizushima, Ege_Korkan