Lists Home |
Date Index |
- To: "James Clark" <email@example.com>,<firstname.lastname@example.org>
- Subject: RE: [xml-dev] Interesting mailing list & a rare broadside
- From: "Dare Obasanjo" <email@example.com>
- Date: Fri, 7 Jun 2002 19:59:59 -0700
- Thread-index: AcIMXF1YfzPucBHFTXqPiuJJ3S+z8QCO7rIQ
- Thread-topic: [xml-dev] Interesting mailing list & a rare broadside
> -----Original Message-----
> From: James Clark [mailto:firstname.lastname@example.org]
> Sent: Tuesday, June 04, 2002 11:41 PM
> To: Dare Obasanjo; email@example.com
> Subject: Re: [xml-dev] Interesting mailing list & a rare broadside
> Thanks! I am glad to hear MSXML allows this to be detected.
> Now suppose I change example.xml to:
> <bar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> where bar.xsd is:
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
> <xs:element name="bar">
> Is there also some way to tell MSXML not to allow the
> instance to provide additional schemas so that this would be
> detected as invalid as well?
Oops, forgot to answer this.
Since xsi:noNamespaceSchemaLocation is a hint, it can be ignored at the
discretion of the implementation. MSXML ignores the namespace location
in the instance document if
A.) No validation is requested by the user either via setting
validateOnParse property or invoking the validate() method.
B.) A schema is provided by the user via an XML Schema Cache for
validating the document.
PITHY WORDS OF WISDOM
The shortest distance between two points is under repair.
This posting is provided "AS IS" with no warranties, and confers no