Issue 12274: new constraint ? (uml2-rtf) Source: Eclipse Foundation (Mr. Kenneth Hussey, kenn.hussey(at)gmail.com) Nature: Uncategorized Issue Severity: Summary: Should there be a constraint ensuring that named elements with private visibility cannot be accessed outside their owning namespace? For example, the type of a property should not be a private member of a namespace outside of its namespace hierarchy… Resolution: Revised Text: Actions taken: March 11, 2008: received issue Discussion: End of Annotations:===== ubject: UML RTF Issue Date: Tue, 11 Mar 2008 23:16:14 -0400 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: UML RTF Issue Thread-Index: AciD7228RD0YqBstRuSfi8IDEJCPrA== From: "Kenn Hussey" To: X-OriginalArrivalTime: 12 Mar 2008 03:16:14.0606 (UTC) FILETIME=[6E014AE0:01C883EF] X-TM-AS-Product-Ver: SMEX-7.0.0.1345-5.0.1023-15780.002 X-TM-AS-Result: No--19.991000-8.000000-31 Should there be a constraint ensuring that named elements with private visibility cannot be accessed outside their owning namespace? For example, the type of a property should not be a private member of a namespace outside of its namespace hierarchy. Kenn Hussey Program Manager, EA/Studio Embarcadero Technologies, Inc. | www.embarcadero.com 110 Spadina Avenue, Suite 400 | Toronto, ON M5V 2K4 Kenn.Hussey@embarcadero.com Mobile: 613-301-9105 CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.