InfoQ

News

Controlling SOA development in OASIS?

Posted by Mark Little on Mar 28, 2007 07:38 AM

Community
SOA
Topics
Web Services
Tags
Standardization
An interesting side-note to last week's announcement concerning SCA and SDO is the formation of the OASIS Open Composite Services Architecture group, that will oversee the evolution of these specifications. Normally in OASIS, it's a one-member/one-vote policy, with a chair (or co-chairs) to help direct the flow of the work to completion. This time, however, OASIS (or some of its members) believe it necessary to impose more structure on the work. They may be right: the open process that OASIS has in place has resulted in many technical committees being diverted from target or delayed significantly by internal struggles. Therefore, a board of members (steering committee) to watch over this and make sure the results are in line with requirements may make sense; the OMG has such a thing which has worked well in the past, and the lack of such a body in the JCP is frequently cited as a downside to that process.

However, as the OASIS announcement says:

The Open CSA Member Section Steering Committee will consist of seven
members. Initially, four seats will be filled by representatives from BEA
Systems, IBM, Oracle, and SAP, each of whom will serve a term of two years.
Elections will be held to fill the three remaining seats. To ensure
consistency of management, those elected to these three seats initially will
serve one year terms with subsequent election for terms of two years.
the original authors of the specifications already have a controlling interest in the steering committee. Given how fully formed these specifications were upon initial submission to OASIS, this could be seen as a worrying move to simply have a rubber-stamping exercise around them. It has to be asked why all 7 seats could not have been put up for open vote? Furthermore, is this a precedent that will have further implications in OASIS? Hopefully the 3 voted members and the 4 initial members will act co-operatively to make sure the results of the various committees are good and useful, even if that requires changes to the work as submitted. After all, this is supposed to be for the benefit of the community as a whole and not just imposed from above.

No comments

Reply

Exclusive Content

Book Except and Interview : Aptana RadRails, An IDE for Rails Development

Aptana RadRails: An IDE for Rails Development by Javier Ramírez discusses the latest Aptana RadRails IDE, a development environment for creating Ruby on Rails applications.

Fast Bytecodes for Funny Languages

Cliff Click discusses how to optimize generated bytecode for running on the JVM. Click analyzes and reports on several JVM languages and shows several places where they could increase performance.

Scott Ambler On Agile’s Present and Future

Scott Ambler, Practice Lead for Agile Development at IBM, speaks on the current status of the Agile community and practices having a look at the perspective of the Agile’s future.

Manager's Introduction to Test-Driven Development

Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD).

Structured Event Streaming with Smooks

Smooks is best known for its transformation capabilities, but in this article Tom Fennelly describes how you can also use it for structured event streaming.

How to Work With Business Leaders to Manage Architectural Change

Successful architectures evolve over time to meet changing business requirements. Luke Hohmann presents how to collaborate with key members of your business to manage architectural changes.

Colors and the UI

In this article, Dr. Tobias Komischke explains how colors used in a GUI can influence our interaction with a computer and offers advice on using the appropriate colors for the interface.

Building your next service with the Atom Publishing Protocol

In his presentation, recorded at QCon San Francisco, MuleSource architect Dan Diephouse explores ways to use the Atom Publishing Protocol (AtomPub) when building services in a RESTful way.