Sun to join Oasis standard committee


Sun to join Oasis standard committee

Sun Microsystems will be attending a committee meeting next week to begin formalising a web services process choreography standard, even though the company is playing a leading role in crafting a rival specification.

Sun is still selecting its representative to attend the first meeting of Oasis' Web Services Business Process Execution Language (WSBPEL) technical committee, which will meet on 16 May.

Sun, in collaboration with several other industry suppliers, released the Web Service Choreography Interface (WSCI) specification. Two months later, IBM, Microsoft and BEA Systems unveiled a similar effort, the Business Process Execution Language for Web Services (BPEL4WS) specification.

Now, the two competing standards are under review by different standards bodies, as the World Wide Web Consortium considers WSCI and the Oasis group begins work on BPEL4WS.

With heavyweights IBM and Microsoft backing it, BPEL4WS is the specification gaining industry momentum. BEA Systems, which had a hand in crafting both BPEL4WS and WSCI, is working on including BPEL4WS in a forthcoming update of its WebLogic Platform.  It has not drawn up similar plans for WSCI.

For now, Sun remains committed to WSCI and interested in monitoring the progress of BPEL4WS.

"At this point, the [Oasis] group has just come together, so I think Sun is going to wait to make any decisions as the process unfolds," said Sun spokesman Bruce McConnell.

 "It's too early to begin answering questions like, 'Does this mean Sun is pulling out of WSCI or supporting BPEL?'.'"

Email Alerts

Register now to receive 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