[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
At 07:15 AM 3/12/2004, David wrote:
Alternatively, you can arrange it so that the data you need your script to query is actually put out in some form into the HTML output, most likely using HTML/CSS to hide it from the browser display. This can also be convenient because the transform can restructure it into the simplest possible form, optimized for your script.
This way of doing it will work if your transforms happen on the server or in batch production, as well, since the HTML page, even with the scripting, is completely self-contained -- so the presentation layer doesn't need to query into the next layer down. Of course there are disadvantages too: for example if you have a large data set to query and only want your HTML page to show a small bit of it, you may not want to send the entire data set to the client.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] binding xml to stylesheet
|
Subject: Re: [xsl] binding xml to stylesheet From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Fri, 12 Mar 2004 11:49:21 -0500 |
At 07:15 AM 3/12/2004, David wrote:
> Where has the original document gone? you haven't said what browser you are yousing. In IE this is explained in the msxml3 sdk that you can download from microsoft
Browsing XML Using XSLT Style Sheets
says
The document.XMLDocument property returns the root node of the XML source document.
The document.XSLDocument property returns the root node of the XSLT style sheet document.
Mozilla has something similar.
Alternatively, you can arrange it so that the data you need your script to query is actually put out in some form into the HTML output, most likely using HTML/CSS to hide it from the browser display. This can also be convenient because the transform can restructure it into the simplest possible form, optimized for your script.
This way of doing it will work if your transforms happen on the server or in batch production, as well, since the HTML page, even with the scripting, is completely self-contained -- so the presentation layer doesn't need to query into the next layer down. Of course there are disadvantages too: for example if you have a large data set to query and only want your HTML page to show a small bit of it, you may not want to send the entire data set to the client.
Cheers, Wendell
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] binding xml to stylesheet, David Carlisle | Thread | [xsl] XSLT parameters in TrAX filte, Stephen Summerfield |
| [xsl] Create XSL with Saxon, Schreifels, Mark J. | Date | Re: [xsl] xsl and xml CDATA or Not , Peter Flynn |
| Month |