[OSM-talk] OSMF to provide commercial tile service? [WAS: something else]

[Stefan de Konink]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Op 09-10-11 19:40, Frederik Ramm schreef:
> On 10/09/2011 05:51 PM, Stefan de Konink wrote:
>> OSMF could be the primary shareholder of a private entity that 
>> commercially exploits hosting tiles (..and what not more).
> 
> I'm surprised to hear that from someone who usually doesn't trust
> OSMF one bit!

That doesn't mean that I trust the shareholders of any other company I
get services from?


> RichardWeait is right in saying that this would be a recipe for a
> PR disaster. Whenever OSMF would change their tile policy -
> blocking additional IPs or applications or usage patterns, changing
> the definition of what is ok and what isn't - people would accuse
> OSMF of just wanting to regulate tile access in order to make more
> money with the commercial arm.

The idea is indeed that the OSMF would set a tile policy or uses the
current policy and enforce it. This will create a level playing field
for any commercial provider. Think of the ones that Andy mentioned and
are placed on the wiki. I see even an possibility that anyone that
wants to use the OSM should dedicated theirself to serve x percent of
the tiles as part of a global OpenStreetMap CDN.

But I was never an out-of-the-box thinker so ignore my fooling thoughts!


> And if your past attitude is anything to go by, then you would be
> one of the first to cry foul in such a situation.

Since I currently placed my arrows on the distribution and the use of
PD, CC-0 and CC-BY data. And work closely with Google to publish our
Dutch transit feeds to them as -open data-, I have better things to
do, because more people would use my data :) I thought that was the
idea of OSMF too: getting more people to use OpenStreetMap ;)


Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREKAAYFAk6UjJgACgkQYH1+F2Rqwn1rCQCeO4YajWxWOstotj3hHTbiqqv9
dWsAoIC9aCeUS2YM9Ya1eH0CZgvomCpp
=BKv1
-----END PGP SIGNATURE-----