Issue 9012: Section: Classes (uml2-rtf)
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Minor
Summary: Associations can have static ends, but this violates the semantics of static (that they are properties of the class or subclasses, not instances). If we are following programming languages, the semantics of isStatic should be that it is properties of instances, but is the same on all instances. The current semantics would be the right one if isStatic identifies "metaproperties". 

Resolution: 
Revised Text: 
Actions taken:
September 25, 2005: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 25 Sep 2005 11:20:07 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Notification: No
Specification: UML 2 Superstructure
Section: Classes
FormalNumber: ptc/04-10-02
Version: 
RevisionDate: 
Page: 
Nature: Revision
Severity: Minor
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Description
Associations can have static ends, but this violates the semantics of static (that they are properties of the class or subclasses, not instances). If we are following programming languages, the semantics of isStatic should be that it is properties of instances, but is the same on all instances. The current semantics would be the right one if isStatic identifies "metaproperties".