Good points.
On #1, if I publish the web pages to spdx.org/licenses/preview a manual review
of the license text could be performed - a bit labor intensive, but possible.
I like the idea of #2 - It would require maintaining the original text files
along with the XML for test purposes. We
Would this also be an opportune time to think about/discuss (1) a one-time
check that our manual modifications haven't borked the text? and (2) some
type of continuous integration or unit testing to make sure our changes
don't screw up matching against texts we believe should always match?
--
I do think we'll want some sort of XML manifest; we need at least somewhere to
define the synonyms, among other bits.
From: Gary O'Neall [mailto:g...@sourceauditor.com]
Sent: Sunday, May 15, 2016 14:26
To: Kris.re ; 'J Lovejoy' ;
'SPDX-legal'
Hi Kris, Jilayne and legal team,
I'm seeing a lot of activity on the XML licenses, so I started looking into
expanding the tools that generate the website to support the new XML format.
Here's what I'm currently thinking:
- write a new command line tool which takes three parameters, a tag