13:01:29 RRSAgent has joined #wot-uc 13:01:33 logging to https://www.w3.org/2023/03/07-wot-uc-irc 13:01:54 meeting: WoT Use Cases 13:02:25 present+ Kaz_Ashimura, Changkyu_Lee, Michael_McCool 13:04:02 present+ Mun_Hwan_Choi, Michael_Lagally, Tomoaki_Mizushima 13:04:08 chair: Lagally 13:04:16 rrsagent, make log public 13:04:20 rrsagent, draft minutes 13:04:22 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 13:04:53 mlagally has joined #wot-uc 13:05:04 zakim, who is on the call? 13:05:04 Present: Kaz_Ashimura, Changkyu_Lee, Michael_McCool, Mun_Hwan_Choi, Michael_Lagally, Tomoaki_Mizushima 13:06:07 Mizushima has joined #wot-uc 13:07:33 McCool has joined #wot-uc 13:07:43 scribenick: McCool 13:07:47 ryuichi has joined #wot-uc 13:08:00 topic: housekeeping 13:08:15 https://www.w3.org/2023/02/07-wot-uc-minutes.html 13:08:18 ml: minutes from Feb 7, last use cases call 13:09:01 ... small typo in spelling of requirements 13:09:03 s|https://www.w3.org/2023/02/07-wot-uc-minutes.html|-> https://www.w3.org/2023/02/07-wot-uc-minutes.html Feb-7| 13:09:05 kaz: fixed 13:10:05 ml: no objections to publishing? 13:10:13 ... none, let's publish 13:10:19 topic: PRs 13:10:29 subtopic: PR #205 13:10:42 ml: UC and requirements process 13:10:54 ... is a PPTX, will provide a PDF 13:10:58 ... skip for now 13:11:07 subtopic: PR #210 13:11:20 ml: fixes links in template 13:11:25 i|UC and|-> https://github.com/w3c/wot-usecases/pull/205 PR 205 - UC and requirement process - new WG charter| 13:11:50 i|fixes links|-> https://github.com/w3c/wot-usecases/pull/210 PR 210 - Fix the links to the templates| 13:12:15 mm: should we use absolute links to be safer? 13:12:25 ml: should not matter in this case 13:12:29 mm: ok, let's merge 13:12:35 subtopic: PR #211 13:12:41 ml: SIFIS use case 13:12:56 ... need Luca for this, will defer 13:13:23 subtopic: PR #212 13:13:30 i|SIFIS|-> https://github.com/w3c/wot-usecases/pull/211 PR 211 - SIFIS-Home use-case| 13:13:30 ml: removes business justification 13:14:17 mm: should probably be a filtering/prioritization step in the *process*; maybe create an issue for followup? 13:14:51 i|removes|-> https://github.com/w3c/wot-usecases/pull/212 PR 212 - Remove Business Impact from Requirements Template| 13:15:42 q+ 13:15:49 ml: creates issue #220 13:16:34 mm: we can define later, will have to put comments on issue 13:16:49 -> https://github.com/w3c/wot-usecases/issues/220 Issue 220 - Process needs to take Business motivation into account 13:16:53 ack k 13:17:31 ml: merges PR 13:18:15 i/we can/kaz: I agree it would be useful to have description on business need. However, as already noted the other day, I'm not sure "Business Justification" would be the best term for this purpose./ 13:18:17 Mizushima_ has joined #wot-uc 13:18:43 i/we can/mm: probably something like "Business Motivation" would be better./ 13:18:49 i/we can/kaz: agree/ 13:18:54 rrsagent, draft minutes 13:18:56 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 13:19:13 sorry today I also had an overlapping meeting 13:19:29 present+ Luca_Barbato 13:19:41 s/sorry today I also had an overlapping meeting// 13:19:44 rrsagent, draft minutes 13:19:46 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 13:20:22 i/it would be useful/scribenick: kaz/ 13:20:27 i/we can define/scribenick: McCool/ 13:20:29 rrsagent, draft minutes 13:20:31 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 13:20:51 subtopic: PR #214 13:21:08 mm: just a start, but I wanted to describe the variants 13:21:26 i|just a start|-> https://github.com/w3c/wot-usecases/pull/214 PR 214 - Create geolocation-requirements.md| 13:21:55 rrsagent, draft minutes 13:21:56 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 13:22:32 ... but still a lot of work to do, missing sections, etc. 13:25:09 -> https://github.com/w3c/wot-usecases/blob/mmccool-geolocation-requirements/REQUIREMENTS/geolocation-requirements.md geolocation-requirements.md (rendered) 13:25:14 rrsagent, draft minutes 13:25:16 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 13:25:54 ... can either merge and create issue, or leave open and ask for comments on PR 13:26:04 ml: let's leave it open and ask for input and reviews 13:26:32 q+ 13:28:02 mm: if people can use the "suggestion" features in github for concrete comments 13:28:17 q+ 13:28:20 ack luca 13:29:16 ... for large changes, make a PR against my branch 13:29:38 ack k 13:30:36 kaz: if large changes are expected then better to merge and make PRs against the repo 13:30:52 mm: suggest leave open for week to capture comments, then merge, then do bigger PRs 13:31:08 ml: reminder that is an example, so comments on the template also useful 13:33:14 kaz: still better to merge in my opinion 13:33:27 mm: either is ok with me; will probably immediately create a new PR 13:33:44 kaz: also suggest we merge the template PR as well 13:34:13 ml: fine with me 13:35:01 ml: ok, let me merge the template PR 13:35:55 mm: geolocation as well 13:36:40 ml: including some changes, including adding "Draft" to title; merged 13:37:35 subtopic: PR #216 13:37:43 ml: by Changkyu Lee 13:37:53 ... et al 13:38:00 i|by C|-> https://github.com/w3c/wot-usecases/pull/216 PR 216 - A new usecase about smart agriculture| 13:38:04 rrsagent, draft minutes 13:38:05 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 13:38:35 cl: feel IoT is useful in agriculture, want to submit several use cases for this industry 13:38:50 ... two new use cases actually, #216 is for livestock management 13:38:56 -> https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/216/5fdbe0c...echkyu:ded354f.html#Livestock%20Health%20Management diff - 2.1.6 Livestock Health Management 13:39:23 ... IoT is useful to track health status, combined with AI to do prediction 13:39:53 ... can send alerts if it detects problems 13:40:23 ... need sensors, cameras, need wireless networks, need environmental controls, some systems to analyze the data 13:40:42 ... have some expected data as well, some means to detect disease 13:41:01 ... environmental controls also useful: humidity, temperature, CO2 levels, etc. 13:41:23 ... result is a plan to address issues 13:41:58 q+ 13:42:09 q+ 13:42:20 cl: as for requirements, have communication, sensors, etc. 13:42:30 ... note that failures need to be dealt with 13:42:43 q? 13:42:46 q+ 13:42:50 q+ 13:45:21 mm: could see clearer requirements, e.g. for protocols esp for streaming 13:45:31 ... and analytics 13:45:45 luca: interesting that have three kinds of sensors 13:45:54 ... one is biometric 13:46:02 ... another is multimedia, e.g. video 13:46:32 ... both need to identify entities, i.e. a particular cow, where it is, etc. 13:46:35 q? 13:46:38 ack mc 13:46:39 ack lu 13:46:47 ... would be good to cross-reference with other use cases 13:47:05 ... for example, with geolocation 13:47:42 ... other issues, on-site vs. off-site compute 13:47:54 mm: what third category of sensor? 13:48:15 luca: biometric, multimedia, location 13:48:28 s/location/identity/ 13:48:38 s/location/location and identity/ 13:49:17 kaz: would be useful to consider variations, e.g. might be differences between how chickens and cows are managed; also differences by country 13:49:36 ack k 13:49:42 ack ml 13:50:17 ml: a bit more of a description of what benefits the AI would bring; I see predictive results, etc. 13:50:27 ... but maybe also learning from other farms? 13:50:42 ... for example, discovering communicable diseases early 13:50:54 ... by comparing data across farms 13:51:19 s/by country/by country and area/ 13:51:23 ml: in summary I think it is a useful addition; we have plants, but not animals, which has additional aspects like dynamic location 13:51:36 ml: do you want to refine it or merge it now? 13:52:10 mm: I suggest we merge it and look for future PRs to improve 13:52:10 q 13:52:18 s/q// 13:52:24 q+ 13:52:29 ... as it is it is quite good, comments are in the nature of improvements, not blockers 13:53:03 mz: agree to merge, but if possible, would like to see a diagram if possible (as a future improvement) 13:53:17 ml: what would you like to see in the diagram? Logical components? 13:53:40 mz: how to get data and how to flow data into server 13:53:51 q+ 13:53:54 ack mi 13:54:43 ml: would you want to do an image in a future PR? 13:54:59 cl: yes, would like to merge this version and do another PR for improvements 13:55:19 kaz: agree would be useful have a diagram for dataflow, but can be done later 13:55:27 ... diagram can also include stakeholders 13:55:32 ack k 13:56:05 ml: ok, we agree to merge - done. Looking forward to further improvements. 13:57:15 ml: let's close the meeting here, will look at other topics next week 13:57:57 [adjourned] 13:58:04 rrsagent, draft minutes 13:58:05 I have made the request to generate https://www.w3.org/2023/03/07-wot-uc-minutes.html kaz 16:06:58 Zakim has left #wot-uc