For a long time, json-schema was stuck at draft-04, and it looks like in the last few months under new authorship it's up to draft-07. The mapping of these names to IETF RFC revisions is more complicated, and explained on the site [1].
Json-schema is useful for describing JSON data structures in JSON, so you can bring a codegen and generate corresponding structures in your language, or perform some payload validation at an API gateway; and many higher-level API specs -- like OpenAPI/Swagger -- make use of Json-schema underneath.
However, I'm not sure I fully understand why they branched out into also becoming a hypermedia description language [2] when there's already half a dozen others in this space [3], and reading some of the discussion about this [4] makes my head hurt.
Json-schema is useful for describing JSON data structures in JSON, so you can bring a codegen and generate corresponding structures in your language, or perform some payload validation at an API gateway; and many higher-level API specs -- like OpenAPI/Swagger -- make use of Json-schema underneath.
However, I'm not sure I fully understand why they branched out into also becoming a hypermedia description language [2] when there's already half a dozen others in this space [3], and reading some of the discussion about this [4] makes my head hurt.
[1] http://json-schema.org/specification.html [2] http://json-schema.org/latest/json-schema-hypermedia.html [3] https://sookocheff.com/post/api/on-choosing-a-hypermedia-for... [4] https://github.com/json-schema-org/json-schema-spec/issues/4...