Search

200 result(s) for BrowseNames

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.2 Interface Model
  Node's base type. Clients can also use the TranslateBrowsePathsToNodeId Service with BrowseNames of Interface members to get the NodeId of these members directly. In the example in Figure
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.4 BrowseName
  localised human-readable name when browsing the AddressSpace to create paths out of BrowseNames . The TranslateBrowsePathsToNodeIds Service defined in OPC 10000-4 can be used to follow a path constructed ... BrowseNames . A BrowseName should never be used to display the name of a Node . The DisplayName should be used instead for this purpose. Unlike NodeIds , the BrowseName cannot be used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  then all Nodes referenced with forward hierarchical References direction shall have unique BrowseNames in the context of this Object . If the Object is created based on an InstanceDeclaration then
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  described in Clause 7 . All Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of an ObjectType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.4 DataVariable
  InstanceDeclaration (see 4.6 ) all Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of this DataVariable
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  described in Clause 7 . All Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of the VariableType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  InstanceDeclaration (see 4.6 ) all Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of this Method . The Variable referenced by a HasArgumentDescription ReferenceType shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.5 BrowsePath
  BrowsePath A BrowsePath is a sequence of BrowseNames used to describe a path between Nodes related w ith a Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.3 ExposesItsArray
  Therefore it references two instances of the same type as the InstanceDeclaration ArrayExpose. The BrowseNames of those instances are not defined by the ModellingRule . In general, it is not possible
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.4 OptionalPlaceholder
  expects from instances of the TypeDefinition to add instances with specific References without defining BrowseNames for the instances. For example, a Device might have a Folder for DeviceParameters
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.1 Description
  from which the RelativePath is based. The RelativePath contains a sequence of ReferenceTypes and BrowseNames . One purpose of this Service is to allow programming against type definitions. Since BrowseNames shall
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.1 Overview
  using a Node in the type system and relative path constructed from ReferenceTypes and BrowseNames . SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition ... relative path constructed from BrowseNames
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.5 SimpleAttributeOperand
  path to a Node . This parameter specifies a relative path using a list of BrowseNames instead of the RelativePath structure used in the AttributeOperand . The list of BrowseNames is equivalent
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.30 RelativePath
  Table 169 - RelativePath Name Type Description RelativePath structure Defines a sequence of References and BrowseNames to follow. elements [] RelativePath Element A sequence of References and BrowseNames to follow. This structure
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  A.2 BNF of RelativePath
  reserved character is escaped by inserting the '&' in front of it. Examples of BrowseNames with escaped characters are: Received browse path name Resolves to "&/Name_1
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  4.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this standard is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 4.1 and defined in OPC 10000-6 . WriteMask Optionally the WriteMask Attribute
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.4 Historical Data Configuration Object
  shall have a BrowseName of 'HA Configuration'. Additional configurations can be defined with different BrowseNames . It is highly recommended that display names for historical configuration historical configuration are chosen that
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  10.2 Handling of OPC UA Namespaces
  standard namespaces. Table 162 provides a list of namespaces and their index used for BrowseNames in this document. The default namespace of this document is not listed since all BrowseNames
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.2.2 DataTypeSchemaHeader
  affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained in the messages. If the Subscriber receives Structure DataTypes where the target Variables DataTypes
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.9.4 DataSetMetaData
  affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained in the messages. If the Subscriber receives Structure DataTypes where the target Variables DataTypes
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.2 Safety ObjectType definitions
  ReferenceType HasProperty (and shall not be derived from ReferenceType HasProperty ) for Property References . As BrowseNames (i.e. name and Namespace ) are used to find Methods , the names of Objects and Properties
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  C.1 Overview
  Pull all AliasNameCategory instances, merge any that have identical Name part of the BrowseNames . The GDS will provide the ExpandedNodeId of all of the referenced NodeIds and the ServerUri
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  10.2 Handling of OPC UA Namespaces
  standard namespaces. Table 37 provides a list of namespaces and their index used for BrowseNames in this document. The default namespace of this document is not listed since all BrowseNames
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  4.1 Type and Naming Conventions
  types used by the related managed objects of IEEE and IETF. BrowseNames of Variables and parameter sets (UA interface) are preferably derived from standardized IETF / IEEE YANG models
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  10.2 Handling of OPC UA Namespaces
  used in a Scheduler Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/Scheduler/ Namespace for NodeIds and BrowseNames defined in this document. The namespace index is Server specific. Vendor specific types A Server
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.2 Limitations
  Limitations Since the BrowseNames of the Variables in the SerializationScope are used as field names for the SerializationFieldDataType fields in the SerializationValue DataType , limitations for BrowseNames arise: The characters used ... BrowseNames must be permissible in field names of Structure DataTypes . To achieve this, it is recommended to limit the characters used in BrowseNames to letters (lower- and uppercase), digits
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.7 CustomMetaDataProperties Property
  Variable . Sub- Variables are represented with elements containing KeyValuePairs with keys equal to the BrowseNames of the Variables (see "Variable1", "Variable2" and "Variable3" elements
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.4.3 SerializationFieldDataType of Variables with Children
  mapped child. Servers shall make sure that field names are unique (e.g., two BrowseNames can have the same text field but different namespaces). The SerializationFieldDataType of each of those fields
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.2 AutomationComponentType definition
  contains Variables that report diagnostic statistics and counters (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). EstablishCallCount diagnostics counter Variable provides a count of the number of EstablishConnections calls received. EstablishCallFailedCount
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.2 FunctionalEntityType definition
  Variables representing the configuration items of the FunctionalEntity (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). The optional Tuning FunctionalGroup contains Variables that can be used to optimise the behaviour ... FunctionalEntity (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). The optional Capabilities is a FunctionalEntityCapabilitiesType Folder that describes the functionality provided by a FunctionalEntity (see 6.4.7 ). The optional PublisherCapabilities provide
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.4 InputsFolderType
  Variable via subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes ). The BrowseNames of Variables in this Folder shall be unique within this Folder ; the use of nested
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.5 OutputsFolderType
  Variable via subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes ). The BrowseNames of Variables in this Folder shall be unique within this Folder ; the use of nested
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.2 ConfigurationDataFolderType definition
  Variables via subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes ). The BrowseNames of Variables in this Folder shall be unique within this Folder . All Variables in this folder ... into a tree of FunctionalGroups . This will also assist with the uniqueness requirement for BrowseNames . The optional Methods SetStoredVariables , ClearStoredVariables , and ListStoredVariables allow for the maintenance of storage for configuration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.2 ConnectionManagerType definition
  Diagnostics FunctionalGroup contains Variables and Methods for diagnostics (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). For UAFX, this includes the defined diagnostic Variable in Table 78 - ConnectionManagerType additional subcomponents Table
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.15.2 AssetVerificationType definition
  expected that this list contains IdentifierBrowsePath with a PortableRelativePath as Keys using BrowseNames as defined in Table 31 . ExpectedAdditionalVerificationVariables hold the variables to be verified for compatibility and/or identity
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.39 PortableRelativePath
  PortableRelativePath This structure contains a PortableRelativePath , which defines a sequence of References and BrowseNames to follow for storing a relative path outside the context of where the target ... Structure defined in OPC 10000-5 Elements 4:PortableRelativePathElement[] A sequence of References and BrowseNames to follow. This array defines a sequence of elements. Each element in the sequence
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  14.2 Handling of OPC UA namespaces
  UAFX Server NamespaceURI Description Use http://opcfoundation .org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have the namespace index 0. Mandatory Local Server ... between a ConnectionManager and an AutomationComponent . Mandatory http://opcfoundation.org/UA/FX/AC / Namespace for NodeIds and BrowseNames defined in the AutomationComponent -related part of this document. The namespace index is Server -specific
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.4 Additional Attribute values
  DataType includes a NamespaceIndex ( QualifiedNames , NodeIds or ExpandedNodeIds ) then the notation used for BrowseNames is used. If the value is an Enumeration the name of the enumeration value is entered
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.4.1 Model
  BrowseName of a FunctionalGroup should indicate its purpose. A list of well-known BrowseNames is in 4.4.2 . Figure 3 shows the FunctionalGroupType components. It is formally defined in Table ... Variable 1:UIElement 0:BaseDataType 1:UIElementType O Conformance Units DI Information Model All BrowseNames for Nodes referenced by a FunctionalGroup with an Organizes Reference shall be unique. The Organizes
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.10 DeviceFeatures entry point
  Devices referenced by the DeviceSet . Companion specifications can standardize such instances and their BrowseNames . Figure 13 shows the AddressSpace organisation with this standard entry point. Figure 13 - Standard entry point
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  12.2 Handling of OPC UA namespaces
  Devices Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is Server specific. Mandatory Vendor specific types
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  16.2 Handling of OPC UA Namespaces
  Asset Management Basics Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/AMB/
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  8.2 Handling of OPC UA Namespaces
  Data Types Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/XML/ Namespace for NodeIds and BrowseNames defined in this document. The namespace index is Server specific. Mandatory Vendor specific types
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  9.2 Handling of OPC UA Namespaces
  Industrial Automation Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/IA/
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  10.2 Handling of OPC UA Namespaces
  Relative Spatial Location Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Optional http://opcfoundation.org/UA/RSL/
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  12.2 Handling of OPC UA Namespaces
  Global Positioning Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server URI Namespace ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/RSL/ Namespace for NodeIds and BrowseNames defined in OPC 10000-210 . The namespace index is Server specific. http://opcfoundation.org/UA/GPOS/ Namespace
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  8.2 Handling of OPC UA Namespaces
  Control Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/ISA95JobControl/ Namespace for NodeIds and BrowseNames defined in this document. The namespace index is Server specific. Mandatory Vendor specific types
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  3.4.1.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  3.4.2.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.1.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  8.2 Handling of OPC UA Namespaces
  Connectivity Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server URI Namespace ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/WoT-Con/ Namespace for NodeIds and BrowseNames defined in this document. The namespace index is Server specific. Vendor specific types A Server
• OPC-10101 – OPC UA for WoT Binding
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-10101 – OPC UA for WoT Binding
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  12.5 Handling of OPC UA Namespaces
  Controller Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is server specific. Mandatory http://PLCopen.org/OpcUa/IEC61131-3/
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 and defined in Annex A . WriteMask Optionally the WriteMask Attribute
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  10.3 Handling of OPC UA namespaces
  AutoID Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is server specific. Mandatory http://opcfoundation.org/UA/AutoID/
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.1 Concepts
  This means Client applications can be designed to search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.2 Namespaces
  QualifiedNames are non-localised names qualified with a Namespace . They are used for the BrowseNames of Nodes and allow the same names to be used by different InformationModels without conflict ... with the same BrowseName s. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30020 – MDIS OPC UA Companion Specification
  15.2 Handling of OPC UA Namespaces
  MDIS Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/MDIS Namespace for NodeIds and BrowseNames defined in This specification. The namespace index is Server specific. Mandatory Vendor specific types
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  3.5.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  3.5.3.1 General
  NodeClass Shall reflect the NodeClass of the Node NodeId The NodeId is described by BrowseNames as defined in 3.5.2.1 and defined in Annex A . WriteMask Optionally the WriteMask Attribute
• OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML
  3.3.3.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML
  3.3.4.1 General
  NodeClass Shall reflect the NodeClass of the Node NodeId The NodeId is described by BrowseNames as defined in 3.3.3.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML
  9.1 Handling of OPC UA namespaces
  namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/AML/ Namespace for NodeIds and BrowseNames defined in AutomationML. The namespace index is server specific. Mandatory http://opcfoundation.org/UA/AML/AMLLibs/ Namespace ... NodeIds and BrowseNames defined in AutomationML libraries. The namespace index is server specific. Optional
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a Type the BrowseNames uniquely identify the child. This means Client applications can be designed ... search for children based on the BrowseNames from the Type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses Types that multiple devices
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace . They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... TypeDefinitions . Instances of a TypeDefinition are expected to have children with the same BrowseNames . TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  8.2 Handling of OPC UA namespaces
  PackML Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/PackML/ Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is server specific. Mandatory Vendor specific types
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30060 – OPC UA for Tobacco Machine Communication
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30060 – OPC UA for Tobacco Machine Communication
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30060 – OPC UA for Tobacco Machine Communication
  14.2 Handling of OPC UA Namespaces
  Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server URI Namespace ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/TMC/v2/
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual configuration of systems if a Client uses types that multiple Servers
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  6.1 Overview
  Process Automation Devices. This PA-DIM OPC UA Companion Specification defines the OPC UA BrowseNames and corresponding IEC 61987 Semantic CDD Dictionary IDs. For each Node with a dictionary reference
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  12.2 Handling of OPC UA Namespaces
  Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server URI Namespace ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is server specific. Mandatory http://opcfoundation.org/UA/Dictionary/IRDI
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.4.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.5.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.4.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  14.2 Handling of OPC UA Namespaces
  Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server URI Namespace ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/FDT/1.01/
• OPC-30100 – OPC UA for SERCOS Devices
  4.3.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30100 – OPC UA for SERCOS Devices
  7.3 Handling of OPC UA namespaces
  Sercos Server Namespace Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory http://sercos.org/UA/ ... Namespace for NodeIds and BrowseNames defined in Sercos. The namespace index is server specific. Mandatory Vendor specific types and instances A server may provide vendor specific types or vendor specific
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 and defined in Annex A . WriteMask Optionally the WriteMask Attribute
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  9.3 Handling of OPC UA namespaces
  POWERLINK OPC UA Server Namespace Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace index 1 in the server. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100. The namespace index is server specific. Mandatory http://opcfoundation.org/UA/POWERLINK/
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  15.6 Handling of OPC UA namespaces
  Link Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is vendor-specific. Mandatory http://opcfoundation.org/UA/IOLink/
• OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)
  8.3 Handling of the OPC UA Namespace
  CSPPlusForMachine Server NameSpace Description Optional/ Mandatory http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. M Local Server ... namespace shall have namespace index 1. M http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in [OPC 10000-100]. The namespace index is server specific. M http://opcfoundation.org/UA/CSPPlusForMachine/
• OPC-30140 – OPC UA for PROFINET
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30140 – OPC UA for PROFINET
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30140 – OPC UA for PROFINET
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30140 – OPC UA for PROFINET
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30140 – OPC UA for PROFINET
  7.5 Handling of OPC UA Namespaces
  PROFINET OPC UA Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/PROFINET/ Namespace for NodeIds and BrowseNames of the base information model defined in this specification. The namespace index is Server specific
• OPC-30141 – OPC UA for PROFIenergy
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30141 – OPC UA for PROFIenergy
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30141 – OPC UA for PROFIenergy
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30141 – OPC UA for PROFIenergy
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different Information Model ... without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30141 – OPC UA for PROFIenergy
  13.2 Handling of OPC UA Namespaces
  PROFIenergy Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in [OPC 10000-100] . The namespace index is Server specific. Optional http://opcfoundation.org/UA/PNEM/
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30142 – OPC UA for PROFINET Remote IO
  4.3.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30142 – OPC UA for PROFINET Remote IO
  4.3.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30142 – OPC UA for PROFINET Remote IO
  7.1.2 RioChannelGroupConfigType
  Object as are needed to represent the substitute values of all RIOforFA Channels . The BrowseNames of the RioBitFieldVariableType Variable shall be extended with a suffix ensuring uniqueness and indicating
• OPC-30142 – OPC UA for PROFINET Remote IO
  7.1.4 RioFaAnalogChannelGroupType
  Group Object as are needed to represent the qualifiers of all RIO Channels . The BrowseNames of the RioBitFieldVariableType Variables shall be extended with a suffix ensuring uniqueness and indicating
• OPC-30142 – OPC UA for PROFINET Remote IO
  7.1.6 RioFaDigitalChannelGroupType
  Group Object as are needed to represent the qualifiers of all RIO Channels . The BrowseNames of the RioBitFieldVariableType Variables shall be extended with a suffix ensuring uniqueness and indicating
• OPC-30142 – OPC UA for PROFINET Remote IO
  13.2 Handling of OPC UA Namespaces
  PROFINET Remote IO Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/PNRIO/
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.5.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  7.3 EncoderProbesType
  many EncoderProbeType Objects as are needed to represent all probes provided. The BrowseNames shall be provided as defined by the template string <Probex>, where x is the probe
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  12.2 Handling of OPC UA Namespaces
  PROFINET Encoder Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server URI Namespace ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. http://opcfoundation.org/UA/PNENC/ Namespace
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  6.7.1 BMPs with assigned text array
  Range Property . The elements of the assigned text array shall be used as BrowseNames of the 0:BaseDataVariableType Variables representing the array elements. There shall be as many Variables
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  7.2 GsdGenIoDataType
  Output") element in the GSDML (see Figure 10 also). To ensure unique BrowseNames , the Server shall substitute the 'x' in the placeholder template string with the item number ... Input" ("Output") element in the GSDML (see also). To ensure unique BrowseNames , the Server shall substitute the 'x' in the placeholder template strings with the content
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  12.2 Handling of OPC UA Namespaces
  PROFINET GSD Generic Model Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. http://opcfoundation.org/UA/PNGSDGM/ Namespace
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.6.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  11.2 Handling of OPC UA Namespaces
  PROFINET Drives Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server URI Namespace ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. http://opcfoundation.org/UA/PNENC/ Namespace
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  4.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  4.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  22.3 Handling of OPC UA Namespaces
  commercial kitchen devices Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100. The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/
• OPC-30250 – OPC Unified Architecture for DEXPI
  4.2.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
• OPC-30250 – OPC Unified Architecture for DEXPI
  4.2.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 4.2.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30250 – OPC Unified Architecture for DEXPI
  5.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30250 – OPC Unified Architecture for DEXPI
  5.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30250 – OPC Unified Architecture for DEXPI
  12.2 Handling of OPC UA Namespaces
  DEXPI Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DEXPI/ Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is server specific. Mandatory Vendor specific types
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this companion specification is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  9.2 Handling of OPC UA Namespaces
  I4AAS Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. M Local Server ... namespace shall have namespace index 1. M http://opcfoundation.org/UA/I4AAS/ Namespace for NodeIds and BrowseNames defined in this companion specification. The namespace index is Server specific. M Vendor specific types
• OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  4.2.3.1 Concepts
  PersonType" are expected to have the same children with the same BrowseNames . Within a type, the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that are implemented
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  10.2 Handling of OPC UA Namespaces
  used in a LADS Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This Namespace shall have Namespace index 0. Local Server ... This Namespace shall have Namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The Namespace index is Server specific. http://opcfoundation.org/UA/Machinery/ Namespace
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-34100 – OPC UA for Energy Consumption Management
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-34100 – OPC UA for Energy Consumption Management
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-34100 – OPC UA for Energy Consumption Management
  6.2.2.1 Overview
  unique identification that is used as BrowseName for instances of the EnergyMeasurementType . Those BrowseNames are also used for the interfaces (see 6.2.3 ). The Description (in English) may be used
• OPC-34100 – OPC UA for Energy Consumption Management
  6.2.2.2 Explanations to the defined measurements
  system integrator or manufacturer may use any period that is appropriate or available. The BrowseNames of the standardized measurement identifiers follow the following naming conventions: AcPe: Phase to Neutral AcPp
• OPC-34100 – OPC UA for Energy Consumption Management
  12.2 Handling of OPC UA Namespaces
  Energy Consumption Management Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. http://opcfoundation.org/UA/IA/ Namespace
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  20.2 Handling of OPC UA Namespaces
  Machinery Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server URI Namespace ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. http://opcfoundation.org/UA/IA/ Namespace
• OPC-40001-2 – OPC UA for Machinery - Part 2: Process Values
  11.2 Handling of OPC UA Namespaces
  Machinery - Process Values Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. http://opcfoundation.org/UA/Dictionary/IRDI Namespace
• OPC-40001-3 – OPC UA for Machinery - Part 3: Job Management
  11.2 Handling of OPC UA Namespaces
  Machinery Job Management Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/ISA95-JOBCONTROL_V2/ Namespace for NodeIds and BrowseNames defined in OPC 10031-4 . The namespace index is Server specific. http://opcfoundation.org/UA/Machinery/ Namespace
• OPC-40001-4 – OPC UA for Machinery - Part 4: Energy Management
  6.1 General
  energy. In the example, it provides information on Electricity , CompressedAir , and Steam _ Superheated . The BrowseNames of those Objects are defined in this specification (see 6.3 ), representing different resources. Details
• OPC-40001-4 – OPC UA for Machinery - Part 4: Energy Management
  6.3 Standardized BrowseNames to group energy measurements based on resources
  Standardized BrowseNames to group energy measurements based on resources This specification defines standardized BrowseNames as entry points to energy metering points of specific resources. They are defined
• OPC-40001-4 – OPC UA for Machinery - Part 4: Energy Management
  9.1 Well-Known 0:FolderType BrowseNames
  Well-Known 0:FolderType BrowseNames The 0:FolderType BrowseNames are formally defined in Table 11 . Table 11 - Well-Known 0:FolderType BrowseNames BrowseName Purpose Electricity Entry point for energy measurements
• OPC-40001-4 – OPC UA for Machinery - Part 4: Energy Management
  11.2 Handling of OPC UA Namespaces
  Machinery Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server URI Namespace ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/Machinery/ Namespace for NodeIds and BrowseNames defined in OPC 40001-1 . The namespace index is Server specific. http://opcfoundation.org/UA/IA/ Namespace
• OPC-40001-101 – OPC UA for Machinery - Part 101: Result Transfer
  12.2 Handling of OPC UA Namespaces
  Machinery - Result Transfer Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. http://opcfoundation.org/UA/Machinery/Result/ Namespace
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identifies the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  12.2 Handling of OPC UA Namespaces
  Robotics Server. NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100. T he namespace index is Server specific. Mandatory http://opcfoundation.org
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.2.2 BrowseNames
  BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.3.1 General
  NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  4.2.3.1 Concepts
  instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that multiple Servers
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  4.2.3.2 Namespaces
  QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  11.2 Handling of OPC UA Namespaces
  Cranes and Hoists Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/Robotics/
• OPC-40077 – OPC UA interfaces for plastics and rubber machinery - Data exchange between injection moulding machines and MES
  7 IMM_MES_InterfaceType
  vendor specific namespace with server specific namespace index (see Table 14 ). The BrowseNames of the nodes below are in the namespace of the specification where used Type is defined. Examples