See also: OATC Wiki Home
Date: October xx, 2010
Time: yy - zz CEST
Venue: Skype Conference Call
Topic: From OpenMI 2.0 Beta to OpenMI 2.0
Table of contents
Participants
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
Jesper Grooss, DHI (jgr@dhigroup.com)
Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Standa Vanecek, DHI (s.vanecek@dhi.cz)
~don, Deltares (gennadii.donchyts@deltares.nl)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)
Apologies:
-
1. Remaining issues from meeting no 33, top 2
- Added by Stef when finishing the beta release documentation.
- More issues added by Rob when finishing the Java version and updating the XSD files.
- Issue added based on Peter Gijsber's email.
Issue |
Description |
status |
decision |
|---|---|---|---|
OpenMI XSD files |
The component and compliancy XSD files still are based on 1.4. Must be extended. |
Done by: Rob |
Ok (TimeSpace compliancy issued postponed) |
TimeSpace compliancy in XSD file |
Decide if TimeSpace compliancy needs to be included in the OpenMICompliancyInfo.xsd file and if so how to do it. |
Postponed |
Mark as deprecated in Beta1 |
Move interfaces to TimeSpace extension |
ISpatialDefinition, IElementSet, ITime, ITimeSet could be moved from the base to the TimeSpace extension |
Postponed |
Leave as is for Beta1 |
Update copyright notice |
Add year 2010 to the OpenMI copyright header in all source files |
Java updates done: Rob. |
Update headers |
Distribution package |
Distribute base and timespace extension in a single package or as two? |
Postponed |
Keep as 1 package for Beta1 |
Merge IValueDefinition and IDictionaryItem |
IValueDefinition (with related classes) and IDictionaryItem bought describe data semantics and could be unified. |
<status: open> |
|
<new issue> |
<description> |
<status: open> |
|
Transcript of discussions on the above topics and a few other subjects:
- Compliancy XSD: Remaining issue: Do we want to include TimeSpace specific exchange item information in the compliancy XSD? If so, what should be included and how?
- Release of the 2.0 Beta: Also notify people who participate in the review process about the new version and changes made according to their input.
2. Issues raised in Rob Knapens mail from 23.09.2010
2.1. Final agreement on the extensions
- not clear if OAEC agrees with it or not.
- proper definition of how to use them and what it means for OpenMI-compliancy. Also when mixing OpenMI endorsed and 3rd party extensions.
2.2. Request of US EPA
- how dimensionless data fits into OpenMI without loosing the unit information (measures).
2.3. Mixing time-dependent and time-independent components
- Clarify what should happen when time-dependent and time-independent model components are mixed in a model chain.
- Is there enough "contextual" information available for processing?
