11:00:53 RRSAgent has joined #wot-profile 11:00:57 logging to https://www.w3.org/2023/04/05-wot-profile-irc 11:01:02 meeting: WoT Profile 11:03:00 present+ Kaz_Ashimura, Ege_Korkan, Luca_Barbato, Tomoaki_Mizushima 11:03:18 present+ Michael_Lagally 11:03:25 chair: Lagally 11:04:59 Ege has joined #wot-profile 11:05:12 scribenick: luca_barbato 11:06:10 topic: Past Minutes Review 11:06:13 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Profile_WebConf#Profile_-_April_5th.2C_2023 11:09:10 -> https://www.w3.org/2023/03/22-wot-profile-minutes.html Mar-22 11:09:42 ml: Consensus? 11:09:57 .. published 11:09:57 (approved) 11:10:05 present+ Michael_McCool 11:10:19 topic: Open Issues 11:11:14 ryuichi has joined #wot-profile 11:11:59 https://github.com/w3c/wot-profile/issues/302 11:12:00 subtopic: #302 11:12:24 s|https://github.com/w3c/wot-profile/issues/302|| 11:12:39 The issue can be closed 11:12:46 i|The|-> https://github.com/w3c/wot-profile/issues/302 Issue 302 - Clarify the payload formats of read/write property| 11:12:54 subtopic: #299 11:12:59 q+ 11:14:55 ege: We discussed about it, we need to add something to the profile spec 11:15:06 .. a PR is open for it. 11:15:12 i|We dis|-> https://github.com/w3c/wot-profile/issues/299 Issue 299 - Contradiction with the Arch spec on protocol bindings| 11:15:19 https://github.com/w3c/wot-profile/issues/223 11:15:20 present+ Ryuichi_Matsukura 11:15:29 subtopic: #223 11:15:45 s|https://github.com/w3c/wot-profile/issues/223|| 11:15:57 ege: The example 48 should address it 11:16:00 ml: Closed 11:16:06 i|The e|-> https://github.com/w3c/wot-profile/issues/223 Issue 223 - Example 46 is not about subscribeallevents| 11:16:11 rrsagent, make log public 11:16:18 rrsagent, draft minutes 11:16:19 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:16:44 subtopic: #213 11:18:05 q+ 11:18:30 ml: The linked PR is already a significant improvement 11:18:43 ack e 11:19:14 i|linked|-> https://github.com/w3c/wot-profile/issues/213 Issue 213 - Wrong place to use HTTP Baseline Profile| 11:19:43 ege: Michael's last review is pending 11:19:58 i|Mich|-> https://github.com/w3c/wot-profile/pull/297 related PR 297 - Revised Abstract and Introduction - fixes #115| 11:20:42 ml: Is everybody happy with merging this PR ? 11:20:56 mm: Let's merge it 11:21:53 mm: Merged and Issue closed 11:22:05 subtopic: #171 11:22:22 ml: Outdated and to be closed 11:23:29 subtopic: #299 11:23:41 i|Out|-> https://github.com/w3c/wot-profile/issues/171 Issue 171 - Identification of profiles| 11:23:42 q+ 11:24:00 qq+ McCool 11:24:04 q- Mc 11:24:32 -> https://github.com/w3c/wot-profile/issues/299 Issue 299 - Contradiction with the Arch spec on protocol bindings 11:25:02 q+ 11:25:52 ack e 11:27:50 kaz: I cannot agree with Ben's position 11:28:29 .. we need to refactor all the specifications, and do that in the new charter 11:29:19 s/cannot// 11:29:21 s/cannot// 11:29:34 rrsagent, draft minutes 11:29:35 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:30:38 ege: The pr linked is fixing a different problem 11:30:59 s/do that/we'll do that/ 11:31:03 ack k 11:32:27 subtopic: #349 11:32:29 -> https://github.com/w3c/wot-profile/issues/349 Issue 349 - Are all TD 1.1 assertions valid in all profiles? 11:33:14 -> https://github.com/w3c/wot-profile/pull/368 related PR 368 - Add TD assertion conformance 11:33:37 ml: I support going with that PR 11:38:28 11:38:45 s/mer/PR368 mer/ 11:39:19 11:39:26 topic: Security-labeled issue 11:39:40 mm: We'll discuss them in the wot-security 11:39:49 s/Security-labeled issue/#313/ 11:40:17 i|We'll|-> https://github.com/w3c/wot-profile/issues/313 Issue 313 - Include the "auto" security scheme to the list of supported schemes| 11:40:43 mm: but it conflicts with the work on wot-discovery that has higher priority 11:41:50 mm: All the issues are all related and might be addressed in a single PR. 11:41:55 i|313|topic: Security-labeled issues| 11:42:11 s/topic: #313/subtopic: #313/ 11:42:44 subtopic: #348 11:42:46 https://github.com/w3c/wot-profile/issues/348 11:42:50 i|subtopic: #313|-> https://github.com/w3c/wot-profile/labels/security security issues| 11:43:09 mm: it is related to formatting assertions 11:43:26 .. the security issues have priority 11:43:59 s|https://github.com/w3c/wot-profile/issues/348|-> https://github.com/w3c/wot-profile/issues/348 Issue 348 - Create sub-assertions for Keywords in the Links section| 11:44:34 rrsagent, draft minutes 11:44:35 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:44:44 rrsagent, make log public 11:44:45 q+ 11:44:48 q+ 11:45:12 rrsagent, make log public 11:45:15 rrsagent, draft minutes 11:45:16 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:45:25 mm: I'll ask to opensource the generator script 11:45:31 i|Issue 313|subtopic: #313| 11:46:05 ml: We'll wait for a response on the request 11:46:06 rrsagent, draft minutes 11:46:07 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:47:04 q? 11:47:07 ml: Please expand the information on the issue so other may help 11:48:06 ack l 11:48:50 kaz: is 348 part of the security issues? 11:49:46 ml: 348 is not related to security, but needs mm contribution 11:50:43 s|topic: Security-labeled issues|| 11:50:49 s/subtopic: #313// 11:50:51 rrsagent, draft minutes 11:50:52 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:50:58 kaz: 11:51:29 (just removed "Security-labeled issues" from the topic within the minutes) 11:51:31 rrsagent, draft minutes 11:51:33 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:51:59 mm: Help wanted on addressing the P1 issues still open 11:52:39 topic: New pull requests 11:53:27 subtopic: #382 11:54:06 ml: It is a draft, ege already started reviewing it 11:54:59 i|It is|-> https://github.com/w3c/wot-profile/pull/382 PR 382 - Draft: initial draft of webhook properties section| 11:55:17 .. it contains a proposal for the an observe mechanism for properties 11:57:01 rrsagent, draft minutes 11:57:03 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz 11:57:15 q+ 11:57:20 ack k 11:57:29 q+ 11:59:04 lb: Better to use POST for both subscription and unsubscription 11:59:31 -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/pull/382.html#http-webhook-profile-protocol-binding-unobserveallproperties preview - 8.4.1.4 unobserveallproperties 11:59:58 ege: Make sure the refer to properties instead of event 12:01:27 q+ 12:01:36 ege: DELETE would need a identifer for the matching observe 12:01:42 see https://stackoverflow.com/questions/299628/is-an-entity-body-allowed-for-an-http-delete-request 12:02:03 mm: I'll do another iteration 12:02:04 ack e 12:02:08 ack l 12:02:09 ack k 12:02:29 [Kaz notes we're out of time and suggests continue the discussion next time] 12:02:31 [adjourned] 12:02:37 rrsagent, draft minutes 12:02:38 I have made the request to generate https://www.w3.org/2023/04/05-wot-profile-minutes.html kaz