RE: [xml-dev] Chameleon schemas <include>ing chameleon schemas

["Dare Obasanjo" <dareo@microsoft.com>]

a.) What do you think is the difference between "target namespace" and "targetNamespace attribute"
 
b.) Once simpleTypes.xsd was included with contactTypes.xsd they became a single logical schema so they shouldn't be treated as different by a schema processor. 

________________________________

From: Paul Spencer [mailto:ps@boynings.co.uk]
Sent: Tue 7/1/2003 2:39 AM
To: Dare Obasanjo
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Chameleon schemas <include>ing chameleon schemas



Can you quote a section on this? I have looked at the specification
quite carefully, and can't see it. I have also been careful to
differentiate between "target namespace" (which I have assumed can be
inherited) and "targetNamespace attribute" (which I have assumed
cannot).

Regards

Paul

On Tue, 1 Jul 2003 01:57:57 -0700, you wrote:

>According to the W3C XML Schema recommendation the types described in simpleTypes.xsd should exist in the "apd" namespace. 
>
>________________________________
>
>From: Paul Spencer [mailto:ps@boynings.co.uk]
>Sent: Tue 7/1/2003 1:09 AM
>To: xml-dev@lists.xml.org
>Subject: [xml-dev] Chameleon schemas <include>ing chameleon schemas
>
>
>
>I frequently come across the case where a schema document with no
>targetNamespace attribute (call this one simpleTypes.xsd) is
><include>d in another schema document with no targetNamespace
>attribute (say, contactTypes.xsd), which is, in turn, <include>d in a
>schema document with a targetNamespace attribute (say, main.xsd having
>a targetNamespace attribute value of "apd"). (I am using "apd" as a
>URI here to save typing.)
>
>Clearly, any data type defined in contactTypes.xsd will exist in the
>"apd" namespace. What about data types defined in simpleTypes.xsd? Do
>they exist in the "apd" namespace, or do they have no target
>namespace?
>
>At least two suppliers of XML tools have different interpretations of
>this. My solution is therefore to avoid the problem by making target
>namespaces explicit, but my enquiring mind would love a definitive
>statement on which interpretation is correct. Perhaps the tool vendors
>will then take note.
>
>I hope this is clear. I have examples if anyone wants them.
>
>Regards
>
>Paul Spencer
>
>-----------------------------------------------------------------
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>
>To subscribe or unsubscribe from this list use the subscription
>manager: <http://lists.xml.org/ob/adm.pl>
>
>
>