See also: OATC Wiki Home

Date: 16 Februari 2012
Time: 14:30- 15:30 CEST
Venue: Skype Conference Call
Topic: OGC documentation and SDKs

Table of contents

Participants

Adrian Harper, Innovyze Ltd (adrian.harper@innovyze.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
Jesper Grooss, DHI (jgr@dhigroup.com)
~s.vanecek@dhi.cz, DHI (s.vanecek@dhi.cz)
Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)

Apologies

-

E-mail from the dissimination committee (Johan)

up-to-date list of OATC members

Stef will send an e-mail to all current members on the list, and ask whether they:

• still want to be on it
• access the wiki pages

Specification document replaced by OGC format version?

Correct, we are waiting for the OGC people (David Lemon and Simon Cox) to check if they agree with the format we choose.

State of play SDK and GUI?

Next Monday there is a meeting at HR on the formal release date. Most probable another beta in March, and version 1.0 a bit later on.
People who want the latest version can download it from SourceForge. People who are not able to download and build can e-mail Adrian.

State of the documentation of the SDK?

The documentation will be addressed once the SDK and the GUI are released.

Running OpenMI 1.4 components in Pipistrelle (2.0)

Johan of correct, but there are a few things to make clear:

• the OpenMI 1.4. component is able to run in Pipistrelle, and interact with 2.0 components
• however, it does not become OpenMI 2.0 compliant itself (it is just wrapped)
• all the 1.4 component's data operations are not visible and therefore can not be used (however, this can be replaced by the 2.0 adapted outputs

Planning of the OpenMI 2.0 components

Java SDK / GUI

Alterra has funding available for the development of OpenMI. Plans to be made yet on what effort goes to models, applications, SDK, GUI, etcetera.
A way to work with java components in the GUI would be:

• let the component write its 'exchange item xml'
• create the composition in the Pipistrelle GUI
• write a composition XML
• run that composition in a lean and mean jave run time environment

Status OGC

See note above ("Specification document replaced by OGC format version").

Status OpenMI 2.0

No the issue is how to specify and implement the mandatory conformance tests.

• Just state for every interface that its methods are implemented correctly?
• Just say that the component should be loaded in Pipistrelle?
  After some discussion we decided that we will use the same approach as done for netcdf: assume that there is a testing tool implemented, en specify the things to be tested (see the first download on http://www.opengeospatial.org/standards/netcdf)

Johan has asked Standa for the status on the OpenMI 2.0 implementation. Standa will forward the question to Adrian, and Adrian will answer it.
There also is a need for an overview of OpenMI 2.0 compliant components. DHI has a few, but no formal xml etc. yet. Stef will ask the OAEC to find someone to put more effort in gathering compliant components. As a first step Stef will ask the OAEC for a specific email (compliance@openmi.org).
There is a EU proposal (CEnTIEM ³) that will put more attention to OpenMI and existing component.
Jan once implemented a tool that generates 1.4. compliancy info XML after loading the component. We should try to find the source of that tool (Jesper will have a look).

Next meetings

Thursday Feb 2nd, 13:30 CET - 14:30 CET