SOA Meets Compliance: Shift from age old to COA

Its a old say , no matter how raw your data is, How you architect your solution, eventually you have to obey the rules of BIG. Saying that what I mean is till a little while ago, we were all putting our head on SOA, and its beautification, Now making SOA look good is not enough, MAKING SOA SECURE IS MORE IMPORTANT,
Are we following rules provided by Governance, to make SOA bullet-proof?
Good article about SOA Meeting Compliance Compliance and Integration - SOA Meets Compliance: Compliance Oriented Architectures - ebizQ
We have seen this shift for ages
Raw Text -> XML->Web Services->SOA-COA
Every organization, who implement SOA in their indiviual business units they can not leave their services loose, it needs to meet whole nine yards of compliance, SOX (Sarbanes-Oxley),
Message to them is "do it slow but do it right",

More to come on this soon...stay tuned..

SOA; Open source Push

Indeed Simplicity is good to understand , whether it is in life or field where we work,
Basically the way I'm trying to take SOA as a example for Open source representation, and use Michael Curry's Blog as justification for my words.
SOA started with simplistic idea, as concept and stanard around XML based communication from different systems and went ten fold from basic Web service invocation framework (WSIF) to Web service Modeling Language/Web Service Management Layer, well it will go much further to moon..
Michael Curry's words about stanards like CORBA; why it didnt fly as much as SOA/Web Service, justifies Open source widespread and its fundamental adoption in the developer community for any technology/concept/standard faster than anything that happened decades ago.
As community grows, reach becomes easy, more power to open source.