[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: The prefix "fgdc" for element "fgdc:fgdc" is not bound
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="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="Root"> <xs:complexType> <xs:sequence> <xs:element name="firstChild" type="xs:string"/> <xs:element name="firstSibling" type="xs:integer"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> you can determine that this instance in not schema valid :- <Root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Nonamepsace_Schema.xsd"> <firstChild>String</firstChild> <firstSibling>this should be an integer to be valid</firstSibling> </Root> Fraser. 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"?
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|