<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2015-09-26 22:43, moltonel wrote :<br>
</div>
<blockquote
cite="mid:799D06E2-6279-4C02-9DA2-1FCCEE09EB88@gmail.com"
type="cite">
<pre wrap="">
On 26 September 2015 19:05:09 GMT+01:00, "André Pirard" <a class="moz-txt-link-rfc2396E" href="mailto:a.pirard.papou@gmail.com"><a.pirard.papou@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">It is
<keyname>:warning=<text>
which acts only when that key is changed.
geometry:warning=<text> to protect the coordinates of the element
name:warning=<text> to protect its name.
Those tags do not warn against changing other tags.
</pre>
</blockquote>
<pre wrap="">
May I suggest 'edit_warning', or something else that explicit (because a 'warning' key could be used for so many purposes) ? And use proper namespace ordering, ie edit_warning:name=blah rather than name:edit_warning=blah (because many keys, like name or phone, are also namespaces that can be followed by arbitrary sufixes).</pre>
</blockquote>
OK with me for a more explicit term as long as it is not too long.
The best inventor will win.<br>
But I'm afraid that the correct namespace order is
name:edit_warning=*.<br>
edit_warning is a qualifier of name and not the opposite.<br>
It is the edit warning of (for) name and not the name of the edit
warning.<br>
It's just like the order of the words in an English phrase.<br>
Adding a qualifier makes the word more specific, "with warning"
rather than plain.<br>
If you speak of the building antenna type, it's building:antenna:4G=yes<br>
The left side of the road is road:left and not left:road.<br>
And BTW, source:maxspeed is a mistake, there is no such thing as the
speed of a source<br>
The source of the maxspeed should be maxspeed:source.<br>
And its date should be maxspeed:source:date and not <br>
source:date:maxspeed or source:maxspeed:date or
date:maxspeed:source..<br>
But it's typical of an OSM article about namespaces not to speak of
the order.<br>
Let us stop making more mistake.<br>
<blockquote
cite="mid:799D06E2-6279-4C02-9DA2-1FCCEE09EB88@gmail.com"
type="cite">
<pre wrap="">That said, you should open bugs on the various editors as soon as possible to discuss with them what they think of such a feature. Unless this tag gets editor support, it doesn't bring anything that the already popular 'note' tag doesn't give. Sadly, inexperienced mapers are the ones most likely to miss a plain 'note' tag, but they are also most likely using iD, whose developers are pretty warning-averse...
</pre>
</blockquote>
Don't speak like that of mappers and developers ;-) You're going to
get in trouble with Julien Fastré who will say that you're trying to
convince us, and yourself, that "they are doing bad job" and that
you will frighten newcomers (sic) ;-)<br>
This said, seriously and frankly, I have a serious dilemma when I'm
hippy hopping the JOSM Area Selection Plugin along the way and I
meet polygons completely askew and 4-5 m or more away from their
place with just "building=yes" and that in one single click I can
draw the house with a 20 cm precision and complete tags, the house
number being incremented for the next house ! I feel like a 5
years' work has to be restarted afresh. Fortunately, not afresh for
fixing road geometry in Improve Way Accuracy mode of that JOSM
again.<br>
Isn't there a convincing tutorial to compare methods and show that
(fixing)?<br>
I know two friends who are ¾ convinced but who can't get rid of
their habits and make the first step.<br>
I myself know too little of the other products to be a good
comparator and convincing advisor.<br>
All that I can say is that a good migration method is to use the old
and the new programs simultaneously, more and more of the new one.
It's what I did when simulating a shift from JOSM to Merkaartor, but
it turned out that there were too many things that Merkaartor
couldn't do.<br>
<br>
Cheers
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</body>
</html>