Issue 15551: Page 341. Choreography Activity instead of Task (bpmn2-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: It says: “The three (3) or more partitions in the Sub-Choreography shape provide the distinction between this type of Task and an Orchestration Sub-Process (in a traditional BPMN diagram).” A Sub-Choreography is not a “type of Task”, but it is a “type of Choreography Activity”. Then, it should say: “The three (3) or more partitions in the Sub-Choreography shape provide the distinction between this type of Choreography Activity and an Orchestration Sub-Process (in a traditional BPMN diagram).” Resolution: Revised Text: Actions taken: September 17, 2010: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 16 Sep 2010 22:27:05 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Eduardo Jara Employer: mailFrom: ejara@craftware.net Terms_Agreement: I agree Specification: BPMN 2.0 Beta 2 Section: 11.4.2 FormalNumber: dtc/2010-06-05 Version: 2.0 Doc_Year: 2010 Doc_Month: June Doc_Day: Day Page: 341 Title: Page 341. Choreography Activity instead of Task Nature: Revision Severity: Minor CODE: 3TMw8 B1: Report Issue Description: It says: .The three (3) or more partitions in the Sub-Choreography shape provide the distinction between this type of Task and an Orchestration Sub-Process (in a traditional BPMN diagram).. A Sub-Choreography is not a .type of Task., but it is a .type of Choreography Activity.. Then, it should say: .The three (3) or more partitions in the Sub-Choreography shape provide the distinction between this type of Choreography Activity and an Orchestration Sub-Process (in a traditional BPMN diagram)..