Issue 19851: Inconsistency in constraints and rules for property merge (uml2-rtf) Source: (, ) Nature: Enhancement Severity: Significant Summary: The constraint #2 (i.e., The value of isUnique of matching Properties must be the same.) demands the values of isUnique for matching properties are the same, which is a prerequisite for merging, but the transformation rule #7 (i.e., For matching Properties: if either the merged and/or receiving elements have isUnique = false, the resulting element has isUnique = false; otherwise, the resulting element has isUnique = true.) ignores it. How to explain it? Resolution: Revised Text: Actions taken: November 5, 2015: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 05 Nov 2015 04:24:49 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Jingang Zhou Employer: Neusoft mailFrom: zhou-jg@neusoft.com Terms_Agreement: I agree Specification: OMG Unified Modeling Language Section: 12.2.3.6 FormalNumber: formal/2015-03-01 Version: 2.5 Doc_Year: 2015 Doc_Month: March Doc_Day: 01 Page: 244 Title: Inconsistency in constraints and rules for property merge Nature: Enhancement Severity: Significant CODE: 3TMw8 B1: Report Issue Remote Name: 124.93.222.115 Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36 Time: 04:24 AM Description: The constraint #2 (i.e., The value of isUnique of matching Properties must be the same.) demands the values of isUnique for matching properties are the same, which is a prerequisite for merging, but the transformation rule #7 (i.e., For matching Properties: if either the merged and/or receiving elements have isUnique = false, the resulting element has isUnique = false; otherwise, the resulting element has isUnique = true.) ignores it. How to explain it?