Create vers-type-definition.schema-0.1.json

[mjherzog]

First draft of a VERS type definition schema

• Adapted from PURL type definition schema and VERS test schema
• Using JSON schema 2020-12 as requested by tschmidtb51
• Encountered error from https://www.jsonschemavalidator.net/ on line 113: After parsing a value an unexpected character was encountered: : (double-quote)

[mjherzog]

@pombredanne
I made some updates including use of prefixItems which is new with JSON Schema Draft 2020-12
Still getting an error on last line:
"Additional text encountered after finished reading JSON content: }."

I expect that this has something to do with pairing braces, but I cannot figure it out.
I also need your review of the schema content.

[johnmhoran]

@mjherzog I think there's an extra closing brace } at the bottom of the file.

[mjherzog]

@johnmhoran I expect that it is a problem with the braces, but when I remove the last closing brace I get different errors

[johnmhoran]

@mjherzog Can you paste the error text here?

[mjherzog]

I appreciate your help. The best way to reproduce is to open a browser tab for: https://www.jsonschemavalidator.net/
Use View file for https://github.com/package-url/vers-spec/pull/78/changes#diff-d967d379320cccad968a26d8cac921fd79af0a3c0c423b4329069cca6407d66a to get the text and paste it into the validator.
This way you can see the error in real-time and experiment with fixes.

[johnmhoran]

@mjherzog We've been using "$schema": "http://json-schema.org/draft-07/schema#", but your example uses "$schema": "http://json-schema.org/2020-12/schema#". Have we decided to move to 2020-12?

[mjherzog]

We had a specific request for this from the CSAF team so we should use the current version for a new standard imho. I used a 2020-12 feature for prefixItems.
I am proposing that we also upgrade for PURL but that is a separate question.

[johnmhoran]

@mjherzog Sticking with 2020-12, I saw that the error pointed to the "examples" object (line 116), that "examples" is one of the items listed under "required" (lines 28-35), and that each of the items under "required" -- except "examples" -- is listed (starting at line 36) under "properties". I moved "examples" to the "properties" object immediately following "description" (line 69), joining the other items listed under "required", and the modified JSON passed the 2020-12 validation.

[mjherzog]

@johnmhoran Hallelujah. Please update the PR to make that change if you can.

[johnmhoran]

@mjherzog I had thought I could not update someone else's PR, based on looking into the question a year or two back, but I do see an "edit" button and will click it and see what I can do. . . . Excellent -- I was able to replace with an updated and reformatted file and it still passes the 2020-12 check.

[mjherzog]

Outstanding - thank you!

[mjherzog]

@pombredanne Please review the schema for accuracy.