---
title: "9.7 Choreography within Collaboration"
chapter: "9 Collaboration"
source: "OMG BPMN 2.0.2 — formal/2013-12-09"
pages: "136-138"
---
> 9 Collaboration · páginas 136-138 · [índice](../README.md)
## 9.7 Choreography within Collaboration
**Choreographies** can be included in a **Collaboration** diagram. A **Collaboration** specifies how the *Participants* and **Message Flows** in the **Choreography** are matched up with the *Participants* and **Message Flows** in the purpose. To handle the *Participants*, the innerParticipant of a ParticipantAssociation refers to a *Participant* in the **Choreography**, while the outerParticipant refers to a *Participant* in the **Collaboration** containing the **Choreography**. This mapping matches the **Participant Bands** of the **Choreography Activities** in the **Choreography** to the **Pools** in the **Collaboration**. Thus, the names in the **Participant Bands** are NOT REQUIRED (see Figure 9.32).
*Figure 9.32 – An example of a Choreography within a Collaboration* (p. 137)
in the **Choreography**, while the outerMessageFlow refers to a **Message Flow** in the **Collaboration** containing the **Choreography**. This mapping matches the **Message Flows** of the **Choreography** (which are not visible) to the **Message Flows** in the **Collaboration** (which are visible). This allows the **Message Flows** of the **Collaboration** to be “wired up” through the appropriate **Choreography Activity** in the **Choreography** (see Figure 9.32).
*Participants*. For example, if a **Choreography Activity** has a *Participant* with the same partnerEntity as a *Participant* in the **Collaboration** containing the **Choreography**, then these two *Participants* could be assumed to be the same **Message** in a **Call Choreography Activity** and the **Collaboration**, could be automatically synchronized by a MessageFlowAssociation, if only one **Message Flow** has that **Message**.
*Figure 9.33 – Choreography within Collaboration class diagram* (p. 138)