Issue 15815: Attributes of Transaction Element (bpmn2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: According to the class diagram of Sub-Process (Figure 10.29, page 181), Transaction has two attributes (protocol and transaction). However, in Table 10.21 on page 185 only method is mentioned (transaction missing). In addition, the class diagram specifies that the data type of method is string. Table 10.21, however, defines that the data type is of TransactionMethod. Since an element TransactionMethod is not defined in any metamodel, I would suggest to use data type string. In addition, protocol could be inserted in Table 10.21 with a cardinality of [0..1] or [1]. Resolution: Revised Text: Actions taken: November 12, 2010: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 12 Nov 2010 08:09:48 -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.2.5 FormalNumber: dtc/2010-06-05 Version: 2.0 Doc_Year: 2010 Doc_Month: June Doc_Day: 05 Page: 181ff Title: Attributes of Transaction Element Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: According to the class diagram of Sub-Process (Figure 10.29, page 181), Transaction has two attributes (protocol and transaction). However, in Table 10.21 on page 185 only method is mentioned (transaction missing). In addition, the class diagram specifies that the data type of method is string. Table 10.21, however, defines that the data type is of TransactionMethod. Since an element TransactionMethod is not defined in any metamodel, I would suggest to use data type string. In addition, protocol could be inserted in Table 10.21 with a cardinality of [0..1] or [1].