Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider whether '+' should work for Exceptions IDs too #346

Closed
swinslow opened this issue May 12, 2020 · 2 comments
Closed

Consider whether '+' should work for Exceptions IDs too #346

swinslow opened this issue May 12, 2020 · 2 comments
Labels
profile: licensing Licensing Profile and related matters
Milestone

Comments

@swinslow
Copy link
Member

It looks to me like the + operator only works with License IDs in the current syntax, not Exception IDs.

There was a discussion at spdx/license-list-XML#1027 (comment) about an instance where this would be nice to have. Further discussion in that thread indicated that it isn't necessarily required, but it's probably worth at least discussing as part of 3.0 whether this change is useful to make.

@swinslow swinslow added this to the 3.0 milestone May 12, 2020
@swinslow swinslow added the profile: licensing Licensing Profile and related matters label May 31, 2020
@goneall
Copy link
Member

goneall commented Apr 4, 2024

Since this would be a non-breaking change, moving this to a 3.1 milestone

@goneall goneall modified the milestones: 3.0, 3.1 Apr 4, 2024
@swinslow
Copy link
Member Author

swinslow commented Apr 7, 2024

There hasn't been any further discussion of this since my originally filing this issue nearly 4 years ago, so I'm going to go ahead and close it.

For the record, personally I don't see a need for this. I suspect it's vanishingly rare for licensors to use an "or-later" construct with regards to future versions of license exceptions. If someone really needs to communicate this in a license expression, they can always use a LicenseRef- or ExceptionRef-, or perhaps even suggest that the "or-later" construct be added to the official Exceptions List.

@swinslow swinslow closed this as not planned Won't fix, can't repro, duplicate, stale Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
profile: licensing Licensing Profile and related matters
Projects
None yet
Development

No branches or pull requests

2 participants