Is SOA just another layer on the IT infrastructure? If not, are there unique characteristics of  SOA that change the game? What are they? Can't I just forget about 'legacy' architectures/infrastructure and 'do SOA'? Why not? Paul Lipton, Principal Architect at CA, asked this series of non-trivial questions at the start of his General Session presentation at SOA World 2007 West in the Grand Ballroom at the Grand Hyatt in San Francisco.

About the Speaker: Paul Lipton is a Senior Architect in the CA Intellectual Property and Standards Group where he specializes in SOA, Web services, standards, and emerging technologies. He has participated in many standards organizations such as OASIS and the W3C, is a founding member of the CA Council for Technical Excellence, a Microsoft Most Valuable Professional, and a Sun Java Champion. Paul has also been an architect and developer of enterprise systems for over 25 years. He is a highly sought-after author and speaker, and has shared his knowledge with appreciative audiences around the world covering such topics as Enterprise Architecture, SOA, Web services, management/security, governance, Java, .NET, and emerging technologies.