Skip to Content
avatar image
Former Member

Duplicate XSD Schema includes, are they valid?

I have a rather complex XSD schema which has broken out reusable components in several

library schemas which are leveraged via an include statement.

I have the following scenario.





<xs:include: schemaLocation="LibSchemaB.xsd"/>


<xs:include: schemaLocation="LibSchemaB.xsd"/>

<xs:include: schemaLocation="LibSchemaC.xsd"/>

If a complex element in LibSchemaC references one in LibSchemaB, then in MasterSchemaA,

it references both the LibSchemaC new complex element prime, built on a base complex element in LibSchemaB,

and the base complex element in LibSchemaB, will this schema be valid for the SAP XSD Schema importer/xml validator?

If not, is it considered syntactically correct or within the XSD schema standard?

Any input would be much appreciated.



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Feb 18, 2010 at 04:39 PM

    You may use xs:import statement in the parent xsd and import all of them. A lengthier way is also explained here.




    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for providing the link, it's helpful for understanding the mechanics of how to import an XML Schema, however, this doesn't answer my question.

      I'm trying to understand how SAP will parse/interpret a complex schema which makes references to several other schemas which in themselves make reference to, include, other schemas which may already be included in the includee schema.

      If SAP comes across a complex element that has already been defined in a previous include statement, does it simply throw out the newly referenced include or does it manage to track it. My concern are complex elements built on complex elements referenced in the includes.