12:09:21 RRSAgent has joined #wot-script 12:09:25 logging to https://www.w3.org/2024/03/04-wot-script-irc 12:09:31 meeting: WoT Scripting API 12:09:32 topic: Minutes Review 12:09:50 ca: I checked the minutes and they were very useful as a short summary for the last time 12:10:01 ... I encourage everyone to do so as well 12:10:12 ... so as usual, we discussed the PRs 12:10:21 present+ Kaz_Ashimura, Cristiano_Aguzzi, Jan_Romann, Tomoaki_Mizushima 12:10:28 ... we are going to revisit the one first one today 12:10:35 i|checked|->https://www.w3.org/2024/02/19-wot-script-minutes.html Feb-19| 12:10:50 i|checked|scibenick: JKRhb| 12:10:52 ... very important is that we assigned Daniel to label the issues relevant for the TD taskforce 12:10:55 rrsagent, make log public 12:10:59 rrsagent, draft minutes 12:11:00 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:11:07 ... that's it, everyone okay with approving them? 12:11:51 ... there are a couple of IRC messages in-between the regular minutes, maybe we should remove them 12:11:58 Kaz: Will do 12:12:17 s/regular minutes/regular minute-taking/ 12:12:31 ... fixed, please reload 12:12:49 ca: If there are no other points, minutes are approved 12:12:54 Minutes are approved 12:13:00 topic: Updates 12:13:16 ca: As you probably heard, we are on a bi-weekly schedule 12:13:36 ... if you feel like there is there the need to change the schedule again, just let us know 12:13:43 topic: PRs 12:13:52 subtopic: PR 489 12:14:04 https://github.com/w3c/wot-scripting-api/pull/489 12:14:16 ca: This one is basically stalled, not sure if it can be fixed, for now this is mostly a reminder for us 12:14:22 subtopic: PR 534 12:14:29 https://github.com/w3c/wot-scripting-api/pull/534 12:14:42 ca: I want to talk about this one since Jan pushed some commits 12:14:48 s|https://github.com/w3c/wot-scripting-api/pull/489|-> https://github.com/w3c/wot-scripting-api/pull/489 PR 489 - Better types for Scripting API| 12:15:12 ... I remember that we discussed this last time and that there were some things that needed to be fixed 12:15:15 scribenick: cris_ 12:15:17 s|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:15:23 rrsagent, draft minutes 12:15:24 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:16:00 jan: I addressed the comments 12:16:00 ... I also discovered that default keyword (adressed to be a candidate for the algorithm) 12:16:07 ... it is just an annotation only for documentation 12:16:14 ... it is from json schema specification 12:16:21 ... and we can simply skip it 12:16:53 ... other than that I think the PR is ready to be merged 12:16:58 ... we can check the rendered document 12:17:23 ca: I share your view on default 12:17:37 ... was only meant as a documentation for developers 12:17:54 ... did not find the reference to JSON schema, glad that you did 12:18:13 ... we might be able to put some additional semantics in Web of Things 12:18:29 ... but this not well-defined yet so I am definitely fine with keeping it as is 12:18:51 ... (opens the rendered diff) 12:19:25 q+ 12:20:10 dape has joined #wot-script 12:20:16 ack k 12:21:25 (Kaz has no problem with Vivaldi browser, but Cristiano has problem with Firefox and the diff is highlighted by "black" :( ) 12:21:38 q+ 12:21:39 ... from my point of view these are fine 12:21:52 ... maybe we need to wait for Zoltan 12:22:05 s/Kaz has/Regarding the diff, Kaz has/ 12:22:24 ... is an improvement for developers, but not a perfect algorithm yet, can be further improved in the future 12:22:42 present+ Daniel_Peintner 12:22:44 dp: I approved the PR a while ago 12:22:54 ... gave thumbs up to the latest changes 12:23:09 ... but don't know how to proceed with the whole data schema topics 12:23:15 s/topics/topic/ 12:23:37 ... needs some further improvement in the future, but is an improvement already 12:23:46 ca: Then we can go ahead with merging this PR 12:23:56 ... (adds a comment to the PR) 12:24:27 ... if no one objects, then we can merge it 12:24:32 ack dape 12:24:51 ... of course we can always check back with Zoltan and fix it later on 12:25:02 No objections, PR is merged 12:25:11 subtopic: PR 545 12:25:20 ca: This is another draft PR by Jan 12:25:20 https://github.com/w3c/wot-scripting-api/pull/545 12:25:27 ... previously discussed this 12:25:33 scribenick: cris_ 12:25:49 jan: I tried to expand the exploreDirectory algorithm 12:26:04 ... maybe we can cover also the query api 12:26:17 s|https://github.com/w3c/wot-scripting-api/pull/545|| 12:26:30 i|This is|-> https://github.com/w3c/wot-scripting-api/pull/545 PR 545 - feat: expand exploreDirectory algorithm| 12:26:34 rrsagent, draft minutes 12:26:35 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:27:12 ... it's an early status 12:27:12 s/scibenick/scribenick/ 12:27:12 rrsagent, draft minutes 12:27:13 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:27:19 ... I will work on it for the next meeting 12:27:30 ... I want to add the ability to filter things 12:27:38 i|I share your view|scribenick: JKRhb| 12:27:40 rrsagent, draft minutes 12:27:41 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:27:57 ... basically using the search API 12:28:26 cris: do you mind to share some early ideas 12:29:43 jan: at the moment we can only use the things property 12:29:52 ... to retrieve thing descriptions 12:30:06 ... that's the only way implemented in the Scripting API spec 12:30:20 ... I wanted to add also actions for search things 12:30:27 ... search API 12:30:36 ... with that we can use json path and sparql 12:30:52 ... maybe we can have a wrapper algorithm 12:31:03 ... to identify which endpoint to use 12:31:19 ... we can also fallback to things API if search api is supported. 12:32:04 cris: do you want to create an abstraction layer for queries? 12:32:17 ... or simply sending string queries? 12:32:31 q+ 12:32:53 jan: just strings added to a basic payload that have an hint to the runtime about with query language to use 12:34:32 rrsagent, draft minutes 12:34:33 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:35:17 dape: I will keep it simply and it matches very well with the API 12:35:21 cris: +1 12:35:28 ack dape 12:36:22 topic: Issues 12:36:58 subtopic: Issues relevant for the TD Spec 12:37:13 ca: Maybe you can present the list you've got so far, Daniel? 12:37:46 i|dape:I will keep|scribenick: JKRhb| 12:38:15 i|Maybe|-> https://github.com/w3c/wot-thing-description/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needed+by+other+TF%22 Issues on wot-thing-description repo related to Scripting API| 12:38:16 rrsagent, draft minutes 12:38:17 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:38:47 q+ 12:38:59 dp: Sometimes there are several places we can link, but generally have labels defined both in the TD repo and the Scripting API repo 12:39:24 ... we need more feedback on how to handle actions, especially when it comes to querying and cancelling 12:39:33 ... this is currently underspecified in the TD spec 12:39:55 ... others are slightly less important, for example canonicalizations 12:40:18 ... was postponed a bit because people said that JSON-LD offers this functionality, but not sure about that 12:41:16 ... another issue is related to properties that are writable but might not process a value exactly as it is put it (e.g., with regard to precision) 12:41:49 q+ 12:41:50 ... a concrete example would be Phillips Hue, where the value that is actually written is returned 12:42:28 ... these are just examples, in general the linking is in the process which then need to be discussed in the TD taskforce 12:43:02 kaz: Very important work to clarifiy the relationship between TD and Scripting API, thank you for that 12:43:16 +1 12:43:32 ... however, the label in the TD repo should also say "Needed by Scripting API" 12:43:54 dp: Forgot to talk about this with Ege, will talk to him 12:44:15 ... that we have another label, will create an issue for that 12:45:01 ... in the TD repo 12:45:08 ca: Definitely agree with that 12:45:17 ... there should be different labels per taskforce 12:45:38 ... is there anything concrete to help the TD taskforce to move over with these issues? 12:45:38 ack k 12:45:42 ack c 12:45:45 q+ 12:45:46 ack c 12:46:05 dp: Currently, the TD taskforce is still in the process of preparing its work, no technical work is happening at the moment 12:46:34 ... maybe we could pick out a couple of issues that are the most important to us (one or two) 12:46:58 ... should form a consensus and then drive the issues forward in the TD taskforce and give our input in the calls 12:47:22 ... last week I couldn't join, but I think the technical work has not started, right? 12:47:26 ca: Correct 12:47:48 ... we probably also need to provide use cases 12:48:09 dp: Some are labelled with the use-cases label, maybe we need to talk to Ege and Michael Koster 12:48:27 kaz: This work between taskforces should be clarified in general 12:48:51 ... maybe the use-case discussion is also related to that 12:49:11 ... maybe we need to think about how to collaborate across taskforces in general 12:49:22 ... should be part of the WG procedure 12:49:24 ack k 12:49:54 ca: Agree, in general we should know how to process issues 12:50:09 ... currently, we are kind of making our own rules, should be clarified 12:50:43 dp: There are a lot of issues related to use cases, about 100 12:51:09 ca: Maybe we can integrate that in the use cases workflow, using the project 12:51:13 topic: AOB 12:51:28 ca: I think we can close early, any other business? 12:52:16 dp: I have something in my backlog regarding semantic @@@, but I will need to work a bit more on that, will present something at some point 12:52:33 ca: Do you have a use case in Siemens? 12:53:22 dp: So far, there is not much happening regarding semantic annotations in general, improving on that could be a great selling point for WoT 12:53:29 ... will keep you posted 12:53:44 ca: Another thing that came to my mind was the versioning problem 12:53:58 ... that could also be put on the agenda for the TD call 12:54:12 https://github.com/w3c/wot-scripting-api/issues/488 12:54:13 ... then we can publish a 1.0 version 12:54:26 https://github.com/w3c/wot-thing-description/pull/1969 12:54:34 ... this is related to issue 488 12:54:49 dp: There is a PR (1969) in the TD repo 12:54:55 ... but it still a draft 12:55:38 ca: I bring this up because we could then publish 1.0 under a tag and then make a clean up 12:55:51 ... will try to talk to Ege to clarify this 12:56:11 rrsagent, draft minutes 12:56:13 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:56:20 q+ 12:56:24 dp: Agree, versioning scheme should be clear, also to be able to publish snapshots inbetween 12:56:40 ca: Will talk to Ege as a homework 12:57:23 ... see you in two weeks 12:57:29 i/Maybe you can pre/scribenick: JKRhb/ 12:57:32 s/@@@/API 12:57:34 [adjourned] 12:57:44 ack k 12:57:51 rrsagent, draft minutes 12:57:52 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:58:49 i|I have something in|subtopic: Semantic API| 12:58:51 rrsagent, draft minutes 12:58:52 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 12:59:30 i/Another thing/subtopic: Versioning/ 12:59:31 rrsagent, draft minutes 12:59:33 I have made the request to generate https://www.w3.org/2024/03/04-wot-script-minutes.html kaz 15:16:36 Zakim has left #wot-script