XOM API for Processing XML with Java

[Peter Murray-Rust <pm286 AT cam.ac.uk>]

The problem is that the original document is copyright and chemistry
publishers are absurdly possessive. By posting the URL for the external DTD
you know as much as I do. The internal DTD subset consisted of about 6 NDATA
entities (to TIFF files) and I can find it if toy wish but deleting it made
no difference - the problem seems to occur without an explicit internal DTD
subset.

The file b511922g.xml was what I posted to the list - as small as possible -
one DOCTYPE, and one single toplevel element. I stripped it down but the
error persisted.

P.



On Wed, Sep 16, 2009 at 11:22 AM, Elliotte Rusty Harold
<elharo AT ibiblio.org>wrote:

> On Tue, Sep 15, 2009 at 7:56 AM, Elliotte Rusty Harold
> <elharo AT ibiblio.org> wrote:
> > I know what's happening. It is a XOM bug, not a Xerces bug.
> >
>
> Actually it may be a Xerces bug after all, albeit an old one and one I
> can work around. The problem is likely that Locator.getSystemID
> returns a URL when called from startDocument but null when called from
> within the internal DTD subset. It should return the same value both
> times, either null or non-null.
>
> --
> Elliotte Rusty Harold
> elharo AT ibiblio.org
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest
>



-- 
Peter Murray-Rust
Reader in Molecular Informatics
Unilever Centre, Dep. Of Chemistry
University of Cambridge
CB2 1EW, UK
+44-1223-763069