Dear Alistair, after working intensely with XSLT again (with a break for several years), I wholeheartedly concur. You guys are right though, through the document function it would be possible. So any particular tool-set you could recommend? Günther Am 25.02.10 15:01, schrieb Bayley, Alistair:

...

From: haskell-cafe-bounces@haskell.org [mailto:haskell-cafe-bounces@haskell.org] On Behalf Of Günther Schmidt

Anyway through a very, very tedious process of xslt-transformations I finally have the XML document I need.

But now I need to amend the attributes of some elements with looked up values from the outside, the lookup-key is a particular attribute value of the nodes. This I cannot do through xslt processing as the information needed is not within the xml document.

Not the answer you were looking for, but...

Is the lookup table in another XML document? If so then you might well be able to use the document() function, if your xslt processor supports it e.g.

That said, if you can, use Haskell to do all the transformations i.e. avoid xslt altogether. I despise xslt.

Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************

Hi Alistair, sorry, misunderstanding. I meant which *Haskell* - XML-tools. Günther Am 25.02.10 15:44, schrieb Bayley, Alistair:

...

From: haskell-cafe-bounces@haskell.org [mailto:haskell-cafe-bounces@haskell.org] On Behalf Of Günther Schmidt

You guys are right though, through the document function it would be possible.

So any particular tool-set you could recommend?

On Windows, the Microsoft xslt processor supports document(), I believe. Other than that, I have no recommendations.

Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************

Hello Gregory, we have pretty much come to the same conclusion :) Günther Am 25.02.10 17:17, schrieb Gregory Collins:

Günther Schmidt writes:

...

My question to those with experience of the Haskell-XML tools: which one should I use?

You'll need to evaluate which one fits your needs best; in my mind the contenders are:

------------------------------------------------------------------------------ xml: http://hackage.haskell.org/package/xml

Small, simple, comprehensible DOM interface with some simple search + cursor functions, uses String internally. If performance is not a concern this one is the "nicest" in my opinion.

------------------------------------------------------------------------------ hexpat: http://hackage.haskell.org/package/hexpat

A binding to the expat C library; super-fast as a result, most of the useful functions from xml have been ported over here. Has support for SAX parsing. This is the one I usually use when I don't need things like DTD validation or XPath support (i.e. 100% of the time). Not much in the way of docs (haddock only) but it's small enough to be comprehensible.

------------------------------------------------------------------------------ HXT: http://hackage.haskell.org/package/hxt

Dauntingly enormous, oodles of features, you need to grok arrows. Uses String internally. The documentation is pretty iffy -- individual modules are haddocked pretty well but there are a zillion of them and a table of contents is sorely needed. Website docs/manuals are of the "read this wiki page, this paper, and my master's thesis" variety, but the wiki page is actually pretty good. This is the one I use when I need a feature hexpat doesn't have, but normally I avoid it if I can because arrows cause me to "grind the gears".

------------------------------------------------------------------------------ HaXml: http://hackage.haskell.org/package/HaXml

Lots of modules and features here, uses String internally, has the same "table of contents" issue as HXT, manual seems to consist of an ICFP paper from 1999, Haddock is a little terse/spotty.

Hope this helps,

G