Although I understand you would like to tackle such a problem, I think the specification shouldn't try to be prescriptive of the allowed values. Such responsibility is too much of a burden to take in my opinion.

Developers should understand such technicalities based on their generators or whatever they are doing language-specific.

I think doing something like OpenAPI on this one is prudent

From: https://spec.openapis.org/oas/latest.html

Unique string used to identify the operation. The id MUST be unique among all operations described in the API. The operationId value is case-sensitive. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is RECOMMENDED to follow common programming naming conventions.

Although I understand you would like to tackle such a problem, I think the specification shouldn't try to be prescriptive of the allowed values. Such responsibility is too much of a burden to take in my opinion.

Developers should understand such technicalities based on their generators or whatever they are doing language-specific.

I think doing something like OpenAPI on this one is prudent

I agree that there should be no section defining what is allowed from a JSON schema perspective, anything should.

However, once it reaches a generator for a specific language, you will need to know about these things. This section is only aimed to help everyone more easily to get started. That once you as a provider of such generator find inconsistency in the reserved keywords, we can keep this documentation up to date 🙂

Got it