Search

189 result(s) for namespaceUri

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.2 URIs
  query subcomponents and/or fragments. Below are recommended URI formats for different use cases. 1) NamespaceUri assigned by the creator of a InformationModel : tag:<authority-domain-name>,<yyyy
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.12 DiagnosticInfo
  related information. Table 132 - DiagnosticInfo Name Type Description DiagnosticInfo structure Vendor-specific diagnostic information. namespaceUri Int32 The symbolicId is defined within the context of a namespace. This namespace is represented ... Client in the stringTable parameter of the ResponseHeader parameter defined in 7.33 . The namespaceUri parameter contains the index into the stringTable for this string. -1 indicates that no string
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in 6.2 HasProperty Variable NamespaceUri String PropertyType Mandatory HasProperty Variable NamespaceVersion String PropertyType Mandatory HasProperty Variable NamespacePublicationDate DateTime PropertyType Mandatory ... NamespaceIndex of the QualifiedName and the namespace URI as name of the QualifiedName . The NamespaceUri Property contains the namespace represented by an instance of the MetaDataType. The NamespaceVersion Property provides
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.37 AuditClientUpdateMethodResultEventType
  identifies the Object on which the Method was called. The ExpandedNodeId shall use a namespaceUri , the serverIndex shall be set to 0 and the serverIndex shall be ignored. MethodId identifies ... method that was called. The ExpandedNodeId shall use a namespaceUri , the serverIndex shall be set to 0 and the serverIndex shall be ignored. The ServerUri in the parent class
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  C.2.1 TypeDictionary
  that are referenced by StructuredTypes defined in the dictionary. Each import element specifies the NamespaceUri of the TypeDictionary being imported. The TypeDictionary element shall declare an XML namespace prefix
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.12 QualifiedName, NodeId and ExpandedNodeId String Encoding
  opaqueid> = "b=" BASE64 NodeIds with a NamespaceIndex of 0 or a NamespaceUri of http://opcfoundation.org/UA/ shall only use the <identifier> form
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.10 ExpandedNodeId
  ExpandedNodeId An ExpandedNodeId extends the NodeId structure by allowing the NamespaceUri to be explicitly specified instead of using the NamespaceIndex . The NamespaceUri is optional. If it is specified, then ... encoded by first encoding a NodeId as described in 5.2.2.9 and then encoding NamespaceUri as a String . An instance of an ExpandedNodeId may still use the NamespaceIndex instead
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.12 DiagnosticInfo
  actually present in the encoded form. As described in OPC 10000-4 , the SymbolicId , NamespaceUri , LocalizedText and Locale fields are indexes in a string table which is returned ... Info 0x20 InnerStatusCode 0x40 InnerDiagnosticInfo SymbolicId Int32 A symbolic name for the status code. NamespaceUri Int32 A namespace that qualifies the symbolic id. Locale Int32 The locale used
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.2.10 NodeId
  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> form ... application. The second abnormal state occurs when the decoder cannot convert a NamespaceUri to a NamespaceIndex . If this occurs the decoder shall set the NamespaceIndex to 0, the IdType
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.2.11 ExpandedNodeId
  Identifier to the JSON string. When the ServerIndex is 0, decoders shall replace a NamespaceUri with a NamespaceIndex when a mapping exists or if a mapping can be created ... mapping exists or one cannot be created the NamespaceUri is stored in the NamespaceUri field of the ExpandedNodeId
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.2.13 DiagnosticInfo
  default value is -1. It is not encoded if the value is -1. NamespaceUri Int32 A namespace that qualifies the symbolic id. The default value ... value is null. It is not encoded if the value is null. The SymbolicId , NamespaceUri , Locale and LocalizedText fields are encoded as JSON numbers which reference the StringTable contained
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.2.14 QualifiedName
  encoding error. This can occur when the encoder cannot map a NamespaceIndex to a NamespaceUri . In this case, the encoder shall encode the NamespaceIndex using the <namespace-index ... application. A second abnormal state occurs when the decoder cannot convert a NamespaceUri to a NamespaceIndex . If this occurs the decoder shall set the NamespaceIndex to 0 and the Name
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  A.3 Numeric Node Ids
  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
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  H.2 NodeId
  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
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  H.3 ExpandedNodeId
  this field. Namespace For ReversibleEncoding this field is a JSON string with the NamespaceUri if the NamespaceUri is specified. Otherwise, it is a JSON number with the NamespaceIndex. The field ... NamespaceIndex is 0. For NonReversibleEncoding this field is the JSON string containing the NamespaceUri or the NamespaceUri associated with the NamespaceIndex unless the NamespaceIndex
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  H.5 QualifiedName
  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
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.6.4.1 General
  units used in all industries, the EUInformation structure includes a separate field (the namespaceUri ) to identify the system on which the exposed unit is based. The default OPC UA mapping
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.6.4.4 Mapping of UN/CEFACT to EUInformation
  available here: https://reference.opcfoundation.org/files/UNECE_to_OPCUA.csv?u=http://opcfoundation.org/UA/ This mapping has been generated as follows: The namespaceUri shall be http:// www.opcfoundation.org/UA/units/un/cefact The Common Code (represented as an alphanumeric variable length
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.6.4.5 Mapping of IEC 62720 to EUInformation
  available here: https://reference.opcfoundation.org/files/IEC62720_to_OPCUA.csv?u=http://opcfoundation.org/UA/ This mapping has been generated as follows: The namespaceUri shall be http:// www.opcfoundation.org/UA/units/cdd/IEC62720 The Code is the data identifier of the IRDI
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  B.2 Numeric Node Ids
  addition, this document defines Nodes which are only used by GlobalDiscoveryServers . The NamespaceUri for any GDS specific NodeIds is http://opcfoundation.org/UA/GDS / The CSV released with this version
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.3 SubscribedDataSetMirrorType
  created in the Subscriber from the DataSetMetaData if they do not exist. The NamespaceUri of the created DataTypes shall match the namespace contained in the DataSetMetaData
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.2.2 AddRole Method
  Role to the RoleSet Object defined in 4.3 . The combination of the NamespaceUri and RoleName parameters are used to construct the BrowseName for the new Node . The BrowseName shall ... Roles are defined in OPC 10000-6 . Signature AddRole ( [in] String RoleName, [in] String NamespaceUri, [out] NodeId RoleNodeId ); Argument Description RoleName The name of the Role . NamespaceUri The NamespaceUri qualifies
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  A.1 Namespace and Identifiers for the Onboarding Information Model
  addition, this document defines Nodes which are only used by Registrars . The NamespaceUri for any Device Onboarding specific NodeIds is: http://opcfoundation.org/UA/Onboarding/ The CSV released with this version
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  A.1 Namespace and Identifiers for the Scheduler Information Model
  Name for the ExceptionSchedule InstanceDeclaration within the ScheduleType declaration is: ScheduleType_ExceptionSchedule. The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/Scheduler/ The CSV released with this version
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.3.2 PortableNodeId provided
  connecting to the Server , reading the NamespaceArray from the Server , and matching all NamespaceUri from the NamespaceArray to the URI's store in the PortableNodeId and storing the Index ... Connection to ensure it has not changed. Repeat for all Servers . When resolving NamespaceUri , if a null or empty NamespaceUri is encountered, the Server shall assume that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.3.3 PortableRelativePath provided
  connecting to the Server , reading the NamespaceArray from the Server , and matching all NamespaceUri from the NamespaceArray to the URI's store in the PortableRelativePaths . PortableRelativePathElements and storing the Index ... process for resolving BrowsePaths shall be repeated. Repeat for all Servers . When resolving NamespaceUri , if a null or empty NamespaceUri is encountered, the Server shall assume that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.6.6 Loading / Saving ConnectionConfigurationSets
  ExpandedNodeIds and QualifiedNames that must be modified, so the NamespaceIndexes and ServerIndexes reference the NamespaceUri and ServerUri tables in the UANodeSet." When generating a UANodeSet XML file, the NamespaceArray
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.2.2 Namespaces
  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 as an index into this ... NodeId and RelativePath  contained in the DataTypes to their portable versions using the NamespaceUri from the Namespace array when it loads the ConnectionConfigurationSet from the data structure
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.2.3 ATL_OpcAmlMetaModel library
  following AttributeTypes used to compose the specialized mapping of NodeId described in A.3.7 : NamespaceUri - An AttributeType with a data type of xs:anyURI to hold a NamespaceUri of a NodeId
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.3.7.1 QualifiedName DataType
  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 ... index. Wherever NamespaceUri is used, the AutomationML datatype is always xs:anyURI
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.3.7.5 PortableNodeId data type
  type PortableNodeId - The identifier field of PortableNodeId has the same definition as NodeId. The NamespaceUri information of the PortableNodeId is already present in the identifier and, therefore, redundant
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.4 NodeClass mapping
  Attribute name Included in SystemUnitClasses or Instances Notes NodeId X If the NamespaceUri portion of the NodeId or the entire NodeId is not present, then the AML object contains ... Name portion of the BrowseName is inferred by the AML object Name. If the NamespaceUri sub-attribute of the BrowseName AML attribute is not present and the AML Object
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.9 Instance mapping
  InstanceHierarchy, care must be given to setting the URIs properly to reflect the correct NamespaceUri for both the BrowseName and the Node . In the InstanceHierarchy, an empty or missing NamespaceUri ... BrowseName ) or UaNodeNamespaceUri shall imply the default NamespaceUri of the OPC UA Server (i.e. Namespace index 1). In all other cases, the URI attributes shall contain valid URIs that reflect
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.10 Limitations on AML to OPC UA conversion
  NamespaceIndexes : OPC UA FX AML does not use NamespaceIndexes . It always uses the NamespaceUri as a string; Bit order in OptionSets and Bitmasks : In OPC UA FX AML, OptionSet
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A . For InstanceDeclarations
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  A.1 NodeSet and Supplementary Files for DI Information Model
  Information Model is identified by the following URI: http://opcfoundation.org/UA/DI/ Documentation for the NamespaceUri can be found here . The NodeSet associated with this version of specification can be found ... latest version of the specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/DI/&i=2 The NamespaceUri for the package_metadata.json with structures and enumerations used for Software Package files is: http://opcfoundation.org/UA/DI/PackageMetadata/
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 16.2 . For InstanceDeclarations of NodeClass
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 8.2 . For InstanceDeclarations of NodeClass
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. For InstanceDeclarations
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 10.2 . For InstanceDeclarations of NodeClass
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  A.1 Namespace and identifiers for Relative Spatial Location Information Model
  Name for the Identifier InstanceDeclaration within the SpatialObjectType declaration is: SpatialObjectType_Identifier . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/RSL/ The CSV released with this version
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 8.2 . For InstanceDeclarations of NodeClass
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  3.4.1.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  3.4.1.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 8.2 . For InstanceDeclarations of NodeClass
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  A.1 Namespace and identifiers for IEC 61131-3 Information Model
  Name for the ParameterSet InstanceDeclaration within the CtrlConfigurationType declaration is: CtrlConfigurationType_ParameterSet . The NamespaceUri for all NodeIds defined here is http://PLCopen.org/OpcUa/IEC61131-3/ A computer processible version of the complete
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  3.4.2.1 NodeIds
  Node have a unique name in this specification, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note: This specification does not only define concrete Nodes , but also requires
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  A.1 Namespace and identifiers for AutoID Information Model
  Name for the DeviceLocation InstanceDeclaration within the AutoIdDeviceType declaration is: AutoIdDeviceType_DeviceLocation . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/AutoID/ The CSV released with this version
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.2 Namespaces
  from different sources. Namespaces in OPC UA have a globally unique string called a NamespaceUri and a locally unique integer called a NamespaceIndex . The NamespaceIndex is only unique within
• OPC-30020 – MDIS OPC UA Companion Specification
  10.4 UANodeSet Development
  This is to enable smaller devices like controllers to be able to store Namespaces . NamespaceUri usually reference back to the company that is the owner of the Namespace . The NodeIds
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.2 Namespaces
  from different sources. Namespaces in OPC UA have a globally unique string called a NamespaceUri and a locally unique integer called a NamespaceIndex . The NamespaceIndex is only unique within
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  A.1 Namespace and identifiers for PackML Information Model
  Server that wishes to expose the InformationModel (types) defined in this specification. This The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PackML/ A computer processible version
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 14.2 . For InstanceDeclarations of NodeClass
• OPC-30060 – OPC UA for Tobacco Machine Communication
  A.1 Namespace and identifiers for TMC Information Model
  within the <type> declaration is: <type>_<property> . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/TMC/ v2/ The CSV released with this
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.2.1 NodeIds
  Node have a unique name in this specification, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this specification is defined in Annex A . The NamespaceIndex ... this NamespaceUri is Server -specific and depends on the position of the NamespaceUri in the server namespace table. Note that this specification not only defines concrete Nodes , but also requires
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.2.2 BrowseNames
  Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this specification is defined in Annex A . For InstanceDeclarations
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.4.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.4.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 14.2 . For InstanceDeclarations of NodeClass
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  A.1 Namespace and identifiers for FDT Information Model
  SymbolName for the DisplayFormat InstanceDeclaration within the FdtParameter declaration is: FdtParameter_DisplayFormat . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/FDT/ 1.01/ The CSV released with this version
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  A.1 Namespace and identifiers for POWERLINK Information Model
  InstanceDeclaration within the DIA_ERRStatistics_Type declaration is DIA_ERRStatistics_Type_HistoryEntryWrite_U32 . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/POWERLINK/ The CSV released with this version
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  14.3 Mapping of ISDU Errors in DiagnosticInfo
  Mapping of ISDU Errors in DiagnosticInfo DiagnosticInfo structure element ISDU Error related description example namespaceUri IO-Link ErrorType Namespace " http://opcfoundation.org/UA/IOLink /" symbolicId Error Code and Additional Code ... Subindex not available" additionalInfo Vendor-specific diagnostic information "" The field namespaceUri contains the IO-Link ErrorType Namespace: " http://opcfoundation.org/UA/IOLink/ ". The field symbolicId contains
• OPC-30140 – OPC UA for PROFINET
  A.1 Namespace and identifiers for OPC UA for PROFINET Information Model
  type. An underscore character is used to separate each BrowseName in the path. The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PROFINET/ The CSV released with this version
• OPC-30141 – OPC UA for PROFIenergy
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30141 – OPC UA for PROFIenergy
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. For InstanceDeclarations
• OPC-30141 – OPC UA for PROFIenergy
  A.1 Namespace and identifiers for OPC UA for PROFIenergy Information Model
  type. An underscore character is used to separate each BrowseName in the path. The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PNEM/ The CSV released with this version
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 13.2 . For InstanceDeclarations of NodeClass
• OPC-30142 – OPC UA for PROFINET Remote IO
  A.1 Namespace and identifiers for OPC UA for PROFINET Remote IO Information Model
  within the <type> declaration is: <type>_<property> . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PNRIO/ The CSV released with this version
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 11.2 . For InstanceDeclarations of NodeClass
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  A.1 Namespace and identifiers for commercial kitchen devices Information Model
  Name for the DeviceLocationName InstanceDeclaration within the CommercialKitchenDeviceType declaration is: CommercialKitchenDeviceType _ DeviceLocationName. The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/CommercialKitchenEquipment/ The CSV released with this version
• OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 10.2 . For InstanceDeclarations of NodeClass
• OPC-30250 – OPC Unified Architecture for DEXPI
  A.1 Namespace and identifiers for DEXPI Information Model
  Name for the DesignHeatFlowRate InstanceDeclaration within the PlateAndShellHeatExchangerType declaration is: PlateAndShellHeatExchangerType_DesignHeatFlowRate . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/DEXPI/ The CSV released with this version
• OPC-30260 – OPC UA for OPEN-SCS - Serialization Object Model: OPEN-SCS
  A.1 Namespace and identifiers for OPENSCS-SER Information Model
  PropertyValue> InstanceDeclaration within the <type> declaration is: OPENSCSSIDClassPropertyDataType_PropertyValue . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/OPENSCS-SER/ Note that NamespaceURIs are NOT live URLs
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  A.1 Namespace and identifiers for I4AAS Information Model
  Name for the ModelingKind InstanceDeclaration within the AASSubmodelType declaration is: AASSubmodelType _ModelingKind . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/I4AAS/ The CSV released with this version
• OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases
  4.1 Introduction to Cloud Library
  stored NameSpace in the Cloud Library, a globally unique identifier such as the NamespaceUri (as defined in OPC 10000-100) can be used
• OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases
  4.2.3.2 Namespaces
  different sources. Each namespace in OPC UA has a globally unique string called a NamespaceUri which identifies a naming authority, and a locally unique integer called a NamespaceIndex , which ... NamespaceIndex  can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed. The Services defined
• OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition
  4.2.1 Method Find
  Cloud Library. Note: A recommended approach to generate these identifiers is to hash the NamespaceUri and the PublicationDate of the information model included in the nodeset file as these
• OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition
  4.2.2 Method Namespaces
  models found in the UA Cloud Library as an array of strings, where the NameSpaceUri and the identifier are comma separated. Response Body Schema [ "string
• OPC-30400-2 – OPC UA for Cloud Library - Part 2: API Definition
  4.2.5 Method Upload
  matching NameSpace from another organization. The Namespace can be uniquely identified by its NamespaceUri and its PublicationDate and this is how the information model identifier can be generated. The reference
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor specific and depends on the position of the NamespaceUri in the server Namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 10.2 . For InstanceDeclarations of NodeClass
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  4.2.3.2 Namespaces
  different sources. Each Namespace in OPC UA has a globally unique string called a NamespaceUri which identifies a naming authority, and a locally unique integer called a NamespaceIndex which ... NamespaceIndex  can change between Sessions and still identify the same item even though the NamespaceUri 's location in the table has changed. The Services defined
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A . The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A . For InstanceDeclarations
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 11.2 . For InstanceDeclarations of NodeClass
• OPC-40077 – OPC UA interfaces for plastics and rubber machinery - Data exchange between injection moulding machines and MES
  A.1 Namespace and identifiers for OPC 40077 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/IMM2MES/ The CSV released with this version
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  A.1 Namespace and identifiers for OPC 40082-1 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/TCD/ The CSV released with this version
• OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices
  A.1 Namespace and identifiers for OPC 40082-2 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/HotRunner/ The CSV released with this version
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  3.2.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  3.2.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. If the BrowseName
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  A.1 Namespace and identifiers for OPC 40083 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/GeneralTypes/ The CSV released with this version
• OPC-40084-1 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 1: General Type Definitions
  A.1 Namespace and identifiers for OPC 40084-1 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/GeneralTypes/ The CSV released with this version
• OPC-40084-2 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 2: Extrusion Line
  A.1 Namespace and identifiers for OPC 40084-2 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/ExtrusionLine/ The CSV released with this version
• OPC-40084-3 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 3: Extruder
  A.1 Namespace and identifiers for OPC 40084-3 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Extruder/ The CSV released with this version
• OPC-40084-4 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 4: Haul-off
  A.1 Namespace and identifiers for OPC 40084-4 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/HaulOff/ The CSV released with this version
• OPC-40084-5 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 5: Melt pump
  A.1 Namespace and identifiers for OPC 40084-5 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/MeltPump/ The CSV released with this version
• OPC-40084-6 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 6: Filter
  A.1 Namespace and identifiers for OPC 40084-6 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Filter/ The CSV released with this version
• OPC-40084-7 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 7: Die
  A.1 Namespace and identifiers for OPC 40084-7 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Die/ The CSV released with this version
• OPC-40084-8 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 8: Pelletizer
  A.1 Namespace and identifiers for OPC 40084-8 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Pelletizer/ The CSV released with this version
• OPC-40084-9 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 9: Cutter
  A.1 Namespace and identifiers for OPC 40084-9 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Cutter/ The CSV released with this version
• OPC-40084-10 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 10: Calibrator
  A.1 Namespace and identifiers for OPC 40084-10 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Calibrator/ The CSV released with this version
• OPC-40084-11 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 11: Corrugator
  A.1 Namespace and identifiers for OPC 40084-11 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Corrugator/ The CSV released with this version
• OPC-40084-12 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 12: Calender
  A.1 Namespace and identifiers for OPC 40084-12 Information Model
  Name for the ControllerName InstanceDeclaration within the MachineInformationType declaration is: MachineInformationType_ControllerName . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/Calender/ The CSV released with this version
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  A.1 Namespace and identifiers for Machine Vision Information Model
  property> InstanceDeclaration within the <type> declaration is: AutoIdDeviceType_DeviceLocation . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/MachineVision/ The CSV released with this version
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 14.2 . For InstanceDeclarations of NodeClass
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 13.2 . For InstanceDeclarations of NodeClass
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. If the BrowseName
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  A.1 Namespace and identifiers for OPC UA for Pumps and Vacuum Pumps Information Model
  Name for the ArticleNumber InstanceDeclaration within the PumpIdentificationType declaration is: PumpIdentificationType_ArticleNumber . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/Pumps/ The CSV released with this version
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. If the BrowseName
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  A.1 Namespace and identifiers for OPC UA for Compressed Air Systems Information Model
  Name for the Hostname InstanceDeclaration within the CommunicationSettingsType declaration is: CommunicationSettingsType_Hostname. The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/CAS/ The CSV released with this version
• OPC-40301 – OPC UA for Flat Glass Processing
  3.5.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40301 – OPC UA for Flat Glass Processing
  3.5.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. For InstanceDeclarations
• OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Table 164 . For InstanceDeclarations
• OPC-40444 – OPC UA for Textile Testing Devices
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40444 – OPC UA for Textile Testing Devices
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass
• OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass
• OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. If the BrowseName
• OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model
  A.1 Namespace and identifiers for OPC UA Information Model for CNC Systems
  Version Property . The Name for the Version InstanceDeclaration is: CncInterfaceType_Version . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/CNC/ The CSV released with this version
• OPC-40503-1 – OPC UA for Metal Forming - Part 1: General
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40503-1 – OPC UA for Metal Forming - Part 1: General
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass
• OPC-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 11.2 . For InstanceDeclarations of NodeClass
• OPC-40505 – OPC UA for Wireless Machine Tool Peripherals
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40505 – OPC UA for Wireless Machine Tool Peripherals
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 10.2 . For InstanceDeclarations of NodeClass
• OPC-40530 – OPC UA for Laser Systems
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40530 – OPC UA for Laser Systems
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 9.2 . For InstanceDeclarations of NodeClass
• OPC-40540 – OPC UA for Additive Manufacturing
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40540 – OPC UA for Additive Manufacturing
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 13.2 . For InstanceDeclarations of NodeClass
• OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 9.2 . For InstanceDeclarations of NodeClass
• OPC-40560 – OPC UA for Mining - General
  3.2.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40560 – OPC UA for Mining - General
  3.2.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Table 32 . For InstanceDeclarations
• OPC-40561-1 – OPC UA for Mining - Part 1: Extraction General
  A.1 Namespace and identifiers for OPC 40561-1 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/Extraction/General/ The CSV released with this version
• OPC-40561-2 – OPC UA for Mining - Extraction - Part 2: Shearer Loader
  A.1 Namespace and identifiers for OPC 40561-2 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here: http://opcfoundation.org/UA/Mining/Extraction/ShearerLoader/ The CSV released with this version
• OPC-40562-1 – OPC UA for Mining - Loading - Part 1: General
  A.1 Namespace and identifiers for OPC 40562-1 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/Loading/General/ The CSV released with this version
• OPC-40562-2 – OPC UA for Mining - Loading - Part 2: Hydraulic Excavator
  A.1 Namespace and identifiers for OPC 40562-2 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/Loading/HydraulicExcavator/ The CSV released with this version
• OPC-40563-1 – OPC UA for Mining - Transport Dumping - Part 1: General
  A.1 Namespace and identifiers for OPC 40563-1 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/TransportDumping/General/ The CSV released with this version
• OPC-40563-2 – OPC UA for Mining - Transport Dumping - Part 2: Armoured Face Conveyor
  A.1 Namespace and identifiers for OPC 40563-2 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/TransportDumping/ArmouredFaceConveyor/ The CSV released with this version
• OPC-40563-3 – OPC UA for Mining - Transport Dumping - Part 3: Rear Dump Truck
  A.1 Namespace and identifiers for OPC 40563-3 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/TransportDumping/RearDumpTruck/ The CSV released with this version
• OPC-40564-1 – OPC UA for Mining - Mineral Processing - Part 1: General
  Annex A OPC 40563-1 Namespace and mappings (Normative)
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/MineralProcessing/General/ The CSV released with this version
• OPC-40564-2 – OPC UA for Mining - Mineral Processing - Part 2: Rock Crusher
  A.1 Namespace and identifiers for OPC 40564-2 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here: http://opcfoundation.org/UA/Mining/MineralProcessing/RockCrusher/ The CSV released with this version
• OPC-40565-1 – OPC UA for Mining - Development Support - Part 1: General
  A.1 Namespace and identifiers for OPC 40565-1 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/DevelopmentSupport/General/ The CSV released with this version
• OPC-40565-2 – OPC UA for Mining - Development Support - Part 2: Roof Support System
  A.1 Namespace and identifiers for OPC 40565-2 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/DevelopmentSupport/RoofSupportSystem/ The CSV released with this version
• OPC-40565-3 – OPC UA for Mining - Development - Part 3: Dozer
  10.1 Namespace and identifiers for OPC 40565-3 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/DevelopmentSupport/Dozer/ The CSV released with this version
• OPC-40566-1 – OPC UA for Mining - Monitoring Supervision Services - Part 1: General
  A.1 Namespace and identifiers for OPC 40566-1 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/MonitoringSupervisionServices/General/ The CSV released with this version
• OPC-40567-1 – OPC UA for Mining - PELO Services - Part 1: General
  A.1 Namespace and identifiers for OPC 40567-1 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/PELOServices/General/ The CSV released with this version
• OPC-40567-2 – OPC UA for Mining - PELO Services - Part 2: Face Alignment System
  A.1 Namespace and identifiers for OPC 40567-2 Information Model
  Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification . The NamespaceUri for all NodeIds defined here is: http://opcfoundation.org/UA/Mining/PELOServices/FaceAlignmentSystem/ The CSV released with this version
• OPC-40570 – OPC UA for Wire Harness Manufacturing
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40570 – OPC UA for Wire Harness Manufacturing
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 14.2 . For InstanceDeclarations of NodeClass
• OPC-40570 – OPC UA for Wire Harness Manufacturing
  4.2.3.2 Namespaces
  different sources. Each namespace in OPC UA has a globally unique string called a NamespaceUri which identifies a naming authority and a locally unique integer called a NamespaceIndex , which ... NamespaceIndex  can change between Sessions and still identify the same item even though the NamespaceUri 's location in the table has changed. The Services defined
• OPC-40600 – OPC UA for Weihenstephan Standards
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40600 – OPC UA for Weihenstephan Standards
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in Annex A. If the BrowseName
• OPC-40600 – OPC UA for Weihenstephan Standards
  A.1 Namespace and identifiers for OPC UA for Weihenstephan Standards Information Model
  Name for the WSVersion InstanceDeclaration within the WSMachineType declaration is: WSMachineTyp_WSVersion . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/Weihenstephan/ The CSV released with this version
• OPC-40700 – OPC UA for Surface Technology - General Types
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40700 – OPC UA for Surface Technology - General Types
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 9.2 . For InstanceDeclarations of NodeClass
• OPC-40701 – OPC UA for Surface Technology - Cleaning and Pretreatment
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40701 – OPC UA for Surface Technology - Cleaning and Pretreatment
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 9.2 . For InstanceDeclarations of NodeClass
• OPC-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems
  3.3.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems
  3.3.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 9.2 . For InstanceDeclarations of NodeClass
• OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 9.2 . For InstanceDeclarations of NodeClass
• OPC-40719 – OPC UA for Plasma Surface Technology
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40719 – OPC UA for Plasma Surface Technology
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 9.2 . For InstanceDeclarations of NodeClass
• OPC-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)
  3.4.2.1 NodeIds
  Node have a unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex ... this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table. Note that this document not only defines concrete Nodes , but also requires
• OPC-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)
  3.4.2.2 BrowseNames
  Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass