Discussion of tooling ecosystem and gaps
summary
RC1 of SPDX 3.0 (model) exists and RC2 aims to land in about two to three weeks with a JSON-LD serialization spec; prototypes and libraries for Python and Java are already usable (Java tends to be faster; Python had a recent performance fix but processed a 2.2M-line JSON overnight). There is a shared spdx test bed for unit tests and a tools page listing version support; profiles (core plus AI, security, build, etc.) can be combined; gaps: Rust client missing, Go arriving, JS planned, and documentation/CI integration still needs work.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:14SPDX 3.0 feedback
- 3:19Release timeline RC1
- 6:10SPDX 3.0 adopter feedback
- 7:37Accessing SPDX 3.0 specs
- 10:50Machine-readable field definitions
- 14:21Version flexibility in dependencies
- 20:07JSON-LD context support
- 21:09Post-3.0 roadmap hardware
- 23:20Business profile OSCAL integration
- 24:23Tooling landscape feedback
- 26:54Python library updates
- 30:04Ecosystem SBOM connections
- 32:51Tool quick start guides
- 35:01Tooling awareness initiatives
- 36:03Closing remarks
related talks
07mTooling and Sharing Traceability Discussion
48mThe State of OpenAPI Specification: what's new in 3.1
14mExploring possibilities for integrating StrictDoc with ELISA's requirements temp...
25mJSON Schema - draft 2020 and other things you should know
24mSpeculative Development
21mLet there be docs!
54mPanel: Mechanized Specifications for Real-World Programming Languages
29mStop Documentation Debt: Industrialize Your ADRs and READMEs with Spec-kit