The same processes that keep *.wikipedia.org up to date *should* work with *.wikidata.org -- eventually, it is the same software underneath.

The API is not going to change within the close future. In mid-term, I expect the Wikidata APIs to evolve together with the underlying Mediawiki API, but we will not devote resources to this in this month. Currently, the last month of the initial development has started, and we need to finish a few other things first.

And as Yuri says, the changes to the API are planned to be backward compatible, anyway.

So, in short, for real time data, the API is the right approach, as described here: <http://www.wikidata.org/w/api.php>

For keeping a mirror, the methods used for Wikipedia should be applicable to Wikidata too.

Cheers,

Denny

2013/3/5 Jiang BIAN <bianjiang@google.com>

Thanks Jeroen for your confirmation.

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?

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.

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?

> Are the APIs above ("action=query&prop=revisions" and "actioon=query&list=recentchanges") the supported way to retrieve wikidata.org in realtime?

I suspect this is your best bet for now. We have a mechanism for change propagation to mirrors, though right now the only implementation on top of this that we have is WMF specific. Volunteers and third parties can however create their own implementation suitable for non-WMF use.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--

_______________________________________________
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l

--
Jiang BIAN

This email may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it went to the wrong person. Thanks.

_______________________________________________
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l

--
Project director Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. +49-30-219 158 26-0 | http://wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.