Open Collective
Open Collective
JSON Schema draft 2020-12 patch 1 RC-0
Published on May 5, 2022 by Ben Hutton

Feedback for RC-0 closes on 2022-05-14.

Patch release?

"What the heck is a JSON Schema patch release?" I hear you say?
Glad you asked. Let me explain.

We've done a patch release once before, but you might not have noticed. And that's OK because patch releases are non-functional updates to the specification documents.

Although the notion of a patch release existed, we hadn't formalized the process. There's a GitHub Discussion outlining the proposal, which has been broadly accepted. Patch releases focus on fixes and clarification and avoid any feature changes or anything that would require an update to any of the meta-schemas.

Call to review

You can view the first release candidate, RC-0, by taking a look at our seldom updated work-in-progress page:

Here is some of the information duplicated for your convenience.

You can find RC-0 preview of the following documents:
There are no changes to the Relative JSON Pointer specification.
View the git diff on GitHub for:

How to provide feedback for RC-0

Please make use of the two-week feedback window for RC-0 by either:
Please remember, only feedback relating specifically to the changes found in the above diff is useful. This release is not making functional changes.

2022-Q2 - Organization and community updates

One of the biggest struggles I feel JSON Schema faces is being visible. JSON Schema is often used without people even realising it. It's often seen as a configuration file for validation or form generation.

We're trying to do a better job of telling the JSON Schema story.

To help make people more aware of JSON Schema, we created our YouTube channel, and as of today, we're only 10 subscribers away from being able to claim our own short URL.
Our first video series, "JSON Schema in Production", has reached a total of three recordings, however for written case studies, only one is published.
It has taken considerably more effort to manage and create these case studies than I had anticipated. I've mentioned previously that JSON Schema was looking to hire for two roles (via Postman), and the uncertainty of how soon those roles would be filled has left me in a situation where I've found it hard to plan for Q2. 

After chatting with Fran, my colleague at AsynAPI, I came to the understanding that maybe OKRs (Objective, Key Results) don't need to be different each period if not met. I'm still feeling my way a little with OKRs.

I hope that with a slightly larger full-time team, JSON Schema can build a lot clearer direction moving forward. There are so many immediate concerns that looking far forward into the future has been challenging. There should be some more news on this in the coming months.

I'll leave it there for now, as I really wanted to get this out to you sooner, but I've been somewhat time-limited.

Feel free to reach out with any questions, either on our Slack server or via Twitter.