If the PI is inadequate, can anyone else come up with an alternative?
Or perhaps a list of use cases that a solution should meet?
One alternative would be to accept that sending XML over the wire to be
styled on the client with a lightweight styling and transformation
language has not been a universally popular proposal, so to abandon the
XML experiment and revert back to using full SGML on a back end server
system and using dsssl rather than its lightweight younger sibling, XSL
to transform the in house semantically rich markup down to presentation
oriented formats such as html 2 and postscript and sens that over the
wire to be displayed on clients that don't need (and don't have) much
processing capability.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--