Aehso’s Output

OASIS to form six committess to advance SCA.

Heh, OASIS have formed six technical committees to “simplify SOA application development”. According to OASIS this makes sense because:

“They’re simplifying something very complex — and something that’s made up of very distinct components. They need BPEL experts to work on the BPEL part, Java experts to work on the Java part, etc.,” Geyer said in an e-mail. “Trying to put people with such different skill sets and interests into one committee — and get quorums for meetings and approvals on drafts — would slow things down. I think we’ll see results much faster with six groups working in parallel.”

Six committees, working on interrelated specifications in parallel and not a reference implementation or compatability test suite in sight. This is bordering on the sublime but apparently a lot of people want this the SCA beast to live. Why exactly is beyond me.

Speaking of implementations, does anybody know what the heck really happened in the Tuscany project that caused the Fabric3 fork? I mean, it must have been pretty bad to fork a project that was backed by both IBM and BEA.

(via Tim Bray’s ongoing)

No comments yet.

Leave a comment