package-url
[#202] propose VIP and NIPKG package formats
- Added pURL types for NIPKG (NI Package Format) and VIP (VIPM VI Package) for common LabVIEW package formats #202
Clarified nipkg namespace attribute inclusion and removed vip namespace, updated PR from master.
After the merge of PR #514, PURL tests and defs are now defined in new JSON schemas :angel: :innocent: :grin: :
- See #514
... therefore with the new approach... this PR would need to be updated.
Do you think you can update this PR to the new format?
Sorry for the churn. :heart:
Hi @samsharp99, @pombredanne. I'm on the VI Package Manager (VIPM) team (along with @Tom-McQuillan) and we're working on a plan for better SBOM support for VIPM's packages (.vip and legacy .ogp file extensions) and also NIPM's packages (.nipkg file extension) -- we have a configuration management solution for this VIPM+NIPM packaging space. Internally, we've been discussing the purl type/namespace for these two package management protocols.
From the README.md
type: the package "type" or package "protocol" such as maven, npm, nuget, gem, pypi, etc. Required.
Based on that, and also checking out the purl examples, I would suggest going with the package "protocol" (vipm and nipm) moreso than the package file "type" (vip, ogp and nipkg).
Here are some of those examples, I'm referring to:
pkg:pypi/[email protected]
pkg:rpm/fedora/[email protected]?arch=i386&distro=fedora-25
pkg:rpm/opensuse/[email protected].?arch=i386&distro=opensuse-tumbleweed
Here is what I'm proposing/thinking for VIPM and NIPM packages:
pkg:vipm/[email protected]
pkg:nipm/[email protected]+f197?repository_url=download.ni.com/support/nipkg/products/ni-d/ni-daqmx/23.8/released
Let me know how I and @Tom-McQuillan can help support this effort. I appreciate all the great thought and efforts you've put into this, @samsharp99. Cheers.
