Issue 15066: Notation for expanded hexagons (bpmn2-rtf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: Filed for soaML: When multiple hexagons (conversation/communication) are
expanded, it isn't possible to tell which message flows go with which
hexagons, because the hexagons disappear.  Should have a grouping
notation to show which message flow came from expanding which hexagons.
Resolution: 
Revised Text: 
Actions taken:
February 18, 2010: received issue
Discussion: 
This is deferred for more discussion on a notation for this.
Disposition: Deferred
End of Annotations:=====

m: webmaster@omg.org
Date: 18 Feb 2010 16:49:32 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Conrad Bock
Company:       NIST
mailFrom:      conrad.bock@nist.gov
Notification:  Yes
Specification: BPMN 2 Beta 1
Section:       Conversation
FormalNumber:  dtc/2009-08-14
Version:        
RevisionDate:   
Page:           
Title:         Notation for expanded hexagons
Nature:        Revision
Severity:      Significant
test:          3qw8
B1:            Report Issue


Description:


Filed for soaML: When multiple hexagons (conversation/communication) are
expanded, it isn't possible to tell which message flows go with which
hexagons, because the hexagons disappear.  Should have a grouping
notation to show which message flow came from expanding which hexagons.