License compatibility

Explanation (Raw data)

Compatibility of a particular first (leading) license with another (subordinate) license becomes an issue when a work that is licensed under the other license is to be integrated into a common work and to be compliantly copied and distributed under the leading license.

Such compatibility is assumed, if

• compatibility with the other license is explicitly ruled in a particular license, or
• the two licenses in question both do not contain a copyleft clause, or
• the leading license contains a copyleft clause and the other license does not and also does not impose any obligation that the first license does not allow to impose.

Incompatibility is assumed, if

• incompatibility with another license is explicitly ruled in a particular license, or
• one license imposes an obligation that the other license does not allow to impose, or
• the two licenses in question both contain a copyleft clause and no license contains an explicit compatibility clause for this license combination.

In addition, the term "dependent compatibility" has been introduced. Such compatibility is assumed if the two licenses are incompatible, but one or both licenses explicitly allow the license to be updated to a newer version or to switch to another license that is then no longer incompatible. The respective change path is described in the "Interpretation" of the DEPENDING COMPATIBILITY line of the checklist.

Last modified: June 3, 2024 00:19

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