published HTML docs munge quotes

[alxndrsn]

At

OpenAPI-Specification/versions/3.2.0.md

Line 2123 in 251d1db

| <a name="responses-code"></a>[HTTP Status Code](#http-status-codes) | [Response Object](#response-object) \| [Reference Object](#reference-object) | Any [HTTP status code](#http-status-codes) can be used as the property name, but only one property per code, to describe the expected response for that HTTP status code. This field MUST be enclosed in quotation marks (for example, "200") for compatibility between JSON and YAML. To define a range of response codes, this field MAY contain the uppercase wildcard character `X`. For example, `2XX` represents all response codes between `200` and `299`. Only the following range definitions are allowed: `1XX`, `2XX`, `3XX`, `4XX`, and `5XX`. If a response is defined using an explicit code, the explicit code definition takes precedence over the range definition for that code. |

, the specific quote marks around 200 are important to the meaning of the documentation.

When published as HTML at https://spec.openapis.org/oas/v3.2.0.html#patterned-fields-0, the quotes have been converted from " to ”:

“200”

This changes the meaning of the sentence:

This field MUST be enclosed in quotation marks (for example, "200") for compatibility...

making the example invalid.

Affected versions of the spec likely 3.0.1 through 3.2.0:

https://github.com/search?q=repo%3AOAI%2FOpenAPI-Specification+%22be+enclosed+in+quotation+marks+%22&type=code

[ralfhandl]

@alxndrsn Thanks for spotting this, the Markdown should use backticks around the "200".

Would you mind opening a pull request against branch v3.3-dev for fixing this in version 3.3.0? This can then be downported later to fix versions 3.2.1 and 3.1.3.

Thanks in advance!

[alxndrsn]

@ralfhandl something like this? #5065

[ralfhandl]

Almost, see my comment.

Thanks!