JSON Schema file does not capture the license information for the schema itself.

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      Note that I also filed issue [806|https://github.com/json-schema-org/json-schema-spec/issues/806] wit the json schema project to see if we can't get some standard way to include this in the data model for a JSON Schema.

      If such a proposal is accepted, then I suggest that this JSON schema use what ever comes out of that proposal.

      Show
      Note that I also filed issue [806| https://github.com/json-schema-org/json-schema-spec/issues/806 ] wit the json schema project to see if we can't get some standard way to include this in the data model for a JSON Schema. If such a proposal is accepted, then I suggest that this JSON schema use what ever comes out of that proposal.

      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.

            Assignee:
            Unassigned
            Reporter:
            Eric Johnson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: