For instance, you can do something called service reflection because of that separation. The idea is that you should be able to look at a service and turn it into something else. For instance, I should be able to take an Oracle database table and create a service out of it. This idea of reflection is being able to look at one thing and turn it into something else. And that is not something we typically do in component-based software development.
SODA also encompasses the idea of lookup and discovery.
You've got a situation where the pieces of application are out there somewhere, and you have to discover them. Finally, SODA includes the concept of dynamism. In component-based development, when a developer builds a component, there is a static piece of code. But in a services-oriented world, the code you'll be bringing into your project won't be a static piece of code. It'll be a live service somewhere.