On 29-04-2021 11:27, Josephine Lim wrote:
Hope you are all safe and well. After having finalized our plans for
WLM integration into the Commons app based on community feedback
, which was
posted to this mailing list a couple of months ago), we have started
work on implementation.
Good to hear you're working on this! One of things I
see on that page is
the mention of the importance of the unique ID. That was always the case
before we had Wikidata. Now every Wikidata item has an unique qID so
that makes the unique identification a lot easier.
We have run into a bit of an issue, however, that we are hoping to get
help with. The initial plan (based on the discussion at
and at the abovementioned wiki page) was to use Wikidata as our data
source, displaying all Wikidata items with the identifier property of
P2186 (Wiki Loves Monuments ID) on our map.
I'll say it a bit stronger than the
other commenters: Don't ever use
P2186 (Wiki Loves Monuments ID). That's the horrible hack/work around
that got introduced for countries that didn't have a well documented ID.
However we have now found out that some countries don't use P2186 at
all. Someone kindly linked
me, and based on that it seems that there is a rather large variety of
identifiers that different countries use.
Realistically speaking, it would be really difficult for us to account
for every possible identifier that every country uses, and it would
also make stability and maintenance much more tricky. We can try, but
it would be risky and tedious.
On the other hand, it was suggested to me that if there is WLM
community consensus that P2186 should be used as a universal
identifier, countries might be willing to adopt P2186 for the sake of
Relic from the past. Usage should be reduced, not expanded.
Does anyone have any thoughts on this?
Why do you need the ID again? What problem are you trying to solve?
Every in scope item should have heritage designation (P1435) on it. You
can just query SPARQL for that with distance or bounding box to get
Also because most (all?) heritage properties need this P1435, it's
usually added as a constraint for which you can query, see
For fun and to show what's possible, a query of all different types of
monuments around the tripoint where Belgium, German and the Netherlands
I'm sure we can figure out a nice scalable solution.