|
1 | 1 | # OpenAPI 3.1.X JSON Schema |
2 | 2 |
|
3 | | -Here you can find the JSON Schema for validating OpenAPI definitions of versions 3.1.x. |
| 3 | +This directory contains the YAML sources for generating the JSON Schemas for validating OpenAPI definitions of versions 3.1.X, which are published on [https://spec.openapis.org](https://spec.openapis.org). |
4 | 4 |
|
5 | | -As a reminder, the JSON Schema is not the source of truth for the Specification. |
6 | | -In cases of conflicts between the Specification itself and the JSON Schema, the |
7 | | -Specification wins. Also, some Specification constraints cannot be represented |
8 | | -with the JSON Schema so it's highly recommended to employ other methods to |
9 | | -ensure compliance. |
| 5 | +Due to limitations of GitHub pages, the schemas on the spec site are served with `Content-Type: application/octet-stream`, but should be interpreted as `application/schema+json`. |
| 6 | + |
| 7 | +The sources in this directory, which have `WORK-IN-PROGRESS` in their `$id`s, is _not intended for direct use_. |
| 8 | + |
| 9 | +## Choosing which schema to use |
| 10 | + |
| 11 | +There are two schemas to choose from for 3.1 usage, both of which have an `$id` that starts with `https://spec.openapis.org/oas/3.1/` and end with date or the `WORK-IN-PROGRESS` placeholder: |
| 12 | + |
| 13 | +* `https://spec.openapis.org/oas/3.1/schema/{date}` — A self-contained schema that _does not_ validate Schema Objects beyond `type: [object, boolean]` |
| 14 | +* `https://spec.openapis.org/oas/3.1/meta/base/{date}` — The vocabulary metaschema for OAS 3.1's extensions to draft 2020-12 |
| 15 | +* `https://spec.openapis.org/oas/3.1/dialect/base/{date}` — The dialect metaschema that extends the standard `draft/2020-12` metaschema by adding the OAS "base" vocabulary |
| 16 | +* `https://spec.openapis.org/oas/3.1/schema-base/{date}` — A schema that combines the self-contained schema and the "base" dialect schema to validate Schema Objects with the dialect; this schema does not allow changing `$schema` or `jsonSchemaDialect` to other dialects |
| 17 | + |
| 18 | +The name "base" for the dialect was intended to indicate that the OAS dialect could be further extended. |
| 19 | + |
| 20 | +An additional schema that validates the Schema Object with the OAS 3.1 dialect but does not restrict changing `$schema` is [under consideration](https://github.com/OAI/OpenAPI-Specification/issues/4147). |
| 21 | + |
| 22 | +## Schema `$id` dates |
| 23 | + |
| 24 | +The published schemas on the spec site have an _iteration date_ in their `id`s. |
| 25 | +This allows the schemas for a release line (in this case 3.0) to be updated independent of the spec patch release cycle. |
10 | 26 |
|
11 | 27 | The iteration version of the JSON Schema can be found in the `$id` field. |
12 | 28 | For example, the value of `$id: https://spec.openapis.org/oas/3.1/schema/2021-03-02` means this iteration was created on March 2nd, 2021. |
13 | 29 |
|
14 | | -The `schema.yaml` schema doesn't validate the JSON Schemas in your OpenAPI |
15 | | -document because 3.1 allows you to use any JSON Schema dialect you choose. We |
16 | | -have also included `schema-base.yaml` that extends the main schema to validate |
17 | | -that all schemas use the default OAS base vocabulary. |
| 30 | +We are [working on](https://github.com/OAI/OpenAPI-Specification/issues/4152) how to best provide programmatic access for determining the latest date for each schema. |
18 | 31 |
|
19 | | -## Contributing |
| 32 | +## Improving the schemas |
20 | 33 |
|
21 | | -To submit improvements to the schema, modify the `schema.yaml` and add test cases for your changes. |
| 34 | +As a reminder, the JSON Schema is not the source of truth for the Specification. In cases of conflicts between the Specification itself and the JSON Schema, the Specification wins. Also, some Specification constraints cannot be represented with the JSON Schema so it's highly recommended to employ other methods to ensure compliance. |
| 35 | + |
| 36 | +The schema only validates the mandatory aspects of the OAS. |
| 37 | +Validating requirements that are optional, or field usage that has undefined or ignored behavior are not within the scope of this schema. |
| 38 | +Schemas to perform additional optional validation are [under consideration](https://github.com/OAI/OpenAPI-Specification/issues/4141). |
| 39 | + |
| 40 | +Improvements can be submitted by opening a PR against the `main` branch. |
| 41 | + |
| 42 | +Modify the `*schema*.yaml` files and add test cases for your changes. |
22 | 43 |
|
23 | 44 | The TSC will then: |
24 | 45 | - Run tests on the updated schema |
25 | 46 | - Update the iteration version |
26 | 47 | - Publish the new version |
27 | 48 |
|
28 | | -## Tests |
29 | | - |
30 | 49 | The [test suite](../../tests/v3.1) is part of this package. |
31 | 50 |
|
32 | 51 | ```bash |
33 | 52 | npm install |
34 | 53 | npm test |
35 | 54 | ``` |
36 | | - |
37 | | -You can also validate a document individually. |
38 | | - |
39 | | -```bash |
40 | | -node scripts/validate.mjs path/to/document/to/validate.yaml |
41 | | -``` |
|
0 commit comments