Fix dialect link from 3.1 to 3.2

[valerii15298]

• schema changes are included in this pull request
• schema changes are needed for this pull request but not done yet
• no schema changes are needed for this pull request

This PR updates link to the new one.

I noticed that in 3.2 spec there is a lot of references to 3.1, more than 20 cases. Shouldn't be they replaced to be 3.2 ?

[ralfhandl]

@valerii15298 Thanks for finding and reporting this!

As explained in https://github.com/OAI/OpenAPI-Specification/blob/main/CONTRIBUTING.md, the published specification files in the main branch are "frozen".

Please open a pull request against the v3.2-dev branch with proposed changes to file src/oas.md.

The proposed new text should not contain a concrete date in the dialect URI and rather use a placeholder YYYY-MM-DD because schema files are published independently of the spec patch releases.

Thanks in advance!

[valerii15298]

@ralfhandl and what about other places in the 3.2 spec where 3.1 is used? Should it be changed to 3.2 also?

As I mentioned in many places 3.1 is used as example version, etc

[ralfhandl]

3.1 as an example version in section 2.1 Versions and Depreciation is ok.

The only problematic place I found is in 4.14.7 Considerations for File Uploads:

In contrast to OAS 3.0, the format keyword has no effect on the content-encoding of the schema in OAS 3.1.

That should become "in OAS 3.1 and later".

If you find other places problematic, please point to them.

Thanks in advance!

[handrews]

That should become "in OAS 3.1 and later"

I could have sworn I fixed that... might have gotten lost in the switch to the new branching system 🤦

[valerii15298]

Created new PR #4994