Gary O'Neall

I can create a PR to fix if there is agreement the OSI Approved attribute should be set to false for these licenses.

Thanks @swinslow - very useful history! My reading of the thread is that they are very likely OSI approved, so we probably should not change the SPDX license list OSI...

@jlovejoy Let's leave this open for now - there is still an inconsistency between the OSI website, [OSI GitHub metadata](https://github.com/OpenSourceOrg/licenses) and the SPDX license list. Although the description makes sense,...

Here's the error from the validation: ``` Test for license SugarCRM-1.1.3 failed: Test for license ID SugarCRM-1.1.3 failed due to difference found Normal text of license does not match starting...

Just another note - if there are license texts similar to those in the current test file, we'll need to add variable text markers to allow both versions to match.

> Depending on what's more convenient for you, I can create a new clean PR with the tests also corrected or add commits to this one. Either approach is fine

The format for Regex is [POSIX extended regular expression (ERE)](http://pubs.opengroup.org/onlinepubs/9699919799/). The Regex format is specified in the [license template subsection](https://spdx.github.io/spdx-spec/appendix-II-license-matching-guidelines-and-templates/#spdx-license-list-template-access) of the license matching guidelines.

FYI - there is a GSoC project to update the Python license matching library now known as [yalm](https://github.com/m1kit/yalm-python)(yet another license matcher). One of the challenges we are facing in this...

I'm going to assign this one to myself so I can coordinate with the GSoc project on the updates.

@swinslow I don't see anything obviously wrong - so I also suspect the tool. I found the XML file above - I'll take a look and update the issue on...