invalid OpenAPI specification should retains the Json schema validator errors

[LasneF]

given the doctor

when i set a valid Json but invalid API document
i got
"unable to parse OpenAPI specification: The requested specification cannot be parsed as an OpenAPI Spec. vaccum cannot read the file: unable to parse specification: yaml: control characters are not allowed"

in fact it could be interesting to distinguish the 2 use case

invalid JSON / YAML file ( such as mention wrong char, or not closed brackets and so on
vs
an issue due to the fact that the OAS does not comply with the OAS schema

in both case it would be interesting to retains the error of the underlying ( parser , or json schema validator) to be able to correct

in my case
i was using such
license:
name: Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
identifier: CC-BY-NC-SA-4.0
url: https://toto.toata

would be interesting to have the schema validator exception that would have mentionned that the 2 fields (identifier and url) are mutualy exclusive . this being expressed in the OAS schema

notice here is basic , could be more complex / real , topic being to have the infra to store what parser / validator generate