14:02:16 RRSAgent has joined #wot-discovery 14:02:16 logging to https://www.w3.org/2022/08/01-wot-discovery-irc 14:02:20 https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#1_August_2022 14:02:26 meeting: WoT Discovery 14:02:27 ktoumura has joined #wot-discovery 14:02:32 s/https/agenda: https/ 14:02:40 chair: mcCool 14:02:48 s/mcCool/McCool/ 14:02:50 glomb has joined #wot-discovery 14:03:16 present+ Kaz_Ashimura, Michael_McCool, Christian_Glomb, Farshid_Tavakolizadeh, Kunihiko_Toumura, Tomoaki_Mizushima 14:05:26 acimmino has joined #wot-discovery 14:06:54 -> https://www.w3.org/groups/wg/wot WoT WG page including "Join the group" 14:07:27 present+ Andrea_Cimmino 14:07:56 cris_ has joined #wot-discovery 14:08:11 present+ Cristiano_Aguzzi 14:08:43 scribenick: acimmino 14:09:56 meeting starts 14:09:59 Topic: reviewing minutes 14:11:02 Topic: PR review 14:11:11 subtopic: PR #383 14:12:06 link: https://github.com/w3c/wot-discovery/pull/383 14:12:15 dezell has joined #wot-discovery 14:12:28 present+ David_Ezell 14:12:42 FarshidT has joined #wot-discovery 14:12:46 the PR has no problems in theory but should resolve the IPR issue first 14:13:01 -> https://www.w3.org/groups/wg/wot WoT WG page including "Join the group" 14:14:06 https://labs.w3.org/repo-manager/pr/id/w3c/wot-discovery/383 14:14:48 s/link: h/-> h/ 14:15:16 s|pull/383|pull/383 PR 383 - Clarify Anonymous ID assignment and Location header| 14:15:51 i|PR review|-> https://www.w3.org/2022/07/18-wot-discovery-minutes.html July-18| 14:16:01 i|PR review|approved| 14:18:38 cristiano raises a question about issue #379 related to this PR. 14:18:45 regarding the value that Location heather may have 14:22:08 https://datatracker.ietf.org/doc/html/rfc8141#section-4.3 14:22:26 i|379|-> https://github.com/w3c/wot-discovery/issues/379 Issue 379 - Location must contain an URL| 14:25:34 zkis has joined #wot-discovery 14:26:19 q+ 14:28:50 finally, as conclusion, there is consensus on the fact that PR #383 improves the overall situation, nevertheless, some issues still remain to be solved 14:29:01 ack k 14:30:28 kaz: merging PR 383 itself is fine, and keeping Cristiano's issue 379 is also ok 14:31:59 s/also ok/also ok, but WoT mechanism is basically protocol-agnostic, so we should be careful how to describe the core WoT Discovery capability and how to map that with protocol-dependent features like HTTP's Location header./ 14:32:39 PR # 383 is merged 14:34:48 Next Topic: Tag Review 14:35:05 |Next Topic|-> Tag Review 14:35:34 mcoool: we got some feedback on this matter. We need to take care about references to other works and links 14:36:06 s/Next Topic: Tag/topic: TAG review/ 14:36:28 s/|Next Topic|-> Tag Review|// 14:36:36 rrsagent, make log public 14:36:42 rrsagent, draft minutes 14:36:42 I have made the request to generate https://www.w3.org/2022/08/01-wot-discovery-minutes.html kaz 14:37:21 mccool adds a note to the related work section indicating to see the WoT Discovery document for the links. 14:37:42 then a PR is created with the new Explainer.md 14:38:58 i|we got some|-> https://github.com/w3ctag/design-reviews/issues/733 design review issue 733 - Discovery, some small action items| 14:40:09 mccool answers the issue # 733 (https://github.com/w3ctag/design-reviews/issues/733) informing 14:42:23 Some references: https://www.sciencedirect.com/science/article/abs/pii/S2542660520301256?via%3Dihub and https://dl.acm.org/doi/10.1145/2991561.2991570 14:43:01 +1 for the links above. I used them too as good references 14:45:24 they are good refs 14:45:27 I also use them 14:50:46 s/Next Topic: Tag/topic: issues about testing report assertions 14:52:34 s|s/Next Topic: Tag/topic: issues about testing report assertions|| 14:52:46 topic: Issues about testing report assertions 14:53:07 (McCool describes the general issue related to the policy assertions) 14:55:21 acimmino_ has joined #wot-discovery 14:55:37 apologies, my laptop died 14:56:11 s/apologies, my laptop died// 14:56:40 mm: basically, would reword those policy assertions 14:57:25 (some more discussion) 14:57:36 mm: think there are possible three approaches 14:57:49 ... opt 1. changing the tools 14:58:06 ... opt 2. fixing the table within the implementation report 14:58:12 q+ 14:58:29 ... opt 3. @@@ 14:58:53 ... please note that the bigger issue is the features missing implementations within this result table 14:59:03 ... some of them are rather easy 14:59:18 ... but related to discoverer, etc. 15:00:02 s/@@@/edit the text to say we can't distinguish/ 15:00:14 present+ David_Ezell 15:00:15 ack k 15:00:25 present+ Christian_GLomb 15:00:31 s/GLom/Glom/ 15:00:33 q? 15:00:33 q? 15:01:11 kaz: just to make sure, please upload the latest implementation reports 15:01:14 mm: ok 15:01:18 [adjourned] 15:01:32 rrsagent, make log public 15:01:36 rrsagent, draft minutes 15:01:36 I have made the request to generate https://www.w3.org/2022/08/01-wot-discovery-minutes.html kaz 15:05:22 i/McCool describes/scribenick: kaz/ 15:05:23 rrsagent, draft minutes 15:05:23 I have made the request to generate https://www.w3.org/2022/08/01-wot-discovery-minutes.html kaz 16:00:03 benfrancis8 has joined #wot-discovery 16:30:21 benfrancis9 has joined #wot-discovery 16:36:46 benfrancis has joined #wot-discovery 16:49:44 benfrancis9 has joined #wot-discovery 17:00:48 benfrancis4 has joined #wot-discovery 17:06:09 benfrancis has joined #wot-discovery 17:11:58 benfrancis3 has joined #wot-discovery 17:35:04 benfrancis9 has joined #wot-discovery 18:03:16 Zakim has left #wot-discovery 18:42:42 benfrancis1 has joined #wot-discovery 18:58:17 benfrancis8 has joined #wot-discovery 19:00:20 JKRhb has joined #wot-discovery 20:30:49 benfrancis2 has joined #wot-discovery