Hi Hen, Thanks for letting us know. As per SPDX License List Matching Guideline 1.2, “extraneous” text that is not part of the substantive license text can be ignored for purposes of matching. See htt

Hi All, We have our next call tomorrow at the usual time and place: https://wiki.spdx.org/view/Legal_Team We are a bit late on getting version 3.3 of the SPDX License List out, so we’ll focus on ident

correct. SPDX’s goal is to create a common language with which to communicate information about (open source) software. The SPDX License List was born out of the recognition for efficiency in referrin

Philippe is correct. We didn’t have written guidelines (aka, the “inclusion principles) for the first few iterations of the license list. If memory serves, all the CC licenses were recommended to be a

Hello Matt, SPDX does not approve or certify licenses as “OSS compliant”. You might be thinking of the Open Source Initiative (OSI) which maintains the Open Source Definition and reviews licenses that

Richard, As the author of the license, do you have any input/preference as to the full name and identifier? (we usually try to ask the author, if the license is not submitted by the author) Thanks, Ji

dial-in info here: https://wiki.spdx.org/view/Legal_Team Jilayne SPDX Legal Team co-lead opensource@...

Hi all, Sorry for the last minute notice, but I need to cancel todays’ call. We’ll be back to our regularly scheduled program in two weeks. Thanks, Jilayne SPDX Legal Team co-lead opensource@...

We’ll pick up with going through “old” issues, cleaning out. Sorry for late notice! Jilayne SPDX Legal Team co-lead opensource@...

Hi all, We'll have our usual meeting today but keep it somewhat short and focus on reviewing and providing feedback for the XML editor. If you haven't had a chance to check it out please do so! Jilayn

Hi all, I just gave the XML editor a test run – using the Sendmail license differences - adding alt tags - as a test run. This way, maybe we can use this PR, instead of deleting 😉 First observation: e

Hi all, I did a merge and compare and looks like most of the changes should be accommodated via markup (for different names) – see green highlighting in attached. There is one extra bit (in yellow hig

Hi all, Meeting minutes have now been posted for the last couple meetings: https://wiki.spdx.org/view/Legal_Team/Minutes/2018-07-12 and https://wiki.spdx.org/view/Legal_Team/Minutes/2018-07-26 We had

at the usual time! We’ll try to focus on some of the really old issues or tasks that have been hanging around, and then look at any new issues. Update on the XML editor (GSoC project) if anyone has ha

HI all, I’ve updated this, including one of Trevor’s additional edit below for the first bullet (the other suggestion you had was the same as I had, but my strikethrough seemed to have gotten lost in

HI all, We have the monthly SPDX General call in about 15’ - this is of special interest to the legal team, as the GSOC student working on the XML translator is presenting! Our bi-weekly legal call fo

I’ve now updated the page further to remove references to the spreadsheet and a few other minor outdated items. I also updated the field names to be more accurate and consistent with what one sees on

One other reminder: The SPDX general call is next Thursday (instead of today, due to holiday in US this week) on July 12th - the guest speaker on that call will be the Google Summer of Code student, T

Hi all, Meeting minutes from last week are posted here: https://wiki.spdx.org/view/Legal_Team/Minutes/2018-06-28 As per the discussion on updating URLs to licenses that was going on in a couple places

HI David, Thanks for your email. We endeavor to keep identifiers consistent and only change them under very compelling circumstances. The somewhat recent change to using “or-later” as part of the iden