Gary, Sameer and I discussed it. We believe the LicenseInfoInFiles field would best be represented as a list of license expression expressions and therefore we agree with your recommendation.
Best, - Mark From: [email protected] [mailto:[email protected]] On Behalf Of Gary O'Neall Sent: Tuesday, February 10, 2015 11:20 AM To: [email protected] Subject: Conflict in OrLater licenses and LicenseInfosInFIles I just ran across an issue while preparing files for the Collab Summit. The "OrLater" is a complex license type according to the model. The LicenseInfoInFiles is of type SimpleLicensingInfo which does not include the OrLater type. The SPDX Tools parser is now flagging errors for the use of GPL 2.0+ which used to be an SPDX listed license, but is now an OrLater license. My proposed solution is to change the range of LicenseInfoInFiles to be AnyLicenseInfo. This would also allow conjunctive and disjunctive licenses, which we did discuss a couple years ago and rejected - but I'm thinking it may be OK to allow since the legal group is now talking about having a license expression for some of the SPDX listed licenses. Let me know what you think. Gary ------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: [email protected]<mailto:[email protected]>
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
