Altova Mailing List Archives

Re: [xml-dev] Motivations for namespaces (sorry)

From: "Eric van der Vlist" <vdv@--------.--->
To: <chiusano_joseph@---.--->
Date: 7/9/2003 4:29:00 PM

Chiusano Joseph said:
> Eric,
> I'm not sure if I correctly interpreted "the combination used to mix
> the namespaces" in your original response below, but anyway here's an
> example with generic namespace identifiers/prefixes and elements:
> <?xml version="1.0" encoding="UTF-8"?>
> <ns1:MyRootElement
>    xmlns:xsi=""
>    xmlns:ns1="
>    xmlns:ns2="
>    xsi:schemaLocation=" Schema1.xsd
>               Schema2.xsd>
>    <ns1:SomeDate>2001-01-01</ns1:SomeDate>
>    <ns2:AnotherDate>2001-01-01</ns2:AnotherDate>
> ...
> </ns1:MyRootElement>

I would argue that in this case, what's identifying your "document type"
is the xsi:schemaLocation more than the namespaces!
My point was rather that namespaces alone are not enough to guess what's
the document as a whole is about.
Freelance consulting and training.
Eric van der Vlist  
(W3C) XML Schema ISBN:0-596-00252-1


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.