The original Call For Participation for this TC may be found http://lists.oasis-open.org/archives/tc-announce/200309/msg00007.html
The charter for this TC is as follows.
OASIS ebXML Business Process (ebXML BP) Technical Committee
Statement of Purpose
The purpose of the OASIS ebXML Business Process TC is to continue work on a royalty-free technology representation and model compatible with an underlying generic metamodel for business processes, activities, and collaboration. This business collaboration could occur within or between enterprises. The collaboration may be enforceable, easily manageable, and/or traceable. This representation and model will provide a set of guidelines to define the business process-rules, semantics and syntax for both binary and multi-party collaborations. The representation and model will work within the ebXML architecture (for metamodel and model exchange) and will also support standards-based development and exchange of business process definitions.
In no event shall this Technical Committee finalize or approve any technical specification if it believes that the use, distribution, or implementation of such specification would necessarily require the unauthorized infringement of any third party rights known to the Technical Committee, and such third party has not agreed to provide necessary license rights on perpetual, royalty-free, non-discriminatory terms.
At the appropriate time the OASIS ebXML Business Process TC shall submit its Committee Drafts for balloting by OASIS membership for OASIS Standard status.
Scope of Work
The OASIS ebXML Business Process TC's effort will address and align with vertical industry needs for business process collaboration and focus on ease of use. The specification can be integrated into and bind with existing or emerging technologies.
The TC's work should build upon similar, existing standards wherever possible and align with other relevant standards for:
- Feature reuse
- Guidelines on how to jointly use the specification with other related standards
- Addressing requirements from other related standards
The following features are outside the TC's scope:
- Specific business process interface descriptions
- Business process execution languages
- The run-time execution instance
The specification will support the computable and executable language used for business collaboration, rather than the processing accomplished from the view of a single party. The TC may identify bindings to support the business process instance and ultimately the run-time execution. A binding (map) could enable other executable process mechanisms to drive enterprise applications where ebBP controls (rather than create) service behavior.
The TC will base its work upon the ebXML BPSS v1.01 specification (ebXML Business Process Specification Schema v1.01, http://www.ebxml.org/specs/index.htm) jointly developed by OASIS and UN/CEFACT, and derivative work expected to be donated by co-sponsors and participants.
The work of the TC will:
- Enable business systems to be configured in a canonical way to support the execution of business collaborations and transactions. This will improve interoperability of business processes across and within enterprises and should help to simplify and converge current collaboration models and methodologies.
- Enable an organization to express characteristics of its business processes -- such as configuration parameters specific to choreography and business collaboration and refined by a collaboration agreement (such as an ebXML Collaboration Profile Agreement) -- to enable electronic integration of business processes as part of a larger collaboration. This includes the interaction points in the organization's business process to determine whether and how to engage in a collaboration and the kinds of information exchanges required. ebBP will be capable of working with e-business specifications from other industry and standards organizations such as RosettaNet, EAN.UCC, and UN/CEFACT.
- Provide integrated operational and functional service views of business processes, which will enable business analysts to more directly participate in business collaboration creation and management.
- Allow business process models to be expressed visually (through diagrams) and in XML (machine readable).
- Support the ebXML framework and Web services to provide a loosely coupled, highly aligned specification set, while enabling support for other emerging technologies. Promote the utility of this principle, through, for example, actively working with other OASIS technical committees, industry and standards organizations.
List of Deliverables
- Requirements document: Due within 2 months of first meeting.
- ebXML Business Process specification and schemas: This specification will reflect refinements and changes made to the submitted version of ebXML BPSS that are identified by the TC members for additional functionality, semantic clarity and technical robustness within the scope of the TC charter. Final draft will be due within 6 months of first meeting.
- Industry or domain specific examples or implementation guides may be developed. The due dates will be determined after the initial set of deliverables is complete.
The primary audience for the final output of this TC is business process analysts and implementers.
All business will be conducted in English.