> I could really benefit from some sample SPDX files. I am currently
> using the ones
> from https://github.com/goneall/SPDX-Tools/tree/master/Examples
> and https://github.com/triplecheck/reporter/tree/master/run/reports

Usually the SPDX documents you find on the triplecheck git were automatically generated, except perhaps for the AdblockPlus spdx where you find fields set by an auditor such as:
- LicenseConcluded
- ArtifactOfProject

Static location of this specific spdx is:
https://github.com/triplecheck/reporter/blob/6d99b92a1103fcb2e68f9b75aff28a8920636976/run/reports/adblockplusandroid-2014-06-01.spdx

The second SPDX that I'd recommend testing is this one:
https://github.com/triplecheck/misc/blob/master/misc_spdx/linux-coreos.spdx

This a single SPDX using the Linux kernel as example. Has some 46000 files listed with some 20k licenses declared. Uses some 20Mb of disk space and has some 440K lines of data. The kernel represents a project with 14M lines of code, so I used this code as upper limit test that stresses the parser/writer.

The first parser/writer that I've implemented wasn't able to digest bigger projects. On the second version, using a normal laptop (i5 CPU, 4Gb RAM) I'm loading the same SPDX under a second with each field interpreted. A blog post was written with more details at http://nunobrito1981.blogspot.de/2014/05/java-parsing-text-files-with-minimum.html (don't know if it will apply to your case).

In either case, I hope these two SPDX files already give some real-world examples. I'd also love to have some feedback in regards to their compliance with the standard specification and how well other tools can digest them.

I'm gathering the SPDX documents from other sources that I could find at https://github.com/triplecheck/misc/tree/master/misc_spdx


If there's anything else where I can help, please do let me know.


With kind regards,
Nuno Brito
_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech

Reply via email to