– DRAFT –
WoT Scripting API

past minutes

<cris> https://www.w3.org/2024/12/11-wot-script-minutes.html

Cristiano: suggested corrections to the minutes

Minutes approved.

<kaz> (typos, etc., have been fixed)

PRs

PR 561

PR 561 - Extended return type of invokeAction()

Zoltan: we need to map better the interactions (actions) to the scripting patterns

Cristiano: the CG is working on the AI agent framework using WoT
… we can ask feedback from there

Cristiano: originally I considered using events to solve this problem, but we can step back and check other options

Cristiano: we should check the new profile spec for actions
… we had query and cancel actions, but not observe actions

Zoltan: we should look at developer best practices on exposing agentic flows and action handling and then come back.

Cristiano: yes, the underlying systems could return even percentage of completion, and we should support it.

<kaz> WoT Profile - 9. HTTP Basic Profile

Daniel: showing the HTTP Basic Profile for WoT
… we have invokeAction, query, cancel, queryAll

Zoltan: we should have the action control object, that is ActionInteractionOutput. That should include cancel(), completed() as promises, and status as a getter.
… the status format is mapped from the TD

Cristiano: we should stick to the TD spec, query and cancel the action and leave it to the script to do polling or events

Daniel: in the TD we have the op values, but query is not necessarily supported for each Thing

Cristiano: ok, then we can go with the promise approach for cancel() and query()

Zoltan: what would the query() return?

Cristiano: it could be another ActionInteractionOutput object

Zoltan: it's too complex that way

<kaz> WoT Thing Description 1.1 ED - 5.3.4.2 Form

Zoltan: it seems the query status is not defined in the TD spec
… so we have a gap there?
… maybe we should ask Ege

Cristiano: will do

Daniel: right, let's open an issue at the TD spec

Cristiano: the Profile spec assumes to report the status as an object or error

<dape> WoT Profile - 9.2.2.2 queryaction

Kaz: the whole WoT WG needs to think how to handle the result of querying actions

issues

issue 507

<cris> Issue 507 - Should we refactor getThingDescription to a JS getter?

Cristiano: we are considering these, but not decided

Zoltan: I agree that `getThingDescription()` is not very webby, but then we must spec how to deal with the internal slot, when to initialize etc.

Web Platform Design Principles Note

Zoltan: we should read again the web platform design principles

and also spec coding conventions: https://github.com/webmachinelearning/webnn/blob/main/docs/SpecCodingConventions.md
… we should at least align with these.

Cristiano: time up, meeting adjourned.

<kaz> [adjourned]