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:
|   I never intended to make a full implementation of TR9401. What I have
| was enough for the existing SGML catalog deployed. But I made sure to
| implement XML Catalog fully, i.e. read and understand the spec and implement
| accordingly. And now I'm told that the spec suddenly incorporate TR9401
| while this was never mentionned before. No I don't like this.

I don't think you're being asked to implement TR9401. If you don't
implement it, and someone points to one, it won't be recognized as an
XML Catalog and you should treat it like a resource you couldn't
retrieve.

Is your concern interoperability or something else?


                                        Be seeing you,
                                          norm

- -- 
Norman Walsh <ndw@nwalsh.com> | Always do one thing less than you think
http://nwalsh.com/            | you can do.--Bernard Baruch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+f3QhOyltUcwYWjsRAntjAKCFR/ZlmqigO2m+jXVCNpS1cZ3iYACgl/8t
k8ghRqiwvsmCyHaqpIt1z+8=
=OPDO
-----END PGP SIGNATURE-----