[FEATURE] Support time-bound update of augmented properties #14
Description
In many situations when creating a Digital Twin one may need to store data that has a relationship with the time that has passed in the lifecycle of the DT.
One classical example would be to compute and store the total power consumption of a device or the total time of operation since its activation...
This goes towards the topic of (basic) augmentation.
How to support the definition and management of such properties?
What does that mean for the Digital Twin State? Are they part of it or should they be separated from it?
Maybe the library should support some patterns to handle this properly avoiding developers coming up with original solutions.
Some ideas:
- scheduled fake "time" events could come from the custom physical adapter to update the value of some properties (or from a dedicated adapter that handles only this fake time related events)
- jobs can be scheduled within the shadowing function to compute and update the value of some properties
- reading a special kind of property from a Digital Adapter could trigger an update mechanism to compute the most up-to-date value