W3C

WoT Scripting API

25 October 2021

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura, Tomoaki_Mizushima, Zoltan_Kis
Regrets
-
Chair
Daniel
Scribe
kaz

Meeting minutes

Slide for the vF2F

Scripting API slides

Daniel: have generated slides
… ToC includes "Consume options", etc.
… [Consume options - Reduce TD size & complexity]
… each interaction ca specify formindex
… proposed API change

Cristiano: looks good

Daniel: [Discovery improvements]
… discovery spec is not fully ready
… Scripting discovery API
… an What's next?
… other ways of discovery?
… security concerns: separate library network interface

Cristiano: exposing yourself?
… need discussion during vF2F

Daniel: (adds points on how to use ConsumedThing as ExposedThing, e.g., properly test it)
… consume ExposedThing
… own Constructor
… discovery using discovery function
… (might be discussed separately)
… [Action state and control]
… how the Actions look like
… proposed changes in API (control object)
… from: Prose<IteractioOutput> invokeAction(...)
… to: Promise<ActionControl> invokeAction(...)
… several open points
… [Expose options]
… separate API entry point + security from client API (discovery + consume)

Cristiano: one after another

Daniel: possible change for ExposedThing as already shown
… if you have any comment, please give that
… also wondering about testing
… [Eclipse node-wot]
… recent status/update

Cristiano: good to be presented
… struggling to catch up the recent changes of the Scripting API
… need to speed up
… what do you think?

Cristiano: someone needs to review what is missing

Daniel: first implement and then update the spec?

Kaz: we need to think about what to be done/documented during this Charter period, i.e, within 3 months
… and what to be done during the next Charter period
… Scripting API is currently a group Note
… but we still need to think about that

milestone calculator

Daniel: what to do during the next Charter?
… maybe TD signing?
… also keep up with new features

Kaz: Scripting API is a group note, so have more flexibility
… but depends on the Thing Description spec

Daniel: and the Discovery spec
… what about the Profile spec?

Kaz: yeah
… and that's why I suggest we have Editors calls regularly

Daniel: we need to make up decision on our side too

Kaz: yes

Daniel: would like to create issues on that point

Kaz: ok

Daniel: e.g., security management and scripting management for the next period

(discussion on "Reduce TD size & complexity)

(also about "Expose options")

Daniel: will reorganize the slides

Zoltan: summary slide on where node-wot is used would be useful

Daniel: (adds that point)

Kaz: btw, regarding some of your points, e.g., how to reduce TDs, how to expose Things,
… we should be able to ask those implementers about their opinions

Daniel: definitely

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).