It's nice to see that XMLSpy is getting better at reporting errors in your
schema!

The value of schemaLocation is a sequence of pairs of URIs: first the
namespace URI, then the URI of a schema document for that namespace. I don't
know what you intended by supplying a list of three URIs, so I can't tell
you how to correct it.

There's another problem here, which is that you're not supplying a URI at
all, but a Windows file path. That's wrong according to the W3C products,
but some products, including probably Altova, will let you get away with it.
However, it also looks to me as if your filename might have a space in the
middle of it. That will certainly confuse the parsing. If you use URIs, you
can replace the space by %20, but I've no idea if that works when you are
supplying filenames, as it's outside the scope of the W3C specifications.
You'll have to ask Altova.


> Unfortunately, I am not allowed to modify the xml documents 
> further upstream to remove that extra path before it gets to 
> me; it is used by a third party and would break stuff on 
> their end apparently. Am I SOL??
> 

I don't know what SOL means (not trained in text shorthand...). However, all
the benefits of using standards in an IT architecture are lost if you start
accepting stuff that doesn't conform to the standards. Fixing it at source
is the right thing to do; patching it downstream is short sighted, and is
something that will cost you dearly in the long term.

Michael Kay
http://www.saxonica.com/ 


From siva@d... Sun Mar 30 09:05:40 2008
Received: from farnsworth.w3