These things are currently very poorly defined: in fact the spec says as
much, it explicitly acknowledges that component identity is not fully
defined.

I think a number of products adopt the interpretation that components are
identical (and duplicates eliminated) if they are loaded from the same
absolute URL. Others would claim that the languuage of the spec invites you
to treat components as identical using some kind of "deep equality" or
"indistinguishability" test.

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

> -----Original Message-----
> From: xmlschema-dev-request@w... 
> [mailto:xmlschema-dev-request@w...] On Behalf Of Tobias Koenig
> Sent: 18 November 2008 15:32
> To: xmlschema-dev@w...
> Subject: when are duplicated type definitions allowed?
> 
> 
> Hej,
> 
> I can't find any clear explanation in the schema 1.1 (1.0) 
> spec how to handle multiple imports of the same schema 
> through different documents.
> 
> e.g. A imports B and C (with different namespaces)
>        B imports D 
>        C imports D
> 				(B and C import D with the same 
> namespace)
> 
> so all the types/elements/attributes from D appear suddenly 
> twice in the target schema... is that allowed?
> 
> Another situation: let's have the same type/element/attribute 
> definitions in two schema files with different filenames 
> (URIs) What should happen if a third schema includes (or 
> imports) these two files?
> 
> Thanks in advance
> 
> Ciao,
> Tobias
>