Re: [xsl] Copy results

Subject: Re: [xsl] Copy results
From: Steven Ericsson-Zenith <steven@xxxxxxxxxxxxx>
Date: Tue, 8 Jul 2008 03:38:41 -0700
Just so that I am clear, I am writing a book that is utilizing a project schema (memeio/structured text).

The book (and in fact all my current work, consisting of a variety of nascent research papers and books) is represented as a hierarchy of collections stored in an eXist database. Various sub-documents are generated by processing the entirety (such as an index) and a variety of application level analysis is performed (also written in XPath/ XSLT). And, indeed, I do process and generate multiple documents (although logically it is always one document).

Frankly, the system I use now (that includes Saxon 9, with which I am mightily impressed) is a more powerful and productive document authoring and publishing system for highly technical documents and scientific research than anything I have ever used (and I am a veteran of TeX, LaTeX, Word, Frame Maker et al). It has enabled features that I could only dream of before.

I do hope that Michael (Kay) is not expressing skepticism concerning this application of XSLT. It seems to me to be common enough.


On Jul 8, 2008, at 3:14 AM, Michael Ludwig wrote:

Steven Ericsson-Zenith schrieb:
[...] All I am doing in my pipeline is XML to XML transformations on a
hierarchy of collections. It is just that at one point in that process
I may want the output to go to two locations. To do this outside of
XSLT I will have to generate a different file that contains the
published file list and then copy the files - introducing unhelpful
latencies and potential points of failure.

If the glue for your series of XSL transformation was a general- purpose
language like Perl (only XSL 1.0, unfortunately) or Java or some .NET
language, there'd be no latency in the sense of process creation overhead.

As for failure to copy, if the disk is full, it is full - regardless of
platform chosen.

Surely the mere fact that results-document exists in XSLT suggests
some elementary file processing may be required.

I think this is mainly intended for generating multiple output documents, like document() and collection() serve you when you have multiple input documents.

Michael Ludwig

Current Thread