ax wrote:
xmlns:address=" C:\Test\file_ad dress.xsd"
xmlns:hobby="C: \Test\file_hobb y.xsd"
Don't confuse namespace names and schema locations. A namespace is not
guaranteed to be the location of the schema, and in fact more commonly
is NOT.
And that's a broken namespace name in any case. Namespace names should
be absolute URI references; the use of relative references was
DEPRECATED after a long and painful debate which concluded that there
was no agreed-upon way to interpret them. Unless you're considering C:
to be a URI scheme -- which I doubt! -- this filename is not a URI. You
meant "file:///C:\Test\file_ad dress.xsd", and even that is a VERY poor
choice for a namespace name since it's too likely that someone else may
use the same string. Pick a real URI based on a domain name you control,
to ensure against namespace collision.
How can i formulate
xmlns:address=" blablablabla\fi le_address.xsd" to look in the SAME
folder as the XML is located?
Good example of why not to confuse these.
Namespace names should be absolute URI references; the use of relative
references was DEPRECATED after a long and painful debate which
concluded that there was no agreed-upon way to interpret them. But you
want a relative reference to your schema.
Divide the issue. Use a real URI for the namespace name, as discussed
above, and then provide additional direction for where to look for that
schema, typically by using the xsi:schemaLocat ion attribute.
http://www.w3.org/TR/2004/REC-xmlsch...schemaLocation
If XML Spy doesn't support schemalocation or some equivalentmecha nism
for distinguishing between a namespace name and the schema which defines
that namespace -- if it insists that the namespace is the schema
location -- it's broken. Change tools.
--
Joe Kesselman / Beware the fury of a patient man. -- John Dryden
