Altova Mailing List Archives

Re: [xml-dev] The prefix "fgdc" for element "fgdc:fgdc" is not bound

From: "Fraser Goffin" <goffinf@----------.--->
To: "Nassar, Anthony" <ANassar@----.--->
Date: 12/13/2007 9:06:00 AM
You can still use a XSD to validate an instance if that XSD doesn't
declare any target namespace. For example :-

<xs:schema xmlns:xs=""
elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:element name="Root">
            <xs:element name="firstChild" type="xs:string"/>
            <xs:element name="firstSibling" type="xs:integer"/>


you can determine that this instance in not schema valid :-

<Root xmlns:xsi=""
	<firstSibling>this should be an integer to be valid</firstSibling>


On 13/12/2007, Nassar, Anthony <ANassar@h...> wrote:
> I thank everyone for their responses. Perhaps this bears out Dr. Kay's claim, but I'm actually more baffled than ever. If the NUnit test-results.xsd schema specifies *no* namespace, then the types it declares are in *no* namespace, is that right? How does a schema-aware parser use them, if at all? Does it simply fake it (i.e., if you were foolish enough to declare types in the non-namespace, I guess I'll have to bail you out)?
> My more immediate question, which I might need to answer for myself, is simply, is NUnit's schema just "wrong"?


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.