I recently started following mediawiki/extensions/Wikibase on Gerrit,
and quite astonishingly found that nearly all of the 100 most recently
updated changes appear to be owned by WMDE employees (exceptions being
one change by Legoktm and some from L10n-bot). This is not the case, for
example, with mediawiki/core.
While this may be desired by the Wikidata team for corporate reasons, I
feel that encouraging code review by volunteers would empower both
Wikidata and third-party communities with new ways of contributing to
the project and raise awareness of the development team's goals in the
The messy naming conventions play a role too, i.e. Extension:Wikibase
is supposed to host technical documentation but instead redirects to the
Wikibase <https://www.mediawiki.org/wiki/Wikibase> portal, with actual
documentation split into Extension:Wikibase Repository
ignoring the fact that the code is actually developed in a single
repository (correct me if I'm wrong). Just to add some more confusion,
there's also Extension:Wikidata build
<https://www.mediawiki.org/wiki/Extension:Wikidata_build> with no
And what about wmde on GitHub <https://github.com/wmde> with countless
creatively-named repos? They make life even harder for potential
Finally, the ever-changing client-side APIs make gadgets development a
pain in the ass.
Sorry if this sounds like a slap in the face, but it had to be said.
I'm a longtime OSM contributor. I like the idea of Wikidata and what I'm
really interested in is a sort of bridge between both projects.
Would somebody be interested in writing a game like application, which
would invoke JOSM Remote Control (JOSM RC) at the coordinates in the
wikidata item and
in the clipboard?
That would make it easier to add such tags to the OSM objects.
I'd like to announce a new Labs tool to show a periodic table
and features several improvements:
* 'tiles' are wider and taller;
* most of them are now provided with a background color (the same as
based on the elements' "subclass of" property
<https://www.wikidata.org/wiki/Property:P279> (the same that powers
* for labels, Wikidata's built-in language fallback is used instead of
just falling back to English;
* a public JSON API <https://tools.wmflabs.org/ptable/api> is
available for everyone!
And some more under the hood:
* rewritten in Python with Jinja2:
o more object-oriented
o presentation is split from actual logic
o less vulnerable to XSS attacks
* a LRU (least recently used) cache with a maximum TTL (per-item
time-to-live) value of 6 hours is used to avoid hitting data sources
on every request;
* both the Wikidata API and Wikidata Query can be used interchangeably
I had to create some items such as Q19753344
<https://www.wikidata.org/wiki/Q19753344> and Q19753345
<https://www.wikidata.org/wiki/Q19753345> to properly categorize
elements. My knowledge of chemistry is limited, so please report/fix
every mistake you can find ;-)
Future plans include:
* oxidation state
* responsive design
* alternative table structures
Hey folks :)
We've been looking into performance issues of the special page
https://en.wikipedia.org/wiki/Special:UnconnectedPages for example).
There are a few improvements we can make to make it work better.
However to evaluate if we can make those changes or not I need to know
what you are currently using this page for exactly.
So if you're using it it'd be great if you could tell me how you're
using it currently to achieve what exactly.
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
I need to know about the possibility of making queries on a Wikibase
instance. I think it is possible to make queries on data on a
particular instance only with external tools at the moment, right?
Thanks for the answer. :)
Luca "Sannita" Martinelli
I started bot of auto-transliterating names of humans, initially with
Persian and English (as a pair) since I know both and I can debug. After
some modifications, In the last check, In more than several hundreds of
edits I checked, I couldn't find any errors, I want to expand this bot for
other languages but before, I need opinions of people who know rules of
transliterating names in these languages, I tried to realize rules and this
is my result but I need someone familiar to confirm
*Chinese: Instead of space it uses "·" character (it's not dot) but order
is the same. e.g Alan Turing is: "艾伦·图灵"
which "艾伦" means Alan and "图灵" means Turing
*Japanese: it's the same but different separator: "・", e.g. "アラン・チューリング"
*Russian: The separator is space character but order is like "FamilyName,
GivenName" e.g. "Тьюринг, Алан"
"Turing, Alan". Handling names with more than two words would be pretty
complicated (I skip them)
*I checked Hebrew and Greek and both are simple languages like Persian,
same order, space as separator.
If you can help me, it would make a great difference in number of labels in
your language. Things you can help are:
1- Confirm or correct rules of these languages and add other rules if
2- Suggest more languages. I thought about Sanskrit, Hindi, and Telugu but
I don't know anyone who can check the rules, if you do, please help me.
3- For any language I will do an initial run just to test, if you can check
edits of the bot (which is pretty easy, e.g. see this
it would be awesome.
Hi, a small question about qualifiers and ranks.
It is well known that the number of planets changed in 2006. Or did it ? Of
course, Pluto is still here, it's just its status that changed. The
definition of planets changed in 2006.
This imply that (imho), the statement "the number of planets in the solar
system in 9" should be deprecated. But infovarius did not agree with me and
changed the rank of the claim back to normal and put an end date. I still
think it should be deprecated, but it raise me a question: How are we
supposed (if we are) to express an information about a deprecation ? Should
we include something about the deprecation in the sources ? Should we have
a qualifier ''deprecation date'' ?
I was lately looking into the use of novalue in wikidata, specifically
in qualifiers and references. While use of novalue in property values is
pretty clear for me, not sure it is as useful in qualifiers and refs.
As we can see, Edwin Mah Lee is the mayor of San Francisco, with end
date set to "novalue". I wonder how useful is this - most entries like
this just omit end date, and if we query this in SPARQL, for example, we
would do something like "FILTER NOT EXISTS (?statement q:P582
?enddate)". Inconsistently having novalues there makes it harder to
process both visually (instead of just looking for one having no end
date we need to look for either no end date or end date with specific
"novalue") and automatically. And in overwhelming majority of cases I
feel "novalue" and absence of value model exactly the same fact - it is
a current event, etc. Is there any useful case for using novalue there?
Another example: https://www.wikidata.org/wiki/Q2866#P569
Here we have reference with "stated in":"no value". I don't think I
understand what it means - not stated anywhere? How would we know to
make such claim? Is a lie? Why would we keep confirmed lies in the data?
Does not have confirmed source that we know of? Many things do, why
would we have "stated in" in this particular case?
Summarily, it is unclear for me that novalue in references is ever useful.
To quantify this, we do not have a lot of such things: on the partial
dump I'm working with for WDQS (which contains at least half of the DB)
there are 14 novalue refs and 13 properties using novalue as qualifier,
leader being P582 with 200+ uses, and overall 422 uses. So volume-wise
it's not a big deal but I'd like to figure out what's the right thing to
do here and establish some guidelines.