Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/opcfoundation/ua-nodeset

UA Nodeset
https://github.com/opcfoundation/ua-nodeset

companion-specification normative-files opc-ua-specifications uanodeset

Last synced: 1 day ago
JSON representation

UA Nodeset

Awesome Lists containing this project

README 

        
# OPC UA NodeSets and Other Supporting Files



## Contents



* [Files Found Here](#files-found-here)

* [Release Process](#release-process)

* [Error reporting](#error-reporting)



## Files Found Here



This repository contains UANodeSets and other normative files which are released with a specification.

Any change to a specification (release of a new version or errata) may require a change to the files in this repository.  



For each specification the following normative files need to be published:



* .NodeSet2.xml - The formal definition of the Nodes defined by the specification;

* .Types.xsd - The XML schema for the DataTypes defined by the specification;

* .Types.bsd - The OPC Binary schema for the DataTypes defined by the specification (obsolete);

* .NodeIds.csv - A CSV file containing the NodeIds assigned to Nodes defined by the specification;



In addition, the following non-normative support files may be published:



* .Classes.cs - C# classes for Nodes used with the [.NETStandard](https://github.com/OPCFoundation/UA-.NETStandard) stack;

* .DataTypes.cs - C# classes for DataTypes used with the [.NETStandard](https://github.com/OPCFoundation/UA-.NETStandard) stack;

* .Constants.cs - C# constant declarations used with the [.NETStandard](https://github.com/OPCFoundation/UA-.NETStandard) stack;

* .PredefinedNodes.uanodes - A non-normative binary representation of the UANodeSet for use with [.NETStandard](https://github.com/OPCFoundation/UA-.NETStandard) stack;



If a companion specification working group uses the ModelCompiler to create the UANodeSet then the following files are published:



* .Model.xml - The Nodes defined by the specification using the [schema](https://github.com/OPCFoundation/UA-ModelCompiler/blob/master/Opc.Ua.ModelCompiler/UA%20Model%20Design.xsd) needed by the [ModelCompiler](https://github.com/OPCFoundation/UA-ModelCompiler);

* .Model.csv - The NodeIds assigned to the Nodes defined by the specification;



For the core OPC UA specifications the following additional files are published:



* StatusCode.csv - The StatusCodes defined by the OPC UA specification;

* AttributeIds.csv - The identifiers for the Attributes defined by the OPC UA specification;

* UNECE_to_OPCUA.csv - The numeric codes assigned to the UNECE units (see Part 8);

* ServerCapabilities.csv - The ServerCapabilities defined by the OPC UA specification (see Part 12);

* Opc.Ua.NodeSet2.Services.xml - A UANodeSet that includes DataTypes which are used only with OPC UA Services;

* OPCBinarySchema.xsd - The OPC Binary schema definition;

* UANodeSet.xsd - The UANodeSet schema definition;

* SecuredApplication.xsd - The SecuredApplication schema definition (see Part 6);



The files for each companion specification are in a subdirectory with the short name of the specification.

The files for the core specification are in the Schema subdirectory.



## Release Process



**This repository contains the latest released versions of the normative files.**



The [member-only version](https://github.com/OPCF-Members/UA-NodeSet) has draft and release candidate versions of the files.



Instructions on requesting access to the member only repository can be found [here](https://opcf-members.github.io/Help/).



Tags are applied whenever a NodeSet is released. **Use the tags if a older version is required.**



The v1.04 and v1.03 branches are only updated when errata are published.



When the files are reviewed and published a tag will be created in this repo with the publication date specified in the UANodeSet. 



**Note**: that adding tags is a step that was added late in the process so tags prior to 2019-05-01 do not exist and users must use the dates on the commits.  



**There are currently 4 branches in the repository:**



* latest - the latest released version of all nodesets.

* v1.05 (obsolete - merged into latest but tags prior to 2022-05-01 reference this branch).

* v1.04

* v1.03



When a companion specification is released it will be added to the latest branch and tagged.



## Error reporting



If an error or problem is found in any of the files it should be [reported](https://apps.opcfoundation.org/mantis/main_page.php) as a mantis issue against the appropriate specification.



More information on the process can befound [here](https://opcfoundation.org/resources/issue-tracking/).