The latest articles on DEV Community by gauamg (@gauamg). https://dev.to/gauamg https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F618010%2Fbf04ae71-8771-4a99-9c76-48f9b215795d.png https://dev.to/gauamg en gauamg Tue, 20 Apr 2021 19:24:31 +0000 https://dev.to/gauamg/validating-oas3-x-yaml-spec-files-against-the-oas3-0-spec-in-java-21ma https://dev.to/gauamg/validating-oas3-x-yaml-spec-files-against-the-oas3-0-spec-in-java-21ma <p>I am new to this forum and this is really more a question than a post. Hopefully this is OK.</p> <p>I would like to be able to validate OAS3.X compatible YAML spec files against the OAS3.0 spec (<a href="https://spec.openapis.org/oas/v3.1.0">https://spec.openapis.org/oas/v3.1.0</a>). The built-in capabilities in swagger-parser and openapi4j appear to give inconsistent results. For instance the swagger-parser is not flagging that 'decimal' is not a valid data type in OAS3 etc. How could I write a validator from scratch in Java that would load the OAS3 spec and then validate the YAML spec files against it? (Note: In openapi4j, if the URL points to the OAS3.0 spec file, the parser quits with an exception.)</p> <p>Thanks!</p>