Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-08 Thread Dave Stubbs
2009/3/8 Andy Allan gravityst...@gmail.com: On 7 Mar 2009, at 23:56, OJ W ojwli...@googlemail.com wrote: On Sat, Mar 7, 2009 at 9:10 PM, Gervase Markham gerv- gm...@gerv.net wrote: b) If people are reverse-engineering our stuff,  they need a massive, sustained, continuous Mechanical Turk

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-08 Thread Richard Weait
On Sun, 2009-03-08 at 13:00 +0100, Frederik Ramm wrote: If someone really wants to jump through these hoops to get it done, let him do it. I think this will be a niche application and, if at all, only used very seldom. And if we later find that someone is really being a thorn in our side

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-08 Thread Nic Roets
On Sun, Mar 8, 2009 at 7:37 PM, Ulf Möller use...@ulfm.de wrote: The problem with this though is that if you make an exemption for CC-BY-SA then you can drive the whole planet file through that loophole. If you want to close the loophole, you will need to get everyone to accept the

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-08 Thread 80n
On Sun, Mar 8, 2009 at 6:02 PM, Nic Roets nro...@gmail.com wrote: On Sun, Mar 8, 2009 at 7:37 PM, Ulf Möller use...@ulfm.de wrote: The problem with this though is that if you make an exemption for CC-BY-SA then you can drive the whole planet file through that loophole. If you want to

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-08 Thread Frederik Ramm
Hi, Gervase Markham wrote: I would be reluctant to name them. Assuming the data remains bound by some form of share-alike, in 50 years time, OSM or OSM derivatives is going to be the only database anyone ever uses for storing and retrieving public global mapping data. At that point, we

[OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-07 Thread Gervase Markham
The question has been raised in these discussions about the ODbL's reverse-engineering provisions, and their compatibility or otherwise with share-alike licenses. Here is my analysis and suggestions. 1) The ODbL wishes to prevent people regenerating the Database from Produced Works. ODbL

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-07 Thread 80n
On Sat, Mar 7, 2009 at 9:10 PM, Gervase Markham gerv-gm...@gerv.net wrote: a) GPL and CC-BY-SA compatibility of produced works is more important. Agreed, but... b) If people are reverse-engineering our stuff, either they need a massive, sustained, continuous Mechanical Turk effort, or

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-07 Thread Andy Allan
On 7 Mar 2009, at 23:56, OJ W ojwli...@googlemail.com wrote: On Sat, Mar 7, 2009 at 9:10 PM, Gervase Markham gerv- gm...@gerv.net wrote: b) If people are reverse-engineering our stuff, they need a massive, sustained, continuous Mechanical Turk effort unless they create SVG files that just

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-07 Thread Frederik Ramm
Hi, Gervase Markham wrote: So what can be done? I agree that reverse engineering is a risk. Life is not perfect. But still, my suggestion is that we should abandon the idea of trying to prevent reverse engineering, for the following reasons: a) GPL and CC-BY-SA compatibility of produced

Re: [OSM-legal-talk] Reverse-Engineering Maps and Share-Alike Licences

2009-03-07 Thread Frederik Ramm
Hi, Andy Allan wrote: I think without the reverse engineering clause, you may as well make it PD in the first place.. As I said: You could drop the reverse engineering clause for certain share-alike licenses only, thus making reverse-engineering into a share-alike form possible but that