Tim Hibbs schrieb am 17.02.2010 um 16:52:12 (-0600): > Michael, > > Many thanks for the feedback.
Tim, you're very welcome. > Prior to my solicitation for help from this group, I'd read through > (but not fully understood) the book "Definitive XSLT and Xpath" by G. > Ken Holman. Ken Holman also highly recommended. > I'm not really clear WHY we need a namespace for the project I'm > working on, so I'll soon be trying to process without a namespace > specifier to see if that makes things easier to work with. Quite often, namespaces aren't really needed, but people will still put them there because that looks professional. And in the end it maybe is. Anyway, namespaces aren't terribly complicated for the user, so my advice is to just accept their existence and get used to them. > I will take your advice and review the built-in template rules (Nathan > also provided some useful information on that in one of our exchanges) > as well as the identity template. I'm not sure what the latter is at > this point, as I don't recall seeing that phrase before. <xsl:template match="@*|node()"><!-- identity template --> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> This is it. It matches everything and copies everything. The usefulness of this comes to bear when you want to make small modifications to a document. Say, filter out all <odd> elements, or take away bla/@blub attributes. You can then define exceptions: <xsl:template match="odd | bla/@blub"/><!-- just drop them --> Or skipping the element while continuing to process the children: <xsl:template match="odd"> <xsl:apply-templates/> </xsl:template> -- Michael Ludwig