Hi,

Consider the following two schema files:

<!-- includee.xsd -->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <xsd:element name="el" type="type"/>
</xsd:schema>

<!-- includer.xsd -->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns="test" targetNamespace="test">
  <xsd:include schemaLocation="includee.xsd"/>

  <xsd:simpleType name="type">
    <xsd:restriction base="xsd:string"/>
  </xsd:simpleType>
</xsd:schema>

Here includer.xsd chameleon-includes includee.xsd which in turn
references a type from the including schema. It seems that this
should be legal however I couldn't locate the relevant part in
the spec (4.2.1 appears to be covering this case).

I am wondering of an implementation that conceptually transforms
includee.xsd (for the purpose of being included in includer.xsd)
into the following schema would do the right thing:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            targetNamespace="test"
            xmlns="test">
  <xsd:element name="el" type="type"/>
</xsd:schema>


Thanks,
Boris

-- 
Boris Kolpackov, Code Synthesis Tools   http://codesynthesis.com/~boris/blog
Open source XML data binding for C++:   http://codesynthesis.com/products/xsd
Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde

From mike@s... Thu May 15 11:30:17 2008
Received: from maggie.w3.org ([193.51.20