Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Help with Namespaces and Includes

From: "Rowan Bradley" <rowan.bradley@------------.--->
To: <xmlschema-dev@--.--->
Date: 6/4/2009 2:56:00 PM
Michael,

Many thanks for your helpful answers.

I now have a working solution. I tried to make "chameleon include" work,
and found that it would validate in oXygen and Liquid XML but not in
XMLspy. 

However I've now removed the default namespace declaration from my XML
files, so the elements and attributes are in no namespace, removed the
targetNamespace declarations from the XSD files, and used
noNamespaceSchemaLocation to reference the XSD files. The XML files now
validate in all three tools.

The original error was having a default namespace in the XML file but
referring to the XSD files via a noNamespaceSchemaLocation declaration
(and having a targetNamespace declaration in the XSD files). How it
validated 6 years ago I don't know - old and less picky version of
XMLspy I guess.

Anyway, thanks for your help. I now understand this a bit better!

Rowan




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