Problem with specialization using the Archetype Editor
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
Problem with specialization using the Archetype Editor
Hi To specialise in the current AE, you open the parent and then File->specialise. Cheers, Sam -Original Message- From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Peter Gummer Sent: Friday, 11 January 2013 3:04 PM To: For openEHR technical discussions Subject: Re: Problem with specialization using the Archetype Editor 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.or g
Problem with specialization using the Archetype Editor
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. 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.) Peter
