11:05:23 <RRSAgent> RRSAgent has joined #wot-script
11:05:23 <RRSAgent> logging to https://www.w3.org/2022/07/18-wot-script-irc
11:05:38 <kaz> meeting: WoT Scripting API
11:05:41 <kaz> chair: Daniel
11:05:53 <kaz> present+ Kaz_Ashimura, Daniel_Peintner Ege_Korkan
11:06:22 <kaz> present+ Tomoaki_Mizushima
11:06:42 <dape> scribe: dape
11:06:54 <dape> TOPIC: Minutes
11:07:12 <dape> -> July-11 -> https://www.w3.org/2022/07/11-wot-script-minutes.html
11:08:29 <kaz> present+ Cristiano_Aguzzi
11:08:45 <dape> <Minutes approved>
11:09:31 <dape> TOPIC: PRs
11:09:39 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#18_July_2022
11:09:43 <dape> SUBTOPIC: remove observeHandler from emitPropertyChange() steps
11:09:47 <dape> -> https://github.com/w3c/wot-scripting-api/pull/415
11:12:15 <dape> CA: using read handler to push update
11:12:55 <dape> Ege: Somewhat fine.. but what if i am using a library to interface with sensor
11:13:14 <dape> ... reading physical value twice
11:14:09 <dape> CA: emitProperty change should convey the same value than reading
11:14:56 <dape> .. but I see the efficiency issue
11:15:10 <dape> Ege: will try to provide example
11:15:22 <dape> ... agree with merging
11:15:46 <dape> DP: let's merge
11:16:13 <dape> CA: Agree, feedback is welcome
11:16:31 <dape> SUBTOPIC: move allowed of of the parenthesis to make it more official
11:16:35 <dape> -> https://github.com/w3c/wot-scripting-api/pull/414
11:19:39 <dape> CA: I would like to use "MUST"
11:19:49 <kaz> q+
11:20:41 <cris_> cris_ has joined #wot-script
11:20:57 <cris_> q?
11:21:43 <dape> Kaz: MUST is fine
11:21:47 <kaz> s/allowed of/allowed types out/
11:21:52 <dape> ... btw, typo in PR header
11:22:13 <kaz> rrsagent, make log public
11:22:17 <kaz> rrsagent, draft minutes
11:22:17 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/18-wot-script-minutes.html kaz
11:23:03 <dape> DP: agree to merge with MUST statement
11:23:21 <dape> TOPIC: Issues
11:23:38 <dape> SUBTOPIC: Do we need an EventHandler?
11:23:42 <dape> -> https://github.com/w3c/wot-scripting-api/issues/408
11:24:50 <dape> CA: event algorithm for eventHandler: data is collected in eventHandler
11:24:58 <dape> ... then send data though network
11:25:06 <dape> ... Q: Do we need EventHandler
11:25:28 <dape> ... different to property change
11:25:47 <dape> ... no event get read afterwards. properties are ready later on
11:26:20 <dape> Ege: mixed up the topic. I was thinking about subscription handler
11:27:29 <dape> CA: Even difficult to write event handler
11:27:46 <dape> Ege: I usually don't use eventHandler
11:29:23 <dape> CA: eventHandler *before* data on the wire
11:30:16 <dape> ... handler not needed
11:30:21 <dape> Ege: Agree
11:31:14 <dape> DP: Why do we have 9.28 and 9.29
11:31:30 <dape> CA: I think we can merge the 2 sections
11:35:57 <Ege> Ege has joined #wot-script
11:36:14 <dape> CA: Will work on PR
11:38:50 <dape> Ege: BTW, channel in calendar invite is wrong
11:39:08 <dape> DP: will check with McCool
11:40:09 <dape> ISSUE: Harmonize the exposing process
11:40:19 <dape> -> https://github.com/w3c/wot-scripting-api/issues/409
11:41:10 <kaz> q?
11:41:12 <kaz> ack k
11:41:52 <dape> DP: Shall we collect such issues for next version?
11:42:06 <dape> CA: Makes sense. Not sure how to handle this.. as W3C note
11:42:16 <dape> q?
11:43:43 <kaz> q+
11:44:20 <dape> Kaz: Synchronize with other documents and calling it 1.1
11:44:34 <dape> ... bigger changes with TD2.0
11:44:41 <dape> ... if we can wait
11:45:11 <cris_> q+
11:45:24 <dape> DP: This change does not relate to TD2.0
11:45:45 <dape> Kaz: External developers might have a different understanding
11:46:48 <dape> ... 2 policies .. compatibility implementors vs. compatibility of prev. scripting API
11:47:02 <Ege> q+
11:47:14 <kaz> ack k
11:47:15 <dape> CA: We do have versioning problem in general
11:47:23 <dape> ... do not have policy
11:47:29 <kaz> q+
11:47:57 <dape> ... synchronization with TD version ... might also have downsides
11:48:20 <dape> ... Scripting API 4.0 can be still compliant with TD.1.1
11:49:09 <kaz> s/compatibility implementors/compatibility with the other WoT specs for implementers/
11:49:16 <dape> ... should look into versioning problem and solve it
11:49:33 <dape> Ege: General problem.. with WoT versioning
11:49:36 <kaz> s/compatibility of prev/compatibility with the prev/
11:49:47 <dape> ... queryaction is not supported yet, for example
11:50:05 <dape> ... some TD features are not yet possible in scripting API
11:50:16 <dape> ... some policy would be nice
11:50:26 <cris_> q+
11:50:31 <kaz> ack c
11:50:32 <kaz> ack e
11:50:33 <dape> ... we need some explanation
11:50:43 <kaz> q+ cris_
11:50:57 <dape> CA: fetch API are living standard
11:51:10 <dape> ... they are always updating
11:51:16 <dape> ... can look into what they do
11:52:22 <dape> Kaz: Compatibility between specs. Should check this separately
11:53:01 <dape> ... fixing fatal bug would need to merge an update
11:55:03 <dape> DP: no compatibility issue now
11:55:10 <dape> ... API could evolve quicker
11:56:21 <dape> Kaz: should think about WoT internal versioning
11:56:39 <dape> q?
11:56:46 <dape> ack kaz
11:57:57 <dape> DP: Wonder how living standards work
11:58:27 <dape> Kaz: HTML5 familiy.. is about "adding" features ... and not removing anything
11:58:41 <dape> ... we should think about our own policy
11:59:02 <dape> s/familiy/family
12:00:20 <dape> CA: Supporting previous function might not be possible in any case
12:01:16 <dape> Kaz: HTML4 to HTML5 change caused different JS versions
12:02:38 <dape> ... scripting API is group note.
12:02:54 <dape> ... 6 more month left... but we should be careful about new features
12:03:45 <kaz> s/is group/is a group/
12:04:40 <dape> CA: Let's wait for Zoltans opinion as well
12:04:58 <kaz> s/Zoltans/Zoltan's/
12:06:18 <kaz> s/HTML4 to HTML5 change caused different JS versions/please remember what happened. HTML5 added many breaking changes but those changes are basically added as separate JavaScript APIs./
13:44:30 <Mizushima> Mizushima has left #wot-script
13:58:07 <Zakim> Zakim has left #wot-script
14:00:37 <kaz> kaz has joined #wot-script
16:51:49 <kaz> kaz has joined #wot-script
23:34:27 <kaz> kaz has joined #wot-script