WebMink
Simon Phipps's personal commentary

Fast track to...? [WebTech]

This extract from an article from webservices.org explains more eloquently than I could manage why 'fast path' standardisation ("we've done all the thinking, why should we discuss it further? Just make it a standard") is a very dubious idea.

As a follow-up to the BPEL4WS specification that was released yesterday, IBM have developed an implementation of BPEL4WS called BPWS4J. The IBM Business Process Execution Language for Web Services JavaTM Run Time (BPWS4J) includes the following: a platform upon which can be executed business processes written using the Business Process Execution Language for Web Services (BPEL4WS); a set of samples demonstrating the use of BPEL4WS; and a tool that validates BPEL4WS documents.

Basically, the day after the release of the BPEL4WS specification, IBM shows up with a downloadable product suite which exploits this 'new standard'. Now either IBM engineers are able (to quote Elmer Fudd) to work "vewy vewy fast", or they had a major head start on developing the technology required which, if enshrined by an instant endorsement from a standards body, gives them an advantage over all competitors that should not be permitted.

Bottom Line: It makes it that much tougher to compete when you are reduced to attempting to implement the already developed and productized APIs of your major competitors. We either have standards or monopolies. The two must not be allowed to mix.

posted at 7:28 PM (UK) | |