...
- Question: what does isAvailable() mean in case of multiple consumers. Do all consumers need to have the same time(s)?
Discussion/Conclusion:
We decided to extend the IsAvailable() method with an IExchangeItem argument, so that the caller can specify which availability he wants to check:
bool IsAvailable(IExchangeItem querySpecification).
The ValueDefinition/ElementSet/TimeSet definition of the querySpecification specifies exactly what is needed.
Generally speaking, it is on one of the consumers that is passed as the argument:
...
- The Timezone issue has been re-adressed. The .Net TimeZone does not provide what we need, while the TimeZoneInfo is only available in 3.5, and therefore will not run on MONO.
Discussion/Conclusion led to the following decisions:- Daylight Saving Time jumps in time series are not allowed
- The TimeSet will contain a property that expresses its offset from UTC, expressed in hours (see below). The Gui will check these offsets, and if they are different, it will ask the user to put a decorator in between.
Note: in future and/or more platform specific versions of the standard we may reconsider introducing the timezone info again.
- Decorator issues:
- Do we need to recognize the type of decorator (time, space, SI-conversion)?
- Do we want to support 3th-party decorators indeed?
Discussion/Conclusion: We will add an Update() method to the OutputDecorator. The linkable component calls this Update() on all its decorators at the end of its own Update(). This actually is completely the same as what happens in the current 1.4 Wrapper: after IEngine.PerformTimeStep the wrapper updates the buffers.
...