Dear David,
As you know, I consider your project OpenEMed as one
of the best out there. It is truely built on Object Technology
and a pure distribution of services.
Great, that CORBAmed is now being mentioned
more often in this discussion list to lead the right way.
I'd like to ask you some things yet:
1 Which relation is there between OpenEMed and the
TeleMed project? Can't they be melted into one?
2 I guess, you used the BSD license to allow commercial
users working with your code. Is there no way to convince
you to use the GPL?
3 I appreciate the work of you and your institute.
Just some time ago I found a license description of TeleMed
that requires to mention your University whenever using
code of your project. Is that fair when perhaps many other
developers around the globe will work with on your project?
4 I would like to see you as a leading architect giving advice
to many of our projects. How about taking the list of
possible CORBA modules (= packages = different programs)
and distribute that work to our projects?
One would do the PIDS (you), another project the
LexiconQueryService-LQS (Bud??) etc.
There are many members of this list using Script languages
who could provide web GUIs - besides your Swing clients.
Others are experienced in administrating databases (mostly ER).
Many would just like to do proper OO development in the core
using common Business Objects.
Some (such as I) like to bring systematics into all that,
analyse Frameworks and (Meta)Models, e.g. by using the UML.
So I suggest to do a document or better web page giving
an overview just as Thomas Beale wrote:
"...collaborative document - a sort of comparison table..."
Are we all on the way to unite?
David Forslund wrote:
> One point that might be of help here. If systems communicate
> through a well defined
> open interface, then I believe you could mix GPL and BSD type licenses
> since the codes
> would not have to be delivered together. For example, an application
> that uses DNS doesn't need
> to have a GPL version of DNS since it talks to it through an open
> API. This also is an avenue
> for open source systems to talk with vendor systems through an open
> API. This seems
> to me to be a viable approach which allows open source systems to
> promote interoperability
> without the source code licenses getting into the way.
>
> Dave
--
Kind regards from
Christian
www.resmedicinae.org
- Information in Medicine -
