XPath Binding API (Was: XPattern Specification)

[Alan Gutierrez <alan-xml-dev@engrm.com>]

* Karl Waclawek <karl@waclawek.net> [2005-01-17 10:23]:
> Alan Gutierrez wrote:
> >* Karl Waclawek <karl@waclawek.net> [2005-01-17 09:16]:
> >
> >
> >>> 4. Position counters (to enable position predicates and
> >>> position()
> >>
> >>>function)
> >>
> >>Especially for a streaming processor, should the goal of a pattern
> >>matching language not be, to allow for flexible cooperation
> >>between what the language does and what the handlers do?
> >
> >
> >    Brings me back to my suggestion for a generic XPath binding API.
> >
> >    public interface Function {
> >        public Node invoke(NodeList arguments);
> >    }
> >
> >    Works for Java.
> >
> >    What works across all languages?

> If one "language" needs to interact with multiple other
> languages, then what we are talking about is multiple
> "lanuage bindings".

    I'm talking about a SAX like API that defines an API that is
    a guideline for different langauges. SAX was specified in Java,
    but was designed in such a way that other langauges have a
    SAX API that is similiar to the Java SAX API.

    I'm looking at Saxon, Jaxon, and Xalan, and they all have a
    different Java language binding for XPath, which is annoying for
    me as an application developer.

--
Alan Gutierrez - alan@engrm.com