11:08:40 RRSAgent has joined #wot-profile 11:08:40 logging to https://www.w3.org/2022/06/29-wot-profile-irc 11:08:44 meeting: WoT Profile 11:08:47 mlagally has joined #wot-profile 11:09:03 zakim, who is here? 11:09:03 Present: (no one) 11:09:05 On IRC I see mlagally, RRSAgent, Zakim, McCool, Mizushima, kaz, benfrancis 11:09:07 present+ Michael_Lagally, Michael_McCool, Tomoaki_Mizushima, Kaz_Ashimura 11:09:09 chair: Lagally 11:11:50 topic: minutes 11:11:58 scribenick: McCool 11:12:02 ml: review of 06/22 minutes 11:12:19 i|review|-> https://www.w3.org/2022/06/22-wot-profile-minutes.html June-22| 11:13:09 ml: note that I cleaned up and merged some things we decided on last week 11:14:18 s/topic: minutes/topic: Agenda/ 11:14:27 s|-> https://www.w3.org/2022/06/22-wot-profile-minutes.html June-22|| 11:14:44 topic: Minutes 11:14:56 -> https://www.w3.org/2022/06/22-wot-profile-minutes.html June-22 11:15:37 ml: reviewed a lot of issues at a high level, will drill down on some of these a bit more today 11:16:40 mm: also, for the agenda, suggest we don't spend too much time on length limits, other things are higher priority 11:16:44 ml: agree 11:16:51 ml: publish if no objections? 11:16:58 ... hearing none, will publish 11:17:13 topic: PR 198 11:17:20 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_June_29th.2C_2022 11:17:22 https://github.com/w3c/wot-profile/pull/235 11:18:21 s/PR 198/PR 235/ 11:18:26 s/https/-> https/ 11:18:27 ml: event payload format, has a lot of merge conflict, have created new PR 235 11:18:45 s/235/235 PR 235 - CloudEvents as message payload format for WebHooks/ 11:18:47 ... note there is however a lot of useful discussion under the old PR 11:18:57 ... will close, but will link back to it from the new PR 11:19:45 i|event payload|-> https://github.com/w3c/wot-profile/pull/198 original PR 198 (closed due to merge conflicts) - WIP: event payload format| 11:19:48 ml: issue with multiple devices talking to the same cloud endpoint, single listener, multiple "speakers" 11:20:28 ... message has to convey device; also timestamp, affordance (event source), data payload, etc. 11:20:52 ... naive approach would be to define a JSON schema for the message format 11:21:19 ... but if you look at what cloud companies do, there is already a format for this purpose 11:21:55 mm: is this the *only* format being used? 11:22:32 ml: not aware of any other public standard used broadly 11:24:00 mm: note this constrains not onl the Things but the cloud endpoints 11:24:17 ml: correct, this is for webhooks also (not just SSE) 11:24:45 s/(not just SSE)// 11:26:45 mm: a little worried about the formality of the cloud events spec, also versioning 11:26:52 ml: is versioned 11:27:18 mm: ok, but I think we should also have enough information in our spec to be clear even if the cloud events spec goes away 11:28:37 mm: ok with merging if others are 11:30:03 mm: what is the minimum implementation? 11:30:21 ml: less than ten attributes in a message 11:31:12 mm: actually, count only 5 attributes that are mandatory 11:31:46 ml: if no other questions, will merge 11:31:52 topic: PR 233 11:32:01 ml: constrained set of link relation types 11:34:11 mm: also think we may want to limit the media types 11:34:21 ml: and also make the type mandatory 11:34:50 s/PR 233/Issue 233/ 11:35:07 i|constrained|-> https://github.com/w3c/wot-profile/issues/233 Issue 233 - Define a constrained set of link relation types| 11:35:45 mm: also, tm:* relations are allowed? Are TMs covered by profiles? 11:36:25 mm: also, TMs are definitely going into the TD spec now 11:38:49 ml: not clear about manifest 11:38:58 ... which refers to a UI 11:41:05 mm: ben may have some input on, WebThings tends to return HTML for affordances unless requested otherwise 11:42:20 mm: if we DO support manifest, I think we should be specific about the type is points to 11:42:28 ml: but we can leave it out for now 11:42:31 mm: agree 11:42:52 -> https://w3c.github.io/wot-thing-description/#link TD draft - 5.3.4.1 Link 11:42:56 ml: also "alternate" has a number of examples of different representations 11:44:38 mm: my preference would be to insist on JSON-LD serializations of TDs in profiles 11:45:37 ml: so "alternate" does not make sense 11:45:47 ... let me make a note about that 11:48:21 ml: anyway, these six are the suggested types 11:48:47 ... I will do a PR if there are no other volunteers 11:49:01 topic: issue 232 11:49:09 ml: minimum set of supported languages 11:49:38 ml: could look at locales supported by Java 11:50:36 mm: might also want to look at browser support, take the intersection 11:52:58 ... suggest we ask i18n team, and can also label, tag @aphillips, etc. 11:56:54 topic: cleanup 11:57:07 ml: merged impl report, that is done 11:57:42 ml: PR 207 updates the JSON Schema ref 11:58:07 i|PR 207|subtopic: PR 207| 11:58:22 i|PR 207|-> https://github.com/w3c/wot-profile/pull/207 PR 207 - updating JSON Schema Validation reference| 11:58:38 mm: just make sure this is not changing from the version used in the TD spec 11:58:49 i|merged impl|subtopic: PR 227| 11:59:07 i|merged impl|-> https://github.com/w3c/wot-profile/pull/227 PR 227 - Update Implementation Report| 11:59:16 ... I'm not even sure we need this in profiles if TD specifies it 11:59:30 rrsagent, make log public 11:59:34 rrsagent, draft minutes 11:59:34 I have made the request to generate https://www.w3.org/2022/06/29-wot-profile-minutes.html kaz 12:00:44 [adjourned] 12:00:46 rrsagent, draft minutes 12:00:46 I have made the request to generate https://www.w3.org/2022/06/29-wot-profile-minutes.html kaz 12:17:23 q+ 12:21:58 mlagally_ has joined #wot-profile 13:12:24 Mizushima has left #wot-profile 14:42:35 Zakim has left #wot-profile 15:03:13 kaz has joined #wot-profile