Advertisements Yes ... this is what cable is saying ... Well ... cable is not directly precluding this second approach either. They aren't providing the specs and standards that would allow for it. Then again ... perhaps they will in the future. Then again ... perhaps they won't. Perhaps the free market will force them to. Then again ... perhaps it won't. They prefer to ... at the very least ... have that option. What if someone decides not to provide VOD. What if someone decides to provide VOD ... but filters out all titles contating the word "The"? Ok ... the second product probably wouldn't sell very well. But ... you get my gist. What if someone ... somewhere ... provided some product that did _______. Yes it is somewhere in between. On the one hand, the client side (STB) is fairly open. Developers can write their own applications to do all sorts of things. A CNN poll that allows the viewers to interactively / immediately vote ... for example. On the other hand ... cable can squash any of those apps they want to. And again, the OCAP standard does not preclude / prevent a more standardized way of OCAP apps talking cable's servers and allowing CE developers to provide those additional advanced applications (like a 'better' VOD client). It just doesn't immediately provide for one either. Hard to give up complete control when you're used to having it. The cell phone and portable content are great examples where the free market and / or additional desired functionality might force cable to standardize and / or open up better. Then again ... they may not. I think the CableLabs specs take both these use cases pretty well into account ... but perhaps not.