Skip to content

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

Closed
@gregsdennis

Description

@gregsdennis

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

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions