RE: [xsl] DTD validation with SVG graphics transformations

Subject: RE: [xsl] DTD validation with SVG graphics transformations
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Date: Fri, 4 Dec 2009 14:00:27 -0000
Yes, the XML parser will read the DTD - typically from a cache in the
nearest proxy server.

You can avoid this by using a catalog resolver to redirect the reference to
a local copy.


Michael Kay 

> -----Original Message-----
> From: Ylvisaker, Steve [mailto:steve.j.ylvisaker@xxxxxxxxxxxxx] 
> Sent: 04 December 2009 13:46
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] DTD validation with SVG graphics transformations
> I am currently using Saxon to perform transformations of SVG 
> graphics. All of the graphics contain a DOCTYPE reference to 
> the W3C DTD: <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" 
> "";>
> A question has come up in our technical review team regarding 
> the impact of this reference. Is the DTD some how 
> internalized in the transformation tools in general and Saxon 
> in particular or should we be establishing a local copy of 
> the DTD with the necessary DNS pointers and such? The trigger 
> for our concern was the following error message coming from a 
> Saxon transformation:
> Server returned HTTP response code: 503 for URL:
> Thanks in advance for any insight into what is really 
> happening in the background. Are we reading a DTD and if so, 
> from where?
> Steve
> Information transmitted by this email is proprietary to 
> Medtronic and is intended for use only by the individual or 
> entity to which it is addressed, and may contain information 
> that is private, privileged, confidential or exempt from 
> disclosure under applicable law. If you are not the intended 
> recipient or it appears that this mail has been forwarded to 
> you without proper authority, you are notified that any use 
> or dissemination of this information in any manner is 
> strictly prohibited. In such cases, please delete this mail 
> from your records.
> To view this notice in other languages you can either select 
> the following link or manually copy and paste the link into 
> the address bar of a web browser:

Current Thread