IRC log of wot-script on 2022-02-28

Timestamps are in UTC.

12:02:01 [RRSAgent]
RRSAgent has joined #wot-script
12:02:01 [RRSAgent]
logging to https://www.w3.org/2022/02/28-wot-script-irc
12:02:16 [dape]
dape has joined #wot-script
12:04:49 [kaz]
meeting: WoT Scripting API
12:04:55 [Mizushima]
Mizushima has joined #wot-script
12:05:04 [kaz]
present+ Kaz_Ashimura, Daniel_Peintner, Zoltan_Kis
12:06:57 [cris]
cris has joined #wot-script
12:08:34 [kaz]
present+ Tomoaki_Mizushima
12:08:46 [kaz]
present+ Cristiano_Aguzzi
12:08:49 [zkis]
scribenick:zkis
12:09:00 [zkis]
Topic: previous minutes
12:09:10 [dape]
-> https://www.w3.org/2022/02/21-wot-script-minutes.html
12:09:21 [kaz]
s/html/html Feb-21/
12:09:36 [zkis]
no objections
12:09:39 [zkis]
minutes approved
12:10:00 [zkis]
Topic: quick updates
12:10:22 [zkis]
DP: on the main call it was asked when Scripting TF will update the spec
12:10:47 [zkis]
DP: it depends on the other publications; TD is stable, others maybe not
12:10:52 [kaz]
rrsagent, make log public
12:10:56 [kaz]
rrsagent, draft minutes
12:10:56 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/28-wot-script-minutes.html kaz
12:11:06 [cris]
+1
12:11:07 [zkis]
DP: we could wait a few weeks that the dependent specs are updated
12:11:43 [zkis]
DP: currently the main dependency is Discovery
12:11:48 [zkis]
Topic: PRs
12:12:13 [dape]
-> https://github.com/w3c/wot-scripting-api/pull/386
12:12:30 [zkis]
DP: there is a stalled PR (dependent on discovery) and the obsolete package lock (link above(
12:12:37 [zkis]
s/above(/above)
12:13:01 [kaz]
i/386/subtopic: PR 386/
12:13:22 [kaz]
s/386/386 PR 386 - refactor: remove obsolete package-lock.json files in sub-directories/
12:13:44 [zkis]
Topic: issues
12:13:57 [dape]
SUBTOPIC: Check alignments with Architecture
12:14:05 [dape]
-> https://github.com/w3c/wot-scripting-api/issues/376
12:14:12 [zkis]
i/issues/Subtopic: issue 376
12:14:58 [kaz]
s/SUBTOPIC: Check alignments with Architecture//
12:15:21 [kaz]
s/376/Issue 376 - Check alignments with Architecture/
12:15:29 [kaz]
rrsagent, draft minutes
12:15:29 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/28-wot-script-minutes.html kaz
12:16:05 [kaz]
chair: Daniel
12:16:44 [zkis]
DP: the discussion converged on text aligned with the conformance classes
12:16:50 [zkis]
DP: any objections?
12:17:13 [zkis]
DP: will prepare the PR for Architecture
12:18:16 [zkis]
Subtopic: issue 384
12:18:19 [dape]
-> https://github.com/w3c/wot-scripting-api/issues/384
12:18:47 [zkis]
DP: there is a related PR in Discovery
12:19:07 [zkis]
CA: establish minimal requirement for client in order to be able to discover
12:19:28 [zkis]
... now it includes HTTP
12:20:37 [zkis]
s/HTTP/HTTPS
12:20:54 [kaz]
s/384/384 Issue 384 - Align discovery and scripting/
12:22:34 [zkis]
DP: the work should continue beyond HTTP
12:22:49 [zkis]
... in Scripting we'll have the same restriction
12:23:04 [zkis]
CA: yes, the discovery conformance class must implement HTTPS
12:23:46 [zkis]
ZK: it doesn't change the API shape, but it has to be clear in the spec, for implementations
12:23:58 [zkis]
DP: there was also a pagination that only worked in HTTP
12:24:13 [zkis]
... was that the reason why HTTP is mandatory?
12:25:12 [zkis]
ZK: did they study the CoAP discovery, e.g. in OCF - that is a very clear mechanism
12:25:20 [zkis]
CA: yes, it was considered
12:25:56 [zkis]
DP: do we know when they plan to converge on this?
12:26:21 [zkis]
CA: the deadline is close, but is not known (it's being shifted)
12:28:03 [zkis]
ZK: this is not a strong dependency for Scripting, only for implementations (node-wot)
12:28:19 [zkis]
CA: there is the issue why Scripting allows using the Fetch API
12:28:48 [zkis]
ZK: Scripting discovery API may use also other architectural solutions for discovery than the one described in the Discovery spec
12:29:07 [dape]
SUBTOPIC: Conformance section necessity
12:29:16 [dape]
-> https://github.com/w3c/wot-scripting-api/issues/354
12:30:50 [zkis]
DP: the chairs need to send an email to the AC reps participating in the WG
12:30:53 [dape]
-> https://www.w3.org/2022/02/23-wot-minutes.html#t05
12:31:10 [zkis]
... since Notes are not covered by W3C patent policy, so it needs to be agree within the WG
12:32:00 [zkis]
KA: we need to think about how to deal with normative sections in Notes, but we might also put the Scripting API back to the REC track in the next charter
12:32:11 [zkis]
DP: one doesn't exclude the other in my opinion
12:33:04 [zkis]
ZK: the point was that ML didn't consider this side-agreement a clean solution
12:33:13 [zkis]
... it would be cleaner to be regulated by the W3C process
12:33:25 [zkis]
KA: let's check with the chairs about the progress
12:33:48 [zkis]
DP: OK, so let's keep this open
12:34:20 [dape]
SUBTOPIC: New op values (queryaction and cancelaction)
12:34:27 [dape]
--> https://github.com/w3c/wot-scripting-api/issues/335
12:34:33 [kaz]
s/354/354 Issue 354 - Conformance section necessity/
12:35:07 [zkis]
DP: in the TD spec the PR was merged which introduced the new op values
12:35:39 [dape]
-> https://github.com/w3c/wot-thing-description/pull/1208/files
12:35:43 [cris]
q?
12:35:48 [cris]
q+
12:36:38 [zkis]
DP: we might need to change the API, e.g. invokeAction()
12:37:14 [kaz]
s/335/335 Issue 335 - New op values (queryaction and cancelaction)/
12:37:17 [zkis]
CA: we can query only one instance of an action
12:37:54 [zkis]
DP: my assumption was that we need to know the action instance in order to be able to later interact with it
12:38:30 [zkis]
... so we cannot just add 2 new methods like queryAction() and cancelAction()
12:38:35 [zkis]
CA: so we need to change the return value
12:40:34 [cris]
q+
12:42:19 [zkis]
ZK: can we identify action instances on the wire (i.e. protocol binding dependent)?
12:43:11 [zkis]
DP: that was my assumption
12:43:52 [zkis]
q+
12:43:55 [zkis]
ack cris
12:44:12 [zkis]
CA: it's quite difficult to specify an algorithm to handle action instances
12:44:31 [zkis]
... if the TD doesn't define this well
12:44:55 [zkis]
DP: we need to check if it's not well defined
12:45:38 [zkis]
CA: in the last plugfest we experimented with this
12:46:17 [zkis]
CA: if an invokeAction() returns a JSON, how can we fake that as a control object?
12:46:21 [zkis]
... it will be complex
12:48:30 [zkis]
ZK: we can define an action control object that has a callback (event) for completion, returning InteractionOutput, and one method for querying
12:49:02 [zkis]
CA: what if different things will return different results for the same action?
12:52:40 [zkis]
ZK: I still think we could do a control object that will work
12:53:29 [zkis]
... I could draft a few alternatives in the issue, and when we have consensus, we can decide and make a PR
12:53:49 [zkis]
DP: yes, and as CA mentioned, we should check the TD spec completeness as well
12:54:07 [zkis]
q?
12:54:10 [zkis]
ack z
12:56:07 [zkis]
DP: we can also query (and cancel?) all actions
12:57:01 [zkis]
CA: the feature is in risk because no implementations yet
12:57:16 [zkis]
DP: sooner or later there will be implementations, even for Profiles
12:57:47 [zkis]
... but if no one implements these, then it's out of the game
12:58:00 [zkis]
CA: the Things gateway implements this on protocol level
12:59:24 [zkis]
ZK: I think it would make even more sense to support cancel all actions, than query all actions
12:59:39 [zkis]
... we need to wait until this is clarified, since it will change the API shape
12:59:46 [kaz]
rrsagent, draft minutes
12:59:46 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/28-wot-script-minutes.html kaz
13:00:36 [zkis]
DP: I will take a look at that
13:02:01 [kaz]
q+ to whisper we need to move to another call
13:02:09 [zkis]
DP: Ben had a use case for querying all actions
13:02:17 [zkis]
ZK: looks like network optimization, makes sense
13:02:25 [zkis]
DP: we need to adjourn
13:02:30 [zkis]
adjourned
13:02:34 [kaz]
rrsagent, draft minutes
13:02:34 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/28-wot-script-minutes.html kaz
13:02:37 [kaz]
q-
13:05:37 [kaz]
agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#28_February_2022
13:05:39 [kaz]
rrsagent, draft minutes
13:05:39 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/02/28-wot-script-minutes.html kaz
13:08:03 [Mizushima]
Mizushima has left #wot-script
15:06:49 [Zakim]
Zakim has left #wot-script