Who governs the Solid Protocol today? The Open Data Institute's 2024 stewardship

Not the people who wrote it, and not us. Since October 2024 the Solid project, protocol and community have sat with the Open Data Institute.

What changed, and when

From October 2024, the Open Data Institute, co-founded by Tim Berners-Lee and Nigel Shadbolt, took Solid into its stewardship activities. The project, the protocol and the community moved together, rather than the specification being handed over on its own.

Before that, the work sat with the community group that had carried it since the MIT years.

Why moving a specification to an institution matters

A community group has no institutional continuity. It exists while its participants show up. That is a fine arrangement for exploratory work and a poor one for something organisations are being asked to deploy.

A steward with a legal identity, funding and a remit changes three things: somebody is answerable for the specification's upkeep, there is a place to send a governance question, and the work survives the departure of any individual, including the individual whose name the project is usually attached to.

None of that makes a specification better. It makes it maintainable, which is a different and more boring property, and the one that actually determines whether a standard is still around in ten years.

The observation the artifacts support, and its limit

The specification document's own masthead predates the move.

Version 0.11.0 is dated 12 May 2024 and identifies itself as a community-group report, and the stewardship transition happened five months later. So the document a reader downloads today still names the previous arrangement.

Stated carefully, because this is somebody else's project: that is what the artifacts say. It is not evidence of neglect: a specification is not required to be re-published because its steward changed, and re-publishing has costs of its own. It does mean a reader checking the governance question from the document alone will get the older answer, which is worth knowing before you cite it.

What it is not

It is not a move onto a formal standards track. The document still says of itself that it is not a W3C Standard and not on the standards track, and a change of steward does not change that.

It is not a claim about adoption. The deployment picture is separate and it belongs to other people.

And it is not a change of ownership of the implementations. The reference server remains a community and academic project, the one this surface runs.

Where we sit in this, which is nowhere

We are not a member, a contributor or a steward of anything on this page. We have contributed nothing to the specification, we hold no position in its governance, and our involvement with Solid is that we run somebody else's implementation of it.

A page about governance is exactly where an estate like this would be tempted to imply participation. Our own standing is an entry in a registry, which is a list, and that is a different thing from a seat.

Why a reader should care about the governance question at all

Because "who maintains this in five years" is the question a buyer is actually asking when they ask whether a specification is safe to build on, and it is a fairer question to ask of us than of Solid.