14:00:03 RRSAgent has joined #wot-discovery 14:00:08 logging to https://www.w3.org/2023/05/22-wot-discovery-irc 14:00:48 McCool_ has joined #wot-discovery 14:00:53 meeting: WoT Discovery 14:01:04 present+ Kaz_Ashimura, Tomoaki_Mizushima 14:01:30 present+ Kunihiko_Toumura 14:01:39 present+ Farshid_Tavakolizadeh 14:02:00 ktoumura has joined #wot-discovery 14:04:00 present+ Michael_McCool 14:04:25 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#22_May_2023 14:05:06 FarshidT has joined #wot-discovery 14:06:47 q+ 14:06:57 topic: Minutes review 14:07:46 ack k 14:07:56 -> https://www.w3.org/2023/05/15-wot-discovery-minutes.html May-15 14:08:08 topic: PRs 14:08:25 mmc: some PRs will close some issues 14:09:35 subtopic: Resolve tdd-registrationinfo-expiry-config #482 14:09:38 https://github.com/w3c/wot-discovery/pull/482 14:10:29 mmc: commented out the markdown in case we wanna add it back and reuse the same ID 14:10:45 ... changed MAY to may 14:11:16 s/markdown/assertion markdown/ 14:11:29 acimmino has joined #wot-discovery 14:11:34 subtopic: Resolve tdd-http-alternate-language and tdd-validation-response-lang #483 14:11:38 https://github.com/w3c/wot-discovery/pull/483 14:12:34 present+ Jan_Romann, Andrea_Cimmino 14:14:58 [refer to PR description and new inline comments for details] 14:15:51 merged 14:16:06 subtopic: Resolve resolve-tdd-notification-data-diff-unsupported #484 14:16:10 https://github.com/w3c/wot-discovery/pull/484 14:19:26 mmc: accepted the suggestion on PR for simpler working 14:19:35 s/working/wording/ 14:19:38 merged 14:19:53 subtopic: Resolve exploration-secboot-oauth2-flows #485 14:20:13 JKRhb has joined #wot-discovery 14:20:20 rrsagent, draft minutes 14:20:21 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html JKRhb 14:20:34 rrsagent, make log public 14:26:09 mmc: it appears that the entire "MUST reply with an HTTP "401 (Unauthorized)" response code..." assertion was at risk. So we need to downgrade the whole assertion. 14:27:03 ... need to reword the PR 14:27:21 s/reword/rework/ 14:27:43 ... will close in favor of a new PR. 14:28:44 subtopic: Resolve security assertions #486 14:28:47 Sorry I can't join (noisy cafe), but surely, technically, as long as a server responded with either 401 response, or a 302/304 response, the assertion was satisfied? 14:30:09 (Never mind, I will follow up asynchronously) 14:30:57 https://github.com/w3c/wot-discovery/pull/486 14:31:36 mmc: We can't make the entire section informative (PR suggestion), because some of the assertions are not at risk. 14:35:04 subtopic: Resolve privacy assertions #487 14:35:08 https://github.com/w3c/wot-discovery/pull/487 14:37:08 mmc: some normative assertions but they were all at risk going into CR 14:38:56 ... making everything under the section as informative requires consensus 14:39:31 ft: better leave them mixed in as with the security considerations 14:40:18 subtopic: Resolve sort_by specification issue #488 14:40:22 https://github.com/w3c/wot-discovery/pull/488 14:44:22 mmc: we didn't specify the syntax for the sort_by 14:44:35 ... we also didn't specify what to do if the field is missing from the TD 14:46:08 ... it was at risk going to CR, so we can downgrade the whole assertion to an informative statement 14:47:32 ... and at the same time replace it with JSON Pointer. 14:54:29 ... Keeping the feature as informative is strange. Better take out the whole assertion and related ones. 14:56:23 ... there is one non-at-risk assertion but it depends on the at-risk ones. So, removing that too is justified. 14:59:40 ... This also affect the sort_order argument which is specified together with sort_by in the same at-risk assertion. 15:02:11 Need to also edit the Thing Model to drop sort_by and sort_order 15:07:32 ... as well as the example for HTTP error codes. 15:12:38 rrsagent, draft minutes 15:12:39 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:12:51 s/issue #488/PR #488/ 15:12:57 rrsagent, draft minutes 15:12:58 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:13:12 chair: McCool 15:13:27 subtopic: add reference to IoT'16 paper #489 15:13:34 https://github.com/w3c/wot-discovery/pull/489 15:13:40 s/Need to/... Need to/ 15:13:46 scribenick: JKRhb 15:13:46 scribenick: JKRhb 15:14:07 subtopic: PR 489 15:14:17 mm: This PR resolves Issue 147 15:14:33 ... by adding a paper mentioned in the issue 15:14:44 ... promised the authors to reference them 15:15:05 ... cited them in the examples section and added them to the Acknowledgements section 15:15:44 ... also need to finish the Acknowledgement section, mention all contributors, should be very mechanical based on the commit logs of the last two years 15:15:48 ... can also do it offline 15:15:57 ... any objection to merging this? 15:16:03 ... hearing no objection, merging 15:16:07 https://github.com/w3c/wot-discovery/pull/489 15:16:15 Merged 15:16:26 https://github.com/w3c/wot-discovery/issues/490 15:16:41 still need to finish the acknowledgement 15:16:42 mm: The issue about the Acknowledgments is #490, I will open another PR to resolve it 15:16:56 ... will resolve by the time of the final resolution 15:17:05 subtopic: PR 472 15:17:17 mm: This one also relates to an at-risk item 15:17:31 ... we agreed the assertion regarding UDP and TTDs was unresolvable 15:17:37 https://github.com/w3c/wot-discovery/pull/472/files 15:17:38 ... so we split up the table 15:18:01 rrsagent, draft minutes 15:18:03 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:18:18 ... I added a sentence saying that "this table is normative" and marked the TTD UDP assertion as "For future use" 15:18:28 ... as it is reserved, since it is registered with IANA 15:18:36 s|subtopic: PR 489|| 15:19:21 ... (explains the new table structure in the document) 15:19:26 ... any objections to merging? 15:19:36 No objections, merged 15:19:50 subtopic: PR 471 15:19:51 i|https://github.com/w3c/wot-discovery/issues/490|subtopic: Add Acknowledgements #490| 15:20:04 mm: We had this long discussion regarding context URLs 15:20:17 ... made a long list of changes 15:20:41 i|This one also relates|-> https://github.com/w3c/wot-discovery/pull/471 PR 471 - Update context URLs| 15:21:00 ... context URLs are now using the year 2022 and "-did" instead of "/did" 15:21:08 ... in order to avoid conflicts in the future 15:21:39 s|-> https://github.com/w3c/wot-discovery/pull/471 PR 471 - Update context URLs|-> https://github.com/w3c/wot-discovery/pull/472 PR 472 - Make DNS-SD service name for UDP TDD informative| 15:21:54 ... the context URL for directories is still using "/discovery" 15:22:05 ... also updated all of the examples 15:22:11 i|We had this|-> https://github.com/w3c/wot-discovery/pull/471 PR 471 - Update context URLs| 15:22:18 rrsagent, draft minutes 15:22:19 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:22:32 ft: I am wondering if you also removed all of the editors' notes? Since there were a couple that mentioned this 15:22:38 mm: Let me check 15:23:32 ... (finds that there still a number of Editor's notes regarding this issue, removes them) 15:24:19 ... one other note is commented out, I will leave that one alone 15:24:56 ... (finds a couple of other commented out notes, leaves them as they are) 15:26:24 ... (looks at the new state of the PR) 15:26:47 ... let's double check the rendering 15:28:39 ... URLs got changed, some whitespace changes, notes got taken out, pagination got also updated 15:28:50 ... I think we're good, any objection to merging? 15:28:58 ... (no objections, merged) 15:29:12 mm: I think that means we have no more PRs 15:29:17 topic: Issues 15:29:28 mm: Let's filter by "resolve by PR" 15:29:44 ... there is a distressingly large number left 15:29:56 ... but I guess that can also be interpreted as "defer" 15:30:03 https://github.com/w3c/wot-discovery/issues/187 15:30:06 subtopic: Issue 187 15:30:24 mm: This is about the registration with IANA 15:30:27 ... this is all done 15:30:35 ... (closes the issue) 15:30:43 subtopic: Issue 201 15:31:09 mm: This one, I did not get around to, I am not going to resolve it, so no sequence diagram 15:31:10 s|https://github.com/w3c/wot-discovery/issues/187|| 15:31:23 ... but I will simply mark it as "defer to discovery 2.0" 15:31:34 subtopic: Issue 402 15:31:41 mm: I think this one is also done 15:31:47 i|This is about|-> https://github.com/w3c/wot-discovery/issues/187 Issue 187 - Registration of Well-known URI, DNS-SD and DID Service Names, CoRE Resource Type| 15:31:57 ... the issue is that they haven't merged there PR yet since they need an ontology file 15:32:01 ... but I have created a PR 15:32:13 s/there/their/ 15:32:25 ... and updated it 15:32:26 i|This one,|-> https://github.com/w3c/wot-discovery/issues/201 Issue 201 - Sequence diagrams for DID based discovery approaches| 15:32:48 ... (adds a comment to the issue) 15:32:53 i|I think thi|-> https://github.com/w3c/wot-discovery/issues/402 Issue 402 - Register DID service names| 15:33:06 ... question is, should we leave it open and wait or should we close it? 15:33:10 q+ 15:33:21 ... I think it is something that we can label as "Resolve by REC" 15:33:46 kaz: As I mentioned, this kind of registration process is different from the publication process 15:33:48 ack k 15:33:59 ... so we can move ahead and resolve this issue later 15:34:20 mm: I agree, let's label it as "Resolve by end of charter" 15:34:28 ... (adds the label) 15:34:46 subtopic: Issue 467 15:34:52 mm: We did this 15:34:58 ... but the ontology is still open 15:35:08 ... let's relate it to the other issue (402) 15:35:17 ... (adds a comment) 15:36:04 ... (adds the label "Resolve by end of charter") 15:36:10 subtopic: Issue 449 15:36:18 mm: This has been fixed actually 15:36:25 ... so I think we can close this issue 15:36:28 https://github.com/w3c/wot-discovery/issues/449 15:36:50 subtopic: Issue 448 15:36:58 mm: This one, I actually fixed already 15:37:42 ... PR 472 fixed it, but the issue was not automatically closed for some reason 15:37:46 i|We did this|-> https://github.com/w3c/wot-discovery/issues/467 Issue 467 - Resolve Remaining DID issues| 15:38:06 ... (adds a comment and closes the issue) 15:38:08 https://github.com/w3c/wot-discovery/issues/448 15:38:19 i|This has been|-> https://github.com/w3c/wot-discovery/issues/449 Issue 449 - DID Implementation Fix| 15:38:33 subtopic: 328 15:38:42 https://github.com/w3c/wot-discovery/issues/328 15:38:48 mm: This was an editorial review, I am sure we resolved all of the points, so I am going to close it 15:38:58 i|This one,|-> https://github.com/w3c/wot-discovery/issues/448 Issue 448 - Assertion for DNS referencing UDP may be split normative/informative| 15:39:12 ... not sure if it was fully resolved 15:39:27 s|https://github.com/w3c/wot-discovery/issues/328|-> https://github.com/w3c/wot-discovery/issues/328 Issue 328 - CR WD review June 2022| 15:39:30 ... I am going to remove the label 15:39:32 rrsagent, draft minutes 15:39:33 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:39:54 ... (adds a comment that the issue is not a blocker for PR) 15:40:09 subtopic: Issue 148 15:40:17 mm: This one I think is also resolved 15:40:40 ... we had to sort out which our context URLs are and I think we did that 15:40:41 https://github.com/w3c/wot-discovery/issues/148 15:40:45 ... so we can close the issue 15:40:51 ... any objections to closing? 15:41:07 ... (adds a comment and closes the issue) 15:41:10 s|https://github.com/w3c/wot-discovery/issues/148|| 15:41:13 subtopic: Issue 141 15:41:30 mm: Great idea, but did not get around to work on it 15:41:35 i|This one I think|-> https://github.com/w3c/wot-discovery/issues/148 Issue 148 - Discovery context and namespace under w3.org/ns 15:41:37 ... let's defer it to 2.0 15:41:49 ... (changes the label) 15:42:09 i|Great idea|-> https://github.com/w3c/wot-discovery/issues/141 Issue 141 - Add query examples to spec| 15:42:14 subtopic: Issue 69 15:42:15 https://github.com/w3c/wot-discovery/issues/69 15:42:28 mm: In general, we probably need to defer informative issues 15:42:37 ... this also applies to this issue 15:42:47 ... (adds the "Defer to 2.0" label) 15:43:02 subtopic: Issue 64 15:43:29 mm: (adds the "defer to 2.0" label) 15:43:40 ... now we have two issues left 15:44:24 ... my plan is to do the acknowledgements offline and then send an email to the group to check 15:44:29 subtopic: Issue 185 15:45:18 mm: To resolve this, I think we should move this to the Profile repository 15:45:38 ... (moves the issue to the wot-profile repository) 15:46:03 ... now only the Acknowledgments are left, which means that we are basically done 15:46:14 ... I could do that now or offline 15:46:34 ... I'll do it offline and then send an email around 15:46:34 rrsagent, draft minutes 15:46:35 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:47:07 ... with an alphabtical list of all people who submitted a PR, whether it was merged or not 15:47:08 s/subtopic: 328/subtopic: Issue 328/ 15:47:29 ... editor's won't be mentioned a second time in the Acknowledgements section 15:47:42 s/editor's/editors/ 15:47:52 i|adds the "def"|-> https://github.com/w3c/wot-discovery/issues/64 Issue 64 - XPath queries of vocabulary using namespaces| 15:48:07 ... anything else we need to worry about? 15:48:08 q+ 15:48:35 ... I will do another readthrough, if I notice anything editorial, I will send an email around 15:48:55 ... it will basically be a sanity check, other than that we are done 15:49:12 kaz: Do you mean we will make the resolution for publication by email? 15:49:26 mm: We could do the resolution right now 15:49:32 ... which is not a bad idea 15:50:23 proposal: Discovery TF approves the current version of the WoT Discovery document as the PR draft, with the exception of additional acknowledgements and spelling and grammar corrections. 15:50:43 kaz: Does that mean that we already resolved all necessary issues and PRs? 15:51:04 mm: Yes, we are done, except for editorial changes 15:51:40 proposal: Discovery TF approves the current version of the WoT Discovery document as the PR draft, with the exception of additional acknowledgements and spelling and grammar corrections. Final editorial changes will be approved during the main call prior to the resolution for PR transition. 15:51:43 ... we should do a call for resolution in the main call for PR transition 15:52:14 kaz: So the remaining issues can be deferred? 15:52:31 mm: The remaining ones are deferred or related to the implementation report 15:52:40 ... but there are also some editorial ones 15:53:07 ... in the remaining time we could scan these issues to see if there is anything we should resolve 15:53:30 ... (goes through the issues, labels some as editorial) 15:53:54 ... will double-check issue 410 15:54:17 ... will see if I can clean it up as part of the general cleanup 15:54:51 rrsagent, draft minutes 15:54:53 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:54:59 ack k 15:55:08 ... (labels issue 413 as deferred to Discovery 2.0) 15:55:20 i|adds the "defer|-> https://github.com/w3c/wot-discovery/issues/64 Issue 64 - XPath queries of vocabulary using namespaces| 15:55:39 proposal: Discovery TF approves the current version of the WoT Discovery document as the PR draft, with the exception of additional acknowledgements and spelling and grammar corrections. Final editorial changes will be approved during the main call prior to the resolution for PR transition. 15:56:13 resolution: Discovery TF approves the current version of the WoT Discovery document as the PR draft, with the exception of additional acknowledgements and spelling and grammar corrections. Final editorial changes will be approved during the main call prior to the resolution for PR transition. 15:56:22 topic: Testing 15:56:35 mm: Some testing things need to be resolved by PR transition 15:56:35 https://github.com/w3c/wot-discovery/issues/416 15:56:49 ... issue 416 has been resolved, going to close it 15:56:55 ... (closes issue 416) 15:57:11 ... issue 415 has also been resolved 15:57:24 ... can you look into this issue, Farshid? 15:57:32 i|To resolve this,|-> https://github.com/w3c/wot-profile/issues/397 former wot-discovery Issue 185, which has been moved to wot-profile as Issue 397| 15:57:48 ft: Will look into it 15:58:12 i/now only the issue/topic: Next steps/ 15:58:15 rrsagent, draft minutes 15:58:16 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 15:58:34 mm: I update the implementation report, please look into the testing-related issues in the meantime 15:58:59 ... (adds "Resolve by PR" to issue 415) 15:59:34 mm: Let's close the meeting 15:59:46 [adjourned] 16:00:50 i/now only the Ac/topic: Next steps/ 16:00:51 rrsagent, draft minutes 16:00:52 I have made the request to generate https://www.w3.org/2023/05/22-wot-discovery-minutes.html kaz 18:13:09 Zakim has left #wot-discovery