Skip to content

Conversation

handrews
Copy link
Member

@handrews handrews commented Jun 9, 2024

See the original PR for the detailed history including why it is OK to weaken this MUST to a SHOULD in a patch release. This port is slightly different from the original because it includes both example and examples in the Schema Object, while 3.0.4 only had example.

The four ways of specifying parameter or media type examples
are confusing. There is a lot of guidance that is repeated,
making it harder to see the essentials.  Some of that guidance is
also contradictory, with most saying that the examples SHOULD
match various conditions, but one saying that they MUST.

Research shows that SHOULD was repeatedly advocated, and instances
of MUST corrected back to SHOULD, except for one final commit
where MUST was introduced, and the subsequent commit to revert
to SHOULD seems to have simply missed one instance.  So this
change takes the position that the MUST was an error and weakens
it to SHOULD to match the other four or five places where the
requirement was specified.
@handrews handrews added bug clarification requests to clarify, but not change, part of the spec example obj/keywords Issues with the Example Object or exampel(s) keywords labels Jun 9, 2024
@handrews handrews added this to the v3.1.1 milestone Jun 9, 2024
@handrews handrews requested a review from a team June 9, 2024 23:26
@ralfhandl ralfhandl merged commit 258e85d into OAI:v3.1.1-dev Jun 10, 2024
@handrews handrews deleted the examples-311 branch June 10, 2024 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug clarification requests to clarify, but not change, part of the spec example obj/keywords Issues with the Example Object or exampel(s) keywords

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants