Editing Proposal process
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
<!--T:79--> | <!--T:79--> | ||
As a documentation change, an approved proposal is not binding on any mapper, software developer, or data consumer. However, tagging backed by an approved proposal is usually regarded as having survived a level of community vetting and scrutiny, and thus carries more weight when compared to alternative methods of mapping a feature. OpenStreetMap does not restrict mapping to tagging schemes backed by an approved proposal -- you can still use [[any tags you like]]. Nonetheless, there is benefit to mappers and data consumers alike in agreeing on a common data model and corresponding tags by reducing conflict between mappers, edit wars, and tagging disputes. | As a documentation change, an approved proposal is not binding on any mapper, software developer, or data consumer. However, tagging backed by an approved proposal is usually regarded as having survived a level of community vetting and scrutiny, and thus carries more weight when compared to alternative methods of mapping a feature. OpenStreetMap does not restrict mapping to tagging schemes backed by an approved proposal -- you can still use [[any tags you like]]. Nonetheless, there is benefit to mappers and data consumers alike in agreeing on a common data model and corresponding tags by reducing conflict between mappers, edit wars, and tagging disputes.. | ||
<!--T:80--> | <!--T:80--> | ||
As a non-binding documentation change, '''the outcome of a proposal vote does not compel a change in tools which use and generate OSM data''', such as the [[standard tile layer]] renderings or [[editor]] [[preset]]s. An approved proposal will not be automatically rendered or added to presets; this is at the discretion of the developers and maintainers of those tools. Also, a vote result is '''never''' permission for large-scale re-tagging of existing objects. See [[automated Edits code of conduct]] for more about this topic. | As a non-binding documentation change, '''the outcome of a proposal vote does not compel a change in tools which use and generate OSM data''', such as the [[standard tile layer]] renderings or [[editor]] [[preset]]s. An approved proposal will not be automatically rendered or added to presets; this is at the discretion of the developers and maintainers of those tools. Also, a vote result is '''never''' permission for large-scale re-tagging of existing objects. See [[automated Edits code of conduct]] for more about this topic... | ||
<!--T:81--> | <!--T:81--> |