Altova Mailing List Archives

Re: Question about prefix and namespaces with schemas

From: "Matevz Gacnik" <matevz.gacnik@-----------.-->
Date: 4/12/2004 9:14:00 PM

Did you check for default namespace(s) being present in your instance


"Carsten Klevenhusen" <Carsten.Klevenhusen@t...> wrote in message
> Hello everybody,
> I've some trouble using xml files with schemas. Would be nice if someone
> could help.
> Sorry, if I don't manage to get everything clear.I can always tell it more
> concrete when it's needed.
> I have some third party xml files which I'm supposed to validate against a
> schema in an application.
> The schema defines a target namespace and sets the elementFormDefault to
> qualified.
> In the xml files the schema is referenced using "schemaLocation"
> However there is no namespace prefix used in the xml files.
> So I'd expect, that a namespace prefix has to be defined in the xml files
> and used with each element.
> At least I understand that from the MSXML 4.0  SDK documentation.
> My Question now is: If a target namespace is defined, must one use a
> in the xml files or are there exceptions ?
> Problem is, that MSXML 4.0 validates the xml without prefixes alway as ok.
> Is the rule defined by W3C or Microsoft and are there parsers which
> xml files and target-namespacee without prefixes ?
> thanks in advance
> Carsten


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.