There should be a syntactical constraint to guarantee that every relationship stereotyped as «datatypeRelationship» that have a «structuredDatatype» in its source association end must have the meta-attribute isReadOnly = true in its target association end.

What steps will reproduce the problem?
1. Create a «structuredDatatype»;
2. Create a «simpleDatatype»;
3. Create a «datatypeRelationship» from the «structuredDatatype» to the 
«simpleDatatype»;
4. Verify the model.

What is the expected output? What do you see instead?
Despite the target association end having isReadOnly = false (by default), the 
editor does not shows a verification error. When creating a 
«datatypeRelationship» that have a «structuredDatatype» in its source 
association end, the editor should:
1. Automatically set the meta-attribute isReadOnly to true in the target 
association end;
2. Forbid the user to set the meta-attribute isReadOnly to false as long as the 
«datatypeRelationship» have a «structuredDatatype» in its source 
association end.

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

TheProjecter / ontouml

There should be a syntactical constraint to guarantee that every relationship stereotyped as «datatypeRelationship» that have a «structuredDatatype» in its source association end must have the meta-attribute isReadOnly = true in its target association end. #15