> Aha!! Now I finally understand (amazing how dense module maintainers
> can be sometimes ;-)
>
> Yes, I agree completely this type of high-level documentation is
> completely missing from Xerces-P/C/J
>
Yup, even the source code from the module is sometimes difficult to read.
> In Xerces, Parser::parse() does all the validation for you without
> needing to call the is_valid() method. (Just curious, why set
> validation(1) when you call is_valid() by hand? And what is the
> difference between validate() and is_valid()?).
The parser in LibXML only checks if your XML is well-formed.
> Depending on which subclass of Parser you are using (i.e. DOMParser,
> SAXParser, SAX2XMLReader, or IDOMParser) you would handle things
> slightly differently for the steps after handling the DTD, but they
> all handle DTD's the same.
>
Ok
> The simplest way to deal with DTD's is to use SYSTEM and make sure
> that the DTD's are where you say they will be. If not, then ou need to
> setup an EntityResolver. I believe this is all part of the XML spec,
> and so, although the other library is convenient, it's not actually
> implementing the spec...
>
Ah, so you can't do it in your set the DTD in your code. It depends on the
XML. But the XML gets send from somewhere else and I need to validate it as
it comes in. But I can't rely on the SYSTEM thingie to be correct...
> I'm afraid to say that Xerces.pm has not yet implemented
> EntityResolver's completely (oh the shame ....). All the framework is
> there. I just need to hook it up. I'll try to cut a release while I'm
> here at the Open Source conference.
No problem. For the moment I'll use the XML::LibXML module. But the xerces-p
module has nice prospects :)
Friendly greets.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
