Subject: RE: [xsl] XSLT & SQL From: Americo Albuquerque <aalbuquerque@xxxxxxxxxxxxxxxx> Date: Fri, 12 Jul 2002 18:06:52 +0100 |
but that is because those processors are working on the same concept, MSXML start with http://www.w3.org/TR/WD-xsl and changed to http://www.w3.org/1999/XSL/Transform. that didn't happen with SQL, each database has its version of SQL. and that will go on until they start to use a standard SQL lamguage. -----Original Message----- From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Charles Knell Sent: Friday, July 12, 2002 5:31 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: RE: [xsl] XSLT & SQL What I was trying to express is the distinction between the XSLT processor as a "machine" and the XSLT document as "raw material". In the SQL world the data and the SQL engine are intimately bound. By this I mean that you couldn't expect to use MS SQL Server to process SQL queries against a set Oracle database files without several intervening helper mechanisms. XML/XSLT, on the other hand, are uncoupled from any particular processor. You could use Saxon, Xalan, MSXML, Oracle or any number of other processors against the same set of data and stylesheet files and should get the same results in each case. -- Charles Knell cknell@xxxxxxxxxx - email ---- "bryan" <bry@xxxxxxxxxx> wrote: > Could the processing of an inline stylesheet be considered as something > which is not external to itself? 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 |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSLT & SQL, David Carlisle | Thread | [xsl] Please help: Transforming a n, s s |
RE: RE: [xsl] Forming a Tree, Michael Kay | Date | RE: [xsl] XSLT to find missing char, Michael Kay |
Month |