12:00:54 RRSAgent has joined #wot-profile 12:00:54 logging to https://www.w3.org/2022/02/23-wot-profile-irc 12:01:10 Ege has joined #wot-profile 12:01:33 meeting: WoT Profile 12:01:48 present+ Kaz_Ashimura, Ege_Korkan, Michael_Lagally 12:02:46 Mizushima has joined #wot-profile 12:06:29 invite zakim 12:07:25 McCool has joined #wot-profile 12:08:13 https://www.w3.org/2001/12/zakim-irc-bot.html 12:08:55 zakim, start meeting 12:08:55 RRSAgent, make logs Public 12:08:56 please title this meeting ("meeting: ..."), mlagally 12:09:08 meetin: WoT Usecases 12:09:15 meeting: WoT Usecases 12:09:27 s/Usecases/Profile/ 12:09:37 Topic: Agenda 12:10:43 ml: I would like to focus on the eventing model 12:11:12 present+ Ben_Francis, Michael_McCool, Ryuichi_Matsukura, Sebastian_Kaebisch, Tomoaki_Mizushima 12:11:51 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_Feb_23rd.2C_2022 12:11:53 topic: minute review 12:12:03 |minute review|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_Feb_23rd.2C_2022 agenda| 12:12:10 i|minute review|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_Feb_23rd.2C_2022 agenda| 12:12:20 ryuichi has joined #wot-profile 12:12:22 s/minute review/minutes review/ 12:12:35 ->https://www.w3.org/2022/02/16-wot-profile-minutes.html Feb-16 12:12:53 ml: anything to change? 12:13:33 topic: OOTBI 12:14:07 ml: i have added link to h-2020 project 12:15:03 dape has joined #wot-profile 12:15:03 i/OOTBI/(typo fixed, and minutes approved)/ 12:15:16 ml: i have added interoperability definitions into the text 12:15:23 s/OOTBI/Out of the Box Interoperability/ 12:15:32 rrsagent, make log public 12:15:36 rrsagent, draft minutes 12:15:36 I have made the request to generate https://www.w3.org/2022/02/23-wot-profile-minutes.html kaz 12:15:54 present+ Daniel_Peintner 12:15:56 rrsagent, draft minutes 12:15:56 I have made the request to generate https://www.w3.org/2022/02/23-wot-profile-minutes.html kaz 12:16:04 ml: we can do the editorial fixes later after merging 12:16:42 i|I have added link|-> https://github.com/w3c/wot-profile/pull/176 PR 176 - OOTBI section| 12:17:10 chair: Lagally 12:17:32 (PR 176 merged) 12:18:01 topic: requirements 12:18:16 ml: I have added the accepted requirements with the supporters in the comments 12:18:32 i|have add|-> https://github.com/w3c/wot-profile/pull/175 PR 175 - incorporating accepted requirements| 12:18:33 ml: We can delete them later as well 12:19:18 ml: we should polish the text later 12:19:47 mm: I think the editors note is important 12:21:06 q+ 12:21:49 ack m 12:22:33 ml: I am ok to change industrial vs home 12:23:33 q? 12:24:03 ml: other comments? 12:24:13 bf: generally use cases and requirements are another document in w3c specs 12:24:56 topic: PR 130 12:24:58 s/another document/described by a separate document/ 12:25:14 s/w3c specs/w3c specs but we can deal with that later./ 12:25:31 i/PR 130/(merged)/ 12:25:52 mm: I agree with Ben that we should not have two use cases to maintain 12:26:05 i|agree|-> https://github.com/w3c/wot-profile/pull/130 PR 130 -Add Use cases section| 12:27:16 q+ 12:27:47 mm: requirements should be driven from use cases. thus, it is better to have these in the use cases document so that internal links work better 12:28:03 ml: this is not a new use case 12:29:17 bf: I am ok with the text except for the last sentence 12:29:42 q+ 12:30:19 bf: profile does not enable cross protocol interoparability so the text is misleading. You will need custom adapters 12:30:25 ack b 12:30:47 ml: The text says enhancing 12:31:07 q? 12:31:20 ack 12:31:21 ek: I also agree with mccool 12:31:21 ack m 12:32:06 ml: can we approve this MR then? 12:32:16 (group agrees) 12:32:28 topic: PR 109 12:32:45 ml: I was removing rfc assertions 12:33:06 mm: we should rerun the tool then, which will remove some assertions 12:35:15 q+ 12:35:48 ml: mandating json schema makes a lot of sense 12:35:50 q+ 12:36:37 q+ 12:36:37 kaz: pr 130 to be merged after fixing the sentences right? 12:36:39 ack k 12:36:53 s/sentences/3 sentences/ 12:36:54 [[ 12:36:55 separation of the interaction model and the protocol binding. 12:36:55 This separation makes it possible to define common protocol agnostic 12:36:55 rules that enhance interoperability between different protocols. 12:36:56 ]] 12:37:00 @@@ to be moved 12:37:04 q? 12:37:41 i|I was re|-> https://github.com/w3c/wot-profile/pull/130 PR 130 - Add Use cases section| 12:38:02 ack e 12:40:09 ek: there is an annoying problem with the format keyword that different json schema implementations use the formats in different "lazyness" levels, like checking @ sign for email or doing full regex validation 12:40:22 mm: this is just a cleanup though 12:40:43 mm: please create a separate issue on that 12:40:57 topic: event model 12:41:33 q+ 12:43:19 i|I was removing|-> https://github.com/w3c/wot-profile/pull/109 PR 109 - preparing implementation report - cleanup assertions| 12:43:40 ml: there are TDs from TUM, Siemens and NHK that use longpoll 12:43:56 q+ 12:44:24 ack m 12:44:52 mm: if the Consumer cannot have the server functionality 12:45:13 ml: I would approach this in another way, we can have a conditional language 12:46:13 q+ 12:46:18 ack b 12:47:05 bf: we just merged a requirement saying that consumer must be able to interact with all interactions 12:47:26 bf: so if the Thing has webhook as the single event approach, some consumers cannot use it 12:47:36 bf: so I think that for this we would need a separate profile for this 12:47:49 mm: we can also define a profile without events 12:48:24 q+ 12:48:58 mm: we have multiple options, let's list them and weigh pros and cons 12:49:20 mm: we can have fallback 12:50:41 mm: like if the Thing cannot offer webhooks, it must offer sse in the worst case 12:53:12 q+ 12:53:50 bf: having server capability requirement on consumers imply change for all interactions 12:55:00 mm: let's open an issue for discussion 12:55:11 bf: we have already 6 issues on this topic, another issue will not help 12:55:20 mm: let's pick one in this case 12:55:23 q? 12:55:31 ml: I think we should list them 12:55:32 ack m 12:55:57 q+ 12:56:02 ack e 12:57:28 ek: I think that having options for consumers or fallbacks, increase implementation complexity for consumers 12:57:41 ack k 12:57:57 ... not having events means that if my use case have events, I will not be able to use this profile and write non-profile TDs 12:58:09 topic: PR 117 12:58:31 ml: any objections to merge? 12:58:39 ml: (merges) 12:58:42 ml: aob? 12:58:48 adjourned 12:58:56 i/PR 117/kaz: given we're out of time, I agree we'll continue the discussion next week, but we should think about how to proceed as well, e.g., need another use case? need a concrete implementation?/ 12:59:49 i|any obj|-> https://github.com/w3c/wot-profile/pull/117 PR 117 - Add Identifier section to Core Profile - closes #111| 13:00:01 rrsagent, draft minutes 13:00:01 I have made the request to generate https://www.w3.org/2022/02/23-wot-profile-minutes.html kaz 14:00:53 sebastian has joined #wot-profile 14:13:21 Mizushima has left #wot-profile 15:07:25 Zakim has left #wot-profile