[Tagging] Removal of "amenity" from OSM tagging

[Tod Fitch]

Just exactly how can a data consumer be “abstracted from our tags”? Where in a typical rendering process could this abstraction be placed where it would be automatic and transparent to the people maintaining the data consumers?

For example, I generate PDF/paper trail maps for an organization using OSM. My scripts download the extract from geofabrik that includes our area of interest and makes the maps from that. Unless geofabrik translates (abstracts) the tags, an unlikely and undesirable thing for them to do, then I will need to make changes in my scripts to handle any changes in tagging that my organization cares about. Maybe it would be in the stage where we load a database with object information, maybe it would be in the rendering stage or maybe in both areas. But I will have to make changes to get my map generation working again. I strongly suspect that many other data consumer maintainers would have the same issue.

—Tod

> On May 17, 2015, at 6:28 AM, Janko Mihelić <janjko at gmail.com> wrote:
> 
> I agree with this, but I think consumers should be abstrated from our tags too. It shouldn't be impossible to change the meaning of a tag. But untill such abstraction is made, no major changes should be made.
> 
> Janko
> 
> ned, 17. svi 2015. 15:14 David Earl <david at frankieandshadow.com <mailto:david at frankieandshadow.com>> je napisao:
> 
> It shouldn't matter what the tags are called, this is like assembly code, only the geeks should need to ever see them. This really ought to be abstracted in the editors, as indeed it is in ID.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20150517/736e3cc6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1868 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20150517/736e3cc6/attachment.bin>