[Tagging] Deprecation - waterway=riverbank vs water=river

[Tomas Straupis]

2021-02-11, kt, 10:07 Marc_marc rašė:
>> what is next?
> my wishes : depreciated any argument based on
> - it's incompetence.

  Do you think it is good for a project to accept decisions, which are
counted as bad by IT experts?

> going back to our "basic rules of IT":
>>   1. Do not touch it if it works.
> you don't need to touch any datause, it should already use both tag :)
> if you use preset, you don't need to touch anything, preset
> do the job.
> if you maintain a preset, it require you to change a few words.
> to be positive, perhaps we could include that whoever brings
> a depreciation proposal, agree to open tickets to all projects
> declared via taginfo

  How many QA tools, data export tools, maps, web applications, blogs
have YOU created and are maintaining?
  Or are you talking about work of OTHERS as "easy", because it is not
you who has to do the work?

>>   2. benefits<>cost
> if it didn't take "years" to argue against immobility, it would
> probably take only a few hour, which is very low compared to the time it
> takes to code one more alias for "every" use of the data multiplied by
> the number of times it happens (for overpass requests alone,
> it's very boring to have to write "a or b or c or d" to sucess).
> as you say yourself in the other email, we spend hours every year
> discussing these things. solving it sometimes takes less time than
> saying we gain nothing (except time) by solving it :)

  What is a BENEFIT of changing waterway=riverbank to water=river when
it marks exactly the same features?

> fragmentation is an issue, a major one because everybody
> need to take care of both (or more) schemas.

  Yes, fragmentation is an issue. So lets prevent fragmentation in the
first place. And this goes back to my question above: what is a
benefit of changing a tag from K1=V1 to K2=V2?

-- 
Tomas