Re: ADL specification question

I might just add that I am not aware of experienced clinical modellers ever making use of cardinality constraints. It has just proven too hard for people to get their head around, even when there are some potential uses e.g expressing an XSD-type 'choice'. There was also a known feature of the ori

Re: ADL specification question

Hi Georg, the other answers are right, but for reference you may want to read the relevant part of the ADL specification (ADL2 version ; ADL1.4 version

Re: ADL specification question

As Pieter said, default occurrences (if not stated) are 0..* So if the attribute is ordered, this means that if the object appears, it has to be in that specific order, in your case at0002, at0002...at0003, at0003 Cardinality tells you how many of these are valid, so minimum 2. Take into account th

Re: ADL specification question

Hi Diego, The items inside the CLUSTER look like this: CLUSTER[at0001] matches { items cardinality matches {2..*; ordered} matches { ELEMENT[at0002] matches { value matches { DV_COUNT matches {*} }

Re: ADL specification question

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

Re: ADL specification question

Hello Georg, What (and how many) objects you have inside the items attribute? Think the cardinality as the "vector" capacity, and inside you can put them in order (depending on their occurrences, they may even not appear at all) Regards El jue., 29 nov. 2018 10:31, Georg Fette escribió: > Hell

ADL specification question

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