Issue 4452: Predefined datatypes (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: The various datatypes that are the result of expressions are not
     defined in UML.  For example, there is no subtype of Datatype
     called Boolean. This means users will all define their own Boolean,
     Integer, etc., breaking interchangeability.

     The datatypes defined in the Datatypes packages are not model
     elements, so theoretically cannot be used in M1 models.  However,
     the interchange model for UML includes these types, making them
     available for user models.  If this is the case, it should be made
     clear in the UML spec.  The overview of the Datatypes package
     (section 2.7.1) says it contains types used in defining UML, so
     they formally belong to the MOF.

Resolution: 
Revised Text: UML 2.0 now defines Boolean etc - in the PrimitiveTypes package.
Actions taken:
August 3, 2001: received issue
March 9, 2005: closed issue
Discussion: 
The meta architecture of UML will be re-defined for UML 2.0 when UML and MOF will be properly aligned (RFP requirement). In this new context, this issue should beaddressed.

End of Annotations:=====
Reply-To: <conrad.bock@kabira.com>
From: "Conrad Bock" <conrad.bock@kabira.com>
To: <issues@omg.org>
Cc: "Cris Kobryn" <ckobryn@acm.org>
Subject: UML 1.5 issues
Date: Fri, 3 Aug 2001 08:57:48 -0700
Message-ID: <NDBBJCCGLKIFNFMGDBHNMECNDHAA.conrad.bock@kabira.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: Q?+e9Oe%!!h^(!!~DRd9


Juergen,

Here are my issues for UML 1.5.  These are submitted as comments on
the
UML 1.4 as specified in ad/2001-02-13.

Thanks,

Conrad

7) Predefined datatypes

     The various datatypes that are the result of expressions are not
     defined in UML.  For example, there is no subtype of Datatype
     called Boolean. This means users will all define their own
     Boolean,
     Integer, etc., breaking interchangeability.

     The datatypes defined in the Datatypes packages are not model
     elements, so theoretically cannot be used in M1 models.  However,
     the interchange model for UML includes these types, making them
     available for user models.  If this is the case, it should be
     made
     clear in the UML spec.  The overview of the Datatypes package
     (section 2.7.1) says it contains types used in defining UML, so
     they formally belong to the MOF.


     Nature: Revision
     Severity: Medium