This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Driving XSL based on WAP phone characteristics
- To: xsl-list at mulberrytech dot com
- Subject: RE: Driving XSL based on WAP phone characteristics
- From: Matt Sergeant <matt at sergeant dot org>
- Date: Wed, 26 Apr 2000 14:36:09 +0100 (BST)
- Reply-To: xsl-list at mulberrytech dot com
On Wed, 26 Apr 2000, Steven Livingstone wrote:
> Yep - I've been thinking about this recently.
>
> In IIS, there is a file called browscap.ini, which can help us understand
> the functionality of all the known browsers and this file contains details
> of this.
>
> Why not extend this to all devices, and mark it up as well. Basically have
> an XML file containing information about all browsing type devices.
>
> Then, we simply map the user-agent to the entry within the file and have
> access to the functioality provided by that browser.
>
> The question is, how far do we go? Do we define the scripting langauges
> supported, the tags supported (important in the case of WAP) etc....?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If this is an issue then WAP needs fixed, just like HTML did. WAP browsers
should degrade gracefully just like HTML4+CSS browsers can if the output
is designed right.
Admittedly I don't know a whole lot about WAP, though.
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org http://xml.sergeant.org
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list