W3C home > Mailing lists > Public > www-xpath-comments@w3.org > October to December 1999

Re: lack of if/else?

From: Mark D. Anderson <mda@discerning.com>
Date: Sun, 14 Nov 1999 21:37:33 -0800
Message-ID: <00ca01bf2f2b$872e2230$0200a8c0@mdaxke>
To: "James Clark" <jjc@jclark.com>
Cc: <www-xpath-comments@w3.org>

> It's on the list of features for future versions (see the Appendix in
> the XSLT spec).

Seems it'd help future generations if that appendix were split
into things applicable to xpath, and things applicable only to
xslt. xpath has implications for several other efforts, obviously.

things in that appendix that strike me as xpath issues are (quoting that text):
- a conditional expression;
- a way to get back from an element to the elements that reference it (e.g. by IDREF attributes
- support for regular expressions for matching against any or all of text nodes, attribute values, attribute names, element type
names;
- case-insensitive comparisons;
- normalization of strings before comparison, for example for compatibility characters
- allow unions in steps (e.g. foo/(bar|baz));
- a way to group together consecutive nodes having duplicate subelements or attributes;

that is about a third of the issues.

in particular, in this case it seems like a more significant issue
for xpath than xslt, since xslt has xsl:if and xsl:choose, as baroque
as they may be.

-mda
Received on Monday, 15 November 1999 00:38:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 October 2007 16:05:53 GMT