13:08:32 RRSAgent has joined #wot-uc 13:08:32 logging to https://www.w3.org/2022/12/06-wot-uc-irc 13:08:39 meeting: WoT Use Cases 13:09:20 present+ Kaz_Ashimura, Michael_Lagally 13:13:28 present+ Michael_McCool 13:16:05 present+ Tomoaki_Mizushima 13:16:09 topic: Agenda 13:16:12 ml: two topics 13:16:22 ... PR review 13:16:34 ... and due diligence 13:16:38 Mizushima_ has joined #wot-uc 13:16:47 topic: PRs 13:16:51 subtopic: PR 200 13:17:00 s/200/193/ 13:17:26 -> https://github.com/w3c/wot-usecases/pull/193 PR 193 - Add new requirement fields for the template 13:17:42 ml: Ege proposes we add a requirement field to the use case template 13:17:58 ... comments from Mizushima-san there 13:18:13 -> https://github.com/w3c/wot-usecases/pull/193#issuecomment-1113986027 Mizushima's comments 13:19:13 ml: Mizushima-san's comments are reasonable 13:19:23 ... don't think we need to rush in 13:19:46 q+ 13:20:40 ... (shows the proposed new requirements) 13:22:28 kaz: there are two possible options to handle requirements 13:22:39 ... one possibility is putting requirements into each use case 13:22:54 ... and second option is generating requirements template separately 13:23:05 ... I personally think the second option would make more sense 13:23:24 ... because some (sometimes many) of the use cases have similar or identical requirements and 13:23:40 ... putting them into each use case template would be too much and kind of redundant 13:23:42 mm: agree 13:24:24 ... also changing the use case template would make it inconsistent with the current use cases 13:24:30 q+ 13:24:49 ack k 13:24:55 kaz: yes 13:25:28 ... note that we still reuse Ege's proposed items on requirements to update the requirements template 13:25:48 ml: (put comments based on the discussion) 13:27:13 -> https://github.com/w3c/wot-usecases/pull/193#issuecomment-1339389611 Lagally's comments 13:27:24 subtopic: PR 196 13:27:50 -> https://github.com/w3c/wot-usecases/pull/196 PR 196 - Update README-coverage.md 13:28:02 ml: (goes through the proposed changes) 13:28:14 ... (fixing typos) 13:29:00 ... now would suggest we merge this PR 13:30:24 ... should we assign spec Editors for the assessment of use case coverage? 13:30:29 q| 13:30:32 s/q|// 13:30:33 q+ 13:30:59 mm: pretty clear we have to check the coverage itself 13:31:22 ... use case owners themselves also should see the coverage 13:31:53 kaz: yeah 13:32:26 ... would suggest we say "each spec TF and the use case generator should collaboratively work on the coverage check" 13:32:31 ml: ok 13:32:35 ... we can merge this PR itself 13:32:42 ... and then add further improvement 13:32:53 merged 13:33:24 ml: (adds some more improvement on the collaboration) 13:33:58 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/README-coverage.md updated README-coverage.md 13:34:17 subtopic: PR 197 13:34:39 -> https://github.com/w3c/wot-usecases/pull/197 PR 197 - Use case coverage review for TD and Binding 13:34:51 ml: (goes through the changes) 13:35:15 ... would suggest we merge this 13:38:03 -> https://github.com/w3c/wot-usecases/blob/531c20baa3c4ffebe8abbae1891b1e3b4bb71857/USE-CASES/coverage.csv rendered version of coverage.csv 13:38:22 mm: let's not think about the hierarchy style issue 13:38:28 ml: ok 13:40:05 mm: btw, I don't think the second problem since we've reorganized the retail use cases, etc. 13:40:47 merged 13:40:55 subtopic: PR 198 13:41:17 -> https://github.com/w3c/wot-usecases/pull/198 PR 198 - Update README.md to link to the latest published version. 13:42:20 merged 13:42:30 subtopic: PR 200 13:42:39 -> https://github.com/w3c/wot-usecases/pull/200 PR 200 13:42:53 s/PR 200/PR 200 - Add new use cases for smart agriculture-Milking/ 13:43:30 -> https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/200/e136245...mhchoi76:dbf425d.html#Automatic-milking-system diff - 2.1.4 Automatic milking system for dairy farm 13:43:37 ml: (goes through the diff) 13:48:28 mm: some concerns about security management 13:48:45 q+ 13:49:08 ... this is a good use case on edge computing 13:50:31 kaz: feel a bit odd to have only RFID as the technology to identify the cows 13:50:56 q+ 13:50:58 ... possibly QR codes, etc., or video recognition could be also applied 13:51:02 mm: right 13:51:11 ... potential improvement around that 13:51:13 ack k 13:52:00 mizu: is it necessary to distinguish the current Charter from the next Charter? 13:52:08 q+ 13:52:20 ... my point is that we're now at the end of the current Charter 13:52:36 ... so it would make more sense to include this use case for the next Charter 13:52:51 ml: that's true 13:53:20 ... but we could continue to update the use case document in parallel 13:53:22 mm: right 13:53:37 ... note the WoT Use Case document is an IG Note 13:53:54 q? 13:53:56 ack mi 13:53:58 ack mc 13:53:59 q+ 13:54:37 ack k 13:54:40 kaz: agree 13:55:02 ... we should be clear about which use cases from which use case document to be applied to which version of the WG specs 13:55:06 mm: right 13:55:29 ... and as we've been discussing, we should note potential improvements 13:55:35 ... e.g.: 13:55:39 ... security requirements 13:56:14 ... not only RFID tags but also other possible options like QR codes or bar codes 13:56:45 ... latency of the control systems for edge computing 13:57:05 ml: (adds those points to the comments for the PR 200) 13:57:38 mm: also we should have another use case call in 2 weeks 13:57:49 ... for that purpose, we should allocate a new WebEx for this slot 13:57:56 ... o Dec 20 13:58:02 s/ o / for / 13:58:06 kaz: will do 13:58:38 topic: Next call 13:59:08 ml: would talk about the coverage.csv 13:59:47 i|Next|-> https://github.com/w3c/wot-usecases/pull/200#issuecomment-1339429617 Lagally's comments| 14:00:04 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv coverage.csv 14:00:47 ml: we also have descriptions on the requirements as well 14:00:59 -> https://github.com/w3c/wot-usecases/tree/main/REQUIREMENTS REQUIREMENTS area 14:01:02 [adjourned 14:01:10 s/adjourned/adjourned]/ 14:01:17 rrsagent, make log public 14:01:21 rrsagent, draft minutes 14:01:21 I have made the request to generate https://www.w3.org/2022/12/06-wot-uc-minutes.html kaz 16:18:43 Zakim has left #wot-uc