Hi Ben,
As you said, right now the only way to describe schemas is with JSON Schema, and we’ve added some extensions to help with XML modeling. The solution would be to convert the XSDs to JSON Schema with the use of those special extensions. That said, not all XSDs can be converted and not all XML can be represented using JSON Schema. As for the spec itself, we’ve considered and will still consider adding support for additional schema types in future versions, but there’s no guarantee as to if and when it will happen. From: benjamin_preston2004 via Swagger <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, September 27, 2017 at 02:36 To: Swagger <[email protected]> Subject: Externally defined XML Schema Despite numerous attempts to ask this question on this forum and elsewhere and despite sitting in on the Open API 3.0 Webinar sessions yesterday and asking questions (which weren't selected) I am yet to get any clarity on the following: Many organisations have invested time in defining XML Schemas which will form the payload for their requests/responses. I appreciate that Swagger (OAPI 2.0) and OAPI 3.0 don't/won't provide full support for externally defined XSDs, but I would love to hear what a valid work around would be? Any insightful replies would be much appreciated. Ben. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
