InfoWorld: Where does WSRP [Web Services for Remote Portlets] enter into this? It was mentioned in passing like we all would have already known that. There just seems like too many elements here to grasp.

Levy: WSRP is just a standard. [It is] one of the standards that govern the behavior of SOA.... I don't believe people need to know the standard, they just need to know that the products that they're combining are all maintaining the same standard. Think of cars. There's only two standards [for] cars -- metric and inch... If you need tooling for cars, you can buy tools for cars. The only thing you need to know is whether the car is following a metric system or inch system? Everything else is provided. Our goal is to do the exact same thing. [We] provide you with a set of tools that supports those standards without you needing to actually think through which standards does which and which standard does what. So in that respect we greatly simplify SOA implementation, because all you really need to know from a user perspective -- this is now not from my side, the architecture that comes from underneath -- but how a user sees it. All the user needs to know is based on the role in the cycle - which tool they need to use. And the interface, by the way, all of them would be identical in behavior, different in function, because obviously they're different functions. So as you move in the cycle, all you have to worry about is picking up, logging into your tool... You shouldn't care about the fact that there's something called a repository or WorkSpace Central. It's just there so you wouldn't have to repeatedly ask for information from before.

InfoWorld: I understand there is going to be a modularization of some of the products that are out there now, like WebLogic Server?

Levy: Correct.

InfoWorld: How does that play into this?