Standards families
BPMN choreography
Interactions as first-class tasks: each choreography task names the initiating and receiving participants in its bands.
bpmn.choreography@1New DDN source
Why use it?
When no party owns the process, the contract is the sequence of exchanges itself — the choreography draws exactly that.
When it helps
Cross-organisation protocols: ordering, settlement, any dance with no conductor.
How to read it
- Each task is one exchange; the shaded band is the receiver, the light band initiates.
- Sequence flow orders the exchanges, not internal steps — internals live in each party's own process.
What you need
- The participants
- The ordered exchanges
- Who initiates each one
Things to check
- Do not model one party's internal steps here — that is a process diagram's job.
- The initiator band must be the sender of the first message in the exchange.
Scope of this diagram
Declared choreography with participant-band validation; enforcement between organisations is out of scope.
Work with the converted example
- Open the viewer and select
choreography. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.