Format validation of integer types

[lud]

Hello,

In the specification I can read the following:

All format attributes defined in this section apply to strings, but a format attribute can be specified to apply to any instance types defined in the data model defined in the core JSON Schema. [CREF1]

Does that mean that the format validation, for those predefined formats, is only executed when the data is a string? (Like properties are only used if the data is an object). Or should the format fail if the data is not a string?

I'm trying to implement a validator for OAS 3.1 and their formats include integer formats like int64. We can have a schema of {"type": "integer", "format": "int64"}.

Should my validator fail if the input data is not an integer (say an array), or should it check that the format does not applies to arrays and ignore it?

Thank you.

[gregsdennis]

We can have a schema of {"type": "integer", "format": "int64"}.

Yes. This is correct. I believe that's the intended purpose for that OAS format as well.

should the format fail if the data is not a string?

Should my validator fail if the input data is not an integer (say an array), or should it check that the format does not applies to arrays and ignore it?

Formats ignore (implicitly pass) instance types they don't check. So if you have int64 and don't get an integer, the validation is skipped.

[lud]

Thank you!