How to use events and prognoses

[GoetzGoerisch]

Add how to section to whitepaper

Original UC-135
Relates to #5

Additional background:
Please also note: BaseModelChangeEvent - Reasons for use and usage example

See OPC UA Part 3, 9.32 ModelChangeEvents

Coming soon: This event is triggered when the address space changes. In umati we use it in dynamic lists. This way a client can recognize that a list item has been added/deleted. If the list is always static in the server, the event never has to be sent. Changes are additionally visible at the NodeVersion (property of the node which is the entry point or "head" of the list) - the NodeVersion changes as well when the list changes. The OPC UA specification specifies that the NodeVersion must be present if the server sends ModelChangeEvents and should not be present if it does not. Whether a list changes at runtime can therefore be determined from the presence of the NodeVersion in the "list header".

Translated with www.DeepL.com/Translator (free version)