There should be a syntactical constraint to guarantee that when a (meronymic) relationship is non-shareable, then the extremity connected to the whole must have a cardinality of exactly one.

What steps will reproduce the problem?
1. Create two classes, e.g., two «kind» classes;
2. Create a meronymic relationship between these classes, e.g., a 
«componentOf» relationship;
3. Set the meta-attribute isShareable of the «componentOf» relationship to 
false;
4. Set the lower and upper cardinality constraints in the extremity connected 
to the whole to numbers different from 1.

or

1. Create two classes, e.g., two «kind» classes;
2. Create a meronymic relationship between these classes, e.g., a 
«componentOf» relationship;
3. Set the lower and upper cardinality constraints in the extremity connected 
to the whole to numbers different from 1.
4. Set the meta-attribute isShareable of the «componentOf» relationship to 
false.

What is the expected output? What do you see instead?
The editor should forbid:
1. To alter the cardinalities of the extremity connected to the whole when 
isShareable is false;
2. To set isShareable to false when the cardinalities of the extremity 
connected to the whole are different from 1.

Original issue reported on code.google.com by alessand...@gmail.com on 8 Nov 2010 at 11:13

TheProjecter / ontouml

There should be a syntactical constraint to guarantee that when a (meronymic) relationship is non-shareable, then the extremity connected to the whole must have a cardinality of exactly one. #13