OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: ebBP v2.0.4 Submitted for OASIS Standard

OASIS Members:

The OASIS ebXML Business Process Technical Committee has submitted the following
specification set, which is an approved Committee Specification, to be
considered as an OASIS Standard:

- ebXML Business Process Specification Schema Technical Specification v2.0.4
- ebXML Business Process Specification Schema Technical Specification Appendices
- Schema
- SignalSchema

The text of the TC submission is appended.

You now have until 15 November to familiarize yourself with the submission and
provide input to your organization's voting representative.

On 16 November, a Call For Vote will be issued to all Voting Representatives of
OASIS member organizations. They will have until the last day of November,
inclusive, to cast their ballots on whether this Committee Specification should
be approved as an OASIS Standard or not.

Members who wish to discuss this ballot may do so through

In accordance with the OASIS Technical Committee Process, this Committee
Specification has already completed the necessary 60-day public review period,
as well as an additional 15-day public review period, as noted in the submission

The normative TC Process for approval of Committee Specifications as OASIS
Standards is found at

Any statements related to the IPR of this specification are posted at:

Your participation in the review and balloting process is greatly appreciated.


Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
phone: 603.232.9090


v2.0.4 Committee Specification [1]
a) Document links
Spec-doc [2]: 

Includes technical specification, appendices and read-me


Includes technical specification, appendices and read-me**

Spec-html (Spec only):  

Includes technical specification and read-me

Spec-Appendices-html (Appendices only): 

Includes Appendices and read-me


Note: TC administration is requested to also make available the .xsd as agreed
and documented at http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
that resolves to http://docs.oasis-open.org/ebxml-bp/2.0.4/ebbp-2.0.4.xsd
Includes Schema and read-me


Note: TC administration is requested to also make available the .xsd as agreed
and documented at http://docs.oasis-open.org/ebxml-bp/ebbp-signals-2.0 that
resolves to http://docs.oasis-open.org/ebxml-bp/2.0.4/ebbp-signals-2.0.4.xsd
Includes signal schema and read-me

Other supplemental information

Includes Public review comments v2.0.2 and v2.0.3, sample transforms, and


Includes documentation for Schema and read-me


Includes documentation for SignalSchema and read-me

Other References:
odf version: 

Includes technical specification, appendices and read-me

b) Included above

c) All schema and XML instances are well formed, and all expressions are valid.
Note, several examples, such as those where explicitly commented, are
abbreviated. In addition, in the Document Supplements package, these are samples
designed to be further developed for transformation purposes and are identified
as such.

d) The eBusiness eXtensible Markup Language (ebXML) Business Process
Specification Schema (BPSS) technical specification provides a standards-based
business process foundation that promotes the automation and predictable
exchange of business collaboration definitions using XML. With such an ebBP
process definition, business systems may be configured to support execution of
Business Collaborations consisting of Business Transactions.

e) The ebBP may be used with other process, configuration, registry, and
business document specifications and/or emerging technologies. For example:
a. An XML representation of an ebBP definition may be stored in the ebXML
repository and registered in the ebXML registry for discovery and use of ebBP
process instances.
b. An ebBP process definition document may be referenced by the Collaboration
Protocol Profile (CPP) and used in Collaboration Protocol Agreement (CPA) XML
documents. Guided by the CPP and CPA specifications the resulting XML document
may become the configuration file for one or more Business Service Interface,
i.e. the software component that may manage either business partner's
participation in a Business Collaboration.
c. If one or more parties wish to participate on the basis of web service
definitions the corresponding WSDL files associated to the Business Transaction
Activities that are representing the party may be generated and referenced in
the CPA, as necessary. The ebBP provides a mapping between BTAs (i.e. the usage
of a Business Transaction definition in a Business Collaboration definition) and
operations of one or multiple web services.
d. The ebXML Message Service Specification may provide the infrastructure for
message / signal for in the choreography specified in an ebBP process
e. The ebBP supports modular process definitions supporting UBL v1.0 and small
business subset have been released and approved as Committee Specifications (see
public ebBP site).

f) Current certifications:
http://lists.oasis-open.org/archives/ebxml-bp/200605/msg00083.html or

Bologna ENEA UDA PMI:  


g) Public reviews were conducted for v2.0.x. Substantive review notices
Public review v2.0.1, 60 day (to v2.0.2) Began 17 August 2005. Concluded 15
October 2005.
http://lists.oasis-open.org/archives/members/200508/msg00005.html (Clark)

Public review v2.0.2, 15 day (to v2.0.3) Began 3 February 2006. Concluded 18
February 2006 http://lists.oasis-open.org/archives/members/200602/msg00005.html

v2.0.3 initiated with non-substantive changes to v2.0.4 and Committee
Specification vote
http://lists.oasis-open.org/archives/ebxml-bp/200610/msg00018.html (McRae)

Document links held therein.

h) Committee Specification votes

Opened 21 April 2006. Concluded 28 April 2006.

Opened 6 October 2006. Concluded 13 October 2006.

i) Comments actually held and documented in Documentation-Supplements packages
To v2.0.3: 

As held in v2.0.4 from approved Committee Draft Errata and diff document 
Diff document on v2.0.4 candidate: 

Approved Committee Draft Errata: 

j) http://lists.oasis-open.org/archives/ebxml-bp-comment/
Note: Some comments were made directly to TC members or the chairs and 
forwarded to the TC for disposition, and were documented in
item i).

k) No minority reports

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]