13:03:50 RRSAgent has joined #wot-uc 13:03:54 logging to https://www.w3.org/2022/12/20-wot-uc-irc 13:03:55 meeting: WoT Use Cases 13:04:01 chair: Michael_Lagally 13:05:41 present+ Kaz_Ashimura, Michael_Lagally, MunHwan_Choi, Changkyu_Lee, Michael_McCool 13:06:41 q+ 13:07:08 kaz: this is an IG call, so should be clear about WG relationship 13:07:26 ... also, we have some guests, who are WG but not IG members 13:08:06 ml: my understanding is that use case does not impact IP 13:08:45 kaz: we should be clear about that and need to formally invite them 13:09:04 mm: I propose we invite the guests to participate with a resolution 13:09:22 s/members/members. we can still invite them to this call as guests. MunHwan and Changkyu, please consider asking your AC rep to nominate you as IG participants as well 13:09:28 rrsagent, make log public 13:09:32 rrsagent, draft minutes 13:09:33 I have made the request to generate https://www.w3.org/2022/12/20-wot-uc-minutes.html kaz 13:10:11 q? 13:10:34 ryuichi has joined #wot-uc 13:10:44 present+ Ege_Korkan 13:10:50 present+ Tomoaki_Mizushima 13:10:54 proposal: Invite WG members from ETRI to participate in this call 13:11:06 resolution: Invite WG members from ETRI to participate in this call 13:11:19 topic: minutes 13:11:31 ml: notes from 6 Dec 2022 13:11:53 ... looked at and merged several PRs, and reviewed use case for agriculture 13:12:19 ml: kaz, you mind fixing the names, other than that fine with publishing them? 13:12:43 https://www.w3.org/2022/12/06-wot-uc-minutes.html 13:12:50 ... hearing no objections, notes can be published, with the name abbreviations expanded 13:13:07 topic: New Use Cases 13:13:32 subtopic: Smart Agriculture - Milking Use Case 13:13:42 ml: this is PR #200 13:15:13 ... Automatic milking system for dairy farm 13:15:32 Ege has joined #wot-uc 13:15:32 mm: we should look at what we discussed last time; tagging, security, etc. 13:15:45 ml: has been some improvements addressing this feedback 13:16:44 q+ 13:16:56 ack k 13:17:11 agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#Dec_20th.2C_2022 13:17:14 mm: see tagging has been improved, but security still needs work 13:17:26 ... however ok with merging for now 13:17:55 i|this is PR #200|-> https://github.com/w3c/wot-usecases/pull/200 PR 200 - Add new use cases for smart agriculture-Milking| 13:17:55 ack e 13:18:08 q+ 13:18:24 ege: did comment on the issue 13:18:48 ... also some feedback about why there is not as much detail on security and protocols 13:19:19 kaz: but in summary ok to merge, and proposers plan to make improvements later 13:19:20 q+ 13:19:27 ml: ok, also agree to merge it 13:19:34 ack k 13:20:15 ml: should however remove extra empty sections and move affiliation to the end of the document. 13:20:39 ... would be helpful to include contributors to end of the document 13:21:05 ... would like to ask submitters to make these changes, offline 13:21:32 mm: for the record I agree to merging it offline after those changes 13:21:57 q? 13:22:00 mhchoi: agree, I will do 13:22:13 rrsagent, make log public 13:22:14 ege: ok to merge 13:22:17 rrsagent, draft minutes 13:22:18 I have made the request to generate https://www.w3.org/2022/12/20-wot-uc-minutes.html kaz 13:22:33 q+ 13:22:36 ack e 13:22:57 ... but comment on process, want to do two phases, but feel that is a bit unrealistic due to gap between uc and req extraction 13:23:10 ... would be better to gather requirements when the uc is submitted 13:23:30 ml: yes, will have to think about how to improve process in next charter 13:23:55 ... but the original idea is that anyone can submit a uc, and may not be aware of all the existing specs 13:24:20 kaz: let's talk about this some other time 13:24:58 mm: agree, we have to get to the WG charter discussion today 13:25:04 s/let's/we've already started that discussion separately, so let's/ 13:25:15 topic: Other Contributions 13:25:27 ml: new requirements template, defer 13:25:42 ml: PR 202, adding coverage gaps 13:26:13 ... the coverage document lists the current use cases 13:26:37 ... I recently imported it into excel, did some cleanup, sorting, grouping 13:27:07 ... and this PR includes an MD file listing and grouping the gaps 13:27:54 mm: agree with merge, and I think this will also be helpful for our discussion next week 13:27:58 ml: merges 13:28:04 ml: next is PR 203 13:28:33 rrsagent, draft minutes 13:28:34 I have made the request to generate https://www.w3.org/2022/12/20-wot-uc-minutes.html kaz 13:28:41 ... requirements for next WG charter 13:29:06 i/this is an IG/topic: guests/ 13:29:34 i/PR 202/subtopic: PR 202/ 13:30:08 i|PR 202|-> https://github.com/w3c/wot-usecases/pull/202 PR 202 - adding coverage-gaps.md| 13:30:23 i|next is PR 203|subtopic: PR 203| 13:30:25 i|next is PR 203|subtopic: PR 203| 13:30:52 mm: let me draft an agenda for the charter discussion in Jan and will have to make sure this and the coverage-gaps.md file is linked from it 13:30:53 s|subtopic: PR 203|-> https://github.com/w3c/wot-usecases/pull/203 PR 203 - preparing requirements for next WG charter| 13:31:26 i|new requirements tem|subtopic: PR 193| 13:31:34 ml: would also like to mention Profile PR 344 which factors out profile requirements into a separate document 13:31:41 i|new requirements tem|-> https://github.com/w3c/wot-usecases/pull/193 PR 193 - Add new requirement fields for the template| 13:31:46 q+ 13:31:47 rrsagent, draft minutes 13:31:49 I have made the request to generate https://www.w3.org/2022/12/20-wot-uc-minutes.html kaz 13:31:55 ack k 13:32:36 ege: is mention of profiles, this is the issue with having multiple requirements 13:32:39 ack e 13:32:54 ... should be made clear if this is for current or next profile document 13:33:11 ml: we have been narrowing down 1.0 to fit in the current charter 13:33:26 ... so 1.x is for things that we don't feel will fit in the current charter 13:34:05 ege: ok, perhaps can explain at the top of the document, was a little confusing from the name of the document 13:34:10 q+ 13:35:04 i|would also like|subtopic: PR 204| 13:35:12 ack 13:35:19 s/ack// 13:35:20 ack k 13:35:46 i|would also like|-> https://github.com/w3c/wot-usecases/pull/204 PR 204 - carry over profile requirements from profile spec| 13:36:26 i|would also like|-> https://github.com/w3c/wot-profile/pull/344 wot-profile PR 344 - refactoring requirements to a separate document| 13:37:12 topic: Requirements Coverage and Gaps 13:37:31 mm: think we need to look at both coverage gaps and deliverable proposals 13:38:04 ml: ok, but first want to clean up what we have, in particular get rid of duplicates 13:38:07 i|think we|-> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage-gaps.md coverage-gaps.md| 13:38:20 mm: ok, makes sense 13:38:52 i|think we|-> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv coverage.csv| 13:40:27 mm: for a start, the semicolon indicates a set of requirements, so for instance sensory modality is not part of geolocation, but a different topic under accessibility 13:40:35 ... also alternative I/O 13:41:01 q+ 13:44:12 mm: would keep FoI/SSN, geopose (orientation), topology 13:44:44 ack k 13:45:16 mm: to be clear about FoI, sometimes the location of that is different from the device itself 13:46:18 q+ 13:48:14 mm: under protocol binding, not clear what LDWAN is about, that's not a protocol, but a communication technology 13:48:57 kaz: suggest some categories, first there are "Other SDOs/Ecosystems/IoT Ecosystems" 13:49:16 ack k 13:49:16 ... then LPWAN, etc. are low-level protocols 13:50:38 ml: ok, bit of overlap with KNX 13:51:08 q+ 13:51:10 mm: also Matter is missing, would put under "Emerging standards"; and should be listed under smart home 13:52:09 i/for a start/(all start to edit coverage-gaps.md dynamically based on the discussion during this meeting)/ 13:52:20 q? 13:52:31 ack e 13:52:42 q+ 13:52:43 mm: under security, I also thing we should add something similar for emerging standards, e.g. DID 13:52:54 ack k 13:52:59 ... also, I would add key distribution, esp on the LAN 13:53:09 rrsagent, draft minutes 13:53:11 I have made the request to generate https://www.w3.org/2022/12/20-wot-uc-minutes.html kaz 13:53:49 ml: complex interactions, thing graphs 13:53:49 ... basically higher level descriptions 13:53:49 q+ 13:53:56 ege: I think here we have two categories: groups of devices vs. complex interactions 13:54:15 ... behaviour vs relationships 13:54:38 ml: ok 13:54:52 ml: Digital twins also mention twin graphs 13:55:06 q? 13:55:11 ack e 13:55:19 q+ 13:56:01 q+ 13:56:21 kaz: not clear what graphs means here 13:56:26 ... grouping, management 13:56:33 Choi has joined #wot-uc 13:56:57 ml: we have links already 13:57:06 kaz: I think relationship is clearer 13:57:14 Choi has left #wot-uc 13:57:46 ... also, grouping and history were mentioned by ECHONET/Matsuda 13:58:13 q? 13:58:18 ack k 13:58:24 ack e 13:59:00 ege: for individual items that are in two categories, how can we relate, maybe duplicate, link somehow 13:59:05 ml: what should I do? 13:59:15 ege: eg. like 47 and line 55 are the same 13:59:45 q? 13:59:47 ... but they perhaps belong in two different categories 13:59:55 ml: (adds a "see also" note) 14:00:09 q+ 14:00:34 ack k 14:00:46 kaz: please put a note about where we were 14:00:57 ml: clear by formatting, but will add a note 14:01:12 ml: AOB? 14:01:18 rrsagent, draft minutes 14:01:20 I have made the request to generate https://www.w3.org/2022/12/20-wot-uc-minutes.html kaz 14:01:35 (none) 14:01:44 [adjourned] 14:01:46 rrsagent, draft minutes 14:01:47 I have made the request to generate https://www.w3.org/2022/12/20-wot-uc-minutes.html kaz