Skip to content

Conversation

ralfhandl
Copy link
Contributor

@ralfhandl ralfhandl commented Sep 12, 2025

We used both "case-sensitive" and "case sensitive", switching to the variant used first in the spec.

Happy to switch the other way round.

  • 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

We used both flavors, with and without dash.
@ralfhandl ralfhandl requested review from a team as code owners September 12, 2025 12:19
@ralfhandl ralfhandl changed the base branch from main to v3.2-dev September 12, 2025 12:19
@ralfhandl ralfhandl added the editorial Wording and stylistic issues label Sep 12, 2025
@ralfhandl ralfhandl added this to the v3.2.0 milestone Sep 12, 2025
@ralfhandl ralfhandl requested a review from a team September 12, 2025 19:10
@ralfhandl ralfhandl enabled auto-merge September 12, 2025 19:10
@ralfhandl ralfhandl disabled auto-merge September 12, 2025 20:15
@@ -64,7 +64,7 @@ OAD authors SHOULD NOT rely on any such JSON-incompatible YAML values.

### Case Sensitivity

As most field names and values in the OpenAPI Specification are case-sensitive, this document endeavors to call out any case-insensitive names and values.
As most field names and values in the OpenAPI Specification are case sensitive, this document endeavors to call out any case-insensitive names and values.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I appreciate the push for consistency, it feels weird to me to hypenate "case-insensitive" but not "case sensitive." AFAICT, the more common approach is to hyphenate both.

WDYT about always hyphenating both variants in the spec?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think hyphenating might be more correct as it's an adjective, so I'm in favour

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial Wording and stylistic issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants