<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">The discussion that followed Gervase's email last week was fascinating, especially the analysis of the OSM community as a anarcho-collective.<br><br>However I was surprised to see no one suggest necessary (at least to my mind) technical solutions that don't even touch on the subject of the tag "approval" system.<br><br>Currently there's massive duplication of information on tags. Besides what's described below in the wiki, there are presets defined in JOSM and Potlatch, rendering rules for osmarender and mapnik, and other places as well.<br><br>Can the key/value, rendering rules and outputs, comments and descriptions, photos, and perhaps if we decide it makes sense, the "approval" process be abstracted to a model for
use in rails? What would the goal look like, and are there small intermediate steps which are obtainable?<br><br>-Mikel<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Gervase Markham <gerv-gmane@gerv.net><br>To: talk@openstreetmap.org<br>Sent: Wednesday, March 19, 2008 5:54:29 AM<br>Subject: [OSM-talk] Tag proposal/approval system is too heavyweight<br><br>
[I'm afraid this might be a bit of a complaint without a solution, as I <br>don't have the necessary wiki skills to fix this. But I hope someone <br>else does.]<br><br>The admin involved in proposing and approving tags, in terms of the wiki <br>changes required, is far too heavyweight. (Note: I'm _not_ complaining <br>about the voting system, only the admin required.) In order to mark two <br>new values as approved, I had to:<br><br>- Remove each one from Proposed Features<br>- Add them back to Approved Features<br>- Edit the relevant Map_Features sub-template to add a new line for each<br>- Create a new page for each tag, explaining what it does (which <br>duplicates data on the individual Proposal page)<br><br>Each of these editing operations is tricky because you have to fill in <br>various fields in various templates which are far from obvious as to <br>their function.<br><br>Here's the way it would work in an ideal world:<br><br>- Cut the relevant
table line out of Proposed_Features and add it to <br>Map_Features<br>- Er...<br>- That's it.<br><br>This would require:<br>- Proposed_Features and Map_Features to have compatible templates.<br>- Writing proposals in a style as if they were accepted, which is fine. <br>(Unaccepted proposals would be automagically marked with "this proposal <br>is not yet official.)<br>- Creating all tag explanation pages in the same namespace, rather than <br>Proposed_features/Foo and Map_Features/Foo.<br>...<br><br>Does anyone else see what I'm driving at?<br><br>Gerv<br><br><br>_______________________________________________<br>talk mailing list<br><a ymailto="mailto:talk@openstreetmap.org" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br><a href="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk" target="_blank">http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk</a><br></div><br></div></div></body></html>