[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: missing XPath axis
I think it's good to keep number of alternate language syntax (i.e the built-in language keywords) to minimum, if they achieve the same purpose. This also helps with following aspects, 1) reduces the construction complexity/effort of the language processor 2) reduces the functional complexity, verbosity and learning curve for the language For the case of your proposed syntax 'child-or-self::', I think the following (already available) XPath expression may also serve the purpose, .|node() On Sat, Sep 24, 2011 at 8:28 PM, Johannes.Lichtenberger <Johannes.Lichtenberger@uni-konstanz.de> wrote: > Hello, > > I just wandered what was the reason for the authors of the XPath > recommendations to not include the XPath axis 'child-or-self::' as a > counterpart to 'descendant-or-self::' in XPath 1.0, 2.0 or at all? > > Although I'm not sure if this is the appropriate mailinglist to ask -- > just in case, please point me to the right mailinglist. > > I know it's doable via 'expression/(self::node()|node())' but I think > that's more or less a work around to the lack of the 'child-or-self::' axis. > > kind regards, > Johannes -- Regards, Mukul Gandhi
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|