11:00:12 RRSAgent has joined #wot-profile 11:00:12 logging to https://www.w3.org/2022/05/04-wot-profile-irc 11:00:17 meeting: WoT Profile 11:00:41 mlagally has joined #wot-profile 11:01:01 McCool_ has joined #wot-profile 11:02:50 chair: Lagally 11:03:12 present+ Kaz_Ashimura, Ege_Korkan, Michael_Lagally, Michael_McCool 11:03:52 Mizushima has joined #wot-profile 11:04:05 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_May_4th.2C_2022 11:04:15 q+ 11:05:01 regrets+ Ben 11:05:08 present+ Tomoaki_Mizushima 11:06:28 q- 11:06:38 scribenick: McCool_ 11:06:52 topic: minutes 27 April 11:07:00 -> https://www.w3.org/2022/04/27-wot-profile-minutes.html Apr-27 11:07:43 mm: have some suggestions for security... 11:07:52 ml: but let's not discuss on this call 11:08:06 ml: last meeting we resolved some issues and PRs 11:08:52 present+ Sebastian_Kaebisch 11:09:17 ml: 401 error issue we didn't really discuss... 11:09:38 mm: we have discussed in discovery, can follow up there, create an issue in profiles if necessary 11:10:21 ml: did some updates on WebHook will talk about today... 11:10:35 mm: any progress on explainer? even just general intro? 11:10:42 ml: not yet, but is a placeholder 11:10:58 ml: anything in the minutes to change? Can we approve? 11:11:05 ... no objections, approve 11:11:11 topic: Publication Blockeres 11:11:22 s/Blockeres/Blockers/ 11:11:51 ml: can close "Describe Key Use Cases" 11:12:11 ... should also look at "close" tag later... 11:13:22 ml: generic issue, "blocker for publication", Just an example, we can close now (#110) 11:13:56 ml: timestamps, Ben has a proposal 11:14:38 ml: issue #90 is not really a blocker in my opinion, is an informative example 11:14:59 mm: agree is useful, but because informative is not technically a blocker 11:15:54 i|can close "|-> https://github.com/w3c/wot-profile/issues?q=is%3Aissue+is%3Aopen+label%3A%22blocks+publication%22 Issues labeled as "blocks publication"| 11:16:00 ml: issue #17 - vocabulary 11:16:19 mm: the issue is really that if there is new vocabulary, it should be in a context files 11:16:59 i|can lose "D|subtopic: Issue 128| 11:17:12 i|can lose "D|-> https://github.com/w3c/wot-profile/issues/128 Issue 128 - Describe key use cases for Profiles| 11:17:19 ... one issue is that if we define new vocab, we should probably use a prefix 11:17:52 i|generic issue|subtopic: Issue 110| 11:18:10 i|generic issue|-> https://github.com/w3c/wot-profile/issues/110 Issue 110 - Blocker for publication| 11:18:27 ml: have 24 blocks issues, and 18 marked as "close" 11:18:50 i|issue #90|subtopic: Issue 90| 11:19:15 i|issue #90|-> https://github.com/w3c/wot-profile/issues/90 Issue 90 - Provide example TD and declarative protocol binding illustration for Core Profile| 11:19:30 rrsagent, make log public 11:19:34 rrsagent, draft minutes 11:19:34 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 11:20:20 ... will look at close issues myself 11:20:58 i|issue #17|subtopic: Issue 17| 11:21:10 i|issue #17|-> https://github.com/w3c/wot-profile/issues/17 Issue 17 - Vocabulary not in TD context| 11:21:38 rrsagent, draft minutes 11:21:38 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 11:21:57 q+ 11:22:04 mm: also ussue #139, we have to avoid triggering a privacy review complaint, problem is the word "global" 11:22:26 ... suggest we use uuidv4, also avoids collisions and privacy issues with metadata in ids 11:23:28 s/ ussue / issue / 11:23:38 i|#139|subtopic: Issue 139| 11:24:06 ... and making use if uuidv4 solves a bunch of problems 11:24:09 i|#139|-> https://github.com/w3c/wot-profile/issues/139 Issue 139 - unique id| 11:24:19 ml: agree, better than developers doing something random 11:24:47 proposal: use uuidv4 for ids: https://datatracker.ietf.org/doc/html/rfc4122 11:25:03 proposal: use uuidv4 for ids: https://datatracker.ietf.org/doc/html/rfc4122 and make ids mandatory 11:25:58 ack k 11:26:06 rrsagent, draft minutes 11:26:06 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 11:26:59 Ege has joined #wot-profile 11:27:05 brb 11:28:31 resolution: use uuidv4 for ids: https://datatracker.ietf.org/doc/html/rfc4122 and make ids mandatory 11:28:46 s/brb// 11:28:48 rrsagent, draft minutes 11:28:48 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 11:29:27 topic: PRs 11:29:46 subtopic: PR #195 11:30:24 i|can close "D|subtopic: Issue 128| 11:30:55 i|can close "D|-> https://github.com/w3c/wot-profile/issues/128 Issue 128 - Describe key use cases for Profiles| 11:31:09 rrsagent, draft minutes 11:31:09 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 11:31:57 ml: example TD for HTTP baseline and HTTP SSE 11:32:07 i|example|-> https://github.com/w3c/wot-profile/pull/195 PR 195 - Example TDs for HTTP Baseline and HTTP SSE profiles| 11:32:09 back 11:32:18 s/back// 11:38:50 mm: issue with units, should probably use qudt, and I have an example in wot-testing 11:39:55 ... it would also be nice to have an easy way to get the "renderable unit" 11:42:01 ml: will create an issue for that: issue #196 11:42:27 subtopic: PR #194 11:42:43 i|PR #194|-> https://github.com/w3c/wot-profile/issues/196 Issue 196 - How to get a renderable unit string?| 11:43:07 ml: adopting proposed language for 3xx errors, that we don't treat them in any special way; are HTTP protocol internal 11:43:15 i|adopting|-> https://github.com/w3c/wot-profile/pull/194 PR 194 - Adopting proposed language from https://github.com/w3c/wot-profile/issues/151| 11:43:31 ... but adds assertions that Thing will not emit 3xx errors 11:45:20 mm: suggest we merge, but raise issues if there is any reason we need to use 3xx 11:46:05 rrsagent, draft minutes 11:46:05 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 11:46:08 ml: also a lot of issues with id duplicates... 11:46:36 mm: numbering of ids is also a pain. But please please don't change now, need to merge my PR first, then we can fix 11:47:13 ml: ok, will merge 11:47:25 ml: (merges PR #194) 11:47:33 subtopic: PR #192 11:47:55 ml: this is for webhooks; not done, but a complete section now 11:48:30 ... be aware there are some whitespace changes but can turn this off in the diff 11:49:59 mm: typo, SEE should be SSE 11:52:32 mm: should perhaps expand what is meant by "scalable", i.e. "can support devices that can disconnect between sending events" 11:52:36 rrsagent, draft minutes 11:52:36 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 11:52:55 ml: still work to do, mentioned in editor's notes 11:53:59 mm: if we merge, I can fix up the assertion markup... 11:54:02 i|this is for w|-> https://github.com/w3c/wot-profile/pull/192 PR 192 - Webhook HTTP profile| 11:54:14 ml: ok to merge if we agree this is not the final version 11:54:46 mm: I am personally fine with merging, ed notes make it clear it is not done 11:55:11 seb: however another issue is the use of "notify", which we don't have in the TD 11:55:24 ... would at the very least be at-risk, need implementations 11:56:35 mm: markup has to be done for other issues 11:56:49 ml: I can also commit to an implementation 11:56:55 seb: so we need one more 11:58:51 mm: I know of devices I want to "describe" that do use webhooks, and that would give us a second "implementation" 11:59:18 ml: is a conflict 11:59:34 mm: how about we agree you can merge after fixing the conflicts, and also the typo 12:00:23 [adjourned] 12:00:33 rrsagent, draft minutes 12:00:33 I have made the request to generate https://www.w3.org/2022/05/04-wot-profile-minutes.html kaz 12:38:25 q+ 12:45:31 q? 12:45:34 q- 13:32:42 Mizushima has left #wot-profile 15:01:12 Zakim has left #wot-profile