Issue 3448: MOF 1.3 Package should subtype Classifier (mof-rtf)
Source: Escape Velocity (Mr. Don Baisley, donbaisley(at)live.com)
Nature: Uncategorized Issue
Severity: 
Summary: In the MOF 1.3 Specification, a Package is not a subtype of Classifier.  But
an M2 package does have M1 instances (package extent objects), and the M2
Package defines the type of those M1 objects.  Therefore, a Package really
is a Classifier.  It is a type.  It can be thought of as a component type,
and in that sense a Package should be able to contain behavioral features.
Also, an attribute type that is a Package should be treated as a pointer to
a package extent object.

Recommendation:  make Package a subtype of Classifier, or fold Classifier
into GeneralizableElement.

Resolution: 
Revised Text: 
Actions taken:
March 22, 2000: received issue
Discussion: 

End of Annotations:=====
From: "Baisley, Donald E" <Donald.Baisley@unisys.com>
To: issues@omg.org
Subject: MOF 1.3 Package should subtype Classifier
Date: Wed, 22 Mar 2000 19:02:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-UIDL: ,)%!!oT/e9'Of!!V),e9

In the MOF 1.3 Specification, a Package is not a subtype of
Classifier.  But
an M2 package does have M1 instances (package extent objects), and the
M2
Package defines the type of those M1 objects.  Therefore, a Package
really
is a Classifier.  It is a type.  It can be thought of as a component
type,
and in that sense a Package should be able to contain behavioral
features.
Also, an attribute type that is a Package should be treated as a
pointer to
a package extent object.

Recommendation:  make Package a subtype of Classifier, or fold
Classifier
into GeneralizableElement.
 
Don Baisley
Unisys