Re: clarification/errata: circular attributeGroup, ur-type & include

Khaled Noaman wrote:

> Hi Henry,
>
> On the same topic:
>
> If schema A includes B & C, and imports D. Do B and C have access to
> components in D?

This is a good example of bad design if B and C are allowed to access
the components in D.  It means that whoever uses B and C needs to
imports D too.

If there was a need to allow the above happen, the spec should provide
a way to specify that the pre-condition of including B and C is by importing
D.

>
>
> Thanks,
> Khaled Noaman
> IBM Toronto Lab
> knoaman@ca.ibm.com
>
> xmlschema-dev-request@w3.org wrote:
>
> > Sandy Gao writes:
> > >> >If schema document A includes B, and B *imports* C. Does A have access
> > >> > to components in C?
> >
> > Henry Thompson responds:
> > >> See above -- no.
> >
> > Clarification.  You cannot make explicit references from document A using
> > a prefix (or default NS) resolving to C.  BUT, your components in A may be
> > indirectly using components from C.  Lets assume that a type declared in B
> > derives from one in C (which is possible because B imports C).  Document A
> > can declare elements using that type because it includes B.  Such use
> > obviously involves information from the base type in C as will as the
> > explicit reference in B.
> >
> > In the end, it's all one schema, but there are limitations on references
> > that can be explicitly made in schema documents.
> >
> > ------------------------------------------------------------------------
> > Noah Mendelsohn                                    Voice: 1-617-693-4036
> > Lotus Development Corp.                            Fax: 1-617-693-8676
> > One Rogers Street
> > Cambridge, MA 02142
> > ------------------------------------------------------------------------

Received on Thursday, 25 October 2001 15:32:14 UTC