W3C

WoT Scripting API

25 September 2023

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Jan_Romann, Kaz_Ashimura, Tomoaki_Mizushima
Regrets
-
Chair
Cristiano/Daniel
Scribe
dape, kaz

Meeting minutes

Previous minutes

-> Sept 18

Cristiano: Minutes look good. Names need to be fixed
… no objections -> minutes are approved

Publication check

Cristiano: Still waiting...

Kaz: I am working on it
… maybe publish it today or tomorrow
… will ping webmaster as well

Scripting API report

Cristiano: Briefly talked about it in main call
… other pressing issues in main call
… we might need to ping again
… not sure "when" to do it or "where" to do it

Daniel: Yes, we might need to wait a bit

Kaz: General report during main call makes sense
… this week we will have policy discussions in main call.. and might take longer
… suggest to make report in 2 weeks or so

Cristiano: Yes, let's put topic on hold for now

What's next

Cristiano: Start reviewing use-cases...
… looking into missing features
… I guess we might need to wait for re-chartering

Daniel: In the meanwhile we can look into existing issues

<kaz> wot-scripting-api issues

Cristiano: I checked some issues as well..
… some are not about use-cases.. just technical improvements
… Zoltan had also some improvements in mind
… labeling and such is very welcome

PRs

Better types for Scripting API P R489

w3c/wot-scripting-api#489

Cristiano: I tried to improve typing for scripting API
… helps to get better (more precise) errors
… for example the name of properties is checked
… helps to avoid typos
… this is the goal of the PR
… I ask you to review it

Daniel: Nice work.. will take a look

Jan: Promising work
… is the union of string needed?

Cristiano: Tricky
… if "T" is any.. keyof causes issues

Jan: Union does not prevent auto completion, right?

Cristiano: It should work just fine

Jan: Great

Cristiano: Will discuss this PR again next week....

Discovery

Jan: Updated PR in node-wot w.r.t. discovery
… might be 2 things worth discussing
… wondering about explore function..
… and general discover method

<cris_> node-wot PR

Jan: direct method is a left over
… I implemented requestThingDescription ... works quite well
… a more general question I had was about exploreDirectory
… url pointing to TD
… should we consume TD ?

Cristiano: I suggest to start experimenting with it

Kaz: Wondering about relationship between this Pullrequest 864 on the node-wot repository and W3C WoT specifications. Which WoT spec is related to this Pullrequest, WoT Scripting API, WoT Discovery or WoT Thing Description?

Cristiano: We are exploring discovery API
… impact for Scripting API

Jan: If general tests work we can align the API

Cristiano: Concrete implementations can help

Kaz: Shall we talk about it in Discovery calls as well?

Cristiano: Maybe, but we are not there yet

Kaz: So this is a trial implementation to see what kind of API definition would be the best, and proposal for the WoT Discovery spec should be also made after settling the discussion.

Jan: second question
… about general discover function
… in implementations how to specify which kind of discovery should happen?

Jan: multiple protocols supported but how to limit discovery to CoAP only?
… I was wondering about 2nd argument

Cristiano: I think this goes on with new feature discussion
… we might need use-cases

Jan: ThingFilter no longer contains URL anymore ...

Cristiano: Would be nice to have some backtracking what is needed

Cristiano: AOB ?

-> none -> [adjourned ]

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).