NOTE: Other parts of this series of standards can extend the OPC UA Meta Model by adding Attributesand defining new ReferenceTypes.

Base is shown in Figure B.4.

Figure B.4– Base

ReferenceTypeis shown in Figure B.5and predefined ReferenceTypesin Figure B.6.

Figure B.5– Reference and ReferenceType

If Symmetricis “false” and IsAbstractis “false” an InverseNameshall be provided.

Figure B.6– Predefined ReferenceTypes

Attributes are shown in Figure B.7.

Figure B.7– Attributes

There may be more Attributesdefined in other parts of this series of standards.

Attributesused for references, which have a NodeIdas DataType, are not shown in this diagram but are shown as stereotyped associations in the other diagrams.

Objectsand ObjectTypesare shown in Figure B.8.

Figure B.8– Object and ObjectType

EventNotifierare shown in Figure B.9.

Figure B.9– EventNotifier

Variable and VariableType are shown in Figure B.10.

Figure B.10– Variable and VariableType

The DataTypeof a Variableshall be the same as or a subtype of the DataTypeof its VariableType(referred with HasTypeDefinition).

If a HasPropertypoints to a Variablefrom a Base“A” then the following constraints apply:

• The Variable shall not be the SourceNode of a HasProperty or any other HierarchicalReferences Reference.
• All Variableshaving “A” as the SourceNodeof a HasProperty Referenceshall have a unique BrowseNamein the context of “A”.

Method is shown in Figure B.11

Figure B.11– Method

DataType is shown in Figure B.12.

Figure B.12– DataType

View is shown in Figure B.13.

Figure B.13– View