10:59:15 <RRSAgent> RRSAgent has joined #wot-profile
10:59:15 <RRSAgent> logging to https://www.w3.org/2022/06/22-wot-profile-irc
11:02:33 <McCool_> McCool_ has joined #wot-profile
11:02:55 <kaz> meeting: WoT Profile
11:05:36 <mlagally> mlagally has joined #wot-profile
11:05:40 <Mizushima> Mizushima has joined #wot-profile
11:05:49 <kaz> present+ Sebastian_Kaebisch
11:07:12 <kaz> present+ Kaz_Ashimura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima
11:07:53 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_June_22th.2C_2022
11:07:58 <kaz> chair: Lagally
11:09:51 <McCool_> topic: minutes
11:10:01 <McCool_> from 06-15
11:10:19 <kaz> -> https://www.w3.org/2022/06/15-wot-profile-minutes.html June-15
11:10:28 <McCool_> ml: PR #203 should be under "Cleanup"
11:10:32 <kaz> i/from/scribenick: McCool_/
11:10:45 <McCool_> ml: then talked about length limits
11:11:18 <McCool_> ... please change section 2 title to "cleanup"
11:11:21 <McCool_> kaz: fixed
11:11:48 <McCool_> ml: and issue #200 should add "Length and size limits"
11:14:10 <McCool_> ml: any objections to appoving?
11:14:16 <McCool_> ... none, approved.
11:14:27 <McCool_> topic: New Issues
11:14:46 <McCool_> ml: not time to discuss all today, but will review, discuss in git
11:15:11 <McCool_> ml: page 1 is all new issues coming in the last month
11:16:46 <McCool_> ml: issue 234 - simplified array syntax
11:17:24 <McCool_> ... issue 233 - need constrained set of link types with unambigous semantics
11:18:30 <McCool_> mm: generally for this I think we want to add only what we need, i.e. start a the small end of the egg
11:18:39 <McCool_> s/start a/start at/
11:18:57 <McCool_> ml: issue 232 - minimum set of supported languages
11:19:21 <kaz> i|issue 234|-> https://github.com/w3c/wot-profile/issues/234 Issue 234 - Simplified array syntax|
11:19:52 <kaz> i|issue 233|-> https://github.com/w3c/wot-profile/issues/233 Issue 233 - Define a constrained set of link relation types|
11:19:52 <McCool_> mm: mostly related to things with displays
11:20:08 <McCool_> ... issue with politics here, which are the "important" languages?
11:20:21 <McCool_> ml: true, but could use Java/javascript ones
11:20:27 <kaz> i|issue 232|-> https://github.com/w3c/wot-profile/issues/232 Issue 232 - Define minimum set of supported languages|
11:20:32 <sebastian> sebastian has joined #wot-profile
11:21:21 <McCool_> ml: issue 231 - bidir heuristics elimination
11:21:26 <sebastian> sorry, I will reconnect later
11:21:43 <McCool_> ml: issue 230 - default language mandatory - not optional
11:21:57 <kaz> i|issue 231|-> https://github.com/w3c/wot-profile/issues/231 Issue 231 - Simplified processing of bidirectional text in multi-language TDs|
11:22:28 <McCool_> ml: issue 229 - webhook protocol binding
11:22:35 <kaz> i|issue 230|-> https://github.com/w3c/wot-profile/issues/230 Issue 230 - Make default language mandatory|
11:23:00 <kaz> i|issue 229|-> https://github.com/w3c/wot-profile/issues/229 Issue 229 - remove http-webhook-profile-protocol-binding-general-2 assertion|
11:23:05 <kaz> rrsagent, make log public
11:23:09 <kaz> rrsagent, draft minutes
11:23:09 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/22-wot-profile-minutes.html kaz
11:24:20 <McCool_> mm: so one weird thing here is what if we have three?  This sets up webhooks as an alternative to SSE, but what if there is a third option, or you don't use it at all?
11:25:10 <McCool_> ml: also, regarding whether baseline is needed or not as part of SSE profile
11:25:31 <McCool_> ml: issue 228 - baseline part of SSE or not
11:25:48 <McCool_> ml: issue 225 - retried events in Webhooks
11:26:13 <McCool_> ... ege is suggesting being stricter
11:26:18 <kaz> i|issue 228|-> https://github.com/w3c/wot-profile/issues/228 Issue 228 - Is HTTP Baseline required for HTTP Webhooks or SSE?|
11:26:48 <kaz> q+
11:27:10 <McCool_> mm: being too strict may make using libraries harder
11:27:13 <McCool_> kaz: agree
11:27:44 <kaz> i|issue 225|-> https://github.com/w3c/wot-profile/issues/225 Issue 225 - Retried events in Webhook Profile|
11:28:01 <McCool_> ... suggest we invite existing implementers and ask about their approach
11:28:21 <McCool_> mm: also, number and spacing of retries does not affect interop, so maybe out of scope
11:28:43 <McCool_> ml: issue 224 - subscribeall security requirements
11:29:45 <kaz> i|issue 224|-> https://github.com/w3c/wot-profile/issues/224 Issue 224 - subscribeallevents security requirements|
11:31:01 <McCool_> mm: generally different access controls for different affordances
11:31:17 <McCool_> ... access controls are a thing, sorry they aren't RESTful
11:31:24 <McCool_> ... guess I should comment
11:31:37 <McCool_> ml: issue 223 - minor, will address
11:31:51 <McCool_> ml: issue 22 - security requirements for webhook consumere
11:32:26 <kaz> i|issue 223|-> https://github.com/w3c/wot-profile/issues/223 Issue 223 - Example 46 is not about subscribeallevents|
11:32:52 <kaz> s/consumere/consumer/
11:33:01 <kaz> s/issue 22 /issue 222 /
11:33:28 <kaz> i|security|-> https://github.com/w3c/wot-profile/issues/222 Issue 222 - Security Requirements for WebHook Consumer|
11:33:56 <McCool_> mm: probably the thing to do here is provide all needed information to support webhook, including things like bearer tokens for access
11:34:20 <McCool_> ml: issue 221 - security schemes are too loose
11:34:53 <McCool_> ml: agree, needs to be more specific
11:35:00 <McCool_> mm: agree, need to narrow
11:35:16 <kaz> i|issue 221|-> https://github.com/w3c/wot-profile/issues/221 Issue 221 - Security Schemes are too loose|
11:36:05 <McCool_> mm: agree, needs to be narrowed to standard HTTP usage
11:37:08 <McCool_> ml: issue 220 - too many security schemes
11:37:18 <McCool_> mm: maybe, digest and basic do overlap
11:37:34 <McCool_> ml: issue 219 - common rules apply to all profiles?
11:37:54 <McCool_> ml: issue 218: JSON Schemas for all profiles?
11:37:56 <kaz> i|issue 220|-> https://github.com/w3c/wot-profile/issues/220 Issue 220 - List of required Security Schemes|
11:37:57 <McCool_> ml: yes
11:38:16 <McCool_> ml: issue 217 - TD version dependency, should say TD 1.1
11:38:24 <kaz> i|issue 219|-> https://github.com/w3c/wot-profile/issues/219 Issue 219 - Common Rules apply to all profiles|
11:38:26 <McCool_> ... agree
11:38:44 <McCool_> ml: issue 215 - explanation would be useful for info model
11:38:47 <McCool_> ... agree
11:38:50 <kaz> i|issue 218|-> https://github.com/w3c/wot-profile/issues/218 Issue 218 - JSON Schemas for profiles|
11:39:12 <McCool_> ml: issue 214 - wrong section/headers - editorial
11:39:20 <kaz> i|issue 217|-> https://github.com/w3c/wot-profile/issues/217 Issue 217 - TD version dependency|
11:39:44 <McCool_> ml: issue 213 - wrong place for use of HTTP profile
11:39:49 <kaz> i|issue 215|-> https://github.com/w3c/wot-profile/issues/215 Issue 215 - Explaining why HTTP Basline Profile has Information Model Constraints|
11:40:11 <McCool_> topic: Event Payload Format for Webhooks
11:40:16 <kaz> i|issue 214|-> https://github.com/w3c/wot-profile/issues/214 Issue 214 - Wrong sections/headers for HTTP profiles|
11:40:42 <kaz> i|issue 213|-> https://github.com/w3c/wot-profile/issues/213 Issue 213 - Wrong place to use HTTP Baseline Profile|
11:42:19 <McCool_> mm: so one comment, issue 222, may mean that we want to add security information to the payload format
11:42:54 <McCool_> ml: may be more for subscription; let me first review PR
11:43:13 <McCool_> ... was based on digital twin use cases
11:43:37 <McCool_> ... need clear way to describe event data
11:44:02 <McCool_> ... relate this to the cloud events specification
11:44:37 <McCool_> ... encodes timestamps, and event source (e.g. affordance)
11:45:30 <McCool_> mm: and also an actual payload?
11:46:24 <McCool_> ml: yes, and also a type
11:46:54 <McCool_> mm: also wondering how we deal with non-JSON data, e.g. an image; do we have to use base-64 encoding, etc?
11:47:30 <McCool_> mm: more generally, ready to merge, or still WIP?
11:47:39 <McCool_> ml: still WIP, need more input
11:48:05 <kaz> i|issue 222|-> https://github.com/w3c/wot-profile/issues/222 Issue 222 (revisited) - Security Requirements for WebHook Consumer|
11:48:16 <McCool_> ... some arguments that need something simpler, could be its own "Digital Twin" profile
11:48:31 <McCool_> topic: Length and Size Limits
11:48:54 <McCool_> ml: looked into a couple of constraints that may be inspiring
11:49:05 <kaz> i|may be more for|-> https://github.com/w3c/wot-profile/pull/198 PR 198 - WIP: event payload format|
11:49:08 <McCool_> ... e.g. URL length, e.g. 255
11:50:02 <kaz> i|looked|-> https://github.com/w3c/wot-profile/issues/200 Issue 200 - Revisit length limits|
11:51:38 <McCool_> mm: random thoughts, particular formats can avoid needing to specify length limits, i.e. if we say ids are uuidv4, length limit for id redundant
11:52:02 <McCool_> ... as for URLs, issue is long query parameters, i.e. encoded SPARQL queries
11:52:12 <McCool_> ... want to avoid breaking things
11:52:47 <McCool_> ... but in general long URLs tend to result from query parameters
11:53:02 <McCool_> topic: New PRs
11:53:45 <McCool_> ml: close stale PR, ECHONET example, close without merging, Ege agreed
11:53:56 <McCool_> ml: closes PR #85
11:54:38 <kaz> zakim, who is on the call?
11:54:38 <Zakim> Present: Sebastian_Kaebisch, Kaz_Ashimura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima
11:55:35 <McCool_> ml: PR #87, placeholder for transport security
11:55:47 <McCool_> mm: merge, we can now update to point at Arch
11:56:06 <McCool_> ml: PR #119, timestamps for event protocol
11:56:20 <McCool_> ... has a merge conflict, need to talk to Ben
11:58:19 <McCool_> mm: problem is terminology is incorrect, I need to make some suggestions
12:00:44 <kaz> i|PR #85|-> https://github.com/w3c/wot-profile/pull/85 PR 85 - Create echonetExampleTD.td.jsonld|
12:00:55 <McCool_> ml: PR 226 and 227
12:01:12 <kaz> i|PR #87|-> https://github.com/w3c/wot-profile/pull/87 PR 87 - Placeholder section on transport security|
12:01:12 <McCool_> mm: suggest we merge 226, then I will fix the merge conflicts in 227 and merge
12:01:19 <McCool_> ml: ok, let's do that
12:01:24 <McCool_> ml: merges 227
12:01:41 <McCool_> s/merges 227/merges 226/
12:01:47 <McCool_> mm: and I will fix 227
12:01:57 <kaz> i|PR #119|-> https://github.com/w3c/wot-profile/pull/119 PR 119 - Add timestamps to event protocol binding - closes #100|
12:02:58 <kaz> i|PR 226 and|-> https://github.com/w3c/wot-profile/pull/226 PR 226 - HTTP Baseline Profile Usage fixes and section ordering|
12:03:37 <kaz> i|and 227|-> https://github.com/w3c/wot-profile/pull/227 PR 227 - Update Implementation Report|
12:03:39 <kaz> [adjourned]
12:03:44 <kaz> rrsagent, make log public
12:03:51 <kaz> rrsagent, draft minutes
12:03:51 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/22-wot-profile-minutes.html kaz
12:23:57 <Mizushima> Mizushima has left #wot-profile
14:00:09 <Zakim> Zakim has left #wot-profile