Page MenuHomePhabricator

Create a WDQS-based ElementProvider
Closed, ResolvedPublic


To eventually replace the WDQ-based one.

Event Timeline

Ricordisamoa raised the priority of this task from to Needs Triage.
Ricordisamoa updated the task description. (Show Details)
Ricordisamoa added a subscriber: Ricordisamoa.
Restricted Application added a project: Wikidata. · View Herald TranscriptDec 31 2015, 6:04 PM
Restricted Application added subscribers: StudiesWorld, Aklapper. · View Herald Transcript

Change 315671 had a related patch set uploaded (by Ricordisamoa):
Add and use SparqlElementProvider

@ArthurPSmith do you think there's still need for WDQ-based implementations?

Change 315671 merged by jenkins-bot:
Add and use SparqlElementProvider

Ricordisamoa closed this task as Resolved.Oct 14 2016, 3:38 PM
Ricordisamoa removed a project: Patch-For-Review.

Now deployed and working.

I see you've closed - looks good by the way. Anyway, on the question of
retaining WDQ - no I don't think that's necessary, I think Magnus would
like to shut it down eventually. I don't see that WDQ adds anything to this
tool now SPARQL is working reliably, it's fast and stable. So feel free to