(re)classifying FOSS licenses
summary
Proof-of-concept license reclassifier extends Herminé’s clause-and-trigger model to check compatibility between obligations rather than full-license matrices, encoding rules as JSON rules that compile to Python checks and producing a generated compatibility matrix. It finds that about 15 expressions cover most obligation comparisons, handles exceptions and dual-licensing, flags mismatches (e.g., GPL “no further restrictions” vs Apache patent clauses), and passes preliminary tests against existing resources while trading some precision for readability.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 1:06License compatibility basics
- 3:17Context in license compatibility
- 5:02Defining license obligations
- 6:30Hermine data classification
- 8:00Default yes approach
- 10:08Compatibility matrix values
- 12:02JSON specification rules
- 13:07Use case and results
related talks
26mThe FOSSology Project – Open Source Software for Open Source License Compliance
29mFOSS, AI & non-code artifacts: What’s new and noteworthy?
31mLicense Compliance 101
26mThe FOSSology Project – Open Source Software for Open Source License Compliance
30mOpen Source Licensing: Use Versus Abuse
01h 38mOpen Source Licensing: Types, Strategies and Compliance
42mWhy and How We Updated Our License Policy for Use of Open Sou...
14mOpen Source Licensing in a Business World