Ted Epstein

@BenjamenMeyer, > openapi-spec-validator does support this per the v3 spec; The OpenAPI v3 spec does support the use of [Reference Objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#referenceObject) (i.e. object with a `$ref` property) in a wider...

@BenjamenMeyer , sorry this one slipped through the cracks. I just re-read this issue in the context of researching another one. Generally, we believe that KaiZen OpenAPI Editor _should_ allow...

@BenjamenMeyer, I have opened a new issue #439 that describes in detail the problem of overly restrictive references. If you are able to say whether the problems you encountered were...

@cvgaviao , sorry for the delay. I have opened an issue here to get some clarification on the spec: * https://github.com/OAI/OpenAPI-Specification/issues/1889 These other open issues suggest that OpenAPI may still...

@cvgaviao , we would need to look more carefully at this. If this is required of all OID implementations, then it's possible to implement validation and/or code assist for OID...

Thanks for that info, @cvgaviao .

@elicoten, this is a restriction of the YAML syntax itself, which [specifically says](https://yaml.org/spec/1.2/spec.html#id2777534) that leading tabs are not recognized as indents. So whatever editor or generator produced your existing Swagger...

@elicoten , the following support article is written for our commercial product, RepreZen API Studio. But most or all of the information and tips in that document are relevant to...

@elicoten , please feel free to change the name and we can leave this issue open. We don't have plans to support full editing with JSON syntax at this time.

> Would it be better to use the object name used in the OpenAPI3 Specification at the template name, and to put the keyword in brackets afterwards if there is...