Discussion: how to handle SPDX Spec version 3 dot releases
还没有人认领这个 Issue。
评估
调研方向
首先审查 spdx-model-to-java 代码生成器，以及该库目前如何处理 SPDX 2 规范版本。比较四种提议的 package 和 interface 方案，包括 enum 兼容性和先前版本的验证；当维护者就应如何表示 SPDX 3 的点版本达成决定时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Adding support for the SPDX 3.1 release will require an update to spdx-model-to-java code generator to support multiple dot releases of the spec.
The simplest approach would be to just add another package specific to the dot release (e.g. org.spdx.library.model.v3_1).
This, however, will require all applications that access the model through Java update their imports to the new version - including the utilities in this library.
Since dot releases are backwards compatible, we could create a package which is always the "latest" - this is similar to how we treat the SPDX 2 spec versions.
I can think of a few specific alternatives:
- Just produce the latest version and drop support for earlier dot releases
- Produce one package per dot release
- Produce one package per dot release plus a "latest" package (e.g.
org.spdx.library.model.v3_latest) - Use interfaces rather than class hierarchies and use multiple interfaces and an interface hierarchy to create a common interface that would work across all versions
In looking into 4, I ran into problems with the enums since you can not extend the enum classes and there is no straightforward way that I could find to support a compatible enum class that allows extensions for later dot releases (e.g. adding additional relationship types). 4 is also the most complex and involved solution.
Implementing 3 would be straightforward and I believe will support most use cases.
2 has the issue of requiring code updates on every release to change the imports.
1 doesn't support validating previous versions.
- 主要语言
- Java
- 星标
- 71
- 派生
- 44
- 平均合并
- 16 小时 17 分钟
- 30 天内合并 PR
- 9
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
spdx/Spdx-Java-Library 的其他 Issue
-
question
难度 5/5 一周以上 新手友好度 30/100
spdx/Spdx-Java-Library#449 ·
-
question
难度 5/5 一周以上 新手友好度 30/100
spdx/Spdx-Java-Library#398 ·
-
wontfix
难度 3/5 1-2 天 新手友好度 45/100
spdx/Spdx-Java-Library#393 · 2 条评论 · 1 个 reaction ·
-
matching
难度 5/5 一周以上 新手友好度 35/100
spdx/Spdx-Java-Library#392 · 4 条评论 ·
-
matching performance
难度 4/5 3-5 天 新手友好度 35/100
spdx/Spdx-Java-Library#369 · 3 条评论 · 2 个 reaction ·
查看 spdx/Spdx-Java-Library 的全部 Issue
相似的 Issue
-
[BUG] S3 CORS responses omit Access-Control-Allow-Credentials for matched origins可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
sqlcipher/sqlcipher-android#97 · 1 条评论 ·
-
area-integrations
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
bug IIIF interoperability
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 72/100