11:57:20 <RRSAgent> RRSAgent has joined #wot-script
11:57:25 <RRSAgent> logging to https://www.w3.org/2023/02/06-wot-script-irc
11:57:40 <kaz> meeting: WoT Scripting API
12:06:49 <zkis> zkis has joined #wot-script
12:06:55 <kaz> present+ Kaz_Ashimura, Cristiano_Aguzzi
12:07:31 <Mizushima> Mizushima has joined #wot-script
12:10:25 <kaz> present+ Tomoaki_Mizushima
12:11:06 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#February_6.2C_2023
12:11:22 <kaz> topic: Minutes
12:11:30 <kaz> -> https://www.w3.org/2023/01/30-wot-script-minutes.html Jan-30
12:12:56 <cris_> cris: minutes looks good, just one minor issue with Jan names
12:13:33 <kaz> fixed
12:13:47 <cris_> ... minutes looks good, any issues?
12:13:51 <cris_> ... ok minutes accepted
12:13:52 <kaz> i/minutes look/scribenick: cris_/
12:14:02 <cris_> topic: quick updates
12:14:03 <kaz> s/... minutes/cris: minutes/
12:14:08 <dape> dape has joined #wot-script
12:14:46 <kaz> s/quick updates/Publication/
12:15:32 <cris_> cris: I'm not going to be available next week, should we cancel the meeting?
12:15:57 <kaz> s/Publication/Cancellations/
12:16:08 <kaz> present+ Daniel_Peintner, Zoltan_Kis
12:16:18 <cris_> dape: it should be possible to have the meeting
12:16:24 <cris_> ... but I might be late
12:17:09 <kaz> q+
12:17:38 <zkis> zkis has joined #wot-script
12:17:39 <cris_> cris: we can start 10 min later
12:17:58 <cris_> kaz: please record the decision on the wikis
12:18:46 <kaz> s/wikis/Scripting API wiki and the main wiki (cancellations section)/
12:18:46 <cris_> dape: we should also mention it during the main call
12:19:29 <kaz> q+
12:20:04 <dape> q+
12:20:07 <kaz> ack k
12:20:13 <kaz> topic: Publication schedule
12:20:22 <zkis> q+
12:20:26 <cris_> kaz: when do you think we will publish an updated note? middle February?
12:20:33 <cris_> dape: the sooner the better
12:20:46 <cris_> ... we are already collecting complex changes
12:21:08 <cris_> cris: I agree
12:21:10 <dape> ack dape
12:22:11 <cris_> zoltan: we basically have agreed to do two publications: one first with just fixes and the other with bigger refactors
12:22:13 <dape> q+
12:22:35 <cris_> ack z
12:22:39 <cris_> ack d
12:22:39 <kaz> ack d
12:22:54 <cris_> dape: we should also discuss about next charter proposal
12:24:36 <cris_> kaz: end of May is the deadline for the extended charter.
12:24:48 <cris_> ... we should choose carefully where we are going to fit in
12:25:19 <cris_> ... we should clarify questions one by one and deciding a concrete dealine
12:26:02 <dape> q?
12:26:39 <cris_> cris: ok I think we can start from clarifying the issues that we want to tackle in the first publication
12:26:53 <kaz> s/end of May is the deadline for the extended charter./end of July is the deadline of the extended Charter, but the WG would like to finish our work by the end of May./
12:27:06 <kaz> ack k
12:27:46 <kaz> s/we should clarify/my suggestion is clarifying/
12:28:49 <cris_> topic: Issue organization
12:29:42 <kaz> s/we should choose carefully where we are going to fit in/so we should carefully think about by when we should do what./
12:29:54 <cris_> cris: we already have a label for easy fixes of the apis
12:29:59 <cris_> zoltan: exactly
12:30:44 <kaz> i|we already|-> https://github.com/w3c/wot-scripting-api/issues wot-scripting issues|
12:32:43 <cris_> cris: should we add more issues?
12:34:38 <cris_> zoltan: 430 might fall in that category but I think we can do it as part of the next big pubblication
12:34:50 <kaz> q+
12:35:14 <kaz> s/pubb/pub/
12:35:56 <cris_> kaz: I partially agree with Zoltan. Clarifying relationships between spec documents is very important for the future
12:36:41 <cris_> ... how to use protocol binding from scripting API and how to send parameters and action between the peers (also error codes) is very important
12:37:01 <cris_> ... we need an additional categorization for issues
12:37:14 <cris_> ... across all WoT repositories
12:37:23 <cris_> cris: I agree
12:38:30 <cris_> ... maybe it is better to talk about it in the main call and define a common approach
12:39:44 <cris_> ... as suggestion for the next call we should fix the issue list and define the concrete dealine for the pubblication
12:40:06 <cris_> ... is that ok?
12:40:07 <cris_> kaz: ok
12:40:09 <cris_> dape: ok
12:40:24 <cris_> topic: Issues
12:40:31 <cris_> subtopic: Issue 422
12:40:37 <cris_> https://github.com/w3c/wot-scripting-api/issues/422
12:41:07 <cris_> dape: PR is ready to be reviewed
12:41:16 <cris_> ... see https://github.com/w3c/wot/pull/1068
12:41:38 <kaz> q+
12:41:42 <kaz> q?
12:41:51 <cris_> ... I added an item on the charter document
12:42:01 <cris_> ... a concise summary of our goals
12:42:22 <cris_> ... in the old charter we linked to the last published document
12:42:37 <cris_> ... now I'm linking to a very old published Scripting API document
12:42:46 <cris_> ... we should keep this in mind
12:42:50 <cris_> ... and update it
12:42:56 <dape> old charter: https://www.w3.org/2022/07/wot-wg-2022.html#other-deliverables
12:43:39 <cris_> q+
12:44:24 <kaz> -> https://github.com/w3c/wot-charter-drafts/pull/11 add scripting api as other deliverable to 2023 wg charter
12:44:44 <cris_> kaz: As a mentioned last week, I will copy the PR to the new charter repository
12:45:25 <cris_> dape: just a quick note, the PR is in draft mode until we approve it
12:46:04 <cris_> kaz: charter document should be approved by the whole working group
12:46:25 <cris_> ... the discussion should happen on charter specific meeting or main call
12:46:35 <dape> q+
12:47:12 <cris_> ... most important things to be noted in the charter are: what is normative and whant is not and liasons
12:47:38 <cris_> ... the question should be: would we like to make the scripting api normative again?
12:48:18 <cris_> q?
12:48:22 <kaz> ack k
12:49:33 <cris_> cris: We can talk about that topic in the next call
12:49:42 <zkis> q+ to ask if in issue 449 the filer, who is not member of the group, makes a non-substantial contribution
12:50:21 <cris_> ack cris
12:50:21 <zkis> q+ on the charter items
12:50:37 <cris_> cris: should we also mention onboarding or managining ?
12:51:02 <dape> https://github.com/w3c/wot-scripting-api/issues/422#issuecomment-1240381443
12:51:14 <kaz> s/I will copy the PR to the new charter repository/I have already copied the PR 1068 to the dedicated wot-charter-drafts repo as its PR 11./
12:52:13 <kaz> q+
12:52:25 <kaz> rrsagent, make log public
12:52:31 <kaz> rrsagent, draft minutes
12:52:32 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/06-wot-script-minutes.html kaz
12:52:39 <cris_> dape: we already decided that Scripting API should be a Normative Note
12:52:42 <dape> ack dape
12:52:56 <kaz> chair: Cristiano
12:53:31 <dape> q++
12:53:31 <cris_> zoltan: there was a formal objection against Scripting API being a normative document
12:53:40 <dape> ack +
12:53:50 <dape> qq+
12:53:54 <cris_> ... so if we want to change it we should address those comments
12:54:23 <kaz> s/I partially agree with Zoltan/I agree with Zoltan, and also would suggest some more./
12:54:31 <kaz> s/more../more./
12:54:39 <cris_> zoltan: managment api can happen on scripting API but usually they are tackled as a different security level
12:55:05 <cris_> ... my personal opinion is that it should be published in another document
12:55:13 <cris_> ... we can talke about configuration API
12:55:21 <cris_> s/talke/talk/
12:56:12 <cris_> q?
12:56:49 <cris_> zoltan: but it is important to discuss it
12:58:33 <kaz> ack d
12:58:33 <Zakim> dape, you wanted to react to +
12:58:39 <cris_> zoltan: please kaz check if https://github.com/w3c/wot-scripting-api/issues/449 is ok in regards to W3C policy
12:59:15 <cris_> dape: Just one comment, currently we are not aiming for a normative scripting api document
12:59:38 <cris_> ... this means that we didn't open the pandora box about formal objections
12:59:54 <dape> ack dape
13:00:08 <dape> ack zkis
13:00:08 <Zakim> zkis, you wanted to ask if in issue 449 the filer, who is not member of the group, makes a non-substantial contribution and to comment on the charter items
13:00:48 <cris_> kaz: basically regardless of the document type, we should not have ideas from no-members
13:01:11 <cris_> ... getting inputs for use cases is fine
13:01:22 <cris_> ... but for the wg work is complicated
13:02:11 <Mizushima> +1 kaz
13:02:21 <cris_> ... we should start from an use case
13:03:31 <cris_> ... we can work together with the user to define a complete use case
13:05:44 <kaz> s/charter document should be approved by the whole working group/We as the Scripting API TF can provide any proposals for the new Charter, but the WG as a whole is in charge of the Charter discussion./
13:05:50 <cris_> [adjourned]
13:06:03 <kaz> rrsagent, draft minutes
13:06:04 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/06-wot-script-minutes.html kaz
13:08:09 <Ege> Ege has joined #wot-script
13:09:41 <Ege> Ege has joined #wot-script
15:34:02 <Zakim> Zakim has left #wot-script