| scrollbar |
|---|
...
See also: OATC Wiki Home
Date: June 8 - 9, 20010
Venue: Unesco-IHE, The Netherlands
...
Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Standa Vanecek, DHI (s.vanecek@dhi.cz)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
Jesper Grooss, DHI (jgr@dhigroup.com)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)
Apologies:
~jnh@dhigroup Unknown User (jnh@dhigroup.com), DHI (jnh@dhigroup.com)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade@baw.de)
Daniele Andreis,Universita` di Trento,(daniele.andreis@gmail.com)
Jan Gregersen, LicTek
...
Cons: It adds complexity to the standard (A standard developer may not have/do not want to have bother about this level of skills), and it is specific to java and .net.
...
Update the IQuality interface
First change: Return type of IQuality.Categories differs in java and C#. Options:
| Code Block |
|---|
IEnumerable<ICategory>
IList<ICategory>
ICategory[]
|
IList<ICategory> 
.
Second and third changes: Difficult to make as well a generic as a special quality implemention that does this correctly, taking into account that the category may come from another component elsewhere. Though it was found potentially usefull .
Loop approach
Duplicate - has to do with parallelism
...
Rename IOutput and IInput into IOutputItem and IInputItem
Has been discussed before. There is was also discussed that without "item" it is very implicit. 
How to make the standard extendable
Meeting with EPA on how to make OpenMI and FRAMES work together, and also several reviewers, have revealed the necessity of making the standard extendable instead of "all inclusive". since the "all inclusive" is very difficult to predict.
The base idea is to make very general versions of interfaces, and provide specializations of these. These specializations can be released at a later stage than the standard, and without affecting the standard.
See the section on "Possible candidates for extensions" and this additional discussion page about the Extendable OpenMI 2.0 version.
Strategy for releasing 2.0
...
IValueSet.ElementCount and IValueSet.TimesCount is removed - redundant .
Whats next
- Go through those issues marked with
on a Skype meeting in the near future. - Go through bugs and documentation issues listed in the review.
- Implement proposal for splitting up interfaces in general ones and specific ones. Jesper will look at in within the next month.
- Dictionary implementation updated according to meeting with FRAMES people. Stef will do that.
- Updates agreed on at this and last meeting should be implemented. Stef will take the lead, and can delegate.
- GUI: Someone needs to find resources for this!