Namespace
The InnovaEdge twin type namespace
This URI identifies the type library of a digital twin modelled in InnovaEdge. If you arrived from an i3X namespace declaration, an OPC UA NodeSet or a Thing Description, this page is what that identifier means.
https://innovaplatform.org/twin/v1
01 — The scheme
One namespace per tenant, not one for everybody.
Each organisation authors its own object types. If every tenant declared them under a single shared URI, an outside consumer could not tell one organisation's type library from another's — two different types could claim the same global identity. So each tenant gets its own namespace beneath this base.
Base
https://innovaplatform.org/twin/v1— reserved for a shared platform type library that tenant namespaces can extend through the ordinary import path.
Per tenant
https://innovaplatform.org/twin/v1/orgs/<organization>— the namespace that uniquely identifies one organisation's type library.
Why these do not resolve individually
A namespace URI is an identifier, not a fetchable resource, and serving a page per organisation would publish a list of who the customers are. The types themselves are served to authorised callers by the i3X server, not from this site.
Stability
Permanent identifiers. The v1 segment marks the namespace scheme, not a release of the product — a tenant's namespace does not change when the platform ships.
02 — Where the types come from
The same model that configures the device.
Types in this namespace are not a separate modelling exercise performed after the fact. The definition that configures a device and parses what it sends back is the definition served to plant systems as i3X, exported as an OPC UA NodeSet2, or emitted as a Thing Description. An existing i3X namespace or NodeSet2 can also be imported, and its types register alongside the ones authored here.
Full interoperability surface: i3X, OPC UA, WoT and Sparkplug. The annotation vocabulary used inside a Thing Description is separate — see the i3X annotation vocabulary.