Oasis forms ebXML business process committee


Oasis forms ebXML business process committee

Oasis has formed an ebXML Business Process Technical Committee to further define the ebXML BPSS (e-business XML Business Process Specification Schema) model for business collaborations within and between enterprises.
The ebXML BP technology, which is royalty-free, will support the exchange of standards-based process definitions, such as those developed by industry-specific organisations. It is part of a suite of specifications enabling conducting of business over the internet.

The committee will base its work on ebXML BPSS Version 1.01, jointly developed by Oasis and the United Nations Centre for Trade Facilitation and Electronic Business (CEFACT).

Additionally, the committee plans to collaborate with other Oasis committees, such as those developing the Web Services Business Process Execution Language (WSBPEL).

Work also will be aligned with relevant efforts from other organisations, such as the W3C and RosettaNet.

Committee members include Cyclone Commerce, Fujitsu, Sterling Commerce and Sun Microsystems. Participation remains open to all organisations and individuals.

The committee is the fifth formed by Oasis for the purpose of advancing ebXML. Other committees have been formed to focus on specific issues related to registry, collaboration, messaging, and implementation and interoperability.

The multiple pieces of XML necessitate many committees to deliberate on it, said Oasis vice-president Karl Best . Oasis has worked on ebXML for more than four years, he added.

Paul Krill writes for InfoWorld

Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy