Tony Tam
There are many requests for finer-grained control over both ordering and visibility of elements, etc. These have been implemented in different integrations but might need to be in the spec,...
Currently, every single operation must declare its' own responses. This causes a whole bunch of duplication, which would be better served by having a top-level `responses` section in the spec....
Currently swagger-core is jackson-only, many users want to support GSON. Need to see how feasible this is, but it would be nice if user-selectable.
We should either throw an error or ignore creative, but invalid http verbs in the spec.
The java-jersey-jaxrs petstore is not setting an alternative name for `Pet`, nor is it declaring the response to be wrapped. Thus the definition does not match the payload.
https://github.com/swagger-api/validator-badge/blob/c7c2d84c4aa3fe798e1dcee213fc542b920148e2/src/main/java/io/swagger/validator/services/ValidatorService.java#L47
It is an important function in the inflector code but there is no documentation on it.
Should check for slash before prepending `swagger.json`
We need to provide some good examples of how to use inflector in a CI environment like Travis.