12:03:13 RRSAgent has joined #wot-script 12:03:18 logging to https://www.w3.org/2023/11/20-wot-script-irc 12:03:18 Zakim has joined #wot-script 12:03:27 Mizushima has joined #wot-script 12:06:41 JKRhb has joined #wot-script 12:07:18 meeting: WoT Scripting API 12:07:37 present+ Kaz_Ashimura, Daniel_Peintner, Jan_Romann, Tomoaki_Mizushima 12:10:22 cris__ has joined #wot-script 12:10:59 topic: minutes 12:11:04 dape: looks fine 12:11:15 --> Nov 11 -> https://www.w3.org/2023/11/06-wot-script-minutes.html 12:11:22 ... we merged 12:11:28 ... PRs and issues 12:11:38 q+ 12:11:43 ... ok we can approved them 12:11:53 s/issues/look issues/ 12:12:07 s/11/6/ 12:12:10 s/Nov 11/Nov 6 12:12:25 rrsagent, make log public 12:12:30 rrsagent, draft minutes 12:12:32 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:12:39 topic: Next calls 12:13:00 dape: first of all, xmas is near. We should decide if there will be cancellations 12:13:09 i/Next calls/(approved)/ 12:13:21 i/looks fine/scribenick: cris__/ 12:13:23 rrsagent, draft minutes 12:13:24 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:13:30 ... it seems that in other calls they already cancelled calls. 12:14:09 ... is the plan ok 12:14:18 s/ok/ok?/ 12:14:38 ... no call the 25th of december and first of January 12:14:44 ... let us know if you don't agree 12:15:07 subtopic: 2 weeks slot call? 12:15:15 dape: 2 calls in a month? 12:15:24 q+ 12:15:28 q- 12:15:32 q+ 12:16:23 cris: 2 weeks slot make sense. We don't have that much topics to discuss 12:16:44 dape: agree 12:16:48 ack cris__ 12:17:07 jan: second that, we are corrently working mostly async anyway. We can still merge PR once every two weeks 12:17:17 ... we can also always switch back 12:18:01 dape: suggestion keep weekly slot but use the wiki to cancel it 12:20:07 PROPOSAL: For the near future the Scripting task force is going to have a 2-week schedule. Ahead of time it will be made public the when the next call will take place. W3C calendar entries remain as is for now. 12:20:12 q+ 12:20:26 +1 12:20:30 q+ 12:20:33 ack jk 12:20:36 ack JKRhb 12:21:13 ack mi 12:21:49 chair: Daniel 12:22:24 rrsagent, draft minutes 12:22:25 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:23:01 present+ Cristiano_Aguzzi, Zoltan_Kis 12:23:01 rrsagent, draft minutes 12:23:02 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:25:14 q+ 12:25:19 ack k 12:28:41 ack c 12:28:42 ack c 12:29:07 dape: changing to intention. Meanwhile we discuss the plan 12:29:19 let's see if we can came up with a plan 12:29:22 q+ 12:29:41 ... and cancel the next call if needed 12:30:16 kaz: if you have a clear time span when you want to have a bi-weekly call you should say it in the text 12:30:22 ... near future is vague 12:30:34 ack k 12:30:34 INTENTION: For a while the the Scripting API task force might want to have a bi-weekly schedule. Meeting cancellations will be made official ahead of time. W3C calendar entries remain as is for now. 12:31:21 topic: PRs 12:31:25 dape: no updates 12:31:52 ... one about improvements, we are stuck and we need time to look into it 12:32:00 s/near future is vague/"near future" is vague. also if your intention is actually "for a while until the work on TD 2.0 and Discovery 1.1 starts", you should say so./ 12:32:11 rrsagent, draft minutes 12:32:12 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:32:18 q? 12:32:18 ... the next twos are about discovery 12:32:19 ... and how to align 12:32:51 subtopic: PR 513 12:33:53 -> https://github.com/w3c/wot-scripting-api/pull/513 PR 513 - feat!(typescript): align TypeScript definitions with Discovery API 12:35:31 cris_ has joined #wot-script 12:35:39 cris: looks good to me 12:36:03 dape_ has joined #wot-script 12:36:13 dape: merging PR 12:36:25 kaz2 has joined #wot-script 12:36:51 scribenick: cris_ 12:37:11 dape: we can now start working with node-wot 12:37:20 jan: it was a blocker, great to merge 12:37:41 dape: thank you jan 12:38:06 subtopic: PR 517 12:38:20 dape: we are using constructors in the webIDL 12:38:34 ... it wasn't in the TS definitions 12:38:46 ... it is not what we intended 12:39:02 ... we should also use the term creating instead of contracting 12:39:20 zoltan: do we have the expose method still ? 12:39:24 dape: yes 12:39:24 i|we are|-> https://github.com/w3c/wot-scripting-api/pull/517 PR 517 - feat!: remove constructor from ConsumedThing interface| 12:39:39 q+ 12:39:43 q+ 12:39:54 zoltan: consistent deciding 12:39:55 s/contract/construct/ 12:40:15 ... it is a complication and it is misunderstanding 12:41:04 dape: it was there for hystorical reasons 12:41:42 q? 12:41:52 zoltan: ok to merge 12:43:04 kaz: what is the intention? given the current sample code we can remove the constructor code but the text can still say construct 12:44:00 dape: we don't change anything else, but just align the text 12:44:33 kaz: it sounds ok, who and when the object it self is created? 12:45:18 ... was it a bug? 12:45:26 dape: it was a leftover from old days 12:45:39 ... it was also in ExposeThing 12:49:08 cris: two comments. It is true that creates confusion. In the CG we got feedback about how it was not clear the process to create a ConsumedThing. Second I recall that the constructor was there for facilitating testing, still we can remove it 12:49:18 dape: ok, merging 12:49:30 subtopic: PR #512 12:49:52 dape: kaz created a script to handle duplicated ids created by a bug in respect 12:49:53 s/PR/Issue/ 12:50:21 i|kaz cre|-> https://github.com/w3c/wot-scripting-api/issues/512 Issue 512 - Add perl script (for fixing duplicate IDs) to master/release folder 12:50:37 rrsagent, draft minutes 12:50:38 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:50:47 dape: added also readme 12:50:49 q+ 12:50:58 i/Issue #512/PR #518 and Issue #512/ 12:51:00 q- 12:51:06 ack c 12:51:38 ... similar to what other repos have 12:51:44 ... is that ok to merge it? 12:52:08 q+ 12:52:22 zoltan: ok 12:52:30 ack k 12:52:30 kaz: ok too, thank you 12:52:33 jan: ok too 12:52:55 s/ok too,/ok too. if needed, we can modify the description later./ 12:53:01 rrsagent, draft minutes 12:53:02 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:53:23 +1 me too 12:53:37 i|Issue 512 -|-> https://github.com/w3c/wot-scripting-api/pull/518 PR 518 - refactor: add readme and perl script for publication/release| 12:53:42 rrsagent, draft minutes 12:53:43 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:54:10 jan: should we add a followup issue? 12:54:21 cris: I little bit overkill but that's ok 12:54:23 s/Issue #512/PR #518 and Issue #512/ 12:54:24 rrsagent, draft minutes 12:54:26 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:54:45 dape: it already there 12:54:57 s/I little bit/a little bit/ 12:54:59 rrsagent, draft minutes 12:55:00 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 12:55:06 ... Issue 480 12:56:05 subtopic: PR 489 12:56:23 dape: cristiano worked on better typings 12:56:32 ... there were problems 12:58:05 i|cristiano worked|-> https://github.com/w3c/wot-scripting-api/pull/489 PR 489 - Better types for Scripting API| 12:58:08 rrsagent, draft minutes 12:58:09 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 13:00:08 cris: there are tricky parts 13:00:26 zoltan: we should take care to not make more restrictions 13:00:36 ... than the one are in the algorithms 13:02:15 I will also have another look into it :) I hadn't had found a solution for the problem so far as well :/ 13:03:02 s/had// 13:03:24 [adjourned] 13:03:26 rrsagent, draft minutes 13:03:27 I have made the request to generate https://www.w3.org/2023/11/20-wot-script-minutes.html kaz 13:58:37 mahda-noura has joined #wot-script 15:27:54 Zakim has left #wot-script