InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Controlling SOA development in OASIS?

Posted by Mark Little on Mar 28, 2007

Sections
Enterprise Architecture
Topics
SOA ,
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.
  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.