<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="">Hi Rube, <div class=""><br class=""></div><div class="">That’s exactly what I meant, thanks. Even communication interns are surprised when we tell them to not use copyrighted imagery and to attribute open stuff. They don’t learn that in their (college) universities courses, let alone, figure it our themselves. My guess here is that they just hired a graphic designer to make this flyer and whoever is actually responsible (Cf. VU address) hasn’t even the slightest clue that they were doing something wrong. </div><div class=""><br class=""></div><div class="">Considering how fuzzy the imagery is, this could just be a Mapbox Studio screenshot in high quality with adjusted colours. </div><div class=""><br class=""></div><div class="">Kind regards,</div><div class="">Pieter-Jan</div><div class=""><div class="">
<div class=""><table style="font-family: Times; widows: 1;" class=""><tbody class=""><tr class=""><td valign="middle" style="padding: 0px 8px 0px 0px;" class=""><div style="float: left;" class=""><img width="80" height="80" src="http://be.okblogfarm.org/files/2016/01/emblem-green1.png" style="border-top-left-radius: 50%; border-top-right-radius: 50%; border-bottom-right-radius: 50%; border-bottom-left-radius: 50%;" class=""></div></td><td valign="middle" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(127, 185, 36); padding: 0px 0px 0px 8px;" class=""><div class=""><span display:="" ;"="" style="color: rgb(127, 185, 36); font-size: 11px; font-family: '‘Open Sans’';" class=""><span style="font-family: 'Open Sans';" class="">Community Coordinator</span></span></div><div class=""><span style="font-size: 11px; font-family: 'Open Sans';" class="">Open Knowledge Belgium</span></div><div class=""><span style="font-size: 11px; color: rgb(127, 185, 36); font-family: 'Open Sans';" class="">m:</span> <span style="font-size: 11px; font-family: 'Open Sans';" class="">+32 476 66 27 77</span> <span style="font-size: 11px; color: rgb(127, 185, 36); font-family: 'Open Sans';" class="">a:</span> <span style="font-size: 11px; font-family: 'Open Sans';" class="">Sint-Salvatorstraat 18/101, 9000 Gent</span><div class=""><span style="font-size: 11px; color: rgb(127, 185, 36); font-family: 'Open Sans';" class="">s:</span> <a href="http://www.openknowledge.be/" target="_blank" style="color: rgb(0, 0, 0); text-decoration: none; font-size: 11px; font-family: 'Open Sans';" class="">www.openknowledge.be</a> <span style="font-size: 11px; color: rgb(127, 185, 36); font-family: 'Open Sans';" class="">e:</span> <a href="mailto:pieterjan@openknowledge.be" target="_blank" style="font-size: 11px; color: rgb(0, 0, 0); text-decoration: none; font-family: 'Open Sans';" class="">pieterjan@openknowledge.be</a></div></div></td></tr></tbody></table><div class=""><br class=""></div></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 03 Aug 2016, at 16:06, Ruben Maes <<a href="mailto:ruben@janmaes.com" class="">ruben@janmaes.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Pieter<br class=""><br class="">Thanks for your reply. Replying inline:<br class=""><br class="">On woensdag 3 augustus 2016 15:49 Pieter-Jan Pauwels wrote:<br class=""><blockquote type="cite" class="">“What do you mean we can use Images on Google Images? Then why would they make them available in the first place?”<br class=""></blockquote><br class="">I believe you meant "What do you mean we can*not* use Images on Google Images?"<br class="">Assuming that:<br class=""><br class=""><blockquote type="cite" class="">(...) I have a non-print marketing background and I can tell you nobody knows the anything about licenses in re-using materials (except contributors and legal counselors). I’ve been evangelising open licenses for over 2 years now and I still get the same reaction from high level marketeers to uni students: “What do you mean we cannot use Images on Google Images? Then why would they make them available in the first place?” And that’s just for images, let alone, data or virtual maps.<br class=""></blockquote><br class="">Really? How unprofessional...<br class=""><br class=""><blockquote type="cite" class="">So yes contact them, but don’t start with going in offensive mode by tapping them on the fingers. Awareness and open discussions bring in more souls to the (l)(r)ight side.<br class=""></blockquote><br class="">You're right.<br class="">I kind of assumed that given the scale of this they must be knowing what they do.<br class=""><br class=""><blockquote type="cite" class="">Maybe we should consider more info on <a href="http://osm.be/nl/usage" class="">http://osm.be/nl/usage</a> <<a href="http://osm.be/nl/usage" class="">http://osm.be/nl/usage</a>> about how the license applies when graphically copying or screenshotting the map, because now it’s very data focused, no? <br class=""></blockquote><br class="">It's like they created their own style. That also contributed to me thinking they knew what they were doing. (Or they just used a rendering I haven't seen before.)<br class=""><br class=""><blockquote type="cite" class="">(...)<br class=""><br class=""><blockquote type="cite" class="">On 03 Aug 2016, at 15:30, Ruben Maes <<a href="mailto:ruben@janmaes.com" class="">ruben@janmaes.com</a>> wrote:<br class=""><br class="">I have a feeling that they were actually aware of the attribution requirement, but deliberately didn't do it because it's difficult for us to act on.<br class=""></blockquote></blockquote><br class="">-- <br class="">This message is OpenPGP signed._______________________________________________<br class="">Talk-be mailing list<br class=""><a href="mailto:Talk-be@openstreetmap.org" class="">Talk-be@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/talk-be<br class=""></div></div></blockquote></div><br class=""></div></body></html>