Mike Ralphson

See also https://github.com/OAI/Overlay-Specification/issues/36

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

@IvanGoncharov could you give me your thoughts on the issues with non-English-language API definitions? What might need changing/translating?

@sanchojaf Vtex seem to have moved over to using [Postman collections](https://help.vtex.com/developer-docs/) to document their APIs. Can you confirm? If so it would be dependent on [this issue](https://github.com/lucybot/api-spec-converter/issues/79)

VTEX seem to have moved (back) to OpenAPI 3.0 - https://github.com/vtex/openapi-schemas

Given URL 404s, please can you check?

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

We're not always that focussed, i.e. with a presentation, but any examples you might want to put together of `link` improvements either as new syntax or a proposal/extension would be...