Companion specification · Tier 2

WoT-Con

Version1.02.0
Published2025-12-05
Namespacehttp://opcfoundation.org/UA/WoT-Con/
SectorWeb of Things connectivity

The Web of Things connectivity model, at 1.02.0 as of December 2025 and among the more actively developed Tier-2 models. It bridges W3C Web of Things Thing Descriptions and OPC UA, which matters as web-native and industrial description approaches converge.

Where it sits in the stack

Built on the core information model, published in the OPC 10100 series. It is the OPC UA side of a bridge whose other side is a W3C standard.

The types that matter

TypeWhat it carries
(type inventory not confirmed)We have not verified the type inventory. Browse the released nodeset.

Using it on a real machine

  1. Understand the two sidesA WoT Thing Description is a JSON document describing a thing's interaction affordances. This model is how that meets an OPC UA address space.
  2. Note the activityRevised through 2024 and 2025 - one of the more active models here, which suggests real interest.
  3. Consider it for non-OPC UA devicesThe interesting application is bringing web-native devices into an OPC UA world without writing a bespoke adapter for each.

What it gives you for OEE

No direct OEE contribution. Its relevance is architectural: if some of your equipment speaks web protocols rather than OPC UA, this is a standards-based route to a single namespace instead of a pile of custom adapters.

Try it free: No free public server exposes this model as far as we know. To see it you need a machine that implements it or a vendor demo. If you find a public endpoint, tell us and we will add it.

Gotchas

  • Actively developed - revised through 2024 and 2025.
  • Requires understanding both the WoT Thing Description model and OPC UA. Two learning curves.
  • Its value is architectural convergence, not production data.
Verify before you rely on this: We have not verified the type inventory or the current maturity of implementations. The type inventory on this page is deliberately short. We list only type names we are confident of and would rather publish five correct ones than twelve with four wrong. Browse a real server or the released nodeset for the complete list.

Once the machine speaks a companion spec, the OEE mapping is portable across vendors, which is the point at which analytics stops being a per-machine project.

See Jemba →

Last verified 7 September 2026 against OPC UA 1.05.07. Version and publication date read from the released nodeset. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.

Free download
OPC UA Machine Data → OEE Mapping Kit
Which nodes to subscribe to, how they become Availability, Performance and Quality, and which companion specification already gives you the answer, so you stop inventing tags.
Get the free mapping kit →
Free, no course, no login