wot-specs: revise WoT Binding and add registry-first Connectivity 1.1

README.md

@@ -19,6 +19,9 @@ See [`CONTRIBUTING.md`](CONTRIBUTING.md) for the full workflow, validation, and
 
 - `companion-specs/` — draft OPC UA companion specifications, one folder per domain.
   - `Generators/` — draft Companion Specification for electrical power **Generator Sets (GenSets)**: the information model (`Opc.Ua.Generators.NodeSet2.xml`), the NodeId assignments (`Opc.Ua.Generators.NodeIds.csv`), the specification document, and `tools/build_model.py` — a generator that emits the NodeSet, CSV, and reference tables from a single source of truth.
+- `wot-specs/` — Web of Things specification drafts and their supporting tools/examples, kept separate from OPC UA Core and domain companion-specification work.
+  - `WoT-Binding/` — draft **OPC UA — Web of Things (WoT) Binding**: a standalone revision of OPC 10101 that describes an OPC UA interface as a W3C Thing Description / Thing Model — preserving the official `uav` vocabulary, the Read / Write / Observe / Call and security mappings, and the URI rules — and adds a collision-safe model/platform vocabulary plus a bidirectional NodeSet2 conversion with a `uav:nodeSet` preservation envelope. Contains the specification, the JSON-LD context, an extension/preservation JSON Schema, worked examples, and a standard-library `tools/validate_local.py`.
+  - `WoT-Connectivity/` — draft **OPC UA — WoT Connectivity** (additive revision **1.1**): a **registry-first** revision of OPC 10100-1 that layers a W3C Thing Model / Thing Description **document registry** over the abstract [`xregistry/`](core-specs/xregistry/) base model (`WoTRegistryType` subtypes `RegistryType`; `ThingDescriptionGroupType`/`ThingModelGroupType` subtype `GroupType`; `ThingDescriptionFileType`/`ThingModelFileType` subtype the abstract `WoTDocumentType` `ResourceType`), exposed as a well-known `WoTRegistry` Object under the **Server** object (`i=2253`). The stored documents/versions are canonical; the OPC UA AddressSpace is a **derived, shadow-switched, generational projection** (Thing Models → types, Thing Descriptions → instances, affordances → Variables/Methods/EventTypes, links → References, forms → binder plans) with a `Refresh` Method, validation/load/refresh events, and desired/active version lifecycle. The full **OPC 10100-1 v1.02** model is **incorporated into the same combined NodeSet and namespace** — preserving every published NodeId (`1..172`), type and method signature — and its superseded management surface is marked `Deprecated` (per OPC 11030); the revised WoT Binding `uav` vocabulary is a normative JSON-LD dependency (not a NodeSet `RequiredModel`). Contains the specification, the generated combined NodeSet (`Opc.Ua.WoTCon.NodeSet2.xml`) / CSV, the pinned 1.02 sources under `legacy/`, the canonical `tools/build_model.py`, a standard-library `tools/validate_local.py`, and worked examples.
 - `core-specs/` — draft **extensions to the base OPC UA specification** (proposed additions to the `http://opcfoundation.org/UA/` namespace), intended for submission to an OPC Foundation Working Group. Each encoding/catalog folder below contains only the **normative** spec documents, its `README.md`, and the **base reference schema**; all tooling, examples, generated (non-base) schemas, and the shared validation package live under `core-specs/extras/` (a parallel, mirrored tree).
   - `openusd-binding/` — draft *OPC UA — OpenUSD Bindings*: a generic representation, live-binding, command, alarm, and composition layer that lets any OPC UA companion model drive OpenUSD prims through a discoverable `Server/OpenUSD` contract. Contains the base NodeSet, CSV, specification document, and implementer addenda for `pumps/` and `robotics/`; runnable descriptors, USD assets, writers, renderers, and tutorials live under `core-specs/extras/openusd-binding/examples/`.
   - `observability-export/` — draft *OPC UA — Observability Export*: a small, transport-neutral layer that lets a Server, or a companion specification, declare **how its data lands in an observability system** — as OpenTelemetry (OTEL) **metrics, logs and traces** — so a generic read-only **bridge** can forward it over the **classic client/server (RPC) interface** and, **optionally**, over **PubSub (Part 14)** without understanding the domain. Contains the base NodeSet, CSV, and specification document, plus one **standardized subfolder per companion spec** (`pumps/`, `robotics/`, `facets/`, `di/`), each holding the companion-spec **addendum(s)** and the instance-overlay `NodeSet2.xml`. The generator tooling and example descriptor sources live under `core-specs/extras/observability-export/` (below). A non-normative **overview deck** ([`core-specs/observability-export/README.md`](core-specs/observability-export/README.md)) summarizes the why, what and how.