Page MenuHomePhabricator

Expose new split sparql endpoints in api
Open, Needs TriagePublic

Description

Today the siteinfo api call only exposes the old (and now partial) sparql endpoint (though wikibase-sparql) it should instead expose both of the new endpoints (https://query-scholarly.wikidata.org/sparql and https://query-main.wikidata.org/sparql) in order for downstream tooling (such as pywikibot) to be able to provide access to them.

Event Timeline

Lydia_Pintscher subscribed.

Thanks for raising this. I had totally forgotten about that.
Do we know how many tools, etc assume that there is only one value there? How much and what are we going to break?
I'd love to get some more input from people here.

Also can someone clarify what the connection between the siteinfo API information and Wikibase Manifest is here?

I don’t know where Wikibase Manifest gets its info from, but the response in the siteinfo comes from $wgWBRepoSettings['sparqlEndpoint'] FWIW.

See also T369079 and T374021 where we made WikibaseQualityConstraints use both SPARQL endpoints (via an additional config variable, so that the existing one still only contained a single string).

Gehel subscribed.

Discovery-Search will be watching, but expecting WMDE to drive the change.

Also can someone clarify what the connection between the siteinfo API information and Wikibase Manifest is here?

I don’t know where Wikibase Manifest gets its info from, but the response in the siteinfo comes from $wgWBRepoSettings['sparqlEndpoint'] FWIW.

Looks like WikibaseManifest gets it from $wgWBRepoSettings['sparqlEndpoint'] as well: ConfigExternalServicesFactory.php#9
But it can also be manually specified / overridden with $wgWbManifestExternalServiceMapping: Extension:WikibaseManifest#External_services