OATC meeting no 8, Delft, October 22 - 24, 2007

OpenMI Association Technical Committee meeting no 8

Date: October 22 - 24, 2007

Venue: WL|Delft Hydraulics, The Netherlands

Participants:
Jan Gregersen, LICTEK (gregersen@lictek.dk) (chairman of the meeting)
Peter Sinding, DHI - Water & Environment (psi@dhi.dk)
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, WL | Delft Hydraulics (stef.hummel@wldelft.nl)
Gennadii Donchyts (Gena), WL | Delft Hydraulics (gennadii.donchyts@wldelft.nl)
Onno Rooseschoon, Alterra (Onno.Roosenschoon@wur.nl )
Peter Gijsbers, WL | Delft Hydraulics (Peter.Gijsbers@wldelft.nl)
Rob Knapen, Alterra (Rob.Knapen@wur.nl) - Tuesday afternoon + Wednesday

Apologies:
Wiktoria Daniels, Wallingford software (wiktoriad@wallingfordsoftware.com)

Objective:
OpenMI 1.4 release
OpenMI version 2.0

Documents:
http://www.openmi.org/
http://sourceforge.net/projects/openmi
http://www.lictek.dk/openmi/

Agenda / Issues:

1. Minutes from last meeting 

See document:http://www.lictek.dk/openmi/Meetings/Meeting07/OpenMIAssocaition.TechnicelComitteeMeeting.7.Minutes.doc

1. Use cases

   1.  

2. Feature requests

   1. From Jan: I have activated the feature request facility on source forge again. I think that this a more practical way for handling these requests rather that the HTML list.  I made some categories: OpenMI.Standard, Oatc.OpenMI.Sdk, Oatc.OpenMI.GUI, Oatc.OpenMI.Tools, Oatc.OpenMI.Examples, and documentation. And I made some groups: 1.4.0.0 Release, 1.4.1.0 Release, 2.0.0.0 Release, Considered,  Rejected, and Don't use. The latter is there simply because it is not possible to remove existing groups (we can rename it to something else when we need a new group).  The main idea is to categorize items after which package/namespace these belongs to and to groups these after which release they are accepted to be implemented for. Some items may also be grouped as rejected or considered.
      
      I hope that the meeting will agree with this approach. In this case:
      
      We need to review the requests and assign implementation of these to someone.
      We also need to review the request listed on : http://www.lictek.dk/openmi/ and decide which should be moved to source forge features request list and which simply should be removed.

3. OpenMI 1.4.0.0 release

   1. General status for OpenMI 1.4 release.
      See also OpenMI 1.4.0.0 task on source forge

4. OpenMI 2.0 architecture

   1. OpenMI version 2.0 roadmap
      We need to make an updated version 2 roadmap.

5. OpenMI Java and OpenMI .net synchronization

   1. The new OpenMI standard definition: Personally I am not in favor of making the standard language (implementation) specific. However, looking forward, how will this 1.4 version be updated / modified so that the 2.0 version includes both a .NET and a Java implementation? (Rob)

6. Miscellaneous issues

   1. Meeting plan for 2008
      From Jan: We should make a list with new dates for OATC meeting for 2008. My suggestion is to make the meeting less frequent (e.g. use a two months interval rather than a six weeks interval.) Also I think we should schedule more frequent web conferences (e.g. weekly or every second week).

7. Tasks and unresolved issues

   1. Moved to source forge
      From Jan: I was getting a bit frustrated over managing all the tasks and unresolved issues. I have therefore moved these to https://sourceforge.net/projects/openmi/. Hope that this helps.
      We need to review these tasks and update status for these.

8. Any other business