Page MenuHomePhabricator

Rediscover, review, and update the federation input process for WDQS
Open, HighPublic5 Estimated Story Points

Description

As a user of WDQS, I want to have an easy way to submit additional federation endpoints.

As an operator of WDQS, I want to have a simple process that provides flexibility but also protects the service from abuses.

https://www.wikidata.org/wiki/Wikidata:SPARQL_federation_input has been marked as inactive. Some dicussion around this topic: https://lists.wikimedia.org/pipermail/wikidata/2020-March/013929.html

We need community input on the process, the Search Platform team should not be in charge of deciding which request make sense and which does not.

We don't have a good understanding of the cost of federation from the WDQS perspective, we want to make sure there are no negative impact.

AC:

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Currently another way is to create a Phabricator task for each request of federation endpoint.

I created a discussion on the wikidata project chat for defining the community side of the process.

TJones renamed this task from Review the federation input process for WDQS to Rediscover, review, and update the federation input process for WDQS.Oct 26 2020, 6:34 PM
CBogen set the point value for this task to 5.Feb 1 2021, 4:42 PM
Gehel triaged this task as High priority.Dec 16 2021, 1:33 PM
MPhamWMF subscribed.

I am still a little bit puzzled about what this needs to get forward. Is it a community process or WMF search team actions?

If it is a community discussion, could the process just:

  • Data in the endpoint needs to be openly licensed (CC-BY, CC0, CC-BY-SA, ODbL ... )
  • create a phabricator ticket for enabling the endpoint for federation