14:05:38 RRSAgent has joined #wot-discovery 14:05:38 logging to https://www.w3.org/2022/03/21-wot-discovery-irc 14:05:45 meeting: WoT Discovery 14:06:11 present+ Kaz_Ashimura, Michael_McCool, Farshid_Tavakolizadeh, Kunihiko_Toumura, Tomoaki_Mizushima 14:06:19 https://www.w3.org/2022/03/14-wot-discovery-minutes.html 14:09:16 i/html/topic: Minutes/ 14:09:20 (typos fixed) 14:09:32 rrsagent, make log public 14:09:37 rrsagent, draft minutes 14:09:37 I have made the request to generate https://www.w3.org/2022/03/21-wot-discovery-minutes.html kaz 14:11:26 topic: PRs 14:11:38 subtopic: PR 287 14:12:04 -> https://github.com/w3c/wot-discovery/pull/287 PR 287 - Cleanup of Security Considerations 14:12:40 mm: (goes through the changes) 14:12:57 ... we have location tracking 14:13:12 ... added anonymous TDs 14:13:33 ... any problem with this wording? 14:13:38 ft: this look ok 14:14:58 mm: (adds tweaks to "Mitigations") 14:15:49 (merged) 14:16:15 subtopic: PR 286 14:16:28 JKRhb has joined #wot-discovery 14:16:31 -> https://github.com/w3c/wot-discovery/pull/286 PR 286 - Add Amplification DDOS Security Consideration and Mitigations 14:16:38 zakim, who is on the call? 14:16:38 Present: Kaz_Ashimura, Michael_McCool, Farshid_Tavakolizadeh, Kunihiko_Toumura, Tomoaki_Mizushima 14:16:48 present+ Jan_Romann 14:17:10 mm: (goes through the changes) 14:17:26 s/look ok/looks ok (some comments on Mitigations) 14:18:25 ... (discussion on "Mitigations" for "Amplification and Distributed Denial of Service") 14:18:46 ... how many URLs for TDs to be obtained? 14:19:32 ... would let you guys review this PR a bit more 14:19:45 ... Jiye is on vacation and also to review this 14:20:07 subtopic: PR 290 14:20:21 -> https://github.com/w3c/wot-discovery/pull/290 PR 290 - Refactor directory API assertion IDs 14:20:35 mm: did you change anything, Farshid? 14:21:02 ft: one more assertion D for tdd-serach-sparql-federation-version 14:21:09 mm: ok 14:21:22 ... we need to update the testing files too 14:21:39 ... a bit annoying but need to fix it 14:21:50 ft: I can also do that 14:22:37 ... another update is about "tdd-thigs-..." instead of "tdd-reg-create-..." 14:23:09 ... btw would be better to use "unified view" for the diff 14:23:20 mm: (changes the diff setting to "unified") 14:24:11 subtopic: PR 288 14:24:27 -> https://github.com/w3c/wot-discovery/pull/288 PR 288 - WIP: Implementation Report 14:25:10 mm: my tool expects having 3 fields, ID, status and details 14:25:43 ... would suggest we merge this PR 14:25:54 ... who would work for Hitachi? 14:26:10 kt: currently all the results are "null" 14:26:34 mm: ok, we don't worry about Hitachi's results then 14:26:53 ft: "null" and "not implementation" are same for the tool 14:27:30 ... if some feature is not implemented, it would be a fail 14:27:41 zakim, who is on the call? 14:27:41 Present: Kaz_Ashimura, Michael_McCool, Farshid_Tavakolizadeh, Kunihiko_Toumura, Tomoaki_Mizushima, Jan_Romann 14:28:11 mm: the reason to have "null" is for templating for further edit later 14:28:23 ... same thing as omitted 14:28:49 ... in the test results, you can create a directory 14:29:04 ... separate file for manual testing 14:29:13 ... anyway, let's merge this as the starting point 14:30:20 ft: btw, does everyone use LinkSmart as the reference? 14:30:22 mm: no 14:32:10 ... (visits 2022.03.Online/Discovery/Results to show an example) 14:32:26 -> https://github.com/w3c/wot-testing/tree/main/events/2022.03.Online/Discovery/Results 2022.03.Online/Discovery/Results 14:32:56 (PR 290 merged) 14:33:32 rrsagent, make log public 14:33:36 rrsagent, draft minutes 14:33:36 I have made the request to generate https://www.w3.org/2022/03/21-wot-discovery-minutes.html kaz 14:34:11 topic: Updated implementation report 14:34:23 mm: (shows the updated implementation report on his PC) 14:35:42 ... some of the manual assertions to be added 14:37:02 ... the problem here is 14:37:19 ... would be too strong to require "MUST" for tdd-validation-result 14:37:31 ... probably should be "SHOULD" 14:37:52 ... also 14:38:12 ... "necessary details" required is too much 14:38:36 ft: need another assertion to describe what is needed then? 14:38:55 q+ 14:39:11 FarshidT has joined #wot-discovery 14:39:13 https://w3c.github.io/wot-discovery/#validation 14:41:18 ft: "7.2.2.1.6 Validation" above 14:41:54 mm: it's funny to have an assertion on SPARQL though it's informative 14:42:31 ft: it's optional but normative 14:42:33 mm: ok 14:43:09 ... the question is who would be the client? 14:43:23 ... Web browsers? or IoT devices? 14:43:34 ft: do we need two clients? 14:43:39 mm: think so 14:44:30 ft: we have to implement most of the things from scratch 14:44:52 mm: right 14:45:14 ... anyway, if you think we need further issues, please create GitHub Issues 14:45:46 ft: Andrea will implement it at least 14:45:54 LinkSmart has it too 14:46:18 kaz: which specific feature are we talking about? 14:46:35 mm: discovery features in general 14:46:57 ... would leave them "work-in-progress" 14:47:28 subtopic: PR 292 14:47:41 -> https://github.com/w3c/wot-discovery/pull/292 PR 292 - PR for adding assertion of discovery @context 14:48:09 mm: should we allocate the context URL? 14:48:20 https://w3c.github.io/wot-discovery/context/discovery-context.jsonld 14:48:29 q+ 14:48:40 mm: I'm OK with merging this 14:49:37 ft: currently we're trying to allocate a new URL 14:51:44 (some more discussion) 14:53:10 kaz: note that "www.w3.org/ns/td" is obsolete and we are now using "www.w3.org/2022/wot/td/v1.1" for TD 14:53:29 ... so we could use "www.w3.org/2022/wot/discovery" for WoT Discovery 14:54:00 https://github.com/w3c/wot-discovery/issues/148 14:58:23 subtopic: PR 291 14:59:01 i/291/Issues/ 14:59:08 s/PR 291/Issue 291/ 14:59:24 -> https://github.com/w3c/wot-discovery/issues/291 Issue 291 - Needed new assertion for discovery @context 14:59:54 mm: (leaves a comment) 15:00:00 -> https://github.com/w3c/wot-discovery/issues/291#issuecomment-1074005460 McCool's comment 15:00:57 [[ 15:00:58 We need a temp URL for testing/tooling/validation purposes 15:00:58 Third style is probably better (IMO) - using explicit tdd prefix 15:00:58 Base context URL in these examples need to be updated, and there is a namespace already allocated 15:00:58 We could automatically include the tdd context in the td1.1 (similar to how htv is included...), but for td1.0 it will have to be explicitly included (e.g. MAY/SHOULD) - use of tdd prefix is not not mandatory, but RECOMMENDED 15:01:00 "Expanded" names ok (MAY), but only if base URL is consistent with standard context URL for the tdd 15:01:02 ]] 15:01:04 mm: aob? 15:01:08 (none) 15:01:10 [adjourned] 15:01:20 rrsagent, draft minutes 15:01:20 I have made the request to generate https://www.w3.org/2022/03/21-wot-discovery-minutes.html kaz 15:02:46 chair: McCool 15:02:47 rrsagent, draft minutes 15:02:47 I have made the request to generate https://www.w3.org/2022/03/21-wot-discovery-minutes.html kaz 15:03:08 i/subtopic: PR 292/ 15:03:20 i/subtopic: PR 292/topic: PRs - revisited/ 15:03:22 rrsagent, draft minutes 15:03:22 I have made the request to generate https://www.w3.org/2022/03/21-wot-discovery-minutes.html kaz