The cardinality you mention only defines how many values the items attribute must have. In this case at least two.
Which values that are depends on the child elements/items and their occurrences attribute. If the occurrence of both of these is 1 exactly, they must both appear. If they both are 0..*, it can be two or more of the first, two or more of the second, or at least one but possibly more of both. More options are possible. If occurrences is not defined, in this case I think it defaults to 0..*. Regards, Pieter Bos Op 29 nov. 2018 10:31 schreef Georg Fette <[email protected]>: Hello, I have an archetype with a complex object derived of CLUSTER with "items cardinality matches {2..*; ordered}" and those two items are also defined inside the complex object. I understand the semantics of this definition that both items always have to appear together inside the cluster but the package of those two items may appear any number of times. Is it allowed for instances of this archetype to have an uneven number of items > 2 inside this cluster, because that would still suffice the restriction of having 2..* children. Or do the instances always have to have both elements as a package that are defined as items in this cluster. As I am not the author of the archetype I do not completely understand how the definition has to be interpreted. Greetings Georg -- --------------------------------------------------------------------- Dipl.-Inf. Georg Fette Raum: B001 Universität Würzburg Tel.: +49-(0)931-31-85516 Am Hubland Fax.: +49-(0)931-31-86732 97074 Würzburg mail: [email protected] --------------------------------------------------------------------- _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
