JSR:评估规范与构建实施规范

发布于 2024-12-18 04:55:40 字数 280 浏览 8 评论 0 原文

请任何人解释一下两者之间的区别:对于任何可用的 JSR 流程,评估规范与构建实现的规范,例如,JSR 299

有时这是很有价值的信息来源,但对于我作为一名开发人员来说,我应该下载并阅读哪一个?令人烦恼的是,有时这两者是相同的。

有什么想法吗?

Could anyone, please, explain what is the difference between the two: Specification for evaluation vs Specification for building an implementation for any available JSR process, for example, JSR 299.

Sometimes this valuable source of the information, but for me as a developer which one should I download and to read? What annoys a lot - is that sometimes these two are the same.

Any thoughts?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

无人接听 2024-12-25 04:55:40

区别在于您在下载规范之前接受的许可证。我很惊讶您在仔细研究每个文档时没有注意到这一点!对于我检查过的 JSR,文档是相同的 — 包括文档中内嵌的实施许可证。

评估链接提供了用于评估规范的“有限评估许可证”。我认为这是针对 JCP 参与者、公共评论员和想要了解该规范的应用程序开发人员的。

实施链接为实施者提供了许可证。他们获得免版税许可,可以在某些条件下分发实现。宽松地解释一下,这些要求包括:实现完全实现规范,实现不会修改 java 包命名空间超出规范允许的范围,并且实现通过适用的 TCK。

The difference is in the license that you accept before downloading the specification. I'm surprised you didn't notice this as you carefully studied each document! For the JSRs I've checked, the documents are identical—including the implementation license in-lined in the document.

The evaluation link offers a "Limited Evaluation License" for evaluating the specification. I think this is aimed at JCP participants, public commentators, and application developers that want to understand the specification.

The implementation link offers a license to implementers. They get a royalty-free license to distribute implementations under certain conditions. Paraphrasing loosely, these requirements include: that the implementation completely implements the specification, that the implementation doesn't modify the java package namespace beyond what the specification allows, and that the implementation passes the applicable TCK.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文