Issue 6093: Edge constraint for control nodes (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: The constraint for ControlNode ("The edges coming into and out of a
control node must be either all object flows or all control flows.")  is
inconsistent with the semantics for JoinNode, which permit mixed types
of incoming edges.  Likewise a merge node can merge control and data
flows.  What type of edge should be outgoing in this case?
Resolution: Remove constraint [1] for Control Node, p 317.
Revised Text: 
Actions taken:
August 30, 2003: received issue
March 8, 2005: closed issue
Discussion: 

End of Annotations:=====
Name: Jim Frank
Company: IBM
mailFrom: joachim_frank@us.ibm.com
Nature: Revision
Severity: Significant
Subject: Edge constraint for control nodes


The constraint for ControlNode ("The edges coming into and out of a
control node must be either all object flows or all control flows.")  is
inconsistent with the semantics for JoinNode, which permit mixed types
of incoming edges.  Likewise a merge node can merge control and data
Issue 6093: Edge constraint for control nodes           Activities      Karl F
http://www.omg.org/issues/issue6093.txt
yourdirectory/uml2-superstructure-ftf.open.html#Issue6093


Resolved


Remove constraint [1] for Control Node, p 317.

flows.  What type of edge should be outgoing in this case?