[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdht-dev] core features
|
Hi Sean,
I thought that I already moved all the terminology plugins from core to cda a few weeks ago, or maybe only moved the the plugins out of Uml feature into CDA feature for build. In any case, yes I agree. We need a complete overhaul of terminology modeling and binding for FHIR.
The original intent of org.elipse.mdht plugin was to define general workbench config, e.g. The MDHT perspective and generic top-level menus and preference page. It was never fully fleshed out or completed.
Dave
On Tuesday, April 26, 2016,
sean.muir@xxxxxxxxxxxxxxx <
sean.muir@xxxxxxxxxxxxxxx> wrote:
Dave
We currently have to features within core - I believe the original breakdown was to support general UML editing (table editor)
and the second feature supports terminology which was anticipated to support a broad range of constraint models
org.eclipse.mdht and org.eclipse.mdht.uml
the org.eclipse.mdht features includes the org.eclipse.mdht.uml
Are we using any of the original term.core etc in fhir (i did not think so)
does it make sense to deprecate org.eclipse.mdht and move the term to cda ?
Thanks
Sean
the breakdown of plugins for org.eclipse.mdht.uml
<plugin id="org.eclipse.mdht.emf.runtime"
<plugin id="org.eclipse.mdht.transform.core"
<plugin id="org.eclipse.mdht.uml.common"
<plugin id="org.eclipse.mdht.uml.common.ui"
<plugin id="org.eclipse.mdht.uml.edit"
<plugin id="org.eclipse.mdht.uml.transform"
<plugin id="org.eclipse.mdht.uml.transform.ui"
<plugin id="org.eclipse.mdht.uml.ui"
<plugin id="org.eclipse.mdht.uml.ui.navigator"
<plugin id="org.eclipse.mdht.uml.ui.properties"
<plugin id="org.eclipse.mdht.uml.validation"
the breakdown of plugins for org.eclipse.mdht
<plugin id="org.eclipse.mdht.uml.term.core"
<plugin id="org.eclipse.mdht.uml.term.transform"
<plugin id="org.eclipse.mdht.uml.term.ui"
<plugin id="org.eclipse.mdht.uml.ui.ide"
--
Thank you,
Dave Carlson, Ph.D.
mobile: 406-253-3055
email: dcarlson@xxxxxxxxxxxxxxx
Clinical Cloud Solutions LLC, healthcare on HL7 FHIR
