- From: Mukul Gandhi <mukul_gandhi@yahoo.com>
- Date: Wed, 16 Feb 2005 08:52:11 -0800 (PST)
- To: public-qt-comments@w3.org
Hello, I have a suggestion for XPath 2.0 language! I am refering to the latest Working Draft of XPath 2.0(Feb 11 2005') at URL http://www.w3.org/TR/xpath20/ Presently XPath 2.0 defines the following Axes - 1) ForwardAxis ----------- child descendant attribute self descendant-or-self following-sibling following namespace 2) ReverseAxis ----------- parent ancestor preceding-sibling preceding ancestor-or-self I feel the need for 2 more Axes definitions; namely - following-sibling-or-self , and preceding-sibling-or-self Just like we have descendant-or-self and ancestor-or-self , why should not we also have following-sibling-or-self and preceding-sibling-or-self .. Sometimes, we need this functionality, and we have to do workaround like - self | following-sibling , and self | preceding-sibling i.e. we have to use the union (|) operator.. I feel, providing following-sibling-or-self and preceding-sibling-or-self will make Axes definitions more complete.. If these new Axes cannot be incorporated, probably descendant-or-self and ancestor-or-self Axes should be deprecated (just like the namespace axis is deprecated in XPath 2.0).. I also feel, if following-sibling-or-self and preceding-sibling-or-self could be justified , then we should also have self version for child, following, parent and preceding Axes (i.e. child-or-self, following-or-self, parent-or-self and preceding-or-self) ! Probably, adding so many additional -or-self Axes will confuse users; so it will be best, if we should deprecate existing descendant-or-self and ancestor-or-self Axes .. (a workaround with union operator will still work).. Regards, Mukul __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
Received on Wednesday, 16 February 2005 16:52:47 UTC