I suggest that you use the properties on the enclosing folder in the
XMLSpy browser to assign the schema.
That assignment will apply to every .xml file in that folder, but will
not cause any change in the xml instance document itself.
Best regards,
David Ezell
Message
From: xmlschema-dev-request (AT) w3 (DOT) org [mailto:xmlschema-dev-request (AT) w3 (DOT) org]
Behalf Tyson Tate
Sent: Wednesday, November 23, 2005 12:52 PM
To: xmlschema-dev (AT) w3 (DOT) org
Subject: Re: No, I Don't Want No Namespace!
That's what XMLSpy 2005 puts in when you assign a schema to it through
the GUI, so it appears that this is an XMLSpy 2005 issue. Can anyone
verify this?
-Tyson
Michael Kay wrote:
Your xsi:schemaLocation looks wrong. The first string should be the
namespace URI, that is http://www.xyzcorp.com/Vessel rather than
www.xyzcorp.com/Vessel. The second string should be a location URI
rather than a Windows filename. I suspect that XMLSpy lets you get
away with the incorrect location URI, but is tripping up on the
incorrect namespace URI.
Michael Kay
http://www.saxonica.com/

>Message
>From: xmlschema-dev-request (AT) w3 (DOT) org
>[mailto:xmlschema-dev-request (AT) w3 (DOT) org] Behalf Tyson Tate
>Sent: 21 November 2005 18:11
>To: xmlschema-dev (AT) w3 (DOT) org
>Subject: No, I Don't Want No Namespace!
>>
>
>>
><Vessel xmlns="http://www.xyzcorp.com/Vessel"
>xmlns:cdm=""
>xmlns:xsi=""
>xsi:schemaLocation="www.xyzcorp.com/Vessel
>C:\path\to\schema\Vessel2.xsd">