A business process definition created using the semantics and syntax provided in the ebBP technical specification is referred to as an ebBP definition. ebBP definitions describe interoperable business processes that allow business partners, or collaborating parties, to cooperate and achieve a given business goal. It contains the specification of the Business Transaction, the choreography for using the Business Transaction(s) that comprise a Business Collaboration, and the Business Collaborations themselves. An ebBP definition is a machine computable and interpretable specification. The software component that manages these activities on behalf of a business partner is termed a Business Service Interface (BSI).

The ebBP OASIS Standard is a technical business process specification. It defines a standard language so that business systems can be configured to support the execution of business collaborations between partners or collaborating parties rather than the processing accomplished from the perspective of one business partner. The formal designation has been eBusiness Extensible Markup Language (ebXML) Business Process Specification Schema (BPSS). It is more commonly known as ebBP (after the OASIS ebXML Business Process Technical Committee).

Review answers to the frequently asked questions below on ebBP. Post new questions and additional comments at the FAQ Forum. See also: ebXML FAQ, ebCPPA FAQ, ebMS FAQ, and Registry FAQ.

Read more

The benefits of an XML Registry are numerous and include:

• Promotes efficient discovery and maintenance of registered objects
• Enables efficient version control for registered objects

Read more

An XML registry is an information system that stores XML artifacts (e.g., XML schemas, data elements, etc.) and non-XML artifacts (e.g. supporting documents), as well as details (metadata) about the artifacts.

Read more