vrandecic

No. A global encyclopaedia might be global, but does not have to be imperialist, if the control over the content and the ability to contribute to the encyclopaedia is not limited to imperial structures.

Unless you equate "global" with "imperialist", in which case your statement is true by definition. But then everything that is done on a global scale is necessarily imperialist, and then one of the two terms does not seem useful anymore.

Equity can be global.

That would require the equation to be wrong.

As planned, with our first scheduled weekly deployment, the JSON object is not being displayed anymore.

Sine the wiki hasn't been opened for editing yet, there is indeed only one function that has visible implementations (which was added for testing purposed): https://www.wikifunctions.org/view/en/Z10000 - all others are built-in and then invisible.

The two implementations are in Python and JavaScript (and rather trivial): https://www.wikifunctions.org/view/en/Z10004 https://www.wikifunctions.org/view/en/Z10005

This particular work is mostly funded through a set of large restricted donations, not through the general funds.

exactly that! I have a design mockup that is quite similar to that.

Thanks, that's really helpful to read! The page is still in a very early stage. You are right, the current object section is just confusing, we will remove it.

Maybe a better start to understand what Wikifunctions does - but it is a very simple example too - is this function: https://www.wikifunctions.org/wiki/Z10000

The other functions that you found randomly are currently not well supported.

We are working on it, to make it less confusing. Such feedback is very helpful.

I have a half hour YouTube video on that topic, maybe you'll find it interesting, but likely too long: https://www.youtube.com/watch?v=WqYBx2gB6vA

Thank you for the follow up. I updated my post a little, mostly with a link to this discussion, as it contains and explanation of the query, and now also links to tutorial.

I agree with some of your suggestions on making the system easier to use. It's open source, and I hope someone will be motivated enough to give it a try - the development team can only do so many things, unfortunately.

Thanks again for the constructive comments!

Thanks for the answer!

I got the query wrong (reason: https://twitter.com/vrandezo/status/1430206988177219593 )

Here's the corrected query: https://w.wiki/3x8u

This includes a few more thousand results.

AKG does show up (but has indeed no connection to Anguganak), ALZ shows up (again, without a connection to a city). Article pages are not a requirement for the data to be in Wikidata.

I see your point. The duplicate entries can often be explained (e.g. ABQ is indeed the IANA code both for Albuqerque Sunport and the Kirtland AF Base, which are adjacent to each other), but that's already a lot of detail.

If a single table provides the form of clean data one is looking for, that's great and should be used (and slightly different than the original question that triggered this, where we had to go through many different pages and fuse data from thousands of pages together). Different tasks benefit from different inputs!

I hope this helps with getting started: https://w.wiki/3x3n

And here's a visualization on a map, using geocoordinates: https://w.wiki/3x3g

I'd suggest that in this case one should consider using MusicBrainz, in order to get more comprehensive and better results than either with Wikidata or Wikipedia.

Sounds a lot like DBpedia to me

That would be a bug and should not be the case. I just tried it and couldn't replicate it. There is no difference between 7-7-2000 and 07-07-2000 in xsd, and neither in the SPARQL query endpoint.

Here are the people in Wikidata born on 07-07-2000: https://w.wiki/3wrj

And here the people born on 7-7-2000: https://w.wiki/3wrk

The results are identical.

(This doesn't mean we have no duplicates at all in Wikidata - the post actually mentions five discovered duplicates within Queen Elizabeth II's ancestors. But these are entities, not within the datatypes)

Wikidata's API doesn't require registration, credentials, etc.

There are plenty of Wikidata users who have learned some SPARQL without being programmers.

Thank you. I am the author of the post, and appreciate your comments, and I agree with them.

I have to say that it indeed wasn't my intention to show how to get to the query - that is a form of tutorial that would be great to write too, agreed, and maybe I should have. What I wanted to write is just comparing the results of the two approaches.

Having said that, yes, again, I agree, a tutorial on describing how to get that data would be great too, and maybe I should write it, maybe someone else should. I agree that it is not trivial at all how to get to the query (and that is a particularly tricky query, certainly not what I would begin with).

Thank you again for your comment, it made me think and mull over the whole thing more. I will talk tomorrow with the lead of the Wikidata team, and I will bring these (and many other points that were mentioned in the last few days) with me. It will take a while, but I hope we can improve the situation.

I found that work very interesting. So I downloaded the data by OP (thanks for publishing it!) and compared it with Wikidata. The results are here:

http://simia.net/wiki/Main_Page