<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Stace<div class=""><br class=""></div><div class="">Regarding your first email on this topic you said - </div><div class=""><br class=""></div><div class="">"<span style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">to built a geocoding platform on Open Source software and Public Domain data that could be used to geocode research data</span><span style="white-space: pre-wrap;" class="">”</span></div><div class=""><span style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class="">Could you give an example of what the geocodable string would look like (just make one up)? Is it like “1 Alpha Street, Fooville” or is it more like “Smallville, AK” ?</span></span></div><div class=""><span style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class="">If it’s address data - are you aware that OSM doesn’t actually contain much at all and thus can’t help you?</span></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class="">If it’s not address data - are you aware that there are multiple PD sources for non-address level geocoding?</span></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class="">Because either way I’m having trouble understanding why OSM is in the way to achieving what you’re trying to do?</span></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></span></div><div class=""><span style="background-color: rgb(255, 255, 255);" class=""><span style="white-space: pre-wrap;" class="">Best</span></span></div><div class=""><span style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><div class=""><span style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">Steve</span></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 12, 2015, at 2:08 PM, Mr. Stace D Maples <<a href="mailto:stacemaples@stanford.edu" class="">stacemaples@stanford.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">
<div class="">
<div class="">Thanks, Alex. </div>
<div class=""><br class="">
</div>
<div class="">Clarity is exactly what is needed. Ambiguity = IRB Death. I’m going to be going through the OSM Licensing/Copyright Guidelines more closely over the next week and will comment outside this thread, if I have comments. </div>
<div class=""><br class="">
</div>
<div class="">For the record, I hardly think solving things like diarrhoeal disease (2nd leading cause of death in children, globally) and tracking human rights abuses in repressive regimes are a 1% problems. </div>
<div class=""><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">In F,L&T,</span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">Stace Maples </span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">Geospatial Manager </span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">Stanford Geospatial Center</span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">@mapninja </span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">staceymaples@G+</span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">Skype: stacey.maples</span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">214.641.0920</span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">Find GeoData: </span><a href="https://earthworks.stanford.edu/" class="" style="font-family: Helvetica; font-size: 18px;">https://earthworks.stanford.edu</a><span style="font-family: Helvetica; font-size: 18px;" class=""> </span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">Get GeoHelp: </span><a href="https://gis.stanford.edu/" class="" style="font-family: Helvetica; font-size: 18px;">https://gis.stanford.edu/</a><br class="" style="font-family: Helvetica; font-size: 18px;">
<br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">"I have a map of the United States... actual size. </span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">It says, "Scale: 1 mile = 1 mile." </span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">I spent last summer folding it." </span><br class="" style="font-family: Helvetica; font-size: 18px;">
<span style="font-family: Helvetica; font-size: 18px;" class="">-Steven Wright-</span></div>
</div>
</div>
<div class=""><br class="">
</div>
<span id="OLK_SRC_BODY_SECTION" class="">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span>Alex Barth <<a href="mailto:alex@mapbox.com" class="">alex@mapbox.com</a>><br class="">
<span style="font-weight:bold" class="">Reply-To: </span>"Licensing and other legal discussions." <<a href="mailto:legal-talk@openstreetmap.org" class="">legal-talk@openstreetmap.org</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Monday, October 12, 2015 at 12:32 PM<br class="">
<span style="font-weight:bold" class="">To: </span>"Licensing and other legal discussions." <<a href="mailto:legal-talk@openstreetmap.org" class="">legal-talk@openstreetmap.org</a>><br class="">
<span style="font-weight:bold" class="">Subject: </span>Re: [OSM-legal-talk] Proposed "Metadata"-Guideline<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Fri, Oct 9, 2015 at 5:41 PM, Steve Coast <span dir="ltr" class="">
<<a href="mailto:steve@asklater.com" target="_blank" class="">steve@asklater.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="adM">
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Oct 9, 2015, at 3:22 PM, Alex Barth <<a href="mailto:alex@mapbox.com" target="_blank" class="">alex@mapbox.com</a>> wrote:</div>
<div class="">
<div dir="ltr" class="">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, Oct 9, 2015 at 12:07 PM, Steve Coast <span dir="ltr" class="">
<<a href="mailto:steve@asklater.com" target="_blank" class="">steve@asklater.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you want all these rights, you can just pick up the phone and pay HERE or TomTom for them, they’d love to hear from you.</blockquote>
<div class=""><br class="">
</div>
<div class="">What's more interesting than sending people to HERE and TomTom is making them contributors to OpenStreetMap, no?</div>
</div>
</div>
</div>
</div>
</blockquote>
<br class="">
</div>
</div>
</div>
<div class="">Absolutely, but at what cost?</div>
<div class=""><br class="">
</div>
<div class="">OSM solved 95% or 99% of our problems. Should we fundamentally change OSM to claim the last 1% so someone can make slightly more money or complete an academic project? I don’t think that’s a worthwhile tradeoff. I’m super happy with the 99% we achieved
already.</div>
</blockquote>
</div>
<br class="">
I'm very happy about what we have achieved too. I don't think we're solving 95% of our problems with OSM though.</div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">"our problems" would of course need more definition and I'm running the risk here of misinterpreting what you said. I'm thinking about all the cases where OSM isn't used yet, all the mapping that isn't happing in OSM yet. OSM has the
potential to fundamentally change how we capture and share knowledge about the world but we aren't anywhere near the full impact we should be having. 300,000 active mappers is impressive but the world is much bigger. At a time where the internet that was supposed
to be Open is turning more and more into a closed game of big players and growth for OSM is linear - what's our plan? Fixing the license surely can't be the extent of our plan, but we need to be able to have a frank conversation about how licensing is hurting
use cases and engagement on OSM, without second guessing people's intentions and without just showing them the door to TomTom and HERE. In that context I find comparing ODbL to Public Domain absolutely useful.</div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">I think Stace's comments give a great glimpse into licensing pain points in the academic community in the US and the guideline Simon pulled together is going to fix some of the issues he's brought up. Having clarity how data linked
to OSM does not extend the ODbL's share alike to that data should go a long way to address some of the concerns he raised.</div>
<div class="gmail_extra"><br class="">
</div>
</div>
</div>
</div>
</span>
</div>
_______________________________________________<br class="">legal-talk mailing list<br class=""><a href="mailto:legal-talk@openstreetmap.org" class="">legal-talk@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/legal-talk<br class=""></div></blockquote></div><br class=""></div></body></html>