Re: [OSM-talk] [Osmf-talk] ODbL text

2018-04-09 Thread Simon Poole
Am 09.04.2018 um 00:30 schrieb Michael Kugelmann: > On 08.04.2018 at 14:12 Simon Poole wrote: >> PS: that doesn't mean that having our own clean copy as a backup >> wouldn't be a good idea, > I very much encourage the OSMF to host a copy of the license as the > OSMF distributes their data (=>

Re: [OSM-talk] [Osmf-talk] ODbL text

2018-04-08 Thread Michael Kugelmann
On 08.04.2018 at 14:12 Simon Poole wrote: PS: that doesn't mean that having our own clean copy as a backup wouldn't be a good idea, I very much encourage the OSMF to host a copy of the license as the OSMF distributes their data (=> the raw OSM data)  using this license. This could be clearly

Re: [OSM-talk] [Osmf-talk] ODbL text

2018-04-08 Thread James
Just because you are not the curator of the license doesnt mean you cant display the full legal text somewhere else...The text wont change. GPL, LGPL, BSD, etc projects usually distribute their software with a license text file with the full legal text and dont depend on 1 single point of failure

Re: [OSM-talk] [Osmf-talk] ODbL text

2018-04-08 Thread Simon Poole
Am 08.04.2018 um 13:30 schrieb James: > why not host it on the osmf website? Because we don't own the domain (which is what most references to the actual text use) and are not the curators of the licence (aka we could in principle simply covertly change the text of the license, having a third

Re: [OSM-talk] [Osmf-talk] ODbL text

2018-04-08 Thread James
why not host it on the osmf website? On Sun, Apr 8, 2018, 5:46 AM Simon Poole, wrote: > Currently I'm pointing to > http://web.archive.org/web/20180317184051/https://opendatacommons.org/licenses/odbl/ > however as the opendatacommons.org links are all over the place that > isn't

Re: [OSM-talk] [Osmf-talk] ODbL text

2018-04-08 Thread Simon Poole
Currently I'm pointing to http://web.archive.org/web/20180317184051/https://opendatacommons.org/licenses/odbl/ however as the opendatacommons.org links are all over the place that isn't really a solution. OKI seems to be aware of the issue, but that is about all what we know (they seem to be