[
Lists Home |
Date Index |
Thread Index
]
Just take the case of the "middle" schema document, contactTypes.xsd.
This does not have a targetNamespace attribute in the xs:schema
element. However, once it has been <include>d, each definition has a
target namespace. This was the differentiation I was making. It seems
to be relevant when interpreting 4.2.1 of XML Schema part 1.
My interpretation has always been the same of yours, but at least one
vendor has stated that this is wrong. Also, another tool does not
handle this case as you say, but has acknowledged this to be an error.
Regards
Paul
On Tue, 1 Jul 2003 02:54:53 -0700, you wrote:
>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>
>>
>>
>>
>
>
>
|
