[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: xsl:sort in old MSXML
David, I understand the approach, and let me explain (maybe I did it wrong before). I'm concerned on both: a) portability (user machine needing to install one of this processors (Saxon, MSXML, etc.), and let say for this that certain browsers install the second one (MSXML, am I right?) and b) processing (capability to run against an XML data in the moment the process is instatiated, and not to show a static HTML with data inside it). Claudio. -----Original Message----- From: David Carlisle [mailto:davidc@xxxxxxxxx] Sent: Miércoles, 02 de Julio de 2003 10:17 a.m. To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: xsl:sort in old MSXML > Sorry, but when you mean "to convert", do you mean "to transform"? yes. > But if the answer is "to convert", why should I convert to HTML and > place the output in my pages? Why not to use the "on-the-fly" > processing of XSLT to get the "output=HTML"? Because you said you didn't have access to the server to do on the fly transformation as the request is made (as for instance is done with cocoon and several other systems that let you run xslt as part of the web server) and you were concerned about Netscape 4 and similar browsers that can't do XSLT at all. It is _very_ common to have all your data in XML (or a database with an XML view), convert to HTML using XSLT as a batch process to generate an entire web site (or at least directory) full of html (or pdf) etc files and then put those HTML files on your server. That way you get the benefits of XMl to control and automate document production, but the end user just needs any old html browser. This is what the W3C do for example. The specifications for (at least) XML, MathML, XSL, XSLT, Xpath, Xquery, XML Namespaces, are all authored in XML, converted to various formats via XSLT ( formats generated include HTML, XHTML, FO (for pdf) LaTeX (for pdf) and then these formats are placed on the W3C website. You can read the XSLT spec without needing a browser that implements XSLT, as it is just HTML. In the case of MathML for instance we have one XML source document (spread over a few files) and a set of XSLT transformations generates from that 160 HTML files 80 XHTML+MathML files, two TeX files (for the pdf versions of the spec) and the TeX source to generate 200 images that are included into the HTML documents. We could just serve the XML file and expect the clients to generate all these files on the fly, but we don't. (We do though make the entire set of transformations available in a source .zip file linked from the spec, should anyone want to try, or is interested in looking at how it is all put together). David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. 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 XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|