> That seems like a pretty hard ask ... to be able to solve requirements
> before the community with the requirement comes to us. But I
> think that's
> a good argument in favor of XPath, thanks :) As the only way
> to be able
> to solve unknown requirements is to be flexible with a wide
> scope for how
> requests can be handled within a standardised framework.
General consensus seems to be for Xpath so I'll withdraw my objections.
But...
In general (and can we leave it mute whether Xpath is an example or not)
I'd still like to follow the principle of adding stuff to SRW to solve
existing requirements rather than following the Z39.05 model of
producing a highly versatile spec which can address new requirements
before they are formed but which doesn't get used since it is too
complex!
