15:00:15 RRSAgent has joined #wot-discovery 15:00:19 logging to https://www.w3.org/2023/03/06-wot-discovery-irc 15:00:21 meeting: WoT Discovery 15:00:33 Mizushima has joined #wot-discovery 15:00:52 present+ Kaz_Ashimura, Michael_McCool 15:00:55 acimmino has joined #wot-discovery 15:00:55 chair: McCool 15:03:23 JKRhb has joined #wot-discovery 15:03:36 present+ Andrea_Cimmino, Jan_Romann, Tomoaki_Mizushima 15:03:46 present+ Kunihiko_Toumura 15:03:49 ktoumura has joined #wot-discovery 15:05:51 q+ 15:05:58 scribenick: JKRhb 15:06:06 ack k 15:06:26 McCool_ has joined #wot-discovery 15:06:34 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#6_March_2023 15:06:37 topic: Minutes Review 15:07:12 mm: It's been a while due to all of the charter discussions. Let's read the minutes carefully 15:07:25 ... some typos, but I am not too worried of them 15:08:25 ... (marks a comment by Kaz) Is that actually reflecting what you said? 15:08:35 kaz: I updated the comment offline 15:09:18 mm: We should have a look on the "Propose Closing" issues today 15:09:25 ... (updated the Agenda) 15:09:44 ... minutes look okay, only a few typos, but let's publish the minutes as they are 15:09:48 ... any objections? 15:10:03 No objections, minutes are published 15:10:08 topic: Issues 15:10:23 subtopic: Issues marked as "Propose Closing" 15:10:47 mm: We have a lot of open issues, some of which are labelled Propose Closing 15:11:12 ... I would simply close them in bulk, if someone disagrees, they can reopen them 15:11:34 ft: I think we should rather go through them one by one 15:12:09 ... for example, the issue about the diff parameter could be postponed 15:12:28 ... however, I added the label myself, so it can probably be closed 15:13:07 mm: I would simply close them, they could be reopened if needed 15:13:11 ... will do it offline 15:13:16 subtopic: Issue #462 15:13:36 rrsagent, make log public 15:13:41 rrsagent, draft minutes 15:13:42 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:13:49 mm: This PR has not been merged yet, but we got feedback by PLH 15:13:54 ... still some work to do regarding URLs 15:14:03 ... and updates to changelog 15:14:13 ... port discussion in the PR was resolved 15:15:06 ... comment by Manu Sporny needs to be addressed. Will create an issue for deciding on the URL and some additional points that need to be clarified, but will merge it as is 15:15:20 ... does anyone feel the need to edit this PR before it is merged? 15:15:40 ... this resolves the DNS-SD stuff and makes progress regarding DID 15:15:59 i|We have a lot|-> https://github.com/w3c/wot-discovery/issues?q=is%3Aissue+is%3Aopen+label%3A%22Propose+Closing%22 Issues with "Propose Closing" label| 15:16:00 ... in any case, I can merge it and apply additional fixes afterwards 15:16:02 rrsagent, draft minutes 15:16:04 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:16:31 ... I am not hearing anyone's opinion, so I will first create the issue 15:16:53 ... (creates an issue regarding outstanding DID fixes) 15:19:16 ktoumura has joined #wot-discovery 15:19:47 i|This PR has not|-> https://github.com/w3c/wot-discovery/pull/462 PR 462 - CR Update - DID and DNS-SD fixes| 15:19:52 mm: So, we do not need to refer to the DID ontology in my opinion. We should follow up on this discussion and go ahead with the PR for now. 15:20:23 s/Issue #462/PR 462/ 15:21:41 s/topic: Issues/topic: Issus and PRs/ 15:21:49 rrsagent, draft minutes 15:21:51 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:22:19 ... (moves the issue from the wot repository, where it was accidentally created, to the wot-discovery repository) 15:22:57 ... changes are to the top-level index.html file, so we need to update the CR candidate at some point 15:23:07 ... (merges the PR) 15:23:41 i|moves the|-> https://github.com/w3c/wot-discovery/issues/467 wot-discovery issue 467 (transferred from the wot repo)| 15:23:43 rrsagent, draft minutes 15:23:44 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:24:20 https://github.com/w3c/wot-discovery/pull/462 merged 15:25:17 rrsagent, draft minutes 15:25:19 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:25:51 mm: Regarding the outstanding issues, we should go through them and figure out whether they need to be resolved by PR or deferred 15:25:56 FarshidT has joined #wot-discovery 15:26:14 https://github.com/w3c/wot-discovery/issues/234 15:26:21 https://github.com/w3c/wot-discovery/issues/129 15:26:25 ... we probably have about 60 issues still open 15:26:42 present+ Farshid_Tavakolizadeh 15:27:00 ft: The JSON path issues marked as "Propose Closing" should be kept open 15:27:10 mm: Oh, yes, that was a mistake 15:27:32 ... or we can only leave one open 15:28:07 rrsagent, draft minutes 15:28:08 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:28:49 i|Regarding the outs|subtopic: Other issues| 15:28:51 rrsagent, draft minutes 15:28:52 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:29:13 ... we should have a look at the latest IETF draft for JSON Path, maybe we can use it, but we should leave it open when it comes to the new charter 15:30:13 mm: We can close Issue 129 and will continue the discussion in Issue 234 15:31:11 ... and remove the Consolidation label from that issue 15:31:26 s|https://github.com/w3c/wot-discovery/issues/234|-> https://github.com/w3c/wot-discovery/issues/234 Issue 234 - JSONPath as a search query language| 15:31:48 ... we should probably go through the issues and see which ones can be marked as deferred or Resolve by PR 15:32:04 subtopic: Issue 466 15:32:13 s|https://github.com/w3c/wot-discovery/issues/129|-> https://github.com/w3c/wot-discovery/issues/129 Issue 129 - Review IETF JSON Path draft| 15:32:14 rrsagent, draft minutes 15:32:15 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:32:48 -> https://github.com/w3c/wot-discovery/issues/466 Issue 466 - Removing the RFC 9175 assertion? 15:32:52 rrsagent, draft minutes 15:32:53 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:34:32 mm: Is about the multicast DDoS CoAP assertion, that will probably go away anyway since it is marked as "At Risk" 15:35:56 subtopic: Issue 465 15:36:41 q+ 15:37:22 jr: Thing Model API description has the problem of not defining a contentType for all response objects in forms 15:37:45 ... leading to invalid TDs if instantiated as is 15:38:12 ... proposed a workaround, also raised the issue in TD repository 15:38:49 i|Thing Model|-> https://github.com/w3c/wot-discovery/issues/465 Issue 465 - TDD Thing Model is missing contentType in response objects| 15:38:59 mm: Could be fixed by an informative statement or the workaround you proposed 15:39:37 s/you proposed/Jan proposed/ 15:39:56 ack k 15:40:10 ... needs a longterm fix, probably in the TD spec 15:40:25 subtopic: Issue 464 15:40:42 -> https://github.com/w3c/wot-discovery/issues/464 Issue 464 - How to keep Thing Descriptions updated in a Directory 15:40:53 mm: Issue raised by Ben Francis 15:41:03 ft: Can be marked as a question 15:41:43 ... asks why there is no standard way of keeping Thing Descriptions updated 15:42:11 mm: (Adds a comment that this would be good to be clarified) 15:42:18 subtopic: Issue 463 15:42:34 mm: Is related to 464 15:42:39 ... (adds a comment) 15:42:46 subtopic: Issue 458 15:43:01 mm: I think we should close this issue and move it to the charter discussion 15:43:18 ... will mark it as "Propose Closing" and close it in the next round of things 15:43:37 subtopic: Issue 448 15:43:45 mm: We may have already fixed this issue 15:43:57 ... I think the PR I just merged has fixed this 15:44:16 i|We may|-> https://github.com/w3c/wot-discovery/issues/448 Issue 448 - Assertion for DNS referencing UDP may be split normative/informative| 15:44:25 ... can leave the "Resolve by PR" label and leave it as is for now 15:44:31 subtopic: Issue 445 15:44:50 mm: I think this is also "Resolve by PR", just cleans up the Implementation Report 15:45:45 subtopic: Issue 416 15:45:45 mm: This is related to testing, I will label this issue and similar ones as such 15:45:45 i|I think|-> https://github.com/w3c/wot-discovery/issues/445 Issue 445 - Implementation Report Fixes| 15:45:50 ... (applies the label to other issues as well) 15:46:10 i|This is related|-> https://github.com/w3c/wot-discovery/issues/416 Issue 416 - clean up logilab results| 15:46:34 ... (also applies the label "Resolve by PR to Issues 414 and 415) 15:46:42 s/"Resolve by PR/"Resolve by PR"/ 15:46:51 subtopic: Issue 413 15:47:07 mm: The description is a bit unclear, not sure what I wanted to do here 15:47:29 ... was probably more of an English thing or an editorial problem 15:47:37 subtopic: Issue 410 15:47:46 i|The description is|-> https://github.com/w3c/wot-discovery/issues/413 Issue 413 - Improve wording of tdd-absolute-time assertion| 15:47:46 mm: I think this one was also editorial 15:47:54 ... not sure if it is resolved yet 15:48:06 ... I think resolving by PR would be good, but it is not critical 15:48:16 i|I think this|-> https://github.com/w3c/wot-discovery/issues/410 Issue 410 - Use TDD consistently| 15:48:21 subtopic: Issue 333 15:48:34 mm: This is a weird one 15:48:39 ... which we should fix right now 15:49:27 i|This is a|-> https://github.com/w3c/wot-discovery/issues/333 Issue 333 - [repository] No link to the spec from the repository| 15:49:31 ... (sets the link to the rendered version of the specification as the repository's "homepage") 15:49:51 q+ 15:49:52 ... (adds a comment and closes the issue) 15:50:16 ... are you okay with closing? 15:50:29 ack k 15:50:45 kaz: @@@ 15:50:45 kaz: I agree with closing, and this is a question for the whole working group, of how to deal with the rendered HTML document 15:50:50 s/kaz: @@@// 15:51:00 mm: Okay, I am going to close it 15:51:08 Issue closed 15:51:36 subtopic: Issue 283 15:52:05 mm: This one is labelled "Resolve by CR", will mark it as "Resolve by PR" and add the testing label 15:52:14 subtopic: Issue 327 15:52:31 mm: Is this still an issue we need to worry about, Farshid? 15:52:50 ft: There were some use cases that were not included in the explainer 15:53:13 mm: I am more concerned about incorrect than missing correct statements 15:53:43 ft: I don't think there are any incorrect statements, but I will have another look. We don't need to add a label for the issue 15:53:56 subtopic: Issue 257 15:54:18 mm: This one is marked as "Resolve by CR" 15:54:33 ... I don't think we have any assertions about that 15:54:50 ... and I think that was our conclusion regarding this issue 15:55:08 ... and Ege agrees in an issue comment 15:55:29 ... I would propose deferring it, as we cannot add assertions at the moment 15:55:58 ... (adds a comment to the issue) 15:56:04 rrsagent, draft minutes 15:56:05 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 15:56:12 ... I think signing will impact this 15:56:18 ... once we support it 15:56:54 ... (removes existing labels and adds "defer to Discovery 2.0") 15:57:12 subtopic: Issue 239 15:57:27 mm: This one is just cleanup, so I will mark it as such 15:57:41 ... (adds the "Cleanup" label) 15:57:51 subtopic: Issue 224 15:57:58 mm: This one does not have an appropriate label 15:58:49 ft: I agree with Ben, the consumer can add the default, does not need to be done by the directory 15:59:17 ... could be added as part of the SPARQL DB (?) 16:00:21 ac: As an implementor, this @type is mainly necessary for the framing 16:00:44 i|This on is marked as|-> https://github.com/w3c/wot-discovery/issues/257 Issue 257 - What part of a TD can a TDD modify| 16:00:48 q+ 16:00:52 ... if the @type is missing, then we inject it, and store the fact that it has been injected privately 16:01:23 ... should be open to the implementors how to handle this 16:01:39 ... don't need to change the specification 16:01:45 rrsagent, draft minutes 16:01:47 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 16:02:06 mm: We need to clear about this in the next specification version, since it may affect signing 16:02:37 kaz: Maybe we can organize a W3C developer meetup to gather feedback before the next charter period 16:02:53 ack k 16:02:54 ... we need to identify what needs to be added separately 16:02:56 rrsagent, draft minutes 16:02:57 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 16:03:34 mm: We are out of time, we will continue next time, until then, please scan through the issues 16:03:47 [adjourned] 16:03:49 i|Is related to 464|-> https://github.com/w3c/wot-discovery/issues/463 Issue 463 - Align Context URLs with TD specification| 16:04:40 i|I think we should close this|-> https://github.com/w3c/wot-discovery/issues/458 Issue 458 - WG 2023 Charter - Update| 16:04:49 rrsagent, draft minutes 16:05:20 I have made the request to generate https://www.w3.org/2023/03/06-wot-discovery-minutes.html kaz 18:14:21 Zakim has left #wot-discovery