title: Relative path for xsl:import or xsl:include
body: <p>I am trying to use VBScript to do an XSLT transform on an XML object.<br>
  The XSL file I'm translating includes the <code>&lt;xsl:import href="script.xsl"/&gt;</code> directive. If I use the absolute URL (<code>http://localhost/mysite/script.xsl</code>), it imports the style sheet fine; however, if I use the relative path (<code>script.xsl</code>) it reports "resource not found." I need to be able to port this amongst a set of machines, so I need to be able to use the relative URI. Any suggestions?</p>
  
  <p>Notes:</p>
  
  <ul>
  <li>VBScript file is at <code>http://localhost/myscript.asp</code></li>
  <li>first XSL file is at <code>http://localhost/mysite/styles.xsl</code></li>
  <li>second XSL file is at <code>http://localhost/mysite/script.xsl</code></li>
  <li>using the relative path <code>mysite/script.xsl</code> also does not work</li>
  </ul>
  
  <p>Addendum:</p>
  
  <p>Thanks, everyone, for your answers. The more I dig into the code that is doing this, the stranger it is. <code>myscript.asp</code> is a rather unusual compilation of code. What happens is <code>styles.xsl</code> is included in the HTML output of <code>myscript.asp</code> as an XML chunk (<code>&lt;xml src=...&gt;</code>) and then that chunk is loaded as a stylesheet, using VBScript, on the client side. This stylesheet is then used to transform an XML chunk that is retrieved via XMLHTTP. So the problem is the context of <code>styles.xsl</code> is the HTML on the client side and has no relation to where <code>script.xsl</code> is.</p>