W3C home > Mailing lists > Public > xmlschema-dev@w3.org > April 2002

RE: import/include

From: Dare Obasanjo <dareo@microsoft.com>
Date: Wed, 24 Apr 2002 22:03:22 -0700
Message-ID: <8BD7226E07DDFF49AF5EF4030ACE0B7E05C69A2D@red-msg-06.redmond.corp.microsoft.com>
To: "Mauni, Manisha" <Manisha.Mauni@ind.xerox.com>, <xmlschema-dev@w3.org>
> -----Original Message-----
> From: Mauni, Manisha [mailto:Manisha.Mauni@ind.xerox.com] 
> Sent: Wednesday, April 24, 2002 9:22 PM
> To: xmlschema-dev@w3.org
> Subject: import/include 
> Hello all.
> I am having a doubt regarding import/include tags.
> I'll appreciate the help.
> I am not able to understand the basic purpose of these tags. 
> Let me explain the doubt by an example.
> Say we have two  schemas 
> 	a.xsd  (having elements a1 a2 ) and
> 	b.xsd  (having elements b1 b2 and b3 which extends a1 of a.xsd).

b.xsd would be invalid because the schema processor cannot locate a
definition for a1. 

> Now if b.xsd  imports/includes a.xsd what will b.xsd be like.
> 	1) will it  have elements (a1 a2 b1 b2  and b3 )

Yes. These elements will be treated as part of the schema in b.xsd. 

> 	2) or will it have  (b1 b2 and b3 ) where b3 will 
> internally have a1 of a.xsd

I'm not completely sure what this means but I think the answer is no. 
> Hope i am able to explain my doubt. 
> (I am clear that the import will be used if a.xsd and b.xsd 
> are from different namespaces and include will be  used if 
> both are in the same
> namespace)

If you want to recapture your youth, cut off his allowance.  
This posting is provided "AS IS" with no warranties, and confers no
You assume all risk for your use. (c) 2002 Microsoft Corporation. All
rights reserved.
Received on Thursday, 25 April 2002 01:03:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:56 UTC