RE: Driving XSL based on WAP phone characteristics

Subject: RE: Driving XSL based on WAP phone characteristics
From: "Martin Bryan" <mtbryan@xxxxxxxxxxxxxx>
Date: Thu, 27 Apr 2000 08:21:30 +0100
What the ISIS European XML/EDI Pilot Project found was most important in designing WAP applications last year was the need to have "alternative" texts and ordering for the WAP version. What was required was a mechanism for converting the "long" strings used for both browser presentation and typical information dissemination messages into a short form that could be displayed on a WAP screen. This involves more than simple truncation of long lines. Often you need an alternative form of information for the WAP presentation. These "translations" were stored as separate resources, while other "resources" were used to hold information relating to the characteristics of different types of devices. By interrogating these multiple resources in a relevant order it was possible to convert the incoming message to either a long-hand browser orientated view or into a WAP view, but in neither case did the contents of the original message form the bulk of the displayed data, which invariable came from the style sheet or one of the resources it dynamically accessed.

Martin Bryan
Technical Manager, ISIS European XML/EDI Pilot Project
(http://www.tieke.fi/isis-xmledi)


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


Current Thread