- From: Aung Aung <aaung@microsoft.com>
- Date: Thu, 27 Sep 2001 11:44:47 -0700
- To: <xmlschema-dev@w3.org>
- Message-ID: <22AC3F532BE25849BF04BE95350FF91B03BC4F15@red-msg-08.redmond.corp.microsoft.com>
>So since valid includes must be from a schema doc't to a schema doc't >which _share_ a targetNamespace value, references in the includer to >components defined in the includee look just like references in the >includer to itself. No transfer of namespace bindings, which are >purely a matter for the XML Namespaces REC, is implied or required. Henry, Your answer does not quite answer the question Mike is asking. How about references in the includee to components defined a different includee?? The example of the issue is below. Questions: 1. should the "a.xsd" be valid XSD? please note that type="foo" in b.xsd is not qualified (there is no namespace declared for it). a.xsd~~~~~~~~~~ <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="foo" xmlns="foo"> <xsd:include schemaLocation="b.xsd" /> <xsd:include schemaLocation="c.xsd" /> </xsd:schema> b.xsd~~~~~~~~~~~ <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="foo" type="foo"/> </xsd:schema> <!-- Q?: Does "b.xsd" requires namespace declaration xmlns="foo" --> c.xsd~~~~~~~~~~~ <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:simpleType name="foo"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="test"/> </xsd:restriction> </xsd:simpleType> </xsd:schema> Thanks, -Aung
Received on Thursday, 27 September 2001 14:45:19 UTC