When naming derivative files to be BIDs compliant, I often come to a problem of illegibility to the human eye in …desc-…
when in the value I’d like to say something that conveys for example, that the image was skullstripped with a 2-voxel boundary (using FreeSurfer’s mri_synthstrip). I know the meta data can be more descriptive, but parsing the files visually gets to be a pain as “-”, "", " ", as well as any other symbols are not compliant, from what I understand…leaving only Camel case.
_desc-Brain2voxBoundary is so ugly.
I’m sure I can choose better, but this is all to say that I wish there was a spacer symbol that could be used for human readability.