Skip to content

How are golang sub-modules supposed to be expressed by purl? #63

@andrewstein

Description

@andrewstein

I am confused reading the spec for purl in relation to golang sub-modules.
For example, looking at the submodule expressed in this go.mod file: https://github.com/go-modules-by-example/submodules/blob/master/a/go.mod, released by the a/v1.0.0 tag: https://github.com/go-modules-by-example/submodules/releases

Is the purl:

  1. pkg:golang/github.com/go-modules-by-example/submodules/[email protected]
  2. pkg:golang/github.com/go-modules-by-example%2Fsubmodules%[email protected]
  3. pkg:golang/github.com/[email protected]#submodule/a
  4. pkg:golang/github.com/go-modules-by-example/[email protected]#a
  5. pkg:golang/github.com%2Fgo-modules-by-example%2Fsubmodules%[email protected]

It basically comes down to what is the namespace (if any), what is the name and what is the sub-path (if any) for this submodule.

Metadata

Metadata

Assignees

No one assigned

    Labels

    PURL type definitionNon-core definitions that describe and standardize PURL typestype: golangProposed new type as well as component discussions

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions