mlhim-owners team mailing list archive

[Luciana Tricai Cavalini <lutricav@xxxxxxxxx>]

Hello Tim and the MLHIM community,

Em 29/01/2011 16:25, Tim Cook escreveu:
> > Hi Everyone,
> >
> > There have been several discussions in the past re:modelling tools.
> >
> > Within the collaboration community of MLHIM there is a good deal of use
> > from the EMF tools.  These tools can provide us with Java code
> > generation, XSD Generation and UML generation.  I believe we can get
> > some productivity from using the Eclipse Modelling Framework (EMF).

I understand that this approach will bring us closer to the Java
developers' community, right? That's highly desirable, since that
enables them to build Java-and-MLHIM-based applications.

> >
> > I have code created branches for both the MLHIM 1.x (openEHR 1.0.2)
> > specifications as well as the new  MLHIM 2.x specifications.  We need
> > both of these completed soon.

I understand that the MLHIM 1.x specifications will remain the way they
are right now, right?

  Since I am working on the initial draft
> > of MLHIM 2.x so we can begin open discussions.

OK, so I want to make a statement: I think it is highly desirable
for the MLHIM Project (at least the part that I coordinate, inside
INCT-MACC) to move to MLHIM 2.x right now.
For instance: with Tim's support, two days ago I was able to migrate a
simple openEHR archetype from the ADL to the XMind format and it was fun
and made much more sense for an epidemiologist with a bare shallow
understanding of the RM. And then today I started teaching that for my
undergrad granters and MSc students and it was a success. It raised a
lot of questions and some of them became "rebels" because they don't
understand why the RM is so complex, "because with Google Forms we make
forms so fast", but then I had a moment to connect to the first
theoretical half of the course and then they had that "aaaaaw" moment.
That's *excatly* what we need IMO. The specs only need to be developed
once, so do the RM implementations in each language. So, still IMO, the
tools need to be comprehensive enough to enable common mortals to start
modelling the knowledge on CCDs soon, and the same for application
developers (aka OSHIP users): the more "plugable" to any development
platform the implementations are, the better, because that will take the
application platforms out of the way from the RM implementation to the
application development.

Cheers,

Luciana.


  I believe it would be
> > helpful for those of you wanting to get familiar with Eclipse and the
> > EMF to go ahead with work on the MLHIM 1.x model based on the openEHR
> > 1.0.2 specs.  The branch is named mlhim-openehr-emf
> >
> >
https://code.launchpad.net/~mlhim-specs-dev/mlhim-specs/mlhim-openehr-emf
> >
> > I created a subdirectory of the Eclipse 'workplace' directory called
> > mlhim-openehr for the bzr branch.
> >
> > You will need to install Eclipse with the EMF framework and the ECore
> > tools.  You should also install the BZR plugin for Eclipse
> >
> > http://wiki.bazaar.canonical.com/BzrEclipse/Installation
> >
> > You can also use Eclipse as a Python IDE with the PyDev plugin.  Ihave
> > been a longtime user of WingIDE but I see a real usefulness in having
> > the same sandbox to do all of my playing in. :-)
> >
> >
http://plone.org/documentation/kb/developing-plone-with-eclipse/installing-eclipse
> >
> > Let me know if you want to help and need write access to the branch.
> >
> > Cheers,
> > Tim
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~mlhim-owners
> > Post to     : mlhim-owners@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~mlhim-owners
> > More help   : https://help.launchpad.net/ListHelp

-- 
Esta mensagem foi verificada pelo sistema de antivírus e
 acredita-se estar livre de perigo.