Issue 6107: Pin multiplicity (uml2-superstructure-ftf) Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov) Nature: Revision Severity: Significant Summary: What is the semantics of pin multiplicity? If it has no execution effect, then remove it. If it is the same as the multiplicity inherited from TypedElement, then use that. If multiplicity has the same semantics as bound, then multiplicity should be used instead of bound Resolution: See discussion and resolution to Issue 6090. Revised Text: Actions taken: August 30, 2003: received issue March 8, 2005: closed issue Discussion: End of Annotations:===== Name: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Nature: Revision Severity: Significant Subject: Pin multiplicity What is the semantics of pin multiplicity? If it has no execution effect, then remove it. If it is the same as the multiplicity inherited from TypedElement, then use that. If multiplicity has the same OMG Issue No: 6107 Title: Pin multiplicity Source: Kabira Technologies, Inc. (Mr. Conrad Bock, conrad.bock@nist.gov) Summary: What is the semantics of pin multiplicity? If it has no execution effect, then remove it. If it is the same as the multiplicity inherited from TypedElement, then use that. If multiplicity has the same semantics as bound, then multiplicity should be used instead of bound Discussion: See discussion and resolution in Issue 6090. Disposition: Resolved OMG Issue No: 6107 Title: Pin multiplicity Source: Kabira Technologies, Inc. (Mr. Conrad Bock, conrad.bock@nist.gov) Summary: What is the semantics of pin multiplicity? If it has no execution effect, then remove it. If it is the same as the multiplicity inherited from TypedElement, then use that. If multiplicity has the same semantics as bound, then multiplicity should be used instead of bound Discussion: See discussion and resolution to Issue 6090. Disposition: Resolved semantics as bound, then multiplicity should be used instead of bound.