This page contains the roadmap for the Linked Open Data (LOD) ecosystem in 2026 (Wikidata, Wikibase Suite, Wikibase Cloud). Quarterly estimates will be added at the start of each quarter; currently only Q1 items are listed.
Strategic outcomes and Q1–Q4 activities
Stability, sustainability, and scalability of infrastructure has improved to ensure the long-term resilience and thriving of the Wikibase ecosystem
Reduce the size of the recent changes tables on the clients by reducing the amount of changes from Wikidata
Work with an external partner to find possible improvements to Wikidata’s data storage
Q2
Q3
Q4
The distributed Wikibase ecosystem is more sustainable because of clear data governance policies, increased feature parity, and interoperability/smooth transitions across products
Agree on the solution to the workflows implementing the Wikibase Cloud hosting policy and plan the pilot phase of the process
Ensure that REST API and default language codes were correctly enabled on Wikibase Cloud as a result of the update to MW 1.43 that happened last quarter
Q2
Q3
Q4
The communities of the Wikibase ecosystem continue to grow
Prototype and test a new Wikibase discovery service
Q2
Q3
Q4
Wikimedia editors have better awareness, understanding, and tools to monitor and manage Wikidata’s impact on their projects
Q1
Support the infrastructural foundations for Wikidata use in other Wikimedia projects by further reducing the size of the recent changes tables in the database, to ensure that editors can rely on the Recent Changes and Watchlists of their wikis to help keep the content they care about in shape.
Support Wikidata use in other Wikimedia projects by reducing recent changes to database table size, ensuring editors can rely on their wikis’ Recent Changes and Watchlists pages to maintain content.
Wikidata edits can affect client wikis content but be hidden to editors due to user settings. We will make this setting an opt-out to increase visibility/transparency of changes due to Wikidata edits.
Q2
Q3
Q4
Movement or movement-adjacent partner groups outside Europe and North America have the resources and capacity to carry out technical initiatives that strengthen the Wikibase ecosystem communities and foster digital skills development
Q1
Looking into further possibilities to provide resources to Movement or movement-adjacent partner groups
Q2
Q3
Q4
The ability to federate knowledge across instances has improved, creating a viable path for taking load off of Wikidata
Q1
Ontology federation: making it possible to use Wikidata’s Items as values in statements on other Wikibase instances (demo session) and enable a public test version for the community
Agree on a way to reduce the number of non-operational endpoints on the Wikidata Query Service allowlist
Q2
Q3
Q4
Users holding and contributing marginalized knowledge find the Wikibase LOD ecosystem (Wikidata, Wikibase Suite, and Wikibase Cloud) attractive for their use cases
Q1
Implement a way for Wikibase Cloud users to indicate that their instance contributes to knowledge equity
Publish 2 more showcases of holders of marginalized knowledge using Wikibase Cloud for their use cases
Conduct internal workshop, begin continuous interviewing, identify and prioritize research needs towards understanding and furthering knowledge equity
Attend FOSSASIA to present ‘Building Bridges: How Open Linked Data Connects Communities’
Q2
Q3
Q4
We have made Wikibase self-hosting operations more accessible, robust and easier to manage, fostering project success
Q1
Through user tests we have identified issues and barriers along the Wikibase Suite installation process. We will address them in Q1: Installation guide, domain setup and environment settings
Q2
Q3
Q4
We offer new and/or improved access methods and they are increasingly used
Q1
Improve the technical infrastructure behind Wikidata dumps
Start UX research into improving documentation for reusers
