...

• Move IsAvailable to IExchangeItem. Is it only for a thread-safety? If yes than see also ICollection.IsSynchronized

  Stef: The question is confusing, the actual issue is that we should distinguish between IsAvailable and IsValid.
  We are now realized that there is a difference between IsAvailable (only for output item, means it is for consumers) IsValid (probably for IExchangeItem, meaning if item is valid in the context of current component, maybe updated during Validate() call)?

  • To discuss lator
• Move Values { get; set; } to IExchangeItem

  Stef: alternative would be to add get to the IInputExchangeItem

  • get accepted,
  • set review lator
• Change ID to Id - .NET Style Guidelines, FxCop

• Wiki Markup
  Add *params* keyword to IArguments\[\] args parameter in Initialize(IArgument\[\] args).

  •  Adrian review, if happy then ...
• Change "string Validate()" to "bool IsValid(IExchangeItem item)"

  Gena: probably the second one is not needed if we will have IsValid in IExchangeItem.
  string return type in the Validate() has to be changed to void.

  • Requires review after more experiance with implementing standard

• Wiki Markup
  Add "params IExchangeItem\[\] items" argument to Update() in order to specify explicitly what should be updated.

  • as IOutputItem, maybe later generalise to IExchangeItem i.e. allow IInputItem
• Remove AddConsumer/RemoveConsumer and use BindingList in the implementation instead to listen to IOutputItem.Consumer.Add() / Remove()
  • Not critical yet, so leave for now, review again later
• Temporal ==(rename)==> TimeSet and add Durations, TimeZone properties to it (see also changes from Rob in Java version)
  • Rename
  • Requires discussion in lator meetings
• When we get loops in the compositions - we have to tell which component will be first! (WHAT SHOULD WE DO IN THIS SITUATAION?) Relevant when implementing the Runner process in GUI
  • Revisit in lator meeting
• Replace all ITime, ITimeStamp, ITimeSpan by: System.DateTime, System.TimeSpan. Should be straightforward. For components working in Julian only time in FORTRAN CalendarConverter can be used. But for .NET all nice features of the .NET date time, time span will be available, e.g. DateTime.AddDays(int), DateTime.AddHours(int), time1 > time2, time1.AddDays(1) > DateTime.Now, and so on.
  Seems to be very straightforward and simple to implement.**
  •   Review lator (today?)
• Change XYPoint+XYZPoint, ZYPolyline+XYZPolyline => Point, Polyline (make it look more like OGC entities)
  • Review OGC methods to see how we know when a Z coordinate exists?
• Split IIdentity into class IIdentifiable { long Id { get; set; } } and class IDescribable { string Caption { get; set; } string Description { get; set; } }
  • Splitting interfaces
  • Make various interfaces derive from IIdentifiable, to review
• Do we need a TimeHorizon in the ILinkableComponent ? Seems to be useless since we have ITemporal
• IArgument needs a mechanism for identifying the type of argument e.g. File, Path, int double etc Very usful for providing customised GUI functionality
  • Adrian to come up with proposal for next meeting
• Using empty Temporal and ElementSet in the Input items
• Changing of the ElementSet during the time and different Time Times (steps) for different elements Elements
  • For the Time can be probably solved by missing values

...

interface IDecorator : IOutputItem, IInputItem
{
   IArgument[] Arguments { get; }
}

• We need to address this
• Method: this is one possibility, others need review

Using empty Temporal and ElementSet in the Input items

Two components

• C1 Provider of non-equidistant time series /100 steps/ for the set of the 30 XYpoints elements (for example database)
• C2 Component using TS for computation (consumer)

Case1

• C1 - InputItem Temporal set of Time /5 steps equidistant /, ElementSet - 3 Elements
• C2 - OutputItem after update - obtain values (time step) for the element in ElementSet 15 values
  Decorator can be needed for both Time and Space

Case2

• C1 - InputItem Temporal Empty, Element Set - 3 Elements
• C2 - OutputItem after update - obtain All values (time steps) for the element in ElementSet 300 values
  Decorator can be needed for Space

Case3

• C1 - InputItem Temporal set of Time /5 steps - equidistant/, Element Set - empty
• C2 - OutputItem after update - obtain 5 steps for all elements 150 values
  Decorator can be needed for Time

Case 4

• C1 - InputItem Temporal set empty, Element Set - empty
• C2 - OutputItem after update - obtain 100 steps for all elements 3000 values
  Decorator not needed

Suggestion

Based on this - suggestion for possibility to

...

Use Case: analytical function

5. OATC Procedures

6. www.OpenMI.org and wiki.OpenMI.org

...

All tasks are handled by sourceForge. GOTO: OpenMI Tasks on source forge

9. Any other business

...

• Check ideas mentioned in the poster of Jon Goodall :

See goodall_poster.pdf

...

• - see meeting 22