SOA and EA Convergence?

I happened to read these articles about SOA and EA Convergence ....

http://weblog.infoworld.com/realworldsoa/archives/2007/02/soaea_convergen.html
http://weblog.infoworld.com/realworldsoa/archives/2007/02/open_group_deba.html

Hmm ... I think the author is confused. In my mind, EA is a process where is SOA is an approach.

When one looks at frameworks like TOGAF and FEAF, its clearly about the architecture process. These frameworks also encapsulate a detailed methodology of their own. Net-net, its about steps and best practices in understanding as-is architecture, bring in different drivers to define to-be architecture. EA approaches/process doesnt care about different pieces of technology or how the business processes are defined. Its just about providing principles for creation of sound architecture foundation satisfying the drivers of today and tomorrow.

On the other hand, SOA is an architectural approach - it does care about the way processes are defined enabling service orientation. It does care about specific pieces of technology and resulting interoperability between various components. It does expect such principles as reusability is put to action from top to bottom.

So, one should be able to apply EA principles/process to SOA approach... isnt it? In the process of applying EA principles to SOA approach, some specific steps may have to be redefined - such as QOS/SLA as SOA promotes organization interoperability.

Any thoughts folks?