I believe that the XML Catalog bundled with XXE should resolve the
global URI for the DocBook XSL Stylesheets to their location within the
XXE distribution. This entry would look like:
<rewriteURI xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
uriStartString="http://docbook.sourceforge.net/release/xsl/1.65.1/";
rewritePrefix="docbook/xsl/"/>
to indicate the exact version that XXE is using, or possibly:
<rewriteURI xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
uriStartString="http://docbook.sourceforge.net/release/xsl/current/";
rewritePrefix="docbook/xsl/"/>
If you are not already convinced, read on for an argument for why this
is needed.
When writing a customization layer for the DocBook XSL Stylesheets
(DXS), a user may import the core and then override certain templates.
When importing the core of the package, a user can name the imported
stylesheet using the global name and then resolve that global name to a
local distribution. This is useful for all of the standard reasons that
controlled URI resolution is useful.
When working within XXE, the bundled XML catalog provides portability
for the resources distributed within XXE. It is possible to still get
access to the DXS distributed with XXE; they can be referenced using the
URI <xxe-config:docbook/xsl/docbook.xsl>. However, such a URI
effectively defeats portability for the stylesheet. I want to be able
to use the same stylesheet customization layer for a different toolchain
(such as a publishing backend) and have it function in both places.
In effect, what I want to be able to say is "import the DXS" and what I
am forced to say is "import XXE's DXS". With a catalog entry for the
global URI, I have the choice; I can either refer to the DXS directly
and allow XXE (or any other tool) to resolve that to a usable local
copy, or I can explicitly refer to XXE's local copy of the DXS.
Thank you for your consideration,
John L. Clark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20041104/965b1713/attachment.sig
