Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Unqualified elment - but still have prefix at the root

From: "Michael Kay" <mike@--------.--->
To: "'Avihaimar'" <avihaimar@-----.--->, <xmlschema-dev@--.--->
Date: 8/25/2009 10:03:00 AM
> 
> i have two schemas A,B. 
> B import A. 

Actually, you have one schema made up from two schema documents.

> 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? 
> 

Are you saying (a) you don't want the elements to be in a namespace, or are
you saying (b) you want them to be in a namespace, but you want that to be
the default namespace (so it needs no prefix)?

If you want (a) then you'll have to change your schema. Without seeing the
schema, it's hard to say how.

If you want (b), then this depends on the tool that you are using to
generate instances from your schema. You haven't told us what tool you are
using.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 





transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent