Issue 19772: Clarify Property Qualifiers with a full Example (uml2-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Clarification Severity: Minor Summary: Figure 11.37 has an example with presumably an Association for: Bank::persons : Person[*] {opposites Person::banks} Person::banks : Bank[*] {opposites Bank::persons} adding explicit names for clarity. The qualifier presumably adds a nested Property Bank::persons::accountNo : Person[?] specifying an important multiplicity and a possibly redundant type, although a qualified association might perhaps return a derived type. Where is it modeled that the qualifier itself is Integer[1] or perhaps String[3]? Presumably an opposite qualifier is required and this must form part of a refined Association. If this is indeed the case it needs a better example. If it not the case, the alternative solution needs an example. Resolution: Revised Text: Actions taken: June 2, 2015: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 02 Jun 2015 05:19:02 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: E.D Willink Employer: mailFrom: ed@willink.me.uk Terms_Agreement: I agree Specification: UML 2.5 Section: 11.5 FormalNumber: 13-09-05 Version: 2.5 Doc_Year: Year Doc_Month: Month Doc_Day: Day Page: 207 Title: Clarify Property Qualifiers with a full Example Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Remote Name: edwillink.plus.com Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Time: 05:18 AM Description: (JIRA won't let me Create this Issue) Figure 11.37 has an example with presumably an Association for: Bank::persons : Person[*] {opposites Person::banks} Person::banks : Bank[*] {opposites Bank::persons} adding explicit names for clarity. The qualifier presumably adds a nested Property Bank::persons::accountNo : Person[?] specifying an important multiplicity and a possibly redundant type, although a qualified association might perhaps return a derived type. Where is it modeled that the qualifier itself is Integer[1] or perhaps String[3]? Presumably an opposite qualifier is required and this must form part of a refined Association. If this is indeed the case it needs a better example. If it not the case, the alternative solution needs an example.