<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Le 18/10/2022 à 17:14, Brian M. Sperlongano -
<a class="moz-txt-link-abbreviated" href="mailto:zelonewolf@gmail.com">zelonewolf@gmail.com</a> a écrit :<br>
</p>
<blockquote type="cite"
cite="mid:CAMrfQx1deefy2-6nmas=40cijtVkdn1NHqU6hXJ0ip7qWT8weg@mail.gmail.com">
<div>Well, this is absolutely possible. Geographically-aware
processing is completely within our technical ability. Now,
this would be pretty terrible for a key like "smoothness", but
there are many very legitimate cultural, legal, socioeconomical
and organizational differences between countries that might make
it absolutely appropriate for the same tag to have slightly
differing meanings in different countries.</div>
</blockquote>
<p>One good example is highway network, as the hierarchy is
optimized for a country or a region. So
primary/secondary/tertiary/unclassified are for different roads.<br>
</p>
<p>But normally you should try to stick to more or less universal
keys and values and add a secondary tag for specificities.</p>
<p>One example is amenity=school, for France we have on top of that
a secondary tag school:FR to match the French system.</p>
<p>Suffixed by the country as the possible values in France could be
different as in Belgium for instance.<br>
</p>
<blockquote type="cite"
cite="mid:CAMrfQx1deefy2-6nmas=40cijtVkdn1NHqU6hXJ0ip7qWT8weg@mail.gmail.com">
<div>The real problem is when "objects tagged a certain way by Joe
mean XYZ but it means ABC when that tag is used by Alice".
That's when the meaning becomes ambiguous and impossible to
process.</div>
</blockquote>
<p>Then a NEW tag should be found and completed by a secondary tag
saying if it's XYZ or ABC.</p>
<p>Some big mistakes were done by an editor because a developer
didn't new the legal context and considered 2 different tags as
being the same, making the difference unusable.</p>
<p>But sometimes differences remain. For instance the usage or non
usage of associatedStreet. It's forbidden in some countries and
welcomes in others (were you have multiple language, adding the
information on each way, each housenumber fills the database with
noise and typos). AFAIK, I would prefer the editor to work with
associatedStreet for a better modelling but allow people to map
"the dirty way", having the optimization (or tag sharing if you
prefer to avoir associatedStreet) made behind the scene.<br>
</p>
<p>Jean-Yvon<br>
</p>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>