stable spec URLs

J Lovejoy

Hi again,

Now that 2.3 is out, this question is more pertinent:

Note, if I want to link to a specific part of the SPDX spec, I can find it via the HTML format, for example:

if I wanted to see this same section in v2.2.2, the link is:

but if I simply removed the version number in the URL -
it ends up going to v2.2.2

That doesn’t seem right - should it default to the most current version?


On Jul 25, 2022, at 10:00 PM, J Lovejoy <opensource@...> wrote:

(cross-posting to tech and legal team, as I suspect others may be interested)

Hi SPDX-tech team,

I just wanted to confirm my understanding of the various formats we now have for the SPDX specification and linking to specific sections.

If I wanted to link to, for example, Annex D, in a way that would remain stable with subsequent versions of the spec, then I could use the HTML format, and then the link - and this would still point to the Annex D on SPDX license expressions even for version 2.3 of the spec - is that right? (assuming of course that Annex D doesn't change name such that the link also changes)