xsd:any help needed

[Robert Rolls]

I've got the following really simple schema :

<?xml version="1.0" ?>
<xs:schema targetNamespace ="urn:503A2B 4E-B364-47a4-AE5C-16E727275A70"
xmlns:mstns="ur n:503A2B4E-B364-47a4-AE5C-16E727275A70"
xmlns="urn:503A 2B4E-B364-47a4-AE5C-16E727275A70"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
attributeFormDe fault="qualifie d" elementFormDefa ult="qualified" >
<xs:element name="SMSAdapte r" >
<xs:complexType >
<xs:sequence>
<xs:element name="phone" type="xs:string " minOccurs="0" />
<xs:element name="message" type="xs:string " minOccurs="0" />
<xs:any namespace="##an y" processContents ="skip" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
When I read the following xml

<?xml version="1.0" encoding="utf-8" ?>
<sms:SMSAdapt er xmlns:sms="urn: 503A2B4E-B364-47a4-AE5C-16E727275A70">
<sms:phone>0401 328893</sms:phone>
<sms:message>So uth Africa 256/6 after 65 overs</sms:message>
</sms:SMSAdapter>

I get the error

The content model must be deterministic. Wildcard declaration along with a
local element declaration causes content model to become ambiguous. An error
occurred at file:///D:/Adapter.xsd(4, 4).

What exactly is wrong with this I need the schema to be expanded with
elements I don't understand or care about hence the xsd:any element.

Please help
Robert.

[Oleg Tkachenko [MVP]]

You schema isn't deterministic. That's it. Remove minOccurs="0" on
message element definition to make it deterministic.
--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com

[Robert Rolls]

Can you explain a little more in detail I'm a complete idiot when it comes
it Xml Schema.

Thanks
Robert.

"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!P LEASEtkachenko. com> wrote in message
news:Oc******** ******@TK2MSFTN GP11.phx.gbl...

You schema isn't deterministic. That's it. Remove minOccurs="0" on
message element definition to make it deterministic.
--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com

[Daniel Cazzulino [XML MVP]]

The WXS processor needs to know which schema particle it's validating an
element agains. So, in your schema, the following sequence causes a problem:

<xs:element name="phone" type="xs:string " minOccurs="0" />
<xs:element name="message" type="xs:string " minOccurs="0" />
<xs:any namespace="##an y" processContents ="skip" />

When the WXS processor finds an element "phone", how does it know whether it
should be validated against the optional (minOccurs="0") element or the
##any element? Being optional means that it could be validated by any. One
way of disambiguating the schema is to make the xs:any element be anything
on any namespace other than yours. This way, the processor knows that a
phone element in your namespace must be validated against your schema. And
any other elements NOT in your namespace should be skipped. That is, the
schema became deterministic with respect to the xs:any element. You can do
so by setting:

<xs:any namespace="##ot her" processContents ="skip" />

--
Daniel Cazzulino [XML MVP]
Lagash Systems SA
http://weblogs.asp.net/cazzu

"Robert Rolls" <rr**@yahoo.com > wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

Can you explain a little more in detail I'm a complete idiot when it comes
it Xml Schema.

Thanks
Robert.

"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!P LEASEtkachenko. com> wrote in message
news:Oc******** ******@TK2MSFTN GP11.phx.gbl...

You schema isn't deterministic. That's it. Remove minOccurs="0" on
message element definition to make it deterministic.
--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com