Once T128040: Document and implement the REST API format versioning and negotiation policy is resolved, there will be on-wiki documentation about this.
- Mentioned Here
- T128239: Google: Add Accept: header to your HTML requests to RESTBase/Parsoid as per T124365
T71870: Enable DOM editing of transclusion parameters
T124365: RFC: Define a policy for REST API result format versioning / negotiation
T128040: Document and implement the REST API format versioning and negotiation policy
@Jdforrester-WMF: Accept headers are used for response versioning / negotiation per entry point, but they aren't meant to be used for the selection of fundamentally different resources. Arguably wikitext and HTML versions of data-mw are falling somewhere in between, but I think there are several advantages in exposing those as separate resources, including documentation and the ability to directly link to the latest format of each.
All but google have updated their clients to send the Accept header. Google is waiting for the Accept header to actually be used, so we shouldn't block on them.
Resolving for that reason.
As mentioned on the task, https://www.mediawiki.org/wiki/API_versioning#Content_format_stability_and_-negotiation sets out the policy.
We don't implement format conversions for current minor changes, but *will* provide a conversion for the upcoming major change. By providing a version now, you get control over when you upgrade to the latest format after it has been released.