• To: xml-dev@l...
• Subject: RE: Problem with noNameSpaceSchemaLocation
• From: "Atchley, John" <John.Atchley@f...>
• Date: Tue, 12 Mar 2002 09:36:50 -0500

Hmmm, oops.  I just went back to check the case for absolute file refs and
realized that I was using file://... when I should have been using
file:///...  (Hey, when you guys get up to 15 strokes I'm bailing out to
drive a truck! <g>)

Anyway, that's what I get for relying on examples from various tutorials
instead of putting in the time to decipher the original recommendations.

John Atchley
Senior Software Analyst
Engineering and Design, Courseware Support
FlightSafety International, Inc.
mailto:John.Atchley@F...




-----Original Message-----
From: Richard Tobin [mailto:richard@c...]
Sent: Tuesday, March 12, 2002 8:17 AM
To: Atchley, John; Richard Tobin
Subject: RE:  Problem with noNameSpaceSchemaLocation


> If you use file://RelativePath.xsd it tries to
> open "CurrPath/file://RelativePath.xsd" for example.

As far as I can tell such relative URIs are not legal.  According to
RFC 2396, any URI with a scheme part (eg file:) is absolute.  The
relative URI would just be "RelativePath.xsd", and would only work if
the base URI had the file: scheme.

In fact, in "file://RelativePath.xsd" RelativePath.xsd should be
interpreted as host name!

Of course, turning it into CurrPath/file://RelativePath.xsd is bogus.

-- Richard

• Prev by Date: Re: Problem with noNameSpaceSchemaLocation
• Next by Date: Referencing an external DTD
• Previous by thread: Re: RE: (091)xml-dev(093) What happened to WAP
• Next by thread: Referencing an external DTD
• Index(es):
  • Date
  • Thread