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.

Sign up for GitHub

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

Jump to bottom

Change exception identifier to avoid confusion with SPDX spec #4

Closed
silverhook opened this issue Sep 13, 2018 · 2 comments
Closed

Change exception identifier to avoid confusion with SPDX spec #4

silverhook opened this issue Sep 13, 2018 · 2 comments

Comments

@silverhook
Copy link
Collaborator

REUSE specs 2.0 currently refers to the following tags:

  • Valid-License-Identifier to tag the actual text of a license (and License-Text to include a copy of its text)
  • SPDX-Exception-Identifier to tag the actual text of an exception (and Exception-Text to include a copy of its text)

While the license identifier tag was already changed in order not to clash with the SPDX spec’s own tags, the exception tag was not updated to match it. This can cause confusion.

I would suggest that we also change the license exception tag from SPDX-Exception-Identifier to Valid-Exception-Identifier.

For more info, see discussion on SPDX Legal mailing list.
silverhook added a commit to silverhook/reuse-docs that referenced this issue Sep 14, 2018
@silverhook
Changed exception identifier to be clearer re SPDX
b7268db 
Fixes fsfe#4

More info in the issue and on SPDX Legal mailing list:
https://lists.spdx.org/g/Spdx-legal/topic/change_use_of_spdx/24005641?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,24005641
@silverhook silverhook mentioned this issue Sep 14, 2018
Closed
@mxmehl
Copy link
Member

mxmehl commented Sep 5, 2019

Is this solved in REUSE 3.0?

@carmenbianca
Copy link
Member

No longer relevant in REUSE 3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix exception identifier silverhook/reuse-docs
3 participants
@silverhook @mxmehl @carmenbianca