Chuck Heazel

One reason to provide multiple servers (or at least URLs) it that each server supports a different authentication protocol. Even if we have Security Requirement objects at the Path level,...

It comes down to access control and level of trust. If you authenticate using HTTP basic, I would have a rather low level of trust that you are in-fact who...

It's about being competitive in the market. A complex spec adds cost to the tool developers. An inadequate spec adds cost to the system developers. A spec which can not...

I'll vote for extensible enumerations. However, it would be useful if the enumerated values were resolvable. This allows a client to "discover" the meaning of an unknown value. If the...

@JonKohler Take a look at the Draft Features section of Development.md. This is a new process for test-driving proposed features prior to making them a formal part of the spec.

OpenAPI issue 1532 may help here. It is a proposal to allow multiple alternate schemas in the Media Type object. These alternate schemas are not restricted to JSON schema. This...

@cportele - Thanks. I'll put together an update reflecting the discussions at Mondays TSC meeting. We can discuss specific requirements under this issue.

See Pull Request #256 This may address at least some of the requirements.

The /info element serves this purpose. And we can extend it if necessary. Two key points: 1) An API is not a service. Not all of the info in a...

@pvgenuchten A valid point. I've mapped capabilities to OpenAPI, I can do the same for catalog metadata. A discussion of now a catalog would harvest an API would also be...