Darrel

@t1 One of the goals we keep reminding ourselves of when updating this spec is we want it to be as straightforward as possible for people to build tools around...

@wohnemus OpenAPI has never had the goal of describing a dynamic hypermedia API. The idea of a static API description and hypermedia are contradictory goals. I spent 6 years building...

@bassmanitram 6570 URI Templates support what you describe, `/seg1/seg2{/restofPath}` We can easily add this syntax by introducing a new style value. That's not a problem. I do understand the need....

@stevendearborn For consistency, I would agree that having SecurityRequirement objects at the path level would be logic. @cmheazel Can you expand a little on why multiple servers that expose the...

@cmheazel It's not about "requiring" that all servers implement the same security scheme. It's a cost/benefit argument for adding the ability to limit some servers to only use some security...

It is good to see someone making an effort to standardize an application protocol on top of WebSockets. However, until WAMP makes it out of IETF draft status (especially expired...

An alternative solution that could potentially also address this concern is to introduce the notion of a globally defined array of OperationTypes. In the same way that there can be...

@mpnally That's definitely an interesting workaround even with the JSON limitation. However, there is additional value to being explicit about the operation type. When it comes to creating client code,...

@davidnewcomb > REST interface definitely has a preference for path-based parameters Can you point to specifications that substantiate this claim? My understanding is this a misconception based on text in...

@davidnewcomb I agree that using only the path to identify the resource is a nice simplification that is sufficient for most cases. However, a significant number of people come to...