12:02:32 RRSAgent has joined #wot-script 12:02:32 logging to https://www.w3.org/2021/02/01-wot-script-irc 12:02:36 dape has joined #wot-script 12:06:02 Mizushima has joined #wot-script 12:06:11 Meeting: WoT Scripting API 12:07:54 present+ Kaz_Ashimura, Daniel_Peintner, Zoltan_Kis, Cristiano_Aguzzi, Tomoaki_Mizushima 12:08:14 cris has joined #wot-script 12:08:31 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#1_February_2021 12:09:11 scribe:zkis 12:09:35 Topic: previous minutes 12:11:02 -> https://www.w3.org/2021/01/25-wot-script-minutes.html Jan-25 12:11:36 No objections, approved. 12:11:56 Topic: PR 289 12:12:00 -> https://github.com/w3c/wot-scripting-api/pull/289 12:12:15 -> realted with https://github.com/w3c/wot-architecture/issues/574 12:12:22 DP: related to the issue discussed in Architecture 12:12:26 s/realted/related 12:12:51 DP: the PR was merged, so we have a definition for the Partial TD 12:13:27 ... since it may be useful for other use cases as well 12:13:43 ... so now we have the PR from Cristiano 12:13:56 ... we decided last time to rename PartialTD to ExposedThingInit 12:14:18 CA: yes, it's been a minor update, just a name change 12:15:34 ZK: usually we don't make separate sections for dictionaries 12:15:41 CA: but we have 2 algorithms 12:15:49 ZK: ok then it makes sense 12:17:49 CA presents the PR 12:22:11 Discussing structuring of the ExposedThingInit section into the produce() section 12:23:31 ... as subsections of produce() 12:26:27 CA: another thing, what to do with the table for generating the partial TD 12:27:17 ... and how to deal with possible differences in implementations 12:28:34 ... in order to be interoperable 12:29:02 ... also, take care of mandatory definitions (like security, context, ...) 12:29:41 DP: if someone specifies a scheme that is not supported, it should replace or handle it 12:30:48 ZK: usually we need to specify in the algorithms how to handle these 12:31:05 DP: for instance, could href point to another Thing? 12:31:48 ZK: do we do syntactic or semantic check? 12:31:53 CA: syntactic 12:32:23 ... the app might not want the impl to replace the href 12:33:36 ZK: the TD should give us possibility for that 12:33:46 CA: we could use relative URI here 12:34:24 DP: the problem is that e.g. node-wot uses the input to generate a full href, and the app cannot have that knowledge 12:39:27 CA: the input from app should be respected up to the level of definition: name, partial URI, or full URI 12:39:49 ... if it cannot be respected, then an error would be reported 12:40:01 ... but the parts not specified should be completed by the runtime 12:40:18 ... also, understand that we cannot use other URIs than the ones we own 12:40:35 DP: need to check this 12:41:54 DP: impls should not allow other origins in the input 12:42:11 ... but rather use the handlers for accessing external URLs 12:42:49 CA: also have a use case that the address generated by node-wot is not what was expected by the app 12:43:22 ... anyway, I agree, make it simple and don't accept other origins here 12:45:06 ZK: also need a default handling for security input (e.g. no-security) 12:45:20 DP: difficult to provide the right credentials for the exposed Thing 12:45:31 CA: will try to propose something and discuss in github 12:47:21 ZK: it would be nice if the TD TF would define the exact TD producing 12:47:37 DP: the TD TF is concerned only about the decoding, not the encoding 12:47:56 ... the only thing to make sure is that everyone decodes the same way 12:48:24 ZK: so you say it's application's domain to describe the encoding 12:48:30 DP: well, yes 12:50:33 ZK: we should separate the pure syntactic checks from the semantic checks and transformations by impl 12:50:48 ... and feel it's a gap if we don't specify the transformations 12:50:53 CA: agree with that 12:51:04 DP: so let's start with syntactic and then decide 12:51:37 Topic: implementation feedback 12:51:50 -> https://github.com/w3c/wot-scripting-api/issues/292 12:51:54 DP: InteractionOutput is too complex 12:56:23 ZK: we need to support other content types than DataSchema 12:56:33 ... the TD permits that and it was a gap 12:56:41 CA: I also wonder why can't we have streams 13:01:30 ZK: we could raise up in the main call if we want to stick to DataSchema 13:01:42 DP: just not sure about this in real life 13:01:55 ... this will be a problem in many implementations 13:02:13 CA: but streams is optional, the value() function can throw 13:02:48 ZK: I think any impl based on http or coap library can do it out of the box 13:03:01 DP: ok, let's discuss further 13:03:56 rrsagent, make log public 13:04:00 rrsagent, draft minutes 13:04:00 I have made the request to generate https://www.w3.org/2021/02/01-wot-script-minutes.html kaz 13:04:13 adjourned 13:04:17 rrsagent, draft minutes 13:04:17 I have made the request to generate https://www.w3.org/2021/02/01-wot-script-minutes.html kaz 14:11:25 Zakim has left #wot-script