11:01:20 RRSAgent has joined #wot-script 11:01:20 logging to https://www.w3.org/2021/05/31-wot-script-irc 11:02:22 dape has joined #wot-script 11:02:37 Meeting: WoT Scripting API 11:03:16 Agenda: 11:03:33 https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#Agenda 11:04:46 cris has joined #wot-script 11:06:30 present+ Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi, Zoltan_Kis 11:06:36 scribenick: cris 11:06:54 dape: last week no call 11:07:06 i/last/topic: Minutes 11:07:06 topic: previous minutes 11:07:34 dape: not sure why the minutes reports Smart City Workshop 11:07:41 ... we discussed about f2f and testing 11:08:18 ... I also mentioned that the dates are overlapping with my vacation plans 11:08:43 ... the rest of the minutes was about issue 193 11:09:05 ... the discussion focused on echonet example 11:09:16 ... should write property operation return something? 11:09:47 ... the consensus was to not return anything 11:10:16 ... but if the binding using some returned values the implementation might throw an error to inform the application logic 11:10:23 ... we should make this clear in the document 11:10:31 ... no changes are required to the API 11:10:35 zoltan: yes 11:10:58 dape: minutes approved 11:11:03 topic: quick updates 11:11:08 Mizushima has joined #wot-script 11:11:41 dape: proposal during the test week no call 11:11:55 ... but the test fest does not conflict with the scripting call 11:12:04 present+ Tomoaki_Mizushima 11:12:06 q+ 11:12:11 ... theoretically we could do it 11:12:40 kaz: I expected that the ordinary calls would be cancelled 11:12:42 ack k 11:12:55 dape: for me it is ok to cancel 11:13:23 zoltan: I can join if there's a call 11:13:58 cris: ok for cancel 11:15:12 dape: if nothing urgent come up, no call 11:15:23 s/come/comes/ 11:15:37 dape: I'll be on vacation from the 12 to the end of june 11:16:34 ... some of you can schedule calls? do we have anything to present during the F2F ? 11:17:32 cris: I think we don't have some many updates right now 11:17:41 s/some/so/ 11:21:08 dape: june it is pretty packed up maybe we will skip a few calls 11:21:45 zoltan: we should get inputs from bindings and TD 11:23:28 dape: we can discuss about open issues with different task force 11:23:40 zoltan: we could take an hour an just finish eairler 11:26:24 dape: should we add a bullet point dedicated to scripting? 11:27:25 cris: why don't we split our topics into the different task force topics? 11:27:32 dape: yes, let me do it 11:28:06 topic: issues 11:28:37 dape: please review the three big issue dedicated to TD, discovery, and security 11:28:47 ... before F2F and Testing 11:30:30 -> https://github.com/w3c/wot-scripting-api/issues/313 Issue 313 - ThingDescription TaskForce related issues 11:30:33 cris: I think topic in issue 313 should be moved under PartialTD validation 11:30:39 dape: yes 11:30:55 ... please also check issue 314 11:31:31 ... it would be also useful to discover local things around me 11:31:54 ... there is a dedicated issue 11:32:14 zoltan: we have use cases before experiments with the feature. 11:33:25 daniel: I'd to have the possibility to look for things around me at operational time 11:33:50 ... it seems that right now we focus just on the second phase discovery 11:34:04 ... we should explore it also in node-wot 11:34:28 ... the next task force topic was about security 11:35:01 ... it goes around provisioning of security credential and management api 11:35:12 ... zoltan proposed to move the discussion to another document 11:35:47 ... about our API we should be able to pick one of the configurations and assing to the specific Thing 11:35:59 cris: yes 11:37:54 -> https://github.com/w3c/wot-scripting-api/issues/315 Issue 315 - Security TaskForce related issues 11:38:24 i|issue 314|-> https://github.com/w3c/wot-scripting-api/issues/314 Issue 314 - Discovery TaskForce related issues| 11:39:39 dape: node wot uses a configuration file that has a map with ids and credentials 11:40:01 cris: yes, it is basic and it works only if you know beforhand the id of the consumed thing 11:41:06 dape: yes, you need to first add the credentials and then consume the thing 11:41:49 zoltan: the principle that there's no man in the middles 11:42:13 ... we should not give then plain to other software agents 11:43:37 dape: there's no way to specify which security to use in an expose thing 11:43:49 ... selectivly 11:44:40 zoltan: we already agreed that exposing a Thing is a system level privildge 11:44:58 dape: we could have a code example about it 11:48:44 zoltan: we could use "special things" that contains this kind of information 11:49:04 ... so we might not need a new api 11:49:17 ... but then we need a way to discovery them 11:50:02 cris: it is not a bad idea, but maybe a little bit overkill 11:50:18 zoltan: we maybe just need special filters in the discovery 11:51:06 dape: I am not sure about the example in 299 11:51:40 zoltan: yeah I was thinking about the source of information about the supported security schemes 11:52:02 dape: what about a setSecurityHandler 11:52:23 zoltan: yeah you need to have it for each interaction level 11:54:20 ... we can think a nice api to do it after production phase 11:55:31 dape: we are almost there, but just to be precise we are missing the securityDesfinitions 11:55:53 zoltan: yes about that we have the two options presented above: one funciton or a special Thing object 11:58:03 ... if it is an api it needs to be controller by authorization coinstraints (permissions) 11:59:39 zoltan: I got a lot of updates about writeProperty return 11:59:48 dape: ok I'll review it 12:00:09 ... next week call cancelled if nothing urgent happen 12:05:41 Mizushima has left #wot-script 12:05:46 [adjourned] 12:05:50 rrsagent, make log public 12:05:54 rrsagent, draft minutes 12:05:54 I have made the request to generate https://www.w3.org/2021/05/31-wot-script-minutes.html kaz 14:30:21 Zakim has left #wot-script