Should I keep it in all caps, e.g. ref:SE:DIARIENR or change it to ref:SE:diarenr? Same question for ref:SE:nvrid. Are these commonly lowercase or uppercase in Sweden?
NVRID should probably be kept in uppercase, as NVR is an initialism and ID is usually also in uppercase. (When using the API you use camelcase (nvrId) but in official documents they use all caps for the definition.)
Diarienr should probably be lowercase since diarie is a word, and “nr” a standard shortform for number. Other cases wouldn’t make much sens (diarieNR looks wrong).
Yeah, those should ideally be converted to uppercase as well. Or not. I hade a quick glance over all ref values and it’s a big mess, but there are lots of somewhat established tags in uppercase, so either those are to be cleaned up and standardised as well, or uppercase is actually deemed to be fine in tags. I don’t feel like making that call, though. :)
the only part uppercase would be :SE: - which has a specific reasons:
these two letter codes easy to be mistaken as language codes, and ISO writes them uppercase for this not to happen
it is very widely established in OSM keys to use uppercase for the ISO 3166 code and in OSM values it is the only form, following ISO practice, cf. https://taginfo.openstreetmap.org/keys/ISO3166-1:alpha2#values - yes, the OSM key in this case uses uppercase (part of the “big mess”), but it doesn’t even use “ref:” which is inconsistent.
To use lowercase after ref:SE: is: a) easy to remember b) consistent with current practice within ref:SE: c) not inconsistent with practice elsewhere because consistency there doesn’t exist (“I hade a quick glance over all ref values and it’s a big mess”).
Just using lowercase for all ref:SE is a terrible idea. There is absolutely no consensus/consistency for that. If something is written in uppercase, it should stay uppercase. If not, it should stay lowercase. As an example, the French are pretty good with this.
Votes were to standardize anything that’s Swedish from ref:* to ref:SE:*, not using lowercase for everything.
I don’t disagree with using ref:SE:diarienr, I disagree with using lowercase for literally everything. Why would you do that? Standardization is good, but over-standardization is a terrible idea. So I’ll ask the question again:
If they’re acronyms, then surely they should be uppercase. You really think we should use usa instead of USA? fbi instead of FBI?
If they’re names, then lowercase is fine. I made some research and from what was mentioned on this thread, acronyms are:
A few ref:diarienr existed, they have been converted to ref:SE:diarienr. Conversion of ref:DIARIENR to ref:SE:diarienr may take some time. I have no JOSM and don’t know how to do it in one edit. The user that help in the other conversions doesn’t provide help in that case, despite agreement to convert to ref:SE:diarienr.
The topic was to add “:SE:” first on “ref:raa” then on other SE-specific keys, to make these keys 1) easier findable, recogonizable and 2) unique (=in other countries there might also be references named “raa” etc.)
Lowercase was used overwhelmingly and currently each “ref:SE:xyz” uses “xyz” in lowercase, which is also easier to type. Some SE-specific keys that did user allcaps ref:XYZAB also had a few cases where users used “ref:xyzab”, i.e. “Acronyms should stay uppercase” leads to inconsistency within the set of “ref:SE:…”, because some acronmys aren’t uppercase and therefore cannot “stay uppercase”.
FAQ - OpenStreetMap Community Forum : “Rather than taking an existing topic in a radically different direction, use Reply as a Linked Topic.”
You said everything should be lowercase, I said that’s pretty brainless because acronyms are inherently uppercase (usa, fbi, cia, nato, unesco… really?). You said this has nothing to do with the thread… the intellectual level…
In any case, have fun learning about how to use JOSM or finding someone else to do this for you.
The topic is confined to the naming of OSM keys starting with “ref:SE:” or those that should be converted to use this prefix. “usa, fbi, cia, nato, unesco”-OSM keys (if they exist) are not prefixed “ref:SE:” nor has there been a proposal to do so.