13:05:46 RRSAgent has joined #wot-profile 13:05:51 logging to https://www.w3.org/2025/05/14-wot-profile-irc 13:05:51 Mizushima has joined #wot-profile 13:05:53 meeting: WoT Profile 13:06:02 mjk has joined #wot-profile 13:06:36 present+ Kaz_Ashimura, Ben_Francis, David_Ezell, Ege_Korkan, Kunihiko_Toumura, Mihcael_Koster, Tomoaki_Mizushima 13:06:43 rrsagent, make log public 13:06:48 rrsagent, draft minutes 13:06:49 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:08:05 luca_barbato has joined #wot-profile 13:08:56 chair: Ben 13:09:22 present+ Luca_Barbato 13:09:28 rrsagent, draft minutes 13:09:30 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:10:04 Volunteers for scribe? 13:10:28 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Profile_WebConf#Profiles_-_May_14th%2C_2025 13:11:01 scribenick: EgeKorkan 13:11:27 topic: Minutes 13:11:29 topic: Minutes 13:11:29 -> https://www.w3.org/2025/05/07-wot-profile-minutes.html May-7 13:11:41 s/topic: Minutes// 13:11:43 bf: any remarks to the minutes 13:11:52 ... nothing, confirmed 13:11:54 s/Volunteers for scribe?// 13:12:03 rrsagent, draft minutes 13:12:04 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:12:24 topic: Resolutions 13:12:28 dezell has joined #wot-profile 13:12:33 q+ 13:12:36 present+ David_Ezell 13:12:36 bf: We agreed to publish the current work as a note 13:13:10 q+ 13:13:19 kaz: please send an email to confirm the resolution 13:13:20 ack k 13:13:34 bf: Let's proceed as if it is done 13:13:47 lb: I think so too. The email should mention that we can handle complaints 13:14:05 topic: WG Note Process 13:14:13 bf: (shows the W3C process) 13:15:12 q+ 13:15:15 q+ 13:15:17 s/please send an email to confirm the resolution/we meant to make a group-wide resolution about our plan during the main call but completely forgot. sorry. given you've sent an email about the proposed resolution, we can simply conclude that by email too./ 13:15:22 bf: should we do a draft not or a note? 13:15:23 rrsagent, draft minutes 13:15:25 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:16:11 q? 13:16:15 lb: given your constraints, is it better to do a draft note now or wait for a note 13:16:22 q- 13:16:59 rrsagent, draft minutes 13:17:01 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:17:14 q+ 13:17:29 q? 13:17:31 +1 to moving ahead 13:18:17 q? 13:18:26 ek: I think we should just go ahead like the other deliverables 13:18:30 ... (checks examples) 13:18:35 ... ok we should go with a note 13:18:43 s/draft not or a note/Draft Note or a Note/ 13:18:45 rrsagent, draft minutes 13:18:47 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:18:53 ack e 13:18:53 ack k 13:19:09 topic: Issue Triage 13:19:24 bf: Should an issue block if we go for a note 13:19:30 s/do a D/publish a D/ 13:19:31 q? 13:19:38 ... we should go through an assign to people based on the triage 13:20:03 i|Issue Triag|kaz: also OK with publishing a Note based on our resolution| 13:20:32 i|also|scribenick: kaz| 13:20:36 q? 13:20:40 ... I have reduced it with profile 1.0 label 13:20:42 q+ 13:20:49 i|Should an|scribenick: EgeKorkan| 13:20:52 rrsagent, draft minutes 13:20:54 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:21:12 q+ 13:21:28 ek: is the "blocks publication" label usable? 13:21:44 bf: seems inconsistent. "profile 1.0" are for features we want to include 13:22:29 (Kaz just would like to suggest we look into each Issue which has the "blocks publication" label.) 13:22:31 ack e 13:22:32 ack k 13:22:59 subtopic: Issue 6 13:23:00 q+ 13:23:02 subtopic: Issue 6 13:23:03 q_ 13:23:04 q? 13:23:05 q+ 13:23:08 s/subtopic: Issue 6// 13:23:19 bf: this is old, from 2019 13:23:30 ... should we ask McCool 13:23:45 lb: we should let the user decide 13:23:46 i|this is|-> https://github.com/w3c/wot-profile/issues/6 Issue 6 - Recommended Security| 13:23:55 ... we can say that this is not a profile problem 13:24:32 q? 13:24:36 q+ 13:24:47 rrsagent, draft minutes 13:24:48 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:25:02 s/q_// 13:25:35 q? 13:25:42 ack l 13:26:54 ack e 13:27:24 ek: not sure anymore, I thought it can be closed if it is this old 13:27:41 kaz: we can close it but revisit it for profile 2.0 13:29:53 s/we can close it but revisit it for profile 2.0/personally tend to agree with you all to close this issue. However, given McCool is not available during the whole May, I'd suggest we mark this not "blocks publication" but "need clarification" for today./ 13:29:55 subtopic: ISsue 42 13:30:08 s/subtopic: ISsue 42/subtopic: Issue 41 13:30:25 bf: Ege you have commented fairly recently 13:30:44 ek: It can be closed 13:30:58 subtopic: issue 63 13:30:58 i|Issue 41|bf: would close the issue itself with an explicit note to ask McCool for review./ 13:31:04 rrsagent, draft minutes 13:31:05 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:31:11 bf: we did not decide on this requirement 13:31:12 q+ 13:31:15 q- 13:31:26 q+ 13:31:43 i|Ege you have|-> https://github.com/w3c/wot-profile/issues/41 Issue 41 - Specific constraints on OAuth need to be defined| 13:31:49 rrsagent, draft minutes 13:31:50 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:32:29 i|we did not|-> https://github.com/w3c/wot-profile/issues/63 Issue 63 - Accessibility review of WoT Profile specification| 13:32:31 rrsagent, draft minutes 13:32:33 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:32:42 q+ 13:32:59 q- 13:33:05 ack e 13:33:07 q? 13:33:17 ek: if we don't have a UI requirement, we don't need this "feature" 13:33:30 kaz: would suggest we mark this "Profile-2.0" instead of "Profile-1.0" 13:33:41 i|would|scribenick: kaz| 13:33:47 scribenick: EgeKorkan 13:33:50 bf: it is about an accesibility review 13:33:51 rrsagent, draft minutes 13:33:53 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:34:00 ek: then we can close 13:34:07 kaz: we can add profile 2.0 label and not close it 13:34:09 bf: done 13:34:38 s/kaz: would suggest we mark this "Profile-2.0" instead of "Profile-1.0"// 13:35:05 s/and not close it/instead of the "Profile-1.0"label"/ 13:35:35 s/profile 2.0 label/a new "Profile-2.0" label/ 13:35:38 rrsagent, draft minutes 13:35:39 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:35:45 q+ 13:36:27 s/issue 63/Issue 63/ 13:36:35 subtopic: Issue 397 13:36:41 de: w3c specs have a minimum of accessibility requirements 13:36:50 q? 13:36:55 bf: authentication is indeed tricky on sse 13:37:00 ... it is not a blocker for 1.0 13:37:11 s/subtopic: Issue 397// 13:37:19 i|authen|subtopic: Issue 397| 13:37:43 i|authen|-> https://github.com/w3c/wot-profile/issues/397 Issue 397 - OAuth2 and SSE Notifications| 13:37:53 rrsagent, draft minutes 13:37:55 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:38:31 q? 13:38:41 q+ 13:38:52 de: I agree, it is tricky 13:39:00 bf: we had a workaround for this in webthings 13:39:18 ... this is just about best practices though 13:40:14 kaz: we can move it to the security best practices repo 13:40:30 s/repo/repo, but would suggest we check with McCool/ 13:40:37 ack d 13:40:39 ack k 13:40:46 rrsagent, draft minutes 13:40:48 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:41:05 subtopic: Issue 105 13:41:28 -> https://github.com/w3c/wot-profile/issues/105 Issue 105 - Action Improvements: identity /owner of an action invocation 13:41:31 rrsagent, draft minutes 13:41:33 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:41:39 q? 13:41:42 subtopic: Issue 105 13:41:48 bf: never seen it done 13:41:54 ek: me neither but kinda makes sense 13:42:01 s/subtopic: Issue 105// 13:42:01 bf: probably only for complex systems 13:42:02 rrsagent, draft minutes 13:42:03 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:42:36 ek: I think it can be close and opened by someone when they encounter the issue during implmentation 13:43:10 subtopic: Issue 141 13:43:23 -> https://github.com/w3c/wot-profile/issues/141 Issue 141 - how to handle multiple forms 13:43:29 rrsagent, draft minutes 13:43:30 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:43:58 subtopic: Issue 141 13:44:10 s/subtopic: Issue 141// 13:44:11 q? 13:45:26 q? 13:45:34 q+ 13:46:37 bf: how should we handle this? left open? 13:46:41 ack k 13:46:45 ek: it makes sense to have a public and local url 13:46:52 kaz: it can be handled in the TD spec as well 13:47:33 s/it can/wondering if this is really an issue for WoT Profile. Maybe it can/ 13:47:37 rrsagent, draft minutes 13:47:38 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:48:21 subtopic: issue 211 13:48:35 bf: no figures like that, it can be closed 13:48:47 i|no fig|-> https://github.com/w3c/wot-profile/issues/211 Issue 211 - Image update for HTTP baseline profile| 13:48:51 rrsagent, draft minutes 13:48:53 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:49:31 subtopic: Issue 221 13:49:33 -> https://github.com/w3c/wot-profile/issues/221 Issue 221 - Security Schemes are too loose 13:49:36 rrsagent, draft minutes 13:49:37 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:50:58 bf: (shows the current spec) 13:51:05 ek: ok we can close it, it is addressed 13:51:13 rrsagent, draft minutes 13:51:15 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:51:34 q? 13:51:45 subtopic: Issue 237 13:51:56 -> https://github.com/w3c/wot-profile/issues/237 Issue 237 - Rework profile overview figure 13:53:25 q+ 13:53:47 q- 13:54:52 q? 13:56:26 subtopic: Issue 254 13:56:35 i|254|(closed)| 13:56:55 -> https://github.com/w3c/wot-profile/issues/254 Issue 254 - Webhook unsubscribe operation in diagram doesn't match protocol binding 13:56:59 rrsagent, draft minutes 13:57:00 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 13:57:28 bf: it seems like a bug and we agreed on delete 13:57:36 bf: I will do it 13:57:50 q+ 13:58:30 kaz: Is that a bug on the TD side? 13:58:45 bf: no just an inconsistency on the profile documenty 13:58:56 s/documenty/document/ 13:59:04 ack k 13:59:28 q+ 14:00:08 topic: Review 14:00:17 bf: please everyone make sure to review the document 14:01:21 ack k 14:02:04 bf: aob? 14:02:16 ... adjourned 14:02:30 i|aob|kaz: we can continue the discussion next week if needed| 14:02:48 i|aob|bf: have a conflict next week...| 14:03:07 i|aob|kaz: let's continue the discussion in 2 weeks then :)| 14:03:36 i|aob|bf: meanwhile, would be great if people could review the Issues on GitHub.| 14:03:41 rrsagent, draft minutes 14:03:42 I have made the request to generate https://www.w3.org/2025/05/14-wot-profile-minutes.html kaz 14:07:08 cris has left #wot-profile 16:27:42 Zakim has left #wot-profile 22:54:03 EgeKorkan has joined #wot-profile 23:27:06 EgeKorkan has joined #wot-profile 23:44:16 EgeKorkan has joined #wot-profile