You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compared to the SPDX 2.3 UML class diagram, the SPDX 2.3 ExtractedLicenseText is named CustomLicense. There is also an additional abstract class in SPDX 2.3 SimpleLicensingInfo which is a superclass of both License and ExtractedLicenseText.
Since the class is concrete, the name change will impact serializations. We should either change the name back or write up some reasoning for the change.
The abstract classes have less of an impact. I personally like the proposed 3.0 structure, but it will create some incompatibilities in some of the current libraries.
The text was updated successfully, but these errors were encountered:
Thanks @goneall. For this one, I'm inclined to keep it as CustomLicense. I think that the context change from the historical ExtractedLicenseText name is sufficiently different that CustomLicense is an appropriate name here.
Hopefully this also won't cause compatibility problems for tooling such as with the LicenseExpression vs. AnyLicenseInfo item in #222.
Compared to the SPDX 2.3 UML class diagram, the SPDX 2.3
ExtractedLicenseText
is namedCustomLicense
. There is also an additional abstract class in SPDX 2.3SimpleLicensingInfo
which is a superclass of bothLicense
andExtractedLicenseText
.Since the class is concrete, the name change will impact serializations. We should either change the name back or write up some reasoning for the change.
The abstract classes have less of an impact. I personally like the proposed 3.0 structure, but it will create some incompatibilities in some of the current libraries.
The text was updated successfully, but these errors were encountered: