Hi SPDX community, I’m Suman Mandal, and I’ve been contributing to the tools-golang repository recently. I’m planning to apply for GSoC 2026 with SPDX and wanted to get feedback on a proposal idea.
While exploring the SPDX 3.0 implementation in tools-golang (particularly spdx/v3/v3_0/convert.go ) and the existing conversion chain, I noticed that forward conversion (SPDX 2.3 → 3.0) is implemented, but I wasn’t able to find an implementation for backward conversion (3.0 → 2.3). I’m considering proposing a project to implement backward conversion from SPDX 3.0 to 2.3, following the existing versioned conversion patterns. This could also help improve interoperability for downstream tools that rely on tools-golang for SPDX 3.0 support. The plan would be to: * start with core elements (Document, Package, Relationships) * expand incrementally to additional elements * validate using round-trip testing (2.3 → 3.0 → 2.3) * document expected lossy transformations Does this sound like a useful and reasonable direction for GSoC? I’d really appreciate any feedback on scope, approach, or priorities. Thanks for your time! Best regards, Suman Mandal GitHub: https://github.com/jijo-OO7 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2147): https://lists.spdx.org/g/spdx/message/2147 Mute This Topic: https://lists.spdx.org/mt/118603019/21656 Mute #gsoc:https://lists.spdx.org/g/spdx/mutehashtag/gsoc Mute #spdx:https://lists.spdx.org/g/spdx/mutehashtag/spdx Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/spdx/leave/2655439/21656/1698928721/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
