OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [entity-resolution] (Fwd) Re: [entity-resolution] Mixing XMLCatalog and TR9401


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

/ "Lauren Wood" <lauren@textuality.com> was heard to say:
[...]
| From:           	Daniel Veillard <veillard@redhat.com>
[...]
|   The fundamental problem is really an interoperability problem,
| and at 2 levels:
|     - for the XML Catalog implementations, if Sun's and Apache's 
|       implementations allow an XML Catalog to point to a TR 9401
|       subtree well, other implementations will have to do the same
|       or face requests from users like I did.

If I've personally contributed to this problem by publishing a TR9401
catalog somewhere, well, I'd be happy to unpublish it :-)

|     - for XML deployement, building XML catalogs is one good way
|       to ensure that no SGML resource is referenced by mistake,
|       we had this problem (in Red Hat 7.2 if I remember correctly)
|       of pointing to the ISO SGML resources for XML tools and that
|       was of course a disaster, separating cleanly the catalogs (and
|       the tree of resources) is something which can help prevents
|       those mistakes.

Yes, and the ability to point to both kinds of resources with the same
set of catalog files is a feature. Not a feature that I'm using at the
moment, I admit, but it would be a feature if I had an SGML tool that
understood XML Catalogs.

|   A separate issue I would like to point out, is that in the Linux 
| framework I tried to get XML default catalogs to get located in 
| /etc/xml/catalog , the reason is that one cannot expect all users to
| reliably have an environment variable or another mechanism to 
| indicate
| to the XML tools where to lookup catalogs by default. Having a 
| predefined
| path is useful to get some default system wide processing. 
| Traditionnally
| the SGML tools have used "SGML_CATALOG_FILES" environment variable, 
| for
| libxml2 I used "XML_CATALOG_FILES" as the environemnt variable 
| allowing
| to override the default /etc/xml/catalog,  maybe your group could
| suggest where to find the system catalog entries, this would 
| definitely help
| on interoperability, I understand that /etc/xml/catalog is very Linux
| specific (won't work on Windows and I think Sun changed that when 
| embedding
| libxml2) still at least suggesting an environment variable would be 
| nice.

Suggesting and environment variable seems reasonable.

                                        Be seeing you,
                                          norm

- -- 
Norman.Walsh@Sun.COM    | Mankind are always happy for having been
XML Standards Architect | happy; so that if you make them happy now,
Web Tech. and Standards | you make them happy twenty years hence by the
Sun Microsystems, Inc.  | memory of it.--Sydney Smith
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+gLUpOyltUcwYWjsRAqeIAJ9PsogHz9ek8ztpZ4LE7gD0asb3oACglerA
gH7DjAw4KPQAqnepbRjTL1s=
=VOlJ
-----END PGP SIGNATURE-----


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]