Hi Stas, This is *really* exciting news -- thank you so much for your work on this.
I can see it being valuable in so many ways -- the kind of things that people have put tickets in for so far, eg categories, image sizes, page stats etc, are just the tip of the iceberg.
One question: were there particular reasons why you went for wrapping a SERVICE round the Mediawiki API, rather than eg a SPARQL layer round the SQL tables, suitable for SPARQL federation?
Are there efficiency issues? Or did you think that the SERVICE approach was simply more user-friendly for the most commons APIs ?
-- James. On 27/04/2017 22:40, Stas Malyshev wrote:
Hi! I am developing functionality that will allow WDQS query to get data from Mediawiki API [1]. Currently, the design is as follows: - The API should have a pre-defined template - The template also specifies which results are available from the API The need for template is currently because we need to convert data from API's treelike format to tabular format that SPARQL needs, and the template allows to specify how the conversion is done. See https://www.wikidata.org/wiki/Wikidata:WDQS_and_Mediawiki_API for detailed description of how it works. The prototype implementation is running on http://wdqs-test.wmflabs.org/ (only Categories API described in the page above is configured now, but more will be soon). I'd like to hear feedback about this: - does template model make sense at all? Is it enough? - what APIs would we want to expose? - any other features that would be useful? Other comments and ideas on the matter are of course always welcome. Please comment on the talk page[2] or reply to this message. [1] https://phabricator.wikimedia.org/T148245 [2] https://www.wikidata.org/w/index.php?title=Wikidata_talk:WDQS_and_Mediawiki_API&action=edit Thanks,
_______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
