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

Including schemata with duplicate referents

From: Kasimier Buchcik <kbuchcik@4commerce.de>
Date: Fri, 05 Nov 2004 13:56:37 +0100
To: <xmlschema-dev@w3.org>
Message-ID: <418B7885.4070402@4commerce.de>

Hi,

I have difficulties understanding what to do with included components
at sub-schema constrution stage - acting as referents - which cannot be
included into the final schema.

A simplified example:

- A, B1, B2 and C are schemata
- B1 includes C and references components of C (referred to as B1.C)
- B2 includes C and references components of C (referred to as B2.C)
- A includes B1 and B2

Since the B1.C components are already included in A, the B2.C components
won't be added to A. The spec states properties of components to have 
components as their values; the values of components of B2 referencing 
B2.C would become unavailable, since not added to A.

This all assumes a recursive construction of the schemata, i.e. B1 and 
B2 don't know of each others includes; plus the components of C being
created twice, for B1 and B2, since originating from a schema document -
or possibly from different schema documents.

I wonder if there are some proposed techniques to solve this.
Do the references of B2 to B2.C components need to be remapped to B1.C
components? Any experience with a machanism that is aware of duplicates,
i.e. removes them if including/importing _before_ any attempt of
resolving references is performed - if this is possible at all.

But maby this is not a problem at all, in which case I would be glad
to have the knot in my head removed.

Greetings,

Kasimier
Received on Friday, 5 November 2004 13:14:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:40:23 UTC