10:53:39 <RRSAgent> RRSAgent has joined #wot-profile
10:53:39 <RRSAgent> logging to https://www.w3.org/2022/04/27-wot-profile-irc
10:55:10 <kaz> meeting: WoT Profile
10:55:55 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_April_27th.2C_2022
11:01:03 <mlagally> mlagally has joined #wot-profile
11:01:13 <Mizushima> Mizushima has joined #wot-profile
11:04:27 <kaz> present+ Kaz_Ashimura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima
11:04:38 <ryuichi> ryuichi has joined #wot-profile
11:07:17 <kaz> scribenick: kaz
11:07:26 <kaz> topic: Minutes
11:08:27 <kaz> -> https://www.w3.org/2022/04/06-wot-profile-minutes.html Apr-6
11:08:34 <kaz> ml: (goes through the minutes)
11:08:47 <kaz> ... have the discussion done by the Security TF?
11:08:50 <kaz> mm: not yet
11:09:02 <kaz> ... will add it to the agenda for the next week now
11:09:07 <mlagally> https://github.com/w3c/wot-profile/issues/6
11:09:14 <mlagally> https://github.com/w3c/wot-profile/pull/87
11:09:41 <McCool_> McCool_ has joined #wot-profile
11:09:56 <kaz> https://github.com/w3c/wot-profile/issues/6
11:10:01 <kaz> https://github.com/w3c/wot-profile/pull/87
11:10:32 <kaz> mm: btw, mandating HTTPS might be difficult
11:11:56 <kaz> ... we're looking at several things
11:12:36 <kaz> ... but can't mandate HTTPS, e.g., for local networks
11:13:23 <kaz> ml: what we could do is demanding something different
11:13:31 <kaz> mm: it's a complicated object
11:13:59 <kaz> ... requiring TLS for home devices would get push back
11:14:31 <kaz> ... it's under discussion by TD as well
11:14:56 <kaz> ... the problem is that the other approaches also have problems
11:15:47 <kaz> ... note that we need to add an additional section on Security and Privacy too
11:16:26 <kaz> regrets+ Sebastian
11:17:04 <McCool_> https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#Upcoming
11:17:32 <kaz> i|Upcom|-> https://github.com/w3c/wot-profile/issues/182 Issue 182 - New section: Security considerations|
11:17:56 <kaz> mm: just added the discussion to the next agenda for the Security TF
11:19:38 <kaz> ... OK with the minutes themselves
11:19:40 <kaz> ml: ok
11:19:42 <kaz> approved
11:19:58 <kaz> topic: Publication
11:20:09 <kaz> -> https://github.com/w3c/wot-profile/issues?q=is%3Aissue+is%3Aopen+label%3A%22blocks+publication%22 Publication blockers
11:20:40 <kaz> mm: does that mean we've not got consensus?
11:20:52 <kaz> ml: not for all
11:21:19 <kaz> ... also some of the issues can be deferred
11:22:48 <kaz> ... (removes "blocks publication" label from issue 190)
11:23:08 <kaz> i/removes/subtopic: Issue 190/
11:23:23 <kaz> i|remove|-> https://github.com/w3c/wot-profile/issues/190 Issue 190 - Consider splitting Use Cases & Requirements out into a separate document|
11:23:30 <kaz> subtopic: Issue 150
11:23:40 <kaz> s/150/158/
11:24:01 <kaz> -> https://github.com/w3c/wot-profile/issues/158 Issue 158 - Define a protocol binding for readmultipleproperties?
11:24:11 <kaz> mm: not a blocker but an improvement
11:24:23 <kaz> ml: ok
11:24:26 <kaz> ... (removes the label)
11:25:44 <kaz> subtopic: Issue 151
11:25:55 <kaz> -> https://github.com/w3c/wot-profile/issues/151 Issue 151 - Consolidate Error responses
11:26:11 <kaz> mm: we don't need to list all the detailed error responses there
11:26:32 <kaz> ... also should we handle error 3xx ?
11:26:49 <kaz> ml: (shows the HTTP error codes)
11:27:26 <kaz> -> https://en.wikipedia.org/wiki/List_of_HTTP_status_codes List of HTTP status codes
11:29:03 <dape> dape has joined #wot-profile
11:29:13 <kaz> q+
11:30:17 <kaz> mm: not all the browsers handle the error code properly
11:31:21 <dape> q+
11:31:27 <kaz> kaz: we should be consistent with the other SDOs' error codes
11:31:28 <kaz> ack k
11:31:32 <benfrancis> benfrancis has joined #wot-profile
11:31:39 <kaz> ... so some survey would be useful
11:32:05 <kaz> q?
11:32:23 <kaz> present+ Daniel_Peintner
11:32:50 <kaz> mm: should be consistent with browsers too
11:33:11 <kaz> dp: not sure how to deal with the details here
11:33:27 <benfrancis> Sorry I'm not able to join the call as I'm out of the office today, but lurking in IRC.
11:33:45 <kaz> ... the details on error handling subject to change
11:33:55 <kaz> regrets+ Ben
11:34:48 <McCool_> q+
11:35:10 <dape> ack dape
11:35:15 <kaz> mm: two possibilities there
11:35:32 <kaz> ... one extreme which is consistent
11:35:55 <kaz> ... and the other is consistent with the current browsers
11:36:27 <kaz> q?
11:36:32 <kaz> ack m
11:36:34 <kaz> q+
11:36:58 <kaz> ack k
11:37:19 <kaz> kaz: btw, the error codes themselves usually will be returned from the Web server
11:37:38 <kaz> ... so we need to see the Web servers' behavior (as well). right?
11:38:01 <kaz> mm: yeah, browser behavior and the codes
11:38:02 <Ege> Ege has joined #wot-profile
11:38:05 <Ege> q+
11:38:16 <kaz> present+ Ege_Korkan
11:38:27 <kaz> ... standard codes as errors
11:38:44 <kaz> ek: this is about the profile for HTTP. right?
11:38:48 <kaz> ml: yes
11:39:18 <kaz> ek: I myself don't handle 3xx codes within my implementations
11:40:06 <kaz> ... we should not block the client based on the errors
11:40:18 <kaz> mm: the consumers should handle it
11:41:26 <kaz> ek: 301 should be an error for WoT, though
11:41:38 <kaz> ml: let's do some quick assessment
11:43:53 <kaz> ... should be handled as errors?
11:43:57 <kaz> ... 300: no
11:44:05 <kaz> ... 301: no
11:44:10 <kaz> ... 302: no
11:44:36 <kaz> q+
11:44:38 <kaz> ack e
11:44:51 <kaz> dp: probably "no" for all?
11:45:28 <kaz> mm: Consumer may consider a 3xx code as an error
11:45:30 <kaz> q?
11:46:44 <kaz> kaz: probably we should look into concrete scenarios a bit more
11:47:08 <McCool_> https://www.eurovps.com/blog/300-errors/
11:47:16 <McCool_> q+
11:47:24 <kaz> ack k
11:47:47 <kaz> kaz: we don't need to describe it using the ordinary use case template
11:48:09 <kaz> ... but should clarify the situation and scenario with the WoT components
11:48:25 <kaz> ... i.e., Consumer - intermediary - Thing
11:49:09 <kaz> mm: we could look into some blogs on 3xx errors as well
11:49:21 <Ege> q+
11:49:45 <kaz> ack m
11:50:14 <kaz> ek: what about proxy setting?
11:50:30 <kaz> kaz: would suggest we think about several possible settings including that
11:51:13 <kaz> ek: would ask Ben also for opinions
11:51:42 <kaz> q+
11:51:44 <kaz> ack e
11:52:46 <kaz> kaz: we should see what should be done for those who have been participating in Plugfests
11:53:02 <kaz> ... e.g., WebThing, ECHONET, OPC-UA, ...
11:53:38 <kaz> ml: can we ask people about this during the Plugfest call?
11:53:49 <kaz> mm: let me add that to the agenda
11:54:55 <kaz> topic: PRs
11:54:57 <benfrancis> Note that for a 401 Unauthorized error code there's a discussion about how a consumer should react to that as part of WoT Discovery https://github.com/w3c/wot-discovery/issues/135. This is an important part of the discovery process for Consumers to get access to Things which require authentication.
11:54:57 <benfrancis> If WoT Discovery solves that, then we may want to refer to that text. See https://github.com/w3c/wot-profile/pull/121 for how discovery fits into WoT Profile.
11:55:05 <kaz> subtopic: PR 192
11:55:26 <kaz> -> https://github.com/w3c/wot-profile/pull/192 PR 192 - WIP: Webhook HTTP profile
11:55:47 <kaz> ml: please review the PR
11:56:15 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/192/d41bd09...1ed7c58.html#http-webhook-profile preview diff
11:56:45 <kaz> mm: should have 2 sections
11:57:04 <kaz> ... 1 describes what Web hook is like
11:57:09 <kaz> ... 2. how to use that
11:57:14 <kaz> s/1 d/1. d/
11:57:30 <kaz> ... real question is identifier and payload
11:58:15 <kaz> subtopic: PR 193
11:58:33 <kaz> -> https://github.com/w3c/wot-profile/pull/193 PR 193 - Create Explainer.md
11:58:42 <kaz> mm: just created a draft Explainer for Profile
11:59:13 <kaz> ml: let's merge this (as a starting point)
11:59:15 <kaz> merged
11:59:34 <kaz> ml: we 13 open PRs now
11:59:42 <kaz> ... let's continue the discussion next week
12:00:27 <kaz> subtopic: PR 182
12:00:44 <kaz> -> https://github.com/w3c/wot-profile/pull/181 PR 181 - Implementation Report and Assertion Markup Fixes
12:00:55 <kaz> kaz: need to move to the main call
12:01:00 <kaz> ... so let's discuss it next week
12:01:02 <kaz> [adjourned]
12:01:06 <kaz> rrsagent, make log public
12:01:30 <kaz> rrsagent, draft minutes
12:01:30 <RRSAgent> I have made the request to generate https://www.w3.org/2022/04/27-wot-profile-minutes.html kaz
12:02:20 <Mizushima> Mizushima has left #wot-profile
13:54:14 <Zakim> Zakim has left #wot-profile