I think it's a most important gap almost in our development story today, is that, for wireless and voice and all these different technologies, you have no single authoring model. No single way of creating your application. And what we have been supporting is, I think, the most promising standards ever in this space which is W3C's XHTML-based push with the support of XForms which is coming in version 2.0 of XHTML.

We actually provide you a very powerful framework for creating what we can multi-channel application. Which means you can author now in XHTML, which people know, combine with XForms and then get the events controls that you need for further things like voice and then you have cascading style sheets and you get support for the different style and representation and rendering under different devices.

And then, you know, what we do in our server, of course, is take that output and then listen to what kind of device connects during the request and then do the re-formatting to that markup. In some cases we'll convert it to-in the app server, transparently-to things like WML, Compact HTML, Voice XML, and all these other markups. But the native layers that you have in the XHTML, Xforms-based authoring model and app server take care of rendering to the native layers, as I like to call them, whether that be WAP or XHTML or whatever.