...

• IIdentity has been split in IIdentifiable and IDescribable. Some interfaces already have been derived from IIdentifiable and/or IDescribable
  • At some stage, we should check all interfaces on whether to derive from IIdentifiable and/or IDescribable or not.
  • At this meeting, we should check that IIdentifiable and/or IDescribable are not used as seperate entities.
• 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.
  See http://public.wldelft.nl/display/OPENMI/Empty+Sets+in+the+Input+Items+-+Element+set+changing+in+time
• Changing of the ElementSet during the time and different Times (steps) for different Elements
  • For the Time can be probably solved by missing values

3.6

...

The ITime Issue

3.6.1 Interface(s)

After some discussions, their were four proposals. See list below (including the original 1.4 situation).
Note: naming to be done yet.

  public interface ITime {
      public double StampAsMJD();
      public double DurationAsMJD();
  }	
  public interface ITimeSet {
      public List<ITime> getTimes();
      bool HasDurations { get; }
  }

...

  public interface ITimeSet
  {
      IList<double> TimeStamps { get; }
      TimeZoneInfo TimeZone { get; }
  }
  public interface ITimeSpanSet : ITimeSet
  {
      IList<double> Durations { get; }
  }

  public interface ITime
  {
  }
  public interface ITimeStamp : ITimeSet
  {
      double ModifiedJulianDay {get;}
  }
  public interface ITimeSpan : ITime
  {
      ITimeStamp Start { get; }
      ITimeStamp End   { get; }
  }

3.6.2 Platform specific time or Modified Julian?

Adrian suggests that we incorporate as less platform specific things in the Standard as possible. This also holds for Lists and events. Will be put on the agenda for next meeting.

5. OATC Procedures

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

...