Skip to content

Commit f185d06

Browse files
Remove unneeded detail on "format"
This was just duplicating info from the JSON Schema spec. Co-authored-by: Darrel <[email protected]>
1 parent 5e817f7 commit f185d06

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

versions/3.1.0.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ However, to support documentation needs, the `format` property is an open `strin
153153
Additional formats MAY be used even though undefined by either JSON Schema or this specification.
154154
Types that are not accompanied by a `format` property follow the type definition in the JSON Schema. Tools that do not recognize a specific `format` MAY default back to the `type` alone, as if the `format` is not specified.
155155

156-
Note that by default, JSON Schema validators MUST NOT attempt to validate the `format` keyword. It is primarily treated as an annotation that informs applications of the intended nature of the data. For historical reasons, it is possible to configure JSON Schema validators to validate `format`, but this is not consistently implemented and SHOULD NOT be relied upon in any environment where an unknown validator or unknown validator configuration might be used.
156+
Note that by default, JSON Schema validators will not attempt to validate the `format` keyword. https://json-schema.org/draft/2019-09/release-notes.html#format-vocabulary
157157

158158
The formats defined by the OAS are:
159159

0 commit comments

Comments
 (0)