Hi Peter, I've uploaded here a set of screenshots explaining what I've done. You'll see in the 3rd image the "weird" ADL. This was an empty copy of the parent (1st & 2nd images), it doesn't had any nodes on the ACTIVITY description and I added one ELEMENT. Trying to reproduce the same behaviour on the Archetype Editor, I got another structure and cannot reproduce the first "weird" specialization (4th image). Here are the screenshots:https://plus.google.com/109540968085207927247/posts/er5QzBkc5Mt
Just for clarification: * I'm using AE 2.2.779* In all cases I do: File > Specialize when editing the parent archetype (images 1 & 2)* I asked for this " 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" because of what I got the first time I specialize the parent (image 3). About validation, it takes a lot of time to do something manually, then validate - fix - validate - fix again ... that time could be saved using just the AE. BTW: I found a possible bug when editing scpeialized archetype on image 4, if I put a constraint occurrences 0..0 on the DV_QUANTITY node, the ADL still says 0..1. I'll update my AE to the new version to see if this still happen. Just a question about specialization: is there a specialization level constraint? the AE doesn't allow to make an specialization from an specialization (3rd level of specialization). Thanks a lot! -- Kind regards, Ing. Pablo Pazos Guti?rrez www.cabolabs.com > Subject: Re: Problem with specialization using the Archetype Editor > From: peter.gummer at oceaninformatics.com > Date: Fri, 11 Jan 2013 16:33:32 +1100 > To: openehr-technical at lists.openehr.org > > pablo pazos wrote: > > > 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? > > > I'm not sure, but I think that when you upload a specialised archetype to CKM > it validates it against the parent. You can also use ADL Workbench to > validate it. > > Nonetheless, that's a nice suggestion, Pablo. It would need to be a new menu > item, since "File | Specialise" already does something (i.e., it creates a > specialisation of the specialisation). Maybe "File | Update Specialisation"? > > It would take a while to implement something like that, however, because we'd > have to make sure it handled everything properly. Even then, I'm sure that > corner cases would remain where the specialised archetypes got out of step. > > ADL 1.5 is the only real solution. I'd rather put that effort into moving to > ADL 1.5. > > 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/20130116/0a6a8378/attachment.html>
