Problem with specialization using the Archetype Editor
Hi Peter! > Subject: Re: Problem with specialization using the Archetype Editor > From: peter.gummer at oceaninformatics.com > Date: Fri, 11 Jan 2013 12:38:51 +1100 > To: openehr-technical at lists.openehr.org > > pablo pazos wrote: > > > I'm testing archetype specialization using the AE, but I can't find a way > > to redefine a constraint of the parent archetype inside the specialized one. > > The problem is that the AE doesn't show the nodes of the parent archetype > > on the specialized one. > > > Hi Pablo, > > AE is currently still stuck on ADL 1.4, so it doesn't support differential > archetypes as defined in ADL 1.5. > > Therefore, when you work on a specialised archetype in AE, you will see the > parent's nodes only if they were copied from the parent archetype. This works > okay (more or less) as long as the specialised archetype was created when > work on the parent archetype had already been completed. On creating the > specialised archetype, everything is copied from the parent. Where it fails, > however, is that if there have been further modifications to the parent > archetype, after the specialised archetype was created, the new changes don't > magically appear in the specialised archetype: someone has to copy those > changes manually from the parent. > I think it would be better if the AE copies the parents nodes into the specialized archetype when the AE user clicks on "File > Specialize", of course, only when the ADL version is 1.4.Manual copying is error prone. What do you think? > This is a maintenance problem. Fixing this is one of the main benefits of ADL > 1.5. > > By the way, Pablo, I think you mentioned recently that you were still using > AE 2.2.779. There have been a lot of improvements to how AE handles > specialisation since then, so I recommend that you install the latest > release. (Although it won't fix problems intrinsic to ADL 1.4, of course.) > I have that update in my TODO list :) it is very kind of you to remember that, thank you. > Peter > ___ > 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/20130110/6c20ad48/attachment.html>
Problem with specialization using the Archetype Editor
Hi all! I'm testing archetype specialization using the AE, but I can't find a way to redefine a constraint of the parent archetype inside the specialized one.The problem is that the AE doesn't show the nodes of the parent archetype on the specialized one. Is this a bug or there is some functionality somewhere to redefine parent's constraints? Thanks! -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130110/4c376d2e/attachment.html>
csingleattribute and existence
Hi Bert, it always helps me to make correspondences between the AOM and UML class models (they are basically the same thing). If you look at this: http://www.openehr.org/wiki/download/attachments/196630/openehr_entry_uml.jpg?version=1&modificationDate=1193397393000You'll note the [0..1] and [1] on attributes, that's the "existence", and the "occurrence" is the cardinality on relationships (that's for relationships that are no collections, i.e. single_attributes) (e.g. 0..1 in the ACTION.instruction_details relationship with INSTRUCTION_DETAILS). Also, "CMultipleAttribute.cardinality" for collection attributes is the "cardinality" on UML relationships like "INSTRUCTION.activities" or "ENTRY.other_participations". Hope that helps. -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos > Date: Sun, 6 Jan 2013 16:51:00 +0100 > From: bert.verhees at rosa.nl > To: openehr-technical at lists.openehr.org > Subject: csingleattribute and existence > > Excuse me the following question, maybe I am just looking over the > answer all the time > > What is the use of both together existence and occurences in case of a > CSingleAtttribute. > > And what if both have conflicting information? > > For example, existence gives REQUIRED and occurrences gives minOccurs=0 > > Thanks for a short answer > > Bert > > ___ > 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/20130110/2f19ef1b/attachment.html>
