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 ;-)
>
>> Oh, and does anyone have a URL for a definition of an "XML Catalog"? I
>> haven't been able to find a spec for it and the implication is that they
>> aren't the same as ISO SGML Open Catalogs?
>
>The one I looked at was:
>
>http://home.ccil.org/~cowan/XML/XCatalog.html
Ok. I dug around XML-Deviant and XML-Dev archives a little, and I came
across a curious reference from April Y2K or so that claims Xerces (-J,
presumably) supports EntityResolution using XML Catalogs of the Cowan
variety.
Question: Is this correct?
Question: Does Xerces-C++ -- and, by extension, Xerces-P -- do that?
I'm guessing that the answer to the former is "Yes" but the answer to the
latter is "No", or you would have used that instead of futzing with your
own version using DOMParse in EntityResolver.t.
Given that, I'm continuing to tinker with my own Entity Manager in Perl.
A little study has also revealed that OASIS has a running Committee on
Entity Resolution using XML Catalogs that is about to publish a final
specification for the mechanism using a significantly different (from the
Cowant draft) syntax.
Question: Is it safe to assume that Xerces-* has not been updated to
use the new OASIS (draft) specification?
Another issue is that the above specification seems to require that XML
Catalogs be processed sequentially (i.e. the physical order in the file is
significant).
Question: Will this require the use of SAX rather then DOM interfaces?
And as if I hadn't exposed enough of my ignorance on the subject yet;
is there any reason to use SAX1 for new applications instead of SAX2? :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
