On 03/07/18 09:28, Frederik Ramm wrote:
On 02.07.2018 19:42, Mateusz Konieczny wrote:
It would make development of QA tools easier as authors would not need to
discover and implement support for this duplicated key.
I think the downsides of such a large mechanical edit far outweigh the
advantages.
Don't forget that new FIXMEs will continue to appear all the time.
Software should be able to deal with both.
I'm with you on this Frederik. The correct fix for a 'FIXME' tag is to
deal with it or remove it completely if no longer valid, and adding
extra change events to 'fixme' only gets in the way of that.
IF there is a general consensus that some tags are no longer acceptable,
then the first step is to fix the API to prevent their use? Once the
source of the problem is eliminated THEN address the historic data.
Is there any case for not enforcing lowercase only tags? The fact that
'FIXME' and 'fixme' can exist on the same node just seems wrong in ANY case?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
