Search

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

43 result(s) for DisplayName

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

5.2.4 BrowseName

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 to unambiguously
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.5 DisplayName

DisplayName The DisplayName Attribute contains the localised name of the Node . Clients should use this Attribute if they want to display the name of the Node to the user. They ... this purpose. The Server may maintain one or more localised representations for each DisplayName . Clients negotiate the locale to be returned when they open a session with the Server . Refer
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.6 Description

localised text using the same mechanisms for localisation as described for the DisplayName
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.3.2 Attributes

used in References that specify that the SourceNode contains the TargetNode . The inherited DisplayName Attribute contains a translation of the BrowseName. The BrowseName of a ReferenceType shall be unique ... having the corresponding "Sourced To" inverse References to its signal sinks. The DisplayName and the InverseName are the only standardised places to indicate the semantic of a ReferenceType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.3.3.3 HasSubtype References

subtypes and can be refined there (e.g. "spans a special hierarchy"). The DisplayName , and also the InverseName for non-symmetric ReferenceTypes , reflect the specialization. If a ReferenceType specifies
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.3.2 Attributes

NodeId . Inherited Attribute values may be overridden by the subtype, the BrowseName and DisplayName values should be overridden. Special rules apply for some Attributes of VariableTypes as defined
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.4 OptionalPlaceholder

further considered for instantiating the TypeDefinition . It is recommended that the BrowseName and the DisplayName of InstanceDeclarations having the OptionalPlaceholder ModellingRule should be enclosed within angle brackets. When overriding
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.5 MandatoryPlaceholder

further considered for instantiating the TypeDefinition . It is recommended that the BrowseName and the DisplayName of InstanceDeclarations having the MandatoryPlaceholder ModellingRule should be enclosed within angle brackets. When overriding
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.21 IsDeprecated ReferenceType

Object which represents the information model version where the Node was first deprecated . The DisplayName and Description of the TargetNode should suggest the information model version and other suggestions
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

C.2.2 Simple notation

NodeClass Graphical Representation Comment Object Rectangle including text representing the string-part of the DisplayName of the Object . The font shall not be set to italic. ObjectType Shadowed rectangle including ... text representing the string-part of the DisplayName of the ObjectType . The font shall be set in italic. Variable Rectangle with rounded corners including text representing the string-part
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

C.2.3 Extended notation

NamespaceIndex or LocaleId is used in those structures they can be omitted. The DisplayName contains a LocaleId and a String . Such a structure can be exposed as [<LocaleId ... String> where the LocaleId is optional. For example, a DisplayName can be "en:MyName". Instead of that, "MyName" can also be used. This rule applies
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.29 ReferenceDescription

nodeId shall contain the namespace index. browseName 1 QualifiedName The BrowseName of the TargetNode . displayName LocalizedText The DisplayName of the TargetNode . nodeClass 1 NodeClass NodeClass of the TargetNode . typeDefinition ... because the local Server might not continuously monitor the remote Server for changes. The displayName shall be provided for remote Nodes
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

5.1 General

specified in Table 3 . Table 3 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each server shall provide the DisplayName identical to the BrowseName of the Node
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.2 BaseEventType

source of the Event . This could be the string-part of the DisplayName of the Event source using the default locale of the server, if the Event is specific ... whenever an Event cannot be assigned to a more concrete class. ConditionClassName provides the DisplayName of the of the ConditionClassType provided in the ConditionClassId . ConditionSubClassId specifies additional class[es] that
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.6 FolderType

Node of a subtree, and have no other semantics associated with them. However, the DisplayName of an instance of the FolderType , such as "ObjectTypes", should imply the semantics
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.6.4.3 Definition of EUInformation

Int32 Identifier for programmatic lookup. -1 is used if a unitId is not available. displayName LocalizedText The displayName of the engineering unit is typically the abbreviation of the engineering unit
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.6.4.4 Mapping of UN/CEFACT to EUInformation

unitId = unitId | c; } The Symbol field shall be used as invariant locale for displayName . Servers can configure multiple additional locales for each displayName . However, if none of the LocaleIds specified
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.6.4.5 Mapping of IEC 62720 to EUInformation

unitId = unitId | c; } The Short Name field shall be used as invariant locale for displayName . Servers can configure multiple additional locales for each displayName . However, if none of the LocaleIds
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

A.3.1.3 Item

item in the DA Server is used as the BrowseName and the DisplayName for the Node in the COM UA Wrapper. See also clause A.3.1.5 . The ItemId
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

A.3.1.4 Property

property in the DA server is used as the BrowseName and the DisplayName of the Node in the COM UA Wrapper. The PropertyID and ItemID (if they exist
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

A.4.2.2 Object Nodes

ReferenceTypeId as Organizes and HasChild. IncludeSubtypes as True NodeClassMask as Object and Variable The DisplayName of the OPC UA node is used as the Name for each Branch ... Description attribute is provided. Item Description (Property ID: 101): The value of the DisplayName attribute of the node in the OPC UA Server is assigned to this property. NOTE
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

A.4.2.3 Variable Nodes

server is represented in the Data Access COM UA Proxy as an Item. The DisplayName of the OPC UA node is used as the Name for each Item ... assigned the EU Units property . Item Description (Property ID: 101): The value of the DisplayName attribute of the node in the OPC UA Server is assigned to this property. High
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.1 Event areas

Method s. The Area name returned by BrowseOPCAreas is used as the BrowseName and DisplayName for each Area Node . The QualifiedAreaName is used to construct the NodeId . The NamespaceURI qualifying
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.3 Event categories

Server as ObjectTypes which are subtypes of BaseEventType . The BrowseName and DisplayName of the ObjectType Node for Simple and Tracking Event Types are constructed by appending the text 'EventType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.4 Event attributes

HasProperty Reference s from the ObjectTypes which represent the Event Categories. The BrowseName and DisplayName are the description for the Event Attribute . The data type of the Event Attribute
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.10.3.2 ParentNodeName

ParentNodeName This parameter with DataType String defines the BrowseName and DisplayName of the parent Node for the Variables representing the fields of the subscribed DataSet
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.2 AliasNameType ObjectType Definition

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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

product family, but this shall be described on the OPC Foundation product page. The DisplayName of the instance of the AutomationComponent shall be able to be resolved on the Website
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.4 AssetConnectorType definition

example, it might be the name of the target of this connector, the DisplayName would be slot1, and the Name would be Pump1. Figure 23 provides an illustration of some
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.4 NodeClass mapping

BrowseName is the default OPC UA server Namespace ( Namespace index equals one). DisplayName X If not present in the AML, the OPC UA DisplayName is inferred by the AML object ... Name. If the OPC UA DisplayName is present and has multiple localizations, the localizations are mapped to additional localized sub-attributes of the DisplayName AML attribute . All DisplayNames that
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.2.2 BrowseNames

Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.3.1 General

specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.2.2 BrowseNames

Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.3.1 General

specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

10.5.3 AddLink Method

writable, so the end-user can change the URI. In addition, the BrowseName , DisplayName , and Description might be writable. Servers might restrict the execution of this Method as well ... respectively. Signature AddLink ( [in] 0:UriString LinkToExternalSource, [in] 0:QualifiedName BrowseName, [in] 0:LocalizedText DisplayName, [in] 0:LocalizedText Description, [out] 0:NodeId LinkVariable); Table 31 - AddLink Method Arguments Argument Description
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.2.2 BrowseNames

Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.3.1 General

specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.2.2 BrowseNames

Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.3.1 General

specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each server shall provide the DisplayName identical to the BrowseName of the Node
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.2.2 BrowseNames

Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.3.1 General

specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.2.2 BrowseNames

Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.3.1 General

specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node