11:02:46 <RRSAgent> RRSAgent has joined #wot-script
11:02:50 <RRSAgent> logging to https://www.w3.org/2023/04/24-wot-script-irc
11:02:52 <kaz> meeting: WoT Scripting API
11:03:21 <kaz> present+ Kaz_Ashimura, Daniel_Peintner, Zoltan_Kis
11:04:22 <dape> dape has joined #wot-script
11:04:40 <Mizushima> Mizushima has joined #wot-script
11:05:24 <dape> scribe: dape
11:05:56 <dape> TOPIC: Previous minutes
11:06:14 <dape> -> April 17 -> https://www.w3.org/2023/04/17-wot-script-minutes.html
11:07:43 <dape> CA: Minutes look good -> approved
11:07:50 <dape> TOPIC: Quick updates
11:08:16 <dape> CA: General Issue: we should clean-up issues on Agenda
11:08:24 <dape> SUBTOPIC: Publication Schedule/Decision April 2023
11:08:56 <dape> CA: Got resolution in main call to publish after PR is merged
11:09:34 <dape> DP: Correct
11:09:37 <kaz> q+
11:09:37 <dape> CA: Good
11:10:59 <dape> Kaz: We should be clear what should be integrated in this PR
11:11:05 <kaz> ack k
11:11:12 <dape> DP: Correct, should remain editorial
11:11:36 <dape> SUBTOPIC: Next charter review
11:11:44 <dape> CA: remove the agenda item ?
11:11:49 <kaz> q+
11:11:50 <dape> ... task is compledted
11:12:07 <dape> s/compledted/completed
11:12:18 <dape> Kaz: Proposed draft charter has been agreed
11:12:32 <dape> ... topic can be removed
11:12:37 <dape> q+
11:12:40 <kaz> akc k
11:12:44 <kaz> s/akc k//
11:12:48 <kaz> ack k
11:13:28 <dape> DP: Back to normative note?
11:15:47 <dape> Kaz: PLH and I proposed to use non-normative note
11:16:13 <dape> ... WG approved draft and it was send to review
11:16:31 <dape> CA: remove nominative statements ?
11:16:37 <dape> Kaz: Yes
11:17:04 <zkis> q+
11:17:09 <dape> s/nominative/normative
11:17:16 <dape> q+
11:18:18 <dape> CA: Kind of a surprise for me and Daniel
11:18:25 <kaz> s/I proposed/I have been proposing/
11:18:28 <kaz> ack k
11:18:59 <dape> ack dape
11:19:26 <dape> ZK: Do we have a formal resolution on publishing normative node?
11:19:34 <dape> s/node?/note?
11:19:46 <dape> CA: Yes, I think we have one...
11:20:08 <kaz> q+
11:20:12 <kaz> ack z
11:20:15 <dape> ack zkis
11:20:49 <dape> q?
11:21:11 <dape> Kaz: we can still raise question/issue
11:21:30 <dape> ... from my view-point normative note is problematic
11:21:45 <dape> ... rather make normative REC document
11:22:36 <dape> ZK: W3C should make that clear in guidelines
11:23:00 <dape> Kaz: several view-points
11:23:14 <dape> ... publishing normative note would be problematic
11:23:35 <dape> ... can still do that if we have a resolution of the group
11:24:30 <zkis> q+
11:24:32 <dape> Kaz: dangerous .. not covered by policy
11:26:39 <kaz> s/by policy/by the W3C Patent Policy/
11:26:42 <dape> CA: I will start some investigation and make sure that everybody is aware of it
11:27:41 <zkis> q?
11:27:44 <zkis> ack k
11:28:17 <dape> ZK: I don't see a change to go on REC track
11:28:25 <dape> ... what we wanted to have is the normative language
11:28:39 <dape> ... I think we can keep the normative statements
11:29:01 <dape> ... the other alternative would be to move work to CG
11:29:12 <dape> CA: Still not covered by patent policy
11:30:44 <dape> TOPIC: PR
11:30:57 <dape> SUBTOPIC: Align spec with INFRA
11:31:03 <dape> -> https://github.com/w3c/wot-scripting-api/pull/469
11:31:11 <dape> CA: marked as editorial
11:31:19 <dape> ... no major change in algoritmn
11:31:25 <dape> ... spotted minor issue
11:31:44 <dape> ... does not change text at all.. just about respec linking
11:31:50 <dape> ZK: Already corrected it
11:32:03 <dape> ... we can have a last review if you want
11:32:43 <dape> CA: I am okay with a final review
11:33:22 <dape> ... let's give it this afternoon
11:33:29 <dape> ... and than start publishing process
11:33:30 <kaz> q+
11:33:36 <dape> ZK: +1
11:33:40 <dape> DP: +1
11:33:50 <dape> q+
11:34:49 <dape> Kaz: Should NOT integrate other stuff in this PR
11:35:39 <dape> ... IF we do other editorial stuff we should send email
11:36:22 <kaz> ack z
11:36:25 <dape> CA: Okay I got your point
11:36:27 <dape> ack dape
11:36:28 <kaz> ack k
11:36:46 <dape> SUBTOPIC: Update README.md with versioning information
11:36:52 <dape> -> https://github.com/w3c/wot-scripting-api/pull/462
11:37:01 <dape> CA: Explain versioning
11:37:10 <dape> ... not about document itself
11:37:45 <dape> ... I think we can merge PR as is and create yet another issue about the version number
11:39:15 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#April_24.2C_2023
11:39:33 <dape> DP: Not sure if we need to merge now.. could add it to this PR
11:39:44 <dape> TOPIC: Issues
11:39:57 <dape> SUBTOPIC: Check if record is better than map Editorial
11:40:04 <dape> -> https://github.com/w3c/wot-scripting-api/issues/465
11:40:20 <dape> ZK: I think we are done with it with the pending PR
11:40:24 <kaz> rrsagent, make log public
11:40:28 <kaz> rrsagent, draft minutes
11:40:30 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/24-wot-script-minutes.html kaz
11:40:40 <dape> CA: Will link PR
11:40:54 <kaz> chair: Cristiano
11:41:10 <kaz> present+ Cristiano_Aguzzi, Tomoaki_Mizushima
11:41:14 <kaz> rrsagent, draft minutes
11:41:15 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/24-wot-script-minutes.html kaz
11:41:48 <dape> SUBTOPIC: Update the "expand an ExposedThingInit" steps wrt security definitions
11:42:00 <dape> -> https://github.com/w3c/wot-scripting-api/issues/471
11:42:29 <kaz> s|-> https://github.com/w3c/wot-scripting-api/pull/469|-> https://github.com/w3c/wot-scripting-api/pull/469 PR 469 - Align spec with INFRA|
11:42:36 <dape> ZK: I think text is improved in the meanwhile about security definitions
11:42:48 <dape> ... we need to do a better prose
11:42:51 <dape> ... more exact
11:43:12 <kaz> s|-> https://github.com/w3c/wot-scripting-api/pull/462|-> https://github.com/w3c/wot-scripting-api/pull/462 PR 462 - Update README.md with versioning information|
11:43:22 <dape> CA: in node-wot we also not fully follow the algorithm
11:43:32 <dape> ... but that is a different aspect
11:43:47 <kaz> s|-> https://github.com/w3c/wot-scripting-api/issues/465|-> https://github.com/w3c/wot-scripting-api/issues/465 Issue 465 - Check if record is better than map|
11:43:54 <kaz> rrsagent, draft minutes
11:43:55 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/24-wot-script-minutes.html kaz
11:44:10 <dape> SUBTOPIC: Update listener internal slots to map<name, structure>
11:44:16 <dape> -> https://github.com/w3c/wot-scripting-api/issues/470
11:44:38 <kaz> s|-> https://github.com/w3c/wot-scripting-api/issues/471|-> https://github.com/w3c/wot-scripting-api/issues/471 Issue 471 - Update the "expand an ExposedThingInit" steps wrt security definitions|
11:44:47 <dape> ZK: we should leave this after publication
11:45:08 <dape> ... should check this by reading through
11:45:17 <kaz> s|-> https://github.com/w3c/wot-scripting-api/issues/470|-> https://github.com/w3c/wot-scripting-api/issues/470 Issue 470 - Update listener internal slots to map<name, structure>|
11:45:20 <kaz> rrsagent, draft minutes
11:45:21 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/24-wot-script-minutes.html kaz
11:45:38 <dape> ... i reformulated the prose a bit
11:45:50 <dape> CA: Did you introduce DataHandler construct?
11:45:52 <dape> ZK: No
11:46:09 <dape> CA: Okay, let add "enhancement" label
11:47:43 <dape> SUBTOPIC: Check pair vs tuple usages Editorial
11:47:48 <dape> -> https://github.com/w3c/wot-scripting-api/issues/466
11:47:57 <dape> CA: pending PR will solve this?
11:48:13 <dape> ZK: Yes, I think this should be covered by PR 469
11:48:49 <dape> SUBTOPIC: Consider aligning with IntersectionObserver
11:48:59 <dape> -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf
11:49:03 <kaz> s|-> https://github.com/w3c/wot-scripting-api/issues/466|-> https://github.com/w3c/wot-scripting-api/issues/466 Issue 466 - Check pair vs tuple usages|
11:49:21 <dape> -> https://github.com/w3c/wot-scripting-api/issues/427
11:49:42 <kaz> i|SUBTOPIC|-> https://github.com/w3c/wot-scripting-api/pull/469 PR 469 - Align spec with INFRA|
11:49:51 <dape> CA: We can "copy" the design.. after publication
11:50:11 <dape> ... even though we have different use-case
11:50:20 <kaz> s|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf Scripting API wiki|
11:50:26 <dape> ... not sure if it is great in Web of Things
11:50:34 <dape> ... shall we keep it open?
11:50:47 <dape> ZK: Yes, prefer to keep it open
11:50:53 <kaz> s|-> https://github.com/w3c/wot-scripting-api/issues/427|-> https://github.com/w3c/wot-scripting-api/issues/427 Issue 427 - Consider aligning with IntersectionObserver|
11:50:58 <kaz> rrsagent, draft minutes
11:50:59 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/24-wot-script-minutes.html kaz
11:51:05 <dape> ... should check what other specs do
11:52:35 <kaz> s|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf Scripting API wiki||
11:52:38 <kaz> rrsagent, draft minutes
11:52:39 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/24-wot-script-minutes.html kaz
11:53:27 <dape> SUBTOPIC: Explain the new tagging mechanism for experimental features
11:53:37 <dape> -> https://github.com/w3c/wot-scripting-api/issues/458
11:54:02 <dape> CA: TODO left and missed explanation
11:54:32 <dape> ... I think we can close issue after PR 462
11:54:37 <kaz> s|-> https://github.com/w3c/wot-scripting-api/issues/458|-> https://github.com/w3c/wot-scripting-api/issues/458 Issue 458 - Explain the new tagging mechanism for experimental features|
11:55:13 <kaz> -> https://github.com/w3c/wot-scripting-api/pull/462 PR 462 - Update README.md with versioning information
11:55:53 <dape> SUBTOPIC: Stale issues
11:56:10 <dape> CA: I think we went to other issues I wanted to discuss
11:56:30 <dape> ... let's adjourn
12:01:28 <kaz> rrsagent, draft minutes
12:01:29 <RRSAgent> I have made the request to generate https://www.w3.org/2023/04/24-wot-script-minutes.html kaz
14:03:42 <Mizushima> Mizushima has left #wot-script
14:09:14 <Zakim> Zakim has left #wot-script