On 03/01/15 22:05, François Lacombe wrote: > I include some mechanical edits as vandalism, other than that, > vandalism has not caused me any problems at all. > > I was too. > And I don't understand why a static snapshot can't help you regarding > changes that don't suit your needs.
Think about that in practice! Chris is currently ADDING new data to the database, using his current set of tagging rules and needs to update his view of the data as that is added. HOW can that be done if he is forced to take a static snapshot? There have been several comments about 'phasing things out' rather than simply point in the sand destroy that data. By all means introduce new or expanded tags, but only destroy data after there has been a period of time to allow a switch over. I don't like the way PHP handles some areas of 'improvement', but one does at least get a warning that something will be removed later. I would STILL prefer a database of approved tags rather than the random notes provided by the wiki, and this could then be used by editors to identify valid entries, and eventually flag up deprecated tags and values. The same database would provide a cross reference perhaps to what is rendered by a particular service, or recommend alternate ways of doing something. This is possibly a case for a separate API for the management of tag metadata? Nothing stopping private tagging, but controlling better the core tagging infrastructure and allowing MANAGEMENT of the evolution of tags. -- 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
