For questions about this archive, please contact webmaster@hl7.org.
Luca Berardinelli (Mar 19 2019 at 15:46):Dear HL7 users, I am researcher/practitioner expert in Model-Driven Engineering (https://www.linkedin.com/in/lucaberardinelli/) (https://www.researchgate.net/profile/Luca_Berardinelli). I am playing with HL7. I started with RIM and I found that your are exporting it in XMI in the wrong way. It seems that the export step in UML is done via commercial tools like IBM Rational Rose that mixes open source de-facto standard (Ecore) with tool specific conventions. I strongly suggest to use Eclipse UML as a reference exporting format (.uml) which is compatible with many commercial tools and fully compatible with OMG standards (like UML. XMI, MOF and many others). Moreover, you are not exporting the UML profile in XMI. And the .xmi obtained at the end is useless. Do you plan to fix this issue? thanks
Lloyd McKenzie (Mar 19 2019 at 19:32):Short answer: no current plans to fix. The XMI representation has never been widely consumed and is not instrumental to HL7's internal processes. What's currently exposed is exposed on the basis that it was "relatively easy to do". There isn't an obvious return on revisiting that process, particularly given that most HL7 implementers aren't terribly focused on RIM-based standards at the moment (though we do continue to use the RIM internally). That doesn't mean that HL7 would necessarily object to spitting out the RIM in XMI in a manner that would be more conformant/useful, just that if it's needed, you should expect to have to do a lot of the work yourself to make that happen (or find others with a similar need who are willing to do the grunt work). If that's of interest to you, we can do a bit of digging and figure out how the XMI export is happening right now and point you at the code so you can work on making the needed adjustments. (Side note - I'm not stating official policy, merely expressing opinion as someone who's heavily involved with the work group responsible for RIM maintenance and who has a reasonable degree of familiarity with the tooling involved.)
Grahame Grieve (Mar 23 2019 at 06:35):what is the tooling involved?
Lloyd McKenzie (Mar 23 2019 at 20:10):I don't actually know. @Lynn Laakso?
Jean Duteau (Mar 24 2019 at 04:44):Woody used IBM Rational Rose.
Luca - along with the XMI export from Rational Rose that we provide, we also provide an Enterprise Architect file that you can use to export different flavours of XMI if you so wanted to.
Lynn Laakso (Mar 24 2019 at 13:54):Thanks @Jean Duteau I really would have no idea where to start right now. We haven't even balloted a RIM-based standard in a year so we haven't generated any RIM content for publication, even. The tooling is quite dusty
Grahame Grieve (Mar 24 2019 at 20:07):if we are actually using rational rose, it should be possible to also do a manual export to the ecore format?
Rene Spronk (Mar 25 2019 at 08:40):FYI - Nictiz maintains a full working stack of v3 tools because of their use of v3. Alexander Henket (not on this Zulip) should know more - in case it's ever needed.
Lloyd McKenzie (Mar 25 2019 at 13:24):Including for RIM maintenance?
Rene Spronk (Mar 27 2019 at 07:32):That's rather unlikely - they've picked one specific RIM version (and datatypes R1) as the basis for their v3 developments.
Last updated: Mar 23 2020 at 00:02 UTC