6.2 AliasNameType ObjectType Definition
Instances of the AliasNameType ObjectType provide alternate names for Nodes. The AliasNameType is formally defined in Table 1.
| Attribute | Value | |||||
| BrowseName | AliasNameType | |||||
| IsAbstract | False | |||||
| References |
Node
Class | BrowseName | DataType | TypeDefinition |
Modelling
Rule | |
|---|---|---|---|---|---|---|
| Subtype of the BaseObjectType defined in OPC 10000-5 | ||||||
| ConformanceUnits | ||||||
|---|---|---|---|---|---|---|
| AliasName Base |
This ObjectType has no Properties or Variables. The BrowseName of the Object is used as the alias name. The string part of the BrowseName shall be the DisplayName with an empty locale id and no other locale shall be provided. This Object shall have at least one AliasFor Reference (or subtype of).
A Client shall always ignore the namespace associated with an AliasName for comparison with other AliasNames. AliasName can be defined in Namespace 1 (the local Server) or in some vendor defined namespace. See OPC 10000-3 for additional details on Namespaces.
The AliasName Object’s BrowseName shall not be modified once it is defined. If an AliasName is to be changed, it shall be a deletion of the old AliasName and the addition of the new AliasName. This requirement allows aggregating Servers to detect new AliasNames. The deletion and then addition of an AliasName results in a new NodeId for the AliasName.