Issue 15253: Data associations need to be revisited and their use clarified. (bpmn2-rtf) Source: Trisotech (Mr. Denis Gagne, dgagne(at)trisotech.com) Nature: Revision Severity: Significant Summary: Data associations need to be revisited and their use clarified. Data association should have there own visual depiction. Using the look of association is misleading as data associations have a different meaning than associations. A data association is an edge between flow elements (data objects(ref) and data stores(ref))as such they should not cross boundaries of pools or can they? This is not clear. It is also not clear if data objects(ref) and data stores (ref) can be drwan outside lanesets or pools. Resolution: Revised Text: Actions taken: May 13, 2010: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 13 May 2010 13:48:51 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Denis Gagne Company: Trisotech mailFrom: dgagne@trisotech.com Notification: Yes Specification: Denis Gagne Section: 10.3.1 FormalNumber: BPMN 2.0 Version: v 0.9.14 RevisionDate: may 22 Page: 228-231 Title: Data Associations Nature: Revision Severity: Significant test: 3qw8 B1: Report Issue Description: Data associations need to be revisited and their use clarified. Data association should have there own visual depiction. Using the look of association is misleading as data associations have a different meaning than associations. A data association is an edge between flow elements (data objects(ref) and data stores(ref))as such they should not cross boundaries of pools or can they? This is not clear. It is also not clear if data objects(ref) and data stores (ref) can be drwan outside lanesets or pools.