Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents

1. Comments from review

Consider support for parallel computations

This is a candidate for an extension to the component, see section "Possible candidates for extensions". We will try to make the standard such that it ease the development of such an extension.

Make clear how use IElementSet to work with OGC formats

Two alternatives were discussed:

...

The discussion turned into which strategy was the best for OpenMI: To document specialized interfaces, or to have general ones and allow them to be extended over time.

Add initialize method to IAdaptedOutput

Adding Initialize() to IAdaptedOutput, similar to the method of the ILinkableComponent (thumbs up).

See minutes of meeting 26 - the "IArgument.IsReadOnly" section - describes that the Initialize should not have any arguments. Though, that has not been implemented, and may produce some work, especially for the GUI. We will investigate the amount of work, and may leave it with the arguments in. In any case we will assure that the two have the same Initialize method signature.

Re-introduce the IState interface

Discussion turned first to whether the IIdentifiable should extend from the IDescribable, in which case the IState is redundant. Their relation has been discussed before.

Especially extra method has been introduced due to the two interfaces not being related.

Two options were discussed:

Code Block

public interface IIdentity : IIdentifiable, IDescribable {}

or alternatively

Code Block

public interface IIdentifiable : IDescribable {
  string Id { get; }
}

Currently all classes implementing IIdentifiable also need to implement IDescribable. Hence there is no problem in either ways.

Vote resulted in the bottom case. (thumbs up)

IManagedState still returns the IIdentifiable, and will then include the description.

Does not have any impact on SDK.

How to make the standard extendable

...

Releasing standard and then extensions.

Possible candidates for extensions

...

:

  1. LinkableComponent: Parallel computing component
  2. ExchangeItem: FRAMES dictinaries.
  3. ValueDefinition: ontologies, FRAMES dictinaries.
  4. ElementSet: Advanced spatial/GIS functionality.
  5. ValueSet: FRAMES dictinaries.
  6. TimeSet.

ad: ElementSet: Advanced spatial/GIS functionality:

Typical geometrical element types for models are:

...

Check in the status flag whether there are specific loop approach flags.

Releasing full standard

The full release, reflecting all suggested review requests, including fully functional and tested SDK and GUI.

Current problems:

No model, neither test models nor real world model has really been used and tested using the 2.0 standard. Hence, there are many unknowns and in order to get around all possible issues, quite a lot of work is required.

...

IValueSet.ElementCount and IValueSet.TimesCount is removed (thumbs up).Adding Initialize(IArgument[] arguments) to IAdaptedOutput, similar to the method of the ILinkableComponent - redundant (thumbs up).