Hello,
Constrained Container RM-Types can define a "cardinality" for their list/array fields and the contained types can define "occurrences" for themselves inside the array.
The summed max-"occurrences" may never surpass the max-"cardinality and the summed min-"occurrences" may never be less than the min-"cardinality".
The min-max-"occurrences" could perhaps even be calculated from the "occurrences".
What information gain does the "cardinality" provide ?
Or what is the usecase where a given "cardinality" is needed, because the information is not already given by the all "occurrences" ?
Greetings
Georg
You can see cardinality as the size of the array that contains objects. For your examples:
- The summed max-“occurrences” may never surpass the max-“cardinality”
They might, specially as things like occurrences of 0..* or 1..* are a thing. Nothing wrong with having a cardinality that further constraints that.
- the summed min-“occurrences” may never be less than the min-“cardinality”
They also might, even if all your objects are optional (i.e. 0..1) you could have a cardinality of [1..*] to say that you need at least one.
However, I would say that in normal cases you could just sum them and be fine, but this duality allows for some cool tricks at validation time
Regards