Issue 16003: Incoming/Outgoing Data Associations of DataInputs/Outputs (bpmn2-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: According to page 213: Data Inputs MAY have incoming Data Associations and page 215: Data Outputs MAY have outgoing DataAssociations I think that it should be the other way round. A Data Input should have an outgoing Data Association and a Data Output should have an incoming DataAssociation. This would correspond with Figure 7.8. The Data Input "Part Requisition" only has an outgoing Data Association and vice versa, the Data Output "Part Requisition" only has an incoming Data Association. Resolution: Revised Text: Actions taken: February 2, 2011: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 02 Feb 2011 09:18:36 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Christine Natschlaeger Employer: Software Competence Center Hagenberg GmbH mailFrom: Christine.Natschlaeger@scch.at Terms_Agreement: I agree Specification: Business Process Model and Notation (BPMN) Section: 10.3.1 FormalNumber: formal/2011-01-03 Version: 2.0 Doc_Year: 2011 Doc_Month: January Doc_Day: 03 Page: 213-215 Title: Incoming/Outgoing Data Associations of DataInputs/Outputs Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Description: According to page 213: Data Inputs MAY have incoming Data Associations and page 215: Data Outputs MAY have outgoing DataAssociations I think that it should be the other way round. A Data Input should have an outgoing Data Association and a Data Output should have an incoming DataAssociation. This would correspond with Figure 7.8. The Data Input "Part Requisition" only has an outgoing Data Association and vice versa, the Data Output "Part Requisition" only has an incoming Data Association.