OpenStreetMap bot removes waypoints after licensing change (The H)
The reason for the licensing change is that the current Creative Commons licence is largely inapplicable to collections of data such as the OpenStreetMap mapping database. The Open Database licence has been developed to resolve this problem. Like the Creative Commons licence, it is a share-alike licence, meaning users must return any improvements or changes to the data to the community." The removal is said to be "
barely noticeable in many places" but there have been some complaints in the OSM community.
Posted Jul 28, 2012 0:44 UTC (Sat)
by lordsutch (guest, #53)
[Link] (12 responses)
Posted Jul 28, 2012 8:28 UTC (Sat)
by epa (subscriber, #39769)
[Link] (11 responses)
Posted Jul 28, 2012 13:09 UTC (Sat)
by giggls (subscriber, #48434)
[Link]
Besides the fact that I prefer ODBL over CC-by-SA for a couple of reasons (e.g. Mixing free for non-commercial use data like cgiar SRTM with osm for tile production will now be possible) I think flosm.org is doomed to fail.
The impact of the licence has not been that bad as I suspected anyway.
Here is the a short blog article I wrote while looking at the aerea I live after the redaction bot came by:
Sven
Posted Jul 28, 2012 16:55 UTC (Sat)
by robert_s (subscriber, #42402)
[Link] (9 responses)
It's only self inflicted in the way an appendectomy is.
"or you can instead use fosm.org, which will stay with CC and so is not deleting any contributions."
..though it is run by a bunch of clowns and malcontents and is a great way of sending your contributions down a dead end.
I feel it's important to add that warning.
If people just want the old data, the old planet files are still up and always will be.
Posted Jul 29, 2012 14:44 UTC (Sun)
by macc (guest, #510)
[Link] (8 responses)
Pft!
More like gauging out your other perfectly good "blue" eye because it has a pigmentation fault.
Posted Jul 29, 2012 15:28 UTC (Sun)
by robert_s (subscriber, #42402)
[Link] (7 responses)
Thing is, the whole sticking-your-fingers-in-your-ears-and-screaming-"the-license-is-ok-as-it-is-the-license-is-ok-as-it-is" approach doesn't tend to work in court.
Posted Jul 29, 2012 19:43 UTC (Sun)
by macc (guest, #510)
[Link] (4 responses)
Destructively removing voluntary work is the worst thing
Compare to the DE wikipedia relevance nazis.
This will cost dearly, imho.
Posted Jul 30, 2012 9:03 UTC (Mon)
by robert_s (subscriber, #42402)
[Link] (3 responses)
By this logic we shouldn't remove contributions where people have blatantly traced from google aerial view.
Posted Jul 30, 2012 9:58 UTC (Mon)
by macc (guest, #510)
[Link] (2 responses)
Good Bye.
Posted Jul 31, 2012 8:52 UTC (Tue)
by robert_s (subscriber, #42402)
[Link]
cf. "can selfafflict unto itself".
Good bye.
Posted Jul 31, 2012 20:59 UTC (Tue)
by robert_s (subscriber, #42402)
[Link]
Oh and no, I'm not really interested in discussion. There have been 5 years of discussion. I've been there since day one. I have heard an awful lot of nonsense in those 5 years, and a lot of people seem to just want to discuss things into the sunset.
Posted Jul 29, 2012 21:37 UTC (Sun)
by tzafrir (subscriber, #11501)
[Link] (1 responses)
Posted Aug 2, 2012 22:14 UTC (Thu)
by ElCapitano (guest, #86078)
[Link]
Posted Jul 28, 2012 8:23 UTC (Sat)
by epa (subscriber, #39769)
[Link] (4 responses)
You can read more in this thread: http://article.gmane.org/gmane.comp.gis.openstreetmap.leg...
The summary is that the OSM map data is covered by copyright, and there is no reason to suppose that the CC licence doesn't work for it just as it does for other copyrightable works.
Another point to note is that while ODbL is also a share-alike licence, the licence change means that derived works or improvements to the map can no longer automatically be fed back to OSM, since the OSMF now require agreement to a set of contributor terms.
Posted Jul 28, 2012 17:01 UTC (Sat)
by robert_s (subscriber, #42402)
[Link] (3 responses)
Posted Jul 30, 2012 9:23 UTC (Mon)
by epa (subscriber, #39769)
[Link] (2 responses)
The two US law firms employed did not want me to distribute the full report publicly because of privilege issues. I do not agree with that but I went along at their insistence. That is why the version linked above is only a summary. If you are interested I would be happy to send you the full research which cites the relevant cases and arguments.
Posted Aug 2, 2012 22:17 UTC (Thu)
by ElCapitano (guest, #86078)
[Link] (1 responses)
Posted Aug 3, 2012 10:42 UTC (Fri)
by epa (subscriber, #39769)
[Link]
Posted Jul 30, 2012 10:05 UTC (Mon)
by ballombe (subscriber, #9523)
[Link] (12 responses)
Posted Jul 30, 2012 10:45 UTC (Mon)
by gioele (subscriber, #61675)
[Link] (11 responses)
Why do you way so?
Section 3 of the OSM contributor term forces the OSMF to always use "free and open licenses":
> 3. OSMF agrees that it may only use or sub-license Your Contents as part of a database and only under the terms of one or more of the following licences: ODbL 1.0 for the database and DbCL 1.0 for the individual contents of the database; CC-BY-SA 2.0; or such other free and open licence (for example, http://www.opendefinition.org/okd/) as may from time to time be chosen by a vote of the OSMF membership and approved by at least a 2/3 majority vote of active contributors.
One may disagree with the new licences and the methods used to achieve this change, but OSM is still a well behaving member of the free software/knowledge community.
Posted Jul 30, 2012 11:43 UTC (Mon)
by hummassa (subscriber, #307)
[Link] (8 responses)
For starters, because the ODbL 1.0 does not pass the DFSG? (It has a desert-island-test problem in section 4.6 IIRC...)
Posted Jul 30, 2012 13:36 UTC (Mon)
by gioele (subscriber, #61675)
[Link] (1 responses)
I could not find a detailed analysis of the problems of DFSG with ODBL. Pointers?
The only thing I have seen is <http://lists.debian.org/debian-legal/2010/08/msg00006.html> there the author says he finds a problem with licence and he does not want it accepted as DFSG-compliant, for the same reasons he do not think that AGPLv3 should be treated as DFSG-complieant. Anyhow, he later admits that AGPLv3 has been accepted as DFSG-compliant by the FTP masters and that ODBL is probably as much compliant as AGPLv3.
Posted Jul 30, 2012 17:27 UTC (Mon)
by hummassa (subscriber, #307)
[Link]
> The ODbL try to enforce EU-style sui-generis database right in jurisdiction where they do not exist in law.
Posted Jul 31, 2012 8:56 UTC (Tue)
by robert_s (subscriber, #42402)
[Link] (5 responses)
The key letter there is the S in DFSG. The DFSG is designed for _software_, and those who wrote it would be the first to point that out.
Unfortunately geodata is one of the most complex corners of copyright law.
Posted Jul 31, 2012 19:44 UTC (Tue)
by nowster (subscriber, #67)
[Link] (1 responses)
Is a PostScript document sent to a printer not software? Can a list of points and lines be software for some virtual machine? The distinction is not clear.
Posted Aug 2, 2012 22:19 UTC (Thu)
by ElCapitano (guest, #86078)
[Link]
Posted Jul 31, 2012 20:12 UTC (Tue)
by hummassa (subscriber, #307)
[Link] (2 responses)
Ah, silly me, but that is *exactly* Debian's definition... Any WORK contained in debian must be Free in accordance to the DFSG.
Seriously, now, geodata is complex because it is not considered everywhere as copyrightable. And the ODbL is not DFSG-compliant, not because it is analog to the AGPL, but both because it does not pass the desert island test and because it tries to emulate database-rights restrictions in jurisdictions where databases do not generate any rights. THAT is why CC-BY-SA was a better license than ODbL for OSM data.
Posted Jul 31, 2012 21:06 UTC (Tue)
by robert_s (subscriber, #42402)
[Link] (1 responses)
Well, it's not just that - it's also about what is considered a derived work.
"THAT is why CC-BY-SA was a better license than ODbL for OSM data."
Except that its fuzziness in the area of geodata had the beautiful dual quality of scaring off potential commercial users while at the same time probably also being unenforceable. Certainly unenforceable against a foe with any real legal budget to speak of as OSM's legal budget is ~0.
Posted Aug 1, 2012 8:16 UTC (Wed)
by epa (subscriber, #39769)
[Link]
Posted Jul 30, 2012 14:12 UTC (Mon)
by ballombe (subscriber, #9523)
[Link] (1 responses)
Any "license" that restrict rights you would have in the absence of a license is non-free (and is actually a contract).
Posted Aug 2, 2012 22:10 UTC (Thu)
by ElCapitano (guest, #86078)
[Link]
The only honest alternative to ODbL is to declare the data public domain. Otherwise you have the inequitable situation, as with CC-BY-SA, where users of the data in the US have more rights than users of the data in the UK.
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
Certainly not because of licence terms but because OSM is where the people are.
http://blog.gegg.us/2012/07/my-subjective-perception-of-t...
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
a project like this can selfafflict unto itself.
( people that have a live just don't add/edit anymore )
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
You are in it here for winning an argument
and not for a beneficial discussion.
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
CC licenses are going in exactly the wrong direction for OSM. CC's declared intent is that its Share-Alike clause will tend to the maximalist (see point 3). That is diametrically opposed to ODbL's Produced Work clause.
OpenStreetMap bot removes waypoints after licensing change (The H)
Supposed reason for licence change
Supposed reason for licence change
Supposed reason for licence change
Certainly it would be interesting to see the unedited brief which you gave to these lawyers. I don't believe there's anything preventing you publishing that.
Supposed reason for licence change
Supposed reason for licence change
OpenStreetMap bot removes waypoints after licensing change (The H)
Fare well.
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
> Any "license" that restrict rights you would have in the absence of a license is non-free (and is actually a contract).
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)
OpenStreetMap bot removes waypoints after licensing change (The H)