IRC log of wot-script on 2024-02-05
Timestamps are in UTC.
- 12:02:17 [RRSAgent]
- RRSAgent has joined #wot-script
- 12:02:22 [RRSAgent]
- logging to https://www.w3.org/2024/02/05-wot-script-irc
- 12:02:24 [kaz]
- meeting: WoT Scripting API
- 12:02:59 [kaz]
- present+ Kaz_Ashimura, Cristiano_Aguzzi, Jan_Romann
- 12:03:11 [Mizushima]
- Mizushima has joined #wot-script
- 12:05:12 [JKRhb]
- JKRhb has joined #wot-script
- 12:10:30 [kaz]
- present+ Tomoaki_Mizushima
- 12:11:40 [kaz]
- scribenick: kaz
- 12:12:03 [kaz]
- agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#February_5%2C_2024
- 12:12:18 [kaz]
- topic: Minutes
- 12:12:25 [kaz]
- -> https://www.w3.org/2024/01/29-wot-script-minutes.html Jan-29
- 12:12:56 [kaz]
- ca: have reviewed them
- 12:13:28 [kaz]
- ... any objections?
- 12:16:07 [kaz]
- (some minor problem with the CSS style, etc.)
- 12:16:17 [kaz]
- regrets+ Zoltan
- 12:16:38 [kaz]
- approved
- 12:16:52 [kaz]
- topic: Cancellations
- 12:17:10 [kaz]
- ca: next week, the Scripting API call will be cancelled
- 12:17:38 [kaz]
- topic: Feedback from TD TF
- 12:17:41 [dape]
- dape has joined #wot-script
- 12:19:17 [kaz]
- ca: joint discussion with the TD TF
- 12:19:47 [kaz]
- -> https://github.com/w3c/wot-scripting-api/issues?q=is%3Aissue+is%3Aopen+label%3Await-for-td Issues with wait-for-td label
- 12:20:23 [dape]
- present+ Daniel_Peintner
- 12:20:36 [kaz]
- ... about meta operation work item, etc.
- 12:21:29 [kaz]
- q+
- 12:22:02 [kaz]
- kaz: think we should clarify the procedure for the joint discussion as well
- 12:22:19 [kaz]
- ... how to continue the collaborative discussion, etc.
- 12:22:20 [kaz]
- ack k
- 12:22:24 [kaz]
- ca: yeah
- 12:22:33 [kaz]
- ... should clarify our goals, etc.
- 12:22:39 [kaz]
- q?
- 12:22:47 [kaz]
- rrsagent, make log public
- 12:22:53 [kaz]
- rrsagent, draft minutes
- 12:22:54 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/02/05-wot-script-minutes.html kaz
- 12:23:03 [kaz]
- topic: PRs
- 12:23:20 [kaz]
- subtopic: PR 534
- 12:23:32 [cris_]
- https://github.com/w3c/wot-scripting-api/pull/534
- 12:23:50 [kaz]
- s|https://github.com/w3c/wot-scripting-api/pull/534|-">https://github.com/w3c/wot-scripting-api/pull/534|-> https://github.com/w3c/wot-scripting-api/pull/534 PR 534 - fix(InteractionOutput): don't require schema.type in value function|
- 12:24:09 [kaz]
- jr: discussion over node-wot as well
- 12:24:30 [kaz]
- ... schemas can be more complex
- 12:24:44 [kaz]
- ... multiple different schemas are possible
- 12:25:15 [kaz]
- ... this PR moves one proposal to summarize the discussion so far
- 12:25:32 [kaz]
- ... we need to remove (some of) the type requirements
- 12:25:41 [kaz]
- ... proposing to add constraints
- 12:26:21 [kaz]
- ... adding this suggestion might not make sense for some cases
- 12:26:26 [dape]
- q+
- 12:26:37 [kaz]
- ... not sure if we can merge PR now
- 12:26:38 [cris_]
- q+
- 12:26:43 [kaz]
- ... maybe need some more discussion
- 12:28:24 [kaz]
- q+
- 12:28:51 [kaz]
- -> https://pr-preview.s3.amazonaws.com/JKRhb/wot-scripting-api/pull/534.html#the-check-data-schema-algorithm rendered HTML - 7.2.3 The check data schema algorithm
- 12:28:59 [kaz]
- dp: maybe we can shift the validator
- 12:29:18 [kaz]
- ... the possible downside is valiadation without any library
- 12:29:36 [kaz]
- ... not sure if we want to put any additional requirement
- 12:29:39 [dape]
- ack dape
- 12:29:40 [kaz]
- ca: good pint
- 12:29:44 [kaz]
- s/ping/point
- 12:29:55 [dape]
- s/pint/point
- 12:29:57 [kaz]
- ... we're using JSON Schema for two purposes
- 12:30:18 [kaz]
- ... for scripting itself and protocol binding applications
- 12:30:31 [kaz]
- ... put requirements for our logic which is not existing yet
- 12:31:02 [kaz]
- ... what to be done for random bytes?
- 12:31:17 [kaz]
- ... would it be a real requirement?
- 12:32:20 [kaz]
- ... not sure if everything is allowed by TD
- 12:32:40 [JKRhb]
- q+
- 12:32:41 [cris_]
- ack c
- 12:32:41 [kaz]
- ... anyway JSONSchema is not a standard
- 12:34:00 [kaz]
- ack k
- 12:34:04 [kaz]
- kaz: agree
- 12:34:19 [kaz]
- ... JSONSchema is only one possible mechanism for validation
- 12:34:45 [kaz]
- ... we should start with our own spec text for Scripting API
- 12:35:02 [kaz]
- ... if we can apply JSONSchema for that purpose luckily, that's fine
- 12:35:05 [kaz]
- ca: agree
- 12:35:18 [kaz]
- ack k
- 12:35:24 [kaz]
- jr: maybe we can't cite JSONSchema
- 12:35:41 [kaz]
- ... but need to define necessary algorithm ourselves
- 12:36:01 [kaz]
- ca: not sure about the expected data mapping here completely
- 12:36:17 [kaz]
- ... e.g., around the second channel data
- 12:36:26 [kaz]
- ... it's not trivial about the mapping
- 12:36:32 [dape]
- q+
- 12:36:37 [kaz]
- ... have to look into the detailed use cases
- 12:36:43 [kaz]
- ... tx for your input, Jan
- 12:36:46 [kaz]
- ack jk
- 12:37:07 [kaz]
- dp: we've been already defining some simple form of JSONSchema here
- 12:37:17 [kaz]
- ... we could continue to work on that direction
- 12:37:25 [kaz]
- ... or can also work on one-off definition
- 12:37:42 [kaz]
- ... but for simplicity, reducing the complexity would be better
- 12:37:58 [kaz]
- ... e.g., no need for validation on our own
- 12:38:25 [kaz]
- ... would try to cover them with too strict restriction with JSONSchema
- 12:38:49 [kaz]
- ca: would be kind of compromise for us until we clarify the detail on the mapping payload
- 12:39:09 [kaz]
- ... we should not work on the detail now
- 12:41:19 [kaz]
- ... btw, everything in the table 4 at 5.3.1.2 InteractonAffordance from WoT Thing Description is optional
- 12:41:38 [kaz]
- -> https://w3c.github.io/wot-thing-description/#interactionaffordance TD spec ED - 5.3.1.2 InteractionAffordance
- 12:42:20 [kaz]
- -> https://w3c.github.io/wot-thing-description/#dataschema TD spec ED - 5.3.2.1 DataSchema
- 12:42:29 [kaz]
- s|-> https://w3c.github.io/wot-thing-description/#interactionaffordance TD spec ED - 5.3.1.2 InteractionAffordance||
- 12:42:35 [dape]
- q?
- 12:42:38 [dape]
- ack dape
- 12:43:09 [kaz]
- s/at 5.3.1.2 InteractonAffordance/at "5.3.2.1 DataSchema"/
- 12:43:17 [kaz]
- rrsagent, draft minutes
- 12:43:18 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/02/05-wot-script-minutes.html kaz
- 12:43:50 [kaz]
- ca: (adds comments to PR 534)
- 12:44:24 [kaz]
- q|
- 12:44:27 [kaz]
- s/q|//
- 12:44:28 [kaz]
- q+
- 12:45:29 [kaz]
- ack k
- 12:45:43 [kaz]
- kaz: which vocabulary terms to be handled here?
- 12:46:49 [kaz]
- ca: think we need four of them: @@@
- 12:47:20 [kaz]
- s/@@@/oneOf, const, enum, @@1/
- 12:47:26 [kaz]
- q+
- 12:47:39 [kaz]
- s/@@1/default/
- 12:47:55 [kaz]
- dp: can put "?" for "default" here?
- 12:48:05 [kaz]
- ca: (put "?" to "default")
- 12:48:25 [kaz]
- ... related to Issue 537
- 12:48:49 [kaz]
- -> https://github.com/w3c/wot-scripting-api/issues/537 Issue 537 - Proposal: use TD default values
- 12:49:26 [kaz]
- ca: Jan, can you work on "default"
- 12:49:33 [kaz]
- s/t"/t"?/
- 12:49:37 [kaz]
- jr: ok
- 12:49:47 [cris_]
- q?
- 12:50:15 [kaz]
- ack k
- 12:50:33 [kaz]
- kaz: it would be nicer to have some brief description for each parameter
- 12:50:51 [kaz]
- ... e.g., in which case for what, we need "enum"
- 12:50:55 [kaz]
- ca: yeah
- 12:51:09 [JKRhb]
- +1
- 12:51:17 [kaz]
- ... important to describe the use cases
- 12:51:49 [kaz]
- ... maybe need some additional description for that
- 12:52:52 [kaz]
- subtopic: PR 538
- 12:53:10 [kaz]
- -> https://github.com/w3c/wot-scripting-api/pull/538 PR 538 - Type definition generator information to readme
- 12:53:15 [kaz]
- dp: typo?
- 12:53:46 [kaz]
- s/typo?/typo causing a merge conflict?/
- 12:53:48 [kaz]
- ca: ah
- 12:54:11 [kaz]
- dp: can copy the first line
- 12:54:31 [dape]
- q?
- 12:54:37 [kaz]
- merged
- 12:54:54 [kaz]
- subtopic: PR 543
- 12:55:10 [kaz]
- -> https://github.com/w3c/wot-scripting-api/pull/543 PR 543 - fix: respec warnings about anchor/link
- 12:55:19 [kaz]
- dp: simply fixes
- 12:55:30 [kaz]
- s/fixes/fixes about ReSpec issues/
- 12:55:58 [kaz]
- merged
- 12:56:16 [kaz]
- subtopic: PR 544
- 12:56:28 [kaz]
- -> https://github.com/w3c/wot-scripting-api/pull/544 PR 544 - fix: minor capitalization typo
- 12:56:32 [kaz]
- ca: another typo fix
- 12:58:24 [kaz]
- q+
- 12:58:47 [kaz]
- ack k
- 12:59:22 [kaz]
- kaz: do we want to use "DoS" acronym for the title as well?
- 12:59:44 [kaz]
- ... "DoS" is more popular as a possible risk than "Denial of Service"
- 12:59:47 [kaz]
- ca: ok
- 12:59:58 [kaz]
- ... (adds "(DoS)" to the title too)
- 13:00:00 [kaz]
- merged
- 13:00:38 [kaz]
- [adjourned]
- 13:00:43 [kaz]
- rrsagent, draft minutes
- 13:00:45 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/02/05-wot-script-minutes.html kaz
- 13:01:15 [kaz]
- s/[adjourned]//
- 13:01:18 [kaz]
- topic: Next call
- 13:01:29 [kaz]
- ca: let's continue the discussion next time
- 13:01:39 [kaz]
- ... remember we won't have the call next week on Feb 12
- 13:01:43 [kaz]
- [adjourned]
- 13:01:46 [kaz]
- rrsagent, draft minutes
- 13:01:47 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/02/05-wot-script-minutes.html kaz