OpenStreetMap Forum

nickvet419

Member

Registered: 2010-10-28

Posts: 3

RFC Blue Ribon Features

Hey everyone... I am proposing a new idea to mark features that have been
discussed, agreed, and are in standard practice of marking the OSM map.

http://wiki.openstreetmap.org/wiki/Blue_Ribbon_features

Here is the definition:
Blue Ribbon Features Are map features that have gone though the proposal
process. They have been discussed and found by the OSM community to be a
standard way to mark a map feature.

The Blue ribbon is a way to certify a tag/key/relation is being used in standard
practice of marking the OSM map, and has taken proper steps to be discussed and
agreed upon by the OSM community.

The reason for this proposal comes from the ongoing debate of the proposal
process.  Even though it is acceptable to document every tag used on OSM, I think
this would be a positive way to show that a feature has gone thought the proposal
process and that it is considered safe to use to mark the map by the OSM
community.

Please take time to consider the positives of this proposed label
* Promotes the use of Proposed features for better definitions and
documentation.
* Gives users assurance that a tag is widely used.
* Will define better that the proposal process is not mandatory, but helpfull
in getting community support.

Thanks,  Nickvet419

cartinus

Member

From: Houten

Registered: 2008-01-06

Posts: 502

Re: RFC Blue Ribon Features

Please take time to consider the positives of this proposed label
* Promotes the use of Proposed features for better definitions and
documentation.

Since when does the current proposal system automatically generate better definitions and documentation?

The whole reason so many people don't like the proposal system is that it never did that.

nickvet419

Member

Registered: 2010-10-28

Posts: 3

Re: RFC Blue Ribon Features

Have to disagree there... What I've heard over and over is people don't like the "Voting" process. The proposal process itself is very helpful for people to collaborate together and create great documentation of a feature/tag among other things.

Since when does the current proposal system automatically generate better definitions and documentation?

The whole reason so many people don't like the proposal system is that it never did that.

!i!

Member

Registered: 2009-11-28

Posts: 3,313

Website

Re: RFC Blue Ribon Features

Well IMHO the discussion about a draft leads to a better design (I don't say that this one is a perfect one, but better). But let's pause the talk about the proposal process cause there is so much irritation and sticked positions.

I see this as a chance to help newbies to see if a feature runs trough a discussion or if not if it is at least widely used and indirect accepted by the community. This might be a first step to get a better ordering on all the tags, proposals,...

---

privater Account von KVLA-HRO-Mei