Re: [entity-resolution] Mixing XML Catalog and TR9401

[Norman Walsh <ndw@nwalsh.com>]

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

/ Daniel Veillard <veillard@redhat.com> was heard to say:
| On Mon, Mar 24, 2003 at 01:09:53PM -0500, Norman Walsh wrote:
[...]
|> I'm pretty confident that I implemented them with exactly the same
|> code base. I have a loader class that transforms either catalog format
|> into an internal representation and that representation is used for
|> processing.
|
|   Hum, for me XML Catalogs can be computed progressively, and I do this,
| while the TR9401 can't and I first parse them all and simply build a
| couple of hash table.

You *cannot* implement catalogs with a couple of hash tables. The
interaction of public and system identifiers with override makes that
impossible.

|   Even if I have a huge XML Catalogs I usually don't need to parse anything
| for it until it's really needed, and that's different processing wise.

Right. There's no reason to trace down nextCatalog entries until you have to.

                                        Be seeing you,
                                          norm

- -- 
Norman Walsh <ndw@nwalsh.com> | Of all lies, art is the least
http://nwalsh.com/            | untrue.--Flaubert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+f13fOyltUcwYWjsRAj0NAJ9mPLJ1UsltbqqPUCCDiGAsnW/XQgCff6Xw
hULHDiAY2D+jnR22w1VulDI=
=pjzr
-----END PGP SIGNATURE-----