XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

On Oct 29, 2004, at 11:25 AM, Michael Kay wrote:

> It's to identify the object model. The architecture is that you can 
> have a
> number of XPath engines available, and each one says which object 
> models it
> supports, and you can then call a factory interface to ask for an XPath
> engine that supports your chosen object model.

Thanks for the clarification.

> Is your Saxon-to-XOM bridge now stable, by the way? I don't plan on
> releasing for a little while so there's no hurry.
>
> Mike

Have a look at the current state of affairs.
It passes the tests and I haven't seen any issue for the last few 
releases. IMHO, it's stable.
Wolfgang.

> > -----Original Message-----
> > From: Wolfgang Hoschek [mailto:whoschek AT lbl.gov]
> > Sent: 29 October 2004 18:46
> > To: Michael Kay
> > Cc: xom-interest AT lists.ibiblio.org
> > Subject: Re: [XOM-interest] URI for XOM XPath
> >
> > Michael,
> >
> > Is that per object model or per combination of object model / xpath
> > engine?
> > If it's the former, I'm happy with whatever Elliotte picks...
> >
> > Wolfgang.
> >
> > On Oct 29, 2004, at 10:22 AM, Michael Kay wrote:
> >
> > > The JAXP 1.3 API uses URIs to identify object models when
> > requesting an
> > > XPath engine, for example "http://java.sun.com/jaxp/xpath/dom";
> > > identifies
> > > the DOM object model.
> > >
> > > Could you please allocate a URI to identify the XOM model?
> > >
> > > Michael Kay
> > >
> > > _______________________________________________
> > > XOM-interest mailing list
> > > XOM-interest AT lists.ibiblio.org
> > > http://lists.ibiblio.org/mailman/listinfo/xom-interest