If you think that JSON Schema is too big and complex for your needs, you can have a look at JSON Type Definition (JTD). It’s a new standard for defining JSON schemas that became an experimental RFC in November 2020. One downside of JTD is the lack of granular data validation. But, it offers simplicity, and perhaps in future, an IETF-backed specification.
This document proposes a format, called JSON Type Definition (JTD), for describing the shape of JavaScript Object Notation (JSON) messages. Its main goals are to enable code generation from schemas as well as portable validation with standardized error indicators. To this end, JTD is intentionally limited to be no more expressive than the type systems of mainstream programming languages. This intentional limitation, as well as the decision to make JTD schemas be JSON documents, makes tooling atop of JTD easier to build. This document does not have IETF consensus and is presented here to facilitate experimentation with the concept of JTD.
RFC 8927: JSON Type Definition
Il existe plusieurs langages pour décrire la structure d'un document #JSON. Aucun ne fait l'objet d'un clair consensus. Sans compter les nombreux programmeurs qui ne veulent pas entendre parler d'un schéma formel. Ce nouveau #RFC décrit un de ces langages, #JTD, JSON Type Definition. Une de ses particularités est que le schéma est lui-même écrit en JSON.