Figure A.7 shows a SerializationScope configured by the SerializationEntity referenced by the “EnergyManagement” folder (see OPC PE) which is modified by a second SerializationScope.

The ConsiderSubElementSerializationProperties SerializationProperty set to true directs the SerializationProcess to evaluate the SerializationProperties of the SerializationEntity Object referenced by the “MeasurementY1” Variable, which is already part of the “enveloping” SerializationScope.

The IncludeStatus SerializationProperty of this second SerializationEntity is set to true, causing the StatusCode of the “MeasurementY1” Variable Value to be part of the SerializationValue DataType.

The ExcludeReferenceTypes array containing one element with the value HasProperty ReferenceType excludes all Properties of the “MeasurementY1” Variable.

The JSON snipped shows how the resulting SerializationValue structure DataType is serialized using VerboseEncoding (see OPC 10000-6) and RawData field encoding (see OPC 10000-14) in a PubSub scenario. If the StatusCode of the “MeasurementY1” Variable Value is Good, an empty “Status” is generated by the encoder. If the StatusCode is Uncertain or Bad, the StatusCode and the corresponding symbol are generated by the encoder, as shown in Figure A.7. In contrast, the StatusCode of the “MeasurementX1”, “MeasurementX2” and “MeasurementXn” Variable Values is never encoded into JSON.

Figure A.7 – Combining Serialization Scopes

_________