Hi Dave, everything inside and <xsd:documentation> needs to be well:formed xml. This means any elements declared in the documentation should be declared properly. I believe its actually the rules of XML that require prefixes to be defined. In other words you will have this problem when you do something like: <xsd:documentation> <foo:undefinedPrefix /> </xsd:documentation>
but not with <xsd:documentation> <undefinedPrefix /> </xsd:documentation> or <xsd:documentation xmlns:foo="..."> <foo:undefinedPrefix /> </xsd:documentation> or <xsd:documentation> <foo:undefinedPrefix xmlns:foo=""/> </xsd:documentation> Also, you should be receiving the same errors from other xml tools as well. I verified Xerces has issues with content like above. HTH, -jacobd On Thu, Feb 21, 2008 at 10:32 AM, dave <[EMAIL PROTECTED]> wrote: > > > I just put some sample XML inside <xs:documentaion> > element in my XML schema. This sample XML refers to > some undeclared namespace prefix. The XMLBeans > renders > such XSD file invalid when validated against. Am > just curious why? > > Of course, removing this ns prefix solved the > problem though. > > > > > ____________________________________________________________________________________ > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I'm competing in a Half-Ironman distance triathlon to raise money for the fight against cancer! Please help support my efforts by going to: http://www.active.com/donate/tntwaak/jacobd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
