The following elements or features of BPMN are not fully defined
in this version of the specification:
- Message Flow is currently defined as being between to Participants (Pools).
The issue is whether Message Flow should be allowed to connect two objects
within the same Pool (i.e., the Participant sends a message to itself).
- A more comprehensive definition of the behavior and notation of Transactions
and their .g to BPEL4WS.
- The set of attributes for Flow Objects may be updated, including:
- A more formal mechanism for defining extensions to the graphical elements.
- Attributes of a Service Task, perhaps defining different types of
services (e.g., web service, client applications, etc.).
- Attributes of a User Task (workflow attributes).
- Attributes of a Task relating to choreography (collaboration) business
processes.
- Attributes of a Complex Gateway and its mapping to BPEL4WS.
- A better definition of the usage for the Quantity attribute of Sequence
Flow (e.g., for batching/unbatching) and its to BPEL4WS.
- A fully definition of Mapping to abstract business processes (BPEL4WS).
- Mapping to Languages for choreography businesses processes (e.g., ebXML
BPSS). This might involve the creation of a new type of activity: a Collaboration
Activity, which is a container for showing Participants (Pools) and their
interactions (Message Flow).
- The formal relationship between BPMN and other high-level business modeling
topics, such as organization, strategy, and business rules.
- Specification of BPMN as an XML language layer above BPM execution languages
(BPEL4WS).