XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

Elliotte,

Just to let you know that the download links are inconsistent.
The xom homepage has two sections where code can be downloaded: near the 
top as well as on the right navigation bar. The one on the top is out of 
date (points to d21).

Wolfgang.

xom-interest-request AT lists.ibiblio.org wrote:
> Send XOM-interest mailing list submissions to
>         xom-interest AT lists.ibiblio.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.ibiblio.org/mailman/listinfo/xom-interest
> or, via email, send a message with subject or body 'help' to
>         xom-interest-request AT lists.ibiblio.org
>
> You can reach the person managing the list at
>         xom-interest-owner AT lists.ibiblio.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of XOM-interest digest..."
>
>
> Today's Topics:
>
>    1. XOM API stability (Krueger, Carsten)
>    2. XOM 1.0d22 posted (Elliotte Rusty Harold)
>    3. Re: XOM API stability (Elliotte Rusty Harold)
>    4. Re: XOM API stability (John Cowan)
>    5. Re: XOM API stability (Elliotte Rusty Harold)
>    6. Re: XOM API stability (John Cowan)
>    7. Re: XOM API stability (Elliotte Rusty Harold)
>    8. Re: CanonicalXMLSerializer exceptions (Janek Bogucki)
>    9. Re: CanonicalXMLSerializer exceptions (Elliotte Rusty Harold)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 12 Nov 2003 17:48:06 +0100
> From: "Krueger, Carsten" <ckr AT ti.com>
> Subject: [XOM-interest] XOM API stability
> To: "'xom-interest AT lists.ibiblio.org'"
>         <xom-interest AT lists.ibiblio.org>
> Message-ID:
>         <23FC7B6A090ED311A7F70000F8CB3A5B0DF37089 AT dfre02.itg.ti.com>
> Content-Type: text/plain;       charset="iso-8859-1"
>
> Hi,
>
> I wonder how stable the XOM API is. Are there any predictable changes
> in the next versions ?
>
> We are currently using JAXB 1.0 (Early Access) which seemed to do what
> we want a while ago. It's only now that we had to discover that it is
> buggy and even worse it's successor has a completely different design
> and API - which would force us to completely rewrite our code.
>
> XOM seems very promissing. Before trying to port our code to it I want
> to insure as much as possible that we are not running into the same
> problem again.
>
> Thanks for your help.
>
> Carsten
>
> ------------------------------
>
> Message: 2
> Date: Wed, 12 Nov 2003 12:43:14 -0500
> From: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
> Subject: [XOM-interest] XOM 1.0d22 posted
> To: xom-interest AT lists.ibiblio.org
> Message-ID: <p06002003bbd81f37147d@[192.168.254.4]>
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
> XOM 1.0d22 has been posted in the usual location:
>
> http://www.cafeconleche.org/XOM/
>
> This is a fairly major release that accumulates many changes that 
> have gone into CVS over the last couple of months.  The proximate 
> cause for this release was the new XInclude working draft which makes 
> a number of changes to XInclude syntax. This release supports the 
> *old* XInclude syntax and 2001 namespace URI. Probably the next 
> release will only support the new XInclude syntax and namespace URI.
>
> There are a number of breaking changes in this release. Most importantly:
>
> 1. ParseException has been renamed ParsingException
> 2. NodeList has been renamed Nodes.
>
> There are also a number of new features including:
>
> 1. The Builder can now validate documents without rejecting invalid 
> but well-formed documents.
> 2. Subclassing of Serializer is much easier
> 3. DOMConverter can now convert individual DOM nodes into XOM 
> objects. It is no longer limited to converting entire documents.
> 4. Serializer can normalize its output using Unicode normalization form C.
>
> And of course there are lots of new unit tests, sample programs, and 
> bug fixes. Complete details can be found on the web page.
>
> Please pound on it and let me know of any problems you find. If 
> there's nothing showstopping, I'll announce it more broadly on Cafe 
> con Leche in the next day or two.