Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is "PURL" (all caps) considered an incorrect abbreviation? #280

Open
joeattardi opened this issue Dec 4, 2023 · 3 comments
Open

Is "PURL" (all caps) considered an incorrect abbreviation? #280

joeattardi opened this issue Dec 4, 2023 · 3 comments

Comments

@joeattardi
Copy link

All throughout the spec, the abbreviation "purl" (all lowercase) is used. I was wondering, is this intentional - is all uppercase ("PURL") or a mix ("pURL") considered incorrect when referring to a package URL?

@prabhu
Copy link

prabhu commented Dec 13, 2023

@joeattardi, the value that begins with pkg: is more important. I have tools that use purl as a "bom-ref" and other ids for uniqueness.

@noqcks
Copy link

noqcks commented Jan 7, 2024

I have the same question.

I see purl being used. Example: https://tomalrichblog.blogspot.com/2023/12/the-naming-problem-isnt-complicated-if.html

And PURL. Example: https://resilientcyber.substack.com/p/whats-in-a-name

Would be great to give guidance on the correct naming usage.

@jbmaillet
Copy link

...and here is another example with all caps, from people who should know:
CVEProject/cve-schema#173
These is the kind of pesky detail that does not help convincing decision maker that a project is serious.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants