Annex G (normative) Dictionary Reference 
G.5 Examples

The example in Figure G.3 shows how OPC UA Properties of the DeviceType defined in OPC DI refer dictionary entries in the IEC 61987 Common Data Dictionary.
Figure G.3 – DeviceType Property example
The following Figure G.4 shows how OPC UA Objects could refer to classes in the IEC 61987 Common Data Dictionary and OPC UA Properties to properties in the data dictionary.
In this example, the weight property is referenced from two OPC UA Properties and the different semantic is provided by the referenced classes Transmitter housing or Transmitter body of the parent OPC UA Objects.
Figure G.4 – Example with references to classes and properties
The following Figure G.5 shows how a server can expose the hirarchy of two dictionaries below the optional Dictionaries Object.
Figure G.5 – Example with two dictionaries
OPC 10000-7, OPC Unified Architecture - Part 7: Profiles 
Add the following ConformanceUnits to section 5.4, Table 14 “Address Space Model”:
Category | Title | Description |
---|---|---|
Server | Address Space Dictionary Entries | Support external dictionaries by relating OPC UA Nodes to dictionary entries using the HasDictionaryEntry ReferenceType. |
Client | Address Space Client Dictionary Entries | Follow HasDictionaryEntry References to determine the relatedness of OPC UA Nodes with dictionary entries. |
Add the following ConformanceUnits to the section 6.6.3 Core 2017 Server Facet:
Group | Conformance Unit / Profile Title | Optional |
---|---|---|
Address Space Model | Address Space Dictionary Entries | True |
Add the following ConformanceUnits to the section 6.6.83 AddressSpace Lookup Client Facet:
Group | Conformance Unit / Profile Title | Optional |
---|---|---|
Address Space Model | Address Space Client Dictionary Entries | True |