- From: Gary Adams - SMI Software Development <gra@zeppo.East.Sun.COM>
- Date: Fri, 17 Mar 2000 11:27:53 -0500 (EST)
- To: jim@ewingdata.com
- Cc: www-mobile@w3.org
There are some features in the WML User Agent and in the WML markup that are not covered by XHTML. e.g. variable substitution and navigational stack side effects of browsing and WML specific event handling. There are other W3C technologies that could come to bear on some of those WAP specific features, but they are not currently part of that infrastructure. e.g. object model, style mechanism, future forms and future events should be designed with a "basic subset" in mind for limited devices. $.02 > From: "James Ewing" <jim@ewingdata.com> > To: <sandeep@wde.org>, "Masayasu Ishikawa" <mimasa@w3.org> > Cc: <smarsden@etranslate.com>, <www-mobile@w3.org> > Date: Fri, 17 Mar 2000 16:42:19 +0100 > Subject: Re: WAP and its competitors > > > > > Well, if XHTML Basic 2 is seemingly the way to go, in terms of the W3C > > anyway, is there any use learning WML ? Infact doesn't XML make WML > > obsolete too ? Surely an XML DTD would be used when the document > > encounters a mobile device, and format the page accordinly. If browsers > > then support (limited) HTML as well as WML, we won't have to move to > > WML, everyone would just start using the greatly versatile XML. > > > > Or am I making no sense here ? :) > > Actually, WML is 100% XML. You can even map other XML languages to WML by > using an XSL style sheet. > > The language that the W3C is currently pushing is XHTML (among others). > AFAIK, this is basically HTML reformed with a DTD and the XML requirements > for well-formedness and lower case tags. > > Cheers, > > Jim Ewing >
Received on Friday, 17 March 2000 11:28:06 UTC