Re: explanation for ensuring no duplicate identifiers


Philippe Ombredanne
 

On Fri, Jun 15, 2018 at 7:51 PM, Kate Stewart
<kstewart@...> wrote:


On Fri, Jun 15, 2018 at 12:25 PM, Philippe Ombredanne <pombredanne@...>
wrote:

Alexios:
good catch, though even printable may be too generous. A colon is
printable and not a supported in a Windows file name for instance.

Jilayne:
We could/should more simply list the allowed characters and be very
specific.
Here is my suggestion:

Allowed characters are ASCII:
- Lower and upper case letters from A to Z.
- Numbers from 0 to 9
- Dash '-', underscore '_', period '.' and plus '+'

need to be a little careful here Philippe...

"+" is reserved for license expressions.
I listed this because SPDX has issued ids that contained a + in the past.
But that's minor alright!

Best to stick with what's in Appendix IV of the spec today

idstring = 1*(ALPHA / DIGIT / "-" / "." )

where ALPHA and DIGIT are per definition in
https://tools.ietf.org/html/rfc5234

ALPHA = %x41-5A / %x61-7A ; A-Z / a-z

DIGIT = %x30-39 ; 0-9



If you want to see "_" added, then probably should open an issue
against the spec for 2.2 and get it consistent tthroughout.
I do not care much for the underscore. Good catch!

--
Cordially
Philippe Ombredanne

Join Spdx-legal@lists.spdx.org to automatically receive all group messages.