13:01:09 <RRSAgent> RRSAgent has joined #wot-profile
13:01:14 <RRSAgent> logging to https://www.w3.org/2025/05/28-wot-profile-irc
13:01:18 <Mizushima> Mizushima has joined #wot-profile
13:01:57 <kaz> meeting: WoT Profile
13:02:27 <kaz> present+ Kaz_Ashimura, Ben_Francis
13:02:30 <kaz> chair: Ben
13:02:51 <kaz> present+ Michael_Koster
13:03:44 <kaz> present+ Sebastian_Kaebisch
13:03:53 <kaz> present+ Tomoaki_Mizushima
13:04:35 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Profile_WebConf#Profiles_-_May_28th%2C_2025
13:05:24 <kaz> regrets+ Ege, Daniel
13:07:07 <sebastian> sebastian has joined #wot-profile
13:07:59 <mjk> mjk has joined #wot-profile
13:08:02 <kaz> present+ mjk
13:08:19 <kaz> topic: Minutes
13:08:22 <kaz> -> https://www.w3.org/2025/05/14-wot-profile-minutes.html May-14
13:08:25 <mjk> topic: issues review
13:08:49 <mjk> s/issues review/minutes
13:09:09 <mjk> topic: PR review
13:09:19 <mjk> subtopic: PR # 419
13:09:44 <kaz> -> https://github.com/w3c/wot-profile/pull/419 PR 419 - Explicity state contentType of application/json in Forms - closes #141
13:11:00 <sebastian> q+
13:11:39 <mjk> bf: How does a TD consumer select from multiple forms?
13:11:42 <benfrancis> q?
13:12:20 <cris> cris has joined #wot-profile
13:12:28 <kaz> -> https://github.com/w3c/wot-profile/issues/141 related Issue 141 - how to handle multiple forms
13:12:29 <mjk> seb: We don't need to explicitly specify applicatoin/json in the form because it is the default
13:13:40 <mjk> ... TD 2.0 will also have global definitions that might help with this issue
13:14:23 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/419/4165bf1...benfrancis:fd01363.html#http-basic-profile-protocol-binding-readproperty Diff: 6.2.1.1 readproperty
13:14:45 <sebastian> https://w3c.github.io/wot-thing-description/#table-default-values-of-vocabulary-terms-that-are-used-when-the-terms-are-not-present-in-a-td
13:14:49 <mjk> bf: The TD spec is not clear enough about the behavior of default content types
13:15:05 <kaz> q+
13:15:28 <mjk> seb: Here is a link to the TD spec section
13:15:43 <sebastian> ack s
13:16:09 <kaz> present+ Cristiano_Aguzzi
13:16:31 <benfrancis> q?
13:17:23 <mjk> bf: t(reviews the algorithm for content type selection in the profile document )
13:17:51 <mjk> seb: (explains the content selection algorithm commonly used by WoT clients)
13:17:59 <kaz> s/t(/(/
13:18:06 <mjk> s/t(/(
13:18:19 <kaz> rrsagent, make log public
13:18:23 <kaz> rrsagent, draft minutes
13:18:24 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:18:47 <mjk> seb: A client does need to know which content type it needs and need to look in the form
13:19:19 <mjk> s/need to/needs to
13:19:29 <benfrancis> q?
13:19:37 <mjk> bf: there are some cases that won't work
13:20:14 <cris> q+
13:20:32 <kaz> ack k
13:20:34 <mjk> kaz: we should make an issue for TD and go ahead with Profile 1.0
13:20:57 <mjk> bf: I have made an issue for TD 2.0
13:21:21 <mjk> ... will leave the issue #141 open for discussion
13:21:54 <kaz> present- mjk
13:22:15 <kaz> rrsagent, draft minutes
13:22:16 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:22:45 <kaz> i|PR review|scribenick: mjk|
13:22:46 <kaz> rrsagent, draft minutes
13:22:48 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:23:18 <kaz> s/topic: minutes//
13:23:19 <kaz> rrsagent, draft minutes
13:23:20 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:23:27 <benfrancis> q?
13:23:39 <kaz> i|PR review|(minutes approved)|
13:23:41 <kaz> rrsagent, draft minutes
13:23:42 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:23:52 <mjk> seb: to clarify, the redundancy doesn't hurt, and we can improve the definition in TD 2.0
13:24:27 <mjk> cris: It seems appropriate for Profile clienmts to look for application/json content type
13:25:42 <mjk> s/clienmts/clients
13:26:20 <kaz> -> https://github.com/w3c/wot-profile/issues/141#issuecomment-2916344867 Ben's comments for Issue 141
13:26:23 <mjk> subtopic: WIP PRs
13:26:42 <mjk> bf: can the WIP PRs be closed?
13:27:05 <kaz> s/subtopic:/topic:/
13:27:10 <kaz> subtopic: PR 334
13:27:10 <mjk> s/closed/closed or merged?
13:27:21 <kaz> -> https://github.com/w3c/wot-profile/pull/334 PR 334 - WIP: Provide example in the new introduction section
13:27:31 <kaz> rrsagent, draft minutes
13:27:32 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:28:57 <kaz> -> https://github.com/w3c/wot-profile/pull/334#issuecomment-2916355829 Ben's comment on PR 334
13:29:08 <mjk> subtopic: PR #271
13:29:32 <kaz> -> https://github.com/w3c/wot-profile/pull/271 PR 271 - WIP: Common constraints - identifiers
13:30:15 <kaz> s/subtopic: PR 334/subtopic: PR #334/
13:30:15 <kaz> rrsagent, draft minutes
13:30:16 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:30:22 <mjk> bf: I don't think using urn:UUID is necessary
13:30:25 <mjk> seb: agree
13:31:24 <mjk> ... it it's important to use UUID URNs you can do that
13:32:16 <mjk> bf: Does anyone disagree that this isn't necessary?
13:32:36 <mjk> seb: We should leave this for Lagally review
13:32:57 <mjk> subtopic: PR #314
13:33:17 <mjk> bf: For this one we should wait for McCool to return
13:33:35 <mjk> subtopic: PR #330
13:33:55 <kaz> i|For this|-> https://github.com/w3c/wot-profile/pull/314 PR 314 - WIP: Allow auto security scheme for other permitted security schemes|
13:34:19 <kaz> -> https://github.com/w3c/wot-profile/pull/330 PR 330 - Cloud Events Message Format
13:34:21 <kaz> rrsagent, draft minutes
13:34:22 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:34:29 <mjk> bf: there is disagreement about cloud events
13:34:48 <mjk> ... it was for Profile 1.1, should we keep it open
13:35:28 <mjk> seb: Cloud Events has been used in the market but I'm unsure about the formal specification
13:36:37 <mjk> ... We should discuss more
13:36:55 <benfrancis> q?
13:37:54 <mjk> cris: if there is no activity, we can close the PR and re-open if we need more discussion
13:38:01 <cris> ack cr
13:39:29 <mjk> bf: OK to close the PR with comments?
13:39:56 <mjk> ... OK, will close
13:40:06 <mjk> subtopic: PR #417
13:40:29 <sebastian> as I mentioned, I need to go earlier. bye
13:40:43 <mjk> bf: This was to drive consensus on the requirements for Profiles 2.0
13:40:53 <kaz> i|This|-> https://github.com/w3c/wot-profile/pull/417 PR 417 - A start on use cases and requirements for Profiles 2.0|
13:41:02 <mjk> ... We could leave it open to continue the discussion
13:41:02 <kaz> s/as I mentioned, I need to go earlier. bye//
13:41:09 <benfrancis> q?
13:41:20 <kaz> q+
13:41:39 <mjk> bf: any opinions?
13:42:23 <kaz> q-
13:42:35 <mjk> kaz: It was resolves that a task force can work on the use cases and requirements
13:43:10 <benfrancis> q?
13:43:22 <mjk> bf: It's important to have a central place for use cases but also a separate place for each specification
13:43:43 <mjk> Topic: issues review
13:44:38 <mjk> subtopic:Issue #, already discussed wit hte PR141
13:45:05 <mjk> subtopic: issue #255
13:45:40 <mjk> bf: The idea is to constrain the use of link relations for interoperability
13:46:26 <kaz> s/subtopic:Issue #, already discussed wit hte PR141//
13:46:36 <kaz> s/issues review/Issues review/
13:46:41 <mjk> ... It's difficult to make testable assertions
13:46:42 <kaz> s/issue #/Issue #/
13:46:46 <kaz> rrsagent, draft minutes
13:46:48 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:47:00 <benfrancis> q?
13:47:04 <cris> q+
13:47:13 <mjk> ... Is fixing this important for TD 1.0?
13:47:20 <kaz> i|The idea is|-> https://github.com/w3c/wot-profile/issues/255 Issue 255 - Remove or re-work section 6.1.2 Links|
13:47:22 <kaz> rrsagent, draft minutes
13:47:23 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:47:46 <mjk> cris: Is the concern stability or interoperability?
13:48:08 <mjk> bf: The concern is testability
13:48:26 <mjk> s/stability/testability
13:48:49 <benfrancis> q?
13:49:19 <benfrancis> q?
13:49:37 <mjk> cris: agree that is is difficult to test
13:50:12 <mjk> bf: There are a couple of ways we can improve this
13:50:57 <mjk> ... We can remove it or we can fix the text
13:51:35 <mjk> ... What do we need to do for the Profile 1.0 note, considering testability is not as important for a note?
13:51:58 <kaz> q+
13:52:17 <mjk> cris: The content is useful as informative to have in the document, and will improve the note
13:53:48 <mjk> kaz: I agree, and suggest we add a clear explanation in the  text as an editors note
13:53:49 <kaz> ack c
13:53:51 <kaz> ack k
13:54:28 <kaz> -> https://github.com/w3c/wot-profile/issues/255#issuecomment-2916445422 Ben's updated comment
13:54:34 <kaz> rrsagent, draft minutes
13:54:35 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
13:54:41 <mjk> subtopic: Issue #258
13:55:06 <kaz> -> https://github.com/w3c/wot-profile/issues/258 Issue 258 - New section on Webhook message format
13:55:37 <mjk> bf: This proposal for webhooks is aligned with SSE
13:56:09 <mjk> ... the metadata is in HTTP headers instead of the body
13:56:11 <mjk> q?
13:56:45 <mjk> bf: It avoids the need for a content wrapper
13:57:01 <mjk> ... does this need to be fixed for 1.0?
13:57:03 <benfrancis> q?
13:57:17 <cris> q+
13:57:20 <mjk> ... It is needed for interoperability
13:58:22 <mjk> cris: Should we remove this section?
13:58:47 <mjk> bf: We might define our own payload format or use the header approach
13:59:11 <kaz> q+
13:59:25 <mjk> cris: The webhook is easier to use with Profile 1.0
13:59:56 <mjk> ... because the payload is described in the data schema
14:00:00 <mjk> q?
14:01:45 <mjk> kaz: This discussion should include the binding group
14:02:14 <mjk> ... Webhooks don't need to be resolved for Profile 1.0
14:03:09 <mjk> bf: Agree thet 2.0 is the place tp resolve this, the issue is that there is a specific requirement in Profile 1.0
14:03:20 <mjk> ... minimum effort is the guidance
14:03:22 <kaz> s/tp/to/
14:03:34 <mjk> Topic: AOB and Adjourn
14:03:43 <mjk> bf: adjourned
14:03:49 <kaz> rrsagent, draft minutes
14:03:50 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
14:03:57 <kaz> q-
14:03:57 <kaz> ack c
14:05:26 <kaz> s/... minimum/kaz: minimum/
14:05:26 <kaz> rrsagent, draft minutes
14:05:27 <RRSAgent> I have made the request to generate https://www.w3.org/2025/05/28-wot-profile-minutes.html kaz
14:05:54 <cris> cris has left #wot-profile
16:27:46 <Zakim> Zakim has left #wot-profile