Skip to content

Commit e06befe

Browse files
committed
Be more clear about "format" validation behavior
1 parent 66f90d6 commit e06befe

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

versions/3.2.0.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,8 @@ Data types in the OAS are based on the types supported by the [JSON Schema Speci
146146
Note that `integer` as a type is also supported and is defined as a JSON number without a fraction or exponent part.
147147
Models are defined using the [Schema Object](#schemaObject), which is a superset of JSON Schema Specification Draft 2020-12.
148148

149-
<a name="dataTypeFormat"></a>As defined by the [JSON Schema Validation vocabulary](https://tools.ietf.org/html/draft-bhutton-json-schema-validation-00#section-7.3), data types can have an optional modifier property: `format`.
149+
<a name="dataTypeFormat"></a>As defined by the [JSON Schema Validation specification](https://tools.ietf.org/html/draft-bhutton-json-schema-validation-00#section-7.3), data types can have an optional modifier property: `format`. As described in that specification, `format` is treated as a non-validating annotation by default; the ability to validate `format` varies across implementations.
150+
150151
OAS defines additional formats to provide fine detail for primitive data types.
151152

152153
The formats defined by the OAS are:

0 commit comments

Comments
 (0)