Well, the point is today, if you want to build a mobile wireless application, there's really nothing you can say that we can be sure will work on every browser today. That doesn't exist. So the question is, "How can you minimize your risk? How can you minimize the chance that you would have to do any rewrites over the years?" Given that you will have to transform underneath no matter which approach you choose. And the point is with XHTML and XForms we are at a point where I think we can all see that this is going to be the de facto standard. This support for rendering on the client side is going to improve only over time and you just fill the gap until then with transformation and proxying. But the point is you're going to be able to retain all the investment in code that you put in today. If you put all your time into VoiceXML or SOAP or WAP or something like that, you're going to have to rewrite it, because those are not technologies that are brought up by anyone or people that are building in a large scale way.