You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for raising this!
Looking at the intent of purls, which is to identify "packages" I get the impression that we should probably only translate directory, release or revision SWHIDs.
On a side note, it would be great if we could have SWHIDs used in other package managers, instead of naked hashes as we see in the purl examples, but that's for another day I suppose :-)
Do want to work towards defining an encoding of SWHID as a package-url ?
The specification is at https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst
One can see how different other types are handled in https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst
I assume the majority of work would be to see what encoding/decoding has to be specified in the representation.
The text was updated successfully, but these errors were encountered: