Please correct me if I am wrong,

Please take it as a request for information, or if I am wrong and need 
to be corrected, as a discussion.

I will do a few statements about what I have seen around the openehr-website

- The folder in the RC 1 for ITS is a bit empty. No 
database-definitions, no languages specific information, no 
distribution-formalism.
As the roadmap-document explains, this will be taken care of, but has 
not yet happened.

- Although there is a lot of Java-code, but it represents a previous 
version, and there is no guaranteed effort that it will be up to date 
with the official Openehr-Eiffel-code.
It can be used as is, but for own risk for missing the project developments.

- One can say, the Eiffel-code, as Thomas states somewhere, is the 
case-tool, it represents the formal state of work/definitions.
One can create dotnet-libraries with it, which is already done. I can 
load them in my Visual Studio and Delphi.NET. But I have no way of 
checking if there is something happening behind the 
interface-properties, or if they are just there as placeholders for 
later use. My knowledge of Eiffel is really not enough for judging the 
source-files.
This is a confusing and maybe conflicting situation.
Because the code is at the same time case-tool storage, it serves two 
purposes, which can for an outsider be confusing.
In a case-tool there is no need to write code behind the properties of a 
class, one does not want to do that because code-writing is another kind 
of job then software-architecture. A case-tool is a tool for an 
architect, a designer, not for a programmer, although those two 
professions can come together in one person, an outsider can never be 
sure who was talking here behid this particular property or method.

- There are no example implementations of a complete openehr-system on 
this website, does this mean that there are no open source implementations?
Only parts can be found, which are interesting pieces of work, but the 
things do not come together now.

- Are there any known closed source implementations which run fine?
- Can the experienced programmers be hired?
- why is the ITS and knowledge coming from the closed source-projects 
not returned to the project? "Give and Take" is the idea of open source 
which I like.

This are very important things for me to realize, because it means, if I 
am right, there is no way now to implement openehr in a live application 
open source or commercial for low cost..
Building an implementation at this stage means one has to rebuild the 
complete system, and in this way contribute to the ITS-part of the specs.
Maybe a tool can be build which generates C# and Java from Eiffel-code, 
but for now, that is not the case. Keeping up with the formal 
definitions is a matter of re-typing the sources and guarding the 
developments very well. When this is true, it is, sadly, not suitable 
for the project I am thinking of. There is not a lot of money to help 
build a system on a uncertain and lengthly time-schedule.
In this way, if I am right the promise of a low maintenance EPD is not 
yet forfilled.

But the possibilty exist then I am really missing important parts which 
prove that I am very (or a bit) wrong, and it is very well possible at 
this moment to build a low cost implementation for a project which has 
to be up and running in a few months. If this is the case, I can donate 
my thinkings and workings back to the project. Code written in other 
languages, db-schema's, interface-schemas, etc.

Please comment to this!!

Next monday I have to report on my findings

Thanks
Bert Verhees

Reply via email to