11:05:03 <RRSAgent> RRSAgent has joined #wot-script
11:05:03 <RRSAgent> logging to https://www.w3.org/2022/07/11-wot-script-irc
11:05:09 <kaz> meeting: WoT Scripting API
11:05:21 <kaz> present+ Kaz_Ashimura
11:05:21 <cris> cris has joined #wot-script
11:06:30 <Mizushima> Mizushima has joined #wot-script
11:08:42 <kaz> present+ Cristiano_Aguzzi, Daniel_Peintner, Tomoaki_Mizushima
11:09:55 <kaz> scribenick: kaz
11:10:09 <kaz> topic: Minutes
11:10:38 <kaz> -> https://www.w3.org/2022/07/04-wot-script-minutes.html July-4
11:11:37 <kaz> approved
11:11:51 <kaz> topic: PRs
11:11:57 <kaz> dp: two PRs there
11:12:23 <kaz> ... any opinions?
11:12:45 <kaz> ... would skip them given lack of participation
11:12:48 <kaz> ok
11:12:50 <kaz> topic: Issues
11:13:10 <kaz> subtopic: Issue 409
11:13:41 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/409 Issue 409 - Harmonize the exposing process
11:13:51 <kaz> dp: may need another publication
11:14:19 <kaz> ... regarding the "ExposedThing" interface
11:14:39 <kaz> ... proposal on two-step approach
11:14:50 <kaz> ... ProduceThing and then ExposedThing
11:14:58 <kaz> ... but this is a breaking change
11:15:03 <kaz> q+
11:15:15 <kaz> dp: looks good to me, though
11:15:41 <kaz> ... makes a lot of sense
11:17:26 <kaz> kaz: from my viewpoint, this is related to programming language mechanism
11:17:51 <kaz> ... objective programming languages support constructor/destructor mechanism
11:18:15 <kaz> ... and "ProduceThing" should be handled by that mechanism instead of our own defining a new method
11:18:40 <kaz> ... so it would have impacts for the existing implementations
11:19:17 <kaz> dp: right
11:19:26 <kaz> ... so it's a breaking change
11:20:09 <kaz> kaz: so I'm wondering if it's possible for us to get some more support from the JavaScript programming environment and existing libraries
11:20:17 <kaz> dp: good question
11:20:56 <kaz> ca: JavaScript doesn't support objective programming like Java
11:22:26 <kaz> rrsagent, make log public
11:22:30 <kaz> rrsagent, draft minute
11:22:30 <RRSAgent> I'm logging. I don't understand 'draft minute', kaz.  Try /msg RRSAgent help
11:22:35 <kaz> s/rrsagent, draft minute//
11:22:37 <kaz> rrsagent, draft minutes
11:22:37 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/11-wot-script-minutes.html kaz
11:24:47 <kaz> s/ca: JavaScript doesn't support objective programming like Java/ca: JavaScript supports objective programming/
11:25:16 <kaz> ... but normal constructor is not enough for productThing
11:25:28 <kaz> dp: exposing, consuming, and discovery
11:25:53 <kaz> ca: network/filesystem handling capability
11:26:42 <kaz> kaz: if we really need it, we should go for that
11:27:15 <kaz> dp: not *needed* but it would be clearer to see what to be called when if we had it
11:29:34 <kaz> kaz: making the mechanism clearer is a possible "need" for the change
11:29:45 <kaz> ... but we should be careful about the need
11:30:06 <kaz> ... and possible impacts for the existing implementations
11:32:30 <kaz> dp: yeah, it would have impact to implementers
11:32:55 <kaz> kaz: also need a possible DeleteThing in pare with this ProducedThing?
11:33:12 <kaz> dp: note that the method itself, ProducedThing is not added
11:33:32 <kaz> ... but on of the sub methods, etPartialThingDscription() will be added
11:33:35 <kaz> kaz: ok
11:33:50 <cris> q+
11:33:53 <kaz> ack
11:34:44 <kaz> ... what about expose()?
11:35:02 <kaz> ... changing from the type from void to returning something?
11:35:05 <kaz> dp: yes
11:36:56 <kaz> kaz: if we add the "getPartialThingDescription(), who would validate it and what would happen if any errors?
11:37:04 <kaz> ca: good question
11:37:09 <kaz> ... should be validated beforehand
11:37:42 <kaz> q?
11:37:44 <kaz> ack k
11:37:45 <kaz> ack c
11:37:47 <kaz> q+
11:38:37 <kaz> dp: should change the return type to "ExposedThingInit"?
11:40:24 <kaz> kaz: it sounds a bit dangerous to me to apply this change to the Scripting API spec directly
11:40:58 <kaz> ... so would suggest we see the potential impact based on some specific use case scenario after adding a change as a trial
11:41:03 <kaz> ca: agree
11:41:10 <kaz> dp: yeah
11:41:20 <kaz> ... should get further feedback and comments
11:42:50 <kaz> ... would see Jan's opinion as well
11:42:56 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/409#issuecomment-1180306619 Daniel's comments
11:43:54 <kaz> q?
11:43:55 <kaz> ack k
11:44:17 <kaz> subtopic: Issue 403
11:44:28 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/403 Issue 403 - DataSchemaValue misaligned in TS definitions
11:45:05 <kaz> dp: relates to another issue 296
11:45:23 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/296 Issue 296 - DataSchemaValue in TS should not be any
11:45:49 <kaz> dp: it was impossible to handle the details by WebIDL
11:45:58 <kaz> ... so we wanted to use Typescript instead
11:46:08 <kaz> ... maybe we might want to revisit that approach as well
11:46:33 <kaz> ... would suggest we once close this Issue 403 itself
11:47:41 <kaz> dp: (adds a comment to Issue 403)
11:48:05 <kaz> ... we should move parenthesized text out
11:48:24 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/403#issuecomment-1180311627 Daniel's comment
11:48:55 <kaz> subtopic: Issue 408
11:49:08 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/408 Issue 408 - Do we need an EventHandler?
11:49:17 <kaz> dp: need for a dedicated Event Handle?
11:49:23 <kaz> s/Handle/Handler/
11:50:15 <kaz> ... got a comment from Ege
11:50:34 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/408#issuecomment-1174279184 Ege's comment
11:51:18 <kaz> q+
11:51:41 <kaz> dp: (shoes the example code within Cristiano's comment)
11:51:52 <kaz> [[
11:51:53 <kaz> var produced; // Produced Thing
11:51:53 <kaz> produced.setEventHandler("noDataEvent", () => undefined);
11:51:53 <kaz> / exposing
11:51:53 <kaz> await produced.expose();
11:51:53 <kaz> produced.emitEvent("noDataEvent");
11:51:55 <kaz> ]]
11:52:12 <kaz> ca: a picture would be helpful
11:53:30 <kaz> kaz: agree system configuration figure and communication diagram would be helpful
11:54:02 <kaz> ... also we should clarify what kind of entities to be included how for what kind of use case scenario as well
11:54:23 <kaz> dp: yeah
11:54:34 <kaz> ... would invite Ege to join the Scripting call too
11:55:54 <kaz> ... thought there was a related PR as well
11:56:08 <kaz> -> https://github.com/w3c/wot-scripting-api/pull/218 PR 218 - Add ExposedThing property observe, unobserve and event handler suppor
11:56:17 <kaz> s/suppor/support
11:56:26 <kaz> dp: but that includes too many changes...
11:56:40 <kaz> subtopic: Issue 407
11:56:56 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/407 Issue 407 - Incosistency in emit property changed
11:57:50 <kaz> ca: for node-wot, we don't call eventHandler but call readHander directly
11:59:19 <kaz> dp: (shows 8.13 emitPropertyChange() from the published WD)
11:59:25 <kaz> -> https://www.w3.org/TR/wot-scripting-api/#the-emitpropertychange-method 8.13 The emitPropertyChange() method
11:59:35 <kaz> s/WD/Note/
12:00:29 <kaz> dp: we could use the same handler unless there is a specific need/use case
12:01:22 <kaz> i/we could/ca: could use emitPropertyChange(), etc. if needed./
12:02:31 <kaz> ... will propose a PR
12:02:45 <kaz> ... would get feedback from others too
12:02:51 <kaz> [adjourned]
12:02:54 <kaz> rrsagent, make log public
12:02:59 <kaz> rrsagent, draft minutes
12:02:59 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/11-wot-script-minutes.html kaz
12:05:00 <Mizushima> Mizushima has left #wot-script
14:08:28 <Zakim> Zakim has left #wot-script
15:56:34 <dape> dape has joined #wot-script
18:29:14 <kaz> kaz has joined #wot-script