unexpected error: Could not resolve the metaschema of the schema

[tschmidtb51]

I was trying to validate a JSON instance against its schema:

$ jsonschema validate ../csaf/csaf_2.1/json_schema/csaf.json ../csaf/csaf_2.1/test/validator/data/mandatory/oasis_csaf_tc-csaf_2_1-2024-6-1-06-01.json \
  -r ../csaf/csaf_2.1/json_schema/meta.json \
  -r ../csaf/csaf_2.1/referenced_schema/first/cvss-v2.0_strict.json \
  -r ../csaf/csaf_2.1/referenced_schema/first/cvss-v3.0_strict.json \
  -r ../csaf/csaf_2.1/referenced_schema/first/cvss-v3.1_strict.json \
  -r ../csaf/csaf_2.1/referenced_schema/first/cvss-v4.0.1_strict.json '
  -r ../csaf/csaf_2.1/referenced_schema/certcc/SelectionList_2_0_0.schema.json \
  -r ../csaf/csaf_2.1/json_schema/extension-metaschema.json \
  -r ../csaf/csaf_2.1/json_schema/extension-content.json -v

when the following error occurred:

unexpected error: Could not resolve the metaschema of the schema
Please report it at https://github.com/sourcemeta/jsonschema

So I opened this ticket. You can find all data and schemas at https://github.com/tschmidtb51/csaf/tree/csaf-2-1-csdpr01-feedback_extensions

PS: I patched the $id/id values in the CVSS JSON schemas by removing the part beginning with ? to make the tool work.

[jviotti]

Hey @tschmidtb51 , looking into this now!

[jviotti]

Fix incoming! I aim to release a new version in a couple of hours max.

[jviotti]

@tschmidtb51 Please try v14.13.4: https://github.com/sourcemeta/jsonschema/releases/tag/v14.13.4. The unexpected error cases should be gone and instead replaced with better explanations! If you hit any other problem, feel free to re-open the issue and we'll continue looking into it.

Also, always happy to help with any OASIS related work you are doing. If you have questions about JSON Schema or the tool, feel free to open discussions here or reach out through the JSON Schema Slack.

By looking at your repo, you might enjoy some of the other things we have in this tool, like the test and install command. We are trying hard to fix the JSON Schema development ecosystem, so any feedback or ideas you have while working on your repo, we would love to hear about them.