...
* 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 do these compliancy definitions 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 can exchange their data. A component with a date and time definition can for example provide a consumer component, defining its simulation time by an index, with data. The provider should contain an AdaptedOutput converter using both definitions and thus being able to convert the time to the index value. This requires more user knowledge about both time definitions enabling him to check the plausibility of the results. This price is paid for the higher flexibility, not 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 conversions in AdaptedOutput are easier to use and to check.
One should remember that compliancy does not mean a total plug and play connection. The OpenMI provides the community with an interface standard and tools for convenient data exchange. But the user has the responsibility for selecting the appropriate quantities and the locations where they are defined, 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
...