Hi,
please don't add dozens of plain translations to name and address tags. The address of an object should be just the official address in the official language of the place (sometimes there are 2 or 3, but never more than 20).
The same goes for the name which should contain only official names in other languages, but no plain translations.

cc-by-4.0 is not suitable for OSM.
https://blog.openstreetmap.org/2017/03/17/use-of-cc-by-data/

You need to obtain a special permission using e.g. this letter:
https://osmfoundation.org/wiki/Licence/Waiver_and_Permission_Templates/Cover_letter_and_waiver_template_for_CC_BY_4.0

Hi,
I agree that especially for short operator names there might be the risk of conflicts. However, the scheme without 'operator' is by far the most common scheme.
However, if there is some discussion you have my full support for "officially" recommending adding 'operator' to the name tag.

Stimmt hier "parking:right:psv:conditional" wirklich? 'psv' schließt Taxis mit ein, die damit rund um die Uhr dort parken dürfen.

way/1102612746

Hi,
what does "wine_tourism" mean? This tag isn't used in any other place.

Hi,
please don't dump data from external sources into OSM.
All these waterways have a large number of foreign tags that should not be in OSM.

Please read our import guidelines:
osm.wiki/Import/Guidelines

My concern is the missing "s" :-)

Tags wie diese an einem einzelnen Objekt sind normalerweise ein klares Zeichen, dass fremde Daten importiert wurden und vergessen wurde tags richtig anzupassen.
Neue Keys sollten der allgemeinen Form entsprechen, z.B. kein CamelCase
osm.wiki/Any_tags_you_like#How_to_name_new_tags

Was spricht gegen schon etablierte Tags, z.B. das in Polen übliche osm.wiki/Pl:Key:highway:category:pl

Da es sich hier sicherlich um eine lokale Einordnung handelt, sollte das am Tag auch klar erkennbar sein.

Da die Klassifizierung von Straßen ein sehr weitreichendes Problem ist (das auch schon häufig diskutiert wurde), sollte es zunächst im Forum besprochen werden.

Hi,
could you check your edits? There are at least 9 'macot' and 'macot:...' tags around the world.

Hi,
thanks for the explanation!
Please don't add such data to the global OSM database if they are just for you research - other users of the data can't make any use of it.

There are much better places for that, e.g. displayed via umap.

You can remove the space, but it is not required. I'm sure that every tool that handles the ';' properly also can work with white space before and after.
E.g. osm.org properly adds links no matter if there is a space or not.

I read the tag as the alternative name of the related law, which doesn't make sense.
Wouldn't the law related to the name not be better tagged as
alt_name:related_law , similar to e.g. alt_name:wikipedia ?

Hi,
what do these tags mean? They are not used in any other place:

capacity:diario
capacity:lunes

Hallo,
ein paar Fragen...

können hier tatsächlich 6x6=36 Lastwagen gleichzeitig laden?

"CCS" ist kein Steckertyp, ich nehme mal an, du meinst "type2_combo"?

Wieviele von dieser Sorte gibt es?

Bitte verwende nicht "amenity_2". Immer einen eigenen Node verwenden, sonst werden diese Informationen nicht nutzbar sein. Wahrscheinlich hat ohnehin nicht jeder Ladepunkt eine eigene Dusche und Verkaufsautomat?

Are you sure there is gate right in the middle of this major road?

Are you sure there is a gate here blocking the main road?

Hi,
could you explain the meaning of these 'erosion=yes' tags? These are not used in any other place.

Hallo,
was heißt denn "socket:Mennekes"? Das ist kein Anschlusstyp, sondern dessen Hersteller.

Have a very close look to the first version of the node, there is no space. What there is is a special unicode character at the end of the key and the beginning of the value. This 0x2009 character in the key is what I removed.

For some reason the Level0 editor doesn't show it in the value, so this stayed. I even can't remove it now in iD, it doesn't display this special character at all...

But wasn't the last modification in 2023 then?

In this particular case I'd suggest to add this using the date namespace:

building:1895-1968 = depot (or whatever the proper tag is)
building:1968- = warehouse

For dates of rebuilds or renovations there are also a couple of tags:

We already have a couple of tags:
year_of_construction
last_renovation
renovation_date
year_of_construction:rebuilt