Issue 9339: consistent ordering of Association::memberEnd and ownedEnd (uml2-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: Given that these are both {ordered}, indicating that ordering is important, then it seems only sensible that the ordering should be consistent, i.e. if Property p appears before Property q in memberEnd then that should also be the case for ownedEnd. There should therefore be a constraint added to this effect. There should probably also be a review of other cases where an ordered Property subsets another ordered property. Or should there be a more general constraint defined at the meta-level? Resolution: Revised Text: Actions taken: January 31, 2006: received issue Discussion: End of Annotations:===== ubject: UML2 Issue: consistent ordering of Association::memberEnd and ownedEnd Date: Tue, 31 Jan 2006 10:00:11 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: UML2 Issue: consistent ordering of Association::memberEnd and ownedEnd Thread-Index: AcYmkC3IaFClpLaHQcu8Wqy4AImR5Q== From: "Pete Rivett" To: Given that these are both {ordered}, indicating that ordering is important, then it seems only sensible that the ordering should be consistent, i.e. if Property p appears before Property q in memberEnd then that should also be the case for ownedEnd. There should therefore be a constraint added to this effect. There should probably also be a review of other cases where an ordered Property subsets another ordered property. Or should there be a more general constraint defined at the meta-level? Pete Rivett (mailto:pete.rivett@adaptive.com) CTO, Adaptive Inc. Hello House, 135 Somerford Road, Christchurch, BH23 3PY, UK Tel: +44 (0)1202 491243 Fax: +44 (0)1202 491241 http://www.adaptive.com