<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/01/19 04:07, Paul Allen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPy1dOKVxv2Go1-hxN-DaWCvq407wzAqwKyN7W1YBgcgLQBk=Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">
<div dir="ltr">On Sat, 5 Jan 2019 at 16:33, Hufkratzer <<a
href="mailto:hufkratzer@gmail.com" moz-do-not-send="true">hufkratzer@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Oh, this was new to me; I
thought the rule "Any tags you like" only <br>
applies to adding additional tags in the database and not to
changing <br>
old tags or to rewrite the documentation. I will keep that
in mind.<br>
</blockquote>
<div><br>
</div>
<div>Yeah, I thought that too. And it's not so much a guiding
principal as an admission of laxity.</div>
<div>Nobody can stop you inventing and using any tag you want,
but it is most certainly NOT</div>
<div> encouraged. It is preferred that you discuss it here
first, and go through a formal proposal, in</div>
<div>order to prevent multiple tags for the same objects
and/or poorly-conceived tags. We can't</div>
<div>stop you making tags up all by yourself, but we'd prefer
it if you didn't.</div>
</div>
</div>
</blockquote>
<br>
There is no requirement not to use any new tag that you like. Nor is
there a requirement to document it.<br>
<br>
What 'we' would like is another matter. <br>
As for 'encouragement' the proposal process and then the voting
reality is far from any from or 'encouragement' .. more like a
torture path, <br>
look at the rejected proposals and the way that votes were cast by
people who took no part in the discussions. <br>
<br>
What I would like is some discussion here first. I would highly
encourage that and have done so in the past. <br>
Then the person can make a decision - used it and document it or
make a formal proposal. <br>
I no longer encourage people to the tagging list, and certainly not
to the proposal process. <br>
<br>
<blockquote type="cite"
cite="mid:CAPy1dOKVxv2Go1-hxN-DaWCvq407wzAqwKyN7W1YBgcgLQBk=Q@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>As for inventing a new tag to replace existing tagging
and then going around changing existing</div>
<div>tags without consultation, that is borderline vandalism
(no matter how well conceived your new tag</div>
<div>is). And then changing the wiki to match your new scheme
that you discussed with nobody in</div>
<div>order to provide a veneer of retro-active justification,
I do consider that to be vandalism. OSM may</div>
<div>be a bit anarchical, but it cannot function unless it is
a consensual anarchy.</div>
</div>
</div>
</blockquote>
<br>
That was not my intent! I quote<br>
-------------------------<br>
<br>
On 5.1.2019 08:25, Warin wrote:
<br>
On 05/01/19 12:57, Graeme Fitzpatrick wrote:
<br>
<blockquote type="cite" style="color: #000000;">Yes, should
definitely be a full proposal & discussion before a major
change is pushed through by one user.
<br>
</blockquote>
<br>
Not mandatory in OSM ... "Any tags you like".<br>
<br>
------------------------------<br>
By that I mean "Not mandatory to make a full proposal & discuss
before introducing new tags. "<br>
I do condone the use of new tags on new entries. <br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAPy1dOKVxv2Go1-hxN-DaWCvq407wzAqwKyN7W1YBgcgLQBk=Q@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>I do not consider this particular advice from Warin to be
helpful or to reflect the majority opinion.<br>
</div>
</div>
</div>
</blockquote>
<br>
I do not condone the replacement of tags by new tags that have not
been discussed and resolved into one being a suitable replacement
for the other. <br>
Such discussion should take place on this tagging list (not
elsewhere!). <br>
<br>
<br>
<br>
I hope that is clear? <br>
<br>
</body>
</html>