Issue 18185: UML association semantics vis-a-vis Interfaces (and other types of classifiers) (uml25-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: The semantics of associations are specified in terms of links, which the UML 2.4 spec defines as: "a tuple with one value for each end of the association, where each value is an instance of the type of the end" and the 2.5 spec as "a tuple with one value for each memberEnd of the Association, where each value is an instance of the type of the end". However, the specs include several examples of associations between interfaces. Since interfaces are abstract classifiers they cannot have instances ("Interfaces may not be instantiated"), the semantics of associations whose ends terminate on interfaces cannot be described by the above semantics. Some other semantics need to be provided for such cases. Furthermore, the issue extends to other types of classifiers (e.g., collaborations) where the meaning of "instance" is not straightforward. Resolution: Revised Text: Actions taken: October 19, 2012: received issue Discussion: End of Annotations:===== M-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=+o+pacwmz7UMygxtafPGnHaNUjtIiTnlvoq48T6idqc=; b=sPMYs8ufjpI2JV6bydOrIwxEjrjysliz2msZjAh44A80tThIj+PQEQOnOveL5jet3G 3EWJnKnHUiPy5Bejy1hP5XzCtP2ybmOLfXYS2WZqHd4c0av+ui5zRYudWP59xkA1T5w+ FNNOOHU8JpBnvHfnD0k6QGX+h1A8mGsENJybWCy28j5bWPEVtDUy//zp9nY+5wVuqMTn UwIRjXULxTvyh2LDwUldajca+jXn2hkKdhL8Z83FyZkRUnxryVMbrPoiyeWVbDGMQGPz 1TJ6Ub5KWWfKhDKj3EvPb5kCknSXF1XAduzWEQJ9zzBU67vAH8SiwQRxz72TWnpTCaVJ jf/Q== Sender: bran.selic@gmail.com From: Bran Selic Date: Fri, 19 Oct 2012 14:29:29 -0400 X-Google-Sender-Auth: 3_ZraKJ6yHkTV7Cv_KdJbxNKMjM Subject: UML association semantics vis-a-vis Interfaces (and other types of classifiers) To: issues@omg.org Cc: Juergen Boldt The semantics of associations are specified in terms of links, which the UML 2.4 spec defines as: "a tuple with one value for each end of the association, where each value is an instance of the type of the end" and the 2.5 spec as "a tuple with one value for each memberEnd of the Association, where each value is an instance of the type of the end". However, the specs include several examples of associations between interfaces. Since interfaces are abstract classifiers they cannot have instances ("Interfaces may not be instantiated"), the semantics of associations whose ends terminate on interfaces cannot be described by the above semantics. Some other semantics need to be provided for such cases. Furthermore, the issue extends to other types of classifiers (e.g., collaborations) where the meaning of "instance" is not straightforward.