Yep XMI is tough... A short time ago I thought about adapting the .DIA * XML format to represent UML diagrams (cleaning the graphic part and leaving only the structure of the model). My idea was to do some code generation targeting Java/Groovy from the DIA diagrams directly to simplify my development process. This can be easily done using something like FreeMarker **. The problems are: 1. .DIA is not a standard and is more for graphical information than information structures and 2. there is no clear standard to represent UML class models in XML. E.g. this can be used to generate reference implementations of any openEHR spec targeting multiple programming languages, so when specs change, we can generate our implementations automatically. Obviously this strongly depends on the tools used to create UML diagrams, and I suspect the tools currently used are propietary as the current tools/formats for spec documentation. * DIA is an open source UML modeller I use a lot, and it's output format is XML: https://live.gnome.org/Dia** http://freemarker.sourceforge.net
-- Kind regards, Ing. Pablo Pazos Guti?rrez http://cabolabs.com > From: yampeku at gmail.com > Date: Wed, 1 May 2013 16:02:21 +0200 > Subject: Re: About openEHR BMM > To: openehr-technical at lists.openehr.org > > We don't. I had a look to XMI back in the day, but discarded it for > being a mess (too vendor specific). On the other hand generating a > clean XMI from archetypes could be a good idea. > > 2013/5/1 pablo pazos <pazospablo at hotmail.com>: > > Hi Thomas, having a small spec would be great, thanks! > > > > BTW, does anyone use XML representation of UML diagrams to process class > > models? > > > > > > -- > > Kind regards, > > Ing. Pablo Pazos Guti?rrez > > http://cabolabs.com > > > >> Date: Tue, 30 Apr 2013 19:09:15 +0100 > >> From: thomas.beale at oceaninformatics.com > >> To: openehr-technical at lists.openehr.org > >> Subject: Re: About openEHR BMM > > > >> > >> On 30/04/2013 18:30, Diego Bosc? wrote: > >> > I think Thomas created it from scratch. There is a page on the wiki > >> > discussing it > >> > (http://www.openehr.org/wiki/display/dev/Machine-readable+model+representations+of+openEHR), > >> > but we studied mostly to the bmm files included on the archetype > >> > workbench in order to understand it. > >> > >> yep. That link explains why I did it. Simple summary: XMI is a horror > >> and hardly works between tools that implement it (and there is no hope > >> of hand-writing an XMI schema). And Ecore was broken for generic types. > >> We might converge to some Ecore/EMF format at some point, but right now, > >> BMM is a nice lightweight format, and works ok. > >> > >> Michael van der Zel at Results4Care put together a great little plug-in > >> for Enterprise Architect that traverses a UML model in memory and pumps > >> out a BMM schema for it. So now we have a nice way of having a primary > >> UML model expression and a generated tool-consumable format (BMM > >> schemas), which will help tool chains components to communicate - right > >> now the ADL workbench and now LinkEHR can consume it. > >> > >> The converter is pretty good right now, but David Moner's group has > >> obviously found a few more bugs than I found, which is good - hopefully > >> we can converge on a very tight version of the EA converter soon. Then > >> the same thing can be done with openEHR, 13606, any other model in EA, > >> which means we have a way of representing a RM in UML, and driving > >> archetype tools from that. > >> > >> I'm just putting together a GitHub repo now for it on which I'll post a > >> spec, the class models I use (in UML) and pointers to every > >> implementation we can find. > >> > >> - thomas > >> > >> > >> _______________________________________________ > >> openEHR-technical mailing list > >> openEHR-technical at lists.openehr.org > >> > >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130501/a77bf7da/attachment.html>
