Friday, March 23, 2007

SCA, OASIS, and the JCP

My take on Mark Little's InfoQ post on the news that SCA/SDO go to OASIS is that the move makes a lot of sense. I'm actually amazed it has taken this long to happen. SCA/SDO are language/platform independent, not unlike a lot of the WS-* specifications on OASIS.

So, much like the JCP has implemented key WS-* specs within the Java platform, they should focus on doing the same with SCA/SDO as the specs work their way through the broader community review/input process.

On a related note, there's been way too much chest-thumping on SCA being a threat to Java EE, JBI, etc. Mike Edwards offers a perfect overview of the Relationship of SCA and JBI; lays out the similarities and differences nicely. SCA is from the tops-down user perspective; JBI is from the bottoms-up platform builder perspective. While they may share some similar patterns, those who pit SCA vs. JBI only demonstrate their inability to distinguish between the two perspectives.

Bottom-line: It is time to get the SCA/SDO specs out in the open and let the community process take it forward.


Brian said...

"those who pit SCA vs. JBI only demonstrate their inability to distinguish between the two perspectives."

I completely agree. In fact, we've set out to prove it in actual implementation. You can see our work here:

and I posted anecdotal information here:

let me know what you think.

Shaun Connolly said...

Nice! I love the "I'm a simple man, a caveman really" angle...sums up my initial reaction as well. The political posturing makes what should be a pretty straightforward topic way more complex than it needs to be.

I've passed your caveman post to Mark Little to see if he has any color to add to the topic.