> I'm going to muddy waters between two threads that are going on here. You are more welcome to do so since your proposition seams a rather very good one.
> formal part of the API to update it, so you could in principle introduce > new tags (with descriptions), as well as translations for existing tags, > through the API via an editor (either one built for the purpose, or > through JOSM/Potlatch/whatever, or both). That would be, by far the BEST way to go imho, what's best to describe the content of a database than a table of the database itself ? But this sounds like a major proposal that has to be carefuly though of. ( I have no clues to who will make the code) But I have right now many fears that comes to my mind. By order of magnitude : 1) Won't that end in a way to enforce possible tags and makes it impossible to tag my own ? 2) won't that remove my freedom from proposing new tags ? 3) won't that end in an horrible mess of thousand of duplicate tags ? 4) won't that look rather like the output of tagwatch ? If those can be adressed correctly I am much much in favor of that, than every editors having their presets, having maplint parsing a wiki page, having a too big map features page. How do we start to talk about it ? are some devs on the problem ? is this a virtual proposition for now ? -- sly sylvain letuffe _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
