Search

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

7 result(s) for HierarchicalReference

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

3.1.9 Hierarchical Reference

Hierarchical Reference Reference that is used to construct hierarchies in the AddressSpace Note 1 to entry: All hierarchical ReferenceTypes are derived from HierarchicalReferences
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.4 View NodeClass

References HierarchicalReferences 0..* Top level Nodes in a View are referenced by hierarchical References (see 7.3 ). HasProperty 0..* HasProperty References identify the Properties of the View . Standard Properties NodeVersion ... standards may define additional Properties for Views . Views can be the SourceNode of any hierarchical Reference . They shall not be the SourceNode of any NonHierarchical Reference
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.1 Description

AddressSpace hierarchy. Using this Service , each Node is added as the TargetNode of a HierarchicalReference to ensure that the AddressSpace is fully connected and that the Node is added
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.7 UAInstance

InstanceDeclarations and shall reference a UANode which is the source of a HierarchicalReference to the Node. DesignToolOnly Boolean If TRUE the instance is a placeholder for use by design tools
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.9 DeviceSet entry point

either directly or indirectly reference all instances of a subtype of ComponentType with a Hierarchical Reference . For complex Devices that are composed of various components that are also Devices , only ... DeviceSet Object . The components of such complex Devices shall be locatable by following Hierarchical References from the root instance. An example is the Modular Device defined in 9.4 and also
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.1 Node definitions

Dependencies exist if the Node is the source of HasTypeDefinition , HasInterface , HasAddIn or any HierarchicalReference . Dependencies also exist if the Node is the target of a HasSubtype Reference . For Variables
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.1 Node definitions

Dependencies exist if the Node is the source of HasTypeDefinition , HasInterface , HasAddIn or any HierarchicalReference . Dependencies also exist if the Node is the target of a HasSubtype Reference . For Variables