Building new opportunities for both revenue generation and free knowledge dissemination through partnerships and earned income.
|Project||Main page • Principles|
FAQ & Essay (March 2021)
|Technical||MediaWiki • Updates • Phabricator • Git •|
ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯏꯟꯇꯔꯄ꯭ꯔꯥꯢꯁ ꯑꯁꯤ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯐꯥꯎꯟꯗꯦꯁꯟ ꯒꯤ ꯗꯤꯄꯥꯔꯠꯃꯦꯟꯇ ꯀꯌꯥ ꯌꯥꯎꯕ ꯑꯅꯧꯕ ꯊꯧꯔꯥꯡ ꯑꯃꯅꯤ ꯊꯧꯔꯥꯡ ꯑꯁꯤꯒꯤ ꯄꯥꯟꯗꯝ ꯗꯤ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯒꯤ ꯑꯌꯥꯎꯕꯁꯤꯡ ꯕꯨ ꯄꯥꯛ ꯆꯥꯎꯅ ꯁꯦꯟꯗꯣꯡ ꯂꯩꯅ ꯍꯟꯅ ꯁꯤꯖꯤꯟꯅꯕ ꯁꯤꯡꯗ ꯁꯦꯕ ꯇꯧꯅꯕ ꯁꯥꯔꯚꯤꯁ ꯀꯌꯥ ꯁꯦꯝꯒꯠꯅꯕꯅꯤ꯫ ꯊꯧꯔꯥꯡ ꯑꯁꯤ ꯍꯥꯟꯟ ꯑꯣꯀꯥꯄꯤ ꯍꯥꯏꯅ ꯈꯪꯅꯔꯝꯃꯤ꯫
ꯃꯤꯠꯌꯦꯡ ꯑꯁꯤ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯒꯤ ꯀꯟꯇꯦꯟꯇ ꯁꯤꯡꯕꯨ ꯑꯇꯣꯞꯄ ꯃꯑꯣꯡꯗ ꯁꯤꯖꯤꯟꯅꯕ ꯄꯥꯝꯕ ꯂꯨꯞꯁꯤꯡ(ꯑꯣꯔꯒꯅꯥꯏꯖꯦꯁꯟꯁꯤꯡ) ꯗ ꯊꯝꯂꯤ꯫ꯑꯆꯧꯕ ꯆꯥꯡ ꯗ ꯗꯇꯥ ꯁꯔꯚꯤꯁ ꯁꯤꯡ ꯐꯪꯍꯟꯕ ꯃꯗꯨꯗꯤ ꯍꯦꯟꯅ ꯊꯨꯅ ꯊꯥꯖꯅꯤꯉꯥꯏ ꯑꯣꯏꯕ ꯑꯃꯁꯨꯡ ꯆꯦꯛꯁꯤꯟꯅ꯫ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯏꯟꯇꯔꯄ꯭ꯔꯥꯢꯁ ꯅ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯄꯥꯕ ꯁꯤꯖꯤꯟꯅꯔꯤꯕꯁꯤꯡ ꯒꯤ ꯈꯨꯗꯣꯡ ꯆꯥꯕ ꯑꯩꯈꯣꯏꯒꯤ ꯋꯦꯕꯁꯥꯏꯠ ꯁꯤꯡꯗꯒꯤ ꯃꯄꯥꯟꯗ ꯐꯪꯍꯟꯗꯨꯅ ꯃꯤꯑꯣꯏ ꯀꯌꯥꯗ ꯂꯥꯏꯅ ꯌꯧꯍꯟꯗꯨꯅ ꯃꯁꯤꯒꯤ ꯀꯥꯟꯅꯕ ꯑꯃꯁꯨꯡ ꯑꯆꯨꯝ ꯑꯔꯥꯟ ꯈꯪꯗꯣꯛꯄ ꯌꯥꯟꯕ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯒꯤ ꯃꯄꯣꯠ ꯁꯤꯡ ꯍꯟꯅ ꯁꯤꯖꯤꯟꯅꯔꯤꯕ ꯂꯨꯞꯁꯤꯡ ꯗ ꯃꯁꯥꯒꯤ ꯄꯩꯁꯥ ꯊꯥꯗꯖꯗꯨꯅ ꯐꯪꯍꯟꯅꯕꯅꯤ꯫
ꯆꯨꯝꯅꯒꯤ ꯏꯕꯥ ꯁꯦꯝꯗꯣꯛꯄ ꯅꯇꯅ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯒꯤ ꯀꯟꯇꯦꯟꯇ ꯁꯤꯡ ꯗꯥꯇꯥ ꯏꯟꯇ꯭ꯔꯤ ꯗ ꯁꯤꯖꯤꯟꯅꯕꯗ ꯌꯥꯝ ꯋꯥꯡꯕ ꯄꯜ ꯑꯃ ꯂꯩ꯫ ꯃꯁꯤꯒꯤ ꯃꯔꯝꯗꯤ ꯀꯟꯇꯦꯟꯇ ꯁꯤꯡ ꯑꯁꯤ ꯃꯦꯆꯤꯟ ꯁꯤꯡꯅ ꯁꯦꯒꯃꯦꯅꯠ ꯇꯧꯕ ꯑꯃꯁꯨꯡ ꯂꯧꯁꯤꯟꯕꯗ ꯋꯥꯕꯒꯤꯅꯤ ꯃꯁꯤꯅ ꯃꯔꯝ ꯑꯣꯏꯔꯒ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯗꯤ ꯗꯇꯥ ꯁꯤꯡꯁꯤ ꯃꯁꯥꯒꯤ ꯃꯅꯨꯡꯗ ꯅꯠꯇꯅ ꯃꯄꯥꯟꯗ ꯀꯗꯥꯏ ꯐꯥꯎ ꯌꯧꯍꯟꯕ ꯍꯥꯏꯕꯁꯤ ꯏꯊꯤꯜ ꯄꯤ ꯑꯃꯁꯨꯡ ꯃꯁꯤꯅ ꯀꯔꯝꯕ ꯆꯥꯡ ꯐꯥꯎꯕ ꯏꯊꯤꯜ ꯄꯤꯕ ꯌꯧꯍꯟꯕ ꯍꯥꯏꯁꯤ ꯑꯋꯥꯕ ꯑꯣꯏꯔꯤ꯫
In the Movement Strategy recommendations to increase the sustainability of our movement and improve user experience there are the recommendations to, respectively: "Explore new opportunities for both revenue generation and free knowledge dissemination through partnerships and earned income—for example...Building enterprise-level APIs," and "Make the Wikimedia API suite more comprehensive, reliable, secure and fast, in partnership with large scale users.... and improve awareness of and ease of attribution and verifiability for content reusers."
It is well known that a few massive companies use our projects' data. Those companies recognize that without the Wikimedia projects, they would not be able to provide as rich or reliable an experience to their own users. There has long been a feeling among community members that these companies should do more to reinvest in the Wikimedia communities for the benefits they gain from the content and resources they use.
This led to the idea of developing a new approach that is more sustainable in the long term and provides a much clearer relationship between Wikimedia and enterprise users. Most financial benefit for Wikimedia would likely only come from a very small handful of heavy for-profit users, and would feed back into the Wikimedia movement.
As this idea developed, it became clear there is a responsibility to democratize our data for organizations that do not possess the resources of these largest users, to ensure we are leveling the playing field and helping to foster a healthy internet without reinforcing monopolies. The benefits of such a service shouldn't just be for startups or alternatives to the internet giants, but also for universities and university researchers; archives and archivists; along with the wider Wikimedia movement.
Wikimedia Enterprise’s focus is on businesses that reuse our content, typically at a large scale—e.g., integrated into knowledge graphs, search, voice assistants, maps, news reporting, community tools, third party applications, and full-corpus research studies. Augmenting Wikimedia's many datasets to put structure behind our unstructured content will allow all our content reusers to meet their individual requirements while also setting us up to build new tools and services in the future, available to everyone. Reusers of our content are looking for three critical components:
- ꯇꯣꯏꯕꯒꯤ ꯆꯥꯡ: ꯆꯥꯡ ꯅꯥꯏꯅ ꯂꯧꯕ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯊꯧꯔꯥꯡꯁꯤꯡꯒꯤ snapshots
- ꯊꯥꯖꯕꯒꯤ ꯆꯥꯡ: ꯃꯔꯨꯝ ꯊꯨꯞꯄ ꯌꯥꯕ,ꯂꯥꯏꯅ ꯐꯪꯕ ꯏꯅꯐ꯭ꯔꯥ ꯏꯁꯇ꯭ꯔꯛꯆꯔ
- ꯃꯒꯨꯜ: “ꯈꯋꯥꯏꯗꯒꯤ ꯐꯕ ꯏꯅꯧ ꯅꯧꯕ ꯁꯦꯝꯒꯠꯄ”
Emphasizing a self-funding set of specific use cases allows the Wikimedia API team to focus on volunteers, teams, and organizations looking to access (and, most importantly, interact with) our data sets. This includes the majority of community editing tools, which will be out of scope for this service. For more information on improvements to the existing Wikimedia APIs see the service page on the "API Gateway" initiative.
- Content: Make more of our movement's content available in consistent machine-readable formats, freely available for all researchers and re-users.
- Resource-load: Reduce the need for high-intensity site-scraping by the highest-frequency and highest-volume reusers, which currently target our production servers.
- Fundraising: Provide a clearer and more consistent way for the largest re-users to reinvest derived benefits back to the movement, instead of making occasional altruistic donations that vary in size.
Contact the team if you would like to arrange a conversation about this service with your community, at a time and meeting software platform of your choice.
Past public meetings:
2021 March #1
2021 March #2
Following are the introduction paragraphs for a much more detailed Community essay.
Libre and Gratis are the two meanings of “free,” commonly phrased as free as in speech, or free as in beer.
Wikimedia projects are, have always been, and will always remain libre. The principles of free cultural works mean that anyone can use Wikimedia without restriction, including commercially. As a movement, we embrace this. It is why we reject ‘non-commercial’ licenses, as they would limit the kinds of reuse possible. And it is why we consider commercial reuse an important means of distributing knowledge to audiences.
Equally, Wikimedia projects are, have always been, and will always remain gratis. The ability to freely access the knowledge available across all Wikimedia projects has always been core to the mission of the Foundation and the movement. We provide this access not only to individuals visiting our websites but also programmatically to machines so that our content can be repurposed in other environments. The full corpus of Wikimedia content always has been, and will continue to be, made available for reuse in various forms (including but not limited to database dumps, APIs, and scraping) at no cost.
As a result, our content is often repurposed by for-profit organizations that rely on it to support their business models, and which consequently earn revenue from it. Outside of voluntary corporate donations to the Wikimedia Foundation, the movement has never received benefits from any of this revenue through return investment. In acknowledgement of this, under the heading of Increase the sustainability of our movement the Movement Strategy process asked the Wikimedia Foundation to explore, among other things, “enterprise-level APIs...models for enterprise-scale for-profit reusers, taking care to avoid revenue dependencies or other undue external influence in product design and development.” Furthermore, under the heading Improve User Experience, a further recommendation stated, "Make the Wikimedia API suite more comprehensive, reliable, secure, and fast, in partnership with large scale users where that aligns with our mission and principles, to improve the user experience of both our direct and indirect users, increase the reach and discoverability of our content and the potential for data returns, and improve awareness of and ease of attribution and verifiability for content reusers."
The Enterprise project team is developing a new resource aimed at for-profit content reusers, who have product, service, and system requirements that go beyond what we freely provide. Use of this offering will not be required for for-profit content reuse; companies can continue to use the current tools available at no cost. All Enterprise API revenue will unequivocally be used to support the Wikimedia mission—for example, to fund Wikimedia programs or help grow the Wikimedia Endowment.
This project represents a new kind of activity at the Foundation. The project is at a very early stage that should be considered a learning period. We will have successes, we will make mistakes, and we will need to adapt our strategies. The team is committed to listening, engaging, and where possible, integrating the feedback we get on our work. This document is organic and is reflective of the team's current thinking; we are attempting to document as much work as possible in the open. Up until now, our work has been shaped by a series of initial interviews with community members, Wikimedia Foundation Board and staff, researchers, and reusers.
Given the nature of the service, primary decision making for it will rest with the Wikimedia Foundation. We are seeking community input, in particular from the technical community and those who have been involved in the strategy process, throughout the lifetime of the service. Technical feedback has been gathered from colleagues at the Wikimedia Foundation, industry and research partners, technical partners across the movement, and with the broader technical communities via Phabricator. Input into the funding development side of the service will follow a similar pattern. We will continue gathering input via research interviews and focus groups, as well feedback here on Meta as per our principles.
Over time, the "product" being offered will grow and improve. We are still defining the exact nomenclature for API endpoints and documentation, but these are the main products that our team is currently building. This information is accurate as of Version 1.0.
Structured Content API
High-volume reusers that use an infrastructure reliant on the EventStream platform depend on services like RESTBase to pull HTML from page titles and current revisions to update their products. High-volume reusers have requested a reliable means to gather this data, as well as structures other than HTML when incorporating our content into their KGs and products.
Wikimedia Enterprise Structured Content API, at release, will contain:
- A commercial schema
High-volume reusers currently rely heavily on the changes that are pushed from our community to update their products in real time, using EventStream APIs to access such changes. High-volume reusers are interested in a service that will allow them to filter the changes they receive to limit their processing, guarantee stable HTTP connections to ensure no data loss, and supply a more useful schema to limit the number of api calls they need to make per event.
Enterprise Firehose API, at release, will contain:
- Filtering of events by Project or Revision Namespace
- Guaranteed connections
- Commercially useful schema similar* to those that we are building in our Structured Content API and Bulk API
*We are still in the process of mapping out the technical specifications to determine the limitations of schema in event platforms and will post here when we have finalized our design.
For high volume reusers that currently rely on the Wikimedia Dumps to access our information, we have created a solution to ingest Wikimedia content in near real time without excessive API calls (Structured Content API) or maintaining hooks into our infrastructure (Firehose).
Enterprise Bulk API, at release, will contain:
- 24-hour JSON*, Wikitext, or HTML compressed dumps of "text-based" Wikimedia projects
- A hourly update file with revision changes of "text-based" Wikimedia projects
*JSON dumps will contain the same schema per page as the Structured Content API.
To obtain access to the Enterprise API datasets, there are three methods:
- ꯄꯩꯁꯥ ꯄꯤꯒ꯭ꯔꯦ
- Realtime API (Batch and Streaming) Through the dedicated Enterprise API product website at https://enterprise.wikimedia.com/
- Creating an account via the project's website also includes a no-cost trial period of access. Wikimedians who have a mission-relevant use-case for continued access to the official service that cannot be fulfilled via existing methods, or those listed below, can request continued no-cost access.
- ꯁꯦꯜ ꯇꯤꯡꯗꯦ
- Snapshot API An update of the Enterprise API data is provided for all every two weeks at https://dumps.wikimedia.org/other/enterprise_html/
- Snapshot API + Realtime (Batch) Via Data services, available to anyone with a Wikimedia cloud services account.
The Wikimedia Foundation staff who work specifically on this project:
Names in bold indicate management.
Many people from different teams also contribute significantly, including from the WMF Legal, Engineering, Partnerships, Design, Communications teams etc. Additional contract work provided by: Speed & Function are providing engineering support; Boldr provide customer support services; Vuurr are assisting our sales process; and Super Natural Design are the designers of the project website.
The board of the LLC overseeing the project are from Wikimedia Foundation leadership, representing their Wikimedia Foundation staff roles. This includes the Chief Advancement Officer Lisa Seitz-Gruwell; General Counsel Amanda Keton; Chief Technical Officer [position currently vacant], and Lane Becker who serves as the LLC's president. Ultimately, the LLC is subject to the governance of the Wikimedia Foundation Board of Trustees as described at the Wikimedia Foundation Board Statement on Wikimedia Enterprise revenue principles.
Documents covering the legal relationship of the LLC to the Wikimedia Foundation are published on the Governance Wiki under "Category:Wikimedia Enterprise". Specifically, these are the operating, cost-sharing, and inter-company licensing agreements.The LLC's legal registration can be found at the State of Delaware, Division of Corporations, Entity name: Wikimedia, LLC, File number: 7828447.
|Commercial launch - October 2021|
Wikimedia Foundation Press release
|First customers - June 2022|
- API:Main page – the central listing of all Wikimedia APIs.
- Wikitech: Data Services portal – A list of community-facing services that allow for direct access to databases and dumps, as well as web interfaces for querying and programmatic access to data stores.
- Enterprise hub – a page for those interested in using the MediaWiki software in corporate contexts.