begin quoting Tracy R Reed as of Wed, Nov 30, 2005 at 06:46:07AM -0800:
> Wade Curry wrote:
> > similar effect for an open map database. How would you keep it
> > open and still mitigate against errors, innocent or malicious?
>
> Wikipedia info can be very subjective and difficult to verify. I suspect
Most things are difficult to verify.
> that an open map database would be far simpler.
Depends on the verification process.
It needs to be easy to correct (in order to encourage people to submit
corrections) and hard to corrupt. Those goals are probably at odds...
> If someone places the
> lat/long for the Eiffel Tower in San Diego, something's up. More subtle
Or the London Bridge in Arizona.
> position errors are more difficult to detect but because people would
> actually be using this info for navigation and incorrect data would be a
> real problem you can bet people would notice
Well, there's "notice", and then there's "notice and fix", and then
there's "THE HELL I'M GOING TO LET YOU INVADE MY PRIVACY" types who'll
obsessively "uncorrect" fixes if there's not a good mechanism to prevent
'em.
If just anyone could modify the geodata, how long before we have
advertising ("wait a minute, the 8 doesn't spell out 'Coca-Cola'
out in Santee!") and petty corporate warfare (A McDonalds manager
deletes or moves the locations of Burger Kings).
> unlike some questionable
> info which gets included in someones school report which the teacher
> probably would not notice as incorrect either.
Like the rules regarding run-on sentences...
-Stewart "Correcting the World Vector Shoreline was fun." Stremler
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
