[asterisk-dev] swaggerVersion

[David M. Lee]

On Aug 12, 2013, at 6:23 PM, Paul Belanger <paul.belanger at polybeacon.com> wrote:

> We appear to be running a mix of 1.1 and 1.3 for the json schema's
> generated by Swagger. Could we move everything to 1.3?

Possibly, but not likely. (And, re-reading with fresh eyes, I think it should be 1.2 instead of 1.3. I'll ping them for clarification).

The only resource that uses the updated Swagger spec is the /events resource, and only because Swagger 1.1 models were unable to represent our events model.

I believe that the updated Swagger spec (whether it's 1.2 or 1.3) is still being developed. If that's the case, I'd rather avoid that where we can. Since the /events resource is the only thing for which Swagger 1.1 was insufficient, everything else will probably stick with Swagger 1.1.

We're also past feature freeze. While using mixed versions of Swagger for the API's isn't ideal, I don't know if it's something that we would say is broken.

> If I am reading Swagger's documentation correctly, they have now have
> support for json schema draft 4 and more json schema compatibility
> fixes.

Interesting. Last time I chatted with those guys[1] about schema models, they were sticking with their own custom schema due to JSON Schema limitations.

 [1]: https://groups.google.com/d/msg/wordnik-api/EC3rGajE0os/ey_5dBI_jWcJ

> Right now I am having issues getting the current schema to validate
> according to http://json-schema.org/

Can you be a bit more specific?

I'll hit up the Swagger ML to check on the status of their new spec.

-- 
David M. Lee
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at:  www.digium.com  & www.asterisk.org