oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

On Mon, 2009-10-05 at 23:45 +0900, Vanna wrote:
> Dear all,
> 
> 
> Please tell me what is the best way for a beginner to learn about
> MLHIM?

Hi Vanna,

Welcome to the OSHIP project.

Since you are already well versed in openEHR, you aren't a beginner in
MLHIM.  It's just a new acronym at this point.

In fact, it really hasn't been announced or anything yet.  But since
you've asked.....

As of yesterday the MLHIM project has come into being.  It is:
Multi-Level Healthcare Information Modeling
https://launchpad.net/mlhim and is an umbrella project for several
projects which OSHIP is one of them.

If you are one of the people that have been following the openEHR
mailing lists then you are well aware of the issues that are being
discussed concerning copyrights and licensing of things like archetype
(.adl) files and specifications.  There is a group of us, some of whom
have been working with these specifications for several years that are
getting very concerned that there is far too much commercial influence
inside the openEHR Foundation and we see the "openness" sliding away in
terms of software being produced/promoted by the foundation as well as
attempts to control how certain other artifacts are used and translated.

While the hope is that this is completely unnecessary.  A small group of
us decided to err on the side of caution and not allow the honest
efforts of hundreds of people to be taken over without any democratic
process.  We have established the MLHIM Community and exercised our
rights under the openEHR Free Commercial Use License as displayed on the
openEHR Foundation website at
http://www.openehr.org/download/copyright.html#dsy19-OE_Commercial as of
4 October, 2009 to copy the specifications and other text files.
Convert them to openly available and useful file formats (though the
process was ugly, took several hours of work already and they will still
require some cleanup work) and repost them under the Creative Commons –
Attribution 3. license found here
http://creativecommons.org/licenses/by/3.0/legalcode attribution is to
be given to the MLHIM Community and it is defined in the new documents
as:

The MLHIM Community is the group of persons and/or organizations that
participate in any manner as users or content creators within any of the
projects listed under the MLHIM Umbrella Project at
https://launchpad.net/mlhim

We are in our infancy in some ways but we are not naive. Our approach is
to be inclusive and democratic.  We need to develop governance policies
and we need to be certain that everyone understands that there are
licenses issues that we must adhere to.  

But, we are now free to discuss in public and make changes in democratic
ways.  We hope that we stay exactly in sync with openEHR.  But we will
not be held hostage to small groups of people that make proclamations
from behind closed doors on announcement lists.

I JUST received an email that our specifications email list has been
approved.  I ask you all to join us in moving forward in spreading this
technology into more languages and applications under the flags of
freedom and openness.  There are three more projects being launched
within the week under this umbrella as tools in this area.  But I'll
leave that for later.

https://launchpad.net/mlhim-specs

You will need to have a login on Launchpad and then request to join
MLHIM Specification Developers from the link above.

If anyone needs assistance navigating Launchpad please ask and I'd be
happy to help.


Sincerely,
Tim Cook

Attachment: signature.asc
Description: This is a digitally signed message part