Skip to content

Need to be able to describe relationships between SPDX license-list files (new element?) #13

Open
@kestewart

Description

@kestewart

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?

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions