DOCBOOK-APPS: Re: XML catalog resolution problems

[Norman Walsh <ndw at nwalsh dot com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ "Jeanson Mauritz" <Mauritz.Jeanson@iom.sorman.se> was heard to say:
| What is the reason for requiring EntityResolver to always return 
| fully resolved system IDs in the first place? Why did Norm lose 
| the argument?

I'm not sure I can answer this question in a completely objective way.
I think the answer boils down to this: the SAX folks made some
decisions about their API in the V1 days and unfortunately no one
noticed the places where the decisions they made were going to impact
proper functioning of a resolver. Because SAX is very popular, and
perhaps because they disagree that their API is broken, they are
unwilling to change the public API. So if you're going to use SAX,
you're stuck with a broken API.

I'm hoping to move away from SAX and start using the Xerces Native
Interface myself. XNI exposes all of the events that occur and will
allow me to do some quite nice things (like profile at the parser
level, normalize namespace prefixes, implement XInclude before DTD
validation, etc.).

                                        Be seeing you,
                                          norm

- -- 
Norman Walsh <ndw@nwalsh.com>      | The common excuse of those who
http://www.oasis-open.org/docbook/ | bring misfortune on others is that
Chair, DocBook Technical Committee | they desire their
                                   | good.--Vauvenargues
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+OnNROyltUcwYWjsRAqugAJ9BR3af4TrHrgnZxbjSnl4+PhdHIACeMbDQ
AFPv47FNp+MT/imRN/svs0A=
=9iUM
-----END PGP SIGNATURE-----