This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: [Fwd: RE: catalogs support in Saxon]
- To: Kay Michael <Michael dot Kay at icl dot com>
- Subject: Re: DOCBOOK-APPS: [Fwd: RE: catalogs support in Saxon]
- From: Norman Walsh <ndw at nwalsh dot com>
- Date: Wed, 10 Jan 2001 15:01:27 -0500
- Cc: docbook-apps at lists dot oasis-open dot org
- References: <3A5CAC62.C99653DD@mandrakesoft.com>
| I don't intend to support SGML-like catalogs in Saxon unless and
| until W3C standardize them for use with XML. I hope that others can
Would you be satisfied by other industry support, such as OASIS?
| interface such catalogs using the URIResolver (and EntityResolver)
| mechanism which is already there in the product.
Setting aside for the moment my objection to your statement that
entityResolver() support is SGML-related :-), can I ask one clarifying
question?
The last time I checked, Saxon didn't use the entityResolver hook to
access documents referenced by xsl:import, xsl:include, or the
document() function, has that changed in recent releases?
(Note, also, that the entityResolver() can change the base URI so some
care has to be taken in order for it to be properly supported.
If I have <xsl:import href="foo/A.xsl"/> and the entity resolver
redirects that to "bar/A.xsl" then references *inside A.xsl* of the
form <xsl:import href="B.xsl"/> must resolve to "bar/B.xsl".
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | To create a little flower is the
http://www.oasis-open.org/docbook/ | labour of ages.--Blake
Chair, DocBook Technical Committee |