See also: OATC Wiki Home
Date: november 3-5, 2008
Venue: Deltares, Rotterdamseweg 185, Delft, The Netherlands
Participants:
Jan Gregersen, DHI / LicTek (gregersen@lictek.dk) (chairman of the meeting)
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
~don (Gena), Deltares (gennadii.donchyts@deltares.nl)
Peter Schade, Bundesanstalt fuer Wasserbau, Germany (Peter.Schade@BAW.DE)
Andrea Antonello, Universita` di Trento, (andrea.antonello@gmail.com)
~onnoroos, Alterra (Onno.Roosenschoon@wur.nl)
Peter Gijsbers, Deltares (Peter.Gijsbers@deltares.nl)
Jon Goodall, Univ South Carolina (goodall@engr.sc.edu)
Apologies:
Rob Knapen, Alterra (Rob.Knapen@wur.nl)
Documents:
http://www.openmi.org/
http://sourceforge.net/projects/openmi
wiki.openmi.org
Agenda
1. Minutes from previous OATC meeting
Minutes: ToDo
2. Maintenance and support
2.1 Reported bugs
(GOTO bug list on SourceForge)
Minutes: ToDo
2.2 Help issues
(GOTO help issues on SourceForge)
Minutes: ToDo
2.3 Discussion issues
(GOTO discussion issues on SourceForge)
Minutes: ToDo
3. OpenMI 2.0 Issues
3.1 Use cases
Minutes: ToDo
3.2 OpenMI 2.0 architecture
3.2.1 Current status
The current OpenMI Standard interfaces a shown in the figure below. The implementation is located in the trunk on source forge.
Minutes: ToDo
3.2.2 Events
At the last meeting we discussed if we adapt the way events are used in C# rather that using our own implementation.
See page : Use standard events instead of many interfaces like IListener, IPublisher
Minutes: ToDo
3.2.3 Configuration interfaces
Minutes: ToDo
3.2.4 IQuality and IQuantity
see also: Rename IValueDefinition to IMeasurable
Minutes: ToDo
3.2.5 Spatial issues
see: Changes to spatial classes related to interoperability with OpenGIS
Minutes: ToDo
3.2.6 ITime
Minutes: ToDo
3.2.7 IArgument
Comment by Jan: I think we need a more powerful argument interface. Such interface should facility different types such as doubles, strings, bool, and selection types. By selection types I think about situations where the user will select on or multiple options from a predefined list. At our last meeting the IDictionary interface was mentioned, but I have doubts that it will provide the functionality needed. Then I came to think about the functionality provided by XML schema files. E.g. for our OpenMICompliancy schema file a pretty complex data structure is well defined. However, I would prefer not to include schema files into the nice clean interfaces based standard, so maybe we can find a interface based solution that has the same functionality as a schema.
Minutes: ToDo
3.2.8 Using Object to pass the values
Minutes: ToDo
3.2.9 IInputExchangeItem
Comment by Peter: In the design as presented before the meeting, the IInputExchangeItem has a Values-set property. I wonder if this is wise from a communication perspective. to outsiders. We want to pull-mechanism to remain the main focus of OpenMI components, such that they can easily be used in a service-oriented architecture. When introducing SetValues at the root level of an IInputExchangeItem, it is much more difficult to explain that we prefer usage of the pull-mechanism, but that some advanced applications may need this put mechanism. I would therefore recommend to move the Values-set property to a separate (derived) interface called IAdvancedinputExchangeItem. This makes explanation much easier, while we introduce less risk with components not being able to handle a set-value.
.
Minutes: ToDo
3.2.10 State management
Comment by Peter: Finally, it becomes time for a persistent state. However, it might be wise to evaluate the experiences with the current state mechanism.
Minutes: ToDo
3.2.11 ILinkableComponent instantiation
Comment by Peter: The OMI file is a pragmatic method to instantiate a component. A Factory pattern should be considerd for the Standard, where the default implementation of the SDK is based on the OMI file.
Minutes: ToDo
3.3 Development and release road map
Version 2 development plan:
September 11th 2008 - November 2nd 2008
Finish the configuration architecture (the decorator pattern)and update SDK and GUI.
November 3 - November 5 2008.
OATC meeting in The Netherlands: special focus on return types and geometry (ElementSet)
November 6th 2008 - January 12th 2009
Implementation of new geometry interfaces and return types. Update SDK and GUI
January 13th - January 15th 2009
OATC meeting in UK. Final decision for the version 2 standard interfaces. This also implies deciding which requested feature that will not be include in version 2.
January 16th - March 9th 2009
Complete implementation and unit testing of the version 2 standard, SDK and GUI
March 10 - March 12 2009
OATC meetings, Denmark. OpenMI 2 standard, SDK and GUI beta release
March 13 - April 20, 2009
Migrate and test selected commercial models and components for version 2
April 21 - April 23
OATC Meeting i The Netherlands. Evaluate real models test and further refinements for version 2
April 24 - June 09 2009:
Continues real models testing, write documentation.
June 10 - June 12 2009
OATC meeting in Denmark. Final evaluation, submission of the version 2 to the OpenMI Association Executive Committee for acceptance
June 13 - October 13 2009
The standard is reviewed by external reviewers
October 14 - December 19, 2009
Adjustments based on comments from the reviewers. Finalization of the OpenMI 2 release.
December 20th 2009
OpenMI 2 standard, SDK and GUI release.
Minutes: ToDo
3. OpenMI Java and OpenMI .net synchronization
Minutes: ToDo
4. OATC Procedures
4.1 Proposal for procedures for OpenMI Standard releases
see: Proposed procedure for OpenMI Standard releases
Minutes: ToDo
4.2 Proposed procedure for evaluation of OpenMI compliance
see Proposed procedure for evaluation of OpenMI compliance.
Minutes: ToDo
4.2 Review and update the OATC procedures
What is the status with respect to procedures other that the standard release procedure (point 4.1)
Minutes: ToDo
5. www.OpenMI.org and wiki.OpenMI.org
5.2 Could we simply use a wiki for the official OpenMI web site
A proposal to the OAEC is ready in a draft version: see OpenMI Association website proposal_MB.doc
Minutes: ToDo
6. Miscellaneous issues
6.3 Submitted OpenMI compliance XML's
Since last meeting some XML has been submitted. See TUDamstat.zip
The currently accepted components are listed here : M.4.2 Compliant software
6.4 Demo of HRW SDK and Pipistrelle
Adrian will demonstrate the work done by Walling Software.
7. Tasks and unresolved issues
All tasks are handled by sourceForge. GOTO: OpenMI Tasks on source forge
