Issue 18163: Node::nestedNode should subset Class::nestedClassifier, not Namespace::ownedMember. (uml25-ftf)
Source: Microsoft (Mr. Steve Cook, stcook(at)microsoft.com)
Nature: Uncategorized Issue
Severity: 
Summary: The way it is modeled now, a Node’s nested nodes will not appear in its nestedClassifier property, which must be wrong.


Resolution: 
Revised Text: 
Actions taken:
October 10, 2012: received issue
Discussion: 

End of Annotations:=====

m: Steve Cook <Steve.Cook@microsoft.com>
To: "issues@omg.org" <issues@omg.org>
Subject: UML2.5 FTF Issues
Thread-Topic: UML2.5 FTF Issues
Thread-Index: Ac2m5nUzjEGXWuQlRD6a4DoFF3CPng==
Date: Wed, 10 Oct 2012 12:57:10 +0000
Accept-Language: en-GB, en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.166.18.105]
X-Forefront-Antispam-Report: 
 CIP:131.107.125.37;CTRY:US;IPV:CAL;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(74502001)(47976001)(20776001)(16826001)(44976002)(16406001)(1076001)(16696001)(15202345001)(47736001)(51856001)(42186003)(3846001)(31966008)(49866001)(5343655001)(4196001)(46102001)(8716001)(4396001)(33656001)(74662001)(512954001)(47446002)(306001)(50986001)(5343635001)(316001)(3556001)(3746001);DIR:OUT;LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0630013541


Issue title: Node::nestedNode should subset Class::nestedClassifier, not Namespace::ownedMember.

                                                                                                                                                                                                 

The way it is modeled now, a Node.s nested nodes will not appear in its nestedClassifier property, which must be wrong.

 

-- Steve