Search

8 result(s) for InstanceDeclaration Hierarchy

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.2 Interface Model
  with the ModellingRule Mandatory using the same BrowsePath in the fully-inherited InstanceDeclarationHierarchy of the ObjectType . The rules for instantiating InstanceDeclarations defined in 6.2.6 shall be applied. Each optional InstanceDeclaration ... with the ModellingRule Mandatory or Optional using the same BrowsePath in the fully-inherited InstanceDeclarationHierarchy of the ObjectType . The rules for instantiating InstanceDeclarations defined in 6.2.6 shall be applied
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.3 InstanceDeclarationHierarchy
  InstanceDeclarationHierarchy The InstanceDeclarationHierarchy of a TypeDefinitionNode contains the TypeDefinitionNode and all InstanceDeclarations that are directly or indirectly referenced from the TypeDefinitionNode using forward hierarchical References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.6 BrowseName within a TypeDefinitionNode
  forward hierarchical References from any InstanceDeclaration . This means that any InstanceDeclaration within the InstanceDeclarationHierarchy can be uniquely identified by a sequence of BrowseName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.1 Overview
  HasSubtype References from the subtype. This collection of InstanceDeclarations is called the fully-inherited InstanceDeclarationHierarchy of a subtype. The remainder of 6.3.3 define how to construct the fully-inherited InstanceDeclarationHierarchy
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.2 Fully-inherited InstanceDeclarationHierarchy
  Fully-inherited InstanceDeclarationHierarchy An instance of a TypeDefinitionNode is described by the fully-inherited InstanceDeclaration­Hierarchy of the TypeDefinitionNode . The fully-inherited InstanceDeclarationHierarchy can be created by starting with the InstanceDeclarationHierarchy ... TypeDefinitionNode and merging the fully-inherited InstanceDeclarationHierarchy of its parent type. The process of merging InstanceDeclarationHierarchies is straightforward and can be illustrated with the example shown in Figure 25 which
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.1 Overview
  Instance of a TypeDefinitionNode will be the root of a hierarchy which mirrors the InstanceDeclarationHierarchy for the TypeDefinitionNode. Each Node in the hierarchy of the Instance will have a BrowsePath ... same BrowsePath . Clients that need to distinguish between the Nodes based on the InstanceDeclarationHierarchy and the Nodes that are not based on the InstanceDeclarationHierarchy can accomplish this using the TranslateBrowsePathsToNodeIds
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.3 Constraints on an Instance
  InstanceDeclaration or a subtype of it. If two InstanceDeclarations of the fully-inherited InstanceDeclarationHierarchy have been connected directly with several References , all those References shall connect the same Nodes
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.3 UANode
  address space. This implies that any instances shall include the fully inherited InstanceDeclarationHierarchy as defined