Re: \

> No, but it  has a _single_ path component called "\data\file.xsl" so if
> that file has an <xsl:include href="foo.xsl"/> then foo.xsl is a
> relative uri that corresponds to
> "http://example.com/foo.xsl"
> which probably is not what was intended.

No,

http://example.com/\data\file.xsl/../foo.xsl

file -> \data\file.xsl/../foo.xsl

Then, in case the filesystem uses backslashes as path separators, 

file -> \data\file.xsl\..\foo.xsl

Then, in case  .. means one level up, as it is in the case of Win32,
x\.. are removed (where x is a file name constitutient)

file -> \data\foo.xsl

Exactly what was required.

I don't think .. has special meaning in URLs. In file names, it only
has special meaning under Win32 and similar systems, where it means 'one level up'.
If you type 

c:\winnt\system32\abracadabra\..\cmd.exe

on a Windows box, cmd.exe will execute.

In a traditional Unix file system, '..' is a regular name, so under Unix, .. are not reduced
with the previous component. If a directory does not have a '..' entry, then you cannot go up.

David

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list