Jacob Kjome wrote:
At 02:02 PM 4/16/2004 -0400, you wrote:
>The originator of this thread complained that Xerces would not allow
>file:/c:/test.xsd
>as a URI in a schemaLocation specification.
I've always seen _very_ strong recommendation to use
file:///c:/test.xsd
... and I had the impression that the version shown above was a
problem for
many tools, not just Xerces.
(Whether it *should* be a problem or not, I'm honestly not sure; I've
have
to reread the RFCs.)
Might want to tell that to Sun with their URL class. Calling
url.toExternalForm() always results in
"file:/c:/some/path/to/file.txt". Should they be returning it in
"file:///c:/some/path/to/file.txt" form?
Once upon a time I interpreted the RFC as allowing any odd number of /
characters after the scheme to precede a path, where an even number
would indicate the presence of an authority before the path. Everyone
comes away from the RFC with a different idea, however, and one just has
to adapt to whatever form software allows.
If Xerces disallows file:/path or interprets the first part of the path
as an authority, file a bug report.
Bob Foster
http://xmlbuddy.com/
|
