title: Mulesoft RAML - Api specification with request body schema and response body schema on nested XSD file
body: <p>I'm trying to create an API specification with a request body schema and response body schema that referenced two files XSD OTA_CancelRQ.xsd and OTA_CancelRS.xsd</p>
  <p><a href="https://i.stack.imgur.com/BT7Ih.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/BT7Ih.png" alt="enter image description here" /></a></p>
  <p>My problem is that the file OTA_CancelRQ.xsd references two XSD files &quot;OTA_CommonTypes.xsd&quot; and &quot;OTA_SimpleTypes.xsd&quot; with a xs:include string</p>
  <p><a href="https://i.stack.imgur.com/SbDOs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/SbDOs.png" alt="enter image description here" /></a></p>
  <p>If I use this API specification with a project in Anypoint Studio, and call the method OTA_CancelRQ with a XML body request, I have an error that said &quot;Cannot resolve the name 'OTA_PayloadStdAttributes' to a(n) 'attribute group' component&quot;, but the 'OTA_PayloadStdAttributes' component is contained in &quot;OTA_CommonTypes.xsd&quot; file.</p>
  <p>I tried also with the command &quot;xs:import&quot;, but the final result is the same &quot;Cannot resolve the name 'OTA_PayloadStdAttributes' to a(n) 'attribute group' component&quot;</p>
  <p>My question is: it's possible to create a API specification with XSD schema that referenced another local XSD file?</p>