-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Freedom of Panorama info in Nearby #2952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm a user which talked :) I open app on my city (Dnipro, Ukraine) and it shows a lot of places I can photo. If you open corresponding wiki-article you will see it is already illustrated. But even if the user will make a suggested photo, it will be deleted in few days. User will experience bad user experience :) The reason is - no FOP in Ukraine. Probably it makes sence to not show items which don't have FOP or show it with different icon. |
yes, it seems "place state" option can be used. |
Thanks @alcpp , will edit discussion accordingly. |
The restrictive law does not cover Wikidata items such as famous trees,
streets, mountains, ponds, very old buildings and statues, architecturally
uninteresting buildings, etc, right?
Is there a way to know whether an Ukrainian item is forbidden to shoot or
not, using SPARQL?
…On Sat, May 18, 2019, 00:39 neslihanturan ***@***.*** wrote:
Thanks @alcpp <https://github.com/alcpp> , will edit discussion
accordingly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2952?email_source=notifications&email_token=AAAYKBVES2QK6OF3CW6N5C3PV3GSZA5CNFSM4HNVBVBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVVDJWI#issuecomment-493499609>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAYKBQHTM34RWE3KNXBNBTPV3GSZANCNFSM4HNVBVBA>
.
|
I tried to write a query, but I think it would have to be specific for each country, we don’t have the copyright laws of different countries in structured form: # attempt at a query to determine if a Ukrainian monument may be photographed or not
ASK {
BIND(wd:Q25394061 AS ?item) # change item ID here
?item wdt:P31/wdt:P279* wd:Q4989906;
wdt:P17 wd:Q212.
OPTIONAL {
# creator died more than 70 years ago
?item wdt:P170 ?creator.
?creator wdt:P570 ?dateOfDeath.
FILTER(?dateOfDeath < "1949-01-01"^^xsd:dateTime)
}
OPTIONAL {
# monument was installed more than 150 years ago, assume the creator died more than 70 years ago
?item wdt:P571 ?inception.
FILTER(?inception < "1869-01-01"^^xsd:dateTime)
}
FILTER(BOUND(?dateOfDeath) || BOUND(?inception))
} |
Executing this SPARQL query for each item shown on the map, potentially for several countries, would take too much time, but here is a
So I suggest we:
|
I don’t think I agree with that usage of “image: no value”… it works if you interpret P18 as “freely licensed image on Wikimedia Commons”, but it’s not like the item physically cannot be photographed. |
P18 effectively means “freely licensed image on Wikimedia Commons” since no other images are allowed :-) |
"Executing this SPARQL query for each item shown on the map, potentially for several countries, would take too much time," True :) But I was thinking about some automatic properties in each wikidata item at that momment, so proposed to make a script for 1 item. Definetly here should be used script for a list of items. |
A first step with no perfomance issue could be I don't think we should prevent upload or set "no value" in Wikidata, because we can upload the most representative picture we can take that still is legal, for instance a fisheye picture of the plaque of a sculpture, with the sculpture blurred behind the plaque. Example: I took this picture for https://www.wikidata.org/wiki/Q18763693 and it is still there: |
A user at the hackathon talked to me about images being deleted because there is no way to invoke freedom of panorama https://en.wikipedia.org/wiki/Freedom_of_panorama from within the app. Anyone know if this is possible, and if so, how to implement it?
The text was updated successfully, but these errors were encountered: