11:02:09 RRSAgent has joined #wot-script 11:02:09 logging to https://www.w3.org/2021/04/12-wot-script-irc 11:02:18 Meeting: WoT Scripting API 11:02:41 present+ Kaz_Ashimura, Cristiano_Aguzzi, Zoltan_Kis 11:03:34 dape has joined #wot-script 11:03:36 present+ Daniel_Peintner 11:05:05 -> https://www.w3.org/2021/03/15-25-wot-minutes.html#d6-t03 vF2F Day 6 11:06:15 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#12_April_2021 11:07:32 Mizushima has joined #wot-script 11:08:46 scribe: zkis 11:08:57 Topic: approving past minutes 11:09:00 -> https://www.w3.org/2021/03/08-wot-script-minutes.html 11:09:43 present+ Tomoaki_Mizushima 11:09:58 s/html/html March-8 11:14:03 Minutes approved. 11:14:21 Topic: vF2F recap 11:14:34 -> https://www.w3.org/2021/03/15-25-wot-minutes.html#d6-t03 11:14:48 DP: we need to approve the minutes 11:16:31 ZK: we had 3 action points: meeting with Discovery TF, Security TF and work with TD TF on ExposedThing 11:17:28 ZK: we need to allocate meetings and make tracking issues 11:20:19 Minutes approved. 11:20:48 daniel: back to agenda, no pending PR 11:21:07 ... I added a list of issues that were recently updated 11:21:59 cris: can we discuss the possible meeting with the others groups? 11:22:03 daniel: ok 11:22:15 topic: joint meetings 11:22:43 daniel: about TD joint call usually all of us are there 11:23:04 ... we should talk about how to create an expose thing from a ThingModel 11:23:13 ... we have a tracking issue for this 11:23:23 ... it is still work in progress 11:23:50 ... the other thing is about the validation. For exampl, title is mandatory or not 11:24:09 s/exampl/example/ 11:25:03 scribe:zkis 11:26:10 https://github.com/w3c/wot-thing-description/issues/1047 11:26:30 CA: about generation of Thing Models 11:26:39 ... we can do it in 2 steps 11:26:48 ... Thing Model --> Partial TD 11:26:58 ... then we can use the partial TD in Scripting 11:27:10 DP: I see some problems, e.g. title 11:27:59 CA: we can discuss this during the next call, needs discussion in the TD call 11:29:18 DP: creating tracking issues for TD 11:30:28 ... or checkboxes for TODO list 11:31:33 Topic: simplifying discovery, #311 11:31:47 https://github.com/w3c/wot-scripting-api/issues/311 11:32:59 ZK: discovery methods will be direct and directory, by default directory 11:34:14 DP: when making a discovery query, one could get a direct TD (fragment) or a directory 11:34:54 CA: queries are not just filters, but you can select parts of the objects 11:35:14 ... for instance just the title 11:35:21 ... that is problem with Scripting API 11:36:22 DP: you can ask a directory for TDs with a certain title 11:37:12 ZK: what can you do with a partial TD? what's next? 11:37:33 CA: it's like database queries, and optimizes bandwidth 11:38:32 ZK: that can be done in a script, but doesn't need to be the Scripting API 11:39:16 DP: we can make query from Scripting 11:39:30 CA: we could put constraints on those queries 11:39:53 DP: in the implementation I would just pass it to the app 11:41:18 ZK: we need to separate the use cases, understand them and then design an API for them 11:41:29 ... first we should have the API to get TDs 11:43:19 DP: the discovery conformance class is separate, no need to create ConsumedThings 11:43:44 ZK: the dicovery TF spec is too complex right now, we should wait for crystallized use cases 11:44:13 CA: an app could get the TD of the directory, then figure out the rest from there 11:45:28 ... the use case of returning a fragment of TD should be done with the current API 11:46:21 DP: discovery API provides a TD, in node-wot we could use the TD of the directory to handle it 11:47:01 ZK: that is the vanilla API and it's possible, but we could have a better API 11:47:04 CA: agreed 11:47:38 CA: handling directly directory TDs is very complex, we'd need a better abstraction indeed 11:49:30 ZK: proposing small steps, implement them, play with them on plugfest, then move on 11:49:37 CA: agreed with that direction 11:49:42 DP: makes sense 11:50:23 ZK: will create a PR based on #311 11:51:05 Topic: security 11:51:08 rrsagent, make log public 11:51:13 rrsagent, draft minutes 11:51:13 I have made the request to generate https://www.w3.org/2021/04/12-wot-script-minutes.html kaz 11:51:14 CA: provisioning security 11:52:28 ZK: a script should not be able to provision security. It needs a different API meant for another level of security for the runtime. 11:52:50 ... it belongs to the Scriping task force, but a different deliverable 11:52:57 CA: right 11:53:16 DP: CA is working on a PR, so how should we continue 11:53:36 -> https://github.com/w3c/wot-scripting-api/issues/299 11:53:43 -> https://github.com/w3c/wot-scripting-api/issues/298 11:57:30 ZK: we should make focused proposals on the security provisioning use case, developer flow and API 11:57:52 DP: we also need to think about what we can do in the core API 11:58:20 CA: developers could know what security schemes are supported 11:59:39 ZK: that is a valid use case for ExposedThing 12:00:44 DP: if we expose a thing node-wot adds all supported security schemes 12:01:08 CA: yes, and if something is not supported it can include info for that 12:01:44 DP: we need to adjourn 12:02:01 rrsagent, make log public 12:02:04 Meeting adjourned. 12:02:06 rrsagent, drat minutes 12:02:06 I'm logging. I don't understand 'drat minutes', kaz. Try /msg RRSAgent help 12:02:09 rrsagent, draft minutes 12:02:09 I have made the request to generate https://www.w3.org/2021/04/12-wot-script-minutes.html kaz 12:14:07 zkis2 has joined #wot-script 13:33:58 Zakim has left #wot-script