Issue 6929: UML 2 Super / Classes / Properties owned by properties (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: It seems that the lower bound of Feature::featuringClassifier should perhaps be 0 (not 1) to allow for the situation in which a Property is owned not by a class, association, or data type, but another property (as one of its qualifiers) Resolution: see above Revised Text: Actions taken: January 26, 2004: received issue March 8, 2005: closed issue Discussion: Indeed, figure the metamodel fragment shown in Fig. 66, shows that a Property can own another Property. Since Property is a kind of Feature, it is necessary to loosen the multiplicity shown in figure 28 from 1..* to 0..*. The following changes are required: Superstructure specification fixes: ?? In figure 28 on page 71, change the multiplicity of Feature::featuringClassifier from 1..* to 0..* ?? In the Associations subsection of section 7.9.2 (Feature) for the “featuringClassifier” entry, change the multiplicity fro 1..* to 0..* Infrastructure specification fixes: ?? In figure 18 on page 45, change the multiplicit y of Feature::featruingClassifier from 1..* to 0..* ?? End of Annotations:===== ubject: UML 2 Super / Classes / Properties owned by properties X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Mon, 26 Jan 2004 15:27:39 -0500 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 01/26/2004 15:27:41, Serialize complete at 01/26/2004 15:27:41 It seems that the lower bound of Feature::featuringClassifier should perhaps be 0 (not 1) to allow for the situation in which a Property is owned not by a class, association, or data type, but another property (as one of its qualifiers) Bran Selic Distinguished Engineer IBM Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 OMG Issue No: 6929 Title: UML 2 Super / Classes / Properties owned by properties Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Summary: It seems that the lower bound of Feature::featuringClassifier should perhaps be 0 (not 1) to allow for the situation in which a Property is owned not by a class, association, or data type, but another property (as one of its qualifiers) Discussion: Indeed, figure the metamodel fragment shown in Fig. 66, shows that a Property can own another Property. Since Property is a kind of Feature, it is necessary to loosen the multiplicity shown in figure 28 from 1..* to 0..*. The following changes are required: Superstructure specification fixes: · In figure 28 on page 71, change the multiplicity of Feature::featuringClassifier from 1..* to 0..* · In the Associations subsection of section 7.9.2 (Feature) for the .featuringClassifier. entry, change the multiplicity fro 1..* to 0..* Infrastructure specification fixes: · In figure 18 on page 45, change the multiplicity of Feature::featruingClassifier from 1..* to 0..* · Disposition: Resolved e-mail: bselic@ca.ibm.com