Skip to content

Commit b5851a5

Browse files
handrewskarenetheridge
authored andcommitted
Explain that schemas are for mandatory requirements
We do not host linting schemas here.
1 parent 1471f14 commit b5851a5

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

CONTRIBUTING.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -259,6 +259,11 @@ As part of the publishing process, the YAML source files are converted to JSON,
259259

260260
#### Schemas and OAS Requirements
261261

262+
Not all uses of OAS Objects and fields are necessarily useful.
263+
However, the OAS does not forbid various questionable combinations, for
264+
reasons ranging from preserving possible future use with new features to
265+
maintaining compatibility with past versions that neglected to forbid something.
266+
262267
The schemas published by the OpenAPI Initiative _only_ validate mandatory
263268
OAS requirements. This means that a field value or combination with another
264269
field is only forbidden in a schema if there is a corresponding MUST / MUST NOT /

0 commit comments

Comments
 (0)