On petek, 06. september 2019 05:35:48 CEST, J Lovejoy wrote:
I really wouldn’t conflate attribution and copyright notices -
that seems to lead to a lot of unnecessarily confusion and other
energy
FWIW - this reminded me that there are some licenses that
require a specific acknowledgment (I’m
better late, than never...
> On Aug 22, 2019, at 8:34 AM, Matija ?uklje wrote:
>
> On Sunday 28 July 2019 22:16:34 CEST
> garysourceaudi...@gmail.com wrote:
>> [G.O.] First a disclaimer - I have not implemented this specific
>> use case in an SPDX document, but here is one approach: For the
>>
On Sunday 28 July 2019 22:16:34 CEST
garysourceaudi...@gmail.com wrote:
> [G.O.] First a disclaimer - I have not implemented this specific
> use case in an SPDX document, but here is one approach: For the
> origin package, create a package definition (you can use
> FilesAnalyzed=False to keep the
Hi Matija,
> -Original Message-
> From: Spdx-legal@lists.spdx.org On Behalf Of
> Matija ?uklje
> Sent: Wednesday, July 24, 2019 11:14 AM
> To: SPDX-legal
> Subject: How to best handle modification notices and notices of origin in SPDX
>
> Hi all,
>
> rec
Hi all,
recently I’ve been thinking about how to store¹ additional notices that are
required by some licenses on the SPDX license list. Specifically reference
to the origin of the work, and notice of modification of original work.
I’m sure people on this list are very well aware of the notice