Darrel

I'd be open to considering allowing HTTP method be an unconstrained string. I wouldn't want to re-enumerate all the methods in the IANA registry in the OpenAPI spec. We should...

Examples can be separated out into a different file using the `externalValue` property of the [example object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#exampleObject). Is this sufficient for your needs?

And we are back today!!

I'm having a real hard time creating a response to this. Let me start with some low hanging fruit. @dilipkrish In the example you show, you are not really describing...

@OAI/tsc (or at least some subset of it) agrees with @ahx assessment.

Proposal to start separate working groups to drive special interest areas: Overlays Working Group - Ron Security Working Group - Initially MikeR Scenario Descriptions - Phil Basic process (suggested): -...

@emmanuelproulx My recommendation in the past has been to use a stream by default and a byte array only if there is a maxlength defined.

@handrews You definitely can advertise that a server supports chunk encoding for a particular response using a header declaration. And I agree chunk-encoding and client side data representation are orthogonal...

We discussed this in the #1585 TSC meeting and the consensus was that tooling should interpret `{"type": "string", "format": "binary"}` as a stream of bytes and the `maxLength` schema property...

I agree that we want to enable ExpandDerivedTypesNavigationProperties. However, before we do that we must ensure the following things: - Where only a subset of derived types are supported on...