W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2004

RE: following/preceding-sibling shorthands in XPath 2.0

From: Alex Kodat <alex@sirius-software.com>
Date: Wed, 17 Nov 04 09:47:21 EST
To: mhk@mhk.me.uk
Cc: lholst@students.cs.uu.nl, public-qt-comments@w3.org, www-xpath-comments@w3.org
Message-ID: <E1CURRw-0006Sn-Si@frink.w3.org>

> I think that a lot of people feel that XPath syntax is terse enough already,
> and there will be little enthusiasm in the working groups for the
> introduction of further abbreviations. You can always create functions
> z:next(.) and z:prior(.) if you really need to save keystrokes.

I don't think the point of a terse syntax is necessarily to save keystrokes.
More important is readability. While XPath syntax is well defined, the
unabbreviated syntax is pretty tough sledding for mere mortals, like
myself, and the presence of unabbreviated syntax in the middle of
a bunch of location steps, definitely slows me down. Adding functions
only solves part of the problem, as it makes the programmer scanning
the code have to worry about what the heck the function does.

While you're correct about the problem with using the unary operator
for following-sibling and previous-sibling axes, it also strikes me
as a bit bizarre that such important axes don't have an abbreviated syntax.

Alex Kodat
Sirius Software

Note: I've cc'ed public-qt-comments@w3.org as Paul Cotton suggested.
      Sorry if I shouldn't have cc'ed www-xpath-comments@w3.org.
      Or maybe I shouldn't have cc'ed the former because the original
      note didn't go there?
Received on Wednesday, 17 November 2004 16:57:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:02 UTC