On 9/4/2011 6:51 PM, john whelan wrote:
The issue with using data like this with OSM is when you contribute it
under the new contribution terms you accept that OSM can change the
license at a later date. Practically speaking it makes it impossible
to respect any other license so currently
No, it was put in because we didn't want to have a rerun of all this mess if
something better came along next time.
Steve
Unfortunately it had implications that don't seem to have been thought
through especially for imports which I think are important for Canada where
we seem to have lots of
Maybe it wasn't thought through and maybe it has implications, but that wasn't
the point.
Steve
stevecoast.com
On Sep 7, 2011, at 17:56, john whelan jwhelan0...@gmail.com wrote:
No, it was put in because we didn't want to have a rerun of all this mess if
something better came along next
version first though.
THanks!
Tyler
--
Message: 3
Date: Wed, 07 Sep 2011 17:24:19 -0600
From: SteveC st...@asklater.com
To: talk-ca@openstreetmap.org
Subject: Re: [Talk-ca] BC Open Data License compatibility
Message-ID: 4e67fd23.3050...@asklater.com
Content
Hi,
What is the status on the BC Open Data site launched earlier this year?
License: http://www.data.gov.bc.ca/dbc/admin/terms.page?
It looks fine to me, but i know licensing is a big problem with osm.
In particular, i am looking at doing a manual import of protected areas amd
hiking trails (I
The issue with using data like this with OSM is when you contribute it under
the new contribution terms you accept that OSM can change the license at a
later date. Practically speaking it makes it impossible to respect any
other license so currently only PD data and things you have explicitly
6 matches
Mail list logo
