11:05:21 <RRSAgent> RRSAgent has joined #wot-script
11:05:21 <RRSAgent> logging to https://www.w3.org/2022/08/01-wot-script-irc
11:05:32 <kaz> meeting: WoT Scripting API
11:05:51 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#1_August_2022
11:05:52 <dape> s/Charter: /Agenda:
11:06:17 <kaz> present+ Kaz_Ashimura, Daniel_Peintner, Critiano_Aguzzi, Jan_Romann, Zoltan_Kis
11:06:23 <Mizushima> Mizushima has joined #wot-script
11:07:00 <zkis> scribenick:zkis
11:07:24 <zkis> DP: approving previous minutes
11:07:36 <dape> -> https://www.w3.org/2022/07/18-wot-script-minutes.html
11:07:52 <kaz> s/html/html July-18/
11:08:49 <zkis> DP: no objection, minutes can be made public
11:09:06 <zkis> Topic: cancellations in August
11:09:09 <kaz> present+ Tomoaki_Mizushima
11:09:45 <zkis> DP: cannot make 15 Aug
11:10:23 <zkis> CA: can't make it on 15 and 29, perhaps 5 Sep, too
11:10:44 <zkis> CA: Sep 5 works
11:11:49 <zkis> ZK: let's try to do it biweekly in August, on 8 and 22
11:11:57 <Mizushima> +1
11:12:00 <zkis> DP: will send out cancellations
11:12:41 <zkis> Topic: next charter
11:13:25 <zkis> DP: we can move the Scripting API from the W3C Note Track
11:13:32 <zkis> s/from/to
11:13:55 <kaz> q+
11:14:02 <zkis> DP: this is a different process, we need to study it, etc
11:14:47 <zkis> KA: did not mean to re-publish the doc, just provide the latest description of the W3C process, with a possible option to adhere to it
11:15:02 <zkis> ... and to discuss in the group and W3C what is the best way to move it forwards
11:15:10 <zkis> s/forwards/forward
11:15:31 <zkis> DP: ok - the next charter starts in February, until then we need to clarify these things
11:16:24 <kaz> q+
11:16:36 <zkis> DP: we need to discuss the charter topics as well
11:17:29 <zkis> KA: the document is already a Note and adding the Note Track was that the CG's have right to publish Notes. On the other hand, WG's could not publish Notes that have normative features.
11:17:47 <zkis> ... there are 3 possible options, and we need to discuss which is best for Scripting
11:18:08 <zkis> KA: options: informative Note, formal Note, RC
11:19:06 <zkis> ... an RC document is a deliverable of the whole W3C, whereas a Note is a deliverable of the WG
11:19:25 <zkis> ack kaz
11:20:21 <zkis> DP: this is not a minor update since we need to change the API as well
11:20:41 <zkis> ... we need to discuss it in the WG
11:22:41 <zkis> Topic: issues
11:23:00 <zkis> Subtopic: issue 417
11:23:09 <dape> -> https://github.com/w3c/wot-scripting-api/issues/417
11:25:19 <kaz> s/417 Issue 417 - emitPropertyChange does not take low-level event apis into account/
11:31:38 <kaz> q+
11:33:10 <zkis> ZK: there seems to be a misunderstanding in the usage of the API
11:33:28 <zkis> KA: I suggest discussing with Ege with concrete usage scenario
11:36:11 <zkis> ZK: we could support an informative value with notifications, but we cannot guarantee that value
11:37:59 <zkis> ZK: also, the value may be long or complex (e.g. stream) - we don't pass values with notifications
11:38:45 <kaz> ack k
11:39:19 <zkis> Subtopic: issue 408
11:39:22 <dape> -> https://github.com/w3c/wot-scripting-api/issues/408
11:44:58 <kaz> zakim, who is on the call?
11:44:58 <Zakim> Present: Kaz_Ashimura, Daniel_Peintner, Critiano_Aguzzi, Jan_Romann, Zoltan_Kis, Tomoaki_Mizushima
11:46:05 <zkis> CA explains why we don't need an EventHandler
11:48:38 <zkis> DP: we have optional data when emitting events, but why we don't have data with change notifications
11:49:00 <zkis> CA: because the data is defined locally when emitting events, and read with notifications
11:53:05 <zkis> ZK: it's a broad and deep change, and needs more considerations and checks
11:53:17 <zkis> JA: will also check this from implementation pov
11:53:23 <zkis> CA: I can work on a PR
11:56:26 <zkis> DP: we need to check the related spec sections for possible simplifications
11:56:40 <zkis> Subtopic: issue 409
11:56:48 <dape> -> https://github.com/w3c/wot-scripting-api/issues/409
11:59:38 <zkis> ZK: explained the comment in the issue
11:59:49 <zkis> CA: yes, that is an alternative way
12:01:00 <zkis> ... they differ in the moment the checks are done for a valid exposed Thing
12:03:33 <kaz> q+
12:05:07 <kaz> s/409/409 Issue 409 - Harmonize the exposing process/
12:05:42 <kaz> ack k
12:05:52 <zkis> KA: we should focus on the use cases and continue offline
12:06:00 <zkis> DP: meeting adjourned
12:06:18 <kaz> rrsagent, make log public
12:06:22 <kaz> rrsagent, draft minutes
12:06:22 <RRSAgent> I have made the request to generate https://www.w3.org/2022/08/01-wot-script-minutes.html kaz
12:43:26 <Mizushima> Mizushima has left #wot-script
14:01:39 <kaz> kaz has joined #wot-script
14:08:26 <Zakim> Zakim has left #wot-script
14:25:34 <zkis> zkis has joined #wot-script