13:01:33 <RRSAgent> RRSAgent has joined #wot-profile
13:01:37 <RRSAgent> logging to https://www.w3.org/2025/06/25-wot-profile-irc
13:01:38 <kaz> meeting: WoT Profile
13:01:39 <EgeKorkan> EgeKorkan has joined #wot-profile
13:02:04 <kaz> present+ Kaz_Ashimura, Ben_Francis, Josh_Thomas, Michael_Koster
13:02:12 <kaz> regrets+ Sebastian, Ege
13:02:23 <kaz> present+ David_Ezell, Tomoaki_Mizushima
13:02:25 <mjk> mjk has joined #wot-profile
13:02:29 <kaz> rrsagent, make log public
13:02:34 <kaz> rrsagent, draft minutes
13:02:35 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/25-wot-profile-minutes.html kaz
13:02:56 <kaz> chair: Ben
13:03:07 <dezell> dezell has joined #wot-profile
13:03:15 <dezell> present+ David_Ezell
13:04:41 <kaz> present+ Kunihiko_Toumura
13:04:44 <kaz> rrsagent, draft minutes
13:04:45 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/25-wot-profile-minutes.html kaz
13:06:00 <kaz> present+ Daniel_Peintner
13:06:27 <dape> dape has joined #wot-profile
13:06:36 <kaz> scribenick: kaz
13:06:48 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Profile_WebConf#Profiles_-_2025-06-25
13:07:02 <kaz> topic: Agenda
13:07:10 <kaz> -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Profile_WebConf#Profiles_-_2025-06-25 Agenda for today
13:07:19 <kaz> bf: (goes through the minutes)
13:07:30 <kaz> s/minutes/agenda
13:07:37 <kaz> rrsagent, draft minutes
13:07:38 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/25-wot-profile-minutes.html kaz
13:08:29 <kaz> q+
13:09:13 <kaz> q-
13:09:46 <kaz> kaz: we as the Profile TF should think about the publication schedule as well
13:10:39 <kaz> bf: don't think we can publish the REC during this Charter period, but we should think about our publication schedule in general
13:10:43 <kaz> topic: Minutes
13:10:54 <kaz> -> https://www.w3.org/2025/05/28-wot-profile-minutes.html May-28
13:10:55 <kaz> approved
13:11:06 <kaz> topic: PRs
13:11:58 <kaz> subtopic: PR 419
13:12:09 <kaz> -> https://github.com/w3c/wot-profile/pull/419 PR 419 - Explicity state contentType of application/json in Forms - closes #141
13:12:40 <kaz> bf: related to issue 141
13:12:58 <kaz> -> https://github.com/w3c/wot-profile/issues/141 Issue 141 - how to handle multiple forms
13:14:28 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/419/4165bf1...benfrancis:fd01363.html#http-basic-profile-protocol-binding-readproperty diff from PR 419 - 6.2.1.1 readproperty
13:14:40 <benfrancis> q?
13:15:08 <kaz> bf: not big changes but several clarifications
13:15:25 <kaz> ... (goes through the changes starting with Section 6.2.1.1)
13:15:42 <dape> q+
13:15:44 <kaz> ... (then 7.2.1.2)
13:15:51 <kaz> ... got comments from Ege and Daniel
13:16:15 <benfrancis> q?
13:16:28 <kaz> dp: got your response
13:16:50 <kaz> ... this PR makes the document clearer
13:17:10 <dape> ack dape
13:17:12 <kaz> ... various algorithms are handled by the Scripting API Note also
13:17:23 <dezell> q+
13:17:27 <kaz> ... wondering about which document to have what description
13:17:35 <kaz> q+
13:18:02 <kaz> bf: different implementations may have different approaches
13:18:05 <benfrancis> q?
13:18:27 <kaz> de: we struggled JSON
13:18:45 <kaz> ... if it's specified as application/json
13:19:00 <kaz> ... what would happen with possible wrapper
13:19:16 <kaz> ... it would be treated as text possibly
13:19:39 <kaz> ... indicates some additional breaklines...
13:19:44 <kaz> bf: really good point
13:20:28 <kaz> ... what if you had a line break with empty lines
13:20:38 <kaz> de: where is the project?
13:20:45 <benfrancis> https://github.com/w3c/wot-profile/issues
13:21:16 <kaz> bf: please give your input as a GitHub Issue on the above repo
13:21:19 <kaz> de: ok
13:21:29 <kaz> ack d
13:21:38 <benfrancis> q?
13:22:18 <kaz> ack k
13:22:24 <kaz> kaz: ok with this PR itself
13:23:54 <benfrancis> benfrancis
13:24:42 <kaz> s/itself/itself, but as Daniel also mentioned, we need to think about refactoring later/
13:24:46 <kaz> (merged)
13:25:06 <kaz> subtopic: PR 421
13:25:23 <kaz> -> https://github.com/w3c/wot-profile/pull/421 PR 421 - Switch reference from wot-security-best-practices to wot-security - closes #269
13:25:48 <kaz> -> https://github.com/w3c/wot-profile/issues/269 related Issue 269 - Remove reference to security best practices document
13:25:54 <kaz> bf: Ege had a comment
13:26:11 <kaz> -> https://github.com/w3c/wot-profile/pull/421#pullrequestreview-2957954097 Ege's comment
13:27:14 <kaz> kaz: it depends on which content to be referred to
13:27:25 <kaz> ... Security Best Practices or Security Note
13:27:48 <benfrancis> q?
13:28:19 <kaz> bf: (shows the text within the WoT Profile)
13:30:02 <kaz> kaz: if that is just general reference for Security and Privacy, a reference to the public Note would make sense
13:30:08 <kaz> bf: what about the HTML notation?
13:30:37 <kaz> ... should use the ReSpec notation instead of the direct link using HTML?
13:30:45 <kaz> dp: right
13:30:46 <kaz> kaz: yes
13:30:56 <kaz> bf: (done)
13:31:02 <kaz> rrsagent, draft minutes
13:31:03 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/25-wot-profile-minutes.html kaz
13:31:15 <kaz> ... can we merge this now?
13:31:40 <kaz> kaz: yes
13:31:42 <kaz> merged
13:32:21 <kaz> topic: Triage 1.0 issues proposed for closing
13:32:43 <benfrancis> q?
13:32:56 <kaz> -> https://github.com/w3c/wot-profile/issues?q=is%3Aissue%20state%3Aopen%20label%3AProfile-1.0%20label%3Aclose%20sort%3Acreated-asc old issues
13:33:10 <kaz> subtopic: Issue 299
13:33:23 <kaz> -> https://github.com/w3c/wot-profile/issues/299 Issue 299 - Contradiction with the Arch spec on protocol bindings
13:34:16 <benfrancis> q?
13:34:24 <kaz> bf: any thoughts?
13:34:55 <kaz> q+
13:35:33 <kaz> kaz: maybe we could add an Editor's Note for Profile 1.0 about our concern
13:35:34 <kaz> q-
13:36:11 <kaz> present+ Ege_Korkan
13:36:17 <kaz> dp: also we should check with Ege
13:36:23 <kaz> (Ege has just joined)
13:36:34 <kaz> bf: (describes the points to Ege)
13:36:59 <kaz> ... shall we defer this issue to Profile 2.0?
13:37:07 <EgeKorkan> q+
13:37:15 <kaz> ek: that's fine
13:37:26 <kaz> ack e
13:37:50 <kaz> bf: don't want to close this but defer to 2.0
13:37:53 <benfrancis> q?
13:38:16 <kaz> ... (removes "Profile-1.0" label and adds "defer to 2.0" label
13:38:39 <kaz> subtopic: Issue 310
13:38:57 <kaz> -> https://github.com/w3c/wot-profile/issues/310 Issue 310 - Requirements due diligence
13:39:03 <kaz> bf: (goes through the issue)
13:39:13 <benfrancis> q?
13:39:16 <kaz> ... would suggest we close this
13:39:28 <kaz> ek: that's fine
13:40:01 <kaz> ... maybe we could collect requirements for 2.0
13:40:02 <benfrancis> q?
13:40:05 <kaz> bf: right
13:40:11 <kaz> closed
13:40:16 <kaz> subtopic: Issue 312
13:40:42 <kaz> -> https://github.com/w3c/wot-profile/issues/312 Issue 312 - Define Plugfest Test Scenarios
13:41:01 <benfrancis> q?
13:41:05 <kaz> dp: defining test scenario itself is important but for 2.0
13:41:07 <kaz> bf: right
13:41:25 <kaz> ... (changes the label to "Profile-2.0")
13:41:29 <kaz> subtopic: Issue 323
13:41:56 <kaz> -> https://github.com/w3c/wot-profile/issues/323 Issue 323 - Revisit section 6 title and structure
13:42:02 <kaz> bf: (goes through the issue)
13:42:09 <kaz> ... let me show you the document
13:42:33 <benfrancis> q?
13:43:02 <dape> q+
13:43:03 <kaz> -> https://w3c.github.io/wot-profile/#common-constraints it's section "5. Common Constraints"
13:43:12 <kaz> dp: the title itself is fine
13:43:25 <kaz> ... but what is confusing to me is the paragraph after that
13:43:54 <kaz> bf: which says "The following sections are applicable for all of the HTTP profiles defined by this document." ?
13:43:56 <EgeKorkan> +1 to what daniel said
13:43:57 <kaz> dp: right
13:44:11 <kaz> bf: would you create another issue about that?
13:44:16 <kaz> dp: will do
13:44:36 <benfrancis> q?
13:44:38 <kaz> rrsagent, draft minutes
13:44:39 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/25-wot-profile-minutes.html kaz
13:44:56 <kaz> bf: now would like to close this issue itself
13:45:00 <kaz> closed
13:45:14 <kaz> subtopic: Issue 358
13:45:39 <kaz> -> https://github.com/w3c/wot-profile/issues/358 Issue 358 - Wide review
13:45:45 <kaz> q+
13:46:29 <kaz> ack d
13:46:30 <kaz> ack k
13:46:41 <kaz> kaz: I'm OK with closing this issue
13:47:06 <kaz> ... when we publish WoT Profile 2.0 as CR, etc., we can create a similar issue again :)
13:47:09 <kaz> bf: ok
13:47:11 <kaz> closed
13:47:15 <kaz> subtopic: Issue 384
13:47:41 <kaz> -> https://github.com/w3c/wot-profile/issues/384 Issue 384 - Read-only events should require authentication
13:48:02 <kaz> bf: related to the PING review
13:48:38 <EgeKorkan> q+
13:48:45 <kaz> q+
13:48:48 <benfrancis> q?
13:49:06 <kaz> ek: this is part of the process for REC-Trac
13:49:11 <kaz> s/Trac/Track/
13:49:24 <kaz> ack e
13:50:58 <kaz> kaz: right. my suggestion is keeping this open as an issue for 2.0, and talk about this with the new Privacy group when we publish the WoT Profile 2.0
13:51:01 <kaz> q-
13:51:57 <kaz> subtopic: Issue 401
13:52:12 <kaz> -> https://github.com/w3c/wot-profile/issues/401 Issue 401 - Document a timeline for the WG
13:52:27 <kaz> bf: this is still essential
13:52:41 <kaz> q+
13:53:13 <kaz> kaz: agree
13:53:20 <kaz> ... so would suggest we keep this open
13:53:32 <benfrancis> q?
13:53:39 <kaz> ... we should update our publication schedule anyway
13:53:42 <kaz> q-
13:54:10 <kaz> topic: Triage 1.0 issues proposed to defer to 2.0
13:54:30 <kaz> subtopic: Issue 306
13:54:42 <kaz> -> https://github.com/w3c/wot-profile/issues/306 Issue 306 - Additional implementers feedback of profile assertions
13:54:51 <kaz> bf: useful but not for Profile 1.0 Note
13:54:57 <kaz> q?
13:54:59 <kaz> kaz: +1
13:55:15 <kaz> bf: (changes the label to "Profile-2.0")
13:55:37 <kaz> subtopic: Issue 359
13:55:49 <kaz> -> https://github.com/w3c/wot-profile/issues/359 Issue 359 - Security - open issues
13:55:54 <kaz> bf: meta issue around security
13:56:20 <kaz> q?
13:57:05 <kaz> dp: technicaly, that's right but the first two bullet points don't have links for actual issues yet
13:57:12 <kaz> bf: ah, correct
13:57:21 <benfrancis> q?
13:57:22 <kaz> ... let's defer this to 2.0 for the moment
13:57:42 <kaz> subtopic: Issue 394
13:57:56 <kaz> -> https://github.com/w3c/wot-profile/issues/394 Issue 394 - Some assertions need splitting up into multiple assertions
13:58:21 <benfrancis> q?
13:58:24 <kaz> bf: this is important for REC-Track but not for NOTEs
13:58:30 <kaz> s/NOTE/Notes/
13:58:48 <kaz> (no objections)
13:59:10 <kaz> bf: (changes to "Profile-2.0")
13:59:18 <benfrancis> https://github.com/w3c/wot-profile/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22needs%20PR%22%20label%3AProfile-1.0
13:59:32 <kaz> i|https|topic: Assign issues needing a PR|
13:59:49 <kaz> bf: would be helpful if people could go through the issues above
14:00:03 <kaz> ... and we could get volunteers for PRs
14:00:40 <kaz> ... For example, Webhook Profile is kind of big
14:00:57 <kaz> ... so if nobody is interested, I can work on that for a stub
14:01:06 <kaz> topic: AOB
14:01:07 <benfrancis> q?
14:01:11 <kaz> bf: aob for today?
14:01:12 <kaz> (none)
14:01:30 <kaz> s/(none)//
14:01:56 <kaz> ek: Luca had an implementation of Webhook, I think
14:02:00 <kaz> bf: will check with Luca
14:02:09 <kaz> q?
14:02:12 <kaz> q+
14:02:49 <kaz> kaz: we're out of time, so let's continue the discussion next time and/or by GitHub and email
14:02:56 <kaz> bf: ok
14:03:14 <kaz> ... anyway, if you're interested in any of the issues, please let us know
14:03:16 <kaz> [adjourned]
14:03:20 <kaz> rrsagent, draft minutes
14:03:22 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/25-wot-profile-minutes.html kaz
14:18:25 <EgeKorka_> EgeKorka_ has joined #wot-profile
14:47:29 <EgeKorkan> EgeKorkan has joined #wot-profile
14:53:08 <EgeKorkan> EgeKorkan has joined #wot-profile
14:54:23 <EgeKorka_> EgeKorka_ has joined #wot-profile
14:55:20 <kaz> kaz has joined #wot-profile
15:10:17 <kaz> kaz has joined #wot-profile
16:25:57 <Zakim> Zakim has left #wot-profile
17:09:12 <EgeKorkan> EgeKorkan has joined #wot-profile
17:43:38 <EgeKorkan> EgeKorkan has joined #wot-profile
17:44:02 <EgeKorkan> EgeKorkan has joined #wot-profile