Open
Description
Problem: how do we capture sets of related licenses, esp. Translations
- Proposed solution: treat every license as separate file, then describe relationship w/ new element?
- Any way to describe relationships among license groups such as official/unofficial translations, ported/unported, etc.?
- For EU Public License in German, that might look something like this:
<relatedLicenses>
<relatedLicense relationshipType="official-translation" targetLicenseIdentifier="EUPL-1.1">EUPL-1.1</relatedLicense>
</relatedLicenses>
...
Note: Up to 24 for EUPL, etc.
- Could this include license stacks (like newlib)? License stacks used as licenses? How to differentiate from license stacks used as informal package-license manifests?