Skip to content

PNE PURLs incomplete #154

@dylan-mulligan

Description

@dylan-mulligan

It appears we are missing an important part of the PURL spec, type, as can be seen below.
image
Spec: (https://github.com/package-url/purl-spec)
scheme:type/namespace/name@version?qualifiers#subpath
The definition for each components is:

  • scheme: this is the URL scheme with the constant value of "pkg". One of the primary reason for this single scheme is to facilitate the future official registration of the "pkg" scheme for package URLs. Required.
  • type: the package "type" or package "protocol" such as maven, npm, nuget, gem, pypi, etc. Required.
  • namespace: some name prefix such as a Maven groupid, a Docker image owner, a GitHub user or organization. Optional and type-specific.
  • name: the name of the package. Required.
  • version: the version of the package. Optional.
  • qualifiers: extra qualifying data for a package such as an OS, architecture, a distro, etc. Optional and type-specific.
  • subpath: extra subpath within a package, relative to the package root. Optional.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghigh priorityMark the issue as a high priority task

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions