-
Key: UML25-405
-
Legacy Issue Number: 18034
-
Status: closed
-
Source: Delligatti Associates, LLC ( Mr. Lenny Delligatti)
-
Summary:
his clause states, “A lost Message is a Message where the sending event occurrence is known, but there is no receiving event occurrence. We interpret this to be because the Message never reached its destination.”
The semantics described in the second sentence seem unnecessarily strict. Additionally, this interpretation for a lost Message is inconsistent with the interpretation of a found Message described in the next paragraph: “We interpret this to be because the origin of the [found] Message is outside the scope of the description.” The semantics of a lost Message should be similar.Proposed Resolution:
Change the second sentence in the excerpt to read: “We interpret this to be because the destination of the [lost] Message is outside the scope of the description.”
-
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
Change the second sentence in the excerpt to read: “We interpret this to be because the destination of the
[lost] Message is outside the scope of the description.”. -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location: Pg. 615, Figure 17.4.3: Semantics, Sub-clause: Messages
- Key: UML25-405
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF