Because the REST guide and the reusable OpenAPI documents mostly seem to be used for new APIs or major new revisions that use OpenAPI 3, we could consider phasing out OpenAPI 2.0.
could we start phasing out now or still too early?
maybe keep the last version of the guide supporting OpenAPI 2.0 around on another URL, linked for the 'main' version?
can 2.0-support be dropped inside new minor versions of the belgif OpenAPI artifacts? (previous releases are still available)
is it OK for the styleguide validator to also drop support?
Advantages would be:
simplify the guide with sections that illustrate both OpenAPI versions
don't need to maintain all belgif openapi documents in duplicate (often forgotten to update Swagger)
less confusion for users which example or belgif schema to look at
don't need to test styleguide validator on OpenAPI 2.0 and implement OpenAPI 2.0 workarounds
Because the REST guide and the reusable OpenAPI documents mostly seem to be used for new APIs or major new revisions that use OpenAPI 3, we could consider phasing out OpenAPI 2.0.
Advantages would be: