W3C home > Mailing lists > Public > xmlschema-dev@w3.org > November 2008

RE: when are duplicated type definitions allowed?

From: Michael Kay <mike@saxonica.com>
Date: Tue, 18 Nov 2008 15:56:08 -0000
To: "'Tobias Koenig'" <tobias.koenig@trolltech.com>, <xmlschema-dev@w3.org>
Message-ID: <5579B586417E4ABDBC87772B987EE284@Sealion>

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

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

> -----Original Message-----
> From: xmlschema-dev-request@w3.org 
> [mailto:xmlschema-dev-request@w3.org] On Behalf Of Tobias Koenig
> Sent: 18 November 2008 15:32
> To: xmlschema-dev@w3.org
> 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
Received on Tuesday, 18 November 2008 15:56:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:15:48 UTC