Re: [OSM-legal-talk] Updated geocoding community guideline proposal

2014-07-16 Thread Richard Fairhurst
[I'm going to break my rule of not posting to the mailing lists for this, because it's an interesting query and important for OSM. Since I started writing this, Robert has made an excellent posting which covers much of the same ground and comes to related conclusions, but from a slightly different

Re: [OSM-legal-talk] Updated geocoding community guideline proposal

2014-07-16 Thread Kai Krueger
I thought I'd throw in my $0.02 into the discussion as well. First of all, I think it is good that we are having this discussion and I hope that eventually we can come to a OSMF sanction conclusion (set of community guidelines) one way or another. Overall, I think the route via produced works is

Re: [OSM-legal-talk] Updated geocoding community guideline proposal

2014-07-16 Thread Kai Krueger
Robert Whittaker (OSM lists) wrote So the way I see it, if there's any (substantial) addition of external geo-data along the way, then that addition creates a derivative database, before the produced work is created. So if you want to publicly use this database (or any produced work based on

Re: [OSM-legal-talk] Updated geocoding community guideline proposal

2014-07-16 Thread Frederik Ramm
Hi, On 07/17/2014 01:25 AM, Kai Krueger wrote: For forward geocoding, the picture gets a bit more murky though, as the distinction between what is for human consumption and what is data, and thus a derived database, is much less clear cut. Indeed. If we were only talking about the enter your