Open kestewart opened 7 years ago
From discussions in brainstorming google doc
I believe this is non-breaking - so moving to 3.1.
@kestewart - if you disagree, please move back to the 3.0 milestone.
To the extent this was about representing "official translations" of licenses, there was a discussion in license-list-XML at https://github.com/spdx/license-list-XML/issues/438 about this a few years ago, with the general outcome deciding not to implement changes to the license-list-XML fields or syntax.
If there is anything here to be discussed, I'd be inclined to suggest moving the discussion to license-list-XML since I suspect that's where any changes would be implemented. (At least, unless / until the license-list-XML fields are documented formally as part of the spec itself, which I think may be part of what #32 is about.)
Problem: how do we capture sets of related licenses, esp. Translations