11:03:15 RRSAgent has joined #wot-script 11:03:15 logging to https://www.w3.org/2021/05/10-wot-script-irc 11:03:25 meeting: WoT Scripting API 11:04:25 zkis has joined #wot-script 11:05:02 cris has joined #wot-script 11:05:24 present+ Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi 11:06:24 present+ Zoltan_Kis 11:06:32 Mizushima has joined #wot-script 11:08:58 topic: minutes 11:09:30 daniel: approved previous minutes 11:09:35 present+ Tomoaki_Mizushima 11:10:06 ... then discussed with the security task force about open issue on runtime provisioning 11:10:14 ... we defined at least two security levels 11:10:23 ... or security realms 11:11:00 ... zoltan is proposing to create a new document for describing the high privilege security level 11:11:17 ... then we schedule the call with discovery task force 11:11:28 daniel: minutes approved 11:11:37 ... no quick updates 11:11:41 topic: PRs 11:11:50 i/approved/scribenick: cris/ 11:12:12 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#10_May_2021 11:12:18 daniel: we have two PRs realtated to typescript types from ThingDescriptions 11:12:35 ... they look good, but I have two comments 11:12:48 ... first about do we want to keep the package.json 11:14:06 cris 11:14:35 cris: I uploaded it cause it may help us to keep track of the version of the tool that I am using 11:14:56 daniel: ok it's fine we may remove it if we find it troublesome. 11:16:24 daniel: another comment is about copying the json schema 11:16:46 ... it might be better to only have one file in the TD repository 11:19:13 daniel: don't have a strong opinion 11:19:26 zoltan: we could start from here 11:20:09 i|I uploaded|subtopic: PR 318| 11:20:30 i|I uploaded|-> https://github.com/w3c/wot-scripting-api/pull/318 PR 318 - Introduce thing description type from json schema| 11:21:13 daniel: Also line 78 might not work in node wot 11:23:02 cris: we could merge it so that I can check it's proper behaviour 11:23:06 daniel: ok to merge it? 11:23:13 zoltan: ok by me 11:25:12 daniel: merged 11:27:05 cris: ok it worked 11:28:39 daniel: just maybe thinking again if we can get rid of the duplicated schema file 11:29:29 topic: issues 11:29:43 daniel: any comments on the issues from the joint calls? 11:29:59 ... ok seems we still have some work todo 11:30:12 subtopic: issue 193 11:30:15 -> https://github.com/w3c/wot-scripting-api/issues/193 11:30:56 daniel: should writeProperty return a value? the use case was to give feedback about the written values 11:31:15 ... like returning 1.23 if the application wrote 1.2345 11:31:24 rrsagent, make log public 11:31:29 rrsagent, draft minutes 11:31:29 I have made the request to generate https://www.w3.org/2021/05/10-wot-script-minutes.html kaz 11:31:37 ... http would not return any value 11:32:20 ... lately ben proposed in the profile document that the PUT method may return a value 11:32:45 ... even if in the end he said that it is a bad practise to return a value 11:33:08 ... in our case we just cannot model the possiblity to return a value 11:33:37 zoltan: we already have a function for reading 11:34:02 daniel: the reason is for automatic reading/writing 11:34:31 zoltan: if it is an async system you should deal it with synchronization primitives 11:35:30 daniel: may proposal is to follow better the possibility from protocols 11:35:40 zoltan: do we have use case? 11:35:54 daniel: yes the one presented before, at least what I had in mind 11:37:39 i|another comment|subtopic: PR 319| 11:37:59 i|another comment|-> https://github.com/w3c/wot-scripting-api/pull/319 PR 319 - Add a github action to automatically sync the json schema| 11:38:28 cris: we should abstract from the protocol binding level 11:38:48 zoltan: we have observed property to keep track of changing values 11:39:02 daniel: I agree 11:39:27 rrsagent, draft minutes 11:39:27 I have made the request to generate https://www.w3.org/2021/05/10-wot-script-minutes.html kaz 11:39:27 ... but I have another use case 11:39:42 ... it is from the philips hue smart lightbulb 11:40:41 zoltan: it is a binding level information 11:40:53 daniel: not sure if this is relevant for the application 11:42:10 zoltan: is this a writing multiple properties at once? 11:42:24 daniel: not sure 11:42:26 -> https://github.com/w3c/wot-profile/pull/77 wot-profile PR 77 - New Protocol Binding section 11:44:13 zoltan: we might need an operation that writes multiple prop and tells that one fails 11:44:23 cris: yeah true 11:46:40 cris: I still think this is an issue for interaction model of the TD 11:46:51 ... it is a bit profound 11:47:13 ... it touches the definition on the interaction between TDs and consumers 11:48:00 daniel: going back to the problem should we return a value 11:48:16 zoltan: we should wait until it is solved in the design 11:48:29 ... still it is a bit odd returning the written value 11:49:15 daniel: I feel like the previous example is good use case 11:49:27 ... but of course returning a whole file is nonsense 11:51:07 rrsagent, draft minutes 11:51:07 I have made the request to generate https://www.w3.org/2021/05/10-wot-script-minutes.html kaz 11:53:19 cris: uriVariables is also quite odd 11:53:34 zoltan: I agree it is a little bit from a protocol level 11:56:11 daniel: I see so do you want to just remove uriVariables? 11:56:48 cris: well kind of but if we find out that is a common use case we could introduce them as optional arguments for readproperty 11:57:02 zotlan: +1 11:58:01 zoltan: as an long-running goal we could change completely the interaction model, not a request and response 11:58:35 ... we could create a message base api 11:58:42 ... but it's ok 11:58:48 rrsagent, draft minutes 11:58:48 I have made the request to generate https://www.w3.org/2021/05/10-wot-script-minutes.html kaz 11:59:01 ... we can experiment with it later 11:59:15 ... the problem is that fetch api is really similar 11:59:49 daniel: at least our definitions would work with other protocols 12:02:02 daniel: ok commenting on the issue to summarize the discussion so far? 12:02:18 daniel: good 12:02:24 daniel: adjourned 12:02:34 rrsagent, draft minutes 12:02:34 I have made the request to generate https://www.w3.org/2021/05/10-wot-script-minutes.html kaz 13:37:13 Zakim has left #wot-script 13:39:47 zkis has joined #wot-script 14:07:11 Mizushima has left #wot-script