Multiple XSD Level for a single XML with multiple namespaces

[John Smith]

Ok, I am not sure if it is possible. But what I'm trying to do is
validate an XML file with out having to add namespace in the xml.

What I mean is lets say I have 2 XSD
they have different namespaces and lvl2 is used in lvl using the
import feature

lvl1.xsd
-> lvl2.xsd

the xml I would like to validate would be as follow

<level1>
<level2>
<string>hello</string>
<Number>10</Number>
</level2>
<level1>
right now I have to define the namespace of a level to to use the
sublevel tag that way:
....
<l2:string>hello</l2:string>
<l2:Number>10</l2:Number>
....

my problem is I don't want the guy who write the xml to be aware of
the structure I use for the XSD. and I want the possibility of having
multiple tags with the same name having different signification based
on where they are placed in the schema.

what I though of is in someway, if he find a tag <level2> it
automaticaly switch the default namespace to the level2 and so on
until it reach </level2> where it would switch back to the level1
namespace.

I think what I want should be pretty easy to do but I just can't
manage make that work.

Thx in advance for your help

[Zafar Abbas [MSFT]]

There is no way of directly validating your instance based on multiple
prefix mappings for a namespace. It is possible, though, for you to play
with the namespaces (via the API) to create and maintain context to achieve
this. Are you using MSXML or System.XML?

If you want the user to not *know* about the namespace in yoru schemas then
why dont you put the schema content in one schema with no targetNamespace?
or even in one commo namespace?

Zafar
"John Smith" <me*********@hotmail.com> wrote in message
news:71**************************@posting.google.c om...

Ok, I am not sure if it is possible. But what I'm trying to do is
validate an XML file with out having to add namespace in the xml.

What I mean is lets say I have 2 XSD
they have different namespaces and lvl2 is used in lvl using the
import feature

lvl1.xsd
-> lvl2.xsd

the xml I would like to validate would be as follow

<level1>
<level2>
<string>hello</string>
<Number>10</Number>
</level2>
<level1>
right now I have to define the namespace of a level to to use the
sublevel tag that way:
...
<l2:string>hello</l2:string>
<l2:Number>10</l2:Number>
...

my problem is I don't want the guy who write the xml to be aware of
the structure I use for the XSD. and I want the possibility of having
multiple tags with the same name having different signification based
on where they are placed in the schema.

what I though of is in someway, if he find a tag <level2> it
automaticaly switch the default namespace to the level2 and so on
until it reach </level2> where it would switch back to the level1
namespace.

I think what I want should be pretty easy to do but I just can't
manage make that work.

Thx in advance for your help

[John Smith]

well, my last message screwed when I tried to send it so I won't write
it again. But well thx for your input. I'll have to look how to do
that myself using System.XML.

Right now I'm only using the validator in Visual Studio .Net
(XML|Validate XML) but I get all kind of errors: the 'blablabla'
element is not defined but in XMLspy the schema is working perfectly.
They are not in the same project but they are part of the same
solution. So I'm kind of lost about what I'm doing wrong.

Anyway, thx for your help I'll look into that

"Zafar Abbas [MSFT]" <za****@microsoft.com> wrote in message news:<ua*************@TK2MSFTNGP12.phx.gbl>...

There is no way of directly validating your instance based on multiple
prefix mappings for a namespace. It is possible, though, for you to play
with the namespaces (via the API) to create and maintain context to achieve
this. Are you using MSXML or System.XML?

If you want the user to not *know* about the namespace in yoru schemas then
why dont you put the schema content in one schema with no targetNamespace?
or even in one commo namespace?

Zafar
"John Smith" <me*********@hotmail.com> wrote in message
news:71**************************@posting.google.c om...

Ok, I am not sure if it is possible. But what I'm trying to do is
validate an XML file with out having to add namespace in the xml.

What I mean is lets say I have 2 XSD
they have different namespaces and lvl2 is used in lvl using the
import feature

lvl1.xsd
-> lvl2.xsd

the xml I would like to validate would be as follow

<level1>
<level2>
<string>hello</string>
<Number>10</Number>
</level2>
<level1>
right now I have to define the namespace of a level to to use the
sublevel tag that way:
...
<l2:string>hello</l2:string>
<l2:Number>10</l2:Number>
...

my problem is I don't want the guy who write the xml to be aware of
the structure I use for the XSD. and I want the possibility of having
multiple tags with the same name having different signification based
on where they are placed in the schema.

what I though of is in someway, if he find a tag <level2> it
automaticaly switch the default namespace to the level2 and so on
until it reach </level2> where it would switch back to the level1
namespace.

I think what I want should be pretty easy to do but I just can't
manage make that work.

Thx in advance for your help

[Valentin]

Internally, when validating a schema, .NET call a function
Schema.Compile. If the schema contains any include or import, those
url references needs to be resolved.
If you are currently using .NET framework 1.0, be advised that .NET
framework 1.0 does not implement/call a default XmlResolver.
It means that all schema containing include or import would fail, .NET
will not be able to validate the file against the schema.
Those schema will be valid in XMLSpy. XMLSpy will also be able to
validate the file against the schemas.
If you are using .NET framework 1.0, even
implementing a custom XmlResolver will not work, because it will not
be called, the overloaded version of function XmlSchema.Compile with
the Xml Resolver, XmlSchema.Compile( ValidationEventHandler,
XmlResolver) did not exist in framework 1.0. In framework 1.0, one
trick to bypass the problem is to merge both file. You can do that
manually, but you can also do that programatically: load both files,
take the types (complex and simple types) definition from the second
schema. Add every type definition to the first file (Don't forget to
add the namespace definitions). Validate the file against that new
schema.[list:a3563162a1]In .NET framework 1.1, you can also implement your
own XmlResolver derived class.[/list:u:a3563162a1]