On 01.08.01 at 23:32, Jason E. Stewart <[EMAIL PROTECTED]> wrote:
>Check out t/EntityResolver.t for an example of using XML Catalog. This is
>pretty rudimentary, but it does what you asked for (ask and ye shall
>recieve ;-)
Thanks jas, that's exactly what I was looking for!
>The one I looked at was:
>
>http://home.ccil.org/~cowan/XML/XCatalog.html
Thanks. I managed to find an up-to-date spec at OASIS (published yesterday,
no less!) which differs pretty heavily from that early draft. When I can
scrape together the time I'm going to look into writing support for the
full spec (though possibly just a subset at first) for Xerces-P (no
guarantees tho�).
I'm thinking a module like XML::Xerces::<EntityResolver> (suggestions for
name to use gratefully appreciated! ;D) that you init and get back a
resolver you can feed to Xerces which in turn takes a FPI or SI and returns
an InputSource.
Suggestions for namespace to use and API details welcome! :-)
I'll probably ask a bunch of Stupid Questions� here until I figure out what
I need of how to interact with Xerces. Apologies in advance if I try your
patience. :-)
I'll post details when I have time and code -- :-) -- but you may want to
consider whether or not you want this for Xerces-P -- and whether it would
be sample code or a companion module -- because that will influence how I
design this beastie. Are there any license issues I should be aware of?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
