Hi Richard: <richard.purdie@...> wrote: I think there may be a different perspective to consider: Why include the GPL text if it does not apply (or for that matter for

You might want to consider using something more general, like LicenseRef-FSF-license-text or even LicenseRef-license-text, to use the same for all license files... -- zvr

Thanks, so to summarise, the answer is that: a) there are no SPDX identifiers for the license of a license text b) there are no plans to add any c) we can create our own namespace as mentioned above

Hi Richard, thanks for the detailed explanation -- I think I understand your use case better now. What I'd suggest would probably be that if you do want to represent this, one way might be to use a

Hi Steve, Thanks for the reply, it matches my first take on understanding this situation and is what we do today, however, we're seeing some push back from our users and I do think they have a point

"Steve Winslow" <swinslow@...> writes: It might be worth noting that one reason for this is that some license texts are not themselves released under an open source license, and

Hi Richard, Thanks for your email. A couple of thoughts, speaking just for myself: When it comes to the question of "what license applies to a license text," I think this is something that has

In the spirit of “any suggestions and/or modifications will be very much appreciated”, I have inserted comments below.

Hello all, The next regularly-scheduled SPDX legal team meeting will be tomorrow, Thursday, June 18, at 9AM PDT / noon EDT. I'm hoping that we can take a few minutes at the beginning of the meeting to

Hi Smith, Thanks for your well-laid-out email and your GSoC proposal. Trying to think about this from the perspective of the LicenseListPublisher repository over time, I would imagine the validity and

Hi all, I am working on a Google Summer of Code project that emanates from this discussion/issue; concerning the validation of license cross references. Here is a link to my GSOC proposal. The focus

To be clear: I'm agnostic about identifying snippets in a fixed work. REUSE looks to be trying to apply snippets to living open source code and the case that specifically concerns me is where the

We spent quite a bit of time discussing snippets in the SPDX technical working group. There are definitely a number of issues and considerations. At the conclusion of the discussions, there was a

I really think this is a recipe for disaster. What's wrong with simply keeping the licence of the file? since to be contributed, the snippet must be compatible with it. To put it another way, why

Hi all, At REUSE, we currently discuss how to correctly handling snippets from a third party, potentially under a different license [^1]. Since we strive to make as much use of SPDX as possible, I

Here a PR for the notes from the meeting: https://github.com/spdx/meetings/pull/2 --V

You have been invited to the following event. SPDX joint legal / tech team meeting When Tue Jun 9, 2020 1pm – 2pm Eastern Time - New York Where https://zoom.us/j/663426859

Hello all, the next regularly-scheduled SPDX legal team meeting will be this Thursday, June 4 at 9AM PDT / noon EDT. The main focus will be to review the status of issues for 3.10 that were assigned

Hi, I work on the Yocto Project and we use SDPX identifiers when working with open source licenses. An issue has come up and it was suggested I ask about it here. The question is quite

Hello all, the next regularly-scheduled SPDX legal team meeting will be Thursday, May 21 at 9AM PDT / noon EDT. Now that 3.9 has been released, there's a few things I'm hoping to focus on for this