byte vs base64 format

[hkosova]

Data Types defines format: byte as base64-encoded characters.

Considerations for File Uploads and Special Considerations for multipart Content mention format: base64, which is not mentioned in Data Types. Is this a typo and meant to say format: byte? Or are base64 and byte different formats?

[axlbonnet]

I've stumbled on the same issue and the spec is incoherent on this point.

I've found this remark on the PR that introduces a "base64" that suggests that "byte" is the good format but there was no corrections.

[handrews]

@hkosova @axlbonnet

JSON Schema draft-07 (which would be relevant to OpenAPI 3.1 at the earliest, possibly 4.0, assuming OAI wants to adopt it at all) adds the contentMediaType and contentEncoding parameters for general support of encoding other forms of data in JSON strings.

These were formerly the type and binaryEncoding keywords within Hyper-Schema's media object, but we do not think JSON Schema users should have to adopt Hyper-Schema for this functionality (or readOnly or writeOnly, both of which are also now in the validation spec).

[pbryan]

Where does this leave interpreting "format"? Based on my reading of 3.0.1, it would seem right now that "byte" and "base64" would be synonyms.

[handrews]

@pbryan in the long run, format should not be used for this. OpenAPI worked around deficiencies in JSON Schema, but I'm hoping we can drop the workarounds and converge on the existing unambiguous solution.

[pbryan]

Thanks @handrews.

[hkosova]

Closing in favor of #1547.

[mma5997]

Hi @hkosova,
we are using the 3.0.0 version currently.
So please can you help me with this query ==> comment