Help and clarify how JSON Schema can be interpreted from validation rules to data definition. This extends to how those data definitions can be represented in any programming language
While the project is only first getting started, the initial agenda is:
- Define a processing model for interpreting JSON Schema to data definitions.
- Define code generation vocabulary as needed, while the processing model is being defined
To help explain the process, the project, the SIG and the community, in terms of how they all relate, please refer to the charter.
Respect each other. Choose empathy over judgement. Act according to the Code of Conduct.
If you want to review changes, creating documentation, help form suggestions or take charge in figuring out a specific task, we welcome any way you want to get involved.
If you find an issue you would like to work on you can drop a comment, ask questions or discuss the approaches. Or if you see we are missing specific things feel free to create new issues.
We have a dedicated slack channel #vocab-idl- in the JSON Schema slack, join the JSON Schema slack here: https://json-schema.org/slack.
You can use this channel if you don't know where to get started, discuss specifics of issues, get updates, or in general hang out.
In case contributions are for changing content on git, please refer to git workflow.
Any contributions that changes the content of this repository MUST go through pull requests.
Thanks goes to these wonderful people (emoji key):
 Ben Hutton 👀 |
 Jason Desrosiers 👀 |
 Jonas Lagoni 📖 |
 Henry Andrews 🤔 |
 Karen Etheridge 🤔 |
This project follows the all-contributors specification. Contributions of any kind welcome!