Lists Home |
Date Index |
- From: Robb Shecter <firstname.lastname@example.org>
- To: Mark Birbeck <Mark.Birbeck@iedigital.net>
- Date: Mon, 08 Feb 1999 11:20:51 +0100
Mark Birbeck wrote:
> I wrote:
> > How about this: Have one XSL document per client side
> > scripting language.
> We do something similar for browser types, by generating all XSL
> documents through an ASP page. In our case, we detect the browser type,
> and change the rules in the stylesheet dynamically. Your scenario would
> benefit too, because you wouldn't need to send loads of sylesheets to
> the client...
Interesting idea. It reminds me of the IBM Alphaworks "XML Enabler" project, which is a
framework for doing the same thing: selecting an appropriate XSL stylesheet based on browser
type. ( http://www.alphaworks.ibm.com ) This sounds better to me than what you're doing,
actually, because it's pure Java/servlets; not Microsoft/ASP dependent.
Anyhow, in my scenario, the server would be run by one organzation, and the clients by
others. The clients would be responsible for making their own XSL sheets depending on
whatever type of platform they have. So, only the XML User Interface / Component description
would come over the wire, not the XSL.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)