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
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?
The text was updated successfully, but these errors were encountered:
...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.
Would be great to give guidance on the correct naming usage.
IMHO we should not be pedantic about case: you can use any way you like, PURL is not case sensitive.
I like to use PURL, all uppercase when I mention it in writings. But when using it in code for a variable or field name, I use purl all lowercase. YMMV.
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?
The text was updated successfully, but these errors were encountered: