W3C

– DRAFT –
WoT Scripting API

29 October 2025

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Zoltan_Kis
Regrets
-
Chair
-
Scribe
zkis

Meeting minutes

Previous minutes:

<cris> https://www.w3.org/2025/07/23-wot-script-minutes.html

Discussing automated meeting minutes taking by recording and summarization tools.

Host rights are needed for this, and needs integration in W3C minutes management.

Minutes approved.

PRs

PR #578

<cris> w3c/wot-scripting-api#578

DP: fine with merging

PR merged.

issues

ReSpec error for async_iterable not found

ZK: should check the doc headers for the xref tag

CA: we should ask for help

issue #530

<cris> w3c/wot-scripting-api#530

ZK: we could close this, as a Fetch example is not strictly needed for publication.

CA: issue closed.

issue #531

w3c/wot-scripting-api#531

DP: Profiles supports it and we could also do it now.

CA: what extra things we need to do on the top of the Scripting API
… if we support TD, we automatically support all the Profiles
… maybe too much to track individually each Profile

DP: I agree
… some Profiles are a superset of the TD, but nowadays they are subsets.

CA: the only issue is the "all_..." operations for Events, observing properties, query all actions
… Scripting does not support those. Will comment on the issue.

DP: propose a change, instead of returning InteractionOutput, return ActionInteractionOutput.

CA: no other mechanisms needed.

DP: ack dape

DP: commenting on the not supported ops (not the "all" forms) -- in code we could shim by looping, but it's not the same

CA: since it should do a single network request
… implementations can choose to loop, or use the form from the TD with single network request
… always the schema dictates
… the problem is which schema to use in the "all" methods
… apps might need to do the parsing themselves for value

ZK: what is important for Scripting is whether this needs mandatory algorithmic steps or API changes

CA: noticed we cannot shim by looping since the algorithm rejects if there is no single network operation e.g. in readAllProperties()

Web MCP relationship

ZK: should investigate the synergies of WoT with MCP/Web MCP, working together with the Web NN CG
… something for the future

meeting adjourned

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

Maybe present: CA, DP, ZK

All speakers: CA, DP, ZK

Active on IRC: cris, dape, zkis