API v0.7: Difference between revisions
Line 13: | Line 13: | ||
Some map features in OSM (e.g. borders) have an authority that officially or legally designates their location or path. These features should not be allowed to move except by verified users. |
Some map features in OSM (e.g. borders) have an authority that officially or legally designates their location or path. These features should not be allowed to move except by verified users. |
||
=== Free Ponies === |
|||
All users should be sent a pony each time they interact with the api. |
|||
== Improving Existing Features == |
== Improving Existing Features == |
Revision as of 00:06, 12 December 2009
API v0.7 is the next version of the OSM API. At this point, we're brainstorming new/changing features for API version 0.7.
Brainstorming
Please Note: The concept of Brainstorming means that everyone can add their ideas, however stupid, and the others are asked not to say immediately that they find the idea stupid. That phase (weeding out the stupid stuff) comes after the brainstorming. Please view the list below in light of this remark: If there is one person in the world who thinks that all OSM tags should exclusively be in Chinese in the future, then the list will have that feature. Indeed, for illustration, I have added this "idea" to the list. --Frederik Ramm 18:55, 11 December 2009 (UTC)
New Features
Layers
Support for layers so that editors only receive certain types of data to limit work load on clients and server.
"Verified" Users / Locked Tags
Some map features in OSM (e.g. borders) have an authority that officially or legally designates their location or path. These features should not be allowed to move except by verified users.
Free Ponies
All users should be sent a pony each time they interact with the api.
Improving Existing Features
All Tags in Chinese only
All tags should be translated to Chinese, and only Chinese characters should be accepted for tags in the future.
- Klingon would be better
Status During Diff Uploads
See osm-dev thread.