Issue 8472: Section: Activities (uml2-rtf) Source: International Business Machines (Mr. Jim Amsden, jamsden(at)us.ibm.com) Nature: Revision Severity: Minor Summary: Object node should be a multiplicity element, and use multiplicity upper for upperbound Resolution: Though seemingly small, this would actually be a significant change to the metamodel for activities and it would fundamentally change the current semantics for multiplicity of pins, which now only effect the execution of actions. If object node in general were made a multiplicity element, one would not only have to reconcile the current semantics of object node upper bound with the semantics of the multiplicity upper bound of a pin, one would also need to consider what the general semantics are for the multiplicity lower bound of an object node. This issue is thus considered strategic and out of scope for an RTF. Revised Text: None Disposition: Closed Out of Scope Revised Text: Actions taken: March 6, 2005: received issue April 26, 2010: closed issue April 26, 2010: closed issue Discussion: Due to lack of time, the RTF/FTF agrees that the following are problems that need fixing, but decided to defer their resolution to a future RTF working on this specification. End of Annotations:===== m: webmaster@omg.org Date: 06 Mar 2005 10:08:57 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jim Amsden Company: IBM mailFrom: jamsden@us.ibm.com Notification: No Specification: UML 2 Superstructure Section: Activities 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 Object node should be a multiplicity element, and use multiplicity upper for upperbound.