Wow, this looks awesome! Thanks a lot for working on this!

I think the configuration model could use some more documentation, but in principle I’d say it looks pretty reasonable. It’s also probably powerful enough for most reasonable needs (I read “XPath” and my eyes lit up :D ).

As for which APIs should be exposed: one thing I can remember that was felt as missing from WDQS several times is access and historical data, so I think that exposing action=query with prop=pageviews and prop=revisions might be useful.

Cheers,
Lucas

On 27.04.2017 23: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,

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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

Reply via email to