Evaluate the usage of official test suite by JSON Schema implementations.

[benjagm]

Slack Discussion: Link

Work Summary:

Understand how JSON Schema implementations are currently using the official test suite by JSON Schema to find missing and out-of-date tests. The resulting report would be beneficial and highlight why Bowtie is so important.

Requirements:

1. The list of JSON Schema implementations https://json-schema.org/implementations.html#validators or the smaller list of implementations bowtie supports https://github.com/bowtie-json-schema/bowtie/tree/main/implementations.
2. Access to the GitHub repositories of each implementation.
3. Search for a reference to the official test suite repository in the implementation's GitHub repository.
4. Determine the age of the version of the test suite being referred to and write down the commit hash of the test suite.

Expected outcome:

• A report with information about the usage of the official test suite by JSON Implementations, including which have missing or outdated tests.
• The report will provide a comprehensive overview of the adoption of the official test suite and the importance of using Bowtie to maintain up-to-date testing.

Do you think this work might require an Architectural Decision Record (ADR)? (significant or noteworthy)

No

Work Detail:

• The list of JSON Schema implementations https://json-schema.org/implementations.html#validators or the smaller list of implementations bowtie supports https://github.com/bowtie-json-schema/bowtie/tree/main/implementations.
• Access to the GitHub repositories of each implementation.
• Search for a reference to the official test suite repository in the implementation's GitHub repository.
• Determine the age of the version of the test suite being referred to and write down the commit hash of the test suite.
• Create document with the results.

Any further requirements to resolve this issue

[github-actions]

Hello! 👋

This issue has been automatically marked as stale due to inactivity 😴

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience ❤️

[pohwanimohit]

@benjagm
Observations & Analysis -->

1. Patterns Found:
   (e.g., Most JavaScript implementations use old commits, Python ones integrate directly, etc.)
2. Common Issues:
   (e.g., Some repos reference outdated forks, others have no visible linkage to the test suite.)
   3)Bowtie Relevance:
   (Explain how Bowtie helps unify testing, reduces staleness, and simplifies cross-implementation validation.)

Recommendations -->

1. Encourage implementations to:
   Reference the test suite as a Git submodule or with a scripted sync.
   Include automated checks to pull updates from the official suite.
2. Promote Bowtie as a shared, up-to-date framework for testing JSON Schema implementations.