Search

Scope: Core (OPC-10000-*) All specs

73 result(s) for namespaceIndex

OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

3.3.2 Conventions for defining NodeClasses

standard are defined by their name, which is mapped to the BrowseName having the NamespaceIndex 0, which represents the Namespace for OPC UA. The Use column (optional or mandatory) does
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.2 NodeId

identifier NodeId elements of a Node as well as the Namespace Uri which the namespaceIndex NodeId element references. A Server may change the namespaceIndex NodeId element of a Node with ... future Sessions and therefore a Client shall not assume the namespaceIndex will not change. The structure of the NodeId is defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.3 DataType NodeClass

with the BrowseName "Default Binary" or "Default XML" having the NamespaceIndex 0. The BrowseName of the DataTypeEncoding Objects shall be unique in the context
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.22.1 Overview

exposed shall be the same as the field name of the Structure DataType . The NamespaceIndex of the BrowseName shall be the same as the NamespaceIndex of the Structure DataType which ... BrowseName of the Parent Node and 'N' shall be the array index number. The NamespaceIndex of the BrowseName shall be the same as the NamespaceIndex of the DataType which first
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.25 HasFieldDescription

name as the field of the Structured DataType that it refines, and the same NamespaceIndex as the DataType , where the field of the Structure is defined. The DataType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.29 AllowedSubtype

Variable describes the used DataType including its ValueRank. However, it should not use the NamespaceIndex of the DataType NodeId unless it is defined in the same Namespace
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.2.4 Identifier value

parameter. A canonical null NodeId has an IdType equal to Numeric , a NamespaceIndex equal to 0 and an Identifier equal to 0. In addition to the canonical null NodeId ... shall be considered a null NodeId . Table 24 - NodeId Alternative Null Values IdType NamespaceIndex Null Value String 0 A null or Empty String ("") Guid 0 A Guid initialised
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.7 BaseDataType

encoding defined in OPC 10000-6 . Any direct subtype shall only be defined in NamespaceIndex 0. A BaseDataType is an abstract DataType which represents any possible value including arrays
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.24 Integer

encoding defined in OPC 10000-6 . Any direct subtype shall only be defined in NamespaceIndex
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.30 Number

encoding defined in OPC 10000-6 . Any direct subtype shall only be defined in NamespaceIndex
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.33 UInteger

encoding defined in OPC 10000-6 . Any direct subtype shall only be defined in NamespaceIndex
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.51 StructureField

BrowseName of the DataVariable shall be the same as the StructureField name and the NamespaceIndex of the BrowseName shall be the same as the Structure DataType Node NamespaceIndex
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

C.2.3 Extended notation

values of all DataTypes should be represented by an appropriate string representation. Whenever a NamespaceIndex or LocaleId is used in those structures they can be omitted. The DisplayName contains ... text used in the graphical representation of a Node . The BrowseName contains the NamespaceIndex and a String . Such a structure can be exposed as [<NamespaceIndex>:]<String
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.1 AdditionalParametersType

read the Server's current NamespaceArray . This means that only names with a NamespaceIndex of 0 or 1 may be used in the requests for these Services. Companion specifications ... vendors can define names in for use with NamespaceIndex 1 if they add prefix that ensures uniqueness. The same restriction applies to values which contain DataTypes with NamespaceIndexes . The components
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.3 FilterOperator

Locale to "". QualifiedName values are converted to Strings by dropping the NamespaceIndex . Strings are converted to QualifiedName values by setting the NamespaceIndex to 0. A StatusCode
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.35 SessionAuthenticationToken

identify a Node in the AddressSpace . Servers may assign a value to the NamespaceIndex ; however, its meaning is Server specific
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.2.3 QueryFirst

allowed to specify a NodeId in the QualifiedName. This is done by setting the namespaceIndex of the targetName to zero and the name part of the targetName ... relativePath may contain a type NodeId. This is done by setting the namespaceIndex of the targetName to zero and the name part of the targetName to the XML representation
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.1 Overview

string representation of relative paths is used instead of the actual structure. The NamespaceIndex used in all examples is 12 (it could just as easily have been ... value). For more information about NamespaceIndex , see OPC 10000-3 . The use of the NamespaceIndex illustrates that the information model being used in the examples is not a model defined
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

4.1 NodeIds

based on the InstanceDeclaration described above has the symbolic name "Server.ServerCapabilities.MinSupportedSampleRate". The NamespaceIndex for all NodeIds defined in this standard is 0. The namespace for this NamespaceIndex ... Server . The NodeIds of those Nodes are server-specific, including the Namespace. However the NamespaceIndex of those Nodes cannot be the NamespaceIndex 0, because they are not defined
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

4.2 BrowseNames

Nodes defined in this standard is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this document
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

5.1 General

General For all Nodes specified in NamespaceIndex 0, the Attributes named in Table 3 shall be set as specified in Table 3 . Table 3 - Common Node Attributes Attribute Value DisplayName
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

5.2 Objects

Objects For all Objects specified in NamespaceIndex 0, the Attributes named in Table 4 shall be set as specified in Table 4 . Table 4 - Common Object Attributes Attribute Value EventNotifier
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

5.3 Variables

Variables For all Variables specified in NamespaceIndex 0, the Attributes named in Table 5 shall be set as specified in Table 5 . Table 5 - Common Variable Attributes Attribute Value MinimumSamplingInterval
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

5.4 VariableTypes

VariableTypes For all VariableTypes specified in NamespaceIndex 0, the Attributes named in Table 6 shall be set as specified in Table 6 . Table 6 - Common VariableType Attributes Attributes Value Value
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

5.5 Methods

Methods For all Methods specified in NamespaceIndex 0, the Attributes named in Table 7 shall be set as specified in Table 7 . Table 7 - Common Method Attributes Attributes Value Executable
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.13 NamespaceMetadataType

example, be done by using the index of the namespace in the NamespaceArray as NamespaceIndex of the QualifiedName and the namespace URI as name of the QualifiedName . The NamespaceUri Property ... this Namespace . A Node of this Namespace is identified by having the corresponding NamespaceIndex in the NodeId . A Client can use the ConfigurationVersion Property in conjunction with the Constant Field
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.14 NamespacesType

example, be done by using the index of the namespace in the NamespaceArray as NamespaceIndex of the QualifiedName and the namespace URI as name of the QualifiedName . Clients should
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.29 BitFieldType

DataVariable shall be the same as the BitFieldDefinition name field and the NamespaceIndex of the BrowseName shall be the same as the BitFieldDefinition name field's NamespaceIndex . Optional bit fields
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.31 DataTypeSchemaHeader

array of namespace URIs. The index into the array is referred to as NamespaceIndex . The NamespaceIndex is used in NodeIds and QualifiedNames , rather than the longer namespace URI. NamespaceIndex ... identify an element in this list. The first entry in this array maps to NamespaceIndex 1. structureDataTypes StructureDescription[] Description of Structure and Union DataTypes used in the data that follows
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.12 QualifiedName, NodeId and ExpandedNodeId String Encoding

ExpandedNodeId String Encoding QualifiedNames , NodeIds and ExpandedNodeIds optimize representation of NamespaceUris by using a NamespaceIndex to reference the location of the URI in a NamespaceTable . The NamespaceTable ... 4HEXDIG) "-" 12HEXDIG <opaqueid> = "b=" BASE64 NodeIds with a NamespaceIndex of 0 or a NamespaceUri of http://opcfoundation.org/UA/ shall only use the <identifier
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.9 NodeId

defined. Table 18 - Standard NodeId Binary DataEncoding Name Data Type Description Namespace UInt16 The NamespaceIndex . Identifier * The identifier which is encoded according to the following rules: NUMERIC UInt32 STRING String
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.10 ExpandedNodeId

NodeId structure by allowing the NamespaceUri to be explicitly specified instead of using the NamespaceIndex . The NamespaceUri is optional. If it is specified, then the NamespaceIndex inside the NodeId shall ... encoding NamespaceUri as a String . An instance of an ExpandedNodeId may still use the NamespaceIndex instead of the NamespaceUri . In this case, the NamespaceUri is not encoded in the stream
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.15 ExtensionObject

specification have a numeric node identifier assigned to them with a NamespaceIndex of 0. The numeric identifiers are defined in A.3 . Decoders use this field to determine the syntax
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.10 NodeId

encoded as a JSON string using the format defined in 5.1.12 . NodeIds in NamespaceIndex 0 use the <identifier> form. All other NodeIds use the <namespace ... form. The first abnormal state occurs when the encoder cannot map a NamespaceIndex to a NamespaceUri . In this case, the encoder shall encode the NamespaceIndex using the <namespace-index
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.11 ExpandedNodeId

ServerIndex . If this occurs the decoder shall set the ServerIndex to 0, the NamespaceIndex to 0, the IdType to String and the Identifier to the JSON string. When the ServerIndex ... decoders shall replace a NamespaceUri with a NamespaceIndex when a mapping exists or if a mapping can be created. If no mapping exists or one cannot be created the NamespaceUri
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.14 QualifiedName

JSON string using the format defined in 5.1.12 . The form with the NamespaceIndex is not allowed unless there is an encoding error. This can occur when the encoder cannot ... NamespaceIndex to a NamespaceUri . In this case, the encoder shall encode the NamespaceIndex using the <namespace-index> form. The decoder shall pass this NamespaceIndex to the application
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.3 UANode

String with the form: <namespace index>:<name> Where the NamespaceIndex refers to the NamespaceUris table. SymbolicName String A symbolic name for the Node that
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.15 Example

Namespaces referenced in the document except for the base OPC UA InformationModel. A NamespaceIndex of 1 refers to the URI " http://sample.com/Instances" . <NamespaceUris ... document that cannot be edited by hand. No matter which DataTypeEncoding is used, the NamespaceIndex used in the ManufactureName field refers to the NamespaceUris table in this document. The application
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.2 NodeId

encoding of this field. Namespace This field is a JSON number with the NamespaceIndex . The field is omitted if the NamespaceIndex is 0. For NonReversibleEncoding this field is the JSON ... string containing the NamespaceUri associated with the NamespaceIndex unless the NamespaceIndex is 0. If the NamespaceIndex is 0 the field is omitted
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.3 ExpandedNodeId

NamespaceUri if the NamespaceUri is specified. Otherwise, it is a JSON number with the NamespaceIndex. The field is omitted if the NamespaceIndex is 0. For NonReversibleEncoding this field ... JSON string containing the NamespaceUri or the NamespaceUri associated with the NamespaceIndex unless the NamespaceIndex is 0 or 1. If the NamespaceIndex is 0 the field is omitted. ServerUri
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.5 QualifiedName

QualifiedName . Uri For ReversibleEncoding this field is a JSON number with the NamespaceIndex . The field is omitted if the NamespaceIndex is 0. For NonReversibleEncoding this field is the JSON string ... containing the NamespaceUri associated with the NamespaceIndex unless the NamespaceIndex is 0. If the NamespaceIndex is 0 the field is omitted
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.8.2 Namespace table

Proxy constructs the translated name as follows: QualifiedName translatedName = new QualifiedName(Name,(ushort) ServerMappingTable[NamespaceIndex]) where Name - the unqualified browse name of the Node NamespaceIndex - the Server index the ServerMappingTable
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.2 PubSub configuration properties

that can be applied to all PubSub components are defined in Table 4 . The NamespaceIndex of the QualifiedName in the KeyValuePair for properties defined in this document shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.2 DataTypeSchemaHeader

potentially contained in the associated DataSetMessages . DataTypes defined in the OPC UA namespace ( NamespaceIndex 0) that are not built-in types or the abstract types Number , UInteger , Integer or Enumeration
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.7.4 ConnectionProperties

concrete functionality may be defined by transport protocol mappings or vendor-specific extensions. The NamespaceIndex of the QualifiedName in the KeyValuePair for properties defined in this document shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.4.3 Connection Properties

PubSubConfiguration . The properties are defined through the KeyValuePair array in the ConnectionProperties . The NamespaceIndex of the QualifiedName in the KeyValuePair shall be 0 for DTLS standard properties. The Name ... suites that are accepted if sent by a DTLS client in the handshake. The NamespaceIndex of the QualifiedName in the KeyValuePair for properties defined in this document shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.4 Connection properties

DataSetWriter . The properties are defined through the KeyValuePair array in the ConnectionProperties . The NamespaceIndex of the QualifiedName in the KeyValuePair shall be 0. Table 201 formally defines the ConnectionProperties used
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.8 Message header

PubSubConnection , WriterGroup or DataSetWriter through the KeyValuePair array in the WriterGroupProperties and DataSetWriterProperties . The NamespaceIndex of the QualifiedName in the KeyValuePair shall be 0. The Name of the QualifiedName
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

B.3.4 Connection properties

properties are defined through the KeyValuePair array in the ConnectionProperties WriterGroupProperties and DataSetWriterProperties . The NamespaceIndex of the QualifiedName in the KeyValuePair is 0 for AMQP standard properties. The Name
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

B.3.7 Message header

WriterGroup or DataSetWriter through the KeyValuePair array in the WriterGroupProperties and DataSetWriterProperties . The NamespaceIndex of the QualifiedName in the KeyValuePair is 0 for AMQP standard message properties. The Name ... LocalizedText Not supported and the related field is discarded. NodeId If the NamespaceIndex = 0 the value is encoded as an AMQP 'string' type using the format for a NodeId defined
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.7 CustomMetaDataProperties Property

qualified with the OPC UA Namespace . This allows the encoder to omit the NamespaceIndex when serializing the QualifiedName inside the KeyValuePair . Figure 10 shows the structure of the CustomMetaDataProperties
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.16.3.2 PubSubCommunicationModelConfigurationType definition

Connections . The PubSubConfiguration2DataType is defined in OPC 10000-14 . Namespaces contains namespace URIs for NamespaceIndex used in the PubSubConfiguration . Examples are NodeIds contained in PublishedDataSets . The NamespaceIndex in the PubSubConfiguration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.2 Handling of OPC UA namespaces

this document. Since NamespaceIndexes are dynamically assigned during the start of a Server , the NamespaceIndex , for example, for DI, may be different from 5 in a specific Server . Table
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.6 Loading / Saving ConnectionConfigurationSets

subscribed) that would include fields that are of NodeId DataType . NodeIds contain a NamespaceIndex . The NamespaceIndex is an index into a NamespaceArray that contains the URI that describes the owner ... Server . This document describes how these NodeIds are to be resolved to the correct NamespaceIndex on the target Server before the structure is transmitted as part of an EstablishConnections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.2 Namespaces

uses Namespaces , and in a defined scope, all identifiers ( NodeId , QualifiedName ) use a NamespaceIndex instead of a NamespaceUri . The scope has a NamespaceArray with URIs where the NamespaceIndex is defined ... those identifiers is defined by the related ServerAddressConfDataType structure containing a Namespace array. The NamespaceIndex of a node identifier is used as an index into the Namespace array
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.6 CommunicationFlowConfigurationConfDataType

IntervalRange[] The AvailableRanges KeyValuePair corresponds to the subcomponent defined in Table 99 . The NamespaceIndex of the QualifiedName in the KeyValuePair for properties defined in this document shall be the namespace
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.15 NodeIdentifier

defined in OPC 10000-5 Node 0:NodeId The NodeId of the Node . The NamespaceIndex of the NodeId relates to the Namespaces in the ServerAddressConfDataType (see F.1.11 ) of the related ... starting Node of the IdentifierBrowsePath shall be specified where this type is used. A NamespaceIndex in the RelativePath relates to the Namespaces in the ServerAddressConfDataType (see F.1.11 ) of the related
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.7.1 QualifiedName DataType

A.3.7.1 QualifiedName DataType QualifiedName - The integer NamespaceIndex used in OPC UA is replaced by a NamespaceUri in AutomationML . In AutomationML , the full URI is always used, and there is never
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.7.3 NodeId DataType

NodeId - NodeIds in running OPC UA Servers are represented as an ID and a NamespaceIndex . In order to make reference to Nodes in the offline AutomationML file, a more flexible
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.4 Additional Attribute values

value field. Double quotes are not included. If the DataType includes a NamespaceIndex ( QualifiedNames , NodeIds or ExpandedNodeIds ) then the notation used for BrowseNames is used. If the value
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.2.1 NodeIds

NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri ... Server . The NodeIds of those Nodes are Server -specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.1.1 Node definitions

symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.2.1 NodeIds

NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri ... Server . The NodeIds of those Nodes are Server -specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.1 Node definitions

symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.2.1 NodeIds

NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri ... Server . The NodeIds of those Nodes are Server -specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.1 Conventions for Node descriptions

symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see Table 73 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.2.1 NodeIds

NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri ... Server . The NodeIds of those Nodes are Server -specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.1.1 Node definitions

symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.2.1 NodeIds

NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri ... Server . The NodeIds of those Nodes are Server -specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.1 Node definitions

symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.2.1 NodeIds

NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri ... Server . The NodeIds of those Nodes are Server -specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.2 Namespaces

NamespaceUri which identifies a naming authority and a locally unique integer called a NamespaceIndex , which is an index into the Server's table of NamespaceUris . The NamespaceIndex is unique only ... Session between an OPC UA Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location