...
* at 2.: This leads to a main difference between OpenMI 1.x and OpenMI 2. In order to become 1.x compliant the classical time and space dependent component just had to implement the basic ILinkableComponent. This component would have to implement the basic and the time and space specific extension interfaces for becoming OpenMI 2 compliant.
2.1.3. What
...
does the compliancy
...
definition mean for the user?
Linking OpenMI 2 compliant components has become much more flexible than it used to be with OpenMI 1.x. Components with different concepts or in OpenMI language extensions can exchange their data. A component with a date and the classical Modified Julian Day time definition can for example provide a consumer component, defining its simulation time by an index, with data. The provider would implement the time and space extension whereas the consumer could implement an extension for index-related dictionaries. The provider should contain an AdaptedOutput converter using both time definitions and thus being able to convert the time to the index value. This requires more user knowledge about both time definitions enabling him More knowledge about the underlying extensions is required from the user in order to select the appropriate items and to check the plausibility of the results. This is the price is being paid for the higher flexibility, not less due to the OpenMI but to the complexity of the task.
If both LinkableComponents implement the same OpenMI extension interface, their provider consumer relationship will remain as straight forward as with OpenMI 1.x. The , the conversions in AdaptedOutput are will be easier to use and to check.
One should remember that compliancy does not mean a total pure plug and play connection. The OpenMI provides the community with an interface standard and tools for convenient data exchange. But the From the technical point of view most of the input and output of two LinkableComponents can be connected for data exchange. The approved, but updated interface definitions as well as the extensions preserve the used slimness of the OpenMI. Neither the standard nor the related sdk offer too much methods for checking the correctness of the variables. The user has the responsibility for selecting for example the appropriate quantities and the locations where they are defined.
2.1.4. What does the compliancy definition mean for an application developer?
todo, after 2.2. has been decided, since OpenMI 2 has remained a slim standard. It offers the approved methods for efficient data exchange and additional extensions for a wider spectrum of components.
2.2. How to define the extension interfaces
...