10:54:10 <RRSAgent> RRSAgent has joined #wot-script
10:54:10 <RRSAgent> logging to https://www.w3.org/2022/05/30-wot-script-irc
10:54:17 <kaz> meeting: WoT Scripting API
11:01:54 <kaz> present+ Kaz_Ashimura, Cristiano_Aguzzi, Jan_Romann
11:01:59 <cris_> cris_ has joined #wot-script
11:03:44 <dape> dape has joined #wot-script
11:06:20 <JKRhb> JKRhb has joined #wot-script
11:06:36 <JKRhb> scribenick: JKRhb
11:06:40 <dape> TOPIC: Previous minutes
11:06:56 <dape> -> May-16 -> https://www.w3.org/2022/05/16-wot-script-minutes.html
11:06:58 <JKRhb> topic: Previous Minutes
11:07:11 <JKRhb> RRSAgent, make draft public
11:07:11 <RRSAgent> I'm logging. I don't understand 'make draft public', JKRhb.  Try /msg RRSAgent help
11:07:18 <Mizushima> Mizushima has joined #wot-script
11:07:19 <JKRhb> RRSAgent, draft minutes
11:07:20 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html JKRhb
11:08:02 <JKRhb> RRSAgent, make log public
11:08:19 <JKRhb> s/Previous Minutes//
11:08:41 <kaz> s/topic: //
11:08:48 <kaz> rrsagent, draft minutes
11:08:48 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html kaz
11:08:56 <JKRhb> The group goes over the minutes and discusses the minutes
11:09:14 <JKRhb> dp: Minutes look good, we can publish them
11:09:48 <JKRhb> topic: Quick Updates
11:09:56 <kaz> present+ Daniel_Peintner, Tomoaki_Mizushima
11:10:01 <zkis> zkis has joined #wot-script
11:10:02 <JKRhb> dp: Can be skipped
11:10:03 <zkis_> zkis_ has joined #wot-script
11:10:23 <JKRhb> ... we will publish a new WD, once the discovery question has been resolved
11:10:26 <JKRhb> topic: PRs
11:10:31 <zkis> zkis has joined #wot-script
11:10:33 <JKRhb> subtopic: PR #404
11:10:59 <JKRhb> dp: PR is about a missing emitPropertyChange method on the ExposedInterface
11:11:00 <zkis> present+ Zoltan_Kis
11:11:10 <JKRhb> ... PR is already merged, changes are published on npm
11:12:10 <JKRhb> subtopic: PR #405
11:12:27 <kaz> i| PR is about|-> https://github.com/w3c/wot-scripting-api/pull/404 PR 404 - fix: add missing emitPropertyChange() method|
11:12:44 <zkis> q+
11:12:55 <kaz> -> https://github.com/w3c/wot-scripting-api/pull/405 PR 405 - feat!: add new Discovery Web IDL definitions
11:12:59 <cris_> q+
11:13:25 <JKRhb> dp: PR contains a WebIDL proposal for a new discovery API
11:14:00 <JKRhb> jr: Still WIP, based on an issue with concrete code examples
11:15:14 <JKRhb> ... we can discuss the PR based on the issue
11:15:19 <JKRhb> topic: Issues
11:15:32 <JKRhb> subtopic: Issue #364
11:16:02 <JKRhb> dp: In your proposal, fields are mandatory
11:16:19 <kaz> i|In your|-> https://github.com/w3c/wot-scripting-api/issues/364 Issue 364 - Using a callback-based approach for Discovery?|
11:17:03 <JKRhb> jr: With the code examples, I got the impression that these fields should be mandatory, but this change can be reverted
11:18:19 <zkis> q?
11:18:22 <zkis> ack zkis
11:18:37 <JKRhb> zk: We need to discuss the algorithms
11:19:59 <JKRhb> ... making parameters mandatory changes the allowed behavior, local discovery would not be possible with mandatory ones
11:22:14 <JKRhb> ca: Issue touches a different topic, general shape of the API, parameters are second step
11:23:39 <kaz> scribenick: kaz
11:24:41 <kaz> ( discussion on Jan's comments: https://github.com/w3c/wot-scripting-api/issues/364#issuecomment-1137703749 )
11:29:10 <kaz> q+
11:29:14 <kaz> ack c
11:32:33 <cris_> q+
11:37:10 <zkis> q?
11:37:14 <zkis> ack kaz
11:37:17 <kaz> kaz: I'm wondering which would be better to include this change into the Scripting API at the moment (=during this Charter period) or not
11:37:38 <kaz> zk: it would make the API simpler
11:37:46 <kaz> ... and we could get feedback
11:38:01 <kaz> ca: could be included in ver. 1.1
11:38:13 <kaz> ... but can be deferred to the next version
11:38:51 <kaz> ... we're not changing the target use cases
11:39:11 <kaz> zk: we need feedback from the Discovery TF
11:39:21 <kaz> ... also implementation feedback as well
11:39:36 <kaz> q?
11:39:37 <kaz> ack c
11:39:51 <kaz> ... from my viewpoint, this is just a small syntactic change
11:40:34 <kaz> ... once the PR is approved, we need to think about an updated algorithm as well
11:40:47 <kaz> dp: I'm also a bit unsure
11:40:59 <kaz> ... you could still use the old API
11:41:09 <kaz> zk: that's true
11:41:35 <kaz> ... would need to implement the "next" method
11:41:52 <kaz> rrsagent, draft minutes
11:41:52 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html kaz
11:41:58 <kaz> jr: right
11:42:04 <kaz> ... can update the example too
11:42:30 <kaz> dp: Jan is also proposing renewed algorithm for node-wot too
11:43:03 <kaz> zk: people could use both the methods, the current design and the new one
11:43:10 <kaz> ... and see which would be better
11:44:06 <kaz> ... think it would be make it more portable if we use the new "next" method
11:44:27 <dape> q?
11:44:30 <kaz> ... it's more modern approach
11:44:38 <kaz> s/more/a more/
11:44:51 <kaz> dp: ok, tx for your proposal, Jan
11:44:59 <kaz> rrsagent, draft minutes
11:44:59 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html kaz
11:45:10 <kaz> subtopic: Issue 396
11:45:45 <JKRhb> scribenick: JKRhb
11:45:55 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/396 Issue 396 - The future of the conformance class WoT Discovery
11:46:22 <kaz> s|-> https://github.com/w3c/wot-scripting-api/issues/396 Issue 396 - The future of the conformance class WoT Discovery||
11:46:39 <kaz> subtopic: Issue 403
11:47:01 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/403 Issue 403 - DataSchemaValue missaligned int TS definitions
11:47:11 <kaz> ca: need some more discussion
11:47:20 <kaz> ... didn't have time to create a PR, sorry
11:47:34 <kaz> subtopic: Issue 402
11:47:53 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/402 Issue 402 - Emitting no data for events
11:47:57 <JKRhb> RRSAgent, draft minutes
11:47:57 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html JKRhb
11:48:24 <JKRhb> s/scribenick: JKRhb//
11:48:27 <kaz> scribenick: JKRhb
11:48:32 <JKRhb> scribenick: JKRhb
11:48:34 <JKRhb> RRSAgent, draft minutes
11:48:34 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html JKRhb
11:49:07 <kaz> s/subtopic: Issue 396//
11:49:15 <kaz> rrsagent, draft minutes
11:49:15 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html kaz
11:50:10 <JKRhb> ca: Current dataschema does not really allow for emitting no value at the moment
11:51:47 <zkis> q+
11:52:06 <JKRhb> ... question whether we should align WebIDL and typescript definitions, restricting the type of DataSchemaValue to a set of values instead of any
11:52:19 <JKRhb> ... this is currently the case in typescript
11:52:42 <JKRhb> zk: We discussed this earlier and we made a decision for a reason
11:52:57 <JKRhb> ... however, the API should be clear about what is optional or not
11:54:17 <JKRhb> ... I am not sure if we can define DataSchemaValue as a value other than any, but making it optional would be possible
11:54:57 <JKRhb> dp: Could we run into problems due to the recursive definition for Arrays?
11:55:16 <JKRhb> zk: Recursive values are illegal in WebIDL
11:56:10 <JKRhb> ... algorithms need to be specified to handle recursive data structures, syntactically they cannot be defined in WebIDL, however
11:57:05 <JKRhb> ca: We might already be aligned with the typescript definitions via the specification's prose
11:57:59 <JKRhb> dp: Issue 402 has a simple solution, adding the optional keyword to the parameter
11:58:12 <JKRhb> ca: ... and updating the algorithm
11:59:57 <JKRhb> ca: There was also an issue regarding returning no value from actions
12:00:14 <JKRhb> ... but it was in the TD repository?
12:01:31 <JKRhb> dp: (Looks for the issue (#1234) and finds it)
12:02:02 <JKRhb> ... the problem is not the same, though
12:03:03 <JKRhb> [adjourned]
12:03:15 <kaz> rrsagent, draft minutes
12:03:15 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html kaz
12:05:05 <Mizushima> Mizushima has left #wot-script
12:05:39 <kaz> chair: Daniel
12:05:41 <kaz> rrsagent, draft minutes
12:05:41 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/30-wot-script-minutes.html kaz
14:26:53 <Zakim> Zakim has left #wot-script
17:40:36 <zkis> zkis has joined #wot-script
21:18:36 <zkis> zkis has joined #wot-script
21:33:36 <zkis> zkis has joined #wot-script
21:47:36 <zkis_> zkis_ has joined #wot-script