W3C’s Physical AI Agenda Starts With Describing Devices
An AI agent spots the lamp on your desk in a camera image. How does it find the address to call to switch that lamp off, and what is W3C adding by 2028?
- The renewed W3C Web of Things charter includes physical AI and guidance for agents interacting with devices.
- Thing Descriptions express device capabilities and access information in a machine-readable form.
- TD 2.0 targets Recommendation status in June 2028; this is a development agenda, not a finished universal control agent.
An agent needs to know what a device exposes
In its October 21 announcement, W3C explained how the Web of Things Working Group’s renewed charter includes physical AI. The charter began on September 14. Planned developer resources will address agents discovering devices, sensing their environment and taking actions through them.
WoT addresses fragmented device ecosystems, including buildings and industrial automation. Its approach is to describe access across existing protocols, giving applications a common way to understand what otherwise disparate devices offer.
Properties, actions and events do different jobs
The Thing Description 1.1 Recommendation, published in 2023, supplies the existing foundation. A TD includes capabilities, data schemas, communication details and security metadata.
| Element | Specification’s lamp example | Purpose |
|---|---|---|
| Property | status | Read or control a parameter. |
| Action | toggle | Invoke a function that changes the lamp’s state. |
| Event | overheating | Deliver an asynchronous notification. |
The example also associates capabilities with access URLs. Identifying an object as a lamp is different from knowing where to request its status or invoke its controls.
Separate the existing specification from the next deliverables
The charter proposes richer descriptions for matters such as time-series values, dynamic resources and location. Its schedule includes these targets:
| Deliverable | Target | Role |
|---|---|---|
| WoT Binding Registry | Q1 2027 draft | Maintain records of protocol bindings. |
| WoT Primer and Best Practice | Q4 2027 | Developer guidance including AI agents and MCP. |
| Thing Description 2.0 | June 2028 Recommendation | Extend the description model. |
These dates are planning targets. A product requirement that assumes TD 2.0 is already complete would get ahead of the published roadmap.
A description does not grant permission
The charter relies on existing security mechanisms. Changes to underlying protocols remain the responsibility of their respective standards organizations.
The WoT security guidelines illustrate why access still needs enforcement. Their home-network scenario includes a guest reaching camera footage or requesting a door unlock when proper authentication is missing. Being able to describe an operation does not decide who should be allowed to perform it.
TPAC takes place in Dublin on October 26–30 and includes a three-day Plugfest. These hands-on interoperability sessions test how implementations work together.
FAQ
Does WoT replace HTTP or MQTT?
No. Bindings connect the WoT model to existing protocols; both appear in the new work plan.
Can an agent control every device once it has a TD?
A TD describes capabilities and access information. The connection, authentication and authorization still need implementation.
The practical advance is a richer common description of devices. Evaluate supported capabilities and protocols alongside the permissions needed to use them.