Issue 4238: The role name of the Namespace->ModelElement association end (mof-rtf)
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: 
Summary: Title: The role name of the Namespace->ModelElement association end should
be the same
than the corresponding reference name.
This role is named 'containedElement'  while the reference is named
'contents'. 
Even if this is legal, we should avoid this in the MOF model because it's
error prone (in particular
when we use the UML class diagram notation as a convenience for specifying
MOF compliant
metamodels).

Resolution: 
Revised Text: 
Actions taken:
March 27, 2001: received issue
Discussion: 

End of Annotations:=====
From: BELAUNDE Mariano FTRD/DTL/LAN
<mariano.belaunde@rd.francetelecom.fr>
To: "'Juergen Boldt'" <juergen@omg.org>
Subject: Two Ossues to the MOF 1.4 RTF
Date: Wed, 21 Mar 2001 13:25:05 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: IQPe9dE(e91"%!!>%Z!!

Juergen,

I would like to post the following two issues to the MOF 1.4 RTF.
Thanks in advance,

Mariano

----------------- ISSUE
Title: The role name of the Namespace->ModelElement association end
should
be the same
than the corresponding reference name.
This role is named 'containedElement'  while the reference is named
'contents'. 
Even if this is legal, we should avoid this in the MOF model because
it's
error prone (in particular
when we use the UML class diagram notation as a convenience for
specifying
MOF compliant
metamodels).