-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add $id
to validation/schema.json
#52
Comments
Oh, one aspect of this that actually would be directly relevant to #51 is including versioning in said schema reference. This is valuable for any other schemas that would like to either use an explicit version of OSV (e.g. |
Perhaps the following?
|
Thanks for raising this! We can probably set this up to serve from https://ossf.github.io/osv-schema/ (rather than https://osv.dev), and track the different versions via branches/tags in the repo. We might need to tweak with the site generation (which is currently a Jekyll site) to do this, but I haven't looked too closely to figure out how feasible this is. Would you like to take a stab at this? |
See also: google/osv.dev#1166 |
Fixes #52 Per #132 (comment), the OSV schema must be fully backwards interoperable, meaning using main instead of a specific version tag is the sanest option. --------- Signed-off-by: Josh Buker <[email protected]>
@oliverchang I'm not sure what the best place for that to live would be, worst case scenario we can point it at the raw link for the main branch (https://raw.githubusercontent.com/ossf/osv-schema/main/validation/schema.json).
Relates to #51 somewhat (aiding parsers in knowing when an object is OSV, and what to expect from said OSV).
The text was updated successfully, but these errors were encountered: