RE: Driving XSL based on WAP phone characteristics

Subject: RE: Driving XSL based on WAP phone characteristics
From: "Steven Livingstone" <s.livingstone@xxxxxxxxxxxxxx>
Date: Wed, 26 Apr 2000 13:12:24 +0100
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....?

It doesn't solve the problem of various device specific styles but would go
a long way to helping us write to varying browsers.

Would that be useful?? We could get started on a schema.

cheers,
Steven

Author
Pro XML
http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003110
Pro Site Server 3, Wrox Press
http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861002696
Pro Site Server 3.0 Commerce Edition, Wrox Press
http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861002505

Steven Livingstone
Glasgow, Scotland.
07771 957 280 or +447771957280

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of Neill James
Sent: 26 April 2000 11:50
To: xsl-list@xxxxxxxxxxxxxxxx; wap_technical@xxxxxxxxxxx
Subject: Driving XSL based on WAP phone characteristics


The wapforum body is looking at extending the scope of what is effectively
the HTTP_USER_AGENT header field to include more structured information
about the functional capabilities and physical characteristics of WAP based
mobile devices (eg, screen height, colour availability, font availability).

Has anybody looked at how these characteristics can be used to drive an XSL
style sheet to deliver an XML transformation that provides a good look and
feel for any WAP device (for which the characteristics are known)?

Do you reckon this is just a pipe dream. Or is the only option to do
seperate XSL files to deliver XML content for each WAP device that is
distinct from the next. For me, this sounds like a nightmare as there are so
many device types out there - and more to come.


Regards
James


James Neill
Industry Consultant
ICL Financial Services
26 Finsbury Square
London EC2A 1SL
United Kingdom

email:  james.neill@xxxxxxx
mobile: +44 (07867) 824543



International Computers Limited
Registered in England no 96056
Registered Office
26 Finsbury Square
London EC2A 1SL
http://www.icl.com/fs


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread