JSON schema principles

Explanation (Raw data)

General rule when converting checklists to JSON format:

As a general rule, non-optimized OSADL OSLOC checklists in JSON format are recursive associative arrays with the language construct as key and the related dependent text such as use case, license obligation or further attributes as value, but the value may be void. For example, a simple checklist in a file named CHECKLIST may read

USE CASE Source code delivery

YOU MUST Forward License text

YOU MUST Forward Copyright notices

IF Source code modification

YOU MUST Provide Modification report

YOU MUST Provide Copyright notices

USE CASE Binary delivery

YOU MUST Provide License text In Documentation OR Distribution material

which will become

in JSON format. Arrays with empty values can be converted to a string, if a single key exists or to a list, if more keys exist. Thus, after optimization the above checklist would become:

Special case:

Since a particular checklist hierarchy level may contain more than a single "EITHER", "OR", "EITHER IF" or "OR IF" element that are significant in the original checklist, but are not in the JSON format because the ordering is lost, an enumeration level had to be introduced. The checklist snippet

USE CASE Binary delivery

EITHER

YOU MUST Distribute Source code In Product

OR

YOU MUST Provide Delayed source code delivery

OR

YOU MUST Provide Source code Via Internet

EITHER

YOU MUST NOT Promote

OR

YOU MUST Credit Original authors

will be converted to the JSON snippet

or after optimization to

This additional enumeration ensures that the original checklist can be reproduced from the JSON version and that several JSON checklists can be combined and thus simplified (see also this project.).

JSON schema:

A schema to validate license checklists in JSON format (plain and optimized version) is shown below. This is version 2 of the schema. It validates single as well as merged licenses.

Last modified: June 7, 2024 02:01

Checklists project disclaimer

The above information has been assembled with maximum diligence and care; however, the authors do not warrant nor can be held liable in any way for its correctness, usefulness, merchantibility or fitness for a particular purpose as far as permissible by applicable law. Anyone who uses the information does this on his or her sole responsibility. For any individual legal advice, it is recommended to contact a lawyer.

Draft state note
Please note that the entire material of the checklists projects currently is work in progress and in draft state. It, therefore, cannot yet be used for any purpose other than its development. This draft state note will be removed when the material will be released.

Request for approval of checklists project participants

Please assist us to validate the above text. When clicking on the below button, you confirm that you approve the text in its current version taking into account the disclaimer below the text.

Request for feedback from checklists project participants

Please assist us to improve the above text taking into account the disclaimer below the text. Your feedback will be integrated into the text as soon as possible, and you will be notified. We gratefully acknowledge any comments, amendments and additions.

You may type or paste your text here.

Links