Looking for Go module path (contains version) suggestion for github.com/spdx/spdx-go-model

[Meng Zhuo]

Hi, 

What should we do if module named with version?

```

import (
    "testing"

    Spdx3_0_1 "github.com/spdx/spdx-go-model/v3_0_1"

```

https://github.com/spdx/spdx-go-model/pull/1

[Dan Kortschak]

From the code that's in that change, the import path is
github.com/spdx/spdx-go-model/spdx_v3_0_1, not github.com/spdx/spdx-go-
model/v3_0_1.

[will....@gmail.com]

Meng,

It's unclear to me what you're asking. Are you asking whether the path should be changed to be more idiomatic? I would have expected it to be github.com/spdx/spdx-go-model if the major version is 0 or 1; and github.com/spdx/spdx-go-model/v3 if the major version is 3.

Will

[Meng Zhuo]

The spdx has it's own version for SPDX spec (i.e. v3_0_1)

https://spdx.github.io/spdx-spec/v2.3/

but go module's version might conflict this.

If an user import spdx v2.3(with go mod version 1.0.0), he will end up import  `github.com/spdx/spdx-go-model/v2_...@v1.0.0 `

That's very confusing to me.

[Dan Kortschak]

On Fri, 2025-01-24 at 18:29 -0800, Meng Zhuo wrote:
> The spdx has it's own version for SPDX spec (i.e. v3_0_1)
> https://spdx.github.io/spdx-spec/v2.3/
>
> but go module's version might conflict this.
> If an user import spdx v2.3(with go mod version 1.0.0), he will end
> up import  `github.com/spdx/spdx-go-model/v2_...@v1.0.0 `
>
> That's very confusing to me.

As noted above, the version does not have a v prefix, it has the prefix
"spdx_v". This is also noted in this comment
https://github.com/spdx/spdx-go-model/pull/1#discussion_r1913449817.

So the import would be github.com/spdx/spdx-go-model/spdx_...@v1.0.0