Issue 6151: Diamond notation for merge junctions (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: Merge junctions should have a diamond notation option, for readability
and backward compatibility
Resolution: 
Revised Text: 
Actions taken:
August 30, 2003: received issue
March 9, 2005: closed issue
Discussion: 
Merge junctions have been introduced in UML1.5 in the context of activity-graphs. There
is no reason to include this notation for statemachines as the concept of merge junctions
as such does not exist there nor it is used in that context.
Disposition: Closed, no change.
End of Annotations:=====
Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Nature: Revision
Severity: Significant
Subject: Diamond notation for merge junctions


Merge junctions should have a diamond notation option, for readability
UML 2.0 Superstructure FTF
Resolution proposals for Statemachines 
OMG Issue 6151
Title: Diamond notation for merge junctions 
Source: NIST (Mr. Conrad Bock, mailto:%20conrad.bock@nist.gov)
 
Summary: 
Merge junctions should have a diamond notation option, for readability
and backward compatibility

Discussion: Merge junctions have been introduced in UML1.5 in the context of activity-graphs. There is
no reason to include this notation for statemachines as the concept of merge junctions as such does not exist there
nor it is used in that context. 
Disposition: Closed, no change. 
and backward compatibility.