Re: [OSM-talk] Attribution guideline status update

2019-10-30 Thread Nuno Caldeira
And the hypocrisy goes on. "Strava launches gorgeous new outdoor maps" 
https://blog.mapbox.com/strava-launches-gorgeous-new-outdoor-maps-977c74cf37f9


If anyone spots any reference or attribution to OpenStreetMap (well this 
one actually has it 
https://miro.medium.com/max/1395/0*llxj5jTIZqpXBsST.jpg might be a case 
of interpreting ODbL that you only need to attribute once or an 
exception for promo usage that disqualifies attribution being needed or 
probably mixes a lot of different data sources).


Às 18:08 de 09/09/2019, Nuno Caldeira escreveu:


These loopholes are already being exploited, especially from corporate 
members of OSMF Mapbox (they have several articles, medium tutorials 
and such where's no attribution) and Facebook. Which is a shame, as 
they are well aware of the spirit of OSM.






___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-09-13 Thread Nuno Caldeira
Here's another example by Uber. They attribute the tiles visibly, not 
OSM... how can we measure if it's 50% OSM? we can't 
https://movement.uber.com/cities?lang=en-US test in multiple cities 
around the world and compare side by side with OSM. clearly more than 
50%. Not to mention they mix all the attribution no matter which city 
you are viewing.


Às 15:37 de 09/09/2019, Mateusz Konieczny escreveu:


9 Aug 2019, 10:41 by si...@poole.ch:

 consolidate all attribution guidance in to one document

Thanks for work on that!

Unfortunately proposed version contains
major loophole that will be deliberately
exploited by organisation like Facebook
or Maps.me or Mapbox that describe
OSM data as their own.

"If OpenStreetMap data accounts for a minority (less than 50%) part of 
the visible map rendering, attribution with other sources on a 
separate page that is visible after user interaction is acceptable."


In basically any readable map less that 50% of
visible map rendering is using OSM data
or can be trivially modified to do it.

For example - claim that land area is not
from OSM data but default map state
or use alternative data for land boundaries.



Note that claim that this companies* will
use ridiculous loopholes is not prediction,
they are doing it already or simply lying.

Mapbox representative explicitly claimed in
mail to me that hiding attribution behind i
buttons fulfills ODBL requirements.

FB and mapsme ignored multiple reports
about their attribution violation.

*and other, but in this cases I reported their
illegal use of work of OSM mappers and got
ignored.​

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-09-09 Thread Nuno Caldeira
Today i was check the maps on their website and noticed they have a 
report button, which i thought would create a note on OSM. Oh i was 
wrong, no note on OSM, wonder where that report will go to. Also quite 
funny that once you submit you get a message "your feedback help us to 
*_make Facebook maps_* better for everyone"had that ahah moment. 
Example i just done, feel free to try it yourself on the so called 
Facebook Maps https://youtu.be/FF6rOOO51Ig


If anyone can reach them and ask them where that report goes i would 
like to know. I could email them, but they still haven't replied to 
several of my emails.


Another great example of promoting the growth of open data by corporate 
member of OSMF. Great citizens of OSMF.


These loopholes are already being exploited, especially from corporate 
members of OSMF Mapbox (they have several articles, medium tutorials and 
such where's no attribution) and Facebook. Which is a shame, as they are 
well aware of the spirit of OSM.


Oh and by the way, today makes one year i first sent an email to 
Facebook asking to comply. 
https://lists.openstreetmap.org/pipermail/talk/2019-March/082147.html


Also makes 3 months i have asked the board to terminate Facebook rights 
under ODbL (no decision as fair as i know) 
https://lists.openstreetmap.org/pipermail/talk/2019-June/082653.html


Meanwhile, Facebook did attribute on some maps, not on all. Evidence 
gathered in July of no attribution, that i just confirmed still not 
fixed. The most hilarious is their app Local, which uses OSM data but 
there's a reasonable calculated logo of HERE on the left corner of the 
map https://drive.google.com/drive/folders/1B5AF2i0Go5_jQfuoO26d5mfbi0XE-vg_


Às 15:37 de 09/09/2019, Mateusz Konieczny escreveu:

Unfortunately proposed version contains
major loophole that will be deliberately
exploited by organisation like Facebook
or Maps.me or Mapbox that describe
OSM data as their own.

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-09-09 Thread Mateusz Konieczny
9 Aug 2019, 10:41 by si...@poole.ch:

> As we've mentioned multiple times over the last months, the LWG decided
> last year to consolidate all attribution guidance in to one document
>
In general I would explicitly state in
document itself that it is not waiving
any rules from ODBL and is unable to impose any new restrictions.

And that it is merely interpretation of
the ODBL licence in form more readable and useful to a typical person

"It is permissible to use a mechanism to collapse the attribution as long as it 
is initially fully visible"

This is a second major loophole.

Mapsme is already showing attribution 
for second or two after startup (startup is very long, 
so user is extremely unlikely to notice and 
read brief appearance of text).

I have no good idea how to close it.
I would recommend removal of this part.

"If multiple static images appear on the same webpage, one instance of 
attribution is sufficient."

"for the most prominent item, with wording 
clearly covering all static images with 
OSM data" is missing, otherwise you 
would be allowed to add harmless 
attribution to last image that no-one will notice.

--

"In accordance with the Substantial Guideline, static images of areas less 
10’000 m2"

This is extremely surprising to me.
 Where in ODBL licence attribution is 
waived for all small areas? I can find cases 
where so small areas will have 
substantial data that is valuable and represents 
significant work of OSM mappers.

Though given that it is just quoting something 
else it may be a poor moment to change this.
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-09-09 Thread Mateusz Konieczny

9 Aug 2019, 10:41 by si...@poole.ch:

>  consolidate all attribution guidance in to one document 
>
Thanks for work on that!

Unfortunately proposed version contains
major loophole that will be deliberately
exploited by organisation like Facebook
or Maps.me or Mapbox that describe
OSM data as their own.

"If OpenStreetMap data accounts for a minority (less than 50%) part of the 
visible map rendering, attribution with other sources on a separate page that 
is visible after user interaction is acceptable."

In basically any readable map less that 50% of
visible map rendering is using OSM data
or can be trivially modified to do it.

For example - claim that land area is not
from OSM data but default map state
or use alternative data for land boundaries.



Note that claim that this companies* will 
use ridiculous loopholes is not prediction,
they are doing it already or simply lying.

Mapbox representative explicitly claimed in
mail to me that hiding attribution behind ibuttons fulfills ODBL requirements.

FB and mapsme ignored multiple reports
about their attribution violation.

*and other, but in this cases I reported their
illegal use of work of OSM mappers and got
ignored.​
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-15 Thread Simon Poole
Thanks to Christine and the SotM-WG we've been allocated a slot and a
room in Heidelberg see https://2019.stateofthemap.org/sessions/AV9NWC/

Simon

Am 09.08.2019 um 09:41 schrieb Simon Poole:
> As we've mentioned multiple times over the last months, the LWG decided
> last year to consolidate all attribution guidance in to one document and
> address some of the use cases that have become common over the last 7
> years that previously had none. Particularly in the light of the
> parallel discussions about attribution on larger social media platforms
> we need to make up our minds what we actually want, and define concrete
> minimum requirements for acceptable attribution. To not do this just
> provides the excuse of pointing to the cacophony of voices all saying
> something different. 
>
> We've been working on and off on the document for a while, and are now
> largely finished. Going forward we intend to wikify the document and
> make it available for public comment together with a BoF session at SotM
> next month (which probably means that we'll have to appropriate a coffee
> break). You can have a glimpse at the text here
> https://docs.google.com/document/d/1e_IQYHtqVivGRw4O4EOn6__-LGMuzPlWz6XKEdAkwW0/edit?usp=sharing
> the few things that are not nailed down belong to those that we would
> appreciate feedback on.
>
> Simon
>
> PS: the number of coffee breaks permitting we might want to appropriate
> another one for the discussion of a tile licence change.
>
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk


signature.asc
Description: OpenPGP digital signature
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-13 Thread Nuno Caldeira


Às 22:04 de 13/08/2019, Kathleen Lu escreveu:



>
> And to Martin's point, which would you consider more important,
the overlay of rare information, the gas stations, or the basemap?
Or is the overlay only more important than the basemap if the
overlay comes from OSM?


In a basemap/overlay data constellation, I would generally
consider the overlay more important (it’s the reason the map was
published), but of course this doesn’t mean you would not have to
attribute the basemap as well, if it were a requirement of the map.


As far as I know, no one is talking about no attribution at all, but 
rather attribution after a click


You mean the reasonable calculated Mapbox and VOST logo on the left 
corner of the map and the "i" with permanent mouse hover to be displayed?


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-13 Thread Martin Koppenhoefer


sent from a phone

> On 13. Aug 2019, at 23:04, Kathleen Lu  wrote:
> 
> As far as I know, no one is talking about no attribution at all, but rather 
> attribution after a click


in some cases we are talking about several clicks, but what I meant was that it 
could well happen that you’d have to attribute both, basemap and overlay data, 
directly on the map (not hidden and visible only after clicking).
I have seen this quite often and it makes perfect sense.

Cheers Martin 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-13 Thread Kathleen Lu via talk
>
> > And to Martin's point, which would you consider more important, the
> overlay of rare information, the gas stations, or the basemap? Or is the
> overlay only more important than the basemap if the overlay comes from OSM?
>
>
> In a basemap/overlay data constellation, I would generally consider the
> overlay more important (it’s the reason the map was published), but of
> course this doesn’t mean you would not have to attribute the basemap as
> well, if it were a requirement of the map.
>

As far as I know, no one is talking about no attribution at all, but rather
attribution after a click
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-13 Thread Martin Koppenhoefer


sent from a phone

> On 13. Aug 2019, at 20:19, Kathleen Lu  wrote:
> 
> And to Martin's point, which would you consider more important, the overlay 
> of rare information, the gas stations, or the basemap? Or is the overlay only 
> more important than the basemap if the overlay comes from OSM?


In a basemap/overlay data constellation, I would generally consider the overlay 
more important (it’s the reason the map was published), but of course this 
doesn’t mean you would not have to attribute the basemap as well, if it were a 
requirement of the map.


Cheers Martin 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-13 Thread Nuno Caldeira
https://janaodaparaabastecer.vost.pt/ is a very interesting example. 
On my screen, the attribution clearly stretches longer than the width 
of the map.


It's funny that you mention that, i contacted them, they weren't even 
aware they were using OpenStreetMap. They even said their data was "open 
data", when in reality comes from Waze But hey they use 
OpenStreetMap tiles via Mapbox with a bit of shy attribution.


And seems Mapbox doesn't know how to set a proper hyperlink on that page 
it heads to https://www.openstreetmap.org/about/ instead of 
https://www.openstreetmap.org/copyright


But what's the arm? Mapbox logo, Waze and everything else comes first 
and get proper exposure like it should.



Is your opinion then that they should attribute similar to your 
European Commission example of "correct" attribution 
https://ec.europa.eu/transport/infrastructure/tentec/tentec-portal/map/maps.html, 
where some of the attribution is visible immediately, and the rest 
after clicking?


I see OpenStreetMap being attributed 100% of the time. Maybe they should 
just hide like our Corporate Member of OSMF.Or not even attribute at 
all, like the ones i shared yesterday.



And to Martin's point, which would you consider more important, the 
overlay of rare information, the gas stations, or the basemap? Or is 
the overlay only more important than the basemap if the overlay comes 
from OSM?
As i pointed out they didn't knew it was OSM. About the importance, let 
me remind you of Facebook reply telling me "static maps not being 
informative". Sure, if they are not just don't use them at all, a blank 
tile will look much better, feel free to use it instead.Attribution is 
really such a hard task to fulfill.


If you browse the portuguese press about VOST map, you will notice 
endless references to Waze. You know how many to OpenStreetMap? Less 
than onezero. Another lovely opportunity loss to advocate for 
OpenStreetMap and open data.


Examples:

https://sicnoticias.pt/especiais/crise-energetica/2019-08-12-Vost-Portugal-disponibiliza-online-os-postos-onde-ainda-ha-combustivel
https://www.dn.pt/pais/interior/mapa-online-mostra-que-bombas-ficam-sem-combustivel-veja-aqui-11189237.html
https://4gnews.pt/waze-diz-te-quais-as-bombas-de-gasolina-onde-abastecer-nesta-greve-dos-motoristas/








On Sat, Aug 10, 2019 at 10:33 AM Nuno Caldeira 
mailto:nunocapelocalde...@gmail.com>> 
wrote:


Hi Martin,


For another perspective, imagine someone making a world map with
85% OpenStreetMap data and 15% XY inc. data, if someone looks on
a part of this map which is fed by these 15% XY data, you would
not want to have it incorrectly attributed to OpenStreetMap
(although we are generally the principal data provider).

Well, the example i gave previously
https://janaodaparaabastecer.vost.pt/ is a good example of what
you are saying. What do you do to fix it? Mapbox will say nothing
or "believe this is the common, VOST won't say anything. Meanwhile
99.9% of that map is OSM a the gas station status update is
provided by Waze. Sounds fair doesn't it?



I believe the 50% rule is ok, if it refers to the displayed
objects on the screen (although this can also be arbitrary, since
you can always split a way, or interpolate nodes to get more of
them).
Imagine a map which chooses a different data provider per
country. For zoomed in maps (you only see data from one provider)
you would want this one provider prominently attributed. If you
attribute to someone else more prominently and show the actual
data provider only in „others“, you will inevitably create a
wrong impression about the source, and if it’s us who miss out on
visible attribution, we should care.


Good that you mention this. On my email from 10th of October 2018
to facebook and Mapbox (both stopped replying), i pointed out
these examples which have zero issues about having multiple
sources being attributed visibly and not hiding them:


Microsoft - Uses HERE and OSM and attributes both visibly on the
footer

https://www.bing.com/maps/?v=2=48.187141%2C%2016.349561=48.187141%2C16.349561=48.18694871145921~16.349901334904583=18=1



ARCGIS Web - Uses OSM and ESRI data, credits both

https://www.arcgis.com/home/webmap/viewer.html?webmap=fae788aa91e54244b161b59725dcbb2a

European Commission  - credits OSM and other sources

http://ec.europa.eu/transport/infrastructure/tentec/tentec-portal/map/maps.html
and

http://emergency.copernicus.eu/mapping/copernicus-emergency-management-service#zoom=2=23.42974=16.28085=00B0T


Sadly, some say this is hard to implement. The above sites, must
have a hell of a research UX dept to make it possible and others
just say it's hard. Google does the same on "dynamic 

Re: [OSM-talk] Attribution guideline status update

2019-08-13 Thread Kathleen Lu via talk
 https://janaodaparaabastecer.vost.pt/ is a very interesting example. On my
screen, the attribution clearly stretches longer than the width of the map.
Is your opinion then that they should attribute similar to your European
Commission example of "correct" attribution
https://ec.europa.eu/transport/infrastructure/tentec/tentec-portal/map/maps.html,
where some of the attribution is visible immediately, and the rest after
clicking?

And to Martin's point, which would you consider more important, the overlay
of rare information, the gas stations, or the basemap? Or is the overlay
only more important than the basemap if the overlay comes from OSM?

On Sat, Aug 10, 2019 at 10:33 AM Nuno Caldeira 
wrote:

> Hi Martin,
>
> For another perspective, imagine someone making a world map with 85%
> OpenStreetMap data and 15% XY inc. data, if someone looks on a part of this
> map which is fed by these 15% XY data, you would not want to have it
> incorrectly attributed to OpenStreetMap (although we are generally the
> principal data provider).
>
> Well, the example i gave previously https://janaodaparaabastecer.vost.pt/
> is a good example of what you are saying. What do you do to fix it? Mapbox
> will say nothing or "believe this is the common, VOST won't say anything.
> Meanwhile 99.9% of that map is OSM a the gas station status update is
> provided by Waze. Sounds fair doesn't it?
>
>
> I believe the 50% rule is ok, if it refers to the displayed objects on the
> screen (although this can also be arbitrary, since you can always split a
> way, or interpolate nodes to get more of them).
> Imagine a map which chooses a different data provider per country. For
> zoomed in maps (you only see data from one provider) you would want this
> one provider prominently attributed. If you attribute to someone else more
> prominently and show the actual data provider only in „others“, you will
> inevitably create a wrong impression about the source, and if it’s us who
> miss out on visible attribution, we should care.
>
> Good that you mention this. On my email from 10th of October 2018 to
> facebook and Mapbox (both stopped replying), i pointed out these examples
> which have zero issues about having multiple sources being attributed
> visibly and not hiding them:
>
> Microsoft - Uses HERE and OSM and attributes both visibly on the footer
> https://www.bing.com/maps/?v=2=48.187141%2C%2016.349561=48.187141%2C16.349561=48.18694871145921~16.349901334904583=18=1
> 
>
> ARCGIS Web - Uses OSM and ESRI data, credits both
> https://www.arcgis.com/home/webmap/viewer.html?webmap=fae788aa91e54244b161b59725dcbb2a
>
> European Commission  - credits OSM and other sources
> http://ec.europa.eu/transport/infrastructure/tentec/tentec-portal/map/maps.html
> and
> http://emergency.copernicus.eu/mapping/copernicus-emergency-management-service#zoom=2=23.42974=16.28085=00B0T
>
> Sadly, some say this is hard to implement. The above sites, must have a
> hell of a research UX dept to make it possible and others just say it's
> hard. Google does the same on "dynamic attribution". It's not rocket
> science, especially when it's for desktop use, there's plenty of space to
> attribute visibly. It's just excuses.
>
>
> What about maps that display an overlay over a basemap? This would lead to
> the overlay data provider mostly being pushed in the second row because it
> is quantitatively less, but the overlay data might be the rare unique data
> that is interesting. In case someone displayed an OpenStreetMap based
> overlay over a different background, why would we deliberately renounce
> from attribution in these cases?
>
> We shouldn't as it would violate the license.
>
>
> It is crucial that the 50% relate to the actually visible map features,
> and not to the total map. If the latter was possible, you could just fill
> your db with random crap in the middle of the ocean and distort the
> proportion.
>
> Obviously, we know those dirty tricks. Fatmap is a perfect example of that
> https://fatmap.com/adventures/@38.6755407,-9.1596113,3096.1899062,-40.2439178,19.7162561,31.6575309,normal
> and there's is plenty of room to add the attribution visibly.
>
>
> To be honest i'm kinda fed up of all of this, nothing happens. And it's a
> shame stating "the license doesn't say this or that", it neither says you
> must attribute with the exact text “© OpenStreetMap contributors”, must
> be unreasonable calculated to acknowledge. Common sense and fairness is all
> needed, not crappy legal interpretations and placing fear for legal actions
> from corporate interests. Sadly i'm starting to believe the concerns that
> some have shared on the list that OSMF is being "controlled" by corporate
> interests and not by the spirit that it was created.
>
>
___
talk mailing list
talk@openstreetmap.org

Re: [OSM-talk] Attribution guideline status update

2019-08-12 Thread Nuno Caldeira

Another lovely example from our OSMF Corporate Member.

https://blog.mapbox.com/designing-the-treasure-map-style-4318390ad81c

Also feel free to check every hyperlink on that page. If you find any 
attribution, let me know. Might be the case that it's not 50% OSM... 
Even on the guide that contradicts their attribution 
 of using 
Mapbox


The /text attribution/ contains at least three links: |© Mapbox| 
, |© OpenStreetMap| 
 and |Improve this map| 
. This attribution 
is strictly /required/ when using the Mapbox Streets tileset due to 
OpenStreetMap's data source ODbL 
 license.


Streets that quote "Mapbox Streetsvector tiles are largely based on data 
from OpenStreetMap (OSM), an open source resource of volunteer 
maintained geographic data. " 
https://www.mapbox.com/resources/guide-to-map-design-part-1a.pdf search 
"OpenStreetMap" and be amazed.


Seems none takes OSMF seriously any more, not even the corporate members 
and the writing of this guidance was a waste of time and effort. Let's 
stop the hypocrisy and switch license to something else, at least 
contributors won't be illuded with this "Both licenses /_are “By 
Attribution_/” and “Share Alike”. " 
https://wiki.osmfoundation.org/wiki/Licence/Historic/We_Are_Changing_The_License#What_are_the_main_differences_between_the_old_and_the_new_license.3F



Às 11:58 de 10/08/2019, Andrew Harvey escreveu:
On Sat, 10 Aug 2019 at 17:27, Joseph Eisenberg 
mailto:joseph.eisenb...@gmail.com>> wrote:


It's even hard to recommend apps like Maps.me when they don't
attribute Openstreetmap, instead putting their own logo in the lower
right corner.

If people don't know that OSM is the source of the data in a map, they
won't know how to get involved to improve it.


They do provide the attribution, tt's under Settings | About (then 
again under Settings | About | Copyright).


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Nuno Caldeira

Hi Martin,

For another perspective, imagine someone making a world map with 85% 
OpenStreetMap data and 15% XY inc. data, if someone looks on a part of 
this map which is fed by these 15% XY data, you would not want to have 
it incorrectly attributed to OpenStreetMap (although we are generally 
the principal data provider).
Well, the example i gave previously 
https://janaodaparaabastecer.vost.pt/ is a good example of what you are 
saying. What do you do to fix it? Mapbox will say nothing or "believe 
this is the common, VOST won't say anything. Meanwhile 99.9% of that map 
is OSM a the gas station status update is provided by Waze. Sounds fair 
doesn't it?



I believe the 50% rule is ok, if it refers to the displayed objects on 
the screen (although this can also be arbitrary, since you can always 
split a way, or interpolate nodes to get more of them).
Imagine a map which chooses a different data provider per country. For 
zoomed in maps (you only see data from one provider) you would want 
this one provider prominently attributed. If you attribute to someone 
else more prominently and show the actual data provider only in 
„others“, you will inevitably create a wrong impression about the 
source, and if it’s us who miss out on visible attribution, we should 
care.


Good that you mention this. On my email from 10th of October 2018 to 
facebook and Mapbox (both stopped replying), i pointed out these 
examples which have zero issues about having multiple sources being 
attributed visibly and not hiding them:


Microsoft - Uses HERE and OSM and attributes both visibly on the 
footer 
https://www.bing.com/maps/?v=2=48.187141%2C%2016.349561=48.187141%2C16.349561=48.18694871145921~16.349901334904583=18=1 



ARCGIS Web - Uses OSM and ESRI data, credits both 
https://www.arcgis.com/home/webmap/viewer.html?webmap=fae788aa91e54244b161b59725dcbb2a


European Commission  - credits OSM and other sources 
http://ec.europa.eu/transport/infrastructure/tentec/tentec-portal/map/maps.html 
and 
http://emergency.copernicus.eu/mapping/copernicus-emergency-management-service#zoom=2=23.42974=16.28085=00B0T


Sadly, some say this is hard to implement. The above sites, must have a 
hell of a research UX dept to make it possible and others just say it's 
hard. Google does the same on "dynamic attribution". It's not rocket 
science, especially when it's for desktop use, there's plenty of space 
to attribute visibly. It's just excuses.



What about maps that display an overlay over a basemap? This would 
lead to the overlay data provider mostly being pushed in the second 
row because it is quantitatively less, but the overlay data might be 
the rare unique data that is interesting. In case someone displayed an 
OpenStreetMap based overlay over a different background, why would we 
deliberately renounce from attribution in these cases?



We shouldn't as it would violate the license.


It is crucial that the 50% relate to the actually visible map 
features, and not to the total map. If the latter was possible, you 
could just fill your db with random crap in the middle of the ocean 
and distort the proportion.
Obviously, we know those dirty tricks. Fatmap is a perfect example of 
that 
https://fatmap.com/adventures/@38.6755407,-9.1596113,3096.1899062,-40.2439178,19.7162561,31.6575309,normal 
and there's is plenty of room to add the attribution visibly.



To be honest i'm kinda fed up of all of this, nothing happens. And it's 
a shame stating "the license doesn't say this or that", it neither says 
you must attribute with the exact text “© OpenStreetMap contributors”, 
must be unreasonable calculated to acknowledge. Common sense and 
fairness is all needed, not crappy legal interpretations and placing 
fear for legal actions from corporate interests. Sadly i'm starting to 
believe the concerns that some have shared on the list that OSMF is 
being "controlled" by corporate interests and not by the spirit that it 
was created.



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Martin Koppenhoefer


sent from a phone

On 10. Aug 2019, at 11:27, Nuno Caldeira  wrote:

>> can't they use more than one data source?
>> Yes, i do agree. Sounds like a good argument to remove the 50% of the 
>> guideline.
>> 
> Yes, i do agree. Sounds like a good argument to remove the 50% of the 
> guideline.
> 



I believe the 50% rule is ok, if it refers to the displayed objects on the 
screen (although this can also be arbitrary, since you can always split a way, 
or interpolate nodes to get more of them).
Imagine a map which chooses a different data provider per country. For zoomed 
in maps (you only see data from one provider) you would want this one provider 
prominently attributed. If you attribute to someone else more prominently and 
show the actual data provider only in „others“, you will inevitably create a 
wrong impression about the source, and if it’s us who miss out on visible 
attribution, we should care.

For another perspective, imagine someone making a world map with 85% 
OpenStreetMap data and 15% XY inc. data, if someone looks on a part of this map 
which is fed by these 15% XY data, you would not want to have it incorrectly 
attributed to OpenStreetMap (although we are generally the principal data 
provider).

It is crucial that the 50% relate to the actually visible map features, and not 
to the total map. If the latter was possible, you could just fill your db with 
random crap in the middle of the ocean and distort the proportion.

What about maps that display an overlay over a basemap? This would lead to the 
overlay data provider mostly being pushed in the second row because it is 
quantitatively less, but the overlay data might be the rare unique data that is 
interesting. In case someone displayed an OpenStreetMap based overlay over a 
different background, why would we deliberately renounce from attribution in 
these cases?


Cheers Martin ___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Nuno Caldeira

Oh right that sounds fair...not.

Same applies to this https://janaodaparaabastecer.vost.pt/ theres Mapbox 
logo, there's VOST logo, then under  "i" crap load of sources...oh yeh 
that's OSM for sure, i know my edits well. clearly the 50% rule needs to 
be removed from the guidance as users are using already in a misleading 
way. And again another Mapbox tied map.



Às 11:58 de 10/08/2019, Andrew Harvey escreveu:
On Sat, 10 Aug 2019 at 17:27, Joseph Eisenberg 
mailto:joseph.eisenb...@gmail.com>> wrote:


It's even hard to recommend apps like Maps.me when they don't
attribute Openstreetmap, instead putting their own logo in the lower
right corner.

If people don't know that OSM is the source of the data in a map, they
won't know how to get involved to improve it.


They do provide the attribution, tt's under Settings | About (then 
again under Settings | About | Copyright).


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Andrew Harvey
On Sat, 10 Aug 2019 at 17:27, Joseph Eisenberg 
wrote:

> It's even hard to recommend apps like Maps.me when they don't
> attribute Openstreetmap, instead putting their own logo in the lower
> right corner.
>
> If people don't know that OSM is the source of the data in a map, they
> won't know how to get involved to improve it.
>

They do provide the attribution, tt's under Settings | About (then again
under Settings | About | Copyright).
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Tobias Knerr
On 09.08.19 16:35, Frederik Ramm wrote:
> I wonder if we could perhaps get rid of the "Contributors" mention
> altogether.

This idea makes a lot of sense. Especially as both the guideline draft
and the current FAQ already allow this "if space is limited":

> Because OpenStreetMap is its contributors, you may omit the word
> "contributors" if space is limited

So aside from making it much less awkward to attribute OSM in
non-English or multilingual contexts, this change would also simplify
the rules a bit and remove one source of ambiguity. I like it!

Tobias



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Nuno Caldeira


So maybe it is an unauthorized use of Mapbox. Anyone can sign up free. 
You should report it to Mapbox.


Nah, they stop replying me, they must have me on blacklist. Which goes a 
bit against their values "*Be respectful and humble.* To everyone — 
always." https://www.mapbox.com/about/values/


Speaking of them, seems their interpretation of ODbL is the same as mine:

The /text attribution/ contains at least three links: |© Mapbox| 
, |© OpenStreetMap| 
 and |Improve this map| 
. This 
_*attribution is strictly *__*/required/*_ when using the Mapbox 
Streets tileset due to OpenStreetMap's data source ODbL 
 license.


https://docs.mapbox.com/help/how-mapbox-works/attribution/



About DJI, i presume you know they stopped using Altitude Angel
(the company that omitted the attribution and runs
https://dronesafetymap.com/) and are now using Mapbox instead as
you can see here https://www.dji.com/pt/flysafe/geo-map Mapbox
owns me a cup of tea for another client, oh well i can refuse that
cup of tea for adding the attribution proudly and not behind "i"
or even omitting. Sometimes i think they are ashamed of using OSM
data instead of proudly showing it. It's not about the data, it's
what you do with it that matters and Mapbox does it well, but
hiding the source is dirty.

How do you know that they stopped using Altitude Angel? I can see from 
the map that they use Mapbox now, but can't they use more than one 
data source?


Yes, i do agree. Sounds like a good argument to remove the 50% of the 
guideline.



That might be your opinion, but I think a court would disagree. Courts 
often look at norms in order to interpret a licence.


This is the issue and feels like we are being abuse and pressured with 
the court/judge motive. When we shouldn't even go there but doing what's 
common sense. Maybe we should just switch to a public domain license, 
because that's what seems we have.



 The objects don't say anything about strict attribution requirements. 
In fact, requirements that are too strict will *discourage* the 
"distribution of free geospatial data" by making it too difficult to 
use. That's the opposite of "providing geospatial data for anybody to 
use and share."


Sure, i have send those concerns to the board. I don't see any 
difficulty to use it, you just need to attribute.



Great, so now you are saying that OSM has been doing it wrong since 
the beginning?


Well apparently we were tricked when we switched from CC to ODbL, 
judging by your opinion, we don't need this guidance or the copyright at 
all, with the argument of license doesn't say so.



"You must keep intact" means don't delete them, not, "can't be a 
link". That last clause is "to the extent reasonably practicable, the 
Uniform Resource Identifier, if any, that Licensor specifies to be 
associated with the Work." In other words, include a link if the 
Licensor wants you to include a link! No one has suggested that the 
attribution should be only (c) OpenStreetMap with no link back to 
https://www.openstreetmap.org/copyright


So we are living in a lie since the beginning and dont need the 
attribution page at all. Please Board explain.



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Richard Fairhurst
Kathleen Lu wrote:
> "reasonably calculated" means "reasonable." What does reasonable mean? 
> Well a court would look at what other people in the industry do. Do others 
> in the industry list attribution, especially to multiple data sources,
> after 
> a click (or many clicks)? Yes, all the time.

It would be interesting to get some data behind this.

OSM's position when the current attribution text was drawn up in 2012 has
been exactly that: "reasonably calculated" means "what people would expect
for other data providers".

There are only three other geodata providers with a similar product to OSM,
i.e. a worldwide street-level database used for display maps: Google,
TomTom, and Here. In 2012 all three generally required direct on-map
attribution and my impression is that this is still the case, but real data
about current usage and practices would be great.

> A court would also look at what OSM does. Does OSM list its data sources
> after a link? Yes, sometimes two links (first to
> https://www.openstreetmap.org/copyright, then to
> https://wiki.openstreetmap.org/wiki/Contributors). Some of this data is
> also under ODbL! Why is this not reasonable?

OSM expressly states that our "after a link" behaviour is not compliant with
licences such as ODbL and the CC-BY family. Instead, we need to get an
attribution waiver before using any data licensed under such terms. As per
https://wiki.osmfoundation.org/wiki/Licence/Licence_Compatibility :

"Many sources simply require attribution of the source as a condition of
use, however as we cannot provide attribution on works created or derived
from OpenStreetMap data and our licence only requires attribution of the
overall data source, permission for attribution via our central
'Contributors' pages needs to be obtained and documented."

cheers
Richard



--
Sent from: http://gis.19327.n8.nabble.com/General-Discussion-f5171242.html

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-10 Thread Joseph Eisenberg
I'm just an individual mapper who would like more people to be aware
of Openstreetmap. I'm not a professional cartographer, nor do I have
any ties to any map providers.

My concern right now is that most of my friends and family are
completely unaware of the existence of Openstreetmap, even though our
data is powering many of the maps on their cell phones and many
website.

It's even hard to recommend apps like Maps.me when they don't
attribute Openstreetmap, instead putting their own logo in the lower
right corner.

If people don't know that OSM is the source of the data in a map, they
won't know how to get involved to improve it.

However the license wording is changed, the OSMF needs to convince
Mapbox and company to start actually attributing Openstreetmap in all
views, especially on mobile apps and platforms that the majority of
users see.

There shouldn't be exceptions which hide the Openstreetmap name.

This isn't a matter of pride, it's a matter of whether Openstreetmap
will grow and be recognized as an important source of geodata which
people ought to get involved in improving.

Joseph Eisenberg
Wamena, Indonesia

On 8/10/19, Kathleen Lu via talk  wrote:
> On Fri, Aug 9, 2019 at 3:27 PM Nuno Caldeira 
> wrote:
>
>> Your complaint about LiveStream is that their attribution is completely
>> missing, not that it's behind a click. I agree that it's missing and that
>> it should be somewhere. It's not clear at all where they are getting
>> their
>> data (the rendering looks like Leaflet). If they are looking into it,
>> then
>> why not believe they are looking into it? They will probably fix it after
>> they figure it out. DJI fixed it after investigating, and it took them a
>> while to investigate as well.
>>
>> By inspecting their code from the link i shared you get. src=
>> "https://b.tiles.mapbox.com/v3/livestreamllc.i64m05c3/16/18179/27868.png;
>> 
>> unless they are using Mapbox without their attribution which i presume
>> would be unauthorized use of Mapboxeither that or are premium clients
>> (i did asked them that, they didn't reply obviously). None the less I
>> gave
>> up on asking Mapbox to make sure their clients comply with our license
>> and
>> their terms of service, as they ignore it. Which is a shame coming from a
>> OSMF corporate member. Anyway i have asked, several times, even public,
>> another OSMF corporate member to do the same, still displaying HERE logo
>> on
>> our data. Probably they take HERE seriously (legal) and not OSMF or OSM
>> contributors.
>>
>> So maybe it is an unauthorized use of Mapbox. Anyone can sign up free.
>> You
> should report it to Mapbox.
>
>
>> About DJI, i presume you know they stopped using Altitude Angel (the
>> company that omitted the attribution and runs
>> https://dronesafetymap.com/)
>> and are now using Mapbox instead as you can see here
>> https://www.dji.com/pt/flysafe/geo-map Mapbox owns me a cup of tea for
>> another client, oh well i can refuse that cup of tea for adding the
>> attribution proudly and not behind "i" or even omitting. Sometimes i
>> think
>> they are ashamed of using OSM data instead of proudly showing it. It's
>> not
>> about the data, it's what you do with it that matters and Mapbox does it
>> well, but hiding the source is dirty.
>>
> How do you know that they stopped using Altitude Angel? I can see from the
> map that they use Mapbox now, but can't they use more than one data source?
>
>>
>> "reasonably calculated" means "reasonable." What does reasonable mean?
>> Well a court would look at what other people in the industry do. Do
>> others
>> in the industry list attribution, especially to multiple data sources,
>> after a click (or many clicks)? Yes, all the time.
>>
>> Discussing the reasonable definition is nonsense. Also comparing us to
>> the
>> others in the industry is not reasonable as we do not accept money for
>> providing data or removing attribution.
>>
> That might be your opinion, but I think a court would disagree. Courts
> often look at norms in order to interpret a licence.
>
>
>> Why not 100 click attribution? well that wasn't, isn't and never will be
>> the spirit of open data. Unless OSMF is going against it's owns Objects
>> of
>> the foundation articles:
>>
>> OBJECTS
>>
>> 3. The Foundation is established for the purposes listed below:
>> (1) encouraging the growth, development and distribution of free
>> geospatial data; and (2) providing geospatial data for anybody to use and
>> share.
>>
>>  The objects don't say anything about strict attribution requirements. In
> fact, requirements that are too strict will *discourage* the "distribution
> of free geospatial data" by making it too difficult to use. That's the
> opposite of "providing geospatial data for anybody to use and share."
>
>
>> A court would also look at what OSM does. Does OSM list its data sources
>> after a link? Yes, sometimes two links (first to
>> 

Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Kathleen Lu via talk
On Fri, Aug 9, 2019 at 3:27 PM Nuno Caldeira 
wrote:

> Your complaint about LiveStream is that their attribution is completely
> missing, not that it's behind a click. I agree that it's missing and that
> it should be somewhere. It's not clear at all where they are getting their
> data (the rendering looks like Leaflet). If they are looking into it, then
> why not believe they are looking into it? They will probably fix it after
> they figure it out. DJI fixed it after investigating, and it took them a
> while to investigate as well.
>
> By inspecting their code from the link i shared you get. src=
> "https://b.tiles.mapbox.com/v3/livestreamllc.i64m05c3/16/18179/27868.png;
> 
> unless they are using Mapbox without their attribution which i presume
> would be unauthorized use of Mapboxeither that or are premium clients
> (i did asked them that, they didn't reply obviously). None the less I gave
> up on asking Mapbox to make sure their clients comply with our license and
> their terms of service, as they ignore it. Which is a shame coming from a
> OSMF corporate member. Anyway i have asked, several times, even public,
> another OSMF corporate member to do the same, still displaying HERE logo on
> our data. Probably they take HERE seriously (legal) and not OSMF or OSM
> contributors.
>
> So maybe it is an unauthorized use of Mapbox. Anyone can sign up free. You
should report it to Mapbox.


> About DJI, i presume you know they stopped using Altitude Angel (the
> company that omitted the attribution and runs https://dronesafetymap.com/)
> and are now using Mapbox instead as you can see here
> https://www.dji.com/pt/flysafe/geo-map Mapbox owns me a cup of tea for
> another client, oh well i can refuse that cup of tea for adding the
> attribution proudly and not behind "i" or even omitting. Sometimes i think
> they are ashamed of using OSM data instead of proudly showing it. It's not
> about the data, it's what you do with it that matters and Mapbox does it
> well, but hiding the source is dirty.
>
How do you know that they stopped using Altitude Angel? I can see from the
map that they use Mapbox now, but can't they use more than one data source?

>
> "reasonably calculated" means "reasonable." What does reasonable mean?
> Well a court would look at what other people in the industry do. Do others
> in the industry list attribution, especially to multiple data sources,
> after a click (or many clicks)? Yes, all the time.
>
> Discussing the reasonable definition is nonsense. Also comparing us to the
> others in the industry is not reasonable as we do not accept money for
> providing data or removing attribution.
>
That might be your opinion, but I think a court would disagree. Courts
often look at norms in order to interpret a licence.


> Why not 100 click attribution? well that wasn't, isn't and never will be
> the spirit of open data. Unless OSMF is going against it's owns Objects of
> the foundation articles:
>
> OBJECTS
>
> 3. The Foundation is established for the purposes listed below:
> (1) encouraging the growth, development and distribution of free
> geospatial data; and (2) providing geospatial data for anybody to use and
> share.
>
>  The objects don't say anything about strict attribution requirements. In
fact, requirements that are too strict will *discourage* the "distribution
of free geospatial data" by making it too difficult to use. That's the
opposite of "providing geospatial data for anybody to use and share."


> A court would also look at what OSM does. Does OSM list its data sources
> after a link? Yes, sometimes two links (first to
> https://www.openstreetmap.org/copyright, then to
> https://wiki.openstreetmap.org/wiki/Contributors). Some of this data is
> also under ODbL! Why is this not reasonable?
>
> Thanks for the suggestion, maybe we should fix it and give the example of
> one click only, just to avoid unreasonable interpretations. Anyway it's
> this kind of misleading interpretation of adding a simply “© OpenStreetMap
> contributors” to the data they are using, like it was some kind of secret
> (probably is for none OSMers and general public) that places OSMF projet at
> risk as it clearly does not encourage anything.
>
Great, so now you are saying that OSM has been doing it wrong since the
beginning?


> And you are pointing to the wrong version of CC-BY, btw, 4.0 came out long
> after the license change, but since "reasonable" is the standard, Creative
> Commons itself gives as an example of "best practices" attribution for
> multiple sources this page: https://learn.saylor.org/course/view.php?id=28
> Click on "Course Terms of Use" to see a list of attributions.
>
> well 4 c) says of CC-BY-SA 2.0 says:
>
> If you distribute, publicly display, publicly perform, or publicly
> digitally perform the Work or any Derivative Works or Collective Works, *You
> must keep intact all copyright notices* for the Work 

Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Nuno Caldeira
Your complaint about LiveStream is that their attribution is 
completely missing, not that it's behind a click. I agree that it's 
missing and that it should be somewhere. It's not clear at all where 
they are getting their data (the rendering looks like Leaflet). If 
they are looking into it, then why not believe they are looking into 
it? They will probably fix it after they figure it out. DJI fixed it 
after investigating, and it took them a while to investigate as well.


By inspecting their code from the link i shared you get. 
src="https://b.tiles.mapbox.com/v3/livestreamllc.i64m05c3/16/18179/27868.png; 
unless they are using Mapbox without their attribution which i presume 
would be unauthorized use of Mapboxeither that or are premium 
clients (i did asked them that, they didn't reply obviously). None the 
less I gave up on asking Mapbox to make sure their clients comply with 
our license and their terms of service, as they ignore it. Which is a 
shame coming from a OSMF corporate member. Anyway i have asked, several 
times, even public, another OSMF corporate member to do the same, still 
displaying HERE logo on our data. Probably they take HERE seriously 
(legal) and not OSMF or OSM contributors.


About DJI, i presume you know they stopped using Altitude Angel (the 
company that omitted the attribution and runs 
https://dronesafetymap.com/) and are now using Mapbox instead as you can 
see here https://www.dji.com/pt/flysafe/geo-map Mapbox owns me a cup of 
tea for another client, oh well i can refuse that cup of tea for adding 
the attribution proudly and not behind "i" or even omitting. Sometimes i 
think they are ashamed of using OSM data instead of proudly showing it. 
It's not about the data, it's what you do with it that matters and 
Mapbox does it well, but hiding the source is dirty.



"reasonably calculated" means "reasonable." What does reasonable mean? 
Well a court would look at what other people in the industry do. Do 
others in the industry list attribution, especially to multiple data 
sources, after a click (or many clicks)? Yes, all the time.


Discussing the reasonable definition is nonsense. Also comparing us to 
the others in the industry is not reasonable as we do not accept money 
for providing data or removing attribution.


Why not 100 click attribution? well that wasn't, isn't and never will be 
the spirit of open data. Unless OSMF is going against it's owns Objects 
of the foundation articles:




OBJECTS

3. The Foundation is established for the purposes listed below:

(1) encouraging the growth, development and distribution of free
geospatial data; and
(2) providing geospatial data for anybody to use and share.



A court would also look at what OSM does. Does OSM list its data 
sources after a link? Yes, sometimes two links (first to 
https://www.openstreetmap.org/copyright, then to 
https://wiki.openstreetmap.org/wiki/Contributors). Some of this data 
is also under ODbL! Why is this not reasonable?


Thanks for the suggestion, maybe we should fix it and give the example 
of one click only, just to avoid unreasonable interpretations. Anyway 
it's this kind of misleading interpretation of adding a simply “© 
OpenStreetMap contributors” to the data they are using, like it was some 
kind of secret (probably is for none OSMers and general public) that 
places OSMF projet at risk as it clearly does not encourage anything.





And you are pointing to the wrong version of CC-BY, btw, 4.0 came out 
long after the license change, but since "reasonable" is the standard, 
Creative Commons itself gives as an example of "best practices" 
attribution for multiple sources this page: 
https://learn.saylor.org/course/view.php?id=28 Click on "Course Terms 
of Use" to see a list of attributions.


well 4 c) says of CC-BY-SA 2.0 says:

If you distribute, publicly display, publicly perform, or publicly 
digitally perform the Work or any Derivative Works or Collective 
Works, _*You must keep intact all copyright notices*_ for the Work and 
give the Original Author credit reasonable to the medium or means You 
are utilizing by conveying the name (or pseudonym if applicable) of 
the Original Author if supplied; the title of the Work if supplied; to 
the extent reasonably practicable, the Uniform Resource Identifier, if 
any, _*that Licensor specifies to be associated with the Work*_


https://creativecommons.org/licenses/by-sa/2.0/legalcode

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Kathleen Lu wrote:
>
> "reasonably calculated" means "reasonable." [...]

I am sorry but this is completely distorting the ODbL.

"reasonably calculated to make any Person that uses, ... aware" means 
that the calculation on what effect the specific form of attribution 
chosen is going to have on the awareness of the person about the data 
used needs to be performed in a reasonable fashion.

If the attribution required to accomplish that is reasonable from the 
perspective of the wannabe data user for their desired use case or if 
it is comparable to possible attribution requirements of other geodata 
sources produced by people who are paid for their work has zero effect 
on the fulfilment of the requirements of the license.

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Kathleen Lu via talk
Your complaint about LiveStream is that their attribution is completely
missing, not that it's behind a click. I agree that it's missing and that
it should be somewhere. It's not clear at all where they are getting their
data (the rendering looks like Leaflet). If they are looking into it, then
why not believe they are looking into it? They will probably fix it after
they figure it out. DJI fixed it after investigating, and it took them a
while to investigate as well.

"reasonably calculated" means "reasonable." What does reasonable mean? Well
a court would look at what other people in the industry do. Do others in
the industry list attribution, especially to multiple data sources, after a
click (or many clicks)? Yes, all the time.
A court would also look at what OSM does. Does OSM list its data sources
after a link? Yes, sometimes two links (first to
https://www.openstreetmap.org/copyright, then to
https://wiki.openstreetmap.org/wiki/Contributors). Some of this data is
also under ODbL! Why is this not reasonable?

And you are pointing to the wrong version of CC-BY, btw, 4.0 came out long
after the license change, but since "reasonable" is the standard, Creative
Commons itself gives as an example of "best practices" attribution for
multiple sources this page: https://learn.saylor.org/course/view.php?id=28
Click on "Course Terms of Use" to see a list of attributions.


On Fri, Aug 9, 2019 at 11:38 AM Nuno Caldeira 
wrote:

> Where in CC-BY-SA's license does it say that attribution must be on top of
> an image
>
> As written on CC-BY-SA
>
> *Attribution*.
>
> If You Share the Licensed Material (including in modified form), You must:
> retain the following if it is supplied by the Licensor with the Licensed
> Material:
>
>1. identification of the creator(s) of the Licensed Material and any
>others designated to receive attribution, in any r*easonable manner
>requested by the Licensor* (including by pseudonym if designated);
>
>  in 3 a 1 A 1 https://creativecommons.org/licenses/by-sa/4.0/legalcode
>
>
>
> that no interaction is allowed???
>
>
> it says:
>
> 4.3 Notice for using output (Contents). Creating and Using a Produced
> Work does not require the notice in Section 4.2. However, if you
> Publicly Use a Produced Work, *You must include a notice associated with*
> * the Produced Work* reasonably calculated to make any Person that uses,
> *views,* accesses, interacts with, or is *otherwise exposed* to the
> Produced
> Work aware that Content was obtained from the Database, Derivative
> Database, or the Database as part of a Collective Database, and that it
> is available under this License.
>
> If you can explain me how  "reasonably calculated" to anyone that views or
> is exposed means that no attribution must be visibly on the Produced work.
> Feel free, i would like to know.
>
> Unless OSMF when we switched from CC to ODbL mislead the contributors and
> it's contributor terms, which i highly doubt.
>
>
> Let's do an exercise.
>
> LiveStream, a company of Vimeo uses OSM data on their website via a third
> party provider (Mapbox). I contacted LiveStream to comply with the license,
> they reply they are not using OSM data. Strange since i see my
> contributions on it, maybe they are not aware (being premium clients
> doesn't allow you to remove the attribution, other than the service
> provider, Mapbox). Asked them who sold them my data without complying with
> the license that i agreed my content to be distributed under. For over one
> month their legal department is still checking this.
>
> Link with a map example (feel free to browse to your contribution area),
> click on the "i" for the map to display
> https://livestream.com/accounts/9869799/events/7517661 printscreen of the
> maphttps://ibb.co/TH4LbFp
>
> Now the questions:
>
> 1 - Are they fulfilling the license?
>
> a) yes
>
> B) no
>
>
> 2 - Who's responsible?
>
> a) Mapbox
>
> b) LiveStream/Vimeo
>
>
> But following your "Where in CC-BY-SA's license does it say that
> attribution must be on top of an image or that no interaction is allowed",
> i have search all LiveStream website and there's no notice at all of OSM
> data.
>
>
> 3 - Who's not aware?
>
> a) Mapbox, an OSMF corporate member
>
> b) LiveStream/Vimeo, client of Mapbox
>
> c) contributors/OSMF
>
>
>
> Às 18:56 de 09/08/2019, Kathleen Lu escreveu:
>
> Where in CC-BY-SA's license does it say that attribution must be on top of
> an image or that no interaction is allowed???
>
>
> On Fri, Aug 9, 2019 at 10:17 AM Nuno Caldeira <
> nunocapelocalde...@gmail.com> wrote:
>
>> So you are saying that when we switched from CC to ODbL, the bellow quote
>> was not true?
>>
>> Both licenses are “By Attribution” and “Share Alike”.
>>
>>
>> https://wiki.osmfoundation.org/wiki/Licence/Historic/We_Are_Changing_The_License#What_are_the_main_differences_between_the_old_and_the_new_license.3F
>>
>>
>> Also the license is clear, anyone that views, i don't have to interact to
>> acknowledge the 

Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Richard Fairhurst wrote:
>
> For better understanding, you claimed "this looks pretty much like
> being written by corporate representatives", and I pointed out that
> one of the items in point 2 that you object to was written by me in
> 2012, so not a corporate representative, and has been at
> osm.org/copyright ever since.

Then let me rephrase:

It looks pretty much like being put together by corporate 
representatives.

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Richard Fairhurst wrote:
>
> These new guidelines say that, for 480px+ screens, hiding OSM
> attribution behind a click is not acceptable.

Unless "OpenStreetMap data accounts for a minority (less than 50%) part 
of the visible map rendering" - which is the case for almost all 
commercial maps.

> That's unambiguous all 
> we need. Fussing about what other logos might be on the map is a
> diversion and is not supported by the ODbL.

I don't think anyone but you talked about logos here.

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Richard Fairhurst
Christoph Hormann wrote:
> Just for understanding what second rate attribution is:  For example 
> the map on the bottom right of:
> https://www.zeit.de/politik/2019-07/strasse-von-hormus-bundesregierung-marinemission-usa-iran
> printing a prominent "Zeit Online" below the map (self attribution) but 
> showing OSM attribution only on user activity.

Right. The problem there is not that the "Zeit Online" attribution is too
big. The problem is that the OSM attribution is not compliant. Don't make
the issue more complex than it needs to be.

> The purpose of the guideline is to give practical guidiance how 
> to comply with the license.

And if the guidance suggests something that is not in the licence, it will
be - rightly - ignored, and we will have made no progress.

Community Guidelines explain how to apply the ODbL to real-world situations
("ambiguity or grey area in the specific and practical context of the Open
Database License"). You say "it can of course suggest things that are not
strictly required by the license", and sure, it could. It could also tell me
what the weather will be like tomorrow and the relevance of Martin Luther to
21st century religious thought. But that's not what Community Guidelines are
there for. They are here to explain how to apply the ODbL. If you want
somewhere to post good advice that isn't in the ODbL, I believe you have a
blog.

> > Your point 2 is objecting to something I wrote in 2012 when I
> > was editing a magazine about inland waterways and has been on
> > osm.org/copyright ever since, so nope. :)
>
> You are free to disagree with me but i hope you do not consider 
> this statement to be an argument on the matter.
>
> For better understanding:  Point 2 refers to a certain pattern in 
> the design of the document and lists a number of example to 
> demonstrate that.  You could argue the observation of there being 
> such a pattern or you could argue the individual examples.  You 
> however did neither of these in your statement.

For better understanding, you claimed "this looks pretty much like 
being written by corporate representatives", and I pointed out that one 
of the items in point 2 that you object to was written by me in 2012,
so not a corporate representative, and has been at osm.org/copyright
ever since.

Richard



--
Sent from: http://gis.19327.n8.nabble.com/General-Discussion-f5171242.html

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Richard Fairhurst

Martin Koppenhoefer wrote:

If you look at Apple Maps, and for example zoomed into some place in Denmark, 
there is an i-button which brings you to an overlay which has a TomTom logo and 
a link „and others“
while in Denmark the data is from OpenStreetMap. IMHO this second rate 
attribution clearly goes against „reasonably calculated“ because it’s 
misleading.


I know this, but let's not confuse the matter by calling this "second 
rate attribution". It isn't. It's no attribution.


These new guidelines say that, for 480px+ screens, hiding OSM 
attribution behind a click is not acceptable. That's unambiguous all we 
need. Fussing about what other logos might be on the map is a diversion 
and is not supported by the ODbL.


Richard

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Nuno Caldeira


. Plus, if anyone went to court trying to enforce something that OSMF 
recommended that was outside the licence, they would lose, and perhaps 
be forced by the court to pay attorney's fees.


Maybe individual contributors might feel "scary" of the attorney fees, 
but probably not these contributors (some even shared under CC):


Our contributors are thousands of individuals. We also include 
openly-licensed data from national mapping agencies and other sources, 
among them:


  * *Austria*: Contains data from Stadt Wien
 (under CC BY
), Land
Vorarlberg


and Land Tirol (under CC BY AT with amendments

).

  * *Australia*: Contains data sourced from PSMA Australia Limited

licensed by the Commonwealth of Australia under CC BY 4.0
.
  * *Canada*: Contains data from GeoBase®, GeoGratis (© Department of
Natural Resources Canada), CanVec (© Department of Natural
Resources Canada), and StatCan (Geography Division, Statistics
Canada).
  * *Finland*: Contains data from the National Land Survey of
Finland's Topographic Database and other datasets, under the NLSFI
License
.
  * *France*: Contains data sourced from Direction Générale des Impôts.
  * *Netherlands*: Contains © AND data, 2007 (www.and.com
)
  * *New Zealand*: Contains data sourced from the LINZ Data Service
 and licensed for reuse under CC BY
4.0 .
  * *Slovenia*: Contains data from the Surveying and Mapping Authority
 and Ministry of Agriculture, Forestry
and Food  (public information of
Slovenia).
  * *Spain*: Contains data sourced from the Spanish National
Geographic Institute (IGN ) and National
Cartographic System (SCNE ) licensed for
reuse under CC BY 4.0 .
  * *South Africa*: Contains data sourced from Chief Directorate:
National Geo-Spatial Information , State
copyright reserved.
  * *United Kingdom*: Contains Ordnance Survey data © Crown copyright
and database right 2010-19.


from https://www.openstreetmap.org/copyright


Would be interesting to hear from these agencies what their thoughts of 
the lack of attribution or different interpretation of ODbL. Probably 
not happy and would certainly arm OSMF reputation.



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Kathleen Lu wrote:
> I disagree that there is no harm. [...]

Not sure if you noticed but my argument was the inherent asymmetry of 
the situation when creating a guideline with recommendations.  If there 
is harm like "hurt feelings" from erring on the side of caution in a 
guideline is completely beside the point.

The credibility point does decidedly *not* go both ways.  The OSMF is 
not a neutral intermediary, it has the obligation to represent the 
interests of the project and not those of outside data users.  As Nuno 
linked to the OSMF right now points out the reasons why we ask for 
attribution:

"We want you to attribute OpenStreetMap, i.e. you show users and viewers 
of whatever you do with our data clearly where you got the data from. A 
lot of contributors have spent and spend a lot of time and effort 
adding data from virtually every country in the world. We would also 
like people to know about our project and perhaps use or contribute 
data themselves."

It is completely acceptable and even expected that the OSMF asks for and 
encourages attribution of OSM beyond the minimum required by the 
license.  That this would result in the loss of trust from anyone seems 
ridiculous.

And by the way if i try to follow your line of reasoning: you 
interestingly did not mention the most significant harm resulting from 
potentially unneccessary requirements:  Lost profits.

Ein Schelm wer böses dabei denkt...

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Nuno Caldeira
Where in CC-BY-SA's license does it say that attribution must be on 
top of an image

As written on CC-BY-SA


*Attribution*.

If You Share the Licensed Material (including in modified form), You must:

retain the following if it is supplied by the Licensor with the 
Licensed Material:


 1. identification of the creator(s) of the Licensed Material and any
others designated to receive attribution, in any r_*easonable
manner requested by the Licensor*_ (including by pseudonym if
designated);


 in 3 a 1 A 1 https://creativecommons.org/licenses/by-sa/4.0/legalcode




that no interaction is allowed???


it says:


4.3 Notice for using output (Contents). Creating and Using a Produced
Work does not require the notice in Section 4.2. However, if you
Publicly Use a Produced Work, _You must include a notice associated with__
__the Produced Work_ reasonably calculated to make any Person that uses,
_views,_ accesses, interacts with, or is _otherwise exposed_ to the 
Produced

Work aware that Content was obtained from the Database, Derivative
Database, or the Database as part of a Collective Database, and that it
is available under this License.
If you can explain me how  "reasonably calculated" to anyone that views 
or is exposed means that no attribution must be visibly on the Produced 
work. Feel free, i would like to know.


Unless OSMF when we switched from CC to ODbL mislead the contributors 
and it's contributor terms, which i highly doubt.



Let's do an exercise.

LiveStream, a company of Vimeo uses OSM data on their website via a 
third party provider (Mapbox). I contacted LiveStream to comply with the 
license, they reply they are not using OSM data. Strange since i see my 
contributions on it, maybe they are not aware (being premium clients 
doesn't allow you to remove the attribution, other than the service 
provider, Mapbox). Asked them who sold them my data without complying 
with the license that i agreed my content to be distributed under. For 
over one month their legal department is still checking this.


Link with a map example (feel free to browse to your contribution area), 
click on the "i" for the map to display 
https://livestream.com/accounts/9869799/events/7517661 printscreen of 
the maphttps://ibb.co/TH4LbFp


Now the questions:

1 - Are they fulfilling the license?

a) yes

B) no


2 - Who's responsible?

a) Mapbox

b) LiveStream/Vimeo


But following your "Where in CC-BY-SA's license does it say that 
attribution must be on top of an image or that no interaction is 
allowed", i have search all LiveStream website and there's no notice at 
all of OSM data.



3 - Who's not aware?

a) Mapbox, an OSMF corporate member

b) LiveStream/Vimeo, client of Mapbox

c) contributors/OSMF



Às 18:56 de 09/08/2019, Kathleen Lu escreveu:
Where in CC-BY-SA's license does it say that attribution must be on 
top of an image or that no interaction is allowed???



On Fri, Aug 9, 2019 at 10:17 AM Nuno Caldeira 
mailto:nunocapelocalde...@gmail.com>> 
wrote:


So you are saying that when we switched from CC to ODbL, the
bellow quote was not true?


Both licenses are “By Attribution” and “Share Alike”.



https://wiki.osmfoundation.org/wiki/Licence/Historic/We_Are_Changing_The_License#What_are_the_main_differences_between_the_old_and_the_new_license.3F


Also the license is clear, anyone that views, i don't have to
interact to acknowledge the notice.

Às 18:08 de 09/08/2019, Kathleen Lu escreveu:


Guidelines by the licensor


On legal advice, *what a Licensor says carries weight with
users of our data and, potentially, to a judge*. A court
would make a final decision on the issue, however we hope
these guidelines are helpful to *avoid *disputes arising in
the first place and can be considered by the courts in
coming to their verdict. 


from
https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines


Nuno, you are quoting this like it's the law, but what you have
quoted here isn't the *law*, it's what *OSMF* thinks *might*
happen and what motivates OSMF to put out guidelines. Frankly,
OSMF can choose to change the language you have quoted as a part
of changing the guidelines!
Under the law, the licensor's opinion, as one party to the
contract, is taken into consideration. However, it is *not* the
only thing that matters. The words of the licence matter more,
and if there is a conflict between what the licensor thinks and
what the licence says, the words of the licence will control. In
that case, the licensor is simply "wrong" (and there are plenty
of cases where that was the end result).
You are right that we hope to avoid disputes by setting out
reasonable guidelines, but if OSMF sets out guidelines that are
unreasonable and not tied to the language of the licence, then no
one, either users of the data or judges, will listen to 

Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Martin Koppenhoefer


sent from a phone

> On 9. Aug 2019, at 14:19, Richard Fairhurst  wrote:
> 
> But you can't start requiring that "the OpenStreetMap attribution needs to
> be at least on the same level of 
> prominence and visibility as... other data providers, designers, service
> providers or publicists", because that's not in the ODbL.


If you look at Apple Maps, and for example zoomed into some place in Denmark, 
there is an i-button which brings you to an overlay which has a TomTom logo and 
a link „and others“ 
while in Denmark the data is from OpenStreetMap. IMHO this second rate 
attribution clearly goes against „reasonably calculated“ because it’s 
misleading.

Cheers Martin 


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Kathleen Lu via talk
I disagree that there is no harm. The credibility point goes both ways.
While no one could sue OSMF for recommending something that is not required
by the license, OSMF would lose the trust of data users, mappers, and any
adjudicative tribunals.
And it would be misleading and harmful to anyone who sought to enforce the
licence, causing, at the very least, confusion, arguments and hurt
feelings. Plus, if anyone went to court trying to enforce something that
OSMF recommended that was outside the licence, they would lose, and perhaps
be forced by the court to pay attorney's fees. While this would probably
not cause financial harm to OSMF, but it would be very damaging to the
community.

On Fri, Aug 9, 2019 at 10:29 AM Christoph Hormann  wrote:

> On Friday 09 August 2019, Kathleen Lu wrote:
> > You are right that we hope to avoid disputes by setting out
> > reasonable guidelines, but if OSMF sets out guidelines that are
> > unreasonable and not tied to the language of the licence, then no
> > one, either users of the data or judges, will listen to OSMF, and,
> > under the law, rightly so.
>
> The key point is that it is fine if the guidelines deviate from the
> license on the side of caution, i.e. as Richard puts it: requiring
> something that is not in the license.  That is possibly suboptimal but
> there is no serious harm to err on the side of caution.  No data user
> could sue the OSMF for in the guidelines recommending something that is
> not required by the license.  OTOH if the guidelines recommend
> something that is not allowed by the license that is a serious problem,
> it defeats the whole purpose of the guideline and endangers the
> credibility of the OSMF both with mappers and data users.
>
> In the current form i have the impression that the guideline draft tries
> to state the most lenient interpretation of the license w.r.t.
> attribution that is imaginable which is not obviously wrong (and in
> case of the 50 percent rule i think it goes beyond that - this is
> obviously not compatible with the license from my point of view).  I
> find this kind of - well - reckless.
>
> --
> Christoph Hormann
> http://www.imagico.de/
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Kathleen Lu via talk
Where in CC-BY-SA's license does it say that attribution must be on top of
an image or that no interaction is allowed???


On Fri, Aug 9, 2019 at 10:17 AM Nuno Caldeira 
wrote:

> So you are saying that when we switched from CC to ODbL, the bellow quote
> was not true?
>
> Both licenses are “By Attribution” and “Share Alike”.
>
>
> https://wiki.osmfoundation.org/wiki/Licence/Historic/We_Are_Changing_The_License#What_are_the_main_differences_between_the_old_and_the_new_license.3F
>
>
> Also the license is clear, anyone that views, i don't have to interact to
> acknowledge the notice.
> Às 18:08 de 09/08/2019, Kathleen Lu escreveu:
>
>
> Guidelines by the licensor
>>
>> On legal advice, *what a Licensor says carries weight with users of our
>> data and, potentially, to a judge*. A court would make a final decision
>> on the issue, however we hope these guidelines are helpful to *avoid 
>> *disputes
>> arising in the first place and can be considered by the courts in coming to
>> their verdict.
>>
>> from https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines
>>
>
> Nuno, you are quoting this like it's the law, but what you have quoted
> here isn't the *law*, it's what *OSMF* thinks *might* happen and what
> motivates OSMF to put out guidelines. Frankly, OSMF can choose to change
> the language you have quoted as a part of changing the guidelines!
> Under the law, the licensor's opinion, as one party to the contract, is
> taken into consideration. However, it is *not* the only thing that matters.
> The words of the licence matter more, and if there is a conflict between
> what the licensor thinks and what the licence says, the words of the
> licence will control. In that case, the licensor is simply "wrong" (and
> there are plenty of cases where that was the end result).
> You are right that we hope to avoid disputes by setting out reasonable
> guidelines, but if OSMF sets out guidelines that are unreasonable and not
> tied to the language of the licence, then no one, either users of the data
> or judges, will listen to OSMF, and, under the law, rightly so.
>
>
>>
>>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Kathleen Lu wrote:
> You are right that we hope to avoid disputes by setting out
> reasonable guidelines, but if OSMF sets out guidelines that are
> unreasonable and not tied to the language of the licence, then no
> one, either users of the data or judges, will listen to OSMF, and,
> under the law, rightly so.

The key point is that it is fine if the guidelines deviate from the 
license on the side of caution, i.e. as Richard puts it: requiring 
something that is not in the license.  That is possibly suboptimal but 
there is no serious harm to err on the side of caution.  No data user 
could sue the OSMF for in the guidelines recommending something that is 
not required by the license.  OTOH if the guidelines recommend 
something that is not allowed by the license that is a serious problem, 
it defeats the whole purpose of the guideline and endangers the 
credibility of the OSMF both with mappers and data users.

In the current form i have the impression that the guideline draft tries 
to state the most lenient interpretation of the license w.r.t. 
attribution that is imaginable which is not obviously wrong (and in 
case of the 50 percent rule i think it goes beyond that - this is 
obviously not compatible with the license from my point of view).  I 
find this kind of - well - reckless.

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Dave F via talk wrote:
> Hi
>
> Static Images.
>
> "Static images should be generally attributed the same way as dynamic
> images, " I agree & a way to enable users to easily add attribution
> needs to be created. The Share>Image feature on the main page should
> automatically image stamp the attribution into the corner. "images of
> areas less 10’000 m2or fewer than 100 features do not require
> attribution." For a static image I'm struggling to see what the area
> coverage or the number of items contained has to do with adding an
> attribution - an image is an image, irrelevant of size. DaveF

I think the idea is that if you create a map based on an insubstantial 
amount of OSM data no attribution is required - this derives from 
the "Substantial" Guideline.

If you now crop from a larger map a rectangle that equally contains only 
an insubstantial amount of OSM data it makes sense to treat this the 
same way.  This would only apply to individual small images though - 
not to pages systematically showing lots of different crops.  This 
restriction, which would match the "Substantial" Guideline, is missing 
so far.

I am not sure about the origin of the 10k m^2 limit - that is not in 
the "Substantial" Guideline at the moment.

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Nuno Caldeira
So you are saying that when we switched from CC to ODbL, the bellow 
quote was not true?



Both licenses are “By Attribution” and “Share Alike”.


https://wiki.osmfoundation.org/wiki/Licence/Historic/We_Are_Changing_The_License#What_are_the_main_differences_between_the_old_and_the_new_license.3F


Also the license is clear, anyone that views, i don't have to interact 
to acknowledge the notice.


Às 18:08 de 09/08/2019, Kathleen Lu escreveu:


Guidelines by the licensor


On legal advice, *what a Licensor says carries weight with users
of our data and, potentially, to a judge*. A court would make a
final decision on the issue, however we hope these guidelines are
helpful to *avoid *disputes arising in the first place and can be
considered by the courts in coming to their verdict. 


from https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines


Nuno, you are quoting this like it's the law, but what you have quoted 
here isn't the *law*, it's what *OSMF* thinks *might* happen and what 
motivates OSMF to put out guidelines. Frankly, OSMF can choose to 
change the language you have quoted as a part of changing the guidelines!
Under the law, the licensor's opinion, as one party to the contract, 
is taken into consideration. However, it is *not* the only thing that 
matters. The words of the licence matter more, and if there is a 
conflict between what the licensor thinks and what the licence says, 
the words of the licence will control. In that case, the licensor is 
simply "wrong" (and there are plenty of cases where that was the end 
result).
You are right that we hope to avoid disputes by setting out reasonable 
guidelines, but if OSMF sets out guidelines that are unreasonable and 
not tied to the language of the licence, then no one, either users of 
the data or judges, will listen to OSMF, and, under the law, rightly so.



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Pierre Béland via talk
I agree, this would be more snappy and more international. It woulrd not be 
necessary to translate the attribution for various languages.   By shortening 
the attribution, their would be less excuses to not attribute on the map.

 
Pierre 
 

Le vendredi 9 août 2019 10 h 40 min 27 s UTC−4, Frederik Ramm 
 a écrit :  
 
 Hi,

I wonder if we could perhaps get rid of the "Contributors" mention
altogether.

The term "OpenStreetMap Contributors" is the unwieldy; it just sounds
strange to say "this is a map made by OpenStreetMap contributors" when
what we really want to say is "this is OpenStreetMap". When translated
into German, you would have to say "OpenStreetMap-Beitragende" or, more
correctly, "Beitragende zu OpenStreetMap", which to the un-initiated
sounds a bit strange and kind of dilutes the OpenStreetMap brand by
adding things before or after. I am pretty sure that there are languages
where grammar in fact requires that the "contributors" be placed before
OSM (as in my "Beitragende zu OpenStreetMap" example) and where no
grammatically correct way exists to place OSM first.

I know, OpenStreetMap is not a legal entity and therefore cannot be said
to own the copyright. Then again, "(c) OpenStreetMap contributors" is
not technically correct either, as there are many ways in which you can
contribute to OSM, but only some of them will earn you a share of the
copyright in the map. Someone who contributes to OSM by giving us money,
or writing code, or organising meetups, is not part of the group that
holds the rights in the map.

I would find a simple "(c) OpenStreetMap" better, more snappy, more
recognizable than if we demand that the "contributors" are mentioned.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
  ___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Kathleen Lu via talk
> Guidelines by the licensor
>
> On legal advice, *what a Licensor says carries weight with users of our
> data and, potentially, to a judge*. A court would make a final decision
> on the issue, however we hope these guidelines are helpful to *avoid *disputes
> arising in the first place and can be considered by the courts in coming to
> their verdict.
>
> from https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines
>

Nuno, you are quoting this like it's the law, but what you have quoted here
isn't the *law*, it's what *OSMF* thinks *might* happen and what motivates
OSMF to put out guidelines. Frankly, OSMF can choose to change the language
you have quoted as a part of changing the guidelines!
Under the law, the licensor's opinion, as one party to the contract, is
taken into consideration. However, it is *not* the only thing that matters.
The words of the licence matter more, and if there is a conflict between
what the licensor thinks and what the licence says, the words of the
licence will control. In that case, the licensor is simply "wrong" (and
there are plenty of cases where that was the end result).
You are right that we hope to avoid disputes by setting out reasonable
guidelines, but if OSMF sets out guidelines that are unreasonable and not
tied to the language of the licence, then no one, either users of the data
or judges, will listen to OSMF, and, under the law, rightly so.


>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Nuno Caldeira



* What's the guidance on scenarios where software does not ship with OSM
data, and does not display online maps, but e.g. allows downloading map
data for offline use? Would it be acceptable to make the license
information part of the download process, or is it still required that
attribution is visible on-screen during use?

Tobias



From my perspective, the user is aware of the map source and must be 
sure of the terms of it. Example Arcgis or QGIS software, both allow to 
use OSM as basemap or download the data. They do not show the license.


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Nuno Caldeira


Às 14:56 de 09/08/2019, Christoph Hormann escreveu:

On Friday 09 August 2019, Richard Fairhurst wrote:
It is a community guideline - a recommendation of the community on how
to work with OSM data to comply with the license.  No data user has to
follow the guideline - the only binding document is the license itself.
The purpose of the guideline is to give practical guidiance how to
comply with the license.  The Guidelines should never suggest something
that would violate the license (like as mentioned the 50 percent rule)
but it can of course suggest things that are not strictly required by
the license.  And saying "if you attribute in this way that is
perfectly fine with the community" is useful even if "this way" goes
beyond the minimum requirements of the license.


Guidelines by the licensor

On legal advice, *what a Licensor says carries weight with users of 
our data and, potentially, to a judge*. A court would make a final 
decision on the issue, however we hope these guidelines are helpful to 
*avoid *disputes arising in the first place and can be considered by 
the courts in coming to their verdict. 


from https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines

what companies are doing, is exactly the opposite, they justify their 
actions based on the license interpretation to their own interests, not 
taking into account what the licensor says.


The license is clear:


4.3 Notice for using output (Contents). Creating and Using a Produced
Work does not require the notice in Section 4.2. However, if you
Publicly Use a Produced Work, You must*include a notice* associated with
the *Produced Work reasonably calculated to make any Person* that uses,
*views*, accesses, interacts with, *or is otherwise exposed to the 
Produced**

**Work aware that Content was obtained from *the Database, Derivative
Database, or the Database as part of a Collective Database, and that it
is available under this License.
Unless someone can explain me how i'm i suppose to see the notice when 
i'm view or am exposed to their produced work if they are not showing it 
visibly and clearly without me having to interact to either click an "i" 
icon or go through endless submenus to figure out what's the map source. 
the word "interacts" is there for a reason...






And i also think rejecting second rate attribution is perfectly in line
with and supported by the "reasonably calculated" requirement of the
ODbL since with a significantly less prominent attribution of OSM
compared to other attributions given this is less the case.  In the
case linked to above for example removing the "Zeit Online" would
increase the likelihood that a page visitor - when asked - could
correctly identify the map source because they would be more likely to
look under the 'i' than if they have the obvious other explanation (map
produced by Zeit Online out of thin air) being presented as the
simplest answer.


quoting ODbL:


4.8 Licensing of others. You may not sublicense the Database.

They must keep the notice intact, therefore attributing OSM.


When we switched from CC to ODbL, this was documented as:


Both licenses are “By Attribution” and “Share Alike”.


https://wiki.osmfoundation.org/wiki/Licence/Historic/We_Are_Changing_The_License#What_are_the_main_differences_between_the_old_and_the_new_license.3F

Ditching the attribution for second rate attribution is not only unfair, 
does not meet this and also goes against OSMF objects of the foundation 
articles 
. 
Unless someone explains me how we are promoting the growdth, development 
and distribution of free geospatial data to those that are not aware of 
it by hiding the source of the wonderful maps those companies do with 
the data from this lovely community.


you show users and viewers of whatever you do with our data clearly 
where you got the data from. A lot of contributors have spent and 
spend a lot of time and effort adding data from virtually every 
country in the world. We would also like people to know about our 
project and perhaps use or contribute data themselves. 


https://wiki.osmfoundation.org/wiki/Licence/Licence_and_Legal_FAQ#What_do_you_mean_by_.22Attribution.22.3F

Also it's crucial the attribution has in marketing and promotion of the 
project. Or are we having a Working group for that?



About omitting permanently the "contributors" part by me is fine, but i 
truly hope the argument of "lack of space to display" will not be used 
like it's being abusively justified like it is now.


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Tobias Knerr
Thank you for your work! I believe that clearly documenting our
expectations is a very important step towards solving the current
problems surrounding attribution. It will help well-intentioned data
users to avoid accidentally messing up OSM attribution, and it leaves
fewer excuses for the less well-intentioned ones – making it easier for
us to put pressure on them to improve their practices.

I do have a couple of questions/comments about the current draft:

* Can you confirm that the current attribution practices on Wikipedia
and many similar projects would be covered by the "small images" case?

* I believe video games/simulations should be given similar treatment as
fictional movie productions by permitting attribution in the credits as
an alternative to the current options. Not allowing this seems to
contradict the larger "in a location where customarily attribution would
be expected" principle, as rolling credits are customary for many gaming
genres. (I'm mostly thinking of traditional PC or console games here,
not so much of mobile apps.)

* What's the guidance on scenarios where software does not ship with OSM
data, and does not display online maps, but e.g. allows downloading map
data for offline use? Would it be acceptable to make the license
information part of the download process, or is it still required that
attribution is visible on-screen during use?

Tobias

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Dave F via talk

Hi

Static Images.

"Static images should be generally attributed the same way as dynamic 
images, " I agree & a way to enable users to easily add attribution 
needs to be created. The Share>Image feature on the main page should 
automatically image stamp the attribution into the corner. "images of 
areas less 10’000 m2or fewer than 100 features do not require 
attribution." For a static image I'm struggling to see what the area 
coverage or the number of items contained has to do with adding an 
attribution - an image is an image, irrelevant of size. DaveF On 
09/08/2019 08:41, Simon Poole wrote:

As we've mentioned multiple times over the last months, the LWG decided
last year to consolidate all attribution guidance in to one document and
address some of the use cases that have become common over the last 7
years that previously had none. Particularly in the light of the
parallel discussions about attribution on larger social media platforms
we need to make up our minds what we actually want, and define concrete
minimum requirements for acceptable attribution. To not do this just
provides the excuse of pointing to the cacophony of voices all saying
something different.

We've been working on and off on the document for a while, and are now
largely finished. Going forward we intend to wikify the document and
make it available for public comment together with a BoF session at SotM
next month (which probably means that we'll have to appropriate a coffee
break). You can have a glimpse at the text here
https://docs.google.com/document/d/1e_IQYHtqVivGRw4O4EOn6__-LGMuzPlWz6XKEdAkwW0/edit?usp=sharing
the few things that are not nailed down belong to those that we would
appreciate feedback on.

Simon

PS: the number of coffee breaks permitting we might want to appropriate
another one for the discussion of a tile licence change.




___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Jóhannes Birgir Jensson
I concur, this becomes long and unwieldy fast in my own language and to fully 
capture it requires a full sentence, with a comma for clarity even.

Behind OpenStreetMap the brand we have contributors amongst others.



9. ágúst 2019 kl. 14:40, skrifaði "Frederik Ramm" :

> Hi,
> 
> I wonder if we could perhaps get rid of the "Contributors" mention
> altogether.
> 
> The term "OpenStreetMap Contributors" is the unwieldy; it just sounds
> strange to say "this is a map made by OpenStreetMap contributors" when
> what we really want to say is "this is OpenStreetMap". When translated
> into German, you would have to say "OpenStreetMap-Beitragende" or, more
> correctly, "Beitragende zu OpenStreetMap", which to the un-initiated
> sounds a bit strange and kind of dilutes the OpenStreetMap brand by
> adding things before or after. I am pretty sure that there are languages
> where grammar in fact requires that the "contributors" be placed before
> OSM (as in my "Beitragende zu OpenStreetMap" example) and where no
> grammatically correct way exists to place OSM first.

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Clifford Snow
On Fri, Aug 9, 2019 at 7:35 AM Frederik Ramm  wrote:

> Hi,
>
> I wonder if we could perhaps get rid of the "Contributors" mention
> altogether.
>

I agree, I've often felt that the OpenStreetMap Contributors was unwieldy.
If we agree to the change, I imagine that OpenStreetMap would need to be
redefined to include its data contributors.

Best,
Clifford

-- 
@osm_washington
www.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Frederik Ramm
Hi,

I wonder if we could perhaps get rid of the "Contributors" mention
altogether.

The term "OpenStreetMap Contributors" is the unwieldy; it just sounds
strange to say "this is a map made by OpenStreetMap contributors" when
what we really want to say is "this is OpenStreetMap". When translated
into German, you would have to say "OpenStreetMap-Beitragende" or, more
correctly, "Beitragende zu OpenStreetMap", which to the un-initiated
sounds a bit strange and kind of dilutes the OpenStreetMap brand by
adding things before or after. I am pretty sure that there are languages
where grammar in fact requires that the "contributors" be placed before
OSM (as in my "Beitragende zu OpenStreetMap" example) and where no
grammatically correct way exists to place OSM first.

I know, OpenStreetMap is not a legal entity and therefore cannot be said
to own the copyright. Then again, "(c) OpenStreetMap contributors" is
not technically correct either, as there are many ways in which you can
contribute to OSM, but only some of them will earn you a share of the
copyright in the map. Someone who contributes to OSM by giving us money,
or writing code, or organising meetups, is not part of the group that
holds the rights in the map.

I would find a simple "(c) OpenStreetMap" better, more snappy, more
recognizable than if we demand that the "contributors" are mentioned.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"



signature.asc
Description: OpenPGP digital signature
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Andy Mabbett
On Fri, 9 Aug 2019 at 08:41, Simon Poole  wrote:

> to consolidate all attribution guidance in to one document

Some thoughts:

> www.openstreetmap.org/copyright

openstreetmap.org/copyright (without "www") works, and should be
preferred (several occurrences).

> Our requested attribution is "© OpenStreetMap contributors".

Add "or the equivalent in the local language".

Change "requested" to "preferred", since other forms are allowable.

> You should qualify the credit to explain what OSM content you are
> using. For example, if you have rendered OSM data to your own
> design, you may wish to use "Map data © OpenStreetMap contributors".

Confusion between "should" and "may".

> If OpenStreetMap data accounts for a minority (less than
> 50%) part of the visible map rendering...

The concerns others have raised could be addressed by changing this to
"If less than 50% of the data used for the visible map rendering is
from OpenStreetMap..."

> Except for small images

"small" is subjective; give a definition.

>Applications that incorporate a geocoder must credit OpenStreetMap

Change to "Applications that incorporate a geocoder that uses
OpenStreetMap data must credit OpenStreetMap"

> or in a footnote/endnote if that is where other credits appear and/or in the 
> "acknowledgements" section

Change to "or in a footnote/endnote and/or in the 'acknowledgements'
section, whichever is where other credits appear"

> Tv, film or video

Typo; should be "TV, film or video"

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Jóhannes Birgir Jensson wrote:
> I think we move in different mapper communities as "mapping for the
> reward of being recognized by external data users" has never even
> been on my list, or of those mappers I know, of reasons for why we
> map.

Please don't twist my words - i have not said mappers are "mapping for 
the reward of being recognized by external data users".  I said "While 
elsewhere people generating geodata are almost always rewarded for 
their work also in other form (like salery) in OSM the only recognition 
mappers receive from external data users is the attribution required by 
the license".  That is a huge difference.

The growth of the mapper community and in particular the increase in the 
number of mappers who are externally motivated to map (like paid 
mappers or mappers in organized humanitarian mapping projects) can 
certainly lead to the impression that those mappers whose commitment 
depends on the social contract between mappers and data users being 
honored by the data users are not strictly needed any more for the 
project to survive.  I would not be too sure about that though.  
Research on social networks in general typically shows that the 
function and attractiveness of a network to participants often depends 
on a relatively small number of participants.  And in particular power 
mappers who might have over many years mapped a significant fraction of 
their home town and environment are quite likely to become demotivated 
when they see that data users increasingly just rip off their work and 
can't be bothered to even acknowledge their contribution in a very 
basic and collective fashion.  With mapper retention over longer time 
being an issue in general this is a significant problem.

Note that this idea of the function of attribution in OSM is not my 
invention, this is a matter that has been discussed plenty of times 
over the years with the basic point i am trying to make here being 
agreed on by many different people.  Obviously there are also many 
mappers who don't care about attribution and who would be fine or would 
even prefer if OSM data was PD.  But that is not my point here.  
Because also those mappers are to a large fraction fully aware that 
this view is not universal.

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann
On Friday 09 August 2019, Richard Fairhurst wrote:
> > It does not in any way address the problem of second rate
> > attribution (i.e. someone else - usually the service provider of
> > the map service or the media outlet publishing the map) is being
> > attributed more prominently than OSM.
>
> That is not something that the ODbL requires. There are licences with
> an obnoxious advertising clause but ODbL isn't one.
>
> "Second rate attribution" is not a problem. [...]

Just for understanding what second rate attribution is:  For example the 
map on the bottom right of:

https://www.zeit.de/politik/2019-07/strasse-von-hormus-bundesregierung-marinemission-usa-iran

printing a prominent "Zeit Online" below the map (self attribution) but 
showing OSM attribution only on user activity.

> But you can't start requiring that "the OpenStreetMap attribution
> needs to be at least on the same level of
> prominence and visibility as... other data providers, designers,
> service providers or publicists", because that's not in the ODbL.

It is a community guideline - a recommendation of the community on how 
to work with OSM data to comply with the license.  No data user has to 
follow the guideline - the only binding document is the license itself.  
The purpose of the guideline is to give practical guidiance how to 
comply with the license.  The Guidelines should never suggest something 
that would violate the license (like as mentioned the 50 percent rule) 
but it can of course suggest things that are not strictly required by 
the license.  And saying "if you attribute in this way that is 
perfectly fine with the community" is useful even if "this way" goes 
beyond the minimum requirements of the license.

And i also think rejecting second rate attribution is perfectly in line 
with and supported by the "reasonably calculated" requirement of the 
ODbL since with a significantly less prominent attribution of OSM 
compared to other attributions given this is less the case.  In the 
case linked to above for example removing the "Zeit Online" would 
increase the likelihood that a page visitor - when asked - could 
correctly identify the map source because they would be more likely to 
look under the 'i' than if they have the obvious other explanation (map 
produced by Zeit Online out of thin air) being presented as the 
simplest answer.

> Your point 2 is objecting to something I wrote in 2012 when I was
> editing a magazine about inland waterways and has been on
> osm.org/copyright ever since, so nope. :)

You are free to disagree with me but i hope you do not consider this 
statement to be an argument on the matter.

For better understanding:  Point 2 refers to a certain pattern in the 
design of the document and lists a number of example to demonstrate 
that.  You could argue the observation of there being such a pattern or 
you could argue the individual examples.  You however did neither of 
these in your statement.

-- 
Christoph Hormann
http://www.imagico.de/

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Richard Fairhurst
Christoph Hormann wrote:
> It does not in any way address the problem of second rate attribution 
> (i.e. someone else - usually the service provider of the map service 
> or the media outlet publishing the map) is being attributed more 
> prominently than OSM.

That is not something that the ODbL requires. There are licences with an
obnoxious advertising clause but ODbL isn't one.

"Second rate attribution" is not a problem. If Mapco[1] want to put a big
Mapco logo on their maps, that is absolutely fine and dandy according to the
ODbL.

The problem is when there is a big Mapco logo on the map; no OSM attribution
other than the infamous "(i)"; and the latter is justified by saying
"there's no room" when the former clearly disproves that. This is an
infringement of ODbL 4.3 and our favourite "reasonably calculated" clause.

But you can't start requiring that "the OpenStreetMap attribution needs to
be at least on the same level of 
prominence and visibility as... other data providers, designers, service
providers or publicists", because that's not in the ODbL.

> Overall i think this is totally unacceptable and looks pretty much 
> like being written by corporate representatives

Your point 2 is objecting to something I wrote in 2012 when I was editing a
magazine about inland waterways and has been on osm.org/copyright ever
since, so nope. :)

Richard

[1] let's be honest, we're mostly talking about Mapbox and Carto here



--
Sent from: http://gis.19327.n8.nabble.com/General-Discussion-f5171242.html

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Jóhannes Birgir Jensson
I think we move in different mapper communities as "mapping for the reward of 
being recognized by external data users" has never even been on my list, or of 
those mappers I know, of reasons for why we map.

Of course everyones self-image is their own, so I don't know about your claim 
of there being a fundamental one for the whole community.

Just my 2 krónur.

-- /OSM: Stalfur


9. ágúst 2019 kl. 11:15, skrifaði "Christoph Hormann" :

> And frankly it also contradicts the fundamental self-image of the mapper 
> community. As has been discussed plenty of times the way geodata is 
> generated in OSM is fundamentally different from other geodata sources. 
> While elsewhere people generating geodata are almost always rewarded 
> for their work also in other form (like salery) in OSM the only 
> recognition mappers receive from external data users is the attribution 
> required by the license. Putting OSM on the same level as other data 
> providers like you do above is totally inappropriate.

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Nuno Caldeira
About the 50% exception. i recently had to be unpleasant with Fatmap 
(their app and website https://fatmap.com/), after 2 months of zero 
action from their side. Source 
https://twitter.com/iamnunocaldeira/status/1136624467000602624 after my 
message on the 3rd of August, they contacted me via private message, to 
which i explained how to attribute, linking to copyright page, OSMF 
guidelines and license terms. They stated:


"Thank you - yes our mapping and tech teams are in touch with them 
both now. _We have over 20 different providers for our map_, all with 
different requirements and different integrations. So we are working 
out the best solution!"


To which i replied i had nothing to do with the other sources, how they 
must fulfil the other sources attribution (if applies)  and they should 
comply with our attribution as required. They then replied:


Once we have found a solution together with the OSM and MapBox teams, 
I will let you know!"
i asked them with whom of OSM/OSMF they are speaking to, they never 
replied back. Can anyone from OSMF tell me with who they are working in 
OSM/OSMF? I would like to know or if they are just saying they are 
talking to, when they are not. AFAIK we do not open exceptions about 
this subject.



Another concern i have by their reply is Mapbox teams dictating how and 
when the attribution must be displayed. This being said, i start to 
believe we should remove the 50% exception (how would we actually know 
if it's 51% OSM or 49%?), because it will be used as a loophole to avoid 
the attribution. Fatmap example is a perfect of Christoph concern about 
corporate usage. We shouldn't place our data/derivate with attribution 
with the same usage of paid map data/derivates that is not subject to 
attribution if paid for.


It's just another example to the long list of example of Strava, 
Facebook, Instagram, Vimeo Livestream (Mapbox client, that has their 
legal dept checking if they should attribute or not) and more that are 
using OSM without attributing at all. As i have shared on other lists, 
_*it's a shame*_ most of these lack of attribution examples i gave comes 
first or second handed from corporate members of OSMF (Facebook and 
Mapbox). Up until they give an example of how to be good citizens of 
OSM, these guidelines won't solve the issue. For months, both of these 
companies have been silence about it and OSMF board too. Which results 
in the lack of attribution being a "normal thing", when it's not.


Sadly i'm starting to believe these lack of attribution will only be 
solved once a contributor (individual or a national agency that provided 
data to OSM under the license) sues one of these companies. As we know 
as soon as someone does not comply with the license (or formally 
informed by the licensor) it's rights are terminated. If a contributor 
wants to sue for their content that they licensed to OSMF to be 
distributed only under ODbL, they are legit to take action. If this 
occurs, i fear it will damage OSM/OSMF image and fear of usage of data. 
which is not what we want and will affect OSMF OBJECTS 
. 
All of it can be avoided by simply doing what's on the license, instead 
of arguing if it should or not attribute open data that they are using 
for free without crediting.


Mea culpa as i also helped on this guidance. We do need to improve it, 
so feel free to suggest, share concerns.




Às 12:06 de 09/08/2019, Christoph Hormann escreveu:

I am strongly against this in the current form because it addresses none
of the major issues about corporate attribution of OSM (or lack
thereof).

1) It does not in any way address the problem of second rate attribution
(i.e. someone else - usually the service provider of the map service or
the media outlet publishing the map) is being attributed more
prominently than OSM.  The '50 percent rule' you invented:

"If OpenStreetMap data accounts for a minority (less than 50%) part of
the visible map rendering, attribution with other sources on a separate
page that is visible after user interaction is acceptable."

is ridiculous because 50 percent of the map area being functionally
empty is essentially a property of most maps, in particular at large
scales or high zoom levels.  There is no basis in the ODbL for allowing
attribution in a case where attribution is required that is
not "reasonably calculated to make any person [...] aware".  Therefore
i would consider that rule in clear violation of the license.

And frankly it also contradicts the fundamental self-image of the mapper
community.  As has been discussed plenty of times the way geodata is
generated in OSM is fundamentally different from other geodata sources.
While elsewhere people generating geodata are almost always rewarded
for their work also in other form (like salery) in OSM the only
recognition mappers receive from external data users is the attribution
required by the 

Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Richard Fairhurst
SimonPoole wrote:
> the few things that are not nailed down belong to those that we 
> would appreciate feedback on.

This is really good, and very much in accordance with both the text of the
ODbL and the long-standing precedents set by the osm.org/copyright page.
Thank you.

Two small wording clarifications:

"If OpenStreetMap data accounts for a minority (less than 50%) part of the
visible map rendering, attribution with other sources on a separate page
that is visible after user interaction is acceptable."

This probably needs to be qualified to the "currently visible map
rendering", and "50%" phrased as "50% of objects" or similar - just to
clarify the (quite likely) scenario where a map uses OSM data in (say)
Turkey, TomTom everywhere else, and Natural Earth for coastlines/land.

"It is permissible to use a mechanism to collapse the attribution as long as
it is initially fully visible"

This would be better as "It is permissible to provide a user-activated
mechanism to...". There are apps which flash up an OSM credit for under a
second, after which it disappears (including one terrific iOS mapping app
which I would otherwise recommend).

cheers
Richard




--
Sent from: http://gis.19327.n8.nabble.com/General-Discussion-f5171242.html

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Yves
Hi Simon,
This guideline is a great piece of work, thanks a lot to all the participants.
Inevitably, this will be too much or not enough for anybody, however I find the 
content reasonable and in line with what I understood from current written 
expectations.
A few more mockups, notably for minimaps and apps would be great.
After all the text is clear enough and I would find the "yes, but we want to 
let the designer some freedom" argument a bit hypocritical.
Yves 

Le 9 août 2019 09:41:25 GMT+02:00, Simon Poole  a écrit :
>As we've mentioned multiple times over the last months, the LWG decided
>last year to consolidate all attribution guidance in to one document
>and
>address some of the use cases that have become common over the last 7
>years that previously had none. Particularly in the light of the
>parallel discussions about attribution on larger social media platforms
>we need to make up our minds what we actually want, and define concrete
>minimum requirements for acceptable attribution. To not do this just
>provides the excuse of pointing to the cacophony of voices all saying
>something different. 
>
>We've been working on and off on the document for a while, and are now
>largely finished. Going forward we intend to wikify the document and
>make it available for public comment together with a BoF session at
>SotM
>next month (which probably means that we'll have to appropriate a
>coffee
>break). You can have a glimpse at the text here
>https://docs.google.com/document/d/1e_IQYHtqVivGRw4O4EOn6__-LGMuzPlWz6XKEdAkwW0/edit?usp=sharing
>the few things that are not nailed down belong to those that we would
>appreciate feedback on.
>
>Simon
>
>PS: the number of coffee breaks permitting we might want to appropriate
>another one for the discussion of a tile licence change.
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Attribution guideline status update

2019-08-09 Thread Christoph Hormann

I am strongly against this in the current form because it addresses none 
of the major issues about corporate attribution of OSM (or lack 
thereof).

1) It does not in any way address the problem of second rate attribution 
(i.e. someone else - usually the service provider of the map service or 
the media outlet publishing the map) is being attributed more 
prominently than OSM.  The '50 percent rule' you invented:

"If OpenStreetMap data accounts for a minority (less than 50%) part of 
the visible map rendering, attribution with other sources on a separate 
page that is visible after user interaction is acceptable."

is ridiculous because 50 percent of the map area being functionally 
empty is essentially a property of most maps, in particular at large 
scales or high zoom levels.  There is no basis in the ODbL for allowing 
attribution in a case where attribution is required that is 
not "reasonably calculated to make any person [...] aware".  Therefore 
i would consider that rule in clear violation of the license.

And frankly it also contradicts the fundamental self-image of the mapper 
community.  As has been discussed plenty of times the way geodata is 
generated in OSM is fundamentally different from other geodata sources.  
While elsewhere people generating geodata are almost always rewarded 
for their work also in other form (like salery) in OSM the only 
recognition mappers receive from external data users is the attribution 
required by the license.  Putting OSM on the same level as other data 
providers like you do above is totally inappropriate.

As previously said my suggestion for regulating this is:

"If anyone else is attributed in the context of a work based on OSM data 
(like other data providers, designers, service providers or publicists) 
the OpenStreetMap attribution needs to be at least on the same level of 
prominence and visibility as those."

2) Also beyond that you formulate more exceptions than actual 
requirements and where you formulate requirements they are put in 
obviously weasely terms or are tightly limited to very specific 
situations:

* "you may omit the word "contributors" if space is limited" - since 
space is always limited obviously this is a bogus requirement with no 
practical effect.  So you essentially say "© OpenStreetMap" is always 
sufficient.

A suitable rule would be:

"if space is so limited that printing '© OpenStreetMap contributors' at 
a legible text size would take an unreasonable amount of space you can 
shorten this to '© OpenStreetMap'"

* "Except for small images, attribution must be visible [...]" - being 
vague here while being precise with the 480 pixel in case of mobile 
applications is remarkable.  But even more remarkable is that there is 
no attribution requirement given for these "small images" - which can 
be interpreted as if no attribution is required for small images at 
all!

* Naturally the section on "Geocoding - Search" would be generic on any 
non-visual interactive applications using OSM data.  Limiting these 
requirements strictly to geocoding is questionable.

* Declaring printing the URL as the only and a sufficient method "to 
make any Person [...] aware that [...] is available under this License" 
in non-digital/non-interactive applications does not seem a good way to 
implement the idea of the license.  Mentioning the license directly (© 
OpenStreetMap - source data available under ODbL) seems a more suitable 
and should at least be an equally allowable method of attribution in 
such cases.

3) Your paragraph about "Machine learning models" is essentially out of 
place in an attribution guideline.  The whole idea of a produced work 
becoming a derivative database is extremely delicate and with various 
issues.  The concept of derivative databases and produced works depends 
on an uninterrupted chain of responsibility from the original database 
via derivative database to produced work.  Interrupting this chain by 
allowing a produced work to be turned back into a derivative database 
essentially breaks the license.

The very purpose of a machine learning system is to generate semantic 
data and a common property of such systems is that when run on the 
training scenario they more or less reproduce the training data.  
Considering this an exceptional use case is highly questionable.

Sneaking this into an attribution guideline is ill-advised IMO.  
It seems this has been looked at purely from the perspective of 
corporate OSM data users and not from the perspective of hobby mappers.  
I see no reason other than corporate greed why machine learning models 
trained with OSM data should not be considered derivative databases.

4) The most obvious practical guideline to fulfill the "reasonably 
calculated" would be that the attribution would need to be designed in 
a way that at least 50 percent of the map users could, when asked about 
the origin of the map they are looking at, quickly and without much 
difficulty point to 

[OSM-talk] Attribution guideline status update

2019-08-09 Thread Simon Poole
As we've mentioned multiple times over the last months, the LWG decided
last year to consolidate all attribution guidance in to one document and
address some of the use cases that have become common over the last 7
years that previously had none. Particularly in the light of the
parallel discussions about attribution on larger social media platforms
we need to make up our minds what we actually want, and define concrete
minimum requirements for acceptable attribution. To not do this just
provides the excuse of pointing to the cacophony of voices all saying
something different. 

We've been working on and off on the document for a while, and are now
largely finished. Going forward we intend to wikify the document and
make it available for public comment together with a BoF session at SotM
next month (which probably means that we'll have to appropriate a coffee
break). You can have a glimpse at the text here
https://docs.google.com/document/d/1e_IQYHtqVivGRw4O4EOn6__-LGMuzPlWz6XKEdAkwW0/edit?usp=sharing
the few things that are not nailed down belong to those that we would
appreciate feedback on.

Simon

PS: the number of coffee breaks permitting we might want to appropriate
another one for the discussion of a tile licence change.




signature.asc
Description: OpenPGP digital signature
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk