11:53:08 <RRSAgent> RRSAgent has joined #wot-script
11:53:08 <RRSAgent> logging to https://www.w3.org/2022/01/31-wot-script-irc
11:53:29 <kaz> meeting: WoT Scripting API
12:00:35 <JKRhb> JKRhb has joined #wot-script
12:00:54 <dape> dape has joined #wot-script
12:01:41 <kaz> present+ Kaz_Ashimura, Jan_Romann
12:02:34 <cris> cris has joined #wot-script
12:03:17 <zkis> zkis has joined #wot-script
12:05:03 <Mizushima> Mizushima has joined #wot-script
12:05:29 <zkis> Meeting: WoT Scripting
12:05:41 <zkis> scribe: zkis
12:05:56 <zkis> Agenda:
12:06:21 <dape> --> https://www.w3.org/2022/01/24-wot-script-minutes.html
12:06:34 <zkis> Topic: past minutes
12:07:26 <zkis> No objections
12:07:35 <zkis> DP: minutes are public
12:07:39 <zkis> Topic: PRs
12:07:54 <dape> SUBTOPIC: resolve ReSpec warnings
12:07:59 <dape> --> https://github.com/w3c/wot-scripting-api/pull/368
12:08:26 <kaz> present+ Daniel_Peintner, Cristiano_Aguzzi, Tomoai_Mizushima, Zoltan_Kis
12:09:28 <zkis> DP: should we leave out JSON-LD reference<
12:09:33 <zkis> s/</?
12:09:52 <zkis> CA: not so critical, we can improve it later - but not very precise
12:10:27 <zkis> q?
12:11:24 <JKRhb> q+
12:11:26 <zkis> ZK: I suggest leaving it out and add it later when the formulation becomes more exact.
12:12:20 <zkis> Jan: we could mention that TDs are JSON-LD documents
12:13:20 <zkis> DP: the sentence was lifted from the TD spec abstract
12:13:22 <kaz> q+
12:13:30 <zkis> ack JK
12:13:33 <zkis> ack kaz
12:14:13 <zkis> KA: technically it depends on whether the group wants plain JSON, but we could just refer to the TD and don't mention details in the Scripting AP
12:14:32 <zkis> DA: true, but we could still explain something that is true
12:14:53 <zkis> ... meaning that JSON-LD tools can be used on it.
12:15:41 <zkis> KA: agree with Jan, if the group wants to give detail also in Scripting, but we can refer to TD since it's define elsewhere.
12:16:20 <zkis> ... if the TD definition is changed in the future, then we need to change it in every place
12:17:05 <zkis> DP: so we either remove it, or we add more explanation.
12:17:23 <cris> +1
12:17:46 <JKRhb> +1
12:18:21 <zkis> ZK: let's keep it simple and remove JSON-LD reference from now
12:18:46 <zkis> DP: so one more edit, and will merge afterwards.
12:19:05 <dape> SUBTOPIC: refactor: remove obsolete files
12:19:10 <dape> --> https://github.com/w3c/wot-scripting-api/pull/370
12:19:48 <kaz> q?
12:20:10 <kaz> q+
12:20:19 <zkis> DP: in the TD spec repo it was also removed
12:20:23 <zkis> KA: it's OK to remove
12:20:26 <zkis> ack kaz
12:20:41 <zkis> DP: merged
12:21:06 <dape> SUBTOPIC: Fixes some minor typos/issues
12:21:11 <dape> --> https://github.com/w3c/wot-scripting-api/pull/371
12:22:20 <zkis> ZK: just editorials, go ahead
12:22:25 <dape> SUBTOPIC: Generate types for unreachable definitions
12:22:29 <dape> --> https://github.com/w3c/wot-scripting-api/pull/372
12:23:08 <zkis> CA: this relates to TypeScript and JSON schema definitions
12:23:32 <zkis> ... there was a problem with TypeScript tools
12:23:59 <zkis> ... so for undefined things it will generate definitions
12:24:13 <zkis> ... adds almost no information
12:24:38 <zkis> ... opened an issue on how can we add this feature to the dependency library, no answer yet
12:25:20 <zkis> ... these comments can stay for the moment
12:26:12 <JKRhb> q+
12:26:28 <zkis> DP: fine for me
12:27:03 <zkis> Jan: for TD there isn't a comment generated (probably not referenced) - but isn't there a comment field in the definition?
12:27:20 <zkis> CA: already addressed this in the comments on the PR
12:29:10 <zkis> DP: if we merge it, we should create an issue to remind checking later
12:30:38 <zkis> Jan: a number of merge conflicts, should rebase first
12:30:41 <zkis> CA: right
12:31:32 <zkis> DP: will create the issue
12:31:49 <zkis> q?
12:31:56 <zkis> ack JK
12:32:37 <dape> SUBTOPIC: Thing model types
12:32:43 <dape> -> https://github.com/w3c/wot-scripting-api/pull/373
12:33:11 <zkis> DP: creates TS definitions for Thing Models
12:33:26 <zkis> ... useful for implementations
12:33:37 <zkis> CA: indeed in node-wot we needed these
12:33:59 <zkis> ... also update the script in the github CI
12:34:07 <zkis> s/update the/updated the
12:34:32 <zkis> ... not tested yet, though
12:35:00 <zkis> DP: some typos still
12:36:54 <zkis> CA: and some conflicts to fix before merging
12:37:43 <zkis> Topic: issues
12:37:55 <dape> SUBTOPIC: Conformance section necessity
12:38:00 <dape> --> https://github.com/w3c/wot-scripting-api/issues/354
12:38:10 <kaz> q+
12:38:26 <zkis> ack kaz
12:38:58 <zkis> KA: if the WG would like to publish a document named WG Note which includes normative content, we can do that, but it's not a W3C recommendation.
12:39:36 <zkis> ZK: so we need a group resolution
12:40:07 <zkis> KA: the W3C process is changing these days, and defined a group note track, which we can use, based on the WG resolution
12:40:21 <zkis> DP: will add an agenda item on the main call
12:42:26 <zkis> ZK: we should check the content of the Note track before the main call
12:43:10 <zkis> KA: if the Scripting TF wants to go a certain way, we can record a TF resolution and then bring it to the WG for a WG resolution
12:44:23 <zkis> DP: updated the comment in the issue
12:45:07 <zkis> ZK: we also need to send a formal email to the group
12:47:29 <dape> SUBTOPIC: Rename Use Cases section
12:47:33 <dape> -> https://github.com/w3c/wot-scripting-api/issues/355
12:48:23 <kaz> q?
12:49:24 <zkis> action: ZK creates a PR proposal
12:49:29 <cris> +1
12:49:42 <kaz> q+
12:50:05 <zkis> ack kaz
12:51:28 <dape> SUBTOPIC: Using a callback-based approach for Discovery
12:51:34 <dape> --> https://github.com/w3c/wot-scripting-api/issues/364
12:53:54 <JKRhb> q+
12:54:09 <zkis> DP: should we treat this together with Cristiano's proposal for new API
12:54:13 <zkis> ack Jan
12:54:32 <JKRhb> ack JK
12:54:52 <zkis> ZK: let's treat them separately
12:55:03 <zkis> Jan: should we make a PR on this?
12:56:03 <zkis> ZK: no, let's first agree on the WebIDL before the PR  - or well, we can start with a PR and change that one
12:56:20 <zkis> Jan: yes, we can start with that
12:57:01 <zkis> ZK: only that in a PR there are much more comments if there is disagreement on the API details
12:57:13 <zkis> Jan: will post in the issue first, then
12:58:34 <zkis> DP: we should stop here, time is up
13:02:33 <zkis> adjourned
13:02:39 <kaz> rrsagent, make log public
13:02:43 <kaz> rrsagent, draft minutes
13:02:43 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/31-wot-script-minutes.html kaz
13:04:12 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#31_January_2022
13:04:13 <kaz> rrsagent, draft minutes
13:04:13 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/31-wot-script-minutes.html kaz
13:05:07 <kaz> chair: Daniel
13:05:09 <kaz> rrsagent, draft minutes
13:05:09 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/31-wot-script-minutes.html kaz
13:48:57 <zkis> zkis has joined #wot-script
14:02:57 <zkis_> zkis_ has joined #wot-script
14:55:10 <Zakim> Zakim has left #wot-script