[OSM-talk] proposed mechanical edit - moving FIXME=* to fixme=*

[Dave F]

Hi Michael...

On 03/07/2018 00:23, Michael Reichert wrote:
> Hi Mateusz,
>
> Am 02.07.2018 um 19:42 schrieb Mateusz Konieczny:
>> Please comment - especially if there are any problems with this idea.
>> Please also comment if you support this edit, in case of no response
>> at all edit will not be made as there would be no evidence that
>> this idea is supported.
> There are 177,152 FIXME and 1,216,043 fixme according to Taginfo. I did
> not have a closer look on the average age of FIXMEs and fixmes.
>
> What's the benefit in this mechanical edit? It just sets the
> last_modified attribute to a recent date and data consumers, mappers and
> QA tools get the impression that the object is not old.

This is not a valid reason to not update: 'tagging incorrectly to suit 
the validator/renderer...' etc

> FIXME should make alarm bells ring in validator tools because its key
> only contains uppercase characters.

Editors should have that alarm to prevent them being added in the first 
place.

> If you want to search for uses of FIXME, use the OSM Inspector. It
> supports FIXME case-insensitive for about ten years now (even our new
> C++ implementation does). It does not matter if you write FiXmE,
> or FixmE. Btw, todo=* (lower case only) is also supported.

Great, but why the objection to a mechanical edit, rather than 
individually? Doing it one by one still updates the last_modified 
attribute.


DaveF