Either-or modeling #140
ASL-rmarshall
started this conversation in
Ideas
Replies: 2 comments
-
Need to move this into a Discussion, as this PBI cannot be completed independently. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@ASL-rmarshall @bhavinbusa I converted issue #17 into Discussion #140 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are several places in the model where it would be beneficial to specify that an attribute can be one of a choice of classes. Examples include:
At the moment, the first two examples are implemented simply as two different attributes, only one of which is expected to be used. However, there is currently nothing in the model to constrain the use of the attributes. The third example is currently implement as a multi-value list, which nothing in the model to constrain the number of values depending on the comparator.
Need to determine whether modeling of these types of constraint is needed and, if so, how should it be implemented.
Beta Was this translation helpful? Give feedback.
All reactions