net10.0.NETFramework4.7.2.NETFramework4.8net8.0net9.0.NETStandard2.1
OPC UA xRegistry abstract registry base model (Annex B): content-addressed resource identity, companion NodeSet and shared registry abstractions.
Published
Jan 1, 1900
128y ago
Total Downloads
0
0
Install
dotnet add package OPCFoundation.NetStandard.Opc.Ua.XRegistry.Debug --version 2.0.0-preview.2
| Product | Versions |
|---|---|
| .NET | |
| .NET Standard | |
| Other |
README
Opc.Ua.XRegistry
The abstract xRegistry registry base model for OPC UA: a content-addressed resource-registry companion namespace plus the shared abstractions a concrete registry (for example a schema registry) builds on.
This package contains:
- the
http://opcfoundation.org/UA/xRegistry/abstract base companion model, compiled into the assembly by the OPC UA model source generator — the ObjectTypes, their Methods and Variables, the generatedNodeStateclasses and the*TypeClientObjectType proxies. No NodeSet2 XML is parsed at runtime; XRegistryWellKnown— the base companion namespace URI and the provisional NodeIds of the instances a registry materializes at runtime (the registry root, the federation proxy and the start of the dynamic instance range). The identifiers of the model itself come from the generatedObjectTypeIds,MethodIdsandVariableIdsclasses;IResourceContentIdProvider— the seam that maps a resource document + format to its content-derived identity (the fingerprint that makes a resource addressable by an Opaque NodeId, stable across registries).
It has no dependency on the OPC UA server or client SDKs; the generic client and server
pieces live in Opc.Ua.XRegistry.Client and Opc.Ua.XRegistry.Server.
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
This version is marked prerelease. Validate its API and upgrade path before production use.No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.Compatibility metadata lists 6 target frameworks; confirm the exact target used by your application.The published metadata declares 124 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.