Isidor Zeuner wrote:
the shredding of multiple documents is solved by a batloop on the MIL level calling the xml shredder for each document separately. The DTD lookup is performed by libxml2 (not by Pathfinder).
libxml2 provides means to redirect remote DTDs to local copies, using catalogs (see [1]). So the intended way to cope with that situation would be to add the required DTD to your local XML catalog.
This is true but requires manual intervention and earlier the OP wrote: Roberto Cornacchia wrote:
What happens is that, for each xml file, the DTD is downloaded and shredded/used(?). It is not even cached (I tried using xquery_cacherules, but apparently it has no effect on DTDs).
Surely the appropriate component in the stack should be taking notice of HTTP Cache-Control[1] directives? Or is the DTD served without cache control, in which case the originators should be told. Then the system would behave sensibly without the need for manual intervention in every application to create a catalog. Cheers, Dave [1] http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic