purl-spec

purl-spec copied to clipboard

Fix URL of package-url rust-lang repository

2

Changed from `packageurl-rs` to `packageurl.rs` because that seems to be what the actual repo/fork is using.

Xiphoseer

i found the lack of an example for `qualifiers.checksums` odd. therefore i added a simple example.

jkowalleck

i found the lack of an example for `qualifiers.vcs_url` and `qualifiers.download_url` odd. i am not certain if the example i added are according to spec, feel free to add a...

jkowalleck

common qualifiers

1

It is useful to define (purl-wide, as opposed to type specific) common qualifier keys and values such as OS, architecture, GUI framework. It would improve automated consumption of purls.

jlb-bb

Add mostly universal version range spec draft

29

Originally at https://github.com/nexB/univers/pull/11 This is an work in progress for "vers" a new mostly universal version ranges specification to use as a companion to purl. This is a possible solution...

pombredanne

"pacman" should be listed instead of "arch" under "Other candidate types to define"

1

The Arch distro uses the pacman package manager. Other pacman based distros are listed here: https://en.wikipedia.org/wiki/Category:Pacman-based_Linux_distributions I recommend that "arch" in the "Other candidate types to define" list is replaced...

bronze51

Add OmniBOR (previously GitBOM) namespace identifier as a PURL Type

13

The GitBOM community is [working](https://github.com/git-bom/spec/issues/2) to specify a URI Namespace Identifier for GitBOM Identifiers. This issue proposes creating a new PURL Type for that GitBOM URI NID once the syntax...

jeff-schutt

`github` type is ambiguous

2

This is likely my misunderstanding, and apologies if there's a similar issue or discussion that I missed 😃 PURL defines itself as an approach to "reliably identify and locate software...

robcresswell

Revert "Fix missing percent-encoding in purl example with repository_url"

11

This reverts commit 37626c43ace346f38f390f9266ef99eef654bf66. Escaping slashes in qualifiers necessary and does not match the test cases nor the spec: https://github.com/package-url/purl-spec/blob/37626c43ace346f38f390f9266ef99eef654bf66/test-suite-data.json#L110-L121 see also: https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst#character-encoding

maxhbr

Link: https://github.com/kubernetes-sigs/bom It outputs bill of materials with purl references.

sbs2001