Michael Kay wrote:
> Yes, I think that's correct.
> To be honest, I've forgotten why the
> externalNamespaceResolver is there. Saxon itself doesn't
> ever use it. There was probably some use case involving an
> application that was able to supply a namespace resolver
> but wasn't able to enumerate the namespaces: I've no idea
> whether this use case is still relevant. You could
> probably ignore the external namespace resolver and just
> say that your code (whatever it's doing) doesn't support
Actually, I though to use it. Maybe describing a little
bit further what I'd like to do may help you to see if I go
the right way.
I'd like to develop a little tool for the Emacs editor.
To goal is to have a shell-like interface to evaluate XQuery
expressions (or a command interactively prompting for a
single expression to evaluate). I think this could be
interesting while developing with XML, to check something in
a file, instead of open it and looking for the right place.
But it wouldn't be interesting if we have to write all the
namespace declarations for each query. So I'll have command
to add namespace declarations interactively, during the
whole edition session. But also a command to remove a
namespace binding. And the only thing I found to be able to
remove bindings was to use the external resolver.
Furthemore, I think it is the right place for such
namespaces to be resolved: at the very end of the chain. If
the query contains bindings, they have to be used instead,
> P.S. to all readers of this list: I will be on vacation
> next week and may not respond to requests as quickly as
> usual. Please help each other if you can...
Have a good week, so. And see you at Prague.
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.