From e0b2012a52bb2e6fce372b176a62ccdd197fa536 Mon Sep 17 00:00:00 2001 From: Ralf Handl Date: Fri, 30 Aug 2024 10:12:00 +0200 Subject: [PATCH 1/2] Different JSON Schema also affects 3.0 --- versions/3.1.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/3.1.1.md b/versions/3.1.1.md index 396f391bcb..cc8cc6768c 100644 --- a/versions/3.1.1.md +++ b/versions/3.1.1.md @@ -1572,7 +1572,7 @@ application/json: In contrast to OpenAPI 2.0, `file` input/output content in OpenAPI 3 is described with the same semantics as any other schema type. -In contrast to OpenAPI 2.0, the `format` keyword has no effect on the content-encoding of the schema. Instead, JSON Schema's `contentEncoding` and `contentMediaType` keywords are used. See [Working With Binary Data](#working-with-binary-data) for how to model various scenarios with these keywords, and how to migrate from the previous `format` usage. +In contrast to OpenAPI 3.0, the `format` keyword has no effect on the content-encoding of the schema. Instead, JSON Schema's `contentEncoding` and `contentMediaType` keywords are used. See [Working With Binary Data](#working-with-binary-data) for how to model various scenarios with these keywords, and how to migrate from the previous `format` usage. Examples: From 1802a9e8e8f955295f15d3121c392b972ab02abb Mon Sep 17 00:00:00 2001 From: Ralf Handl Date: Fri, 30 Aug 2024 10:17:21 +0200 Subject: [PATCH 2/2] Update 3.1.1.md --- versions/3.1.1.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/versions/3.1.1.md b/versions/3.1.1.md index cc8cc6768c..7506d5ad47 100644 --- a/versions/3.1.1.md +++ b/versions/3.1.1.md @@ -1570,9 +1570,9 @@ application/json: ##### Considerations for File Uploads -In contrast to OpenAPI 2.0, `file` input/output content in OpenAPI 3 is described with the same semantics as any other schema type. +In contrast to OpenAPI 2.0, `file` input/output content in OAS 3.x is described with the same semantics as any other schema type. -In contrast to OpenAPI 3.0, the `format` keyword has no effect on the content-encoding of the schema. Instead, JSON Schema's `contentEncoding` and `contentMediaType` keywords are used. See [Working With Binary Data](#working-with-binary-data) for how to model various scenarios with these keywords, and how to migrate from the previous `format` usage. +In contrast to OAS 3.0, the `format` keyword has no effect on the content-encoding of the schema in OAS 3.1. Instead, JSON Schema's `contentEncoding` and `contentMediaType` keywords are used. See [Working With Binary Data](#working-with-binary-data) for how to model various scenarios with these keywords, and how to migrate from the previous `format` usage. Examples: