Roadmap Discussion for JSON Schema – Community Input Needed

[benjagm]

Objective:
We’d like to open an issue to invite everyone in the JSON Schema Community to share their thoughts and proposals on our priorities for the next two years. The time for us is exciting, but it is important to have this discussion to make sure we invest our efforts in what is best fort JSON Schema Specification and the JSON Schema Community.

We encourage participation from everyone: users, contributors, implementers, adopters, sponsors, ambassadors, and the TSC. Your feedback and involvement are crucial in shaping our future direction.

Next Steps

Please share your thoughts as comments on this discussion. We want to hear your ideas, feedback, and suggestions!

How to Contribute:

• Comment below with your insights or proposals.
• If you have specific projects or initiatives in mind, please share those as well.
• Feel free to tag others in the community who should be part of this discussion.

Let’s work together to create a roadmap that reflects the needs and aspirations of our community. Your participation is crucial!

Thank you, and We look forward to our collective brainstorming!

[benjagm]

My proposal of focus areas are:

1. Specification

   • Stable Spec development.
   • Spec Development and publication lifecycle.

2. Open Governance

   • Strengthen our governance model to ensure transparency and inclusivity in decision-making processes.
   • Make it easier for contributors to join governing roles.

3. Support for Implementers

4. Ecosystem Collaboration

   • Foster collaborations with related ecosystems, such as OpenAPI.

5. Sponsorship Retention and Attraction

6. JSON Schema Conference

7. Join an Open Source Foundation

[gregsdennis]

I think (7) can probably help and inform a lot of this, especially (2) and (6).

[jviotti]

@benjagm 's proposal looks really good. What I would specifically highlight apart from that, is that we should double down on how we market ourselves. I want to fix what many others raised before:

• Lots of companies/developers are not even aware they are using JSON Schema because they thing its just OpenAPI, etc
• Lots of companies/developers think JSON Schema is just the configuration format of AJV
• As a consequence, we a LOT less attention that higher level projects that hugely depend on us. We should be making big fuss about who we are and the value we bring to the table

We need a plan to properly educate people and tackle these common confusions, otherwise everything else we do has less impact.