Open guidoni opened 3 years ago
So far we have only manipulate default cardinalities on associations, more specifically when the user applies a stereotype. This is because (i) the stereotype provides an ontological argument for us to suggest a default cardinality, and (ii) the "apply stereotype" action is an ease trigger to change the association.
In the case of attributes, I believe we should look for an ontological argument suggesting an "OntoUML-defined" default cardinality. Besides, Visual Paradigm allows users to set a default cardinality as a project/application wide setting.
Nonetheless, the default cardinality of attributes on the ontouml-js project is up for discussion.
When creating an attribute for a class when a model is built, the default value of the attribute is "N" (many). This means that the attributes are multivalued by default. Evaluate the possibility of the default value be "1" or "0..1".