Henry Andrews

The recommended way in JSON Schema to do this (using draft-06's `const`, but one-element `enum`s work in OpenAPI and are effectively constants) is: ```YAML cvv_check: type: string title: CVV check...

With #1977 the idiom I provided above will be supported in OAS 3.1. There may be further work to do on how to best recognize that idiom in tooling, but...

@emmanuelproulx `type` is from JSON Schema and only refers to the data type, not how it is produced or consumed (because JSON Schema is not aware of those things, although...

If your content is `image/png` then it's not JSON. Looking at the [Media Type Object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#mediaTypeObject) the `schema` field is not required. So I'm not sure you even need one (although...

@emmanuelproulx these are orthogonal concerns- the Media Type Object is just describing the response contents. Whether or not chunked encoding is used is set in `headers` in the Response Object.

@darrelmiller why wouldn't this be indicated through headers? I'm apparently misunderstanding something here.

@darrelmiller makes sense, thanks!

@kylebevans This sounds mostly like a tooling problem. And I still think that if you want to indicate streamed processing you should do so with a header (that can be...

@kylebevans well of course it depends on what your tooling supports. But at a glance this looks like the right approach for the header to me. If the response will...

But keep in mind, with the multiple JSON documents thing, this is a limitation of HTTP and not simply OpenAPI. At some point, OAS cannot be expected to describe arbitrary...