Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Re: Unqualified elment - but still have prefix at the root [Thread Next] Re: Unqualified elment - but still have prefix at the rootTo: Avihaimar <avihaimar@-----.---> Date: 8/25/2009 1:15:00 PM I think what you may be trying to say is that despite the fact that you are using elemFormDefault="unqualified", your elements are qualified. Global elements belong to the target namespace; the elemFormDefault only applies to local elements (ie, within a complex type). If you don't want any of your elements to be in a namespace, you will have to get rid of the targetNamespace. Kevin On 8/25/2009 8:49 AM, Avihaimar wrote: > Last one - (Thank you!!!!!) > > > I know - i can handle this XML with any prefix. Its depend on the > declaration in the header (xlmns). > > But, > > XML without any prefix will failed in validation . I want to have the option > to not have prefix at all and i dont know how can i do this either by > chanigng the xsd or the instance. > > When i send example of XML to the cutomers i want to send them XML with no > prefix and i didnt success to have one by chanigng the xsd or the instance. > > > > Avihaimar wrote: > >> Hey, >> >> i have two schemas A,B. >> B import A. >> Both of them defined as unqualified element, but the xml that generated >> from B has n1: as a prefix for the root elements. >> Is there a way to have no prefix at all? >> >> Thank you >> >> > > | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
