Yep, I've been caught out a few times where the default predicate axis is
child but my brain is reading it as self and I'm pulling hair out knowing
there is something obvious wrong...
That and forgetting the $ on a variable so it gets interpreted as a node is
the other one :-)
Peter
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com]On Behalf Of
Michael Kay
Sent: Friday, 17 January 2003 4:07 a.m.
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] Abbreviated Syntax
Are there any advantages with unabbreviated syntax ?
It's sometimes clearer, for example I sometimes use x[child::y] for
emphasis. I would expect most processors would handle the two syntaxes
identically - it's just possible that a processor might use some
optimization for "//a" that it doesn't use for
"/descendant-or-self::node()/a", but it's unlikely.
Michael Kay
Software AG
home: Michael(_dot_)H(_dot_)Kay(_at_)ntlworld(_dot_)com
work: Michael(_dot_)Kay(_at_)softwareag(_dot_)com
e.g. When transforming, does it process faster? Is it more
standards compliant?
Below is an example of unabbreviated syntax
Abbreviated syntax: <xsl:value-of select="@number"/>
Unabbreviated syntax: <xsl:value-of select="attribute::number"/>
--
Best regards,
Arthur mailto:ArthurMaloney(_at_)seipas(_dot_)com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list