10:59:45 <RRSAgent> RRSAgent has joined #wot-script
10:59:45 <RRSAgent> logging to https://www.w3.org/2021/09/06-wot-script-irc
11:01:44 <dape> dape has joined #wot-script
11:02:08 <cris> cris has joined #wot-script
11:02:34 <kaz> meeting: WoT Scripting API
11:02:56 <kaz> present+ Kaz_Ashimura, Cristiano_Aguzzi, Daniel_Peintner
11:03:32 <zkis> zkis has joined #wot-script
11:04:54 <kaz> present+ Zoltan_Kis
11:05:28 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#6_September_2021
11:06:19 <Mizushima> Mizushima has joined #wot-script
11:06:59 <kaz> scribenick: cris
11:07:00 <cris> topic: previous minutes
11:07:16 <kaz> -> https://www.w3.org/2021/08/30-wot-script-minutes.html Aug-30
11:07:40 <cris> dape: we tackled some PRs and looked on label categorization.
11:07:45 <cris> ... they look ok
11:07:50 <cris> ... any concerns?
11:07:53 <cris> zoltan: none
11:08:02 <cris> dape: minutes approved
11:08:10 <cris> topic: quick updates
11:08:36 <cris> dape: just keep in mind that we might need to decide whether to publish on Semptember
11:08:41 <cris> topic: Open PR
11:08:49 <cris> dape: minor update
11:09:03 <cris> ... Zoltan and Cristiano are already on board
11:09:10 <cris> ... just a link to the label sections
11:09:20 <cris> s/sections/section
11:09:44 <cris> ... go to go
11:09:54 <cris> s/go to/good to/
11:10:10 <kaz> present+ Tomoaki_Mizushima
11:11:03 <cris> cris: are you planning to add descriptions to the current list of labels?
11:11:16 <cris> dape: right, adding an issue to keep track of this
11:12:15 <cris> ... any other comments?
11:12:17 <kaz> kaz: +1 to add descriptions
11:13:51 <cris> topic: issues
11:14:10 <cris> dape: essentially there are two issues
11:14:18 <cris> subtopic: Op values
11:14:23 <dape> New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
11:14:41 <cris> dape: it's about query action and cancel action
11:15:04 <cris> ... in the td repo there's an open pr for queryaction and cancel action operations
11:15:34 <cris> ... our issue is just a heads up
11:16:03 <kaz> i|minor update|-> https://github.com/w3c/wot-scripting-api/pull/333 PR 333 - Label Table|
11:16:13 <cris> ... probably we'll add two new methods in consume thing for those two new operations
11:16:16 <kaz> rrsagent, make log public
11:16:21 <kaz> rrsagent, draft minutes
11:16:21 <RRSAgent> I have made the request to generate https://www.w3.org/2021/09/06-wot-script-minutes.html kaz
11:16:43 <cris> ... any comments? other alternatives?
11:18:01 <cris> cris: maybe we could return an handle and there add the functions to handle these new ops
11:18:24 <cris> dape: we have to keep in mind that we should not break the current API
11:21:32 <cris> cris: btw I am not sure if the new operations will be for a dynamic queue of actions or just for a static single action
11:21:51 <cris> zoltan: also not all servers might support this mechanism
11:22:29 <kaz> rrsagent, draft minutes
11:22:29 <RRSAgent> I have made the request to generate https://www.w3.org/2021/09/06-wot-script-minutes.html kaz
11:23:02 <kaz> chair: Daniel
11:24:09 <cris> dape: is it planned for 1.1?
11:24:12 <cris> cris: yes
11:24:26 <cris> dape: ok at least we have already two possible solutions in mind
11:24:52 <cris> subtopic: NotFoundError
11:24:59 <dape> https://github.com/w3c/wot-scripting-api/issues/334
11:25:13 <kaz> i|NotFound|-> https://github.com/w3c/wot-thing-description/pull/1208 related TD PR 1208 - Add queryaction and cancelaction operations - closes #302|
11:25:29 <cris> dape: in some situations the call expect an affordance name as argument
11:25:43 <cris> ... what happen if the property name is not found
11:25:57 <cris> ... the algorithm does not explain it
11:26:10 <cris> ... who can check this issue?
11:26:47 <kaz> s/https/-> https/
11:27:11 <kaz> s/334/334 Issue 334 - NotFoundError is not used/
11:27:37 <cris> cris: I could propose a simple proposal of how it would look
11:27:47 <cris> s/look/look like/
11:28:06 <cris> ... but I might not have time to check the security concerns
11:28:17 <cris> dape: no big deal, I'll review it later
11:28:54 <cris> cris: is NotFoundError standard?
11:28:59 <cris> zoltan: I think so
11:29:56 <cris> dape: regarding this they are located on DOM exceptions
11:32:39 <cris> ... Ege also asked for a better list of which errors might be thrown
11:32:41 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/200 related Issue 200 - Error Handling
11:34:05 <cris> cris: the PR will only be about client side checkings not networking errros, right?
11:34:08 <cris> dape: yeah
11:35:57 <cris> cris: about networking... are we planning to tackle error reported from binding implementations?
11:36:11 <cris> dape: I had some use cases
11:36:45 <cris> zoltan: the problem is that applications in wot should not have knowledge of the specific binding
11:37:35 <cris> ... we should keep this simple
11:37:43 <cris> dape: I agree on one hand side
11:38:19 <cris> ... people will look for ways to know what is happening on the network level
11:38:49 <cris> ... also we have a formIndex, isn't already a protocol information?
11:39:13 <cris> zoltan: I see it as a temporary feature to cover corner use cases
11:39:40 <cris> dape: I like this feature because it can open to complex application behavior
11:40:49 <cris> zoltan: yeah, but it requires the application to go down one level in the abstraction layers
11:41:05 <cris> ... we might re visit this in the future
11:41:44 <cris> ... text based search in the discovery?
11:42:10 <cris> ... should we represent bindings at all in the scripting api?
11:42:19 <kaz> s/re visit/re-visit/
11:42:21 <cris> dape: currently no
11:42:48 <cris> zoltan: one design choice could be having an endpoint for each binding
11:43:11 <cris> ... but this will lock all the interactions using that specific binding
11:43:50 <cris> dape: development time requires formIndex
11:44:30 <cris> zoltan: we don't have really that use case in the scripting api
11:47:27 <cris> cris: we used formIndex to specify a form with a particular secuirity scheme
11:48:19 <cris> zoltan: we didn't really analyze the use case...
11:48:30 <cris> ... actually we didn't even create it
11:48:53 <cris> dape: I think it was there, otherwise we wouldn't add the formIndex
11:49:21 <cris> zoltan: we make an issue to discuss the use case of form index
11:51:57 <cris> cris: this might be loosely related to security management
11:52:30 <cris> zoltan: we might find good use case scenarios for users, cause it is pretty basic
11:54:31 <cris> subtopic: clean f2f issues
11:54:37 <dape> Clean-up F2F issues, see https://github.com/w3c/wot-scripting-api/labels/F2F
11:56:22 <cris> dape: we had those list of issues to be discussed in the f2f
11:56:27 <cris> ... those are still valid
11:56:41 <cris> ... how do you think is better to relabel them?
11:59:45 <cris> cris: I would start from removing the f2f label
11:59:51 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/219 e.g., Issue 219 - Discussion about read- write-/multipleproperties
12:00:02 <cris> dape: ok I'll look into it, I may also comment with relavant information
12:00:13 <kaz> [adjourned]
12:00:18 <kaz> rrsagent, draft minutes
12:00:18 <RRSAgent> I have made the request to generate https://www.w3.org/2021/09/06-wot-script-minutes.html kaz
14:24:50 <Zakim> Zakim has left #wot-script