-
Notifications
You must be signed in to change notification settings - Fork 157
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
Comments
@joeattardi, the value that begins with |
I have the same question. I see And Would be great to give guidance on the correct naming usage. |
...and here is another example with all caps, from people who should know: |
IMHO we should not be pedantic about case: you can use any way you like, PURL is not case sensitive. I like to use |
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: