json-schema-org/json-schema-spec

🧹 Clarification: MAYs in several sections are linquistic, not requirements

Closed this issue · 1 comments

gregsdennis commented

Specification section

Validation spec:

  • deprecated
  • readOnly / writeOnly

What is unclear?

There are several "MAY" words that don't need to be capitalized as they are neither constrictive nor permissive. This usage is just informing the reader that something could happen in the data that the schema is describing; it's not related to an implementation, tooling, or an application.

Proposal

Fix the casing to lowercase.

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

jdesrosiers commented

Thanks for looking out for things like this. I think there's quite a few places in the spec where we use these uppercase terms inappropriately.