<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span><div>> It would appear that any and all data associated with a website or mobile app becomes fair game once OSM data is used. </div><div><br></div><div>That may be "an" appearance, but it is not true.</div></span></div><div style="color: rgb(0, 0, 0); font-size: 16.363636016845703px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16.363636016845703px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;"><span>Actually, you should be fine, this is a very common use case. </span></div><div style="color: rgb(0, 0, 0); font-size: 16.363636016845703px; font-family: 'times new roman', 'new york', times, serif; background-color:
transparent; font-style: normal;"><span>There are some details, but when making tiles, as long as they are only rendered together, not put together in a single "database", there's no share-alike.</span></div><div style="color: rgb(0, 0, 0); font-size: 16.363636016845703px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;"><span><a href="http://wiki.openstreetmap.org/wiki/License/Use_Cases#Case_3:_I_want_to_publish_something_based_on_OSM_and_my_own_data">http://wiki.openstreetmap.org/wiki/License/Use_Cases#Case_3:_I_want_to_publish_something_based_on_OSM_and_my_own_data</a><br></span></div><div></div><div> </div><div>I agree this isn't clear. Confusion is certainly an issue with ODbL.</div><div><br></div><div>Alex's issue with geocoding is different. I agree, we need to take a serious look at this, and have it clarified.</div><div><br></div><div>* Mikel Maron * +14152835207 @mikel
s:mikelmaron<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Rob <smarttiki@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> Licensing and other legal discussions. <legal-talk@openstreetmap.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, February 27, 2013 4:19 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [OSM-legal-talk] License question, user clicking on map<br> </font> </div> <br>
<div id="yiv1479802613"><div><div>+1 +1 +1</div><div><br></div><div>Would love to use OSM data to create a tile server for a project I have in the works but the share-alike clause has stopped me from moving forward with OSM. </div><div><br></div><div>Rather than share-alike I would like to share-what-I-like but that is not an option.</div><div><br></div><div>Currently there seems to be no limit to what OSM could claim rights to under the share-alike clause. </div><div><br></div><div>It would appear that any and all data associated with a website or mobile app becomes fair game once OSM data is used. </div><div><br></div><div>Rob</div><div><br><br>Sent from my iPhone</div><div><br>On Feb 27, 2013, at 3:24 PM, Marc Regan <<a rel="nofollow" ymailto="mailto:marcregan@gmail.com" target="_blank" href="mailto:marcregan@gmail.com">marcregan@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<div>
<blockquote type="cite"><div dir="ltr">I'm also going to add we should do away with share alike in the mid term. It's just complicated and hurting OSM. Case in point: example at hand.</div></blockquote>
</div>
<div><div>+1. If you want to do anything with OSM data besides make map tiles, the cloud of uncertainty around what you can and can't do with the data is pretty terrifying. Instead of rallying around the community and getting excited about improving OSM, you instead spend time looking at alternatives and trying to find lawyers who are experts in software licensing who you can afford to talk to.</div><div><br></div><div>The share-alike clause makes the barrier to using OSM data very high. </div><div><br></div><div><br></div>-- <br>Marc Regan<br><div><br></div></div>
<div style="color:#A0A0A8;">On Wednesday, February 27, 2013 at 2:04 PM, Alex Barth wrote:</div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div dir="ltr"><div><br><div>On Fri, Feb 22, 2013 at 11:19 AM, Kate Chapman <span dir="ltr"><<a rel="nofollow" ymailto="mailto:kate@maploser.com" target="_blank" href="mailto:kate@maploser.com">kate@maploser.com</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div> My<br>
understanding is you are saying "I would like it to be this way," but<br>
at the moment it is not. Correct?</div></blockquote></div><br>Actually to be more specific: I'm saying "I would like geocoding-like use cases to be clarified, at the moment it is not clear. Here is what we should do: specifically allow narrow extractions of OSM for geocoding-like use cases to happen without the share-alike clause to kick in.". I'm also going to add we should do away with share alike in the mid term. It's just complicated and hurting OSM. Case in point: example at hand.</div>
<div><br></div></div>
</div><div><div>_______________________________________________</div><div>legal-talk mailing list</div><div><a rel="nofollow" ymailto="mailto:legal-talk@openstreetmap.org" target="_blank" href="mailto:legal-talk@openstreetmap.org">legal-talk@openstreetmap.org</a></div><div>http://lists.openstreetmap.org/listinfo/legal-talk</div></div></div></span>
</blockquote>
<div>
<br>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>legal-talk mailing list</span><br><span><a rel="nofollow" ymailto="mailto:legal-talk@openstreetmap.org" target="_blank" href="mailto:legal-talk@openstreetmap.org">legal-talk@openstreetmap.org</a></span><br><span><a rel="nofollow" target="_blank" href="http://lists.openstreetmap.org/listinfo/legal-talk">http://lists.openstreetmap.org/listinfo/legal-talk</a></span><br></div></blockquote></div></div><br>_______________________________________________<br>legal-talk mailing list<br><a ymailto="mailto:legal-talk@openstreetmap.org" href="mailto:legal-talk@openstreetmap.org">legal-talk@openstreetmap.org</a><br><a href="http://lists.openstreetmap.org/listinfo/legal-talk" target="_blank">http://lists.openstreetmap.org/listinfo/legal-talk</a><br><br><br> </div> </div> </blockquote></div> </div></body></html>