11:59:54 RRSAgent has joined #wot-profile 11:59:54 logging to https://www.w3.org/2022/02/02-wot-profile-irc 11:59:59 meeting: WoT Profile 12:01:33 mlagally has joined #wot-profile 12:02:49 present+ Kaz_Ashimura, Farshid_Tavakolizadeh, Michael_McCool, Ben_Francis 12:02:56 present+ Michael_Lagally 12:04:11 FarshidT has joined #wot-profile 12:04:32 Mizushima has joined #wot-profile 12:05:28 McCool_ has joined #wot-profile 12:05:51 present+ Tomoaki_Mizushima 12:06:22 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.2F_Profile_-_Feb_2nd.2C_2022 12:06:33 for the agenda, would like to discuss self-description fixes... 12:06:33 present+ Ryuichi_Matsukura 12:06:44 https://github.com/w3c/wot-discovery/pull/269 12:07:12 ... addressing https://github.com/w3c/wot-discovery/issues/263 12:07:25 i/for the agenda/topic: Agenda/ 12:07:45 i|for the agenda|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.2F_Profile_-_Feb_2nd.2C_2022 Agenda for today| 12:07:47 ... and also https://github.com/w3c/wot-profile/pull/121 12:08:27 present+ Sebastian_Kaebisch 12:09:40 topic: Minutes review 12:10:33 ml: will upload the summary document after the call 12:11:37 ... no objections to publishing 12:12:30 ... now taking a look at minutes from 24th 12:13:24 i/for the agenda/scribenick: McCool_/ 12:13:39 i/will upload/scribenick: FarshidT/ 12:13:58 ... no objections to publishing 12:13:59 https://github.com/w3c/wot-usecases/pull/179/files 12:14:03 topic: Requirements 12:14:48 Profile requirements: https://github.com/w3c/wot-usecases/pull/179 12:15:06 ml: added identifications of profiles 12:15:30 ... will go ahead and merge it 12:16:20 rrsagent, make log public 12:16:23 rrsagent, draft minutes 12:16:23 I have made the request to generate https://www.w3.org/2022/02/02-wot-profile-minutes.html kaz 12:17:03 rrsagent, draft minutes 12:17:03 I have made the request to generate https://www.w3.org/2022/02/02-wot-profile-minutes.html kaz 12:17:27 s/will go ahead and merge it/continue review after identification of profiles/ 12:18:12 s/identifications/identification/ 12:18:31 chair: Lagall 12:18:45 s/chair: Lagall/chair: Lagally/ 12:18:48 rrsagent, draft minutes 12:18:48 I have made the request to generate https://www.w3.org/2022/02/02-wot-profile-minutes.html kaz 12:19:12 ml: reviewing defining a finite set of features 12:19:37 q+ 12:20:14 dape has joined #wot-profile 12:20:35 bf: things should be allowed to define beyond the finite set of features 12:22:07 mm: basic functionality should be covered 12:24:05 bf: there could be forms for both ws and http. A consumer that doesn't support one, can ignore it. 12:24:45 s/features/protocols/ 12:25:08 ack m 12:25:18 ml: recorded Ben's comment. Discussion may continue offline. 12:26:15 q+ 12:26:30 ml: https://github.com/w3c/wot-profile/issues/163 12:26:58 subtopic: limit resource consumption 12:27:12 sk: not sure why Siemens is mentioned here 12:27:14 q+ 12:27:50 ack s 12:27:57 s/ml: reviewing defining a finite set of features/subtopic: defining a finite set of features/ 12:28:13 present+ Daniel_Peintner 12:28:18 rrsagent, draft minutes 12:28:18 I have made the request to generate https://www.w3.org/2022/02/02-wot-profile-minutes.html kaz 12:29:03 sk: The constraints are not needed 12:29:25 q? 12:29:28 ack b 12:30:15 bf: it's okay to have a profile to define resource constraints. But it shouldn't be here. 12:31:23 ryuichi has joined #wot-profile 12:31:43 s/be here/apply to all profiles/ 12:32:42 q+ 12:33:09 subtopic: security and privacy best practices 12:33:19 q? 12:34:43 mm: security guidelines not yet published. Currently not clear how to define security definitions that apply to all use cases. 12:36:50 cris has joined #wot-profile 12:38:31 present+ Cristiano_Aguzzi 12:38:57 subtopic: developer mode 12:39:55 bf: it implies that nosec is disallowed, but there are very valid use cases for it 12:40:56 mm: it overlaps with best practices. nosec can be used if use case demands it. 12:42:02 ca: how can we test this if nosec is conditional and sometimes valid? 12:43:38 topic: Requirements 12:43:51 ml: comments added and merged https://github.com/w3c/wot-usecases/pull/181 12:44:32 q+ 12:45:01 ack m 12:45:03 ack b 12:45:28 ... to have a conversation next week about objections to individual goals without conflicting with requirements of other organizations 12:46:06 bf: we don't need to cover everything in this (version of) document 12:46:48 topic: Modelling of multiple things as Thing Link 12:47:29 https://github.com/w3c/wot-profile/issues/112 12:47:44 mm: there is PR on discovery side: https://github.com/w3c/wot-discovery/pull/269 12:48:38 ... Thing Link is a TD that only links to other TDs 12:48:48 q+ 12:51:20 bf: this doesn't solve our self-discovery problem. What use case is this PR solving? 12:51:59 q+ 12:56:22 bf: the alternative way of using directories to list TDs adds additional implementation complexity 12:56:40 mm: it would be just about the listing, not the whole TDD API 12:59:36 rrsagent, draft minutes 12:59:36 I have made the request to generate https://www.w3.org/2022/02/02-wot-profile-minutes.html kaz 12:59:45 q+ 13:00:34 ft: listing may also require pagination 13:01:26 we should move to the main call 13:02:03 bf: I don't think the well-known URL is that useful because the information may already be known. It rathers adds limitations 13:02:51 [adjourned] 13:02:53 rrsagent, draft minutes 13:02:53 I have made the request to generate https://www.w3.org/2022/02/02-wot-profile-minutes.html kaz 15:00:31 Zakim has left #wot-profile 17:01:48 sebastian has joined #wot-profile