Figure A.3 shows how Process Values (see
OPC RIO) belonging to RioChannelType Objects are mapped into the SerializationValue DataType.
The “SerializationEntity” referenced by the SerializationStartNode directs the SerializationProcess to follow only HasRioOutputChannel ReferenceTypes. Although the SerializationDepth is configured as “no limit” (see 6.3.5), the SerializationProcess would stop as soon as a RioChannelType Object is reached, since these Objects only have components referenced using the HasComponent ReferenceType. To include the components of the RioChannelType Objects into the SerializationScope, each Channel Object references a “SerializationEntity” Object which has the IncludeReferenceType array Property containing the HasComponent ReferenceType. The ConsiderSubElementSerializationProperties SerializationProperty of the “SerializationEntity” (see 6.3.6) referenced by the SerializationStartNode causes the settings of the “SerializationEntity” Objects referenced by the Channel Objects to be applied, effectively extending of SerializationScope with all components of the subtrees originating from the Channel Objects.
The JSON snipped shows how the Values in the SerializationScope are serialized using VerboseEncoding (see OPC 10000-6) and RawData field encoding (see OPC 10000-14) in a PubSub scenario.
In Figure A.3 the details of the generated QualifierValueStructureDataType structures are not shown in the table visualizing the nested structure DataTypes, whereas the JSON snippet shows these structures in-depth.
