[OASIS Issue Tracker] (CSAF-42) JSON Schema file does not capture the license information for the schema itself.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Eric Johnson created CSAF-42:
--------------------------------

             Summary: JSON Schema file does not capture the license information for the schema itself.
                 Key: CSAF-42
                 URL: https://issues.oasis-open.org/browse/CSAF-42
             Project: OASIS Common Security Advisory Framework (CSAF) TC
          Issue Type: Improvement
            Reporter: Eric Johnson


In looking at on-the-fly modifications of the JSON for testing purposes, I note that the schema file itself includes no information about the license constraints on the schema.

We need to clarify with OASIS about what legalese needs to appear in the JSON schema file, so that we don't leave downstream consumers of the schema confused.

Even better if we can get permission from OASIS to allow the use of one of the standard open source licenses defined by the SPDX project.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)