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
Adrian Harper, Innovyze Ltd (email@example.com)
Stef Hummel, Deltares (firstname.lastname@example.org)
Jesper Grooss, DHI (email@example.com)
~firstname.lastname@example.org, DHI (email@example.com)
Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)
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:
- The more formal way, as used by the OGC for e.g. specifying the content of xml files (a list of requirements, see e.g. the first download on http://www.opengeospatial.org/standards/om)
- The more 'narrative way' a mixture of UML, explanatory text and requirements, like use for defining some interface standards, see e.g. the first download on http://www.opengeospatial.org/standards/wcs)
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 (firstname.lastname@example.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).
Thursday Feb 2nd, 13:30 CET - 14:30 CET