[
Lists Home |
Date Index |
Thread Index
]
Hi Paul,
I was going to say that this was not what I was doing, and it still doesn't work, but for some reason it is working fine today.
Maybe I had some sort of thing going on in memory that was messing things up. Who knows?
Thanks for the help.
Chris Strolia-Davis
Database Specialist
Contractor - CDO Technologies Inc.
-----Original Message-----
From: Paul Spencer [mailto:xml-dev@boynings.co.uk]
Sent: Wednesday, December 10, 2003 10:39 AM
To: Strolia-Davis Christopher Contr MSG/MAT
Cc: xml-dev@lists.xml.org
Subject: RE: [xml-dev] MSXML and the "<any>" tag in XML Schemas
Chris,
I use xs:any a lot with MSXML, and find that the parser is very good at
reporting non-deterministic schemas that result from its incorrect use. This
is a good thing :-). Some other parsers do not report these errors, so you
might think that MSXML is wrong when it is not. I make it a rule to test all
schemas with MSXML for this reason.
That is the preliminary. These errors result from the parser not being able
to tell if an element should be parsed against the xs:any or some other part
of the content model. You are therefore playing safe(r) using
namespace="##other". However, this will not work if you reference an element
from some other namespace in your content model in a way that could still be
misconstrued. For example:
<xs:element name="MyElement">
<xs:complexType>
<xs:sequence>
<xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="ns:SomeChildElement" minOccurs="1" maxOccurs="1"/>
<xs:element ref="SomeOtherChild"/>
</xs:sequence>
</xs:complexType>
</xs:element>
You don't appear to be doing that, but then it looks as though you have
tailored your schema to post it here. Could it be something like that in
your real example? Either that, or I have missed something really obvious.
Regards
Paul Spencer
|
