BPMN2 — Aliases for imported definitions

Filed for Martin and Steve, based on choreograph discussions. When importing definitions, names of imported elements might not be suitable for the application of the importing definitions. The importing definitions should be able to assign aliases to the imported elements for use within the importing definitions.

-------------------------------------------------------------------------------------------------------------------
Proposal to review: [Suzette Samoojh - March 18, 2009]
-------------------------------------------------------------------------------------------------------------------

Assumption: "Aliasing" is required when you need to use an existing element, but wish to label it differently based on a usage context.
Two known use-cases:

• A Participant references a Role (or Entity) and wishes to apply a name that is different from the Role (or Entity) name.
• A CallActivity references a CallableElement and wishes to show a name that is different from the name of the CallableElement.

Proposal: Use existing 'name' attributes to achieve this.

• Participant.name: If specified, serves as the 'alias' for the referenced Role or Entity. If unspecified, the original name of the Role or Entity is used.
• CallActivity.name [inherited from FlowElement]: Ditto
  No MM changes needed. Just spec text.

If anyone has an example that the above does not satisfy, please post it.
[Note that a concrete example then means we will tackle this issue in a samples-driven manner].

This issue cannot be fixed in this FTF.
Disposition: Closed, Out Of Scope