14:58:31 RRSAgent has joined #wot-discovery 14:58:31 logging to https://www.w3.org/2022/02/07-wot-discovery-irc 15:02:59 ktoumura has joined #wot-discovery 15:03:31 meeting: WoT Discovery 15:03:48 present+ Kaz_Ashimura, Farshid_Tavakolizadeh, Jan_Romann, Kunihiko_Toumura 15:03:53 regrets+ Christian 15:03:57 chair: McCool 15:04:16 Mizushima has joined #wot-discovery 15:05:53 present+ Michael_McCool 15:06:27 present+ Tomoaki_Mizushima 15:07:41 cris has joined #wot-discovery 15:07:43 present+ William_Holroyd, Cristiano_Aguzzi 15:09:17 acimmino has joined #wot-discovery 15:09:21 present+ Andrea_Cimmino 15:09:44 Ege has joined #wot-discovery 15:09:49 topic: previous minutes 15:10:07 mc: talked about feature freeze 15:10:10 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#7_February_2022 15:10:22 topic: Guest 15:10:33 s/Guest/New participant/ 15:10:34 kaz: we have William as a new member 15:10:37 cperey has joined #wot-discovery 15:10:44 Sorry to be late 15:11:10 present+ Christine_Perey 15:11:25 wlliam: I'm working on client and cloud software at Homobo 15:11:50 mc: thank you for checking with us, here we are working on discovery 15:12:00 s/Homobo/Lenovo/ 15:12:14 Thank you, Kaz! 15:12:17 ... but on Wednesday we have a broader call with all the Task Forces 15:12:59 q+ 15:13:05 mc: we are on a clean up phase 15:13:46 McCool_ has joined #wot-discovery 15:13:47 wholroyd has joined #wot-discovery 15:14:03 topic: minutes review 15:14:17 mc: we have just one section, it is not usual 15:14:32 ... probably we forgot to add subtopics 15:14:42 i|we have|-> https://www.w3.org/2022/01/31-wot-discovery-minutes.html Jan-31| 15:14:49 15:15:33 ... we discussed about ThingLink and use cases 15:15:57 ... remember that we had a resolution for freeze everything except the ThingLink topic 15:16:23 ... minutes oks, please fix the sub topics 15:16:43 topic: Pull Requests 15:16:54 mc: don't worry about 256 is informative 15:17:05 subtopic: PR 269 15:17:44 FarshidT has joined #wot-discovery 15:17:55 mc: basically we have a discovery process composed by an introduction and an exploration phase 15:18:52 ... we identified a corner case that we want to cover analyzing the /.well-known introduction mechanism 15:19:08 ... in particular, it does not cover having multiple TDs on a single enpoint 15:19:19 present+ Ege_Korkan 15:19:29 rrsagent, make log public 15:19:34 rrsagent, draft minutes 15:19:34 I have made the request to generate https://www.w3.org/2022/02/07-wot-discovery-minutes.html kaz 15:19:34 ... for example an outlet strip which has different Things for each outlet 15:21:11 william: is this something about handling sub-things from a root component? 15:21:13 i|basically we|-> https://github.com/w3c/wot-discovery/pull/269 PR 269 - Permit use of TD Links for Self-Description of Multiple Endpoints| 15:21:44 mc: I played a bit with it and I think it is better to model does sub components as sub things not sub affordances. 15:21:55 s/topic: previous minutes/ 15:22:07 s/mc: talked about feature freeze// 15:22:10 rrsagent, draft minutes 15:22:10 I have made the request to generate https://www.w3.org/2022/02/07-wot-discovery-minutes.html kaz 15:22:17 ... back to the use case we have a Directory API service but it is not really suited for this small static TDs 15:22:33 i/don't worry about 256/subtopic: PR 256/ 15:23:54 i|don't worry about 256|-> https://github.com/w3c/wot-discovery/issues/256 Issue 256 - Small fixes on Creation| 15:24:01 s/PR 256/Issue 256/ 15:24:20 q+ wholroyd 15:24:27 ack k 15:24:29 akc w 15:24:51 s/akc w// 15:24:52 ack w 15:25:35 rrsagent, draft minutes 15:25:35 I have made the request to generate https://www.w3.org/2022/02/07-wot-discovery-minutes.html kaz 15:25:39 mc: to get a better understanding of the use-case let me review comments 15:26:25 ... ben concerns was that he can only point to a directory was to use a ./well-known endpoint 15:26:41 ... adding a thing link might introduce complexity to the client 15:27:33 ... we might not put the Discovery API optional 15:28:41 ... also link should not contain affordances 15:29:25 ... a Thing collection only apply to thing models 15:29:49 ... it is flatten in thing models 15:30:29 farshid: Ben's concern is not about parse the list, but more about the fact the registration api is mandatory 15:30:37 ... then also understand the TDs 15:30:46 mc: I agree the read-only thing should be fixed 15:31:25 ... the issue about understanding the TD in the TM is normative a consumer can just cherry pick what it needs. 15:31:46 s/in the/if the/ 15:32:00 farshid: yes, but still it needs to read the base path 15:32:06 mc: yes but reasonable 15:32:33 q+ 15:32:50 Multiple Responses from Peer-to-Peer Discovery: https://github.com/w3c/wot-discovery/issues/249 15:32:50 farshid: I can work on the read-only point 15:33:17 ... please refer to the issue above 15:33:46 mc: the title is not perfect 15:33:53 ... we should fork to another one 15:34:31 ... returning an array from the .well-known/ should cover the issue 15:34:50 farshid: actually the spec from well known allow that 15:36:34 mc: the ThingLink was equivalent to the array 15:36:48 ... just because other introduction methods return always a TD 15:38:00 ... partial thing description directory might be also impractical implementation side 15:40:28 ... so we have the option of making the TDD API has everything optional 15:40:38 ... but only read operations mandatory 15:40:59 TD is Thing Directory, correct? 15:41:09 ... still need two fetches 15:41:12 TD: Thing Description 15:41:50 TDD: Thing Description Directory !! 15:41:53 ... but a good nonetheless 15:42:13 :) we are full of similar acronyms 15:43:16 mc: I would move listing chaper outside 15:43:59 ... together with retrieval 15:44:09 farshid: retrival might be not so critical 15:44:35 ... it might add complexity to the implementation 15:44:51 mc: point taken 15:45:19 ... but listing and retrieval go together 15:45:57 ... is the TM requiring something? 15:46:17 farshid: we have a tm require 15:46:21 ... I can do the PR 15:47:35 q? 15:51:58 cris: I'm glad that we are introducing this 15:52:11 ... but we are not covering TM model compositions 15:52:43 mc: I think discovery should just strictly focus on flat lists of TDs 15:52:57 ... plus we are missing a formal process described in the spec 15:54:01 s/formal process/formal client discovery/ 15:54:13 mc: I can work on it 15:54:30 ... but we cannot add normative statements 15:55:42 rrsagent, draft minutes 15:55:42 I have made the request to generate https://www.w3.org/2022/02/07-wot-discovery-minutes.html kaz 15:57:48 proposal: resolve issue https://github.com/w3c/wot-discovery/issues/272 as well before normative feature freeze 15:58:10 Reading this spec is like trying to learn English by reading a dictionary 15:58:21 What is the best way to propose a series of questions to resolve some issues I have 15:58:56 resolution: resolve issue https://github.com/w3c/wot-discovery/issues/272 as well before normative feature freeze 15:58:57 ...where issues I have is things I don't understand yet 15:59:27 regarding wholroyd's point, I will also try to fill in some missing informative sections as part of resolving issue #272 15:59:56 @wholroyd, would be best to search (https://github.com/w3c/wot-discovery/issues) in open/closed issues and file new issues for each remaining question. 16:00:31 [adjourned] 16:00:39 rrsagent, draft minutes 16:00:39 I have made the request to generate https://www.w3.org/2022/02/07-wot-discovery-minutes.html kaz 16:01:53 Is it fine to pile a bunch of questions into a single issue, or break them out?