Hi Philippe, I’m a bit lost on what the goal of this is. Can you provide a bit more context.
I looked at a couple entries and noticed, for example, this one: https://github.com/nexB/spdx-license-namespaces-registry/blob/master/scancode/licenseref-scancode-bsd-innosys.spdx which then points to this: https://github.com/nexB/scancode-toolkit/blob/develop/src/licensedcode/data/licenses/bsd-innosys.yml which notes that this is common in the Linux kernel. Weren’t we going to add to the SPDX License List some of the other common licenses you all were finding in the kernel? Thanks, Jilayne > On Mar 7, 2019, at 10:44 AM, Philippe Ombredanne <pombreda...@nexb.com> wrote: > > See https://github.com/nexB/spdx-license-namespaces-registry/ > and https://github.com/nexB/spdx-license-namespaces-registry/pull/1 > > -- > Cordially > Philippe Ombredanne > > +1 650 799 0949 | pombreda...@nexb.com > DejaCode - What's in your code?! - http://www.dejacode.com > AboutCode - Open source for open source - https://www.aboutcode.org > nexB Inc. - http://www.nexb.com > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2558): https://lists.spdx.org/g/Spdx-legal/message/2558 Mute This Topic: https://lists.spdx.org/mt/30299819/21656 Group Owner: spdx-legal+ow...@lists.spdx.org Unsubscribe: https://lists.spdx.org/g/Spdx-legal/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
