14:01:50 RRSAgent has joined #wot-discovery 14:01:50 logging to https://www.w3.org/2022/04/04-wot-discovery-irc 14:02:01 ktoumura has joined #wot-discovery 14:02:16 meeting: WoT Discovery 14:02:39 present+ Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima 14:03:32 glomb has joined #wot-discovery 14:03:43 McCool has joined #wot-discovery 14:03:57 present+ Farshid_Tavakolizadeh 14:04:26 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#4_April_2022 14:05:22 acimmino has joined #wot-discovery 14:06:34 present+ Andrea_Cimmino 14:06:44 present+ Christian_Glomb 14:09:06 meeting starts reviewing the minutes 14:09:53 mccool: today we should discuss the implementation reports (discussed also last week) 14:10:28 mcool: kaz please edit the issue 291 for changing not* to note* 14:10:42 Topic: Minutes 14:11:02 s/Topic: Minutes/ 14:11:10 i/meeting starts/topic: Minutes/ 14:11:25 i|meeting starts|-> https://www.w3.org/2022/03/28-wot-discovery-minutes.html Mar-28| 14:11:47 mcool: add to issue 271 still under discussion 14:12:08 rrsagent, make log public 14:12:18 rrsagent, draft minutes 14:12:18 I have made the request to generate https://www.w3.org/2022/04/04-wot-discovery-minutes.html kaz 14:12:54 cris_ has joined #wot-discovery 14:13:05 present+ Cristiano_Aguzzi 14:14:13 zakim, who is on the call? 14:14:13 Present: Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima, Farshid_Tavakolizadeh, Andrea_Cimmino, Christian_Glomb, Cristiano_Aguzzi 14:16:00 acimmino_ has joined #wot-discovery 14:17:11 scribenick: kaz 14:17:18 topic: PRs 14:17:29 mm: 2 PRs there 14:17:45 subtopic: PR 295 14:18:02 -> https://github.com/w3c/wot-discovery/pull/295 PR 295 - Make Security and Privacy Considerations Normative 14:18:12 mm: discussed this during the security call 14:18:42 ... appropriate to give one more week for review 14:18:56 ... would be good if you all could review it too 14:19:46 -> https://pr-preview.s3.amazonaws.com/w3c/wot-discovery/295/12e8d17...mmccool:6e15dcd.html#security-consideration-dos diff - 8.1 Denial of Service 14:20:41 kaz: should the "should" within section 8.1 also be an assertion? 14:21:00 mm: there is a comment, and we're removing it 14:21:17 ... need more work on this 14:21:34 -> https://github.com/w3c/wot-discovery/pull/295#issuecomment-1087515084 McCool's comment 2-h ago 14:22:03 mm: (then goes through the other sections) 14:22:26 ... 8.2, 8.3, ... 14:22:33 ... 9. Privacy Considerations 14:22:45 ... 9.1 Location Tracking 14:23:21 ... section "10. Performance Considerations" is non-normative 14:23:23 q? 14:23:43 ft: easily testable 14:24:19 mm: similar issue with TD 14:24:34 ... section "11. Directory Service API Specification (Thing Model)" 14:24:42 ft: can move it 14:25:21 mm: putting it to the Appendix may make sense 14:26:21 ... we have another section for "Directory Service API" 14:26:36 ft: maybe we should shorten it a bit? 14:27:15 mm: probably we should have a section on Thing Model here (around Directory Service API) 14:27:21 ... but should not repeat it 14:27:47 -> https://github.com/w3c/wot-discovery/issues/294 related issue 294 - Move up Thing Model above Considerations sections #294 14:28:06 mm: agreed to move the section up 14:28:41 ... putting it as a subsection under the "Directory Service API" section 14:29:20 ... Farshid, do you want to work on a PR? 14:29:23 ft: yes 14:30:16 mm: investigate wether we can make it colapsable 14:30:18 q+ 14:31:05 kaz: do you mean some of the example (ex. 4, etc.) withing the TD spec? 14:31:09 mm: yeah 14:31:11 ack k 14:32:01 ...two versions: a hyperlink and inline text for the TM with a checkbox saying "show TM inline) 14:32:13 ... don't hae to worry about that right now 14:32:33 -> https://github.com/w3c/wot-discovery/issues/294#issuecomment-1087632190 McCool's comment on that 14:32:46 topic: Use Case Review 14:33:05 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv Use Case coverage 14:33:46 mm: the trouble is that it's a bit unclear how to describe it 14:34:53 ... need to see the gaps between the requirements from the use cases and the current specs 14:35:00 ... would be useful as the input for the next Charter period 14:35:08 q+ 14:35:38 ... another question is that there are two kinds of use cases 14:36:08 ... industry-specific ones and more vague/generic ones 14:37:17 kaz: some discussion during the Scripting call as well 14:37:37 ... suggested we have some more discussion with Lagally about what/how to do about this 14:37:46 ... e.g., during the Editors call and the Use Cases call 14:37:51 mm: right 14:38:05 ... was there a GitHub issue about this yet? 14:38:18 ack k 14:39:05 https://github.com/w3c/wot-scripting-api/issues/392 14:39:26 i/392/ca: there is an issue for Scripting/ 14:39:44 mm: we can create another issue for Discovery 14:41:43 -> https://github.com/w3c/wot-discovery/issues/296 Issue 296 - Clarify Expectations for Coverage Table 14:43:46 s|-> https://github.com/w3c/wot-discovery/issues/296 Issue 296 - Clarify Expectations for Coverage Table|| 14:44:11 -> https://github.com/w3c/wot-usecases/issues/189 wot-usecases issue 189 - Clarify Expectations for Coverage Table 14:45:23 mm: would be better to have a table of requirements rather than a table of use cases 14:47:01 ... (adds comments to the issue 189) 14:50:21 ... (shows an example of table of requirements) 14:52:06 -> https://www.w3.org/TR/2021/WD-naur-20211012/ example of "Natural Language Interface Accessibility User Requirements" 14:53:14 i|shows|-> https://github.com/w3c/wot-usecases/issues/189#issuecomment-1087655904 McCool's comments| 14:54:58 i|example of|-> https://github.com/w3c/edge-computing-web-exploration example of "For an example of how we could organize this, see Edge Computing Use Case and Requirements analysis"| 14:55:18 s/For an example of how we could organize this, see // 14:55:30 s/example of "N/another example of "N/ 14:56:06 topic: wide reviews 14:56:12 https://github.com/w3c/wot-discovery/issues/280 14:56:28 need to turn this into an MD file 14:56:32 s/https/-> https/ 14:56:45 s/280/280 Issue 280 - Capture Answers to Internationalization Questionnaire/ 14:57:15 next time, want to prep issues and PRs for wide review process, also for security etc. 14:57:15 mm: checkboxes to see the progress for Internationalization review 14:57:28 s/mm: checkboxes to see the progress for Internationalization review// 14:57:44 i/next/mm: checkboxes to see the progress for Internationalization review/ 14:57:53 topic: Testing 14:58:08 cg: question about testing 14:59:28 -> https://github.com/w3c/wot-testing/blob/main/plan/testing_2022.md testing plan 14:59:40 mm: Testing plan 2022 above 14:59:54 ... Farshid, can you add links for tooling? 15:00:19 ft: there is another page named "wot-discovery-testing" within my repo 15:02:34 mm: (adds links) 15:03:04 -> https://github.com/w3c/wot-testing/blob/main/plan/testing_2022.md#discovery-10-1 "Discovery 1.0" section updated with links for testing tools 15:03:08 [adjourned] 15:03:11 rrsagent, make log public 15:03:15 rrsagent, draft minutes 15:03:15 I have made the request to generate https://www.w3.org/2022/04/04-wot-discovery-minutes.html kaz 17:07:02 JKRhb has joined #wot-discovery 18:12:02 Zakim has left #wot-discovery 19:30:49 JKRhb has joined #wot-discovery 19:46:27 JKRhb has joined #wot-discovery 23:12:56 JKRhb has joined #wot-discovery