In another maillist, Yuri pointed me Wikidata API roadmap. I don't know with those changes, if my current use ("action=query&prop=revisions" and "action=query&list=recentchanges") will be supported?

We don't plan to break stuff just for the sake of breaking it :) Will try to keep everything backwards compatible for some time, with the exception of any security or major performance issues we might discover.

Some more background:

We are already using same way (polling recentchanges, and querying latest revisions) to maintain our internal mirror of *.wikipedia.org, *.wiktionary.org in sync. We expect to have similar (same) way to to maintain wikidata.org. According to my experiment, it works fine so far.

To be discussed of the list.

On Tue, Mar 5, 2013 at 1:25 AM, Jeroen De Dauw <jeroendedauw@gmail.com> wrote:

Hey,

> There are some ids like "dewiki", "enwiki" etc, which I guess can be
> interpreted to corresponding languages "de", "en" respectively. But is there
> a reliable map from these *wiki to the language code? And some are even
> using 3-letter prefix, e.g. gotwiki, xmfwiki.

You cannot infer the language from the site identifier. "enwiki" is a site identifier. The software allows having multiple sites for the same language. For instance you could have an entity that is also described on the English Wikitionary. Or an entity described on a third party website as well, such as a movie on imdb. Unfortunately it looks like we are not yet providing an actual API for accessing this information.

@Yuri, do you have plan to implement some API to return such mapping?

I personally wasn't planning on doing it just yet, but it should be done as part of our migration from the interwiki sql table to the sites one (at least that's what i have been told). For now, if you run http://en.wikipedia.org/w/api.php?action=sitematrix the dbname seems to match the site most of the time if not always.