[OHM] OGL & OHM

Tue May 26 06:44:29 UTC 2015

I am in favour or creating a future-compatible environment, but we should
collect data about where the problems are.

Source attribution should ideally not be tied to the issue of copyright. I
think it should be a requirement per se in this environment where the
usefulness of the data stems from knowing the provenance of the data. That
information should go down to feature level.

I think based on Jerry's examples, using OSM data to work locations back in
time is very useful. OSM data provides quantities that are hard to get any
other way. So they should be made compatible.

PD/CC0 would be an ideal exchange basis. What would this block, what is
blocking it? BY is acceptable, though should not be tied to copyright. SA
is already an interoperability issue, I hope we could work on that. What
cases are there? NC and ND are not accepted as open licenses, we should not
support them. Creative Commons is again useful because 4.0 handles database
rights.

Correct me for mistakes.

Susanna

2015-05-26 8:26 GMT+03:00 Jeff Meyer <jeff at gwhat.org>:

> Copyright harmonization across a crowdsourced dataset is tricky, indeed.
>
> Albin - is this the page you're referencing from MapBox:
> https://www.mapbox.com/about/maps/
> OSM actually has a semi-similar (and incomplete) page like that here:
> http://wiki.openstreetmap.org/wiki/Contributors
>
> Also, to be clear, we are talking about the UK Open Government License
> <http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/>
> & not the Open Gaming License
> <http://www.wizards.com/default.asp?x=d20/oglfaq/20040123f>, correct? ; )
>
> Albin, is it a definitive truth that the OGL and ODBL are incompatible?
> Has anyone confirmed that providing a source reference on a wiki wouldn't
> suffice for compliance? There are many methods of attribution. Has the OGL
> been a blocker for importing (yes...) UK-based data into OSM?
>
> Jerry's assertion that academic users will want a richer form of
> attribution seems consistent with academics' need to be able to document
> metadata provenance. My hope, however, is that we can encourage data
> providers to get away from the NC provisions. Governments seem to be fine
> with this, even if academics have yet to move that way.
>
> Does anyone know of any good comparable systems where sources and
> copyright restrictions are traced back down to the tag / metadata level? It
> would, for example, be nice to be able to identify a subset of CC0
> information from within our data.
>
> Thanks, Jeff
>
>
> On Sat, May 23, 2015 at 11:42 AM, SK53 <sk53.osm at gmail.com> wrote:
>
>> Well I (and others) use OSM data for very good reasons: it would be a
>> real pain to have recreate it just to put it into OHM. The approach taken
>> with OSM was to check with OGL folk who's data was in use if they were
>> happy being credited as OpenStreetMap contributors (available as a page on
>> the wiki). OHM will undoubtedly run into issues with attribution, but in
>> practice so does any other project on an inter-connected web.
>>
>> My general concern is that many prospective academic users would expect a
>> CC-BY-SA-NC licence.
>>
>> I suspect that we need richer techniques for attribution over & above
>> OSM; less to meet source providers needs to make make the data acceptable
>> to consumers.
>>
>> Jerry
>>
>> On 23 May 2015 at 18:55, Albin Larsson <albin.post at gmail.com> wrote:
>>
>>> OGL requires attribution back to the original source. Currently OHM
>>> doesn't provide such information.
>>>
>>> We could have a page such as the one Mapbox has for all its data
>>> sources.
>>>
>>> Adding data with different licenses and requirements will give us a lot
>>> of issues when deciding on a license.
>>>
>>> Also using the same approach as Mapbox will make it much harder for
>>> people to reuse OHM data because of the many licenses. Also there is no way
>>> we could know what data is under what license in such a open project.
>>>
>>> Personally I would strongly recommend not adding any data under a non
>>> public domain or public domain like license to OHM before deciding on a
>>> license. I can't see the need of OSM imports, people that want to combine
>>> the data could do so by them self...
>>>
>>> //
>>> Albin
>>> On May 23, 2015 7:17 PM, "Jeff Meyer" <jeff at gwhat.org> wrote:
>>>
>>>> Albin - you tweeted that OGL & OHM were incompatible. Can you clarify
>>>> or add some background here?
>>>>
>>>> Copyright is something we haven't really resolved, but it's not clear
>>>> that we would have to be in lock step with OSM (although that would make
>>>> OSM- > OHM imports trickier.
>>>>
>>>> - jeff
>>>>
>>>>
>>>> --
>>>> Jeff Meyer
>>>> Global World History Atlas
>>>> www.gwhat.org
>>>> jeff at gwhat.org
>>>> 206-676-2347
>>>>
>>>> OpenStreetMap: Mapping with a Human Touch
>>>> osm: Open Historical Map (OHM)
>>>> <http://wiki.openstreetmap.org/wiki/Open_Historical_Map> / my OSM user
>>>> page <http://www.openstreetmap.org/user/jeffmeyer>
>>>> t: @GWHAThistory <https://twitter.com/GWHAThistory> / @OpenHistMap
>>>> f: GWHAThistory <https://www.facebook.com/GWHAThistory>
>>>>
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> Historic mailing list
>>> Historic at openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/historic
>>>
>>>
>>
>
>
> --
> Jeff Meyer
> Global World History Atlas
> www.gwhat.org
> jeff at gwhat.org
> 206-676-2347
>
> OpenStreetMap: Mapping with a Human Touch
> osm: Open Historical Map (OHM)
> <http://wiki.openstreetmap.org/wiki/Open_Historical_Map> / my OSM user
> page <http://www.openstreetmap.org/user/jeffmeyer>
> t: @GWHAThistory <https://twitter.com/GWHAThistory> / @OpenHistMap
> f: GWHAThistory <https://www.facebook.com/GWHAThistory>
>
>
>
>
> _______________________________________________
> Historic mailing list
> Historic at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/historic
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/historic/attachments/20150526/138ac9be/attachment-0001.html>