Hi Moretti, I noted similar problems and discussed with Tom. He suggested that we create a PR. Here is another problem:
AE allows in specialisation setting occurrences higher than defined in parent (with ELEMENT I have tested). So do you want to go ahead and raise the PR issue? Cheers, -koray -----Original Message----- From: openehr-technical-bounces at openehr.org [mailto:[email protected]] On Behalf Of Moretti Leonardo Sent: Wednesday, 19 May 2010 11:26 p.m. To: openehr-technical at openehr.org Subject: Specialisation of archetype - Some doubts When we specialize an archetype, we must keep in mind some rules as: - a specialised archetype can only further narrow existing constraints in the parent (but it may add its own) - constraints are inherited, and can be overridden - overrides are ?covariant?, i.e. the constraints are narrower than the parent, also can be thought of as ?subsumed? - new constraints can be added where allowed by the parent archetype and reference model Using Archetype Editor I noted some strange behaviours, and I don't understand if they are bugs or a my misunderstanding of specs: 1) I can modify an inherited constraint (changing the text on term_definitions, the occurrences or the cardinality) without specialize the constraint (the archetype node id is the same of the parent archetype).. I thought we should specialize a constraint to modify it! 2) when we specialize a cluster with max occurrences > 1, a new constraint is created and all children are deleted (why?) 3) can we delete an inherited constraint? if this is an Element we can do it with Archetype Editor, specializing it and the deleting it. This is not possible for Cluster Many thanks in advance for any comments. Best regards, leo _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
