<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Perhaps your questions were rhetorical but it still deserves response, so here goes.</div><div dir="auto"><br></div><div dir="auto">Taking the cukraszda example, excuse me but from what I can gather these sell pastries? They would be similar to a patisserie in France I guess. In the English language what a patisserie (or cukraszda) makes and sells are pastries and so a shop=pastry is appropriate because that's what it makes/sells, or at least as a generic term we can simplify it as that to mean lots of delicious fattening delicacies behind a glass counter!</div><div dir="auto"><br></div><div dir="auto">But shop=pastry is still very generic. It doesn't tell us if the shop in question also allows you to sit outside with a coffee and consume that delicacy, but we could add an amenity=cafe to the object too. That makes it a little clearer. That doesn't tell a renderer how to label the object on a map. That's what the art of cartography is all about, deciding what and how to represent objects to a reader of a map.</div><div dir="auto"><br></div><div dir="auto">This doesn't mean that cukraszda has no place in OSM at all. We can use a country specify tag as well as the generic tags if that helps understand the object even more or helps in a local context.</div><div dir="auto"><br></div><div dir="auto">This then brings me back to pastry vs confectionery. In the English language these are very different. The former typically means something baked in an oven (cake, but not bread) whereas the latter is very much "sweets", or candy if you like, plus chocolate.</div><div dir="auto"><br></div><div dir="auto">There are many examples where the general English meaning of something becomes lost in translation in another country, or even between english speaking countries. It is this level of inconsistency in OSM that we should seek to correct so that we remove as much ambiguity as possible. Once on a common footing we have ample opportunity to add more keys and values to make an objects meta data richer and more meaningful.</div><div dir="auto"><br></div><div dir="auto">Cheers</div><div dir="auto">Andy</div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:12px;color:#575757" dir="auto">Sent from my Galaxy</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: grin via osmf-talk <osmf-talk@openstreetmap.org> </div><div>Date: 21/10/2022 13:55 (GMT+00:00) </div><div>To: osmf-talk@openstreetmap.org </div><div>Subject: Re: [Osmf-talk] Tagging standards </div><div><br></div></div><br><br>On October 20, 2022 1:08:25 PM GMT+02:00, Frederik Ramm <frederik@remote.org> wrote:<br><br>><br>>But there is a form of colonialism in this "making the world machine-readable", because who decides what the machine can read?<br><br>There is the problem that keys are actually words existing in natural language. The same time they may only mean a looser or stricter meaning of the word.<br><br>For example there is no key for Hungarian cukrászda, which is not confetery, but the key used for such objects. Shall I create a new key? Maybe I should.<br><br>Does café mean something which works like a café (in England?) or something which is CALLED a café locally?<br><br>Conflict is inevitable.<br><br>G<br><br><br>_______________________________________________<br>osmf-talk mailing list<br>osmf-talk@openstreetmap.org<br>https://lists.openstreetmap.org/listinfo/osmf-talk<br></body></html>