And now for a second answer....

Mulberry Technologies (the folks who host this list) has a very good quick 
ref sheet for XSLT and XPath:

http://www.mulberrytech.com/quickref/XSLTquickref.pdf

It is definitely worth getting to know well.

Jay Bryant
Bryant Communication Services
(presently consulting at Synergistic Solution Technologies)




"Mike Schinkel" <mikes@xxxxxxxxx> 
08/26/2005 08:43 AM
Please respond to
xsl-list@xxxxxxxxxxxxxxxxxxxxxx


To
<xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
cc

Subject
RE:  Transform XML to XML






Thanks. 

I'm still confused by ".", "*", "node()", etc.  I've read all the
definitions, but somehow I can't grok them.  Any thoughts?

-Mike

-----Original Message-----
From: David Carlisle [mailto:davidc@xxxxxxxxx] 
Sent: Friday, August 26, 2005 4:54 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Transform XML to XML


                 I guess, like security best practices, my mindset is 
"don't
       allow it unless I explicitly ask for it." 
                 But I guess it doesn't work that way so I shouldn't fight 
it.


I typically begin every stylesheet with a template that looks like

<xsl:template match="*">
<xsl:message>Unsupported element: <xsl:value-of
select="name()"/></xsl:message> </xsl:template>


and so have to keep adding templates until my stylesheet stops moaning
on all test cases.


David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. For more information on a proactive anti-virus
service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________