OASIS CSAF TC: Supporting version control for Work Product artifacts developed by members of TC, including prose specifications and secondary artifacts like meeting minutes and productivity code
I would suggest this links to the Github version of the schema for now. Later on, once it gets official, we should use of the official https://docs.oasis-open.org/csaf/ns/ namespace.
The schema should have an $id property. "The $id property is a URI-reference that serves two purposes:
It is best practice that every top-level schema should set $id to an absolute-URI (not a relative reference), with a domain that you control." https://json-schema.org/understanding-json-schema/structuring.html#the-id-property