Lib::XML::Schema validation fails with UNC path

rovf has asked for the wisdom of the Perl Monks concerning the following question:

I have a schema file, which uses

<xs:include schemaLocation="FILENAME.xsd"/>
[download]

to include common definition. The included file is located in the same directory as my schema file, and XML::LibXML::Schema is used to validate my XML files (running Perl 5.8.8 on Windows). This works well if the xsd file is located on the local drive. However, if the schema file is located on a file share and accessed via UNC path, I get the error message "Element '{http://www.w3.org/2001/XMLSchema}include': Failed to parse the XML resource 'FILENAME.xsd'.". Any idea why this doesn't work?

--
Ronald Fischer <ynnor@mm.st>

Comment on Lib::XML::Schema validation fails with UNC path Download Code

Replies are listed 'Best First'.
Re: Lib::XML::Schema validation fails with UNC path by choroba (Cardinal) on May 05, 2011 at 14:59 UTC
As far as I know, XML::LibXML supports URI's and file paths. I am not sure it supports UNC paths, though. Does perl support them?	[reply]
Re^2: Lib::XML::Schema validation fails with UNC path by Anonymous Monk on May 06, 2011 at 01:08 UTC
FWIW, perl uses OS calls, so if the OS supports UNC paths, perl supports them	[reply]
Re^2: Lib::XML::Schema validation fails with UNC path by rovf (Priest) on May 06, 2011 at 08:03 UTC
Perl 5.8.8, by and large, already supports UNC pathes, though I already encountered a few glitches in the past. -- Ronald Fischer <ynnor@mm.st>	[reply] [d/l]
Re: Lib::XML::Schema validation fails with UNC path by ikegami (Patriarch) on May 06, 2011 at 04:57 UTC
Presumably because of a bug. You didn't give us anything to work with, so we can't test with our versions and we can't play around to find workarounds or the problem.	[reply]
Re^2: Lib::XML::Schema validation fails with UNC path by rovf (Priest) on May 06, 2011 at 08:00 UTC
I didn't expect you to work or test for me (I think this is, first of all, my duty - after all I can dig into the Lib::XML code myself). I just wanted to know whether this is a known issue. If really get stuck, I will, of course, post a simple example program and will ask you to see whether you can replicate the issue. -- Ronald Fischer <ynnor@mm.st>	[reply] [d/l]