[OSM-legal-talk] Progressing OSM to a new data Licence regime
frederik at remote.org
Thu Feb 7 21:58:01 GMT 2008
> > BadMapCo creates a Collective Work based on their own mapping data
> > (roads in most places and footpath/cycle path data in places) and
> > augment this with additional footpath/cycle path from OSM (taken
> > as a Derivative Database with a geocoded boundary) and then
> > published the resulting DB as C BadMapCo as a Collective Database
> > with acknowledgement for OSM.
> If BadMapCo uses *only* footpaths from OSM, then the resulting DB can *not* be
> a collective one.
> For a DB to be part of a collective DB, it must be *unmodified*.
> Converting the data to another format (e.g. MySQL to PGSQL) is a
> modification. Even extracting a polygon is a modification.
Extracting a polygon is a modification but can you not separate the
1. Original OSM data
2. extract polygon, get a derived database, which you have to make
3. use the derived database, in unmodified form, and combine it with
your own data to make a collective database
Your own data would never take part in the formation of a derived
database in this case.
Frederik Ramm ## eMail frederik at remote.org ## N49°00.09' E008°23.33'
More information about the legal-talk