...
http://www.openmi.org/
http://sourceforge.net/projects/openmi
wiki.openmi.org
...
Agenda
1. Minutes from previous OATC meeting
The last OATC meeting was about the configuration interfaces. We had a very exiting discussion about differences between the link approach and the chained approach. At a subsequent web meeting is was decided to go for the chained approach. There is no formal minutes from the OATC meeting.
2. Maintenance and support
...
3.2 OpenMI 2.0 architecture
3.2.1 Current status
We need to remind ourselves about the current status for the OpenMI version 2 development - what is implemented and why. See also: OpenMI.Standard ver 1.4 to ver 2 change log
3.2.2 Configuration interfaces
At the last OATC meetings the focus has been on interfaces that relates to the configuration part of the standard
see also: Jan's ideas for version 2 configuration interfaces
3.2.3 IQuality and IQuantity
One of the change requests we have received for OpenMI Standard version 2 is the ability to handle categorized data. Examples could be "high", "medium", "low" or "grass", "corn", "potatoes".
See use case: Qualitative data support
See UML for proposed OpenMI interfaces
3.3 Development and release road map
Some time ago a prioritized list of issues that should be included in the next release was elaborated (OpenMI version 2 Development plan ). Seems that we already have covered most of the issues plus the quantity/quality issues, which are not listed in the plan. However, we still need a plan with some more strict deadlines.
Since we are dealing with a standard release we must follow the procedure for OpenMI standard releases. So far we do not have such procedure formally accepted by the OAEC. On this agenda (point 4.1) is a proposal for a procedure. So, let's discuss this first and then see how we can fit some dates into this.
3. OpenMI Java and OpenMI .net synchronization
...
The OpenMI standard is released both in a Java and a C# version. This imposes some problems / challenges that we continuously must address:
- The OpenMI standard interfaces.
- Can the proposed changes for the OpenMI 2 release be implemented in both programming languages
- Which one should be developed first and how do we make sure that the implementation are conceptually the same
- The OATC SDK and GUI
For OpenMI 1.4 we have a full implementation of the SDK and GUI in C# but for the Java version the SDK is provided by Alterra and there is no GUI available. How are we going to handle this for version 1.4 and for version 2
- Linking models / components compliant to the Java and C# version, respectively
When running OpenMI linked configurations objects are passed between the components. This makes it technically difficult to handle linked systems where some components are OpenMI Java compliant and some OpenMI C# compliant. At previous meeting we have discussed this issue and one of the conclusion is that since we are not the only ones having this problem, at solution for this may arise from outside. What is the current status with respect to this?
4. OATC Procedures
4.1 Proposal for procedures for OpenMI Standard releases
...
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)
5. www.OpenMI.org and wiki.OpenMI.org
...
We have already put enormous efforts into documenting the OpenMI standard and the SDK. By the end of the HarmonIt project we wrote hundreds of page in the formal documentation (the Book A -F stuff), and more recently we have work worked especially on the wiki to improve the documentation in order to facilitate people new to OpenMI (the HowTo pages). So even though we are well above the typical documentation level for research projects, we still need to improve. I think that improving documentation and guidelines will be the area where we achieve most effect in order to get OpenMI used around the world. Naturally we still need to develop new features, but should not sacrifice documentation. I believe that the getting started pages on the wiki is currently be best entry for new people and I will typically direct such people to these pages. I would appreciate if we could spend a little time going through the getting started pages and assign task for improvements. Specifically, I have noticed that after the upgrade of the wiki sofware some pages have been corrupted.
...
Currently the official OpenMI is exposed on three different web sites www.OpenMI.org, wiki.OpenMI.org and http://sourceforge.net/projects/openmi. There are naturally good reasons for running these three web sites. www.OpenMI.org is the very official nicely formatted quality assured stuff, whereas the wiki is more quick and dirty, and finally sourceforge provides tools for version control, task and bug trackers, and help forum. It is my impression that people, in their search for information about OpenMI may get confused, also I sometimes have doubts about whether I should direct people towards the wiki or www.openmi.org. Maintenance of thee web sites is time consuming, and since we do not know how much funding we will have when the Life project ends, hence we need to go for agile solutions. I discussed these issues with Michiel Blind some month ago and we agreed it should be investigated if we simply could use a wiki for the official web site. There are examples of very nicely formatted wikis around (see e.g.). In my opinion largest advantage of switching to a wiki, it the ability for a large group to easily edit the text on the wiki - so we get the nice stuff out there quickly. So, what is the OATC opinion about this? Can we recommend specific wiki software? Would it be possible to spend some time setting something up, that will demonstrate how is could look? Jan Gregersen
...
Adrain has completed the first version of a tool that can take the OpenMIComplinanceInfo.xml file and transform it into readable HTML. This tool is intended to be used by the OATC in to take XML files submitted to the OpenMI Association and make convert them to HTML and then put these op the OpenMI web (the OpenMI compliant components page). I tried to make it work, but I did not have sufficient patience to make it work. Always a problem with command line programs that take a number of arguments and file paths. Since this tool is something that is going to be used only whenever someone submits a XML file to the OpenMI Association for approval, I think it would be very useful with a simple user interface. Otherwise you will forget how to work with it from time to time. I can see that one of the arguments is the path to the xsd file. Would it not be simpler to have a copy of this file at the same place as the OpenMIComplinceHTML.exe file, it is always the same XSD file that should be used anyway.
...