Hmm, so the types are not actually a part of the JSON output, but they live in a separate schema. That being the case, I would've preferred if this were built o

Hmm, so the types are not actually a part of the JSON output, but they live in a separate schema. That being the case, I would've preferred if this were built on top of http://json-schema.org/ http://json-schema.org/ instead of something entirely new and Python-specific. It seems like for the past couple of years JSON-schema has been just below some critical treshold for it to take off. Why not define models with JSON schema instead of a custom format for each web framework? Why not use JSON schemas to build forms, validation logic and admin interfaces, like https://github.com/jdorn/json-editor https://github.com/jdorn/json-editor does? Why not document your API by specifying the JSON schema a GET request returns? (http://raml.org/ http://raml.org/ sort of does this). Seems like a chicken and egg problem where currently the tools are not yet nice enough to merit widespread adoption, but with widespread adoption they'd get to be really nice and cross-platform.