<div class="gmail_quote">On Wed, Sep 1, 2010 at 9:14 AM, Torsten Rahn <span dir="ltr"><<a href="mailto:tackat@t-online.de">tackat@t-online.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
But I think there should be an aim to introduce some place where I can look up<br>
which services/Urls etc. are considered stable and supported and which are<br>
considered experimental or deprecated. And I think that it should be the aim<br>
of OSM to have a proper deprecation process. :-)</blockquote><div><br></div><div>I don't think OSM provides any services that the public should consider "stable" in the sense of "99.999% uptime, transaction guaranteed or your money back". The closest might be the API server, but even that could possibly go down as has been described before.</div>
<div><br></div><div>OSM is about the data itself, not the services around it. The services available on the website and wiki are there because someone thought it would be a nice way to help debug or otherwise improve mapping and map data quality, not to provide a service to external users like KDE, Microsoft, Google or anyone for that matter.</div>
<div><br></div><div>The bottom line is: if you want a stable service, run it yourself. That's why the data is under a relatively free and open license.</div></div>