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
I would keep everything in lowercase, to make it case-insensitive and more robust towards CAPS LOCK and other capitalization errors (or is there a particular use-case where differing in the cases would be important?)
Interesting thought, I wonder if capitalisation of name could be different in different part of the world. It would feel strance to write my name without capital letter, though.
Note, if we ever expand to have title information, the capitalisation would be important, as some terminology requires captitalisation (for insance, foxP is a gene FoxP is a protein)
The text was updated successfully, but these errors were encountered:
I would suggest keeping capitalisation in names, roles, etc. etc. Where possible, we encourage the use of case-insensitive identifiers (RINGOLD, ORCiD, etc.) so machine-reading shouldn't be hindered by mismatched capitals too badly.
Generally, I think a data representation format should concern itself with representing the data, and tools built on top of JAMS can handle decisions about whether or not to modify capitalisation on fields.
should name be indicated in all lowercase ?
The text was updated successfully, but these errors were encountered: