The ebBP technical specification can be used to specify any shared collaboration. The specification may be effectively used with the other specifications in the ebXML framework, and with other technologies, for example when Web Services software components are being specified to execute Business Collaborations. Or, the ebBP business semantics and syntax are well-suited to enable definition of modular process building blocks that are combined in complex collaboration activities. The ebBP technical specification is also used to specify the business process related configuration parameters for configuring a software component to execute and monitor the collaborations.

A Business Collaboration is a set of roles interacting through a set of choreographed Business Transactions by exchanging Business Documents. A Business Collaboration is defined by the parties in the collaboration; it can be simple or complex, it can include expected and unexpected (but contingent) actions and the collaboration can allow for other than eBusiness options. The ebBP technical specification is used to specify the business process parameters to configure the Business Service Interface (BSI) needed to execute and to monitor the collaborations, including the capability to transition to human interactions or decisions that may be important to eBusiness activity, e.g. a phone call.

A Business Signal is computable. This provides the collaborating parties with a mutual understanding of the business activity. This function allows the parties to know if their expectations in a Business Transaction are realized. This is state alignment, and is important in order for the ebBP specification to have commercial viability. The ebBP specification provides the ability to conduct intended transactions if that is the intent of the collaborating parties.

Business signals have a specific business purpose and are separate from lower protocol and transport signals. One or more Business Signals can be exchanged as part of a Business Transaction to ensure state alignment between both parties. Evaluation of business signals enable the state of a Business Collaboration to be explicitly calculated at run time. The ebBP technical specification provides both the structure and choreography of Business Signals, including allowing for user defined signals.

A Business Transaction is realized as Business Document Flows between Requesting and Responding parties performing roles. A Business Transaction is a specialized protocol used to achieve and support enforceable transaction semantics and state alignment between collaborating parties. The patterns listed in the technical specification provide semantic guidance, and options for a Business Transaction. One or more Business Signals can be exchanged as part of a Business Transaction to ensure state alignment of the respective parties.