Greetings all,
Since we didn't have much time to discuss the license list XML work on this week's legal call, I thought I would send an email update to the distribution list and point out a few remaining issue and next steps. Over the past couple of weeks, we enhanced the SPDX tool that generates the spdx.org/licenses website to test the license templates generated from the license-list-XML repo against the previous license list text. Basically, checking to see if the license text currently on the spdx.org/licenses website would match the new files generated. In the first run of the test, there were a few dozen error reported. Some of the errors were due to bugs in the tools which have now been corrected. Some of the license XML files have been updated and Trevor contributed improvements to the license XML schema as well. There were a few licenses which did not match due to var and/or optional text being nested inside an optional text block. This is not currently supported by the license matching tools. There is a discussion on this topic in issue #462 <https://github.com/spdx/license-list-XML/issues/462> . The other issues found were due to various differences including some character encoding issues. All of the open issues can be found in the issues list <https://github.com/spdx/license-list-XML/issues> . One item we may want to discuss on the mailing list and/or on the next legal call is where we should support var and/or optional text being nested inside an optional text block (issue #462 <https://github.com/spdx/license-list-XML/issues/462> ) in the next release of the license list. Adding this functionality to the tools is a pretty significant task and requires a partial redesign of the template matching code. It would also require an update to the license template documentation in the SPDX specification appendix and possibly other implementation of the license matching algorithms. An alternative would be to replace the nested optional and var blocks with a single var block utilizing a more complex match regular expression. Another alternative would be to postpone implementing the complex optional text to a subsequent release of the license list. Please see issue #462 <https://github.com/spdx/license-list-XML/issues/462> for a more complete discussion. Please feel free to fix any identified issues that are not related to issue #462 <https://github.com/spdx/license-list-XML/issues/462> . Gary ------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: <mailto:g...@sourceauditor.com> g...@sourceauditor.com
_______________________________________________ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
