Re: [OSM-legal-talk] Data consumer use cases

2012-11-30 Thread Igor Brejc
Thank you, Jonathan On Fri, Nov 30, 2012 at 1:32 PM, Jonathan Harley wrote: > > Hi all, just a note to say that I've updated the Use Cases wiki page based > on the comments below from Igor and others who replied to me earlier in the > month. > > Michael - everyone who's commented about your re

Re: [OSM-legal-talk] Data consumer use cases

2012-11-30 Thread Jonathan Harley
Hi all, just a note to say that I've updated the Use Cases wiki page based on the comments below from Igor and others who replied to me earlier in the month. Michael - everyone who's commented about your redrafted guideline has agreed with it - maybe it's time to go ahead and replace what's

Re: [OSM-legal-talk] Data consumer use cases

2012-11-05 Thread Igor Brejc
On Mon, Nov 5, 2012 at 6:18 PM, Martin Koppenhoefer wrote: > 2012/11/5 David Groom : > > btw.: also removing might be of interest, e.g. someone checking "all" > businesses in OSM and removing them in the case they are closed now > would be a major improvement we would like to have fed back into OS

Re: [OSM-legal-talk] Data consumer use cases

2012-11-05 Thread Igor Brejc
On Mon, Nov 5, 2012 at 4:27 PM, Jonathan Harley wrote: > > Michael's reply to you about the "trivial transformation guideline" of 30 > October agrees with this - in his terms it provides no new "physical > observations" and the intent of the license is to capture those for > share-alike, not to e

Re: [OSM-legal-talk] Data consumer use cases

2012-11-02 Thread Igor Brejc
Hi Jonathan, I'm looking at the Case 2 (publish something based on OSM and nothing else). I think we need a clarification on what the "unmodified OSM database" means. For example: it's a common practice to simplify the line and polygon artwork when producing SVGs or PDFs (to reduce the file size a

[OSM-legal-talk] Data consumer use cases

2012-11-02 Thread Jonathan Harley
Goal-oriented wiki page, first draft: http://wiki.openstreetmap.org/wiki/License/Use_Cases Some points deliberately simplified for readability. C&C welcome. As I was going through all the ways one might make a derivative database, it struck me that there's an obvious way of dodging this - to