Altova Mailing List Archives

Re: Namespace problem

From: George Cristian Bina <george@----.-->
To: Volker.Zink@------.--
Date: 8/18/2004 6:07:00 PM

I explained you the problem in my previous post.
If you just add elementFormDefault="qualified" to your schema the 
instance document will be validated without problems.

<schema xmlns="" 

Hope that helps,
George Cristian Bina
<oXygen/> XML Editor & XSLT Editor/Debugger

Volker Zink wrote:
> Hello,
> 1. The Error mentioned was produced by the at 
> Normally i use the validator in 
> my programming environment (VisualWorks Smalltalk), but i trust the one 
> at more, and it has more detailed error messages/warnings.
> 2. If i remove the "grips://"-namespace 
> completely (including "plem:"-prefixes), i get following result
> ----
> PLEMGrips-Schema-Fall.xsd:6:5: Invalid: Undefined type 
> {}:FallImportExport referenced as type 
> definition of fallImportExport
> Problems with the schema-validity of the target
> ---
> I don't write an own validator. It just seems to me, that the validator 
> in VisualWorks has other results as the, so i want to 
> know, whats really correct, and why.
> As a programmer i use namespaces everyday. But XML-namespaces are a bit 
> strange to me compared to the namespaces in VisualWorks Smalltalk. But 
> probably because in XML its all about syntax, in Smalltalk its about 
> objects (classes). One object is in one namespace. Thats quite easy.
> Volker

From Burak.Emir@e... Wed Aug 18 13:33:03 2004
Received: from dr-nick.w3.o


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