[
Lists Home |
Date Index |
Thread Index
]
> Seems like most folks are happy with 1.0 (or at least
> are not too unhappy with it). 2.0 just seems to lose much of
> the simplicity and -value- that XPath 1.0 has for many developers.
Xpath2 as currently drafted in the working draft is basically unusable.
However I'm still hoping that Xpath2 as it finally emerges will be a
usable extension of Xpath2 with regexp and date support and one or two
extra useful operations like "is" (node equality) and unicode and
collation aware string ordering.
The simplest solution is just to move the more horrible bits ito the
xquery-only part of the documents. That would leave Xquery as being in
the same (unpleasant) state, but I'm less worried about that. Xquery is
designed as a top level language so at least it does not affect anything
else, but Xpath is a general purpose language designed to be embedded in
other things, and a bloated XPath2 would in the end affect not only XSLT
(the first casualty) but Xpointer, DOM, ... They may not immediately
pick up on Xpath2 but there would be continual pressure to update any
API based on Xpath 1.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
|
