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

2014-07-15 Thread Mikel Maron
This is a solid proposal and has my support. As long as the purpose of a geocoder is geocoding, and not reverse engineering OSM,  then it sensibly fits within the notions of an ODbL produced work. What I wonder is how we will move to decision making on the proposal? What's the OSMF process?  

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

2014-07-15 Thread Frederik Ramm
Hi, On 07/15/2014 01:26 PM, Mikel Maron wrote: As long as the purpose of a geocoder is geocoding, and not reverse engineering OSM, then it sensibly fits within the notions of an ODbL produced work. What if there are two processes run on a city extract - one is a SELECT * FROM

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

2014-07-15 Thread Paul Norman
On 2014-07-15 4:26 AM, Mikel Maron wrote: As long as the purpose of a geocoder is geocoding, and not reverse engineering OSM, then it sensibly fits within the notions of an ODbL produced work. A geocoder isn't a produced work or a derived database - it's software. Do you mean a geocoding

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

2014-07-15 Thread Martijn van Exel
On Mon, Jul 14, 2014 at 12:40 PM, Paul Norman penor...@mac.com wrote: On 2014-07-14 11:26 AM, Alex Barth wrote: Also if we assume geocoding yields Produced Work the definition of Substantial doesn't matter. A database that is based upon the Database, and includes any translation,

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

2014-07-15 Thread Michal Palenik
On Tue, Jul 15, 2014 at 04:26:28AM -0700, Mikel Maron wrote: As long as the purpose of a geocoder is geocoding, and not reverse engineering OSM,  then it sensibly fits within the notions of an ODbL produced work. please, read ODbL... produced work is “Produced Work” – a work (such as an

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

2014-07-15 Thread Martin Koppenhoefer
2014-07-15 18:01 GMT+02:00 Michal Palenik michal.pale...@freemap.sk: btw, cp planet.osm.bz2 planet.png creates a produced work... LOL I'd doubt this, because an image is likely not to be read like in disk image, and not every file with an png extension will be considered an image...

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

2014-07-15 Thread Randy Meech
On Tue, Jul 15, 2014 at 7:26 AM, Mikel Maron mikel.ma...@gmail.com wrote: This is a solid proposal and has my support. +1 This is a great effort to clarify something that causes a lot of confusion, and does so within the context of the current license. Very productive! As long as the purpose

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

2014-07-15 Thread Michal Palenik
On Tue, Jul 15, 2014 at 06:22:29PM +0200, Martin Koppenhoefer wrote: 2014-07-15 18:01 GMT+02:00 Michal Palenik michal.pale...@freemap.sk: btw, cp planet.osm.bz2 planet.png creates a produced work... LOL I'd doubt this, because an image is likely not to be read like in disk image, and not

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

2014-07-15 Thread Robert Whittaker (OSM lists)
On 11 July 2014 03:52, Alex Barth a...@mapbox.com wrote: I just updated the Wiki with a proposed community guideline on geocoding. Please review: https://wiki.openstreetmap.org/wiki/Open_Data_License/Geocoding_-_Guideline The whole point of the share-alike aspect of our licence is to stop