11:04:52 RRSAgent has joined #wot-script 11:04:52 logging to https://www.w3.org/2021/04/19-wot-script-irc 11:05:04 Meeting: WoT Scripting API 11:05:27 present+ Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi 11:06:27 zkis has joined #wot-script 11:07:14 topic: previous minutes 11:07:15 TOPIC: Previous minutes 11:07:17 -> https://www.w3.org/2021/04/12-wot-script-minutes.html 11:07:24 present+ Zoltan_Kis 11:07:25 present+ Tomoaki_Mizushima, Zoltan_Kis 11:07:32 s/topic: previous minutes// 11:07:43 -> https://www.w3.org/2021/04/12-wot-script-minutes.html Apr-12 11:08:39 daniel: last time we reviewed previous minutes from vf2f and regular meeting 11:09:02 i/last time/scribenick: cris/ 11:09:07 ... we agreed to plan joint calls, but I still need to talk with each taskforce 11:09:49 ... then zoltan proposed to improvements to the discovery api. There's a PR in flight about it. 11:10:03 ... any objection to merge the minutes? 11:10:13 zoltan: they are fine 11:10:23 daniel: minutes approved 11:10:34 topic: quickly updates 11:10:55 daniel: other task forces are ready to publish updated versions of their documents 11:11:21 ... about the Scripting API document, it seems that there are no sensible updates so far 11:11:44 zoltan: since we depend to other documents it is normal to be a little bit late 11:11:55 ... we can publish later 11:12:41 daniel: yeah we can wait until other documents are more stable 11:12:52 cris: +1 for posponing 11:12:57 +1 11:12:59 mizushima: ok 11:13:17 topic: open PRs 11:14:02 daniel: zoltan update the discovery api, it is a substantial change 11:14:10 ... no more local 11:14:17 zoltan: added direct 11:14:44 daniel: it's similar to what we had a while ago (regarding direct) 11:14:58 i|daniel|-> https://github.com/w3c/wot-scripting-api/pull/316 PR 316 - Simplify discovery methods. Update examples.| 11:16:02 ... direct it's difficult to formalize because there are a lot of parameters that a user can provide (url parameters, headers ...) 11:16:20 zoltan: right now url is just a filter 11:17:07 ... plain string, the runtime should check it to understand the address 11:17:35 ... cristiano also proposed to refactor the APIs using the methods instead of filters 11:17:53 ... it's another paradigm more from js frameworks 11:19:00 ... in the web platform is more usual to use filters 11:19:19 daniel: direct method could be a lot 11:19:40 ... can we support api to undarstand if we support coap/http direct? 11:19:57 zoltan: we can't control the binding here 11:20:31 daniel: in node wot we had a method to fetch method, that cause some problems 11:20:49 zoltan: in ocf direct method is well-formalized even parameters 11:20:53 ... we should support 11:20:58 ... it 11:21:50 daniel: ok, I'll check the PR later and we can discuss the new api design later 11:22:18 zoltan: I was concerned about having an API that fit the current discovery spec, we refactor later 11:23:28 zoltan: I also have a PR (closed) for 'once' subscription method. keep it mind and provide feedback if any 11:23:59 daniel: kinda supported, you can unsubscribe right after the first event 11:24:17 topic: Issues 11:24:26 topic: subtopic taskforce related issue 11:24:45 s/topic: subtopic/subtopic:/ 11:25:21 daniel: I create issues to capture discussion topics for each defined joint call with other taskforces. 11:26:15 s/create/created/ 11:26:24 rrsagent, make log public 11:26:29 rrsagent, draft minutes 11:26:29 I have made the request to generate https://www.w3.org/2021/04/19-wot-script-minutes.html kaz 11:26:42 zoltan: the discussion list for TD taskforce looks good 11:27:14 daniel: about discovery we have discovery methods, streaming TDs, and fetching mechanisms 11:27:43 ... fetching is a broad topic 11:28:30 zoltan: I would raname it to something else 11:28:49 rrsagent, draft minutes 11:28:49 I have made the request to generate https://www.w3.org/2021/04/19-wot-script-minutes.html kaz 11:29:13 Chair: Daniel 11:29:14 rrsagent, draft minutes 11:29:14 I have made the request to generate https://www.w3.org/2021/04/19-wot-script-minutes.html kaz 11:29:19 cris: what about just fetch? 11:29:33 ... I opened an issue about it in the discovery repo 11:29:37 daniel: added 11:30:50 i|the discussion list for TD|-> https://github.com/w3c/wot-scripting-api/issues/313 Issue 313 - ThingDescription TaskForce related issues #313| 11:31:44 i|about discovery|-> https://github.com/w3c/wot-scripting-api/issues/314 Issue 314 - Discovery TaskForce related issues| 11:31:48 ... streaming is another big issue 11:31:54 s/raname/rename/ 11:31:57 rrsagent, draft minutes 11:31:57 I have made the request to generate https://www.w3.org/2021/04/19-wot-script-minutes.html kaz 11:32:21 cris: yeah it's an hot topic in the Discovery TF 11:32:52 daniel: I remember that mccool was discussing about field order when streaming 11:33:06 zoltan: it seems out-of-topic for us 11:33:23 daniel: we could allow clients to streaming tds 11:33:53 s/to/to request for/ 11:34:54 daniel: another topic, we discovery can select pieces of TDs 11:35:12 s/we/with discovery/ 11:36:16 zoltan: yes please add it 11:36:35 cris: yeah, I think it has higher priority than streaming 11:38:19 zoltan: I would remove the first topic 11:38:24 daniel: ok 11:38:40 zoltan: cause those are the real question 11:39:00 daniel: we could try to join next week discovery call 11:39:20 zoltan: the earlier the better 11:40:39 daniel: let's set the meeting for the 26th of April 11:40:59 zoltan: should we do also the security call? 11:41:05 daniel: it's ok 11:41:46 zoltan: it's like a big scripting call 3 hours with one hour of break 11:41:54 daniel: yeah it's good 11:43:37 daniel: about the security joint call 11:43:55 ... there are two topics managment api and choose the security scheme 11:43:58 ... kinda related 11:44:26 zoltan: that's off topic 11:44:32 daniel: I know 11:44:52 zoltan: should we try to draft this management api before the call 11:44:59 daniel: we could start from the node-wot 11:46:01 ... in the discovery they started from a TD 11:46:08 ... we could do the same 11:46:32 rrsagent, draft minutes 11:46:32 I have made the request to generate https://www.w3.org/2021/04/19-wot-script-minutes.html kaz 11:46:34 zoltan: I have to think about it, I would be cautions 11:48:08 cris: I'm afraid that some managment methods should never be called remotely 11:48:46 ... so I am not sure that starting from a TD is the best way forward 11:48:53 ... we could have a TD after 11:49:06 ... but still we can look to node-wot as a starting point 11:49:33 i|I am afraid|-> https://github.com/w3c/wot-scripting-api/issues/298 Issue 298 - Requirements for Managment APIs| 11:49:35 zoltan: we have a lot of different deployment methods: docker, web assembly, web manifest etc. 11:50:00 ... it's onboarding I described it in the architecture 11:50:32 ... basically a device has two mode (one for provisioning and one for runtime) 11:51:42 cris: I would say that providing a draft of the management API it's beneficial 11:51:55 daniel: I don't think we have time to define it 11:52:37 zoltan: we don't even have good use cases 11:53:00 ... I am more concerned with the discovery. 11:54:32 cris: we could start from security use case that we had for the managment api 11:54:40 ... I can "formalize" it 11:55:15 zoltan: we could start from it, write code and than switch to the runtime mode 11:58:37 ... ExposeThing is already at managment level api. 12:00:06 rrsagent, draft minutes 12:00:06 I have made the request to generate https://www.w3.org/2021/04/19-wot-script-minutes.html kaz 12:00:22 daniel: ok time is up, let's try to move forward and set up the minutes 12:00:49 ... please zoltan could you ask mccool 12:00:58 zoltan: yeah we can disccus also in the main call 13:09:16 Zakim has left #wot-script