Table A.1 shows Identifiers assigned to Attributes
Table A.1 – Identifiers assigned to Attributes
|
Attribute |
Identifier |
|
NodeId |
1 |
|
NodeClass |
2 |
|
BrowseName |
3 |
|
DisplayName |
4 |
|
Description |
5 |
|
WriteMask |
6 |
|
UserWriteMask |
7 |
|
IsAbstract |
8 |
|
Symmetric |
9 |
|
InverseName |
10 |
|
ContainsNoLoops |
11 |
|
EventNotifier |
12 |
|
Value |
13 |
|
DataType |
14 |
|
ValueRank |
15 |
|
ArrayDimensions |
16 |
|
AccessLevel |
17 |
|
UserAccessLevel |
18 |
|
MinimumSamplingInterval |
19 |
|
Historizing |
20 |
|
Executable |
21 |
|
UserExecutable |
22 |
|
DataTypeDefinition |
23 |
|
RolePermissions |
24 |
|
UserRolePermissions |
25 |
|
AccessRestrictions |
26 |
|
AccessLevelEx |
27 |
Clause A.2 defines the numeric identifiers for all of the StatusCodes defined by the OPC UA Specification. The identifiers are specified in a UTF8 encoded CSV file with the following syntax:
<SymbolName>, <Code>, <Description>
Where the SymbolName is the literal name for the error code that appears in the specification and the Code is the hexadecimal value for the StatusCode (see OPC 10000-4). The severity associated with a particular code is specified by the prefix (Good, Uncertain or Bad).
The CSV released with this version of the standards can be found here:
https://reference.opcfoundation.org/files/StatusCode.csv?u=http://opcfoundation.org/UA/&v=1.05.03
NOTE The latest CSV that is compatible with this version of the standard can be found here:
https://reference.opcfoundation.org/files/StatusCode.csv?u=http://opcfoundation.org/UA/
Clause A.3 defines the numeric identifiers for all of the numeric NodeIds defined by the OPC UA Specification. The identifiers are specified in a UTF8 encoded CSV file. The syntax is informative and provided to assist developers of tools. The UANodeSet is the normative source for all identifiers.
Each line in the CSV file has the following fields:
<SymbolName>, <Identifier>, <NodeClass>
Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears in the specification and the Identifier is numeric value for the NodeId. Each SymbolName is unique within the CSV file.
The BrowsePath for an instance Node may be constructed by appending the BrowseName of the instance Node to BrowseName for the containing instance or type. A ‘_’ character is used to separate each BrowseName in the path. For example, OPC 10000-5 defines the ServerType ObjectType Node which has the NamespaceArray Property. The SymbolName for the NamespaceArray InstanceDeclaration within the ServerType declaration is: ServerType_NamespaceArray. OPC 10000-5 also defines a standard instance of the ServerType ObjectType with the BrowseName ‘Server’. The BrowseName for the NamespaceArray Property of the standard Server Object is: Server_NamespaceArray.
When Nodes do not have a parent that allows the creation of unique SymbolNames then an ad-hoc convention should be adopted. For example, DataTypeEncoding Nodes have the form:
<DataTypeName>_Encoding_<BrowseName>
The NamespaceUri for all NodeIds defined is http://opcfoundation.org/UA/
The CSV released with this version of the standards can be found here:
https://reference.opcfoundation.org/files/NodeIds.csv?u=http://opcfoundation.org/UA/&v=1.05.03
NOTE The latest CSV that is compatible with this version of the standard can be found here:
https://reference.opcfoundation.org/files/NodeIds.csv?u=http://opcfoundation.org/UA/
Globally defined media types are assigned by IANA. This clause lists the media types that have been assigned by IANA to document formats defined by OPC UA.
Table A.2 has media types assigned to OPC UA document formats.
Table A.2 – Media Types Assigned to OPC UA Document Formats
|
Media Type |
Description |
|
application/opc-nodeset+xml |
An XML document that conforms to the XML schema defined in Annex F. It contains set of Nodes. |