Hi Jan,

Thanks for the great confidence — I actually took a look at the code right when you posted, but then I saw the heavy use of CSV storage and decided "not today" :-)

4 days later, I'll try again: I don't believe that you can't figure #1 out yourself, so I'll give a little hint about #2 and then I'll take a second look at the code and come back with something later.

One of the big differences between C# and XSLT (from what I've experienced) is that when you're doing something like this, where you've got a set of objects/nodes that needs filtering, the C# version usually puts the filter inside, e.g.:

foreach (var d in docs) {
if (somefilterExpression == true) {
# Do something with d
}
}

whereas, the XSLT version puts the filter up front:

<xsl:for-each select="$docs[someFilterExpression]">
<!-- Do something with current() -->
</xsl:for-each>

<!-- or you could do a simple apply-templates and have separate output templates  -->

<xsl:apply-templates select="$docs[someFilterExpression]" />

- You see? The xsl:if and xsl:choose constructs should largely be avoided for this kind of selection (IMO).

My suggestion regarding your second "problem" is, of course, to make sure that you filter the nodes from the start - then you'll have a simple way of testing for goal #1, and that your code will almost automatically take care of satisfying #2, too.

BUT: The thing that makes it hard to do in your code is all the comma-separated stuff, which isn't a good "data-type" for XSLT, so...

"I'll be back",

/Chriztian