Discussion: Support for SPDX 3.0

I was originally thinking that it would be too difficult to support the SPDX 3.0 in a spreadsheet format.

I may have come up with an approach that could implement it through a code generation process similar to the spdx-model-to-java code generator. Possible just an extension of the code generator.

The output would be:

• One sheet per Element type with the name of the sheet derived from the type name
  • We would only generate a sheet if the Element of that type was actually found
  • The sheets should be sorted in some logical fashion (e.g. Documents first, Collections second, ...)
• One row per Element of that type
• One column per property within the element
• Non Element object types would be flattened as additional columns with the names derived from the non Element class name and property name
• Values for properties with a range of an Element would be the Element ID

Questions:

• Would this be of value? Are there people/organizations who would use this?
• What feedback or improvements can be made to the design approach?

Start by reviewing the proposed SPDX 3.0 spreadsheet design and the linked spdx-model-to-java code generator. Compare the proposal with the existing spreadsheet storage behavior, then gather feedback on value and design. Done would require an agreed implementation approach and scope before coding begins.