Talk:Tag:substance=LNG
Jump to navigation
Jump to search
Unresolved
Upper or lower case

Is it upper or lower case? The approved proposal was lower case value "lng" and all other used values [1] are lower case, too. --Chris2map (talk) 17:54, 9 October 2024 (UTC)
- In the proposal it was lower case. And we commonly use lower-case letters in keys and values even if the word in English should be capitalized, for example cuisine=italian. And https://taghistory.raifer.tech/#***/substance/LNG&***/substance/lng. So the article should be moved to Tag:substance=lng. maro21 17:40, 5 April 2025 (UTC)
- There has taken place kind of retagging in 2022 from "lng" to "LNG": Tag History. I'm not entirely sure if the tag could be de facto. But it's actually too little for that. On the other hand there are some UCs with "fuel" taginfo fuel. All in all, I see it that lowercase is the basic practice and approved. --Chris2map (talk) 19:09, 5 April 2025 (UTC)
- However, the fact is that the approved tag is in lower case so this information should be in the article. OSM tags are case sensitive. Wiki article is a separate thing than tags in the OSM database and it doesn't mean that wiki editors should retag features, we can just move the article. maro21 14:46, 6 April 2025 (UTC)
- There has taken place kind of retagging in 2022 from "lng" to "LNG": Tag History. I'm not entirely sure if the tag could be de facto. But it's actually too little for that. On the other hand there are some UCs with "fuel" taginfo fuel. All in all, I see it that lowercase is the basic practice and approved. --Chris2map (talk) 19:09, 5 April 2025 (UTC)
@Geozeisig: I want to ask what is your motive for the upper-case notation of the tag value? Since most values in OSM are used in lower-case I think that would be also appropriate with "lng". --Chris2map (talk) 11:30, 7 April 2025 (UTC)
- Alle Schlüsselwörter der tags werden kleingeschrieben. Das gilt auch für die Werte, aber es scheint bei den Abkürzungen Ausnahmen zugeben. Beispiele sind beacon:type=ILS, beacon:type=VOR, operator:short=BVG, network:short=VBB usw. Es handelt sich um Abkürzungen, die in der Literatur auch nur mit Großbuchstaben geschrieben werden und das finde ich gut so.
- Für Namen gibt er die Regel, dass der erste Buchstabe groß, alle anderen kleingeschrieben werden. z.B. solle name=ALDI besser mit name=Aldi geschrieben werden. Hier wird die Regel häufig nicht beachtet.--geozeisig (talk) 06:07, 8 April 2025 (UTC)
- Zu dem Thema Abkürzungen mit Großbuchstaben passen auch folgende tags: content=LPG, content=LNG, fuel:diesel, short_name, network:short --geozeisig (talk) 13:28, 8 April 2025 (UTC)
- (de) Ich finde die groß geschriebenen Abkürzungen auch besser lesbar. Aber soweit ich es überblicke, wird in OSM standardmäßig die Kleinschreibung vorgezogen, wenn nicht Gründe für etwas anderes sprechen. Bei
network
undoperator
erkläre ich es mir so, dass es dort Abkürzungen von Eigennamen sind.content=LNG
ist der gleiche, unentschiedene Fall wiesubstance=LNG
und sollte dann ebenfalls angepasst werden. Aktuell ziehe ich für mich folgenden Schluss: Bei Begriff-Abkürzungen wie eben LNG oder LPG ist zwar die Lesbarkeit bei der Editierung für Menschen besser, aber das ist wohl kein ausreichender Grund, um von der Standardpraxis der Kleinschreibung abzuweichen. Da zudem auch im zugestimmten Proposal die Kleinschreibung verwendet wurde, halte ich die Änderung beicontent
undsubstance
inlng / lpg
für angebracht. - (en) I also find the capitalized abbreviations easier to read. But as far as I can see, lowercase is preferred in OSM by default unless there are reasons to the contrary. In the case of
network
andoperator
, I understand that they are abbreviations of proper nouns.content=LNG
is the same, undecided case assubstance=LNG
and should also be adjusted. My current conclusion is the following: While term abbreviations like LNG or LPG are easier for humans to read when editing, that's probably not a sufficient reason not to go with the standard practice of using lowercase. Furthermore, since the approved proposal also used lowercase, I consider the change to lowercaselng / lpg
forcontent
andsubstance
to be appropriate. --Chris2map (talk) 16:28, 9 April 2025 (UTC)- I agree. Firstly - we cannot ignore the proposal that approved lower case. Secondly - majority of values that are acronyms are lower case. Thirdly - we can create documentation on the Wiki for tags regardless of how they are used - that is, we can describe both variants objectively, without suggesting which "should" be used [both are used]. Fourth - values such as LNG/LPG/lng/lpg are more like variables in programming - there may be different standards among programmers, some prefer lowercase, others uppercase. On OSM the lowercase version prevails. maro21 18:55, 9 April 2025 (UTC)
- The proposal is already over 10 years old and had a completely different topic, lpg is mentioned and incidentally. If LNG and LPG were to be changed to lng and lpg, it would be nice if it were done uniformly. Then all values in the database would have to be changed, so that both do not occur over several years. --geozeisig (talk) 06:39, 10 April 2025 (UTC)
- I agree. Firstly - we cannot ignore the proposal that approved lower case. Secondly - majority of values that are acronyms are lower case. Thirdly - we can create documentation on the Wiki for tags regardless of how they are used - that is, we can describe both variants objectively, without suggesting which "should" be used [both are used]. Fourth - values such as LNG/LPG/lng/lpg are more like variables in programming - there may be different standards among programmers, some prefer lowercase, others uppercase. On OSM the lowercase version prevails. maro21 18:55, 9 April 2025 (UTC)
- (de) Ich finde die groß geschriebenen Abkürzungen auch besser lesbar. Aber soweit ich es überblicke, wird in OSM standardmäßig die Kleinschreibung vorgezogen, wenn nicht Gründe für etwas anderes sprechen. Bei