14:00:55 RRSAgent has joined #wot-discovery 14:00:59 logging to https://www.w3.org/2023/03/27-wot-discovery-irc 14:00:59 meeting: WoT Discovery 14:01:04 McCool has joined #wot-discovery 14:01:09 chair: McCool 14:01:44 present+ Kaz_Ashimura, Andrea_Cimmino, Michael_McCool 14:04:13 Mizushima has joined #wot-discovery 14:05:13 present+ Tomoaki_Mizushima 14:05:19 q+ 14:05:33 ack k 14:08:09 present+ Jan_Romann 14:08:13 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#27_March_2023 14:09:55 topic: Minute 14:09:59 s/Minute/Minutes/ 14:10:09 -> https://www.w3.org/2023/03/20-wot-discovery-minutes.html Mar-20 14:10:54 JKRhb has joined #wot-discovery 14:10:59 approved 14:11:01 topic: PRs 14:11:10 scribenick: JKRhb 14:11:30 https://github.com/w3c/wot-discovery/labels/resolve%20by%20PR 14:11:43 https://github.com/w3c/wot-discovery/labels/Testing 14:11:54 mm: So we have two labels, "Resolve by PR" and "Testing", need to check that we have not missed any issues 14:12:38 ... "Resolve by PR" issues might also be resolved early (in a "won't fix" manner) 14:12:57 ... does somebody here volunteer to address some of these issues? 14:13:26 ac: I can deal with some of the technical(?) issues 14:14:00 mm: Regarding SSE (issue 417), I am not sure what the current problem/state was 14:14:24 ... is referring to the Events API 14:14:41 ... one issue here is that we did not mark SSE as being as risk 14:14:50 ... even though we said so in the issue itself 14:15:11 ... things like the diff query assertion are minor 14:15:36 ... other assertions are not at risk, we have implementations, so we do not need to mark the whole feature as at-risk 14:16:22 ... some of the assertions might not need to be MUSTs in environments like LANs, so we might need to revisit these later 14:16:46 ... (adds a comment to the issue) 14:17:26 ... one thing we can do is moving this to Discovery 2.0 and then discuss alternative mechanisms such as WebHooks 14:18:18 rrsagent, make log public 14:18:21 rrsagent ,draft minutes 14:18:23 https://github.com/w3c/wot-discovery/issues/417#top 14:18:51 ... I will close this issue with comment and then create a new one regarding a scalable event mechanism 14:19:04 rrsagent, draft minutes 14:19:05 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:19:48 i|issue 417|subtopic: Issue 417| 14:20:15 ... (creates issue 468) 14:20:17 https://github.com/w3c/wot-discovery/issues/468 14:20:23 i|issue 417|-> https://github.com/w3c/wot-discovery/issues/417 Issue 417 - Should we make SSE informative?| 14:20:26 rrsagent, draft minutes 14:20:28 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:20:45 ... 417 has been linked automatically to this new issue 14:21:04 s/417 has been/issue 417 has been/ 14:21:30 mm: Now let's get back to other "Resolve by PR" issues 14:21:43 subtopic: Issue 64 14:22:11 mm: XPath is still not a normative specification, so we can also label this issue as "informative" 14:22:16 ... (adds the label) 14:22:49 ... one thing we could do here is defer it to Discovery 2.0 14:22:59 ... when XPath could become normative 14:23:10 ... a bit unclear what to do here 14:23:29 rrsagent, draft minutes 14:23:30 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:23:36 ... does anyone want to volunteer to work on XPath? 14:24:06 No response to the question. 14:24:14 subtopic: Issue 91 14:24:47 mm: This issue is dealing with the "relationship of discovery to lifecycle" 14:25:02 ... reading through this, I essentially proposed doing nothing 14:25:14 ... it's clear that discovery is not the same as onboarding 14:25:26 ... should therefore be informative or moved to Architecture 14:25:39 ... would rather say nothing than saying something wrong 14:25:46 ... does anyone feel different? 14:25:56 ... I would propose deferring this to Discovery 2.0 14:26:29 ... (adds a comment and the respective label, removes the "Resolve by PR" label) 14:26:43 subtopic: Issue 69 14:26:56 mm: This issue is about sequence diagrams 14:27:01 ... I guess I can do that myself 14:27:09 s|rrsagent ,draft minutes|| 14:27:11 subtopic: Issue 439 14:27:11 rrsagent, draft minutes 14:27:13 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:27:34 mm: So we essentially made an assessment, is an ongoing process 14:27:42 ... filled out the blanks in the tabl 14:27:51 ... can be considered done 14:28:03 i|XPath is still|-> https://github.com/w3c/wot-discovery/issues/64 Issue 64 - XPath queries of vocabulary using namespaces| 14:28:05 rrsagent, draft minutes 14:28:06 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:28:26 s/tabl/table/ 14:28:40 ... (adds a comment) 14:28:44 https://github.com/w3c/wot-discovery/issues/439#top 14:28:48 ... any objections to closing this issue? 14:28:59 ... hearing no objections, closing it 14:29:48 i|So we ess|-> https://github.com/w3c/wot-discovery/issues/439 Issue 439 - Use Case due diligence| 14:29:50 rrsagent, draft minutes 14:29:51 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:30:28 subtopic: Issue 466 14:31:59 jr: Is about the assertion regarding the mitigation of Denial of Service Attacks in the context of CoAP. I think the wrong document is cited. It is at risk anyway, though 14:32:58 mm: We could make a PR and make the statement informative 14:33:33 ... we are allowed to drop assertions and turn them into informative statements 14:34:11 jr: Citation should be adjusted, RFC 9175 instead of an Internet-Draft by the IRTF is cited 14:35:10 mm: (adds a comment with a proposal for a reformulation) 14:35:36 jr: I can volunteer to do a PR 14:35:52 mm: (assigns Jan to the issue) 14:36:06 subtopic: Issue 465 14:37:02 mm: Also opened by Jan 14:38:18 jr: Deals with the issue that you have to define a contentType in the response objects 14:39:15 mm: Since the content of the response is empty, the contentType does not really matter 14:39:59 ... need to add an informative note, since the issue in the TD repository is marked as "Defer to 2.0" 14:40:18 ... (adds a comment with a proposal) 14:41:01 rrsagent, draft minutes 14:41:32 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:41:38 ... application/octec-stream can be used as a fallback 14:41:38 i|This issue is dea|-> https://github.com/w3c/wot-discovery/issues/91 Issue 91 - Clarify relationship of discovery to lifecycle| 14:41:40 jr: I can do a PR 14:42:05 mm: Just make it an informative statement, not an Editor's Note 14:42:08 i|This issue is a|-> https://github.com/w3c/wot-discovery/issues/69 Issue 69 - Add sequence diagrams| 14:42:11 rrsagent, draft minutes 14:42:12 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:42:26 ... (adds a new label "Resolution Proposed") 14:43:02 i|Is about the a|-> https://github.com/w3c/wot-discovery/issues/466 Issue 466 - Removing the RFC 9175 assertion?| 14:43:10 ... (also adds the label to previously discussed issues) 14:43:31 subtopic: Issue 463 14:43:45 i|Also opened by Jan|-> https://github.com/w3c/wot-discovery/issues/465 Issue 465 - TDD Thing Model is missing contentType in response objects| 14:43:47 mm: We never finalized the discussion regarding @context URLs 14:43:58 ... there is a PR against the DID repo 14:44:22 ... where a @context URL with a year is used 14:44:52 ... with /did at the end and discovery inbetween 14:45:04 ... therefore there is the discussion to use an "ns" URL instead 14:45:38 ... the TD specification also uses a year in its @context URL 14:46:41 ... is anyone aware of any kind discussion regarding namespaces in the context of the TD specification? 14:46:56 ... (searches the TD issue tracker) 14:47:44 ... (does not find a related issue) 14:47:58 ... seems as if changing the namespace has not been considered so far 14:48:12 ... the PR in the DID repo has not been merged yet 14:48:20 i|We never fina|-> https://github.com/w3c/wot-discovery/issues/463 Issue 463 - Align Context URLs with TD specification| 14:48:23 rrsagent, draft minutes 14:48:24 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 14:48:36 ... they are waiting for us to have a deferenceable URL in the PR before merging it 14:48:43 ... so we can still update it 14:49:22 ... there is also Issue 148 which is fixing it and also uses "ns" 14:49:58 ... let's see if we can make a decision here 14:50:20 ... (adds a comment to Issue 463) 14:52:10 ... I propose using also a different namespace for the TDD vocabulary to avoid having problems 14:52:41 rrsagent, draft minutes 14:52:42 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html JKRhb 14:53:27 s/topic: PRs/topic: Issues/ 14:53:32 rrsagent, draft minutes 14:53:33 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html JKRhb 14:54:26 mm: As a resolution, I propose using 2022 in the namespace 14:54:44 ... is a normative change, but should be editorial 14:54:59 ... however, implementations need to be updated 14:55:20 ... in order to re-validate the assertions 14:55:39 ... I will do a PR 14:58:23 ... does someone want to help with the ontology file? 14:59:00 ... will not change anything just yet, will wait for feedback 14:59:02 -> https://github.com/w3c/wot-discovery/issues/463#issuecomment-1485272509 McCool's comments 14:59:18 topic: Dev Meeting Preparation 14:59:26 mm: We made some preparations 14:59:38 ... prepared slides walking through assertions 14:59:43 i|We made|-> https://docs.google.com/presentation/d/1OZeLR0-qAw01R1UloTG25xQjc5LFuwvRP9o50QVo660/edit?usp=sharing Slides on TD| 14:59:43 ... meeting on the 30th 15:00:05 i|We made|-> https://docs.google.com/presentation/d/16Ow5rPjnojdl693pqkOhoc5bNCBIMOYZvJQC9wHZGsk/edit?usp=sharing Slides on Architecture| 15:00:22 ... TD slides are done, currently preparing Architecture 15:00:31 ... should do something similar for Discovery 15:00:37 ... I can do a first draft 15:00:53 ... currently waiting for stabilization of the opening sections 15:01:03 ... then I can create something similar for Discovery 15:01:20 ... I put the references in the Wiki, you can have a look through them 15:01:33 [adjourned] 15:01:47 rrsagent, draft minutes 15:01:49 I have made the request to generate https://www.w3.org/2023/03/27-wot-discovery-minutes.html kaz 16:31:38 Zakim has left #wot-discovery