- From: <edsimon@xmlsec.com>
- Date: Thu, 2 Aug 2001 15:01:08 -0400
- To: John Boyer <JBoyer@PureEdge.com>, merlin <merlin@baltimore.ie>
- Cc: reagle@w3.org, bdournaee@rsasecurity.com, w3c-ietf-xmldsig@w3.org
Thanks John, I was always curious why the XSLT identity transform specified "node() | @*" if node() matches attributes. I think your explanation solves the mystery. Ed +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Hi Ed, <ed> One more question, is node() in XPath supposed to match attributes? When I read XPath, it seems like it should but my experience with XSLT makes it seem like node() matches all node types but attributes. </ed> <jb> node() will match anything, but the problem is that it will only match nodes on the axis being used. The axes for elements (child, descendant, ancestor, parent, etc.) purposefully exclude attributes and namespaces. However, if you are on an attribute or namespace axis, then node() matches the nodes on that axis. So, node() is kind of useless on these axes because the axes don't contain multiple types of nodes. </jb> ----------------------------------------------------------------------------------------------- Ed Simon XMLsec Inc. Interested in XML Security Training and Consulting services? Visit "www.xmlsec.com".
Received on Thursday, 2 August 2001 15:02:19 UTC