See also: OATC Wiki Home

Date: 26 Januari 2012
Time: 9:00- 10:00 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)

Apologies

Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)

Status OGC

Standa and Stef had a look at the content of comparable OGC documents.
We made such a document, and sent it for review to Roger.
After that we elaborated chapter 7, the requirements, in two different ways:

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 3) 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

  • No labels

Disclaimer